yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] BadAppleDH:
Ok, just got around to doing it. Thank you very much. This all worked great. I think SynCE is the linux activesync equivalent. Oh well, KDE has a plasmoid for google calendar. i think i might give that a try.. maybe get more use out of my calendar that way.

Its actually pretty nice now, my phone had a way more complete list of emails than did my gmail (I usually used hotmail) so now its very nice to have them all moved to my gmail account.

Looks like there is a auto sync setting for calendar, gmail, and contacts in android. looks like i still never have to sync with a computer.. so who needs SynCE? haha. Cuz using it as a disk drive works smooth as butter on ubuntu.
[Touch CDMA Android Development] Nobi125:
Where is this option at?
[Touch CDMA Android Development] njakobs:
To set the max process app limit, open 'dev tools' then 'development settings' and select the max apps you want running.

Note however that in recent builds dzo and the others have set a max mem limit so that you don't need to bother doing this anymore to keep your android vogue fast.

I have noticed that this mem limit is a little to low sometimes for me. Is there anyway we can get a setting for it in the defaut txt Dzo?

Cheers
[Touch CDMA Android Development] derekwilkinson:
Is there a way to use the old Music player? Having all my 435 songs displayed at once does not work very well ;)

Also, is there a way to configure the touch screen? It seems to be off a little... can this be fixed? I am having a problem with my digitizer (ordered a new one today), but it is way more off than on Windows Mobile.
[Touch CDMA Android Development] BadAppleDH:
Ahh thats why my music player acts funny too i bet...

you probably just need to recalibrate or align, i have to do it too.

push the camera button to go to landscape mode,

push and hold the end key

while still holding tap the top right (refering to portrait top right (in landscape like it looks it would be top left) corner of your screen

then tap the caddycorner corner

release end.

and well camera again to go back to portrait view.
[Touch CDMA Android Development] srwalter:
Since you're having trouble with the touchscreen calibration, you might try my latest kernel change:

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

That kernel allows the touchscreen to be calibrated from userspace, for which you'll need an app:

http://dasbrennen.isa-geek.org/~srwalter/vogue/CalibrateScreen.apk (note: must be run in 320 x 480 resolution!)

Hopefully this userspace solution will be easier/friendly than the old on-screen keyboard + magic key-presses. You'll still have to modify defaults.txt, but I hope to remove that need soon.
[Touch CDMA Android Development] wojteko:
Hi Guys,

Is there a way to re-map some buttons?

I really liked how in one of the first releases the red end button acted as the back button. I just can't seem to get used to the current slide up to go back layout.
[Touch CDMA Android Development] derekwilkinson:
It says "Calibrate Screen could not be installed on this phone". I enabled non-market applications to be installed.

And with that zImage, I can't fix the calibration like I could with the other zImage.
[Touch CDMA Android Development] mfpreach:
Hey Vilord, does your latest initrd have the notification lights that msmission (sp?) implimented? I haven't updated yet thats why i'm asking.
[Touch CDMA Android Development] jaredakelly:
have a safe and happy 4th everyone!!
[Touch CDMA Android Development] srwalter:
Hmm, I installed it with adb on my vogue, and that worked. It's also expected that the old calibration method doesn't work in the new kernel. Existing parameters in default.txt should still work, but the on-screen keyboard is gone so you can't use that method to get new calibration parameters.
[Touch CDMA Android Development] wojteko:
Another issue I'm having is that I cannot reject calls.

When a call comes in pressing the red button does nothing.

I have to answer with green button and then press the red one to hang up.

Also, the soft answer/reject buttons don't appear when a call comes in.

android-1.5-2009-06-30.zip on Bell Vogue
[Touch CDMA Android Development] mssmison:
I'm running 320x480 with 160 pixel density and I can open the menu on the left side and select by genre/artist etc with no issues.
[Touch CDMA Android Development] mssmison:
When I tried to install it with adb it said install_parse_failed_no_certificates.

Did you sign the apk with the signing tool?
[Touch CDMA Android Development] srwalter:
I hadn't, no. That should be fixed now. Sorry about that.
[Touch CDMA Android Development] srwalter:
Another LEDs release

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

New zImage and system.img for my LED notification work. Any initrd will do. The attention light does work now. However, you will not get blinks on a missed call. Android simply does not set the LED for missed calls. You will see a blinking light for voicemail, however.

There is also a "sleep" LED again. Where previous builds were completely "off" when suspended, you'll now get a slow blink on the right amber light when in the lowest power savings mode. I like having the reassurance that my battery isn't going to die before the end of the day :-)

Barring any major objections, I'd say this version is ready for integration into vilord's/dzo's builds. The lights.msm7k.so is linked above, and I'll commit the kernel changes into linuxtogo shortly.
[Touch CDMA Android Development] Nobi125:
Amazing release, have it all up and running now. It's amazing that GPS and just about everything else works.

Some questions and suggestions. Is there speakerphone, I'm wondering if I just didn't figure out how to do it? The lock screen is pretty small and sorta blurry, though this is likely just a resolution issue. Icon text is pretty small as well, but the icons are nicely sized.
[Touch CDMA Android Development] mfpreach:
Its a known issue... to activate it, if it were working, when you are in a call you would hit the down volume and activate it if i remember correctly.
[Touch CDMA Android Development] derekwilkinson:
Does anyone have any hints on speeding up Android?

I set it to run only 3 processes at once, and it didn't work.

Can someone make a task manager or something?

Also, it takes around 15 seconds to go to the home screen... and sometimes longer. Is that just how it is?
[Touch CDMA Android Development] dzo:
The best tip I have is to buy yourself a class 6 sd card.
[Touch CDMA Android Development] derekwilkinson:
Eh, it's $18. Do you have a guess on how much performance boost that will give before I take the plunge?
[Touch CDMA Android Development] mfpreach:
Lol is $18 a lot of money? You better go collect some pop cans.
[Touch CDMA Android Development] drprince89:
well just so you know my experience, its definitely never ever taken me 15 seconds to get to the home screen from anywhere, that alone should tell you something, when i hit the home button it takes 3 seconds, if that to close the app and get to the home screen. Also i dont have a limit on how many processes can run.

Android is much faster than WinMo for me.
[Touch CDMA Android Development] tatnai:
This has been discussed multiple times, read back. In a word, not a priority right now.

Update to the latest initrd.gz (the 6/30 package is no longer up to date) and it allows you to hit the red button to reject a call.

I don't set a process limit, and it takes 3-4 seconds max for certain heavy programs to get back to the home screen. most programs take a second to two seconds. And I've got a class 4 card; you've got something wrong.
[Touch CDMA Android Development] tatnai:
srwalter, thx for your work. does the calibration program actually write to the default.txt? just click the red dots, is that how it works?
[Touch CDMA Android Development] volodar:
First of all, thanks everyone for all your work!!!

I can't believe how far this port has come over the last few months - it's really breathed new life into my touch.

I've got one request - after reading previous posts, it seems that there is no way to change "in call" volume. This is a problem, as my call volume is so high that there is major distortion when the person on the other line speaks. I've tried downloading volume apps through the app store, and they work for ringer volume, but not for call volume. Is there any way to slightly lower the volume in the initrd or kernel? Other than this, everything else works great!

Thanks,

Volodar
[Touch CDMA Android Development] dzo:
For in call volume and speakerphone to work we need to write libaudio, it's not difficult and I'll probably get around to it soon (unless someone else wants to try). I'm working on getting audio in working at the moment.
[Touch CDMA Android Development] tatnai:
one thing I've noticed that is different, with these two new files the screen dims in and out when turning off and on and when changing brightness in a slowed stepwise fashion instead of the smooth fast action that occurred before. These actions all take longer now. Switching out the system.img for the most recent system-ion.img resolves this problem.
[Touch CDMA Android Development] srwalter:
It does not update default.txt, no. I would like to enhance the calibration program to remember the correct values and set them on start-up, so the calibration parameters in default.txt wouldn't be needed at all. Yes, all you have to do is touch the red dots. After doing that, do you get an accurate touchscreen? You can use the "Pointer Location" tool in devtools to test it.
[Touch CDMA Android Development] srwalter:
I'm not sure why it's so jerky now, but the lcd-backlight is controlled by the same lights.msm7k.so as the notification LEDs. Unfortunately, I do not believe we have source to this library, so I had to rewrite it from scratch. The lagginess is on my list of things to investigate.
[Touch CDMA Android Development] derekwilkinson:
I have a class 2 card... that must be the reason... :)
[Touch CDMA Android Development] mssmison:
I vote for the same thing we've all said to many 'newer' android users.

Be happy we've come this far.

I can really tell there's been ALOT of new android user's jumping into this thread. And that's great. Thanks for coming, but please don't sit and ask for stuff, re-assigning buttons, in call volume etc. Those of us who have been developing this know what the issue's are. There are bigger fish to fry. If you have things to contribute, like actual initrd or kernel changes, or even system.img changes please do. Writing posts that have been posted many times before complaining about the same little details that have been complained about many times before gets us no where.

We all (dev's) knew nothing about android before starting this, but we've learned. You can too, by reading not only this thread and the other vogue one but the dream forums as well.

There.. that's my rant..
[Touch CDMA Android Development] tatnai:
After using this in 320x480 as you suggested, it actually is less accurate then using my presets in default.txt
[Touch CDMA Android Development] tatnai:
I've been here a while; I am a leecher/tester, I have not added anything to developing besides testing feedback from time to time. Did not post this to ask others to do something about it, I know there are priorities in development, have posted on that before myself, and believe me, I recognize and highly respect all the work done by yourself, dzo, vilrod, f00bar, and others. my reason for posting was trying to figure out if a) if someone already has a solution that I've missed (I read every single post in this and the linux on the vogue thread daily for a while now), and b) if people who know more than me know that this will already be fixed by donut that is being worked on, as an answer to either of those means there is nothing for me to do on this except wait. If the answer is negative to both, I'll get my work boots on and do some reading and jump into whatever file would have to be worked on, as I am interested and motivated.
[Touch CDMA Android Development] frad:
Quick question:

If the cursor stops blinking when booting Android that means its frozen and there is no point in waiting any more. Correct/incorrect?

Thanks.
[Touch CDMA Android Development] derekwilkinson:
I see the mssmison download has been taken off, was there a problem with it?
[Touch CDMA Android Development] srwalter:
Okay, this should be fixed in the new system.img on my site. Let me know if you still see the laggy backlight problem.
[Touch CDMA Android Development] derekwilkinson:
Do you think that an Android ROM will ever be possible? It needs Haret to run on the hardware, right? And that needs WM with the radio software, etc. Android is at least 100MB, which only gives about 46MB for WM to run, and gives Android no additional space to run.

I know this is very far off, but I am just curious of the future.

Also, I am going from a class 2 to class 6 SD card. Will this be a large speed improvement? It is going really slow right now, so I'm hoping it will help with the speed.

Also, what happened to mssmison's files? Are they being updated, or removed permanently?

Whenever I get Android running properly (fast enough to be useable), I am hoping to donate :)
[Touch CDMA Android Development] vilord:
mssmison must have removed his files himself.

I am guessing this is because he has been planning to update all of them with updated components.

I will be updating the bundle, system, initrd, etc in the next day or two, I'm working with srwalter to make sure all of his latest things get added in, along with fixes to ringtones, etc.

also, to answer other folks questions for the past few days...

katmandu: you will still need modem if you want to reconnect after the connection dies, or if you want to disconnect to save power.

badappledh: the fsckxxxx files are created because android runs a file system check on your SD card before it does anything. Any files that only got partially created or partially deleted before the card got ejected or before you unplugged your USB cable in Disk mode, or whatever since you bought the SD card, will be turned into an fsck file.

Once it makes them, it cleans up the disk so you won't get any more until something else gets left behind. It doesn't matter what system you use.
[Touch CDMA Android Development] dzo:
I've just been playing with google skymap, to get it to work you need to do:

touch /dev/akm8976_aot

Because it's trying to use the accelerometer and this fools it into thinking that it exists. It works but the display is upside down for some reason (or is it made for the northern hemisphere and I'm upside down!)
[Touch CDMA Android Development] tatnai:
downloading now. I've been using the new led zimage with the regular system-ion.img, and your notification stuff has been working just fine. will post back on your new system.img tonight.

EDIT: backlight problem is fixed, camera works fine, so far LEDs continue to work fine.
[Touch CDMA Android Development] katmandu421:
Cool. This is one that I've been wanting to try but couldn't get anything to show up.

I think the layout intention is that you hold your phone up, with the camera facing the sky instead of down like you would a regular map.
[Touch CDMA Android Development] katmandu421:
I tried this command in the better terminal app. It said access denied access, so I tried su in front and it prompts me for password. I think the original terminal app in the dev settings had root access without a password. How are others getting around this?

Cheers!
[Touch CDMA Android Development] pchasco:
Once you see that little tux in the top-left corner of your screen, Windows Mobile is effectively no longer in memory. Android has taken over and all system memory is available to it that isn't reserved for some other hardware. Besides the shorter power-on to Android times, there are no real advantages to removing Windows Mobile from your device to replace it with Android.
[Touch CDMA Android Development] mssmison:
Yup, it was getting too hard with so many older build to update them all the time. I've moved to one base system.img that I'll be updating in the future.

I should be able to have it posted later tonight. :)
[Touch CDMA Android Development] vilord:
su will not be asking for a password in the next version of initrd.

regarding an android flash, we are still working out the logistics. I'm still trying to decide whether I want a slim WM install in case things go awry or not...

The internal storage is 256MB from what I can remember... 128MB for the data store and about 80MB for the system image leaves only about 48MB for wince... since most wince images are closer to 120MB, that is a lot of slimming.

Not to mention we would also need to convince the tools to create a yaffs partition for data instead of tfat...

Once I get the spare phone I'll experiment with the flashing tools and with the uboot loader to see what I can get to work. It would also be nice to be able to update the system image without wiping out data.
[Touch CDMA Android Development] derekwilkinson:
Yeah, ROM space is 256. It would be difficult to get it to 48MB, but possibly possible :)

And the speed difference of having it in the ROM would be great :)
[Touch CDMA Android Development] aross6:
Is there an known issue with after losing cell signal that once it returns data no longer works? This happens on both my and my wife's Vogue and we have to reboot every time to get data back working properly again...

Any possible solution to this issue?
[Touch CDMA Android Development] vilord:
aross... have you tried using modem to reconnect?

I noticed that I had that problem last night, even if I switched into and out of airplane mode, it still wouldn't connect again.

I was able to get it to work a couple times by hitting disconnect when it was already disconnected, as it resets some of the modem settings.
[Touch CDMA Android Development] aross6:
I've tried resetting using the MODEM application but then no incoming calls are recieved when the data connection is active... powering the phone off and back on seems to be the only solution I have found that works properly...
[Touch CDMA Android Development] vilord:
Good to know!

I'll rewrite the "reset" strings in the modem script so that it actually properly resets and initializes the modem when i update initrd (this evening or tomorrow evening)... I don't know if it will help though...
[Touch CDMA Android Development] KERKEDAGAIN:
So we talkin' Rosie UI? (fingers crossed)
[Touch CDMA Android Development] aross6:
Thanks a million!!!
[Touch CDMA Android Development] dzo:
The password is "vogue".
[Touch CDMA Android Development] aven_soulgazer:
Is Rosie the old name for the Sense UI from HTC? I want to play with that too just to see what it adds.

Is there anyway to tell what's causing some of our vogues not to be able to run newer zimages? Any way to do diagnostics and see if anything is different?
[Touch CDMA Android Development] dzo:
I think it might be a timing issue caused by the cpld changes, can you get a debug log using a file with this in it.

pwf dmesg 0xe0000 0x20000

(search thread for how to do this).

How far into the boot does it get?
[Touch CDMA Android Development] vilord:
the phones that have the problem seem to lock up when accessing the SD card, either during the dosfsck, or during creating the data.img or extracting.

Unfortunately it is a hard lock, no errors or anything... hopefully a dmesg will give us something.

It was also verified that the zImage from the 04-may-2009 android-1.1 package worked fine, and the zImage from the 11-may-2009 android-1.1 package locked up, so I think it is the cpld code changes. I hope you can figure it out!!!
[Touch CDMA Android Development] Ideal2545:
dzo/viilord,

is your next kernel/itrd gonna have the changes srwalters made with the notifications and stuffs?
[Touch CDMA Android Development] dzo:
Can you try zImage-test from here:

http://cs-alb-pc3.massey.ac.nz/vogue/files

It has a change to the idle code that was introduced on 10th May.
[Touch CDMA Android Development] vilord:
Yes. The next kernel and initrd will have all the changes from srwalter, and also tylerwhall's kaiser gps stuff. Can't guarantee that everything will be updated tonight or tomorrow though...
[Touch CDMA Android Development] katmandu421:
Thanks, I'll give it a go.

Anyone had success geotagging photos by turning on the option in the camera menu? I don't think I have, but I do see the gps pop on just before the camera comes up, so I think it understands the call, just not sure how to verify. I've only tried viewing the photo details in the gallery after shooting a few.

Thanks again folks!
[Touch CDMA Android Development] tatnai:
I turned it on as well; I think it is a matter of time - it takes about 7-10 seconds for me to get a lock in google maps, and I never have the patience to wait that long before taking a pic. I took some today with it on, I'm going to place them in iPhoto to see if a location shows up.

EDIT: so I think that as in Google Maps, every time a menu is entered in camera or a pic is taken, the GPS is reset and starts searching again. Probably have to wait the full 10 seconds each time the live preview comes up to have it lock. none of my photos from a string of 4 got tagged with a position, not sure if this is why. oh well, bigger fish to fry anyways
[Touch CDMA Android Development] PeterDLai:
My Vogue seems to be booting into airplane mode everytime (no problems switching out of airplane mode, but still an annoyance).

Is this normal? If not, how do I fix/change it?

EDIT: Never mind, it seemed to fix itself the last time I booted.
[Touch CDMA Android Development] srwalter:
Okay, I've made a new "release" of CalibrateScreen, with lots of improvements. It is now resolution-independent, and should be more accurate. On my screen, I get near perfect results near the middle of the screen, and decent ones around the edge. I suspect my hardware just has non-linear response, and so no amount of calibration can make it perfect everywhere.

Additionally, it also supports saving the calibration settings and restoring them automatically on boot. No more messing with defaults.txt, yay! Apk same place as before:

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

Source available on github:

http://github.com/srwalter/calibratescreen/tree/master

Let me know what you guys think
[Touch CDMA Android Development] derekwilkinson:
Testing it now, thanks!

Will reply on how it goes.
[Touch CDMA Android Development] trensol:
Using my Sprint Vogue(with bell radio ver 3.42.50) , I tested both the zImage-bootlock-test(hikeit) and the newer zImage-test(DZO), and they both allow it to boot just fine. This was done using a brand new 4gb sd card. I have been using the original 512mb card that came with the vogue, and still met the same issues even when using the newer card( I tried both 32kb and 16kb formatting) using the standard zImage from the zip file with no success.

So the adjustments that have been made to these kernels, seem to benefit the Sprint Vogue.

I'll be more than happy to test any files that will further this project when I can. Thanks for all the hard work.
[Touch CDMA Android Development] wojteko:
Excellent. Works fine now :)
[Touch CDMA Android Development] katmandu421:
I ran the command as root, then exited terminal and started sky with no success. Do you need to launch sky from the terminal as well?

Cheers
[Touch CDMA Android Development] drprince89:
How would i install the screen calibration app?
[Touch CDMA Android Development] ljmeli:
@drprince

Search it out man...

Create folder in root of SD card "AndroidApps" place .apk in that folder.

@srwalter

the calibration tool works like a champ!
[Touch CDMA Android Development] derekwilkinson:
Does anyone know a good task manager for Android? All the ones I have found won't see the apps that are running (or only widgets on the home screen), and the limit app process setting isn't working :(