yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] f00bar:
yeah... as far as I can tell at this point it looks pretty stable... the only things that need to be fixed are SDcard (probably something like the missing NotifyMediaState bug in mountd) and the camera (there were a bunch of conflicts with your original patch and I didn't bother to try to merge them)

Also, you can get paid apps in market by spoofing ro.build.fingerprint to that of the T-mobile G1.

The only changes I made are:

1) Fix rild.libpath, ro.sf.lcd_density, ro.build.fingerprint in build.prop

2) Replace RIL with yours (need to compile against cupcake, you can just take the binary I compiled from my initrd.gz)

3) Replace Contacts.apk, Phone.apk with mine (for fixed dialer) and Modem.apk. Maybe development.apk and term.apk too.
[Touch CDMA Android Development] katmandu421:
Get a google account and import your contacts there. Then forget about syncing as they will always be in sync. Android is made by google, for google.
[Touch CDMA Android Development] katmandu421:
Wondering why you need Steel and ChompSMS now that the keyboard is present? I thought this was the only advantage to these programs, besides ChompSMS and it's cutesy, iphone-ish chat bubbles.
[Touch CDMA Android Development] tatnai:
Yeah, with ChompSMS it's not just the bubbles, bro. The default messaging program has poor contrast in the threaded view, difficult to see in good lighting conditions. I can change the colors of the background, bubbles, and text in ChompSMS, probably its best feature. I don't use its keyboard, I use dzo's blue one. Also, it turns on the screen for ten seconds (keeping it locked) and shows a ticker of the message in notifications, so I can read my texts without touching a button on my phone. Try it - once you get past the "cutesy" bubbles, you may realize you actually like it.

I simply prefer the nicer user interface of Steel. It allows full screen (no top bar, more browsing space), and the bottom bar is see-through when it is up. I feel like I have more screen real-estate using it than using the default browser. And I just turn off its keyboard and use the blue dzo one.
[Touch CDMA Android Development] steve98:
I am using DZO's latest 1.1 release - very nice so far, very slick and fluid -- however I can't seem to open ringtones or notification tones, I just get the 'force close' message. Texts come through with only vibration for notification. Anyone else getting this?

Cheers
[Touch CDMA Android Development] tatnai:
Latest 1.1 you can adjust backlight by changing slider to max, then decreasing; doesn't stick after screen timeout (well, the setting does, but the screen automatically resumes at full brightness). I use a program (Brightness!) that changes brightness with one click on the icon, and have shortcuts to it on every screen; I just tap it when my phone wakes up, my work-around for now.

EDIT1: Steel should work fine once the SD card is working
[Touch CDMA Android Development] katmandu421:
I tried, it, but I get most of that functionality from the stock SMS + SMS Popup, allowing me to either reply without waking the phone or closing and auto dismissing the notification. I agree that the colors and configuration of the stock app have something to be desired.
[Touch CDMA Android Development] Ideal2545:
make sure sound isnt muted inside of windows mobile, ive had that experience because of that
[Touch CDMA Android Development] steve98:
Yeah I've checked that -- done a few resets and still have the same issues. Strange.
[Touch CDMA Android Development] okcoolthnx:
Sounds like your only option is to reinstall. I had this problem back in the 1.0 Days and the only way to fix it was to reinstall.
[Touch CDMA Android Development] steve98:
Thanks, a re-install did the trick. I am noticing, however, a loud BEEP from the speaker when I hang up from a call. Anyone else getting that? LOL! Also I notice when you connect to USB now your PC recognises it as 'Android Phone' -- have never noticed that before? Doesn't seem to know what do with it though as it asks me to choose a driver.
[Touch CDMA Android Development] jaredakelly:
i had that happen to me about a week ago. all you had to do was get some more ringtones/notification tones. for some reason all your ringtones/notification tones got deleted and the system had nothing to open so it was forced to close
[Touch CDMA Android Development] steve98:
I fixed it by uninstalling / reinstalling but out of interest how and where do you get more ringtones for Android?
[Touch CDMA Android Development] tatnai:
you can make them with "Ringdroid" from MP3s, need to be able to access storage card for that though.
[Touch CDMA Android Development] njakobs:
Not all apps.

Hey has anyone else noticed that not all apps are avalible to us in the Market.

I have been trying to get 'ActionComplete' and 'Jewellust' which can both be found on http://www.cyrket.com/ (Pc Browser version of Market)

When I search for these in the market on my Vogue running Dzo 1.1 I can't find them.

Anyone running f00bar's 1.5 have any better luck?

Is it to do with with the way our device is identified? or is it location dependant (I am in NZ)

Cheers
[Touch CDMA Android Development] zkush:
i am also wondering how to get rid of the loud end call beep. also i go to dev sttings and make the app process limit 4, but then i cant run any apps. is there some kind of free task manager or a way to end programs?
[Touch CDMA Android Development] katmandu421:
LOL, isnt this normal? To signal that you have successfully terminated the call? I think all versions have had this. By no means an issue, for me at least. I like getting feedback that the call has ended.
[Touch CDMA Android Development] casualonejp:
1.5

I am having only a few minor issues with foobar's latest 1.5 release.

1. When the screen goes to sleep it will wake up just fine for a while but then sometime down the road when it tries to wake the screen doesn't come back on. The lights all show but just a black screen.

2. I think that MMS is fixed partially on this build as I am now able to receive and view messages from Verizon subscribers which I was unable to in the past.

3. When a data connection is initiated with MODEM it works just fine but when it disconnects it will not reconnect again.

Any suggestions? :D

Edit: Great work by the way DZO/Foobar!
[Touch CDMA Android Development] katmandu421:
I'm pretty sure that the screen wake up issue is know, look a few pages back for a post from dzo. I have had this happen a few times (this morning in fact). I dont think there is a solution or workaround at this point, but if we can make it consistently reproducable it may help with the solution. From memory, the times I have had this happen to me the phone was plugged in charging for an extended period of time. I'll try it again tonight and see if tomorrow morning I can wake it up.
[Touch CDMA Android Development] jaredakelly:
this would be fun and informative for all you developers out there

http://phandroid.com/2009/04/27/android-developer-event-of-the-year-google-io/
[Touch CDMA Android Development] zapat0s:
I just got my first bad SMS encoding messages. Im not exactly sure how they show up for you but mine showed up as if they were sent from my phone number. Is this how they all show up? What exactly causes it? will normal SMS's from specific carriers cause it? or only MMS messages?

Perhaps if we can narrow down the problem we can find a work around or a fix.
[Touch CDMA Android Development] dzo:
Definitely all mms messages will do this because my carrier doesn't support mms so I can't even receive one. I think I have fixed all the sms bad encodings though. If you find a carrier that doesn't work let me know and I'll be able to fix it.
[Touch CDMA Android Development] grktaurus83:
First off, amazing work dzo and f00bar. It's been a while since I posted, but I've been busy and only recently found some time to test the 1.1 builds.

I'm rather speechless with the 3D driver work. I agree that porting this driver to WinMo will be a huge accomplishment and most likely one that will be well received (donation-wise).

Aside from usability issues (speaker phone, call waiting, etc.), it's looking like Android is solid enough to run pretty much full time. Well done.

A few things I wanted to point out:

1) My stock battery only charges to 93% regardless of how long I charge it. Not sure if other people are experiencing the same issue.

2) I've experienced the bug where I couldn't wake up the phone, but only once a few weeks ago. It was immediately after I ended a phone call during which (I believe) I received a text message. I heard a single beep during the call and not a recurring beep like it is for call waiting. This may be linked, or may not be linked, but I thought I'd throw it out there.

3) I still keep running into the issue of not being able to connect to the internet after a few disconnects. I'm not sure why this is, but I might try putting in some time to figure it out in the coming month.

4) Text messages from e-mail accounts are treated oddly. A text message is just an e-mail without a subject sent to your phone address (##########@messaging.sprintpcs.com for sprint users). If you receive a text message from an e-mail account within Android, it shows up as if it's from "6245" and you can't respond to that text message properly. In WinMo, you could respond to that text message and it would show up as an e-mail to whoever you responded to (or at least you used to be able to, this may have been changed recently). This was really handy for a long time.

To answer one of f00bar's questions from before (why Togga was written the way it was, non-FIFO etc.):

I originally modified dzo's modem scripts so that I could simply run a script file to toggle the net connection on and off. Since I rarely use the net on my phone, I wanted to conserve as much battery life as I could and figure out why we couldn't start the connection from within android (and it worked~). The text file arrangement was added for debug and testing when things got more complicated and I never got around to cleaning it all up. That and I just figured it would be easier to spit everything into text files so that I could read states at a later time if need be (mechanical engineer by nature).

I haven't gotten a chance to check out your 1.5 builds yet (I will be trying them out soon), but I'd love to take a look at your modem code so I could get a better idea of how it should be done. I'm always willing to learn and I'd really appreciate the lesson. Go ahead and PM me if you'd like (no big deal if not). I was just happy I could get something important to work, really...

I'll try to figure out why the net connection won't come back on after a few disconnects when I get some time.

Again, this is amazing work!
[Touch CDMA Android Development] tatnai:
mine charges to 96%, that's it

I experience the internet issue as well.
[Touch CDMA Android Development] zkush:
when i have my phone on vibrate or silent i would prefer that there not be a loud beep on my phone when a call is ended. most phones dont do this.
[Touch CDMA Android Development] keeneraver:
As far as the bad encoding for sms/mms, I haven't experienced the problem myself but stumbled upon this website http://code.google.com/p/android/issues/detail?id=1233 so hope it sheds some insight.
[Touch CDMA Android Development] zapat0s:
The biggest problem is i have no clue who sent the texts to me. So Im unsure if they were SMSs from a carrier that still doesnt work or MMSs. Everyone I asked said they hadn't sent me any texts yesterday so... yeah that's helpful. Is there any way to get the real number that it came from?
[Touch CDMA Android Development] katmandu421:
OK, so I had a great idea after reading another user's post about startup procedures and placing a shortcut to Haret.exe in the Start Menu of winmo. What I've done is further that thought into placing Haret.exe in the Startup folder of winmo. I have problems with modem (or togga) connecting unless I first start IE in winmo, so I also created a shortcut to that app in the Startup folder. Now when I boot into winmo I am prompted with Haret and simply have to select run to get back into Android. I'm sure some of you have already figured this out, but thought I would share as it has really sped up my reboots.

So now what we need is someone to whip up a .bat that would accomplish the launching of IE, delay a few seconds to give IE a chance to connect, then launch Haret.exe, delay a few more seconds and (crossing fingers) imitate the enter button to actually run Haret. the reason for the second delay after Haret is so that if you don't want to boot Android you would have the chance to close Haret before execturing.

I imagine that this would be the closest we will get to a "native" Android OS.

Any brave sole up for the challenge?
[Touch CDMA Android Development] tatnai:
I believe this may already have been done, I recall seeing a post over at PPC Geeks on this. . . lemme see if I can find it.

EDIT1: at the bottom of post #1, requires mortscript, credit to qwho at PPC Geeks. Quoted from him:

"Basically it is a script that when you run it, it asks you if you would like to start android. If you click no, it exits to windows. If you click yes, it starts the internet, and runs haret.exe from the storage card root. Then, it waits 5 seconds for haret to start up, and clicks the screen at x=210, y=75, which is the run button, which causes android to boot. If you device is slower at bootup it can be changed to waiting more time."

Attached here for convenience.

EDIT2: Works great for me.
[Touch CDMA Android Development] tetrismonkey:
thanks for the mortscript

thank you so much for the mortscript i have been waiting for something just like this this so i can start up android fast then logging to wm every time i have only used it once and i already love it now i just cant wait for 1.5 to have the sdcard and thanks to DZO and f00bar for all the hard work and thank you to the rest i will test 1.5 later today if i get the time
[Touch CDMA Android Development] katmandu421:
Dude, awesome, thanks a bunch for diggin this out! Can't wait to try...

EDIT: Does what it says on the box! Just install the mort "player" cab from link above - Download the .zip, extract to your phone and install the second file in the CAB folder, thats the PPC version which the Vogue is. Then grab that .msc from said post above and copy/paste a shortcut in the windows startup folder. Easy Peasy.

Cheers!
[Touch CDMA Android Development] connor47:
Android link

Yah hi i was wondering if u could post the link for android installer
[Touch CDMA Android Development] tatnai:
um, to install android? just unzip the package to the root of your SD card . . . no installer necessary. . . see step by step instructions here.
[Touch CDMA Android Development] dzo:
I've rewritten the battery driver, it should be much more accurate now and takes the battery temperature into account. I've also changed the way it charges to copy what wince does. I haven't tested this stuff much especially with a low battery but it should be better than the old code. Only the zImage has changed in the latest zip.
[Touch CDMA Android Development] radem205:
I saw that you have fixed the vibration for 1.5 and 1.1. This means that your files are integrated with SDK1.5?
[Touch CDMA Android Development] dzo:
I just means if you use this kernel with f00bar's 1.5 image the vibrate should work correctly. I haven't tried it though.
[Touch CDMA Android Development] katmandu421:
Correct, vibrate works properly now in 1.5 with the "latest kernel" from your site, but I am experiencing the no wake up issue much more severely now. It seems a little different than the occasional wake up issue in that the light does revert back to flashing red after the timeout period whereas before, the light stayed green until reboot.

EDIT: I tried restoring a backup data file, no luck there, so I reluctantly reverted back to 1.1. It looks like the screen brightness settings sticks through sleep periods now. Good stuff for battery life I'm sure. We'll monitor the rest of today.
[Touch CDMA Android Development] aross6:
Tried the new zImage and it breaks my 1.1; thought maybe I downloaded a corrupt file so I dl'd a 2nd (and again a 3rd) time with the same result... I keep getting Force Close errors after the Android Splash Screen with it...
[Touch CDMA Android Development] katmandu421:
Interesting that it breaks soem of the 1.1's out there. I had it originally on a 1.5, but the screen had issue swking up, so I reverted back to 1.1 and everything is kosher. I would maybe try replacing your data.img? Sometimes it gets corrupt.

On the lighter side, it seems that another gift from dzo was that headphone support now works while hot swapping the headphones. Not sure if it was this kernel that did delivered this. I was playing last.fm in the car this afternoon and when i unplugged, instead of not hearing any sound at all, the music started coming through the phone's speaker. I'm positive this didn't happen when headphone support was first released. Good stuff!

EDIT: There seems to be an issue with the sound having a problem when the phone is asleep. It's not like before where the sound would get distorted right away when the screen went off, but while playing a last.fm track, if the phone sleeps the next song to play is distorted, but not quite like the distortion before. I can grab some log files or turn on debugging if you need, though i may need a bit of instruction.

Cheers.
[Touch CDMA Android Development] katmandu421:
FYI: I authored my very first mortscript and added it to the startup folder to simulate a mouse click on the prompt "Start Android?" after a set delay (mine is at 20 seconds) I will post it this weekend, but all I did was copy and renamed the mortscript for running the prompt. Then I deleted everything but the two lines saying something like "Sleep (5000)" and "Mouse Click (X,Y)". I changed the sleep to 20000 for 20 seconds and the coordinates for the "yes" button on the prompt was determined to be at 65,185 EDIT: 85,165. Again, I'll post the code when I get a chance this weekend. BTW, I am sure there is a more elegant solution for this function, but there is some level of satisfaction for doing it yourself, copying or "based" on others work, of course ;)
[Touch CDMA Android Development] katmandu421:
Heres the zip, hope i remembered the coordinates correctly. Let me know if they work if you try it.

With this and the android loader in your startup folder in winmo android will auto boot, with 20 second choice prompt just in case you want to go into winmo for some tasks. Edit the Sleep line in milliseconds to adjust to your boot up times and prefs. Also, since the android loader begins the data connection immediately, you can take the sleep line in that script down to a second or two as the OS will have the first 20 seconds to establish connection..

EDIT: Coordinates were not right, change to 85, 165...sorry about that, just open it notepad and change

Cheers.
[Touch CDMA Android Development] browningj:
I really hope that this hasn't been brought up before so here goes:

I have been using 1.1 for a while and wanted to explore the splendor of 1.5 by f00bar.

Initially I tried just starting from scratch on the SD card by using dzo's 1.5 and then substituting the initrd.gz and system.img from f00bar. I couldn't connect to the internet to get my emails and stuff.

I then tried only using dzo's 1.5. Same problem.

Then I tried using 1.1 to set up the email and tried the same two scenarios with the same problem, and Gmail kept crashing.

Then, I was getting the error of not waking back up. Well, that corrupted my data.img because I had to soft reset instead of properly powering down. When I tried to use that data image with 1.1 again, the Gmail Storage app (or something similar) would force close.

I would love to have 1.5 f00bar running, but am not enjoying the corruption of data.img. I will gladly start over with a new data image if I can finally get it right this time.

So after that long winded post, any suggestions?

P.S.: I know this is brought up a lot, but please GPS and camera, also, what can I do to help? I am not very programming oriented, but I can follow simple instructions.
[Touch CDMA Android Development] katmandu421:
Stick with 1.1 until things get sorted out with 1.5. I know, it's tough. I didnt want to walk away from that sweet keyboard, native scaling and wonderful widgets myself, but I'm sure the folks in the know will have it all sorted out in a bit.

It never ceases to amaze me how this thing...and technology in general, evolve in such an organic and natural way. I dont mean to sound too crunchy with that statement, more like golden ratio organic.The power of the online community and collaboration is simply amazing.

Cheers!
[Touch CDMA Android Development] tatnai:
so what is in the new zimage dzo?
[Touch CDMA Android Development] tatnai:
is there a way to bring up the cupcake keyboard in landscape mode in f00bar's latest 1.5? I double click the camera button to get into landscape, but then clicking on a text box does not bring up a keyboard for me.
[Touch CDMA Android Development] dzo:
Just some battery and charging fixes and it disables another clock when the panel is off. I get exactly the same power usage as under wince now.
[Touch CDMA Android Development] grktaurus83:
The updated battery driver now reports 100% when charging.

Overall battery performance is very nice.

That's excellent.
[Touch CDMA Android Development] katmandu421:
Anybody else seeing this issue? I am going to try an older zImage (gpu) and see if it is still present.

EDIT: Issue is gone with older (gpu) zImage
[Touch CDMA Android Development] grktaurus83:
Yes, I'm seeing this too.

The most easily reproducible version of this (at least for me) is if the phone sleeps during a call, the beep when the call finally ends comes out distorted.

This coincides with his report of the distorted first sound after waking up from sleep.

This might just be an issue of dzo not disabling some of the debug printing during sleep (since he was trying to find that bug that locks up the phone every week or so). Just a random thought.
[Touch CDMA Android Development] njakobs:
Hey Dzo, with the new zimage (4-5-09) I don't seem to be able to enter full power collapse mode. Green led stays flashing all the time. I seem to be getting pretty good battery life though. Did you change the Led's?

Cheers
[Touch CDMA Android Development] katmandu421:
I had a red LED during sleep, and didnt experience any "green light" moments that I had in previous versions, though they only came about once a week. Once i had them it meant restoring a backup data.img
[Touch CDMA Android Development] tatnai:
zImage3-5-09 was a significant improvement in battery life for me. Back to using that. Still get some jumping around of the battery level, but this seems a lot less. Will test out 4-5-09 again later - tmw maybe - to see if the above was a fluke. At the rate you're going, dzo, you'll probably have another one to test out by then.

EDIT: zImage4-5-09 works fine for me - previous slowness was unrelated.
[Touch CDMA Android Development] moekind:
any nice on screen keyboard in market place?