yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] El Niche:
Same stability so far with almost the same combo. Im running 21.4 as reviews for it well pretty good. This is my first experience OC. I lowered the max to 1.0/312 as the default was 1.2/312. Is there a significant battery hit going back to 1.2/312? Thanks to all the devs for improving my tablet.
[Eee Pad Transformer Android Development] MassStash:
If you brought it back down to 1ghz, you're not experiencing OC tho

~Freshly acquired LTEvo; ViperRom'ed in under 2hrs...
[Eee Pad Transformer Android Development] tpjets62:
The battery hit is minimal at 1200, I would roll it back up there. Im at 1400 most of the time and the trade-off of a bit of juice for the additional performance is worth it for me.
[Eee Pad Transformer Android Development] El Niche:
Perfect thanks! i'll bump it up back up to 1.2. i think that will match my needs although maybe later ill try getting it to 1.4. Thanks
[Eee Pad Transformer Android Development] flydev:
please, is this the right kernel for ARHD?

i'm asking because there is a version for megatron and another for AOKP.

thanks!
[Eee Pad Transformer Android Development] tramane:
Hmmmm

Dont seem to be able to turn on wifi on Cm9 RC1 with 22.6 :(

Im gonna flash another and see if that fixes the issue
[Eee Pad Transformer Android Development] Nonek:
Hey Guevor.

Ok.. So this is in recards to the SOD with the 32gig SD card inserted.

I flashed 1.1 Yesterday...

First boot.. The device was coming up and then I slid to unlock..

It started to boot and was pulling in the pictures for my MultiPicture Live Wallpaper. The tablet then locked. No keyboard and screen response.

I then did a hard reset.. Had it come up and had it Lock again.

So I boot the next time.. It locks up again on the boot..

The third time I get it up, the Live Wallpaper didn't load at all, which tends to make me think that the OS might have had a problem with it, and I just had the Asus background tree. So I decided to run without the Wallpaper.

I get it up and then change the Governor to Conservative to see if that had anything to do with it. Ran that way for a few hours. I changed it back to 1.5 and On demand yesterday and it has run all night..

I have not had an SOD since those big lockups when first loading 1.1.

My Transformer is running super smooth with no hesitation.. Now I do know that when I was running the Live Wallpaper before with 1.1 it seemed to be slower. But without that Wallpaper it's been running smoothly.

About an hour ago I realized that I had no ICON for my SD Card. I Went into File explorer and SD was listed.. When I select the SD card though it was showing blank.. If I removed the SD card from the DOCK it would remove itself in real-time as well as come back in real-time when I plugged it back in. It never showed up on the status bar.. Never showed files in the Explorer.

After a reboot it all seems fine.. So I will continue to run this without the Wallpaper.. And I'm not sure if that is the culprit, as it's supposed to be using the MicroSD card, but maybe it's causing me to run out of a resource or tablespace or whatever..

I know I don't enough yet to say that this is going to continue ok, but I'll run it the rest of the day like this and see how it goes.. I can also go back to 22.6 tomorrow without the Live Wallpaper to see if that is somehow what is causing this.

INFORMATION about MultiPicture Live Wallpaper.

I am running a Live Wallpaper called MultiPicture Live Wallpaper.

Now this Live Wallpaper loads a separate picture for each screen as I scroll back and forth. I have it pointing to a directory that is on the MicroSD card with about 257 pictures that it cycles through that I have taken. I never thought it was even possible it was the issue as the picture directory is on the MSD card..

I figured I would give you something to scratch your head on and I'll let you know as this progresses.. If it is the culprit then it would be interesting to see if other people with the problem are running a Live Wallpaper and maybe that one in particular...

Sorry for the book

UPDATE: So I started to get some reboots on the 1.1 but did NOT get an SOD..I'm back on 22.6 running 1.5 ondemand without a Live Wallpaper.
[Eee Pad Transformer Android Development] kukky:
i know about fires....my girlfriend said she had to be at home for some times because she was not able to breath....and the sun was covered by fog......don't worry...we have idiot men even in italy!!!

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] DammedKiller:
I've tried it and the problem persists. Thanks anyway

Enviado desde mi Transformer TF101 usando Tapatalk 2
[Eee Pad Transformer Android Development] ferchos:
unzipping, flashing, rebooting but dont apply kernel

Hi, i have a stock rom ics TF101 4.0.3 / rooted / kernel version 2.6.39.4 android @ Mercury # 1. Yesterday I bought the kernel manager for the OC. I tried 4 versions:

- Kernel-ICS-test16-OC1700-fb_275.zip

- Kernel-ICS-V22-OC1700-fb_607.zip

- Kernel-ICS-V22.6-OC1700-fb_645.zip

- Kernel-2-ICS-V1.1-OC1700-fb_28.zip

It reads, unzipping, flashing, rebooting. Optimizing applications. But, do not enable the CB and the kernel remains the same (2.6.39.4 android @ Mercury # 1)

Reinstall the Kernel Manager, same problem. Any ideas?
[Eee Pad Transformer Android Development] tpjets62:
I would be installing/flashing the kernel from recovery and after I had made a backup first......that app has a lot of people complaining of the same problem....
[Eee Pad Transformer Android Development] jprattnu:
ARHD & Guevor kerne that doesnt break USB?

anyone recommend the best guevor version that does not break usb connectivity with windows 7 x64? I tried a few but both failed. I'm running the latest ARHD rom.

Thanks!
[Eee Pad Transformer Android Development] ferchos:
thnaks, but...

thanks, but do not want to use the recovery. Already suffered too much with this app

---------- Post added at 08:58 PM ---------- Previous post was at 08:41 PM ----------

ok, i use a Rogue Recovery v1.3.0 and work with this kernel Kernel-ICS-V22.6-OC1700-fb_645.zip, OC running!!! thanks
[Eee Pad Transformer Android Development] tpjets62:
Glad to see you went that route..(both are great choices, I have them myself)..it offers a lot more flexibility and most importantly, backups when you have a mishap.

---------- Post added at 05:28 PM ---------- Previous post was at 05:25 PM ----------

I believe that should work, I am not using ARHD but from what I have read, it looks like its the same for Revolver and ARHD....
[Eee Pad Transformer Android Development] bradysd4:
Yes, or any of the prior versions not listed as megatron or aokp.

I am using it now.
[Eee Pad Transformer Android Development] Nonek:
Hey Guevor,

SOD FIX

Well, it's been 26 hours with no problem. No SOD's and No RR.

So I would never have thought that an App / Live Wallpaper would cause lockups like that.

What's strange is that the my pictures aren't even on the SD card but it only happens when the SD card is inserted.

Is it possible that I'm running out of some sort of index? The last thing that I was seeing in the log was a sync which I believe is going to dump the memory cache to storage. Is it possible that it's opening to the SD card even though it's not supposed to get it in the library? Maybe taking longer to sync and suspending before it's done? Totally shooting in the dark.

It would be very interesting to know if other people with SOD are running a Live Wallpaper of some sort. I had even bought another 32 gig, but that's not it.

For those that don't want to read back, it's looking like the Multipicture Live Wallpaper is what was causing me to have SOD only when my SD card was inserted even though the pictures are on the MicroSD.

Any ideas? running out of resources someplace? Wallpaper trying to access the SD card when the card is in a strange state?

I have had the SD card become non responsive. In other words it wasn't in the status bar and when I took it out and re-inserted it, it never saw it. I had to undock and dock again and then the OS saw the SD card..

ANYWAY.. it has been ROCK SOLID since I turned off the Live Wallpaper.. I'll play around with some other live Wallpapers to see if it's all of them..

22.6 is Rock solid without the Live Wallpaper.. THANK YOU.. It would be very interesting to see if other people with problems are running Live Wallpapers..
[Eee Pad Transformer Android Development] David 617:
21.11 w/ aokp b39

148 hours of uptime and counting. Thank you so much

(PS, u ever think of getting a job with Asus. They still can't fix random reboots lol, that was so 10 kernels ago ;) )
[Eee Pad Transformer Android Development] Mr. Corny:
@Nonek

For me v1.1 is rock solid, no SODs no RR. Several previous versions I tryed had this problem, but there was no obvious connection with live wallpaper usage. Sometimes I was using it, sometimes not, SODs were always there, and I never used any other then Asus provided - ergo ones on internal memory. I am using mSD 8GB and SD 16 GB.
[Eee Pad Transformer Android Development] Nonek:
LOL.. and after all that I got an SOD..

And I hate David above and his 148 hour uptime. ;-) OH boy.. So.. still not rock solid but MUCH better without me running that Wallpaper..

Anyway....crap...
[Eee Pad Transformer Android Development] gkillerx:
Version 9.2.1.27 is getting pushed out guys, if we can believe Gary, it has some new NV and Google codes in it!
[Eee Pad Transformer Android Development] cholywell:
The kernel version in .27 is supposed to be 2.6.39.4 android@mars#1. Not sure if that is different from .24 or not.
[Eee Pad Transformer Android Development] tpjets62:
Hopefully after Guevor checks it out he can let us know if there are any beneficial changes. I dont plan on moving from 22.6 for now. I'm not messin' with success!
[Eee Pad Transformer Android Development] gkillerx:
:( same as .24
[Eee Pad Transformer Android Development] jtrosky:
I know that the kernel version number is the same, but I'm pretty sure that the 'android@mars' is different than it used to be - anyone know what that name (mars) signifies?

Thanks.
[Eee Pad Transformer Android Development] mgeniusm:
22.6 is great for me

I have zero problems with 22.6 and connect to win 7 64 bit with no problem

I recommend using revolver rom 4.1.1
[Eee Pad Transformer Android Development] tpjets62:
Same here........
[Eee Pad Transformer Android Development] clouse2013:
Anyone else having problems with the OC at 1700? I'm on Megatron with kernel 22.6. With the frequencies set that high, and the screen freezes and I have to restart. This happens with an ad card in and happens out as well.

Update: the lockups seem to be happening on frequencies over 1500.
[Eee Pad Transformer Android Development] werewolferx:
Of course it locks up...

My friend, of course it locks up, the CPU overheating causes everything to collapse and finally freeze, the TF101 uses a standard frecuency of 1Ghz from factory, the ability to overclock and test higher speeds are at your own risk so be careful on it, you don't want to fully break your device.

The testing of higher speeds plus the undervoltage helps to prevent damage but is not recommended.

Guevor sets and uses a standard frequency of 1.2Ghz wich is by far a great improvement on our equipments (20% higher than stock).

Hope this illustrates you a bit and helps you not to damage your processor. :good:
[Eee Pad Transformer Android Development] stcanard:
I don't care! Guevor's given me a completely stable system, I'm far more interested in his kernel updates than I am in ASUS's
[Eee Pad Transformer Android Development] sidneyk:
Having built kernels from source myself, I believe that all it signifies is that it was built by a different user setup, perhaps on a different machine than what we were seeing. At any rate, it is at least a different kernel build than what was before. For instance, kernels I build will always say, for example, sidney@ubuntu or something like that unless I change my setup. The kernel version, i.e. 2.6.39-4 or whatever, doesn't automatically get updated even if kernel sources are changed in some way. One of the files has to be changed to generate a different version number. Just like guevor's builds, it seems that android kernel developers mostly just let the build info (android@mars) become something of a 'here's a different kernel' indicator.
[Eee Pad Transformer Android Development] Christian Troy:
that thing is "user@hostname" of the build machine, in that case "android" is the user and "mars" the hostname
[Eee Pad Transformer Android Development] taptotap:
main battery drain?

Hi All

First of all I wanted to say 22.6 and Revolver is a winning combination!! Thanks to Guevor for such an awesome kernel!

Anyway, I've been testing and noticed that my battery seems to be draining a little faster than usual... I took a closer look at the graph from Dual Battery Widget and it seems that when the tablet is sleeping there is a drain on the main battery, while the dock battery stays flat...

... or is this normal?

Can anyone else confirm this?

Thanks!!
[Eee Pad Transformer Android Development] inigoml:
Thank you guevor for your efforts. We can be proud of your work.

My TF101 has been running for 284 hours wihtout ANY issue with your last V1.1 kernel at 1600Mhz. A record for my system!

I'm going to test 22.6 anyway, but v1.1 always will be reference for me in terms of stability.
[Eee Pad Transformer Android Development] heessie:
Guevor, can you please tell something about this, because I see on the first page that you use 1.6 Ghz? Standard we get 1.2 but we can clock it ourself to 1.6, like you did or?...

Thanks in advance, and thanks again for your great kernels!

(Not that I do not believe werewolverx, by the way :-) )
[Eee Pad Transformer Android Development] dgcruzing:
WW is right, if you do some reading you will find numerous posts on this, as a whole 1.2 is norm and anything above is really not giving you any performance gains apart from the big swinging **** syndrome..

With saying that..both of the trannys i have had got have been stable on 1504 and easily clock up to the 1700's..but 1504 is my daily fix..

Running at 1700+ makes mine hot...so of course it got to be doing damage internally..

You don't over clock a pc by 50- 80% without adding cooling systems..so why would you want to risk it on a fully sealed tablet?
[Eee Pad Transformer Android Development] Christian Troy:
the first time i tried 22.6 i had a SOD after ~24 hours... now after reading another user's comment about live wallpapers i have disabled multipicture live wallpaper and have been running that kernel since 3 days without any trouble (and without any charging yet, great job)

I use a B80 tf101 with a B90 dock, a microsd but any SD in the dock

btw i wanted to see if anyone had the same trouble with stock's based 1.1... i have to say that i have the same symptoms with both guevor's 1.1 and stock/roach's eos build43 (both are based on latest asus' with just some frequency tweaks).

when i have my tablet docked and i turn the screen off it sleeps for an amount of ~5/10 secs, after that the cpu ramps up to the maximum defined frequency (with display off and even when the display turns on again), the only way to "fix it" is rebooting the device, but the same thing happens as soon as the device sleeps again

it doesnt bother me that much but since i heard enthusiastic comments about that kernel version i gave it a try... and went back immediately!
[Eee Pad Transformer Android Development] Nonek:
AAAHHHHAAAAAAA!!!! ;-)

I was actually trying the 1.1 and started getting reboots.. It actually seemed to make things worse.. I was the guy that had the multipicture problem.. GREAT to hear that I'm not crazy. I would think that this is a pretty popular Live wallpaper too as I don't know of another app that does the same thing..

So I actually loaded .27 and I'm currently running the Kernel from the OTA. And THAT gave me an SOD with that wallpaper on.. But I started thinking about IO and what it might be opening and maybe hanging on and I noticed that I was getting the pictures from the Library and i was selecting my background pictures that way.. Now (guessing) I figured that even if I didn't have my pictures on my SD card and they were on my MicroSD card, having it use the gallery to lookup my pictures seemed like it might be making a call to Gallery which was opening to all my storage media..

So.. I changed the selection to just do the directory directly and it has been running ok for 13 hours... Which may not mean much, but if this works than it's narrowed down to an interraction with a specific app.. to a specific function call that MIGHT be causing an SOD on everyone that is using that wallpaper which SHOULD be fixable with that kind of specific information. It's good to see that you had the exact same problem with a different / newer Transformer build.

Anybody else with SOD and SD card inserted and Multipicture Live Wallpaper? And although this seems to be an app issue, if the APP can cause this than it's really an OS / Firmware / Kernel issue.. I shouldn't be able to run anything that would cause an SOD.
[Eee Pad Transformer Android Development] tsachi:
Just to add on the overclock issue. Chip manufacturers have a prices that ensures the stated frequency. This means that all chips will be able to handle over 1GHz. The variability in quality chip to chip makes some capable of 1.7 while other overheat at 1.4. Same goes for UV stability. Some hardware can take extreme levels while other will fail at the smallest level of under volt applied.

If your machine can't handle even the smallest overclock then, unfortunately, there is no software that can fix it. Personally I agree with the others - going over 1.2 or 1.4 didn't add much.
[Eee Pad Transformer Android Development] sidneyk:
First, I'll say that I don't really know what protections are in place in the current kernels to prevent apps from bringing the whole system down. First, we have to remember that Android, at it's core, is based on Linux (kernel, file system, etc.). Android is more like GUI polish and other tweaks and ways of doing things on top of the Linux base. Also, to say that an app shouldn't be able to cause SODs, RRs, or bring the system down is nice in theory and perhaps expectation, but in reality, it may not be a fact. It could depend on where functions aree called or running, i.e. kernel space, user space.

Compared to older Windows versions, there were many times that apps could lock the whole system. (BSODs anyone). It was usually badly written drivers or even the app itself trying to do things that weren't permitted by the underlying kernel, i.e. calling on non-existent memory locations or other things that weren't there. Newer Windows versions have things in place at the kernel level that don't allow some of those things to happen anymore and crashing Windows is much less common now, if not nearly impossible.

It could be that SODs may be just that the call to wakeup (from opening the lid or pushing the power button) may either not be getting issued or not being received. Those parts responsible may have crashed and didn't have mechanisms to automatically respawn or some other part in that chain may have broken down. So, if a wakeup call can't be issued or received the unit isn't waking up.

I believe an app surely could cause a reboot if it's trying to do something that the kernel says is illegal or maybe doesn't understand. Again, there could be protections in place now, like there is in Windows, I'm not sure. But, while rare, I have had a few apps or drivers that were able to lock up some Linux distros I've ran with newer kernels than we have here. Of course, they didn''t have all of the Android parts, maybe some.

My main point is that any code written by humans is prone to error, whether it be logic errors or calling illegal functions or simply mistyping or using wrong syntax in even one spot. Unless the kernel and perhaps the Android portion has specific code that prevents any action an app could do from crashing the whole system or causing other weirdness, then it is fully possible for apps to cause the issues we see, even if that app is Android itself. In Linux, you can get a kernel panic, which usually is the same result as a Windows BSOD and means that something was requested of the kernel that the kernel couldn't process. It could be a bug, illegal call, or something the kernel just didn't know what to do with and rather than causing damage, it just panics and halts the system.

Also, we are running here on ARM processors. Most software before now was written for x86 processors, completely different. Maybe some ways of doing things that worked on x86 are either not implemented the same on ARM or not understood fully enough or whatever. We may be trying to apply to much of the x86 thought process to ARM and just missing something.
[Eee Pad Transformer Android Development] *Detection*:
Flashed Kernel-ICS-V22.6-OC1700-fb_645.zip

Working great with stock .27

The OP says it is 3.1, but Info in settings says 2.6.39.4 ?
[Eee Pad Transformer Android Development] jtrosky:
@guevor just said that it's not *really* a 3.1 kernel, but he took alot of the stuff from the 3.1 kernel and backported it to the 2.6 kernel. I think he is just "calling" it the 3.1 kernel to help keep it separate from the other kernel he put out (1.1), which is more like the regular 2.6 kernel.

Hope that help and makes sense...

Good luck!
[Eee Pad Transformer Android Development] *Detection*:
Gotcha, been a while away from the whole custom thing in the hope that asus could actually solve this, actually feels pretty good to have some custom goodness to play with again, tablet seems interesting again
[Eee Pad Transformer Android Development] devilpera64:
Guevor someone has kidnapped you? :cyclops: :p ahah :good:
[Eee Pad Transformer Android Development] jef_k:
Asus's HR Department do it... And they see it's good. :p
[Eee Pad Transformer Android Development] cj1896:
Is this kernel for stock roms only or can I flash it with an AOSP rom?
[Eee Pad Transformer Android Development] gkillerx:
What do you think? After reading the download links:

Kernel-ICS-V22-OC1700-fb_607.zip same file as V21.11

Kernel-ICS-V22-OC1700-fb-AOKP_606.zip

Kernel-ICS-V22-OC1700-fb-megatron_605.zip

I still dont see why people post instead of just search. its way faster and less annoying.
[Eee Pad Transformer Android Development] MassStash:
Hope guevors alright, just sayin

~Freshly acquired LTEvo; ViperRom'ed in under 2hrs...
[Eee Pad Transformer Android Development] Tittah:
Hope he and ricardopvz are not abducted by ASUS...
[Eee Pad Transformer Android Development] MassStash:
lol I was thinking of making a joke along those lines. Hopefully he's getting paid by ASUS

~ TF101 on Revolver4.1.1

Currently OC'ed to 1.4, with Guevor's latest
[Eee Pad Transformer Android Development] :
I flashed guevors Kernel 22.6 (non-Megatron/AOKP - so I used the right Kernel) over the latest Nightly (7.8.12) and wi-fi didn't turn on! Any ideas on this?
[Eee Pad Transformer Android Development] sidneyk:
Guevor, can you please clear this up for us? Do any of your kernel zip files include the new nVidia codecs? Thanks.
[Eee Pad Transformer Android Development] Sean-El:
Werd, took me 2 seconds to decide.
[Eee Pad Transformer Android Development] MassStash:
Nah they don't. Flash the file out the OP

~Freshly acquired LTEvo; ViperRom'ed in under 2hrs...
[Eee Pad Transformer Android Development] sidneyk:
That is the answer that I'm fairly confident about, having looked at the unzipped files, but there seems to be confusion about it, thus the reason for trying to get the dev to chime in and end the confusion for certain. If I'm wrong, then I'll stand corrected.
[Eee Pad Transformer Android Development] tpjets62:
The discussion pertaining to the codecs being a separate item is back in the thread aways but there is a separate codecs file that you have to flash, they were just updated drivers and had nothing to do with the kernel...

Edit....Found it....http://xdaforums.com/showpost.php?p=27363044&postcount=1807