yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] blaxican25:
i flashed it earlier and it felt like my tablet was getting warm but it was running good but i flashed back to 3.0.5
[Asus  Eee Pad Transformer Prime] Subsonic44:
Sleep issue

Hi Motley,

3.0.7 on Androwook 2.1 seemed to be working fine but I noticed this morning that my battery went from 68% to 36% overnight. I checked my deep sleep and found, while it is working, it was only in deep sleep 14% of the time. Flashed back to 3.0.5 and let it sleep for 20 minutes and it already shows deep sleep at 80%.
[Asus  Eee Pad Transformer Prime] plutozz:
I'm on Androwook 2.1 just flashed AAlpha3.07.0 on TF201. Everything was fine except 3.0.70 doesn't mount microSD ( Sandisk Ultra 32GB). I revert back to 3.06.10 and everything is ok.
[Asus  Eee Pad Transformer Prime] JeanEatsWorld:
I'm a bit confused...I've a question..

How this kernel (3.0.7) interact with the AndroWook ROM (2.1) and ATP_tweak?

I mean..

if I want to apply SIO and tune.sh on AndroWook 2.1 ROM with the motley 3.0.7 installed.. should I install ATP_tweak? Should I just select the scheduler somehow..?

I don't know.. I'm sorry fot the double post but I don't know where to post :confused:

:fingers-crossed:
[Asus  Eee Pad Transformer Prime] anoneemooz:
If you're using this kernel, no need for ATP_tweak to load up modules from tune.sh. Motley has these modules built in and they're selectable via apps like SetCPU or whatever free alternative. :)
[Asus  Eee Pad Transformer Prime] Bastaerd:
Or simply use a terminal app or init.d script to set these ;)

Edit: just forked your kernel, hope that's oke with you :)
[Asus  Eee Pad Transformer Prime] sjh4:
Since flashing to latest alpha when prime goes into deep sleep it won't wake up?? I have to hold in power button and force reboot, flashed back to the 3.0.5 for now
[Asus  Eee Pad Transformer Prime] zeus34:
Deepsleep mode not wake up CM9

Older versio works fine.
[Asus  Eee Pad Transformer Prime] svladimir:
Sorry guys, I'm a bit lost here: I've got 32gb international prime with AndroWook 2.1 installed. Which of available variants (not version, I've decided to go with 3.05) of the kernel shall I flash ?

I've tried one, but the 'about phone' says I'm still on 2.6.39.4.
[Asus  Eee Pad Transformer Prime] skarfreak:
If ur using 3.0.5 u shud c #151 at the last portion of where u c 2.6.39.4
[Asus  Eee Pad Transformer Prime] demandarin:
has anyone been having SOD after tablet is docked and in deep sleep for several hours(normal 8hr. workday) on the latest androwook 2.1 or latest motley kernel? I've been having it happen last few days or so. seems only after a long time tablet is docked and in deep sleep. its sleeping a lil too hard..lmao. I have to hold power button for a long time or use reset hole to bring it on. not sure if its the kernel or the rom. I may of had it happen like once or twice on motley 3.05. but now its more frequent. ill let tablet deep sleep tomorrow by itself while I'm at work. to see if only being docked causes it.

seems to only occur after long periods of deep sleep(several hours). not whenever the screen turns off or short periods of deep sleep.

other than that, both the rom and kernel works great.
[Asus  Eee Pad Transformer Prime] svladimir:
Happened to me once with older, stable version of the kernel.
[Asus  Eee Pad Transformer Prime] CharliesTheMan:
Since I'm running the same setup, I can do some testing for you. I haven't noticed it yet, but I usually don't leave my prime alone that long. I play with it at work when I'm stressed out at least a few times a day, and usually power it off when I'm not going to be using it unless I'm charging it.

But tonight I'll leave it on and let it sleep and see what it does when I wake up. Probably about 5 hours that it will have between when I go to sleep and when I wake up and leave for work.
[Asus  Eee Pad Transformer Prime] sjh4:
deep sleep issue causind SOD after a few hours appears still to be caused by latest motley, running android 2.1 had issue 2 or 3 times a day, ended up downgrading motley from 3.0.7 back to 3.0.5, now running fine with no deep sleep issues
[Asus  Eee Pad Transformer Prime] joeyddr:
I went right to wook 2.1 from stock unlock flashed 3.07 never had a SOD everything running great and deep sleep works perfect.... left tablet sleep at work when i get here and after 5hrs of being in sleep mode i woke it up and it still had 98% battery.
[Asus  Eee Pad Transformer Prime] Charsher47:
No SOD after deep sleep with 3.0.7.0 on Jermaine's AOKP Milestone 6.1. Been running it for a couple days now. Thanks Motley!
[Asus  Eee Pad Transformer Prime] sjh4:
might try re flashing motley 3.0.7.0 tonight, never had issues with sleep mode on any motley except latest alpha, as others have said, when docked , and left for more than a couple of hours it refuses to wake, and have to resort to reboot, might just be an issue wihen docked?
[Asus  Eee Pad Transformer Prime] newellj79:
Hmmm, maybe a bad download?

edit, not that it should matter but I did not even clear dalvik.
[Asus  Eee Pad Transformer Prime] _motley:
Yes, it should be in balanced mode when it boots, so it shouldn't be hitting 1.7 unless you have scaling scripts or some app that would do this. Which ROM are you running? Any other customization (other OC method or kernel modules etc.)?
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Running latest version of virtuous, no CPU tweaks running but I do have ATP Tweak installed to set deadline io at boot. I'll play around tomorrow and see if I can get it working.

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] uhmzilighase:
The 1.1 version caused nothing but reboots here but this 2.0 version is behaving quite nicely. I don't have any amazing Antutu benchmarks to post but the device is happy to complete the test this time! It will still reboot if you lock it to 1700 MHz and do anything CPU intensive. When left to 'interactive' or 'ondemand' I don't see any stability issues. Will test for a few days and see how it does. So far so good. :) Well done.

ROM: virtuous_prime_s_9.4.2.15_v2

core_cap_level 1400
[Asus  Eee Pad Transformer Prime] _motley:
Ah, most likely when this app starts at boot, it is crashing the tab since this kernel has deadline as the default scheduler and the kernel module should no longer be loaded.
[Asus  Eee Pad Transformer Prime] demandarin:
Virtuous rom has overclock built into it. That may be messing around with things. As far as you asking the other guy if he had any overclock tweaks or anything added.
[Asus  Eee Pad Transformer Prime] _motley:
I don't think that will hurt anything as others are reporting that they are running Virtuous without issues. Those are just scaling scripts I believe, just like stock. I am pretty sure it is the ATP Tweaks causing the problem since it is loading kernel modules with kernel features already enabled within this kernel. This can't be a good thing and would likely cause instability. Once this is disabled or removed, my guess is that it will work and the app will no longer be required since the functionality is built in.
[Asus  Eee Pad Transformer Prime] SfinxSoft:
Well 2.0 is much better with 1.4v and 1.7Ghz - I've got 5427 in quadrant and 12319 (without 2d/3d as it bugs) in antutu. But 1.4v is still too low for my particular device ;) To be able to pass the antutu test I have to cool the prime - the warm device still reboots in antutu with 1.7 mode.

P.S. Forgot to say that it is interesting to see what happens during instability periods (reboots/hangs) by examinating /proc/last_kmsg file. Mine has a bunch of temp messages and then oops :

....

[ 439.714275] nct1008_get_temp: ret temp=72C

[ 444.724274] nct1008_get_temp: ret temp=74C

[ 449.734269] nct1008_get_temp: ret temp=71C

[ 454.744265] nct1008_get_temp: ret temp=73C

[ 459.754341] nct1008_get_temp: ret temp=74C

[ 464.765282] nct1008_get_temp: ret temp=74C

.... oops .......
[Asus  Eee Pad Transformer Prime] jermaine151:
I'm no expert on those messages but if those temps are correct you should definitely lower your clock speed before your device blows up.

74C = 165.2F = Really hot for electronics
[Asus  Eee Pad Transformer Prime] _motley:
If you use the interactive governor for daily use, it should not be a problem. I don't recommend running the performance governor for long, maybe just for a test or two to see if you are stable. The 4 cores will draw a lot of juice if you continue to tax them and it will get very warm. These cores draw require the same voltage as tegra 2 cores do for 1.5/1.6GHz. Leaving them running hot continuously is useless anyhow. We really probably should be running tests using the interactive governor to see how real world performance compares.

This temp is being reported by the driver for NCT1008 (nct1008.c), a temperature monitoring device from ON Semiconductors. It appears that a thermal shutdown was triggered. EDP will throttle your clock down starting at a certain temp and then thermal shutdown will occur at a max temp.

It is strange that Antutu can't get past the 2d/3d tests. Something doesn't sound right there.

Yes, luckily the tablet was smart enough to shut it down!
[Asus  Eee Pad Transformer Prime] benefit14snake:
74c is not terrible. It depends on the silicone, alot of higher end gpus run 85+ stock. I'm not sure the upper limit of the 40nm process this chip is based off but 74 is out of my comfort zone. 60 or so would be ideal. Does anyone know how the heatsink on this device is setup? Can we mod it?
[Asus  Eee Pad Transformer Prime] jermaine151:
It's terrible enough to make it shut down. :) Mine stays around 40C when I'm using the tablet.
[Asus  Eee Pad Transformer Prime] marko!:
Any chance this supports init.d ?

sent from my Transformer Prime
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Reporting back from before, turns out atp tweak was the problem. I unchecked enable deadline at boot and was able to boot right up and run some benchmarks at 1.7ghz. Then I opened up atp tweak just for fun and my tab immediately rebooted. So I'd add to the op that people need to uninstall or atleast disable Atp tweak.

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Also, plus 1 on this.

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] SfinxSoft:
It never does even in stock kernel - seems like the antutu bug, I do not bother.

It is clear - I'd like the people to know/distinguish the 'reboot/freeze' event that caused by thermal shutdown or by chipset overclock instability. This means that true 1.8Ghz can be possibly achieved with some additional cooling ;)
[Asus  Eee Pad Transformer Prime] benefit14snake:
Where is prime95 when you need it? Lol
[Asus  Eee Pad Transformer Prime] _motley:
Sure, this should be easy to addto the init.rc within the included initramfs in the next version.

For example:

...
[B][I]exec /sbin/sysinit.rc[/I][/B]
class_start default
...

Then, you would be required to provide your own sysinit.rc or the ROM will already have it setup somewhere. I will check some custom ROMs to see what path/naming convention they are using.

Thanks for reporting back Papa. I have updated the OP with this info under requirements.
[Asus  Eee Pad Transformer Prime] newellj79:
I've been trying to keep tabs on my clock speed, just for kicks. Its seems that when I'm set to 1.7 using the interactive governor, I almost never hit 1300, 1400, 1500, or 1600. It's not a problem by any means, I'm just curious if it was designed to be like this. I don't know anything about kernels, other than how to install them. And by the way this one is working great. Really hoping for a 1.8 my temp seem to be fine.

Edit.. whoa, first time I've ever posted a pic. Didn't intend for it to be so big...
[Asus  Eee Pad Transformer Prime] benefit14snake:
Interestingly enough I did try this with the new build of the aokp rom and it works marvelously! ! Quite a bit smoother than the kernel they have packaged with the rom. The only problem is wifi doesn't work! Lol ill probably flash back to virtuous when the new build comes out and use this kernel.

Great work!
[Asus  Eee Pad Transformer Prime] Loccy:
Assume you're using the AnyKernel distribution? I had problems with the full AOKP with ramdisk on milestone 6.1.
[Asus  Eee Pad Transformer Prime] hamdir:
Can we have an explanation of these variables? like 3d scaling?
[Asus  Eee Pad Transformer Prime] Charsher47:
Pretty sure I flashed the one with ramdisk for build 40 but I could be wrong because I think I downloaded both.
[Asus  Eee Pad Transformer Prime] demandarin:
Well I had switched back to motley alpha 3.05. had tablet docked today while at work. was in deep sleep for several hours. I didn't have a SOD when i got off and opened it up. so i think its the latest kernel(3.07) that's causing it. or the combo with wookie 2.1.
[Asus  Eee Pad Transformer Prime] seeknom:
There's a lot of variables for sure, so it's hard to say... could be interplay with the scheduler people choose to use, could be a matter of what background apps are running.

For the record, I decided to switch to deadline (from sio) just to see how it behaved, and it seems to me to be even more responsive than sio. It's too early for me to give a review, but the UI defintely seems faster.
[Asus  Eee Pad Transformer Prime] demandarin:
I'm still using SIO scheduler. seems to be working fine so i don't think that's the issue. honestly, my UI is already super fast. any faster and it'll fly off the screen..lol.
[Asus  Eee Pad Transformer Prime] sjh4:
Reflashed 3.0.7.0 last night, and no deep sleep issues when used without dock, when docked after 3 hrs refused to come out of deep sleep needing reboot this only happens on this alpha, and previous versions had no issues with dock and deep sleep
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
I can confirm motley's latest is not working with milestone 6.1. Tried the full ram disk for aokp 1.7 and was not able to OC past 1.3. Flasehd the anykernel build and get it to OC with scritmanager, but got way too many reboot, including during testing using Antutu and Quadrant. Still on 6.1 and reverted back to 3.0.6 iteration, which has no deep sleep for me -- not a huge deal breaker. Looking forward to the next build,
[Asus  Eee Pad Transformer Prime] Bastaerd:
Did anyone try changing the default cpu governor?

I just changed it from interactive to ondemand. With interactive I had some weird cpu freq spikes but ondemand seems to have tempered them. Will let you guys know how it works out :)
[Asus  Eee Pad Transformer Prime] Loccy:
Mine booted with the full ramdisk, but was an inexplicably laggy, unresponsive experience. Mine seems fine with the anykernel install but I don't overclock and haven't tried anything as scientifically stress testing as Antutu and/or Quadrant. Mind you I've just played a (admittedly low res) episode of a TV show all the way through (45 minutes xvid in BS Player) with no problems.
[Asus  Eee Pad Transformer Prime] demandarin:
I think its the combo of 3.07 kernel and being docked after long deep sleep causing SOD. been a few days or so back on alpha 3.05 and not a single SOD, under same scenario, so far.

that was the only issue i had with 3.07. seems to work great other than that.

how was your battery life on 3.07?
[Asus  Eee Pad Transformer Prime] unxconformed:
I'm having SOD issues too with 3.0.7.0 and the dock. I'm on the stock rom and this kernel is the only modification I've installed. Haven't tried older versions yet, but SOD are pretty much guaranteed every time I let it sit for several hours.
[Asus  Eee Pad Transformer Prime] Bastaerd:
Weird thing is, I'm also running stock rom and _motley's latest alpha and don't have any SOD's (governor: ondemand).
[Asus  Eee Pad Transformer Prime] YoMarK:
I had SOD's all the time when I was unlocked(but rooted) on stock .21 and before.

Every day I put the put the Prime in de dock(on the charger), and almost every day it would not wake up normaly.

Now unlocked on AOKP with motley it's much better, but I'm not running exactly the same apps. In fact, it's been a while since I had this problem.
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
What versions and builds are you running?

On 6.1 milestone had issues with both of Motley's iterations of 3.0.7 and 3.0.6...haven't been solid since b40 and maybe 3.0.5
[Asus  Eee Pad Transformer Prime] BaGRoS:
I instaled motley_tfp_anykernel_generic_3.0.7.0_b303.zip for CM9 nightly, and brick my Prime.

How i can install without brick? I can't find MD5 for test download file.

Wysłane z mojego Transformer Prime TF201
[Asus  Eee Pad Transformer Prime] CharliesTheMan:
I think there's a translation problem, brick means you really screwed it up bad.

Describe your brick please. But if you can't boot, just reflash the CM9 nightly and you should be ok.
[Asus  Eee Pad Transformer Prime] BaGRoS:
Un brick this metod http://xdaforums.com/showpost.php?p=22897771&postcount=1 - Brick 1a - boot always in Clockworkmod rcovery.

Wysłane z mojego Transformer Prime TF201
[Asus  Eee Pad Transformer Prime] hamdir:
we managed GPU OC on the One X

it was 416mhz now its 520mhz

dunno if it help you guys :)
[Asus  Eee Pad Transformer Prime] Tempie007:
use twrp instead of cwm

had this problem too on 3 occasions

its fixable (unbrick thread --> brick 1a)
[Asus  Eee Pad Transformer Prime] Parastie:
TWRP here, never had any problems. Try flashing the stock rom after moving to TWRP to make sure you're booting normally.
[Asus  Eee Pad Transformer Prime] BaGRoS:
TWRP works o'kay!

Wysłane z mojego Transformer Prime TF201
[Asus  Eee Pad Transformer Prime] _motley:
New "Lite" version released

Hi everyone,

I have released a new "Lite" version (see the OP). This will provide a stock-like base and may tell us some things about stability issues that some report. I am wondering if it might help some that have issues with video reboots, SOD etc. As for as dock SOD, I have seen this before on the stock kernel and all variances of my custom kernel. I can go weeks without seeing it and then bam, it happens a couple times in a short period of time. Not sure why it happens. I once thought it happened most often when the dock battery is drained and the tablet was sleeping in the dock. But, I have seen it once on stock when the dock was plugged in and charging...so go figure!

I'll try to pop back in soon to help to answer questions etc. Been really busy with work and family stuff. Hope you are all doing well!

Cheers,

motley
[Asus  Eee Pad Transformer Prime] demandarin:
Alpha kernel 3.05 still running great for me. I downloaded the lite version just in case. I like the more feature packed alpha/experimental kernels.
[Asus  Eee Pad Transformer Prime] tylermaciaszek:
the lite version for AOKP kills the WiFI
[Asus  Eee Pad Transformer Prime] _motley:
Thanks, that ROM has changed a bit lately (ramdisk etc.) so I guess I will need to take a closer look. Did you try the "Anykernel" method or just the full ramdisk?
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
NICE...thanks for the special release...will wait till wifi is fixed and flash...I think I'll also have some time to flash both alpha iterations today and can run whatever tests you like, if need be...I'm on 6.1, currently using the stock kernel, CFQ and the sqlite patch.

Is it good practice to flash the 2.6.11 kernel just to get the scripts right and than flash any of your kernels? I have never done this before, but it occurred to me that this may have been an issue all along...OR is there some simple way to check, without having to flash.
[Asus  Eee Pad Transformer Prime] CekMTL:
Sorry for having disappeared... I guess it's called "life" ... :)

Anyways, I will reply to your other post (I know I know... ages ago, very sorry for that!), but I had a few moments and I thought I'd share my "experiments" with you....

Turns out that all these instabilities and SOD are caused by the INTERACTIVE GOVERNOR (interesting code to have a peek around....scary also)... sometimes it just makes a mess of the cpus going online/offline, and then BAM... reboot after a nice freeze, at ANY FREQUENCY.

There's also the problem when the TF is docked... there's some weird code that does some stuff when it is docked... but my testing revealed (at least for me) that using ONDEMAND, and tweaking it a little bit, is as good as interactive, without the instabilities (ramdom hangs reboots and whatnot).

Thought I'd share my ongoing experience, that is of course with my own kernel and crazy optimizations but based on motley's kernel, but before the 3.0.5 one, way before that...

Enviado desde mi Transformer Prime TF201 usando Tapatalk 2
[Asus  Eee Pad Transformer Prime] seeknom:
Very interesting findings!

So, is there any benefit to us using something like System Tuner to change our CPU governor to the stock ONDEMAND? (even though we don't have your tweaks).
[Asus  Eee Pad Transformer Prime] Blairware:
Actually same question as Seeknom. If you are finding major stability differences run on demand vs. interactive (at a perhaps slightly reduced performance level) and the results are consistent in this, would the "rest of us" that rely on others for things like kernels & tweaks, get any benefit running On Demand? I guess there is one way to find out; do my own testing, which I am game for, just wanted to know if you think it's a good way to go from your experience.

I don't mind discovery, I thrive on it in fact, but I DO like to use my cycles (both personal and on my devices) efficiently, lol.

What do you think Motley?

Sent from my Highly Modified Mr. Coffee

- Using custom built Java App, Naturally!
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
yea, I don't think it's that easy...wish it were...I'm sure you know, aside from the differences from each prime and cpu, there must be a bunch of other variables to consider...I have tried ondemand with one of the newer alphas and still had issues....I mean, I hardly did extensive testing, but had same exact issues as running interactive...

Let us know what you find.
[Asus  Eee Pad Transformer Prime] seeknom:
I agree, it's likely not that easy, but I'm just wondering whether "interactive" has serious problems that "ondemand" does not suffer from so it might be better to avoid interactive altogether...
[Asus  Eee Pad Transformer Prime] Bastaerd:
Been using a tweaked ondemand all along with no SOD's on stock WW.28. Interactive eats battery like crazy with all the weird cpu spiking. Did not dig through the code yet though. Was thinking of creating a badass like governor but it's basicly a heavily modified ondemand.

If people are interested, I could make a zip with sets CPU governor to ondemand with a few presets, performance, battery and the middle-road.

You will need init.d support though ;)