Related
Hi, there!
Before I get started here, let me apologize if this subject has been covered before. I can't seem to get the forum keyword search function to return any results--at all- and I don't have time to read pages and pages of threads to find what I'm looking for. If there is a better place for this, please let me know.
I'm new to the Nook Color, and I'm running CM7 nightly release from 07/02/11. I love it, but I have some questions and a comment.
When the app drawer is open and you long-press an icon, it used to put a shortcut to that app on the homescreen. now it brings up this weird little submenu... What exactly does, "Choose Catalog", mean and what does it do for us? I REALLY miss that long-press to add shortcut to homescreen thing. Is there a setting that I can change to re-enable it?
Is there a specific thread to use to give feedback and ask questions about the nightlies' that is for the Nook Color only? I saw one for the nightlies, but it seemed that it was mostly irrelevent to us since all manner of devices--includung phones-- were being discussed.
I've just been using the CM7 nightly releases with Google Apps installed. Am I missing something by not installing Dalingrin's clockwork mod kernel? I was afraid that it was a replacement--not an addition-- for the CM7 nightly build. Should I install it? I'm sure I'd like to overclock my Nook to over a gigahertz, but I wouldn't like losing the stability and fumctionality of the nightly build I'm using.
Thanks in advance for any assistance y'all can offer.
Looks like the launcher is sorta corrupt. Try a different launcher that will work. Go Launcher EX (free) on the Market. Launcher Pro Plus is the best I think but it costs a little amount. Oh, but if you want to really stick with the stock launcher, go into Settings>Applications>All>ADW Launcher. And uninstall it. Then re-flash CM7 Nightly + Gapps and it should be restored.
First... on the launcher screen... use menu... more.... make sure homescreen is not locked.... Then it will do as you're used to regarding placing on launcher screen.
Actually... you don't have to unlock desktop... just wiggle finger when the menu you are talking about is up.... you will have to unlock desktop to move the item or delete it if you want.
Now I will edit this to answer more... just wanted it posted before you did anything as drastic as replacing or reinstalling your launcher...
The CM7 user thread in the Nook Color section is a great place for discussing all things NookColor CM7 related.
What the catalog does is....
You can place apps in a catalog... then when you're in app drawer then the left and right app launcher buttons turn to < >... use them to move between catalogs... ALL apps will still show everything... but in each catalog will show only the apps you add to it... so you can create a catalog called "Utils" and place all the Nook Color and CM7 utilities in it... scroll to is and ONLY those apps will show on the screen.
As for Dalingrin's OC kernel... if you're not using it and his NookTweaks... you are TRULY missing out... STRONGLY encouraged to use them.
Oh and don't OC past 1.2 GHz in NookTweaks.... it will give you SOD every hour.
Thanks for the quick response. I didn't know about the long-press-and-wiggle technique, and it worked like a champ.
Do I have to start over to install Dalingrin's mod? Does it replace this operating system entirely?
ionizd said:
Thanks for the quick response. I didn't know about the long-press-and-wiggle technique, and it worked like a champ.
Do I have to start over to install Dalingrin's mod? Does it replace this operating system entirely?
Click to expand...
Click to collapse
No you don't have to start over... just flash it after anyof the nightlies... any time after.
Always remember...
YCGIYWG
(You Can't Get... If You Won't Give)
ikingblack said:
Oh and don't OC past 1.2 GHz in NookTweaks.... it will give you SOD every hour.
Click to expand...
Click to collapse
Really? What about some people reporting being able to go up to 1.6 ghz? One of the reasons I bought the NC was in hopes that it could run 1.3 or 1.4 ghz stable.
ikingblack said:
Oh and don't OC past 1.2 GHz in NookTweaks.... it will give you SOD every hour.
Click to expand...
Click to collapse
That is a pretty dumb blanket statement especially when there is a percentage of users who have hit 1.3GHz and higher without getting a sod. I get them less then once a day. I used to get them as often when I was at 1.2GHz. So please don't misinform people
Sent from my NookColor using XDA Premium App
psychoace said:
That is a pretty dumb blanket statement especially when there is a percentage of users who have hit 1.3GHz and higher without getting a sod. I get them less then once a day. I used to get them as often when I was at 1.2GHz. So please don't misinform people
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Well, when I went any higher than 1.2 GHz, I got sod every other hour. When I clocked up to 1600 Mhz, the thing got SOD like every 5 minutes.
EDIT: @PoisonWolf, do you know how to get up to 1.6 GHz no SOD? I would love to be faster than the Flyer... which is double the price.
C'mon, people. We provide feedback based on our own experiences and it's not always 100% true but still, no need to use harsh words to correct the mis-info. Be nice and together we can build a strong community.
Anyway, even though I'm using Dalingrin OC 063001 version and nookcolortweak installed, I cannot ever seen any option to overclock greater 1200MHz, how do you guy get up to 1.3GHz, left alone 1.6GHz? What kernel do you use?
ikingblack said:
Well, when I went any higher than 1.2 GHz, I got sod every other hour. When I clocked up to 1600 Mhz, the thing got SOD like every 5 minutes.
EDIT: @PoisonWolf, do you know how to get up to 1.6 GHz no SOD? I would love to be faster than the Flyer... which is double the price.
Click to expand...
Click to collapse
Well, to be able to get up to 1.6ghz, that is really the luck of the draw. I would gather that the manufacturing process is not perfect and not all chips can achieve such speeds. If anything, I would imagine there to be a range on the "limits" of these chips.
I found out that mine was 1350 mhz. No matter what I did, anything higher than that resulted in clunky responses, choking, skipping, etc.
I was hoping I'd get something in the 1.5 ghz range, but ah well.
Thus, I now run it at 1.3 ghz ondemand!
Just tinker around with the combinations / voltages / governors to see what your true limitation is. While you are doing this, do NOT set anything ON BOOT.
votinh said:
C'mon, people. We provide feedback based on our own experiences and it's not always 100% true but still, no need to use harsh words to correct the mis-info. Be nice and together we can build a strong community.
Anyway, even though I'm using Dalingrin OC 063001 version and nookcolortweak installed, I cannot ever seen any option to overclock greater 1200MHz, how do you guy get up to 1.3GHz, left alone 1.6GHz? What kernel do you use?
Click to expand...
Click to collapse
Same Kernel with U.
Most Nooks go around 1.200-1.300mhz.Some few lucky can go a bit more.
Got it,
Thanks Ras
For CM7 we had a thread with all the known major issues (and solutions) for the most recent roms.
CM7 now is almost perfect and pretty complete. CM9 is still in alpha though and (obviously) seems to have a lot of issues.
Can someone who flashes nightlies / kangs please give a short overview what doesn't work or what does cause problems? Also stability and power issues would be interesting.
Of course there are still problems with video hardware acceleration but what about other areas which are GPU relevant like browser, games or any app that isn't just a list really? What about the sound drivers, do they work in general? does listening to music while using other apps work that also output sound (for example music + navigation or podcast + navigation)?
I think this would be very helpful to a lot of people (me included of course )
Why didnt i think of that?
Silly me that reads this tiny thread... http://forum.xda-developers.com/showthread.php?t=1347118
I didn't find anything useful via search which I didn't know from blogs / g+; as I didn't want to read up on as of now 1256 posts in that thread I had hoped someone could take 1 minute of his time and give a quick run-down.
I was hoping for a serious answer or a sarcastic one which took at least as long to write but would be really douchy. You just linked the thread so I'm not sure what to think lol
i use cm9 daily and i have not seen much problems. its smoother than any other rom i used, the battery holds much longer. whe listening to live streams it would not last longer than 6.5hours, yet on cm9 it holds for 9.5, i also dont need to charge every night or have the battery drained in the morning which was the worst thing and happend for me on all the other roms.
what does not work... let me see, the latest version of opera doesnt work. sometimes it takes a long time to get a data connection, but i think that is because my wifi switches on and off a lot. other than that i dont have any problem and i definitely wont go back to any gb rom.
Sent from my LG-P990 using XDA App
i havs battery extra, but ill wait for a cm9 stable
Sent from my Desire HD using cyanogen mod 7 on tapatalk
grognaz said:
i use cm9 daily and i have not seen much problems. its smoother than any other rom i used, the battery holds much longer. whe listening to live streams it would not last longer than 6.5hours, yet on cm9 it holds for 9.5, i also dont need to charge every night or have the battery drained in the morning which was the worst thing and happend for me on all the other roms.
what does not work... let me see, the latest version of opera doesnt work. sometimes it takes a long time to get a data connection, but i think that is because my wifi switches on and off a lot. other than that i dont have any problem and i definitely wont go back to any gb rom.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Thanks a bunch dude! The improvement on the battery from stock to cm7 was awesome already, getting even more out of it would be great. I assume you are listening via 3g right? getting more than 6 hours is quite an achievement there.
I switch a lot back and forth between wlan / 3g though so I guess I have to wait a bit for that to be sorted out.
razorblade79 said:
Thanks a bunch dude! The improvement on the battery from stock to cm7 was awesome already, getting even more out of it would be great. I assume you are listening via 3g right? getting more than 6 hours is quite an achievement there.
I switch a lot back and forth between wlan / 3g though so I guess I have to wait a bit for that to be sorted out.
Click to expand...
Click to collapse
no im listening over wifi, but the battery usage reflects all over for me, usually i had to worry about my battery even on 2g, now i dont have any worrys, even on 3g it lasts longer than on 2g before.i guess its because it basicly uses 0 battery while not using it while on other roms it constantly drained as if i was using the device.
Sent from my LG-P990 using XDA App
I've been using Nova HD for a week now and even though I was sceptical at the beginning, I'm really happy with it. It's fast, no random reboots yet, no force closes. The battery is not super, but is is ok: I think I can use it for a day with normal use. I'm not going back to CM7
I'm baffled and trying my very best to work out why I'm getting the BSOD on this phone. There appears to be no logic or pattern to when it occurs, so it's very difficult to diagnose what's causing it. I've now had two of these phones where it has occurred. The first one I took back and got a replacement under warranty. The second one worked like a charm on stock GB with no flashing of basebands, but since messing about and installing both CM10 and the latest ICS ROMS it's started happening again.
It seems to occur most when I go to charge the phone. It'll just die a death and I'll have to take the battery out before it even thinks about starting up again. Perhaps the most annoying thing of all is that it resets all time and dates and will then fail to use the network provided settings.
Has anyone else had this problem and found a solution that works long term? What about the cause? The strange thing about it is that it can go for a week without doing it...then, it'll happen twice in one day. And it's getting frequent to the point of being very irritating. I'm wondering If a different baseband would help. It currently detects it as unknown, but if memory serves I flashed the old 528 original stock baseband for use when I first installed CM10.
I have experienced it in every rom (I have experienced it in: cm10, all GB roms Ive tried, all ICS roms etc..) but not in cm 7 ... so I usually go back to that rom most of the time..
What baseband are you using? Whether or not it has anything to do with it I don't know. Desperately trying to find a fix. I'm thinking it can't be a rom issue. I'm just hoping it's not the phones hardware.
Sent from my LG-P990 using xda app-developers app
The worst thing is don't know how we carry cm10 bugs after flashing over different roms even with full wipe..I lost my amazing battery life after cm10 flash got new battery calibrated food full wow did smart flash still battery life drains like in 10% in hour even without any use....gross
This bug has been reported in the CM10 Bug Thread, you should take a look at it.
Basically the workaround is to turn on your screen before plugging the phone to a charger. There are users saying that they also have a lot of BSOD's when plugging the phone in CM10.
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
You seem to be in a foul mood lately, passing such comments on all threads.
And for your info, increasing min cpu clock frequency has no effect on cm10 bsod. It may work in some roms, but not on this one.
Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
Dude if you read my post im saying it occurs whether cm 10 or not. Changing clock frequency did nothing for me so thanks for pointing out the obvious. Like i say, it's a problem I've always had with this phone whether I was on stock gb or not and im getting sick of it. I just wondered if anyone knew the reason and a sure, concrete solution.
Sent from my LG-P990 using xda app-developers app
I am on CM10, and I never get random BSODs. I am on the 11/20 nightly.
For me, the one and only time a BSOD occurs is if my screen is off, and I plug in the charger (USB or wall), and the charger doesn't cause the screen to turn on automatically. If the screen turns on the moment the charger is plugged in, I won't get a BSOD.
My "solution" at the moment is to always turn on the screen before plugging in my charger. No more BSODs.
I used to get random BSODs even off the charger on earlier nightlies, but after 11/10 it was all right.
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
haunterx said:
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
See this is my point.. Just how many folk are having this problem with the device? I might contact LG support to see if it's a known issue. I have it both whilst charging and not whilst charging. A Google of the topic does support a fair number of everyday stock users as having this issue. I just don't think it's a rom specific issue. The occurance is so spasmodic I think it's simply coincidental.
Sent from my LG-P990 using xda app-developers app
withoutwings said:
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
Click to expand...
Click to collapse
Same here. With CM7, very, very rarely would the phone just "die" with a black screen when charging. If I had it plugged in via USB to my computer and then immediately plugged into the wall charger, it would almost always BSOD. The only way to recover was to unplug it, pull out and re-insert the battery. This happened so rarely (especially if I always rebooted the phone after using USB) that it wasn't a problem for me.
With CM10, it will instead BSOD if it's just left idle with nothing connected. This happens 0 to 10 times a day with no logical pattern. Some days, I almost think the problem is gone, others the phone is almost unusable because it keeps dying. It has never had a BSOD while charging. This has happend with every nightly build of CM10. I've also had the problem where the caller/person I call just hears "dialup modem" type noise.
Monday evening I flashed SU660 V30c baseband. Still no BSOD as of today (noon on Wednesday). However it has gone this long without BSOD before, so fingers crossed. I have a "Made in Korea" P990 and it previously had Baseband 20I-EUR. Also going to do a few test calls to see if the noise problem is still there.
That's very useful to know. As you say the problem is so bizarre and so random that's almost impossible to know until weeks later if it's been solved for good. I just hope that final ics and baseband release will put the issue to bed once and for all. Can anyone confirm whether or not they have had this issue with the latest leaked ics baseband?
Sent from my LG-P990 using xda app-developers app
48 hours without a BSOD after flashing BB 30C however now calls have gone completely quiet. Neither party can hear a thing.
Back to the drawing board :silly:
Is anyone else's phove really hot when BSODed or is it just mine? When I was on Gueste 3.6 everything was ok until it BSODed, that's when cm10 came out, tried it, changed a few basebands and didn't have it for almost a month, suddenly a few days ago while I already returned to default bootldr and partition sizes on gueste 3.8ext3 with v28g bb I think (20121110)
Sent from my Optimus 2X using xda premium
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
neovdr said:
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
Click to expand...
Click to collapse
Truth is that I always use root uninstaller and remove the stock browser and this is the first time I haven't. Hmm... let's see...
Sent from my Optimus 2X using xda premium
I think BSODs occur when the relationship between rom, kernel and baseband is not so good.
Yes it appears to be that way. Unfortunately we don't have a BB for the P990 that works properly with ICS/JB ROM (call audio bugs etc.), which is why development of CM10 for P990 was abandoned. I'm now back on CM 7.2 and everything works as it should.
I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium
kaiserXDA said:
I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm not so sure what MPD is but Corn kernel is on GB. Therefor, there's no developping nor support being made for it, which could explain why you got no answer on your previous post.
Luckily, you can get in recovery. Make a backup, wipe cache/dalvik and try to boot up. If that doesn't work, back in recovery, wipe cache/dalvik, factory reset and reflash your ROM. Altough, I would suggest looking at the newer ROMs out there as we're up to JB 4.2.1 (you're on GB 2.3.5).
If you go ahead with the upgrade, make sure you follow the full instructions in the OP.
Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium
kaiserXDA said:
Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Wait, the collective? The Collective and The Family used to be one team.. Yet I dunno what you mean by MPD?
And if you're looking into something stable, I would highly suggest either AOKP or AoCP (4.1.2).
MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium
4-2ndtwin said:
MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Oh I see, was made while I was away. Thanks for the clarification 4-2ndtwin
What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
kaiserXDA said:
What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
If you look up, I already made 2 suggestions
AoCP or AOKP (4.1.2)
kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
There are also tweaks in recovery that u can choose from and even the ability to change the partitions to Ext4. Check the kk4 corn kernel's op for info on these things.
I use my cappy for work and pretty much have stock kk4, with Root, debloated, Ext4 on all partitions and the tweaks i have are sio Scheduler and smartassv2 Governor. Runs great !
Sent from my SGH-I777 using xda premium
I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK
kaiserXDA said:
I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK
Click to expand...
Click to collapse
OC = Overclock
UV = Undervolt
SoD = Sleep of Death
I don't suggest changing voltage on the cappy (UV). The processor isn't strong/fast enough, therefor it takes more time to process what you ask of it = more screen time = more battery drain. While screen off though, your battery will be better (can also cause black screen and SoD at unstable state). Screen on is the main battery drain for androids. So basically, reducing your voltage (UV) will lower your battery consumption, of course at a price = slower processing and despite you intention to reduce battery drain, it might increase it. The Captivate has proved to be quite unstable with OC/UV on GB and up.
Up'in your Mhz (OC) will make your phone faster but at the cost of faster battery drain and faster hardware usage. On top of that, both can make your phone unstable. Finding the right combination can take some time if you really wanna get into it. There are guides about it which you can find with a little search, altough, once again, I don't recommend it.
Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again
kaiserXDA said:
Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again
Click to expand...
Click to collapse
Hehe np. As for what happened before, pulling the battery most likely reseted your kernel settings (OC in this case) as it probably wasn't ''set on boot''. Probably saved you a lot of hastle too
OK, I know the battery life issue for 4.2 ROMs has been beat to death, but I've got something weird happening with AOIP on my phone that doesn't happen with other ROMs.
Basically, when I'm at work, the battery graph (from Battery Monitor Widget Pro) looks like in the AOIPbattery image attached below.
As you can see, it ate all but 3% of the battery in about 11 hours. At times Battery Monitor Widget Pro indicated it was using the battery at 11%/hr or more! This is while I'm at work, and the phone is not doing anything, just sitting on the desk with the screen off, connected to a wifi network but not doing anything with that either.
After a few days of that, I decided I needed to try something else. Originally was going to go back to my "old reliable" backup of 4.1 Rootbox, then thought instead that I'd try the last build of 4.2 Slimbean I still had as a backup. Restored that and got all my current data for the apps reloaded, seemed to be working fine (though still had the stuttering and dumping of apps issues, which was why I wuit using it). Thing is, it's using battery not much faster than the Rootbox one did. See the SlimbeanBattery image to see how it did at work. Same scenario (sitting on the desk, connected to wifi, screen off almost all day). The little bit of high usage was while I was at lunch, reading some web pages and rss feeds, so the screen was on for about a half hour.
So, I'm wondering what the heck is making it use batter so fast on AOIP? I tried several things before switching to Slimbean. Airplane mode made no difference. Used Wakelock Detector to see what was using it up, and it was some part of Android OS making AlarmManager go nuts with wakelocks.
I even backed everything up, factory wiped it a couple times, then loaded the base AOIP 6/3 ROM and loaded GAPPS to see if it still did it.
Nothing seemed to make any difference.
In one sense, I'm hoping the new build that keeps getting hinted at might correct some of this, but I kinda doubt it considering how everyone who brings up battery issues usually gets treated.
That's normal for 4.2 Roms
Sent from my HTC One X using xda premium
I see your point, why does one 4.2 room use that much more battery life then the other, it makes no sense to me. Maybe camcory can shed some light in this issue
Sent from my SGH-T679 using xda app-developers app
That's how my battery life has been on all 4.2 Roms. If aoip is worse for you then most obviously you need to switch Roms.
Sent from my HTC One X using xda premium
I really was hoping that you would see that there might be something wrong with AOIP and take a look at it at least, and not throw out the same tired response. While I do appreciate the work put into AOIP, forum thanks have not happened due to the refusal to notice the glaring issue that everyone else does.
I would really like to know if you even read my post, Smartguy? Seems not or you would have noticed that AOIP in that scenario eats battery three times faster than another 4.2 ROM. Why?
I'm not trying to upset anyone, just trying to hopefully get this resolved in an amicable manner.
Some people don't have battery drain issues that bad with AOIP. You should keep in mind that this phone was never intended to run anything above gingerbread. Every one of these phones handles issues differently, which is unfortunate, but if a Dev doesn't have the same issue it is hard to address. Its just how it is.
Sent from my SGH-T679 using xda app-developers app
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
smartguy044 said:
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Wow hard to believe (well not really) this horse has been beat to death more times than a cat has lives! I'm pretty happy with battery life for the performance and OS I'm getting with AOIP. No hiccups and I have access to all the latest android features. The phone has a small battery anyway so if you want better battery life, time for a new phone or switch to a Gingerbread OS. I charge the phone once a day typically so that's hardly an inconvenience.
Thing is there is something major different in AOIP, as I can typically get just over 24 hours out of this battery in anything other than AOIP, including while I'm at work where the battery usage is a little higher than at home in every ROM I've tried (4.1 and 4.2 based included).
AOIP for some reason eats battery at more than 10% per hour only when I'm at work (less than 3% per hour at home) even when I haven't loaded any apps.
Every time I look at what is using it, it is either "cell standby" or "android os" that is using the most with the other of those two second and the screen usage following in a distant third.
I've tried to figure out what specific item in those two are the source, but it always comes back to some generic service or component in the os that is used by almost everything.
Really any advice to try and improve this, other than "use another ROM", would be appreciated.
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
get a new battery. i dont know what else to tell you. if you are getting 24 hours out of every other 4.2 rom youll be the only one. as i stated i get 10-11 tops on ANY 4.2 rom. so you have 2 choices new battery or different rom
Best thing to to is kill background data turn off Bluetooth WiFi sync and locations when not using your phone for a couple of hours. But your best bet would spring for an 2900mh battery.
tazmaniondvl said:
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
That was the first thing I thought, but it acts the same.
Sent from my SGH-T679 using xda app-developers app
im going to vote you get a new battery if its that big a deal....:good:
go back to gingerbread OS. we gave you suggestions already. 1) new battery. 2) gingerbread OS. simple as that
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
dwolfman said:
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
dwolfman said:
since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
maybe you can code in a "battery fix" and share it with all of us.
Just use a different ROM. Jesus Christ!
teerout said:
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
Click to expand...
Click to collapse
It didn't matter what I installed or didn't install. Once I got the phone at work with AOIP on it, it ate the battery three times faster than any other 4.2 ROM. One time, to rule out anything I was setting or loading, I loaded AOIP, gapps, then put in my account info and disabled auto updates with nothing else changed. It still did it.
As QA software tester, I know how to identify software issues and bugs. The only explanation for what I have happening is there is something going on with AOIP itself to cause this. Like I've already demonstrated other 4.2 ROMs only use the battery a little faster than RootBox 4.1 (RB about 0.6%/hr vs slimbean 4.2 using 1.1 to 1.5 %/hr) with that screenshot in my OP. AOIP uses about 2.5 %/hr at home but over 10%/hr at work.
In any case, it's quite apparent now that this little group of ostriches with their heads still stuck in the sand isn't interested in hearing the truth, so consider this a closed thread.
Sent from my SGH-T679 using xda app-developers app