Related
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
76redrum said:
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
Click to expand...
Click to collapse
Hi,
What version did you install?
3.6.8 or 4.1.8?
Did you do a MD5 checksum?
Did you super wipe?
Did you add any mods?
If you want help,you need to post more information...
Hi i had the same sort of problem with my ARHD but I find out that the faux kernel was causing for difficulties.
Installed a stock kernel and all problems solved.
Still respect all developers
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
76redrum said:
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
Click to expand...
Click to collapse
Hi,
It does sound like a kernel problem.
Try the kernel in my signature.
Absolutely no problems there.
ill try the stock kernel thanks to all
phone:htc senation
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any digestions would be very appreciated
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any sugestions would be very appreciated
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
seatown1two said:
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
Click to expand...
Click to collapse
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
---------- Post added at 03:15 PM ---------- Previous post was at 02:25 PM ----------
Hawke84 said:
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
Click to expand...
Click to collapse
Hi, i've been running the 3.6.x Roms for a while now and think they're great, but was getting interested in the sense 3.5 stuff. What in particular do you like about the 4.1.x roms? Just seeing if it's worth the full wipe effort .
Thanks
Mike
ArcticWolf91 said:
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Click to expand...
Click to collapse
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Hawke84 said:
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Click to expand...
Click to collapse
Lol yes, you are not the first to tell me that, and believe me lesson learned. Though I did mention that it was rooted and that it would be running this Rom. But yes now I am troubleshooting the phone with this person and I may have to give them a refund because they opened a case with eBay.
mrew42 said:
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
Click to expand...
Click to collapse
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
seatown1two said:
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
Click to expand...
Click to collapse
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
mrew42 said:
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
Click to expand...
Click to collapse
how do you up the speed for idle..silly question i know
When i flash any of the whyzor reloaded cm7 roms my triumph over heats, it's currently on a KANG build & dosen't ever over heat, anybody know why this happens ? Has this happened to anyone else ? Because i've tried the same setup on my wife's triumph and the same thing happens it starts to over heat. If anybody can help me with this that would be great, I love CM7 & would love to be running the newer release's, but not if there gonna over heat my phone, that's a deal breaker for me.
I'm using his newest build and have been using it since he posted it and haven't noticed it overheating... Are there any apps running?
no this happens from the moment i flash the rom, i even turned off the phone and let it cool down then just turned it on and thats all, and it still gets hot ? I haven't tried the 1-25 build that was just released but i would expect the same thing will happen, I'm tired of doing fresh install's of this rom just for it to start over heating again, well i'll probably flash it to find out but it's frustrating
Hmmm that is strange... But yea I would try a fresh install of his newest build and see if that stops it. I think I had problems with one of the builds overheating too... But I also had a bunch of apps installed...
Installed or running ? what's the point of a rom that overheats when apps are installed LOL
ok well i fashed the new one & this is weird i flashed fhe gapps to but no market ? And of course it started getting hot
Are you overclocking? Undervolting? If so, what are your settings? was it overclocked/undervolted from a previous install?
yes it's overclocked to 1.5gz on my current rom, but i format the system before i flash the rom & i don't overclock the new rom because it starts getting hot way before i can even get to that stage of the install ?
Were you undervolting at any point before?
no never undervolted ???
It's a very strange issue that you're reporting...
Try flashing the original theOC kernel right after you flash the rom. The kernel from here:
http://forum.xda-developers.com/showthread.php?t=1338825
So do the following in CWM:
1. Wipe/Factory reset.
2. Flash ROM.
3. Flash kernel.
4. Reboot and see what happens.
At least we can narrow it down to if it's something in the ROM causing it or if it's something in that changed in the kernel.
Do you want me to flash the 1-25 or the 1-26 build ? Then the kernel, what about the gapps ? Alright back in a flash LOL
Flash the 01-26 ROM, don't install any apps, see if it overheats, if so, flash theOC kernel, check again if it overheats, then if not, reinstall your usual apps. If it starts overheating, then it's an app you installed. 'Battery usage' should be able to point out what it is. Or settings - applications - running services will also help find it, uninstall it and let the developer of that app know.
i'm wondering if juice defender could be the suspect here ? what should i set my minimum to on my cpu settings ?
overheat
I had an overheating problem to but when I reflashed the rom it stopped.
jaaydogg said:
i'm wondering if juice defender could be the suspect here ? what should i set my minimum to on my cpu settings ?
Click to expand...
Click to collapse
To troubleshoot problems, disable ALL apps services to find a stable base, then start renabling each one individually until the problem comes back, then you know.
Hey i have this strange problem .. what happens is that my SGR some times goes off to sleep and there is no response till i have to restart it ..
i have flashed it with Franks 1.5 mod ..
Any idea why this is hapening .... maybe some setting have gone wrong ... but it happens anytime sometime in 5 mins sometimes in 2 hrs something after a day just dont know what happens on ... If some1 calls me during this time i dont even come to know its ringing as the screen is completely blank.
Need some help here
afzalbhimani said:
Hey i have this strange problem .. what happens is that my SGR some times goes off to sleep and there is no response till i have to restart it ..
i have flashed it with Franks 1.5 mod ..
Any idea why this is hapening .... maybe some setting have gone wrong ... but it happens anytime sometime in 5 mins sometimes in 2 hrs something after a day just dont know what happens on ... If some1 calls me during this time i dont even come to know its ringing as the screen is completely blank.
Need some help here
Click to expand...
Click to collapse
may be your fone is turning off...
Try restarting the fone by press long power on/off button...
N chk what happens
May b its a case of random shutdown
afzalbhimani said:
Hey i have this strange problem .. what happens is that my SGR some times goes off to sleep and there is no response till i have to restart it ..
i have flashed it with Franks 1.5 mod ..
Any idea why this is hapening .... maybe some setting have gone wrong ... but it happens anytime sometime in 5 mins sometimes in 2 hrs something after a day just dont know what happens on ... If some1 calls me during this time i dont even come to know its ringing as the screen is completely blank.
Need some help here
Click to expand...
Click to collapse
same here bro..i use unkown kernal 1.3a.when i put it to charge it switches off or even when i speak a call it hangs..
suggestion:just remove and put the battery again..reminds me of the nokia phone days which hangs and we do same there:-(
any particular issue y it keeps turning off its hapeening only after i flashed new rom ...
is it hardware issue or software .... the problem is i have to keep checking the phone again and again if its on or its gone off quite irritating ..
and yes i keep on/off button long pressed and it restarts itself
This problem occurs particularly on stock ROM and that too on indian ROM...
Theres one ROM mentioned in the below url, where people didnt faced after flashing it. (May be Australian)
Check the link
http://forum.xda-developers.com/showthread.php?t=1420214&highlight=random+shutdown
i am not using stockrom ... using frank's 1.5
I think its a Kernel Problem. Try flashing Stock Kernel/Any other kernel..
Using Stock XWLA4 without any ROOT/CWM and just Stock Kernel..
Its great.. No hangs!!!
Yes the problem is not ROM. Its the Kernel. Not only Unknown Kernel. But all those kernels having Voodoo Sound are acting weiredly. It is draining the whole battery overnight in standby.
Now I have installed Ardatdat kernel 1.6. Lets see if thd problem resolves.
Sent from my GT-I9103 using Tapatalk 2
looks like its the kernel problem ...
i havent flashed any other kernel .. i m on ardatdat kernel v1.7b2 maybe i will flash 1.6 and see if it helps ...
maheep please post your experience too should be helpful
afzalbhimani said:
looks like its the kernel problem ...
i havent flashed any other kernel .. i m on ardatdat kernel v1.7b2 maybe i will flash 1.6 and see if it helps ...
maheep please post your experience too should be helpful
Click to expand...
Click to collapse
give a try with stock kernel, ur phone still have root access but u will loose oc, uv and other tweaks
afzalbhimani said:
looks like its the kernel problem ...
i havent flashed any other kernel .. i m on ardatdat kernel v1.7b2 maybe i will flash 1.6 and see if it helps ...
maheep please post your experience too should be helpful
Click to expand...
Click to collapse
Yes it was the Kernel. I flashed Ardatdat kernel 1.6 and now Phone is working like charm. No deep sleep, no battery drain and not becoming unresponsive.
Sent from my GT-I9103 using Tapatalk 2
well i have done the same since yesterday and kept the cpu @ 1.3 ghz ... soo far its working wonderful ... will keep it on test for like couple of days and then come to conclusion if its good or not.
even after flashing kernel the issue still persists ..
maybe i need to change rom once agan any idea what can be done ?
I too have been facing the unresponsive issue a couple of times since I changed to 1.7b2 kernel but I thought it might be because of the apps I installed..
Sent from my GT-I9103 using XDA
i have noticed it happens more when i m outdoor and phone is in pocket ... i also guess that phone gets heated at times and that when this problem arises more.
ANy idea guyz why it gets heated up when outdoor and goes to deep sleep ... hould i go back to stock rom fir India and then see ... if soo how can i reset the binary data count ... i normally flash thru odin 1.8.5
afzalbhimani said:
ANy idea guyz why it gets heated up when outdoor and goes to deep sleep ... hould i go back to stock rom fir India and then see ... if soo how can i reset the binary data count ... i normally flash thru odin 1.8.5
Click to expand...
Click to collapse
Same thing is happening to me. Going to service center this week
Sent from my GT-I9103 using XDA
F3niX said:
Same thing is happening to me. Going to service center this week
Sent from my GT-I9103 using XDA
Click to expand...
Click to collapse
Can you update me what they say... Ok maybe a noobie question just was trying to check the binary counter and below is details i get from ODIN3 download mode.
Custom Binary Download : No (0 counts)
Current Binary : Samsung Official
does this means i can flash back stock Indian rom and take it to service center and my warranty still holds firm ?
afzalbhimani said:
Can you update me what they say... Ok maybe a noobie question just was trying to check the binary counter and below is details i get from ODIN3 download mode.
Custom Binary Download : No (0 counts)
Current Binary : Samsung Official
does this means i can flash back stock Indian rom and take it to service center and my warranty still holds firm ?
Click to expand...
Click to collapse
Yes you can flash Stock Rom and do factory reset before taking it to Service Center and any repair will be covered under warranty...
I'm getting the same deep sleep problem as the others. It started after I flashed the v1.3a Ultimate kernel. But since i also dropped my phone that day (Not hard, but still), i was scared.
I'm using the stock DDKH4 India 2.3.5 ROM
I will try changing the kernel and give an update.
Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
I had a stock Froyo on my phone and I tried following the steps of this thread : http://forum.xda-developers.com/show....php?t=1894737
The first mistake I did, was I flashed XXKPQ directly by mistake instead of XXKPE, which I noticed while I was in the middle of doing it.
The phone was working properly on the GB rom. After that I rooted it, following the guide using a cf root of XXKPQ.
Now, I didn't know if there was prerequisite for it or not, but I flashed the custom rom of http://forum.xda-developers.com/show....php?t=2300693
The first problem I saw was that while installing it from the sdcard, for a long time, the screen was blank. I left it thinking that it was part of it, but since it persisted, I rebooted it. The phone opened properly and after that I installed the gapps later through recovery mode.
The first major problem I saw was that the phone after screen locking, it used to shut down automatically. After looking through solutions, where none were working, I tried flashing to stock rom via odin (stock rom : http://forum.xda-developers.com/show...php?p=16107097)
After that though, whenever I open the phone, it just stucks at the samsung logo screen and doesn't go further.
Also, when in download mode, I tried it attaching to Odin but "USB device not recognized" comes all the time.
I don't know what to do.. I know I must have made loads of huge mistakes and I should have done everything, being properly informed, but now I really need a solution..
Click to expand...
Click to collapse
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?
tyson123g said:
Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?
Click to expand...
Click to collapse
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.
karthik gowtham said:
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.
Click to expand...
Click to collapse
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?
tyson123g said:
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?
Click to expand...
Click to collapse
Why Do You Got To XXKPE From DDLF2 ,All I Was Trying To Say Was
XXKPE--->DDMF1--->CF-Root or Custom Kernels--->CM10.1 or Any Other Rom.
Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?
tyson123g said:
Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?
Click to expand...
Click to collapse
REMICS v6 now is out (smoother and more stable)
kernel 3.0.8 by dhiru1602 does not support OC but you can change the governor to ondemand or performance (performance>>processor>>CPU governor) and the I/O scheduler to deadline (performance>>I/O scheduler) but first you have to enable the developper options (7 hits on the Build number).
Hit thanks "button" if i helped you!
regards
Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.
tyson123g said:
Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.
Click to expand...
Click to collapse
Yes, because as i know kernel 3.0.8 by dhiru1602 which is the default (preinstalled) kernel of CM10.1 (Jelly bean 4.2.2) (REMICS 5.x and 6 and the newer jelly bean roms are based on CM10.1 by dhiru1602) does not support OC and you won't find other kernel for CM10.1 better than dhiru1602 kernel (it's only my idea).
I think dhiru1602 didn't implement OC in his kernel for reasons of stability and battery backup...and you don't have to use no frills CPU app anymore, just 7 hits on the Build number (About the phone >> Build number) will enable the "developper options" and "performance" (in "performance" you can change the CPU governor and I/O scheduler).
And don't use REMICS 5.8, REMICS 6 is better because many bugs were fixed!!!
Hit thanks "button" if i helped you!
regards
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
in CM10.1 kernel overclocking is not there for some stability issues... overclocking is possible but do it at your own risk
tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
You really don't need to OC your CPU....if you are facing some lags in CM, this maybe because you didn't wipe data before install CM.
Usually I downclock my cpu to 600MHz and set the governor to conservative to save battery without facing lags...so really CM10.1 A8 is not lagging!!!
Okay. I have to install REMICS 6 anyway. I will try again. Hopefully this time, it is quick.
Well, I changed my mind and went with CM 10.1 A8. It is fast and good.
But for some reason, my phone is rebooting by itself.
So very recently my phone started to do things on its own. It starts pressing things on the screen randomly on its own, the screen locks up. I would have to keep tapping something to get it to work, or lock the screen with the power button, then unlock it to work, but then the issues comes back after a few seconds. Its rooted with Cyanogen 7 20130301-NIGHTLY, kernel 2.6.32.55.
I reset the phone to a fresh rom install, and the issues were still there. I changed out the battery, because I am suspicious that it is an issue with the battery or power.
Any help appreciated, thanks!
Flash a custom kernel. I never run CM7 with its stock kernel. The thing about the G2X is that every individual device is "different." My G2X handles the trinity kernel best, Mazout's kernel is great but gives me SOD's constantly, although I have not tested any of his latest builds since I only run ICS hack fests. I think flashing a new kernel would help you out a lot. I would recommend trinity (as they're my favorite), Mazout's kernel or Faux's kernel. In that order. I would also try over clocking and under volting when you get the chance.
Pain-N-Panic said:
Flash a custom kernel. I never run CM7 with its stock kernel. The thing about the G2X is that every individual device is "different." My G2X handles the trinity kernel best, Mazout's kernel is great but gives me SOD's constantly, although I have not tested any of his latest builds since I only run ICS hack fests. I think flashing a new kernel would help you out a lot. I would recommend trinity (as they're my favorite), Mazout's kernel or Faux's kernel. In that order. I would also try over clocking and under volting when you get the chance.
Click to expand...
Click to collapse
Can I flash the kernal while keeping the same rom and contents?
Yes. I would just clear the caches first. Then flash the new kernel
Sent from my Nexus 5 using xda premium
Ya I figured that out, I tried both trinity kernels and mazout, for some reason it would not boot up past the load screen. Not sure if I had to wait that long. I just went back to my nandroid backup, but for whatever reason the problem is not there anymore. I suspected that this was a hardware issue. Funny thing, my spare battery just broke down, it started to inflate. I need to get a new phone me thinks.
But now I am curious as to why I couldn't get the kernel to work. I would still like to do that. I even tried a stable CM7 rom and then flashed the kernels, still to no avail.
It takes a few minutes to boot up after you flash a new kernel because the system has to rebuild the caches.
Sent from my Nexus 5 using xda premium
Pain-N-Panic said:
It takes a few minutes to boot up after you flash a new kernel because the system has to rebuild the caches.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Few minutes does not mean over an hour does it? It just gets stuck at the boot logo for at least 45 minutes before I get annoyed and turn it off.
Lolol no!!!!! Few minutes means 5 at most lol. Are you sure you're flashing the correct kernel? Mazout does make more then one kernel. So does Trinity. Not trying to make you sound stupid or anything.....i just can't imagine why the kernel would cause the phone to freeze during boot.
Sent from my Nexus 5 using xda premium
Pain-N-Panic said:
Lolol no!!!!! Few minutes means 5 at most lol. Are you sure you're flashing the correct kernel? Mazout does make more then one kernel. So does Trinity. Not trying to make you sound stupid or anything.....i just can't imagine why the kernel would cause the phone to freeze during boot.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I have asked about my problem here http://forum.xda-developers.com/showthread.php?p=49089235#post49089235
I got the correct kernel, just some weird issues, but some guy is trying to help me out.
Make sure to use the correct recovery. At least trinity is incompatible with CWM touch.
noobish comments:
-- As the story says, a kiss turned my G2X into an HTC Ruby!