yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] d1rtyd33z:
android boots now

Thanks for the zImage-bootlock-test! This kernel works on my vogue, while the other one has lots of issues during boot, and basically never makes it all the way into android.
[Touch CDMA Android Development] refthemc:
Kind of a simple question but does anyone else have problems playing high quality video on the youtube app?
[Touch CDMA Android Development] srwalter:
How well does GPS work from WinMo? What carrier? WinMo/Radio versions?
[Touch CDMA Android Development] mburris:
Martin, Jesse, Steven, and Craig...

If you guys got HTC Touch Pro 2's would you attempt to port android to them?

People in the Topaz thread think the hardware is almost 1:1 with that of the hero.
[Touch CDMA Android Development] vilord:
Yes please, just tell me where to send my address to get a touch pro 2 :D

For now I'll be sticking with my vogue, if enough donations come in I'll be able to use them for a new phone to experiment with... But so far nothing out there has quite the right balance of power, features and small size the way the vogue does... except for the hero, that is :D
[Touch CDMA Android Development] mburris:
if getting a free touch pro 2 meant switching to a gsm carrier would you?
[Touch CDMA Android Development] tatnai:
vilrod,

I'm on sprint and have been running latest kernels without problems, and I know you stated not to use the bootlock-test unless we were having issues. You also did say there was improved battery life with it, and another member posted on the linux forum that it was way better.

Is this improved over the OLD zimage that worked for sprint people before you made the new test zimage, or would I stand to experience better battery life switching from the lates zimage to the zimage-bootlock test? what are the differences between the two?

thx a bunch
[Touch CDMA Android Development] vilord:
man, that is a tough one... my father's on t-mobile, but I've been happily using the same carrier for the past 4 or 5 years now... And there's very little GSM coverage where my mother lives so... I guess I'd have to think it over.

If I had enough time to devote to the project, I'd say that I'd be happy to just pick up a pre-paid t-mobile sim card and work on it from there, then return it the phone once things progressed... but it would have to wait until after I move cross-country in august.
[Touch CDMA Android Development] vilord:
It would be an improvement only from the very old zImage that worked before the new one. In fact you'd probably get worse battery life.

New stuff in the kernel you have that isn't in the bootlock image:

updated video drivers, updated power management, better communication between the primary and secondary processors, better battery monitoring, basically 2 months worth of code from a kernel developer.
[Touch CDMA Android Development] dzo:
Count me in too! Actually I'm going to have to switch to a GSM phone some time because CDMA is being phased out here in the next couple of years.

I guess the big advantage of the vogue is that they are really cheap, that doesn't apply to touch pro 2!

Martin
[Touch CDMA Android Development] srwalter:
New kernel posted

I've been toying with some input changes, and I like what I've done enough to share it. Basically, I've killed the old 1.1 onscreen keyboard, since it doesn't give you anything on Cupcake. Instead, the camera button acts like a "shift." So now to change volume, instead of bringing up the OSK, you hold camera and use Menu/Back. Likewise, to rotate, hold camera and then press left-dpad. Another benefit is that when in landscape, you can actually see the cupcake keyboard. zImage here:

http://dasbrennen.isa-geek.org/~srwalter/zImage

Try it out and let me know what you think.
[Touch CDMA Android Development] dzo:
Tip: Turn off "Background Data" in Settings..Data synchronisation and you will get much better battery life even with Modem always connected. Although this means no Gmail and Calendar Sync, you can always sync these manually. My battery was only down to 86% yesterday after about 16 hours.

Martin
[Touch CDMA Android Development] refthemc:
Thanks for the tip because my battery was almost dead halfway through the day on saturday. lol
[Touch CDMA Android Development] tatnai:
thx martin
[Touch CDMA Android Development] oxsolid:
Awesome!

Srwalter, it works great for me. Cupcake keyboard on lascape is cool too!
[Touch CDMA Android Development] tallnerd1985:
Touch Pro for Donation

Hey, I posted back awhile ago about donating a Touch Pro CDMA Verizon Variant. I have one left to give thats Hard SPL Unlocked so you can flash whatever ESN or MEID that it needs. The ESN has been registered under the lost/stolen list so it cant be activated under Verizon using the serial numbers already encoded.

By the way guys, I am no programmer or expert on most of these phones but I do run a repair shop for cells phones and I get a lot of CDMA HTC phones that are pretty useless to me and my customers because of how locked down the ESNs are so if you need some "dummy" phones to do your tests on, feel free to PM me. I wont charge for them since they are almost useless to me due to living in a GSM dominated area so I would be more than happy to donate some phones to hopefully put down WinMo for good and give rise to the legion of Androids out there.
[Touch CDMA Android Development] ~David:
No solution for the looping "wakeup" error on boot? :(

This is horrible timing, lol. I hadn't used Android in a long time, and finally decided to try it again yesterday, and liked it so much I decided to use it as my primary OS.

Then I upgraded to the new "camera" release today, and it's not working anymore :( Even worse, I didn't back up the files from the previous release.
[Touch CDMA Android Development] drprince89:
Thats awesome man, i cant program but i still wanna thank you since im sure donations like that will benefit all of us in the future.
[Touch CDMA Android Development] tatnai:
Actually, should have rounded my calculations up; less blurry with 360 x 480, you can read all the start-up linux stuff too. Actually, I think this is as clear as 320x428. Try it!
[Touch CDMA Android Development] drprince89:
I am trying this out, but i wonder will you be able to get though the initial activation with this? it asks you to slide out the keyboard, will rotating the screen solve that?
[Touch CDMA Android Development] srwalter:
It should, yes. I'm emulating the "lid switch," which is exactly what the old on-screen keyboard was doing. If that worked, then so should this.
[Touch CDMA Android Development] tatnai:
Love it! I think we should keep it.
[Touch CDMA Android Development] drprince89:
I've run into a problem. I know others have had it but the instructions provided are a bit unclear.

I am trying to calibrate the screen but the only way i actually get values on the linux terminal screen is if i pres sym 0 and then hold end while tapping the top left and bottom right corners.

The values i got were Min (431,351) Max(3679,3775) p=427, so im assuming for min and max the first value is the x and the second value is the y. Now where do i put these values? I dont see where they go in default.txt. I see there is a section that says the values are YMax YMin Xmax PMin and PMax but i dont see where to actually input them plus i only have 1 p value and 2 x and y values.
[Touch CDMA Android Development] vilord:
Most people getting the wakeup error on boot were able to resolve it by downloading initrd.gz again. Try running a md5 hash on what you have and compare to what is listed from the download page, I think they won't match.
[Touch CDMA Android Development] tatnai:
ok, found an issue. with the old zimage there were many more settings under settings>locale & text> ("Touch input []", "Android input []". now if I switch to the HTC IME keyboard, I have no way to switch back because the checkboxes that used to be there allowing me to turn one on and the other off don't exist. when in the cupcake keyboard, I can long press the numbers to bring up the settings dialog to choose the text input method, but in the HTC IME keyboard, is there a way to do that? if there is please let me know, but right now, the only way I've found of switching back to the cupcake keyboard is to reload the old zimage, switch it by unchecking the "Touch input []" box, then reboot back with the new zimage. great update, but can these settings be added back? thx for your hard work.
[Touch CDMA Android Development] tatnai:
should be between the " " in the last line of the default.txt and should look like this

vogue-ts.XMIN=431 vogue-ts.YMIN=351 vogue-ts.XMAX=3727 vogue-ts.YMAX=3759
[Touch CDMA Android Development] vilord:
PM Sent. Thank you for the offer! Hopefully if you can send it my way I might be able to work on getting the wifi working on it, which will likely cross over to the kaiser's wifi link.
[Touch CDMA Android Development] oxsolid:
leave pmax blank

leave your pmax blank
[Touch CDMA Android Development] tatnai:
Yeah, I deleted my pmax. didn't know if others had done that
[Touch CDMA Android Development] dzo:
Sounds like a good idea, can you push it to the git repo.

Thanks.
[Touch CDMA Android Development] vilord:
srwalter, dzo... any chance we could have a kernel parameter in default.txt to turn it back on? Occasionally it does come in handy, for example I don't know any other way to sym-0 and get the touchscreen values
[Touch CDMA Android Development] drprince89:
Thanks for the help and oxsolid thank you too.

just to verify i can put it at the end of the second line as long as its in between quotes?
[Touch CDMA Android Development] briggs81:
Just wondering if any of you vogue users are plagued by not being able to make calls, but you can receive calls, send and receive text messages.
[Touch CDMA Android Development] srwalter:
A kernel parameter would be a fair bit of extra work. I'll hold off pushing the changes upstream for now, until I can come up with a touchscreen calibration solution. Is that the only caveat you can think of?
[Touch CDMA Android Development] vilord:
thats all I can think of... in fact if you could use the camera(shift)+end call, then adjust values, couldn't we bring up a terminal window and type 'dmesg' to get the values?

-Jesse
[Touch CDMA Android Development] moekind:
Hmm thats weird. After loading the new zimage srwalter posted, my led

blinks green now. Not red anymore. Is it not power saving properly now?
[Touch CDMA Android Development] brsev:
Thanks to all the developers who have worked on this project for donating so much time and hard work. All basic functionality seems nearly flawless, GPS lock-on is still hit-or-miss but it's still awesome, and the update for the camera works really well too (I can take endless pictures if I switch to album view in the top left and then back to camera). I had my phone with me today, took a picture and uploaded it to Picasa without a hitch. Scaled down, it looks pretty decent:

Thanks again!

Edit: one caveat, I feel like we need a better solution for the 'Menu' and 'Back' keys. I'd like to preserve the arrow keys; would it be possible to make 'send' and 'end call' into 'menu' and 'back', and then answer/hangup with software keys?
[Touch CDMA Android Development] ~David:
I tried downloading a the files over three times and it still wouldn't work.

I just tried downloading the compressed bundle though, and that works. :)

Glad to have Android back. The camera is working very well and I can't believe how fast the viewfinder is!
[Touch CDMA Android Development] njakobs:
Getting the same thing with srwalters new zimage. Doesn't seem to be entering full power collapse mode. Not seeing a big hit in power consumption though....

Love the new changes to key mapping for camera button though.

Cheers
[Touch CDMA Android Development] joannerve:
I get looping "wakeup" error on boot constantly. I have never problems with android builds. But with the last ion builds and last dzo 1.5 build I get wakeup error constantly. My device is Nike. I don´t know to do
[Touch CDMA Android Development] fiktion:
Okay... So, no matter what I do, I can't seem to get Android working anymore. I was out of the loop for a couple months because my Vogue was out of commission and I had to use a Samsung Glyde *shudders*, but now I'm back, and anytime I try to boot up Ion, Hero, TheDude's, dzo's, anything, I get nothing. It just stops on different commands, depending on the system I use. I've tried switching every single file out, I've tried leaving default.txt alone, I've tried changing it around. Nothing.

A date file is created every time, and my service LED blinks, and the cursor is blinking like it's going to run a new command, but it just doesn't. I'm getting soooo frustrated with this! :mad: :(

EDIT: Never mind. I ran an error check on my card and it found some errors, that apparently fixed the problem. :o
[Touch CDMA Android Development] tatnai:
My LED doesn't blink at all, whether while the phone is on, or off. If this is a planned LED change then great, I used NueLED in windows to kill all my LEDs cause I hated them flashing all the time. Is there a way in terminal to test what power saving mode is active - but I guess I would need to revert to the old zimage to bring up the terminal . . . catch 22 . . .
[Touch CDMA Android Development] oxsolid:
touch screen stops working

i'm usng the latest everything with srwalters new "shift" function, one bug i'm running into is that after the phone being on for a while my touchscreen stops accepting input. I just downloaded the bundle, and i'll try that with srwalters "shift"

anyone else seeing this?

EDIT: this is a replacement phone since my camera button had broken... it looks like winmo also is NOW experiencing the bad touchscreen... sooo it seems that this is a phone issue not an android issue... looks like i'm going to see about getting another...
[Touch CDMA Android Development] pchasco:
GPS used to work while I ran WM 6.1, but I'm running 6.5 now and I've not been able to get a lock. However, the GPS hardware does work because it does communicate with applications. I did let the customizations run after installing the Verizon updates. I've updated to the bell radio version 3.42.5.
[Touch CDMA Android Development] vilord:
pchasco, you need to remove the verizon junk from the radio...

Follow the procedure here: http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
[Touch CDMA Android Development] Spalla:
It all looks good so far, except...

Each resolution also comes with a logging initrd that will create a log folder on your SD card. Only use this if you are trying to figure out a problem, as leaving it running could fry a small part of your flash (SD cards have a very low number of maximum write cycles)

What does this mean? Anything I should worry about?
[Touch CDMA Android Development] mssmison:
no, it's for development purposes.
[Touch CDMA Android Development] mssmison:
I'm going to be putting out some more builds tonight, Im sure they'll work for you, reported just as fast as ion.
[Touch CDMA Android Development] Spalla:
My phone got corrupted after running this, and I had to hard reset.
[Touch CDMA Android Development] jaredakelly:
is there anyway to build off the very first gpu enabled kernal?

my phone went from peppy and fast to sluggish and slow with a keyboard. i even put running apps at 2 and it's soooooooo slow. i dont know what's wrong with the latest kernals. i know others have this problem as well. right now winmo is faster that what i have right now. i'm not trying to complain because i'm grateful for all the progress but with all the new updates after the first gpu kernal come sluggish performance.

if the phone rings it will be 2 rings before it actually shows who is calling......if i try to pull up one app it takes all the processing power and doesn't pull up for 3-4 seconds....

seriously try the first gpu kernal compared to the latest one, it's a HUGE difference.

is there anything i can do about this sluggish performance?
[Touch CDMA Android Development] katmandu421:
Just curious, are you on a sprint touch? I have these same issues, and yes, I ALWAYS set max apps, but there is something that slows down sprint touches (at least mine, and dzo obviously doesnt see this or he'd have fixed it im sure) after a few hours, and even quicker on cupcake, seems to be triggered by heavy data usage...which makes sense because it's probably a memory thing.
[Touch CDMA Android Development] jaredakelly:
Yes i have a sprint touch. what can i do to solve this? the only thing that didn't cause me problems was first gpu kernal?
[Touch CDMA Android Development] vilord:
I'll download the source of the first GPU kernel and update it with the code for vibrate to function properly... It won't have all the other changes since then tho...
[Touch CDMA Android Development] vilord:
updated the first post with some more instructions... more to come
[Touch CDMA Android Development] aven_soulgazer:
That's what I did except it wasn't the latest of DZO's releases. I can't run the latest of DZO's either. I have to run the 04-05-09 release to get android to run. Is that why I can't run Ion?
[Touch CDMA Android Development] vilord:
what happens when you use the zImage I built, the one you downloaded with thedude's build? Try using that zImage with DZO's latest everything else and let me know what happens.
[Touch CDMA Android Development] aven_soulgazer:
It runs through code up to the point where the splash screen should be and it goes black with a white dot in the upper left corner. Let it sit for 10 minutes with no progress.

Edit:

I tried that zimage with the files from DZO's older build that I had to originally use, it now boots into a black screen as well now.
[Touch CDMA Android Development] bangout:
i used my data image from dzo's build and used the zimage from the dudes build to get it working before that i had problems get this to boot but now i have it running and its smooth as i dont know wht.
[Touch CDMA Android Development] bangout:
one quick question is there a way that i can get teather bot working on this so i can use my phone as a modem if i need to, instead of going back to win6.5. i tried before but i dont think it registered the driver.
[Touch CDMA Android Development] joshboudreau:
hey i just put this on my phone today works great i just have a few questions, when listening to music how do you increase/decrease the volume i tried all the buttons on my phone nothing seems to do it and their is no volume bar in the music player at least not in mine, if you know of a good music player please let me know, also is their a app for msn somewhere out their im having trouble finding one.

Thanks,
[Touch CDMA Android Development] aven_soulgazer:
Did you make any changes in the default or anything else? When I've tried I've had absolutely no luck trying just that. It booted through and instead of a splash screen it was a black screen with white dot in top left. Then after a bit the led started blinking different pattern. I pressed power button, end button, slide up and down. Nothing seemed to wake it up.
[Touch CDMA Android Development] mssmison:
open DZO's keyboard, and use the regular wm volume slider. close keyboard and you're good to go. There was a good app I saw in the app store for volume...
[Touch CDMA Android Development] vilord:
sounds like your data file's corrupt again... do you have an androidapps folder? maybe something in that is killing it?

Try putting the attached data file on your card and bring up the ion system with the zImage from thedude's build

EDIT: Just use this to test it out, right now with this data file there is no internet whatsoever.
[Touch CDMA Android Development] vilord:
Not yet, we need to get a working windows ethernet protocol driver first. That is one of the next things on my list :)
[Touch CDMA Android Development] aven_soulgazer:
AndroidApps folder is completely empty. I can't get DZO's newer builds to work even with thedoods zimage and fresh data file from his site. I'll try this blank one shortly.
[Touch CDMA Android Development] srwalter:
Notification LEDs!

Yes, that is (mostly) expected. I accidentally published some LED changes a bit early. I'll go ahead and announce them now :-)

http://dasbrennen.isa-geek.org/~srwalter/vogue/

Using my zImage/initrd.gz/system.img (based on the latest google code ion builds), you will now get android control of the LEDs. You should see:

* Blinking blue on pending notification (new email, chat, etc)

* Blinking red on low battery

* Solid red/amber/green as battery charges (green means fully charged)

* No LEDs otherwise (don't be confused, the phone is not off)

The only thing that doesn't work quite right is the "attention light." There's supposed to be an amber blink for the attention light, but I never see it. The notification light also doesn't appear for missed calls, possibly because it wants to use the attention light...

Enjoy!
[Touch CDMA Android Development] katmandu421:
I keep getting upload errors with Picasa, are there any tricks here? i can email or attach to message just fine.

EDIT: You have to be patient! When i exited out of galleries it would fail. I let it sit, forgot about it, then popped it open a few minutes later and it was done with success.
[Touch CDMA Android Development] qwho:
This is really getting confusing... so now we have three different builds from three different people? How do we figure out which has what features?
[Touch CDMA Android Development] mburris:
request to include radio log creating script in initrd.gz archive

Vilord,

could you create a file called logradio.sh (chmod'd + x) inside of the initrd.gz you release.

It would make it easier for kaiser people with calling issues to generate the radio log on their SD cards since we don't have adb.

the logradio.sh could be something like:

#!/bin/sh
logcat -b radio > /sdcard/radiolog_`date +%Y_%m_%d_%H%M`.txt

even using the "specail keys" context menu I don't know how they would type the ">" character

Thanks
[Touch CDMA Android Development] vilord:
Martin (dzo) and I are collaborating, so the version on google code is the most recent from us.

srwalter is working on some of his own projects, and he generally is taking my latest published stuff and adding to it.

once I get verification that it is working, and I get info from steven as to what is needed, I incorporate steven's stuff into the main builds on google code.

I haven't heard from steven yet what changed in his versions, but once I do hear, I'll update google code.

Also, from now on the old versions will be posted in google code under "deprecated downloads"
[Touch CDMA Android Development] vilord:
You can avoid the > character by type

logcat -b radio -f /sdcard/radiolog.txt

But yes, it will be included in the next initrd :)
[Touch CDMA Android Development] katmandu421:
FYI: If you try out the new LED files from srwalter and your entire UI is HUGE, add the lcd.density=128 to your default. I have never used this so I never had it in my default, but by default it is 160.

EDIT: I am still seeing some overlapping in gmail with the new settings. Also, I am getting some errors and force closes when viewing directions in maps. Never had that before. I think I'll test a bit more but will go back to the google code builds later this evening.
[Touch CDMA Android Development] jaredakelly:
anybody know why google maps always force closes and is pretty much unusable. i was trying to use it in sf yesterday and it completely wasn't working. google maps is pretty key :(
[Touch CDMA Android Development] craig0r:
Ringtone Looping Fixed!

OK, I fixed all of our ringtones so that they loop properly. Also, I have also imported a large amount of ringtone, notification and alarm sounds from haykuro's dream-to-G1 port. There are also a few wallpapers that look nice, but I haven't tried them out yet.

Get it all at the google code page:

http://code.google.com/p/vogue-andr... Type Status Priority Component Owner Summary

Edit: Click the download link at the bottom.