Related
I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.
Luckily I dont get that issue, buy I think this is a good test :u
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?
it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...
Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).
There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.
tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.
kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.
I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App
Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?
y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu
Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App
mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu
My g tab is an amazing device as all you can attest to. However ive been running cm7 and now cm7.1 RC for a month now. I get random freezes constantly. Itll boot up and then once i get to using the tavle whether scrolling through a video or the app drawer itll freeze up.And can't do anything unless I do a hard reset ive searched endlessly for answers but got nothing ...please help..
All I can tell you is this. Cm7 has an extremely high volume of reports of problems. I'm amazed its still so popular.
I'm running CM7.0.3 stable for Netflix sake. Time to time I got freezes in Dolphin HD 5.6.
Sometimes I just wait and Dolphin would FC or tablet would go into reboot when I tried to put it in hibernation.
Well, as far as I know and my research on this and another problems - it's a nature of Android OS (not mature OS and buggy software for it).
Though I never got freezes from Netflix.
PS: might be overclock CPU to 1.4GHz is too much for your tablet. Try lower it to standard 1Ghz.
Vlad_z said:
Well, as far as I know and my research on this and another problems - it's a nature of Android OS (not mature OS and buggy software for it).
Though I never got freezes from Netflix.
PS: might be overclock CPU to 1.4GHz is too much for your tablet. Try lower it to standard 1Ghz.
Click to expand...
Click to collapse
nope. I'm running calk clem and have not had a single freeze. Calk and clem really struck gold with this one.
I run 7.0.3 and it has been the most stable Gingerbread ROM I have tried. No problems at all and much better battery life - Love it!
Sent from my GTablet using Tapatalk
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
just upgrade to 2.3.4 , i think this will clear ur problem...
We would use lagfix if the devs made it
Sent from my GT-I9001 using XDA App
gangstar said:
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
Click to expand...
Click to collapse
You realy have 2 options :
1. Go to warranty with it (if you have one)
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
larry200ro said:
You realy have 2 options :
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
Click to expand...
Click to collapse
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
can you describe what do you mean by screen/menu lag?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
All using TWLauncher? Have you tried another launchers (GO Launcher EX runs smoothly in my phone)?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
A reason might be a underclock of the processor in order to increase the battery life. You might want to install ROM Toolbox and check at what frequency is the processor working (the device will need to be rooted)
You can also check if the processor is getting hot >43 degrees(battery booster on the market can help you with that)
Please reply with response and if my post helped press on thanks
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Mikolak28 said:
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Click to expand...
Click to collapse
I'l advise you on how to flash it...give me a PM when you are available
2.3.4 not yet available ota
After Upgrading to 2.3.4 rooting and removing twlauncher I have no lag problems any more, ADW, Launcher Pro and Zeam are all working just fine. I know of others that have upgraded to 2.3.4 and still have a 2s lag when waking the phone so IMHO removing twlauncher may be key....
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Well I personally don't see the need for Kies apart from providing the USB drivers so that doesn't really bother me...... but if you were a big Kies user then I guess that would be a show stopper .....
Mikolak28 said:
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Click to expand...
Click to collapse
Personally I didn't remove TWLAUNCHER but just froze it(in case I need it later). I also made a backup with it and installed go launcher. I am very satisfied.
Edit : application is Titanium Backup (I think the best application there is for android)
I did what you said, and it still hasn't changed the screen sleep lag.
It might be a tad bit quicker, but not a lot.
This is a duplicate thread with http://forum.xda-developers.com/showthread.php?t=1284850
Basically there is nothing you can do except increase your cpu frequency which will decrease (drastically) your battery life.
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
igor_999 said:
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
Click to expand...
Click to collapse
Mikolas is refering to the delay the phone has when trying to unlock it. It takes about 2.5 seconds for the screen to turn on.
I also have no lag when waking up the phone .... after pressing home or power I get the lock screen in under a second. BTW if I monitor the current CPU frequency with setCPU then I can see it scale the frequency down to 245 while the screen ist still on and experience no lags when resuming phone use ..... if your experiencing lags of 2.5s then IMHO it must have another cause.
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
On any ROM/kernel combination I've ever used on my nexus s, any CPU stepping past 1000 MHz gives me random reboots whenever I launch google now, or games. I've never had this problem with any other phone/tablet I've ever owned (Nexus One, Nook Color, Samsung Galaxy S, Nexus 7) I've always been able to overclock to the highest stepping. Is something wrong with my nexus s? Thanks for any responses.
i'm on strawberry 10.31 with matr1x 24.0 running at 1320mhz with no problems at all for more than 2 days uptime. try flashing 'em.
i've been playing games and no reboots at all. i got i9023 by the way.
Not all phones like oc. Mine can't run above 1.1 and recently it ran stable at 1.2 with marmite (exceptional). You might have to play with voltages to make it right for your phone. Might take a while but it'll be worth it if you'd want to oc.
If not working, your phone just can't handle it.
Sent from my Nexus S
cmdrtomalacc said:
On any ROM/kernel combination I've ever used on my nexus s, any CPU stepping past 1000 MHz gives me random reboots whenever I launch google now, or games. I've never had this problem with any other phone/tablet I've ever owned (Nexus One, Nook Color, Samsung Galaxy S, Nexus 7) I've always been able to overclock to the highest stepping. Is something wrong with my nexus s? Thanks for any responses.
Click to expand...
Click to collapse
Anything over 1000 is an added bonus. Not all phones like to be overclocked or undervolted and such. Like for instance no matter what kernel/ROM combination I use I cannot run my phone at 100 as the low. I have to set to 200 as a minimum. I am however able to overclock. Sometimes just because the kernel has a lot of extras doesn't mean it's for the best.
ej8989 said:
i'm on strawberry 10.31 with matr1x 24.0 running at 1320mhz with no problems at all for more than 2 days uptime. try flashing 'em.
i've been playing games and no reboots at all. i got i9023 by the way.
Click to expand...
Click to collapse
I'm pretty much this. Can run games fine at 1320mhz.
But for some strange reason, google now is the one thing that reboots my phone, and I actually like google now, so I had to go back to 1200mhz