yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] n2rjt:
No on haret or nand reboot after initial install dont need to do anything, just let it boot. If it refuses to finish booting sometime try clearing dalvik cache.
[Touch CDMA Android Development] toshibashi:
You mean I should only press QUIT instead of INSTALL etc. ?

What about my WiFi problem? It's kinda frustrating having to re-boot everytime I walk into a different wireless LAN range. Does it make sense to up/downgrade the radio ROM from my current Baseband Version 25.83.40.02W_1.70.18.02 ?

And if, which one and how? Under Windows, before NAND-installing Android?

Best regards,

Toshibashi

EDIT:

I just realized HARET Android reboots unattendedly while I was interrupted by a visitor. :-) I Sorry for being too impatient.
[Touch CDMA Android Development] toshibashi:
I'm still amazed about Android and so are my kids :-)

However, it's a bit slow and animated GIFs don't move :-(

What can I do about it? Will a NAND install run much faster and will my GIFs move?

Best regards,

toshibashi

ps

The camera doesn't work correctly. It won't autofocus on one Kaiser and only shows a green background on the other.
[Touch CDMA Android Development] n2rjt:
Read the old threads, answers are available.

For the. Wifi issue, i dont know the answer. You should be able to switch access points.

Camera works for me but no autofocus and no brightness or color correction. Use the volume wheel to focus the camera.
[Touch CDMA Android Development] toshibashi:
Thanks for your hints!

It seems my radio problems have disappeared. Or maybe the radio has got accustomed to the different WiFi access points in my reach.

I've cloned my Haret installation on SD-card to a couple of Kaisers of my kids and friends. I was not aware that it was 'locked' to my first Googlemail account so I had to unlock it to have a fresh version for distribution.

One Kaiser has

WM6 Pro CE OS5.2.1620 (Build 18125.0.4.2)

ROM-Version 1.56.111.4

Radio Version 1.27.12.32

Protocol Version 22.45.88.07H

Camera Version 4.08 (Build 28288) CAMERA NOT WORKING, only shows a green background. Same with the barcode scanner app.

Another Kaiser has

WM6.1 Pro CE OS5.2.19212 (Build 19212.1.0.3)

ROM-Version 3.31.111.4 GER

Radio Version 1.70.18.02

Protocol Version 25.83.40.02

Camera Version 4.08 (Build 30595) CAMERA WORKS, barcode scanner too. Manual focussation needed, however.

Do I need another camera driver? Does Android use 'drivers' at all? Something like NDIS wrappers for CE drivers?

Or would it be sufficient to update the WM6 ROM to 6.1?

Best regards,

Toshibashi
[Touch CDMA Android Development] toshibashi:
Which Windows Mobile ROM version should I flash to have full Android functions, camera and all, in HaRET mode?

I live in Germany and I understand there's WM6.5 GER out there and even WM6.5.5. Has anybody tried HaRET based Android on WM6.5?

I'd like to go with HaRET for a while allowing me to stay with my WM based navigation software and to enjoy the best from both worlds. Once I've found apps for everything I'll do a NAND install.

What radio version is recommended (for Germany)?

Best regards,

Toshibashi
[Touch CDMA Android Development] n2rjt:
I didnt reply. Earlier because i dont know. I use nand only. I believe my sig reflects the radio i use but i dont know anything to help the camera, nor any reason your two phones behave differently. When you switch to nand be sure to use scoots kernel with separate cache. Try google maps or if that doesnt work try brut maps.
[Touch CDMA Android Development] toshibashi:
Thanks for your reply. I've updated my Kaiser to W6.1 using the branding provider's update program. Now I got

WM6.1 Pro CE OS5.2.19212 (Build 19212.1.0.3)

ROM-Version 3.31.111.4 GER

Radio Version 1.70.18.02

Protocol Version 25.83.40.02

Camera Version 4.08 (Build 30595)

Everything seems to be working, both Windows and Android, except one strange thing: one of my favorite WiFi access points won't let me log in with WM6.1. Same phone, same MAC address. It works perfectly with WM6 and with Android but not with WM6.1. Ok, the reason for upgrading was the camera function and the barcode app. so this issue is solved.

However, there is another hardware related problem. Regardless of what WM version, if the charger is plugged in for a while Android shows a white screen and the Kaiser has to be re-booted. Is this a known issue and is it the same with the NAND installed system?

Thanks for the map-software hints. I'll have a look into it tomorrow.

Best regards,

Toshibashi
[Touch CDMA Android Development] n2rjt:
White screen of death is a known issue. Sometimes you can recover by using the Fn-right soft key followed by Fn-left soft key on the keyboard.
[Touch CDMA Android Development] ol1ver:
Polaris user here,

have the same 'green camera' issue with my polaris updated to the 1.65.38.14 radio runing the froyo from sourceforge.

Also wifi 'dies' randomly. If connected it's fine for hours, even when going to sleep and waking up (thus switching between 3g and wifi).

Turning it off however or getting out of range from my work wifi, and an hour later coming into range of my home wifi, it won't ever connect (or find anything)

This also happens when wifi thethering kicks in. I don't know if the seperate app is required, but something (the app) causes tethering to always kick in when wifi or USB is connected and 3G is up. Very annoying because when i stop tethering, I can no longer enable wifi.

I upgraded a second polaris i have to the latest radio +winmo rom from HTC (RUU_Polaris_HTC_NLD_3.13.404.0_radio_sign_25.85.30.07_1.59.42.15_Ship) and the issue using haret now however remains. I have removed the tether apk to see if it would make a difference, but it doesn't. (It did stop it from automatically starting the tethering however) I'm 90% certain the camera remained green here aswell.

Also, I would like to build polaris/kaiser/vogue-droid from scratch. I've seen the git repositories with the kernels and other little bits, I know stock android is used for the android bits, anything else involved? I know there's certain scripts in the fresh-froyo release for example and some closed binaries may be there aswell? (Which btw I think is not even allowed to be hosted on sourceforge).

Edit:

Update. I double checked with haret and on haret, the camera actually works! I haven't done a lot of testing, but it is using the above mentioned radio/firmware, so that may be causing the difference. Or, winmo initializes the camera somehow more then the current android driver.
[Touch CDMA Android Development] toshibashi:
You mean autofocus works? Amazing.

Nothing against volume-knob focussing but it won't allow getting close enough for barcode scans. I mean, not closer than about 30 cm while using autofocus I can go as close as 5 - 10 cm.

[EDITED]

Best regards,

toshibashi
[Touch CDMA Android Development] n2rjt:
I doubt autofocus works. It never did and nobody has worked on it for ages. He probably meant the camera works, without autofocus. But I would be happy to hear I am wrong.
[Touch CDMA Android Development] toshibashi:
How Does The Radio Version Impact The Camera Function?

What is the RADIO firmware anyway - the microcode of the "wireless engine" (the Signal Processor chip for GSM/UMTS/WiFi) or a Windows Mobile driver to handle that engine?

Will the radio firmware remain if I flash Android to NAND? I mean, does Android use this firmware or does it come with it's own radio firmware?

I have no concept of the radio firmware's impact on the camera function. Does HTC use the same Digital Signal Processor engine for wireless and image processing tasks (like autofocus)?

BTW, PDA-Database lists various Chipsets for TyTN II:

Phone+Controller:	Qualcomm MSM7200 (QDSP4000, QDSP5000)

Obviously HTC has made different Hardware for different OEM vendors. T-mobile claims the MDA Vario III has a Qualcomm MSM7200 plus a SIRFstar III for GPS. I can confirm the Sirfstar since I used the SirfTech Tool to enable satellite based DGPS (Google: WAAS, EGNOS).

Will the 1.65.38.14 radio make any difference to my actual 1.70.18.02 ?

Best regards,

toshibashi
[Touch CDMA Android Development] n2rjt:
You know more details than I do. I do know that the radio firmware controls the gsm/cdma/wcdma. I do not know if it also does any camera functions, but always assumed it does not. Same radio firmware used by windows mobile and Android. It is flashed separately and does not get wiped out by most room installed. Factory rooms however often include a radio ROM. Read on WinMo forum for radio version comparisons or experiment.
[Touch CDMA Android Development] dzo:
The radio firmware is ARM code that runs on the ARM9 modem processor. It's actually a Pistachio L4 OS. The modem processor loads firmware into the DSPs, only one DSP (the ADSP) is available to the applications processor (the ARM11) and once it is set up the ARM11 talks directly to the ADSP through a set of queues in shared memory. The ARM11 communicates with the ARM9 using remote procedure calls (RPCs). The ADSP is heavily used by the camera because this is the only hardware that is connected to the video front end (VFE). Different radio firmware will use different RPCs and load different code into the ADSP so may not work with our kernel. Anyway, though this is interesting (and still how QC devices work) it's all rather out of date since nobody is working on these devices any more.
[Touch CDMA Android Development] -Rif-:
repo sync problem

hello..

I want to learn about compiling, but I have a problem..

I've done this step :

$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u git://androidhtc.git.sourceforge.net/gitroot/androidhtc/manifest -b froyo
$ repo sync

but every time I do repo sync it always failed and leave me a message

android.git.kernel.org[0: 149.20.4.77]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)

do I missed something or I downloaded the wrong repo file?

thanks in advance for your responses :)
[Touch CDMA Android Development] cfhplumb:
Problems

When I run haret.exe it runs linuz perfectly, but when it says hold center for setup, and I don't, it lacks a system.img file, and when I do, and I select Install, it spews errors at me, claims its Formatting...and than after 6 hours goes back to regular (htc defualt) boot.

-HTC TyTN II

-VaniljEclair_RLS11.zip

-Windows 7 with the super-hard-to-find Device Center (for win7...:D)
[Touch CDMA Android Development] kallt_kaffe:
Nice, I'll try to do that. I just noticed that you use the resized cyanogen bootanim. The one I sent to you is the standard Nexus bootadnim which I resized yesterday. It's a lot smaller and propably the more apropriate since this isn't a cyanogen release. I'll replace it when I've managed to sync the repo.

EDIT: Oh, and for someone who have never compiled anything other than the kernel... What do I need to do to be able to compile this beast?
[Touch CDMA Android Development] kallt_kaffe:
Actually data stopped working with this release for me. But on the other hand I did modify the build before install (replacing the apn-list was one thing) so it's possible that I broke something. I'll try the old ril and report back.

EDIT: Still no go so I guess I broke something... Oh well...

EDIT2: Still no data even when using your build, unmodfied.

EDIT3: Nevermind... seems to work now. Perhaps it was just something temporary with my provider or perhaps it was adding the default_network=3 to build.prop that did it.
[Touch CDMA Android Development] mssmison:
Haven't seen this many updates from you since android 1.0 days DZO. :) Great to see your enthusiasm about this.
[Touch CDMA Android Development] TheKartus:
I remember the days when the camera button pulled up that ****ty keyboard....
[Touch CDMA Android Development] Nick14:
i've not been here that long but i've seen alot from him :)
[Touch CDMA Android Development] mssmison:
DZO,

You should be able to bump up the audio in buffer size to 4096 in the lib source. Should help with voice dialing etc. It might pin the cpu though, but it's worth a shot.

**EDIT** I was just talking with Jesse (Vilord) about it, and we moved it to dynamic in the end as some apps are hard coded to a certain samplerate. Might have to undo the samplerate change I sent you previously to get it working properly again.
[Touch CDMA Android Development] thoughtlesskyle:
hey dzo is there anyway you could throw together a new release with all the enhancements of the newest one, but with the old RIL (before you used the one from Donut) so that way i have good a solid froyo and can use mms.

or how would i go about changing them myself in the easiest way possible
[Touch CDMA Android Development] dzo:
I've made a manifest for froyo so all you have to do to compile it is

repo init -u git://androidhtc.git.sourceforge.net/gitroot/androidhtc/manifest -b froyo
repo sync
. build/envsetup.sh
lunch full_vogue-userdebug
make -j 6

It will download a few Gigabytes of code and take at least a few hours to compile.

I haven't tried building it from scratch using the manifest file, so let me know if something doesn't work.
[Touch CDMA Android Development] kallt_kaffe:
I'll give it a try and let you know. Btw, in CyanogenMod Eclair I can force Touch UI for the Phone app in the settings. Is it possible to do that somehow, like settning a property with setprop or could it be added to the settings. I've QVGA adjusted the Touch UI for Eclair so I could propably add those xml-files to your git repo but it would be nice to be able to test it first.

EDIT: I just saw that you had to rework my xml-files a bit. Sorry about that. I'm using apktool to extract them so they end up like that. Also nice to see that next build will have Wifi out-of-the-box. On thing about wallpapers and QVGA. I noticed the one you added are resized to 432x320. I'm not 100% sure but from my experience with Eclair it seems to work like this: Wallpaper is stretched to 480 pixels width (twice the display) and everything above or below that doesn't fit is cut off. So 432x320 will be strecthed to 480x356 and then it cropped to 480x320. Our devices have a 3:4 ratio while all non QVGA devices uses 2:3 ratio. So what I did when I realized this was that I resized the pictures to 480 pixels width while keeping the aspect ratio, then cropping height to 320. Once again, mogrify is your friend. The ones I resized was 640x480 orignal so I resized them with this command "mogrify -resize 480x360 -crop 480x320+0+20 *". That should give wallpapers that looks just the same as the one you added except that they do not loose any quality being streched.
[Touch CDMA Android Development] kallt_kaffe:
And another thing. Do include the google maps framework. The Maps app can always be downloaded from market but the framework is needed by 3rd party apps that shows maps. Unless I added it c:geo (geocaching app) force closed when trying to show the map.
[Touch CDMA Android Development] dzo:
Here's another build:

https://sourceforge.net/projects/androidhtc/files/system-froyo-03-07-10_00.tgz/download

It doesn't have the JIT enabled but is based on the FRF85B source so may be more stable than the last one.

edit: actually the JIT is enabled.

Wifi should work on kaiser/polaris and it includes some google apps.

Everything is odexed.
[Touch CDMA Android Development] castlec:
Mild Color Issue

First off, great work to those that were responsible for giving us Froyo on our devices.

I've recently started playing with Eclair on my Tilt. Aside from the keymappings being off, I've been pretty pleased. I backed up Eclair last night to give Froyo a run. It seems to run well enough but I've got color issues. It's like I'm in a lower color mode than the icons are. I searched the forum and didn't see anything.

Please point me to a FAQ and, if the color issues aren't there and it's possible to fix in config, please let me know what I'll need to do.

Thanks,

Chris
[Touch CDMA Android Development] kallt_kaffe:
For keymapping there is a tilt parameter you need to change and for the color issue try changing the panel setting (1,2 or 3) until it works. The settings are in default.txt if you are HaRET booting.
[Touch CDMA Android Development] kallt_kaffe:
I propably should add the stuff I miss to the repo instead of packing up my own version... This is getting crazy...

Btw, where can I find the source .xml files for Phone.apk so that I can put nicely formatted .xml files into to repo. I have a several changes to the Phone.apk where most won't be needed until we can enable the touch UI.

But for the drawer dialpad it's propably easier if you do the change instead of me putting a apktool extracted .xml file into to repo again.

Just change:

android:paddingTop="6.0dip"

to:

android:paddingTop="5.0dip"

In res/layout-finger/dialpad.xml

That's the only one needing adjustment at the moment. Not needing really, but it looks nicer to not haveing the top ones being cut off.
[Touch CDMA Android Development] kallt_kaffe:
Btw, feel free to revert any changes I make if you feel it changes something in a direction you don't want it to go. I'll be happy to contribute to it but I won't be offended if you do not agree to all my tweaks.

I've pushed a bunch of changes. One I am not sure if you like or not. I've have a couple of lines in userinit.sh that sets up ro.product.model automaticly depedning on the real phone model. That means I more or less renamed your build without asking and I feel just a little bit unsure if that is OK. You could of course change userinit.sh to name the model "Full Android on <device name>" instead of "HTC <device name>" if you want to keep the original name. I doesn't matter to me I just think it's nice that the same build says "Kaiser" on my phone and "Polaris" on another phone and so on.

And btw, the MagicSmoke wallpaper. Does it work for you? It force closes for me, propably need more memory than we can give it. Unless it works for you it's just taking up space and should be removed.
[Touch CDMA Android Development] rephlexive:
Speed has improved from last build, good work dzo!

A strange thing is that the Gmail app has huge text for the headers/controls. Text of message body seems fine though.
[Touch CDMA Android Development] Gersonian:
autocorrect on keyboard

I hate to harp on this, but is there any kind of a fix for autocorrect not working? I send emails all day long from my phone and I am going nuts without this working. I miss the auto punctuation and what not.

I tried looking at the difference between DZO's latest build (7/3) and incubus' RLS4 where it last worked since its based off of fresh froyo, but I cannot tell what changed. Any help would be awesome, I do not mind trying to create the fix myself, but I need some advice. Thanks! And thanks for all the hard work you are all doing for Froyo on the Vogue.
[Touch CDMA Android Development] mirth18:
bluetooth not pairing with system-froyo-03-07-10_00

I can't seem to get my H700 motorola ear piece to pair with the system-froyo-03-07-10_00 build.

I am using Haret, with the zImage-02-07-10 file on a HTC Vogue.

The device will show up in my scans, but when I click on it to pair my headset led flashes a few times but never pairs. I will edit this note with some details from the adb log.

Edit: attached log of turning on bluetooth, going into settings, searching for devices, and finally trying to pair.
[Touch CDMA Android Development] incubus26jc:
It because i used latimegoogle instead. Remove latin_ime from his and use latin_ime google from mine. Make sure to remove his latinime odex as well. That should work.
[Touch CDMA Android Development] Gersonian:
Oh sweet. thank you so much! I am going to give this a shot now. Hopefully it will not require a full wipe. I really appreciate this.

Follow up: It worked!!! thanks so much. And it did not require a full wipe. I hope you don't mind, but I posted the solution (credit given to you for responding to me) in your thread. Really, this makes a world of difference in typing speed and mistakes.
[Touch CDMA Android Development] garringm:
Unsupported Content

In few builds there has been the option to allow the browser to download unsupported content, is there a way we can get that integrated into this build. ATM I am having issues with one of my PC's and would like the ability to update my phone by downloads. right now I can't because of this
[Touch CDMA Android Development] loserskater:
I use Opera for that. Luckily it IS in the Froyo market.
[Touch CDMA Android Development] mirth18:
froyo native tethering?

This might be a dumb question and maybe jumping the gun.. but isn't froyo suppose to have native usb (and wifi) tethering? I have been looking in the settings on this build, but it is not there.

Maybe it just hasn't been made to work with vogue yet.. or is it not open sourced?
[Touch CDMA Android Development] dzo:
Those look fine except the build.prop, you should add a PROPERTY_OVERRIDE in the config file rather than do this. Also all the files to copy need entries in device_vogue.mk. Perhaps I'll write a script to automate it, I don't know if we should really be adding the proprietary stuff at all, don't want to get into trouble with Google!

Changing the name is not a problem for me, I was going to do that anyway, it was only "Full Vogue" because I copied the sapphire config files and replaced Sapphire with Vogue.

Most of the live wallpapers need openGL 2.0 so they fail, apparently some of the market wallpapers work. I don't really want my phone wasting it's battery drawing swirly patterns anyway.
[Touch CDMA Android Development] dzo:
Our usb driver doesn't support this, somebody would have to get the gadget driver working (rather than the function driver that we are using).
[Touch CDMA Android Development] incubus26jc:
why is it that when i extract your image all of the files in bin labeled "toolbox" are 0 bytes in size? Is it because im using 7 zip to extract? Should i be using something else?
[Touch CDMA Android Development] incubus26jc:
also, can you uplaod a deodexed version for theming purposes?
[Touch CDMA Android Development] mnjm9b:
UH OH....LOL
[Touch CDMA Android Development] mirth18:
Thanks for the quick reply! Bummer though.. was looking forward to native tethering. Seems like any other tether app I have tried is really flaky. That is the only reason I use SD as I can tether with winmo easily in a pinch.
[Touch CDMA Android Development] dzo:
They are symlinks (symbolic links pointing to another file), I guess 7zip doesn't understand this and windows certainly doesn't. Best would be to use a linux box or linux running in a vm to do your packing/unpacking.
[Touch CDMA Android Development] mssmison:
usually the symlinks should be okay, I've added them/removed them from tars a couple of times with no issues.
[Touch CDMA Android Development] incubus26jc:
how about cygwin?
[Touch CDMA Android Development] incubus26jc:
cygdrive worked thanks. I did a

cd /cygdrive/d/users/Jeff/Desktop/froyo

tar -xvf androidinstall.gz
[Touch CDMA Android Development] kallt_kaffe:
I think 7-zip will leave them alone as long as you don't touch them. I added busybox to the repo but since I allready wrote a symlink script that creates the symlinks for it on the first boot I added the reused the busybox part of it. When I ported CM it didn't have the symlinks but a it a update script with information in it so I made a script for it. It was just easier than to start building the archives in my virtual ubuntu machine as it allowed me to continue working with 7-zip.

In fact it, busybox reports all it's support commands if you run it without arguments so the script could be made more dynamic. toolbox on the other hand doesn't seem to report it's commands.
[Touch CDMA Android Development] kallt_kaffe:
Thanks for the info, I'll change those parts. Btw, the wallpapers you added can't be seen or chosen, they are in the file but not available. I suppose there is an xml file somewhere were you need to list the filenames.

Cyanogen solved it by making the Google apps a separate download. Appearantly Google seems to be OK with that.