Related
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
+1-I am having the exact same issues with same setup although I do have AutoKiller and it is set to Optimum.
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Jason kiDD said:
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Click to expand...
Click to collapse
Sorry, I should've mentioned that I DID try the BFS kernel (9/28 build) and it was after flashing kernels that I noticed it (mostly coincidence I'm sure) which is why I flashed straight CM6 to rule out the kernel
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Jason kiDD said:
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Click to expand...
Click to collapse
It happened with the stock .5 RUU ROM with the only modification being AndROOT...I RUU'd it back to .5 this morning and am going to ride it out untarnished to see if the problem replicates again. If so, I believe I will have successfully found it's a problem with the phone itself, and at that point take it to Sprint and see about paying the $35 for an exchange. I would do the OTA updates but if this shows its fixed I don't want to lose the ability to root, and I don't want to have to RUU back to .5 in order TO root. I was really hoping a dev who understands these ROM's better than I could chime in with some thoughts, but I guess I'll just have to keep test and tuning...I definitely appreciate these responses, though, and I'm happy I'm not the only one having this issue (though I'm still not happy it's happening lol)
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
t12icky0 said:
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
Click to expand...
Click to collapse
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Matt262 said:
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Click to expand...
Click to collapse
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
t12icky0 said:
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
Click to expand...
Click to collapse
Gotcha...if you check out my post count I'm a n00b to these boards, but I appreciate you not blasting me like I've seen others have that happen to them (for not searching ,etc)...maybe a mod could move this for me so I don't clutter the boards?
Dono74 said:
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
Click to expand...
Click to collapse
Exactly! Now if a resolution can be found...since I posted this in the wrong section, maybe there is a resolution and I just wasn't in the right spot to see it...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Decad3nce said:
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Click to expand...
Click to collapse
Actually when I flashed CM6 last night with no tweaks I didn't even install SetCPU or any kernels...just the one that came with it capped at 691.2...no battery tweak or anything
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Jason kiDD said:
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Click to expand...
Click to collapse
Still a mystery to me as to why it's happening with more ROM's than just CM6 though...oh well, I'll see how stock .5 unrooted treats me this weekend, and if I have the same problem happen again, I know it's phone related and not to be blamed on a ROM (which I'd like to make clear -- I do NOT blame CM6, Fresh, or NFXHero for my issues. I know the dev's spent a TON of time building everything for us to have something we would otherwise NOT have, and my sole reason for this post is really to find out exactly what is wrong with my phone, not necessarily with a ROM, and most importantly to find out if I'm the only one experiencing these issues)...I do appreciate all the help and responses, and I'm thoroughly impressed with XDA and the responsiveness of everyone
Just in case anyone was interested at all, my phone completely bricked today (stock .5 running all weekend no issues) and the culprit is the touchscreen and all buttons but power stopped working...sprint's overnighting me a replacement so evidently something got too hot at some point or the like...thanks to all for the responses, and to those who had similar issues (not related to the ROM you're running) then keep an eye out for imminent failure lol
The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.
No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.
Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.
You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.
I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.
I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App
regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?
I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.
viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App
If missing with software and settings dont work you may just have a bad phone.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.
I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.
For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA
Hey guys,
The topic of this thread has change slightly since I started it. Please disregard the first few posts after this one.
The problem is that when I install a new ROM, it works perfectly for an hour or perhaps even the day, and then I start getting random shutdowns. These seem to start out of the blue and I cant work it out.
When installing a new ROM, I always check the MD5 and perform a superwipe before starting to use the ROM. Ill put back a few apps using titanium backup pro.
I don't use any hacked apps or task killers.
I have searched but cant find anything useful.
Currently using Insertcoin Sense 4 RC5. Firmware 3.32.
I have tried three different kernals (Bricked, Sebastian and RCMix), all with the same problem.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz with max screen off at ~500Mhz. Seems stable for now, been running 24hrs - no restarts.
This is interesting because I had a GB Rom running at 1.5Ghz with no problems, maybe its something to do with ICS.
Any ideas?
[SOLVED]
Sent the phone off to htc and they have replaced the motherboard. Its all fine and dandy now!
They dont know why it happened or how to avoid it in the future...useful, but if you're still in warranty then send it off, it took exactly a week to get back to me (Monday to Monday). Good luck!
Max
Well no need for factory reset. Superwipe? Yes.
What roms cause this?
What firmware is ur senny on? Ex: 1.17? 3.24?
Phone have physical damage?
Has it been wet?
Sent From Space Using My ICS Flavored Sensation
Thanks for your reply.
No, the phone is basically new, but as I said this has happened before.
Running this ROM on 3.24:
http://forum.xda-developers.com/showthread.php?t=1468683
But this does happen on other ROMS too, they work perfectly for a while and then slowly begin to develop problems. At this stage I usually install the latest version of the ROM but I'm actually happy with the ROM at the moment and dont want to have to keep changing it!
I've been running Darkforest ROM since early stages and have had no problems so far. Maybe try that one. It's on v 5.1.5 now and it's very fast and very stable, moreso than many other ROMs i've tried.
Could be a defective device possibly? Are u using the kernel that comes with the rom?
Sent From Space Using My ICS Flavored Sensation
I would download 1-click cleaner and clean the cache every week. Also you might want to boot into recovery and wipe cache and dalvik cache every two weeks.
Sent from my HTC Sensation 4G using XDA App
I dont think there is anything wrong with the device, I'll try wiping the cache's and see if that makes a difference. Thank you very much for all your answers so far.
Max
Could possibly be an app try removing all your apps and install 1 by 1 give it a couple of weeks see if it happens again, I got a problem from juice defender pro (payed for) worked alright for few days then my launcher started force closing all the time took me ages to figure it out but got there by removing all my apps and installing them 1 by 1 long and time staking but worth a try
Sent from my HTC Sensation Z710e using xda premium
Okay well ive tried clearing the cache and davlik cache with no luck, less restarts but they are still there. I am resistant to start removing apps as I use them on a daily basis. Before I try this, does anyone have any other ideas?
Thanks,
Max
I have the same problem :/ it happens in both GB and ICS but It never happened to me till about 2 or 3 months ago
Sent from my HTC Sensation Z710e using xda premium
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
darksupernova said:
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
Click to expand...
Click to collapse
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
ardom said:
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
What other information would you like?
I think it may be a kernel issue, I'm going to try a few...
Tried three different kernals now, all with the same problem which would indicate its not a kernal problem? Something else perhaps? (Tried bricked, sebastian and RCMix)
its not a problem, its with network connection
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Danyal93 said:
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Click to expand...
Click to collapse
Pretty sure its a power/bat problem for me.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz
Any ideas?
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Having EXACT ones you are having. Buy another battery if that doesn't work its a hardware problem. I still need to buy my battery but will post and let you know if it worked.
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
darksupernova said:
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Click to expand...
Click to collapse
I'm also starting to think its caused by not letting the battery fully die and recharging it a lot but that's just my guess?
I switched back to gingerbread yesterday and so far I've had no problems which would indicate its not a hardware issue...? Usually by now I've had a few shut downs..
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
sickorwuut said:
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
Click to expand...
Click to collapse
Yeah the problems started again for me on gingerbread. I've read its a motherboard problem I think I'm gonna have to send it off to HTC... Great... 3 weeks no phone...
I just got my G2x from my Optimus V and I'd like to flash a new ROM. I've already rooted it. What ROM is stable and as close to pure Android as possible? I hate all the bloatware that come on these phones from the carriers. I've been reading through all the ROMs in the Dev section but my head is spinning.
If you want super pure, your best bet is probably to stick with stock, since the G2x came with vanilla Android. Use Titanium Backup to freeze/uninstall all the bloat you want gone.
Sent from my LG-P999 using xda premium
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
Thanks, I actually flashed 7.2 a few minutes before I read your post How do I flash the new Kernel?
EDIT: Nevermind, got Faux 050 flashed
bg1906 said:
CM7.2 Official with Faux v50 Kernel. I back the OC down from 1.5 to 1.2 and its suber stable and fast. To help make it even more responsive I use Auto Memory Manager (https://play.google.com/store/apps/details?id=com.lim.android.automemman) set to Aggressive. I've also used Weapon G2x but prefer CM7.2
Click to expand...
Click to collapse
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
Yup, I've been reading a lot and saw some of the things you've mentioned, but thanks for the ideas.
I haven't touched basebands, should I do anything with them?
I'm on 7.2 Stable, do I need a new kernel to OC/UC? I can't seem to get it to work as nothing comes up when I'm in the CM menus.
I'm familiar with nAndroind backups as I did them religiously on my last Optimus V phone.
EDIT: Nevermind, I flashed Faux 050 now and can OC/UV now.
Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...
hairycheapo said:
Looks like you are doing fine. Congrats on figuring out how to flash a Rom/kernel.
Faux 050 stable and CM7 based Temasek rom is what I've been running for weeks now. If you don't have obnoxious static during phone calls (sounds like loud popping) - you don't have a baseband/rom compatibility issue. The baseband is just the firmware that controls the various radios in the device. Some have reported clearer calls and quicker GPS with the new (March 2012) baseband, but the hassle of upgrading to it is - well - a hassle. Also, If you use like to use bluetooth for calls, you need to NOT upgrade...
I am on the new baseband (I don't have blueteeth) and I'll sometimes need to flash the compatibility fix that enables you to run the new baseband with roms designed for the old baseband (or now, for roms/basebands on our international cousin the LG P990). Check owain's Domination thread for his "baseband fix", it will probably come in handy since some roms authors are not clear about whether their rom is for the new or old baseband.
You would just flash the fix through CWM after flashing a Rom, if you find that you have the call sound static...
You might also need a free app called "Get Ril" to fix your Radio Interface Layer. It automatically checks for compatibility and will automatically apply the RIL it detects that you would need if your calling sound has static.
---------- Post added at 01:27 AM ---------- Previous post was at 01:18 AM ----------
Also-
If you are comfortable with backing-up and restoring Nandroids, don't be afraid to at least sample some of the ICS builds. IMHO we have some awesome developers making the best of things considering the massive handicap that is presented by Nvidia withholding the drivers. ICS is getting more stable all the time. Fixes are now being incorporated that address memory-bleed issues, data-dropping, browser rotation crashes, missing APNs, and various stability improvements. Still probably not "daily driver" for most people, but you could be your own judge...
Click to expand...
Click to collapse
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.
Superorb said:
Things seem to be going well with CM7.2+Faux050. I'm waiting till the end of the month for my Virgin Mobile month to end before I start up with T-mobile $30/month plan so I won't know if calls are clear for now. I'll try gVoice sometime soon just to test it though.
EDIT: Once I'm sure this ROM/Kernel is stable I'll do a nAndroid backup and play around with some of the ICS ROMs.
Click to expand...
Click to collapse
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...
hairycheapo said:
I sometimes use GrooveIP with google voice. U 2? Mine works ok and I am thinking of cutting back the number of T-Mobile minutes I pay for each month. Let me know how internet calling works for you...
Click to expand...
Click to collapse
I use GrooveIP on my other phone where it doesn't work on 3G b/c VM service is so ridiculously slow. It should work on 4G though, but I won't be able to test until the end of the month.
Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...
hairycheapo said:
Gotcha. Be aware too that T-Mobile's "4G" is really more like 3G in most places. I see speeds between 2-5 Mb/s. I really only use my GrooveIP at home on my relatively fast Wi-Fi so I am not going to be the best person to talk to about how well it all works on T-Mobile's data network at our "4G" speeds.
Anyhow, its been good chatting. I gotta get some sleep now. Night...
Click to expand...
Click to collapse
Well, when you come from 100-140kbps 2-5mbps is screaming fast! As long as data is reliable inside buildings around town I'll be a happy camper. It's late here too, but I can't stop playing with my new phone
I spoke too soon... Battery was at 50% a minute ago and now it's stuck on 100%. Tried rebooting and wiping battery stats but no good.
hairycheapo said:
CM7.2 (really any CM7 based Rom) is the way to go. Stay away from ICS if you just want everything to work since Nvidia iz not releasing drivers needed for hardware acceleration on the G2x.
Few things to watch out for...
1. Memory managers/app killers are generally a bad idea for stability/battery life
2. Watch what baseband you are on. March2012 has broken bluetooth calling. You may need owain's baseband fix to patch an incompatible rom with your baseband.
3. Some CM7 users have better luck with Morfic's Trinity kernels vs Faux.
4. Lots of overclocking will likely result in stability probs regardless of your Rom/kernel combo (beware of undervolting too)
5. Stock 2.3.4 is now a viable option for stablity. + u could even overclock with Faux's 014b kernel for rooted stock.
6. Read the forums!
Get comfortable with making backups in CWM (oh you shouldn't use CWM Touch - or ROM Manager to flash anything - CWM 5.0.2.0 is fine) That way u can expriment, but restore back if it all starts going to shjt.
Click to expand...
Click to collapse
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?
FatalityBoyZahy said:
What's wrong with CWM Touch? I've been using it for the past few months with no problems whatsoever.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
It's the lack of proper ext4 support.
hairycheapo said:
There were some problems flashing some things with Touch. I can't remember which right now. Maybe Trinity kernels?
Click to expand...
Click to collapse
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch
I'm on the latest CM10 Nightly and the included Torch works fine.
LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10
tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze