Develop Bugs

[Q] Myn's Warm ROM Question

I guess I'm under 10 posts so I could not post in his thread.
But I installed the rom and everything is awesome btw,
Now under his alternative kernels it has the Netarchy's agressive v7 kernel, I installed it, and if I put setcpu at 1.267 ghz my phone shuts off and reboots?
IS there a reason why?

Also it just went to its first reboot and it went into a bootloop?

K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?

you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
r916 said:
K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?
Click to expand...
Click to collapse

4g evo said:
you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
Click to expand...
Click to collapse
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.

any kernels or Roms that i have had it would always loop above 1.1 your lucky that u got it to go that high how was it at that speed lol.
r916 said:
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.
Click to expand...
Click to collapse

i was told that if you OC and start having bootloop scale back the OC until it gets stable again.

I got netarchy's 4.3.2 kernel and it's clocked to 1.228, wont go any higher since the incident.

From my understanding, no two phones are exactly alike and one phone will allow you to OC more than another. The most I ever OC to is 1.19 but I usually keep it at 1.15 and it is very stable. I've gone up to 1.267 and it still worked, but I only left it at that number for a few seconds and I never tried to go higher.

It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App

cloak.n.dagger said:
It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well it was hard to notch it back since I had set at boot checked and it was at 1.267, so I had to re flash the stock #15 htc kernel, and set it at 998 and then flash the new kernel and now it's at 1.228 and stable, and not to mention my battery is amazing.

I keep mine at 1.19 as well, I had it higher at one time, but there's not that much
improvement in performance for me to risk my phone boot looping while i'm asleep at
night.
BTW, Myn's ROM is really good but i've always use KK #9 BFS for it overclocker at 1.19
with no issues, no reboots, only secks.

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

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

franco kernel sluggish or phone damaged?

Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.

I'm on Franco and have no problems. Why don't you try another kernel and let us know how it goes?

tobitronics said:
Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.
Click to expand...
Click to collapse
I understand people want to ask questions first, did you try to wipe and reflash?
At most I can probably assure you, you didn't damage your CPU.. there would probably be more dire issues if it was.
Did you flash a new kernel yet?
Sent from my Galaxy Nexus using Tapatalk 2

Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?

tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Wipe dalvik cache and install trinity.
Sent from my Galaxy Nexus using Tapatalk 2

tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Yes, I've flashed 3-4 kernels on one ROM. You can dirty flash your ROM too or completely wipe and flash.
Either way its fine. I do suggest wiping and flashing though..
Sent from my Galaxy Nexus using Tapatalk 2

And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?

tobitronics said:
And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?
Click to expand...
Click to collapse
Setcpu is fine. In order to get stock, either use a new kernel or dirty flash.
Assuming.. if it was I'd guess the phone probably wouldn't be running?
Sent from my Galaxy Nexus using Tapatalk 2

You need to learn about what you're doing before you do it!

I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?

z06mike said:
You need to learn about what you're doing before you do it!
Click to expand...
Click to collapse
:good: :good:
tobitronics said:
I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?
Click to expand...
Click to collapse
if I have such issues I will never flash an oc kernel to look if everthing is working. Install stock rom kernel back and try. If everything is fine......you can try an oc one.
On Trinity; first number is MAX CPU clock range you can chose and second number is fix GPU clock.....or just reading FAQ, Changelog etc. will answer your questions really quick
regards,
Lars

from what I've heard, some gnexs are really picky with roms and kernels. I guess your phone is one of them. I personally had problems with Trinity Kernel, since when I reboot, it sometimes bootloops for 5minutes and such. I personally had no problems with Franco though. In fact, I use Franco as my daily driver
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Franco's app let's you easily tweak the settings (overclock, change governors, etc.) which may help the sluggishness. I almost exclusively run Franco and his M5 is amazing!
Sent from my Galaxy Nexus using Tapatalk 2

A reflash might be the best option ... either the ROM or Kernel or Both lol thats my inner crack flasher talkin'

Never had problems with franco. It's trinity's kernel that made problems for me.

I run Franco's kernel myself. Just have to be careful with flashing the nightlies, it can be hit or miss. They are experimental.
Sent from my Galaxy Nexus using Tapatalk 2

CHANGE YOUR GOVERNOR HURR DURR.
Sent from my Galaxy Nexus using xda app-developers app

Today I reflashed franco and I must say that trinity is way better, at least for me. Franco keeps being sluggish, trinity works smooth.

trinity is better than Franco's in every way possible...
especially battery life

[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

..