[Android] Droid-Ion Donut 1.6 for the Vogue (Market Fix)

[zenulator]

Well I finished my personal project. It's an Eclair/Droid themed Ion Donut 1.6 build for the Vogue. Nano Droid.

What it has:
*Droid themed launcher, wallpaper and icons.
*Eclair themed dialer
*Themed clock
*Custom themed calculator (could have done it in mspaint)
*Meridian Evolve Music Player
*Gmail from the HTC Tattoo
*Maps and Youtube from Eclair/Sholes
*Work Email with Exchange support
*Jewels (Bejeweled Clone)
*Better Browser with double tap zoom and a couple others.
Installable:
*HTC IME (hero keyboard) (looks funny in qvga so i left it out)

It's made for qvga so set your default.txt to:

mddi.width=240 mddi.height=320 lcd.density=120

Other resolutions work as well.

Use it with the latest basefiles, zImage and rootfs.img at vogue-android (http://code.google.com/p/vogue-android/downloads/list).

I recommend turning off compcache/swap for donut builds. It seems to slow things down by keeping more than needed in compressed memory.
Download this donut.user.conf (http://dl.dropbox.com/u/2888561/donut.user.conf) files if you don't know how to turn off compcache and put it inside /conf on your sdcard. It also has the "chmod 777 /etc/dbus.conf fix for mssmisions recovery/ext2 installer.


New Market fix (Hopefully) build tags/fingerprint in build.prop is for MyTouch3G 1.5.
It seems that when you run donut in qvga the market only shows apps compatible with qvga and remembers those settings even when you go back to ion/xrom etc... vilord has mentioned that if you boot into donut at mddi.width=320 mddi.height=480 lcd.density=160 open the market and login and then switch back to a ion/cupcake build your normal market "should" be back.
I still recommend logging in with a separate Google account if your running donut at qvga and want switch back and forth between cupcake/ion 1.5.


If your new and don't know what your doing then read this (http://vogue-android.googlecode.com/files/Instructions-26-10-09.txt).
Use the built in xda search powered by Google(TM) (http://forum.xda-developers.com/forumdisplay.php?f=390&nojs=1#goto_forumsearch) to search the vogue forum you will learn a lot.
If you still have questions then post them in the help thread here (http://forum.xda-developers.com/showthread.php?t=474576).

This is not a how to thread.
jamezelle will flame you so you've been warned. :D

Screenshots taken from ddms.
http://zen-droid.googlecode.com/files/device4.png http://zen-droid.googlecode.com/files/device3.png http://zen-droid.googlecode.com/files/device1.png http://zen-droid.googlecode.com/files/device5.png http://zen-droid.googlecode.com/files/device6.png http://zen-droid.googlecode.com/files/device7.png

Base System Image Credits go to:
Amon_RA for his sapphire/ion image
Theme Credits go to:
MontAlbert for partial theming based on the work of Wysie
me for adding missing droid/eclair icons and wallpapers and theming the calculator (nobody ever does that)

Download (http://dl.dropbox.com/u/2888561/system-droid-ion-r2.sqsh):D

[brsev]

Looks great, glad to see you're still looking at the Vogue port. Downloading now, will add details...
Most everything seems to work great, I like the new music player and the theming is excellent (especially the 2.0 icons and the analog clock). For some reason, though, it doesn't seem to be going into full sleep mode, or at least it never seems to lock the screen - when I turn it on it just jumps right to the Android home.

[garynsa]

As usual Zen... looks great... Thanks for the lovely build

[deathpod]

Confirmed working well at the usual hero resolution but I gotta admit... those are some crisp screenshots! I'm switching back down now.

[moekind]

does this work with msmissions linux ext2?

[deathpod]

Not without using adb to set some files to r/w while booting.

** more specifically:

# chmod 777 /etc/dbus.conf


But once it's up and running, it's very fast!

[moekind]

can someone modify the build to add those commands

[ruizit0]

wow :D
looks nice zen :D

so what works and what doenst works in this one ?

gps ?
data ?
camera ?

[vilord]

seems to be working great! I didn't make any changes to dbus or anything, just loaded fresh, love it! I forgot to set lcd.density tho, so everything is TINY.
Reduced the res, with 120 density, and it looks awesome! I see now what I was missing before!

What about using the HTC IME from tattoo? That should properly support qvga?

[TheKartus]

Couldn't get it to boot up past the Android logo with the ext2. method.

[zenulator]

seems to be working great! I didn't make any changes to dbus or anything, just loaded fresh, love it! I forgot to set lcd.density tho, so everything is TINY.
Reduced the res, with 120 density, and it looks awesome! I see now what I was missing before!

What about using the HTC IME from tattoo? That should properly support qvga?

I tried the tattoo HTC_IME but it wouldn't install.

[deathpod]

For...
does this work with msmissions linux ext2?

And...
Couldn't get it to boot up past the Android logo with the ext2. method.


Using the adb shell execute the following while looping at the Android logo:

# chmod 777 /etc/dbus.conf

Enjoy!

[Rhys'Droid]

For...


And...



Using the adb shell execute the following while looping at the Android logo:

# chmod 777 /etc/dbus.conf

Enjoy!

Do you have to do this every time you boot, or will the setting hold after doing it once? --nope it won't, but.....

Add it to the donut.user.conf file at the end of the file in the custom_shells section. Boots right up! Easy!

[BJNK]

Do you have to do this every time you boot, or will the setting hold after doing it once? --nope it won't, but.....

Add it to the donut.user.conf file at the end of the file in the custom_shells section. Boots right up! Easy!

Ok lets pretend you have no idea what your doing... kind of like me and half this board ;)

What would I want this to actually look like:

# custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}

[jamezelle]

Ok lets pretend you have no idea what your doing... kind of like me and half this board ;)

What would I want this to actually look like:

# custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}





# custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}

chmod 777 /etc/dbus.conf

#this is a comment it is not read by the shell

this will be read by the shell because there is no pound sign

# echo this will not echo

echo this will

[vilord]

wouldn't it be # custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
chmod 777 /etc/dbus.conf
}

[Rhys'Droid]

wouldn't it be # custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
chmod 777 /etc/dbus.conf
}



yep, thats it. works like a charm! This is a nice build.

[jamezelle]

wouldn't it be # custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
chmod 777 /etc/dbus.conf
}



yeah my bad thanks for catching that

[BJNK]

Thanks guys much appreciated!

[Link9228]

This is awesome. My friend just got the droid today, and he was showing me some pretty cool stuff on it. It's really responsive (I guess I'm just used to the slowness of running from an SD card). I tried showing him my tatoo build, but I was missing some files I needed. I just updated everything and downloaded this. Look forward to messing with it. Thanks!

[moekind]

Wow! It's Like Wow! (Chris Brown Style)

This Rom is the best rom i've used so far, just amazing.
The donut.conf edit thing worked like a charm.
Thank's alot guys.

Good to see Vilord back.

Vilord was wondering if you fixed the issue with the QVGA HTC IME keyboard.
That's the only thing missing.

[moekind]

One more thing, I set it to home, then sleep in spare parts,
but it still doesn't go to home.

[zenulator]

One more thing, I set it to home, then sleep in spare parts,
but it still doesn't go to home.

long press camera button goes home now in the latest zImage

[TheKartus]

Just out of curiosity, is there a reason there is no unlock screen? When the phone is asleep and I hit menu, it goes right to my home page. There is also no way to set an unlock pattern, since it just skips that screen.

[tetrismonkey]

hey i have a question about GPS on this build when ever i try to use it i don't see the little satellite icon at the top
however if i boot WM and and locate my gps and then boot android to works
but only once, if i exit google maps and go back to the app it no longer locates me.

is anyone else having this problem
beside that its a great build and i love it
this will be my default build until i buy the Droid in few weeks, have to wait to have the money

great work zen glad
thank you

[KERKEDAGAIN]

hey i have a question about GPS on this build when ever i try to use it i don't see the little satellite icon at the top
however if i boot WM and and locate my gps and then boot android to works
but only once, if i exit google maps and go back to the app it no longer locates me.

is anyone else having this problem
beside that its a great build and i love it
this will be my default build until i buy the Droid in few weeks, have to wait to have the money

great work zen glad
thank you

gps no workie on donut yet..

[tetrismonkey]

gps no workie on donut yet..
alright thank you for the info
i don't use it that much anyway

[Macmee]

Do I have to change data.img files every time I switch to a new build? I just got mine up and running and want to switch to this already:p

[casualonejp]

This build is fantastic, fast, and lots of coolness! One thing though, the touchscreen is iffy. When I click on icons or use the keyboard it isn't really accurate and sometimes a key or icon from across the screen winds up being the one that gets hit. On xrom it didn't do this but on certain builds it is just all over the place! WinMo is fine though. Any suggestions?

[jamezelle]

This build is fantastic, fast, and lots of coolness! One thing though, the touchscreen is iffy. When I click on icons or use the keyboard it isn't really accurate and sometimes a key or icon from across the screen winds up being the one that gets hit. On xrom it didn't do this but on certain builds it is just all over the place! WinMo is fine though. Any suggestions?

Use the screen calibration tool

[bzo]

long press camera button goes home now in the latest zImage

Is this working for everyone in this build? It used to work for me in an older donut build, but after updating to this one it doesn't work anymore. I'm running it on ext2.

[casualonejp]

Use the screen calibration tool

Ok, stupid question, once in the calibration tool, what is the right way to do it?

[stickus]

I saw this on XKCD today, thought I'd share it with you all:
http://imgs.xkcd.com/comics/iphone_or_droid.png

:)

[weezyfeezy]

Ok, stupid question, once in the calibration tool, what is the right way to do it?

I just push the top left red dot with the stylus, then the bottom right red dot with the stylus, it says calibrated! then I press menu and save. Seems to work okay...

[jamezelle]

Ok, stupid question, once in the calibration tool, what is the right way to do it?

Hit the two dots with stylus then hit menu and save. If the.development app is installed you can hit test calibration otherwise it will force close

[Pandemic187]

Zen, I would just like to commend you for this excellent build. It gives a nice themed look to Android without the slowness of Hero. Well done, sir.

[refthemc]

I seem to have a problem, I'm using all the latest files and it seems like 1 minute its running just fine and then for a bit it slows down, then runs fine, then slows....Makes it a little irritating when all i'm trying to do is use the broswer.....or simply open the dialer....

One other thing, there also seems to be a bit of a lag when waking up, I have to press the button like 4 or 5 times to wake this phone up.

Are these normal problems? if they are then forgive my ignorance because I'm not used to using Donut.

[Macmee]

This is the absolute best 1.6 rom I have used. Thanks :)


edit: THE MARKET EVEN WORKS WITH MY GMAIL ACCOUNT!

[Macmee]

With this build the person I'm calling can't hear me and I can't hear them :(

[kkruse]

I know im strecthing this thing to the limit but if i could make it work somewhat responsive on this old mogul i'd really be happy. xD

[scouzer]

wow best android i've used yet!!! how do we install the htc keyboard?

the QVGA market sure is small lol.. or does that mean the google account i'm using is fouled? i dont even have facebook. do i switch google accounts?

argh. it keeps rebooting itself. it's so so responsive though, i had no idea android could be this fast on our phones

[Rhys'Droid]

wow best android i've used yet!!! how do we install the htc keyboard?

the QVGA market sure is small lol.. or does that mean the google account i'm using is fouled? i dont even have facebook. do i switch google accounts?

argh. it keeps rebooting itself. it's so so responsive though, i had no idea android could be this fast on our phones

What you need to do to get the full market:

1) Delete your Data.img (or you might be able to clear the market cache, not sure...I started with a fresh data.img)
2) Set your resolution your default.txt to 320x480.
3) Boot up Android, log in to your Google account, open the market, everything should be there.
4) Change the resolution in your default.txt back to 240x320, and reboot, everything should still be in the Market, and will stay there unless you clear the data file. :-)

[scouzer]

What you need to do to get the full market:

1) Delete your Data.img (or you might be able to clear the market cache, not sure...I started with a fresh data.img)
2) Set your resolution your default.txt to 320x480.
3) Boot up Android, log in to your Google account, open the market, everything should be there.
4) Change the resolution in your default.txt back to 240x320, and reboot, everything should still be in the Market, and will stay there unless you clear the data file. :-)

Thanks a ton for the help, but unfortunately it didn't work. I booted into 320x480 on a blank img and sure enough, the market was normal. I blanked out my data.img again, switched back to 240x320 and booted up again, market was crippled again. :(

[vilord]

scouzer, don't delete data the second time.

[Rhys'Droid]

Thanks a ton for the help, but unfortunately it didn't work. I booted into 320x480 on a blank img and sure enough, the market was normal. I blanked out my data.img again, switched back to 240x320 and booted up again, market was crippled again. :(

That's 'cause you blanked out your image again. You have to log back into the same image that you created under the 320x480 default.txt. (hence the "unless you clear the data file" caveat at the end of step 4.)

[scouzer]

That's 'cause you blanked out your image again. You have to log back into the same image that you created under the 320x480 default.txt. (hence the "unless you clear the data file" caveat at the end of step 4.)

Ohh!! Sorry, I've been up all night, apparently my attention to detail is about zero :o

Thanks so much!

[gascan555]

Hey, I really like this android build. Definitely fastest/smoothest/prettiest I've come to use (and in actual QVGA!!). 2 quick question though.

First question: I've been told that I can use the internet from my computer to pass through Bluetooth to my phone. Considering I don't have a data plan (and the vogue has no wifi), this is kinda necessary to back up contacts and whatnot. Is this true or can anyone confirm this works?

Second question: I can't get Bluetooth to turn on in Android. It sits and thinks for a bit, the blue light comes on, but then it just uncheck's the settings option and does nothing beyond that. Any ideas why? TIA!

[kkruse]

I know im strecthing this thing to the limit but if i could make it work somewhat responsive on this old mogul i'd really be happy. xD

Call me crazy but vilords new rootfs seems to have helped some on the mogul. Might even buy me time till my contract is up in Jan.

Now i need to figure out whats up with the GPS. I was tempted to replace the gps lib from the 1.5 img on the vogue-android site. That one seems to work fine with mogul (only app that does work is "where").

Im by no means a linux newbie, but I am a newb when it comes to this type of appliication. What is the /dev for the gps?

[enatefox]

gascan555, I don't know about bluetooth but if you want to get online on your phone via USB internet from your computer, assuming it's running Linux:
echo "1" | sudo tee /proc/sys/net/ipv4/ip_forward
If using Windows, maybe ICS would work to enable IP forwarding then on the phone:

ip addr add 192.168.x.100/24 dev usb0
## where "x" is the subnet of your LAN
ifconfig usb0 up
route add default gw 192.168.x.x
setprop net.dns1 192.168.x.x
## where "x.x" is the IP of your computer

With 1.6 it works great (not Market) but like 1.5 it can hard freeze requiring a reboot. I'm looking into that though..

[gascan555]

Considering I'm not running linux, and my computer doesn't recognize drivers when I plug my phone in running android, what should I do?

[Link9228]

Considering I'm not running linux, and my computer doesn't recognize drivers when I plug my phone in running android, what should I do?

if you look on the vogue-android google code page there are adb drivers for windows. Those will allow you to connect your phone.

[gascan555]

if you look on the vogue-android google code page there are adb drivers for windows. Those will allow you to connect your phone.

They don't work. I'm running Windows 7. That a problem?

[Link9228]

That's a possibility. I have XP and they work on that, but it's well known that there are many compatibility problems between xp and vista (and therefore 7)

[vilord]

the drivers up there should work for 32bit win7 (i use those at home).
Here at work I have 64bit win7, and needed new drivers. I just uploaded those as adb2

[scouzer]

So how exactly do we install the HTC keyboard? :)

Nevermind! did my own research, here's a guide for anyone else needing help:

http://androinica.com/2009/08/25/how-to-install-the-htc-android-soft-keyboard-without-rooting-your-phone/

[gascan555]

the drivers up there should work for 32bit win7 (i use those at home).
Here at work I have 64bit win7, and needed new drivers. I just uploaded those as adb2

Awesome. I see my device now! Now, I don't quite get the internet passthrough part. Anyone want to help me with that?

[vilord]

i thought internet passthrough was linux only... no?

[polyrhythmic]

I've. used Tetherbot (http://graha.ms/androidproxy/) successfully on some builds with Firefox in Windows, but there are other ways to tether being talked about on the forums.

sent from this donut build on my Tilt, thanks for the data improvements vilord

[gascan555]

I'm trying to use HTC's "HTC Sync" software, but to no avail so far. Other than that, I guess I'm moving my contacts over one by one. :P

[crackeyes]

I need help. When i try to lauch it it gets to the linux screen and then just sits at "waiting for sd card" and never boots. The files i am using are

default.txt
initrd.gz
rootfs.img
zImage
system.sqsh
haret.exe

I got these files from http://code.google.com/p/vogue-android/ and used the baseline11162009 zip file. I am using the Droid-Ion image that the OP made

Here is a copy of my default.txt

set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"

set cmdline "board-htcvogue.panel_type=0 ppp.apn=gprs-service.com ppp.username=none ppp.password=1234 board-kaiser-battery.battery_capacity=1800 mddi.width=240 mddi.height=320 lcd.density=160 msm_sdcc.msmsdcc_fmax=20000000 pm.sleep_mode=1 no_console_suspend "
boot


Someone please help i want to use this. It is a USCC touch and ill worry about the data connections later. I just want to get this to load.

[mrkite38]

the drivers up there should work for 32bit win7 (i use those at home).
Here at work I have 64bit win7, and needed new drivers. I just uploaded those as adb2
Ah! Thanks, vilord!

And about internet passthrough, i believe it was removed some months ago to troubleshoot the adb connection. it's a personal quest of mine to add rndis support to dzo's kernel but since i have little linux experience and NO c experience it may take a while. :-)

[vilord]

The default.txt you listed there looks a lot like a kaiser default.txt... where'd you get it from? USCC touch is not kaiser. Thats why its not booting. use a vogue default.txt.

I need help. When i try to lauch it it gets to the linux screen and then just sits at "waiting for sd card" and never boots. The files i am using are

default.txt
initrd.gz
rootfs.img
zImage
system.sqsh
haret.exe

I got these files from http://code.google.com/p/vogue-android/ and used the baseline11162009 zip file. I am using the Droid-Ion image that the OP made

Here is a copy of my default.txt

set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"

set cmdline "board-htcvogue.panel_type=0 ppp.apn=gprs-service.com ppp.username=none ppp.password=1234 board-kaiser-battery.battery_capacity=1800 mddi.width=240 mddi.height=320 lcd.density=160 msm_sdcc.msmsdcc_fmax=20000000 pm.sleep_mode=1 no_console_suspend "
boot


Someone please help i want to use this. It is a USCC touch and ill worry about the data connections later. I just want to get this to load.

[jamezelle]

yeah that is kaiser's mtype

try
set RAMSIZE 0x08000000
set MTYPE 1667
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 1=Hitachi 2=Topoly 3=Samsung
# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone
# lcd.density - Defaults to 160, 128 shows more on screen
# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.
#
# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1
# US Sprint vogues usually have type 2 or 3 I think.
# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.
set cmdline "ppp.nostart=0 mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1 no_console_suspend"
boot

[djp3k05]

anyone else have experienced this problem: I imported my sim contacts, and when someone calls me, I do not get the name, just number.
and another problem, wi-fi works perfectly, browsing, google maps, etc., but i can not connect to the market. it is just only me?
congratulations for a super fast build.

[niru1978]

Hi

I installed this rom on my polaris and it works gr8 with the latest basefiles

smooth fast wifi good camera OK (quality is low)

but there are few apps which are crashing such has the barcode scanner.

kindly let me know how do I solve it. (libraries / upgrades / patches)

Also my windows 7 doesn't detect the phone. on the phone it shows usb debug connected but in the laptop I dont get any popups etc. cannot install the drivers if the device is not detected and even with inf file it throws error

Niranjan

[Macmee]

Market was working until I rebooted the phone, now it's gone again :(

[ivku]

Ah! Thanks, vilord!

And about internet passthrough, i believe it was removed some months ago to troubleshoot the adb connection. it's a personal quest of mine to add rndis support to dzo's kernel but since i have little linux experience and NO c experience it may take a while. :-)

How did you get to W7 64bit ? The driver is designed for Vista and my W7 don't recognized it. I try to allow install unsigned drivers, but seems this is not my problem.
Thanks for a hint.

[vilord]

Hi

I installed this rom on my polaris and it works gr8 with the latest basefiles

smooth fast wifi good camera OK (quality is low)

but there are few apps which are crashing such has the barcode scanner.

kindly let me know how do I solve it. (libraries / upgrades / patches)

Also my windows 7 doesn't detect the phone. on the phone it shows usb debug connected but in the laptop I dont get any popups etc. cannot install the drivers if the device is not detected and even with inf file it throws error

Niranjan
Niranjan: glad to hear it is working with your polaris!
The barcode scanner crashes for everyone, as far as I know, on these nonofficial devices...

For polaris to work with USB, the cable must be connected *while* you are booting up... So put the phone in activesync mode in winmo, connect the cable, *then* run haret. Once it starts up fully you can unplug/replug the USB and after a short delay you'll see it pop up on your PC.
Also you will want to disable sleep when USB connected, because as soon as it goes to sleep the usb will disconnect and will need to be replug-ed to show up again.

[JacenSolo2001]

Is there a particular file I would need to change in order for GPS to work on this build?

[silex]

Call me crazy but vilords new rootfs seems to have helped some on the mogul. Might even buy me time till my contract is up in Jan.

Now i need to figure out whats up with the GPS. I was tempted to replace the gps lib from the 1.5 img on the vogue-android site. That one seems to work fine with mogul (only app that does work is "where").

Im by no means a linux newbie, but I am a newb when it comes to this type of appliication. What is the /dev for the gps?
Are you saying you got gps working on the Mogul with this build? Upload your gps lib quick so us Vogue users can mess around with it!

[mrkite38]

How did you get to W7 64bit ? The driver is designed for Vista and my W7 don't recognized it. I try to allow install unsigned drivers, but seems this is not my problem.
Thanks for a hint.
I just selected the androidusb.inf and installed it. I think there are some issues with the dll under x64 but I was able to make an adb connection, run logcat, shell, etc. The shell output was a bit garbled. I'll run through it again tomorrow and post specifics.

[arlojj]

Okay, I know this isn't a how-to thread, but I've never had an Android for Vogue build not boot, so I'm completely stuck.

I had settled on using Google Ion a long time ago due to it's speed. Checked XDA recently and it sounded like this was a great build, and I wanted to use some applications that use the camera, etc.

I decided to start fresh. Formatted my SD card and followed all of the instructions in the first post. Installed the latest basefiles, overwrote the conf from the first posting, set up the default.txt and tried to boot, but it wouldn't.

There's a bit more than this, but I've posted the error bits.

sh: 0: unknown operand
sh: 0: unknown operand
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
e2fsck: No such device or address while trying to open /dev/block/mmcblk0p3
Possibly non-existent or swap device?
mount: mounting /dev/block/mmcblk0p3 on /data failed: no such device or address
Failed
Failed to mount /data
/bin/sh: can't access tty; job control turned off

Any ideas? It doesn't even get to the "creating data.img" stage.

Thanks so much.

[ivku]

Doesn't work for me. INF is not directly installable for me. Error INF does not support this type of installation.

[freddycs]

Okay, I know this isn't a how-to thread, but I've never had an Android for Vogue build not boot, so I'm completely stuck.

I had settled on using Google Ion a long time ago due to it's speed. Checked XDA recently and it sounded like this was a great build, and I wanted to use some applications that use the camera, etc.

I decided to start fresh. Formatted my SD card and followed all of the instructions in the first post. Installed the latest basefiles, overwrote the conf from the first posting, set up the default.txt and tried to boot, but it wouldn't.

There's a bit more than this, but I've posted the error bits.

Any ideas? It doesn't even get to the "creating data.img" stage.

Thanks so much.

can you please show what is in your default.txt?

i had the same problem before when i set the lcd.densit wrongly to 12 instead of 120 :)

[Michel82]

Okay, I know this isn't a how-to thread, but I've never had an Android for Vogue build not boot, so I'm completely stuck.

I had settled on using Google Ion a long time ago due to it's speed. Checked XDA recently and it sounded like this was a great build, and I wanted to use some applications that use the camera, etc.

I decided to start fresh. Formatted my SD card and followed all of the instructions in the first post. Installed the latest basefiles, overwrote the conf from the first posting, set up the default.txt and tried to boot, but it wouldn't.

There's a bit more than this, but I've posted the error bits.



Any ideas? It doesn't even get to the "creating data.img" stage.

Thanks so much.

I had the same thing with the previous rootfs.img. It tries to mount a partition for /data which (obviously) doesn't exist. Make sure you're using the latest rootfs.img http://code.google.com/p/vogue-android/downloads/list?can=2&q=&sort=-uploaded&colspec=Type%20Filename%20Summary%20Uploaded%20Siz e%20DownloadCount

[160bpm]

Hi All,

Collect al latest basefiles, rootfs and the fixed system.sqsh
Everything put on a 2GB fat32 SD card. Installation was very fast and easy. Everything seems work

but i get error message when i want download a app on market

"The application market has stopped"

Can someone help me?
I'm using this on a HTC Kaiser... :)

[vilord]

arlojj: Do you have all the files in the root of the SD card, or do you have them in an android folder? And if they're in root, do you have an empty android folder? That could be part of the issue...

[160bpm]

This message was wrong... was thinking i get a possible solution for my problem

[vilord]

no i meant that if everything is in root, you need to make sure there is *not* an android folder :D

which version of the basefiles and rootfs are you using?
did you rename the rootfs that you downloaded to just rootfs.img (and also rename to system.sqsh or system.img) ?

[160bpm]

Hi

It is solved... I don't know what i did but it is working now...
I will try find out whats happend..

But thanks for the support anyway!!!

[polyrhythmic]

In this build I am having a new issue I haven't seen before:

Occasionally the touch keyboard comes up gray with no graphics, it responds to touch as if the keys are there but the entire keyboard space is gray. When this happens in Maps the keyboard doesn't show up at all, not even gray, but still responds to touch. I can't get it back to normal without a reboot. Idk what's going on, but if there's a way to reload the kb without rebooting (via CLI or otherwise) I'd love to know it!

Thanks again!

[frad]

First question: I've been told that I can use the internet from my computer to pass through Bluetooth to my phone.

I've been trying to do this for ages! Where did you hear this?

Basically I want to tether my unlimited internet Vogue to another android phone via Bluetooth. The Vogue has no Wifi so it has to be Bluetooth. It would need to do the sharing using the PAN profile.

Still I've searched everywhere but not come up with a solution yet. Where did you hear it was possible to access the internet in Android VIA bluetooth? Thanks!

[enatefox]

Just a guess but you should be able to use standard bluetooth tethering on the Vogue and on the other phone set up a bridge to forward the connection (modifying the bluetooth tether instructions to work in reverse) over to USB0 and from there you can ifconfig usb0 up and set the DNS. Worth a shot

[arlojj]

@freddycs
@Michel82
@Vilord

Thanks for the replies, everyone!

I used the latest, separately uploaded, rootfs.img with the latest basefiles package and that solved the problem. It appears that the rootfs in the basefiles package was what was causing the issue.

Thanks again for your assistance! Love Android. I can't afford a new phone, and I'm locked into one of these stupid 3 year Canadian contracts, and these ports make my old WM phone actually useful, fun and productive again!

[160bpm]

Hi Guys,

Can't find it in the tread. But does GPS not work in this build? Or do i have a technical problem , houston? :)

GPS is not working, no GPS icon etc

[TheKartus]

Hi Guys,

Can't find it in the tread. But does GPS not work in this build? Or do i have a technical problem , houston? :)

GPS is not working, no GPS icon etc

GPS does not work in any of the Donut builds.

[160bpm]

Hi

Thanks... Clear answer :) they work on it i hope...

I have moved my leggs from the Kaiser Android builds to the Vogue, so i'm not full into the do/don'ts what is working and not.

But okee.. i know now gps is not working. It seems for me that only bluetooth as well is not working. Wifi, Data, sms, calls and camera are working

[160bpm]

Email is working.. not how i normail used. (you cannot move emails to a folder within the IMAP)
Maybe is that the way of ION Donut.

[arlojj]

Awesome awesome awesome.

Used the market trick (log in high res first, then back to QVGA) and it's flawless (well, except for those apps that don't respect resolution, but fsck them!).

Very fast, and once GPS is working this will be absolutely perfect. I don't have much use for GPS being in a small mountain town right now (come summer hiking it would be useful), but otherwise I am highly impressed. New life for my old crappy phone on my long crappy Canadian contract!

Thanks zenulator!

[wentzeric]

Great looking build BTW

I loaded it and it started up, put in my information and everything seems good. Until it loads for use. that is when I get:

SORRY!
the process android.process.acore has stopped unexpectedly. Please try again.

Ive swapped out the all the fixes posted in the first post and tried two different ZImage files.

HELP! ... ?

[djp3k05]

just information for others: whit this build and latest basefiles, my battery lasted 37 hours. Used mostly in phone calls and SMS (about two hours), played games, played whit the phone. generally quite used. I have not used wi-fi.

[lauyanyameric]

This is a very good build. Love the market comeback trick. but not switching back to QVGA yet as many apps are still made for 160 density (incl. the Camera app).

GPS seems to work only when density set at 160, not 120.

Voice search was amazing for the 1st time, but no response since 2nd time, then it says "Connection Problem", then "Audio Problem" when retry, and phone ear speaker and mic not working anymore, can't receive/make calls unless reboot. (probably still searching?)

btw, I am on Kaiser. thanks zen,

[kkruse]

GPS seems to work only when density set at 160, not 120.
,

Can anyone confirm this on a mogul? I would try but i dont have time today.

[stickus]

I can confirm that GPS is working at 160 density, either 240*320 or 320*428 or 320*480, on my Vogue. Any ideas folks?

[skydirt]

Really?! Gonna go outside to test this...having GPS working would be brilliant.

[160bpm]

GPS is not working for me.. but maybe because i use the Kaiser with this build... Maybe that is the reason for me that it will not work...

[skydirt]

GPS most certainly does not work.

[tatnai]

I can't remember who posted this first, but in donut GPS works after booting if you use it before you make or receive a phone call (maybe sms too); can't recall if it had to be with a new data file. pretty sure it has nothing to do with resolution.

can verify that it worked for me on first boot before making a phone call, then stopped working.

[kiwilime]

Can anyone verify this? I am choosing between 1.5 cupcake and donut. I like donut because it has a better keyboard and I can use Sense UI on it (which I really like), but im afraid that the GPS wont work.

[arlojj]

It's such a shame that I didn't wait 6 months to get a phone... wouldn't be stuck with these QVGA blues. :( But still, for most parts (outside GPS), I'm so glad my phone has the functionality it now has.

[lauyanyameric]

@tatnai @evilclosetmonkeynate were right.

GPS can only start when first boot and then stop working. :(

[Macmee]

This is the last week with my Vogue before the dream arrives :(

But I would love a working market app, if someone could tell me why this didnt work for me I'd appreciate it!

[dyatell]

hello! greeting! Be so kind as lay out the configuration file for kaiser) :confused:

I apologise for my English :)

[tatnai]

using this system with latest files from vogue-android. market fix (boot new data.img in 320x480, lcd 160) worked at first, but don't know for how long. continuing to use this in 320x240, i'm back to a limited market. anyone else have this problem? will try doing fix again, then maybe back to xrom system to see if the problem recurs while using a 1.5 cupcake rom.

[mfpreach]

Could someone tell me what the advantage of Donut is over Ion?

[dyatell]

mmm. i'm make this build working!) it's very nice! i'm wanna flashable rom in future) but may be autorun for haret.exe with command line make my wm phone transform to android?!

my english without translator - very bad?) :eek:

[skydirt]

Google just a few hours ago announced that thier new Google NAV is available and working for Android 1.6 ( Donut ) and is available on the market now. Think we can get some GPS fix love? :)

[frad]

Google just a few hours ago announced that thier new Google NAV is available and working for Android 1.6 ( Donut ) and is available on the market now. Think we can get some GPS fix love? :)

I kindly and humbly second that :)

http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html

[BinaryDroid]

what are the best setting I can use for the clearest screen? I got it almost ok but it just never looks really crisp. i'm not worried about being able to use market right now since its mostly fine with the stock apps and my usage. i have the Sprint 6900

[skydirt]

what are the best setting I can use for the clearest screen? I got it almost ok but it just never looks really crisp. i'm not worried about being able to use market right now since its mostly fine with the stock apps and my usage. i have the Sprint 6900

320x240 looks amazing on the Vogue and is as good as it gets.

[ruizit0]

what are the best setting I can use for the clearest screen? I got it almost ok but it just never looks really crisp. i'm not worried about being able to use market right now since its mostly fine with the stock apps and my usage. i have the Sprint 6900

please read first post...
mddi.width=240 mddi.height=320 lcd.density=120

[myn]

I kindly and humbly second that :)

http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html

Third that! Google Navigation would be epic!

[vilord]

*maybe* i'll look at it tonight... we'll see :)

tatnai, I also saw the market apps go away again... I think that eventually it kills the cache... We might need to dig into the /data/data folders and see where market is storing the resolution, then make a script to change it to standard instead of small_screen for each time it "expires"

[myn]

*maybe* i'll look at it tonight... we'll see :)

Excellent ..

[frad]

*maybe* i'll look at it tonight... we'll see :)



Cool thanks man. I've managed to see my GPS work, but as others have mentioned in this thread only on the first boot. After that the functionality disappears.

I managed to download and install the Google Maps update from the Market. It looks good.

GPS is the last piece of the puzzle to totally make my Vogue insanely awesome. :cool: Well... more awesome :)

Live maps and traffic data would be pretty sweet... I've got the $10 "Unlimited" data plan with Bell so i'd make lots of use of it!

[dyetheskin]

for kaiser users,what exactly is needed to get full market access? im aware of whats needed to revert to for resolution/lcd density

[vilord]

can you elaborate a bit?
changing the resolution and creating a new data file should give you immediate access to the "full market"... but you still won't see any paid apps because google locked unsecure devices out from paid apps.

[skydirt]

Any word on GPS an donut? The release of GoogleNAV for 1.6 hurts, since we can't use it ><

[dyetheskin]

can you elaborate a bit?
changing the resolution and creating a new data file should give you immediate access to the "full market"... but you still won't see any paid apps because google locked unsecure devices out from paid apps.

what should resolution/density be for access? the 1st post mentioned going back and forth with something to allow access

[vilord]

ah. Basically you just need to set resolution to mddi.width=320, mddi.height=428, lcd.density=160 in default.txt, then create a new data file and load up and visit the market. Make sure everything is there

Then, you can set width=240, height=320, density=120, and it'll look better on your screen (less fuzzy). You should have access to all apps in the market for at least a few days or a week, after that it'll revert to just showing the small-screens applications.

It is on my growing list of things-to-do to dig into the /data folder and find out what is being cached that tells market the screen size.

[bpedman]

but you still won't see any paid apps because google locked unsecure devices out from paid apps.

what? I am running donut (droid-ion-donut on kaiser, at 320x480..even though its a little fuzzy) and I see everything, all the paid and non-paid apps...it works great

p.s. - i fourth the nomination for getting gps working in donut (vogue and kaiser) :) cant wait to see it in action, thank you for all your work

[jamezelle]

what? I am running donut (droid-ion-donut on kaiser, at 320x480..even though its a little fuzzy) and I see everything, all the paid and non-paid apps...it works great

p.s. - i fourth the nomination for getting gps working in donut (vogue and kaiser) :) cant wait to see it in action, thank you for all your work

who is your service provider????:eek:

[Michel82]

I am running native and i am also seeing all apps. Both paid and free. I'm on t-mobile NL

[vilord]

maybe for us verizon folks to see paid apps we'll need to switch to a build.prop from a verizon device...

[soundmind]

Have you tried MarketEnabler http://code.google.com/p/market-enabler/ I ran that and now my Ntelos Vogue shows up as a T-Mobile and i have full access to the market

[bpedman]

who is your service provider????:eek:

Im on AT&T...

On another note....I just started having a problem where the android splash screen just keeps showing over and over (kind of like hero builds would when you have a bad resolution)...I just installed a bunch of games before this started happening...not sure if it would be related or not....

Here is some of the output from logcat right before it restarts the boot process:

D/dalvikvm( 1270): GC freed 34060 objects / 1759680 bytes in 296ms
E/System ( 1270): Failure starting core service
E/System ( 1270): java.lang.NullPointerException
E/System ( 1270): at com.android.server.PackageManagerService.scanPacka geLI(PackageManagerService.java:1875)
E/System ( 1270): at com.android.server.PackageManagerService.scanDirLI (PackageManagerService.java:1771)
E/System ( 1270): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:497)
E/System ( 1270): at com.android.server.PackageManagerService.main(Pack ageManagerService.java:266)
E/System ( 1270): at com.android.server.ServerThread.run(SystemServer.j ava:112)
E/AndroidRuntime( 1270): Crash logging skipped, no checkin service
I/SystemServer( 1270): Starting Status Bar Service.
D/dalvikvm( 1270): GC freed 7413 objects / 372744 bytes in 205ms
E/installd( 1148): eof
E/installd( 1148): failed to read size
I/installd( 1148): closing connection
E/SystemServer( 1270): Failure starting StatusBarService
E/SystemServer( 1270): java.lang.NullPointerException
E/SystemServer( 1270): at com.android.server.status.StatusBarIcon.getIcon(St atusBarIcon.java:143)
E/SystemServer( 1270): at com.android.server.status.StatusBarIcon.<init>(StatusBarIcon.java:65)
E/SystemServer( 1270): at com.android.server.status.StatusBarService.makeSta tusBarView(StatusBarService.java:306)
E/SystemServer( 1270): at com.android.server.status.StatusBarService.<init>(StatusBarService.java:237)
E/SystemServer( 1270): at com.android.server.ServerThread.run(SystemServer.j ava:194)
E/AndroidRuntime( 1270): Crash logging skipped, no checkin service
I/SystemServer( 1270): Starting Clipboard Service.
I/SystemServer( 1270): Starting Input Method Service.
E/SystemServer( 1270): Failure starting Input Manager Service
E/SystemServer( 1270): java.lang.NullPointerException
E/SystemServer( 1270): at android.app.ApplicationContext.registerReceiverInt ernal(ApplicationContext.java:782)
E/SystemServer( 1270): at android.app.ApplicationContext.registerReceiver(Ap plicationContext.java:757)
E/SystemServer( 1270): at android.app.ApplicationContext.registerReceiver(Ap plicationContext.java:751)
E/SystemServer( 1270): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java:437)
E/SystemServer( 1270): at com.android.server.ServerThread.run(SystemServer.j ava:209)
E/AndroidRuntime( 1270): Crash logging skipped, no checkin service
I/SystemServer( 1270): Starting NetStat Service.
I/SystemServer( 1270): Starting Connectivity Service.
W/dalvikvm( 1270): threadid=25: thread exiting with uncaught exception (group=0x4001da38)
E/AndroidRuntime( 1270): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1270): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1270): java.lang.NullPointerException
E/AndroidRuntime( 1270): at android.app.ActivityThread.getProvider(ActivityThr ead.java:3938)
E/AndroidRuntime( 1270): at android.app.ActivityThread.acquireProvider(Activit yThread.java:3967)
E/AndroidRuntime( 1270): at android.app.ApplicationContext$ApplicationContentR esolver.acquireProvider(ApplicationContext.java:15 14)
E/AndroidRuntime( 1270): at android.content.ContentResolver.acquireProvider(Co ntentResolver.java:579)
E/AndroidRuntime( 1270): at android.content.ContentResolver.query(ContentResol ver.java:147)
E/AndroidRuntime( 1270): at android.provider.Settings$NameValueCache.getString (Settings.java:472)
E/AndroidRuntime( 1270): at android.provider.Settings$Secure.getString(Setting s.java:1649)
E/AndroidRuntime( 1270): at android.provider.Settings$Secure.getInt(Settings.j ava:1689)
E/AndroidRuntime( 1270): at com.android.server.ConnectivityService.getPersiste dNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1270): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1270): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1270): at com.android.server.ConnectivityService$Connectivit yThread.run(ConnectivityService.java:87)
E/AndroidRuntime( 1270): Crash logging skipped, no checkin service
I/Process ( 1270): Sending signal. PID: 1270 SIG: 9
I/ServiceManager( 1133): service 'telephony.registry' died
I/ServiceManager( 1133): service 'usagestats' died
I/ServiceManager( 1133): service 'netstat' died
I/ServiceManager( 1133): service 'SurfaceFlinger' died
I/ServiceManager( 1133): service 'batteryinfo' died
I/ServiceManager( 1133): service 'entropy' died
I/ServiceManager( 1133): service 'power' died
I/ServiceManager( 1133): service 'clipboard' died
I/Zygote ( 1268): Exit zygote because system server (1270) has terminated
I/DEBUG ( 1269): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1269): Build fingerprint: 'tmobile/opal/sapphire/sapphire:1.5/COC10/150449:user/ota-rel-keys,release-keys'
I/DEBUG ( 1269): pid: 1279, tid: 1283 >>> /system/bin/bootanimation <<<
I/DEBUG ( 1269): signal 11 (SIGSEGV), fault addr 41497000
I/DEBUG ( 1269): r0 41497000 r1 40c2895c r2 b4bbe654 r3 ffdfffdf
I/DEBUG ( 1269): r4 ffdfffdf r5 ffdfffdf r6 ffdfffdf r7 ffdfffdf
I/DEBUG ( 1269): r8 ffdfffdf r9 ffdfffdf 10 ffdfffdf fp ffdfffdf
I/DEBUG ( 1269): ip 40c28980 sp 4030cbe8 lr 80133bec pc afe0da90 cpsr a0000010
I/DEBUG ( 1269): #00 pc 0000da90 /system/lib/libc.so
I/DEBUG ( 1269): #01 pc 00033be8 /system/lib/libhgl.so
I/DEBUG ( 1269): stack:
I/DEBUG ( 1269): 4030cba8 0000d68c [heap]
I/DEBUG ( 1269): 4030cbac a9d2fccd /system/lib/libutils.so
I/DEBUG ( 1269): 4030cbbc a9d2f89d /system/lib/libutils.so

....bunch more debug output....

I/DEBUG ( 1269): 4030cbfc a9d29e05 /system/lib/libutils.so


....bunch more debug output....

I/DEBUG ( 1269): 4030cc0c 80133bec /system/lib/libhgl.so
I/DEBUG ( 1269): #01 4030cc10 4132c008
I/DEBUG ( 1269): 4030cc14 8011db50 /system/lib/libhgl.so
I/DEBUG ( 1269): 4030cc18 4132c008
I/DEBUG ( 1269): 4030cc1c 80133cf8 /system/lib/libhgl.so

....bunch more debug output....

I/DEBUG ( 1269): 4030cc34 801373b0 /system/lib/libhgl.so

.....

I/DEBUG ( 1269): 4030cc54 a9d29e05 /system/lib/libutils.so
I/DEBUG ( 1269): debuggerd committing suicide to free the zombie!
I/DEBUG ( 1291): debuggerd: Sep 21 2009 14:37:06
D/AndroidRuntime( 1290):
D/AndroidRuntime( 1290): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
....restarts here....

any ideas?

thanks

[SuperJMN]

Have you tried MarketEnabler http://code.google.com/p/market-enabler/ I ran that and now my Ntelos Vogue shows up as a T-Mobile and i have full access to the market

Wow, it worked for me! I switched to T-Mobile (US) and I now can download FeedR, an application that I BOUGHT but I couldn't re-download :S Lots of apps appeared.

By the way, I cannot find Shazam, though.

[frad]

Wow, it worked for me! I switched to T-Mobile (US) and I now can download FeedR, an application that I BOUGHT but I couldn't re-download :S Lots of apps appeared.

By the way, I cannot find Shazam, though.


If you can't see Shazam that might be due to the screen resolution/market issue that is described in the first post. At least that was the case for me.

I'm on Bell and I've always seen the paid apps... my only issue with the market occurred when I played around with my screen resolution, but the instructions on the first page solved that for me.

[plemen]

*maybe* i'll look at it tonight... we'll see :)



GPS would be fantastic... google maps was one of my most used apps.

And just got google nav going in Canada in the latest build - very nice tool.

[frad]

GPS would be fantastic... google maps was one of my most used apps.

And just got google nav going in Canada in the latest build - very nice tool.

Umm... wait... how?? :)

Was there an updated build recently released? The link on the first page seems unchanged.

[jamezelle]

Umm... wait... how?? :)

Was there an updated build recently released? The link on the first page seems unchanged.

no google maps with navigation-beta support is now available in the market

only for donut, but we currently dont have full gps support as of now

[frad]

no google maps with navigation-beta support is now available in the market

only for donut, but we currently dont have full gps support as of now

Thanks for the reply... yup I know its in the market... i've installed it myself, but as you said without GPS support there is no working Google Navigation yet.

When I read Plemen's comment it seemed to imply that he had Google Navigation working on his phone with the latest build... not that he just installed it. Which is why I was surprised.

[plemen]

Thanks for the reply... yup I know its in the market... i've installed it myself, but as you said without GPS support there is no working Google Navigation yet.

When I read Plemen's comment it seemed to imply that he had Google Navigation working on his phone with the latest build... not that he just installed it. Which is why I was surprised.

GPS works once when you first boot up....

[frad]

GPS works once when you first boot up....


When you say first boot up do you mean after soft resetting and then loading starting android? If so I've not been able to reliably reproduce this behaviour. Is there something I should... or shouldn't do to get GPS when I start up.

Or

Do you mean deleting your data file and booting up fresh for the first time?

Thanks.

[jamezelle]

When you say first boot up do you mean after soft resetting and then loading starting android? If so I've not been able to reliably reproduce this behaviour. Is there something I should... or shouldn't do to get GPS when I start up.

Or

Do you mean deleting your data file and booting up fresh for the first time?

Thanks.


the latter of the 2

[mssmison]

This works great on Donut:
http://tinyurl.com/yddutgm
Not fully functional as a lockscreen but it will be soon :)

[JeckyllHavok]

Hi there, i tried to make a new donut port from the latest cyanogenmod in G1 forum. It is a donut based build.When i try to boot the romm i get the android_power_wake message. Here is my logcat, it seems to have an odex issue:

/dalvikvm( 2185): VM cleaning up
D/dalvikvm( 2185): LinearAlloc 0x0 used 4100 of 5242880 (0%)
W/dalvikvm( 2185): JNI_CreateJavaVM failed
E/AndroidRuntime( 2185): JNI_CreateJavaVM failed
D/AndroidRuntime( 2191):
D/AndroidRuntime( 2191): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 2191): CheckJNI is OFF
D/dalvikvm( 2191): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2191): Stale deps in cache file; removing and retrying
D/dalvikvm( 2191): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---
E/dalvikvm( 2192): Inconsistent build rev: 17 vs 14
W/dalvikvm( 2191): DexOpt: --- END 'core.jar' --- status=0xff00, process failed
E/dalvikvm( 2191): Unable to extract+optimize DEX from '/system/framework/core.jar'
D/dalvikvm( 2191): Unable to process classpath element '/system/framework/core.jar'
D/dalvikvm( 2191): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2191): Stale deps in cache file; removing and retrying
D/dalvikvm( 2191): DexOpt: --- BEGIN 'ext.jar' (bootstrap=1) ---
E/dalvikvm( 2193): Inconsistent build rev: 17 vs 14
W/dalvikvm( 2191): DexOpt: --- END 'ext.jar' --- status=0xff00, process failed
E/dalvikvm( 2191): Unable to extract+optimize DEX from '/system/framework/ext.jar'
D/dalvikvm( 2191): Unable to process classpath element '/system/framework/ext.jar'
D/dalvikvm( 2191): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2191): Stale deps in cache file; removing and retrying
D/dalvikvm( 2191): DexOpt: --- BEGIN 'framework.jar' (bootstrap=1) ---
E/dalvikvm( 2194): Inconsistent build rev: 17 vs 14
W/dalvikvm( 2191): DexOpt: --- END 'framework.jar' --- status=0xff00, process failed
E/dalvikvm( 2191): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 2191): Unable to process classpath element '/system/framework/framework.jar'
D/dalvikvm( 2191): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2191): Stale deps in cache file; removing and retrying
D/dalvikvm( 2191): DexOpt: --- BEGIN 'android.policy.jar' (bootstrap=1) ---
E/dalvikvm( 2195): Inconsistent build rev: 17 vs 14
W/dalvikvm( 2191): DexOpt: --- END 'android.policy.jar' --- status=0xff00, process failed
E/dalvikvm( 2191): Unable to extract+optimize DEX from '/system/framework/android.policy.jar'
D/dalvikvm( 2191): Unable to process classpath element '/system/framework/android.policy.jar'
D/dalvikvm( 2191): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2191): Stale deps in cache file; removing and retrying
D/dalvikvm( 2191): DexOpt: --- BEGIN 'services.jar' (bootstrap=1) ---
E/dalvikvm( 2196): Inconsistent build rev: 17 vs 14
W/dalvikvm( 2191): DexOpt: --- END 'services.jar' --- status=0xff00, process failed
E/dalvikvm( 2191): Unable to extract+optimize DEX from '/system/framework/services.jar'
D/dalvikvm( 2191): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 2191): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framewor


Thanks for your help

[mssmison]

Generally Android Power wakeups are a problem with your init. did you make a donut.build file in the system folder?

[JeckyllHavok]

Generally Android Power wakeups are a problem with your init. did you make a donut.build file in the system folder

Yes it's all there, the phone detects it as a donut build, too at booting. Some days ago i ported the latest dwang donut from dream, which worked fine. Could you have a look at this? When i'm back home i will upload the system, i would love to see that rom on my device especialy cause i insert the eclair theme for that cyanogen rom version...

[JeckyllHavok]

I'm uploading the system folder as a zip file now. Theese are the steps i made:

-I take the system folder from this:
http://forum.xda-developers.com/showthread.php?t=567610

-put in the apps from the data folder

-copy the things from this theme: http://forum.xda-developers.com/showthread.php?t=577651 over (that was made for this rom)

-now the basics( bin+xbin folder from our vogue donut) and the libs from rootfs (from the donut folder)

-delete all*.prop files from the system folder and create a donut.build and copy the build.prop from the vogue donut rom

Hope someone could help me getting this running


Here this is the link to the zipped system folder, would be nice if someone could take a look into it:
http://rapidshare.com/files/313039624/jeckyllhavokscyanogenporttryBROKENdevonly.zip.html

[mssmison]

Cyanogens latest works have been problematic to get working at times,
Check with the other guy who ported one over already I'm sure he'll have the answer for you. :)

I'm uploading the system folder as a zip file now. Theese are the steps i made:

-I take the system folder from this:
http://forum.xda-developers.com/showthread.php?t=567610

-put in the apps from the data folder

-copy the things from this theme: http://forum.xda-developers.com/showthread.php?t=577651 over (that was made for this rom)

-now the basics( bin+xbin folder from our vogue donut) and the libs from rootfs (from the donut folder)

-delete all*.prop files from the system folder and create a donut.build and copy the build.prop from the vogue donut rom

Hope someone could help me getting this running


Here this is the link to the zipped system folder, would be nice if someone could take a look into it:
http://rapidshare.com/files/313039624/jeckyllhavokscyanogenporttryBROKENdevonly.zip.html

[jamezelle]

for the first time in like forever using this build and the latest market enabler i can see paid apps with verizon,

im faking t-mo US by the way

[Pandemic187]

I'm having two issues:

-At first My Location worked in Google Maps worked, and now it doesn't (GPS or network location).

-Wi-fi won't work. It tells me I'm not in range when I'm literally standing right next to my router.

Any ideas as to what might be wrong?

[polyrhythmic]

I've never been able to get network location to work in any build :(

Right now this build has become corrupted, and I'm away from my Linux box and can't easily debug it. It started freezing and having data issues and now hangs during boot at the Android logo... I'll try a new data.img at some point but first I have to pull my apps out of the old one, I think I can do that with bash script at the end of the donut.conf file. Perhaps it's also time to buy a new SD card...

EDIT: the console says it's stuck in a 'wakeup' loop, says VIBRATE 0 and wakeup with the date/time. Is there any way to pull my settings out from the data.img so that I don't have to start from scratch?

[nap286]

not loading. says mount: mounting /dev/block/mmcblk0pl on /sdcard failed: invalid argument
failed
failed to mount the sd card. cannot continue.
/bin/sh: cant access tty; job control turned off

[sshark]

Could someone tell me what is libreference-cdma-sms.so file?

I have not been able to send SMS on Donut and that was one of the files that I found were added compared to Cupcake, among other things.

I am thinking of taking this file out and see if it sends SMS...

----------
on the same note, how do I mount rootfs for rw? Last night, I was playing with eclair build and rootfs to see if I can get at least a build to boot up. But I was getting lot of power_wake_up (may be due to incorrect ref for libs? :-? :-(

Thanks,
sshark

[polyrhythmic]

on the same note, how do I mount rootfs for rw?


mkdir rootfs
sudo mount -o rw,loop rootfs.img rootfs/


Changes to the mounted rootfs (copying, deleting) must be done as root (su/sudo).

[160bpm]

Hi all,

I can't find on the net the follow answer:
What is responsible for what :)

Zimage: communication between OS and hardware (Network, GPS, wifi etc)?
Rootfs: The filesystem or something?
System: The system itself i think.?

[jamezelle]

Hi all,

I can't find on the net the follow answer:
What is responsible for what :)

Zimage: communication between OS and hardware (Network, GPS, wifi etc)?
Rootfs: The filesystem or something?
System: The system itself i think.?

zImage=compiled Kernel=drivers and such(yes it is what talks to the hardware)

rootfs=exactly what it says=root file system=the main files that the system does not provide that we require to run android

system=the system itself:) they vary

[plemen]

So you were porting over 4.2.5? Here is my port of it - you can do a diff or use it as reference. It's a little modified from his original but you can revert it back to his original by replacing the system/app and system/framework with his original.

For some reason the power off and reboot didn't work with this port.
http://www.4shared.com/file/154035325/4f553c92/system-plemenb091117.html

I'm uploading the system folder as a zip file now. Theese are the steps i made:

-I take the system folder from this:
http://forum.xda-developers.com/showthread.php?t=567610

-put in the apps from the data folder

-copy the things from this theme: http://forum.xda-developers.com/showthread.php?t=577651 over (that was made for this rom)

-now the basics( bin+xbin folder from our vogue donut) and the libs from rootfs (from the donut folder)

-delete all*.prop files from the system folder and create a donut.build and copy the build.prop from the vogue donut rom

Hope someone could help me getting this running


Here this is the link to the zipped system folder, would be nice if someone could take a look into it:
http://rapidshare.com/files/313039624/jeckyllhavokscyanogenporttryBROKENdevonly.zip.html

[plemen]

If you want to use your data.img with another build you can try deleting the contents of the /data/dalvik-cache and try it.

You can do this either by getting via adb or by mounting the data.img in Linux.

Good luck

I've never been able to get network location to work in any build :(

Right now this build has become corrupted, and I'm away from my Linux box and can't easily debug it. It started freezing and having data issues and now hangs during boot at the Android logo... I'll try a new data.img at some point but first I have to pull my apps out of the old one, I think I can do that with bash script at the end of the donut.conf file. Perhaps it's also time to buy a new SD card...

EDIT: the console says it's stuck in a 'wakeup' loop, says VIBRATE 0 and wakeup with the date/time. Is there any way to pull my settings out from the data.img so that I don't have to start from scratch?

[polyrhythmic]

Thanks, but I'd actually prefer to run this build. Since the system is read-only, I think it's more likely my data partition is corrupted. I'd like to retain as much of it as possible -- is there an easy way to boot to Linux shell before the Android VM is loaded? I forgot my Linux LiveCDs at home and don't want to download one over 3G...

[vilord]

i would suggest you rename data.img to databack.img, then boot up... you can then open terminal emulator, and then:

mkdir /sdcard/oldData
losetup /dev/block/loop4 /sdcard/databack.img
mount /dev/block/loop4 /sdcard/oldData
mkdir /sdcard/oldApps
cp /sdcard/oldData/apps/* /sdcard/oldApps

[plemen]

i would suggest you rename data.img to databack.img, then boot up... you can then open terminal emulator, and then:

mkdir /sdcard/oldData
losetup /dev/block/loop4 /sdcard/databack.img
mount /dev/block/loop4 /sdcard/oldData
mkdir /sdcard/oldApps
cp /sdcard/oldData/apps/* /sdcard/oldApps


nice - thanks.

[TeURaS]

I would like to report 2 bugs whit kaiser!

Boht actually do the same thing. Ok when i have Android running and when ever i press the red phone key the device screen goes black and only button it responses to is the power button and then the screen goes on and there is only black and withe stripes. THis allso happens if i let the phone do some prosess Forexpample i started to transfer my sim card info on the phone and it takes a while so i just laid the phone on a table and it kept going until the screen went to saving mode? or it just went black and agin it responses only to a pover button and the same white stripes are on the screen. And i have to reboot the device whit stylus.

[hexto]

Flashed this on Friday and dumped WM all together and it felt good to do so. I love this build. Its fast, battery life is good, and everthing just works with the exception of MMS and GPS. Not sure what to do about GPS. It was working on WM. How about MMS? any ETA on when that will be working?

Anyhow, I'm very happy overall with this build. More so than with any WM build I ever flashed. Thanks

[hexto]

Can I use the phone keypad with xt9 on this build?

[sshark]

keep this thread alive.

[jazmatician]

Second question: I can't get Bluetooth to turn on in Android. It sits and thinks for a bit, the blue light comes on, but then it just uncheck's the settings option and does nothing beyond that. Any ideas why? TIA!

Did you ever figure out how to get this working? I'm having the same problem.

[160bpm]

Guys.. this post was on the Kaiser forum.

Did not try it myself, because have problems with Android and Windows to get install the drivers :(

GPS IS WORKING

FYI...srwalter just got GPS working in donut. Thread here: http://forum.xda-developers.com/showthread.php?t=593786&page=20

What I did:
- Download http://sweb.uky.edu/~srwalt2/libgps.so
- run adb shell mount -n / -o remount,rw
- run adb push libgps.so /lib/donut/libgps.so
- reboot

And as zenulator said, welcome to google maps navigation!

[sancho1234]

My first time trying out the Android OS on my Kaiser. However, it no start. What is the problem? What I left out? See the attachment.

(I rename the Kaiser's file to default.txt.)

[polyrhythmic]

sancho1234, there are pre-made packages in the Kaiser forum, I suggest you find one that already works and try it.

[sancho1234]

Ok, thank you!

[pmcnano]

Hello Zen, using your build for like 1 month from now, atm using fat ext ext method, though i feel more stable using just one partition.

anyway, I have a doubt, any clue why my Market just shows FREE apps? Im running @ 320x480. But like I search Robot Defense, I just get the free version. Cant seem to get any FULL version at all.

Thanks

[polyrhythmic]

Hello Zen, using your build for like 1 month from now, atm using fat ext ext method, though i feel more stable using just one partition.

anyway, I have a doubt, any clue why my Market just shows FREE apps? Im running @ 320x480. But like I search Robot Defense, I just get the free version. Cant seem to get any FULL version at all.

Thanks

pmcnano, I tried to explain this to you in the Kaiser thread. This question has been answered many times, there are entire (http://forum.xda-developers.com/showthread.php?t=591372) threads dedicated to it. (http://forum.xda-developers.com/showthread.php?t=577974) In the future, please use the search instead of cross-posting across forums to get an answer.

Here is an example of some search terms that would help you. (http://tinyurl.com/y8efkdb)

[pmcnano]

pmcnano, I tried to explain this to you in the Kaiser thread. This question has been answered many times, there are entire (http://forum.xda-developers.com/showthread.php?t=591372) threads dedicated to it. (http://forum.xda-developers.com/showthread.php?t=577974) In the future, please use the search instead of cross-posting across forums to get an answer.

Here is an example of some search terms that would help you. (http://tinyurl.com/y8efkdb)

Thanks for your answer this time, i was searching full version apps not paid apps thats why I couldnt come across anything. I downloaded the Market Enabler, ran it, it worked, I can now see Robot Defense in fact I bought it, but now XD..It just doesnt download at all! It is hanging at "Starting download" I will try over Wifi in a while!, but meh!

thanks

[james33440]

i installed this and the home screen looks fine. however when i open any program or the dialer, the image isn't fullscreen.

any ideas?

[tatnai]

that's because you flashed with the 320x480 version, and the build you installed has a default lcd.density of 120. you have two options:
1. flash the 240x320 version, and things will look fine
2. edit build.prop or default.prop in /system/ and change the lcd.density to 160. multiple posts in flashable linux thread about how to do that. method 1 is easier.

[xoltrix2000]

I might of missed the post, but what other files or such do I need to run this build from NAND?

[Newbie16]

Love this build, seems pretty solid. Where is libaudio.so from? Its producing audio lag, would it be possible for the person who compiled libaudio.so to compile a version without this debug info?

D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
W/KeyCharacterMap( 403): No keyboard for id 0
W/KeyCharacterMap( 403): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/NetworkLocationProvider( 111): onCellLocationChanged [1634,287096]
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/dalvikvm( 403): GC freed 4028 objects / 919656 bytes in 156ms
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)

For now i'll keep testing...

[zenulator]

Love this build, seems pretty solid. Where is libaudio.so from? Its producing audio lag, would it be possible for the person who compiled libaudio.so to compile a version without this debug info?

D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
W/KeyCharacterMap( 403): No keyboard for id 0
W/KeyCharacterMap( 403): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/NetworkLocationProvider( 111): onCellLocationChanged [1634,287096]
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/dalvikvm( 403): GC freed 4028 objects / 919656 bytes in 156ms
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)
D/AudioHardwareMSM72XX( 93): AudioStreamOutMSM72xx::write(0xb618, 4096)

For now i'll keep testing...

dzo did the libaudio.so for donut. here is the source http://github.com/dzo/VogueAudio/tree/donut you can compile it yourself if you pull the donut repo and drop that source in mydroid/hardware/msm7k/libaudio

[vilord]

now why did I use srwalter's libaudio as a base when I built the one for eclair?? I feel dumb. I'll need to rework eclair's libaudio with DZO's work soon.

[zenulator]

now why did I use srwalter's libaudio as a base when I built the one for eclair?? I feel dumb. I'll need to rework eclair's libaudio with DZO's work soon.

:eek: i didn't realize you did that. dzo's should support voice search/dial and sound recording.

[Barogi44]

how do you install the htc ime on this? and where do you get the download?

[zenulator]

how do you install the htc ime on this? and where do you get the download?
http://forum.xda-developers.com/showthread.php?t=567294
You can put it on your sdcard and install it through astro or use adb and push it to /data/app/

[krisje8]

I just put this build on my Kaiser, but on sliding out the keyboard the orientation is wrong. I thought his was fixed ages ago?
I tried disabling Orientation in the settings, but that does not make any difference.

When I used 320x428 with density 160 (by accident), the orientation was right.
I then noticed that some apps are not fullscreen, so I read here that I should change the resolution. Since then I have not had good orientation. I also tried deleting my data.img file and start clean, but that does not help either.

How do I solve this? I'd love to be able to use android as my main os but with wrong orientation that's just simply impossible.

[bandur]

Use the latest zImage and your orientation should be fixed

[stajan]

Use the latest zImage and your orientation should be fixed am using the latest zlmage,downloaded from www.androidonhtc.com for my kaizar and showing the same orientation problem..its ok in 160 density(320*428 resolution),but not working properly in 240*320 res (density 120).can u suggest me a latest zlmage link?and letters in 160 density looking blurred.

[myn]

I haven't tested out the latest Donut AOSP but I have tried every other build. This one by far is the fastest.

The only thing I do have a problem with is streaming audio. With DoggCatcher and Google Listen, when you fast forward the audio to say 35 mins, it only seeks to say 2 mins yet it still reports it is playing at the 35 min mark.

I thought this was originally an issue with just DoggCatcher but after playing with other streaming podcast apps the experience was consistant.

I do not experience this issue with ION. And as I mentioned I haven't tried the latest Donut AOSP so perhaps this issue is resolved in that version.

Thanks again Zen :)

[krisje8]

Use the latest zImage and your orientation should be fixed

And which would that be?
I'm using the zImage from basefiles-20091116.zip , and I can't find a newer one.
The zImage from sourceforge is supposed to be newer, but I compared the md5 checksums and they're exactly the same.

There is a new rootfs, and I tried updating that, but I still have the same problem.

So what newer image are you referring to? Could you please post a link?

[jamezelle]

And which would that be?
I'm using the zImage from basefiles-20091116.zip , and I can't find a newer one.
The zImage from sourceforge is supposed to be newer, but I compared the md5 checksums and they're exactly the same.

There is a new rootfs, and I tried updating that, but I still have the same problem.

So what newer image are you referring to? Could you please post a link?

turn off auto orientation in settings

hold power button and it should switch

just because the basefiles are newer doesn't mean the zImage was changed. the rootfs was changed in the latest batch of basefiles. also search a little :o.

read=learn=know=:)

[benutne]

Did we ever get a fix for bluetooth? Also, someone a few pages back mentioned a fix for GPS. Has anyone tried that?

[zenulator]

Did we ever get a fix for bluetooth? Also, someone a few pages back mentioned a fix for GPS. Has anyone tried that?

The fix for gps is in the latest rootfs.img at sourceforce there is a link in my signature.

I've decided to update this build a little since things have pretty much settled down as far as donut development is concerned. So check back in a day or so.

I'll be adding:
Eclair browser
Maps with navigation
Cardock
News/Weather app/widget
Launcher with 5 home screens
Anything else let me know.

[benutne]

The fix for gps is in the latest rootfs.img at sourceforce there is a link in my signature.

I've decided to update this build a little since things have pretty much settled down as far as donut development is concerned. So check back in a day or so.

I'll be adding:
Eclair browser
Maps with navigation
Cardock
News/Weather app/widget
Launcher with 5 home screens
Anything else let me know.
I replaced my current rootfs.img file with the one you linked to and I get a "failed to allocate the storage" error when loading. Any ideas? I'm booting using haret if that makes any difference.

[zenulator]

I replaced my current rootfs.img file with the one you linked to and I get a "failed to allocate the storage" error when loading. Any ideas? I'm booting using haret if that makes any difference.

i don't know about that. i used it the other day to boot a couple builds with no problems.

[krisje8]

turn off auto orientation in settings

hold power button and it should switch

just because the basefiles are newer doesn't mean the zImage was changed. the rootfs was changed in the latest batch of basefiles. also search a little :o.

read=learn=know=:)

I tried disabling Orientation in the settings, but that does not make any difference.
(Yes and I did reboot after that)

The zImage from sourceforge is supposed to be newer, but I compared the md5 checksums and they're exactly the same.
I'm not sure whether you are familiar with checksums, but simply said, the newest zImage on the sourceforge page, and the zImage I have in the zipfile are exactly the same.

So if there is a newer zImage, where would I be able to find it?

As you said, reading helps :).

Thanks for the help anyway.

[jamezelle]

(Yes and I did reboot after that)


I'm not sure whether you are familiar with checksums, but simply said, the newest zImage on the sourceforge page, and the zImage I have in the zipfile are exactly the same.

So if there is a newer zImage, where would I be able to find it?

As you said, reading helps :).

Thanks for the help anyway.

you should get in touch with Newbie16 on the kaiser forum he should be your man to fix the orientation. :)

[roberto188]

The new Rootfs has crashed my system like 5 times in the course of 1 hour. The GPS is impressive, but I saw that the gps library was on another thread http://forum.xda-developers.com/showthread.php?t=606091. I'm using the rootfs from 12/11/09 and it is ROCK solid. EVERYTING works BEAUTIFULLY and fast in this build.

Two questions though...I'm not a developer but i read soemthing about creating a swap file to prevent the home screen from closing and taking a while to reopen after using a memory intensive app (This does happen occasionally). Should and how do we achive this?

Also, could someone post a rootfs with the gps fix from here http://forum.xda-developers.com/showthread.php?t=606091 using the 12/11/09 rootfs? Or maybe give me some direction as to how i can change the rootfs myself. Thanks zenulator for the BEST donut build in all of the forums!

[benutne]

i don't know about that. i used it the other day to boot a couple builds with no problems.

Well shoot. Am I doing something wrong then? All I did was pop the microSD card in a reader and replace the old rootfs file with the new one and that's what I got. I also tried formatting the card and copying everything fresh. Same error.

[roberto188]

Well shoot. Am I doing something wrong then? All I did was pop the microSD card in a reader and replace the old rootfs file with the new one and that's what I got. I also tried formatting the card and copying everything fresh. Same error.

I had a similar problem using the new rootfs yesterday...kept telling me the file stystem was read only...switched back to the 12/11/09 rootfs and it worked like a charm again....only not google NAV =(. Can anyone rebuild the 12/11/09 with the new gps update. The 12/11/09 rootfs works AWESOME.

[benutne]

I had a similar problem using the new rootfs yesterday...kept telling me the file stystem was read only...switched back to the 12/11/09 rootfs and it worked like a charm again....only not google NAV =(. Can anyone rebuild the 12/11/09 with the new gps update. The 12/11/09 rootfs works AWESOME.

I grabbed the rootfs located here (http://forum.xda-developers.com/showthread.php?t=606091) and it seemed to work great.

[roberto188]

I grabbed the rootfs located here (http://forum.xda-developers.com/showthread.php?t=606091) and it seemed to work great.

Oh I missed that one...i just saw the .so file. I'll try it out. Thanks!

[tatnai]

there seems to be a problem with the 2010-01-07 rootfs. I swapped it into my working donut from sd card setup, and it said it could not load the system, then wanted to create a data img. tried placing all files in android folder, same thing. switched back to 2010-01-06a rootfs and all is fine. something in the 01-07 version needs to be fixed.

[myn]

X1

I just switched to the 01/07/2009 rootfs 2 days ago and I began noticing serious slowdown of this rom. Reviewing the memory available it seems to be keeping more things (services/apps) in memory. This morning I checked and only 10mb was available.

Prior to using this new rootfs I had 25 - 35mb of memory available.

For reference I was using this rom (which I have been for awhile) and the following rootfs and zImage using haret and the ext2 method:

http://sourceforge.net/projects/androidhtc/files/2010-01-07/rootfs-2010-01-07.zip/download
http://it029000.massey.ac.nz/vogue/files/zImage-06-01-10



Thoughts?

[detour522]

*Work Email with Exchange support


Hi Zenulator,

Maybe this is more of a general android question then a custom ROM question... What about calendar, task and contacts? Will they sync with Android as well?

Thanks!

[zenulator]

Hi Zenulator,

Maybe this is more of a general android question then a custom ROM question... What about calendar, task and contacts? Will they sync with Android as well?

Thanks!

I've never used the app but I've always assumed the the work email app just does exchange email.

[myn]

I haven't tested out the latest Donut AOSP but I have tried every other build. This one by far is the fastest.

The only thing I do have a problem with is streaming audio. With DoggCatcher and Google Listen, when you fast forward the audio to say 35 mins, it only seeks to say 2 mins yet it still reports it is playing at the 35 min mark.

I thought this was originally an issue with just DoggCatcher but after playing with other streaming podcast apps the experience was consistant.

I do not experience this issue with ION. And as I mentioned I haven't tried the latest Donut AOSP so perhaps this issue is resolved in that version.

Thanks again Zen :)

Just tried out a few more Donut roms. The audio streaming seek and resume bug is apparently only in Donut builds. I loaded xRom (1.5) back and it resumed podcasts within DoggCatcher and Google Listen perfectly.

[spacepimp444]

Im having trouble with this loading. It keeps telling me that it failed to find system.img on sd card. This is what i have on the sd.

config folder
media folder
default
haret
initrd.gz
readme-basefiles
rootfs.img
system.sqsh
zimage

[jamezelle]

Im having trouble with this loading. It keeps telling me that it failed to find system.img on sd card. This is what i have on the sd.

config folder
media folder
default
haret
initrd.gz
readme-basefiles
rootfs.img
system.sqsh
zimage

try putting ALL of that in a folder called android

[tomduan]

where can I get the source for the build?

[spacepimp444]

it is in a folder called android. stilnothing

[zbubblez]

why doesnt my keyboard pop up?

[myn]

Just tried out a few more Donut roms. The audio streaming seek and resume bug is apparently only in Donut builds. I loaded xRom (1.5) back and it resumed podcasts within DoggCatcher and Google Listen perfectly.

Looks like this audio streaming resume issue is known and is being tracked. Unfortunately this hasn't been fixed in 2.01 either (not sure about 2.1)

http://code.google.com/p/android/issues/detail?id=4124

[tomduan]

Can I have the source?

[roberto188]

Is their any plans to get voice search and speaker phone to work with this build? Aside from bluetooth...which I know will never be implemented...these two would put the finishing touches on an AWESOME build.

[zenulator]

Is their any plans to get voice search and speaker phone to work with this build? Aside from bluetooth...which I know will never be implemented...these two would put the finishing touches on an AWESOME build.

they should already work.

[roberto188]

I'm currently using you're image with:
23-10-09 zImage
11-16-09 basefile package
14-12-09 rootfs

The speakerphone just straight up won't work in calls, it works in playing music ect. The voice search feature just hangs, and after it hangs and I restart the phone and the acore service terminates along with the phone service and I then can't see my contacts or make phone calls.

Any insight? BTW thank you so much for all your hard work! Do you have a donation link?

[zenulator]

did you start with a clean data image? i've never had those problems.

[myn]

Never experienced those issues with this build either.

It's by far the fastest build around.

[roberto188]

did you start with a clean data image? i've never had those problems.

Yes I stated with a clean image ...however I'm using a kaiser...perhaps thas the issue?

[benutne]

How does this build compare to plemen's AOSP Donut builds? (what the hell does AOSP mean anyway?)

[slyk221]

I just used shopsavvy and barcode reader, they seem to always force close. Does anyone know of a working 1D Barcode scanner?

[mssmison]

The resolution of the vogue camera is not high enough to do barcode reading sorry..

[hideffer]

The fix for gps is in the latest rootfs.img at sourceforce there is a link in my signature.

I've decided to update this build a little since things have pretty much settled down as far as donut development is concerned. So check back in a day or so.

I'll be adding:
Eclair browser
Maps with navigation
Cardock
News/Weather app/widget
Launcher with 5 home screens
Anything else let me know.

Any progress with these additions? This is my favorite donut build. It is fast and stable and everything seems to work beautifully. I have Google Maps with Navigation working very well with it. Additional home screens would be a great addition. Thank you for your contribution. I am looking forward to your additions.

[detour522]

speaking of google maps... how do i access the "starred" items? do i need to log in separately within the app? if so then how do i get to the sign-in screen? am i simply forgetting to turn something on in the google maps menu??

[zenulator]

Ok I've decided not to release an update for this. I'm just going to just go with a different build with a different theme. Nothing to crazy just a nexus themed launcher with 5 home screens and wallpapers. Plus updated apps and a couple additions. It's metamorph compatible meaning that if you install to nand or ext2 sd partitions you should be able to theme your own builds with it. I'll try to have it up later tonight.

[Shidell]

Interesting, can't wait to see what you have in store. :)

Have/are you reskinning CarDock, etc. yourself to fit? I had problems with that. I'd like to use "DeskClock", but that too isn't displaying properly.

[myn]

Interesting, can't wait to see what you have in store. :)

Have/are you reskinning CarDock, etc. yourself to fit? I had problems with that. I'd like to use "DeskClock", but that too isn't displaying properly.


Rescaling is such a tedious process :(. I wish there was a tool that would open the resources, resize based on a scale, iterating through each.

[Shidell]

Rescaling is such a tedious process :(. I wish there was a tool that would open the resources, resize based on a scale, iterating through each.

I might be able to build a tool to do so (in Windows), if it's uniform and straightforward. How complex would such a tool have to be?

(I don't know what needs to be edited to rescale packages.)

[myn]

I might be able to build a tool to do so (in Windows), if it's uniform and straightforward. How complex would such a tool have to be?

(I don't know what needs to be edited to rescale packages.)

I was thinking the same thing.

Unpacking an APK is easy enough (It doesn't even have to be automatic). If we can get access to the resource files we could run it through the windows app, rescaling the images.

And we could use the goodness of MetaMorph creating a package to inject the images back into the apk and sign it.

[Shidell]

I was thinking the same thing.

Unpacking an APK is easy enough (It doesn't even have to be automatic). If we can get access to the resource files we could run it through the windows app, rescaling the images.

And we could use the goodness of MetaMorph creating a package to inject the images back into the apk and sign it.

Yeah, I could probably automate the rescaling process pretty easily, as long as it's something like this:

1. Locate all files (.png, etc)
2. Change attributes of file from 800x600 (etc) to 240x320 (or whatever)
3. Save changes
4. Archive
5. Sign

It depends on how complex it is.. I'd have to walk through the steps manually once to get a feel for it.

[jamezelle]

Yeah, I could probably automate the rescaling process pretty easily, as long as it's something like this:

1. Locate all files (.png, etc)
2. Change attributes of file from 800x600 (etc) to 240x320 (or whatever)
3. Save changes
4. Archive
5. Sign

It depends on how complex it is.. I'd have to walk through the steps manually once to get a feel for it.

if you actually extract and re-archive the apks they wont work you will mess up the signature and the sha1sum and it wont work. the way i do it is just open the archive then drop in what ever i need to so it doesnt break the apks signature

[mssmison]

+1 James
This is the correct way to theme.. As to resizing the png's I use faststone image resizer in windows and it's works great.

[derringdo]

Is there any chance the HTC IME from the Tattoo will get ported to this build or to myn's Warm Donut build? I'd really love to have the Hero keyboard working properly in qvga :D

Loving the speed of these builds, the Tattoo builds are sadly too slow for me to use :(

[jamezelle]

Is there any chance the HTC IME from the Tattoo will get ported to this build or to myn's Warm Donut build? I'd really love to have the Hero keyboard working properly in qvga :D

Loving the speed of these builds, the Tattoo builds are sadly too slow for me to use :(

it aint pretty but here (http://0938a800.linkbucks.com) it works in QVGA

[derringdo]

it aint pretty but here (http://0938a800.linkbucks.com) it works in QVGA

Oops, I should have clarified. I installed that one but it looks pretty terrible in qvga, so I was hoping a proper qvga version would come out. I'm assuming the Tattoo IME is built for qvga?

Thanks anyway for the link!

[jamezelle]

Oops, I should have clarified. I installed that one but it looks pretty terrible in qvga, so I was hoping a proper qvga version would come out. I'm assuming the Tattoo IME is built for qvga?

Thanks anyway for the link!

yea that was a quick hack the tattoo one is proving impossible:( and well not worth it to port:p


sorry

[hhearld88]

where can i find the "lcd.density and resolution files to change them manually? I would like to find these and change them cause I would like to run at 320x480 res and just increase the size of my icons.. but ive never done it before so dunno where to find it, can anyone give me some info pls?

[jamezelle]

where can i find the "lcd.density and resolution files to change them manually? I would like to find these and change them cause I would like to run at 320x480 res and just increase the size of my icons.. but ive never done it before so dunno where to find it, can anyone give me some info pls?

if [ -d /sdcard ] ; then

echo "its in the default.txt, edit that!"

elif [ -d /nand ] ; then

echo "resolution is what you flash, density is set in build.prop"

else

echo "you're screwed"

fi

:p:p:p:p

lol sorry bored as hell!!!!!!!!!!!!!:rolleyes:

[mrkite38]

lol.........

[hhearld88]

hmm cant find "density is set in build.prop"

[jamezelle]

hmm cant find "density is set in build.prop"

it should be something like this


# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 120
# ro.sf.lcd_density = 160
ro.com.google.locationfeatures=1
'

where the #********* is commented out

[hhearld88]

it should be something like this


# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 120
# ro.sf.lcd_density = 160
ro.com.google.locationfeatures=1
'

where the #********* is commented out

I mean i don't know where to look to find this file

[jamezelle]

I mean i don't know where to look to find this file

its in the system.sqsh

and located on you phone:

/system/build.prop

you need to unsquashfs the system or edit the file via adb

there are plenty of tutorials on unsquashing system.sqsh files and setting up adb on xda


if you have adb set up do this

adb shell mount -o remount,rw / /
adb pull /system/build.prop .
#####make your changes in the file then
adb push ./build.prop /system/

then reboot phone

[hhearld88]

tried looking all over the forums and googling it, but i cant seem to find a tutorial on how to open the system.sqsh.. can someone post a direct link to a guide pls? or program i need to use.

[zenulator]

tried looking all over the forums and googling it, but i cant seem to find a tutorial on how to open the system.sqsh.. can someone post a direct link to a guide pls? or program i need to use.

first you need to run linux and have squashfs-tools installed. version 3.4 not 4.0+. install those and run unsquashfs system.sqsh. it will create a directory called squashfs-root and extract the files to it. i have a tutorial thread which i'll let you find. it should be in the next couple pages in the forum or you could use the search function. they are a big help. good luck.

[cp0020]

I set my default.txt to, mddi.width-240, mddi.height-320,lcd.density -120 and eveything is way too big!!! And I've tried changing the numbers around and its either too big or too small.any suggestions??? 1.5 looks good with 320 width and 480 Height but 1.6 just Looks like crap

[zenulator]

i just pulled the working java from the donut build i've been running. it's attached below. i know for a certain that it works because i've ran it with opera mini beta 5 and also several java games with no problems. the attached is just the apk which goes in /system/app and the lib which goes in /system/lib. check the java thread on how to push them manually through adb or you can make your own androidupdate.tar by making a folder called system with two subdirectories app and lib and then putting the Jbed.apk in app and libjbedvm.so in lib and tar the system folder up. good luck. i hope it's not an eclair specific bug.

[krwilson]

Anyone know what the name of the clock (widget) is from the screenshots on the 1st page of this thread??? And if so, can it be downloaded from the Market??? Thank you.

[clearcase]

Anyone know what the name of the clock (widget) is from the screenshots on the 1st page of this thread??? And if so, can it be downloaded from the Market??? Thank you.

BUMP......

[myn]

BUMP......

It's in AlarmClock.apk and themed that way.

[jfeyrer214]

does anyone have a .img file for ion with working market?

[jfeyrer214]

can you guys help me.. i have a xv6800 and the ion 1.5 build worked with a simple default.txt swap. but i really want a working market, any Chance i could get this working!!?

[jjfad]

Sigh. Was hoping to run this off a microSD card on my Spring HTC Vogue/Touch. Unfortunately, it just keeps crashing once I boot it up.

[mrkite38]

Guys - you'll get much better support in the android subforum.

Sent from my Full Android on Vogue using XDA App

[mrkite38]

can you guys help me.. i have a xv6800 and the ion 1.5 build worked with a simple default.txt swap. but i really want a working market, any Chance i could get this working!!?

please confirm it's a titan (xv6800) and not something else?

try this:
http://forum.xda-developers.com/showthread.php?t=745056

[mrkite38]

Sigh. Was hoping to run this off a microSD card on my Spring HTC Vogue/Touch. Unfortunately, it just keeps crashing once I boot it up.

This build is old. Look around in the android subforum, there are much newer, supported builds and a few walkthroughs/FAQs

try this:
http://forum.xda-developers.com/showthread.php?t=745056

sorry for the triple post, that was lame of me...