Database Info

Linux on tf101

Hey guys!
I followed the process of using ubuntu on a tf101 now for 1 year and thaught thst i will flash it once it is more stable.
Well i kind of searched but i can't find any comments on how good/bad it runs on our tf101.
So i wanted to know how well ubuntu runs on our tablets.
Is it smooth?
Is it useable?
And do you think it is better than android?
I use it mostly for reading pdf's and browsing with little bit of watching live streams or youtube videos. Do you think ubuntu would be better for me?
I used it ubuntu quite a long time for everything but gaming on my desktop so i have enough experience for it.
However if it won't run well on the tf101 i will not flash it and stick with android
Regards
Sent from my Nexus 4 using xda app-developers app

hi!
actually i've the same "problem"...
i've read a lot in the threads about how to install and how to fix some bugs (wifi, bluetooth and so on)
there are also some problems with the dock. (depending on which kernel you're using)
but i hardly find a answer how the usability is... there are some youtubevideos but they main information of them is "it's bootable and i can open browser and office"
it would be really nice if somebody could share his experience with ubuntu, tubuntu or arch on the transformer.
i've just ordered the keyboarddock and once i've got it i'll try it on my own and make a real review of linux on the tf101.
but if somebody of you says:
-> the batterydrain is horrible
-> the browser is much slower than in android
-> there too much bugs and crashes
i'll wait till a better version of ubuntu touch probably.
kind regards

I'm dual booting ubuntu and android on my tab.
The reason i can't let android go, is the lack of hardware accelaration and flash on the ubuntu. Other than that it feels amazing!
Super fast and pretty stable. I even do some programming and compiling on it without problems.
So, if you would only browse the web, and read PDFs, i would recommend it. But as you mentioned Youtube and other streaming services, i'd say android.
Only way to find out is dual booting, then you'll have a taste of having a full desktop experience on your hands

thx!
no hardware acceleration is really a pity but i'll guess it's just a matter of time til it also works.
is it possible to make it run without the keyboarddock or should i wait til it's here?
edit:
which version do you prefer?
at the moment i guess the tubuntu verion is the most relieable?
http://forum.xda-developers.com/showthread.php?t=1995157

Mooks said:
thx!
no hardware acceleration is really a pity but i'll guess it's just a matter of time til it also works.
is it possible to make it run without the keyboarddock or should i wait til it's here?
edit:
which version do you prefer?
at the moment i guess the tubuntu verion is the most relieable?
http://forum.xda-developers.com/showthread.php?t=1995157
Click to expand...
Click to collapse
You can install a touchscreen keyboard in all of them.
The first one i used was Tubuntu, but i had no experience with linux. After feeling a little more confident i've flashed the Raring image just for fun
You'll enjoy it

it worked!
i've accidentally installed the old lubuntuversion v1.1rc1 but it still worked very well! :victory:
however i had the bug with the blank browser, thats why i've tried raring but i've noticed that for raring the hardwarekeyboard is a musthave for installation
now i'll try v1.2 and i'm very positive that its working great!

Mooks said:
it worked!
i've accidentally installed the old lubuntuversion v1.1rc1 but it still worked very well! :victory:
however i had the bug with the blank browser, thats why i've tried raring but i've noticed that for raring the hardwarekeyboard is a musthave for installation
now i'll try v1.2 and i'm very positive that its working great!
Click to expand...
Click to collapse
It's confusing at first, so many threads and information spreaded all over.
Lubuntu 1.2 and chromium kernel is the best combination for starting

ok i've managed to install lubuntu v1.2 (i guess the standardkernel is chromium) but now the wifi is broken

Mooks said:
ok i've managed to install lubuntu v1.2 (i guess the standardkernel is chromium) but now the wifi is broken
Click to expand...
Click to collapse
Download the latest kernel from the same place you downloaded lubuntu (x3's dev.h If I remember correctly). Rename it to Linux.IMG and put it on the images folder of tubuntu app. Flash chromium kernel again from the app .
I'm on mobile now, but as soon I get back to my tablet or PC I'll give you better instructions.
Sent from my GT-N7000 using XDA Premium HD app

thx! but there's no need to hurry
i gueass it's a little bit mor complicated because i've a sbk1-version.
i've downloaded now the 2.6.36 - [cpu 1.4 ghz] [gpu 300mhz] kernel from here http://forum.xda-developers.com/showthread.php?t=1995157 renamed it as you told and flash it by reflashing the whole sys.
the other way for sbk1 for flashing only the kernel is much more complicated...
edit: with the 1.4 ghz kernel the wifi worked but after one minute i've got a freeze. i thought it's maybe because of the oc so i've tried it again with the 1.2ghz (stock) kernel -> also freeze after some seconds...

Mooks said:
thx! but there's no need to hurry
i gueass it's a little bit mor complicated because i've a sbk1-version.
i've downloaded now the 2.6.36 - [cpu 1.4 ghz] [gpu 300mhz] kernel from here http://forum.xda-developers.com/showthread.php?t=1995157 renamed it as you told and flash it by reflashing the whole sys.
the other way for sbk1 for flashing only the kernel is much more complicated...
edit: with the 1.4 ghz kernel the wifi worked but after one minute i've got a freeze. i thought it's maybe because of the oc so i've tried it again with the 1.2ghz (stock) kernel -> also freeze after some seconds...
Click to expand...
Click to collapse
Can't you update the kernel using the tubuntu tool? I think it's the same procedure no matter the sbk version.
Sent from my GT-N7000 using XDA Premium HD app

i looked it up in the how-to from tomcom http://forum.xda-developers.com/showpost.php?p=35895490&postcount=2
i'll try it, but as far as i know, changing the kernel.img into linux.img and reflashing the whole thing should do the same...
the strange thing ist that the only working version was the old build (exept chromium browser bug), the newest tubuntu version has no wifi and with the newest kernel it has random bugs. (freezing at boot, freeze after login, booting into "tf101 login:")
those errors are even with the same version after just rebooting my tablet
edit: ok i've reloaded everything and used the 1.4ghz kernel. the first time wifi wasn't working and it froze but after a reboot wifi worked finally! but it's really slow an unstable

ok, finally i've got my dock.
i've reflashed again 1.2 with 1.2ghz kernel. wifi working, but chromium is really unuseable... sometimes it's loading the page but most of the time it crashes the whole program or there's an errormessage "ups something went wrong"
i'm not shure if lubuntu is unstable only on my tf101 or if i've done something wrong. i fear it's my tablet because i've done everything exactly like in the tutorial.
is it worth to try raring? now i've the dock so i can install it, or is it more unstable than lubuntu?
edit: i've manage to reflash from prime to eos4 and back to working dualboot. suddenly the lubuntu was working better and was more stable. even chromium was much faster than any browser in adnroid. after that i wanted to install th ubuntu softwarecenter, but afer 5min the whole tablet froze... after rebooting i everything worked fine. to i whanted to boot again into linux and now it suddenly can't even boot
is there a way to just reflash only the linuxpart? i don't want to reset android again...

Mooks said:
ok, finally i've got my dock.
i've reflashed again 1.2 with 1.2ghz kernel. wifi working, but chromium is really unuseable... sometimes it's loading the page but most of the time it crashes the whole program or there's an errormessage "ups something went wrong"
i'm not shure if lubuntu is unstable only on my tf101 or if i've done something wrong. i fear it's my tablet because i've done everything exactly like in the tutorial.
is it worth to try raring? now i've the dock so i can install it, or is it more unstable than lubuntu?
edit: i've manage to reflash from prime to eos4 and back to working dualboot. suddenly the lubuntu was working better and was more stable. even chromium was much faster than any browser in adnroid. after that i wanted to install th ubuntu softwarecenter, but afer 5min the whole tablet froze... after rebooting i everything worked fine. to i whanted to boot again into linux and now it suddenly can't even boot
is there a way to just reflash only the linuxpart? i don't want to reset android again...
Click to expand...
Click to collapse
If you wish to only reinstall Ubuntu, put a copy of bootloader.bin and transformer.bct in the \bins directory of your Tubuntu application folder. They are located in the \images directory.
Now copy ubuntu.img (it doesn't matter which image you use for example lubuntu or the others available) to the \bins directory.
Connect your cable and boot the tablet into APX mode. You can have the Tubuntu app open to see "green" letters that say you are connected just to make sure.
Now open a command prompt and make sure it is set for the \bins directory.
Copy each line and hit enter (wait for the command prompt to show it's done each time)
wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
nvflash -r --download 16 ubuntu.img
nvflash -r --go
After the last command there the tablet should reboot and most likely to Android if Android is your primary OS that is loading. Once in Android, shutdown and boot back up with volume down and power, then volume up like normal.
The new image is installed without disturbing the Android partition. There is a function called flash rootfs on the Tubuntu app to do this automatically but X3 is aware it isn't working and will fix it when he gets a chance.

thx! i#ve now installed raring and tried to install gnome-core and (after error an reflashing) lubuntu-desktop.
however i get now a error when installing the gui.
unpacking libpython3.3-stdlib:armhf (from .../libpython3.3-stdlib_3.3.0-12ubuntu3_armhf.deb) ...
dpkg-deb: error subprocess paste was killed by signal (broken pipe)
E: sub-process /usr/bin/dpkg recieved a segmentation fault.

Mooks said:
thx! i#ve now installed raring and tried to install gnome-core and (after error an reflashing) lubuntu-desktop.
however i get now a error when installing the gui.
unpacking libpython3.3-stdlib:armhf (from .../libpython3.3-stdlib_3.3.0-12ubuntu3_armhf.deb) ...
dpkg-deb: error subprocess paste was killed by signal (broken pipe)
E: sub-process /usr/bin/dpkg recieved a segmentation fault.
Click to expand...
Click to collapse
Hmm...did you uncomment universe entries in the aptsources? Can't remember the name of the file but if you install gnome core without editing the sources file it may not get the packages it needs. Rerun through my raring gnome core guide.

jep i've followed your guide.
http://forum.xda-developers.com/showthread.php?p=37803357
i'll try it again. could it be that my cpu or the ram is producing errors?

Mooks said:
jep i've followed your guide.
http://forum.xda-developers.com/showthread.php?p=37803357
i'll try it again. could it be that my cpu or the ram is producing errors?
Click to expand...
Click to collapse
You could try this:
http://dtbaker.com.au/random-bits/dpkg-received-a-segmentation-fault.html

mhm... it's getting stranger and stranger...
i've redone everything and while gnome-core installation i get a lot of:
[random numbers] BUG: scheduling while atomic: swapper/0/0xffff random codes...
i've tried dpkg --clear-avail but apt-get update makes also an error suddenly:
dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct problem.
after that it's still not working.
yesterday i was able to get nearly through the installation with repeating sudo dpkg --configure -a several times, but after 30min my transformer froze...

Is it possibel to use 3g on Ubuntu? Got the 101G.

[Kernel][ROM][Ovation][CM 10.1.3][emmc] "Yellow kernel"

I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
It's packaged as a complete rom to avoid kernel module difficulties. The rom is completely stock minus the boot animation, kernel and kernel modules. Thanks to everyone who has made this possible.
Both the kernel and PVR module have been compiled with linaro.
The kernel has numerous performance and stability enhancements over any other kernel to date.

Great Work. Thank you very much!

Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<

wahidx said:
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
Click to expand...
Click to collapse
I appreciate the last_kmsg. I apologize for using everyone as beta testers, but this demonstrates why it is a good idea- because I have been running OC5 for a few days without a single hiccup at all. I am actually surprised OC4 did so well for you. OC4 was also the first version to sport a new pvr module.
One thing I had been noticing before being able to compile my own pvr was that I could have one kernel play well with the stock pvr, and I could have a kernel right after that not play well with the pvr at all. This was my major motivation to be able to compile my own pvr so that it could match kernel space every time.
Ok, with that said, I compiled the pvr against OC4, and didn't bother updating it against any subsequent kernels. I probably should have known better, but it was working well enough for me.
Your error looks suspiciously like a missmatch between the pvr and kernel space. So if you want to try this update:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
and let me know if it works any better. I made sure to compile the pvr to specifically match the kernel.
Also, when I compiled the pvr before, I used PLATFORM_VERSION=4.1. I used this as an excuse to try
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.2.2
I don't know if it makes a difference or not.
Another thing I noticed you have slightly different hardware than I do. You have elpida ram versus samsung which is what I have.
I modified samsung ram timings to be slightly faster, but the other ram types were left at stock speeds. I may eventually try to clock the elpida ram the same as I have done with samsung, that may or may not make a difference. This may affect pvr performance as well. (It seems your pvr was a little slow bringing up power a few times). Then again, it could be my pvr source (although it works flawless for me, it may be hardware differences- I dunno.

thx for fast replay man,
i will try this release and give you feedbacks.
i have the bad feeling that something is wrong with my hardware. can be the only explanation, why my device reboot so often with CM10.2, CM11 and your OC6 release :/
//EDIT
actually i had just 1 reboot after some hour OC6 using, i will try OC6 for the next 2-3 days, maybe it was just a bad accident. after that i will try your OC7
regards
//EDIT #2
OC6 Test
after 2 days more, just 2 freez-->reboots (check last_kmsg) but still better than CM 10.2 and 11 on my device

Jon Lee said:
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
<snip>
The kernel has numerous performance and stability enhancements over any other kernel to date.
Click to expand...
Click to collapse
Hi Jon:
Hey, since we're asking for the moon, and since you're making THE oc kernel, any chance you can implement f2fs? I've got a Gal Tab 2 and an xda developer over there has a page about what he's done to get f2fs to work. Mostly it seems to require a .101 kernel. And he was kind to update TWRP so it would support f2fs. (I think to keep it from automatically formatting in ext4.) And he even wrote some zips to format /data, /system and /cache to f2fs.
My Tab 2 doesn't benchmark any faster but it sure is faster with f2fs. I image the HD+ would be faster too.

I'm new to flashing the Nook HD+. I was previously using the SDcard booting option for CM 10.1, but I would really like to get Nook off of this completely. Where do I start? I downloaded the ROM, and I have a boot IMG from another ROM on an SD card that takes me to recovery. Where do I put this ROM and how do I overwrite the actual Nook ROM?

install fails using verygreens internal recovery. is there a trick to installing this?

So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?

SynGamer said:
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
Click to expand...
Click to collapse
Yes, that means you still have stock recovery installed. You need to go to my HD/HD+ CWM thread linked in my signature and download and install the 6036 CWM from item 5 there.
Edit: but you know if you upgrade to CM10.2 you lose this kernel, right?
Sent from my BN NookHD+ using XDA Premium HD app
---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------
smatticus said:
install fails using verygreens internal recovery. is there a trick to installing this?
Click to expand...
Click to collapse
It depends on which verygreen internal recovery you are using. You need to have version 6036 or older to flash it. You can get one per my previous post.
Sent from my BN NookHD+ using XDA Premium HD app

Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?

i6941 said:
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
Click to expand...
Click to collapse
Does this work for CM11?

andtron said:
Does this work for CM11?
Click to expand...
Click to collapse
I think the answer is no, when you flash cm11 the OC kernel will be overwrite. But I didn't try this.

As the thread title indicates, this kernel is only for 10.1.3.

it says there is a new update from the option -- about menu...should I?

Jon Lee said:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
Click to expand...
Click to collapse
I couldn't find a tabletUI patch to match the final cm10.1.3 stable so here's one for anyone else downgrading like me.

Here's another experimental kernel update.
http://www.mediafire.com/download/1lkesmn6si6hd1e/ovation-kernel-cm10.1.3_v5.zip
I'm using it on OC7 pvr without issue (?).
1) reduced elpida and hynix ram timings.
2) updated vivante gc320 gcx 2d composition drivers to gitorious.org/gcx staging/alexei-dev. These are significantly different from original. (FWIW Staging/master branch threw memory map bverror 2 logs, but otherwise worked fine).
3) reduced dsp carveout memory. Increased system memory.
If needed, here is just the plain kernel for OC7, should anyone wish to revert back to that for any reason. (So as to not have to flash the entire ROM).
http://www.mediafire.com/download/z4r59n8dasxgz93/ovation-kernel-cm10.1.3_v4.zip
Kernel source for OC7
http://www.mediafire.com/download/6rngvee6x471cc3/android_kernel_bn_omap-cm-10.1_v3.tar.gz

So oc7 has been very unstable for me. I started with a completely clean slate, but it's frequently rebooting and not waking up from sleep. I may remember having these same problems when I was regularly using cm10.1 last year.
I've gone back to cm10.2.1. You should consider developing your kernel for that one.

Ya'know, I make these for me first and foremost. They reflect what I'm working on, trying to fix or improve the performance of my device.
Each one is different, some have worked better than others, but I notice an overall improvement from the original kernel. It is substantially different than any other nook kernel out there and works the best for me.
Here's the last. I think it works well. Made some additional changes to mmc/sdio to try and improve stability with wl12xx.
Source (which includes the vivante driver change from before):
http://www.mediafire.com/download/v4ihnr46eo9ap4d/android_kernel_bn_omap-cm-10.1_v4.tar.gz
Flashable kernel
http://www.mediafire.com/download/c9bsziswrf7y0e4/ovation-kernel-cm10.1.3_v6.zip

I like 10.3.1 but it has two downsides. 1) No automatic TRIM. 2) Unsafe manual TRIM because of Samsung MAG2GA EMMC bug.
Is it possible to implement the workaround used for 10.2.1 and later? Then manual TRIM by using console "fstrim" should be safe.
http://wiki.cyanogenmod.org/w/EMMC_Bugs
I assume the source for the 10.2.1 kernel would have the ported patch.

linux-tegra-nv-3.4 Nvidia tegra3 kernel branch for grouper

Title says it all.
Basically, I'm gonna need help on this, I don't know how much, but I will need it. I'm pushing all my changes to my GitHub repo regularly, but so far I'm simply trying to get the grouper board files set up. Here's how I'm going about that:
cherry-pick Google's commits which added grouper support to 3.1.10 kernel
Fix conflicts
Compile
Inspect errors
Update grouper board files against kai board files commits from here (from the k3.3: kai: Updates to board files commit onwards
Recompile
etc.
Beyond this I'm not really too knowledgeable in al the device tree stuff. Sure, I've read up on alot of stuff, but have no practical experience. Therefore once I've got the board files how I think they should be, if things still don't work then I will need help. Luckily, it looks like the kai board and grouper are extremely similar. So with any luck it'll work without too much hassle.
Beyond this stuff will probably be broken anyway, so I will need help with that.
Feel free to discuss anything relevant, and to offer anything you think might be useful. There are some real devs here who would make a big impact on this, as there's only so much blind tinkering I can do.
Thanks

Here's an updated link https://github.com/enssorcel/Grouper-3.4
The first on doesn't seem to be working

USBhost said:
Here's an updated link https://github.com/enssorcel/Grouper-3.4
The first on doesn't seem to be working
Click to expand...
Click to collapse
Woops sorry, I linked to my testing branch so I had deleted it already. For whoever's following this, you want to go here to see what I've merged into the master branch i.e. what I've fixed, and click the branch pulldown and go here to see what we've been working on, the names are self-explanatory.
Thanks to @sgt. meow 's help we've made quite a bit of progress, we've fixed the errors for the majority of the grouper files so we're getting close to a successful compilation. Beyond that, who knows.
EDIT: Just fixed board-grouper-power.c. sensors will be the next focus, hopefully fixed soon.
EDIT1: All board files are fixed! (well, the compilation errors are gone, but we don't know if they work yet)

Well we've got a zImage built, but I don't think it boots. It'd be helpful if you lot could test to make sure though, just flash in recovery: http://d-h.st/7h3
I don't suppose anyone has a serial cable and access to UART or anything similar?

HTCDreamOn said:
Well we've got a zImage built, but I don't think it boots. It'd be helpful if you lot could test to make sure though, just flash in recovery: http://d-h.st/7h3
I don't suppose anyone has a serial cable and access to UART or anything similar?
Click to expand...
Click to collapse
have you used a grouper boot.img for repacking zImage?

HTCDreamOn said:
Well we've got a zImage built, but I don't think it boots. It'd be helpful if you lot could test to make sure though, just flash in recovery: http://d-h.st/7h3
I don't suppose anyone has a serial cable and access to UART or anything similar?
Click to expand...
Click to collapse
Yeah, it doesn't boot on my tilapia. But I'm glad you use agnostic-kernel

lupohirp said:
have you used a grouper boot.img for repacking zImage?
Click to expand...
Click to collapse
Of course I used the stock boot.img from 4.4.3 unpacked it with unmkbootimg, replaced the zImage, repacked with mkbootimg then replace the boot.img in the agnostic kernel with the new one.
frantisek.nesveda said:
Yeah, it doesn't boot on my tilapia. But I'm glad you use agnostic-kernel
Click to expand...
Click to collapse
I don't know if it would boot on tilapia anyway, I think they use the same board files so maybe. Yeah its especially awesome for stuff like this cause I don't need to worry about making a different version for everyone who wants to test it on different file systems :victory: that said it'd be great if someone can test this on ext4 to make sure.
So can anyone help? Even it you can just be a guinea pig with a serial cable

Will test now
Edit: stuck on Google screen
Edit: I am All-F2FS Carbon ROM

USBhost said:
Will test now
Edit: stuck on Google screen
Edit: I am All-F2FS Carbon ROM
Click to expand...
Click to collapse
This is either because we have more work to do to get it booting, or because the defconfig is being stupid, I remember I couldn't get franco kernel to boot unless I used cyanogenmod's defconfig although of course that's for 3.1.10 so that's not really an option.

HTCDreamOn said:
This is either because we have more work to do to get it booting, or because the defconfig is being stupid, I remember I couldn't get franco kernel to boot unless I used cyanogenmod's defconfig although of course that's for 3.1.10 so that's not really an option.
Click to expand...
Click to collapse
you can use 3.1 kernel config. BTW i saw your config and you don't have added F2FS drivers, so on F2FS roms will not boot. We must test on ext4 rom......otherwise seems a good base for start.

HTCDreamOn said:
It'd be helpful if you lot could test to make sure though, just flash in recovery: http://d-h.st/7h3
Click to expand...
Click to collapse
Hangs at Google logo
Grouper, SlimKat 4.4.4 build 5.2, (all ext4).

lupohirp said:
you can use 3.1 kernel config. BTW i saw your config and you don't have added F2FS drivers, so on F2FS roms will not boot. We must test on ext4 rom......otherwise seems a good base for start.
Click to expand...
Click to collapse
OK I'll try cyanogen's defconfig and see what happens. Will I have to regen for 3.4 or can I just use it straight off? I've added f2fs support in my f2fs-testing branch and enabled it now, thanks for the tip
Lar5 said:
Hangs at Google logo
Grouper, SlimKat 4.4.4 build 5.2, (all ext4).
Click to expand...
Click to collapse
Thanks, now we know it'd definitely not an fs problem :good:

Don't give up your doing great
Remember I'm here to help test and i may even reformat my nexus 7 back to
All-EXT4 to help test

USBhost said:
Don't give up your doing great
Remember I'm here to help test and i may even reformat my nexus 7 back to
All-EXT4 to help test
Click to expand...
Click to collapse
Don't worry, not giving up, just thinking. We Ideally need someone with a serial cable because we're kinda stuck without debuuging unless we can find someone who can spot the problems from the code.

HTCDreamOn said:
Don't worry, not giving up, just thinking. We Ideally need someone with a serial cable because we're kinda stuck without debuuging unless we can find someone who can spot the problems from the code.
Click to expand...
Click to collapse
where can one get such a cable

USBhost said:
where can one get such a cable
Click to expand...
Click to collapse
You need to make one, basically the N7 has a UART port in the headphone jack but you need to make an adapter: http://blog.accuvant.com/jduckandryan/building-a-nexus-4-uart-debug-cable/ it's widely assumed the process is the same for all Nexus devices but I haven't found anyone testing it with the N7 do there's no confirming it would work. Hopefully if it didn't then it'd must be a case of enabling stuff in the kernel (there may have been some commits disabling it for release). If you wanna help out then this would be invaluable though

HTCDreamOn said:
You need to make one, basically the N7 has a UART port in the headphone jack but you need to make an adapter: http://blog.accuvant.com/jduckandryan/building-a-nexus-4-uart-debug-cable/ it's widely assumed the process is the same for all Nexus devices but I haven't found anyone testing it with the N7 do there's no confirming it would work. Hopefully if it didn't then it'd must be a case of enabling stuff in the kernel (there may have been some commits disabling it for release). If you wanna help out then this would be invaluable though
Click to expand...
Click to collapse
interesting I'll see what I can do
Not making any promises
Edit: it shouldn't be too hard to make
Just need $17.17 to make it
Will see

I'm not sure you'll have much luck with the UART cable. An RD (now retired) got his device to recognise the UART board, but failed to receive any output.

As you all probably know, even after updating the board files against KAI from the nvidia source, we couldn't get it to boot. So we applied a few commits from Google, and guess what, still doesn't boot. If anyone wants to join in the chat at hangouts, drop in your gmail here. We need all the help we can get.

Maybe the kernel boots far enough to leave some traces in last_kmsg. The only problem is that the contents are lost if the device is powered off. If you're lucky the contents survive a short time without power. But usually if the kernel boots far enough it will panic and restart itself.

Linux Deploy with Framebuffer on P900

Hi. Has anyone had success with running Linux Deploy in Framebuffer mode on the P900?
Closest I have gotten is with a VT enabled (but WIP) kernel for CM11. I saw the debian desktop flicker on for a second and then all goes black!
Other than that, all my attempts have resulted in a black screen, no backlight.
Ideally, I think I want Linux (deb, ubuntu, something) running on this tablet. I think because of its screen size and powerful spec it would make a very decent laptop replacement, but I feel that the android OS is not designed for this task.
EDIT: I now have debian running using framebuffer on the p900!

notspike said:
I now have debian running using framebuffer on the p900!
Click to expand...
Click to collapse
Is there anyway you would share this in the developer thread, or is it still to early?
I would love to be able to use this option under the MultiROM. If it works on the P-900, it should be possible to have it work under the T-900 as well.

arcadia2uk said:
Is there anyway you would share this in the developer thread, or is it still to early?
I would love to be able to use this option under the MultiROM. If it works on the P-900, it should be possible to have it work under the T-900 as well.
Click to expand...
Click to collapse
Hi acardia, since this message I've gotten P900 to run ubuntu and debian. Unfortuantely there is difficulty with making the touchscreen function correctly - I have the digitizer and spen working though.

I'd like to know what is the utility of using the framebuffer. I use VNC and it's very fluid and functional
What are settings you used to use frambuffer in linux deploy ?
should I use the VT kernel ?
Do you get to use the camera (with VLC for example)?

spen working in framebuffer, USB keyboard working
touchscreen detected, but calibration not complete yet

Hi evereybody!
I have a SM-P905, rooted.
I try to install linux on my device and i got this message (view photo)
After i search on google about my problem, think i haven an incompatible kernel..
Can u help me please? Thx

wikkiz2 said:
Hi evereybody!
I have a SM-P905, rooted.
I try to install linux on my device and i got this message (view photo)
After i search on google about my problem, think i haven an incompatible kernel..
Can u help me please? Thx
Click to expand...
Click to collapse
If I'm right, there is no Kernels with loop device enabled for P905 at the moment.

Can i change the kernel? Or there is no point?
Thx

wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
If you take a look in the development section there is bonuzzz's P-900 kernel that comes with vtfb as one flavor, and there are also a few P-905 kernels. All of these kernels have github repositories, so I'm sure you could cook something up, if you're well versed enough in this domain.

wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
There is a discussion going on about the kernel compilation in the General Forum

notspike said:
Hi. Has anyone had success with running Linux Deploy in Framebuffer mode on the P900?
Closest I have gotten is with a VT enabled (but WIP) kernel for CM11. I saw the debian desktop flicker on for a second and then all goes black!
Other than that, all my attempts have resulted in a black screen, no backlight.
Ideally, I think I want Linux (deb, ubuntu, something) running on this tablet. I think because of its screen size and powerful spec it would make a very decent laptop replacement, but I feel that the android OS is not designed for this task.
EDIT: I now have debian running using framebuffer on the p900!
Click to expand...
Click to collapse
Hello, could you please describe what you had to do in order to get this working? I am trying to do exactly the same without much success. I have rooted my P-901 with the CF AutoRoot, and I have compiled and flashed a non-enforcing kernel using the instructions found at Graeme Hill's Dev Blog (sorry I can't post links yet) -- currently I am able to use Linux Deploy to have a distribution of Arch Linux running using LXDE, but I have to use VNC. I've tried fiddling around with the framebuffer settings in the configuration but it doesn't seem to work... I would love to get this feature working, as my understanding is that it is faster and better than using VNC!
Many thanks in advance!

hi I am currently away for the weekend but I will post some instructions when I'm back. do you know what issue you had when you attempted Framebuffer mode? I've given up on Linux on my tablet for the time being, I got it working but at the end of the day it's not optimised for the hardware so the user experience isn't worth it. too much tinkering and messing about, so I'm back to cm11

wikkiz2 said:
Can i change the kernel? Or there is no point?
Thx
Click to expand...
Click to collapse
The following link was posted by jdparden in the cm11 tread, I think all you need is found in the write-up <My setup with Ubuntu and a custom permissive Kernel: [ Galaxy Note Pro 12.2 ]>, including the link to a kernel.
Good Luck

indotoonster said:
Hello, could you please describe what you had to do in order to get this working? I am trying to do exactly the same without much success. I have rooted my P-901 with the CF AutoRoot, and I have compiled and flashed a non-enforcing kernel using the instructions found at Graeme Hill's Dev Blog (sorry I can't post links yet) -- currently I am able to use Linux Deploy to have a distribution of Arch Linux running using LXDE, but I have to use VNC. I've tried fiddling around with the framebuffer settings in the configuration but it doesn't seem to work... I would love to get this feature working, as my understanding is that it is faster and better than using VNC!
Many thanks in advance!
Click to expand...
Click to collapse
Hi, I used CM11 with the VT/FB enabled kernel.
Linux Deploy settings:
Output: Framebuffer
Additional: disabled VNC server, enabled X server
GUI settings: input as event2, you can check your device list to see what event your S-PEN is, touchscreen does not work properly - so use S-PEN!
use the latest Ubuntu distro

notspike said:
Hi, I used CM11 with the VT/FB enabled kernel.
Linux Deploy settings:
Output: Framebuffer
Additional: disabled VNC server, enabled X server
GUI settings: input as event2, you can check your device list to see what event your S-PEN is, touchscreen does not work properly - so use S-PEN!
use the latest Ubuntu distro
Click to expand...
Click to collapse
Hello notspike, thank you very much, I will try this out again over the weekend!
I can't remember exactly what didn't work last time, just that I remember it was working with VNC, and when I tried reconfiguring it to framebuffer and relaunching it just gave me a blank screen. However, I was doing this on the stock ROM (after rooting with Autoroot and installing a permissive-enabled kernel that I compiled myself as per the instructions on Graeme Hill's blog).
I haven't previously considered using CM11, but if this is what is necessary to get Linux working properly with framebuffer mode, I will bite the bullet and try it out!

indotoonster said:
Hello notspike, thank you very much, I will try this out again over the weekend!
I can't remember exactly what didn't work last time, just that I remember it was working with VNC, and when I tried reconfiguring it to framebuffer and relaunching it just gave me a blank screen. However, I was doing this on the stock ROM (after rooting with Autoroot and installing a permissive-enabled kernel that I compiled myself as per the instructions on Graeme Hill's blog).
I haven't previously considered using CM11, but if this is what is necessary to get Linux working properly with framebuffer mode, I will bite the bullet and try it out!
Click to expand...
Click to collapse
Hey I just noticed a mistake on my part, event8 is S-PEN, event2 is touchscreen, so you want to use event8. Also, if you have any peripherals plugged in at boot (i.e. OTG keyboard) it shifts around your event numbers, so event10 may be your s-pen, make sure you have nothing plugged in at boot and definitely check the device list for what event it is! Good luck

notspike said:
Hi, I used CM11 with the VT/FB enabled kernel.
Click to expand...
Click to collapse
So it seems that to get Linux Deploy working with Framebuffer one must first use a "VT/FB enabled kernel". Unfortunately I am using a P901, and all the custom kernels on these boards seem to be for P900 or P905 only.
I have successfully compiled a P901 kernel before to enable permissive mode using the instructions found at graemehill.ca/compiling-permissive-android-kernel. Does anyone know if creating a "VT/FB enabled kernel" is as simple as just setting the appropriate flags in the makefile and then recompiling the kernel? If so, could someone please point me in the direction of what flags I should set?
Many thanks in advance.

indotoonster said:
So it seems that to get Linux Deploy working with Framebuffer one must first use a "VT/FB enabled kernel". Unfortunately I am using a P901, and all the custom kernels on these boards seem to be for P900 or P905 only.
I have successfully compiled a P901 kernel before to enable permissive mode using the instructions found at graemehill.ca/compiling-permissive-android-kernel. Does anyone know if creating a "VT/FB enabled kernel" is as simple as just setting the appropriate flags in the makefile and then recompiling the kernel? If so, could someone please point me in the direction of what flags I should set?
Many thanks in advance.
Click to expand...
Click to collapse
There is no need for a vtfb enabled kernel. Instead you can use an on/off toggle called SELinux Mode Changer. Linux was successfully deployed by chhaggerty through this feature using Linux Deploy. Additionally, the toggle can be used for all/most kernels, but might run into issues if Knox is not completely removed. You can also achieve this by using a terminal emulator using the command
Code:
su
/system/bin/getenforce
You can also try disable it in build.prop where you set: ro.build.selinux=0,
or build it into a script for init.d
Wanam Xposed might also have the feature built in.

arcadia2uk said:
There is no need for a vtfb enabled kernel. Instead you can use an on/off toggle called SELinux Mode Changer. Linux was successfully deployed by chhaggerty through this feature using Linux Deploy. Additionally, the toggle can be used for all/most kernels, but might run into issues if Knox is not completely removed. You can also achieve this by using a terminal emulator using the command
Code:
su
/system/bin/getenforce
You can also try disable it in build.prop where you set: ro.build.selinux=0,
or build it into a script for init.d
Wanam Xposed might also have the feature built in.
Click to expand...
Click to collapse
Hi arcadia2uk, thanks for the information regarding the ability to enable permissive mode without requiring a recompiled kernel, that's useful. However, my query regarding the VT/FB enabled kernel is unrelated to the enforcing/permissive issue.
The reason I am asking is because I want to try using Linux in framebuffer mode (VNC seems a bit laggy for me), and from what I've read, I need the VT/FB enabled kernel. Unfortunately, none seem to exist for the P901 on these boards, so I'd like to try to compile one myself.

indotoonster said:
Hi arcadia2uk, thanks for the information regarding the ability to enable permissive mode without requiring a recompiled kernel, that's useful. However, my query regarding the VT/FB enabled kernel is unrelated to the enforcing/permissive issue.
The reason I am asking is because I want to try using Linux in framebuffer mode (VNC seems a bit laggy for me), and from what I've read, I need the VT/FB enabled kernel. Unfortunately, none seem to exist for the P901 on these boards, so I'd like to try to compile one myself.
Click to expand...
Click to collapse
I believe the toggle work just as well with framebuffer. Anyhow, you can try using the P-900 kernel the only thing that differentiates the two is the LTE support, and do you really need that with Linux?

OC-K1 Nougat

3.0
given up using peoples dirty code, so downloaded nvidias dirty code instead lol
cleaned the code up best i could, things ive noticed while playing games on the tablet is -
when i play "nitro nation" the first race no longer stutters
when popups appear they dont take a while to appear..
when i play "word mind" it doesnt take ages to load with crackling sound
when using "kernel auditor" if you set the GPU max and min values high (i only did this trying to keep the values standard), when the GPU gets hot, it cant scale down the GPU frequency so it starts trying to kill tasks.
i dont think you need to download/flash blobs as they are for flashing binary stuff, but i cant find a need for it, think its more of a precaution to ensure the kernel boots.. but dont think i have flashed them
-----------------------------------------------------------------------------------------
3.1 : FINAL,
dunno what changes i made but ive recently upgraded my tablet so figured id upload my latest and last
obveously i have had to start again running 3.10.96 but done alot of work to make it as fast as i can so far, but i deleted all references to my old code and cant find them anymore,
GPU is now at 914 MAX as ive found its the GPU that generates a lot of heat, which causes it to throttle, and found values higher than this just degraded performance.
ive known for a long time that "DT2W" works great while connected to USB, due to the custom USB wakelock, i know the app "wakelock revamp - power manager" would resolve it. but ive found tapping where "notifications" would be wakes the screen (ive found bottom right where the camera would be is a good spot) im trying to figure out how to apply the wake lock better.
scores on PCMARK are above the scale on most values
scores on 3DMARK are around 3250 ~ 3320
=========================================
if you want to create your own, i created a guide, also the website i used to help me understand
https://************/how-to-build-android-kernel-on-windows-10/ appuals . com
-----------------------------------------------------------------
Thanks to :
-----------------------------------------------------------------
"hazel nut" for his support, as if he never said "cant wait for it to come out" i dont think it would of pushed me so much
----------------------------------------------------------------
"BitOBSessiOn" for his source code
https://github.com/BitOBsessiOn/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"laufersteppenwolf" for his source code and commits to overclocking and DT2W/STW
https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"Christopher83" for his cross compiler
https://github.com/Christopher83/arm-cortex_a15-linux-gnueabihf-linaro_4.9
-----------------------------------------------------------------
Microsoft, if i didnt hate windows 10 so much, and didnt get a message regarding dropping support for windows 7,
i would still be using a virtual machine which due to it being so slow, i would of probably given up a long time ago
----------------------------------------------------------------
thanks to everyone that has said thank you

Nice to see that you open a thread.
Appreciate a bit companionship here.
In your guide didn't you specify how you create thr zip file.
I used the nethunter installer, which is based on lazy flashed in regard of the external modules, this come in handy, but I found relatively little among the Shield kernel support.
I noticed that you set the make command with the addition of the specifications of the number of CPUs, which are to be used, before every command.
Is this a typo, or is this the correct procedure when you compile with Windows?
Did you mean with
"bin-bash-command"
Click to expand...
Click to collapse
-
cd ~
Click to expand...
Click to collapse
?
PS
1

response
That's just how I make the command, as if you tap the up key, you can scroll through previous inputs, if it makes it faster- that's a bonus.. but you're right about being very little support.
With regards to the zip file - you could use mine or any other zip that is a kernel flash - as long as you drop it into the kernel folder.. I believe there is an "anykernel.zip" somewhere if you prefer to use that.. also if you wish to add your own personal touch, you can modify the script file in the metadata folder

Response
I also chose different colours in the guide and placed it in a separate line so people could understand the exact typing.. or they could copy and paste..
But with regards to support it is one of the reasons I made the guide, in hopes the Nvidia community could follow it, understand how to achieve their own kernel, and improve the tablet. As there seems to be a serious lack of support..
I had to learn on my own, through Google and YouTube, but hopefully this will speed up what took me a month of trial and error..

Is it compatible with stock based fw (5.4)? Just need to flash blobs, then kernel and reboot?

Respond
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom

Reply
Oh, by the way, you can’t compile with windows unless you’re using a virtual machine.. has to be Linux/terminal

Bleeblun said:
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom
Click to expand...
Click to collapse
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?

Reply
attom93 said:
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?
Click to expand...
Click to collapse
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,

Bleeblun said:
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,
Click to expand...
Click to collapse
Yeah, everything worked, awesome, thank you!!

Response
attom93 said:
Yeah, everything worked, awesome, thank you!!
Click to expand...
Click to collapse
Thanks for letting me know, originally you wouldn’t of needed the “wake v3” app, but I started fresh, which gained performance, and I decided to look for an easier way to stop the tablet “deep sleeping” on me.. less of a headache this way :laugh: