***UPDATE***
Files located at the bottom of the post.
Ubuntu runs fairly nice on the GTab. Find a video below to see it boot. Performance is not as smooth as Android, but I've already narrowed down some kernel tweaks to speed it up.
What works:
USB Devices
Wifi
Video (not accelerated)
Internal/external storage
What doesn't work (yet):
Touchscreen
Softkeys
Volume/Power buttons
Accelerometer
Camera
Audio (pulseaudio hangs, haven't investigated)
To get it working, I used a custom kernel with added support for various drivers, but otherwise pretty much the stock VS kernel. It gets the rootfs from the micro SD card, so it only requires a boot.img flash (so it doesn't destroy any user data or the Android system partition).
{
"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"
}
Youtube video of my gtab booting into Ubuntu
***Instructions:
Using linux (via an existing install, or a LiveCD), format a 4GB or larger micro SD card as ext3, and untar the karmic-rootfs on it.
Code:
cd /media/sdcard
tar -xzvf /home/user/Desktop/karmic-rootfs.tar.gz
Install the boot-karmic update zip via ClockworkMod Recovery. ***MAKE SURE YOU HAVE A BACKUP boot update.zip (or grab one from Clemsyn's Kernel Corner)***
Insert the sd card and boot. You will see some yellowish/gold colored text quickly scrolling across the screen - this is normal. This should boot straight to a GDM login screen.
User=gtab Password=gtab
Wireless will work with wicd (not NetworkManager), and you should use a USB hub with a USB keyboard & mouse.
Karmic rootfs tarball (1.1GB)
Karmic kernel update.zip
sweeeeeettttt.
Will you be creating a Rom from this? If so fantastic!
Knew this was just a matter of time...
I'll throw all sorts of support behind this... a stable, fast ubuntu build for this tablet which just push things SO far over the top. Especially since we have that nice usable USB port!
Sweet.....keep us updated!!
jersacct said:
Ubuntu runs fairly nice on the GTab. Find a video below to see it boot. Performance is not as smooth as Android, but I've already narrowed down some kernel tweaks to speed it up.
What works:
USB Devices
Wifi
Video (not accelerated)
Internal/external storage
What doesn't work (yet):
Touchscreen
Softkeys
Volume/Power buttons
Accelerometer
Camera
To get it working, I used a custom kernel with added support for various drivers, but otherwise pretty much the stock VS kernel. It gets the rootfs from the micro SD card, so it only requires a boot.img flash (so it doesnt destry any user data or the Android system partition).
http://www.youtube.com/watch?v=dbLkdvpZVEo
Click to expand...
Click to collapse
Awesome work. Getting 10.10 working with the Unity interface would actually get me very excited.
I'm sure the touchscreen drivers can be retrofitted into something useful - the drivers themselves are pretty straightforward, I guess they'd need to be made to work with X?
The only concern in terms of making it really usable is getting accelerate X11 support. I found this post which is a bit concerning:
http://tegradeveloper.nvidia.com/tegra/forum/newbie-hoping-port-debian-tegra-2
However, I'm guessing we could always use an older X11 that will work with the supported driver ABI?
This thing just gets better
hope the xoom isn't locked down
xbmc
Add xbmc to the rom and you'd have a winner.
WOW! Nice work!
But now you got me all worked up....
....Must....have.....ubuntuuuu....................
I had no clue what Ubuntu was until a Google search.. looks really awesome. It could potentially make this into a thin touchscreen netbook with all the features of a PC.
Keep up the work!
Now that I know that it's feasible, I'm going to continue work on getting a newer kernel up and running. It looks like a lot of the commits have been related to wireless, touchscreen, etc., so a newer kernel could help, along with a nice shiny Maverick build.
WOW! Nice, I will be happy just having Android that works with all the features. I've loaded every flavor of Android so far, but still haven't figured out how to get NTFS to work on the microSD. So far I like TnT Lite the best, but VEGAn is really cool too. Thanks to all for making this so fun and useful.
Aww man.
This would mean I'd have to get a 2nd G-Tab.
Great work.
xinput_calibrator
Hi, FWIW, with help from yuray (for the customized initramfs) and mozzald at slatedroid, I created a rootfs for xubuntu to run on the zt-180 tablet. yuray created the modified boot.img and mozzwald compiled the xinput_calibrator binary to use. It was perfect in getting the touchscreen to work. I also was able to get the onboard keyboard to work fine.
Thanks to mozzwald - If you enter the following from your ubuntu command line - you can see if the touchscreen is identified:
lshal | grep input.product
and to see if it is really working, enter:
sudo cat /dev/input/event2
(if it is working fine, you should see some garbled output on the screen).
If so then you get the source for xinput_calibrator and compile for your build.
HTH.
prscott1 said:
Hi, FWIW, with help from yuray (for the customized initramfs) and mozzald at slatedroid, I created a rootfs for xubuntu to run on the zt-180 tablet. yuray created the modified boot.img and mozzwald compiled the xinput_calibrator binary to use. It was perfect in getting the touchscreen to work. I also was able to get the onboard keyboard to work fine.
Thanks to mozzwald - If you enter the following from your ubuntu command line - you can see if the touchscreen is identified:
lshal | grep input.product
and to see if it is really working, enter:
sudo cat /dev/input/event2
(if it is working fine, you should see some garbled output on the screen).
If so then you get the source for xinput_calibrator and compile for your build.
HTH.
Click to expand...
Click to collapse
Any chance of getting a download link to all this?
Sent from my R2-Droid2 using Tapatalk
Aerv said:
Any chance of getting a download link to all this?
Sent from my R2-Droid2 using Tapatalk
Click to expand...
Click to collapse
Hi - check out the slatedroid thread found at http://www.topic=9501.com . My post with the download link is around page 11 or 12 (can't remember).
Also, This thread is for the zt-180 tablet which has a different arm version. My build probably will not work on gtablet. Also, the wifi drivers and such are for the zt-180 tablet not the gtablet.
There may be some bits of info that may be helpful though.
Any chance we will be able to dual boot this thing? That would be my best option. I i love ubuntu, but android is awesome also. I hope we can have the best of both worlds
Tcsnyder said:
Any chance we will be able to dual boot this thing? That would be my best option. I i love ubuntu, but android is awesome also. I hope we can have the best of both worlds
Click to expand...
Click to collapse
As far as I know, Ubuntu is coming out with a "Tablet" distro. This would mean that it's Ubuntu but optimized for touch screen.
I would also be interested in dual booting also.
Hi Guys,
Do you have boot messages configured.
I'm working blind on the Advent Vega Tablet at the moment.
vgrade
See this post for getting kernel messages to display during the boot process.
http://forum.xda-developers.com/showthread.php?t=893428
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Related
Since msullivan's guide is generalized for all devices I thought I would tailor one specific for our Evo's.
I take no credit for any of this except for what is my own personal experience. 99% of the following has been taken from the original thread HERE
I have not tested this on an AOSP rom nor gingerbread for that matter. If anyone has confirmed it working I will add to the list. Supposedly CM7 cannot find the image file, if that's the case the resolve should be: In Android the "real" location is often /mnt/sdcard, and then the /sdcard mountpoint is added for simplicity. So yeah, my guess would be that Cyanogen doesn't have the /sdcard mount. You can fix your issue by opening the file "bt" in a Unix-compatible text editor (such as Notepad++, or an editor on the phone itself), and replace all instances of "/sdcard" with "/mnt/sdcard".
Working so far:
Froyo Sense (MynsWarmTPTRls5)
Evo Deck (gingerbread) 1.2f
CM7 (gingerbread) Thanks DoManOfFuture
WARNING: THIS IS NOT FOR THE FAINT OF HEART
UPDATE: My goal was to create a version of BackTrack 5 for ARM that was easy to use and install. As of this time, that IS NOT the case! The versions posted here are **probably not** going to work straight out of the box. If you know what you are doing in a Linux environment, you'll probably be able to get it working.
Because of this, the project is currently completely unsupported. You are free to dive in, but you are doing so with no support for me, and I'm not liable for any damage that might be done to your device's ROM.
I encourage you to pass this up unless you know what you are getting yourself into!
If you were referred here from the XDA-Developers.com article...
Hi there! Let's get one thing on the record here... this is *not* a native client! This is the chroot + VNC method that we'd been using to get Ubuntu running with Android for a while. The article makes it sound like that's the case, but sadly it's not. However, with the chroot + VNC method we can really run BackTrack 5 on an Android device, and it really does work. This takes some technical skills, and isn't for the non-Linux experienced user.
Requires a rooted device!
BackTrack 5 installation guides are making their way around this forum. I've tried to synthesize it all, but I've also added my own touches to help with usability and features, along with a workaround for the "ioctl LOOP_SET_FD failed" error message some people have been getting.
In theory this build is nearly universal, so if you have an Android device it should work. I've put it all in one zip file that you can download directly from my website, no hassles or wait timers.
If you are interested have a look, feel free to re-post. Credit goes to the BackTrack team and xda member anantshri (he's got skills, give him props guys), who built the base image file.
If you like what you see help me out, hosting is expensive!
http://www.mattslifebytes.com/donate
(alternatively, you can show interest in the products and services featured on my website, if you know what I mean )
Click to expand...
Click to collapse
Instructions:
BusyBox-
First things first you'll want some of the prerequisites one being Busybox. I'm currently running Myn's Rls5 Rom. All I had to do was go to the market and install "BusyBox Installer." Open that and install the latest version
{
"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"
}
Terminal Emulator-
If you do not have one go to the market and install "Android Terminal Emulator"
VNC-
You'll also need a VNC client. Go to the market and find a suitable VNC Client. "android-vnc-viewer" is a good one.
Starting Backtrack5-
After you have the zip downloaded you'll want to unzip it and place the "bt5" folder on the root of your SD Card.
-Next open your terminal emulator and type “su” <enter>, “cd /sdcard/bt5″ <enter>
-Now enter “sh bt” <enter> (in the future to start BT5 skip the line above and come straight to this command)
-enter "y" when it asks you if you want to start with VNCserver.
Note: I had already ran this before which is why your screen may look different
-Now all you need to do is open your VNC client and connect with the following info:
127.0.0.1:5901 pw: root
When you are finished go back to terminal emulator and type "exit"
Click to expand...
Click to collapse
DOWNLOAD:
Direct HTTP Links:
http://brilldoctor.co.cc/Files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
http://www.shenye.co.uk/files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
Mirrors:
http://www.megaupload.com/?d=M6YCKZLR
[/LIST]
Thanks
I'm running CM7, and am a very competent linux user so I'll give this a shot. I'll post back with the results. Doesn't seem complicated, well getting it running at least, maybe the build process was, but I'll get back with the results none the less.
Update: Works like a charm.
Updated compatibility list. If anyone is running a different rom and these instructions worked for you let me know so I can add it in. Thanks!
Just thought I'd mention, using your guide, this is running perfectly on my Nexus S running 2.3.4 (rooted, deodexed and zipaligned). I have the UI up in the VNC viewer and also can SSH in from my mac too.
Running BT5 on a Nexus S (9023i) with CM7 nightly 88 no problem. It is not very quick, but hey, it works.
Install was not to difficult at all, just download, unzip, run "sh bt", and connect with VNC
so i got it to work on ava-z3 but when in backtrack i tried to run console commands and it didn't work maybe i did something wrong or its just not supported for the phone may be someone can help if they can i was trying to crack my own wep and i have done it many times on my computer but when i tried it on the phone it didn't even recognized basic commands i get it you can run backtrack 5 but what are you able to do with your phone can annyone explain and advice me ?
*rubbing hands together* downloading now. Hope it works on the n1
Sent from my Nexus One using XDA Premium App
Just so you guys know you cannot crack WEP with this. This method CANNOT have direct access to your wifi card therefore it cannot support a lot of the methods used to crack, etc..
This is backtrack5 running on top of your android rom.
Just thought I'd make that clear to those thinking they have a mobile cracking OS That's what netbooks are for lol!
Frank's Tools
This is a compilation of methods used to modify, install and recover your system on the TF101. This is a one click root, ubuntu installer and dianostic/custom set of tools. I did not make any of the ROM's, NVFlash, ADB, aBootimg or any other tools inside of this installer. I just make the user friendly interface and easy to use process for modify your TF101.
{
"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"
}
*****THIS METHOD IS DESTRUCTIVE TO DATA***** THIS WILL ERASE ALL OF YOUR DATA AND INSTALL A FRESH COPY *****
YOUR ARE RESPONSIBLE FOR ANY DAMAGE THAT MAY OCCUR WHILE USING THIS PROGRAM. MYSELF NOR ANY OTHER PERSON OTHER THAN YOURSELF IS LIABLE FOR ANYTHING THAT MAY OCCUR DURING ITS USE.
What you need:
Nvflashable ROM
Ubuntu Filesystem
SBK1 system
Instructions:
1.) Extract archive to a location of your choice.
2.) Put Ubuntu.img and ROM into main folder ( Ubuntu, system, boot and recovery IMG ).
3.) Run the tool.
4.) Do whatever you like
*note: Ubuntu may have to resize the partition. Let it do its thing it may take a couple of minute to do it.
To use Ubuntu you have to press power and volume down when booting. And then press volume up.
Error Reporting Format
1.) Operating System (PC):
2.) SBK Version:
3.) Model:
4.) Transformer Storage Size:
5.) Install Option chosen:
6.) Problem:
7.)Command Output:
- Provide as much information as possible, also if possible pictures are always good.
################################################## ##############
NVFLASH AND ABOOTIMG IS PROPERTY OF THEIR RESPECTFUL OWNERS.
Release notes:
Version 1.1.3
-Dualboot - Android as Default, Ubuntu as Secondary. *Fixed Bootloop
[Carried over from previous version]
Version 1.1.1
-Basic Install with Android as default and ubuntu as secondary.
- Android only install
- Detailed install process
- GUI for aBootIMG and NVFlash* Simple, but still a GUI
- Added Keyboard button for starting the virtual keyboard inside ubuntu.
##DOWNLOADS##
*Due to recent events i will no longer develop this tool. I am releasing the source so everyone can benefit from it. Please if you use my source give me some credit. Part of the reason i am stoping the development of this tool is because to much of my time is being spent on it and causing problems. So here you go guys, merry Christmas...
Frank's Tools SOURCE - VB
Frank's Tools Version 1.1.3
Lilstevie's Thread - Ubuntu Filesystem(Ubuntu.img)
oh my god!you released this,the same vday that i try to put ubuntu on transwformer....i have windows and this,is a big news!hi have a question--ubuntu.img that is HERE...is ok?i put it in main folder?and system.img,you mean the system.img of a nvflashable rom like prime or revolver and i should put it also in main folder?
Hi there,
Sounds like a great tool and im very interested. Can you dual boot with ubuntu and the current rom?
Does it replace CWM ?
Is thereanything to prepare, before installing etc?
I was also wondering if this just completely wipes the tablet and puts only ubuntu or whether it can dual boot. Dual boot would be awesome.
Sorry should of been clearer it uses prime and it is dualboot. Ubuntu is primary. The ubuntu img is from lilstevies thread. Ill update the original post with links.
Can you make an option so that prime is the default and android is secondary?
Where do I get the .imgs? Could've at least linked to them.
The system.img file is a nvflashable rom like prime. The ubuntu img is from lilstevie's thread "Ubuntu on the Transformer". As for the Dual-boot with android as default it will be on my next release. Its a long story on this release. I had alot of options for this release, but it would take alot longer to get it all finished. So i released this mini-version just to let people play around with a little bit. My next version with have a bunch of options along with a GUI interface for ADB and NVFlash.
So will this only work on devices with SBK1?
Correct. As of right now it is on SBK1
frankc123 said:
Correct. As of right now it is on SBK1
Click to expand...
Click to collapse
So it probably won't be possible on an SBK2 device until it is cracked?
This is exactly what i been waiting on gonna try this asap, thanks boss!
Edit: I just hook the transformer up to computer in nvflash mode and click intall?
Sent from my Revolver Powered Asus Transformer
As of right now sbk2 devices does not work with this install method.
Anyone that has used the tool i would like some input if its working for you or if you are having any problems with it.
I need SBK2 cracked lol
Hmm looks like mine is an sbk3
What would have happened if i had tried to flash this ?
hmm maybe i've been out of the loop for the past few month but what is SBK1/2/3 ?
also, i'm already running revolver, would rather keep this intead of prime... is there anyway of installing this without loosing all the data on my revolver install and keeping revolver?
i wait your next release,with android how primary OS.....
So, what if we did a nandroid on our current rom and pulled the system.img from the backup, would that work?
Danny-B- said:
Hmm looks like mine is an sbk3
What would have happened if i had tried to flash this ?
Click to expand...
Click to collapse
where does this SBKv3 come from? I have not heard of devices with yet another SBK, unless of course you are referring to the SL101 or TF101G, but those devices wouldn't be SBKv3, they would be SBKv1 for those devices, the nonclementure for the SBKs are TF101 SBKv1 (The currently known key) and SBKv2, the definition of them is relative to the device itself, as that is key v1 and key v2 for the TF101
sorry i might be wrong. I did a search and found a thread that said it could be sbk3 ...
My serial number is B70KAS309901
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
{
"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"
}
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Haven't slept in over 24hrs and just realized I need to use Aroma Installer. Gonna get some sleep, fix and reup Universal Ubuntop. For those that know what they are doing, edit the scripts to point ot the proper partition to play with it.
Hi, I sent you a pM as well, but I think you want the webtop partition which is not usually called /osh on our device. the block is mmcblk1p24
Lokifish Marz said:
Sorry guys. I was hoping there was a backdoor that I may have missed to get this to work. After working with a couple folks there is no way to make this a user friendly install even with the corrected partition map info. As soon as you guys get unlocked I will revisit this and I will be checking back on a regular basis.
I am looking at yet another Universal release. This time it's not a universal MotoBlur ROM but a possible Universal Ubuntop/Webtop+ release but I need testers. It is based on the latest Webtop release for the Photon (WT-1.2.0-180) and is successfully running on the Atrix, Electrify and Photon. We've been running Ubuntop/Webtop+ since September with minimal issues and I have received multiple requests to port. If successful, the advantage of this universal release is that any improvements and enhancements will carry over to all devices.
Prerequisites:
Unlocked
CWM Recovery (Bootstrap MAY work)
GB Blur based ROM with Webtop support (for now)
/osh be located at /dev/block/mmcblk0p13 (if osh is not located at mmcblk0p13 PM me with the correct partition location)
/osh be atleast 755.9MB
Not afraid of using terminal
Latest version of 7Zip
Ubuntop.7z - 264.3 MB (MD5- AA02B21D7A8D733621AD48B1425E95C8)
DO NOT POST RESULTS - PM ME YOUR RESULTS - IF THIS WORKS I WILL BE RELEASING TODAY
Installing:
Make a full backup including webtop (this is key so you can revert any changes)
Extract the UbunTop.7z file (this requires you have the latest version of 7zip installed)
Copy the Ubuntop folder to internal storage (again this is a must)
From CWM recovery, flash the Univ_Ubuntop_v1.0.0.zip
Reboot and launch webtop
Follow the instructions in the "READ ME!!!" file in the Ubuntop folder
(Right now I'm looking for install success and menupatch success. If you want to install applications and report on that as well that's great.)
Click to expand...
Click to collapse
How can I get this on the atrix 2
Sent from my MB865 using Tapatalk 2
chiikko561 said:
How can I get this on the atrix 2
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Seriously, I am pretty good about helping people out, but this does say right at the top that you basically can't.
On another note, have you talked to jimbridgman, if anyone can help you it's him
Atrix users have been begging me since September to get this on their phones. Unfortunately without any support from the community it wasn't until I sold off stuff for multiple projects that I was able to get an Atrix. After that is was fairly easy to get them on a unified webtop base. As long as I keep under 755MB it should port with no issue once the Atrix2 gets unlocked.
The Atrix/Photon are on Jaunty so the next step is to pull an updated webtop base from another device and get it running on the Photon. After that I can gut it and hopefully get it to fit on the Atrix (it really does require both the atrix and photon to get it to work). In short if I can't shrink it and get it running on the Atrix it's a no go as a unified base is the goal.
I was able to get something close to Ubuntop on the Atrix2 today but it requires a "hard way" method that would limit it to advanced users only. Making it harder is the opposite of where I'm going with this. It really requires unlock to make it a user friendly release.
Lokifish Marz said:
Atrix users have been begging me since September to get this on their phones. Unfortunately without any support from the community it wasn't until I sold off stuff for multiple projects that I was able to get an Atrix. After that is was fairly easy to get them on a unified webtop base. As long as I keep under 755MB it should port with no issue once the Atrix2 gets unlocked.
The Atrix/Photon are on Jaunty so the next step is to pull an updated webtop base from another device and get it running on the Photon. After that I can gut it and hopefully get it to fit on the Atrix (it really does require both the atrix and photon to get it to work). In short if I can't shrink it and get it running on the Atrix it's a no go as a unified base is the goal.
I was able to get something close to Ubuntop on the Atrix2 today but it requires a "hard way" method that would limit it to advanced users only. Making it harder is the opposite of where I'm going with this. It really requires unlock to make it a user friendly release.
Click to expand...
Click to collapse
Can you PM me the steps? I am our webtop/linux guru here, and I am the one that was able to get it run on our SDcard, and get full ubuntu access for the community and I made a full shell script to handle it all for everyone on the Atrix2....
I may be able to make it work very easily for everyone.
P.S. I am pulling this down now everyone, and I will play with this in the morning, and see what I can get setup for us, maybe I can include the whole webtop SDcard hack as well as have it auto start gnome for everyone right out of the gate.
I will keep everyone posted later tomorrow.
jimbridgman said:
Can you PM me the steps? I am out webtop guru here, and I am the one that was able to get it run on our SDcard, and get full ubuntu access for the community and I made a full shell script to handle it all for everyone on the Atrix2....
I may be able to make it work very easily for everyone.
Click to expand...
Click to collapse
lol. I told you Jim would know as always. I'd like to see too. I have never really used web top, but this is great
Sent from my MB865 using xda premium
Alpha preview, not intended for daily use!
Source: https://github.com/nadlabak
Downloads:
Nightly builds: http://skrilax.droid-developers.org/cm10nightly/umts_sholes/
Gapps: http://d-h.st/05j
OpenRecovery 2ndbootOR: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_1.zip
Notes:
JellyBean is very big, therefore ext partition on SD card is required - part of the system and most of the gapps is installed there.
You can find instructions on how to resize fat and create ext partition directly in OpenRecovery in this very fine guide by pontomedon:
Full guide from stock Motorola Android to CyanogenMod 7 for Milestone
Please use 2ndboot based OpenRecovery for installation to avoid sdcard write errors.
The CM10 builds are using 2ndboot to run custom kernel.
Thanks to Skrilax_CZ, the issue of low performance before the first device suspend has been resolved (L2 cache remained disabled before).
The bad GPU performance on CPU clock bellow 600MHz is currently successfully worked around by temporary insmod of older pvr driver
during boot, so it's not an issue anymore (from the user perspective) has been properly fixed by Skrilax_CZ.
Wifi tethering should work since 20121028 nightly.
Other known issues:
- video recording is not working very well currently
HW acceleration increases the application's RAM demands. You can use the included HWA Settings app to disable it per app.
Remember that JellyBean is designed for devices with much bigger RAM than Milestone has. Don't expect miracles .
It really deserved a thread.
You made an incredible job, sir!
JB on the old Milestone, and it is usable as a daily driver. :good:
kabaldan said:
Alpha preview, not intended for daily use!
Source: https://github.com/nadlabak
Downloads:
Nightly builds: http://skrilax.droid-developers.org/cm10nightly/umts_sholes/
Gapps: http://d-h.st/rkk
OpenRecovery 2ndbootOR: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_0.zip
Notes:
JellyBean is very big, therefore ext partition on SD card is required - part of the system and most of the gapps is installed there.
You can find instructions on how to resize fat and create ext partition directly in OpenRecovery in this very fine guide by pontomedon:
Full guide from stock Motorola Android to CyanogenMod 7 for Milestone
Please use 2ndboot based OpenRecovery for installation to avoid sdcard write errors.
The CM10 builds are using 2ndboot to run custom kernel.
Unfortunately, because of yet unknown reason, the device performance is limited until the phone first enters a deep sleep after 2ndboot.
This issue will be hopefully fixed some day.
Other known issues:
- video recording is not working very well currently
HW acceleration increases application's RAM demands. You can use the included HWA Settings app to disable it per app.
Remember that JellyBean is designed for devices with much bigger RAM than Milestone has. Don't expect miracles .
Click to expand...
Click to collapse
Amazing that development still is being made for a device this old! :good: but what about making a cm9 build with 2ndboot ? as jellybean from my experince demands much more resources then ics
With swap even Chrome browser works now - incredible!
After flash this cm10 build , my gallery and music player can't see any images or music , although i had try to remount my sd card , how can i fix it ?
Which rom you used previously?
In case you upgraded from any different from CM10, you should make a full wipe. (data,cache,dalvik-cache)
Do you have ext partition on your sd card? It is necessary to use this rom.
hello. how long it takes after the first boot to run. Sorry for my English. thanks
Eiertschik said:
With swap even Chrome browser works now - incredible!
Click to expand...
Click to collapse
Do you have both swap and compcache activated at the same time?
Can´t believe it´s finally, here, amazing work!! :good:
max_avatar said:
hello. how long it takes after the first boot to run. Sorry for my English. thanks
Click to expand...
Click to collapse
almost 15 mins for first boot
The build from yesterday boots within a few minutes for me.
Skrilax_CZ has fixed the sluggishness after boot!
Another problem solved.
I have had a lot of trouble trying to partition my SD card so is there a easy fool proof way of doing it? I have a 16GB sdcard..
naeem123 said:
I have had a lot of trouble trying to partition my SD card so is there a easy fool proof way of doing it? I have a 16GB sdcard..
Click to expand...
Click to collapse
What trouble? That is usally a straitforward process, especially with the modern GUI tools.
And how it's working? Any errors that would make it unsuable as a daily rom?
_crAss_ said:
Do you have both swap and compcache activated at the same time?
Click to expand...
Click to collapse
No - just swap
64MB partition, mounted with Swapper2, swappiness default (10, iirc)
Super laggy for me, even after deep sleep :/ Excellent work though!
Its been great so far, this rom works like a charm, pitty it doent show all internal ram available with 1GB extra on the SDCard.
Attention everyone!
As you may know or not know, Skrillax_CZ has found out what caused the lag before the first deep sleep.
The latest nightly (10.18) already contains the fix, so i suggest everyone to upgrade.
Works like charm for me, no lag even after the first boot.
Work perfectly!!!
Just to confirm that, the ver 18/10 works so well on my milestone without any errors... What I have done for my phone is as follow:
- Flash back to stock ROM 2.1.1
- Completely format the SD card
- Use the 2nd boot OP to root the phone
- Partition the SD card again
- Flash directly from 2.1.1 to CM10 ver 17/10, and then 18/10...
Work perfectly even with big app like Chrome, G+, Google now, etc...
Here are some screenshots... Again, credit gives to kabaldan. Million thanks to him for great effort for our milestone community...:good:
{
"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"
}
Welcome to bigwheelie for Asus TF101.
Here you will find a utility in both a bash version and a python2 version which will repartition your TF101, giving you much more space where needed for future growth of the software base. The python2 version has prettier output, but functionality is the same for both. To use the python2 version, your environment will need to point any calls to python to whatever the python2 binary is on your particular distro. It currently won't work under python3, only python2. It calls whatever python is set as the default when you type 'python'. You can check with 'python --version'. You may need to, at least temporarily, create a soft link to your python2 to python in your ~/bin directory as root. Check with your distro for instructions. Otherwise, use the bash version which should work on about any modern Linux system.
These are Linux utilities that will handle both SBK1 and SBK2 devices. I have tested both with an SBK1 device. To use, download either zip to a folder on your Linux system. Assuming you named the folder "bigwheelie", then do the following from a terminal:
Code:
cd ~/bigwheelie
unzip bigwheelie.zip
Now plug your device in and place it in APX mode. Easiest way is to power off the device with it plugged into pc and then press volume up and power for about 5-6 seconds. The screen will remain blank. Otherwise, just press volume up and power until the screen goes black then continue to hold for about 5-6 seconds more. Then do this:
Code:
./bigwheelie
You will see this:
Code:
THIS PROCESS WILL WIPE ALL DATA FROM
YOUR DEVICE AND REPARTITION IT WITH
A NON-STOCK PARTITION STRUCTURE.
##### ALL RISKS ARE YOUR OWN!!! #####
##### ENSURE DEVICE IN APX MODE #####
******* REFLASH MENU *******
1) Choose 1 for SBK1 device
2) Choose 2 for SBK2 device
0) Quit
Choice: 1
Choose accordingly to the type of tf101 device you have. If you were actually in APX mode and chose the SBK option correctly, then you should see the process begin and some files moving and then partitioning happening and, finally, the blobs getting written to the device, with an indication of success or failure at the end. If it was successful, then you will see the tablet automatically reboot to Asus ICS stock Android and TWRP_2.8.1.4 will reside in your recovery partition. You will now have the following:
/system 1GB
/cache 1GB
/boot 12MB
/recovery 12MB
You can now reboot into TWRP to flash the ROM or other software of your choice, including larger gapps packages than we were previously able to. The growth of gapps packages sizes and the challenge of keeping TWRP small enough to fit into the stock recovery partition are the main drivers for this.
Enjoy!
Download links:
Filename: bigwheelie-bash.zip
bigwheelie-bash.zip
Filename: bigwheelie-bash.zip.md5
bigwheelie-bash.zip.md5
++++++++++++++++++++++++++++++
Filename: bigwheelie-python2.zip
bigwheelie-python2.zip
Filename: bigwheelie-python2.zip.md5
bigwheelie-python2.zip.md5
Special thanks to bumblebee and rayman for wheelie and other scripts, to nvidia for nvflash, and to Asus for stock firmware blobs.
XDA:DevDB Information
bigwheelie, Tool/Utility for the Asus Eee Pad Transformer
Contributors
sidneyk
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-12-04
Created 2014-12-04
Last Updated 2014-12-04
Reserved
Reserved
Then you did it I'll try
Excellent, new script works perfect! Great Job!
{
"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"
}
Downlaod links added to OP
Download links are now added to the OP.
For Windows how can I do? (PS: it's for curiosity, because I have Ubuntu virtualized...)
And how can I return to old partition table? With restoring Asus Stock blob with nvflash?
Thanks for your work
prendomiao said:
For Windows how can I do? (PS: it's for curiosity, because I have Ubuntu virtualized...)
And how can I return to old partition table? With restoring Asus Stock blob with nvflash?
Thanks for your work
Click to expand...
Click to collapse
I'll post something for Windows later, after a little more testing. Why would you want to return to smaller partitions? Yes, you could use one of the tools available to nvflash an Asus stock rom package back, repartitioning to stock partitions, assuming the tool includes the stock flash.cfg file.
Sent from my SM-N900T using XDA Premium HD app
Thanks (know if it is a reversible process was for curiosity your partitioning method is very useful )
Any news on a Windows version for this? I don't have a spare box to put Linux onto to and use this
Taomyn said:
Any news on a Windows version for this? I don't have a spare box to put Linux onto to and use this
Click to expand...
Click to collapse
Been busy working on kernel. I'll try to get the windows version up in the next couple days.
Sent from my SM-N900T using XDA Premium HD app
Is 12 megabytes enough to be future proof?
Regards
Magissia said:
Is 12 megabytes enough to be future proof?
Regards
Click to expand...
Click to collapse
It's enough to buy us some time. I'm currently building recovery images with kernel and initrd gzipped at around 8.5 mb. That's with Timduru's kernel source. The goal I'm reaching for is to use one kernel source for both rom and recovery. And, also we needed a bigger system partition. The beauty is it can now be changed if we run out again.
Sent from my SM-N900T using XDA Premium HD app
Can't we just throw LVM and ignore the physical partitions? Or would that be too complicated?
Regards
Magissia said:
Can't we just throw LVM and ignore the physical partitions? Or would that be too complicated?
Regards
Click to expand...
Click to collapse
Yeah, was my first thought too. The problem is that the recovery has to reside in a special partition. it is too small to solve the chicken and the egg problem.
doppelhelix said:
Yeah, was my first thought too. The problem is that the recovery has to reside in a special partition. it is too small to solve the chicken and the egg problem.
Click to expand...
Click to collapse
I don't know much about lvm, although I did run across an lvm mod for another device that I considered but I'm not too good with the kernel yet. This works and is simple.
Sent from my SM-N900T using XDA Premium HD app
sidneyk said:
This works and is simple.
Click to expand...
Click to collapse
And elegant. Even if the main development for this device is down to you and tim, a lvm approach has to be integrated into the kernel, either directly compiled or as a module. The forum would be reduced to a "doesn't work" nightmare if people mix lvm-recovery and non-lvm ROM. Your approach ensures backward compatibility. I like that.
doppelhelix said:
And elegant. Even if the main development for this device is down to you and tim, a lvm approach has to be integrated into the kernel, either directly compiled or as a module. The forum would be reduced to a "doesn't work" nightmare if people mix lvm-recovery and non-lvm ROM. Your approach ensures backward compatibility. I like that.
Click to expand...
Click to collapse
Yeah, I've been pulling my hair out trying to get a newer kernel to build and drivers migrated over with not much luck in order to fix seemingly broken selinux support in current kernel, or more specifically proper handling of xattrs and selinux labels.
Sent from my SM-N900T using XDA Premium HD app
@sidneyk - 1st of all, thanks for bigwheelie! Can you tell me why you used 1 GB of space for Cache? Cache was always barely used on my android systems (~50-100mb). Did this change with Lollipop?
GoodSoul said:
@sidneyk - 1st of all, thanks for bigwheelie! Can you tell me why you used 1 GB of space for Cache? Cache was always barely used on my android systems (~50-100mb). Did this change with Lollipop?
Click to expand...
Click to collapse
I read somewhere that cache should be at least 2/3 the size of system for OTA style updates, so I just matched it with system. I don't know if it gets used more with lots of games or not, it always seems to be mostly empty. But, just in case...
Sent from my SM-N900T using XDA Premium HD app