Develop Bugs

[Q] Screen flickers when it wake up from sleep

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.

[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] 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

..

[Q] Random reboots even after Pristine

I've been helping with minor problems in the Q&A section for some time, but now I face my own problem.
After softbricking my phone 3 days ago(probably from too many tweaks crashing in the init.d folder) I re-pristined my phone, and I'll list what is its specs below after recovery.
ROM: CM9RC2
Kernel: I tried all available from HADI and CastagnalT(except CFS)
Mod: Disable CPU Render, Seeder V5, KSM, 16 bit Transparency, Force GPU render, Disabled surface dither.
Probably the standard package in CM9RC2, but thing is it random reboots(mostly from wakes after locking). Once I was watching a movie, specifically the movie is in MKV format using MX player, it rebooted instantly too, after its back to launcher its fine until I finished the movie and locked phone, then when I wake it, it freeze reboot again.
Any ideas people?

possible problems/solutions:
1- maybe it is a problem with the battery, check if it gets fat when charging. if yes then go buy a new one
2- usually battery problems end up with force shutdown, so my secound thought is that it is a problem with the add-ons. try going pristine and sticking to the stock cm9 kernel with no add-ons and see if it still reboots
3- if the above didn't work then maybe it is a hardware problem
i hope i helped

7amada100 said:
possible problems/solutions:
1- maybe it is a problem with the battery, check if it gets fat when charging. if yes then go buy a new one
2- usually battery problems end up with force shutdown, so my secound thought is that it is a problem with the add-ons. try going pristine and sticking to the stock cm9 kernel with no add-ons and see if it still reboots
3- if the above didn't work then maybe it is a hardware problem
i hope i helped
Click to expand...
Click to collapse
I have a strong feeling its Seeder v5 behind this. The original Seeder gave me no issues.
The battery should be fine. I check it once in awhile anyway.

Nah, I don't seeders did it, May be a wrong flash or something, btw turn off force gpu rendering it gives more performance
Sent from my GT-I8150

probably your battery is going to dead. happened to many people that has the galaxy wonder from 1 year or a bit more. check the battery and see if it is swollen

7amada100 said:
Nah, I don't seeders did it, May be a wrong flash or something, btw turn off force gpu rendering it gives more performance
Sent from my GT-I8150
Click to expand...
Click to collapse
Really? I always thought its on for more performance.
SpadaBoss said:
probably your battery is going to dead. happened to many people that has the galaxy wonder from 1 year or a bit more. check the battery and see if it is swollen
Click to expand...
Click to collapse
My battery life is fine though. If its swollen a significant effect would be drastically bad battery life. I learnt this while studying about lithium-ion batteries and experience when I'm working in a camera shop

KiD3991 said:
I've been helping with minor problems in the Q&A section for some time, but now I face my own problem.
After softbricking my phone 3 days ago(probably from too many tweaks crashing in the init.d folder) I re-pristined my phone, and I'll list what is its specs below after recovery.
ROM: CM9RC2
Kernel: I tried all available from HADI and CastagnalT(except CFS)
Mod: Disable CPU Render, Seeder V5, KSM, 16 bit Transparency, Force GPU render, Disabled surface dither.
Probably the standard package in CM9RC2, but thing is it random reboots(mostly from wakes after locking). Once I was watching a movie, specifically the movie is in MKV format using MX player, it rebooted instantly too, after its back to launcher its fine until I finished the movie and locked phone, then when I wake it, it freeze reboot again.
Any ideas people?
Click to expand...
Click to collapse
CastagnaIT 7.5 or 7.3?
It seems many are having some difficulties with 7.5...
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --

some factors
1. battery
2. undervolting
3. governor
4. confilicting scripts
probably there are other factor i dont know

im running cm9 rc1 with castagnaIt kernel 7.5,,
and doesnt have that issue with random reboots,,,
and i also have tons of games,,, 229 user apps to be exact,, including games,,
i also installed link2sd,, partiton my 32gb mmc into Fat32// ext2,,, and no rebooting problems,.,,
what im experiencing is that,,
when i lock my phone,, or leave the phone,, when i try to unlock the phone,,, the screen wont show up but the back button as well as the menu button lights up,,, dont know if its because of my link2sd app or what,,,
by the way,, im running pristine before i started tweaking my phone,,, and took me almost a day re-installing all my apps,,, without the use of TB,,

pepoluan said:
CastagnaIT 7.5 or 7.3?
It seems many are having some difficulties with 7.5...
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
7.5 yes. maybe that's it though.
hadidjapri said:
some factors
1. battery
2. undervolting
3. governor
4. confilicting scripts
probably there are other factor i dont know
Click to expand...
Click to collapse
I once used your 1.4 but it still happened. But only once, I was in a bad mood so before it even rebooted I flashed 7.5 back LOL.
Will try using 1.4 hadiconfig back and test.
Don't think its the kernels own problem though.
santiagoruel13 said:
im running cm9 rc1 with castagnaIt kernel 7.5,,
and doesnt have that issue with random reboots,,,
and i also have tons of games,,, 229 user apps to be exact,, including games,,
i also installed link2sd,, partiton my 32gb mmc into Fat32// ext2,,, and no rebooting problems,.,,
what im experiencing is that,,
when i lock my phone,, or leave the phone,, when i try to unlock the phone,,, the screen wont show up but the back button as well as the menu button lights up,,, dont know if its because of my link2sd app or what,,,
by the way,, im running pristine before i started tweaking my phone,,, and took me almost a day re-installing all my apps,,, without the use of TB,,
Click to expand...
Click to collapse
Yeah! That happens to me too ... Quite a lot. But then sometime I get pissed while trying to get my phone back on, I spammed and it reboots lol.

KiD3991 said:
7.5 yes. maybe that's it though.
I once used your 1.4 but it still happened. But only once, I was in a bad mood so before it even rebooted I flashed 7.5 back LOL.
Will try using 1.4 hadiconfig back and test.
Don't think its the kernels own problem though.
Yeah! That happens to me too ... Quite a lot. But then sometime I get pissed while trying to get my phone back on, I spammed and it reboots lol.
Click to expand...
Click to collapse
maybe kernel problem. i suspected UV to cause this kind of problem.
this happen once on my very first extreme UV mode and this problem is reduced when i raised the voltage one stage
i'm gonna make newer build without any UV i guess

SpadaBoss said:
probably your battery is going to dead. happened to many people that has the galaxy wonder from 1 year or a bit more. check the battery and see if it is swollen
Click to expand...
Click to collapse
my battery is nearly 1 year now but didnt swollen