Develop Bugs

[Help] Lots of freezes and crushes after updating to 4.0.5

Hi,
I've had my Archos G9 80 updated to the latest android official 4.0.5 from and since then i'm expriencing lots of crushes and freezes. I'm getting them randomly with no specific app working.
Also, i have tried to do full formats (Android + Data), and still having same issues.
Does anyone have any idea what else i can try?
Thanks.

I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.

DeeDroid said:
I changed the CPU govenor from "hotplug" to "interactive".
Click to expand...
Click to collapse
how this is done? Ι have the same problem!

africa_twin said:
how this is done? Ι have the same problem!
Click to expand...
Click to collapse
Yes, can this be done from the phone itself? Within the ROM?

You can set this in any tool that is intended for overclocking. I don't overclock, I only changed the Govenor.
I use "SetCPU". ("No-frills CPU Control" should do the same.)

So does this have any other effects on the phone?

RichWPX said:
So does this have any other effects on the phone?
Click to expand...
Click to collapse
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.

I downgraded the device to 4.0.4 and since then, no crushes.. I guess for some reason 4.0.5 isn't stable on my device.. ill stick with this version unroll they get another one out..
To downgrade, just install official update file of the version you want to upgrade to..

DeeDroid said:
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
Click to expand...
Click to collapse
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.

RichWPX said:
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
Click to expand...
Click to collapse
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.

DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
changing govenor from "hotplug" to "interactive" seems to help against random freezes. 4 days without problems until now i had freezes with ics, but never with honeycomb.
device: archos 101g9
[ROM] Archos ICS - Firmware 4.0.5(4.0.3) - ROOT & BUSYBOX , Only for SDE (thanks surdu_petru)

DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
That seems to be my problem too. Setcpu requires root. is there a very easy way to do this, just to run this setcpu? There used to be a z4 tool, but can't seem to find it anymore.
Edit I see that I need superoneclick. Will temporary root suffice or will I need permanent root to change the governor setting.and keep it so.

Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S

DeeDroid said:
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
Click to expand...
Click to collapse
I have the same experience. Hc was laggy and slow. Ics is much faster and smoother.
Sent from my ARCHOS 80G9 using Tapatalk

gen_scheisskopf said:
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
Click to expand...
Click to collapse
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Will "Superoneclick" not root my device ?

sbtwister said:
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Click to expand...
Click to collapse
Special Developer Edition
sbtwister said:
Will "Superoneclick" not root my device ?
Click to expand...
Click to collapse
No, it won't. Gen9 system layout is different than for most other devices

hey, back to topic
5 days without freeze with govenor "interactive". i witched back to "hot plug" this morning and had to reboot my tablet 2 times today. for my case, "interactice" seems to help against random freezes.

mines performance intstead of interactive... experienced some freezing n interactive..

Man I'm really pissed.
Yesterday I had to hard reboot 7 times
Sent from my X8 using xda premium

hmm,
sounds not good. archos stands not for high quality i guess. we get what we pay . i had an archos 101g8, now a 101g9 and trouble with hard-/firmwares since 2010. i think, this was the last one - no furthermore advantures
@IrishStuff09: you did reformat for ics or upgrade from honeycomb? the best way is to start from scratch and skip upgrades.

[Q] Does anyone else's A100 slow down

Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
I do not experience this issue. When you flashed the rom, did you do a clean install? Have you formatting the device?

Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?

Crimson Ghoul said:
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Click to expand...
Click to collapse
The animations should not have anything to do with it. Does this only occur on that rom? Have you tried other roms and experienced that issue?

not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened

Crimson Ghoul said:
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Click to expand...
Click to collapse
This is starting to sound like a hardware issue. Before that is concluded, you could:
- Make sure the governor is not set to "conservative"
- Try a clean install of CM9
If the problem still arises, its most likely a hardware issue.

I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now

Crimson Ghoul said:
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Click to expand...
Click to collapse
It doesn't seem it can be anything else but a hardware issue in that case.
NB. Overclocking to a high frequency can cause instability and bring about that issue (but since you experienced it on the stock rom, its quite likely not to be that).

the overclocking helps to speed it up a tad bit.. for the most part it just lags.. i did a clean install just now

Thought I would jump in. Stock ics would slow down and lag on me, jittery transitions poor performance in games or movies, but it took an hour not a few minutes. However testing the T20 kernel before the release kernel had that exact issue, bogging and lagging within minutes.
His release kernel doesnt do it, and flex extreme as well as my cm9 builds don't, even with T20 kernel. Consider flashing that kernel to see what happens.
Side note...what issues did you have with cm9? And what release? My build 1 has been running for 3 days no reboots stable as can be undervolted and OC when needed. Something to maybe think to try to see if it persists. T20 kernel works fine with it too.
Tapatalked from my Galaxy S II.

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Yup, EVERYTIME I turned on my screen then unlocked it to laggggggg for a lil while. I'm now using CM9 n that issues gone. Try CM9
forum.xda-developers.com/showthread.php?t=1705554
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D

To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.

eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
That reminds me...setting a screen off profile with the same min/Max speed can cause issues with that, give Max a notch or two higher. And don't have it change the governor leave it the same. So like interactive screen on Myst nit be conservative screen off, doesn't work that way.
Tapatalked from my Galaxy S II.

I had the same issue on stock. I noticed there are 2 weather applications installed (version 1 and version 2) immediately after I disabled the old weather application (version 1) this stopped happening. I used the ICS GUI to do the disable.
This might not be the case in custom rom, but is true for stock. Post reply and let me know if this fixed it for you also.

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Do you have a micro SD card plugged in? Try reformatting the card with a computer. Worked for me.
Sent from my A100 using XDA

I felt the need to add my two cents in this....this has been happening to me for the longest with the flex reaper rom ONLY. I've used stock and ZN's rom and those did not lag after unlock...only flex reaper. I'm currently using flex reaper and still experience it from time to time but doesn't destroy my day at all...

Give the CM9 nightly ROM's a go. No Bluetooth n no HDMI audio, but everything else is fine n damn smooth. Those issues will be fixed though
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D

eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
I installed Flex 100 Reaper with stock and it it seemed to run smooth enough. Then I installed the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.

htc_softbank said:
I installed Flex 100 Reaper with the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
Click to expand...
Click to collapse
Setcpu from the play store.
The overclock settings are not integrated like CM.

[Q] Phone performance

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

[Q] CPU throttleed--why? and..best CPU utilization monitor?

I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...

1. I can't tell you why it happens... but I know it is a common problem on the JB ROMs (on the Dinc). There was quite a lot of discussion about it. I know the devs are aware of the issue and were working on it.
2. I don't know of anything that will graph percentage of cpu cycles, or anything exactly like that. But try hooking the phone up to the PC and run ddms (part of the adb tool set) and see what it is doing (or failing to do). While ddms is running in verbose mode it will give you a running output of everything the phone is doing (along with all the errors and warnings).

MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
Click to expand...
Click to collapse
That's because he's using an older version of Evervolv's qsd8k-common. It was fixed on Oct 10 with Change I3a0fff83: powerHAL: fix the screen off bug. This is one of the reasons I do nightlys, is to get all the new tweaks. This bug won't be fixed in his ROM till he resyncs his source and recompiles. It's triggered by the screen turning off. There's a workaround with Tasker, but since this bug is no longer in my ROM, I quit looking at it.
MysticCobra said:
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Click to expand...
Click to collapse
CPUSpy is a pretty good app.

MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
Click to expand...
Click to collapse
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.

musical_chairs said:
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
Click to expand...
Click to collapse
It should work fine on Albinoman's ROM. powerHAL is a generic jellybean feature and should work on all JB ROM's. You won't need the fix however on either of Pon's ROMs whether AOKP or CM10.

I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...

omniatic said:
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
Click to expand...
Click to collapse
It's supposed to change to 614 on screen off. The bug was that it would stick at 614 even on screen on.
I don't recommend that lib for cm. It's outdated.
Also I don't use sav2 anymore as it doesn't and won't implement project butter. Also interactive can be more aggressive than sav2 as it can jump frequency on touch via boostpulse which sav2 doesn't have.
Sent from my Galaxy Nexus using Tapatalk 2

Oh, well, then I guess I'll give the interactive another try. Maybe just needs to settle in longer. Got so used to ICS, wasn't sure what to expect from JB. Guess it's time I read back a few pages and see what else I've missed.
...sorry...I was on the phone...

Thanks, guys--appreciate the help!

Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?

alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).

PonsAsinorem said:
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
Click to expand...
Click to collapse
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.

alph0 said:
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
Click to expand...
Click to collapse
I use Apollo Music regularly on Pons's CM10, it works fine, doesn't reboot.

alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Try flashing to his newest build. It fixed a few problems for me and is incredibly fast. I had to reflash gapps from goo.im though because play store was force closing. Also, doubletwist is a better music player imo because it has a better interface and has good integration with the lockscreen.

[INFO] Sosei/BakedBean ROM-Kernel and tweaks tested; results

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:​SODs​Everyone, 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/FREEZING​I 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/ODDITIES​I, 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 EDITING​I 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

..