yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] craig0r:
The data.img file has your contacts and settings etc. As long as you leave that file intact, you should retain your data.

**In regards to the new headset functionality:**

Martin, as you mentioned, the headphones don't sound quite right. Here's my hypothesis on the cause of that. (And I've by no means actually looked at the code, this is nothing more than an opinion based on my observations.)

I'm guessing that in order to get the headphones to work, you simply switched the audio output from one speaker to another (from the phone's speaker to the headphones), however I think the switch should happen at a higher level. The audio sounds like it is still intended for the phone's speaker, almost like the audio needs different EQ settings for the headphones, or like it's supposed to go through some sort of pre-amp before reaching the headphones.

Just my two cents. I may be way off.
[Touch CDMA Android Development] Magister2k7:
Yes, I think so too. If you look into a audio_out.c, there are all EQ params, and they are the same for both headphones and speakerphone.

So, I think, that's the direction to work.
[Touch CDMA Android Development] f00bar:
Sure, please do. As for git -- it looks like github has the android stuff ready to be "forked" (unchanged stuff doesn't count against 100MB space limit), but how much is it really needed? What else do you plan to work on? The only thing I plan to do is integrate googlelogin fixes when they come about...

one annoying thing about repo is it automatically rebases your changes on sync. this might cause problems...

Anyway, here's all my stuff: http://github.com/jsherman
[Touch CDMA Android Development] ramontomzer:
phonefusion apk files

has anyone had a chance to extract the fusion voicemail plus apk files for installation? im dying to get this going on my vogue!!!
[Touch CDMA Android Development] NeonElixir:
Has anyone had issues with the most recent updates? I had everything working fine with the version from January 21, but the latest ones won't load properly. When I go in haret.exe and click Run, it gives me an error like "Failed to run \Android\zImage". I also noticed the bottom box now lists the machine as MSM7xxx, but I believe it used to say MSM69xx (I have the Touch).

Any ideas? I love using Android, I just wish the I could get my contacts over somehow (I'm on a Mac)!

Thanks for all the hard work.
[Touch CDMA Android Development] olografix:
Can't help with the "not loading" part, sorry. As far as contacts go, I've said it before, I'll say it again, Funambol is your friend. Great walkthrough here :

http://www.myhtcphone.com/import-contacts

I don't see why this would not work on a Mac (I might be wrong).
[Touch CDMA Android Development] wbuju123:
android on vogue

so how did you fix the cant write to memory card issue when you hit run using the vogue
[Touch CDMA Android Development] NeonElixir:
I tried Funambol, but it doesn't work on Mac. However... you did actually help. I never thought of loading it on the Windows Mobile end as well. I setup the new sync service that Google offers. So I have it sync from Google to WinMo, and then I can get it from WinMo to Funambol. Thanks!

Now I just need to be able to get into Android again....
[Touch CDMA Android Development] NeonElixir:
I tried going back to the version from January 21, which I believe was the last version I had working properly, and it's giving me the same error about failing to load zImage. Could there be some sort of conflict??
[Touch CDMA Android Development] hexxamillion:
Hung at Android Splash

I have the Verizon xv6900. I installed the recent version of Android for Vogue posted at http://it029000.massey.ac.nz/vogue/.

No problems saving and I was able to launch it off of my SD Card successfully..fully functional only one time. Since then it hangs at the Android splash screen when loading. It will not advance past that. Any suggestions? my default file seems fine. It worked great the first time including internet. I did not alter anything after that first load.
[Touch CDMA Android Development] Ideal2545:
hey guys, there is an android help desk thread in this forum, i would suggest posting your problems there :D
[Touch CDMA Android Development] tuscho:
Hi dzo... i know that you had asked to don´t ask about another devices, but i want to share my experience running at a P3301 / Artemis.

The phone itself received calls and the sound works... But when start to boot i see the linux screen, and after that the screen got black.... Because of this i didn´t tried to do a call from him.

My ask... it´s too dificult do a display driver for this device? I was googleing, and discover that vogue and artemis had the same hardware (CPU and memory)...

Tanks
[Touch CDMA Android Development] excogitation:
The display is already working on Artemis in Linux.

For Linux on your Artemis you should have a look here (it's nowhere near ready for daily use).

No, the Artemis' CPU (OMAP 850) and the Vogue's (MSM7500) are not the same.
[Touch CDMA Android Development] blasteryui:
Help

Ugh it's starting to mess up, I put it in my root and my storage card, I run it, when I go to type a msg or anything the on screen keyboard does not pop up. Also when I click browser it says it has to shut down unexpectly.

I posted in the help thread, so don't tell me too, I posted a while ago and nobody helped.
[Touch CDMA Android Development] excogitation:
Start with a clean data.gz (or a backup of your data.img you took earlier ;-).

If you only want to get the browser running again - try clearing its cache.
[Touch CDMA Android Development] etx:
I have a build of cupcake working with all of dzo and f00bars patches as well as a couple of my own. The only problem it has is Togga doesn't work. If anyone could chime in and let me know how this think works please do. I assume it runs /toggle.sh which is in the initrd that I haven't touched. When I click Connect in Togga the text view just shows "Modem initialization started Modem initialization completed Done!" Looks to me like it is not running the script at all, perhaps its a permissions issue or something.

I'd like to post this build for people to test, it fixes the tabview issues and fixes the boot screen for qvga.
[Touch CDMA Android Development] grktaurus83:
When I did some digging into getting the internet to work on demand, it appeared that Martin's builds ran setupmodem.sh in a loop. So I modified the setupmodem.sh script and added a few other scripts (toggle.sh being one of them) so that we can control when the connection is initialized.

Togga shouldn't output "Modem initialization started" (or completed). This output is only shown the first time that setupmodem.sh is run (which happens during the boot sequence in Martin's builds). That might mean that you're not using Martin's modifications properly (maybe the RIL modifications and a few others) and setupmodem.sh isn't being run in a loop (which may or may not change how these scripts behave).

Have you tried running Togga again after this output? What does it do on repeated runs? If I remember correctly, it shouldn't show that output if you run it again.

Let me know and I'll try to help out as best as I can.
[Touch CDMA Android Development] hipnetic:
Has anyone gotten this (or another build) to work on the Sprint Treo Pro? I've been playing around with Android on my Sprint Touch, but I'm ready to go back to my Treo 700p. There's a lot that I like about Android, but I'm not in love with the smallish touchscreen. I prefer having an always-available keyboard and D-Pad. Android supports using the D-Pad to navigate around and select things, so I think that Android on a WM Treo could be a great combination.
[Touch CDMA Android Development] ramontomzer:
calls on speakerphone

not sure if this has been addressed so im just posting here... android for Vogue and speakerphone.... is that working?
[Touch CDMA Android Development] dnessl:
Instead of builds based on cupcake, which I understand is and always will be an unstable branch, could we get a build based on the latest stable branch of Android? (Apparently parts of cupcake were recently merged into the stable branch to make Android 1.1) I use my smartphone not just as a basic phone, but also for the PIM apps. But the apps in cupcake don't work -- calendar won't start, can't send mail, etc, apparently because google login is broken. I have all my PIM data in google, so sync'ing to google would be fine, but I could adapt to pretty much any sync solution. As it is, this is a nice toy to show other geeks but not useful for actual everyday use.
[Touch CDMA Android Development] etx:
I downloaded the Togga code from google code and it looks like it is running the toggle.sh script. That is in the initrd image that I didn't touch so I'm not sure whats going on. When I have time to digg through the scripts I will. To answer your question grk, i can press connect over and over, I get the same output. I copied over Martin's libreference-ril.so library from a previous build, foobar said that's all that should be required.

Anyways, inputservice or whatever is crashing on my build now so I'll try a build from the stable branch tomorrow if I can.
[Touch CDMA Android Development] tuscho:
Ok... tank you!
[Touch CDMA Android Development] focusedonsound:
I have been trying to keep up with reading through all of the posts. Can anyone give me a run down of what

IS

and what

IS NOT

working with the current build.

Thank you
[Touch CDMA Android Development] d3mon187:
Hrmmm, I think in the latest build the text message wake up has gotten a little iffy. I noticed a couple times when it didn't notify that I had gotten a text message till I woke the phone up. It may be possible that it was having some problems with sms popup though, so I went ahead and uninstalled it. Right now It seems to be working ok, but I'd hate to always be missing texts. Really, if someone could just change the default vibrate on text receive to include a bunch of long vibrations that would be great. It was just SOOO much nicer with sms popup and my custom vibrate setting of 200,500,200,500,200,500,200,1000. I sure as hell never missed a text with that setting, but If the program is gonna cause problems then it isn't really worth it.
[Touch CDMA Android Development] prairiefire:
I noticed in this latest version (from dzo's site) that I have lost the ability to adjust the screen brightness, I cannot login to my google account in browser (not talking about google login service) and the battery life drains really fast (half battery shown drained in an hour or so... didn't keep specific track of this metric). The "up/down" on the centre button seems to be fine though - up moves the focus on the screen up, as i'd expect. This is with a fresh wipe of the SD card and placing everything in the root of the card and clicking on haret.exe
[Touch CDMA Android Development] Komofu:
I agree can we get a Version based off of the 1.1 SDK? We are not trying to sound needy and ungrateful but would really like to see if this has any improvements that could be merged into our current builds.
[Touch CDMA Android Development] dzo:
I'm working on this now, I've been playing with the blit engine and can get it to scale a 320x480 image to qvga. I've also got a 1.1 image that runs with gmail and market working.

Once this works (it crashes after a while at the moment) it should give us a really nice system that will run most of the market apps.

Give me a few days to iron out the bugs.
[Touch CDMA Android Development] zapat0s:
That's awesome dzo i cant wait. I understand most of android is very modular would it be possible to take the onscreen keyboard included in cupcake and include that in the 1.1 build? As i understand it the current 1.1 version does not include an onscreen keyboard yet. (please correct me if im wrong)
[Touch CDMA Android Development] Komofu:
Thanks DZO you are awesome. I think the hype has started to wear off this project and the ones left are the true fanatics. I can't wait for the new build.
[Touch CDMA Android Development] prodigy2m:
WOW

Can't wait for that to happen. That is awesome. Market place :rolleyes:
[Touch CDMA Android Development] zechsmax:
del..........
[Touch CDMA Android Development] Kmo:
I see you guys mentioned a audio_out.c. is this a file I can edit and change the eq parameters for the headphones? or what would I edit to make the sound better. sorry if the question is vague.
[Touch CDMA Android Development] Rigel7737:
Sync

dzo, will this allow google sync (mail, contacts, calender) to work?? Right now this is what's keeping me from ditching WM and using android regularly.
[Touch CDMA Android Development] Rigel7737:
And

...and thanks for the excellent work!
[Touch CDMA Android Development] blasteryui:
What do you mean data.gz, what exactly do I do, I've deleted both folders on both cards and reput the folders back on and that does nothing if thats what you mean
[Touch CDMA Android Development] nehunter:
Can't get Verizon Data Connection to work

Android works great on my vogue. I absolutely love it. Thanks for all the useful info here. Problem is, I still can't get my data connection to work. There are some posts that say keep username and password the same as default.txt already has it, while others say to use xxxxxxxxxx@vzw3g.com (phone number as x's) and password as vzw. I have tried both, and they both still don't work.

I am making sure everytime to run opera before switching over to android so my data connection is active. I've tried removing all android files off my sd card, and then replacing them with fresh ones, everything works except data connection.

Does anybody have the vogue on Verizon and have the data connection working? I would love the help! Thanks in advance!
[Touch CDMA Android Development] Mr80s:
RE:Can't get Verizon Data Connection to work

NeHunter,

Dumb question but are you using Toga to get your data connection up? It's in the applications list. Use it to toggle your network connection.

Hope that helps,
[Touch CDMA Android Development] euti:
for import of contacts, you don't need "google sync"! you only have to install funambolsync-sync-clientv0.1.1.apk (it's in one of the androidapps collections of dzo ) on android and the equivalent on windows mobile ( https://www.forge.funambol.org/download/ ). than you upload your contacts from WM and download in android. that's it...View attachment funambol-sync-client-v0.1.1.zip
[Touch CDMA Android Development] gazpachoking:
My data connection has been working fine on Verizon for a while. I leave the default username/pass in default.txt
[Touch CDMA Android Development] nehunter:
Unfortunately, Toga is not in my programs list and I can't seem to find where to download it so I can put it in my phone. I'm pretty new to all of this, so I'm slowly finding my way around. If anybody knows how to get Toga on the vogue, please let me know. Thanks!
[Touch CDMA Android Development] julledimanond:
WHAT_

Where are the files:confused:
[Touch CDMA Android Development] julledimanond:
Where are the files for android on windows mobile

Where are the files for android on windows mobile:confused:
[Touch CDMA Android Development] craig0r:
check the link on page 1.
[Touch CDMA Android Development] nehunter:
Getting data to work on Verizon

So, I had to go to myhtcphone.com and actually get the togga.apk file. I installed android on my phone using their directions, however if failed miserably (the way this thread describes installing if far far easier and faster). The nice thing about the failing install is that it had the togga file. So, I yanked everything off the SD card again and put it back on there the way this thread (first post) describes it. Android booted up perfect. I created a folder called AndroidApps. I stuck the togga file in there, launched it while in android, and voila.

So, if you have Verizon, you DO NOT need to change the default.txt file at all.

This forum won't let me attach the togga.apk file by itself, so I don't know how to get it on there without getting it from myhtcphone.com

Once again, just set up android just as the first post in this thread describes. Run android once without adding the AndroidApps folder yet. Once you get android successfully running, then you can add the AndroidApps folder. And yes, it has to be exactly like that.... AndroidApps. Place the togga file in there, load android, pull up togga in programs... and there ya go.
[Touch CDMA Android Development] tallnerd1985:
MMS On Android Port

Just out of curiousity, I have been running the Android port since November and absolutely love it. Its so bad that I upgraded to the Blackberry Storm in January to give the phone a shot and had to switch back to my Vogue with Android because I missed how smooth and somewhat functional the Android Port was. The only issue I have is that anytime someone sends me a extended txt msg or a MMS, it comes up with a bad encoding error. I was wondering if anybody had this error and if there is a workaround for it? I know from past experience that somewhere on the phone you have to configure messaging component to receive MMS from the carrier's server. This is what I found for Verizon Wireless

I dont know if this helps but if you guys need help finding any drivers or workaround, I know a couple of mobile device programmers that might be able to contribute to this project.
[Touch CDMA Android Development] d3mon187:
I've brought the extended txt msg thing up many times, but I haven't heard of any fixes or intentions to fix it. This and the short crappy vibrate on txt messages are two big issues that keeps me going back to WM.
[Touch CDMA Android Development] grktaurus83:
Yea... I think it's partly because of lack of interest from their end and partly because they aren't exactly sure how to fix it (no disrespect intended). The discussion died soon after people brought up the fact that there may be carrier specific issues with it. Trying to fix carrier specific things is a pain in the ass because then everyone on there will need specific things to be figured out for them.

So it's more time efficient to work on other features that lots of people use or are easier to fix.

That's not to say I don't agree with you. I rarely use long text messages, but I think it's something important that should be fixed. Someone will get to it eventually... it just takes some time and patience.
[Touch CDMA Android Development] grktaurus83:
Sounds great. It's been a while since I've been able to test a new build. I'm really looking forward to it.
[Touch CDMA Android Development] dzo:
The problem with mms is that my carrier doesn't support it at all, (good job telecom NZ) so I can't test it and don't really have an incentive to implement it.

However, there are some CDMA changes that look like they are coming to the master android repo soon and that should help.

With the new scaling code, I haven't fixed the on-screen kbd yet so it's not really usable for vogue yet.

You can try it by booting the kaiser experimental zip but I actually prefer cupcake anyway, the HVGA display gives me a headache after a while and is a bit slow.
[Touch CDMA Android Development] Rigel7737:
Thanks.

Thanks, I'll give it a shot. My problem is that I'm kind of dependent on exchange (calendar, contacts, and mail.) I have mailshadowG running to sync my exchange with google, but cant get it to come across on android. If anyone has any suggestions, let me know.
[Touch CDMA Android Development] f00bar:
Yeah I tried simple scaling before the density fix -- it looked pretty bad. If you *really* want to stick with 1.1, the best bet would be to just make a binary patch to libsurfaceflinger.so to multiply the density by a constant (this is what I did before they exposed the ro.sf.lcd_density variable).

It could be nice to have two versions I guess. I personally don't care about market/google apps at all, but do care about the nicer keyboard, adblock, dialer, etc. 1.1 version could be useful for those who really want google apps/market and are willing to give up those things for it (I still suspect that getting market working is just going to result in more than half the apps not working due to QVGA).
[Touch CDMA Android Development] grktaurus83:
Yea... the market will significantly increase the number of app fixes and compatibility issues we have. However, it might keep people busy playing with some of the apps that are out there. Haha. Just a thought.

And I agree, the on screen keyboard is probably one of the most important things to hold on to. What's the point of having all these extra apps if it makes text entry and operating the rest of the phone much more difficult? I guess I'm just more of a minimalist than most people. And SSH on the phone is something I use every now and then to remotely fix a computational cluster. So a bad keyboard makes that even more painful than it is.

Another important thing is the Google login service. I think if that gets fixed again, that'll give people a big set of core features that they are looking for. That way they wouldn't need some of the other apps they are currently using.

Either way, you guys are great and it's really up to you guys where this project goes (until other people jump in some more). You'll get no complaints out of me. I'm enjoying the ride and contributing whenever I can. (I'm still happy that Togga has worked out for so many people. Haha.)
[Touch CDMA Android Development] dzo:
I actually tried to patch libsurfaceflinger exectly as you said but it just seemed to ignore the dpi values and density wasn't add until later I think.

Anyway, the scaling is not a bad solution because android thinks it has a HVGA screen and the blitter converts it to QVGA so all apps will work. What would be ideal is something to switch between QVGA and HVGA to run apps that require it. It won't be hard, but we need the login service working first, hopefully when the magic is released that will help.
[Touch CDMA Android Development] shawn_:
Dzo any luck with the wired headset support? or have you not had time to even look at it? I absolutely love this android port unfortunately cant use it as my primary os without headset support :(
[Touch CDMA Android Development] shawn_:
Dialer - Login codes and pauses

I read here that the android dialer supports pauses with commas in phone numbers to allow for login codes to be entered automatically. ie 5551212,12343#,

I tried this with the latest Android for Vogue port and it does not work. Has anybody tried this and had it work? or not work?
[Touch CDMA Android Development] shawn_:
I see that some users are reporting the headset works. the headphones during a song work fine for me, but my headset during a phone call does not work.
[Touch CDMA Android Development] grktaurus83:
So something I noticed a while back but never mentioned was that my camera stopped working in WM. Whenever I'd try to take a picture, it would hang for a minute and then come up with an error. Also, the picture quality on screen was terrible (similar to what we see in Android).

I don't know if this started shortly after camera support was added to Android or not because I rarely use the camera on my phone. I noticed it about a month ago and just hard reset my phone recently and found that the camera was working again.

I don't think this is directly tied to Android (especially since I found forums with others having similar errors before we got camera support in Android), but I figured I'd throw it out there like I did with the memory card corruption issue.

Anyone else experience this?

edit: One thing I should have checked is if the camera still worked in Android before the hard reset. That would have been interesting to know.
[Touch CDMA Android Development] tErbo b00st:
my camera works perfect in winmo
[Touch CDMA Android Development] joepicco:
help!

how do you enable network functions? Sprint Vogue, running android nicely, got the sam 2 marketplace but cannot connect. also cant use internet and anything that requires the network, except the phone and txt's, they work fine.:confused:
[Touch CDMA Android Development] Drumcoded:
A) Did you use togga to turn on your internet connection?

B) Anything that uses the google services won't work (calendar, etc.)