Related
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
GPS fubared?
No notification when charging usb
Hey guys i recently started having a problem with the back button.it will pick up half the time and then its unresponsive the time any ideas on what i can do?
Probably just lag. Which way did you flash dk28?
Btw, I came up with some other things.
1. Notfications are delayed (ex. Handcents icons in the top bar are sometimes delayed)
2. Keyboard delayed (its actually a bit worse than before)
Sent from my SPH-D700 using XDA App
*Keyboard/touchscreen/captivate button lag/failure to register action/press
*Streaming music skips (last.fm) while doing anything else; like browsing the web.
*Slow orientation change
*No lineout on multimedia dock yet
*None of the unicorns and rainbows flying out of the screen that were promised by the legion of unrelenting froyo fanboys littering this forum for the past month.
Sent from my SPH-D700 using Tapatalk
acer1096xxx said:
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, I guess a few of us got lucky. Just very small things such as checker boarding. I don't have homescreen lagg though, or widgets that disappear.
Sent from my SPH-D700 using XDA App
hardrock121 said:
GPS fubared?
Click to expand...
Click to collapse
GPS actually finally works for me with the update, I'm getting signal indoors in places I hadn't previously and it has yet to time out and require me to reflush the agps data or reboot the phone (used it all day today for work).
dannyzen said:
No notification when charging usb
Click to expand...
Click to collapse
Not seeing this one either, lets me know right away though the notification bar as per usual.
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
That's odd...maybe your phone is actually damaged then
Sent from my SPH-D700 using XDA App
I personally went back to 2.1, rock solid and stable.
On 2.2, Screen rotation is slow as molasses, GPS is stuck on my work location and would not work at all in updating. Browser was a bit slower compared to 2.1. Hated the scattered, non-alphabetical applications folder, wtf?!!
I enjoyed the 2.2 leak but the little niggles weren't enough to stay on it.
I did like the coloured menus, and the ability to turn off 3G when holding the power button for a few secs.
I keep getting errors when connecting to Wifi. I will look down at the phone and wifi will be off even though i never turned it off, and then the notification toggle wont do anything, and when I go into settings to enable it, it says "error" underneath the Wifi entry. Then it takes a few tries to get it connected again.
I do like where Froyo is headed, but this is absolutely no where near polished enough for final release.
Edit: Having a fully working GPS is awesome though. 2 meter accuracy = Awesome.
Does anyone else have lag when trying to adjust brightness on the notification bar?
LordLugard said:
Hated the scattered, non-alphabetical applications folder, wtf?!!
Click to expand...
Click to collapse
If you press menu > edit > menu again, there's an option for A-Z order.
Guess it doesn't matter now since you downgraded, but just thought id let you know.
Edit: lilxflip, yes. I'm getting the same problem but didn't notice that until now
Sent from my SPH-D700 using XDA App
I've noticed since 2.2 that when a caller hangs up, I get a single beep in my bluetooth earpiece confirming that the call has ended, which I like...didn't have any sound before that.
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
I must be one of the lucky few, everything works great, and not only that it fixed all the issues I had with the previous 2.1 build. I've tried out just about everything I can think of wifi, gps, 4g, pandora, etc.
edit: Should add, I did a factory reset after I installed it, wiped everything the only bit I loaded back in was contacts.
muyoso said:
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
Click to expand...
Click to collapse
Give the phone a few secs after the screen comes back on then press it. Works fine; if you immediately press it.. it doesn't hangup. Seems intentional..
Umm.. aside from no GPS now which I plan to fix by reflashing di18 then 2.2... I don't find any major problems. The keyboard does have a bit of a registration flaw but not too major..
The leds do light up whenever the screen is off.
And I don't think the brightness sensor likes my room light because it enjoys changing itself a bit.
Sent from my SPH-D700 using XDA App
I'm always weary about doing wipes, so to test if this is true, mid anyone else testing out this also to see if he's right? =P
punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
kenvan19 said:
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
Click to expand...
Click to collapse
Woah, just tried it. I had similar results. However, I opened the keyboard, let the flash disappear, then 2-3 seconds later it came back. And stayed there too, for about a minute or so!
Not really a big deal in my opinion; I honestly don't use the keyboard often due to its laginess..
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.
Hi all,
I've used the phone for about six weeks and now it starts to act strangely. Since yesterday it keeps entering car mode sporadically and stars the voice recognition app. A minute ago, it even displayed that it was being charged, even though the charger was not plugged in.
I guess this behaviour us due to dirt in the micro USB jack that has accumulated while carrying the device in my pocket. Possibly, dust particles bridge some of the USB pins and trigger the described functions.
I will try to clean the USB jack and report back. Blowing air over the contacts from my mouth was not sufficient, though.
Has anyone of you experienced such symptoms on your device?
If I can't fix this issue myself, I think I'll have the phone exchanged. Hope, that dust will also reset the custom binary counter, then...
For the record: I'm on Villain Rom 1.4 with CF-Root kernel XKF1.
Greetings
Yeh car mode came on with me after installing villain 1.4
I had other issues also like gmail force closing etc... 1.3 was fine but 1.4 made my phone go a bit cuckoo.
I'm on cognition now but I'll be back on villain at 1.5
Sent from my GT-I9100 using XDA Premium App
So a software problem it is... Couldn't google anything about it. Well, I flashed a stock backup KE2+KF2 CF-Kernel and so far my device behaves as it should. No car mode. I really hope it was a software bug. But it looked so much like a hardware fault...
Not sure if its the same case, but sometimes when I answer calls my phoes goes into loud speaker mode on its own... its annoying.
I had the same problem, but it it resolved itself after a few days. Maybe it is some dirt behind the home button.
It's there again! This time on Darky Rom 2 R1.
Same here. Stock SGS2 KG2 rom. Anyone found a fix for this ?
Had my phone since launch and it started to do this a couple of days ago and also draining the battery within 4 or 5 hours because the cpu was in constant use. Also i couldnt turn the phone off, it would just reboot and wouldnt charge. I had the same theory about the usb jack but didnt seem to make any difference. I did a hard reset but the problem was still there, strangely the phone appears to have sorted itself out not and is running fine!
Sent from my GT-I9100 using XDA App
There is other thread
Read here
http://forum.xda-developers.com/showthread.php?t=1132588&page=2
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!