Related
I have a US Wifi Xoom and I recently flashed a AOSP OC Kernel and I'm scared that my Xoom will mess up. Today I unplugged my Xoom and it shut off by itself. I couldn't turn it back on the normal way. I had to hold volume up and power. I have a feeling its kernel related since I flashed it last night. Thanks.
For the US WIFI Xoom, follow the instructions on this thread to return to stock:
USA WIFI 3.1 Stock:
http://forum.xda-developers.com/showthread.php?t=1080963
Pretty straight forward.
Just out of curiosity, which OC kernel did you use? If you're pushing to 1.6GHz, it may not be as stable as others. There are others - 1.5GHz and 1.4GHz that you can try for more stability.
Tiamat's 1.4.2 Kernels:
http://forum.xda-developers.com/showthread.php?t=978013
Keep in mind though, these kernels are tested rigorously before deployment, so unless you decide to mess with the files themselves, you shouldn't inflict any harm on your XOOM with these Kernels.
I did the 1.5 kernel and I just found it weird because I saw a thread today about someone's Xoom not turning on.
Sent from my PC36100 using XDA App
Hello,
Is that possible to have an added kernel to theTiamat list: one without any OC?
Battery consumption is a big concern for me...
Sorry for the post in here but I'm still limited to Q&A on XDA.
You don't have to overclock even though you flashed an oc kernal. I have 1.6 oc and I don't oc at all.
Is there an option to turn off overclock or is the kernel supposed to work with SetCPU or another OC app?
If OC isn't set as default then that's a good thing because I don't see any advantage to overclocking the Xoom.
It was a scare and I don't want it to happen again. Is prefer the stock kernel to avoid any problems.
Sent from my PC36100 using XDA App
The OC isnt set by default. It is still set to the default 1GHz.
The kernel just allows you to overclock to 1.6GHz if you wish.
I had another weird reboot yesterday. The last thing I flashed was the kernel.
Might do that sometimes. Might be whatever you were doing. Or the xoom isn't used to the kernal, or just plain don't like it.
I just got a used G2x (traded for a Galaxy S 4G), and I can run a stock rom just fine, but ANY CM7 ROM causes Sleep of Death, or reboots (actually, both!)...I've tried multiple kernels, and can't figure it out.
It will SOD within just a few minutes...any suggestions?
mm0
If you are having problems with CM7, then you should try Weapon G2X or Faux's 1.3.1 AOSP ROM. They both are great. Weapon G2X is more for someone who wants a fully functional G2x, like A2DP and HDMI capabilities. Faux 1.3.1 with the trinity or faux kernel is for someone looking for a very fast phone. Though it does lack the HDMI and A2DP capabilities. You have to kind of pick which one you like more. If I was you I would try them both out and make nandroids of both of them and figure out what you like.
I'm on Weapon now, and it works great, except that there are just a few things that drive me insane with any stock based build...
I used Faux123's AOSP build, and it worked fairly well, but still had SOD issue's.
I was hoping that maybe there was a solution, but probably not...maybe I'll try to go back to Faux's build.
mm0
Got my transformer a couple days ago already got it romed, I'm looking for a kernal for it. I'm running the latest revolver, and I don't want to over lock it as I am satisfied with the clock speed, but I would like it to be undervolted. Anyone have any any suggestions?
Line up:
Asus Transformer
DroidX
OgDroid
I typically use Clemsyns 22a kernel. The reason I use this one in particular is because the wifi driver in this kernel allows my tablet to properly jump from access point to access point on a wifi mesh network at work, and its fast and stable.
I've noticed that Roach's kernel is a bit snappier than Clemsyn's at times, but with this kernel installed, my tablet doesn't work well at the office because it refuses to seemlessly jump to the closest AP. rather, it will try to hang on to the first one it connected to until the signal dies, then it disconnects and re-connects to the closest one. Its really really really annoying since I run around all day long at the office with my tablet.
Tonight I started using Blades latest OC/UV kernel that he released just this evening. So far its awesome, except voodoo sound module won't load for some reason.
So there you have my thoughts on the three common kernels. I'm liking Blades latest one a lot.... if it works with the wifi at work its my going to be my new daily driver. If not, well, back to clemsyn's 22a kernel.
a.mcdear said:
I typically use Clemsyns 22a kernel. The reason I use this one in particular is because the wifi driver in this kernel allows my tablet to properly jump from access point to access point on a wifi mesh network at work, and its fast and stable.
I've noticed that Roach's kernel is a bit snappier than Clemsyn's at times, but with this kernel installed, my tablet doesn't work well at the office because it refuses to seemlessly jump to the closest AP. rather, it will try to hang on to the first one it connected to until the signal dies, then it disconnects and re-connects to the closest one. Its really really really annoying since I run around all day long at the office with my tablet.
Tonight I started using Blades latest OC/UV kernel that he released just this evening. So far its awesome, except voodoo sound module won't load for some reason.
So there you have my thoughts on the three common kernels. I'm liking Blades latest one a lot.... if it works with the wifi at work its my going to be my new daily driver. If not, well, back to clemsyn's 22a kernel.
Click to expand...
Click to collapse
I'm so used to using android overclock that I'm confused at how to set the voltages and the slots or is this not possible? And thank you very much for the insite about the different kernals.
Line up:
Asus Transformer
DroidX
OgDroid
HaXERxPaYLaY said:
I'm so used to using android overclock that I'm confused at how to set the voltages and the slots or is this not possible? And thank you very much for the insite about the different kernals.
Click to expand...
Click to collapse
I use setcpu to set voltages and overclocks
a.mcdear said:
I use setcpu to set voltages and overclocks
Click to expand...
Click to collapse
How do you do that, I thought that just simpley had sliders and a drop down to change goveners? I guess there's more than meets the eye...
Line up:
Asus Transformer
DroidX
OgDroid
Bump.
Line up:
Asus Transformer
DroidX
OgDroid
Hey guys, I bought myself a Nexus S one month ago and I've flashed about 15 different ICS ROMs. Is it just me or are there almost no stable ICS ROMs? All of them had random reboot issues apart from AOKP and CM9. I had no reboots on AOKP but the clock got stuck every 2nd day, so my phone wouldn't wake me in the morning which is even worse. CM9 I liked a lot, but I couldn't phone in the hands free mode (don't know the propper name of it in english) because the mic wasn't loud enough. Currently I'm on ras cream sandwich and it reboots while i'm listening to music which is really frustrating. Oh and before i forget, I always flashed matr1x kernel and used smartass governor, no OC.
Is there any stable ICS ROM apart from CM9 and AOKP? Or can i fix the other bugs?
Thanks in advance!
Your problem is the kernel, not the rom. My phone also reboots while listening to music in the undervolted matrix kernel. Stay with rascream and flash the _thalamus kernel and see how stable it is. That kernel is really stockish and stable. If you don't want to flash you could try to raise your voltages to stock values in nstools. Some phones like undervolting, some not. ;-)
Verstuurd van mijn Nexus S met Tapatalk
hm I didn't know matrix kernel was undervolted, I thought that's only the case with trinity TEUV kernel by default well I'll try another kernel for the time being and see how that goes.
Yeah. Some of our phones can't handle the voltages mathkids kernel supplies outta the box unfortunately. Either adjust them back to the stock ones or search for another kernel. I prefer either thalamus or Simple Kernel. I just recently flashed the latest version of the former and its great. You can try Air kernel if you want a few more governors and whatnot.
Sent by pocket technology.
Like.. that's what STOCK is all about.
The people that made the phone are the most interested in making a stable ROM, no compromises.
Most stable and fast rom
Try APEX ROM 1.1.2 (latest release), that's what i'm using until aokp milestone 6 comes out. there is no lag, no reboots (just if u OC too much),...
Slim rom with no tweaks is smooth. Try it and u will not regret it.
Good luck
Vs Nexus S 4G
MIUI roms are very stable these days.
Sent from my Nexus S using Tapatalk 2
Well it differs from phone to phone. My phone is good with Matrix kernel. Might be one of the best custom kernels to run for my phone if not the best. Matrix isn't a compromise for my phone.
Sent from my Nexus S 4G
For several days I'm with Slim ICS and Matr1x and I have no problems with random restarts. No OC and no tweaks!
Try CyberGR ROM
I have installed CyberGR ROM and I have not suffered any reboot. I followed one by one all the steps of the development part and I'm quite happy with it.
Good luck.
Well, if you really want stable, get Stock 4.0.4. I'm on 1100+ hours on uptime without a single reboot... The only thing I've done to the stock 4.0.4 is getting root.
I would also like to know. from my own experience, stock 4.0.4 is best, but can CM9 very be made that stable? I'm running it now with ink kernel and no tweaks and it seems slightly laggy :/ should I flash brainmasters tweak pack?
Sent from my Nexus S using xda premium
Bugless Beast hasn't given me any issues. I've rebooted to flash other kernels but the only two kernels that have given consistent performance are Simple(stock with bln) and thalamus. Once I get my new battery, I may see how long I can go without rebooting. But if you want rock solid, go with stock ROM. Hell, my cousin has an EVO 4G and has almost 1200 hours up time. Lol.
Sent by pocket technology.
AOSP+ definitely belongs to this category. Stock with a few useful modifications.
You should try AOKP again
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Apart from stock, Have you tried BuglessBeast? Very stable. No need to flash any custom kernels.
if ur using ra scream use one of the trinity kernels. its super stable, super smooth, and long battery life
im using this black ice rom, in love with it .. shud try
alexfiorani said:
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Click to expand...
Click to collapse
I searched the internet and apparently I'm not the only one with that problem. I tried AOKP twice (i think build 32 or something and m5), always with matr1x kernel. Could this also be a kernel Issue?
I don't know that much about Android, but what I found out in the past days is that my Nexus S can't handle UV. I also get very high Android OS battery usage sometimes but I don't know why. High meaning Android OS once used more battery than display even though i had 2h screen on time. I suspect it's got something to do with titanium backup not restoring apps correctly, but that's just a stab in the dark.
Currently I'm on Apex v1.1.2 with stock kernel. No random reboots so far. I didn't restore apps via titanium backup (which was a pain in the ass). So far Android OS seems to use way less battery than before. But yesterday I had something like SOD when received a call while using TuneIn, so I had to pull the battery and call back. Not what I call stable.
I know that's a lot of text and probably also a bit OT sometimes but I hope some of you will read it , I'm not really a flashoholic and I'm getting sick and tired of switching roms, but I need my phone to be reliable. I'm really tempted to just switch back to stock ROM with stock kernel at the moment...
the things I'd really like to have is bln, notification toggles and stability.
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