I was just wondering if anyone else had this problem, if feels a bit less snappy. Also, and i know quadrant isn't the authority on speed, but with the original release i was getting scores of 2450 with setcpu set to 1200mhz with the ondemand profile, now the best i can get is 1850, everything is the same with the exception being that i flashed the new release of the syndicate rom frozen. Anyone else notice this?
I flashed it last night and I got a Quadrant score ~1600. First time I tried it so wasn't sure what to expect. I thought that was kind of low, esp considering I've never seen less than 1700 with MidnightROM 4.2.
There was some changes to increase stability. The kernel is now clocked at 1.0ghz out the box and you need a program to set it to 1.2ghz. Also the sqlite.so was modified for stability and that's what the main difference in speed. Some people including my self are using sqlite.so from the original release and are scores are right where they where with 1.0 and phone responses
Sent from my SPH-D700 using Tapatalk
i was wondering the same thing myself...so just use setcpu to oc to 1.2? and how can i use the .so file from 1.0?
Sent from my SPH-D700 using XDA Premium App
MysteryEmotionz said:
There was some changes to increase stability. The kernel is now clocked at 1.0ghz out the box and you need a program to set it to 1.2ghz. Also the sqlite.so was modified for stability and that's what the main difference in speed. Some people including my self are using sqlite.so from the original release and are scores are right where they where with 1.0 and phone responses
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Also the sqlite.so file was supposedly giving false quadrant scores making them seem faster. You really won't notice a real world difference from 1.0 to 1.0.1.
solblack said:
Also the sqlite.so file was supposedly giving false quadrant scores making them seem faster. You really won't notice a real world difference from 1.0 to 1.0.1.
Click to expand...
Click to collapse
Theres a very slight increase in real world performance but not much to worry about. If you notice smartbench scores are exactly where they where on 1.0. Just quadrant scores took a hit
Sent from my SPH-D700 using Tapatalk
My issue has been my airplane being turning on and off rapidly and not getting any phone service. The radio keeps turning on and off when the airplane mode. I've done all kinds of wipes and re flashes numerous times and cannot get rid of the issue.
Definitive said:
My issue has been my airplane being turning on and off rapidly and not getting any phone service. The radio keeps turning on and off when the airplane mode. I've done all kinds of wipes and re flashes numerous times and cannot get rid of the issue.
Click to expand...
Click to collapse
Have you tried flashing just the modem?
Sent from my SPH-D700 using Tapatalk
MysteryEmotionz said:
Have you tried flashing just the modem?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
After many flashing and Odin going back to stock and re-doing everything I finally got it to work and work perfectly. Now if I can just figure out how to get the nascar app back on and working properly I'll be gold. If you have any suggestions I started another forum asking for some assistance if you know of anything.
Thanks guys, after a few mores days living with 1.0.1 ive noticed there really isn't any speed difference.
the new syndicate is slower than the first release though it is supposed to be more stable. I have had no issues with v1.0 however so that is what i use and have had no issues
nww007 said:
the new syndicate is slower than the first release though it is supposed to be more stable. I have had no issues with v1.0 however so that is what i use and have had no issues
Click to expand...
Click to collapse
not even the email fc issue? i find that i usually get the email fc when im trying to reply to an email...other than that its ok..
is sprint hotspot working for u?
Sent from my SPH-D700 using XDA Premium App
Definitive said:
My issue has been my airplane being turning on and off rapidly and not getting any phone service. The radio keeps turning on and off when the airplane mode. I've done all kinds of wipes and re flashes numerous times and cannot get rid of the issue.
Click to expand...
Click to collapse
I've run into the exact same problem when I installed 1.0.
Make sure you Odin with the files provided in the syndicate rom frozen thread. The files I got from the Odin thread were different than the Syndicate thread.
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.
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
scott7044 said:
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
Click to expand...
Click to collapse
Go back to the kernel thread look for the voltage table. The voltage levels are too low at the overclock levels, that what's causing your freeze ups. Use incredicontrol app from the market to adjust the voltage levels. You want to mirror the settings to match those of the previous version of the kernel
Sent from my Incredible 2 using Tapatalk
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
I'm fairly new myself but have been using SetCPU for a while. Make sure the "Set on Boot" option is unchecked until you find a setting that will work for your phone. As far as the nandroid, restore is your friend!! lol I've made many mistakes in the past that have totally locked up my phone and the restore option from recovery has saved me every time. There is always a chance that you can damage your phone but as time has gone by the devs have really made that possibility minimal
scott7044 said:
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
Click to expand...
Click to collapse
The app works on any kernel that supports adjustable voltages.
Both methods will work to undo things. Either restore or re flash the rom. But like stated above don't select the set on boot option until you find settings that work good on your phone.
Sent from my Incredible 2 using Tapatalk
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
scott7044 said:
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
Click to expand...
Click to collapse
You can do it by use....open up different apps very quick and switch between them...basically trying to over load the phone by making it multi task at a high level. set cpu also has a built in stress test under the info tab, run that for a few mins. I usually do the stress test for 3-5 mins followed by a quadrant test.
Sent from my Incredible 2 using Tapatalk
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
TheMavic said:
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
Click to expand...
Click to collapse
voltages just need to be changed and made to match 1.0.4 for the kernel to run like a champ
Sent from my Incredible 2 using Tapatalk
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
dtruong23 said:
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I have setcpu with screenoff and in call set at 800 mhz and no issues. I'm suspecting something with your kernel perhaps or maybe just a bad flash?
Alternate
dtruong23 said:
Is anyone having problems with setcpu on any of the ICS leaks or cm9? My phone just freezes up upon boot and has to essentially be redone for the phone to boot. The second setcpu runs, my phone locks up. I have a screen off profile with max at 800mhz. I also tried it without the screen off profile. I have decided to hold off with the app until it is more stable.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Same problem, I have official ICS Rom for Galaxy S2 and several programs are freezing my phone when trying to overclock (or lowerclock). The only program working good for me is "No Frills"
Same here. I had to get rid of set cpu bcuz it would freeze the phone. Now i just have tegrak and i wish it had profiles...
Sent from my SPH-D710 using XDA
I have the same problem, tried setcpu on miui ics, cm9, custom ics roms, it freezes my phone on all ics based roms?
It gives problems on GB as well, and freezes my phone. I suspect its the new version.
My experience was the opposite. I kept freezing with tegrak (free).
I bought ultimate, and havent froze yet. Got profiles so its easy to save battery when you need. No more editing init.d scripts...
RayTrue04 said:
Same here. I had to get rid of set cpu bcuz it would freeze the phone. Now i just have tegrak and i wish it had profiles...
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Antutu CPU Master works well and has profiles.
i had this same issue, the second i downloaded setcpu my phone started freezing for long periods of time, does anybody know if this is because it is conflicting with the presets built into the ROM?
SetCPU is for custom kernels, while tegrak is for stock. Im not sure of any custom ICS kernels besides the repacks. My phone was unplugged for 16 hours using tegrak and FC24. And he only problems i had were on the free versi0n.
My solution would be to check out tegrak if SetCPU is giving you issues.
Some roms come with undervolt scripts built in, SeCPU could be conflicting. Not sure though.
If you check Calk's ics ROM thread in Android Development, his latest release notes say something about having an issue with Ics freezing at 800, so it could have something to do with that. Don't know more myself, but hopefully that points you in the right direction!
Sent from my SPH-D710 using XDA
Not to be a smart***. But everyone does realize that ICS is designed to handle all this for you right? Thats why I never included these cpu or voltage tweaks in my ICS roms. No reboots or freezes... Some may not get issues... But most will if you use them
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
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
..