Develop Bugs

[27.05.2010 Neopeek][ANDROID Froyo + Eclair + Ion] ext2-filesystems - NoSquash

Hi all,
just wanted to let you know that i succeeded in putting Android on EXT2 of internal memory.
As I am also involved in Projects like MeeGo, Bada & Others you may contribute to this builds and help me making this builds better. I will post all Project updates here but as stated above I will more frequently visit my own website due to the other Projects. If you need urgent support in this builds you may leave me a message on my website.
Please have a look at my website if you are interested in contributing.
My Website: Contribute Android
UPDATE 27.05.2010: View original article: Android Froyo Eclair Ion Builds
Why moving to ext2 filesystem and leaving root-filesystem contained in squash / image files?
A squashed / imaged root filesystems had to be unsquashed til now if you ever wanted to make changes in them! Therefore all files could be placed directly into the root of your memory (commonyl FAT32).
ext2 is a linux-only filesystem and you will have to get some tricky tools to get it read in Windows. But in Linux you have now the possibility to write directly into files or even update the filesystem as you want. Possible scenarios are placing archives into it to update Android and so on.
We think that until now a lot of users had problems with the squash filesystem and expect to contribute more users to Android-Porting with ext2. Squashfstools won't be needed any more.
If you are an unexperienced user or don't know how to get a virtual system with Ubuntu running:
Don't hesitate to ask us in the communiyt for help. Now let's start:
Step 1: Partitioning your memory!
Please install Gparted in Ubuntu and partition your internal memory (Diamond) or SD-Card (other devices) as seen below in the screenshot (1 x Fat32, 1x ext2, 1x linux-swap):
{
"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"
}
Step 2: Extracting files onto ext2
* sudo umount /media/disk-1 /*Notice: this could also be something like /media/disk or /media/disk1223-dsf232 etc.! You have to locate the ext2 filesystem which you have partitioned above */
* sudo mkfs.ext2 /dev/sdb2
* sudo mkdir /media/neopeek
* sudo mount -t ext2 /dev/sdb2 /media/neopeek
* sudo tar -xzvf ~/Desktop/neopeek_android.tar.gz -C /media/neopeek /* Alternatively: Neopeek_Android_2.1.tar.gz oder Neopeek_Android_Froyo.tar.gz */
* sudo umount /media/neopeek
Step 3: Extracting files onto FAT32
Download HARET-Paket.zip including latest Kernel. Extract the contents directly onto the root of the FAT32-Partition. That'S it! Unplug your device / sd-card and run Android by executing "HARET.EXE".
Download Android Froyo Eclair Ion
So that's my birthday gift for myself and for you. If anyone wanna make me a gift then move to my site and register / connect to get the latest updates by mail before they appear here and to support my upcoming website!
[/B]
Thanks goes to: XDAndroid-Project, Balsat for the latest builds and many others. You know who you are!
Build notices: Based on XDAndroid's and Balsat's autobuild service for rootfs and kernel. Special thanks go to Balsat for introducing EXT2
Android Ion has buggy WiFi but runs like Myn's Donut!
Android 2.1 runs better for me on ext2. It's the XDAndroid build. On ext2 I can watch videos without stuttering. It's a little bit smoother for me. Test it out!
Android Froyo: This is for the freaks of you! Unproductive / Instable but worth a try hrhrhrrr!
Again i will state this here that it is clear for everyone: This builds are not mine cause I think some of you may think so. The build rootfs is made by Balsat but I have written an tutorial for you and republished builds so that you can get it working with EXT2. The HARET-Packet is modified by me as I couldn't find one from Balsat. Also I will provide you with support / help on how to partition your memory correctly. Especially windows users and beginners will need this support. In the next days / weeks I will port / cook further Android builds on my own and again this will be EXT2.
This thread is intended for introducing EXT2 for all of you who didn't know that it was possible. I either didn't knew it and no one informed me about this. Sure, I inform you!
For anyone having problems with partitioning: Try using fdisk command in console! This should look like this for your $GB internal memory or SD card with equal capacity:
sudo umount /dev/sdb1 or /dev/sdc1 (also sdb2 / 3 if exist)
sudo fdisk /dev/sdb
Press "d" to delete partitons
Select "1" (redo this if you already had mislucked tries with selecting "2" and "3")
Press "n" -> then "p" -> then "1" -> press "enter" -> type "600" or type "+1500M" -> press "enter"
Press "t" -> press "1" -> press "b" -> press "w"
Now you should have partitioned a FAT32 and can use GPARTED to create ext2 and linux-swap (notice: linux-swap-creation only needed for future builds and for testing. No need to create it if you don't wanna test)

Reserved for updates
Reserved....

reserved for updates Part2
Reserved2...

Looking forward to seeing it! I sense a wave of donuts coming...
Also, happy birthday!

Good luck. I hope this time we can have the android.
count on you.
respects

I hope so to,
Will this build have a good battery life so we can use it daily as OS?
Good luck and happy birthday!

good luck and happy birthday

Happy Birthday! We hope that the "diandroid" very fast and stable rom will!

Looking forward too it! And Happy Bday!!

very good man and happy birthday to you!!

do you have a link for your android 1.6? I am looking for a 1.6 w/ working wifi. not found yet. Thanks!

hao214 said:
do you have a link for your android 1.6? I am looking for a 1.6 w/ working wifi. not found yet. Thanks!
Click to expand...
Click to collapse
look arround, on all builds wifi is working, dont be so lazy
vatoloco haerzlichen glueckwunsch zum geburtstag
gruss

Happy Birthday to you.. Man this is best news I have heard in last one and half years !!!
Really looking forward to it. Will definitly test it for you even if its unstable

Can't wait to try your Android build =)

happy birthday

Happy birthday!..waiting for your release

There are already working android avaliable ? Like the one shown in above signature ?

Trying
Hey men...
Im trying your build but i cant synchronizing with my google account...
Anyone have the same issue?

which build are you trying??????????

suhas_sm said:
There are already working android avaliable ? Like the one shown in above signature ?
Click to expand...
Click to collapse
of course..there is XDANDROID,Myn's Warm Donut (the fastest bulid i saw),there is glossy android,Klinux's sense bulid and many other....you can find it in the raphael's android forum or in the blackstone's android forum or here

NBH Editor v4.1

I'm no longer updating this! All of the new changes have been pushed to the atools version. L1q1d is going to be taking over from here on out so check out his thread HERE.
Here's an editor to select which settings you want for your nbh!
All this does is hex edit different things, including the cmdline info, like you could do with a hex editor. It's just a lot more user friendly.
Disclaimer:
I'm not responsible for ANYTHING that happens to you, your phone, or your computer. I would not release something that intentionally harms a computer or phone, but there's always that chance when using unofficial software.
______________________________________________________________________________________________________________________________________
What everything means:​Device:
-Vogue: LINK
-Kaiser: LINK
-Polaris: LINK
Resolution:
-240x320: The native resolution on these devices. Will give the best overall picture quality.
-320x428: The smaller version of the 320x480 that fits our screens better.
-320x480: The native resolution for the G1 and most 1st gen Android devices. Things will fit better as they aren't scaled down, but everything will look blurry/squished.
Version:
-This is the Android version. Be careful not to get it mixed up with a user's release version. Most builds say either Donut, Eclair, or Froyo, but if not then you can install the system and look under Settings>About Phone and look under "Android Version"
-Donut: 1.6
-Eclair: 2.1
-Froyo: 2.2
Panel Type:
-Only Vogues have auto panel detection, so for Kaiser and Polaris users you will just have to pick one. If there's weird pixels, things don't look right, sleeping issues try a different panel.
Keyboard Types:
-Look HERE for more info if you don't know which keyboard type.
More Settings:
-ppp.nostart: If you set this to 1 it should prevent data from starting on boot. Helpful for some people but if you don't have to worry about data then leave it 0.
-CPU Overclock: This uses the same method that myn uses with Rogue Tools. Our CPU's are set to run at 400 MHz, but we can overclock them to over 500 MHz. I would suggest not going over 500 unless you know what you're doing, but some users have reported running at 550 just fine. It could decrease your device's life expectancy if using constantly, but probably won't notice for quite some time.
-System/Data Partitions: You can use this if running system or data off an EXT2 partition to use all of nand. Also helps when using an older Sense build that needed a larger system partition.
-Disable Vibrate on boot: Check THIS POST for more info on that.
-Battery Capacity: Self explanatory.
______________________________________________________________________________________________________________________________________
How to use the Editor:​
WINDOWS, MAC, LINUX:
1. Download python (Version 2.7)
2. Download editor from below.
3. Download the nbh for your phone
a. from DZO's SITE
b. Download the latest one using the editor
4. Open the NBH from the editor
5. Change any settings
6. Save new NBH
7. Enjoy your new nbh
Don't want to install python?
1. Download Windows NBH Editor.zip from below
2. Extract to where you'd like
3. Run nbheditor.exe
Last but not least... Thanks! I've said it all before but this wouldn't be possible without the mighty one, DZO. Thanks to DZO, kallt_kaffe, myn and l1q1d for pointers, and all the other devs that are helping get these what should have been extinct devices back to life!
To Do:
Taking suggestions!
{
"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"
}
Windows NBH Editor.zip
UPDATES
DOWNLOAD!!!(Right Click>Save As...)

loserskater said:
(I spoke with kallt_kaffe and his will probably work soon.)
Click to expand...
Click to collapse
I've posted new a new version that should be compatible but when I change an NBH (Kaiser) to donut the hw3d.version becomes 01 and the "1" overwrites the space what should be after the "0". Setting an NBH to eclair seems to work though. Haven't tried the same with DZO's NBH though but the result should be the same.

kallt_kaffe said:
I've posted new a new version that should be compatible but when I change an NBH (Kaiser) to donut the hw3d.version becomes 01 and the "1" overwrites the space what should be after the "0". Setting an NBH to eclair seems to work though. Haven't tried the same with DZO's NBH though but the result should be the same.
Click to expand...
Click to collapse
Thank you! New zip should have it working now.

loserskater said:
Thank you! New zip should have it working now.
Click to expand...
Click to collapse
Confirmed, seems to work now.

OK, so how easy was THAT?.. Thanks!

New version posted. Now just one program.
You still need to select the NBH for your device.

Excellent work dude, truly the most useful pre-install software, makes setting up everything so easy, intuitive to use too.

Hi Loserskater,
Thanks for your very good job and to help us to use much better our phone with android
Cheers.
loserskater said:
The moment you've all been waiting for... ok, well maybe just a few of you. Here's an editor to select which settings you want for your nbh!
Click to expand...
Click to collapse

Can you also include battery setting (option: experimental) ?

robuser007 said:
Can you also include battery setting (option: experimental) ?
Click to expand...
Click to collapse
That's something DZO will have to do... unfortunately you can't add things to the cmdline of the nbh or else it wont work right. it will have to be added to the source. If I can convince dzo to add it, I will add the option to change that value for other batteries. For now, you can try kallt_kaffe's nbh.
His also work with this editor

loserskater said:
That's something DZO will have to do... unfortunately you can't add things to the cmdline of the nbh or else it wont work right. it will have to be added to the source. If I can convince dzo to add it, I will add the option to change that value for other batteries. For now, you can try kallt_kaffe's nbh.
His also work with this editor
Click to expand...
Click to collapse
Scratch that. New update now includes ability to add default settings (like in kallt_kaffe's) for battery, clock, and ppp.nostart. I just flashed successfully but I haven't had much time to test.

Can now use either kaiser nbh or the vogue nbh.

Hi guys,
Sorry... I might have miss it.
Can someone explain what is the panel different?
I am using HTC Kaiser.
Thanks
Daniel

Re: Loser's NBH Editor v3.0
It just depends what panel you have. The only way to tell is by trying each one. If you get weird pixels then thats the wrong one. I havent found any difference between panel 2 and 3 though...

Apparently there are some differences in the way panel 2 and 3 handle power on, power off, there have been a few reports of white streaks on waking up the lcd by some users on panel 3 using panel 2 settings.
This is not definitive though, since panel3 seems to be pretty rare.

You could set other default settings, like panel2 (most used I guess), I never tried another panel.And eclair for the other default setting (most used nowadays I guess).
Maybe you can add comments (like use 1.7x radio and hardspl 3.34 before flashing and use kernel from...) to make it completly idiot proof (and have less questions here on the forums).
Great work anyway.

Re: Loser's NBH Editor v3.0
You could set other default settings, like panel2 (most used I guess), I never tried another panel.And eclair for the other default setting (most used nowadays I guess).
Maybe you can add comments (like use 1.7x radio and hardspl 3.34 before flashing and use kernel from...) to make it completly idiot proof (and have less questions here on the forums).
Great work anyway.
Click to expand...
Click to collapse
That's a good idea. I'll change those settings to the commonly used ones and maybe save settings on exit so you don't have to do it each time. And add more info in the actual program. Thanks for the input!

Probably will try with Panel 2. I am using the SD boot with Eclair right now.

Re: Loser's NBH Editor v3.1
What would be some things that people would like to see added to this? I was thinking about making it possible to change cpu and gpu OC settings. And maybe battery settings. Can anybody think of any other cmdline settings?

I don't have any suggestions, just wanted to say thanks for the great app. Very convenient.

Android x86 working build. [no sound compiled, and bugs, wifi and fun working )

I just found http://www.androidx86.org/ and took the time to break the dsk and the iso images to build a boot.ini via grub sitting in a directory on the disk version.
Really all you need to do is winimage the dsk from the tar.gz and then grab all the files and setup grubldr in boot.init
Anyhow It booted! On my two laptops I generally get wireless (not stable), and no sound, and vesa, maybe nvidafb on m200. The ibm t60 shows hda_intel on lsmod but files seems to be missing. The m200 didn't mention sound in the console output. The graphics didn't work on the high end (black out), but vesa did. Standby doesn't seem right but thats likely google standby behavior on a unit in gimp mode. I took some video of it running on my laptops need to upload it somewhere. I will join the x86 forum here in a moment. Just wanted to share the build here. Wish it had audio.
I don't think the android build is as advanced as what is here on the phones so development wise I'm curious if I can swap the system files from the phone to the latop but homework calls. I'm uploading the build now it says 200 minutes on my very slow connection.
Can I just say download mssmissions system.img and run the system.img or will binary-arm stuff throw me thus I need to pretend I am a gentoo user and compile stuff or is it all python and java and intependent in the system.img?
Can I merge an ubuntu and android?
Any pointers as far as setting up a dev enviroment within android? You can also run android.iso vrom virtualbox and I'm pretty sure you can tweak it to get sound but I got none if anyone is interested in that. If anyone can give me any kernel advice vs compiling known linux drivers that be nice. Can i confidently think it'll work cause I have generic linux sources. Any sage advice for ati x1300 driver or a nvidia g5500 mobile card? Also my waacom didn't work on my tablet . I just wanted to post the build someone mirror it?
When its done uploading I will edit this.. Don't want the message to time out..
I was very impressed by the browsing speed of droid on the machines...
I just sent a pm to a mod who will move this thread.

dam thats actually pretty legit lol

Drool.
Thanks I thought so too! I just found http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html and my. I need to study :| android crack is bad. But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Download Donut prebuild. Edit boot.ini and reboot
http://rapidshare.com/files/401173367/android-system.rar.html
OR!!!!!
Download this to build your own.
http://grub4dos.sourceforge.net/
http://www.winimage.com/download.htm
http://iweb.dl.sourceforge.net/project/grub4dos/WINGRUB/WINGRUB 0.02 Build 6/WINGRB0206.EXE
http://www.androidx86.org/downloads.html
http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html
(I don't think you'll need the iso, get the usb disk, but the iso is cool cause it boots in virtual box. I'm having sound issue but it looks like it is loaded. )
extract android-system from android.img from gz and put into c:\android-system
download wingrub. Run it tell it to copy stage files.
C:\grub is created
edit the attached menu.lst or use the one from the android.dsk.. Copy the splash screen.xpm.gz from the dsk root to android-system, or wherever and reference it appropriately in menu.lst.
my boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
C:\wubildr.mbr = "Ubuntu"
C:\grldr="Start GRUB4DOS"
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
notice the grldr, Recovery Console, or Ubuntu is not necessary. After you install wingrub you can copy grldr to the root of the c:\ drive. Grldr is in:
C:\Program Files\WinGrub\GRUB
there is a file called grldr_p12 rename it to grldr and put at C:\grldr
my menu.lst in c:\grub
root (hd0,0)
splashimage=/android-system/android-x86.xpm.gz
timeout=600
title Live USB - VESA Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet vga=788 SRC=/android-system
initrd /android-system/initrd.img
title Live USB - Debug Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode vga=788 SRC=/android-system DEBUG=1
initrd /android-system/initrd.img
title Live USB - Run Android-x86 without Installation
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet SRC=/android-system
initrd /android-system/initrd.img
title Installation - Install Android-x86 1.6-r2 to harddisk
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-system INSTALL=1 DEBUG=
initrd /android-system/initrd.img
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
As far as differences in the directions to build your own or to just download the donut prebuild, I made the build I put grub in C:\boot\grub this is not the default. Wingrub installs the stage files to C:\grub by default so in the directions I went that route. I know it works either way cause I just redid that portion following my directions and it gave me stable mute android with wifi for about 30-50 minutes. Thats the only thing different between the build and the directions, and I believe if you move C:\grub to c:\boot\grub it would still work as they are booth search path for grldr.. Anyhow..
Or go download the cdrom iso's and burn it to cdrom/usb

hehehe
I've now entered all my bugs at:
http://code.google.com/p/android-x86/issues/list
here are some screenshots..
http://code.google.com/p/android-x86/wiki/ScreenShots
{
"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"
}
Looks promising if motivated:
http://code.google.com/p/android-x86/wiki/CustomizeKernel
eclair install not going so well initrd.gz referenced but not included on usb image. downloading iso which is good to have anyways for virtual boot in virtualbox. I hope initrd.gz and kernel are in there, but sadly they are older too. So donut maybe better after all. I'm waiting to test eclair. The donut kernel addresses system.sfs the eclair references system.img perhaps i should convert the format : I would try to do a rename but I am downloading the iso.

What does it have common with kaiser on android???

It it relates. It's like sql.
Select Interest from community where Tangent=Related
Okay man its a stretch. I just got excited at the prospect of running android on my other hardware. I should migrate my tangent babbling soon. I shouldn't even be working on this at all. I.E. what does this have to do with physics ii?
Duh.
But, when I saw it I thought ok great I boot android I'll be better able to work on android builds here maybe help out with the phantom haret issue all you l33t experts ignore. I.e. the last post about me not being up to date on stuff is crap. Seriously goto the n00b thread and fix my haret issue with instructions as clear as these..
Also kernel compiling is kernel compiling. I should go to the pure android forum and will move there I guess. But playing with this makes it much easier to work with kaiser droid. From what I've been reading it also makes me wonder about kubuntu and droid as booting android from ubuntu on os86 was mentioned and the kernel compile process seemed straight forward, so it may work? Making it work on my system I could then download all the dev stuff and maybe spew out a cross compile; but then again I'm not some sort of gcc guru. I'm just trying to get to know it is all? Why you downing me brah?
Also this build looks way less advanced maybe I can get some kind of merge on the sources here for the benefit of my 86x. It's funny how sound is an issue on 86x as much as it is here and even that says hey maybe in the 86x world with a keyboard and mouse could soomething so generic be fixed on 86x that it fixes a kaiser issue? But I agree were now in tangent territory. Need to find a better home and give it a link in a more suitable audience/ stronger relationship area.. I mean the affinity isn't that much higher.
I just got done building the last boot.ini grub environment. I'll leave it on that note and find a better place to continue this and link this to that and start over if i continue this work/effort. I just like people in this forum so I wanted them to benefit from my download. But I only was so stoked because I forget how easy it is to download an iso and boot from it when I have to do something else cause my m200 doesn't have a cdrom. Anywho..
-----
http://rapidshare.com/files/401231657/AndroidX86_2.0_and_1.6.basefiles.rar.html
move everything in the archive to the root of C:\
Download (From: http://code.google.com/p/android-x86/downloads/list)
AndroidX86-1.6: donut
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-1.6-r2.iso&can=2&q=
AndroidX86-2.0: eclair
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-eeepc-2.0.iso&can=2&q=
Open the each iso (WinImage, Winrar, MagicIso, or other iso program) then extract system.sfs and place it in its respective directory under grub
(i.e:
android-x86-1.6-r2.iso extract system.sfs from iso and put in C:\Grub\android-donut
android-x86-eeepc-2.0.iso extract system.sfs from iso and put in C:\Grub\android-eclair )
Edit boot.ini to include:
C:\grldr="Start GRUB4DOS"
Happy booting!
Alternatively:
You can of course boot the iso's using virtualbox
Go here: http://code.google.com/p/android-x86/wiki/Releasenotefor20091024dailybuild
for any more info or to report a bug about it.. I'll bet I don't work on this for a while..
-----

I find this interesting, and somewhat relevant, at any rate it looks fun to play with
I may have to experiment with this myself, lol, wonder if it'll work on my spare laptop? ........
Good find Tyler

also a neat find..
http://forum.xda-developers.com/showthread.php?t=553366
Looks like emulation is horrible. Thats sad its a linux kernel and it has a host someone needs to paravirtualize android? I'm reading the android thread it seems like alsa sound should just work so I'm being a ninnny nanny by not compiling stuff into the g.d. kernel, yet bug reports are abundant for lack of certain functions on different devices. grr.
This thread maybe moving soon to:
xda-developers > Android Development and Hacking > Android Software Development ?
bummer the emulator doesn't work well.. I wonder if the x86 kernel does virtualized arm support, someone need to do that...
man this is a distracting bummer. I have to compile a kernel.. I just installed a grub ubuntu too , I need to see if I can just start android in that no matter what, I may get lucky.. maybe even luckier if someone will hook it up in the other thread ..

tyler51773 said:
But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Click to expand...
Click to collapse
I made a working android-x86 alpha eclair 2.1 build with gapps. Designed for aspire one but also should work on vmware and vbox. Will boot and work (somewhat) on most computers (built with generic kernel config so all available .ko drivers are there) however you may have to modprobe the drivers for ethernet and wlan for your hardware. http://www.aspireoneuser.com/forum/viewtopic.php?f=90&t=19299&p=116492&hilit=aoa110#p116492
Make a bootable usb with unetbootin from the .iso is the best way to use it and you can install to hdd too from it.

Password?
just wanted to give the above aspireone-x86 build a try but the rar is password protected?

Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)

{
"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"
}
Android on your Windows Mobile HTC Device...
Supports Blackstone, Diamond, Diamond 500, Fuze, Raphael, Raphael 800, Rhodium, Tilt 2 & Topaz
This thread is dedicated to FroYo, and NOT Eclair releases!
First things first, this post is PURELY an instruction guide for noobies that aims to reflect the latest status and downloads (give or take a day).
I am not an Android developer, I do not create any of this software... this is done by far more talented people than I. This thread is purely to collate the latest info for Android on Windows Mobile HTC devices and make deploying Android on your device as simple as possible.
If you have new information that should be added to the guide (and is relevant for ALL folks) then feel free to add to the thread and I'll update the OP frequently.
These opening few posts should have ALL the latest info you need to get started (no need to trawl through the threads).
The only time you 'might' need to look in the thread is for 'breaking news' info that is no more than a day old...i.e. The Opening Post is the place!
Credits: There are too many to mention, and many are unknown, but basically the guys poring Android to our devices should be thanked, along with all those making the effort to help others test, document, or use their work (along with those who provide answers to the same questions, time and time again). These are the guys who deserve the credit. From memory...
osamaa,
babijoee,
phhusson,
herpez
scanny
klinux
Oliwe
and many more
What's New?
Latest Update: 03 Sep 2010 (V1.6)
InitRD - 20100813-b11116a
Rootfs - 20100828-c29a486
System - XDAndroid 2.2.AOSP.3.9.10.RC.2.2
Kernel - 20100830_01302 (no debugging)
Headset support - Credits to Oliwe
3D support for Blackstone/Diamond/Raphael (Rhodium/Topaz have no 3D)- Credits to Oliwe
Gallery working - Credits to Oliwe
Touchscreen Calibration is back! During first clean install, touch each of the five calibration points CAREFULLY to calibrate your screen before installation completes. Plus, general touchscreen fixes and power off support - Credits to Oliwe
Back to basics System... stock Android system.
Takes about 5 mins usage before the system starts to speed up, so expect it to be a little sluggish for the first 5 mins.
None 3D devices may not show boot screen, so please be patient during install (screen will show black)
I'd advise that once installed, you also launch SpareParts, and configure the window animations etc to 'fast'
There is a chance that after installation, some Startup.txt settings MAY be incorrect for your device. If you discover any mistake, PLEASE let me know, I will correct asap. I need your help on this guys.
How To Install (CAB Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and install the CAB
Download and install the following 'full package' cab (a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid Cab button below.
You MUST install on the Storage Card. The cab file will take a couple of minutes to install Android. Please be patient.
For those that are interested the cab files does the following:
- Installs Android in the root of the SD Card
- Deploys the correct Startup.txt for the device (the user can choose their device type)
- Adds a high res icon for Android in the root of the SD Card
- Installs a shortcut in Program Files named "Android" (launches Haret.exe)
- Installs the high res icon in the registry for WM6.5 users
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
How To Install (ZIP Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and extract the ZIP
Download and install the following 'full package' zip(a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid zip button below.
You MUST unzip to the ROOT of the Storage Card. The zip file will take a short while to extract. Please be patient.
Once you've extracted the zip:
- Click Auto-Setup.exe to configure XDAndroid for your particular device
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
If you want to exit Android and go back to Windows Mobile, then you need to shut down / reboot. To do so with the latest Android releases, hold down the 'end call' button until you see a menu appear.
If this fails to work, then the only option is remove the battery or press the reset button.
Known Issues
Many things are still not working properly, and the developers are fully aware of 99% of them.
SDCard - Most SDCards are working, but if you the 'waiting for SDCard' message, you should try one of these fixes (and please let us know if it works)
Fix 1: Format your card with this tool http://www.sdcard.org/consumers/formatter/
Fix 2: Edit your startup.txt file and add these entries to your cmdline:
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
Fix 3: Tell your wife / girlfriend that you are about to make some modifications to her phone... change the ringtone and steal her old Class 2 SD Card to use with Android. She will never discover what you have done, and if she does, you'll be able to use Android to send texts to your former girlfriends ;-)
SDCard - A few users have claimed to have had trouble using their SD Cards after installing XDAndroid. Some of those have reformatted the SD Card, and it worked, some couldn't recover it. This is a minority of users, but be warned.
Camera - Not working
GPS - working
Battery Status - Highly problematic for most users (don't trust the capacity Android tells you, it's simply up and down a lot, and highly inaccurate)
WiFi - Working for most people, suspected to cause slight heat, definitely drains the battery faster than WinMo.
Audio - Speaker working for most people, microphone can have issues
Deep Sleep - Working for most people, but can have issues waking up (sometimes, it will not wake up)
GPRS - Working
3G - Working for most
PIN Code - Unknown
GSensor - Working (Screen only handles 0 and 270 degrees)
Bluetooth - Experimentally working (don't expect too much, but it's working for a number of users)
OpenGL ES - 'should' be working but only for Blackstone... more to follow soon
USB - Supported, but will NOT operate in mass storage mode. You can charge via USB and you can debug, but forget accessing your files by it.
Headphone Socket - Semi working (see FAQ for details on how to make it work)
Application Errors: It's very common to see 'Application (xxxxxx) is not responding: Force Close or Wait'. Click wait. I do not know the precise reason for this, but from what I can gather, it COULD be related to the slow speed of the SD Card causing the app response times to JUST be a little too slow for Android's liking, thus causing the message. This seems to happen more after bootup or wakeup when the device is busy doing stuff in the background.
Cannot choose ringtones: This is believed to be caused by the media scanner failing (due to discovering some filenames with none English characters). The best option of all is to use a CLEAN SD Card. But, if you insist on hosting other files on the same SD Card, you MUST make sure they have English character filenames.

reserved
reserved reserved reserved 2

Reserved
reserved reserved reserved 3

Reserved
reserved reserved reserved 4

I'm here waiting for the new release......

zsdja said:
I'm here waiting for the new release......
Click to expand...
Click to collapse
Zip now available
Cab will be here in the next hour... but...
This is major move from Eclair to FroYo, and it's slightly slower than the Eclair release (so far).
This is normal though, since many of the Eclair release issues where ironed out, but with FroYo we take a small step backwards before we can progress again...
This release is VERY untested... I used it for 30 mins on a Blackstone only... no other devices tested yet

There is newer system version
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri

jura55 said:
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri
Click to expand...
Click to collapse
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !

TheBrilliantMistake said:
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !
Click to expand...
Click to collapse
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks

looks like just an update from 2.1 to 2.2 - no bug-fixes or new working features, right?
downloading now to have a play

OMFG!! YES!!
android 2.2 has calendar sync to exchange (2007) natively!. this release has hammered yet another nail into WM coffin!
also it looks like my 2.1 install was broken - seems noticably faster and touchscreen seems to be working a bit more predicably.

sorry but where is the file.

:-D First post, Step 2 -> Biiig black button

sorry being a noob, all done and running.
Damo

Is this version include the chinese language?Thanks for the good work.
Sent from my MSM using XDA App

ok MarketPlace is now not working.....argggghhhhh

damianpadden said:
ok MarketPlace is now not working.....argggghhhhh
Click to expand...
Click to collapse
I think you can try to delete the data.img and restart the android then try again,good luck ^_^
Sent from my MSM using XDA App

lol...i just did that exact thing....remembered it from before on 2.1...thanks
Damo

thanks for marketplace fix. i too was having the same issue!

jura55 said:
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks
Click to expand...
Click to collapse
No it does not have Sense. Why would you want it?
You can get virtually all the same widgets from other sources. Sense is a massive resource drain (esp on XDAndroid), and on non 3D supported hardware
If you want the flipclock, you can get it from multiple places, the wallpaper, the wallpaper, and similar widgets are all floating around too.

[TOOL][Windows/Theming] BatchAPKTool

As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
{
"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"
}
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release

Cool.
Suggested it for the portal.

Awesome - thanks a lot!
A slightly updated version is coming sometime soon.

New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.

dfkt_ said:
New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.
Click to expand...
Click to collapse
Not really into cooking ROMs these days, but this tool will definately help if I enter the kitchen again and try my hand at themimg.
Thanks a lot :good:

Thanks for this, it's really productive

Thanks for this tool, Really useful & helpful!

Thanks bro, it makes so much things easier

Thanks mate. I'll give a try asap
I saw your thread from the portal and this is worth cuz it looks very useful on paper :good:

Glad you guys find it useful.
Don't hesitate to report eventual bugs, or illogical combinations of options, etc.

dfkt_ said:
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not.
Click to expand...
Click to collapse
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page

dfkt_ said:
As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release
Click to expand...
Click to collapse
Now this will come in handy very very much! Keep up the good work and keep adding features to it
Sent from my Galaxy Nexus using Tapatalk 4

Not sure that your quote is useful.

8notime said:
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page
Click to expand...
Click to collapse
Yeah, that's a dilemma - the URL for the JRE direct download link is dynamic (the "1880261" part), changes with each new version. So the script would have to be constantly updated (or some really sophisticated URL crawler implemented). The lazy-but-safe way of linking to the index page is probably the best I can offer. Or maybe it's safe to link to the root JDK/JRE download page (which seems to have a fixed URL), and tell people that the JRE is enough, no need to get the JDK.

THANK YOU
Great tool. Im currently working on my dialpad theme. Great find! :good: