yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Kingzak34:
If someone is interested here's the initrd file. ( renamed with zip extension to upload it )

I'll do some test when I'll got a bit more time to see what can me removed in order to flash it...

https://www.wuala.com/Kingzak34/Divers/initrd/?key=NT3gGbRu0UiG
[Eee Pad Transformer Android Development] jrohwer:
When repacking the boot image with abootimg, delete the line

bootsize = xxxxxxxxx

from the bootimg.cfg file.

If you don't delete this line, the boot image is re-packed to the specified boot size which is the same as the original one (so the blob won't be any smaller). It is however safe to delete this line, and then the boot image will be repacked to the actual minimum size.
[Eee Pad Transformer Android Development] Kingzak34:
I'll check that, thanks ! :) I'm learning everyday
[Eee Pad Transformer Android Development] jrohwer:
It's been a helluva learning curve for me as well and I'm still learning ... :)
[Eee Pad Transformer Android Development] Boss_Cuco:
Hi!

I've installed x3maniac's 1.6GHz kernel. Then I changed it with cpufreq to 1.4GHz but when I restart it is back to 1,6.

How can I keep it from changing it again?

Thanks!
[Eee Pad Transformer Android Development] Kingzak34:
It's in this thread somewhere, I dont remember where, I suggest you to search in this thread
[Eee Pad Transformer Android Development] jrohwer:
Create a file /etc/default/cpufrequtils (or edit it if it exists already) to contain the following lines:

ENABLE="true"
GOVERNOR="ondemand"
MAX_SPEED="1504000"
MIN_SPEED="0"

Edit the settings to your liking, but the speeds must be valid speeds:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
[Eee Pad Transformer Android Development] JoinTheRealms:
Another way is by using the cpufrequtils package (sudo apt-get install cpufrequtils) and run "echo cpufreq-set -d 1.4ghz >> /etc/rc.local" and/or "echo cpufreq-set -g *desired cpu governor* >> /etc/rc.local"

cpufrequtils is great with gnome becouse you can add an icon to the panel and change freqs and governors with a drop down menu:good:

Also if anyone wants android like scrolling in chromium try the "chrometouch" addon, it works really well.

Also Also would just like to say the information in this thread is golden I really appreciated it !
[Eee Pad Transformer Android Development] Kingzak34:
Thank you for the tips :)
[Eee Pad Transformer Android Development] TomTcom:
I lost track of where we were at but I gave up on my own initramfs. I installed the old original 3.1 kernel and modules. It boots with my raring image but all kinds of failure finding modules even though the supplement is installed. I may try to recompile again.

The second 3.1 kernel didn't boot.

I'll play some more later and see what happens. I can't resist tinkering with this stupid tablet...lol!
[Eee Pad Transformer Android Development] Kingzak34:
Should be cool to have another 3.1 kernel :) I didnt have time to play with onmail one for mountloop, but I've to.

---------- Post added at 07:37 PM ---------- Previous post was at 07:30 PM ----------

BTW, Does anyone have some trouble with touchscreen that doesnt want to do some action sometimes ?

For exemple, I cant double clic or clic to a folder to open it.

I must click on battery statut first in order to click on anything in the bottom bar of Gnome ( Logout for exemple or Onboard tray icon )

I tried to use touchegg, it see that I do gesture, but on every gesture it says "UNKNOW GESTURE" fingers : x

That's a real pain when you want to use only touchscreen even if I have a keyboard.

I tested ubuntu on Nexus 7 and I should say that ubuntu desktop for Nexus 7 is really amazing.
[Eee Pad Transformer Android Development] transformador:
I had exactly this issue too, only thing that helped was removing touchegg in /usr/bin...

What and were is that onmail kernel? I cant find it..

Hey i found razor qt for arm, try it guys!!! (wtf i cant find the page anymore, i will upload the .deb)
[Eee Pad Transformer Android Development] Kingzak34:
onmail posted his kernel some pages before dont remember where

And what did you have ? Trouble about touchscreen or about touchegg ?
[Eee Pad Transformer Android Development] transformador:
The touch stopped doing actions at one point (but i saw it working because it was marking buttons (but no action lol)), so both :) Removed touchegg and everything worked fine :))

Anyone remembers how to change color mode via xorg.conf? i remember i had a faster experience xDD
[Eee Pad Transformer Android Development] jrohwer:
Did you run:

sudo depmod -a

from a terminal and then reboot? Sometimes that is needed (only once) for modules to be found. Just copying the modules into /lib/modules is not sufficient sometimes.
[Eee Pad Transformer Android Development] TomTcom:
I'll try when I get home, thanks, forgot about that.
[Eee Pad Transformer Android Development] jrohwer:
Only seeing this now, sorry. Sure, you are welcome to post my kernel :)

---------- Post added at 09:23 PM ---------- Previous post was at 08:48 PM ----------

Any luck with this? I tried merging the latest nvidia kernel source for 16.3 into my git which I had originally cloned off Jhinta's kernel tree.

Tried to compile but there were major errors with compiling the file

arch/arm/mach-tegra/board-tf101.c

This file does not exist in the nvidia tree and I'm not sure if Jhinta modified it from board-ventana.c. It is however quite different. In any case I don't have any C programming skills to debug this, so will have to stick with what I've got.
[Eee Pad Transformer Android Development] zachf714:
I learned c++ on youtube. Would you like the link c++ is much easier than java, I'm 14 and have a basic understanding of it :)
[Eee Pad Transformer Android Development] TomTcom:
Not really. I was able to create a zImage but when combining it with a working boot and initramfs it would error out before the GUI loaded. The documentation and details are sorely lacking in my opinion and the Nvidia dev forums aren't much help.

I also tried the scripts from the Nvidia source with the tag of 16.3 per the pdf from linux-tegra website however the Nvflash would appear to work then error out on the send so I keep getting a lot of roadblocks.
[Eee Pad Transformer Android Development] jrohwer:
Sure send me the link :)

---------- Post added at 10:06 PM ---------- Previous post was at 09:58 PM ----------

The nvflash scripts from nvidia won't work. TF101 is not tegra (although it has a tegra board). Hence all the issues we have compiling kernels...

If you compare the nvflash scripts of nvidia with OLiFE you'll see that they are different (bootloader, BCT, etc.).

EDIT: Well at least I was able to get the 16.3 binary drivers going on my Ubuntu. Ran the "apply_binaries.sh" script. It actually works and I get HW accell :good: Needed to simlink the libs (libGLESv2.so.2 and libEGL.so.1) to /usr/lib/arm-linux-gnueabihf (the script installs them in /usr/lib). Then ran "sudo ldconfig".

Running es2gears I get 170 FPS.

It throws me an error

Couldn't open /sys/bus/nvhost/devices/host1x/syncpt/22/max

I assume it has to do with the fact that the kernel is outdated.

However the speed is way faster than what I get with the MESA driver (software GLES rendering), only about 35 FPS

BTW I'm running kubuntu 12.04 (with low-fat settings), runs really nicely. It has a window manager compiled with gles (kwin_gles) if you activate that you can get desktop effects (cube, etc) with hw graphics accell.

Now if only I could get this kernel to boot 13.04....
[Eee Pad Transformer Android Development] zachf714:
[MENTION=3753391]jrohwer[/MENTION] here http://m.youtube.com/#/watch?v=ki3B8a-jLrE&desktop_uri=/watch?v=ki3B8a-jLrE :)
[Eee Pad Transformer Android Development] Kingzak34:
Nice to hear that HW can be better. I'll try to get touchegg working properly in the first time because it's really annoying.

I think we can make something really nice with that ubuntu ( I mean more than now :D )

I'm just waiting for x3maniac return tu repartionate my tab again, cause I think backup option is a really lack and mountloop is a good thing for that :)

BTW, I'll post jrohwer kernel tomorrow for both dualboot and mountloop GUI.
[Eee Pad Transformer Android Development] TomTcom:
I would thank you but I ran out of them today...lol!
[Eee Pad Transformer Android Development] zachf714:
How many do we get lol .. I still need to send my tf101 dock back again to het fixed because of the same problem
[Eee Pad Transformer Android Development] TomTcom:
Only 8 per day. My dock and tf have been workhorses..I've battered them up quite a bit and they still come back for more.
[Eee Pad Transformer Android Development] zachf714:
The battery has expanded inside my dock 4 times now .. the board in the dock needs to be replaced because tve cutoff is bad and I learned that from experience :)
[Eee Pad Transformer Android Development] jrohwer:
What is you problem with touchegg? Works perfectly for me. I get it to load automatically on startup and all works fine. 2 fingers swipe to scroll. 2 fingers tap for right click. 3 fingers up for maximize window, 3 fingers down for minimize. I'm just using the defaults, haven't bothered customizing it but the config file syntax is pretty self explanatory.
[Eee Pad Transformer Android Development] transformador:
When using touchegg in 12.10 or 13.04 the touch sometimes just doesnt do the actions you click on(for me on lubuntu as soon as i click desktopnothing reacts anymore (i mean the touch isnt interpreted right),), i removed touchegg and everything worked again. (but touchegg works nice in 11.10 and 12.04 for me :)
[Eee Pad Transformer Android Development] jrohwer:
OK that explains it. I still use 12.04 :)

BTW what kernel are you running on 12.10/13.04?

Has anyone managed to run 12.10 or 13.04 with a 3.1.10 kernel? Banging my head against a wall herer :confused:

I know 2.6.36 works but then you don't get the graphics acceleration.
[Eee Pad Transformer Android Development] transformador:
Which 2.6.36 are you using with mountloop? I am using jinthas kernel, made a mountloop package, it is in my thread(.linux1) :)) (working with every ubuntu i used :))
[Eee Pad Transformer Android Development] jrohwer:
I am not using 2.6.36 on a regular basis but have tested Lilstevie's original kernel just to see if it boots 13.04. I use Jhinta's kernel as well (self compiled). Strange that it doesn't work, I'll try yours :)

I have moved away from mountloop to running off an ext4 partition on the MicroSD. I've found this to be up to 2x faster for disk access if you have a decent (class 10) microsd!
[Eee Pad Transformer Android Development] transformador:
Really? Means i will get a class 10 micro sd this afternoon :)) Can you make a microsd package of the kernel yourself or should i do one for you? :)

Can you share me your 2.6 kernel pls? (sound working??)
[Eee Pad Transformer Android Development] jrohwer:
No prob I'm compiling kernels, making boot images and backing blobs all the time so I know how to do it :) So I'm onto it and will test your kernel and report back here.

My 2.6.36 kernelblob (blobunpack to get the boot image) attached. It is basically Lilstevie's kernel with the sound patch compiled in so yes, sound is working.
[Eee Pad Transformer Android Development] transformador:
Thanks man :) Btw your 3.1 kernel iis awsome, i use it daily :)
[Eee Pad Transformer Android Development] jrohwer:
So can you boot into 13.04 with my kernel??? WTF??? Why can't I do it myself? (I have TF101G). Are you using my initrd or another one?
[Eee Pad Transformer Android Development] transformador:
No, sadly thats not working :( I use normally 11.10 with your kernel (because of stableness, your kernel and touchegg), but i use both 12.10 and 11.10 :) (but this post is written from 11.10 xD)
[Eee Pad Transformer Android Development] jrohwer:
OK that explains it :) I use 12.04 on a daily basis and am basically happy, almost perfect.

I'll try one of your kernels and extract the config, maybe try to compile with that config to see if it will boot raring.
[Eee Pad Transformer Android Development] TomTcom:
I have a fully updated Raring so I'll give this kernel a shot when I get a chance today just to see what I get. I'll let you know later tonight.
[Eee Pad Transformer Android Development] jrohwer:
Sorry ran out of thanks for the day :(

Update: I can boot raring (in text mode) with "linux1" kernel from transformador. I extracted the config, and compared it to mine, and there are only few differences so that can't really explain it. I will however recompile with his config. The other issue is that the initrd has been compiled into the kernel so I can't see what initrd he used. In the android boot image he just used an empty initrd. Anyone know how to extract an initrd.img from a zImage? I know some samsung phones kernels are compiled in the same way.
[Eee Pad Transformer Android Development] transformador:
I am sorry for not knowing this, because x3maniac compiled the kernel, i extracted it from the program (i forgot from where the kernel was and i just remembered), so it is exactly that jintha kernel that shipped with tubuntu. Btw, wtf happened to x3maniac?

EDIT:

Maybe one of these helps?

http://xdaforums.com/showthread.php?t=1294436

http://xdaforums.com/wiki/Extract_initramfs_from_zImage
[Eee Pad Transformer Android Development] zachf714:
If you can compile the kernel as a boot.img or use koush's anykernel zip to make a boot.img you can decompile that with android kitchen :)
[Eee Pad Transformer Android Development] TomTcom:
See if this link helps you:

http://xdaforums.com/wiki/Extract_initramfs_from_zImage

I noticed that initrd is typically separate from zImage while initramfs is inside zImage (if I have that correct) for kernels later than 2.6 and so on?
[Eee Pad Transformer Android Development] Kingzak34:
Like transformador said, sometimes touchscreen doesnt want to do an action like I said here : http://xdaforums.com/showpost.php?p=42242804&postcount=1118

And I'm using 12.04 ( netinstall touchegg compiled during installation )
[Eee Pad Transformer Android Development] onmail:
Basically how to extract the initrd and zImage:

abootimg -x kernel.img

To extract .config from zImage (look inside the folder "scripts" in your kernel folder:

extract-ikconfig path_to_zImage >> .config

"My" image (not really, I just compiled and used initrd from another image) to play with:

xdaforums.com/attachment.php?attachmentid=2007000&d=1370012904
[Eee Pad Transformer Android Development] Boss_Cuco:
Hi!

Did you create your Raring image with your tutorial? Is it more stable for everyday use than Lubuntu v1.2? I thought Raring was too heavy for our transformers.

What kernel are you using?

Probably stupid question but I don't know if I need to delete/move/replace the supplements from my kernel when I install a different one...

Because my tf only booted with a kernel already with the supplements...

Thanks ;)
[Eee Pad Transformer Android Development] onmail:
TomTcom's tutorial is great. Do not worry about trying it. I think it is comparable with Lubuntu images with 2.6 kernels. It can "work" with 3.1 but when you can't use the Nvidia drivers I think there is no need to. And btw those supplements - see step 13. in this guide. Or you can easily do it with eg. Midnight Commander. The mounted image is just a directory. If you want to have a script to automatically make a new user, set passwords, prepare rc.local with cpufrequtils and install couple of things (even on your PC when chrooted], I can send you just a quick one I made for myself. I am lazy :)
[Eee Pad Transformer Android Development] Boss_Cuco:
Thanks!

I've never heard of Midnight Commander but I might look into it! Whats does your script do btw?
[Eee Pad Transformer Android Development] onmail:
To be clear - mc is nothing more or less than a file manager for linux (I hope you want to "cook" raring image on linux ;) ) And the script - see attachment. Look inside, change, play with it. Basically it was made to be run while chrooted in your basic image. If you look in TomTcom's tutorial, so add a step eg. 13a copy the sh script from this zipfile somewhere inside the mounted image folder. And instead of step 16 run this script. But first have a look "inside" it and change (comment, uncomment) what you like. If your kernel is not stable at 1.4, you can lower the number there etc... Sorry for my English here and in the script. Hope it is understandable...
[Eee Pad Transformer Android Development] Boss_Cuco:
Thanks!

Right now I don't have much time but I'll give it a look :D
[Eee Pad Transformer Android Development] Kingzak34:
One usefull thing more in this thread, thanks for sharing :)
[Eee Pad Transformer Android Development] TomTcom:
I chatted with x3 the other day. He'll be back soon but he's been busy with other things just to let you all know.
[Eee Pad Transformer Android Development] Kingzak34:
That's a good new, I hope he's all right :)
[Eee Pad Transformer Android Development] TomTcom:
Yeah he's good just been focusing on other stuff as far as I know.
[Eee Pad Transformer Android Development] TomTcom:
Correct, I used my own guide to make the image. It's a Raring gnome-core image meaning you would have to install a GUI using my other guide in my signature.

Otherwise on reboot you have no GUI. Takes a while for everything, about 2 hours. You'll have plenty of space.

I find the newer images with 2.6 kernel very stable.
[Eee Pad Transformer Android Development] Kingzak34:
Hey there I've a question. I know that to install an img file on a parition its dd if="XxX.img" of="partition"

But does the inverse work (I mean dd if="partition" of="imgfile" ) ( cause I want to do some backup script, I installed my img in a partition of my Class 10 micro SD. And I didnt have time to test if img file works )
[Eee Pad Transformer Android Development] TomTcom:
Maybe...check out the first big paragraph. It says back up a boot sector but not sure of using it as a back up method.

Click on the DD Unix link when the page loads.

http://en.m.wikipedia.org/wiki/Dd_(Unix)
[Eee Pad Transformer Android Development] Kingzak34:
So, I'll try and let you know !

BTW, here's jrohwer kernel for mountloop GUI version I forgot to post it.

it boots /data/media/ubuntu.hf.img
[Eee Pad Transformer Android Development] jrohwer:
Thanks your second link helped, and I managed to figure it out. It was more difficult than anticipated because the kernel used lzma compression for both the complete kernel, as well as for the initrd inside the zImage. So I've extracted the initrd that Jhinta used in the "linux1" kernel. Busy recompiling my Jhinta kernel tree with the config in that kernel and the extracted initrd. Will keep you posted....

---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------

See my above reply. Re. initrd vs initramfs I think these are really synonyms for the same thing, and whether it's separate or compiled into the kernel are just 2 ways of doing this. E.g. the ubuntu script for generating initrd images is called "update-initramfs" but the initrd images in /boot are called initrd.img-<kernelversion>.

---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------

Never seen this on 12.04 (although I'm running kubuntu, don't know if it makes a difference).

---------- Post added at 09:21 PM ---------- Previous post was at 09:17 PM ----------

Yeah of course I'm fully aware of these commands :) But that's for the "normal" setup when the initrd is separate from the kernel zImage. And then they are compiled together into an Android boot image using someting like abootimg. When the initrd is physically compiled into the zImage, abootimg can't extract it. But I managed with other method (see above replies).

---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------

Yes the inverse works as well, so you can do dd if="partition" of="imgfile". However, I've found that it is generally easier to use tar for backups and restore. This is also what TWRP uses under the hood. So you can mount your partition at a certain mountpoint, say /mnt/aaa, then do

cd /mnt/aaa

tar -czf /path/to/backupfile.tar.gz *

For the restore option, you'd format the partition (ext4), then mount it (again say at /mnt/aaa), then

cd /mnt/aaa

tar -xzf /path/to/backupfile.tar.gz

Just be sure not to have the backupfile on the same partition as the one you're making a backup of.

Another advantage of tar backups is (i) compression and (ii) you only backup data, so if you've only used 2Gb of a 4Gb partition, you'll only backup 2Gb of data whereas with dd you'd backup all 4Gb and thus unnecessarily copy 2Gb of empty space.
[Eee Pad Transformer Android Development] TomTcom:
Hey..regarding your post to me..you are correct on initrd and initramfs. I believe initramfs is baked in making me question how I could use it if abootimg was doing the packing required a separate initrd file. I tried without it and being baked in and it wouldn't let me combine them all to make the flashable image.

It's fairly confusing on what you should and shouldn't use, include not include, etc. Now couple that with Linux on a device that wasn't truly sold as a Linux device and lousy instructions ...lol!

But I guess that's why we still commit to these threads.
[Eee Pad Transformer Android Development] jrohwer:
Sure dd can back up the boot sector but this is not relevant for our TF101 as Android uses a different boot process (bootloader plus Android boot image) which are all on separate partitions. However you can also use dd to do a bit-copy of entire partitions. For example, if you have an Ubuntu partition somewhere you could do a dd and use the outfile for mountloop and it should work perfectly.

---------- Post added at 09:50 PM ---------- Previous post was at 09:44 PM ----------

When using abootimg with a zImage that has the initrd baked in, you have to use an "empty" initrd for abootimg, i.e. just create an empty folder, then cd to that folder, then do "find . | cpio -o -H newc | gzip > ../initrd.img". This will give you a very small dummy initrd.img that you can use with abootimg.
[Eee Pad Transformer Android Development] TomTcom:
Ahhh...gotcha jrohwer...thanks for that. I heard the reference and maybe it was even said here bit I didn't put 2 and 2 together.
[Eee Pad Transformer Android Development] Kingzak34:
Thanks for tips and answers :)
[Eee Pad Transformer Android Development] jrohwer:
3.1.10 kernel for all Ubuntu versions

OK, after hours of testing and debugging I think I finally now have a 3.1.10 kernel that can boot the older and newer Ubuntu versions :good:

There was a problem with the previous initrd I used, however, I'm still not sure why it was happy booting 12.04 but not 13.04.

So the lowdown: Attached are

1. vmlinuz*****.img - kernel image (lzma compressed)

2. initrd.hf.new.lzma.img - initrd.image (lzma compressed). You can used 1 and 2 to roll your own boot image with abootimg.

Alternatively:

3. kernelblob******.img - blob for flashing with dd or with CWM. This assumes Ubuntu is on the microsd (/dev/mmcblk1p2). If you want to change this, you'll have to blobunpack the kernelblob and then use abootimg on the resulting file kernelblob*******.img.LNX

4. Kernel modules. Extract to /lib/modules of your rootfs. Remember to run "sudo depmod -a" after first boot with the new kernel, and then reboot. Otherwise the modules won't load and zram, wifi, etc. won't work.

This works for me using Ubuntu 12.04 and 13.04. Not tested 12.10 but I assume it should work. Testers welcome :)

Other than the changed compression (lzma vs gzip) the kernel configuration is exactly the same as in the previous kernel I posted so it should give the same level of performance and stability :)

Boot process takes slightly longer than the previous one because lzma decompression is slower than gzip. But one up and running it's snappy.

Testers and feedback welcome :fingers-crossed:
[Eee Pad Transformer Android Development] projeto56:
Looks like it's the right time to get back poking my tab :P