Related
This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today
reserved for future updates
also reserved for future updates
and this, too
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
What the F?
♥♥♥
Good luck~♥
Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )
This is pretty consize. I hope it sums up all the main points of fatsal thread on android
With zImage_kovsky_20100313.zip system always lock up during shutdown
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<
gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?
vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.
I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that
dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.
Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?
can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?
I just want to share what i have found with my bricked vogue, after doing some test with mtty and a lot of search.
in WM, bad flash sometimes (rarely) give the internal memory with some bad block,
in android kernel, maybe you'll find some note about those bad blocks.
in my vogue, i have several bad block depends on how i setup the kernel, specially when i set partition in kernel.
if i don't set the partition in kernel, i will have only 1 bad block
in my vogue :
bad block 176
Click to expand...
Click to collapse
when i set the kernel with re-partition the system, will give my vogue to have another bad block
bad block 60
bad block 90
Click to expand...
Click to collapse
everything went normal for months and i still can install android, untill i get this. then a week later, it doesn't wake up anymore.
but i can still enter the bootloader. but never have succeed flashing any nbh (spl, custom WM, radio, android)
in ppcgeeks, cokeman says ; if your vogue can still enter the bootloader, it isn't bricked yet.
so, i try with mtty to rescue the vogue.
After several test with mtty and run command task 28,
i get this :
Fill RSVD information for block 160 to 176
Click to expand...
Click to collapse
( this is my first bad block in android )
and unfortunately, mtty process stuck in this step. ( left this process for 12 hrs with no progress )
mtty command : task 29 can't process either. ( left this process for 12 hrs with no progress too )
another command to test ;
mtty command : set 14 0 ( succeed )
mtty command : set 16 0 ( succeed )
mtty command : task 8 ( succeed )
mtty can proceed any task except task 28 and task 29.
so, i think this bad blocks will have a serious impact in the future.
though my vogue can still enter the bootloader, but seems mtty failed to format the internal memory.
So do you think this was due to the number of times you flashed the device?
How many times (can you estimate?) have you flashed and/or re-sized partitions?
I'm wondering if it was just a faulty flash chip?
Could be different batch quality in the NAND's?
I had a Vogue (no longer with me) that would report a bad flash with 2.6.32 kernel,
but did not report any flash errors with a 2.6.25 kernel?
Nand has a limited number of writing cycle so it's quite normal that after a high number of flashing (or general use) you can't do it anymore.
The different results with partitioning is due to the check on start.
When you create a yaffs flasherase_all, the program create some check blocks for the fs and list them on screen only if they are bad (in this case it map on a different location), so if you change the partition size the blocks would be different.
There is no dependence on kernel, also the 2.6.25 is buggier in bad blocks detection.
Nand has a limited number of writing cycle so it's quite normal that after a high number of flashing (or general use) you can't do it anymore.
Click to expand...
Click to collapse
And as soon as serious that number? I think made I flash to my computer as a 200 times since I got it between WinMO to Android reading this I think that you I will do not more or by least not as often.
@Does_It_Matter
i used to flash kernel +/- 1-2 times a day, dirty estimate maybe about 100-150 or more (i dont count WM custom rom),
i can't remember exactly, mostly i resized the partition since loserskater rls nbheditor.
before i get stuck with the last kernel (it was a busy day with flashing kernel), i was on configuring the best size partition to fit the htc sense rom.
after porting the wildfire rom and give it to jholtom, i was porting the tatfroyo rom in tatto thread.
and XM rom (in dream thread if i'm not mistaken) to compare the size and performance.
but this bad blocks, is not rom related (cmiiw). It is more a kernel related.
in 26.25 i never get those problem, but since i try to find the best kernel to those rom.
several times i flashed the latest 26.32 kernel and get a lot of bad blocks and become worst.
in my opinion, re partition the kernel is not a very good idea ( i was force those rom to get fit both on nand, /system and /data )
but i could be wrong, maybe this is just a faulty chip.
@l1q1d
well, this is an old device, you right. that this device is already reached its life.
i just curious about this.
i never blame to the devs here. i was enjoying my time with all the stuff you all created. and giving me a lot of knowledge.
from playing with apk, xml, porting rom, never had a change to compile my own kernel (run out of space to install ubuntu beside XP).
I did not want to do any kind of criticism, I just wanted to explain the issue that unfortunately plagues this type of memories.
The problem is not related to the kernel or distribution but is inherent in the type of memory unfortunately
I am very sorry for your device.
hey, don't be sorry, i have already let go that vogue.
now i'm wating for a good price for desire. usually in the end of the year there would be a good price for phones.
iphone 4 still have a high price.
i'll miss having you around vellowax, thank you for everything
Yeah, thank you for your all contributions for us
I hope you can find the best phone you want...
Merry christmas And a happy new year...
Cheers.
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi, X11 and the touch screen sort-of working.
The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will be providing some demo images for people who don't have a build environment up and running. These images will not work particularly well, don't get your hopes up .
If you want to have a big linux installation (more than 3 GB) you can flash the images to the second partition on your external sd (obviously you have to create this yourself first). You can use the following boot image (which assumes that linux is on /dev/block/mmcblk1p2 with ext3:
https://ha.xxor.net/o2x/boot-20110813.img
I have also targzipped the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x-20110813.tar.gz
This should be extracted directly to the root file system.
The kernel source code is up at https://github.com/ergoen/LG-Optimus-2x-linux-kernel
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbd recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. At first I thought the problem was that the refresh rate was set to 106 Hz, indeed changing it with xrandr and pushing a new mode got me a visible xterm on Kubuntu 11.04:
https://ha.xxor.net/o2x/xterm.jpg.
On Ubuntu 10.10 it even gave me a nice colored gdm screen:
https://ha.xxor.net/o2x/gdm.jpg
But the image I got there was static and wasn't being updated. Turns out the reason the screen was black earlier with the 106 Hz rate and the reason why the screen is now just showing an image is that the framebuffer device doesn't update the screen like it should..
By modifying the kernel source to redraw the screen every 50 ms (~20 Hz) it's possible to get a scren that works. This is an ugly hack in the tegra-fb driver though, so I'm open for suggestions on how to solve it in a better way!
2.3. Touchscreen
By default the only thing the touchscreen does is force the mouse up in the left corner, I think this is due to some multitouch thing. Some more kernel hacking (basically half-disabling multitouch) makes the touchscreen work.
Pictures:
https://ha.xxor.net/o2x/SAM_0671.jpg
https://ha.xxor.net/o2x/SAM_0672.jpg
Video:
http://vimeo.com/27662093
Thans to RaYmAn and lilstevie on #tegralinux for all their help this far!
3. Misc
(K)Ubuntu 11.04 uses a new version of libc which crashes with the current nvidia kernel (2.6.32.9) on this hardware (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3), so I'm going back to Ubuntu 10.10 until someone ports a newer kernel to the Optimus 2x or this problem can be solved in another way.
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1.
edit 2: X11 working even more, touchscreen works aswell!
edit 3: Landscape mode works with both X11 and the touchscreen now, getting ready for alpha 1!
Current status:
Working:
- adb (best way of controlling device currently)
- X11 (only framebuffer with hardcoded refresh rate of ~20Hz)
- landscape mode fixed! =D
- touchscreen (probably only single touch)
- wifi (only when running things from console, ubuntus network manager does not recognize it)
Not working:
- Basically everything else
Alpha 1:
EDIT: Seems that multiupload has screwed up and this link was going to some crap, anyway this is not relevant anymore
Username 'ubuntu', password 'ubuntuxda'. Don't use this if you don't know how to restore the boot partition! (Or else you won't be able to boot back into android!)
Experiments:
Tried disabling the CONFIG_TEGRA_ERRATA_657451 switch in the kernel to make newer linux versions boot. This might be a bad idea in the long run, but this far things are working better than with the switch enabled..
I tried Ubuntu via chroot method posted in other thread, but I'm a noob.. Can you please explain what is different about your ubuntu?? Does it boot without Android and doesn't need VNC stuff?
Yes, it boots instead of android when turning on the phone, but it doesn't work completely, so I mostly put it up here so that people could help test and fix/hack things.
You rock! Unfortunately I'm no dev, so can't help but hopefully others will, so we'll get a fully working linux on our phone, and maybe later even meego. Is there btw drivers for the gpu? Because hdmi, with usb host ofc, would be really useful!
Anyway, good job, really!
This looks great ergoen! I'm no dev either but I can't wait until it's available to everyone, I would love to have Ubuntu running on my O2x.
Best of luck!
gpu drivers are closed source, and the ones released by nvidia require a newer kernel (2.6.38), so thats not really possible yet.
Newer kernel will be necessary anyway though, since the crashes I'm getting seems to be due to a bug in tegra which gets worked around in 2.6.36. I'm not skilled enough to perform that port though. I will of course give it a try, but most likely I'll go for some older version of ubuntu and/or perhaps meego instead.
Håller med tidigare poster. Would be awesome with native Ubuntu and Meego on the phone... keep up the good work, can't wait to follow this development.
Sent from my Optimus 2X using XDA Premium App
ergoen said:
... I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz...
Click to expand...
Click to collapse
What would happen if you changed this to 72Hz instead? I saw that info when I was browsing System Information in some app. Im not a dev At. All. But tell me what you think it's probably a stupid question
Sent from my Optimus 2X using XDA Premium App
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
ergoen said:
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi working, also X sort-of works (software fb). I have only slightly modified the kernel (built with CONFIG_SIGNALFD=y so that Meego wont complain in a related attempt to get that os booting). The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will not provide a complete root file system for two reasons:
1. It's pretty easy to make yourself, grab the omap3 kubuntu mobile image from the kubuntu site, or use rootstock from an ubuntu installation to build one yourself.
2. My upload sucks, and putting several hundred MB onto the interwebz would hurt me.
However, I have placed an image of my boot partition here (assumes you've got ubuntu on the second partition of the external memory card formatted with ext3):
https://ha.xxor.net/o2x/boot.img
I have also targzipeed the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x.tar.gz
This should be extracted directly to the root file system you aquired earlier.
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbdb recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. After some troubleshooting and voodoo magic I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz, and running it after xinit gets you a xterm!!!
https://ha.xxor.net/o2x/xterm.jpg
Telling /etc/X11/xinit/xinitrc to run it makes sure that it gets set up properly by the startx script, unfortunately startx doesn't go through for me on kubuntu because of some weird error caused by a hardware problem in tegra: (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3).
Unfortunately this (probably) means that either we'll have to stay with old versions of libc or get a newer kernel (2.6.36 contains fix). Old libc seems backwards, but porting a new kernel requires a bit more skill than I possess.
2.2.1. Ubuntu 10.10
Grabbed the image ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz from http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/release/ . After first unpacking the tgz, then unpacking the raw disk image to partition images (with 7zip on windows) and then flashing the 1.img file to the second partition on my sdcard I managed to run a much more bug free ubuntu than before.
Ubuntu 10.10 (Maverick) uses an older version of som libraries that don't crash with the old o2x kernel.
This has lead to the following:
https://ha.xxor.net/o2x/gdm.jpg
Obviously touch screen isn't working properly (pressing it puts the pointer into the upper left corner :S) so can't get further than this currently.
3. Misc
avahi-daemon and cups seems to be crashing all the time and restarting, so removing them (apt-get purge if ubuntu/kubuntu) will make the boot much cleaner. Also I get lots of alignment trap kind of errors that shouldn't be there for different kinds of services, (due to tegra bug mentioned earlier).
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1
Click to expand...
Click to collapse
Its good you got it to work.Saves me some work.I was gonna begin this project my self after the 19th when my exams end.Maybe i could help you.
ergoen said:
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
Click to expand...
Click to collapse
Most computer screens usually support atleast 72hz also, it's just that it only works with d-sub, and sometimes only at a lower resolution.. It's possible to make special drivers to some screens to enable higher refresh rate through dvi also.
Anyway, it's good the screen on the phone refreshes at 72hz instead of 60 for android, but in linux I really don't see the benefit.. Doesn't hurt to have though. Btw, if we would stay on this kernel, can we use the drivers from android then? Shouldn't gpu also work? Or are the drivers limited and don't allow xorg for example? Sorry if it's stupid question, don't have that much knowledge how android works yet.
Update: X11 and touchscreen work on Ubuntu 10.10 Maverick with new kernel (just a few hacks )!
manasgirdhar: sure! Lot's of things to do new kernel is needed for anything newer than ubuntu 10.10, and even here things like sound etc (cpu scaling maybe too) don't work.
kruppin: actually i removed the xorg.conf now, the phone thinks its running at 106 Hz and it works. Unfortunately in practice it goes at more like 20 Hz because of the hack I made to enable the fbdev output in the kernel. Android doesn't use X11, so those drivers wont be of any use. (I will post the kernel modifications to github soon)
edit: kernel source up on https://github.com/ergoen/LG-Optimus-2x-linux-kernel
A List of Things working at 2nd Post would be nice.
So anybody could fast see Updates,...
Edit:
Have you tried some "cleaner" Linux like Debian?
Alpha 1 is up in the second post for anyone who wants to test it (don't ^^).
I have not tried debian no, I thought ubuntu would be the easiest to google errors and bugs for .
You are great! i was hopin' for this since I have mine. You should try to make usb(otg) work to get some devices going i will try to test it soon
That's amazing We have to test USB OTG function. If it works by default, I'll try this right now
It is possible to make a dual-boot: ubuntu and android?
I don't think usb otg works since I am basically using the android version of the kernel, I also won't be able to try since I don't have a cable... (will buy one sooner or later).
Dual boot probably works if you flash the boot.img onto the recovery partition instead of the boot partition (/dev/block/mmcblk0p7 instead of /dev/block/mmcblk0p5). I have not tried this though. That way regular booting would give android and booting while holding volume down would give ubuntu, only problem with this is that cwm will be gone and the only way to fix broken things would be to flash with nvflash.
well it is not a major deal if have cifs avail needs kernel support as well. Benee mentioned (might) some otg support, mayb u could ask.
also, you might give E17 a try, it is butter-fast, and has a touch module for keyboard (letter zooming.!..) LINK
this can be compiled on a lot of hw, and gives good response with fbdev non-accel drivers also.
and most linux apps work on it fine. ofc until we have 2d/3d accel and might try compiz/fusion as well
LINK
Great job ergoen!
I've worked on exactly the same some weeks ago but i never accomplished it. because i stuck creating a working ramdisk. Which toolchain do you use?
MfG
Backtrack5/Ubuntu v10.04 Up & Running On Tab 10.1
StatementHave this on my Samsung Galaxy S2 and working perfect so i figured i would give it a try on the Tab 10.1. There were alot of people who helped get this running for other devices i will mention them so dont worry. Alot of modifications had to be made in order to get this to run on the Tab because it was really made for a phone not a tablet so please follow all the steps cause there is certain code that i had to right to get the screen size to fit. Everything is fully functional and working. Finally i think this would be a nice addon to your Tab esp if your a big Ubuntu fan, I am currently working with other developers to see if we can update this so it has the new Ubuntu v11.10 but for now follow the steps and enjoy and if theres any questions or requests just write on the thread and PM me. ENJOY!!!
Disclaimer
I am not responsible for damaged devices, bricked devices, Soft bricked devices, and if you run wrong code ETC
Thanks To:DooMLoRD, anantshri, n1nj4dude, KingOfThaJungle None of this would be possible without these guys and if im missing anyone please let me know and im sorry
Before We StartThere are going to be 10 files attached at the bottom you need to download all 10, place them on your desktop for now i will explain what your going to do with them after. Next you need to download 7Zip heres the link http://www.7-zip.org/download.htmlOk now those 10 files waiting on your desktop extract ONLY 1! i chose to extract bt.7z.001 once you extract you will be given a .img file create a folder called bt and put all ten of the files inside bt including the .img so you now should have a folder on your desktop called bt with 11 files in it. Take this folder and put on the root of your Tab.Now there will also be another file attached called bt5_sgs2_shell_scripts_v2 take this file and put it on the root of your Tab. Reboot into recovery mode and wipe cache and davik cache and then flash that file once complete reboot your Tab.Once your rebooted use some kind of file explorer i used root explorer and check the /sdcard/bt folder for the following it should look like this when you explore it./sdcard/bt/bt/sdcard/bt/bt.img/sdcard/bt/installbt.sh/sdcard/bt/startbt/sdcard/bt/stopbtOnce your verify that the above if correct you can proceed
Instructions On Launching BTStart Terminal Emulator on your Tab and enter the following commands step by step.sucd /sdcard/btsh installbt.shstartbtbtNow your in Back Track 5 shell! You should see [email protected]:
Instructions On Launching VNC ServerDownload VNC Server from the marketThen still in terminal typevncserver -geometry 1280x700You then will be presented with [email protected]: againThen look under it were it says new 'X' desktop is localhost1 that it the last digit in your port number if you ever exit VNC or close terminal or reboot you will have to run some commands to get back witch i will show you in a minute but always look at that localhost # cause it will change if you reboot so pretty much if it says localhost2 your port would be 5902 get it?
Now Launch AndroidVNCEnter the following into AndroidVNCNickname: btPassword: 12345678Address: 127.0.0.1Port: 5901Username: (Leave Blank)Color Format: 24-Bit Color (4bpp)
Getting Back In After RebootType the following commands to get back insustartbtbt
Screenshots & LinksAt Bottom Thank you and Enjoy!!!
Go to this page for the 10 files http://www.mediafire.com/?f9gk3p3t9wip5
Uhm... file bt.7z.001 is corrupted!? Please check. However, thank you.
go onto the original thread and get the files from there sorry i only posted the mirrors heres the link and your welcome hope you enjoy
http://forum.xda-developers.com/showthread.php?t=1331419
Haven't tried yet but looks great, sweet!
works good. nice guide. i suggest people download bt5_sgs2_shell_scripts_v2 from the link in the 3rd post
Cool. Does the wireless "card" in this device support injection?
FillTheVoid said:
Cool. Does the wireless "card" in this device support injection?
Click to expand...
Click to collapse
I would love to know this
Sent from my GT-P7510 using Tapatalk
i believe it does but im not 100% on that
I cannot get this to work. Every time I try to install the bt5_sgs2_shell_scripts or bt5_sgs2_shell_scripts_v2, it says installation aborted. Needs to be Nandroid restored otherwise it won't boot. Any ideas?
So can i use both of honeycomb and ubuntu alternatively or together? Because in screenshots i can still see honeycomb taskbar at bottom over Ubuntu.
Nice work. And how to uninstall it?
Ok for JAYDAWGX7: are you wiping cache and davik cache before flashing and is your cwm up to date? if so and still having problem try a different kernal and get back to me
Ok for PARAG31: yes you can run bolth all backtrack5/ubuntu is doing is running threw vnc you are not loosing honeycomb you still have that as a base platform backtrack/ubuntu is just running threw vnc so to answer your question this does run bolth
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
celtichazard said:
I try with two diferents kernels and roms first task650 in paris v5 and other with task650 new honecomb 3.2 stock and no luck to install the zip file in recovery instalation aborted allways display. please post your roms and kernels info to migrate and run this on my gt
Click to expand...
Click to collapse
Yep, same problem here. Any ideas? Any one else try this?
P7500 running Overcome 10.1 Rom, with Pershoot Kernel 2.6.36.4, with CWM v5.1.2.3. Yes with wipe of both cache.
EDIT:
After further investigation, the zip file only contains the files found in the bt folder. Just extract it to the /sdcard/bt dir. Assuming that it makes no other changes to system.
Got to [email protected], haven't done the rest yet! Will update post later.
EDIT:
Everything works after this.
Plus, i dont think monitor mode or injection works. Not without modified drivers (STILL HOPING ITS NOT THE CASE). Maybe usb? Hows usb hosting on this? Hope someone can answer these questioms.
I have a compatible wifi adapter, but no usb adapter for the tablet! I'll put it on my buy list.
Will this work on the 3G version also?
Edit: Awesome! It works perfect, thanks! Only remember to have busybox installed guys!
The correct resolution is 1280x752, so it is : "vncserver -geometry 1280×752"
also ur script isnt flashable. only thing in /data is busybox, just install busybox from market and change script
will work on 3g and wifi versions
very nice, also works on GTab 7310 (8.9 Wifi 3g)
heaven, thank you!
Awesome, works like a charm, and it blows everybody's mind.
I spent a little time on try to get capture mode to work, but gave up with the original network drivers.
I hoped it would be possible to use a normal usb wifi stick connected to the adapter, compile the drivers, and load them as modules, but i'm getting error messages when doing that, and that's where my knowledge of linux ends.
Anyone tried this yet? Any pointers? (currently flashing overcome 2.0, will try to post errormsg later)
Also, I read in one of the CarrierIQ threads that one of the pieces of the app actually uses libPcap to snoop on our asses. Would it be any help (or problem) that that's enabled in the parent OS?
Just one question: Can I use bluetooth keyboard/mouse with it? And will TrueCrypt run?
Easy way to speed up your phone
Install instructions:
1. Install Root Explorer
2. Download boost.zip file and then unzip the that file and put in the SD card...
3. Open Root Explorer (Mounted on R / W) / SDCard / menu button / Multi-select / chose boost / Copy / system / bin / then click paste...
4. Open Terminal emulator and taype:
su
boost
5. Your phone is turbo boosted now, enjoy in new speed on your phone...
6. Press thanks if you like my work...
7. Rate my thread...
And what exactly does this "Turbo boost" do?
Have you got any benchmark results or evidence of an performance increase? I'm not giving an program/script root access to my phone, without some proof of an increase.
Upon opening the file with Notepad++ all it had inside was this
#!/system/bin/sh
# Adrenaline Boost
# Brought to you by [email protected] Developers
sync;
sleep 1
echo "3" > /proc/sys/vm/drop_caches;
sleep 1
echo "1" > /proc/sys/vm/drop_caches;
sleep 1
echo " ** Turbo Boosted ** ";
Click to expand...
Click to collapse
Which after some googling found out it does (from a similar script for desktop Linux):
Writing to this will cause the kernel to drop clean caches, dentries and inodes from memory, causing that memory to become free.
Click to expand...
Click to collapse
nejc121 said:
And what exactly does this "Turbo boost" do?
Click to expand...
Click to collapse
Your phone will be faster and working bether...
I just get permission denied in terminal.
spudata said:
I just get permission denied in terminal.
Click to expand...
Click to collapse
Did you type in "su" before "boost"?
Yes, granted su permissions but no joy.
Same thread posted on the i9000 development area. wth
Sorted, had to change permissions of boost file
Can anyone confirm this to work?
Sent from my HTC Desire using Tapatalk
RESERVED.
installed, will update tomorrow with any feedback.
UPDATE: have found it runs pretty much same as V6 Supercharger, drains battery horribly though.
I was on 54% battery last night, data & wifi off and killed tasks before going bed.. I checked CPU Spy, it had been in a deep sleep state for most of the night.
I awoke to a dead phone, which doesn't even happen on the v6 supercharger!
How do I uninstall this script, can I just delete the file from bin?
I tried this but I see no difference ... should i restart the device?
cm 7.2 rc1, smartassv2 264-710 MHz
edit: rebooted the phone....still no difference.....
To really see the benefits of the boost, you need to change the file permissions. Go into a root terminal and type:
chmod +t boost
This gives the boost Time Travel permissions. Now, all processes will be completed before you even run them. Talk about a turbo boost!!
Also set the date of your phone to whatever you want the open the dialer and type "#"#7925#"#" and you'll be timewarped into the future.
Sent from the year 2019 using my years old HTC Wildfire using xda premium
Ok just done a little digging around the op's other thread (which is now locked by a mod) on a different forum as he hasn't exactly explained what this does in any of them which leads me to believe he doesn't exactly know, and probably copied it from someone else, http://forum.xda-developers.com/showthread.php?t=1542602
What this does is clear the cache filesystem. 3 = free pagecache, dentries and inodes, while 1 = just free pagecache. Which in theory will decrease battery life as the cache needs to then be rebuilt afterwards.
This is already included in v6 supercharger so no need to use this if you have v6, just perform the engine flush or whatever its called whenever you want to free up some memory stuck in cache files. Its basically the same thing according to other users, I haven't looked to see if thats true or not but they sounded like they knew what they we're talking about so i believe them.
GlennBrownie said:
UPDATE: have found it runs pretty much same as V6 Supercharger, drains battery horribly though.
I was on 54% battery last night, data & wifi off and killed tasks before going bed.. I checked CPU Spy, it had been in a deep sleep state for most of the night.
I awoke to a dead phone, which doesn't even happen on the v6 supercharger!
How do I uninstall this script, can I just delete the file from bin
Click to expand...
Click to collapse
??
Yes delete and reboot.
Sent from my HTC Wildfire using xda premium
SeeZaar said:
Easy way to speed up your phone
Install instructions:
1. Install Root Explorer
2. Download boost.zip file and then unzip the that file and put in the SD card...
3. Open Root Explorer (Mounted on R / W) / SDCard / menu button / Multi-select / chose boost / Copy / system / bin / then click paste...
4. Open Terminal emulator and taype:
su
boost
5. Your phone is turbo boosted now, enjoy in new speed on your phone...
6. Press thanks if you like my work...
7. Rate my thread...
Click to expand...
Click to collapse
yea, 1star rated as u just copy my work.
Moreover, u didnt give full description and spoiled my fame and work, this should be useful for everyone if they know how to use tis properly
Thread closed as the OP DOESNT have permission fro yhe dev yo post this.
Also he failed to provide credits.
This on XDA is kanging and is not tolerated!!!