yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Jonman409:
Blades, would you mind if I tried to build a kernel with your modifications? I am no stranger to kernel modifications as I frequently make changes with a custom openwrt branch. I wanted to experiment and see if I can add some governers as well as the Brain **** Scheduler. Just playing around and see if it is worthwhile.
[Eee Pad Transformer Android Development] a.mcdear:
Sad day today... I went back to clemsyn 22a because the default undervolting on both the 8-24-2011 and the 11-26-2011 is too much for my tablet to run stable. Too many crashes and sleeps of death. Bummer, cause the Blades kernel is definitely faster, smoother, has better frequency scaling, and spends more time in deep sleep, but without stock voltages I just can't use it and have my tablet work reliably. :'(
[Eee Pad Transformer Android Development] jtrosky:
I believe that Mr. Blades was going to release a version of his kernel with stock speeds and voltage settings by default, so that more folks can successfully use his kernel. Haven't seen it yet though.

@blades - is that still on your to-do list?

Thanks!
[Eee Pad Transformer Android Development] MISFITZ:
I was also having too many crash and sleep of death with my TF101 after using Blade3...I went back to stock..hope Blade puts some thought into this...

Your work is awesome...wish I could use it...

Thanks

Misfitz
[Eee Pad Transformer Android Development] Hammerfest:
you sir have my ABSOLUTE attention... i wont do it myself, but let me find a dog to hump your leg to show you my interest in your "playing around"...

BFS+SWAP=MessInPants...
[Eee Pad Transformer Android Development] Blades:
Funny that bfs has been mentioned. its in now.. Also mentioned was a lower boot clock... thats here.. 1232mhz.. didn't screw with voltages yet.. but i'll have one soon..

http://home.comcast.net/~ibladesi/TF101-CryBaby-12-06-2011.zip

and for those menly men that like their tf101 fast all the time. 1592mhz boot clock..

http://home.comcast.net/~ibladesi/TF101-CptAwesome-12-06-2011.zip

There are other things.. silly things.. like more compiler flag optimizations (after reading all the enthralling arm and gcc docs)..

bfs patch didn't work right out of the box (2.6.36 box, that is).. error is self-explanitory.. but at line 1927 in sched_bfs.c (or whatever the file name is).. change calc_global_load(void) to calc_global_load(unsigned long ticks)

and the guy that wants to modify kernel.. its updated on github.. sans bfs patch... so you can experience the joy of le patch` yourself.

it wasn't that joyful...

I'm forgetting something to mention.. oh yeah.. I kicked the mem timings around again.. I didn't tame them down.. you have been warned. I'll take the links down if it gets doomsday on me. but it won't..

I'll update first post with even LESS information.

edit: Both don't seem to be working very well

edit (obviously the latest edit): BFS threw a hissy fit.. they both work fine in their bfs-less revisions.. i haven't given up tho..
[Eee Pad Transformer Android Development] 006fazer:
Hi,

Tested two kernels, the first witch boot at 1592MHz boot loop, and the second stay on black screen after Bios logo :-(

Back to Blade V3 from 26/11/2011

Regards
[Eee Pad Transformer Android Development] Blades:
it was the bfs sched.. even with the not-so-sane memory timings removed, it still did this.. so i took a few stabs at other unofficial patches.. diy, still no dice.. etc etc.. now i just want to stab stuff.

But I'm running my newer kernel without bfs and its not slow.. and its 4 hours past when i should've not given a ****.. so i'm punching out tonight.. in about 2 minutes.. the above posted links will work.. and actually work on the device..

i will be testing the **** out of them.. perhaps bfs was 'too hard' on the device and thats why it keeled over upon boot up.. it wasn't nuclear.. but it wouldn't boot.. i expected it to go all potty pants in /data/media with ramdump*.. but nope.. it gave me the silent treatment.. which says it didn't get far enough for that fun little log service to run.. forgot to check if it ever got to run adbd..

ok.. so enjoy 12-06-2011 zips.. they work.. no.. do not have bfs. but they work. and they are slightly faster.
[Eee Pad Transformer Android Development] Danzano:
Maybe try SIO same effect and less of a kick in the nuts for the kernel ;)
[Eee Pad Transformer Android Development] jtrosky:
Thanks for all of your hard work, Blades - I absolutely love reading your emails - you have got to be one of the funniest devs that I've had the pleasure of dealing with! :-)

Of course, I will be trying our new kernels - just becuase! I'll be sure to report my findings!
[Eee Pad Transformer Android Development] Hammerfest:
I guess I should have mentioned how much of a BEAST BFS is to tame into a kernel... got it on my HD2 and while it did have issues with SU, I dont use too many root apps all that much. But it was fixed, then the dev abandoned the kernel/device and updates to newer kernels made the speed boost BFS gives a back seat to more compatibility and features...

Needless to say, I think there where a few lines repeated in the kernel/module bundling of BFS (or some **** like that, I am no dev, just trying to remember what I had read about what had to be done to get it fixed) or something like that which caused the SU and stability issues...

Either way, Ill nab the BFS kernels tomorrow sometime hopefully and give them a spin!
[Eee Pad Transformer Android Development] jtrosky:
FYI - Running the CptAwesome 12-06-2011 kernel and all is well so far! I am using the "chgfrq" script from @blades (thank you sir!) to lower the max speed down to 1474Mhz at boot time, however (just to try and lower battery usage a little).

I haven't really had a chance to test battery life yet though - I'll report back as soon as I know something in regards to that....

Thanks again @blades - you the man!
[Eee Pad Transformer Android Development] a.mcdear:
so far no problems with CaptAwesome kernel, but I'm still sort of a crybaby too so i reduced the Max clock to 1544 after boot.
[Eee Pad Transformer Android Development] Blades:
I can make a 1544 for you.

btw.. I've been thinking about trying to implement some sort of software raid..in which desired partitions are md devices composed of equal size partions on both NAND and SD.. obviously this could get tricky, but it wouldn't hurt to try. This wouldn't be in the main kernel, just for myself and anyone else who wants to have a go.
[Eee Pad Transformer Android Development] a.mcdear:
Naw its cool, so far all is working great. Just need to see if it will make it through the night without a Sleep of Death... (the max voltages are still a lot lower than stock though so I'm not sure I should expect it to act any better than the 8-24 or 11-26 kernels...)
[Eee Pad Transformer Android Development] Blades:
In specific, what should I bump up? I can make a kernel that has rediculously high vcore on every freq and allow you to adjust as you see fit.. not too high.. but +200mv where possible.
[Eee Pad Transformer Android Development] jwilliamf:
CptAwesome is really awesome.

@Blade, do you recommend having Setcpu installed or no Setcpu and let the kernel do its thing?
[Eee Pad Transformer Android Development] a.mcdear:
I can't remember exactly what the stock voltage table values are at the moment. I'll flash a stock kernel and write them down when I have time later today.

So far no problems though.... although the only real problem was SODs and I won't know about that til tomorrow morning.
[Eee Pad Transformer Android Development] Blades:
Ugh. Everytime I try to get a linux binary to run on android, its an epic. I have a special little libc. I know this because that's how I got par2 to run.

Once that's out of the way (funny that its the biggest hurdle), I can assemble the raid array using two loop devices, one file on /data/media or wherever and another on /Removable/MicroSD - then I can create the array and test perf. And gloat.
[Eee Pad Transformer Android Development] Blades:
Only if you need to customize your max freq above or below 1592..

Default is

max: 1592

min: 216

That said, I do have a script that takes arguments that can do this for you.
[Eee Pad Transformer Android Development] a.mcdear:
I have been talking about trying to get nstx or icmptx working on Android. I think this would be super rad.
[Eee Pad Transformer Android Development] jwilliamf:
ok, that's what I though!!! I used Setcpu went i had Roach kernel installed to upped to 1544. But since your is 1592, I'll remove Setcpu and let the kernel do its thing.

Thank you!!
[Eee Pad Transformer Android Development] Danzano:
Love the new kernel only one problem cant get the bastard to sleep properly was fine before on last kernel any ideas?????
[Eee Pad Transformer Android Development] jtrosky:
Meaning that it won't go into deep sleep if not connected to AC power? Haven't verified if that works yet - let me check and I'll come back to update this post...

EDIT: Just tested and it DID go into deep sleep after removing the charger (it will never go into deep sleep if connected to the charger).
[Eee Pad Transformer Android Development] a.mcdear:
I just checked mine (which is using the 12-6 CptAwesome kernel since this morning), which has been unplugged with the screen off for the last couple hours... It HAS gone into deep sleep occasionally during that time, but was going into deep sleep more often and for longer times on the clemsyn 22a kernel. That said, I'm still seeing better battery life than with 22a... I unplugged the tablet this morning at 9AM and its almost 3PM and its at 88% still... with clemsyn's kernel it would be at around 70% by now, even when its mostly been unused.
[Eee Pad Transformer Android Development] ursubpar:
Just flashed the crybaby version of the kernel.

No booting, just hanging.

No idea why my eee pad doesn't like your kernel.

Not your fault, just my eeepad's fault. :/
[Eee Pad Transformer Android Development] Danzano:
EDIT: It did eventually go into deep sleep just took longer to than the previous kernel
[Eee Pad Transformer Android Development] sidneyk:
I've tried both of the new kernels and still can't get any of your kernels to boot on my device. What's the chances of some builds with stock voltages or voltages to match the clemsyn-blades-ver22a kernel? That kernel works fine on my device, as well as netformer, primeOC, stock, just can't get yours to boot. I'd like to be able to since everyone that can says how it's faster.
[Eee Pad Transformer Android Development] jtrosky:
Well, it appears that I still have a battery drain problem witht the newer kernels (at least compared to the 8-24-11 kernel - aka blades2). I'm going to re-flash blades2 again, jus to be sure though...
[Eee Pad Transformer Android Development] Agfadoc:
Great work, Using the CptAwesome with Revolver and no OC Daemon, it woke up this morning just fine.

Performance is great, thanks!
[Eee Pad Transformer Android Development] jtrosky:
Just curious - how much battery % do you lose overnight if not used at all (and not charging, obviously). That's ususally how I test my battery usage. With blades2, I only lose 2-3% overnight (if that). With the later kenrels, I'm losing 15-20% overnight when not being used at all! It is going into deep sleep (not sure if stays in deep sleep the whole time or not though)...

Thanks!
[Eee Pad Transformer Android Development] Agfadoc:
I'd have to check that, I use mine all day and leave it charged overnight, so I wouldn't see any degrading at idle. I know when I check CPUstat that it sleeps and is using the lower frequencies more than it did on 8-24 and 11-26... but my usage might have changed a bit playing with Voodoo yesterday...

I'll try to let it sit overnight and see my results.

Sent from my Supercharged Asus Transformer
[Eee Pad Transformer Android Development] a.mcdear:
Well, 12-06 CaptAwesome kernel caused sleep of death again. I was sorta expecting it... gotta be those voltages, the thing just seems way too stable when I'm actually using it though... its only when its plugged in with the screen off over night that seems to cause any problems whatsoever. Survives all benchmarks or stress tests at every frequency without any signs of problems!

Battery life seems OK so far. My tablet shows its going into deep sleep now and then when the screen is off.... yesterday the battery life seemed pretty excellent, but I didn't use the tablet too much so I'll pay more attention to the battery again today.
[Eee Pad Transformer Android Development] jtrosky:
There is absolutely no doubt in my mind that I am, at the very least, getting much better battery life with the older 8-24-11 kernel (aka bades2) - at least while the TF is idle... WIth the blades2 kernel, when my device is not being used, it hardly drains at all. With the newer kernels, it drains much faster when not being used. Again, I'm talking idle battery life. In-use battery life is a little harder to nail day, becuase it all depends on what you are doing....
[Eee Pad Transformer Android Development] ratindahat:
tried latest captAweomse and got boot loops.

Tried wimpy version and wouldn't make it pasts ASUS logo boot screen.

So in short, not working for me.

i'm running revolver 3.9.5 on a B40 tablet.
[Eee Pad Transformer Android Development] philseven:
Not complaing I respect your work and I now it can be tedious. Just my observation I have notice a significant battery drain.
[Eee Pad Transformer Android Development] jtrosky:
+1 - Sent some more beer money - keep up the great work! :-)
[Eee Pad Transformer Android Development] Blades:
Wow. thats bad..

type in term emu (after long idle, short idle, whatever - more values the better):

busybox uptime

lets see what the overall load is..

ps.. changes to latest is just a raise of the enable point for throttling.. its now 52deg C.. but now I have some spicy spicy burn your hands and house highmv kernels.. so remember to undervolt them.. you can do this with a utility or upon init script.. if you want to use a utility once.. copy the values to the init script.. that'll work too..

after you set your values --

cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table > /data/local/UV_mV_table-save

and ten you'd add this to the init script after it mounts the data partition

cat /data/local/UV_mV_table-save > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[Eee Pad Transformer Android Development] a.mcdear:
I tried both of the new kernels from today(12-07)and neither of them will accept my new voltages when I try to undervolt...
[Eee Pad Transformer Android Development] sidneyk:
I tried both of the 'flamable' kernels and still no go. I get the screen with the blue-green progress bar and then the logo screen. I hear the camera click but it just stays on the logo screen. I guess my device just doesn't like to boot at higher than stock frequencies. If I use the prime boot animation it shows clemsyn-blades ver22a booting at 1 GHz. Oh well.
[Eee Pad Transformer Android Development] Danzano:
Hi blades :)

So with the new flamable kernels are the mV values for all freq's up or just high end? Are they well above stock? Are they safe ish?

My TF seems to sit comfortable at 1544mhz. 1592mhz if i stress test etc its fine but then when i have 3-4 programs (not including sys apps) running say Launcher (adwEX) Music (DUBSTEP) Emulator (N64) Vodoo (Mean Sound) it gets crashy!!!!!!!!!!!!!!!!!!! would the flamable kernels make 1592mhz more stable for me due to the increased mV and throttle temp?
[Eee Pad Transformer Android Development] Blades:
if I could increase the voltage for 1592.. I would.. 1450mV is all I can do.. thats 50 lower than the max the stupid ti tps6586x regulator can go.. I gotta check out if the prime (tf201) uses the same part.. If so, that paired with the fact that it has the same 45nm process, means little to no overclockability for the tf201.. I'm already concerned about doing quad core on the same 45nm process.

vdd_cpu must be 50mV lower than vdd_core.. and vdd_core is limited to 1500mv by ti tps6586x.. Texas Instruments.. cockblockers extraordinaire.

I just tried undervolting with the 'flamable' kernel.. it seems theres some sort of ****ed up offset.. undervolting 312 will actually undervolt 216.. Thats one issue i'll get straightened out..

Then it seems that the people that cannot boot either kernel are having problems with the ram changes.. Now.. it would be a big help if you told me what kind of ram you had..

Elpida or Hynix.. wait.. there might not be an easy way to tell... and it doesn't matter..

heres a kernel with stock memory timings

http://home.comcast.net/~ibladesi/TF101-CryBaby-12-08-2011.zip
[Eee Pad Transformer Android Development] Blades:
http://home.comcast.net/~ibladesi/TF101-CptAwesome-12-08-2011-1544.zip

and 1544 boot clock with modded memory timings..

I think I'll be organizing the builds better.. with different versions being available for different preferences.. somewhat automatically.. so every build will have a 'selectable' boot clock depending on the file you download..
[Eee Pad Transformer Android Development] a.mcdear:
So this one has the 1544 boot clock and advanced men timings, but what about the voltages? Same as the flamable kernels, or your undervolted settings?
[Eee Pad Transformer Android Development] Danzano:
Awesome cheers for that mate downloading and testing now :)

I read somewhere that anything over 1.4 on the tf doesnt increase speed that significantly compared to the freq's after 1000 but before 1500 is that true?

With the mem timmings what did you change ? clock freq's ?

I use 1024kb read ahead both blocks and altered clemsyns init.d boot script so sd has 2048kb read ahead wich i think along with the other tweaks and scripts has made my tf fussy the new prime kernel 2.0.6 wont boot at all and clemsyn is crashy so quite interested in youre kernels and work :)

Thanks for the quick answer and patience with those of us wanting to learn more about our tfs and kernels it is appreciated

P.S TRIED THE LINK I THINK ITS DEAD ??
[Eee Pad Transformer Android Development] Blades:
I had a typo in the link... I'm ****in pumped now.. I got raid working in the form of btrfs!!

I'm going to test out speeds however I can (feel free to suggest a benchmark)..

time cp will have to do for now..
[Eee Pad Transformer Android Development] Blades:
/data/local/btrfs # time cp /Removable/USBdisk1/the.universe.s06e01.hdtv.xvid-diverge.avi ./

real 0m 28.77s

user 0m 0.03s

sys 0m 3.60s

/data/local/btrfs # time cp /Removable/USBdisk1/the.universe.s06e01.hdtv.xvid-diverge.avi /data/media/

real 0m 43.54s

user 0m 0.04s

sys 0m 4.22s

ha. HA HA HA HA

ignore the random avi tv show.. its 350mb... and the usbdisk is a patriot supersonic usb3.0 - so it can provide the transfer speeds..

thats two 512mb image files

one in /data/local (/dev/block/loop0)

other in /Removable/MicroSD (/dev/block/loop1)

and I quote tenacious d.. now thats ****in teamwork...

Oh.. and that's 12.16545012165 MB/sec for raid0, 8.038585209003 MB/sec for /data/media.. now tell me, how hard does Android fail at real computer tasks like this? I'd expect nothing else from an OS that includes a smiley face key on its on screen keyboard. ****ers.

btw: kernel grew in size.. :(
[Eee Pad Transformer Android Development] Danzano:
So another link will be up soon?

As for speed testing there is a new benchmark app on the market for mem speeds hard drive transfer rates and sd cards but cant remember what its called ill try find it for you :)
[Eee Pad Transformer Android Development] Blades:
Did you know that Asus did not change the kernel version for the prime kernel? Its probably because they want to reuse their license on tntfs.. ? if that makes sense.

I didn't know you'd be interested in raid.. i'll put up the kernel with a few scripts...

I'll bet we could actually mount /data/app like this.. right after the actual data partition is mounted..

btw.. I was trying to update btrfs from newer releases.. and then I decided to see what 2.6.39 from nvidia looks like. looks like ****.. doesn't compile.. Thats two times I've fixed assembly errors with their garbage.. and I don't even know assembly. There are some scary config options for the tegra3.. and it looks like they apply to the tegra2 as well.. something about enforcing power limits.. blah blah.

I'm guessing the benchmark app would have to have root access... or be able to test a certain mount point on a device.. as of now I have it mounted at /data/local/btrfs
[Eee Pad Transformer Android Development] Danzano:
Hell yeah!!!! To be honest i just want to see our android kernels move up in the world.

I have a netbook at home which i made a custom kernel for and it runs amazingly in comparison to before!!!!! Android in general has had pretty crap kernels with the gt540 i think there where kernel hacks before there was a system.

I think android needs to start thinking about schedulars about scripts to alter timmings etc on the fly within the permissable ranges etc etc people are getting more clued on so expectations rise and i think because of that effect there is a huge calling for people to take crap like what you just explained (nvidia) and actually make something usefull from there sub par efforts.

And i would guess the same but i would think maybe an autoscan of the usual mount points then if still no joy manual path entry.
[Eee Pad Transformer Android Development] jtrosky:
Good stuff... So how does RAID work for flash storage? Are you writing each "chuck" to a different physical flash storage chip or something?

Thanks for the info - like I said - good stuff!
[Eee Pad Transformer Android Development] a.mcdear:
I have that same series on my htpc :-)

** EDIT **

So i was updating to the 12-08 CaptAwesome kernel. Afterwards I told the ladies how awesome I was, but they must have been Apple iFans cause they didn't seem very excited for my body.. even after I showed them the CPU state history.. :'(

Anyways, running great as usual.... still getting SODs almost anytime the tablet isn't used for more than a few hours. :-(
[Eee Pad Transformer Android Development] devilpera64:
So Blades what are your next goals? you will insert them in the next version of Kernel? =) i would hope!! xDD
[Eee Pad Transformer Android Development] Blades:
Sure.. I can do the raid thing right now.. The thing is, what to do with it.. I do like the idea of having /data/apps on there..

I would do this by making a temporary image, transferring the contents of /data/app... copying this to the btrfs image(s) and configuring the tablet to mount the btrfs image(s) before android loads.. Now, I think this may need to be done via the ramdisk.. I don't know.. I'll test it out.. honestly tho.. raw transfer speed isn't lacking when it comes to apps.. its file transfers that I find to be pathetic.. the apps for android are probably created with this suckage in mind..

a.mcdear: Have you changed the voltage at all? It has to be one of the lower clocks.. but wait.. that would mean you'd experience a lock up or two when using it... so.. its when it enters low power state... so what changed then? Possibly memory timings... Did you ever try stock memory timings?
[Eee Pad Transformer Android Development] devilpera64:
Great! I was thought that you wrote few days ago that our TF's memory runs to lowerest freq respect datasheet...have you found why or what's the problem? could them modified as we do for normal PC RAM entering in the Bios? :)
[Eee Pad Transformer Android Development] sidneyk:
I tried this one, still no go for me, so it must not be the memory timings. Thanks for all the work and effort. I'm thinking that it may be the boot frequency because it appears that the clemsyn-blades ver22a kernel boots at stock frequency when there are no helper apps to apply OC settings. That one, netformer, primeOC all boot fine. Again, thanks for the effort.