Related
So i have tried mattc evoleo 1.0 and mattc leofroyo both with evo kernel. I have tried UV EVO kernel as well..and after a while of phone being in sleep, i cannot come out of it?
I have formatted SD CARD, tried different zimages..and cant seem to figure it out. any ideas?
i've had the same issues myself. can't pocket the phone for more than 15minutes without it going to sleep for good.. i've also had issue calibrating gsensor. after hitting ok, it starts... then the vertical sensor goes to the top and stays there. anyone have this issue yet?
oh great, Its not just me then. My girlfriend's phone is exactly the same, if you notice that when the screen goes to sleep u can get it back on with no problem, but when you wait for the button light to turn out, most of the time from then it will not wake up. I tried going back to windows and made sure all the autodim is deselected but with no hope. So I just set her phone to never auto sleep. If you turn the phone down yourself, it will wake up with no problem. Hope she doesnt forget and let the battery drain =]
No SOD problem here, Its running very nicely for me. My only problem is no mobile network.
Had this problem a few times when adding UV OC EVO kernel Hastarin #2 to Bangsters 1.4.
It seemed like the phone was responding but there was just no backlight at all.
So finally decided to format SD and fresh install with the Kernel there for the 1s boot, havn't had a problem yet....fingers crossed.
If you guys are running "SetCPU", dont stick with the standard underclocking that is preset in the program. That is the main cause for it not coming out of sleep. This has been a known issue since the G1.
Then again, as I'm still working with Matt C's 1.7. I cant say for sure. But this has fixed my BSOD issues with every build. Good luck!
I havent used SetCPU at all so far. So i am kind of stumped really
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
I called today the customer service of my carrier "oi" and I spent kinda 30 minutes talking, trying to solve a problem.
When I saw, my phone was in a bootloop with the cyanogenmod boot and I was continuing to talk, without any interrumption.
The only difference was thet the phone was hot!
Running at 1.4 with the last netarchy kernel my max was 38!!! (low)
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
slowz3r said:
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
Click to expand...
Click to collapse
I hope so!
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
No random reboots here, got it on the 3rd. Phone runs smooth as silk. I'm on stock 2.3.2. Out of all the phones I've owned this has been the most stable.
Could my phone possibly be from a different batch? I'm not experiencing any of the issues alot of other people are besides 100% init process, which I solved with keeping USB debugging on.
Sent from my Nexus S using XDA App
ruben8448 said:
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't think it's the kernel, even stock users have the reboot problems.
I don't have any such problem on Cyanogenmod 7 rc1...
iKitsunee said:
I don't think it's the kernel, even stock users have the reboot problems.
Click to expand...
Click to collapse
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
ruben8448 said:
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ah, I'm actually using that kernel as well, hasn't happened to me but I suppose it might vary from phone to phone.
jerrycycle said:
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Click to expand...
Click to collapse
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Serious_Beans said:
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Click to expand...
Click to collapse
The kernel is set to default at stock setting so no need to have it set on boot. It isn't going to overclock unless you raise the cpu past 1g
google have already said that the problem its just s/w and they are going to fix it with an update and it's not the new 2.3.3! Hope it don't take much longer!!
Sent from my Nexus S using XDA App
There is a stock kernel for cm7 out that has all the voodoo engagement and ext 4 hack
I've had random reboots and it only happens to me when I'm using bluetooth.
Sent from my Nexus S using XDA App
its been over one month now and i never had such problem with mine..its running smoothly both with stock and cm7..
I experienced my first random reboot today. Installed clocksync and was fine. Today I loaded the app... screen was blank then saw the boot animation.
Sent from my Nexus S
I experienced 2 reboots in a row trying to retrieve a service from my mobile operator. I got so frustrated ´cause the mobile operator service takes too long,
the last time I looked, elapsed 7 minutes, few minutes later, reboot...
Became afraid to call again from the nexus, not trusting anymore
wifi on, sync on, bluetooth off, gps off, it was charging with the regular charger, factory rom and kernel, not rooted, launcher pro
I also have random reboots. it's strange though, it goes to the boot animation for some time, looks like the phone reboots, then all the apps and launcher is reloaded, but if you check the phone boot time under settings -> about, the uptime is not reset.
can you guys confirm that your boot times are also no reset during the randon reboots oft he known google android software issue for nexus s?
thanks,
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
r0uzic said:
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
Click to expand...
Click to collapse
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Rod3 said:
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Click to expand...
Click to collapse
Thanks, in a couple of hours notice if I have failed the stock rom
I just tried the stock rom GRI40 and I was not locked, so I guess it will be the kernel in CM7.
Not having that problem at all on stock GRI40; by the way, i'm having an odd issue with GRI40 & Gingerbread. The time to auto-lock the screen uses to change by itself; i think it's on 2' by default, but i changed it to 30' on screen settings and also on Widgetlocker settings...well, once a day, the time changes to 2' again. Anybody else having the same issue? Ideas?
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Know-Fear said:
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
Click to expand...
Click to collapse
britoso said:
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Click to expand...
Click to collapse
I doubt it is a hardware failure does not happen to me with Eclair, Froyo or Gingerbread stock, just happened with CM7
Buck Shot said:
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Click to expand...
Click to collapse
I don't use trackball wake, but my nexus is completely blocked, even if I press the unlock button, and I wipe everything before to flash CM7
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
GronHog said:
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
Click to expand...
Click to collapse
Has it happened again since? If it has try and study your phone's behaviour whenever it happens (does it only happen when plugged in? and so on). Once you manage to get an idea of what actions cause it to happen, start up a logcat and replicate it and send it here. Also, if you've restored anything, downloaded a ton of apps, etc. try a clean install (w/ no restores, minimal apps, and so on) and see if it continues. I don't like to just leave things as "it's a hardware issue" because sometimes it can be difficult to tell.
Hasn't touched the phone for several hours, been on computer, when the incident happened. Had installed a flashlight app earlier in the day, TeslaLED. Also installed Google now M6 offline earlier in the week. Will keep an extra eye open to provide you with any info I can. No TB restore done between BR7 and MR1, as update was done OTA automatically with just ok'ing a cache wipe. The update went smooth, to me, from notification to download to flash and reboot on its own.
sent from Glacier under control of SyNthetic_aospX
again
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
GronHog said:
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
Click to expand...
Click to collapse
Whoops I meant I'll need a last_kmsg from after you pull the battery. That will tell me the last thing that happened before the battery pull. The op in my thread has a link that shows you how.
Sent from my MyTouch 4G using xda app-developers app
Been two days now, everything running as should, smooth. Reflashed Rom to get back to unpatched kernel, and did not reinstall gNOW. Later will install your patched kernel and keep an eye on it. Still getting the occasional inverted lockscreen, but that is no big deal, as this is the most stable ICS Rom that has run on my phone. All other ics Roms have barely made it past a week, cept Awesome's vanilla ics which hit the two week mark before giving me "unfortunately so an so has stopped working" and would cascade from there with errors. Will post up another logcat and kmsg log for you on the invert screen when I make happen again.
sent from Glacier under control of SyNthetic_aospX
Inverted lockscreen from yesterday, should be towards end of logcat=http://db.tt/YOl1UM78
A freeze up while using XDA app and following a link into Maxthon browser. Touched link in XDA auto launched browser then froze, let it sit there for a minute as back button did not kill app. Then phone rebooted itself, so found last_kmsg and saved it=http://db.tt/767lXrNH
Saved both files to dropbox
sent from Glacier under control of SyNthetic_aospX
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
BeWeather was spamming that last logcat you gave me. That might be a part of the problem.
That thought popped into my head, don't know what the logcat was saying but seeing that much from BeWeather didn't look right. Thank you again for t the work you have put into this Rom.
sent from Glacier under control of SyNthetic_aospX
Self wake and freeze happen again, checked for last_kmsg there wasn't one, just last radio. Removed BeWeather widget, and unchecked auto update in the app this morning. I installed the kernel overlay last night, two days without overlay since reflash. Going to leave phone as is for now and run kernel log to see if it happens again.
sent from Glacier under control of SyNthetic_aospX
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
Okay. Now bear with me on this one. Because it may seem odd... but try getting a new sim card (it's free) and see if it works. I noticed your logs were different but both had to do with ARM9 crashing due to WCDMA (both times with varying feedback after ARM9 crashing, but both keeping WCDMA common in the kmsg). I looked it up and came across THIS in the cyanogenmod forums. It worked for both of these guys and the other dude basically flipped out on the other because he thought he was dumb, but it worked and ended up looking like a jerk lol.
Another log= http://db.tt/0dfJ4nYJ
Thank you very much for even bothering with my issues. Not to long after my last post the phone froze with screen off and did battery pull. Was able get another last log. I have done a format of everything and reflashed. Installed a few apps and did not do titanium restore. Going to look into getting new sim. Again I thank you and bow to your superior intellect:beer:
Sent from my MyTouch 4G using xda app-developers app