yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] :
Hi :) i have a big problem... I have TF101 16GB with Android Revolution HD 3.6 and i want to unpack ubuntu image in my tablet but every time while extracting, the terminal sticks on a file (every time is different) and i have to stop the terminal (tried waiting 2-3 hours and nothing)... the terminal stucks sometimes on a casual file in /usr and i can't extract it :( can someone help me? i tried guides made by DjDill, jrohwer and Kingzak34 but every time sometimes was wrong...

Thanks in advance :)
[Eee Pad Transformer Android Development] Kingzak34:
What terminal do you use ?

Have you enough space in /data partition ? ( Type df to know )
[Eee Pad Transformer Android Development] :
Android Terminal Emulator... with command df i see: /data Size 12G Used 2G Free 10G
[Eee Pad Transformer Android Development] Kingzak34:
So I dont know, you should try from ADB with a computer.
[Eee Pad Transformer Android Development] :
with which command? :P
[Eee Pad Transformer Android Development] Kingzak34:
Same command, just access to your device with : adb shell

Google it for more informations
[Eee Pad Transformer Android Development] :
thanks a lot :) but there is another problem... XD when i type on pc tar command, every time that i choose the tar.gz (on tablet or on pc) the terminal says: No such file or directory... what can i do? where do i have to put the tar.gz?
[Eee Pad Transformer Android Development] Kingzak34:
Where is your file, what is it name ? and what command do you do exactly ?
[Eee Pad Transformer Android Development] :
it's tf101-14.04-Lubuntu-Tegra-armaf.tar.gz and I have one in platform-tools and one on my internal memory.... i did "adb shell", the other command of your wonderful guide (^^) and then "tar -xpjvf /sdcard/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz" or "tar -xpjvf C:\Users\Domenico\AppData\Local\Android\android-sdk\platform-tools\tf101-14.04-Lubuntu-Tegra-armaf.tar.gz" and the terminal says "no such file or directory"
[Eee Pad Transformer Android Development] Kingzak34:
Rename the file to get the command easier. I think there is a typo error somewhere.

And try to use /data/media/yourfile instead of /sdcard/ check the good path with terminal emulator and auto completion feature

BTW, in adbshell you could not use a file from your computer, it's the same thing as android terminal emulator.
[Eee Pad Transformer Android Development] :
nothing... i thing my tablet is dying... another way to install ubuntu? (i think that there aren't :/)

PS:nothing changing the name :/ the tablet stucks on every file when the process was running... the file now works (i don't know why but it was deleted o.o)
[Eee Pad Transformer Android Development] Kingzak34:
So I can only suggest to format /data partition, it may clean it from errors.
[Eee Pad Transformer Android Development] :
i did it every time XD i go to Katkiss 4.4 sometimes to try new roms, but then i do full wipe and put on the stock rom (ARHD), and i retry flashing ubuntu... i did a lot of wipe data XD i don't know what i have to do... :( only to me...
[Eee Pad Transformer Android Development] Kingzak34:
No, I don't say wipe data, but format data, including internal storage.
[Eee Pad Transformer Android Development] dvhh:
One (unverified) way to check the data partition for error is to boot to recovery (TWRP or ClockWorldMod), then from another computer connected to the tablet use adb shell

unmount the data partition ( should be mmcblk0p7) then run fsck

umount /data
e2fsck -fv /dev/mmcblk0p7

this is from memory, I don't know if the utility is enough to repair the partition, but at least it is enough to mark it clean (which was enough for my needs).

Worst case scenario is to restore from nvflash to have a brand new data partition.
[Eee Pad Transformer Android Development] :
now i'm trying to format all, then i'll try to use nvflash... anyway, thanks for your attention :)

---------- Post added at 05:22 PM ---------- Previous post was at 04:45 PM ----------

the command is e2fsck -fv /dev/block/mmcblk0p7.... but if i do it, the terminal says me that the partition file system is mounted when i unmounted it :(

PS: i know why... i have to unmount /data and also /sdcard because they are the same partition block

---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------

here the log:

~ # ←[6ne2fsck -fv /dev/block/mmcblk0p7

e2fsck -fv /dev/block/mmcblk0p7

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

34782 inodes used (4.13%)

112 non-contiguous files (0.3%)

7 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 21892/18

466507 blocks used (13.87%)

0 bad blocks

1 large file

19626 regular files

2138 directories

0 character device files

0 block device files

1 fifo

15 links

13007 symbolic links (12862 fast symbolic links)

1 socket

--------

34788 files

nothing wrong i see, but the command doesn't work anyway
[Eee Pad Transformer Android Development] jrohwer:
Edit - ignore. I replied too quickly before reading all the replies.
[Eee Pad Transformer Android Development] :
so what can i do? the terminal stucks every time on a casual file in /usr... do you think that i need a repartition?
[Eee Pad Transformer Android Development] jrohwer:
Nothing seems to be wrong with your partition as you have plenty of free space and e2fsck reports no error. The obvious stuff: your downloaded file might be corrupted. Have you checked md5? Or tried redownloading the image? For all the images I posted I have included md5 values.
[Eee Pad Transformer Android Development] :
i'll try to redownload it from another source :P
[Eee Pad Transformer Android Development] :
nothing, nothing nothing :( why??? is my tablet dying? because i redownloaded it but nothing... any hint?
[Eee Pad Transformer Android Development] dasbooter:
Meh, doubt it is dieing. I am having similar problems with lubuntu 14.04 and the .12 kernel. I got fsck errors on first boot & cant mount temp and skipped everything booted up fine wifi was working nicely. Rebooted decided to let e2fsk run its scan and fix the errors and now shows more errors and hangs in the boot. I don't think I'm going to blow out my android install just to try to get this to work just yet. Just thought I would drop you a line to say I had similar problems.
[Eee Pad Transformer Android Development] :
Thanks everyone :) i've booted it but i have another problem XD (the real problem is me XD).. i can't read my microsd as every partition, firefox is too slow and i can't start a video... and at the boot i see: fm34 0-0060: Failed to acces device... systemd-udevd could not open moddep file /lib modules/3.1.10-15-gabaf62d/modules.dep.bin
[Eee Pad Transformer Android Development] dasbooter:
Sigh... it seems I cant restore even from my twrp backup I can only guess that the whole partition that linuxroot resides on is borked which includes the storage of my backup.Restoring boot,data,and system fails in twrp and restoring just system and boot hangs at the asus screen Any thoughts on my plight anybody
[Eee Pad Transformer Android Development] :
restore tablet with easyflasher and stock rom from asus support http://support.asus.com/download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&os=32 then reflash twrp and retry... if twrp backup doesn't work, it's damaged

---------- Post added at 09:41 PM ---------- Previous post was at 09:27 PM ----------

i can't mount any external (or internal) partition but i i do sudo rm -r /home/tf101 i can't boot the next time ubuntu... what can i do? and for firefox is there an alternative browser (better speed and youtube working :P)? thanks :)
[Eee Pad Transformer Android Development] :
YEAAAAAAAAAAAAAAAAAAAH :) i found a working metod to mount USB devices on Lubuntu without deleting anything :)

So let's open: LXTerminal (in Accessories) and Disk (in Preferences)...

1- open LXTerminal, and write

and see which device is yours (example for MicroSD is mmcblk1p1 (it's different for each device)

2-in terminal write

i wrote external only for an example (you can make the folder with every name

3a-then IF the device has a file system as FAT/FAT16/FAT32 write

3b-else IF the device is NTFS write

4- now go in Disk and select in the list the interested device and partition..

4.1- near the partition tabel ther is the STOP button (a square): click it to unmount the device from the actual position...

5- click on the option button and go in Edit Mount Options

6- put Automatic Mount Option to OFF

6.1- in Identify AS menu, select /dev/mmcblkX or /dev/sdX

6.2- then in Mount Point write the folder created before where you'll mount the device, in my example is:

6.3a: for FATxx device in text bar above Mount Point write

6.3b: for NTFS device write

(this is needed because the system doesn't allow an empty text bar)

6.4- finally click on PLAY button to mount the device, and VOILA it's mounted :)

If there is a problem, say it to me (maybe i made a text error :P)

Source: https://help.ubuntu.com/community/Mount/USB
[Eee Pad Transformer Android Development] :
ehm hi :) my sound on Lubuntu 14.04 doesn't work, and even with a reboot it doesn't work, how can i reset it to make it working again? thanks :)
[Eee Pad Transformer Android Development] dvhh:
When the sound don't work a cold reboot is necessary (shutdown then turn on), a hot reboot would not fix the issue.
[Eee Pad Transformer Android Development] :
How can i fix it? Thanks :)
[Eee Pad Transformer Android Development] kekazoh:
Anyone tried to install any java/Android IDE?

I installed the ARM version of Eclipse (from repos) and it works except for the plugins installing and updating. I would like to be able to develope in Android in the TF101.

I also tried with Android Studio but it's not working at all. Now i'm trying with IntelliJ community edition to see if it works, but i'm a Eclipse guy and i don't if i will get use to it...

I also tried to install wine on this, and after hours compiling didn't work ¿Anyone tried?

BTW, I'm using the Lubuntu 12.04 version of DJDill.
[Eee Pad Transformer Android Development] Kingzak34:
Maybe eclipse plugins are not compatible with ARM proc ?

For Wine, almost no chance to get it running.
[Eee Pad Transformer Android Development] folderman:
Hi All,

Anyone is working fine with bluetooth? It works for once but not further.

Which version you are using? v12 or v14?

Thanks!

PS. I am using v12

Rgds,

Kenneth
[Eee Pad Transformer Android Development] jrohwer:
Works for me. I use it regularly to connect a BT mouse and keyboard. Have not really used it for much else. Note that if you want to switch off bluetooth you first have to disconnect all the devices, otherwise it will hang. Works for me on 12.04 and 14.04.
[Eee Pad Transformer Android Development] folderman:
oh, i think it is my problem again. let me take a deeper look first. at least, i know the image should be working fine.

thanks!

kenneth
[Eee Pad Transformer Android Development] maksvlad:
I have the same problem. I tried lubuntu 14.04, 12.04, kubuntu 14.04 with different kernels. keyboard and touchpad stopped properly work in about 30 sec. Full charging didn't effect on. I have no idea what causes are.
[Eee Pad Transformer Android Development] :
Hi :) any news about development?
[Eee Pad Transformer Android Development] jrohwer:
What do you want developed? :)

I have a fully working image with HW acceleration, USB, wifi, BT, overclocked kernel. Only issue that remains is sound, which is flaky, which I haven't been able to solve.
[Eee Pad Transformer Android Development] :
well... which image are you talking about? XD because on DjDill last image HW acceleration is based on mesa drivers (because i have with es2gears only 57fps and youtube has a lot of lags, mounts are broken :P)
[Eee Pad Transformer Android Development] grofweg:
What kind a fps do you want. 57 fps is more than acceptabele for thuis kind of tablet

Verstuurd vanaf mijn Transformer met Tapatalk
[Eee Pad Transformer Android Development] Kingzak34:
When driver are used, it's around 300
[Eee Pad Transformer Android Development] :
which image are you using?
[Eee Pad Transformer Android Development] jrohwer:
Kubuntu 14.04 (third image listed on the OP) made by myself. Tegra drivers are working, es2gears gives more than 300 fps. Note, you have to use a window manager that is GLES aware to get the full benefit (e.g. kwin_gles). I believe you can use kwin_gles with other desktop environments than KDE (e.g. LXDE) but have never tried myself nor know off hand how to set it up. This should certainly help.

For the kernel, you can use my overclocked (1.5 GHz) kernel from this post:

http://xdaforums.com/showpost.php?p=43177640&postcount=3

Note that you will have to copy the modules to your rootfs (they are not part of the kubuntu image as I had not made the kernel yet at that point). And you'll have to manually set the maximum frequency with cpufrequtils as explained here:

http://xdaforums.com/showpost.php?p=54031885&postcount=334
[Eee Pad Transformer Android Development] Kingzak34:
You remember me that I need to update my guide a little with new kernels :)

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] :
hi :) i saw in some images an error at every boot (something about corruption or errors in / -/data/linuxroot-) and i tried to check the disk but i had this

~ # ←[6n e2fsck -fv /dev/block/mmcblk0p7

e2fsck -fv /dev/block/mmcblk0p7

e2fsck 1.41.14 (22-Dec-2010)

Superblock blocks_per_group = 16376, should have been 16384

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 16376 <device>

what does it mean? thanks :)

---------- Post added at 12:40 PM ---------- Previous post was at 11:59 AM ----------

mmm i have another problem... when i flash kubuntu 14.04 or ubuntu 14.04 only base, with 3.1.10-12 or 3.1.10-15, i can't boot ubuntu image... i see every time only normal messages as: power_supply dock_battery: driver failed to reporstatus property, or ulpi messages, but it cannot boot the os... why? thanks in advance...
[Eee Pad Transformer Android Development] jrohwer:
I think it is time that you reformat your /data partition. those ext2 errors don't look good...

Note this is NOT factory reset (That just uses rm -rf on certain folders but leaves /data/media intact). You want to use FORMAT DATA from inside the TWRP advanced wipe menu. Note you will lose ALL DATA including your INTERNAL STORAGE (emulated sdcard). So if you can backup some of that in recovery maybe try to do that before formating.

Also after formating, before re-installing anything, just run e2fsck again to see if the errors are now gone.
[Eee Pad Transformer Android Development] :
yeah :D thanks a lot :) now the ubuntu images boot without any problem (only 14.04 base, wifi doesn't work...)... thank you :) (PS: can i install another desktop on Kubuntu?)
[Eee Pad Transformer Android Development] :
(PPS: touch doesn't work as well... when i touch, sometimes the touches are recognized as cursor move and not as mouse click.... touchpad doesn't work after a while -no problem :P-) how can i enable onscreen keyboard on login?
[Eee Pad Transformer Android Development] maksvlad:
I solved the issue. The cause was in conky activity. I killed conky and keyboard with touchpad didn't stop anymore.

I disabled autostart conky in ~/.config/lxsession/Lubuntu/autostrart.

But I have another question. The keyboard and touchpad stop work on boot and after loggin on till redock. Is this behavior "normal" or not?
[Eee Pad Transformer Android Development] ryanh1222:
I am having a hell of a time getting my wifi to work also. All the wifi networks are visable but I can't autenticate I have tried connecting a 100 different ways via comand promp.

When I try to connect to a network with a wap2 it give me error (7) saying that I didn't provide privelaged information when I did in fact use the correct network key

When trying to connect to an unsecure network it just times out and says network disconnected.

I am running

tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

I have tried different rootbind kernels to no avail.

Whats my problem?
[Eee Pad Transformer Android Development] maksvlad:
I've connected to wifi with nmcli

There are my steps to get wifi connection

in terminal. "w-net" - AP-name

1. sudo nmcli d wifi connect w-net #it creats w-net config in /etc/NetworkManager/system-connections/

folder

2. edit w-net config

in section [802-11-wireless-security]

[802-11-wireless-security]
key-mgmt=wpa-psk
psk=<YourPASS>

Nothing else should be there

3 sudo nmcli c up id w-net #connect to AP

There is system-wide connection. NM will connect one on boot (if AP is in range)

I use kubuntu. After connection I've installed network-manager-gnome and set up nm-applet as default nm-gui instead plasma-nm

---------- Post added at 04:56 PM ---------- Previous post was at 04:42 PM ----------

Use lightdm-gtk-greeter

to set DM use dpkg-reconfigure lightdm

edit /etc/lighdm/lightdm*conf

[greeter]
background=/usr/share/backgrounds/warty-final-ubuntu.png
theme-name=oxygen-gtk
icon-theme-name=LoginIcons
font-name=Ubuntu 11
xft-antialias=true
xft-dpi=96
xft-hintstyle=slight
xft-rgba=rgb
indicators=~a11y;~language;~session;~power #'~a11y' indicator adds accessibility icon to lightdm on boot
keyboard=onboard #set what keyboard use
[Eee Pad Transformer Android Development] DjDill:
Docking can have issues if the battery is low.. I still post without the dock connected and then only connect after I get to a locking screen.

Strange little bugs.. But they keyboard after login works fine for me.. Low battery makes it go crazy
[Eee Pad Transformer Android Development] maksvlad:
In my case I haven't noticed that dock stopped work after dock's or main batteries was discharged.

Now my dock battery is 3% (full discharged), but I can use dock without any issues.

Perhaps the bugs (in your and my case) are the same, but I can't realise what events lead to.

Under your tf101-lubuntu-14.04 image I solved stopped dock bug (SDB) when disabled conky as I wrote above. Now I use kubuntu img by [MENTION=3753391]jrohwer[/MENTION]. There I've solved SDB with disabling sound notification (noteced SDB after sound events) and all battery notifications. In my expirience SDB appears in same time when some battery event occurs.

May be notification system is the cause of SDB, but I haven't got result in logs (perhaps I read wrong logs) and xinput research.

It's little SDB but annoying as big
[Eee Pad Transformer Android Development] maksvlad:
News of SDB reseaching.

Yesterday I installed xfce on ubuntu-mini.

While I worked with console (no anyone notification events there) the dock worked fine without any stop about 3 or 4 hours.

After booting and logging in xubuntu session I got a SDB with battery notification.

Full disabling sound event and battery notification solve SDB.

But I haven't test xfce on SDB with other events like pidgin notifies.

I hope SDB is linked only battery events not all notification events...
[Eee Pad Transformer Android Development] The-Undertaker:
Kubuntu 14.04 With Tegra drivers by @jrohwer TF101g

Sorry, i'm not english, and i'm having lots of problems to understand how to proceed.

I wish to get detailed instructions with how-to install Kubuntu 14.04 With Tegra drivers by [MENTION=3753391]jrohwer[/MENTION] into my TF101g.

The Kubuntu section hasn't many details as like for the other linux images of this tread.

Forgive me for my hard request, but my head is going to explode after reading hundreds of posts. thank you very much in advance, have a good day!
[Eee Pad Transformer Android Development] Kingzak34:
Man there is an how to linked in the first post...

Tapatalké depuis mon OnePlus One MIUI !
[Eee Pad Transformer Android Development] The-Undertaker:
do you mean this one?

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

is the one for all images?
[Eee Pad Transformer Android Development] jrohwer:
Specifically if you are interested in the kubuntu image there are also instructions on my rootbind thread:

http://xdaforums.com/showpost.php?p=43177569&postcount=1

(Installation instructions step #2, you can skip #3 as you don't have to mount the image (it is a tarball that you can extract directly).

http://xdaforums.com/showpost.php?p=52697775&postcount=303
[Eee Pad Transformer Android Development] The-Undertaker:
well, what i have to do is to download the New Ubuntu 14.04 image for rootbind with graphics acceleration and following instructions from http://xdaforums.com/showpost.php?p=43177569&postcount=1&nocache=1&z=7646474256180227 skipping the 3rd point?
[Eee Pad Transformer Android Development] maksvlad:
Download the kubuntu img.

Follow step #2 of instruction http://xdaforums.com/showpost.php?p=43177569&postcount=1. The section begins with words "NEW! For a fully working Kubuntu 14.04 image"

As an adwise, use 3.1.10-15 modules. HowTo install modules Instruction is in step #4 of the fist post. Be Lucky, Don't Worry.

But Kubuntu img has some bugs with panel applets (Expl: I can't add any new applet to panel or manage Network Manager with plasma applet). In this reason I switched on xubuntu (IMO Xubuntu more polish and usable then Lubuntu)

If you want use NetworkManager in Kubuntu then remove plasma-nm and install network-manager-gnome. Set nm-applet autostart on login in
[Eee Pad Transformer Android Development] The-Undertaker:
it takes a life while expanding the image, could i expaind it into linux and after copy it into the TF101g? how to?

---------- Post added at 01:44 PM ---------- Previous post was at 01:31 PM ----------

u0_a35@android:/ $ su
root@android:/ # mkdir -p /data/linuxroot
root@android:/ # busybox chmod 755 /data/linuxroot
root@android:/ # cd /data/linuxroot
root@android:/data/linuxroot # tar -xpjf /storage/sdcard0/kubuntu-14.041.tar.bz2

anythings happens, but the device seems working because it gets very very slow in everythings
[Eee Pad Transformer Android Development] szigeza:
Hi! I have problem. I have made a new utopic image with debootstrap, but unfortunately when I extract to linuxroot folder and start, it is read only filesystem. What can I do? Somebody knows the solution?
[Eee Pad Transformer Android Development] Kingzak34:
Add the v argument, it's for verbose, so it shows you what is being extracted. ( -xvpjf )

There was a discussion about it some times ago, try to search in the threads related to Linux on the TF
[Eee Pad Transformer Android Development] maksvlad:
I never tried to copy img from linux. I coped archive on microsd and extracted one on root. It taked about 20 or 30 min. I think copying from linux takes similar time becouse there are too many files.
[Eee Pad Transformer Android Development] The-Undertaker:
tyvm for the verbose option, now i can see the scrolling rows of expandig image. once finished, i'll install modules, than reboot and flash the kernel Tim_KatKernel_107_JB4.2_Lidpatch.zip ?
[Eee Pad Transformer Android Development] Kingzak34:
No, once you placed modules flash jhrower kernel to boot Linux, and to go back to android, flash the one corresponding to your rom ( katkernel 4.2 for katkiss 4.2 )
[Eee Pad Transformer Android Development] The-Undertaker:
wich one is the [MENTION=3753391]jrohwer[/MENTION] kernel pls? sorry but i'm confused very much
[Eee Pad Transformer Android Development] Kingzak34:
You're on the image thread, kernel is on the jhrower kernel thread.

How to proceed are linked in the first post, I think you must read it. You should not do anything when you dont know what you're doing.
[Eee Pad Transformer Android Development] The-Undertaker:
i'm only confused after reading hundreds of post, i've been flashing my devices since years, i need help because my head is going to explode after reading a lot, english is not my native language. can someone send a link for the right Jorhower kernel pls? tyvm