Develop Bugs

Setcpu is the issue

I have been bouncing back in and forth from rom to rom. Most are great. Warm 2.2, DamageControl, and Virus (currently running). The issue I'm having is no matter witch rom or kernal I run on my Evo froyo, every time I install Setcpu within a couple of hours my launcher (no matter witch one) stops working. I have gone into root to reinstall, install and uninstall and nothing works. All Rome are affected by what I can tell. I'm finding the problem to be with setcpu. I'm surprised if can't find much information on this. Does anyone have ideas?
Sent from my Evo using Tapatalk

Yea, setcpu can improve things but also causes issues elsewhere. I was using launcher pro for a while, and using that in conjunction with setcpu gave me nothing but poor battery life and terrible freezing. I have since then stopped using setcpu and my phone works fine. Besides the difference between 1ghz and 1.1-1.2 is negligible on the Evo unless your benchmarking imo
sent from my DAMN Evo!!

Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.

drmacinyasha said:
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
Click to expand...
Click to collapse
I did all that already. I had my screen off set to 384mhz, im no novice, setcpu has great benefits but has some negatives also.
OP, try ziggys 10/26 kernel. It has scripts that handle oc'ing up to 1.13ghz using interactive governer WITHOUT using setcpu
sent from my DAMN Evo!!

I use SetCPU and Launcher Pro Plus and have used these 2 on every ROM I have used...which is a LOT!! My screen off is set to 245 and I OC to around 1228. I have NEVER had any issues on amy ROM. I dont know what is causing your issue but it isnt SetCPU and Launcher Pro....

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

lock ups

In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.

scott7044 said:
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
Click to expand...
Click to collapse
Go back to the kernel thread look for the voltage table. The voltage levels are too low at the overclock levels, that what's causing your freeze ups. Use incredicontrol app from the market to adjust the voltage levels. You want to mirror the settings to match those of the previous version of the kernel
Sent from my Incredible 2 using Tapatalk

Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.

I'm fairly new myself but have been using SetCPU for a while. Make sure the "Set on Boot" option is unchecked until you find a setting that will work for your phone. As far as the nandroid, restore is your friend!! lol I've made many mistakes in the past that have totally locked up my phone and the restore option from recovery has saved me every time. There is always a chance that you can damage your phone but as time has gone by the devs have really made that possibility minimal

scott7044 said:
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
Click to expand...
Click to collapse
The app works on any kernel that supports adjustable voltages.
Both methods will work to undo things. Either restore or re flash the rom. But like stated above don't select the set on boot option until you find settings that work good on your phone.
Sent from my Incredible 2 using Tapatalk

Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.

scott7044 said:
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
Click to expand...
Click to collapse
You can do it by use....open up different apps very quick and switch between them...basically trying to over load the phone by making it multi task at a high level. set cpu also has a built in stress test under the info tab, run that for a few mins. I usually do the stress test for 3-5 mins followed by a quadrant test.
Sent from my Incredible 2 using Tapatalk

In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!

TheMavic said:
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
Click to expand...
Click to collapse
voltages just need to be changed and made to match 1.0.4 for the kernel to run like a champ
Sent from my Incredible 2 using Tapatalk

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

..