yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] vilord:
cool :) I don't actually need an imap client, I just needed gmail :)
[Touch CDMA Android Development] nbpanjwa:
Great progress made so far....Wondering if this http://xdaforums.com/showthread.php?t=520629 can be ported to our ROM??? It will be treat to eyes and envy to all other phones.....
[Touch CDMA Android Development] vilord:
Sure would be nice... but from that page:

This theme does NOT work on:

JF v1.51 CRB43 US

Ion

Rogers
[Touch CDMA Android Development] fireshaper:
vilord, this is off topic but just wanted to let you know I sent you a PM.
[Touch CDMA Android Development] goooze:
white flashing screen problem

i know you need to change the thing to 3 but i think im putting the 3 in the wrong place. can someone show me the proper way of doing it....i have the sprint touch
[Touch CDMA Android Development] vilord:
gooze, just look all the way to the bottom of the text file. There should be a list of options. It already has =1, just change it to =3. Make sure you use something like "edit" or "notepad++", everything MUST stay on one line.

Also I got the bad-esn vzw touch pro today... it's huge! I don't know how I used to carry my xv6700 around, I just love my vogue! I don't know if I'll ever be able to switch to something else. The VGA screen is nice tho... I wonder if I could take the VGA screen from the pro and put it in my vogue? Hmm... :) A project for after both are running android.
[Touch CDMA Android Development] derekwilkinson:
I didn't know they made a way to do anything with the ESN of the Diamond/Pro.

And you can't do the screen swap, different power consumptions, not to mention the connectors on the main boards are different ;)
[Touch CDMA Android Development] vilord:
fine, ruin my fun ;)

I know I'll just have to wait and hope that eventually someone comes out with a tiny xda device like the vogue supported by android, with a 3.2" VGA screen...

Until then... vogue is the best!

slow progress with the NAND... see the kernel thread for details...
[Touch CDMA Android Development] f4ion1:
Did you have to do anything special to get i to run. I installed both of the apk's. Then went in to Locale & Text and put the check mark to enable the Touchpal keyboard but whenever I go to input text it still is using the default android soft keyboard?

Update - Nevermind, I was in a rush, forgot about step 5
[Touch CDMA Android Development] lazyvegaskid:
Any one with the APK willing to send it to me? The link to download is now broken =[ love the Winmo version but really want it on android
[Touch CDMA Android Development] wanderso:
I agree. I've been bringing up a Vogue for my son (Verizon, enable GPS, get Android on it, etc.) and I've REALLY been impressed with the Vogue, compared to my usual phone, a Kaiser. Even though I like the keyboard on the Kaiser and can go full speed with two thumbs on it, the Vogue is really good with an identical display and the new WM 6.5 virtual keyboard is pretty good. I agree, the form factor on the Vogue is really excellent.

And, believe me, there will be Android WVGA phones in small form factors.
[Touch CDMA Android Development] tatnai:
I'm a little disappointed with TouchPal on Android. It misses a couple of key features present in the WM 6.1 version - namely, a) with half qwerty there is no mistyping correction, and b) no option to add space after words. Also you can no longer swipe a key to the side in half qwerty to pick a single letter (you know what I'm talking about if you used it in win mo).

Both of these really disappointed me. This causes me to use A LOT more key strokes than I did in win mo. The benefits remain excellent prediction (better than the two existing android keyboards). Still, I keep switching back to the Touch Input half qwerty, because it does have error correction, even though the word prediction is inferior.

I emailed CooTek feedback about this. They replied they don't think mistyping correction is necessary with the half qwerty, and acknowledged that there is no option to add a space after words. I guess things won't be changing unless a bunch of us complain.
[Touch CDMA Android Development] TheUrge:
Hey Vilord - just to let you know I think I somewhat figured out what is causing the no service problem I was having. I have a data block on my phone, and yesterday I took it off.

As soon as I loaded android again my phone worked perfectly with both voice and 3g connected. Something with having no data on my phone must have caused a problem with that service from completely starting.

Just thought I would pass that along.
[Touch CDMA Android Development] mfpreach:
I think it works really well and I use touchpal in winmo.

I find the full qwerty works better than in winmo and the prediction is good.
[Touch CDMA Android Development] derekwilkinson:
I used TouchPal for awhile, but went back to "Touch Input" (I think it's from HTC), because it seems to integrate into the system better.
[Touch CDMA Android Development] zenulator:
slow home screen start up

I've noticed that some programs start up automatically even before the home screen is finished loading. Causing several seconds of lag at boot. I ran task killer and it showed about 5 apps already running directly after bootup. After I killed them everything went back to normal. Just wondering if any one else has run into this or if anyone knows how to correct this behavior.
[Touch CDMA Android Development] corypaul:
can anybody tell me how to type something in the defaut.txt that will restart all processes in android while its booting up
[Touch CDMA Android Development] vilord:
the processes aren't running when it first comes up... they're all getting launched on bootup.

Do you have a data block on your phone by any chance?
[Touch CDMA Android Development] corypaul:
i kno i do if you talking to me
[Touch CDMA Android Development] vilord:
yeah, i meant you... but I'm not sure what you wrote.

try setting ppp.nostart=1 in your default.txt and see if that gets you anywhere
[Touch CDMA Android Development] corypaul:
well android comes up and says no service, but to get it to say verizon wireless i use advance task manager to end all processes then it comes up. i was wondering if i could put some quote or something to restart the processes on boot or during boot.
[Touch CDMA Android Development] vilord:
unfortunately everything that is done by default.txt happens before the process gets started, so we'll have to figure out why it is doing it on your phone
[Touch CDMA Android Development] corypaul:
ok i dont know what to do then
[Touch CDMA Android Development] sshark:
I have been reading that everyone is getting poor battery life on Android running on Vogue...so do I.

One thing I have noticed is...Android OS takes less time to charge the phone compared to WinMo when using the same battery and it also drains out battery quickly.

Can this be because Android does not understand battery specs or have incorrect battery information in it?

Could you guys ratify this observation and also see if there is a way to change battery information in OS?

ss
[Touch CDMA Android Development] derekwilkinson:
This has been gone over many times.

It does not correctly sense the temperature, so it is not always right.

However, I seem to have better battery life than WM...
[Touch CDMA Android Development] drprince89:
I cant seem to get this calibration program working, even when i revert to default the calibration is really messed up. I was using the image that had the older version of the app, i figured i should update to the new one which allows me to revert to default settings. But the default settings are way off. Im not sure what to do at this point, android is pretty much unusable, and ive never had an issue like this, im not sure what to do now. I tried getting rid of my data, system, zimage and initrd files, and its all messed up, im not seeing any modifications in default.txt that would change the screen calibration.
[Touch CDMA Android Development] frad:
I would have to strongly disagree with that statement. I love android on my phone and hate having to switch back to WM every now and then, but with respect to battery life it is much much WORSE with android. I see it drop 30% in just a few hours. With WM it generally lasts most of the day only losing like 10% if I use it minimally.

All of this being my humble opinion of course.
[Touch CDMA Android Development] tatnai:
All this battery comparison talk is kinda useless right now. First, each of us used win mo differently and had it set up differently and we probably had different battery life on it. Second, as already stated, there is a battery temp issue being worked on. Third, we all use android differently and have it set up differently. So saying "I disagree with that statement..." doesn't really mean a whole lot, cause, pretty much things are guaranteed to be different.

You CAN get good battery life out of android. I charge all night each night, and seem to get a decent charge this way. Turn off background data as per dzo. I used to go all day with minimal use in win mo (three or 4 texts) and end the day at 6p with 70% left; I could easily use my phone for > 24h. I get at least 18h out of Android before the battery is speant, but I use it a hell of a lot more, so who knows.

Just keep waiting, it keeps getting better as the miracle working devs keep improving things.
[Touch CDMA Android Development] dzo:
I've just uploaded a new kernel to the google code site, it sets a couple of cpld bits on power collapse to copy what wince does, I don't know what this will do but it may help power management. It also has a simple temperature adjustment in the battery code (thanks to Craig for actually putting his phone in the freezer!). This hasn't been tested much but should be OK.

Martin
[Touch CDMA Android Development] srwalter:
Go into Settings -> Manage Applications and find "Calibrate Screen." In there you can clear the data used by the app. That will completely remove any calibration settings you might have saved with the app. The "defaults" used by CalibrateScreen are the same that the kernel defaults to. Are you saying that if you run the new version and tap the two dots, then immediately open "Pointer Location" the calibration is off?
[Touch CDMA Android Development] drprince89:
yes, i am, i have completely wiped the phone except for my default.txt. If i hit defaults in the program the calibration is still off.

Basically the right side of the screen is a little accurate near the bottom, i then tap the two dots and go back to test calibration and then the lewft side is more accurate, as i keep trying to adjust it just keeps getting worse. When i revert to default it doesnt go back to working.
[Touch CDMA Android Development] tatnai:
The amount of work you all put into this never ceases to amaze me, dl'ing this now. Thx dzo.
[Touch CDMA Android Development] lazyvegaskid:
you guys are the ** best, I just bought a new HTC Touch (my third) just because any other sprint phone doesnt measure up when we have android AND Winmo. Im hoping that sprint picks up the HTC Hero as engadget is reporting =]

Untill then im stuck on the forum awaiting updates, you guys rock and keep up the great work
[Touch CDMA Android Development] ark3:
Crash/Restart in Airplane Mode

My Sprint Vogue always crashes and restarts into Windows if I put in Airplane Mode and leave it alone for an hour or two. I'm running the July 9 bundle. How might I collect additional, useful information?

Aside from Airplane Mode, Android has been excellent. I get plenty of battery life (18 hours to get down to 10%) when I'm checking email frequently, keeping up with Facebook on the browser, and sending maybe a dozen texts over the course of the day.
[Touch CDMA Android Development] jaredakelly:
what do the panel types in the new default.txt do exactally?
[Touch CDMA Android Development] vilord:
since people were having trouble changing the panel type themselves, included individual files for each one.

setting the type to 0 will leave the panel powered on even when the phone is asleep

setting it to type 1 will turn it off, but only if it is a specific brand of panel, samsung i think

type 2 and type 3 are for the other panel brands.

sprint seems to *usually* use type 3, verizon in my phone is type 1, and martin's phone also uses type 1... but you really just have to try and see what works and what makes your screen go all white or screwy.
[Touch CDMA Android Development] tatnai:
So far, battery decline is much less erratic - seems the temp adjust is doing something. Will give it a full charge and run down tomorrow.
[Touch CDMA Android Development] drprince89:
Can anyone help me with my calibration issue? Im not really sure what to do at this point. I did a complete wipe of all android files on my sd card and started over, im still having issues, my winmo side works fine though so i dont think it is my screen physically that is the issue.
[Touch CDMA Android Development] s0v3r1gn:
So the other day I sent a TXT over 160 characters... Was the most entertaining infinite loop I have ever seen, also resulted in having to delete my data.img and starting over as it would resume the loop before finishing booting, locking the phone in an endless boot screen. =P

As I regularly send long txts to people I would like to request that the 160 char limit be something you guys look into soon. =P Let me know what I can do to lend a hand. Ive never spent much time in system or driver code, or in Linux for that matter, but Im willing to get my hands dirty if you guys need it.

And thanks for the awesome work you guys. The more I play around in Android the more I want a native Android phone to come out on Sprint. Namely the Hero!
[Touch CDMA Android Development] cointelbro:
I'd seriously consider killing a man for a Hero
[Touch CDMA Android Development] mssmison:
:) There's ALOT of issues. I've been working with it on and off but there are issues that I don't believe are correctable at this time.
[Touch CDMA Android Development] KERKEDAGAIN:
Found this:

My Android Manager

http://xdaforums.com/showthread.php?t=534043

Haven't had a chance to try it out but it seems to provide somewhat of a GUI to the ADB stuff..(mad technical terminology eh?)

Anyone try this yet?
[Touch CDMA Android Development] jaredakelly:
i second that but only if it's for sprint! :D
[Touch CDMA Android Development] tatnai:
FYI SlideMe is now long outdated - 2.8 now available; maybe remove from system.img, and allow people to dl and update themselves, next time it is updated.
[Touch CDMA Android Development] jaredakelly:
will having the wrong panel type cause it to not boot at all? i tried to use the panel type 3 since i have sprint and it wouldn't even boot
[Touch CDMA Android Development] motto_L:
Cant turn on bluetooth ?

Loaded 1.5 2 days ago...Loving it and thanks for all the hard works...Now I have one issue since I cant find it in this thread..so I am posting here...bluetooth not working what should I do?
[Touch CDMA Android Development] motto_L:
White screen

I had tried to edit from the phone the first time and I got white screen..So I edited from my laptop than loaded to the SD card...worked
[Touch CDMA Android Development] jaredakelly:
bluetooth doesn't work yet.....
[Touch CDMA Android Development] jaredakelly:
i tried both with no luck, just went back to my old .txt
[Touch CDMA Android Development] motto_L:
hum they're located towards to the end of document are you edited the right sections?

Thanks for the info about BT...I found some posts after I posted...go figure
[Touch CDMA Android Development] inline4:
dont wipe it just yet. I did the same thing, thinking I could calibrate the screen. it just points weird coordinates...

press volume up, to get back into the homescreen.

press volume down, and tab over to the settings and I think I reset it to default.
[Touch CDMA Android Development] vilord:
jared, the wrong panel type will definitely cause it to not boot. I'm guessing your current file sets it to 0? Have you tried the other two, =1 and =2? Maybe yours has yet another mfg panel...
[Touch CDMA Android Development] drprince89:
I dont think you read my orginal calibation post, even when i reset the calibration to default it is still off, i have already wiped, started with every file being new, and i still cant get my screen to calibrate.

Btw after a format of my card it is slightly better, my calibration is still partially off, although i can at least use the keyboard, but calibrating just keeps making it worse. Im just going to have to stop using android i guess, even though it is a bit better it isnt good enough for daily use. It most affects apps, and even though I'm not always in an app it makes it a pain to do just about anything, clicking an icon sometimes triggers a slide, because since the calibration is off a lot of the time i just end up clicking the space around an icon as opposed to the icon itself.

If no one can help me with this its fine, i just figured someone would be interested since its a very strange issue and no one seems to know what to do yet.
[Touch CDMA Android Development] vilord:
drprince, my suggestion would be to start by modifying your default.txt.

in the second to last line, within the quotes of the set cmdline...

vogue-ts.XMIN=0 vogue-ts.XMAX=5000 vogue-tx.YMIN=0 vogue-ts.YMAX=5000

Then delete or rename your data.img, and boot up.

You will find that the touch screen is basically unusable, but if you can navigate through to the calibration tool, it should hopefully give you a more accurate calibration.
[Touch CDMA Android Development] drprince89:
This didnt really work, the screen was unusable but when i calibrate its still not all that accurate, the cursor is semi accurate in some portions of the screen but the other parts arent accurate enough to let me use the phon normally, especially around the edges.

Also the numbers i get everytime vary severely, even when i revert to default and recalibrate i still get different coordinates every single time.

Thanks for trying, though.
[Touch CDMA Android Development] vilord:
hmm...

you are calibrating to the dots, not the corners right? (This is just me hoping it is something simple)

My other suggestion would be this:

bring up an old zImage from before the keyboard was removed... this one should work

Starting with a fresh data.img, don't use the calibrate screen at all.

press the camera button once to bring up the blue development keyboard.

click "sym" then "0" and the graphical interface should disappear leaving you with a text interface

hold down the red END key, and while holding it down, grab your stylus and tap the extreme top left and bottom right corners of the screen

press the camera button again and look at the screen, you should see a bunch of numbers including a set of min and max coordinates.

write down the numbers, they are the vogue-ts.xmin, ymin, xmax, ymax.

throw those into your default.txt and switch back to the latest kernel. You should be fine as long as you never use the calibration program
[Touch CDMA Android Development] oxsolid:
Old Skool

Yeah, i've got two vogues, and i used the dots to calibrate one and the blue keyboard method to calibrate the other...

What i found to be the most exact was to get a close calibration (with the blue keyboard)... and then i slightly modified the edge numbers (in default.txt) by either adding or subracting 16 and rebooting till i had a perfect calibration

for the red dots i had to try and press the inside corners of the red dots
[Touch CDMA Android Development] drprince89:
Im starting to think my screen might be bad. I cant do this because when i try to press sym after i release the tap the cursor flies to a random point on the screen and hits a few letters along the way.

SO when i try to simply hit sym it ends up typing in x's and z's and a bunch of letters.

Also if i tap a blank space on the home screen my screen actually scrolls a little as if i swiped.

And yes, i do know i should be tapping the red dots.
[Touch CDMA Android Development] vilord:
do you have any dark spots on your screen? My previous touch panel was all over the place and i realized that some of the glue had oozed in between the layers of the touch panel shorting out that section, causing taps to be all over the place.

My new one seems to be starting to do the same thing. Ugh... might be time to order another new alltel case.
[Touch CDMA Android Development] katmandu421:
I'm getting the keyboard opening many times when I hit menu. If I go back to close the keyboard and try again I get the menu as intended.
[Touch CDMA Android Development] drprince89:
i did have the spots over the winter then my screen cracked and it was replaced, i dont see anything on this new one. and the weirder part is it works ok under WM so i cant say its not working at the sprint store
[Touch CDMA Android Development] jaredakelly:
fyi:

after maybe a couple days to a week or so my phone starts to lag off and on real bad. it will sometimes not register that i'm pushing the screen, take a very long time for apps to come up, and basically it's not "peppy" like it usually is.

i've heard of other users having this problem so speak up if you do, i've had this problem when i using dzo's version back when his was the only version available as well (but only after the 3d graphics drivers update).

i've set max apps to 3 and sometimes even 2. i've used advanced task manager to close running apps and it will still give me problems. the only thing that actually gets my phone back to it's peppy android ways is to wipe everything out (data.img also) and start new. maybe it has something to do with data getting full? i have no clue.

vilord could you shed some light on this?
[Touch CDMA Android Development] vilord:
katmandu, it is designed to open the keyboard if menu is held down for more than a second... maybe this is related to the debouncing of "back"?

regarding the slowness, sorry I wish I knew! I think something is getting cached on data, but the SD card isn't as fast as internal memory would be so it doesn't work as intended.

But we won't know until NAND works, and I'm really frustrated with nand at the moment.
[Touch CDMA Android Development] cointelbro:
what's the status of the NAND project anyway?
[Touch CDMA Android Development] mssmison:
Whoops realized I posted it in the other thread.

I've hit a wall with my latest hero themed rom in that it won't work on a fresh data.img file. Only on a current one..

Soo... I'm not sure if I should release what I've got or is there another theme from the dream themes people would like to see ported over?
[Touch CDMA Android Development] jaredakelly:
how old does the data.img have to be? because if it just has to be ran once and setup with google and all that intro stuff then you could just have people do that and then move over to your build.

me personally i'd love to see it, i was enjoying the last hero build. is it fast?
[Touch CDMA Android Development] mssmison:
Yeah that's right. just have to have one already setup, cause you have to set some stuff up for it too boot properly.
[Touch CDMA Android Development] evilninjam0nky:
I loved the last Hero build. I would love to get the new one.
[Touch CDMA Android Development] jaredakelly:
then post it!
[Touch CDMA Android Development] tallnerd1985:
mssmison, go ahead and post it for us. By the way Vilord, hows the Touch Pro treating ya? Sorry I had the crappy rom on there, I was testing some of the different roms on ppcgeeks. I usually used Mighty Rom and set the pagepool to 12MBs and didn't really have any problems.
[Touch CDMA Android Development] marcjc:
Speaker option for calls

I just started really using Android as my main phone (or at least want to) and I tried to use the speaker phone during a call recently. It didn't work for me. Has anyone had any luck with this? VX6900.