yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
Radem, can you try with a CustomRUU from a polaris rom (not sure whether the CustomRUU is device dependent - but the error you're getting seems to be saying this).

Worth a try at least, but I think we may be flogging a proverbial dead horse here. Still cant understand why a Nike radio would work on a Kaiser but not on the Polaris. For the time being they've definitely got the edge on us as we're not going anywhere without the SD card driver.
[Touch Cruise Android Development] excogitation:
SD card still an issue?

I thought the SD problems were resolved by Rogro82 with this kernel.
[Touch Cruise Android Development] rogro82:
I also really dont get the point... sd card was already working ( I was even able to browse my pictures on the sdcard with an earlier android img from DZO ), the problem not showing the sdcard contents is an android image problem which is because f00bar didnt know how to solve it.

You can check his progress in the vogue android forum.

Besides that like i said earlier we were already using the mmc/sd driver the vogue was using. I have seen that DZO is trying to use a newer one from the 2.6.27 kernel, maybe this wont bring in any problems but if they do its about 2 seconds work to switch back to the old code.

I think we are trying to solve a non existing issue, which can be a bit hard sometimes :) ( Al Gore are you listening? Global warming my ass... its freezing cold in here )
[Touch Cruise Android Development] bally3:
sorry rogro, this was raised last night on IRC, according to DZO on the linuxtogo git, he mentioned that the SD card only worked with the 1.65.24.36 radio.

I have to admit I have not seen a working card as yet so this is a suprise to me though I remember you mentioned something about this before, If you're sure it works then thats a relief but I'm confused why no-one else has reported seeing the sd card working - maybe other users who have seen it working may want to post their radio/rom on here. btw, rogro, which radio/rom are you using? and can you post up the files that you used to successfully browse for pictures please?

I think depending on your rom - and its about builds here - you will see different results. The current blackstone builds I think are seeing more successes as it appears for example, the current UDK R4 rom -which is a Blackstone build) seem to be reported as working with the kernel more than the others.
[Touch Cruise Android Development] excogitation:
No. He was talking about (not) getting the phone to work (AT - smd0).

That's a completely different issue than working SD drivers.

You being able to boot 1.0 means that SD is working.
[Touch Cruise Android Development] bally3:
Ok maybe a little too technical for me I guess but it does say here clearly:

http://git.linuxtogo.org/?p=groups/m...2b3e0e730ba86a

that the sd card only works with that radio: "First attempt at merging with kaiser and polaris, vogue-smd should handle kaiser smem channels. sd driver only works with radio 1.65.24.36." so I'm still a little confused.

But again, I have not been able to browse for pictures/music - just tried again on the latest files posted here (foobar build) and it says "Your phone does not have an SD card inserted".

I also as mentioned before, have to change the "board-htcvogue.panel_type=1" to "3" to make it boot or else I get a white blinking screen. I'm using Maxnipers Omnio rom.

Have you been able to browse for pictures then exco?
[Touch Cruise Android Development] rogro82:
Not being able to browse files in android isnt a kernel problem. The kernel supports sdcard else you wont be able to boot.

The problem is the android (system.img) it self which needs a fix to use the sd card.

If you use the system.img from DZO, think its the latest from his site, it does work.

So no problems with the sd card its just the android build that need something fixed. You can read all about it in the vogue forum where f00bar posts all know issues ( like sdcard etc ) .

Besides that the kaiser was/is having sd card problems which i only got on older kernels. Since i started to build against the vogue tree I was always able to extract the data.gz/system.gz from 2,5mb to 64mb with out a problem. The kaiser isnt able using the same code ( I also posted my kernels over there to make them try it ) but they had to extract the data.gz and system.gz by hand to make it boot. On the Polaris we can just drop in a new system.gz and data.gz without a problem and it will extract all the time ( talking to dcordes i tried this procedure about 20 times and i still do it every now and then to update an image ).
[Touch Cruise Android Development] bally3:
Ok so I got my wires crossed a little it seems. :rolleyes:

Oh well.. its a learning curve for all and we do learn new things each day which is the point of being involved in these projects as far as I am concerned... oh yes and its fun too! ;)
[Touch Cruise Android Development] rogro82:
No problem my friend :)

Hopefully DZO fixes the smd code soon. Im having the same issues he is describing so atleast we all have the same problem.

The smd code is our biggest concern at the moment because this will make android really usable ( as a phone that is :) ).

Then the power collapse etc needs some fixing and the code that manages the battery, but i think the kaiser and the polaris are both alike in this ( like many other things ), so eventually this will get fixed also.
[Touch Cruise Android Development] radem205:
For what it is worth: I already tried it with the CustomRUU with the same results :(. But fortunately it is no longer necessary I think...
[Touch Cruise Android Development] mylostnick:
Hi. I have the "Touch Find" model which seems to be the same as XDA Orbit II:

http://pdadb.net/index.php?m=pdamaster&posted=1&model=HTC Polaris 200&num_rows_max=0

I use panel=1 with ION system DBE. It seems to be alright.

Here is my little report for camera!

Thank u for all
[Touch Cruise Android Development] dzo:
I'm using panel type 3 but I don't think it's working perfectly. The panel is a bit flickery and not as fast as it should be. The init sequence is probably wrong, I'll see if I can fix it.
[Touch Cruise Android Development] vorticerosso:
Hi,

I've try the zImage-09-10-09-1 with the Google-polaris-Ion-2009-09-12.rar build on POLARIS 100.

The WI.FI is working well but only if it is disabled it before in Windows Mobile.

If I enable it in Windows Mobile and then boot Android, the WIFI is not working.

The camere is working partially. If I start the camera application on WM, then the camera application in Android shows the preview image very fast, but when I press the shot button, the picture has bad quality and it seams strange.

If I don't start the Camera application in WM, the camera application is not working in Android, but the Barcode scan preview in the "Pkt Auction eBay" is showing the image a little bit purple. Then if I start the Camera application the preview is working but a little bit purple too.

Contact mee if you need more information.

Thanks

VR
[Touch Cruise Android Development] iseeka:
tried the same on a pola100

i get NO WIFI

camera works with same issues
[Touch Cruise Android Development] aitsch:
yesterday my camera works with "normal" colors.

since today pictures look like infa-red pictures (also purple).

barcode scanning is not possible at all.

i use the pola200 model.

aitsch

p.s.: @ DZO can you post which files/images do you use, please.
[Touch Cruise Android Development] Berto88:
Hi guys...can someone tell me where I can find the latest version of the ROM?...and does it flashes normally like any wm ROM?...last but not least...do I need to install some plugins to fix issues or is the ROM fully working?...

cheers!
[Touch Cruise Android Development] dzo:
You have to have used the cam in wince before booting android.

I'm working on the focusing and have written a driver to control the lens.

It will take a bit of work to get autofocus working, i might just use the wheel to let you do manual focusing for now.

The other thing that isn't working is auto white balancing so lighting will affect the colour balance.
[Touch Cruise Android Development] SuperJMN:
Berto, what we've got currently is not a ROM to flash, but individual files that make up the Android OS. It is not flashed to your device (for the moment) because it's being tested, and the kernel needs more work to make a everyday system for the most of users. It loads the Android OS using HaRET, that unloads WM and attach to some hardware in order to use it directly.

I hope this sheds light on your question.
[Touch Cruise Android Development] Berto88:
Ok, I understand!..I'm goin' to copy it on my SD and try it then!thanks for the asnwer, cheers
[Touch Cruise Android Development] dzo:
I just put a new kernel on he google code site. This lets you focus the camera manually, just use the scroll wheel. I also fixed the scroll wheel to generate up/down keypresses but it's probably a bit too sensitive.

Bar code scanning works great now.
[Touch Cruise Android Development] Skywalker74:
It does not work for me. It behaves the same as the previous build, zoom is not working, barscan is crashing.
[Touch Cruise Android Development] Skywalker74:
Zoom works! I started the cam in winmobile and it does not crash any more. (I did not use it there before, I guess).

Barcode scanner is the application that I use, and it still crashes.
[Touch Cruise Android Development] SuperJMN:
It works for me and zooms properly, but Barcode Scanner gives me an error.
[Touch Cruise Android Development] Skywalker74:
Tried ShopSavvy instead and scanning was successful.:)
[Touch Cruise Android Development] Hamzori:
my camera application just crashes
[Touch Cruise Android Development] imfloflo:
Guys this is a kener forum please continue this discution on another thread dedicated to android thanks :)
[Touch Cruise Android Development] vorticerosso:
Hi imfloflo,

I'm sorry about that.

I thought It was useful to test the last kernel and post the results in order to help the developers to understand how it is working for us.

VR
[Touch Cruise Android Development] imfloflo:
@vorticerosso Yes for sure but just a warning to keep this thread clean ;)
[Touch Cruise Android Development] dzo:
Another day, another kernel. This time some improvements to the touchscreen and wheel. The ts was sometimes getting bad x,y coordinates making it hard to type quickly, should be all good now. The wheel should be much more usable now too.

kernel is on google code (same name as yesterday's) and all changes pushed to git.
[Touch Cruise Android Development] SuperJMN:
You are my idol, DZO!
[Touch Cruise Android Development] imfloflo:
Thanks DZO :) i will test it asap.

Very nice to view all this new kernel and very fast improve in few day.

Donators are happy :)
[Touch Cruise Android Development] SuperJMN:
3G/GPRS connection

All these weeks I noticed that the 3G/GPRS connection is very unstable. Sometimes the 3G icon is there, but the connection is down. When you go to the modem application it says: Connecting ppp... and both buttons are disabled. When it reaches this state, you haven't got any options to connect via cellular connection than rebooting Android.

Its erratic behavior makes it almost impossible to check the e-mail or browse pages normally, since you don't really know when the connection is going to fail.

I don't know if it's because the connection is reset and Android doesn't try to establish it again, or because something is broken in the kernel. @DZO, can you take a look at this issue? It's really annoying and one of the things that make me reboot every now and then.

Thanks!
[Touch Cruise Android Development] NatronCH:
hi all,

here are some issues i spotted:

the netcounter does not show any traffic for gsm. is this something the gsm modem driver should report?

the bigger issue is that after connecting the modem, the devices responds much slower than before. I'm not sure if this also happens after making the first call.

It's amazing how well this kernel already works. How do you guys write these drivers/fixes? I don't think you have the specs for the hardware, do you? Are you reversengineering the windows drivers or do you use similar drivers as reference and modify them do match our devices?

Greets
[Touch Cruise Android Development] imfloflo:
FYI on the VOGUE device :
[Touch Cruise Android Development] Kiiv:
Some issues with hero/tattoo builds :

- camera doesn't work at all with hero build (force close). Works fine with Pulse build

- impossible to make a data connection with donut or tattoo builds

Thanks for all those new kernels dzo! :)
[Touch Cruise Android Development] bally3:
For kernel development, I would stick to the cupcake builds as we wont be looking at userspace compatibility until we have a fully working kernel.
[Touch Cruise Android Development] devslashnull:
I've been following this thread for quite some time with interest, but I have to admit I can't figure out:

1) what is the current bleeding edge kernel repository?

I read dzo's comment that it is all committed to the google repository, but which branch are we talking about, exactly?

2) what root file systems are used, and where do you get them from?

Cheers,

Robert
[Touch Cruise Android Development] imfloflo:
@devslashnull just read the topic and the other one in polaris forum (

use search button

) and you will find all your answers
[Touch Cruise Android Development] Michel82:
Power consumption decreased significantly with this new kernel. I think it's even better now then in winmo. I had a 5% drop overnight and 21% during this working day (normal use). One night and one day and i have 74% left. Great work! Haven't been able to get the camera to work, didn't put much effort in it yet though.
[Touch Cruise Android Development] imfloflo:
@Michel82 did you run camera under WM before booting Android ? which build are you using ?
[Touch Cruise Android Development] Leryan:
Approved. Battery live is longer with latest kernel.

2 days (may be a little bit more) - more than 50% battery left with not very active usage. It looks battery life is ~ similar to WiMo.
[Touch Cruise Android Development] Michel82:
@imfloflo. Camera is working now. Had to start it in winmo and actually keep the camera app running (which is quite difficult since its a fullscreen app). I am running the JACxROM btw.
[Touch Cruise Android Development] KaiCrow:
I tried to Download Android from http://blog.paks.no/?download=AndroidPolaris,

but everytime the Download stopped after ~85%. Anything broken with the Download?

Greetings,

KaiCrow
[Touch Cruise Android Development] pananza:
Thanks for reminding me, I'll remove that package. Stay off that package, it's overly old.
[Touch Cruise Android Development] Michel82:
Newest releases are found here: http://code.google.com/p/vogue-android/downloads/

For some different systems you could look here: http://code.google.com/p/vogue-hero/downloads
[Touch Cruise Android Development] devslashnull:
I don't want to be disrespectful, but you might find that more developers would care to join the effort if only they would know which branch is actually being developed in ;). The google repository has a bunch of branches; it should not be too difficult to put the name of that particular branch in the first post of this thread. Reading through the thread and the forum I have come across a whole array of repositories that came and went. It does not seem to be a good use of time.

Similarly, there's a score of 'system' files and it is hard to find out what specifics are covered. A table in a dedicated post on the first page of this thread would be sufficient.

Cheers.
[Touch Cruise Android Development] idreadful:
I want to make a testing only SD with android with the same build as dzo's, tried to look cupcakes in google code vogue-android, the newest one was system-themed-cupcake.sqsh (Oct 10). There were much force closes and crashing camera. Sure it's not the correct build. Had I missed something?

Anyway, really appreciated for all that huge progres, you've already made.
[Touch Cruise Android Development] Kiiv:
You can try system-xrom1.5r4c.sqsh

I think it's something like that.
[Touch Cruise Android Development] radem205:
I have the same connecting problems. These problems appears after the latest kernel changes, made by Dzo.

Ps: I think this is important for dzo to know, so I post this message in this thread.
[Touch Cruise Android Development] hobbit19:
http://rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
[Touch Cruise Android Development] Kiiv:
I'm curious, what can we do with that? It's a Click rom, isn't it?
[Touch Cruise Android Development] Francesco_AA:
Error in booting Linux !!! help !!!!

I don't have the correct file "default.txt" for my HTC Touch Cruise Polaris and Android couldn't run. After "run", the booting of Linux doesn't finish and the system freezes.

Who can help me to complete the code ???? I need to copy from anyone "default.txt". Please adjust the following commands....

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd

set cmdline "ppp.username=\"\" ppp.password=\"\" pm.sleep_mode=0 board-htcvogue.panel_type=1"

boot
[Touch Cruise Android Development] imfloflo:
@Francesco_AA

1. First post

2. says hello

3. post in the right place

4. search ( i found the default.txt in 2 secondes )

5. WARN
[Touch Cruise Android Development] aitsch:
hi,

i have only an slower edge connection with kernel-11-10 and also with the new kernel-15-10 from today. the "G" doesn't shown anymore.

camara with manual focussing works but barcode scanning is not possible for me.

aitsch
[Touch Cruise Android Development] dzo:
I've made some improvements to the camera. It now supports the full resolution and should be much better, there's also no need to start it in windows first.

You will need a new kernel and a new rootfs:

http://vogue-android.googlecode.com/files/zImage-15-10-09

http://vogue-android.googlecode.com/files/rootfs-15-10-09.img

The camera is quite slow when taking a picture and even slower now that it's running at 3.1MP. It looks like android makes very large thumbnails if it doesn't find one in the image and this is what is taking all the time.
[Touch Cruise Android Development] imfloflo:
Thanks dzo, on what have you planning to work after camera ?
[Touch Cruise Android Development] bally3:
Thanks dzo! works a treat.. I hope we can get a work-around for the images, but overall its working great. Will do a picture quality comparison today methinks with winmo but it camera looks smoother than in winmo to me.

Great work :)
[Touch Cruise Android Development] radem205:
With the latest files (15-10: rootfs and zimage) I can't get a signal anymore :s (no service)...

And when I start the camera I get a black screen and can't do anything :(

Edit: strange, after a reset everything is working great! Very great job dzo :)

This is happening often: when I tag music with Shazam, the first time it's working great. When I try another song it takes a while before matching. When I cancel this tag the next time shazam says: "Sorry, we couldn't tag your music. Try again?". This appears all the time now :(

I noticed that the headset is working (but no icon in the upperbar, right?). But when I plugged out the headset the sound during a call isn't coming through the speakers anymore.
[Touch Cruise Android Development] devslashnull:
dzo: I can't boot the system on my Polaris anymore with the kernel build from htc-vogue at commit f5ce436b1bc74b9926d83e03c7982d77ffa0ee5a (=latest). The symptom is that when I boot the kernel through haret, I get a garbled screen with lots of colored pixels and the system does not seem to make any progress anymore. :(

I rolled back one commit, and that zImage works fine (at least it hasn't got the panel problem).

It appears that this happens when the panel in default.txt is set to 0. I've changed it to 1, and it seems to be ok now. Sorry for the confusion.

ps: I use the files from http://code.google.com/p/vogue-android/downloads/list, but my own zImage build from the git repository git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git branch htc-vogue.
[Touch Cruise Android Development] dzo:
I've made a simple fake sensor driver, it lets you use the touch screen for tilt controls.

All you need is a new rootfs from here:

http://vogue-android.googlecode.com/files/rootfs-16-10-09.img

It's not perfect, in particular sometimes it just stops working and won't start again. I tried it with armadillo roll and hyperspace and they're both playable.

Will only work with Ion.
[Touch Cruise Android Development] whitealien:
Battery usage

Hi dzo,

I just wanted to leave some feedback on your great work and sacrifice of your free time to make Polaris users a little more happy. I hope imfloflo won't kill me (I know its developer thread:p)

Used files:

rootfs-15-10-09.img

initrd-01-09-09.gz

zImage-15-10-09

system-xrom1.5r4c.sqsh

Autonomy is increased a little since my last test. With very little usage - 1 short phone call, 2G on all times and little phone browsing battery is empty in 9 hours. Under android its shows 40% while in WM its 20%, which is more true. This is my only issue why I can't use it on daily basis.

WiFi, 2G, phone, SMS, Camera and rest is working fine. Amazing job!

cheers, Whitealien

EDIT: I forgot to add another thing. New button mapping is excellent, just one problem - they are not locked when phone is in standby mode. I keep my phone in pocket and wheel turns on screen all the time. Do you think its possible to lock all buttons, safe one, while in standby?
[Touch Cruise Android Development] li370:
cool, man. thanks

does anyone know how to install Chinese input?
[Touch Cruise Android Development] SuperJMN:
Hello people.

Regarding to power management:

I've got the latest kernel and rootfs-15-10-09v2.img. When I suspend my device the screen turns black, no leds, and when I press any key the device awakes. I think is not the right behavior according to DZO (he said that when the device is in Power Collapse, only the Power Button can awake the system).

I've got this configuration -------

in default.txt: pm.sleep_mode=0 and my panel number is 1.

I Uninstalled any weather application and disabled background connections, but it doesn't work.

----------

What's the problem? I've heard that some people are facing the same behavior.
[Touch Cruise Android Development] dzo:
Sleep mode should be 1. This will make a huge difference.
[Touch Cruise Android Development] niru1978:
Need help

Hell All and expecially DZO

I have installed the folllowing

rootfs-15-10-09.img

initrd-01-09-09.gz

zImage-15-10-09

system-xrom1.5r4c.sqsh

I have POLA100 and I see xrom android screen and then it becomes blank. it is almost 10 mins and nothing comes up. no keys work I guess the phone freezed

tell me the best android that works with POLA100 and atleast with wifi.
[Touch Cruise Android Development] bbezja1:
@Niru1987: please use this thread for non-developing chat:

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

and read it before asking.

latest files boot my android in less than 4 minutes since android splash screen shows, so no point in waitin any longer i guess.. :)

try changing panel-type to 1 in default.txt, ( board-htcpolaris.panel_type=1 ) that will probably work =)

then maybe ( mddi.width=240 mddi.height=320 ) might work, if your setting is different.

and again, please, continue this chat in this thread.

thanks!
[Touch Cruise Android Development] niru1978:
Well I used the combination as posted by whitealien and thus posted the result.

I have been following each and every thread in this forum as I want android on my phone...I dont think anyone is so persistent to get android in his/her **** phone!!!!
[Touch Cruise Android Development] osilvan:
Problem with audio input

Hi all,

Does anyone have problems with audio input? I know that dzo has make great progress in this but I'm still having problems with apps that uses mic (Voice Search, Shazam, Voice Recorder, ...).

I'm using the last kernel and rootfs posted in vogue-android (23/10/2009)

Thanks in advance
[Touch Cruise Android Development] SuperJMN:
Me too. I'm having problems with audio input. Shazam, for example.