Database Info

[Q] Can I get a DEV perspective?

So, I have had 6.1.1 since Dec. 20th, I have noticed that the battery on this ROM has been getting hotter than normal. It has been doing this since about 2 days after installing it. I never had an issue before with the other ROMs.
I have read the changelogs, and noticed that they made a slight Kernel modification in 6.1.1
Would this have anything to do with it?
Also, I noticed on ROM Manager that there is a 6.1.0 Stable and a 6.1.0 RC2
any differences?
I've since reverted back to 6.1.0 and I am doing some testing to see if it gets hot.
Any feedback is greatly appreciate.

I'm not a DEV, but I can try. Devs are usually somewhat busy. I never had heat problems on CM. Are you overclocked? RC2 is a release client. Wont be as stable. Cm6 1.1 is very stable for me and I have no problem. Also, stay away from ROM manager. Only causes problems. Try wiping dalvik and reinstalling in clockwork. I can't read the changelog ATM, but its most likely for performance, and shouldn't have an effect on temperature. I'm not positive though. Good luck and get back to me.
jbizz said:
So, I have had 6.1.1 since Dec. 20th, I have noticed that the battery on this ROM has been getting hotter than normal. It has been doing this since about 2 days after installing it. I never had an issue before with the other ROMs.
I have read the changelogs, and noticed that they made a slight Kernel modification in 6.1.1
Would this have anything to do with it?
Also, I noticed on ROM Manager that there is a 6.1.0 Stable and a 6.1.0 RC2
any differences?
I've since reverted back to 6.1.0 and I am doing some testing to see if it gets hot.
Any feedback is greatly appreciate.
Click to expand...
Click to collapse
Sent from my wonderful Aria

CM7 Graphical Bug

Has anyone else had problems like this? I'm running nightly 260. I went back to CM 7.1 stable to see if the bug existed in there and it didn't, the battery drain on that rom was pretty bad for me. So I changed back. I tested all then nightlies back to 255 and they also had this glitch. Anyone else experienced this?

Nightlies are never guaranteed to be completely stable. If you want better battery life try changing kernels, installing uv scripts and or use a different radio. These three things greatly contribute to battery life.

I use nightlies 260 since it came out never any problem beside the launcher fc from time to time still running it now still.Try redownloading and reflashing that might. Help
Sent from my Inspire 4G using xda premium

OverCaffeinatedHobo said:
Has anyone else had problems like this? I'm running nightly 260. I went back to CM 7.1 stable to see if the bug existed in there and it didn't, the battery drain on that rom was pretty bad for me. So I changed back. I tested all then nightlies back to 255 and they also had this glitch. Anyone else experienced this?
Click to expand...
Click to collapse
There was a graphical error like this with the beweather app with Absolution (CM based rom) but has been fixed since their latest release. If you really want to use CM ROMs, give Absolution a try. Like Gizmoe said, the nightlies are never guaranteed a stable bet.

CM10 CPU Frequency issue.

I tried to post this in the CM10.1 thread but apparently I need 10 post elsewhere first.
There seems to be a problem with setting the Maximum CPU Frequency option in cm-10.1-20130210-NIGHTLY-skyrocket. It will reset to default, or probably never sets, as soon as you leave the screen. The minimum frequency seems to work fine.
Unsure if the developers are aware of this but it would be cool if it could get looked at in the next release. I never game on my phone so I really have minimal reason to keep it above 1GHz.
Thanks.

Well it IS just about a week old..... Try using a different 4.2 kernel. I think there are 2 of them out there somewhere.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

this is a nightly non stable build. there is a bug report option somewhere on the cm site, i just forget where exactly. check the bug reports, and if its not there help the team by reporting it.

I have this same issue with with CM 10 Stable, the latest CM 10 nightlies, and CM 10.1 nightly. I am thinking its an issue that all of them have.

[Q] Which ROM for a stable flash/torch app?

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

Omni Rom vs EOS which one is more "complete"

I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.

AlphaW0lf2014 said:
I currently have the OmniRom 4.4.4 insalled on my Xoom Wingray device. I poked around and saw the EOS Rom. I'm really torn if I want to go and re-wipe and rebuild my device on the EOS rom. What's the pros and cons of each rom based on opinions of the users running each one. Please no flames or fanboys, just honest things you like about your particular Rom.
Click to expand...
Click to collapse
This whole section seems to be lacking people who are willing to or have experience with each releases. But what are your thoughts on Omnirom? Why did you choose that over CM 11 and now looking at EOS. Trying to get as much info as possible before i consider flashing this old tablet and squeezing more life out of it

I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.

AlphaW0lf2014 said:
I chose the Omnirom because it was the first I heard about. I wanted android 4.4.2 and it seemed all google searches pointed to Omni. Now after running it for a week or two I deal with bugs that I don't want to fight with forever. Volume control doesn't work, random chrome crashes and now tablet reboots. I tried to reach teamomni but no luck. And EOS has built and published nightlies more recently than omni. I know I'm pushing this tab!et beyond its years. I figure this is the end of the road for this device, so I want to squeeze every ounce out of it. I can't thank both teams enough for their work. It's more than I would be capable of ever doing.
Click to expand...
Click to collapse
This is what I'm doing as well. Hadn't used the Xoom in forever but figured I'd try to squeeze more life out of it at this point until Nexus 8 or 9 (whichever it's called) comes out. I was running Omni and kept getting "bug reports", so I've switched to EOS due to the fact that they are more actively publishing updates to the ROM.
Only been on EOS for a day or so, but so far so good. With No-frills CPU control installed the Xoom seems to be running fine with no bugs to report. Settings in no-frills:
CPU Max: 1.504 GHz
Min: 456 MHz
Gov: ondemand
i/o scheduler: row

I just want to restate that I value the time and effort of ALL of these developers who graciously give up hours of labor to do this work. I would hope no one is offended by any of my previous statements of issues.

Omni vs TeamEOS
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.

fricklr said:
At first I've installed Omni. I was very happy with it. But after some time I've got performance problems. Also Chrome was freezing many times while browsing around.
So I decided to switch to TeamEOS. I was a fan from EOS since the early days. They kept my Xoom alive. But unfortunenatly I got the same problems on TeamEOS with Chrome. It kept freezing.
Read http://forum.xda-developers.com/showthread.php?t=2738705 if you have the same problem.
At last I am also happy with TeamEOS and it's difficult to say which ROM is better. There are some differences in the preferences and Omni ROM seems to be a bit ahead but at last I'm ok with was TeamEOS offers.
Click to expand...
Click to collapse
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space

runandhide05 said:
The chrome issue boils down to a tegra video driver. It's closed source and has not been updated since the last official release which I believe was 4.1.2
This issue effects many things video related some of it you may see most of it you'll never notice. Since its a closed source driver it's likely to be and issue we will just have to deal with
sent from space
Click to expand...
Click to collapse
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.

After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom

AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
Are you able to cast screen with chromecast ?
I have de Omni 4.4.4 on my xoom and the cast screen do not work, even with mirror enabler app.

Xoom won't be able to, doesn't matter which Rom, it's hardware level, even if I add all the required files to the make file and enable it as soon as you try it reboots. It's the same issue with screenrecord
sent from space

AlphaW0lf2014 said:
I have switched to the Team EOS rom and have been happy with it, I have had the dreaded Sleep of Death bug that many users of the EOS rom have described and I do see the same Chrome crashes that I did on Omni. Now I've switched to Firefox and I don't have the issues.
Oddly I had none of these chrome issues on stock, and the only reason I upgraded from stock was to get Chromecast screen casting working from my tablet so I could use some of my apps on my TV.
Live and learn I suppose.
Click to expand...
Click to collapse
I've used each of the Kit Kat builds and I finally settled on TeamEOS. This ROM had the most updates and continued to have development after nightlies stopped for Omni and CM. I believe each of these ROM's are really great and each have given new life to our tired Xoom's. The only way you can really tell which ROM is best is to try them and see which you like the most. Hopefully, someday we'll be asking the same questions about which Lollipop version is best, or that may just be wishful thinking. TeamEOS is baked already OC'd to 1400 and you can tweak it higher if you want (I use 1600). I've downloaded Trickster MOD from Google Play and I use it to control governor and other settings. As far any SOD's, I believe you can really minimize the concern if you use Trickster MOD and adjust your CPU min to at least 312 or higher. I had an occasional problem with Chrome so I switched to Chrome Beta and it seems to cause less problems. Some folks will have problems while others seem to get by OK. The stock browser is still pretty decent and gives good performance. I also have the Dolphin Browser but don't tend to use it very much.
---------- Post added at 08:15 PM ---------- Previous post was at 08:11 PM ----------
fricklr said:
After some days of using TeamEOS... The battery usage seems to be much more better!
On the other side TeamEOS freezes from time to time. Only a reset helps.
But hey, there's KK on my Xoom
Click to expand...
Click to collapse
Try downloading Trickster MOD from Google Play and using it to set your cpu min to at least 312 or higher. This may help with freezes.