Lowyat.NET: Latest topics by DJFoo000

[WTS] Garmin Instinct (Yellow)

DJFoo000 — Wed, 12 Jan 2022 12:52:09 +0800

Item(s): Garmin Instinct (Yellow)

Package includes: Original Box and Accessories

Price: RM 700

Payment method: Bank-in.

Warranty: Unsure.

Dealing method: COD (preferred) or postage

Location: Puchong Jaya

Contact method/details: PM
---

Item(s) conditions: Like New, Sealed box.

Reason for sale: Received as gift.

Picture:

[WTS] Burnout Paradise: The Ultimate Box (steam)

DJFoo000 — Thu, 19 Dec 2013 14:49:56 +0800

I have one (1) steam code for Burnout Paradise: The Ultimate Box.

Price on steam: USD19.99

My selling price: RM50.

Method of contact: PM

Reason for sale: received as gift.

[WTS] Logitech Wireless Keyboard K270

DJFoo000 — Wed, 26 Jun 2013 21:52:16 +0800

Item(s): Logitech Wireless Keyboard K270

Package includes: Keyboard, USB wireless adaptor, 2 units AAA battery. NO BOX

Price: RM50 (Retail RM70)

Warranty: None

Dealing method: COD

Location: Puchong Jaya

Contact method/details: PM
---

Item(s) conditions: No sign of wear. Barely used.

Picture:

Reason for sale: Spring cleaning

[WTS] Used - Aztech Wireless-N USB 2.0 Adaptor

DJFoo000 — Wed, 19 Jun 2013 01:33:53 +0800

Item(s): Aztech WL552USB Wireless-N USB 2.0 Adaptor

Package includes: Adaptor, set up CD.

Price: SOLD

Warranty: None.

Dealing method: COD preferred.

Location of seller: Puchong, Klang Valley

Contact method/details: PM

Age of item: 2 years, but hardly use.

---

Item(s) conditions: Like new. Only used once. Was desperate to diagnose laptop WiFi card problem.

Picture:

Reason for sale: Spring cleaning.

Learn Korean books

DJFoo000 — Wed, 19 Jun 2013 00:54:14 +0800

Item(s):
1) Korean for Dummies
2) Korean for Beginners

Package includes: CD

Price:

1) Korean for Dummies - RM 60 (Retail RM83.80)
2) Korean for Beginners - RM 50 (Retail RM70.00)

Take both for RM 100 (Retail RM153.80).

Warranty: None.

Dealing method: COD

Location of seller: Puchong, Klang Valley

Contact method/details: PM

Age of item: Less than 1 year.

---

Item(s) conditions: Used. No torn pages, no stains, no creases.

Picture:

Korean for Dummies Preview: http://imageshack.us/a/img842/4894/jxhb.jpg

Korean for Beginners preview: http://imageshack.us/a/img16/6682/6uxz.jpg

Reason for sale: Spring cleaning.

[WTS] Nexus 7 16GB

DJFoo000 — Tue, 25 Dec 2012 22:34:19 +0800

Item(s): Nexus 7 16GB US set

Package includes: tablet, box, charger (US), USB cable

Price: SOLD[/b}

[b]Warranty: Left 2 months.

Dealing method: Cash on delivery.

Location of seller: Puchong

Contact method/details: PM

Age of item: 10 months.

---

Item(s) conditions: Like new. No visible cosmetic defect. Tablet is running custom ROM CM10.1 (Android 4.2.2). Can flash to factory image and relock bootloader upon request.

Picture: It looks just like any other Nexus 7. You look at it when we meet, then only finalise the deal, ok? You can't tell a lot from a picture on the monitor anyway.

Reason for sale: funding for laptop.

Android Fragmentation: Is it really an issue?

DJFoo000 — Mon, 26 Dec 2011 11:06:26 +0800

In this article, I am going to offer an alternative view on the issue of ‘fragmentation’ in the Android mobile OS. It’s a little long so be prepared for the long ride.

The article is intended for anyone with some concept about the 'fragmentation' phenomenon in the Android OS. It is written with the layman in mind, so please forgive the occasional dumb-ed down explanations.

Disclaimer: Many technical aspects of this article may be factually inaccurate as the article is done based on my understanding of the whole situation. I’m only an Android enthusiast whose depth in playing with Android is flashing ROMs and nothing else.

Introduction

Ever since the inception of the modern smartphone days (defined as post-iPhone (2007) for the purposes of this article), there has been a lot of attention on the versioning of a mobile OS, and also the applications support on them. Specifically, there has been a lot of talk about this ‘fragmentation’ issue with the Android OS. Apparently, not all Android phones are created equally, as some apps cannot run on others, and some phones update faster than others. This ‘fragmentation’ has been used as a major point in dismissing Android phones in favour of the iPhone when a comparison is made between two said platforms.

History lesson

To explain things, we need to delve into the history of modern mobile phones (phones with color screens). In the glory days of Samsung, Sony Ericsson and Nokia feature phones, they all designed in-house each and every OS on each and every phone they sell. This brought about a type of OS called the Proprietary Software. It isn’t really a standard OS, but rather a category of OS where the software are made in-house and are incompatible with one another (hence proprietary). Software and applications had to be designed specifically for each phone for them to work properly. A majority of these phones support Java’s J2ME platform of software, which meant that if a game is made with J2ME (usually with the extension .jar), it can probably run on a majority of the feature phones running proprietary software. This meant that while the SMS feature on one J2ME-capable phone is not the same as the other, they will most probably run the same .jar applications or games just fine.

[The average user probably doesn’t even know the type of application their phones can run. If you used a Nokia feature phone with color screen (6230, 6300 and etc), it was running Nokia S40 and it supports .jar files. If you had a Sony Ericsson feature phone with color screen (W800i, K700, K800 and etc), it will also most probably run .jar files. These two brands are the only ones that I know for sure has support for .jar files.]

The problem with .jar files is that they are screen resolution-restricted. Most .jar games do not scale with screen resolution. Often times I find myself installing a .jar game that only runs in the upper left corner of my Nokia 6630 (yes it’s a smartphone, running Symbian S60, which isn’t a feature phone, but it supports .jar files. I’ll get to that later) because it does not scale to the entire screen. From time to time I do find .jar apps that do scale with screen resolution (I switched to an SE W810i after 2 years. Whether it’s a downgrade or not is up to debate ;-) ).

In another mobile operating system parallel universe, we have the smartphones. The more popular ones are Windows Mobile (by various OEMs), and Symbian (predominantly Nokia). Needless to say their apps are not compatible with each other (much like Mac OS and Windows, but I’m not getting into that). WinMo runs .cab files, while Symbian runs .sis files. They both do support .jar files, but to varying degrees, most notably when in games that do not utilize touchscreens (which is most .jar games), it’s almost impossible to play on a WinMo touchscreen smartphone (as in the case of me transferring a .jar game (installation file) to a friend’s HTC Touch 3G. And yes, we can transfer games to people via Bluetooth last time.)

Now you’d say that if all phones then (with color screens) can support .jar games and applications, why don’t everyone make applications in .jar format? The problem lies in the types of apps that can be made using J2ME. This is the reason why smartphone specific games like those in the .cab and .sis formats are richer in graphics and gameplay.

Arrival of Android

With the history lesson out of the way, we shall now dive back into the modern world of Android smartphones. The history lesson was needed because I will be making tons of references to aspects of the ‘old’ phones.

Android’s arrival aims to create a common software platform for devices (besides the fact Android enables Google to enter the mobile device market). Android gives the ability to OEMs to take an existing bunch of codes and apply onto any hardware variation they want. Android’s beauty lies in the ability to make a phone as simple or as feature-full as an OEM wants. And hence starts the Android revolution in phones (it can both be a feature phone, or a smartphone).

Now you see, the way Android is supposed to work is that an OEM takes the source code from the Android repository, modify it to make it technically their OS, and put it into a device. So although Android is the common backbone of all the Android-based devices out there, technically each Android iteration running on each device should be considered individual OSes, since the software running on an OEM device is that particular OEM’s derivative of the same source code. The beauty of all this deriving is that they all support the Android application format, the .apk format. Applications that are contained in a .apk container can be installed on any Android-based device (assuming all things equal).

The benefit of this is that now, OEMs do not have to put in as much effort into making an OS from the ground up as before and can concentrate on making the devices much better in terms of hardware. Functionalities like NFC (Near Field Communication, something similar to Visa Wave) or WiFi Direct are built into the Android source code, and so the manufacturer does not have to invest into a team of programmers to get that functionality into proprietary software. This in theory should make phones cheaper and more accessible to the masses. The same set of codes can be utilized across different hardware (with the appropriate adaptations) and thus major software redesign is not needed when making phones of different hardware variations.

From this, we can see that Android is both a common platform of games and application that all these Android-based devices run, but also proprietary in the sense that the OEMs have the freedom to make the OS as theirs as they want, just like the old days of feature phones. Win for doing things the old way, win for application support.

Fragmentation?

So now with the background information finally made clear, let’s start addressing the issue of ‘fragmentation’ one by one. Fragmentation is defined as the disunity in different aspects across a common platform. This includes user interface, applications support, and OS upgrade.

Interface fragmentation

First in the crosshair is interface fragmentation. Critics often talk about the varying interfaces they experience across the different devices they come across that are known as an ‘Android device’. From HTC we have HTC Sense, from Samsung we have Samsung TouchWiz, from Sony Ericsson we have TimeScape, from Motorola we have Don’t-Call-it-Blur and etc. This, they say, causes some degree of confusion among consumers as to what an ‘Android device’ really is. Consumers are confused as to why certain functions work differently from one ‘Android device’ to another ‘Android device’ if they are all known as ‘Android devices’.

If you’ve read the few paragraphs before this, you would’ve known that Android’s inception wasn’t supposed to be a unified user experience in the first place. It was for the OEMs to utilize a common code to their liking, and reduce production costs in the software department. Look at the Nokia 6300 and Sony Ericsson W810i (both feature phones with proprietary software). Do they look the same? They shouldn’t, or else why would a consumer choose one over the other?

[It should be explained that prior to the iPhone, feature phones were where the real war was, not smartphones. Android’s arrival really took smartphones to the masses. This is why I made references to feature phones so often.]

It used to be the case that a phone of a certain brand has a distinct look and feel both in terms of physical appearance, and software. You know a certain phone is a Nokia from afar, and you know a certain phone is a Sony Ericsson from afar. The way a Nokia operates is very different from how an SE one does. There is also the accompanying crowd of supporters of the respective interfaces. Nokia is known for simplicity but looks outdated; whereas Sony Ericsson is known for a zippier, more polished interface.

Therefore, it is impractical to criticize the varying user experience in the vast amount of variation in Android-based devices. HTC made an HTC phone, so naturally it should look ‘HTC’. Same applies to all the other OEMs out there. Of course some people (including me) prefer the ‘vanilla’ build (means unmodified by OEM) of Android, but at the end of the day, an OEM builds phones not to sell to one individual, but to the market that includes people who don’t know what is Android. This should also highlight the stupidity when comparing an Android phone to the iPhone, and making it sound like an 'Android vs iPhone' battle, where the comparison should've been more 'one-on-one'.

OS Upgrades

Next up is applications support and OS upgrade fragmentation. These two aspects go hand-in-hand as application support often depends on the OS version. The ‘problem’ that Android-based devices have is that due to the customized version of Android running on these different phones, often when a new version of Android is released by Google, it takes an awful long time for the update to reach the users’ phones. And since application compatibility is often due to software versioning (certain functions are only present in the newer version of the OS.), this aspect often receives complaints about why certain apps cannot be run on certain phones when they are all ‘Android devices’. When the truth about the delay is disclosed, more often than not people cite the ideal-ness of the iPhone model where the phone is controlled from top-to-bottom, allowing for rapid updating of software.

Now, if you’ve read the previous paragraphs about background information, you’ve noticed that I did mention a ‘Android devices’ aren’t really supposed to have a unified experience to begin with. Each and every ‘Android device’ is supposed to be one individual device by its own, with no affiliation to something bigger (in this case, the notion that a phone with a common OS should be equal in all aspects). To reiterate, Android works by giving OEMs the freedom to use a common source code to construct the backbone operating system for a hardware (in this case, a mobile phone). Therefore, the OS running on a particular device is essentially the OEM’s own software, with compatibility to a common format of applications (.apk).

The point being, it is up to the OEMs to decide whether a certain phone needs to be updated. This decision should be independent of the versioning upgrade to the main Android branch. It, after all, should be treated as an in-house developed software. One prime example is how Samsung is the only Android-based device maker that incorporates video call over 3G into their phones. No other Android OEM that I know of has this feature built into their phones (having a front-facing camera does not automatically enable video calls over 3G). Only Samsung. It is worth noting that voice call over 3G is not a function supplied by the main Android source codes. Samsung developed proprietary codes to incorporate that function into their Android-based devices.

This begs the question, why do OEMs take their sweet time to ‘upgrade’ the OS in their phones if application support fragmentation is such a big problem? To update the codes to incorporate a new version of Android, major work needs to be done to the main framework of the OEM’s proprietary version of Android. Every OEM Android [/B]device out there has a different framework to support the customizations they put on top of the base Android software. This framework is also hardware-specific. Therefore it is almost impossible even for the underground development community to adapt an OEM’s proprietary version of Android onto another OEM’s hardware (it is impossible to port Samsung’s TouchWiz to an HTC phone, and vice versa).

So, if the customizations are slowing down the work to upgrade the software of a device, why even have those customizations in the first place? Again we come back to the original concept of Android, being that it is just a common set of codes that OEMs are free to modify to their liking to put into their devices.

Is it a problem?

All these ‘fragmentations’ appear to be a huge problem, but is it? When you look back at the history of feature phones and smartphones, OS upgrades are virtually unheard of. Things did not work like that. OEMs are not expected to maintain the software of a phone post-sales (very rarely do we see a software update). If a phone runs new software, it is most probably a new phone. In my Nokia 6630 days, it was impossible for me to upgrade the stock S60v2 to an S60v3 (that ran on an N73) or whatever was in the new phones. Why upgrade, you ask? It is because certain games are only available in the newer version of Symbian (yeah, even at that time). I wasn’t involved in hacking Symbians back in the days, so I am not aware of whether a method of loading S60v3 onto the 6630 exists or not (I doubt it). The only way we can savor the taste of having the ‘new version’ is through installing themes that resemble the new phone’s software. But theming can only bring you so far…

Also, for a consumer who has no concept of operating systems and only knows that a smartphone is only to play games, make calls and access the internet (more commonly known as Facebook), it is very possible they do look at phones the way people used to pre-iPhone: an OEM phone is a phone made by an OEM top-to-bottom. It just so happens that there’s a place to obtain applications that few other devices do too (Android Market). OS updates probably don’t mean much to them, and said fragmentation only becomes apparent when a certain feature is not found and all of a sudden they were bestowed upon the concept of mobile operating systems (as in the case of moving apps to the SD card).

One final question: can the problem of ‘fragmentation’ in Android be solved by the users at least? The answer is both no, and fortunately yes. Why no, you ask? Well since each phone is an individual phone on itself, the software on each phone is thought as different softwares. The first step to solving this ‘fragmentation’ problem by the users is to hack into the phone to gain special access. The technical term for this process is ‘rooting’, coming from the process of gaining ‘root’ access to the phone. Android is a Linux-based OS, and users are given different permissions based on the configuration. By default, certain portions of the phone are locked out by the OEM from user modification to prevent unfortunate events. By ‘rooting’ one’s phone, the user is able to obtain ‘root’ access and enables the internals of the phone to be freely modified by the ‘root’ user. A root user is also known as a superuser (su in Android commands, sudo in Linux).

The problem with hacking one’s phone is that since each phone is internally different (both software and hardware), the way an OEM locks down a phone is also different from one OEM to another and from one individual phone to another by the same OEM. Some phones are more ‘hackable’ than others, like for example the LG Optimus 2X that uses simple, universal ‘one-click’ program that does all the dirty work, while others like the HTC incredible S did not have a proper hack solution until a few months after it was released. The main obstacle is usually the ‘bootloader’ of the phone. It controls the boot sequence of the phone (analogous to the BIOS of a computer). Without unlocking the bootloader, no permanent change can be done to the software of the phone. The bootloader checks through a few checkpoints before authorizing the bootup of a phone. Sometimes if a modification is detected by the locked bootloader, it will force the phone to boot up the unmodified version of the software (usually the case in a temp-root (temporary root) situation). The danger comes when the bootloader does not have a fail-safe mechanism and refuses to boot when met with an unauthorized modification.

By unlocking the bootloader, all changes by the user can be permanent (as in the case of a perm-root (permanent root) situation). This will open up possibilities to make minor changes like replacing the battery icon or font of the phone, or even replace the entire OS of the phone. Different OEMs have different ways of locking down the bootloader, and thus have different ways of hacking. The locked-down bootloader has made headline news across tech news sites (more often those focused on Android news) when thousands of HTC users made complaints through HTC’s Facebook page demanding an unlocked bootloader to ship with HTC phones. Few weeks later HTC’s CEO Peter Chou made an announcement that they will be shipping future phones with unlocked (or unlockable) bootloaders, with efforts to make current bootloaders unlockable by using an online tool. Calls are still being made to make the tool available to all older HTC phones, while HTC phones are still being shipped with locked bootloaders at the moment.

ROMs

A big number (unfortunately not all) of Android phones have an active development community that deals with hacking the phone software (to optimize it) and to ‘port’ the OS of a certain device (usually same brand) to yours. For example, my HTC Desire Z (shipped with HTC Sense 2.0 Android 2.2) has got a port of the OS that is running on the HTC Sensation (HTC Sense 3.0 Android 2.3). It also has a port of the OS running on the HTC Flyer. These are examples of ‘upgrading’ the OS yourself when the OEM doesn’t do it for you. But then, there will come a time where a port is just not possible due to hardware limitations, or lack of effort by the community (all development efforts are voluntary, so it is rude to actually demand work to be done. The motto is "it is done when it is done".).

There is also a very well known Android development project known as CyanogenMod. CyanogenMod is an unofficial collection of voluntary developers that works to bring the untainted ‘vanilla’ (AOSP) build of Android OS to phones. At the time of writing, 56 devices are supported by this project. The fame of this project lies in its support for discontinued phones, like the HTC Hero which is no longer given OS upgrade support by HTC. Through this project, many phones are given a new lease of life in the form of an upgrade to the latest version of Android. However, although the CyanogenMod effort is still going strong, sometimes it is just ‘time’s up’ for certain phones. The first commercially available Android device, the HTC G1, has been discontinued from the official CyanogenMod project update cycle recently due to hardware limitations (though I’m sure there’re independent developers that continue to work on adapting the CyanogenMod project to the HTC G1. Such is the beauty of the Android development community).

Conclusion

In conclusion, Android should not be seen as an OS on a device that is to be updated on a frequent basis by the individual OEMs. It should be accepted as a form of proprietary software on OEM devices that share compatibility with a common application container format. Android’s beauty lies in the freedom to build hardware and software with many variations by anyone. The real beauty of Android is the development community that keeps pushing the limits of a device beyond what is known by the OEMs.

Sry no cliffnotes. It took me 4 hours to perfect this piece. Thumbs up? +1? Share?

Share your thoughts on my alternative view of the whole 'fragmentation' thing.

To mods: Do feel free to move this to the Android section if you feel it's more appropriate there.

[FW] RAM: What is it, and why you shouldn't care.

DJFoo000 — Sun, 02 Oct 2011 14:23:22 +0800

Really recommend for everyone to read. Ditch that task killer, coz you're killing android if you don't.

I've reproduced part of the article below:

Original article from [Android Central]

I do realise this article was a week old. Posting this for the sake of people who don't surf around like the hardcore ones among us do.

QUOTE

RAM: What it is, how it's used, and why you shouldn't care
By Jerry Hildenbrand 25 Sep 2011 5:13 pm

Recently, a wise man holding a new Samsung Galaxy S II made a great observation --

QUOTE

Why, in the name of all things holy, does the fastest, most powerful phone on the market have a widget warning me how many apps are open?

Many of you guys know me, and how I am (if you don't, imagine some godless mash-up of anal retentiveness and OCD), so you know this is something that just had to be addressed or I would never sleep well at night again. Which leads us to here and now. The answer to the question is pretty easy -- user madness and FUD forced manufacturers to add some sort of RAM-cleaning, task-killing, and problem-causing widget to current builds of their software. For most of us, the system running on our Android phones, and the way it handles RAM usage, is very different than what we are used to on our computers. If we take a few minutes to understand the way RAM is managed on our phones, we'll not only be able to better interpret what that widget is telling us, but also understand why it doesn't really matter. Let's do that, after the break.

The 'Task Killer' debate

Every discussion about Android phones and tablets, and how they manage memory will eventually get to the Task Killer debate, so we're going to start with it. Simply put -- task managers are good; task killers are bad. In the hands of someone who is aware of what will happen when they stop a running application, a tool that easily lets them do it is a fine thing for everyone. It's a function built into every operating system, including Android. It's a useful debugging tool, and great for developers and power users alike. The problem is that if you're here at Android Central reading, you're either a power user already, or a power user in training and understand more than most people who just install TASK KILLBOT 2000 because the Market description said it will make your phone ZOMG FAST. You realize that killing the Mail app will stop you from getting mail, or that killing the system clock will make you late for work. Harriet Housewife, who just picked up her shiny new Android phone at the Verizon store doesn't -- and she doesn't have to -- unless she gives in to the FUD (or worse, some kid at a store who thinks task killers are a gift from Zeus himself) and installs the task killer. It's not her fault though, as it seems like every time you turn around someone, somewhere is saying that to get good battery life and ZOMG FAST you need to use one.

You don't. You won't. And it makes Cory twitch a little and think about ammunition and clock towers. Keep reading. ...

What is RAM?

RAM (Random Access Memory) is storage used for a place to hold data. Think of it as a big filing cabinet that keeps things ready for the CPU in your phone to present it to your eyes and ears. It's infinitely (almost) re-writable, very fast, and used differently by different operating systems. Many of you guys understand what it is, how it works, and what I'm explaining -- but we're going to try and break it down so that more normal and well-adjusted people can follow along.

RAM is used for one reason only. Reading and writing to file storage (as in reading and writing to your hard drive in your computer, or your internal memory/SD card on your phone) is terribly slow. Solid-state "disks," like what's used in our Android devices and what a lot of geeks people use as hard drives in their computers, are faster than spinning disk platters (normal computer hard drives), but using it to cache the data we need is still a lot slower that using dedicated, solid-state RAM. RAM is cheap. The bus (a pathway for the electrical signals to travel along) between the CPU and the RAM is fast, and everything is kept orderly and easy to retrieve. It's also resource friendly to read and write to it. Without it, computers of all sizes would suck a lot more.

...

Proceed to [Android Central] for full article. There's a part where it explains how having your RAM fully occupied is how Android is supposed to be used.

QUOTE

Unused RAM is wasted RAM.

Happy reading.

TL;DR:
Use your phone without worrying about RAM, because worrying about RAM is the Android OS' job, not yours.

[WTA] Cantonese cooking movie

DJFoo000 — Wed, 23 Mar 2011 21:28:34 +0800

Hi, I'm looking for a Hong Kong movie. It's about cookery. Filmed in the 90s if I'm not mistaken. The only detail I remember:

In one scene:
The main actor went for a meal. He lost all his sense of taste. A bunch of ppl wanted to prank him so they added a lot of rubbish into his meal like whole bottle of pepper, comb, brush, clippers, mouse trap etc. But the main actor still think the meal was normal despite picking out all the items from his mouth.

In another scene:
The actor was in a preliminary stage of a competition. He cheated by bringing tapau-ed food into the place and reheated to pass it off as his own.

I hope i did not mix up the scenes. The movie is hilarious.

I'm pretty sure it's not Stephen Chow's God of Cookery 食神 coz I just watched it.

----->>> Official HTC Vision Thread V1 <<<-----

DJFoo000 — Wed, 19 Jan 2011 09:51:01 +0800

The Holy Bible for HTC Vision (READ THIS BEFORE YOU READ ANYTHING ELSE): ~~~~~ XDA's HTC Vision Wiki~~~~~~~

Specs comparison (screenshot from GSMArena DZ vs G2 comparison page)

» Click to show Spoiler - click again to hide... «

Differences b/w Desire Z and T-Mobile G2

» Click to show Spoiler - click again to hide... «

Some say the DHD and DZ are using essentially the same processor, but DZ's is underclocked to 800MHz. This is due to them both having identical GPUs (Adreno 205) but difference CPU clockspeed.

HTC Vision uses Gorrila Glass!
http://www.corninggorillaglass.com/#featured-products

Reviews:
This is basically a condensed directory of a Google search
Keyword "Desire Z Review" "T mobile G2 review"
"This allows me to play my favorite games like RSC Legacy on it."

Tech blogs

HTC Desire Z

SlashGear
TechnoBuffalo
Engadget Mobile
TechRadar.com
PhoneArena
GSMArena
CNet UK
CNet Asia
Pocket-lint
Trusted Reviews

T-Mobile USA G2

CNN Tech <----- Holy sh*t i didn't know CNN reviewed this phone until I made this thread
Engadget
Gizmodo
PocketNow.com
PhoneDog.com
PhoneDog Dog Fight - HTC Shift Evo 4G vs T-Mo G2 Pt 1
PhoneDog Dog Fight - HTC Shift Evo 4G vs T-Mo G2 Pt 2
PhoneDog Dog Fight - Samsung Epic 4G vs T-Mo G2 Pt 1
PhoneDog Dog Fight - Samsung Epic 4G vs T-Mo G2 Pt 2
PhoneDog Dog Fight - Motorola Droid 2 vs T-Mo G2 Pt 1
PhoneDog Dog Fight - Motorola Droid 2 vs T-Mo G2 Pt 2
G4TV
PC Magazine
CNet
Android Central
InfoSync
ChipChick
BrightHand
LaptopMag.com
PhoneScoop
MobileCrunch
TechWorld

Click!!! --->>> **** LYN HTC VISION USER LIST **** <<<--- Click!!!

Owners please update it yourselves.

Personalised LYN Users' Reviews:
urb7's First Impressions
DJFoo000's First Impressions
DJFoo000's Review
un_id 's Desire HD vs Desire Z

Student got caught FB-ing using mobile phone

DJFoo000 — Mon, 19 Jul 2010 12:13:26 +0800

White DP is me. The one saying 'kantoi' is discipline teacher. I did not add the teacher.
The one who kena is a kid who's still studying in secondary school.

Help me identify the genre

DJFoo000 — Sat, 05 Jun 2010 22:42:55 +0800

Hi. This is one of the tracks from the Discovery Channel series Deadliest Catch.

http://www.youtube.com/watch?v=XnQ8VC4xfF8&feature=related

What is the genre of this track? Celtic? What is the instrument used in the beginning of the track?

Thanks in advance.

Game over WLAN

DJFoo000 — Sun, 04 May 2008 23:01:28 +0800

Long story cut short, I've tried to play LAN games wit a friend of mine. I brought my laptop to his place and successfully connected wirelessly to his router modem. It's like a normal established connection, eg I can surf the net usin this connection. But when I wanted to play LAN games thru this connection, the game simply never showed any existing LAN connection b/w the 2 computers. But when it was him who created the game, my lappie can detect the game and connected to it!

Info as below:

My lappie: Vista Home Premium
His PC : Win XP Home
My connection to his router modem: wireless (WLAN)
His connection to his router modem: ethernet cable
I create game: his PC cannot detect
He create game: my laptop can detect game.
Game: Counter Strike

Monitor flickers and hisses

DJFoo000 — Sun, 25 Nov 2007 18:48:28 +0800

Today turned on the PC. After 15 minutes the whole monitor sot. The left side go to the right side and vice versa. A hissing sound also came wit the condition. Turning on and off the monitor didn't work. I smacked the sides of it also didn't work. Any ideas?

As you can see it's like you divide the screen into half. Put the right region at the left and the left region at the right. It's not a mirror image, more of rearranging the pages. There's this vertical black thick bar in the middle and flickers like your TV signal not strong.

Monitor bought about one year ago.

How should i handle newborn hamsters?

DJFoo000 — Tue, 15 Aug 2006 18:33:08 +0800

I just bought 2 hamsters, 1 female, the other dunno, maybe female also, 2 days ago. Today one of it (the definite female) just gave birth to 6 lil babies (which is kind of weird as i only bought them for 2 days). The mother ate one of it already and left 5 more. My mom retrieved the remaining 5 as she's afraid that it'll eat them all. Den i explained that if we retrived and replaced them, the mother would eat them all (myth?). Den she put the babies back in coz got no choice already. The other hamster quickly came and attacked 3 of the babies! 2 of it was headless and one of it was injured in the head. We isolated the brutal one already.

Now only 2 baby hamsters and the mother is in the cage. The weird thing is that the mother was constantly looking to escape (or something else la coz it's running here and there). Then it went to the treadmill and ran a number of rounds. It then rested for a while and then ran on the thread mill again. I placed the babies in the small house provided and the mother only visited it twice (once is that i purposely get the mother into the house) and never visit it again. It's either running on the threadmill or resting as i'm typing here.

How should I handle it? The babies would probably die of hunger or hypothermia if the mother ain't no going to them....

Help!!!