yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Kingzak34:
Ho yeah I see, that was the problem when I tried it last time.

I think it comes from the video driver. I cant really tell why but I got a similar problem with my PC. I have sometimes click missing on some object ( It select it instead of click like it can do with touchscreen on our TF ) and if I install video driver it's even worse and unusable. It's maybe not really the video driver itself, but it's linked with I think.

---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------

I asked this cause someone asked to do that lol.

But yeah of course, a dedicated partition is definitively better choice.

And having a backup system on sdcard, is a brilliant idea !

Thanks a lot for those informations ;)

---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------

Updated my guide in order to have more than one linux system or change base location for it.

http://xdaforums.com/showthread.php?p=51163180

As usual, any suggestion is more than Welcome ;)
[Eee Pad Transformer Android Development] :
another method to get it working? http://xdaforums.com/attachment.php?attachmentid=2737523&stc=1&d=1399801979 here, this task manager (or if it is a task manager integrated in the desktop) what is the name of it? (PS: sorry for there names but i'm noob about ubuntu XD)

---------- Post added at 05:30 PM ---------- Previous post was at 04:57 PM ----------

there are too much problems :/ the desktop home doesn't work well, the cursor is laggy and loading animation is broken... the keyboard has problem with touchpad (with a delay), touchscreen works only as a touch-friendly cursor (double click doesn't work as one-click; is it an ubuntu problem?) and without keyboard the os doesn't start :(( nice but with problems... is ther another ubuntu version stable or more working? :P if you need test, i have an empty tablet, i don't use it a lot XD
[Eee Pad Transformer Android Development] jrohwer:
Download links to my Ubuntu 14.04 image from post 303 removed for the time being. There seems to be a problem in that it does not boot up. Need to debug this first and will post here again if it is working.
[Eee Pad Transformer Android Development] jrohwer:
Download links are back up. I tested the image and it is ok. If you have problems booting, see the discussion at the end of this thread: http://xdaforums.com/showthread.php?t=2648862
[Eee Pad Transformer Android Development] :
why this ubuntu rom doesn't work with .12 OC kernel?
[Eee Pad Transformer Android Development] Kingzak34:
Read the end of discussion on the other thread as suggested.

At least 3 last pages

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] DjDill:
[MENTION=3753391]jrohwer[/MENTION]

Got side tracked on building the lubuntu IMG.. But been banging my head on the sound problems

I want to trouble shoot it with a USB audio stick. Problem! Kernel does not support USB audio... No problem.. I will build the modules, build them and modprobe them in.. But no love.. I can't them them to load version magic matches and everything.. I was able to get the dm9061 loaded the same wayaybe audio is more kernel dependent

I went as far as building a whole new kernel off sni's .config with your source.. Added in the rootbind in the image.cfg but the bloody thing kernel panic ed !! Can't win!

Next I will try to build without changing the modules and keep it clean to see if it will post.. I am working off the tf101 wiki on xda for Ubuntu kernel building ..

Oh the pain in my head, lucky I like a challenge!

Oh! On a side note: I tested more hardware over USB.. The Logitech C110 works like a charm! So if anyone wants video go pickup one of those, cheap as chips and work! - maybe one day we will get the onboard cam working
[Eee Pad Transformer Android Development] jrohwer:
What toolchain / cross compiler are you using?
[Eee Pad Transformer Android Development] DjDill:
Compiling natively ;)

---------- Post added at 07:50 AM ---------- Previous post was at 07:00 AM ----------

I plugged it in and restarted this morning ... Alsamixer now shows the device! But it fails to play.. But I am a little closer :)
[Eee Pad Transformer Android Development] jrohwer:
Did you change the kernel source or only the config? If you only changed the config you could post it here and then I could try to compile it on my side as well....
[Eee Pad Transformer Android Development] DjDill:
OK well good news.. I have not fixed the sound issue yet! But now we can play back DVD's on the TF101 (see attached)

USB DVD SUPPORT

One of my goals was to get DVD and CD play back and writting

If you plug in a USB dvd / cd then you can use it.. Only for rootbind kernel 10.12 OC

See attached :) I will add things like this to the builds too! :)

DVD playback is not good.. Laggy .. VOB transcoding is the problem..

If you want to give it a crack you will have to get the DVD decoding libs too:

sudo apt-get install libdvdread4

then install the deb attached dpkg -i .. its the other dvd coding lib that is required.. then you will be able to open using mplayer / gnome-mplayer.. VLC was crashing for me.. smplayer worked really well still laggy but would play

So what else I tested.. Opening files and burning:

Xfburn worked fine ::

Things that you need to do if you want to burn / play back dvd etc

(each time the dvd player is plugged in)

sudo chmod 777 /dev/dvd

sudo chmod 777 /dev/sg0

I use a Samsung usb dvd rw player.. works fine was about $20 AUD

DEB was from here: http://www.deb-multimedia.org/dists/testing/main/binary-armhf/package/libdvdcss2

Used parts of this guide to get the support working after lots of head banging :

http://www.thriveforums.org/forum/t...implemented-kernel-functionality-modules.html
[Eee Pad Transformer Android Development] DjDill:
Full of good news tonight :)

OK I got a working USB audio module see attached .. Not really applicable unless you have a USB audio key stick etc..

I am going to use this to debug sound issues with the kernel / images

:)

Might be hard to see but thats ALSAmixer with the key

I packed everything from the /kernel/sound folder.. But I think we only need kernel/sound/usb - and maybe core.. can't be sure.. until i rebuild

win! - two goals smashed in one night :)

Oh i am using a creative sb1140 that I bought just for this debugging.. :P
[Eee Pad Transformer Android Development] Kingzak34:
What some amazing news and some amazing devs. Thanks for all your doing and for all you've already done djdill and jrohwer of course.

Just amazing.

Tapatalké depuis mon Nexus 4 MIUI !

---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------

If you are on clean build to debug things. What do you think about making a diff of 2 versions with bs diff for exemple and make a recovery zip that patch files may avoid reinstalling everything for a patch?

I've made a program on Windows to make my Nexus 4 rom OTA. It may be adaptable to this case.

What do you think about that?

I'll maybe try to adapt it when you'll release a new build to see how it goes.

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] DjDill:
I like the idea of zip flashing.. But what about pure OTA? having a script that checked for chages from GIT or something then just patches the required files.. IE like if we get audio working correctly just changes the audio config files to fix them.. ETC..

I think linux might be harder to patch via zip then Android?
[Eee Pad Transformer Android Development] DjDill:
OK Sound issues / troubleshooting update!:

My sound stops randomly and will not come back until a reboot.. I think I have told everyone about 100times :P

So if it stops I have been able to edit this file: leafpad .asoundrc

Change it to a non existing sound card

I change from this:

defaults.ctl.card 0
defaults.pcm.card 0
defaults.timer.card 0

TO THIS:

defaults.ctl.card 2
defaults.pcm.card 2
defaults.timer.card 2

Then try to open alsamixer.. it fails :)

Close and play with the audio program.. (in my case firefox)

It does not work. Fine!

Edit .asoundrc

Back to normal..

Open and close Audio App and it works again!!!!

I hope this helps someone.. Also i am going to look in to a way of hot keying this process.. until I can find a fix for the driver / alsa
[Eee Pad Transformer Android Development] Kingzak34:
Yes of course that was just an idea, if you have a better one, it's better :P

BTW, [MENTION=3753391]jrohwer[/MENTION], do you think, if emmc is formated in f2fs, linux will work, or it doesnt support it ? Without speaking of kernel support, because I think kernel must support it too ?

Envoyé de mon Transformer TF101 en utilisant Tapatalk
[Eee Pad Transformer Android Development] :
very nice, thanks :) but for someone who doesn't work? :P

Thanks for your work and also for jrohwer :D
[Eee Pad Transformer Android Development] zachf714:
Myself and [MENTION=4342873]sidneyk[/MENTION] have talked of f2fs in android before, it is just to easily corruptible to be used. I really don't know what all the rants and raves are about it, just stick to what works
[Eee Pad Transformer Android Development] DjDill:
OK my sound fix does not work with mplayer .. Only ff

Ehhhh this is getting strange ... I need to test more with my USB key to see.. Sorry for the wrong info
[Eee Pad Transformer Android Development] jrohwer:
New kernel OC 1.5 GHz

I have managed to compile a kernel overclocked to 1.5GHz with Sni's framebuffer and USB fixes, so "everything" works (except sound, which is buggy and we are working on).

Only snag: for me, it boots only about 30% of the time, the rest of the time it just gives a black screen. I have no idea what is causing this! But if it boots up, it flies and is very stable :) I have not had any issues with it in terms of crashes or something else.

I have also found that undocking during booting increases the chance of a successful boot, just re-dock once it's booted up.

So - enjoy (or not...) - and use at your own risk...

N.B. You'll need new modules as well, extract to /lib/modules in your root file system.

If you want to compile yourself, just check out the "oc1.5" branch from my github:

https://github.com/jmrohwer/TF101-GNU-kernel

MD5:

2225be642d5c473c49fcaf70ceae2897 Ubuntu-3.1.10-13-rootbind-oc1.5.zip
[Eee Pad Transformer Android Development] folderman:
Hi jrohwer,

You are so great!

For the black screen issue on reboot, I have also had such phenomenon, for my case, it usually have black screen after upgrading/reflash the kernel. But after rebooting for several times, it should be smooth.

Is it the same on your case?

PS. I would try to recompile the kernel tmr and let you know how it is going to be.

Rgds,

Kenneth
[Eee Pad Transformer Android Development] folderman:
Hi,

I tried to compile twice, one with defconf and the other using the config.gz from oc1.2, both of them compile sucessfully but cannot let me in to the login page.

Then I use your oc1.5 precompiled version, I tried reboot about ten times, once was success.
[Eee Pad Transformer Android Development] jrohwer:
Which root file system are you using?
[Eee Pad Transformer Android Development] folderman:
I am using net-install-v0.7.

Thanks!
[Eee Pad Transformer Android Development] dvhh:
inverted lid state ?

using the lubuntu 14.04 image

First thanks for building these images, so far I have little issues.

first one small inconvenience, I have a device with a japanese keyboard, setting it up was annoying,

it seems my lid state is inverted causing the lock to only occur only when the lid open and disabling the keyboard and touchpad when opening.

In the meantime I've change the /etc/UPower/UPower.conf file set IgnoreLid to true.

I also think that the broken part with sound is OSS when chmoding /dev/dsp to 000, I didn't encountered any of the usual sound errors, perhaps a valid path to explore.

apparently my data partition has error, causing linux to checking at every boot without being able to finish (usually blocking at 70%), no big deal, but I feel that my TF101 is dying.
[Eee Pad Transformer Android Development] folderman:
Hi dvhh,

I have the same problem before about the partition, I finally need to reflash the tf101 with Android (I reflash from android 4.2 to 4.4) in order to solve the partition problem (http://xdaforums.com/showthread.php?t=2592890). But I am not so sure whether can solve yours.

Before throwing away your tf101, worth trying that.

Rgds,

Kenneth
[Eee Pad Transformer Android Development] dvhh:
Hi Thanks for the tip, that was already my solution when it happened to me the first time, this time I tried with adb to recovery (TWRP in this case) and ran e2fsck from here, looked ok from here
[Eee Pad Transformer Android Development] jrohwer:
New kernel OC 1.5 GHz - STABLE!

I have managed to compile a stable kernel overclocked to 1.5GHz, which boots every time!

Thanks to [MENTION=5376406]MiniBlu[/MENTION] for pointing me in the right direction. The kernel boots up at max frequency and performance cpu profile and the cpu scaling settings only kick in later during boot. This has caused the instability. The workaround has been to add a "dummy" 1.6GHz frequency which is actually scaled to 1.0GHz and thus stable and boots every time.

N.B. You'll need new modules as well, extract to /lib/modules in your root file system.

The only thing you will have to do is to set your maximum cpu frequency manually to 1504 MHz (or lower) using cpufrequtils. As the "maximum" setting of 1.6 GHz is actually not overclocked and won't give you increased performance :)

Once it's booted up I have never had instabilities with 1.5 GHz.

Downloads from post #3. The correct kernel is 3.1.10-15.

If you want to compile your own, changes have been merged into my github:

https://github.com/jmrohwer/TF101-GNU-kernel
[Eee Pad Transformer Android Development] Kingzak34:
Simply AMAZING .

Once again, thanks a lot for your great work !
[Eee Pad Transformer Android Development] :
And I can't try it :(
[Eee Pad Transformer Android Development] folderman:
Oh, what a great news, thanks for the contribution.

I am downloading...
[Eee Pad Transformer Android Development] folderman:
Hi jrohwer,

I have compiled the kernel from source and limit the max cpu freq to 1504000 by cpufreq-set command. The kernel can reboot without problem.

However, when I try to compile the kernel again and check the cpu performance, it is found that in the file /sys/device/system/cpu/cpu0/cpufreq/scaling_cur_freq, it shows 1600000. Is that normal?

Thanks!

Rgds,

Kenneth
[Eee Pad Transformer Android Development] jrohwer:
No it is not normal. Most probably you have not set the max cpu freq correctly. You have to set it every time, or edit it in the file /etc/default/cpufrequtils.

What does the following say (this checks the max freq it is set at):

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Alternatively you can do it by hand:

echo 1504000 | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1504000 | sudo tee /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

but cpufrequtils should set it ok (works on my machine):

sudo cpufreq-set -f 1504000
[Eee Pad Transformer Android Development] folderman:
For the cpufreq, I use the -u option. Let me try the -f, but using -f may not optimal for battery.

I tries the echo command approach, it still using 1.6G as Max. I know it is strange.

Let me try tmr again as the tf101 is not on my hand.

Kenneth
[Eee Pad Transformer Android Development] jrohwer:
Yes, my bad, the -u is the correct option. But you can always check what the max is set at and if it is correct using the cat... command I posted above.
[Eee Pad Transformer Android Development] folderman:
Hi jrohwer,

I have used your pre-compiled kernel and modules, I found a interesting phenomemon

Case 1:

1. set scaling_max_freq to 1504000

2. governor: ondemand

when under loading the scaling_cur_freq would be 1600000

Case 2:

1. set scaling_max_freq to 1504000

2. governor: performance

the cpu would stay at 1504000.

It seems that using ondemand governor would override the setting of scaling_max_freq.

PS. Your kernel is really more stable than before, I can reboot the tf101 almost with 100% success rate.

Rgds,

Kenneth
[Eee Pad Transformer Android Development] jrohwer:
I have not tried ondemand governor but am using interactive as it gives me better responsiveness. With interactive the max freq is set as it should be. I can't see why it would not work with ondemand though. Have you tried setting things in /etc/default/cpufrequtils and rebooting? That's how I set it then I don't have to worry about it again after reboot.
[Eee Pad Transformer Android Development] :
[MENTION=3753391]jrohwer[/MENTION] maybe i can't extract because the tar.gz is too big or it isn't an img file... how can i convert it as img, or how can i reduce size of this tar.gz?
[Eee Pad Transformer Android Development] Kingzak34:
I dont think, everyone can extract it.
[Eee Pad Transformer Android Development] :
i formatted my tablet a repartitioned it with nvflash... i did another time the process, but nothing... maybe is the rom? I have a ARHD 3.6... anyway, i'll put extracting all the night and i'll say you what appens XD
[Eee Pad Transformer Android Development] Kingzak34:
Did you tried from recovery with adb ?
[Eee Pad Transformer Android Development] :
now i know why: it has a problem with /sdcard partition (mmcblk0p7 is the partition for /data and /sdcard) in fact when i mount /sdcard terminal says that it doesn't find it

~ # mkdir -p /data/linuxroot

mkdir -p /data/linuxroot

~ # busybox chmod 755 /data/linuxroot

busybox chmod 755 /data/linuxroot

~ # cd /data/linuxroot

cd /data/linuxroot

/data/linuxroot # tar -xpzvf /sdcard/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

tar -xpzvf /sdcard/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

tar: can't open '/sdcard/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz': No such file o

r directory

/data/linuxroot # tar -xpzvf /data/media/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

tar -xpzvf /data/media/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz

tar: can't open '/data/media/tf101-14.04-Lubuntu-Tegra-armaf.tar.gz': No such file or directory

/data/linuxroot # mount /sdcard

mount /sdcard

mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory

on recovery, when i mount sdcard it says Error mounting.... how can i solve this problem?
[Eee Pad Transformer Android Development] jrohwer:
What recovery are you using? best to use TWRP. When TWRP boots up it already has "/sdcard" and "/data" mounted. Both are actually /dev/block/mmcblk0p7. If you want to mount the MicroSD, then it is /sdcard1 in recent versions of TWRP, can't remember the older ones. In any case it is "external storage".
[Eee Pad Transformer Android Development] Kingzak34:
If i'm not wrong, last TWRP versions are not compatible with 4.0 ROM, only 4.1 +
[Eee Pad Transformer Android Development] jrohwer:
Not sure, but TRWP 2.3.2.3 for sure works with 4.0 (I used it when I was still running stock rooted). So then that may be the best bet.
[Eee Pad Transformer Android Development] sidneyk:
Latest twrp versions from me, for a while now, consider internal sdcard to be /data/media/0 and use a mount point of /sdcard. I've used recent versions to flash from stock rooted to newer 4.1+ roms. I dont remember if 4.0 roms were using /data/media/0 yet or not. That's really the main difference, /system is the same, /data mount point still points at correct data partition which contains /sdcard. More likely an issue with an older update binary or updater script from the rom.
[Eee Pad Transformer Android Development] :
EDIT again XD: i found commands... -p in tar command doesn't work on terminal by adb
[Eee Pad Transformer Android Development] jrohwer:
Multi user support in Android was only introduced in Android 4.2. This goes hand in hand with /data/media/0, /data/media/1, etc. Prior to that, i.e. Android 4.1 and earlier (and by implication in the stock 4.0) /sdcard was just mounted as /data/media. Some versions of TWRP were able to distinguish this automatically and mount /sdcard to /data/media for Android <=4.1 and to /data/media/0 for Android >=4.2. I am not sure about the latest TWRP though as i have never used it with a 4.0 or 4.1 ROM.
[Eee Pad Transformer Android Development] sidneyk:
Same here, haven't tried to flash an older rom from later twrp versions, only flashed to newer rom from older rom. I know some older twrp versions were pointing the sdcard mount point at /data/media. I'd have to look, but I think there have been merges in twrp code to better deal with some aspect of the /data/media situation. I do know that for awhile some older and even newer flash packages on newer twrp versions were having trouble with some assert commands or something even when flashing on correct device. I think there have been recent merges to give better backwards compatibility in this regard, but my recent twrp versions should be enforcing correct device id before allowing flash, if the checks are in the updater script.
[Eee Pad Transformer Android Development] thelangosta:
I just flashed a 4.0 ROM last night on you latest TWRP. Everything went fine.
[Eee Pad Transformer Android Development] sidneyk:
Good to hear. Did you try to flash it a second time and see if it gave you any /data/media/0 folders? If not, then it sounds like the backwards compatibilty must be working right.
[Eee Pad Transformer Android Development] thelangosta:
I did not try doing it a second time though I could if you need.
[Eee Pad Transformer Android Development] sidneyk:
Up to you, just curious. That's when folks were seeing the issue before, after multiple rom installs.
[Eee Pad Transformer Android Development] thelangosta:
Right I remember that issue. You would end up with 0/0/0/0/0/0. Wiping internal data took care of that but was not convenient for everyone.
[Eee Pad Transformer Android Development] folderman:
Hi jrohwer,

Finally tested to use interactive governor, still Max at 1.6G, even the scaling_max_frequency has been modified to 1502000.

Let me try more ways to find out why!

Kenneth
[Eee Pad Transformer Android Development] montolla:
Hello

That was a generic question non related to specific device.

How can I get access to android mmcblk0 from native linux running?

I need to install linux on internal eMMC device but From linux,

Thanks
[Eee Pad Transformer Android Development] jrohwer:
Under linux it is /dev/mmcblk0

From within android it is /dev/block/mmcblk0
[Eee Pad Transformer Android Development] montolla:
Hello

Hm, maybe I didnt ask well.

In android the mmcblk0 device is encrypted or someing like that so you can access to it partition layout (partition table) and for example, mount the partition with boot and "flash" a new one there. dd if=newboot.img of=/dev/mmcblk0p22

The partition are there but you can just "mount /dev/mmcblk0p22 /mnt/boot".

I think the android partition layout is somethink like GPT yask2.

MayBe this can help us http://processors.wiki.ti.com/index.php/Android_gingerbread_eMMC_booting

Thanks
[Eee Pad Transformer Android Development] jrohwer:
What device are you talking about? The TF101 does not have 22 partitons on its mmcblk0. On the TF101 the kernel and recovery partitions are "hidden" so you can't flash to them directly. The kernel or recovery image has to be packed into a special binary format (blob) and flashed to the "staging" partition (mmcblk0p4) with dd or with recovery scripts. On the next boot the bootloader will then flash the image to the correct partition from the staging partition. If you don't know about this then read up first as it is quite dangerous to mess with this, especially if you have a TF101G (where no NVFLASH is available) so you can't rescue your system if you mess it up. On the TF101 you can use wheelie/nvflash to flash to all partitions directly in APX mode.