yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] aven_soulgazer:
I tried srwalters zimage last night. It doesn't work on my screwed up Sprint phone. I'm guessing none of the new ones ever will. I'm thinking about trying to get them to get me another vogue and hope that phone works fine. Not sure how to pull it off, they won't do it just because software won't run.
[Touch CDMA Android Development] pchasco:
What problems are you experiencing now? As far as I know, NO modifications are made to anything on your phone by these Android images. All data is saved on the SD card. The worst case scenario is that your SD card is corrupted beyond repair. Your phone should still work though.
[Touch CDMA Android Development] mfpreach:
works fine for me.

Sounds like you have memory card problems.

I have noticed that Android is ALWAYS broken for you. Maybe try another SD card because I never have any of the problems you do.
[Touch CDMA Android Development] tatnai:
I'm guessing you have lcd.density set to 128 or 120. google maps only works with default lcd density (160), with any other it will force close at different portions of the program, typically with directions or with Lattitude. just delete that entry from the default.txt string or set to 160. you can change the screen resolution to 360 x 480 in the default.txt to compensate so you still have a large amount of screen real estate.

see here http://xdaforums.com/showpost.php?p=4053962&postcount=554
[Touch CDMA Android Development] vilord:
I should be able to bring srwalter's updates into the the bootlock image, it may take me a few days as I'll be out of town this weekend.
[Touch CDMA Android Development] aven_soulgazer:
nice. Could it be something as simple as using the wrong panel type that's causing it to freeze? Just wondering if maybe sprint is using a different panel type in their refurbs if only the refurbs are having problems

Edit: Scratch that, the old zimage works on panel type 3 so that shouldn't be the problem then right?
[Touch CDMA Android Development] lip:
Hi,

I tried this but when I try to use the keyboard in landscape I get a forced close. Any ideas?

Am I supposed to just replace the zImage file on the sd card with yours or do anything else?

Thanks.

LIP
[Touch CDMA Android Development] dzo:
I've fixed the camera, it now shows the raw image when you take a picture and should switch back to preview mode properly after the picture has been saved.

To try it, get the latest initrd.gz from the google code site. (I didn't make a new bundle).

Martin
[Touch CDMA Android Development] tatnai:
Trying now . . . guess I may as well be testing something since I'm up checking this damn site every 10 min anyways . . . :D.

EDIT 1: It appears to work just like the last one did for me. I can initially see preview mode, take pic, I get the thumbnail raw image preview in upper left corner, but preview mode does not auto refresh. I can still cycle into album by pressing thumbnail raw image, and then cycle back to the camera and THEN get the preview mode active again, but I could do that with the last release.
[Touch CDMA Android Development] dzo:
No, it's just the initrd if you want the new button mapping too, use steven's kernel (zImage).
[Touch CDMA Android Development] jaredakelly:
thanks! it's great to have google maps working, i just wish i didn't have to sacrifice my screen being soo blurry :D
[Touch CDMA Android Development] Snakehn:
Is there any way to remove that blue keyboard when you push the camera button?
[Touch CDMA Android Development] tatnai:
It appears to work just like the last one did for me. I can initially see preview mode, take pic, I get the thumbnail raw image preview in upper left corner, but preview mode does not auto refresh even though it allows me to continue taking pics blind. I can still cycle into album by pressing thumbnail raw image, and then cycle back to the camera and THEN get the preview mode active again, but I could do that with the last release.

Maybe I downloaded too early, it said updated 13 min ago when I downloaded it. Hmm, don't know.
[Touch CDMA Android Development] tatnai:
Using the kernel from here will remove it: http://xdaforums.com/showpost.php?p=4053646&postcount=546
[Touch CDMA Android Development] dzo:
Looks like you may have got a cached copy of the old one, I've added it again as initrd-cam, this may help.
[Touch CDMA Android Development] tatnai:
They were different sizes when I compared them. DLing again, will retry.

OK, I'm still getting no change, i.e. no auto return to preview mode after picture. Maybe it's just me or my phone, I guess let's see what others find.
[Touch CDMA Android Development] Snakehn:
Cool, i tried this and that keyboard is gone ;) but now the camera doesn't come up LOL

Now i like how while holding the camera button i can turn the volume up or down with the slider but i have a question...

is there a way to map the hardware keys so that:

Slider up: Volume up

Slider down: Volume Down

Camera button: Camera

Hold Camera button: Rotate

end button: end call and back, hold for Menu

power button: sleep, Hold for phone options (Silent, airplane, power off menu)

or End button: end call, back, hold for phone options (silent, airplane, power off menu)

Power Button: Sleep, hold for menu.

Sorry if it sounds stupid, just wondering.
[Touch CDMA Android Development] grktaurus83:
For anyone having issues with directions in google maps, this solution fixes it. You've said this a few times tatnai, but it bears repeating because people somehow keep missing it.

Other notes:

1) Gmail items do not overlap when dimensions are set to 360x480, which is nice.

2) The dialer keys don't overlap anymore.

3) HTC IME still has the black/unused section on the right hand side of the compact qwerty.

4) The screen does seem more blurry than using the lcd.density=120 option, but maybe I'm just remembering it differently.

So if you're looking to avoid these problems, switch to the settings tatnai suggested.
[Touch CDMA Android Development] tatnai:
Yeah I finally do agree it is a little blurrier at 360x480, but I prefer that to the "clunkiness" of 320 x 428 (where you also can't see all the screen of some select programs that require 480 screen height), or the slightly scrunched aspect ratio of 320 x 480. Pick your poison.
[Touch CDMA Android Development] qwho:
I was wondering why my google maps froze every time I tried to route. I don't really care though, I would rather have zero blurryiness with 240x320 lcdd-128 than have headaches all day and be able to use directions on google maps.

At some point I think someone will figure out a way to get everything working when screen settings are set that aren't blurry. Obviously that will have to wait as many, many other things are more important.
[Touch CDMA Android Development] vilord:
eventually we'll be using lcd density of 120 with screen resolution of 240x320.

But, that will have to wait for donut which adds full support for alternate resolution and alternate density screens.
[Touch CDMA Android Development] drprince89:
As great as it might sound at first a mapping like that, if possible would be way too confusing, if you think about it im sure yoiu use your volume sliders way less than you would use the menu and back buttons so mapping it like this would be very ineffective, i love how its set up with the camera button as a modifier now, if anything it might be good to map some functions to camera+up on d pad and camera+down on d pad like camera launch and something else.

Maybe its just me but i dont use the volume sliders nearly enough to make them a primary function over the menu and back buttons.
[Touch CDMA Android Development] jaredakelly:
i googled but couldn't find anything...

how do i change the preferences for the end button again? i found it one time but never again
[Touch CDMA Android Development] craig0r:
It's in Spare Parts -> End button behaviour
[Touch CDMA Android Development] jaredakelly:
thanks.....it didnt have the option i was looking for. i was trying to find a way to ignore calls, when i push the end button it doesn't ignore calls anymore?
[Touch CDMA Android Development] craig0r:
I think it's a bug in cupcake. There might be an issue filed at the google code site, but if not, maybe submit one. People don't use that site enough for bug reporting. I'm sure the devs would rather have all the issues posted there rather than trying to stay on top of the forums constantly.
[Touch CDMA Android Development] KERKEDAGAIN:
The back (slider up) button ignores the call..you'll still have to silence the ringer but at least you can get back to what you were doing
[Touch CDMA Android Development] vilord:
end button doesn't ignore calls at all yet.

you can silence incoming calls by pushing camera then volume down.

I will update once I have the RIL fixed, but I need to code the HANGUP_WAITING_OR_BACKGROUND function... it appears that windows just sends ATH, but I need to verify if that also occurs when there is another call in progress and if there is a data call in the background
[Touch CDMA Android Development] rdm26:
Remap Menu Button?

Is there a way to remap the menu button from being the volume slider to the square outer ring button on the front of the phone?

Also, Android rocks. Thanks for everybody's hard work that went into this!
[Touch CDMA Android Development] tatnai:
Similarly, the dpad has function in android, so mapping to those buttons would lose function; if you used the camera-shift + dpad, once again as well stated by drprince89, most people use menu and back way more frequently than volume, so it seems more efficient that changing volume requires camera-shift + volume slider, with menu/back taking primary function of the buttons. These functions are written into zimage right now, so I doubt we will get changes to buttons on individual request unless a) you edit zimage yourself, or b) everyone wants it AND srwalter or dzo want it too, and I don't think that b) is the case right now.
[Touch CDMA Android Development] tatnai:
so has anyone gotten the new camara initrd from dzo to work - it's supposed to automatically go back to preview mode after taking a pic without having to use the switch to album trick. wondering what I need to do to get it to work.
[Touch CDMA Android Development] jaredakelly:
it works fine for me
[Touch CDMA Android Development] brsev:
Yes, you're right, volume controls aren't used nearly as often, but considering how often one uses menu and back, I feel like they should be easier to get to (especially one-handed). My ideal solution would be green button as Menu, red button as Back, and use long-press green for answer and long-press red for ignore/hang up.

It would be awesome if they could be customizable at a software level or through default.txt, too. I don't know about you, but I hate the little volume slider on the Vogue, and whenever somebody else is using my phone it can be more confusing than it should be.

But still, this shouldn't be a priority, just something to keep in mind.
[Touch CDMA Android Development] tatnai:
this setup would make it very difficult to answer the phone one handed. . .

and would make answering your phone very confusing to someone else - :D

Jokes aside, I don't know if we can do double press functions in android like you can with AEButton plus in WM, but for one handed operation double tap green and double tap red could be used for menu and back, easy to complete one handed.
[Touch CDMA Android Development] refthemc:
Only thing that bugs me about the buttons is that i think the red button and power button functions should be reversed
[Touch CDMA Android Development] dzo:
Looks like it might not work at resolutions other than 320x428. It's also making very large images and thumbnails, I'll fix that soon.
[Touch CDMA Android Development] tatnai:
Can't wait until we get donut and all this resolution stuff is a thing of the past. Thanks DZO, easy enough for me to live with it as it is.
[Touch CDMA Android Development] jaredakelly:
my resolution is not 320x428 and the camera works just fine
[Touch CDMA Android Development] refthemc:
Camera is working fine here to
[Touch CDMA Android Development] dzo:
It does work but it was generating very large jpeg files so I've uploaded a new initrd.gz. I've also put a libcameraservice.so there so you can update it without having to reboot, just do:

adb push libcameraservice.so /lib

adb shell killall mediaserver

You will need the new initrd for your next boot.
[Touch CDMA Android Development] ~David:
I would prefer that too :) It makes more sense for the power button to be the power button lol
[Touch CDMA Android Development] drprince89:
I agree with this as well, i think the layout is perfect as is otherwise, i just dont see the need to revamp the whole button layout since it works just fine for most people right now.
[Touch CDMA Android Development] vilord:
/me is posting from the phoenix airport in android :D

I say leave the buttons alone, I don't want to push power to end a call!

I fixed ignore call/send to voicemail, but didn't have time to build a new initrd. Martin, can you pull down the ril from git, build, and include in your next initrd post?
[Touch CDMA Android Development] tatnai:
You rock! Does it use the red key to ignore call? Geez, you all rock. I can't say how thrilled I am to be using Android, double props to you DZO for plowing ahead at the beginning.
[Touch CDMA Android Development] drprince89:
I feel like i cant say that enough myself. You guys have given new life to our phones, this project has made it so much easier to wait for the sprint android phone after they jewed us SERO customers on the pre.

I wasnt expecting GPS and camera to be working on cupcake for a while but vilord and dzo you guys have gone above and beyond the call of duty with his project.
[Touch CDMA Android Development] Ideal2545:
look, your used to the way windows mobile handled the hardware... open your minds!

on another note, it actually makes alot sense to have them the way they are now... in the earlier releases we mapped the buttons all over the place. Everyone complained after others released their modified keymap version and switched back to the original. Take it from someone who has been following this since the beginning... they are better left the way they are
[Touch CDMA Android Development] dzo:
OK, all done, latest initrd on the google code site should include this, I've not tested it though.
[Touch CDMA Android Development] moekind:
Is it possible to get button configuration in the default.txt

or a program that maps buttons in android?

So people can customize it the way they want.
[Touch CDMA Android Development] vilord:
Thank you!

I tested it with a fresh call, red key shuts it up. Didn't have time to check canceling a call waiting call.

For the buttons, we have other priorities, stuff that is broken like: New kernel, direct booting, bluetooth, speakerphone, etc.
[Touch CDMA Android Development] oxsolid:
Buttons

YOU ALL ROCK!!!

- i had ideas for the buttons too, and i agree that initially the phone was a little difficult to figure out... i think it's probablly because the hardware wasn't built around android.

After using it as is for a while i'm starting to find it very natural..( second finger -power button, third finder-slider down to unlock is easy one handed) --- i find it way better than lock2.0[slide to unlock] that i had originally gotten as an alternative

--also yes, we all have slightly different useage patterns that would cause us to omit certain funtionallity or remap functionallity.... but as vilord has stated, there are more important things to do...

and as a group we should hold off with our more ecocentric cosmetic changes as long as possible... this will distract the developers less, (it must get old hearing a new key mapping idea every third day)--- as for being able to map the keys yourself in default.txt... that is probablly what will happen one day... but i my guess is that the community as a whole will appreciate the other improvements more.

Thanks again Dev's for your hard work! And thanks to the rest of the community for your enthusiasim!!
[Touch CDMA Android Development] mfpreach:
"Jewed" ? :(
[Touch CDMA Android Development] mfpreach:
Just my opinion, but I don't think you should spend time working on direct booting. It is dangerous not being able to fall back to windows mobile, especially if there is a memory card problem or whatever, its easy enough to just run haret.

JUST my .02 though.

Great work though as usual.
[Touch CDMA Android Development] Snakehn:
Direct booting should be great once all the remaining issues have been resolved, it will be great to ditch winmo.
[Touch CDMA Android Development] mfpreach:
I agree if it were flawless, but I think its quite a while away from that, it would be better to put that on the backburner is all i'm saying.

Seen?
[Touch CDMA Android Development] thoughtlesskyle:
did the charging issue get worked out, i know a long time ago (pre 1.1) there was an issue where the battery didnt know when it was full and it could ruin the battery, any info on this?
[Touch CDMA Android Development] rdm26:
Button swap

I would also prefer that too.:) Anyway, it is really nice how it is.
[Touch CDMA Android Development] tatnai:
There have been huge changes in power management and charging over the last couple of months. I believe this has been fixed.
[Touch CDMA Android Development] thoughtlesskyle:
alright thank you, i have been following this project for a long time now and i must say this is the best yet, great work to everyone who had a hand in it
[Touch CDMA Android Development] drprince89:
sorry :( i didnt mean that in a derogatory sense, just like ill call something gay even though i dont have a problem with gay people, if i offended you i apologize.
[Touch CDMA Android Development] jaredakelly:
i'm a jew and i could care less, i guess it affects different people though
[Touch CDMA Android Development] BadAppleDH:
I am curious about the direct booting. does this require a rom flash of sorts. the only real reason i am interested is because i dont want to run android from my storage card. i know lots of people have had SD card failures from running android, because of all the writing that needs to be done. i was wondering if any of these issues have been fixed? or is there a way to run haret from the system memory without direct booting, or if direct booting is the only option for doing that. i would love to spend more time playing with and just plain using android (especially now that you can use the market) but i dont want to have to go out and buy new storage cards..

I would be interested in running a super slimmed down WinMo just for a safety net, then run android most of the time..
[Touch CDMA Android Development] jaredakelly:
direct boot is probably not going to come that soon because of fixes that still need to happen.

also i haven't heard of android runeing someones sd card in awhile.
[Touch CDMA Android Development] tallnerd1985:
Thank jebus that the phone doesn't eat mSD cards anymore. My boss was always wondering why I kept getting warranty replacements for my burnt mSD cards.
[Touch CDMA Android Development] aross6:
I am loving Ion Android... I was seriously considering paying some ETFs to get out of my Alltel Contract and picking up some iPhones for the fam but with the progress made with Andoid on the Vogue I'm going to stick it out... Thanks for all your hard work!!!
[Touch CDMA Android Development] katmandu421:
I've been running the same 2G sd card fully on android since last September and I've never had a card die. Plus, cards are MUCH cheaper than internal memory.
[Touch CDMA Android Development] BadAppleDH:
ok. that sets my mind at ease. i ran the old android when it came out over a year ago, but i quit using it because of limited functionality, and of course everyone complaining about it frying their sd cards. i guess if i were smart, id go out and buy a cheap small one just for android, but i dont really wanna carry around 2 cards..

Woo hoo! Off i go to play with android for an extended time this time around.

Also, what is the easiest way to move contacts from wm to android. will PIM backup or SPB backup back them up in a way that android can read?
[Touch CDMA Android Development] aross6:
Is there still a problem with calls not ringing in while a data connection is active or is this issue specific to my individual vogue?
[Touch CDMA Android Development] mfpreach:
It didn't particularly offend me since I am not Jewish, I just wanted to point out that saying that is as bad as calling something the 'n' word or all the other derogatory racial slurs. There is a difference with calling something gay and as that is a sexual orientation, not a race. Saying you got 'jewed' is race hating, and its what nazis would say.

However, gay people would probably disagree with me saying its not the same. Anyways, I just wanted to point that out because you don't walk around saying 'THAT is an 'n-word'' for something ****ty.

Feel me?
[Touch CDMA Android Development] aross6:
bump it...
[Touch CDMA Android Development] katmandu421:
The easiest way imho is to get a google account if you don't already have one and upload your contacts there (on your pc). Then your all set for contacts, email, market, etc. as there is constant syncing between the google account and your phone.

Here's a story that shows the power of this sync function, (though you can get other platforms to do this also): I had a friend that accidentally pocketed my phone after a late night. I woke up and found a message on fb saying that he had my phone. I didn't have his new number (it changes ALL the time) but did update it in my phone the night before. My battery would've probably been dead by then, so calling my own phone wouldn't have worked. I logged on to my google account and his new number that I had just updated was already up to date on the pc side, without me doing anything. Awesome, thanks Android!
[Touch CDMA Android Development] katmandu421:
No, and data is automatic these days, no need for togga or modem. In fact, if you set your calibration in default.txt, there is no start up procedure at all anymore. Just hit Haret, run and your golden.
[Touch CDMA Android Development] BadAppleDH:
Awesome. That does sound like a very handy function. No more worrying about lost contacts then. Thank you for your help.. I suppose a thank you to google is in order as well for making my life a little better/easier one step at a time.
[Touch CDMA Android Development] cybik:
use nuevasync to sync your winmo and google contacts. Fun little thing.

BEWARE: if you don't do it properly, you -may- wipe your WinMo contacts. Just to be on the safe side, backup your WinMo contacts with something like PIMBackup.
[Touch CDMA Android Development] aross6:
Awesome, Thank you... and Thanks to Vilord for making a sweet release... Android on the Vogue has come lightyears from when I stopped using it before!!!
[Touch CDMA Android Development] BadAppleDH:
I just quick searched, does google apps for winmo work? im on NFSs wm6.5 v11. also i only have kubuntu 9.04 for a comp. i guess i can use my roomates vista if i have to. I never use computer sync. i only use my phone calendar.

always.

Also,

im on sprint and when i first ran haret i got white screen, changed to setting 2, white, 3 bingo. didnt change anything else with first system. but got a bunch of fsck000*.REC files.

changed to the dudes system and no more. Are they logs of some sort? anyway everything else worked. gps, internet, phone, text.
[Touch CDMA Android Development] craig0r:
GMail has an Exchange server set up so that you can just use ActiveSync in WinMo to keep your contacts and calendar sync'd. That's what I use. It's very nice.

Of course, backup your data before setting this up, but here are the instructions, no extra software required:

http://www.google.com/support/mobile/bin/answer.py?answer=138636&topic=14299

EDIT: Oh, and if you want to sync all this with Ubuntu, the Evolution application has a Google Calendar plugin that will sync up as well. I'm not sure about automatically syncing your contacts with Linux though.