yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] vilord:
Katmandu: You want to use the new data.gz from my suppTools, you want to use the new initrd, and you can take your pick of system.img's, *all* should be compatible with both the data.gz and the initrd.

You don't need to set up your sync in 1.1 anymores, that was one of the biggest milestones in this new initrd, it gets rid of a *ton* of random application crashes etc.

As for zImage, I use the latest, but if you have better luck with an older one, feel free to use it.

Tony, looks like I made a mistake, the dmesg output was blank... apparently it only works if you can soft reset, not if you pull the battery. And, you need to use this command in debug.txt:

pwf kdmesg 0xe0000 0x20000
[Touch CDMA Android Development] cccpms6:
Could anyone please tell me how I would change the orientation of the screen? I am using vilrod's 1.5 build. I've had it change before by accident with the keyboard screen open and by pressing some other buttons but now I can't find the right combination. In settings there does not seem to be anything that would change it. Except the auto rotate with the sensors but this phone has no sensors.

Sorry for such a questions. Thank you
[Touch CDMA Android Development] mfpreach:
Please read Dzo's thread in the vogue section it explains the buttons. You press the camera button twice to change orientation.
[Touch CDMA Android Development] littlebrowntony:
thanks vilord,

i switched sd cards and it no longer freezes during load, so that's good -- however, once it reaches the 'welcome to google ion' screen, the touch screen does not respond -- it eventually freezes up and reboots to the 'android' load screen on it's own -- this happens over and over again until i soft reset. i'll read through the thread to see if others have encountered the same problem, but i went ahead and attached the dmesg file below anyway. thanks again!
[Touch CDMA Android Development] mssmison:
camera button twice.
[Touch CDMA Android Development] dzo:
I've never seen that before, looks like there is something odd about your phone, the i2c driver is failing. Must be that i2c is not initialised correctly what rom are you using, try booting android while swiping your finger across the screen, that might keep the hardware powered up.
[Touch CDMA Android Development] littlebrowntony:
thanks for your reply -- unfortunately, no luck with swiping my finger across the screen during various points of the boot process.

i am using the rom version 3.03.651.4 for sprint -- sorry for all the trouble, i sure do appreciate the help.
[Touch CDMA Android Development] cybik:
@vilord:

Your theory on the problem seems at the very least totally right. Nice call.

Now to see if I can fix that myself ^^
[Touch CDMA Android Development] mogulmaniac6800:
so if i downloaded these files, which files do i need to re-download when an update is released?
[Touch CDMA Android Development] vilord:
when i post an update, I'll always put notes in saying what was updated, for example:

UPDATE 23-June-2009:

-Updated initrd with new RIL that provides:

*reverts the verizon voicemail fix to get SMS back working on Bell Canada/Rogers.

*support for upcoming GPS drivers
[Touch CDMA Android Development] grktaurus83:
Wow... this post was a d**k move...

Update + today's date + GPS

HAHA! Was on the first page to verify before I even knew it. Kudos!

That was just feigned anger, of course~ I'm guessing the reaction was intentional though maybe you were giving us some insight into what you're currently working on...?

Though on a serious note, I'd hate to lose voicemail notifications. I thought that was a huge improvement.

Prairiefire posted in Martin's thread saying that he could reliably cause a "Bad SMS Encoding" message (it's weird how it happens for him). That may help figure out the problem (or at least another problem we might not have known about). I've linked his post below.

http://xdaforums.com/showpost.php?p=4012474&postcount=3930
[Touch CDMA Android Development] Ideal2545:
man your example had me searching for your update lol

btw... if you ever need hosting let me know, i have **** tons of space and more than enough bandwith
[Touch CDMA Android Development] vilord:
Yeah yeah, I figured I'd get a rise out of some of you... I'm uploading my stuff to Google Code now, keeping it spread out on different hosting sites just made me nauseous.

Once my upload finishes (sorry, 128K uploads suck a**) y'all will be the first to hear.
[Touch CDMA Android Development] grktaurus83:
I guess I'll be keeping this page up and refreshing every few minutes then. Haha!

Good stuff.
[Touch CDMA Android Development] hexto:
Any word on when MMS will be available for all carriers other than T Mobile. That's the one thing keeping me from using Android all day.
[Touch CDMA Android Development] vilord:
UPDATE 23-June-2009:

Note on this release: The GPS code was written in its entirety by other people, 99% of the work is from srwalter. Since it is all out there, I think he is okay with me posting it, but if he tells me otherwise I'm going to immediately pull it, and I don't want anyone else to repost.

Disclaimer: This GPS code has very little testing. No guarantees that it will work or not, that it will work after a reboot, or that it won't let the magic smoke out of some important chips in your phone. Please don't turn on GPS unless you're willing to take the risk (and possibly kill your battery).

Please don't spam the list asking for GPS help.

Please don't ask why it won't tell you how fast you are going, or why it won't tell you your altitude.

That is why it is called preliminary. Much of it still needs to be added.

And right now it only does true GPS, no triangulation, and no A-GPS, so may be slow to fix, needs a clear sky, and will drain the battery very quickly.

-Updated initrd with new RIL that provides:

*fixed SMS for Bell

*preliminary GPS support

*boot options for the SMS fix and for lcd density

-Updated system.img that provides:

*updated Maps.apk

*removed recovery.img

*preliminary GPS support

-Updated zImage that provides:

*preliminary GPS support
[Touch CDMA Android Development] vilord:
Just waiting for you to jump in and develop it :D

Or, just wait for android donut which should have a fully supported reference CDMA chain for SMS, MMS, etc...
[Touch CDMA Android Development] grktaurus83:
I'll be giving your new update a spin for a bit tonight.

You removed the link to Martin's zimage in your first post. I think it's very useful to keep that link there or at least add the link that leads to Martin's home page so people can download it from there. I'm not sure which method he would prefer (if any at all).

Man, you pump out updates constantly. I'm sure you know already, but I still think you underestimate how many people appreciate this work.

srwalter, you've just made a lot of people very happy. Regardless of how well it works (as I will be trying it shortly), you've taken GPS from barely a possibility to practically imminent. Congrats and kudos to you.

The same applies to everyone else involved, of course.

Enough of the fawning, it's time to give this baby a go!
[Touch CDMA Android Development] vilord:
I'll put the zImage link back once martin posts the GPS kernel on his site, for now you have to get it from my google code or compile it yourself
[Touch CDMA Android Development] grktaurus83:
I don't see the zimage on your google code...
[Touch CDMA Android Development] qwho:
I've been on the diamond for about 4 months, but if gps is going to be working for android on the vogue I think I will maybe come back. :D
[Touch CDMA Android Development] katmandu421:
Thanks for the assistance. Last night I reformatted my card and loaded everything from your supp tools including a fresh data.img, your latest init and dzo's latest kernel. Works a lot better now, but still have a slow "going home" experience when coming off of the browser or any apps that use the browser, ie FB. Very reproducible, on my device anyways. Doesn't matter how long I've been booted, if I pop open the browser and then go home, it takes like 10 seconds to load icons and another few to be able to swipe the screen again.

Could the culprit be the browser? I tried steel and it seems a little better.

EDIT: I also notice that once this happens, I get the blinking green light of battery death.

And thanks for the GPS tease ;)
[Touch CDMA Android Development] Ideal2545:
im blind i guess... but i dun see the newest zImage with gps support
[Touch CDMA Android Development] cybik:
He may or may not have removed it per srwalter's request.

Howto Request: How can I get the "hi-res" out of this initrd? lcd.density mentions width and height, but those were untouched for older, hires-enabled initrd's. I am at a loss, for I like the smaller sh*t :)
[Touch CDMA Android Development] jaredakelly:
i'm going to try this build out, hopefully i'll have the same success i've been having with the ion build.

how do i find out my username as password to connect to the internet?
[Touch CDMA Android Development] mssmison:
The new initrd needs the new default.txt to configure the lcd density.

You don't need a user/pass to connect to the net. The defaults should be fine. It still is the ion build from before, just an updated file that's all.
[Touch CDMA Android Development] vilord:
No, you're not blind, I am. I forgot to upload it, was tired last night and rather than checking if everything was there I just checked to make sure there were "all 6" files. But I forgot that with audioResources it is now 7. (And the zImage is now posted)

audioResources by the way you only need that if your ringtones get messed up, otherwise it should just work fine.

just set lcd.density=128 to get what the older hires enabled initrd's looked like. Changing the width and height resolution is optional
[Touch CDMA Android Development] cybik:
i'm asking because my vogue got stuck in an infinite loop while trying to boot with that. :/
[Touch CDMA Android Development] vilord:
Okay I just tested and there's a typo regarding lcd.density. As soon as you set it to anything it won't boot. I'll fix it at lunch.
[Touch CDMA Android Development] oxsolid:
test out beta-beta-gps

Removed---
[Touch CDMA Android Development] katmandu421:
HOLY MONKEY IT WORKS!!!

Make sure in settings under location, enable GPS. I did this, fired up google maps (new version, download was slow, but it did finally install for me) and told it to "find my location. It did within a few seconds, and I am indoors, though near a bunch of windows and it is a clear day.

WOW, TOO COOL!! Will continue to test and provide feedback, which is what this is really for afterall.

THANK YOU!!!
[Touch CDMA Android Development] vilord:
oxsolid, you may need a new data.gz to get google maps to load...
[Touch CDMA Android Development] hexto:
Cool. With MMS and GPS I'll never boot up WM ever again. I can live without bluetooth. :)
[Touch CDMA Android Development] jaredakelly:
deleted....
[Touch CDMA Android Development] oxsolid:
Sweet cuppin gps cakes!!!

THANKS KAT,

I just thought this release wasn't at that level yet, after i updated my system was runing way slow, and the gps didn't respond to anything...

so after reading your post, i just did the typical "start from scratch" with all of the new files... and VOLLA! It all works GPS INCLUDED!!!

AWESOME AWESOME AWESOME!!!
[Touch CDMA Android Development] KERKEDAGAIN:
OK..my wife thinks it's an exaggeration n she makes fun of me for it..but Android (thanks to you gents) keeps getting better EVERY DAY, every half hour in some instances!! haaa! GPS works fantastically..sure its semi-slow due to lack of A-GPS as mentioned but it's really only about 20 seconds more of a wait; very tolerable!! Keep up the great work use guys
[Touch CDMA Android Development] jaredakelly:
it works!!! this is awesome!! thank you soooo much!!

how can i make the icons and everything smaller? i'm sure someone else than vilord can answer, i'm sure he's busy
[Touch CDMA Android Development] cybik:
<old post is crap>

THAT IS AN OOPS IF I EVER SAW ONE. Maps requires the "control panel" to have the GPS option checked. The driver doesn't seem to take that into account, as I had correct Longitude and Latitude values. Basically, the bug is not where I first reported it to be!
[Touch CDMA Android Development] longjohn1980:
Does anyone else have problems downloading from the market? I get random success no matter what I do, it works great sometimes, sometimes it will download a few percent then say download unsuccessful, other times it will download 90+ % then fail, other times it will work as it should, and I have rebooted, fresh installed, and even formatted my card and fresh installed...
[Touch CDMA Android Development] oxsolid:
yup

I did, this last install improved my success alot though (hardly any of the apps failed the first install)... but the network is droping down to "edge" from "3g" a lot more often, and the modem just disconnects after a while...

I downloaded an appmanager program though... so i can copy my apps to my SD card and i dont have to redownload them everytime i use a fresh data.img

I've only rebooted once or twice so far with the new build, so my experience with losing the modem connection could be a fluke

-Ox
[Touch CDMA Android Development] Ideal2545:
okay so its 12:40PST right now, my battery was at 90 percent, i just turned on gps and data... ill report how long i get battery life with it currently .
[Touch CDMA Android Development] vilord:
Glad to hear things are working!

I've fixed the initrd.gz to get smaller icons/etc... now just set lcd.density=128 in your default.txt and it'll be just like the old initrdHiRes. Or set it to 100 and everything will be so tiny you can't see it. Or set it to 50 and it'll probably explode (okay I haven't actually tested anything but 128)

Standard/default is 160, so make your own judgement.
[Touch CDMA Android Development] vilord:
I must have missed something... what is the bug? Where is it? I'm confused.

-Jesse

Also FYI, I hear that mssmison will be pushing his system.imgs for all his themed builds onto google code, with the same GPS updates that are in my system.img, so if you like the themed builds keep an eye out :D
[Touch CDMA Android Development] grktaurus83:
Yea, I thought something was amiss~ Haha!

Works here too.

My first lock happened within 4 seconds, it was amazing. Subsequent attempts wouldn't lock, but I'm swapping out the initrd.gz now and going to give it another shot.

Again, thanks to all of you for this. This is epic.
[Touch CDMA Android Development] grktaurus83:
So one thing I notice immediately is that you get a little satelite icon in the status bar the first time you try using GPS in Google Maps.

On subsequent attempts (as in shutting of GPS, waiting 30 seconds, starting it up again) do not show this icon. This might explain why I'm not getting a lock after the first try.

Bug?

Anyone else seeing this?
[Touch CDMA Android Development] defianceX7:
I'm having some trouble getting this newest version running. I was running an older version before. I removed all old files and downloaded everything fresh. I get as far as "creating a new data store", it sits for the expected time (well, slightly more than I had expected, closing in on 10 minutes), then throws a string of errors and drops me to a linux prompt. The errors--

"

Creating a new data store

128+0 records in

128+0 records out

/init: line 62: /bin/e2fmsk: not found

e2fsck 1.40.8 (13-Mar-2008)

/bin/e2fsck: Superblock invalid, trying backup blocks ...

/bin/e2fsck: Bad magic number in super-block while trying to open /dev/block/loop0

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

mount: mounting /dev/block/loop0 on /data failed: Invalid argument

Failed

Faild to mount /data

/bin/sh: can't access tty: job control turned off.

After all that it drops me to a linux shell prompt.

Any ideas what I'm doing wrong? I'm going to put the old files back in place for a bit to see if there's a hardware problem, but I don't think that's it - then I'll try this again from scratch... but wanted to see if there was something obvious I'm missing. Thanks for any ideas! :)
[Touch CDMA Android Development] craig0r:
When you say you turn GPS off, do you mean that you go back to Settings and turn it off? Or do you just mean that you exit Google Maps and go back in?

I've just installed the build, and GPS works great. I only tested it for a few minutes on my smoke break, so I can't comment on battery usage yet, but it's accurate and fast. I find it hard to believe that aGPS isn't working, because it picked up my location faster than WinMo does.
[Touch CDMA Android Development] grktaurus83:
I went into settings, of course. Exiting maps doesn't turn off the GPS, just like exiting a browser doesn't turn off the data connection~ Haha!

Edit: I'm doing a fresh install now (though my first attempt was a fresh install as well) just in case. Yea, my first locks happen REALLY fast also. Unfortunately my first locks are also my last~

And I'm really liking the lcd.density=128 option.

Edit 2: As expected, I see the same behavior. Quick connect the first time I try it, then no icon/connection for subsequent attempts. Anyone else give this a shot?
[Touch CDMA Android Development] katmandu421:
Question on this: Are you just storing the apps on SD or are you looking to run the apps from SD? I looked into A2SD (Apps 2 SD) a while ago and got pretty overwhelmed. Any help you could provide in that area would be appreciated (If you are, in fact, looking to run apps fropm SD).

Cheers!
[Touch CDMA Android Development] katmandu421:
The typo was in default.txt or the code inside init.gz? Just wondering if I should re-download or just add the command to default. I'd like to try the 128 pixel density.

And again, dude, awesome work. I don't think my "GPS Bounty" post had anything to do with it, but I know that me and some other individuals need to pony up some cash for this!
[Touch CDMA Android Development] grktaurus83:
It's in the initrd.gz so download the new one and replace yours.

And don't forget that srwalter was the one who figured out the RPC calls to get GPS working.
[Touch CDMA Android Development] jaredakelly:
wait that doesn't make sense.....maybe i'm not reading it right......

128 is normal but 100 is tiny and 50 is bigger?

is a higher decimal amount smaller icons or larger icons?
[Touch CDMA Android Development] grktaurus83:
Explode as in your phone will spontaneously burst into flames and shrapnel. Haha!

Larger numbers means larger icons.
[Touch CDMA Android Development] jaredakelly:
o haha ok gotcha.

i replaced with the new initrd.gz and i put in exactally this right after the internet login and password:

"lcd.density=130"

it won't boot. all i get is the android splash graphic for waaaaaay to long and every once in a while it will freeze and try again
[Touch CDMA Android Development] grktaurus83:
Maybe 130 is not an option? Try using 128.
[Touch CDMA Android Development] jaredakelly:
vilord made it seem like you could set it to your preference.....i'll try 128 right now
[Touch CDMA Android Development] drprince89:
id just like to thank you and the community behind this project, you guys are doing a great job and this helps a lot until android phones are out on sprint.
[Touch CDMA Android Development] grktaurus83:
Ah, the gmail application looks bad at the 128 density. The entries overlap. Bah.
[Touch CDMA Android Development] Ideal2545:
but touch on ebay

put android on it

profit!

I dont need no stinkin gyroscope!
[Touch CDMA Android Development] drprince89:
after attempting to update to the 6-23-09 files i am noe haing some issues.

When i try to boot it goes into the terminal screen but after extracting data.gz i get the same message a couple of other people on here have. I am getting an error that says tty; job control cannot be turned off, or something along those lines. I tried redownloading everything and starting fresh but i still get that error.
[Touch CDMA Android Development] dragonxyz:
Google Partner Setup crash

I too am getting the same error message (google.partner.setup) crashing after reboot. Market downloads stopped working after that... been pulling my hair out (if I have any) to figure out what's causing the crash. Tried removing app one at a time and rebooting but no avail. End up wiping it out and start fresh. I'm using data file from 1.1 with 1.5 image. Any help would be appreciated, thank you.
[Touch CDMA Android Development] ljmeli:
I get the same issue with extracting the data.gz. Using all new files. I let it run for nearly an hour before I reset and noticed the data extraction had gotten to almost a gig in size. Any ideas what might be up? I will try slowly replacing files with DZO 1.1 and see if I get any luck
[Touch CDMA Android Development] dragonxyz:
Have you try using an older version of zImage? The one dated 4/20? Or try extracting data.gz manually and copy to SD as data.img
[Touch CDMA Android Development] grktaurus83:
Always experiment using a single author's files (if he has all of them) before trying to mix and match. You need to make sure the base system works before a frankenversion will.

All of you should try using _ONLY_ vilord's files and see if that works for you. He has everything posted on his google code page (check the first post in this thread for the link). Everyone is having success with them, so you should too~
[Touch CDMA Android Development] ljmeli:
Agreed. I used only vilord's files. I've been using his stuff for the past few weeks. This is the first run in I had with it (ie - after starting clean and using only his files), where as before we were forced to start with 1.1 to get the sign in started and then move over to 1.5.
[Touch CDMA Android Development] drprince89:
maybe you didnt read thoroughly but I did not try to make my own build, and one of those mentioning mixing and matching is only going to try that as a fix for the issue we are experiencing. You cant dismiss our issue just because youre not experiencing it personally. I even stated i have tried wiping all the files and recopying them to my sd card in the post you quoted, they were all the files from this thread, i have not used DZO's files since i started using this build.
[Touch CDMA Android Development] mssmison:
I just need to clarify something here. There is a significant lack of understanding about who's files to use etc.. The system.img file is just the OS. The initrd is just the ramdisk, the zimage is just the kernel. You can use anyone's system.img with anyones kernel and zimage. Obviously because of gps availability using vilords initrd/zimage combo is the best way to start. You can use any system.img that has been posted. foobar's, mine, vilords, dzo, srwalters. The only difference is the os version; 1.1, cupcake, ion, the theme and the included apps. They all use the same base files (cause we share our knowledge and files) to make it work on the vogue.

Which is exactly why vilord started the googlecode page. One place to access the initrd/kernel and system.img files. Vilord works really hard to update his kernel with any new changes that dzo or anyone else impliments or sends him, the same goes for the initrd.

I hope this clairfies some of these posts about single authors files, because we're all working on this together and make our stuff all work together.
[Touch CDMA Android Development] grktaurus83:
Woops, didn't mean to quote you on that one since you said you started fresh. I had initially turned on multiquote to say something else, but realized it was useless and forgot to unquote.

I wasn't dismissing the problem, just throwing out our typical response of "start fresh, all one author, etc." because that usually solves 90% of the problems people have. This was a "just in case" solution until someone else finds the real cause of this (because I don't know it).

Sorry about the ambiguity.