yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] manu33xtro:
Battery and network...

Hi DZO and iseeka,

First : Thank you very much for your very hard work and for the time you spent for us. And for the battery life and touchscreen now : they work good !

Same effect with my Polaris... I tested with all of your last kernel but when the phone is fully discharge, impossible to charge too :confused: And when I connect for charge, I can see 74% for the battery !!

If you want kmsg, tell me.

And another problem but I don't know if it's kernel or weith the last build of eclair : I sometimes lose network and also when I can see a high signal before. I see that only (I think) when the phone is in sleep mode. Not every time but twice or more by hour. It's very strange.

I've tested with build of Myn, Incubus26jc (CM5.07 and CM5.08), Kallt_kaffe : same thing.

I've also downgraded me radio to 1.44... and same thing.

And a last for BT : I tested with my car but I only heard nothing, just a breath...

And sometimes it's very long to have communication : I've the good screen and wait sometimes 1 minutes before the call begin ! And same for the end call...

If you want more details, for help, tell me.

Thanks in advance.

Cheers.
[Touch Cruise Android Development] chourmovs:
i can confirm those issues
[Touch Cruise Android Development] foxct2005:
Please for Pola100 Users... What Zimage files you use to have working wifi and Bluetooth ?

Can you link or post the latest correct Zimage to don't shoutdown on Run and working everything ?

Thanks a lot.
[Touch Cruise Android Development] zyves:
Hi all,

new reader here, where can i find a manual to install the android on my HTC Touch Cruise?

I found already the wiki, but the links to the files are broken...

Can someone help me?
[Touch Cruise Android Development] Nick14:
fast question

How do i know which panel i need too use ?:)
[Touch Cruise Android Development] l1q1d:
Holy crap! This is kernel thread!!

@Nick14, zyves,foxct2005 : use search button or open another topic!

@dzo: i was watching line 85 of board-htcpolaris-keypad.c, what do you think about changing the binding of camera button (or step 1) to another use (i.e search button)?
[Touch Cruise Android Development] dzo:
I changed the panel code so it always powers on, I could change it back but it may be better to add some code to sleep if the battery is too low. Does it charge OK using an AC adapter, this should provide more power.
[Touch Cruise Android Development] Nick14:
I have a problem where Android does charge and is stuck on 1% and if i unplugg the charger it dies
[Touch Cruise Android Development] SuperJMN:
New release by DZO!

"Set UART gpios to input when not in use, saves lots of power on Kaiser and Polaris".

I'm now testing to see if it really improves the battery.

DZO, you're THE MAN!
[Touch Cruise Android Development] vanvancool:
"New release by DZO!"

and look inside default.txt description

pm.sleep_mode - The mode used when the phone is off

0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,

3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

Default is 1, use 0 for best power savings

Notice: the value for best power savings change from 1 to 0 :confused:

wich value should polaris and kaiser user use for best power saving ?
[Touch Cruise Android Development] DmK75:
You do not have a issue with "error waiting for notbusy" again?

Also i not have sound in speaker with latest zImage.
[Touch Cruise Android Development] l1q1d:
Battery works better but i have always no adb device :-(
[Touch Cruise Android Development] chourmovs:
thank you DZO for the battery fix

it seems to work pretty well
[Touch Cruise Android Development] vanvancool:
unbelivable.... DZO , you are my god.

every night ~8h my Polaris battery lost ernergy from 100% to 93-90%

yesterday i use your new kernel (22.06)

now 8h only 2% less, that amazing :eek:

thx very much

o2 xda2 polaris

warm eclair RLS1 (haret + zimage 22.06 + pm.sleep_mode=1)

8gb SD
[Touch Cruise Android Development] l1q1d:
Wifi stops working :-(

[ 126.759073] wlan: version magic '2.6.25-01050-gbfcf4222-dirty preempt mod_unload ARMv6 ' should be '2.6.25-01098-gc12aeff-dirty preempt mod_unload ARMv6 '
[ 126.865583] TIWLAN: Driver loading
[ 127.341636] trout_wifi_power: 1
[ 127.341696] trout_wifi_reset: 0
[ 127.392001] trout_wifi_set_carddetect: 1
[ 127.392041] mmc0: card_present 1
[ 127.392069] mmc0: Slot status change detected (0 -> 1)
[ 127.818455] mmc0: Command timeout
[ 127.820093] mmc0: card claims to support voltages below the defined range. These will be ignored.
[ 127.820093] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
[ 127.820093] clk_set_rate 19:20000000
[ 127.820093] set sd clock - 0 1
[ 127.925080] mmc0: new SDIO card at address 0001
[ 127.929980] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
[ 127.936250] TIWLAN: Driver initialized (rc 0)
[ 127.936678] TIWLAN: 1251 PG 1.1
[ 127.936720] TIWLAN: Driver loaded
[ 128.342770] set gpio 18 wakeup 40000000
[ 128.471685] ds2746: 3867mV 42mA charge: 15/100 (-1 units)
[ 128.471711] aux0: 233 (1273) aux1: 64 (319)
[ 130.309585] TIWLAN: TIWLAN: Failed to start config manager
[ 130.690133] mmc0: Command expiry misfire
[ 132.270421] ds2746: 3899mV 232mA charge: 15/100 (-1 units)
[ 132.270449] aux0: 234 (1286) aux1: 66 (330)
[ 134.480097] TIWLAN: Driver unloading
[ 135.085650] ds2746: 3894mV 236mA charge: 15/100 (-1 units)
[ 135.085675] aux0: 233 (1273) aux1: 66 (330)
[ 136.556919] TIWLAN: 903.825041: set gpio 18 wakeup 80000000
[ 136.557457] sdio_reset_comm():
[ 136.566102] clk_set_rate 19:144000
[ 136.568196] set sd clock - 0 1
[ 136.678512] clk_set_rate 19:20000000
[ 136.680742] set sd clock - 0 1
[ 136.840377] TIWLAN: Releasing SDIO resources
[ 136.840827] TIWLAN: SDIO resources released
[ 136.842766] trout_wifi_set_carddetect: 0
[ 136.842826] mmc0: card_present 0
[ 136.842859] mmc0: Slot status change detected (1 -> 0)
[ 136.843779] mmc0: card 0002 removed
[ 136.849127] trout_wifi_reset: 1
[ 137.152561] trout_wifi_power: 0
[ 137.152621] TIWLAN: Driver unloaded
[ 139.010290] ds2746: 3899mV 265mA charge: 15/100 (-1 units)
[ 139.010316] aux0: 233 (1273) aux1: 66 (330)
[ 141.080318] ds2746: 3901mV 245mA charge: 15/100 (-1 units)
[ 141.080343] aux0: 232 (1273) aux1: 66 (330)
[Touch Cruise Android Development] DmK75:
"waiting for notbusy" - old bug again.

Maybe, DZO add command in cmdline for disable 2x vibro?

Because, is impossible to use any new kernels (in zImage).

In booting few messages "error: waiting for notbusy" and after slow boot only "process system is not responding".

And all freezes...
[Touch Cruise Android Development] foxct2005:
Same identical problems.

I was glad if you could resolve this problems for zImage users.

Best Regards.
[Touch Cruise Android Development] DmK75:
In zImage-25-06-10 these errors removed.
[Touch Cruise Android Development] l1q1d:
Solved with 25-06-10 release
[Touch Cruise Android Development] foxct2005:
I have Just tried 25/06/2010 zImage ... but ... nothing has changed.

ALWAYS the same problem... double vibrate and "error not busy"

I am very disperate... my kernel is old (april 2010) :-(

Thanks.
[Touch Cruise Android Development] manu33xtro:
Problem with network...

Hi DZO,

I don't if I'm alone with this problem :

When I'm in sleep mode I lose network (not all the time), I can see in the status bar the icon "no network"... And I confirm that I can't receive phone calls... When I wake up my phone, I will wait few seconds (between 5 to 1 minutes !) to retrieve good signal...

BUT when I lose the network and somebody will try to phone me, he can heard the ringtone in his phone and after 5 or 6 he fall in my answering !!! It's very very strange because I think that's when I lose network, I'm not connected ?!?

And what I can see tonight is I've no problems in my home with network ?!? I think it's because I'm really close to a pole transmission and have a clear view...

I'm so disapointed because I've problems only when I'm in my work !!!

AND, I try to make more tests but it's difficult, when I charge my phone and make in many times in sleep mode, I never lose network !! Hum hum But I'm in home... I will try monday when I will stay in my work.

I test it with the versions 17, 22, 23 and 25 and with Incubus26JC or Kallt_kaffe eclair versions (CM5.08) : same thing...

But I don't know if it's a kernel or a build (eclair) problem (sorry for that)...

If you want more informations, tell me.

Or if anybody can confirm ?!?

And in the last buil wifi works : thank you.

Cheers.
[Touch Cruise Android Development] SuperJMN:
Wired headset

Just to report that audio isn't routed correctly to the wired headset, even when you stop, wait, and resume playback.
[Touch Cruise Android Development] tmcfarland:
Unresponsive screen with latest DZO kernel and VaniljEclair RLS6

Hoping someone can help ...

I have a POLA100 and have been running Android from NAND for some time now.

I used LoserSkater's NBH editor to change DZO's most recent kernel (polaimg-panel3-320-27-06-10.nbh) from panel type 3 to type 1. I flashed to NAND using bootloader method and installed VaniljEclair_RLS6, the ROM appears to boot normally. But when prompted to touch the android to begin (this part always reminds me of the Pilsbury doughboy commercials) I get no response from touching the screen. I can navigate using the d-pad, but can get no further.

I have since tried various combinations of panel numbers, HW3D settings, and Eclair ROM's. I even flashed back to WM to see if it was a hardware problem - it wasn't, the screen responds to touch just fine.

Looking through the forums, I don't see where anyone else is having this problem - did I miss something when editing the NBH, or does anyone have a suggestion as to what I might try next?

Many thanks!
[Touch Cruise Android Development] SuperJMN:
I had this issue in the past but ONLY booting with HaRET. Is it working under Windows Mobile?
[Touch Cruise Android Development] manu33xtro:
Yes I can confirm, and no problem with last kernel of DZO...
[Touch Cruise Android Development] tmcfarland:
Interesting ... I reverted to an older DZO kernel, from before we needed to use loserskater's nbh editor to change the panel type, and now my POLA100 screen responds to touch again. I am able to use the phone normally, but for the moment I appear to be stuck with an older kernel. I'll post in loserskater's thread to see if he has any suggestions, but does anyone know what I might be doing wrong in the nbh editor? All I did was change the panel type from 3 to 1. Thanks!
[Touch Cruise Android Development] vanderaatje:
Did you also set it to eclair?

I'm using this tool for sometime now but never had a screen problem (i have a pola100)
[Touch Cruise Android Development] tmcfarland:
I tried both "Eclair HW3D" as well as "Donut HW3D", as well the other panel types. I tried again a few minutes ago with the pppnostart option enabled and got the same result. It's obviously something that I am doing or have done ... but what? Just out of curiousity, did you use the latest version of Loserskater's NBH editor, or perhaps an older version?
[Touch Cruise Android Development] vanderaatje:
It's saying 1.0.0.0

size 15.872

size on disk 16.384

Put androidinstall.tar in andboot folder on SD card (nothing else)

Clear all old android stuff from SD card

What I always do is first a task29 job (not sure if it's of any use with android)

then boot into USB install mode 2x reset + camerabutton

Run DZO file (now i'm using 27-06-2010)

after boot hold middle button and and wipe everything

select install (i'm using VaniljEclair RLS6 (CM5.0.8)

don't select exit but do a reset with stylus

Hope this will help you
[Touch Cruise Android Development] dzo:
Can you look through the kernel changelog here:

http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue

And try to find when the kernel broke for you, was it the new ts driver (15th June) or one of the other changes. My pola200 works fine, but there are always slight changes in the hardware that may break things for other people. Do you also get a "waiting for notbusy" message on boot?
[Touch Cruise Android Development] DmK75:
I use Pola100 and latest kernels (zImage).

And a bit strange then that sometimes it starts normally, but sometimes cannot boot with this "error: waiting for notbusy".

Did nothing affect on this, just randomly.

Last kernel w/o this, is from 29-04-10.
[Touch Cruise Android Development] foxct2005:
Same Issue with newest kernel

Same Problem for me ...

Only With Kernel 29/04/2010 I can boot without any problems...

The newest kernels make a double vibration then:

or shoutdown my cruise

or boot with "error: waiting for notbusy" then Android Starts after 5 minutes crashing on "Wait or Kill Service".

I hope to resolve this problem because I would like you new builds with new Kernels.

Regards.
[Touch Cruise Android Development] Murrky:
Yes, I confirm normal boot with 29/04/2010, not later versions.

The latest builds behave chaotic on my POLA100, saying "Error for notbusy", and booting VERY long time afterwards. It is a luck to boot with 27-06-2010 successfully.

UPDATE:

Maybe this is just a mere coincidence but...

I have managed to boot successfully 27-06-2010 three times in a row switching Bluetooth, Wi-Fi and phone module to its opposite states (i.e. OFF if it was ON and vice versa) after Windows Mobile boot just before running HaRET.

First I've thought that switching Bluetooth and Wi-Fi ON helped me to boot, but it turned out to be wrong after I've tried to reboot and WM has them ON after restart. Thus without switching I have a delay in Haret messages after 2nd second of boot process, and after a while (about 15 sec) it says "notbusy".

Maybe someone would try this.

I do not have enough patience to continue that exercise, you can try it yourself (and there are job calls possible :) )
[Touch Cruise Android Development] Murrky:
Damn, it hang on incoming call and switching all radios didnt't help to boot after it :( ...

But switching everything ON after next reboot helped again to boot Eclair successfully.
[Touch Cruise Android Development] tmcfarland:
I have not seen "waiting for notbusy" yet. I just now tried all kernels since 24-05 and my problem does indeed appear to begin with the 16-06 kernel and perhaps the new ts driver. Do you have any suggestions for me, or is there any info I can get from my phone for you?

polaimg-panel3-320-27-06-10.nbh ... no ts

polaimg-panel3-320-25-06-10.nbh ... no ts

polaimg-panel3-320-23-06-10.nbh ... no ts

polaimg-panel3-320-22-06-10.nbh ... no ts

polaimg-panel3-320-17-06-10.nbh ... no ts

polaimg-panel3-320-16-06-10.nbh ... no ts

polaimg-panel3-320-01-06-10.nbh ... ts ok

polaimg-panel3-320-28-05-10.nbh ... ts ok

polaimg-panel1-320-24-05-10.nbh ... ts ok
[Touch Cruise Android Development] manu33xtro:
Strange, very strange : I use the latest kernel in Nand with new build (Froyo) of Incubus26jc and it's perfect... Boot ok, in and out call very very fast...

Maybe with one specific build ??
[Touch Cruise Android Development] foxct2005:
Can you please give me more details (explain better) How and What switching ?

For Example:

- in WinMo i Have Phone On, BT off and Wifi Off....

What i can do for a succefully boot ?

Thanks.

_________________________________________________________________

I was thinking ... Could the different installed Rom on our Pola100 causes differents behaviour with zImage ???

For example, I have Megan Rom ...

Bye !

___________________________________________________________________
[Touch Cruise Android Development] manu33xtro:
Hi DZO,

I think another problem with the battery: when it shows less than forty percent, it suddenly jumps to less than fifteen and told me he would be put in charge !!

I use vizbattery indicator but same informations with parameters of phone.

Is someone can confirm ?

Cheers.
[Touch Cruise Android Development] Murrky:
Well, how it works for ME (after a couple of more reboots), I switch Phone, BT and Wi-Fi to opposite position (OFF if ON or ON if OFF). There seems to be no strict rules, I cannot figure it out. Then I run HaRET from start menu shortcut. The method is not 100%, but at least I CAN boot enough often.

When Haret runs, if it pauses on about 2 seconds (see scrolling log) even before install menu - do not wait any longer: you'll definetely have "waiting for notbusy" - do a soft reset and try again.

I don't know WHY it works, maybe some status of i2c bus triggers or something, but the fact is working Myn Eclair with zImage-27-06-10.

Sorry for my english.

Well, maybe the successful boot does not depend on that switching. It is just a luck :(
[Touch Cruise Android Development] tmcfarland:
I tried three Eclair builds (incubus, myn, and k_k) on the latest kernel and had the same problem. I didn't think to try a Donut build, but will give Froyo a whirl ...
[Touch Cruise Android Development] manu33xtro:
Yes, try Froyo : look my thread, maybe it's better than the others...
[Touch Cruise Android Development] SuperJMN:
Hi dzo! I wonder if you could make the button mapping have a corresponding "Search" button. The current scheme only has buttons for Back, Home, Menu, Call and End. The button for Camera is used like Power, and the Voice Dial button (the one of the upper-left side (above the volume slider) is used only to rotate the screen.

It would be interesting to have more hardware buttons to automatize some task like toggling wifi, bluetooth, starting apps... I tried In-app Wifi Toggle and it's a must! long press Call to toggle wifi, no matter what application is running in foreground... Things like this one can improve the usability a lot.

Thanks from now!
[Touch Cruise Android Development] aragon4711:
Similar issue here on a POLA200 (Orbit 2). I use HARET to start, installation on SD. Starting up takes more than 10 min, but then no touch screen is available. Any hints yet or something that I can do to help?
[Touch Cruise Android Development] tmcfarland:
DZO suggested that my problem might be with the touchscreen driver implemented 15 June. I have reverted to an older kernel, polaimg-panel3-320-01-06-10.nbh, which works although I miss out on a number of improvements. I have since tried a Froyo build (which is excellent so far, btw) but I still have the problem with the touch screen using newer kernels. Please let me know if you find out anything?
[Touch Cruise Android Development] foxct2005:
No Luck with kernels !

Hi all.

Also with newest kernel ... (until 27-06-10) I have double vibrate and SHOUTDOWN.

Please I am disperate ... what can I do to resolve ?

Maybe some programs in WinMo (sense, s2u2, dcibattery, spbplus...) MAKE CONFLICTS with Kernel ?

Why 29-04-10 Kernel works and the newest no ?

Best Regards.
[Touch Cruise Android Development] DmK75:
Very likely because 29-04-10 kernel not have "double vibrate".

A similar situation was already in March
[Touch Cruise Android Development] aragon4711:
Just tried the latest zImage-01-07-10 (using initrd-22-05-10.gz) on my Orbit 2. Unfortunately still no touch screen.

My default.txt currently looks like this:

#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.nostart	- Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=1 board-htcpolaris.panel_type=3 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
[Touch Cruise Android Development] foxct2005:
And HOW was resolved the problem on march ?
[Touch Cruise Android Development] DmK75:
DZO wrote then:
[Touch Cruise Android Development] foxct2005:
1)

... but is there any chance to have a new zImage working on my pola100?

Any patch, customization, editing.... to resolve ?

2)

But zImage is the SAME of .nbh to flash?

I mean: if I flash my pola100 with nbh and install in NAND, I will have the same problems?

Thanks.

Regards.
[Touch Cruise Android Development] Murrky:
No. I have installed Froyo of Incubus (highly recommended, thanks Dzo and Incubus)- works perfect with latest nbh.

P.S. I have used voguimg-240x320-eclair-01-07-10.nbh modified with NBH Editor.

System and data on NAND
[Touch Cruise Android Development] foxct2005:
Can you please try and review about GPS ?

If you confirm me that:

- Video Playback

- GPS Software (IGO or Navigon)

Work perfect ... I will Flash all on NAND surely.

Thanks.

Regards.
[Touch Cruise Android Development] l1q1d:
@foxct2005 KERNEL THREAD!!!!!

Navigon works

video playback doesn't
[Touch Cruise Android Development] l1q1d:
New button mapping

This is the new button mapping for polaris.

You can try it flashing the latest nbh from here
[Touch Cruise Android Development] SuperJMN:
Will this be sporadic or the new official key mapping for our device? :)

EDIT: I see very CONVENIENT to have Back and Home near, and on the same side. They're buttons that are constantly being used. Some people are just used to the current layout, but I'm almost sure that they'll think it's better, too.
[Touch Cruise Android Development] mylostnick:
Jog wheel...

Hi all.

I only wanna say a lil thing to the kernel developers.

I think that the jog wheel is too responsive... every little contact with the wheel cause a focus movement that in much cases it's a problem.

Someone else have had this problem?

There is a way to change this sensitivity?

Sorry for my english. Bye-

PS: I don't know if this is the best way to communicate with kernel developers. If not someone can say me how to communicate with them? TY
[Touch Cruise Android Development] agruman:
l1q1d: that button mapping looks great.

The only thing im missing is a zImage with those changes.

I suppose you have these changes in a local branch, since the old ones seems to be present in the current source tree?

Are you waiting for input before pushing them upstream?

BR agru
[Touch Cruise Android Development] l1q1d:
Updated on my site, i didn't push my modification yet because i want to know what users thinks about.
[Touch Cruise Android Development] manu33xtro:
Hi,

I'm going to test your build but what is the kernel reference ? Do you use the latest version of DZO (7-7-10) ?

Thanks for your modifications.

Cheers.
[Touch Cruise Android Development] l1q1d:
No i use latest (update today :-) )

I'll commit changes in kernel tomorrow. I want some comment about usability. So vote!!
[Touch Cruise Android Development] tmcfarland:
DZO,

It was mentioned in a Kaiser thread that a sensitivity adjustment was made that helped Kaiser users, and it appears to be one of the changes made around the same time the touchscreen stopped working for me personally. Is changing the sensitivity worth trying, is it something I can push using adb, and (if so) do you have an idea of what values I might try? Many thanks!
[Touch Cruise Android Development] SuperJMN:
I'm really happy with the button mapping after one day. I was very used to the old one, but I think I will master it with some training :)

I noticed the latest kernels suffer from choppy sound in console emulators. I heard that someone did some changes in the audio output (I think it may be a buffer length or polling rate). Please, check it!

By the way, ¡VIVA ESPAÑA!
[Touch Cruise Android Development] foxct2005:
What about "waiting for not busy" - im2c error ?

The only Zimage working for my pola100 it's an old 29-04-10 Version !

I am very disperate!

Bye !
[Touch Cruise Android Development] DmK75:
A little patience, if get error try again and again - he will start.

Is only way so far.
[Touch Cruise Android Development] l1q1d:
Or install in nand....