:::::::::::::: UPDATED :::::::::::::::::::
Lubuntu 14.04 with Tegra drivers by DJDILL
This is build off the core by @jrohwer
Screenshots to come..
Download:
Torrent: tf101-14.04-Lubuntu-Tegra-armaf.tar.gz
Seed this as much as you can to help others..
DIRECT DOWNLOAD:
Main: tf101-14.04-Lubuntu-Tegra-armaf.tar.gz
Goo.IM: tf101-14.04-Lubuntu-Tegra-armaf.tar.gz
Dropbox: tf101-14.04-Lubuntu-Tegra-armaf.tar.gz
Mega: tf101-14.04-Lubuntu-Tegra-armaf.tar.gz
MD5: fca17ed3b426848a97175a9f8c5069a2
SIze: 630MB download
Ondisk: 2gb+ (Sorry, I will trim in the next build)
What works:
- Tegra drivers
- Hotkeys - Use shift+ Hotkey
- Media hotkeys work for VLC use ALT + Hotkey
- Vol keys (rockers) on the side
- OSK on boot for login - You need to press the button next to shutdown to get it to come up.. click twice.
- Sound - but cuts out on some mp3s and will not come back until the tab is fully powered down and back up (not just restart)
- Touchegg
- Bluetooth
- Firefox Youtube (HTML5), VLC video play back (as seen in the youtube in post two) -- This may not work.. BUT!!!!!!!! copy the youtube link to VLC and play it..... It works much better!
- HDMI
- Web / Video camera via USB Logitech C110
--------MODULES addins for kernel .10.12 only
- USB DVD PlayBack works with VLC
- USB DVD rw
- USB Audio / Sound
- USB Network adaptors - dm9601
Fixes from other builds:
- Screen will go to black to save power.
LOGIN Info:
User: tf101
Password is: ubuntu
Please change this for your own piece of mind
HOW TO:
Follow @Kingzak34 Great guide to get it all setup and working:
http://forum.xda-developers.com/showthread.php?t=2684854
THIS NEEDS TO BE UPDATED... OLD
How to change things in this build Post #157
Problems: (in order of what makes me angry)
- Icon theme RED Icon network manager-- Fix here (sorry)
- SD card will not auto mount, delete key will not work - Fixes here: POST 268
- Sound .. Is buggy and crashes .. May need new driver or patch for alsa.. Needs to be fixed..
- Mic does not pickup audio
- GPS
- Cam (both)
- tilt sensors
- Maybe 3G internet.. I don't have a TF101G to test that it works.
--- I am working on the sound issues with kernel modules..
FIXED Problems in this build:
- Sound headphones does not kill speakers sound (they both play) - see workarounds
- VLC crashes when playing mp3s.. use gnome-mplayer for now
- Keyboard: Bluetooth hotkey.. I have the code but didn't add it to disable bluetooth, auto brightness hotkey
- ZRAM -- see post #166
- adduser /sbin commands don't work.. run this: export PATH=$PATH:/sbin:/usr/sbin
If you know of more bugs let me know..
Workarounds:
Firefox can be slow.. Install "no script" plugin.. then its heaps better
Keyboard and mouse can stop if the battery is getting low.. Just redock
- Sound headphones does not stop the speakers playing sound - Use alsamixer on command line and press M on the one you want to mute
- If the sound does not work at all..Run alsamixer and toggle DRC (m button)
What can I do with this that I can't do with Android?
USB printing
Full Desktop and mouse etc..
Crack wifi
Use a second screen.. not as a clone - via HDMI
DVD burning
DVD playback
Lubuntu / ubuntu apps
Get frustrated!
-------------------------------------------------------
Ubuntu 14.04 CORE With Tegra drivers by @jrohwer
Core Shell ubuntu see post: #233
INFO:
Ubuntu 14.04 base system. It boots to the console. It has all the xserver packages set up and pre-installed correctly. All the convencience scripts are there, the Tegra drivers are installed, firmware for wifi and bluetooth is pre-installed, init script for bluetooth fixed, kernel modules for rootbind kernels are preinstalled.
Download links on the post above.. I will mirror later
Kubuntu 14.04 With Tegra drivers by @jrohwer
KDE (kde-plasma-desktop) - Please read the below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please see info here!: @jrohwer kernel thread post 303
Please note this will not work with .12 OC kernel.. Only with Kernel from post one of Jrohwer or .10
See posts in this thread for issues with boot and posting to black
Main Download link (google): kubuntu-14.04.tar.bz2
Mirror: kubuntu-14.04.tar.bz2
Mirror (Mega) : kubuntu-14.04.tar.bz2
Torrent: kubuntu-14.04.tar.bz2
MD5:
2a4d63cd4cf7f714e191e832d15abe7d
This build is by Jrohwer all credit goes to him .. As does the kernel for my builds
Lubuntu 12.04.4 With Tegra drivers
:::::: Image is for @jrohwer kernel on post 3 - rootbind
3.1.10-12 oc - It also includes the other kernels modules and FW on his thread.
This is the kernel I use:
http://forum.xda-developers.com/attachment.php?attachmentid=2379482&d=1383923374
Please see his thread here: http://forum.xda-developers.com/showthread.php?t=2347581
Go and thank him for making this kernel!
:::::::
DOWNLOAD HERE!!
Mirrors to come soon!
Torrent: http://forum.xda-developers.com/attachment.php?attachmentid=2735900&d=1399720601
Direct Download: tf101-12.04.4-Lubuntu-armhf-Tegra.tar.gz
Goo.im Download: tf101-12.04.4-Lubuntu-armhf-Tegra.tar.gz
Dropbox Download: tf101-12.04.4-Lubuntu-armhf-Tegra.tar.gz
(maybe I will get banned)
Mega Download: tf101-12.04.4-Lubuntu-armhf-Tegra.tar.gz
Firedrive Download: tf101-12.04.4-Lubuntu-armhf-Tegra.tar.gz
md5 hash:
b60b7ca68c204421b576dc973b017432
(you can use Ez File Explorer to test the hash for Android, or md5sum under Linux)
545.6 MB download
Unpacks to 1.7gb on disk
What is says on the box
Includes everything so you can point and shoot
What works:
- Tegra drivers
- Hotkeys - Use shift+ Hotkey
- Vol keys on the side
- OSK on boot for login
- Sound - but cuts out on some mp3s and will not come back until the tab is fully powered down and back up (not just restart)
- Touchegg
- Bluetooth
- Firefox Youtube (HTML5), VLC video play back (as seen in the youtube in post two)
- HDMI
- Web / Video camera via USB Logitech C110
- USB DVD rw via module add on see this post:
USB dvd support for 10.12 Rootbind
Fixes from other builds:
- System does not fully turn off the sreen / keyboard so it can always be woken up from keyboard press - this can be changed from power manager
- Auto usb mount
- Cheap usb network adaptors driver installed dm9601
- Play, Next and back hot keys talk directly with gnome-mplayer.. So play your mp3s with that
- Audio controls (hotkeys) on have been mapped to turn down both the headphones and speakers.. at the same time .. As the mixer does not have a "master" control. (see problem / workarounds)
LOGIN Info:
User: tf101
Password is: ubuntu
Please change this for your own piece of mind
HOW TO:
Follow @Kingzak34 Great guide to get it all setup and working:
http://forum.xda-developers.com/showthread.php?t=2684854
How to change things in this build Post #157
Problems: (in order of what makes me angry)
- Sound .. Is buggy and crashes .. May need new driver or patch for alsa.. Needs to be fixed..
- Sound headphones does not kill speakers sound (they both play) - see workarounds
- VLC crashes when playing mp3s.. use gnome-mplayer for now
- Mic does not pickup audio
- Keyboard: Bluetooth hotkey.. I have the code but didn't add it to disable bluetooth, auto brightness hotkey
- GPS
- Cam (both)
- tilt sensors
- Maybe 3G internet.. I don't have a TF101G to test that it works.
- ZRAM -- see post #166
- adduser /sbin commands don't work.. run this: export PATH=$PATH:/sbin:/usr/sbin
If you know of more bugs let me know..
Workarounds:
Firefox can be slow.. Install "no script" plugin.. then its heaps better
Keyboard and mouse can stop if the battery is getting low.. Just redock
- Sound headphones does not stop the speakers playing sound - Use alsamixer on command line and press M on the one you want to mute
- If the sound does not work at all..Run alsamixer and toggle DRC (m button)
What can I do with this that I can't do with Android?
USB printing
Full Desktop and mouse etc..
Crack wifi
Use a second screen.. not as a clone - via HDMI
Get frustrated!
Super thanks to:
@ Everyone who keeps using the TF101.. You all inspire me to keep making this better!
@Kingzak34 - For Guides and keeping me working on this project.
@jrohwer - for making / hacking together the kernel.. That makes this all possible
@Sni - kernel patches
@x3maniac - for getting me my first tf101 Linux based Roms and support
Mini 12.04.4 LTS ::: Ubuntu Core with LXDE armhf
No Frills! .. Nothing really installed at all.. Add what you want Minimal install
-Super small 320mb unpacked - 160mb packed
-Very light on ram (160Used on startup)
-Tegra drivers installed & working
-Wifi works
-HDMI works
-Video playback + Youtube HTML5 works
Not tested / note included: Bluetooth, Hotkeys (scripts are present).. to turn down brightness open new terminal and type brightnessdown
NOTE:
This build maybe very annoying for some people.... It does not include the normal Lubuntu things.. It also does not include Firefox or VLC by default (to save space).. It has just about nothing // People who want a full desktop can wait until I build a full Lubuntu ones with drivers next week sometime
Also usb needs to be manually mounted..
All the above can be installed by using your normally apt-get install firefox vlc ..etc!
Some images:
HDMI with TV
What is included
See now it works with a TV
Youtube of video playback:
https://www.youtube.com/watch?v=muV0uK29S2o
Download:
TF101-LXDE-small-Tegra.tar.gz
MD5:
70b5eea5ca1de582c0ef2ba736b1e679 TF101-LXDE-small-Tegra.tar.gz
No Mirror yet!
Plain 12.04.4 LTS ::: Ubuntu armhf
Ok Boys and girls.. Here is the base 12.04.4 with all updates done to it..
Its on a Ubuntu Unity desktop.. What is slow as ****, and laggy and crashy.. It has crashed and restarted on my twice so far for me while
It has all the keybinds done to it and it auto logins in.. The dock is buggy and will need to be undocked and redocked a few times to get the keyboard / touchpad working
sound, touchpad, multitouch, etc working
This build has all the fixes as 14.04 v1.1 But without the power switch fix.. If you want that please see this post:
Post-15
No nvidia drivers installed.. Please fell free to break it your self
Downloads:
Main Mirror:
tf101-12.04.4-Ubuntu-armhf.tar.gz
Dropbox.. Lets get my account deleted!
tf101-12.04.4-Ubuntu-armhf.tar.gz
Size: 911MB
Hash: MD5: 3871787e0b34a6d20fef9d9ef7b0fe2e
---------------------
What's new in v1.1 ::: Xubuntu armhf
Newest bleeding edge updates from Ubuntu launchpad + new Firefox + lightdm (ugly yellow slash on start)
Keybinds setup for: WiFi off on, touchpad off on, brightness controls up down, start Firefox, start terminal, screenshot
:::::Hold "shift" and press the key you desire .. Ie touchpad button a long the top. :::::
note this will only work currently in the Xubuntu session (default) will not work in xfce or openbox.
Plus black screen on fix - with hack from post #15
New panel shortcut for XDA Developers tf101 forum.. For easy troubleshooting help
New performance monitor on the right: CPU, memory, disk access
Hidden Bluetooth icon and power while on charge
Fixed / hidden mount errors on / when booting up post #53
Now includes all modules for all versions of rootbind kernels
Some apps package cleanup
Fixed panel dots for spacer
Fixed some autoload apps
Turned off power settings for suspend
Turned off screensaver
What's not working:
Bluetooth
HDMI
Camera
GPS
Extra USB adaptors ie: USB Ethernet
Volume for system and volume rockers
... Sound does work but only in some apps
Graphics drivers opengl - no support yet?
If you know of more bugs let me know.. I will see about what I can do to fix it.. or hack away at it ^_^
----
system will take a while to start
First login -firefox will take a bit to open
You may have two errors about libc.. this is fine, they don't come back second reboot..
Unpacking takes 38mins in Android.. It can cause the screen to go black and not come back when its unpacking.. Just leave it!! If you really want to see what its doing set the timeout to none or undock re dock and press the power button..
Downloads
Main mirror
tf101-14.04-xubuntu-armhf-1.1.tar.gz
Dead mirror:
Mirror (Dropbox) : tf101-14.04-xubuntu-armhf-1.1.tar.gz
2nd Mirror Goo.im tf101-14.04-xubuntu-armhf-1.1.tar.gz
Thanks to @x3maniac for the mirror
Size: 863 MB (a little bit smaller then before) But unpacks just as big....
MD5: a0371274e0e28e5b623ca6282d52883e
Thanks to everyone who is posting with bugs etc.. I hope to make your life and mine easier with his new image.. Less work more play !!
Current download stats:
40+ As of last edit
-------------------------- OLD Details from post ONE... ------------------------------------------------
This is a 14.04 build with xubuntu installed (see screeny)
This is a armhf build.. Much faster then armel
:::::: FYI this is for @jrohwer kernel on post 3 - rootbind
3.1.10-12 oc
http://forum.xda-developers.com/attachment.php?attachmentid=2379482&d=1383923374
Please see his thread here: http://forum.xda-developers.com/showthread.php?t=2347581
Go and thank him for making this kernel!
:::::::
DOWNLOAD HERE!! -- This is the old 1.0 Build.. see below for 1.1
Mirrors to come soon!
tf101-14.04-xubuntu-armhf.tar.gz
Mirror dead.. Thanks dropbox!
Mirror - Dropbox tf101-14.04-xubuntu-armhf.tar.gz
md5 hash:
cbc9177f656a7e58cae53ff00fa33d7a
(you can use Ez File Explorer to test the hash - Android, or md5sum under Linux)
867.56 MB download
Unpacks to 2.4gb on disk (Likely there is more cleaning I can do to move not needed files to make it smaller)
What is says on the box
Includes everything so you can point and shoot
Working fine::
-modules,WiFi,touchpad,touchegg,sound etc..
Ok here we go:
User: tf101
Password is: ubuntu
-please change this for your own piece of mind
HOW TO:
In Android..
Rename your current linuxroot if you have one using mv
Download and unpack into /data/linuxroot
Comannds:
Code:
su
busybox mount -o remount,rw /
--Rename old Linuxroot
mv /data/linuxroot /data/linuxroot-old
mkdir /data/linuxroot
chmod 755 /data/linuxroot
cd /data/linuxroot
tar -pxvzf /pathto/tf101-14.04-xubuntu-armhf.tar.gz
busybox mount -o remount,ro /
(This will take bloody ages maybe 40mins+ ... Go have a few coffees) - its faster if your going from micro SD
Reboot and you should be away
If you have any issues just delete /data/linuxroot and mv your old one back
The first time it maybe a bit slow to get going... Just wait... You maybe need to start without dock attached
-second boot should be better..
Problems:
Mine always loads with root file system needs to be checked.. Can get past it by pressing i ... I tried scanning it with the tools in this thread.. But no love for me.. I tired also formatting /data still coming up
As this is a 14.04 build it can't include the nvidia drivers.. So that's not so fun... I am planning to build a 12.04.4 one soon ... Maybe someone has a solution ? Last time I tried to get it working I had to reinstall
Also HDMI does not work.. I am guessing because the nvidia drivers are not installed..
Brightness buttons.. See post 41 - for a hack
Its in the Australia time zone use this to fix for you:
sudo dpkg --configure tzdata
Maybe Audio maybe not work in some apps... I tired to fix up pulseaudio .. By removing it... Anyway audio is working for me with mplayer -ao alsa something.wav
your may need to run alsamixer and enable speaker (3rd tab along) press M to enable it
Performance notice while using firefox chrome etc.. Using ABP helps speed uploading time for pages and helps using pages... Otherwise your loading flashy, gifs other useless things that slow down your TAB
Workaround for the below:
Screen saver turns screen off - This is very annoying -- You can turn off the screen saver or wait for me to fix it
If it goes black and you can turn it back on do this: Pressing power button first (screen will go a little bright).... Then ctrl + alt (search) then f1 (the second key along the top) .. Then alt+ Ctrl and f7 -- And then screen will be back........
see page 2 post 1 for fix for this http://forum.xda-developers.com/showpost.php?p=50399357&postcount=1
I have some code I am working on to get the power bind to do what we just did - will have a fix that can be easily applied
If anyone wants to have a look:
https://github.com/djdill/TF101/tree/hotkeys
... Yes I know I am not using git right
Super thanks to:
@jrohwer - for making / hacking together this kernel.. That makes this all possible
@Sni - kernel patches
@x3maniac - for getting me my first tf101 Linux based Roms and support
Current download stats:
102 As of last edit
http://forum.xda-developers.com/attachment.php?attachmentid=2735900&stc=1&d=1399720601
Nice I think you can rename your thread to be more general and add more img ? What do you think ?
( I mean like a img repository for rootbind kernel )
I'll try to do a img with different DE and things.
Thanks for your work anyway, really appreciated !
BTW, x3maniac, if you read this, glad to see you again around here
For our discussion about 13.10 and 12.04, I think I'll make a 13.10 then, like this we got plenty of choice Nvidia driver are supported until 13.10, and not supported anymore since 14.04
"Envoyé depuis mon Transformer TF101 avec Tapatalk"
Kingzak34 said:
Nice I think you can rename your thread to be more general and add more img ? What do you think ?
( I mean like a img repository for rootbind kernel )
I'll try to do a img with different DE and things.
Thanks for your work anyway, really appreciated !
BTW, x3maniac, if you read this, glad to see you again around here
For our discussion about 13.10 and 12.04, I think I'll make a 13.10 then, like this we got plenty of choice Nvidia driver are supported until 13.10, and not supported anymore since 14.04
"Envoyé depuis mon Transformer TF101 avec Tapatalk"
Click to expand...
Click to collapse
@Kingzak34 Good idea! .. OK so I have renamed it now.. let me know what you think.. If you can thank of a better name.. Just paste it and I will change it
OK didn't know about the support up until 13.10.. I was never able to get it to work past 12.10.. Maybe I am doing something wrong.. I was looking and your thread about installing the drivers.. Or is it better just to do it via the software centre?
Somehow I magically fixed the libgl.... Its even fixed in the tar.gz that I uploaded .... Don't know how I did that.. But now I can run Midori (browser).. Faster then FF on the tablets and lighter
I am going to be building more from Monday.. I want to get more fixed with this image (I think it can start quicker and fix some of the errors in syslog)
And I want to fully remove pulseaudio and get ALSA working by default .. Currently in the img.. Audioapps are trying to load to pulseaudio... Even when its full removed.... NFI why that is happening.. anyway more fun time fixing
Oh and the screen fixes for idle .. never turn the screen off correctly
re x3maniac he PMed me a few times today! He working on a another kernel ... But he does not have much free time so its likely going to be a long process .. Anyway this kernal appears to be working fine for me..
DjDill said:
@Kingzak34 Good idea! .. OK so I have renamed it now.. let me know what you think.. If you can thank of a better name.. Just paste it and I will change it
OK didn't know about the support up until 13.10.. I was never able to get it to work past 12.10.. Maybe I am doing something wrong.. I was looking and your thread about installing the drivers.. Or is it better just to do it via the software centre?
Somehow I magically fixed the libgl.... Its even fixed in the tar.gz that I uploaded .... Don't know how I did that.. But now I can run Midori (browser).. Faster then FF on the tablets and lighter
I am going to be building more from Monday.. I want to get more fixed with this image (I think it can start quicker and fix some of the errors in syslog)
And I want to fully remove pulseaudio and get ALSA working by default .. Currently in the img.. Audioapps are trying to load to pulseaudio... Even when its full removed.... NFI why that is happening.. anyway more fun time fixing
Oh and the screen fixes for idle .. never turn the screen off correctly
re x3maniac he PMed me a few times today! He working on a another kernel ... But he does not have much free time so its likely going to be a long process .. Anyway this kernal appears to be working fine for me..
Click to expand...
Click to collapse
For 13.10, the better way to get nvidia driver is through software center I think. But you maybe right, maybe 12.04 as LTS version can be better, I'll try too.
Anyway, thanks for your work, I'll try to do some too, when I'll got more free time
Kingzak34 said:
For 13.10, the better way to get nvidia driver is through software center I think. But you maybe right, maybe 12.04 as LTS version can be better, I'll try too.
Anyway, thanks for your work, I'll try to do some too, when I'll got more free time
Click to expand...
Click to collapse
14.04 is the next LTS =(
Sent from my SCH-I535 using Tapatalk
zachf714 said:
14.04 is the next LTS =(
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
For whatever reason I could not get the 12.04 core to upgrade to 12.04.4 .. My next plan to to use the pre installed desktop image and roll the 12.04.4 over the top and see how much it breaks .... Then it will be current LTS with support for a little while longer.... If they fixed (didn't drop nivida support) in 14.04 it would be perfect
Sent from my GT-I9305 using xda app-developers app
DjDill said:
For whatever reason I could not get the 12.04 core to upgrade to 12.04.4 .. My next plan to to use the pre installed desktop image and roll the 12.04.4 over the top and see how much it breaks .... Then it will be current LTS with support for a little while longer.... If they fixed (didn't drop nivida support) in 14.04 it would be perfect
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
really 14.04 seems great right now, the only thing I have seen is that when the display shuts off (not really of just goes black) I cant wake it back up but what ever I will figure it out
zachf714 said:
really 14.04 seems great right now, the only thing I have seen is that when the display shuts off (not really of just goes black) I cant wake it back up but what ever I will figure it out
Click to expand...
Click to collapse
Yeah I was looking at a fix for that last night... Anyway you can get around it by pressing power button first.... Then alt + Ctrl f1 (the second key along the top) .. Then alt+ Ctrl and f7
Sent from my GT-I9305 using xda app-developers app
You are sure we can not install the nvidia drivers ? I know @jrohwer had them on 13.04
edit - oh yea KP loloolololol
zachf714 said:
You are sure we can not install the nvidia drivers ? I know @jrohwer had them on 13.04
edit - oh yea KP loloolololol
Click to expand...
Click to collapse
The ability to install nvidia drivers depends on whether nvidia will release the appropriate versions. It depends on the Xorg video abi, which has to match the version that is installed on your system. (Ubuntu 13.10 is abi-14, 14.04 is abi-15). Abi-14 has been released so there is an nvidia-tegra package in Ubuntu 13.10. It remains to be seen whether nvidia will release the abi-15 driver for ventana (tegra2 cpus). Even if Ubuntu does not provide the package you can still download the driver from Nvidia directly and install it yourself.
https://developer.nvidia.com/linux-tegra-rel-16
(Read at the bottom - Additional software).
I would revisit this page once 14.04 has been "officially released" and if nvidia provides the binary driver for abi-15 then that should be no problem.
I don't think they will as stated in 16.3 changelog ventana driver will not be updated in future release
R16.3
Bluetooth Keyboard and Mouse Support
U-Boot is officially supported
This is the final release supporting Ventana. T20 support will not be included in future releases.
Tapatalké avec mon Nexus 4 MIUI !
Kingzak34 said:
I don't think they will as stated in 16.3 changelog ventana driver will not be updated in future release
R16.3
Bluetooth Keyboard and Mouse Support
U-Boot is officially supported
This is the final release supporting Ventana. T20 support will not be included in future releases.
Tapatalké avec mon Nexus 4 MIUI !
Click to expand...
Click to collapse
Sure, but they have updated the abi-14 support for 16.3 after its release (see Additional Software), this is not a new release of the drivers, it is just providing updated xorg abi support. So that may well happen for abi-15 as well.
jrohwer said:
Sure, but they have updated the abi-14 support for 16.3 after its release (see Additional Software), this is not a new release of the drivers, it is just providing updated xorg abi support. So that may well happen for abi-15 as well.
Click to expand...
Click to collapse
OK ! I didn't get that
Tapatalké avec mon Nexus 4 MIUI !
Black screen hack
...After lots of googling and head banging I managed to get a fix for the black screen... Its a hell of a hack.. But for now I am running with it..
So what is happening when the screen goes black is the keyboard and touchpad stop responding (don't think I can fix that)
So we use the power button soft press to get the screen back, but it still stays black... (little bit of brightness can be seen after pressing) - After that the keyboard and touchpad work.. OK good... so then we use ALT CTRL F1 then back to F7.. yah back to it.. But thats too much pressing in my mind.. So I have got this below commands to so that work..
Some other background to this.. Lubuntu and use another config to bind commands so its a little easier but Xubuntu uses xfce what is harder
SO you don't have to wait for your screensaver you can use this to test:
xset dpms force off
---Steps
sudo apt-get install xbinekeys
xbindkeys --defaults > /home/tf101/.xbindkeysrc
vim /home/tf101/.xbindkeysrc
Add the below to the file just below line 51 or just below this: control + b:2
Code:
# turn screen back on agian
"/usr/bin/turnscreenon"
m:0x0 + c:124
Then:
sudo vim /usr/bin/turnscreenon
Code:
echo "ubuntu" | sudo -S chvt 1
wait 1190
echo "ubuntu" | sudo -S chvt 7
sudo chmod a+x /usr/bin/turnscreenon
I also needed to remove all the commands on line 124 in this file and log out and back in
vim .Xmodmap
-----
There must be a better way of doing this.. As this requires your user password ... to run SUDO..
I sure there is a clean way of getting around the blackscreen bug.. But I can't get it fixed with my skill set so this workaround I am sticking with for now...
I'm just starting trying your IMG, will give you some feedback when I can
jrohwer said:
The ability to install nvidia drivers depends on whether nvidia will release the appropriate versions. It depends on the Xorg video abi, which has to match the version that is installed on your system. (Ubuntu 13.10 is abi-14, 14.04 is abi-15). Abi-14 has been released so there is an nvidia-tegra package in Ubuntu 13.10. It remains to be seen whether nvidia will release the abi-15 driver for ventana (tegra2 cpus). Even if Ubuntu does not provide the package you can still download the driver from Nvidia directly and install it yourself.
https://developer.nvidia.com/linux-tegra-rel-16
(Read at the bottom - Additional software).
I would revisit this page once 14.04 has been "officially released" and if nvidia provides the binary driver for abi-15 then that should be no problem.
Click to expand...
Click to collapse
It appears that ubuntu tired doing this already from what I can see..
https://launchpad.net/ubuntu/trusty/.../16.3-0ubuntu2
reports that the package was removed as of: 2014-02-05.
Deleted on 2014-02-05 by Sebastien Bacher
doesn't work with new xorg abis, requested by mlankhorst
The ABI version for 14.04 is abi15 what means the debs are missing for the install.. I have forced installed packages like this in the past and it fails to start xorg after
This package should work for everything apart from 14.04
@MiniBlu for the info! (he can't post here yet)
I had word that Nvidia will stop dev on anything older then E3 for linux
@Kingzak34 Let me know how you go! .. The blackscreen bug was really eating away at me .. But now I have at least a workaround I am much happier
DjDill said:
It appears that ubuntu tired doing this already from what I can see..
https://launchpad.net/ubuntu/trusty/.../16.3-0ubuntu2
reports that the package was removed as of: 2014-02-05.
Deleted on 2014-02-05 by Sebastien Bacher
doesn't work with new xorg abis, requested by mlankhorst
The ABI version for 14.04 is abi15 what means the debs are missing for the install.. I have forced installed packages like this in the past and it fails to start xorg after
This package should work for everything apart from 14.04
Click to expand...
Click to collapse
The abi15 drivers have also not yet been released for the latest Linux for Tegra R17.1 from Nvidia (which only supports Tegra4 devices). So I would not write this off completely yet. If they release them for 17.1 but not for 16.3 then that would be the final nail in the coffin I guess...
https://developer.nvidia.com/linux-tegra-rel-17
DjDill said:
It appears that ubuntu tired doing this already from what I can see..
https://launchpad.net/ubuntu/trusty/.../16.3-0ubuntu2
reports that the package was removed as of: 2014-02-05.
Deleted on 2014-02-05 by Sebastien Bacher
doesn't work with new xorg abis, requested by mlankhorst
The ABI version for 14.04 is abi15 what means the debs are missing for the install.. I have forced installed packages like this in the past and it fails to start xorg after
This package should work for everything apart from 14.04
@MiniBlu for the info! (he can't post here yet)
I had word that Nvidia will stop dev on anything older then E3 for linux
@Kingzak34 Let me know how you go! .. The blackscreen bug was really eating away at me .. But now I have at least a workaround I am much happier
Click to expand...
Click to collapse
It's working great so far, no problem found yet, I didnt have time to test everything, but it's stable and fast, my printer didnt need to be added or anything, so far so good
Just now that i got my new TF700T?
Hahahha. Seems my TF101 will have to stay around for a little longer
Related
Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:
Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)
If it will work man i'll give you a real big THANKS!
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
congratulation
Congratz of your new Project!
I will give it a shot as soon as i can
my teset here ..
this is my test in the log file attached
thx
I appreciate your efforts
reverse numbers problem still exits
big thanks
Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping
Thank you
Thank you very much for your great work.
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.
this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App
Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.
This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).
This thread is for help and support related to ubuntu on the eeepad transformer, all questions not related to development should be asked here, please be friendly and do not flame each other or I will request the thread be closed.
Download links are in the third post.
There is a wiki entry here that has a bit more detailed explanation. Please note though that as it is a wiki information
quoted in there may or may not be entirely accurite.
you will need to download an nvflashable rom, like prime.
Please read the README before attempting this. The readme is below as well as in the kit, YOU WILL LOSE DATA.
Download links are in the second post.
OLiFE for the ASUS transformer
------------------------------------------------------------------
(c) 2011 Steven Barker <[email protected]>
This package should have only been linked to from xda-developers
or rootzwiki if you got the links to this package from anywhere
but those sites please send an email to the above email
address with the subject: "unauthorised posts"
DISCLAIMER
------------------------------------------------------------------
Steven Barker (lilstevie) nor anybody will take any responsibility
for any damage, data loss, fire, death of a loved one, or loss of
data resulting from using this mod for your device. Using this mod
may void your warranty.
NVFLASH
------------------------------------------------------------------
nvflash is the intellectual property of nvidia, and remains the
property of nvidia. Any questions or queries regarding the usage
and licence of nvflash should be directed to nvidia.
abootimg
------------------------------------------------------------------
abootimg is by Gilles Grandou <[email protected]> and is
unmodified. The source is available from online at
http://gitorious.org/ac100/abootimg
usage
------------------------------------------------------------------
Usage has changed since the release of the last kit, please read
these instructions carefully, as the install method is a little
more complex, (but easier once you use it).
If you downloaded OLiFE.tar.gz you will need to inject the android
rom and ubuntu image. You can use any nvflashable rom with this.
I recommend that you use prime as that is the configuration that
I have tested myself, and the ROM that I support for use with this
device. You can download the ubuntu image from
http://lilstevie.geek.nz/ports/ubuntu.img.gz.
If you downloaded OLiFE-Prime-Edition.tar.gz you will not need to
download the ubuntu image or an nvflash rom as they are seeded into
the image.
Install instructions:
1) Download the specific flavour of OLiFE that you want to use, and
extract it with "tar xvf <filename>".
2) If needed inject android rom and ubuntu image.
3) From the directory that OLiFE was extracted in run the main script
with the command ./OLiFE.sh.
4) Read the text that comes up and answer the question it asks.
5) Follow the menu to the option you want (below is a breakdown of
what each menu item is) and follow the instructions prompted. (also below
is instructions on how to get into the modes requested).
Menu items:
1) Backup Menu:
1) Full Backup (stock)
- Full backup (stock) takes a full backup of a stock
android system. This gives you an option to also back
up your user data(this will take a while).
2) Full Backup (ubuntu)
- Full backup (ubuntu) takes a full backup of a system
that dualboots android and ubuntu, this backs up your
system, and the ubuntu image. This gives you an option
to also back up your user data(this will take a while).
3) User data only
- This backs up the user data partition on your device.
(This option takes a while)
4) Android ROM
- This option backs up the android system only. This
option generates all the files (minus bootloader, and BCT)
required to flash a rom via nvflash.
5) Ubuntu Install
- This option backs up the ubuntu install on your device.
2) Flash Device:
1) Dualboot:
- This option will install ubuntu to your device in a
dualbooting configuration with android. During the
installation process it asks you which OS you would like
to boot by default.
2) uboot (linux only):
- This option will install ubuntu with u-boot and the
ChromeOS kernel that supports acceleration. This option
is currently unavailable, but should be available soon.
3) asus boot (linux only):
- This option will install ubuntu with the asus bootloader
with this configuration you will use all the eMMC for ubuntu
and there will be no android system installed on your device.
4) stock:
- This option will partition the device in a stock way and
install the android system that is in ./images. Use this
option if you no longer want ubuntu on your device.
3) Update Device:
1) Android Kernel:
- This option will update the android kernel on your device
with the boot.img from ./images/. This allows you to install
your own kernel on the device for android rather than the one
that comes with your chosen rom.
2) Ubuntu/Linux Kernel:
- This will update the ubuntu kernel on your device to the version
included in this flashkit. This option is for updating just the
kernel with nvflash rather than using the blob method. This method
is also good for if you flash a bad ubuntu kernel to the device.
3) Android ROM:
- This option will update the android rom on the device with the
one from ./images/. This is good for if the ROM you use is updated
or you would like to change ROMs and there is an nvflash image for it.
This option does not destroy your data.
4) Ubuntu Rootfs:
- This will update your ubuntu image on the device. This is destructive
to data stored in the ubuntu image.
5) Advanced (Unsupported):
- Any option in this menu is not supported and should be considered
unstable. There may be bugs in these options and they are not maintained
at this point in time.
1) Flash ChromeOS Kernel (Primary Boot):
- This option will flash the ChromeOS kernel to the primary boot
partition. This option may not currently work in it's current
configuration.
2) Flash ChromeOS Kernel (Secondary Boot):
- This option will flash the ChromeOS kernel to the secondary boot
partition. This option may not currently work in it's current
configuration.
3) Update Uboot Partition:
- This option will update the u-boot boot partition that u-boot
reads the kernel and boot script from. This option does work if
you have installed u-boot by compiling it from source and installed
it yourself.
4) Flash ClockworkRecoveryMod:
- This option allows you to temperarily flash CWR to the device so
you can update the installed rom. It backs up the current kernel in
the recovery kernel position and then flashes CWR. When you have finished
using CWR you then push any key and put the device back in APX mode and
it will restore the kernel that was in that position. (This only works if
android is your primary boot option at this time).
4) Inject Firmware:
1) Bluetooth firmware (default install):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system.
2) Bluetooth firmware (CrOS Kernel):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system and flashes the proper u-boot kernel
if you no longer need adb support.
5) Onscreen Keyboard:
- This runs OnBoard so that you can run through oem-config properly
you only need to use this option if you do not have a keyboard dock
and on the first boot.
1) Standard Kernel:
- This will invoke oem-config on the standard kernel installed
on the device.
2) ChromeOS Kernel:
- This will invoke oem-config on the u-boot kernel that is
installed on the device and flashes the proper u-boot kernel
if you no longer need adb support.
Device Modes:
APX Mode:
-This mode is used by nvflash to write files to the eMMC device.
To boot in this mode you press Power and Vol-Up.
Recovery Mode:
- This mode is where CWR or Asus recovery normally lives, but is
replaced by the secondary OS in the dualboot configuration.
To boot in this mode you press Power and Vol-Down, then Vol-Up when prompted.
Normal Boot:
-This mode is where android normally lives.
To boot in this mode you press the Power button until the screen turns on.
Changelog
------------------------------------------------------------------
1.2a - Release name: Odyssey
* New name for kit: OLiFE
* New menu system
* Updated README
* Better handling of platform detection
* Bluetooth support in ubuntu.img
* Preliminary support for ChromeOS kernel
* Preliminary support for uboot
* Fixed touchpad
* Fixed network manager
* Updated to ubuntu oneiric
* More options for flashing and updating
* OTB Wireless support (No more injecting)
* Smaller ubuntu.img for faster upload to device
* Auto resizing of rootfs on first boot
* Larger partition size (6GB) for ubuntu
* Refactored to more easily between devices
* Maybe something else I have missed
1.1 - Release name: Daedalus
* Firmware injector for BT and wifi firmwares
1.0 and silent updates - Release name: Prometheus
* Support for x86_64 linux distributions
* Updated README for release on xda-developers
* Fixes to install scripts
* Initial Release
Downloads:
RootFS md5sum(1a9fa8a698e4a96245a3c08511841eb4)
OLiFE md5sum(c30263fd8271a23bb211fd9fdd69fa45)
OLiFE Prime Edition md5sum(767779ccfa200e5e00b2f1e33a3d73a9)
Sources:
http://gitweb.lilstevie.geek.nz
To clone the repos "git clone git://lilstevie.geek.nz/$(name of repo).git"
lilstevie said:
This is running natively and from the eMMC so no µSD card required,
The video is a class2 µSD card and speeds are not an example of speeds from this kit.
Click to expand...
Click to collapse
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Finally, is this a final release, or for testing purpose only ?
If final, a step by step guide would be very welcome
Edit : Just saw there is the tag [DEV] so forget about my last question (guide)
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Nice to see the post in XDA Good work !
bud77 said:
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Click to expand...
Click to collapse
The video was taken before I was stable enough to even think about using internal memory, where as this kit is not using the µSD
and yeah you lose recovery after selecting dual boot, not much we can do about that for the time being.
poltak11 said:
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Click to expand...
Click to collapse
I started back at uni this week myself, and have been using my transformer as a netbook replacement with ubuntu. The video is using my stuff but before I had it running on the internal memory.
speed diference is massive between the class2 and internal. It was so great of a difference that I forget that it is arm now that it is on internal
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
ErGo_404 said:
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
Click to expand...
Click to collapse
yes, that is the plan anyway
lilstevie said:
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
Click to expand...
Click to collapse
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
poltak11 said:
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
Click to expand...
Click to collapse
The second battery does work, unless you get one of those dodged ones that just randomly stops charging which happened to me, with the dock connected and the battery in it refusing to charge my battery lasted 6 hours.
the layout is different to standard, UDA(User DAta partition) is 4.2GB smaller than what it was, so you have 9.99gb for android and 4.2 for ubuntu, the kernel and recovery kernels are moved up to the end of the flash as well so that they are accessible through /dev
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing. Good job!
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
aligatro2010 said:
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing.
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
Click to expand...
Click to collapse
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
lilstevie said:
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
Click to expand...
Click to collapse
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
So basically we will be able to dual boot Windows 7 and Android?
liorry said:
So basically we will be able to dual boot Windows 7 and Android?
Click to expand...
Click to collapse
No, Windows 7 doesn't have arm version. Windows 8 maybe in future, long future ....
aligatro2010 said:
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
Click to expand...
Click to collapse
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
lilstevie said:
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
Click to expand...
Click to collapse
"bcm4329_sta.bin" was already there before I even copied 2 modules and it was also loaded as module when I did modprobe. (not 100% sure about the second)That's why I thought it was conflicting with android's modules.
Wow, great work! Can't wait to try it.
Sent from my Transformer TF101 using XDA Premium App
I've probably missed something obvious.. But I get this.
file not found: linux.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
rm: cannot remove `linux.img': No such file or directory
Click to expand...
Click to collapse
After like 5 minutes of NvFlash installing stuff.
New Rom: 2.2 V2.5 #4325
Kernal [email protected] #26
The U0 "u-boot-nand.bin" in the archive "4325" is U-Boot 2009.08-svn733 (Jun 29 2011 - 14:11:58).
Downloads thanks to kiodo1981
as we know Mega is dead..
and at the moment it looks like fileserver is going the same way..
File name: 4325.zip File size: 212.15 MB
This link is working as of 9/02/2012 - leave a post if you cant get it..
dropbox...
http://dl.dropbox.com/u/14174333/4325.zip
iuw1.1-english.rar 291.98 KB for those that dont have it..
http://www.fileserve.com/file/taD2UBA
I suggest you load barsuk_CWMRecovery first, its down in the 2nd post..and do the usual wipes that you should do before flashing a rom..
Just a quick note, hopefully will save others some time too..
I think if you just went ahead and flashed the zip from the sdcard..
and now got 'android' loading with blinking cursor and no further..
For the hell of it, I did the same and got the same result..
The download is not a flash-able zip straight from the sdcard..
read further down for instructions
Then I went ahead and used the USB method..
[GUIDE] :: SuperPad/FlyTouch2/WWE10 Android 2.2 Froyo USB Flashing ::
http://forum.xda-developers.com/showthread.php?t=1074251
No drama.. flashed and working fine.. just no camera at the moment.. I might play with some of the uboot's to see if it makes a difference.. but for now if you want your pad back.. I suggest go the USB route..
if you need a cable.. I use the same cable that comes with the usb cooling fans,
that power the cooling boards that people use under laptops.. Make sure you load the drivers or your computer will not recognize the pad.
Follow SmaRkieS thread and you should be fine..
If you cant burn the main android image using USB method.
You can try the MicroSD card method, but this is only applicable if your tablet will display the right uboot versions under the InfoTMIC start up logo.
@dyfren What does file zSYS.img?
I would say this is recovery.. I flashed it into this section..
hope this helps..
Will play over the weekend with it..
but at this stage running real smooth..
Previous version: 2.2 v2.1 #3925
http://forum.xda-developers.com/showthread.php?t=1067746
uboot-nand broken tab fix: thanks to minescumarius
http://forum.xda-developers.com/showpost.php?p=19598435&postcount=2071
http://forum.xda-developers.com/showpost.php?p=19619395&postcount=2072
Thread: infoTMIC Hardware ID's "hwver" and updates (*.ius)
http://forum.xda-developers.com/showpost.php?p=14859284&postcount=2
Gel case that fits it - found by Jiggity Janx
http://www.amazon.com/Skque-Clear-S...1?s=electronics&ie=UTF8&qid=1325020915&sr=1-1
Reserved for FAQ's
Reserved for info collection
Please note: As to the following rambling, this is just me playing with it and I suggest you watch the thread until it settles down..
I take no responsibility and will not support anyone that does the following and bricks their pad..
will update as I play over the coming week..
Noting of course that this is only a play thing.. so others please chime in as I am not supporting this Rom.. just giving you my experiences..
Working and confirmed on mine:
ROOT -THIS IS A MUST - Confirmed using Z4root
http://forum.xda-developers.com/showthread.php?t=833953
or : Working root using universal androot 1.6.2beta5
http://software2tech.com/tag/download-universal-androot/
:: z4root USB Debug solution ::
Code:
1. Download Launcher Pro.
2. Install Launcher Pro.
3. Tap the Home Button at the upper left, it will let you choose different type of launchers.
4. Select Launcher Pro.
5. Tap Menu Button = or at press the menu button at the top of your tablet.
6. Tap the + add
7. Tap Shortcuts
8. Scroll Down, and Tap the Activities.
9. Wait it will load, scroll down to Settings.
10. Scroll down and look for Development.
11. Press OK without changing the name.
12. On Desktop/Home Tap Development.
13. Check the USB Debugging.
14. Restart if necessary.
15. And your done ready to root.
_barsuk_CWMRecovery..
http://forum.xda-developers.com/showpost.php?p=16803134&postcount=278
Confirmed working.. I flashed Via USB to RECVRD
Power+Home to get to it..
vol-\vol+ - navigate
home - accept
back - back
I also got to it by downloading "system toolbox" from market... then just reboot into recovery..
http://dl.dropbox.com/u/14174333/Barsik%20CWMRecovery.zip
http://www.fileserve.com/file/mDPpyvH/Barsik%20CWMRecovery.zip
Google Market
Edits : Just got Google market to load... All I have done so far is to load up launcher pro and set : debug mode..
HDMI
Working - confirmed on with a Mpeg4 - Stock Video and Mxvideo player - load drivers from the MxVideo -- play movie then hit "Menu"
https://market.android.com/details?id=com.mxtech.videoplayer.ad&feature=search_result
Codec
https://market.android.com/details?id=com.mxtech.ffmpeg.v6_vfp&feature=search_result
Streaming is working both on the pad and out to HDMI - testing using DopoolTV
Which a Chinese streamer (Netflix may work then-someone confirm please)
Will load PPTV on lator and see if works..
Ethernet - working - but had to pull out HDMI - reset the Internet connection then plug HDMI back in.. then worked.. so can be setup as a streaming box..
Wifi - so far all reports are stable
Things to Do..
Bootable SDcard for easy install
U-boot conformation for camera to work
Flash another Ramdisk - Download New Ramdisk image to change the path of save files to SDCard1
and this might fix the USB1&USB2 issues I am having.. as they are not mounting and holding..
Tried to do this work around but its not holding..
http://forum.xda-developers.com/showpost.php?p=14894212&postcount=1
http://forum.xda-developers.com/showpost.php?p=18026187&postcount=428
had enough for one weekend on this thing.. let someone else have a go..
Flash - need to work on this
List Apps that work..
VPN - doesnt want to save settings.. may have to push a module to VPN to get it to work..
http://forum.xda-developers.com/showthread.php?t=1063656&page=2
Scripts - I cant get Script manager to work as yet
Netflix - need to confirm
Problems you may face (As I have)
After burning The U0 "u-boot-nand.bin" in the archive "4325" U-Boot 2009.08-svn733, I am not getting the trademark shut down.. so just downloaded a shut down from market that works..
Many thanks for your kindness.
Your post is really helpfull.
Allready in 3925 and works fine, but ... wanna try that new 4325.
I'll give feedback when tried.
Regards.
Bigfart10
i had a go following the guide and it was fine until i got to flashing the actual Android image, (number 19 in the Guide). PC does its bit, then tablet comes up with "flashing/updating linux" (first bit tablet does) or something like that but the progress bar always stays empty, left it for 10-15 mins and still hadnt moved. tried the version in the guide and the version here: http://forum.xda-developers.com/showthread.php?t=1067746
also tried SD card method, comes up with "Updating image hRamdisk" and a dead progress bar.
Which version of Android did you use at step 19?
Thanks for your help so far, seems to be getting there
bigfart10 said:
Many thanks for your kindness.
Your post is really helpfull.
Allready in 3925 and works fine, but ... wanna try that new 4325.
I'll give feedback when tried.
Regards.
Bigfart10
Click to expand...
Click to collapse
Yes.. I recommend it.. makes it feel just that bit more snappy..
Once I get time this weekend will try the root methods..then load in the V6 scripts and see how it goes..
sent from yet another MikG HTC Evo
which u-boot are you using?
mines still getting stuck at "Updating image linux-2.6.32.9"
MS
mine is Uboot - V 0.6.1.2(587)
Try the usual.. plug unplug and reboot computer..
as IUW can be a bit painful..
anybody test this FW ? i wanna try that new 4325 .
rooting
Working root using universal androot 1.6.2beta5
@hunterx: 4325 is working very fast. IT won't shutdown when in standby but drains battery faster.
Someone can explain how to modify the firmware to support the 3G _Barsuk_ as he had done?
Thanks for the new ROM, just installed USB method, works fine.
Generaly looks very "snappy" for a Pad with only 256mb of RAM.
Camera "force closes"; Youtube works fine, and Wifi also.
I'll keep posting as long as i play with it.
Sheers
anyone got USB1 or USB2 readable?
when I plug them in I am getting "preparing memory device" then "memory device ready for remove"
To me, this is saying that it see's it.. but for some reason is calling to unmount it straight away..
I would say it is fixable as we had a similar problem on other Roms.. its just setting up the right command..
I have loaded a mix of drivers in to the system/lib/modules...but no success..
Then tried to use terminal but not getting access in to the root..
I kinda need to learn a few more commands in terminal..
(Back to DOS days..)
is there a cheat sheet around for the basic commands?
was playing with the aps2sd.. got the sdcard formatted with a sd2ext
But its a no go at the moment.. as even with TB backup
This Rom is not mounting into it..
As said before, I can't even get script manager to load up so can't load V6 scripts..
Maybe someone will have better luck then me..
Sent from my Transformer TF101 using Tapatalk
dgcruzing said:
anyone got USB1 or USB2 readable?
when I plug them in I am getting "preparing memory device" then "memory device ready for remove"
To me, this is saying that it see's it.. but for some reason is calling to unmount it straight away..
Click to expand...
Click to collapse
I am using 4325 without any mods and both USB Ports are working fine with my fat32 sticks.
Can anybody tell me if flashplayer is working properly on this firmware?
Firmware I am running now wont play video in browser (just few seconds than it stops sometime sound is remaning.
What are the benefits of this firmware compared to the one I have now
2.2 V2.1#3925
Flash is working for me on this Rom..
but I haven't tested it a lot.. just been to a couple of sites I know with video and they work ok..
just was playing with a program idisplay..
http://www.shapeservices.com/en/products/details.php?product=idisplay&platform=iphone
works ok on it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also I have been using better keyboard.. its a bit older but the lag is not there on it..
plus wireless mouse working great...
question about the flash
Last time I flashed is a while ago so dont know if im doing things right.
So ive got a few questions before I will flash
On startup my pad shows 0.6.1.2. (587) at the right bottom
So can I skip the uboot part of the SMarkies guide?
The folder of 4325 contains more files than mentioned in the guide if i'm correct I only have to use : Kernal, user, system and ramdisk? Please confirm?
Do i have to use ramdisk in 4325 folder or the one mentioned in the Smarkies guide?
Your advice please have to use my pad on christmastrip for my kids so I cant risk to brick it
It's not a problem with this Rom, I also faced the same with previous versions and stock Rom, any of you guys face accelerometer axels inverted when playing games like Raging Thunder or Labyrinth? When bending down turns right and bending up turns left.
Strange, it happens with all games and still can’t find a solution.
Any suggestions are welcome.
kiodo1981 said:
Someone can explain how to modify the firmware to support the 3G _Barsuk_ as he had done?
Click to expand...
Click to collapse
Try this patched lib.
View attachment libreference_ril.Universal.zip
Is new solution for 3g. It is much easier. Who want may create update.zip for CWM.
Just replace original lib and set permissions to 644 (owner root).
EDIT
Some patched binaries and libs: View attachment patched_binaries.zip
Include wpa_supplicant with ad-hoc (not tested), vold with ntfs support (need to load kernel module first), ril libs with disabled check for modem model (for gsm only, not for cdma).
kolk11 said:
Last time I flashed is a while ago so dont know if im doing things right.
So ive got a few questions before I will flash
On startup my pad shows 0.6.1.2. (587) at the right bottom
So can I skip the uboot part of the SMarkies guide?
Yes, I did...
The folder of 4325 contains more files than mentioned in the guide if i'm correct I only have to use : Kernal, user, system and ramdisk? Please confirm?
Do i have to use ramdisk in 4325 folder or the one mentioned in the Smarkies guide?
Flash all the files as per no:18 of the guide.. but use the ramdisk that comes with this package - dont use sMarkies at this stage - I flashed it to see if any difference but it only was for reading of the USBports.. the one with this package is stable enough
Your advice please have to use my pad on christmastrip for my kids so I cant risk to brick it
Click to expand...
Click to collapse
If you follow the guide, you should be right.
as usually people only brick on the U-boot flashing.
just take your time.
make sure you got the right files setup in IUW before you boot the pad..
then...boot-connect-flash...
best rom so far 4325
I am posting from this right now.
problems:
Wifi not starting on boot
Rotation/accelo messed up. Calibration makes it worse
Cell standby - fixed by renaming phone.apk
Market included but is missing skype and others
Camera working with 612 587 uboot
Anyone have advice on overclocking?
Thanks for the rom it is bad-ass.
[Win32/64][Dual Boot][Mount-Loop] Tubuntu - 1 click installer SBK1 & SBK2! *2/1/2013*
* ADDED Ubuntu Raring(13.04) *
* ADDED ARCH Linux *
Tubuntu - One Click Installer for Windows
Hi, i recently been seeing myself flashing my tf101 a lot using OLiFE2. yes my main os is linux but i also use windows and came across a lot of people asking about windows verison SBK2 for ubuntu installer. I found modified version of Frankc123 tools http://forum.xda-developers.com/showthread.php?t=1760513 but it's down. so i created a new one from scratch.
thanks
lilstevie for his OLiFE scripts
wheelie app
Frankc123
kenshin1388
and a few more. (i will find there names and edit this post again)
*Name is still Pending. couldn't think of a good name when i was making this tool. suggestions are welcomed!
Disclaimer:
you know the usual stuff. use are your own risk blah blah might brick.. will not help your become rocket scientest... yea that stuff.
Note:
this was made using VS2010. package needed to run will be dot net 4.0. google is your friend
this is very alpha not all the features are implemented yet
Code:
v0.4.7:
fixed sbk1 device flashing.
v0.4.6beta:
reworked the code for loading into sync mode for sbk1 devices
basically wasted my time with version 0.4.4b & 0.4.5b due to this new update =P
v0.4.5beta:
removed --setbct parameter for sbk1 devices
v0.4.4beta:
fixed bct loader for sbk1 devices
v0.4.3beta:
fix bootloader injection for sbk1 devices
v0.4.2beta:
fixed more bugs not initiating wheelie when needed to for sbk2 devices
v0.4.1beta:
fixed syntax error for flashing kernels
v0.4beta:
added sbk1 support(not tested nor confirmed yet)
re coded flashing method
fixed kernel flashing
fixed only ubuntu boot
fixed only ubuntu/android boot
v0.3alpha:
added RootFS install only option to selected partition
added 2.6x x3maniac kernel to the mix
removed uboot kernel image.( i will not be developing on uboot yet)
reduces zip from 80mb to 50mb. quicker download for faster hacking =)
v0.2.2alpha:
fixed ubuntu/android flash.(ubuntu as default was not booting)
fixed timing issue caused with apx mode detection.
v0.2.1alpha:
added APX mode detection.(now this app will let you know if you are really in apx mode, using drivers i provided)
v0.2alpha:
added logo
added ability to for different flashes and restore back to stock
added different recovery CWM and TWRP
added kernel flashing for chromium or jhanti
fix textbox not updating with console
few bug fixes in program
v0.1a:
initial release
Known bugs:
Code:
[strike]when flashing with Ubuntu Only. kernel panic and keeps rebooting. i am working on a fix.[/strike]
program appears to not be doing anything while flashing device. if it's not frozen and window can be dragged
around it's working. wait for device to reboot. usually 15 - 20 mins to upload 1gb
Not my program bug. but should be mentioned. After you flash your device the 1st time. let Prime run until welcome
screen. then you can flash twrp to flash custom rom. Failure to do so and flashing custom rom without letting prime
run will cause boot loop in newly flashed custom rom. i havn't looked into the logcat but i'm pretty sure that the data
partion don't match or something.
if you run into any problems and you feel it might be bricked.( haven't happen to be at all using this tool) you can use http://forum.xda-developers.com/showthread.php?t=1688012 easy flasher to fix.
Instructions:
MOUNT-LOOP now possible! * 2/1/2013 *
I have now made my new kernel which supports Mount-Loop!! thanks to transformador for the suggestion.
http://goo.im/devs/x3maniac
what does this mean?
this means that you can now just place the ubuntu.img in your internal sdcard and boot the image.
How it works?
i have turned this into a blob file(can be flash with cwm or twrp). which mean you can boot into your recovery flash ubuntu-mountloop.zip. To go back to your android you would need the kernel blob that goes along with the rom your are using. http://www.mediafire.com/?labcx60jowrdx which can be found here. (this is not my link)
Need more information?
http://forum.xda-developers.com/showthread.php?t=1537566
**Useful posts**information regards to partition size
Thanks again to TomTcom for putting together instruction to get BLUETOOTH working!!!! http://forum.xda-developers.com/showthread.php?t=2128080
**FOR SBK1 devices**Follow this guide TomTcom has created! don't forget to thank him!
http://forum.xda-developers.com/showthread.php?t=2041030
**FOR SBK2 devices**
FOLLOW THIS UPDATED GUIDE [GUIDE][Win32/64][Dual Boot] For SBK2 Install of TFUbuntu for x3Maniac Thread by Kingzak34 & don't forget to thank him!!
download the prime image and have it named system.img(if not so already) and place it in the /images folder
download the ubuntu image of your choice and name it ubuntu.img and plce it in the images folder.
go into APX mode. (press volumn up & power at the same time until screen goes black) for windows try to listen for a usb connected sound( for linux type lsusb and look for nvidia(not asus))
Dual Boot A/U:
use flash from dual boot a/u option and wait for device to reboot.
Flash Recovery for Custom rom:
to flash custom rom. goto advanced option and use "flash TWRP recovery" and click "flash". the button will now say "reflash" to reflash the kernel back into the recovery partition.
Drivers:
this option is to install the drivers for APX mode.
(¯`'•.¸//( Using Custom ROM(cm, aosp, etc......))\\¸.•'´¯)this app will re-partition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the CustomRom.ZIP in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your CustomRom.ZIP. when done flashing custom rom. go back into tubuntu app and click "ReFlash" in (advanced/flash TWRP recovery) to flash the recovery back to booting ubuntu.
Screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
lilstevies Prime
http://forum.xda-developers.com/showthread.php?t=1191141
Tubuntu Image - lightweight ubuntu
Tubuntu In Action! video submitted by hugantic
Ubuntu Raring Ringtail (13.04) is up on goo.im
This is a ubuntu-core image.(this mean it has nothing)
for a quick and dirty howto check post #652
password: family
added Nano
added WPA_SUPPLICANT
added kernel supplicants(2.6.36-12.10+)
added wifi modules on boot
Image is 200M
this is a nightly development from http://cdimage.ubuntu.com/ubuntu-core/daily/20130201/
i have this up cause when 13.04 does launch i know what i'm dealing with =)
ARCH Linux for ARM (alarm)
Arch Linux - http://goo.im/devs/x3maniac 151M
More Details for How To
this is a build it yourself system.
It Boots
root password: family
Ubuntu(ubuntu.img)
Lubuntu v1.2 (12.10) - http://goo.im/devs/x3maniac 496.01 MB
only added support for 2.6.36 kernel.(if you want to use newer kernels must installed kernel and supplements)
please review all change log from previous version to see what and how much i have done
zram is broken with kernel 2.6.36 (I am working on patching this up to new zram variation)
added multi-touch support
minimize - three finger down swipe
scroll - two finger up or down
maximize - three finger up swipe
move window - 3 finger drag
right click - two finger tap
fixed boot loop when using "reboot to recovery" from android space
fixed typos on applations not starting
updated a few program forked from "raring" 13.04
removed unnecessary boot up bloat
fixed conky from dissappearing when clicking on desktop
sound works (must use alsamixer and enable DACL & DACR)
Hot plugging works!
DO NOT INSTALL NVIDIA DRIVERS!!(2.6.36.4 does not have hw acceleration)
Lubuntu V1.1-rc1 (12.10)- [download] -382mb 1.4G unrar (wip)(i don't have dock yet so some stuff can't be tested. but it's stable @ 1.2ghz)
Don't forget to download and flash the new kernel below
lots of fixes read post #236 remember to thank Serkenar!!
changed swappiness to 10
now will start on performance mode on boot(had to recompile the kernel for that)
added script in rc.local to fix sound on boot up(you will now hear a slight click noise on boot, means sound should be working)
added scripts to brighten and darken screen(can't test yet but should would with function keys on keyboard)
using newest 3.1.10 kernel forked from jhinta(i just overclocked it)
added script to turn off backlight completely when xscreensaver "blanks" screen
added initial firstboot script to re-partition file system broken: run "sudo resize2fs /dev/mmcblk0p8" (in terminal for now until i get it working again)
sound is working
added cpufreq goverenor controller(located in menu/preferences/cpu-goverenor)
added conky (auto starts with session)
changed XF86poweroff button to disable screen(instead of logoff-selection)
added adb support(jhinta kernel break it, do doesn't work. i'm looking for a fix)
removed programs that our tablet can't use(example: xbacklight)
added zram support
added cifs support(to mount window shares install cifs-utils)
fixed nvidia tegra headers(now can be installed via "software sources" and disabled if needed)
added support for ntfs read and write support
chromium fixed
added some what of a patching system. to upgrade my builds without having to reflash.
added default user "user" (password family)
fixed "waiting for network". no more waiting
removed option with onbaord on boot in favor or default user
added gnome-system-manager (much better i think)
removed extra /lib/modules/ not needed
fixed apparmor complaining issues on boot.
added kernel boot to show everything(easier to debug for me, will be removed in future release when i know it's stable)
some more stuff i can't seem to think of( just bug fixes).
kernel issue: usb stuff gotta be plugged in before you turn on device
kernel issue: touch pad not working(look at post #154 & #206 for fix)
Discussion starts from page 13: http://forum.xda-developers.com/showthread.php?t=1995157&page=13
Lubuntu (12.10)- download - 448mb zip 1.5gb unzipped -now its working, but still don't have my dock =(
version 1.0
removed ubiquity
removed oem-config-firstinstall
removed wpa-supplicant on boot in flavor of network manager(much easier)
pre-installed all packages needed to startup and run
added support for kernel 2.6x and 3.1x
hardware accereration fully working
(not working :cryingadded onboard support for login(people without dock)
added resize2fs on boot (first time) to resize ubuntu image to fill partition (6gb)
pre-installed openssh
more stuff like bug fixes.
what's not working yet:
**do not use android os to reboot to recovery - you will be stuck in recovery boot loop!**
if you happen to be stuck in recovery loop type this in terminal
Code:
sudo echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
sound
zram
aircrack
webcam(don't think this will ever work)
chromium-browser (use firefox instead for now)
this is a LXDE destop version of ubuntu http://lubuntu.net/ light weight and works pretty fast with our devices. i have not been able to fully test if this linux image is stable. currently still waiting for my keyboard to arrive. i will be making this lubuntu image better as i go.
(root password is family i changed it due to hurricane Sandy, yes i'm from NYC)
i'm in the works for my own Lubuntu Image and Arch linux. (waiting for my keyboard dock to arrive but i do have both os booted)
I use netinstaller v0.5 (smaller file size) v0.6(more bug fixes and better support for no dock)
http://forum.xda-developers.com/showthread.php?t=1852702
lilstevies ubuntu.img
http://forum.xda-developers.com/showthread.php?t=1191141
shaola Debian image
http://forum.xda-developers.com/showthread.php?t=1476835
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
[good]
2.6.36 - [cpu 1.4 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 36
glxgear - 59 fps
[stock]
2.6.36 - [cpu 1.2 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 40
glxgear - 50 fps
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/ then use tubuntu tool to flash new kernel
[whats up with 2.6.x]
clocked at 1.2ghz (for now)
hot plugging works
sound works
chrome works (enable CONFIG_SYSVIPC & CONFIG_SHMEM)
STABLE. does not have freezing issues
lid patch
hardware acceleration (not working)
** experimental NOT Stable! **
compiled with gcc 4.7
3.1.10 - xlinux.img
source - http://github.com/novaspirit
*kernel Instructions*
download kernel unzip and place in \tubuntu\images folder
copy the xlinux.img over linux.img(temp fix to load new kernel until i get the program fixed)
flash using "x3maniac 2.6 kernel" (even tho it says 2.6, your acutally uploading the new xlinux.img, which is 3.1.10)
*updated kernel 12/10/2012*
kernel image - 3.1.10-g6e2783c
kernel supplement - kernel_sup.tar.gz
download the kernel supplement file and place it on the root of the drive.
you can also wget the file
Code:
sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
unzip using root
Code:
sudo tar zxvf /kernel_sup.tar.gz
this will extract the new firmware and modules to the correct location(/lib/modules, lib/firmware)
now use my tubuntu tool copy the linux3.img to the \images\ folder and rename to xlinux.img
now flash using "x3maniac kernel" option in the advanced section.
** I will be making a tutorial when i get around to it **
*linux version*
as per a few request in this thread about a linux version. i will not be creating a linux version for there is one that works perfect!
OLiFE by lilstevie
someone then has modified the version and made it compatible with SBK2 devices using wheelie. due to OLiFE sbk2 is hard to find on this forum i have uploaded the version to my own server
OLiFE sbk2
I did not create this program so support for it will be limited.
*i don't remember where i found the thread nor who modified it. if someone knows the orginal creator please pm me and i will update to apply credit to the dev. the orginal creator contacted me josteink. thanks for his amazing work on updating oLiFe to support sbk2
Source Codes - http://www.github.com/novaspirit/
Downloads - http://goo.im/devs/x3maniac
I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.
LeoBloom. said:
I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.
Click to expand...
Click to collapse
give me a few more days and i'll come up with a good summary for you(waiting for my dock). but as for a brief one. it works really well on minimal install like lxde or gnome classic. everything does work except webcam. it's pretty stable but i've been flashing my device so much i havn't stayed on one os that long(1 day max). hardware acceleration does work on certain kernel (will be updating my programs to inject new kernels later). my goal for this program in general is to keep my transformer as a fully functional 2nd laptop and being able to swap between / backup my ubuntu as i go along trying to find the perfect build.
Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now
LeoBloom. said:
Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now
Click to expand...
Click to collapse
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see
x3maniac said:
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see
Click to expand...
Click to collapse
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.
LeoBloom. said:
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.
Click to expand...
Click to collapse
look in post #3 of lilstevies thread. OLiFE with prime. pull the system.img from there. it's going to be a bit before i get mine up on my website. 500mb
Hi!
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....
Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk
billouetaudrey said:
Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk
Click to expand...
Click to collapse
well "prime" is the ROM stock from asus.
x3maniac said:
well "prime" is the ROM stock from asus.
Click to expand...
Click to collapse
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?
billouetaudrey said:
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?
Click to expand...
Click to collapse
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps
thxxxxxx
x3maniac said:
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps
Click to expand...
Click to collapse
OK Thx I will try tommorow Thx !
Envoyé depuis mon Galaxy Nexus avec Tapatalk
i9apps said:
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....
Click to expand...
Click to collapse
follow the instructions on screen to finish the installtion process. head over to http://forum.xda-developers.com/showthread.php?t=1852702 post #1
Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk
billouetaudrey said:
Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229
x3maniac said:
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229
Click to expand...
Click to collapse
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk
billouetaudrey said:
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.
x3maniac said:
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.
Click to expand...
Click to collapse
OK so I wait because I'm not expert and don't all understand... And I'm french and it's not easy...
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Developers thread for users general.
I will post here some external links and additional information.
GitHub tf700 Repository - place for config files and step-by-step manual to create you own kernel and rootfs
GOO.IM file place
Tablet PPA for Raring
Changed packages is placed in /root/deb directory.
Known problems: (nexus7 wiki, mattfischer blog post, nexus7 bugs)
Unity has some problems with performance and ram eating - this is place for optimizations.
In-device microSD really bad works.
WiFi disabling is fail bcmdhd kernel module.
vt1-only, if you try to switch to vt* (`chvt 2`) - your device is freezes and reboot.
To use unity you need nux-tools, libnux-3.8-0 and libnux-3.8-common with version 3.8.0-0ubuntu1nexus7.1 (this packages are hold)
Sometimes I can see really bad artifacts with fonts and background on the device screen (mostly if using chromium browser). Only reboot fixes it.
Progress list:
Test Linux boot {DONE}
SDCard rootfs {DONE}
Graphical boot{DONE}
Keyboard special keys remapping (Esc, F1-12, Ins, Print, Break, Del, Home->Alt, Search->Meta4) {DONE in 0.8.0}
WiFi {DONE}
OpenGL ES {DONE}
Audio {DONE} In pavucontrol as output device selected Analog Stereo Output, in alsamixer (tegra-codec) unmute IntSpk
Video up to 1080p {DONE} (ac100 info) - Soft audio requires gstreamer0.10-plugins-*
nvgstplayer --sas="audioconvert ! pulsesink" -i <videofile> - Fullscreen mode
nvgstplayer --svs="nvxvimagesink" --sas="audioconvert ! pulsesink" -i <videofile> - Window mode
Touchscreen {DONE in 0.7.0} - used mtev one-touch driver 0.1.13 with api and 2button patches - right click by push one finger and click by second finger (thanx, cb22)
Touchpad {DONE in 0.6.1}
2 fingers scrolling {DONE}
3rd mouse button by 2 finger tap {DONE 0.6.1} - created new version of package multitouch "-swaptaps"
Updated tegra3 drivers and codecs to 16.2 {DONE in 0.6.1}
Ubuntu/Android dualboot {DONE in 0.7.0}
Initrd bootloader trying to boot sda1(dock sd cardreader or usb device), mmcblk1p1(internal microsd cardreader), sdb1 (dock sd cardreader or usb device), mmcblk0p9(inernal device), /data/media/tf700-rootfs-linux.img(in-device installed virtual disk) (0.7.0)
If it can't load linux - fallback to Android (0.7.0)
Boot android if voldown (or special, like Up key) key pressed in menu (0.7.0)
Fixed nvavp problem in android (0.7.0)
Fixed problems with Android sleeping by unbinding vtconsole before Android boot (0.7.0)
Initrd installer to mmcblk0p8 user partition and mount as loop with binding mmcblk0p8 {DONE in 0.7.0}
Fonts and cursor size {DONE in 0.8.0}
ZIP installer by Aroma {partially}
Install of boot image {DONE in 0.7.1}
Install script for SDcard-way and Virtual Disk-way {DONE in 0.8.0}
Possibility of using mmcblk0p8 /data as /home {DONE in 0.8.0}
Dynamical making of boot.blob {DONE in 0.8.1}
Select rootfs to boot {DONE in 0.8.1}
CM10.1 initrd (link) {DONE in 0.8.1}
Android boot from sdcard or virtual drive {DONE in 0.8.1}
UbuntuTouch initrd {DONE in 0.8.2}
Change boot system names {DONE in 0.8.2}
Add option to boot android by default {DONE in 0.8.2}
Check md5 of rootfs archive
Encryption for linux partition
FSCK check & fix rootfs before mounting {DONE in 0.8.2}
GPIO keys {partially in 0.8.0}
Switch rootfs to 13.4 (link) {partially}
Bluetooth
Try this: /system/bin/brcm_patchram_plus --bd_addr `cat /etc/bluetooth/bt_addr` --enable_hci --enable_lpm --no2bytes --tosleep 50000 --baudrate 4000000 --use_baudrate_for_download --patchram /lib/firmware/bcm4334.hcd --i2s=1,0,0,0 /dev/ttySAC0&
Totem and nvgst modules
Go to Wayland+Weston+libhybris to use egl android drivers
Disable speaker if headphones connected
Additional:
Ubuntu Cube Desktop {DONE in 0.6.2}
Chromium browser with egl and ffmpeg support {partially} - Youtube has problems with performance
Games & software {partially}
Duke3D {DONE}
Minecraft {partially}:
+ MCP
+ LWJGL 2.8.x (`ant jars_es && ant compile_native_es`)
+ Hands
Games and Emu (in Russian)
Xonotic
C-Dogs SDL
pcsx-rearmed (pi) (Return Fire and other good ps1 games)
Open Clonk
OpenLieroX
Blender + LuxRender
Need help:
Suspend to RAM - Not working with X (trace), without X (stop lightdm) - suspended, but not wake.
Wakelock to emmc
Wake up: echo "on" > /sys/power/state or powerbutton (maybe with kernel patching)
Totem - now is not working
gstreamer-properties and set Audio->Output=Custom, Audio->Output->Pipeline="nv_omx_audiosink" and Video->Output=Custom, Video->Output->Pipeline="nvxvimagesink"
HDMI copy of screen (any ideas?)
Xorg configuration shows blue lines on HDMI screen
Not working properly with 1920x1080: `xrandr --output LVDS-1 --auto --output HDMI-1 --mode 1920x1080` - I get "xrandr: Configure crtc 1 failed"
Tested on different display with fullhd support - seems like tegra3 drivers problem
Works ok with 1280x800:
xrandr --newmode `gtf 1280 800 60 | tail -n2 | head -n1 | sed 's/ Modeline //'`
xrandr --addmode HDMI-1 1280x800_60.00
xrandr --output LVDS-1 --auto --output HDMI-1 --auto
HDMI audio (any ideas?)
Adobe Flash player (any ideas?)
Skype (any ideas?)
List of optimizations:
ZRam {DONE}
UKSM (Ultra Kernel Samepage Merging) {DONE} (info in Russian)
CPU optimizations {partially}
Clemsyn OC 1.3 - 1.8ghz 650GPU Kernel {DONE in 0.6.2} - seems like not properly working on AndroidRoot hacked bootloader
Boot optimizations {partially}
Initrd scripts {DONE in 0.6.2}
Kernel modules upgrade from initrd {DONE in 0.7.1}
IO optimizations {partially}
Some optimizations of filesystem mounting {partially in 0.6.2}
Install to device main emmc memory {DONE in 0.7.0}
Power optimizations:
Screen off on lid
RAM Sleep
Powersave, Auto and Performance modes
Plans for the future:
Prepare common installer for any tegra3 device.
Test builds:
Nope
If you can help in development - please, write here.
This is very nice! Its certainly a good start.
There are definitely changes between your implementation and Jay's build. It would seem that after reviewing your source code that the major difference is your overall system config and choice of location of rootfs.
The kernels aren't too too different.
you are using noop vs cfq which is understandable since you are using the stock kernel vs CM10
you incorporated less debugging vs debugging (agree with your preference)
you incorporated framebuffer vs no fb
you incorporated zram vs no zram (smart move to help chromium)
your enhancements are much better IMHO.
You are not utilizing the linux for Tegra drivers. I think we could benefit by utilizing the latest version at least for sound. After reviewing the documentation and reviewing the drivers themselves I think we should integrate. That is unless you are trying to have two separate kernels instead of a monolithic kernel that can boot android and linux kind of like "Ubuntu for Android"
Since I have a working nvflash'd tf700 I am working on a dualboot kexec.
I still prefer the monolithic kernel approach for Android and Linux concept though, and make selection during boot as to which environment to go to. Essentially, it is possible to boot the kernel and run a specific environment and end that environment and switch to another environment.
As others have suggested I think we should integrate both into 1 tree and also try to get the tf300 on board because other than their kernel, specific tf700 configs/rules the rest of the rootfs and other portions should be identical.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
quicknik said:
You are not utilizing the linux for Tegra drivers. I think we could benefit by utilizing the latest version at least for sound. After reviewing the documentation and reviewing the drivers themselves I think we should integrate. That is unless you are trying to have two separate kernels instead of a monolithic kernel that can boot android and linux kind of like "Ubuntu for Android"
Click to expand...
Click to collapse
You mean - HW sound? I have integrated drivers, because I use modified nexus7 rootfs. Maybe, I wrong...
Also, integration of kernels is too difficult task for me now...
quicknik said:
Since I have a working nvflash'd tf700 I am working on a dualboot kexec.
I still prefer the monolithic kernel approach for Android and Linux concept though, and make selection during boot as to which environment to go to. Essentially, it is possible to boot the kernel and run a specific environment and end that environment and switch to another environment.
Click to expand...
Click to collapse
I also have nvflash by wheele, but for users preparing device for this - is too difficult. Now I already prepared dualboot with same kernel through initrd menu. In 0.6.0 I will release it. I have some problems with integrated cameras, but wifi is now works in android.
I think we have some problems with non-JB androids with this dualboot... But it is simple.
quicknik said:
As others have suggested I think we should integrate both into 1 tree and also try to get the tf300 on board because other than their kernel, specific tf700 configs/rules the rest of the rootfs and other portions should be identical.
Click to expand...
Click to collapse
Applying to tf300 - is good idea. It's a part of integration all tegra3 devices in same Ubuntu installation for pads.
Sorry, guys. I found my mistake with no-dualboot initrd. Now i replaced it to true dualboot (0.6.1).
rabits said:
Developers thread for users general.
Test builds:
boot.img dualboot initrd Pre-release 0.6.1
for me dualboot nice works, but I need to change verbosity of kernel output and boot menu more user frendly. If you can try it and write your suggestions - that will be cool.
assembly of mini initrd and android JB 4.1.1 (I have CleanROM 2.4 installed on my tf700t).
wifi on android is supported (added p4p bcmdhd option), but nvavp can't load fw.
boot menu (included linux, android, initrd shell) is showing after kernel loading.
Click to expand...
Click to collapse
I am more than willing to try, but how can I dualboot that first build ? If you provide a few step by step instructions, I am sure a lot of people will try which will help the development by giving several feedbacks.
I am currently on Clean Rom Inheritance (= CROMI) 2.7.2 which is the latest update in the Clean Rom series. Since you are using 2.4, I guess the steps woul be exactly the same as for you. I am however using Clemsyn kernel. Is the stock kernel required to be able to dual boot ?
One the OP, Ubuntu seems tobe pretty stable since a lot of features ar working. Is that really the case ? Is compiz already something I could consider using at this point of the developpment or is it still a little bit early ?
I am really interested in this project and I thank you a million time for starting actively a development allowing us to dualboot Ubuntu. Keep up you awesome work !!!
singoutout said:
I am more than willing to try, but how can I dualboot that first build ? If you provide a few step by step instructions, I am sure a lot of people will try which will help the development by giving several feedbacks.
I am currently on Clean Rom Inheritance (= CROMI) 2.7.2 which is the latest update in the Clean Rom series. Since you are using 2.4, I guess the steps woul be exactly the same as for you. I am however using Clemsyn kernel. Is the stock kernel required to be able to dual boot ?
One the OP, Ubuntu seems tobe pretty stable since a lot of features ar working. Is that really the case ? Is compiz already something I could consider using at this point of the developpment or is it still a little bit early ?
I am really interested in this project and I thank you a million time for starting actively a development allowing us to dualboot Ubuntu. Keep up you awesome work !!!
Click to expand...
Click to collapse
Thanks for your support)) I think, you could use users general thread for test boot steps. The steps are the same, but with the current rootfs (0.5.0) linux in dualboot may not start. Android with CleanRom should work. Soon I will release a rootfs 0.6, which can be used with dualboot section.
rabits said:
Thanks for your support)) I think, you could use users general thread for test boot steps. The steps are the same, but with the current rootfs (0.5.0) linux in dualboot may not start. Android with CleanRom should work. Soon I will release a rootfs 0.6, which can be used with dualboot section.
Click to expand...
Click to collapse
can do for TF300 ?
tailormoon said:
can do for TF300 ?
Click to expand...
Click to collapse
I don't know - but you can try.
Hi
How is it going with the developpment? Is the dualboot working nice with Ubuntu now?
Do you think a cube desktop will ever be usable on a dualbooted Ubuntu on our device?
Thanks for the good work
Hello, I have managed to get this booting on my tf300t tablet. It is working alright and I would like to learn a bit about this area of development so I can tweak it to get it working as well as contribute to the project as a whole. So far it has bugs with wifi, bluetooth, and sound. Also, when I select shutdown from the ubuntu menu, it corrupts the image and it will boot to lightdm and then freeze. I tried compiling a kernel for it based on a tweaked tf700t 10.4.4.20 kernel that was patched by untermensch to work for the tf300t but it did not solve any issues, it pretty much performed the same. I wanted infrom everyone of the issues on the tf300t as well as ask for some guidance as to documentation for what steps I can take to fix these issues. Thanks.
keeganmccallum said:
I wanted infrom everyone of the issues on the tf300t as well as ask for some guidance as to documentation for what steps I can take to fix these issues. Thanks.
Click to expand...
Click to collapse
It seems that this is the rootfs problem. Maybe you find some info in tf300 forum or ubuntu forums, but you need try to read log files and, maybe, do hard gdb trace.
Trying it when i get home
Thanks
Sent from my GT-N7000 using xda premium
BTW happy to have CROMI involved with this
rabits said:
[*]boot.blob v0.6.2 - Anyone can try to flash it? I can't flash it by fastboot on AndroidRoot bootloader - maybe it should work on JB bootloader?
Click to expand...
Click to collapse
Your dummy signblob header is one byte too long - there is a 0a byte before "MSM-RADIO-UPDATE" that should not be there.
_that said:
Your dummy signblob header is one byte too long - there is a 0a byte before "MSM-RADIO-UPDATE" that should not be there.
Click to expand...
Click to collapse
Thanx, I missed this byte)) Damn sed. We should always use echo and cat))
Blob is updated.
rabits said:
Blob is updated.
Click to expand...
Click to collapse
Successfully flashed via fastboot and it booted my Android (still the old CleanROM 2.3) fine. The initrd menu and framebuffer console is awesome. Can't try your rootfs right now because my PC cardreader is making trouble (I hate SD cards and readers, they are unreliable sh**, or they hate me).
Only everything is very tiny (160 dpi instead of 240), and adding ro.sf.lcd_density=240 to /system/build.prop did not help. I'll have to add it to the initrd and see if it helps. Strange, because I thought newer CleanROMs also set the dpi via /system/build.prop, but who knows. Eventually I should install CRI 3.0 anyway.
Hm, while I was writing this, the TF700 spontanously rebooted... looks like problems turning off the screen. /proc/last_kmsg contained two WARNINGs with stack trace, both containing do_blank_screen (drivers/tty/vt/vt.c:3728 and vt.c:650)
I just read that this is Clemsyn's kernel - where did you find the sources for the current version and what did you modify? There are so many different binaries in that thread and so few source drops that I totally lost track.
Hi
I've just seen the cube desktop is know supported on 0.6.2. How is it performing ? Is the latest version smoother than 0.5 ?
Thanks for the great work!!! I hope our tabs will soon have a stable and smooth Ubuntu dualbootable with CROMI
_that said:
Only everything is very tiny (160 dpi instead of 240), and adding ro.sf.lcd_density=240 to /system/build.prop did not help. I'll have to add it to the initrd and see if it helps. Strange, because I thought newer CleanROMs also set the dpi via /system/build.prop, but who knows. Eventually I should install CRI 3.0 anyway.
Hm, while I was writing this, the TF700 spontanously rebooted... looks like problems turning off the screen. /proc/last_kmsg contained two WARNINGs with stack trace, both containing do_blank_screen (drivers/tty/vt/vt.c:3728 and vt.c:650)
Click to expand...
Click to collapse
Yeah, seems like too old CR version...
_that said:
I just read that this is Clemsyn's kernel - where did you find the sources for the current version and what did you modify? There are so many different binaries in that thread and so few source drops that I totally lost track.
Click to expand...
Click to collapse
You can find info about kernel here and here. I'm used this source from second link to build 0.6.2 kernel.
singoutout said:
Hi
I've just seen the cube desktop is know supported on 0.6.2. How is it performing ? Is the latest version smoother than 0.5 ?
Click to expand...
Click to collapse
I just installed extra plugins))) Currently Nexus7 is more smoothed then tf700 with unity... Cube is rotating ok, but with IO lags - sd speed so slow.
Currently I working on more basic things, like install linux in main flash drive. If you have any ideas - please, post it here.
Hi everyone,
I've been working on getting ArchLinuxArm running on the TF300 over at http://forum.xda-developers.com/showthread.php?t=1918849
Just something that might help with your touchscreen - you should be able to get basic functionality if you use the xf86-input-mtev driver (see https://aur.archlinux.org/packages/xf86-input-mtev-meego/ )
While less than ideal, it's better than nothing. We have the same issue with X segfaulting when the evdev driver is used. I actually looked into that, and it has to do with the way events are reported by the kernel driver, if I remember correctly.