yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] kr4zyc1d:
Flash

Is there a better tutorial for doing the steps 1-4?

I had found this one: http://www.atwistedweb.com/xv6900/index.html

and it seems to be similar, however there are some ambiguous steps involved, and forgot what the link was that was directly related to the wiki for it. Thanks again.
[Touch CDMA General] sshark:
thanks both of you for reply, I dont have calendar app in drawer..hmm. May be I will flash again!
[Touch CDMA General] kr4zyc1d:
I am quite fond of the date widget. It is very nice!
[Touch CDMA General] sshark:
Does anyone know how to build application drawer? I can see under /system/app calendar app but don't have shortcut for that in the drawer.

I have already cleared dalvik-cache couple of times but to no avail!
[Touch CDMA General] sportsterBK8:
Mod/senior member

Does anyone want the

Car Home, and Dock Home

apps for the droid that will run on this build?

I know others can probably do the exact same thing as I did, but if a moderator would tell me if it is within forum rules, I would gladly post the apk's necissary to launch the two docks in this build.

Pretty much makes the droid feel of the build complete, let me know if anyone wants links

thanks.
[Touch CDMA General] grktaurus83:
There's no way there won't be takers on an offer like that...

I'd say upload it somewhere and link it here. If someone has an issue with it, promptly remove it.
[Touch CDMA General] grktaurus83:
So just loaded the build up right now... Not bad. Not bad at all.

Noticed that this build doesn't have the "have to press the power button multipled times to wake up the phone" issue that some other builds have. That was never really a big deal, just nice to see it respond immediately. This is probably the fastest I've been able to wake up the phone in any of the builds. Very nice.

Call quality is very clear. Might be the best I've heard in Android so far... Might also be me imagining things since this was an issue being specifically pointed out a few pages back.

Seems like this is out of alpha stage, so I'll drop some bug reports. If you still don't want any bug reports, let me know.

1) I'm getting haptic feedback on the dialer and lock screen even though haptic feedback is turned off in the settings.

2) Getting the forced close issue on ringer volume and brightness (as someone else reported).

3) Auto-correct is using contact names and not the dictionary (also reported before).

4) Buttons in Modem app are slightly distorted (looks like left and right edges are shifted down a pixel, but most likely it's the center that's shifted up).

Haven't really noticed much beyond that in the 30 minutes I've been tinkering with it. Very snappy build. Nicely done, Zen.
[Touch CDMA General] kr4zyc1d:
Just read this over and only have one solution: for the haptic feedback, check in spare parts and see if it is checked in there.

I am also getting the force close issue, But I don't use the predictive text, and auto correction isn't enabled. Lastly, the modem app on my phone appears to be alright. Sorry I couldn't have been more help on the other stuff, but hopefully that will work.
[Touch CDMA General] kr4zyc1d:
I sent a PM last night. Not sure if that is working for me however, it's not keeping any records of it and I don't think people are getting them...
[Touch CDMA General] kr4zyc1d:
Battery

Ok, so as stated earlier I had some battery issues. I turned off Facebook sync, but left my gmail sync on. I let it charge for a full 3.5 - 4 hours before going to bed last night, and woke up to a 30% life phone. I started poking around to see what my battery usage was like and it came up with 72% in Cell standby and 23% in Phone idle. Those were my largest. (this is in settings-phone info- battery use). Then I checked in spare parts - battery history and saw that since the last unplugging, it has been running for 100%. (The top most bar simply said "running"). Either way, I think I will turn off gmail sync today and do a full charge and see if that has any effect on the battery. If not, does anyone have any solutions? Thanks everyone, have a good day.
[Touch CDMA General] grktaurus83:
It was disabled in spare parts when I checked just now and it still did the same. Thanks for the tip though, forgot that the option was also in spare parts.

Yea, the predictive text shows only names. Not sure if it actually auto-corrects using those names since it didn't do that during my first few tests.
[Touch CDMA General] vilord:
updated rootfs on sourceforge now supports this... modified the memfree values as well, there were conflicting entries, and i picked a middle ground between them.
[Touch CDMA General] kr4zyc1d:
Just curious as to what the update was or the "this" is; happy to test!
[Touch CDMA General] grktaurus83:
Oh, another thing that didn't work was the Calendar widget. It says "Problem loading widget" whenever you add it.
[Touch CDMA General] vilord:
"this" is eclair 2.0.1 from this thread. The update was adding the modified init.**.rc files and updating init.

Sorry I haven't read the whole thread yet, was it reported that the calendarsyncprovider isn't working (or isn't there)? I don't see an option to sync to my work calendar...
[Touch CDMA General] bri3d:
It looks like the full sleep state is broken (wakelock issues?) - the LED never goes into amber blink and the Spare Parts power meter sticks with 100% Running for everyone.
[Touch CDMA General] polyrhythmic:
Wifi does not work on Kaiser, although I assumed this is a seperate issue from Vogue so we have some Kaiser devs working on it.
[Touch CDMA General] TheKartus:
It was only auto correcting to the names when I had autocorrection on.
[Touch CDMA General] zenulator:
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.SECONDARY_SERVER_ADJ 2
setprop ro.BACKUP_APP_ADJ 2
setprop ro.HOME_APP_ADJ 4
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.CONTENT_PROVIDER_ADJ 14
setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 2048
setprop ro.SECONDARY_SERVER_MEM 4096
setprop ro.BACKUP_APP_MEM 4096
setprop ro.HOME_APP_MEM 4096
setprop ro.HIDDEN_APP_MEM 5120
setprop ro.CONTENT_PROVIDER_MEM 5632
setprop ro.EMPTY_APP_MEM 6144

# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have HOME_APP at the
# same memory level as services.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15

write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144

# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16

# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5

Those should be the values.
[Touch CDMA General] vilord:
those are the right values for a device with more ram than ours.... is that what you'd like to use? it will kill off more background apps with the settings i picked, but it'll also run quicker...
[Touch CDMA General] bzo:
I'm seeing this too. I suppose this is the cause of the battery running down so quickly.
[Touch CDMA General] bzo:
just updated to the new rootfs, seeems to work fine for me. Is this still using conf/donut.user or is there an eclair specific config now?
[Touch CDMA General] Sodbuster:
still hanging

at the same place I was with 1.6.

Vogue, qualcomm processor.

I can't figure out how to format the microsd card, that could be an issue.

Another is this sqsh file. I'm running Win7RC.

Are Haret, default.txt and initrc supposed to be used with the eclair sqsh?
[Touch CDMA General] Sodbuster:
I should specify

'hanging' as in Linux hangs as it boots due to something or other taking too long. the text is about 2 point, and I can't make it out very well.
[Touch CDMA General] chunnell:
I'd like to know the answer to this too. Are the most up to date images on page 1?
[Touch CDMA General] berardi:
Bluetooth working for anyone?
[Touch CDMA General] kr4zyc1d:
rootfs

bluetooth is negative for me, i have not tried the new rootfs file however. Does the new rootfs fix any of the battery issues? Just curious
[Touch CDMA General] grktaurus83:
Noticed the battery drain just now.

I guess that also explains why this build woke up faster than any before... It wasn't sleeping! Haha!

Either way, this progress is amazing.
[Touch CDMA General] bri3d:
The new rootfs actually appears to be where the sleep state regression is - with the new rootfs and a 1.6 /system the device still won't sleep.
[Touch CDMA General] crobs808:
STEPS ??

Is there a how-to on this for someone who has NEVER been exposed to Android before? like 'STEP1: Do this..' then 'STEP2: Do this..'., etc...?

I see that the first post says you need some other files, but how to you do install Android on a currently Windows Mobile verizon touch (Vogue)?

Thanks
[Touch CDMA General] enatefox:
instructions. As for flashing a ROM, you need to check dzo's thread. I won't post the steps because (can't with my phone yet) and it can be risky if you fail at it so you need to read what he says to do. To just run it, look at the link above
[Touch CDMA General] szman22:
Could not place a call...

Looking good....most everything worked for me.....except placing a call. The call connected, but then I received a force/wait and then immediate reboot.

Nice work.
[Touch CDMA General] zenulator:
Well the Nexus One bootscreen works in qvga/hvga so I'll do an update soon. Plus there are a couple apps from the flan dump that work with 2.0.1. Hopefully sometime tomorrow I'll have a new image up.
[Touch CDMA General] Giggles 312:
Resolution?

so. i flashed with 240x320 and its beautiful and works awesomely. but the res is abit to big so i reflashed with 320x428 and now its like tiny. i guess there is no in between?

any ideas?

Thanks

Giggles 312

XV6900

Zen's 2.0.1 Flashed.
[Touch CDMA General] zenulator:
if your running from nand and use a resolution other than 240x320 you need to edit the lcd density in /system/build.prop and set it to 160.
[Touch CDMA General] berardi:
every time i go to settings and ringtone / notification volume it force closes, like if you want to set a diff ringtone volume than notification.

that, speed, and bluetooth Deal breaker for me right now :(

otherwise very nice
[Touch CDMA General] stiltzkin:
First of all, many many thanks to Zenulator - this is an excellent ROM and I'm really enjoying Eclair on my phone. Just about everything that's supposed to work seems to work for me (though I haven't really done any thorough testing...)

My battery life seems shorter - I only got about 24 hours out of it today with light usage (usually it can go a few days). However, this is only my first day with this and I suppose there could have been other factors. I know my panel type is set correctly, so that's not it.

Anyway, this is fantastic work! I'll stick around mashing F5 for all the latest goodies :D
[Touch CDMA General] zenulator:
if your running 240x320 set you lcd density to 120 you'll be glad you did. every thing scales correctly. if your runningg from nand edit the build

prob lcd density.
[Touch CDMA General] stiltzkin:
That's what it's been set up with from the start - 240x320 @ 120. Running from sdcard now but I'll try flashing to nand tomorrow.
[Touch CDMA General] zenulator:
set it to 110.
[Touch CDMA General] cricketman24:
If I am already running from the nand using dzo's method...

Do I just place the following files:

Rootfs.img from vilord (adjusted memfree values)

Squashfs System Image

&

Use the newest zImage from dzo

&

Make sure you start with a blank data.img

in my sdcard and just bootup?

Sorry I just want to make sure, that I have all the steps right without jumping the gun.
[Touch CDMA General] nGm@ze:
Will this work for the Raphael? Or is it like the Hero Sense UI build when your required to have a HVGA/QVGA screen to work, because Android 2.0 have been out for a while now and i am looking a around for it. Btw want to ask another question if HTC soon release a WVGA device with Sense UI does that mean it will work on VGA devices? Thanks in advance

nGm@ze
[Touch CDMA General] zenulator:
try it out. this is android 2.0.1 it's newer than 2.0. it should work for any resolution.
[Touch CDMA General] JeckyllHavok:
I would like to play around with some of the other eclair roms. Is it still the procedure as with porting donut/hero roms? (I mean files and libs)
[Touch CDMA General] babijoee:
It works all the way upto Android setup screen. The only thing in donut that caused a freeze was GPS. So is GPS being initialized upon booting into Android? If so is there a command which can disable GPS or even enable flight mode in startup.txt?
[Touch CDMA General] lupick:
Battery drain

Hi,

It looks like I have a ot of battery drain.....

anyone has got the same issue?

thanks

L.
[Touch CDMA General] zenulator:
for diamond/raph you'll need to unsquashfs the image and remove libgps.so and also edit the build.prop for lcd density 240.
[Touch CDMA General] babijoee:
Thanks for the tip. Will try it now:)
[Touch CDMA General] berardi:
any idea what would make settings force close repeatedly? specifically the ringtone volume (not the ringer volume buttons, but actually going into the ringtone volume setting)

Also calendar widget does not load for me.
[Touch CDMA General] babijoee:
Zenulator, did you receive any of the messages i sent today?
[Touch CDMA General] bri3d:
Look back up the thread - looks like something is preventing the phone from sleeping fully (check the Battery History in Spare Parts or note that the amber LED doesn't blink like usual when the phone is sleeping).
[Touch CDMA General] babijoee:
I've modified the system.sqsh

-remove gps.so and modify lcd.density and rebuilt the sqsh but now it just loads the Android boot screen and seems to loop forever. :(

here are the steps i taken.

-sudo unsquashfs system.sqsh

-delete gps and change lcd.density from build.prop

-sudo mv ./squashfs-root ./system

-sudo genext2fs -d ./system -b 180000 system.ext2

-mkdir ext2mount

(-sudo mount ./system.ext2 ./ext2mount) this step didnt work for me

system.ext2 is not a block device (maybe try `-o loop')

so i did what the terminal suggested and added -o loop

sudo mount -o loop ./system.ext2 ./ext2mount

-sudo mksquashfs ./ext2mount raphdiam.sqsh

I copied raphdiam.sqsh on root of sd and rename to system.sqsh

deleted old data.img
[Touch CDMA General] stiltzkin:
Do we have any idea what that might be? I didn't notice that my LED wasn't blinking until you mentioned it. In About Phone > Battery Use, the breakdown on my phone is:

Cell Standby 73%

Phone Idle 23%

Voice Calls 4%

Display 2%

In Spare Parts, Battery History says:

Running 100%

Screen on 7.3%

Phone on 1.2%
[Touch CDMA General] stiltzkin:
Ah, and if I tap "Running 100%" it says:

Time spent without sleeping: 54m 40s (100.0%). So yeah, it's definitely not sleeping properly. I had it charging until about an hour ago, FYI.
[Touch CDMA General] zenulator:
there are some issues with sleep. i havent had time to work it out.
[Touch CDMA General] zenulator:
you should just be able to unsquashfs make your changes and then mksquashfs squashfs-root/ system.sqsh. if your getting the android boot logo the your half way there. also make sure that your using the new rootsf it might need to be modified for your diamond/raph. if you can boot donut then you should be able to boot this. there isnt much difference in the init. try the rootfs.img in the kaiser thread there is a link a couple pages back.
[Touch CDMA General] babijoee:
Just tried that and same results as before. I can get into Android but it forever loop in Android boot. I'm looking into the rootfs now
[Touch CDMA General] JeckyllHavok:
Will they need a init.eclair.raphael.cfg in their rootfs?

Sorry, this is the wrong forum, hey babijoe open a new thread in raphael forum, so that things got sorted
[Touch CDMA General] babijoee:
opps yeah sorry if this is confusing you.

Yeah i'll create a thread soon. Thanks
[Touch CDMA General] JeckyllHavok:
No problem man, i'm a kaiser user. Here you can post non device specific questions. When i got some time i will have a look in the rootfs for you:)
[Touch CDMA General] babijoee:
Thanks that would be lovely :D
[Touch CDMA General] babijoee:
Sorry this will be my last post for this topic and i'll create a new thread in Raphael forum.

I've done some further testing for rebuilding squashfs. It seems that even if i dont modify anything and recreate the system.sqsh. It doesnt boot the same but rather it just loops at the android boot logo. :confused:

Thanks for everything so far.

Edit: Nvm forgot to change file permissions. :P
[Touch CDMA General] cbaty08:
Is anyone else eperiencing a crackling external speaker?

At the end of a phone call, the phone will beep. mine beeps with a horrible crackling to it....

I went into YouTube and the sound there was horrible too. I have turned down volume but the problem still persists... Works fine in WinMo though...??
[Touch CDMA General] crobs808:
Please tell me what I am missing... (see attached screenshot of SD card root files)

I run the exe file (haret.exe) and it shows the Linux penguin, and a lot of text, but freezes after a couple minutes. No more scrolling, and nothing happening. I left it there for 10 minutes once to be sure, and nothing changed. I am doing this with a 16GB Class-6 MicroSD card, and all the files shown in the attached image.
[Touch CDMA General] KERKEDAGAIN:
whats the last line of text say when booting?
[Touch CDMA General] polyrhythmic:
Freezes where? It looks like you have the right files, but the console output will be more telling.
[Touch CDMA General] stiltzkin:
Well you don't have a data.img, but I assume that's because you're booting for the first time. Check your panel type in default.txt. If you're on Verizon, it should probably be 1. Sprint or other carriers are 2 or 3, IIRC.
[Touch CDMA General] crobs808:
It says...

[ 393.195129] r5:00000000 r4:00000000
[Touch CDMA General] bri3d:
Do you see a line that says BUG:, OOPS:, or PANIC: ?

That looks like the end of a kernel register dump which means something died hard somewhere.

What kernel (zImage) are you running? Have you tried the latest from http://cs-alb-pc3.massey.ac.nz/vogue/files/?C=M;O=D ?
[Touch CDMA General] Farmer Joe:
well i got this running on my 6900. finally figured out some simple stuff and off it booted. took a while on the first boot, but it loaded and had me go through the setup wizard.

all in all its good so far. it kinda jerky sometimes though. dont know whether it just an unfinished work, or the phone just cant keep up with 2.0.

i did run into alot of bugs with this tho. first thing it did when i got the setup wizard was give me an error saying the keyboard crashed. the settings crashed alot too. when trying to change volumes or the screen brightness.

ill keep track of this tho and well see what comes along here in a couple weeks.
[Touch CDMA General] crobs808:
nope, no lines that says that. but now my last line is...

[ 650.93014] r5:00000000 r4:00000000

It keeps getting higher and higher every couple minutes :(
[Touch CDMA General] crobs808:
If I download this file...

voguimg-240x320-17-12-09.nbh

Can I just rename it to "VOGUIMG.nbh", put it on my card, and flash from the boot loader?

...oh dang, I cant flash a NBH via card if the card is over like 2GB or 4GB right? Dang, I only have a 16GB :(
[Touch CDMA General] Giggles 312:
ok so i tried something stupid. i tried to edit the build.prop in android with astro. and changed the lcd.density to 110 with 240x320 but i realised that it wouldnt work. so how would one change the build.prop?

sorry for mah noob-ness. :D
[Touch CDMA General] stiltzkin:
Just unpack the system file on your computer:

unsquashfs system.sqsh

Edit build.prop in the resulting extracted folder.

Then repack the system:

mksquashfs squashfs-root/ newsystem.sqsh

Then delete your old system.sqsh, put newsystem.sqsh on your card and rename it to system.sqsh. Make sense?
[Touch CDMA General] Giggles 312:
yep thanks a bunch. lemme guess i need to use linux. good thing i haz unbuntu :D thanks again.
[Touch CDMA General] jamezelle:
yea in linux, your gonna need squashfs-tools to do that here
[Touch CDMA General] stiltzkin:
Well he's using Ubuntu, so it's in the repos:

sudo apt-get install squashfs-tools
[Touch CDMA General] cbaty08:
Anybody running this on Verizon?

I called my gf and my number came up as a diff. number on her phone... Also 20% or so of my calls have static.... Any Ideas?

.....Or on the external speaker issue?

Thanks
[Touch CDMA General] stiltzkin:
Yeah, I'm on Verizon. But I don't have any of your issues. For the speaker static, maybe try turning the volume up and down a few times? That's resolved minor sound problems for me in the past. No problems with calls or texts though. For me it's just battery life (which it sounds like zenulator is at least aware of).
[Touch CDMA General] polyrhythmic:
This is bad advice. You do not want the version from the repos. You want version 3.1 or lower as linked above.
[Touch CDMA General] cbaty08:
I am def. feeling that batt drain too, luckily I am always by a charger...

Do any of you know what file or folder contains the driver for the external audio? I think I want to try to replace it and see if it clears up... I dunno, a noob attempt but Its buggin' the $hit outta me!! lol

PS Anyone know the reason I would have the loading data constantly up? The little circular icon isn't spinning, even after a reboot?
[Touch CDMA General] stiltzkin:
Oh, well my apologies then - I had been using 4.0. Is there an important difference between the old and new versions?
[Touch CDMA General] polyrhythmic:
To be more specific, as noted here and here you need to have version 3.1, 3.4, or 3.7 . Versions 4+ build the image differently and our Android Linux won't be able to mount it.
[Touch CDMA General] crobs808:
Still cannot get it to work...I tried the premade NBH file with the RUU utility and the rootfs.img on the SD card, as well as the SD card method with all files on the SD card. Neither worked.

Oh well, back to WM6.5.5
[Touch CDMA General] Pandemic187:
Here's a bug: it doesn't have the newest version of Maps, and when I try to update it, the installation is unsuccessful. The same thing was happening on those Donut builds with some Eclair apps till someone fixed it.

Same thing happens with the Facebook app, by the way.

EDIT: Sorry, I meant to post this in the Kaiser Eclair thread.
[Touch CDMA General] bri3d:
It's a bug in the Vogue build too - I think it has to do with the keystore.
[Touch CDMA General] zenulator:
i've updated maps from the market with no problems. as for the power issues something is keeping the phone from sleeping. i'll run the generic sdk build and see if the problem is still there. it could be that the sdk emulator image doesnt sleep properly since it wasn't built to run on real hardware. or it could be the addition of the motorola google apps.
[Touch CDMA General] bri3d:
Interesting - I was unable to update Google Maps - tried several ways:

Fresh data.img pre-reboot.

Fresh data.img post-reboot.

Checked out logcat and noticed a lot of periodic permissions errors on the keystore dir. chowned it. Errors disappeared.

Still didn't work.

The failure is "the application was improperly signed" which also points to a key issue.
[Touch CDMA General] szman22:
Ditto on the google maps error - I am also receiving the same error on update.

Maybe related - the google voice app has disappeared for me in the Market. It just doesn't exist.
[Touch CDMA General] anotherhawkeye:
I have the same problem with google maps.
[Touch CDMA General] wdbanks:
This build works perfectly for me with not bugs on my Vogue. I like it the best so far. Thanks Zen.
[Touch CDMA General] Pandemic187:
Alright, so I'm not the only one having problems with Maps then.