Related
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
Hello, I just wanted to start a thread to discuss battery optimization for AOKP. My battery life is suffering right now, so I'm reaching out to see what you guys are doing to get great battery life with this Rom. Please share your tweaks, thoughts, concerns or whatever....
I'm A O K with AOKP
jworkcoo said:
Hello, I just wanted to start a thread to discuss battery optimization for AOKP. My battery life is suffering right now, so I'm reaching out to see what you guys are doing to get great battery life with this Rom. Please share your tweaks, thoughts, concerns or whatever....
I'm A O K with AOKP
Click to expand...
Click to collapse
post your setup. kernels, tweaks, oc/uv, # of apps..
And what apps are listed in running services. As well as highest wakelocks and duration in Betterbatterystats,
Sent from my SPH-D700 using xda premium
I have setcpu 1400/200. I'm using the nylan kernel also....I'm running build 29....I didn't do any power saver tweaks....what else did you guys need to know?
I'm A O K with AOKP
jworkcoo said:
I have setcpu 1400/200. I'm using the nylan kernel also....I'm running build 29....I didn't do any power saver tweaks....what else did you guys need to know?
I'm A O K with AOKP
Click to expand...
Click to collapse
lol 1400/200!?!? theres ur 1st problem. use voltage control instead of setcpu and stick with 1000/100 or 1100/100. i always found cfq and conservative to be nice for battery, but apparently noop/ondemand is best. maybe try both. also turn data off when not using it most importantly. also try using the auto-start manager in the ROM Toolbox app (free in market) to disable most of ur apps from staying open or updating widgets constantly in the background. freeze system apps you don't use. forget the v6 supercharger, and i'd say stick with the stock kernel. hope that helps..
Do you expect to get good gas mileage running your car at 100 MPH on side streets? Do not OC if you want good battery life.
Sent from my SPH-D700 using xda premium
Thanks for schooling me...lol....I'm implementing your suggestions now....What do you mean turn data off when I'm not using it? Will I still get emails, text, etc?
I'm A O K with AOKP
If you turn of 3g data, you can still send/get phone calls and texts but no email
Also, undervolt you frequencies with voltage control, I don't think you have to go to stock kernel, but do as you please I would imagine the dark blacks from voodoo control would save battery. But anyways, Marcusant had a great guide for setting up any kernel for your phone, ill try to find it..
http://forum.xda-developers.com/showthread.php?t=1420447
Sent from my SPH-D700 using xda premium
sorry for double post this is it, just had to hyperlink
http://forum.xda-developers.com/showthread.php?t=1420447
Sent from my SPH-D700 using xda premium
somebody in another epic thread posted a link to another phone's thread where this guy did a REALLY thorough study about setting up kernels. he found the noop/ondemand was best on battery and that undervolting AT MOST saves about 2% battery, but typically does just about nothing. For that reason, i wouldn't bother doing it..but it's up to you. as for voodoo color you might be right about the blacker blacks..i just noticed on cm9 that the stock kernel saved more battery for me so figured it might apply on aokp too cuz its so similar
FrankyFiggz27 said:
somebody in another epic thread posted a link to another phone's thread where this guy did a REALLY thorough study about setting up kernels. he found the noop/ondemand was best on battery and that undervolting AT MOST saves about 2% battery, but typically does just about nothing. For that reason, i wouldn't bother doing it..but it's up to you. as for voodoo color you might be right about the blacker blacks..i just noticed on cm9 that the stock kernel saved more battery for me so figured it might apply on aokp too cuz its so similar
Click to expand...
Click to collapse
Thanks for that info
Sent from my SPH-D700 using xda premium
Ahem what battery life oh okay
I haven't figured out what is so different but I get much better battery life on AOKP than CM9. My imagination or is something really different on the roms? I don't use the power saver feature because I need my data all the time.
Im running Stock Build 31 on EL30 modem and no custom kernel nor am I oc/uv. I have very few apps and I have no widgets running and im getting horrible battery drain. I purchased the 1800 battery which is a few months old and I just dont know what to do. While my phone is sleeping, the battery drain hardly even moves, but when I start doing simple things like texting or checking emails I start getting drops of 2% percent or more every 5 mins of use.
Any Suggestion would be great.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I wanted to investigate the sporadic freezing in my Galaxy S2. So, I turned on, show CPU usage under the developer's options in ICS. For reference I'm currently running Jedi Knight's latest rom.
I have attached a picture of my cpu usage while at my home screen. The number I've read to be average loads, and anything over 1.00 means trouble. I'm consistently over 10 for my one, five, and fifteen minutes averages. Also, my red bar which apparently measures time in kernel, sometimes spikes and correlates with a brief moment of unresponsiveness.
I've only seen two other screenshots and both users were under two. I was curious what everyone else's loads were. Also, let me know how frequent you have brief freezes, what kind of background apps you usually run. Include info like how many activities do you allow to run in background, do you force gpu rendering, etc. I can't wait to see other's results.
Sent from my SGH-T989
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
ToastMan12 said:
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
Click to expand...
Click to collapse
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
rsromano said:
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
Click to expand...
Click to collapse
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
ToastMan12 said:
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
Click to expand...
Click to collapse
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
RushAOZ said:
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Whoa.. if changing software doesn't help then you for yourself a hardware issue. If you experience lag and heat issues no matter what call tmo and get that handset replace.
Sent from my SGH-T989 using xda premium
That's the thing. I don't experience any lag and the phone is perfectly cool. It gets hot on intensive use, though.
Sent from my SAMSUNG-SGH-T989 using xda premium
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
rsromano said:
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
Click to expand...
Click to collapse
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
ToastMan12 said:
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
Click to expand...
Click to collapse
I was also thinking that it could be calibrated differently somehow. Like, if it was off by a factor of ten. My values would be much more reasonable. But I have seem several screenshots in the 1.0 range.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
If you are idling then look at your batt stats again... screen is probably waaaay up there... play with your brightness settings.
Hope this helped
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Relsig said:
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
Click to expand...
Click to collapse
Can you post a screenshot of your idle processes, please?
rsromano said:
Can you post a screenshot of your idle processes, please?
Click to expand...
Click to collapse
Cell standby, phone idle. They should be higher but I had my screen on several hours more than normal today (hence screen being 55%). Top reads 18 hours on, 21% battery life remaining.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
ive tryed everything. android system is always higher than screen no matter what i flash, ics or jb. this is just getting annoying how it drops 1% every 2 minutes, when using it with data. i really like this phone but this is just killing it for me. i attached some pics of the battery and the kernel wakes. any help would be great.
thanks
WOW, that is crazy. I can only suggest Wicked V7 updated to the latest official ICS. Do a full wipe of everything and install. I have been running for 2 days and have great battery.
Good luck bro
idk what it can be I've been switching roms and ics or not android system is always higher than screen . Could it be an app or a file that's causing this?
Sent from my SGH-T999 using xda app-developers app
There is an app in the playstore I think it is called cpuspy that tells you what rogue app is running in the back ground. You can also try the process of elimination.
saldebot said:
There is an app in the playstore I think it is called cpuspy that tells you what rogue app is running in the back ground. You can also try the process of elimination.
Click to expand...
Click to collapse
Nope cpu spy shows how much time the phone is in different mhz.. like if you turn off your screen it will go into deepsleep and when you open the app it indicates how much time the phone has spent into deep sleep...
And OP maybe its a bad battery if you have tried ics roms and jb ?
Sent from my SGH-T999 using xda premium
shahkam said:
Nope cpu spy shows how much time the phone is in different mhz.. like if you turn off your screen it will go into deepsleep and when you open the app it indicates how much time the phone has spent into deep sleep...
And OP maybe its a bad battery if you have tried ics roms and jb ?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I stand corrected, thank you sir.
Sent from my SGH-T999 using Tapatalk 2
Well, what do you guys think of this? I'm new to the S3 not familiar with the ROMS. What's the best ROM out there for us with good battery life and performance?
I really like the CodenameAndroid and ParanoidAndroid roms in combination with Ktoonz kernel, I get around 2 days of battery with moderate usage and over 6 hours screen time, which IMO is great for the US S3
Androiduser96 said:
Well, what do you guys think of this? I'm new to the S3 not familiar with the ROMS. What's the best ROM out there for us with good battery life and performance?
Click to expand...
Click to collapse
holy sh*t the android system is raping your battery, well I love wicked roms(ICS) awesome battery and super smooth. You can also check out FrostyICS and FrostyJB those are also really good ROM's. I personally like ICS ROM's as they are more stable and don't have minor issues that some the JB ROM's have.
Check out post #3112 and #3113 in the WickedV7 thread and check out the battery life pic people posted on that ROM.
GO to the Play store and download no-frills CPU control or set cpu and check and see what you Min and max is for your CPU.
I have an extended battery and after 4 hours i was at 65 or 70% which is way off!!! I check this and it showed that my min and max was at 1024 once I changed the min to 384 everything got better
saldebot said:
holy sh*t the android system is raping your battery, well I love wicked roms(ICS) awesome battery and super smooth. You can also check out FrostyICS and FrostyJB those are also really good ROM's. I personally like ICS ROM's as they are more stable and don't have minor issues that some the JB ROM's have.
Check out post #3112 and #3113 in the WickedV7 thread and check out the battery life pic people posted on that ROM.
Click to expand...
Click to collapse
I tried latest frosty ics and still bad
Sent from my SGH-T999 using xda app-developers app
You doing a full wipe between? I'd do that if not and trying only installing necessary apps and check overnight or after a day if system is still killing you
Sent from my SGH-T999 using xda app-developers app
yeah full wipe I did some cleaning up erased some files and apps and the android system is now 12% and screen is 56% but I still have a lot of wake of ks
Sent from my SGH-T999 using xda app-developers app
When it comes to battery life, there are many thing that you can do to improve it.
First off, turn autobrightness off, and try and keep the brightness slider as low as comfortably possible.
Dark, if not completely black background are not only sick looking, but they help with your battery life.
Less widgets, especially ones that require frequent updates...like weather widgets, and facebook widgets will wake
your system up to update. I suggest removing most, if not all of your widgets from your home screens.
Download an app like setcpu, nstools, or voltage control to set your min and max frequencies. In setcpu, make some profiles for screen off to
make sure your system isn't throttling up while your phone is not in use.
Change your governor and i/o schedulers. With a high end device like this, you can comfortably sit on conservative governor without experiencing bad lag...i/o schedulars wont effect battery life too too much but simple ones are best (like sio).
Run v6 super charger, kickass kernalizer, and 3 script to improve the way your device runs, and battery life. Stick to wifi when possible. Having low signal will cause your phone to constantly look for a better signal which will prevent it from deep sleeping.
Use titanium backup to freeze unnecessary processes, such as DRM protected content.
Download one powerguard to help also.
Good luck!
Xenoism said:
When it comes to battery life, there are many thing that you can do to improve it.
First off, turn autobrightness off, and try and keep the brightness slider as low as comfortably possible.
Dark, if not completely black background are not only sick looking, but they help with your battery life.
Less widgets, especially ones that require frequent updates...like weather widgets, and facebook widgets will wake
your system up to update. I suggest removing most, if not all of your widgets from your home screens.
Download an app like setcpu, nstools, or voltage control to set your min and max frequencies. In setcpu, make some profiles for screen off to
make sure your system isn't throttling up while your phone is not in use.
Change your governor and i/o schedulers. With a high end device like this, you can comfortably sit on conservative governor without experiencing bad lag...i/o schedulars wont effect battery life too too much but simple ones are best (like sio).
Run v6 super charger, kickass kernalizer, and 3 script to improve the way your device runs, and battery life. Stick to wifi when possible. Having low signal will cause your phone to constantly look for a better signal which will prevent it from deep sleeping.
Use titanium backup to freeze unnecessary processes, such as DRM protected content.
Download one powerguard to help also.
Good luck!
Click to expand...
Click to collapse
Woaahh android system is at 52% now and screen 18%
Sent from my SGH-T999 using xda app-developers app
Jaimesco12 said:
Woaahh android system is at 52% now and screen 18%
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This was mentioned in another thread. DL this app: https://play.google.com/store/apps/details?id=com.eugene373.cpu.sleep
It shuts down one of your cores when the phone isn't in use.
Also DL CPUspy. This will show you exactly how often your phone is using certain frequencies, and whether or not it's going into deep sleep.
It looks from your screenshot however that your standby battery is not the problem, it seems to shoot down when in use (at least I'm assuming that was from when you were using the device).
Click on "System" and take a screenshot so we can see what's going on
Sent from my SGH-T999 using xda app-developers app
Error is the first thing listed. Have you tested the battery by doing a full reset and flash, then not installing any apps? If this is happening across roms and builds its most likely one of your apps not playing well with the system.
Before your next flash, go into dev options and turn on Show CPU Usage. Then let us know what processes seem to stay at the top all the time.
Also get cpu spy from the market and after letting it collect its data for a while (especially when not using the phone) check it to make sure its going into deep sleep.
After those two, do your clean flash and run without installing any apps for a while. Then when you do install them, do not restore from a backup. Download them fresh from the market. Also do not restore any backed up data, at least at first.
When you do flash your system, download the full firmware to your computer (use root66 if you want to keep root). From recovery choose format data, this will wipe your internal sdcard, btw.
Now boot into download mode and using Odin, flash the firmware you just downloaded.
Once done charge back to 100% and see how it goes.
You can get the firmware from my stickied thread in development.
http://forum.xda-developers.com/showthread.php?t=1949687
Good luck!
Sent from my SGH-T999 using xda app-developers app
I'm a little afraid to use odin and I always restore app + data from titanium backup after fresh flash lol
Sent from my SGH-T999 using xda app-developers app
Jaimesco12 said:
I'm a little afraid to use odin and I always restore app + data from titanium backup after fresh flash lol
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
As long as you follow instructions, and make sure you have the correct fw for your model, Odin is actually quite easy to use.
Restoring apps and especially data can cause all kinds of issues when jumping between different builds and especially android versions. The updated apos and system often have different database structures, different data files, and even different storage locations sometimes.
I'm betting this is where the problem will be.
I understand not wanting to go through all that I mentioned, but if you want to know where the problem originates, you have to start removing variables to narrow it down.
If you don't care what's causing it, jump to the flash. Nandroid backup, wipe everything, odin flash, test. If all is well, restore the data part of nandroid. If problems start again then you know its either your apps or data causing the problem.
Odin instructions are in TheExels thread stickied in this section.
Sent from my SGH-T999 using xda app-developers app
This post only pertains to Jellytime Sosei/BakedBean 4.1.2 and is for users experiencing problems with their A100, yours may not. This thread is not to debate or argue about the kernels, please keep that in mind
Hey guys, I was originally testing these ROMs for pio, and constantly am changing or tweaking things on the ROM to find what suits our A100 best. Pio was building these blind, so he has no way to thoroughly test the ROMs and such things as build.prop mods/tweaks as well as kernels.
Let me start by saying this, I AM IN NO WAY BASHING ANY DEVELOPER FOR THEIR WORK. I AM IN NO WAY BLAMING OR STATING THAT ANY BUGS/FLAWS ARE A DIRECT RESULT OF THEIR WORK. THE THINGS I AM LISTING ARE ISSUES/PROBLEMS/BUGS THAT I HAVE OBSERVED OR ENCOUNTERED, AND ALL BUGS/FLAWS WERE TESTED AGAINST THEIR EQUAL. EXAMPLE, USING THE godmachine81/linuxsociety KERNEL, THAN REPRODUCING THE SAME ENVIRONMENT, I WOULD RUN THE STOCK KERNEL FOR TESTING AND VERIFYING THE ERROR.
Kernel Observation:SODsEveryone, including myself, tend to automatically flash linuxsociety's GodMachine kernel v2.0, as it really is our only option for JellyBean/CM10/AOSP based ROMs. We do have ezTerry's kernel, but it has not "supposedly" been tweaked for 4.1.x systems. Although it is the base for GodMachine kernels. I've never used ezTerry's kernel,but I may test it like I've been testing GodMachine.
Anyways, for this ROM, I have found that the godmachine kernel performs poorly on Sosei ROM. With GodMachine kernel, I had tons of issues with constant BSOD/SOD. (Sleep of Death) The SODs were worse if you left wireless on, and the SODs were completely random, no matter what I did, if the tablet fell aslepp, it SOD'd on me. Using the stock kernel pio packed with the ROM, resolved much of this issue for me. The only time I have SOD on the stock kernel is when Wifi was left on, and the chances of this happening were 99% LESS LIKELY compared to GodMachine. You can combat this, by sacrificing battery life and using an app that's free on the playstore, WakeLock. If you choose to go this route, the "Partial_Wake_Lock" option consumes the least amount of battery while still preventing SOD. None of the 3 options for forcing wireless to stay on worked for stopping SOD.
RANDOM REBOOTS/CRASHING/FREEZINGI myself did not have many issues with random reboots, but I did have some issues with random app "force closes" and freezing to the point where you'd have the almost force close I call it, where you get an option to close or wait for the app. I have not had this issue using the stock kernel, unless related to the next topic...
GPU/VIDEO INSTABILITY/ODDITIESI, as well as a few others, have reported issues with display. Most users have noticed an issue with flashing lines, tearing, and artifacts on the desktop. I have also had issues when play a THD/HD game, for example Modern Combat 3: Fallen Nation HD, where anytime after about 20-30min, the display would become compltely distored, almost like when you were trying to pick up a TV station using rabbit ear antennas, and the game crashes/freezes, but you do not get an option to force close, so you have to use the Navigation bar HOME button to get yourself out of it, than you need to kill the game anyway you want, but if you don't kill it, it will load you back to that distorted, frozen image.
In the GodMachine kernel, the GPU is overclocked as well as being able to overclock your CPU, but you cannot adjust the GPU yourself with any application. Linuxsociety states: "Stable GPU Overclock @ 450mhz (scales from 300 - 450)"
I do not have these issues with video when using the stock kernel, nor do I notice any lack of GPU performance with lack of GPU overclocking.
In my honest opinion, I STRONGLY RECOMMEND the STOCK KERNEL. Yes it is lacking in some features, but it is capable of being overclocked as well if your interested in doing so. Using the interactive governor provides the smoothest performance and still retains some battery savings. Conservative, OnDemand, userspace, and Performance are offered as well. The I/O Scheduler only has NOOP available, but if you do some reading, NOOP is actually recommended for Flash Devices, like ours.
To get back to pio's stock kernel, you can boot into recovery, wipe cache and dalvik, and dirty flash the ROM.
BUILD.PROP EDITINGI cannot even begin to tell you the amount of hours I invested in testing and editing the build.prop to obtain what I find to be the most stable while still possibly enhancing performance/responsiveness and battery life. I will link you to my FINAL build.prop mod for you to download if you'd like. In all reality this consisted of just commenting out several lines in the original build.prop that our A100 did not like. This will also fix issues with the video camera recording if you have them, as well as improve certain app and system performance and functions. I've also had more reliability and just odd **** happen when I use the TCP/IP buffer enhancement code lines so those have been commented out as well to keep WiFi stable. I really see no performance gains with them other than SpeedTest and there is a reason, I am a Networking IT Student, and don't feel like explaining that now in this thread. lol
Download build.prop.sosei__tweaked
Using a FileExplorer with ROOT LEVEL ACCESS (I recommend ESFileExplorer),
Copy build.prop.sosei__tweaked into the /system folder
Rename current build.prop to build.prop.bak
Rename build.prop.sosei__tweaked to build.prop
Reboot into recovery (TWRP or CWM) and wipe dalvik cache & cache, reboot
make sure you wait ten, reboot and wait 5-10 before you start using your tablet
This is all in my observed, hands-on testing and experience, and everyone's results will vary based upon factors such as user setup, apps install, the way a user even uses their tablet etc
I hope this might help/inform some of you guys.
Very nice, thanks for taking the time to put this together for the users. How did that kernel I built for you do?
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Very nice, thanks for taking the time to put this together for the users. How did that kernel I built for you do?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I hadn't flashed it yet as i had gotten my tablet into a perfect state, for me, with this ROM and stock kernel, lol
The changed prob won't stop sod, but in my theroy should correct the video glitches.
I'll try it soon and let you know.
G2x-temasek CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
I'm using/testing this rom along with gm's kernel. I have not had wake SOD issue. It sometime takes a couple if clicks on the power button for it to wake, not sure if this is the issue you're referring to as SOD. Everything seems to work great so far. Netflix, audio, headphone all work well. I have always wanted some aokp flavor on this tab, and now that wish is granted thanks to the awesome work of pio, bb devs and gm.
S-Beamed from my GSIII via xda premium
[email protected] said:
I'm using/testing this rom along with gm's kernel. I have not had wake SOD issue. It sometime takes a couple if clicks on the power button for it to wake, not sure if this is the issue you're referring to as SOD. Everything seems to work great so far. Netflix, audio, headphone all work well. I have always wanted some aokp flavor on this tab, and now that wish is granted thanks to the awesome work of pio, bb devs and gm.
S-Beamed from my GSIII via xda premium
Click to expand...
Click to collapse
No, I had sod constantly. But not slow wake up. I get slow wake sometimes on stock, but atleast it will wake.
Everyone's tablet is not the same, some hate the GM kernel.
Mine seems to be one of those, but had I known how smooth and stable the stock kernel was, I prob would have stopped using GM awhile ago, I've had nothing but issues with it, if you've seen any of my old posts over last couple of months.
G2x-temasek CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Other than a couple of SOD's I haven't had any other issues with the gm kernel. I have since bumped up the minimum speed to 312 Mhz and that has seemed to fix the SOD issue but I still need more time to conclude that. I'm also getting some impressive quadrant scores with it too (3046) and that's with a fully loaded non-tweaked system. The only reason I like the gm kernel is the variety of I/O schedulers and governors...there is absolutely nothing wrong with the stock kernel. I'm still very happy with the JB ROM, I have it set up almost identical to my Samsung Nexus phone which makes it very convenient.
GM SOD Issue Resolved ( For Me)
I can now safely say after 4 days of testing that raising my minimum speed in the GM kernel to 312 Mhz has completely eliminated the SOD issues. I know that every device acts differently but this is working on mine!
Gulfstream 650 said:
I can now safely say after 4 days of testing that raising my minimum speed in the GM kernel to 312 Mhz has completely eliminated the SOD issues. I know that every device acts differently but this is working on mine!
Click to expand...
Click to collapse
I didn't want to do that myself and lose the extra battery juice.
The point is it should be able to UC down to 216 and hold there with no issues.
The stock kernel does it perfectly well with no ill effects.
I have a modified Godmachine kernel that is unreleased and I will be testing it soon.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
thanks for the tweaks and info! buti have never encountered a SOD. what happens? it just wont wake up after sleeping? if it happens can you just turn off your tablet by holding the power button or do you have to wait for it to die?
Jaydizzle414 said:
thanks for the tweaks and info! buti have never encountered a SOD. what happens? it just wont wake up after sleeping? if it happens can you just turn off your tablet by holding the power button or do you have to wait for it to die?
Click to expand...
Click to collapse
SoD is just a failure to resume from sleep, reset button or hold power will reset it to normal. Some tegra2 devices have it, some don't, even among the same series, like a100s. The best way to combat it is to not sleep, but of course battery sucks.
Sent from my Thrive - Unified B4 - Balthesaur V2.71
justjackyl said:
I didn't want to do that myself and lose the extra battery juice.
The point is it should be able to UC down to 216 and hold there with no issues.
The stock kernel does it perfectly well with no ill effects.
I have a modified Godmachine kernel that is unreleased and I will be testing it soon.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Click to expand...
Click to collapse
I can understand not wanting to lose the extra battery juice, lots of what we do is to extend it. I did however undervolt the 315 slot to the same as the 216 (750 mV) so there's no addition battery drain. It's a win-win situation! Let us know how the unreleased version works out, I'm always looking for options.
Can you not dowloadd this from your tab? When I tried it said the download was unsuccessful
Sent from my A100 using XDA premium.
Jaydizzle414 said:
Can you not dowloadd this from your tab? When I tried it said the download was unsuccessful
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Just try again, even on WiFi it can be hit or miss.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Just try again, even on WiFi it can be hit or miss.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've tried like a bajillion times lol probably my fault or something. Not that big of a deal though
Sent from my A100 using XDA premium.
Jaydizzle414 said:
I've tried like a bajillion times lol probably my fault or something. Not that big of a deal though
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Try clearing the data on the 'download manager' in the settings > apps. Then retrying.
Romman0 said:
Try clearing the data on the 'download manager' in the settings > apps. Then retrying.
Click to expand...
Click to collapse
Didn't work but thanks for helping
Sent from my A100 using XDA premium.
This is what it shows
Sent from my A100 using XDA premium.
Jaydizzle414 said:
This is what it shows
Sent from my A100 using XDA premium.
Click to expand...
Click to collapse
Looks like network traffic or just a router/tab reset needed. Or try later tonight.
Sent from my Galaxy Nexus using Tapatalk 2
pm me ur gmail and ill send it directly
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
..