yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] webbdn:
Hey bally3,

Your situation sounds a lot like mine. I bought my Polaris about a year ago for $900 AUD (which seemed a bit exxy but sort of reasonable). Don't get me wrong I am pretty happy with it. But since then I've just been looking at it from the point of view of how much better it could be. My previous phones were all just phones (Nokia) and pretty much used only for calling/texting so I didn't care too much that they had flaws.

I'm stuck now in the situation that I know it could do so much better and I don't want to just toss it and upgrade as it's only a year old.

Personally I'm peeved at HTC. It's all very well to pour all your money into new devices but they also need to support last years customers too.

I'd hate to think that people are ditching their cruises and moving onto better phones (though I understand completely why they would). It just seems like such a waste.

HTC, come on, help us out!
[Touch Cruise Android Development] miazza:
First of all let me say hello to everybody.

This is my first post in the forum a I would like to thank you for the excellent job all of you are doing on the subject topic.

I have a small question:

If I install Android on my HTC Touch Cruise, do I loose all the WM6.1 OS with all the personalisatins I've done ?

Thanks

miazza
[Touch Cruise Android Development] excogitation:
step up and stop asking others to get stuff done

I ask you (end)users to put in some effort yourself and check the bugtracker

if there are already bug reports on all problems that you currently experience

and feature requests for things that aren't yet working on your machine.

Also please add to the existing bugs information that might be helpful to pinpoint

and the exact facts that cause the problem (e.g. wifi turned on before booting, ...).

To help make progress on the feature requests collect information that might

have been lost because it's so scattered across this thread and others

(or just important specifics you remember - heaps of valuable information might be buried).

If you always wanted to help but lack the knowledge for kernel/userspace

developement here's your chance to contribute.

All you need is some time to search for the pearls (or maybe you know some by heart) and

make them available to future developers who want to join - and therefore can

join/code faster because they don't have to sift through thousands of posts themselves.

To all developers didn't wanting to waste effort because someone might be working on the

same issue - you can now communicate what you're working on using the bugtracker.

Thanks Stefan for pushing,

and of course many many thanks to all the developers in particular Martin.
[Touch Cruise Android Development] Mormy:
@ Bally3

I tried to download from first page:

http://vstrien.csoft.net/Polaris-build/polaris-build.tar.bz2

But it didn't work.....broken link??
[Touch Cruise Android Development] imfloflo:
I had just try the new zImage from the repo of stephan (http://gigatron.de/.android/builds/) with the lastest change from DZO for the usb.

but boot stop after 2sec(i hadn't the usb plug in).

I retry with the usb plug in and it's ok.

All seems to work, except the LED which doesn't blink at all, and the usb not work for me (I'm under Seven build 7057) and the usb plug in doesn't charge the battery :s
[Touch Cruise Android Development] biktor_gj:
Hi all,

I've been quite mute here for a while, I've been working mostly on the nike lately, sorry..

To make charger detection and enable work on the Polaris you need to know some pins. On the Nike, the USB detect and Charger detect go through CPLD, but the charge enable and charge current are set on normal gpios.

I traced the charge enable and charge current through haretconsole and watch gpios, and disabling charge from Windows Mobile settings (Power settings) and then enabling it back (you should see some Out pin change)

it wasn't me who traced the cpld pins for usb detection though, so you will need to do it yourself (I still don't know how to trace them from windows, I just know how to get the state from linux after booting, wich could be an alternative way if you don't find them yourself)...

Can anybody tell me where is the USB_DETECT, CHARGER_DETECT and if possible,headset_detect pins? Also, if you can tell me wich pins enable charge I would be glad to patch the driver so you can charge the phone within Android.

Also, if anyone can grab the AudioParam*.csv files from \windows folder and put it somewhere else, I can see if they're different from other phones and patch it to help make headset work on polaris (I'm on it for Nike and still have work to do, but I can try anyway)

Regards!

PS: I've been taking a look on the Polaris keypad driver and I think you need to change it a lot to make the wheel work, if anyone want I can try to make something for it... just tell me so :)
[Touch Cruise Android Development] imfloflo:
OK so i can log the gpios with haretconsole to find good pin.

But on the previous release charger battery was working,

so i think the lastest release of dzo break some part of code, maybe.

AudioParam joined
[Touch Cruise Android Development] biktor_gj:
Thanks, I'm porting them to the kernel, will post a build for you to test when I get something to work!
[Touch Cruise Android Development] excogitation:
credits go to biktor_gj

The attached kernel detects AC in Android, USB not yet (1-5 is the only gpio change when I have charging enabled through usb cable - but that doesn't seem to be it - there's no change in Linux to it when connecting it in Android -> see dmesg).

Also it boots without usb connected (dzo's latest changes to usb aren't enabled though) and I didn't check if it does charge but maybe someone tests it an tells us.

Regards!
[Touch Cruise Android Development] radem205:
it's working great! nice leds are blinking while charging. great job biktor!
[Touch Cruise Android Development] imfloflo:
Thanks radem205 & Exco.

The LED works great no USB detection for the moment but good progress.

Just see that the LED only blink when until the screen is OFF after goto sleep mode and return back to the screen the LED doesn't blink anymore.
[Touch Cruise Android Development] marcelkordek:
thanks works great!!

EDIT: testing your zimage, it's not charging...

tested kernel from dzo, android doesn't detect ac but if you launch "MyBattery" (from market) you see that it's charging !!
[Touch Cruise Android Development] marcelkordek:
onscreen keyboard

maybe usefull ?!

when i try to install "install unsucessfull"

On-Screen Keyboard

hope someone can install this.
[Touch Cruise Android Development] radem205:
Good research! But I have the feeling that my phone isn't able to communicate with the SD card. I can't see the pictures stored on the sd card and when I put in some .apk in the directory "AndroidApps" it won't install it :(
[Touch Cruise Android Development] marcelkordek:
I use "Linda Filemanager" and it works fine, i can see all my pictures and music on sd card.

I make a new folder on sd (for example: install) and put .apk's in it. With Linda Filemanager i can see all .apk's in this folder.

-
[Touch Cruise Android Development] radem205:
I also get the message "Installation unsuccesfull". I think it has to do with the apk and not with Android itself.
[Touch Cruise Android Development] imfloflo:
@radem205 didi you success to have polaris USB working ?
[Touch Cruise Android Development] radem205:
No, unfortunatly not :(. But I have talked to Biktor, and he said that it is propably caused by the fact USB charging isn't working yet. When this is working USB is working too.
[Touch Cruise Android Development] imfloflo:
But the usb charging was working before few zImage ago
[Touch Cruise Android Development] Mormy:
ok, is a relly newbie question, but...which is the menù button??
[Touch Cruise Android Development] imfloflo:
Ok it's a really newbie response : try all the button
[Touch Cruise Android Development] Mormy:
:) Already did it, but no clue...

One time it started and I tried to phone, it works, but then I couldn't go back to the main menu.

Quite always it stars "locked" with the writes:"press menu to unlock"
[Touch Cruise Android Development] imfloflo:
Ok just read the Wiki page and you will find all the button mapping

http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux
[Touch Cruise Android Development] Mormy:
I'll must wait to recharge my little one, then I'll try it again. Thanks :)
[Touch Cruise Android Development] imfloflo:
I read in the Dream forum there was a Dump of the HTC Magic rom so we can have the cupcake version with keyboard soon :)
[Touch Cruise Android Development] radem205:
Where exactly did you read that?
[Touch Cruise Android Development] imfloflo:
http://xdaforums.com/showthread.php?t=498026 in this thread but i don't find it anymore
[Touch Cruise Android Development] Mormy:
It seems that I'm unlucky. Now always starts in "safe mode" and "locked".

No button works, also the reset one. I need to remove the battery to restart the system :(
[Touch Cruise Android Development] biktor_gj:
Copy a new data.gz from any package. Probably one of those lockups broke some files and it doesn't boot ok because of that. You will loose your settings though, but it should work
[Touch Cruise Android Development] briggs81:
Has the Wiki been abandoned?
[Touch Cruise Android Development] excogitation:
Feel free to edit away.

There have been no changes to Polaris in particular (kernel side) and I'm not up to date on what has changed with the latest images.
[Touch Cruise Android Development] radem205:
From the kaiser thread: http://xdaforums.com/showpost.php?p=3623839&postcount=4754

SDK 1.5 has a soft keyboard included, so great news for us I think!
[Touch Cruise Android Development] bally3:
Lo peeps :)

Just got back from a refreshing long caravan holiday - unfortunately I couldnt even get a mobile signal let alone 3G or broadband as I was in a proper rural retreat! (bliss for the mrs, hell on earth for me).

Been catching up on the posts, and saw the sdk 1.5 postings - which seemed to have been ignored when I posted the link to it - I wonder what the difference is from mine, apart from the fact that mine said beta?

Anyhoo, looks like we may finally get our keyboard which is great news.

I now have two volunteers to test the naked Maxniper rom and will liaise with Maxniper to get this up as soon as we can.

In the mean time, did anyone try that keyboard posted earlier? it looked like it needed compiling before we could use it.
[Touch Cruise Android Development] excogitation:
meep meep

tracing

so my conclusion is that 1 is fast charge, 170+171 needs to be 0 to detect usb on 21 and 28 is ac and 170to1 is enable charge.

Who doesn't agree?

well anyways there's a kernel ... makes an orange led for usb charging, red one for ac charging.

Feel free to check dmesg if charging is actually working (boot to Android plug in USB/AC for some 10s, reset, pwf dmesg.txt 0xe0000 0x20000 in haret gives you a dmesg.txt on your storage card)

I think it is. Needs to be cleaned up and improved though.

Next up USB networking.

Tell me if booting with/without USB/AC dis/connected does work and if the status is always right.

Good night.

edit: yep, charging is working dmesg ~300-400mA on USB and ~1000mA on AC.

looks good to me.
[Touch Cruise Android Development] radem205:
Nice job exco! so now, probably, usb networking is working too, isn't it? because biktor thougt usb networking isn't working cause usb charging wasn't working before.
[Touch Cruise Android Development] marcelkordek:
thanks exco, works great... boot with/without usb/ac plugged
[Touch Cruise Android Development] miazza:
Hello to everybody

I have copied all the content of Android.zip (All in one) and the last zimage of this 3D on the root of my memory card.

I have launched herat but the phon lock with message Booting Linux and I have to remove the battery to reanimate it.

Why ?

miazza
[Touch Cruise Android Development] imfloflo:
Certainly a bad system.img or initrd files download lastest files froms DZO and copy exco zimage files over it after.
[Touch Cruise Android Development] pananza:
Great work man. Finally a kernel thar is usable. Still Android uses too much power, but at least I'm able to charge now. Went from 100% to about 50% in 3 hours or so.
[Touch Cruise Android Development] miazza:
I have done it again and now the situation is a bit differnt:

Bott starts and the pinguin is visible.

After a few seconds, the boot stops with 1.994251 Kernel panic - not Synkind: attempt to kill init !

At this poin I need agai to remove the battery.

I have a HTC Touch Cruise. Could you link me where to find correct files ?

Now on the root of my SD Card I have the below situation:

13/11/2008 11.58 2.527.781 data.gz

09/02/2009 17.23 1.290 default-kaiser.txt

13/11/2008 13.43 1.097 default.txt

13/11/2008 13.44 137.216 haret.exe

09/02/2009 14.59 2.618.553 initrd.gz

17/02/2009 00.17 38.154.240 system.img

17/02/2009 00.18 1.429.464 zImage

Please help.

miazza
[Touch Cruise Android Development] imfloflo:
I see what the probleme is, and i also see that you only have 3 post.

Please reade the thread and the wiki all has already been say lot of time.

Tips just follow the steps. (ctrl+a)You must change your default.txt

edit: new release from dzo what should we take dzo or exco :p http://xdaforums.com/showpost.php?p=3635666&postcount=4774
[Touch Cruise Android Development] dzo:
If you push any polaris changes to the git repo then they will be the same!
[Touch Cruise Android Development] miazza:
Yes U R Right, I have only 3 posts but now are 4 and may be will increase when the system will boot.

Now the mobile is in charge and I cannot apply for a while.

I have read almost all the 3D (It's about 1 week I'm reading this interesting issue) but have not foind any TIP on the default.txt.

May be you can dyrect me to a more specific 3D This is very long and dispersive)

Sorry disturbing you with so easy things but ...

my default txt is the following:

set RAMSIZE 0x08000000

set MTYPE 1667

set KERNEL zImage

set initrd initrd.gz

set cmdline "msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"

boot

Should I change it as below ?

set RAMSIZE 0x07000000

set RAMADDR 0x10000000

set FBDURINGBOOT 0

set MTYPE 1553

set KERNEL zImage

set initrd "\Storage Card\initrd.gz"

set cmdline "msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"

boot

Thanks

miazza
[Touch Cruise Android Development] imfloflo:
You don't disturbe me ;)

I was just tryig to help you :p

ok so you must have on the root of your SD card only this files about android :

haret.exe

zImage

data.gz

initrd.gz

and default.txt with the good params :

set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1723
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"
set cmdline "board-kaiser-battery.battery_capacity=1800 board-htcnike-keypad.slide_override=0 board-htcnike-keypad.keypadlayout=0 board-htcnike-keypad.sticky_timer_time_ms=700 mddi.width=312 mddi.height=416 ppp.apn=internet ppp.username=\"\" ppp.password=\"\" pm.sleep_mode=0 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend"
boot
[Touch Cruise Android Development] biktor_gj:
Just for you to know (specially excogitation)

Once you get the usb up again you'll be missing a small part you'll have to trick manually. When connecting usb, you have to bring up the ethernet interface manually on the phone and on the computer, so you may need to update your system.img a bit or place a script where you can run it later, with the command 'ifconfig usb0 [address_you_want_for_the_device] up

After that you'll be able to communicate through ethernet using telnet. I think you'll be able to use adb also, but not too sure (it's been 5 days since I don't boot android, and have the phone all wiped out to test it now sorry)

About the board-kaiser-battery, that was mainly for the nike, since it uses a 1150 mAh battery and otherwise percentages don't show correctly, if your battery is 1350 mAh (i think that's what kaiser is) you shouldn't nned that. For htcnike's specific stuff, it's no use having it, you won't get anything different unless you boot with nike's mach type, so you can safely remove that from the cmdline. Also, you shouldn't need the ramsize parametter, unless it's giving you problems booting.

@ the guy with not finding the mmc partition: Try checking/formating your sd card, seems like the kernel doesn't find your card when booting (that's the kernel panic, isn't it?) anyway, for the next time, try to post two or three more lines of the messages, so it's easier to understand for the rest :)

The ppp.apn cmdline parametters are needed for some people who need to type in the username and password (or so they said on the kaiser forum some time ago). I personally only have to use the "internet" apn name on android settings and Im good to go, but it depends on operators...

Regards!

EDIT: Oh! I almost forgot! To gather info about the cameras and such, the bootloader may come handy: Reboot into bootloader mode, disable usb connection on activesync, and launch putty (putty = terminal emulator for windows :)) Open a Serial connection to \\.\WCEUSBH001 and enable all session logging (Session -> Logging -> All session output) and when you've got it open, run "task 38". That will give you the windows log, with it you'll see a lot of useful information (for example, camera models, audio parametters, a lot of crap from manilla/htc home...)

I said putty because it's easier to use and to dump logs from, but you can use whatever tool you want :)
[Touch Cruise Android Development] miazza:
Thank you to imfloflo and excogitation.

This evening I will try and let you know.

Thanks again.

miazza:)

It's working great !!!

Thanks guys.

I also needed to copy system.img.

Thanks again. I will test it and let you know.

Bye.

miazza
[Touch Cruise Android Development] excogitation:
I still have a problem I don't understand:

[ 71.030616] GPIO 170 = 1 before setting
[ 71.030681] Im charging the battery from AC power
[ 71.030728] GPIO 170 = 1 after setting to 0

i = gpio_get_value(170);
mdelay(50);
printk ("GPIO 170 = %i before setting\n", i);
printk ("Im charging the battery from AC power\n");
gpio_set_value(170, 0);
gpio_set_value(1, 1);
i = gpio_get_value(170);
printk ("GPIO 170 = %i after setting to 0\n", i);
[Touch Cruise Android Development] marcelkordek:
new zimage works, but i have a problem now... i haven't audio during calls =(
[Touch Cruise Android Development] radem205:
New zimage works also. Very good job. I'm able to run the terminal on a linux machine (thanks to biktor_gj). I have no problems with audio during calls.
[Touch Cruise Android Development] excogitation:
I don't have audio problems either (but I only had an incomming call before and didn't check calling someone).

For all that want to play with the terminal as well:

initrd.gz which does the ifconfig up on the client (Polaris), thanks dzo.

zImage
[Touch Cruise Android Development] imfloflo:
How can we put text in terminal without keyboard?
[Touch Cruise Android Development] radem205:
Because you have an usb connection between your host pc and your phone you can acces the android terminal on the host pc (linux for example). So you can type whatever you want in the android terminal using your pc :).

And Exco: Telnet is working very well! Great progress! Keep going :)
[Touch Cruise Android Development] imfloflo:
OK with adb shell ? or mount the phone on the host pc ?

Can you explain what command did you enter to do that please. :)
[Touch Cruise Android Development] excogitation:
you don't even need to unplug the usb cable. Just boot with it connected.

then:

root@bored:/home/excogitation# ifconfig usb0 192.168.2.2 up
root@bored:/home/excogitation# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=6.01 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.07 ms
^C
--- 192.168.2.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 3.075/4.544/6.013/1.469 ms
root@bored:/home/excogitation# telnet 192.168.2.1
Trying 192.168.2.1...
Connected to 192.168.2.1.
Escape character is '^]'.

localhost login: root
Password:
# dmesg
[ 0.000000] Linux version 2.6.25-00731-gad3c077-dirty (excogitation@bored) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #194 PREEMPT Thu Apr 16 23:29:55 CEST 2009
[ 0.000000] CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387f
[ 0.000000] Machine: HTC Polaris
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 28672
[ 0.000000] DMA zone: 256 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 28416 pages, LIFO batch:7
[ 0.000000] Normal zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] CPU0: D VIPT write-back cache
[ 0.000000] CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
[ 0.000000] CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 28416
[ 0.000000] Kernel command line: mddi.width=312 mddi.height=416 pm.sleep_mode=0 board-htcpolaris.panel_type=0
[ 0.000000] irq_type0 was f4e401ff
[ 0.000000] irq_type1 was 203c
[ 0.000000] setting GPIO 170 and 171 to 0 to make USB charging work
[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 0.000000] Console: colour dummy device 80x30
[ 0.000036] console [tty0] enabled
[ 0.000951] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.001701] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.014801] Memory: 48MB 64MB = 112MB total
[ 0.014910] Memory: 107276KB available (2624K code, 921K data, 96K init)
[ 0.016338] Calibrating delay loop... 383.38 BogoMIPS (lpj=1916928)
[ 0.230798] Mount-cache hash table entries: 512
[ 0.232210] CPU: Testing write buffer coherency: ok
...

user: root

password: vogue

full dmesg output

Isn't too stable on my machine yet ... maybe network-manager or something is interfering.

discharging
[ 252.549062] 2746: 3816mV -228mA charge: 70/100 (3052 units)
USB charging:
[ 65.598187] ds2746: 3947mV 419mA charge: 68/100 (2939 units)
AC charging:
[ 93.021752] ds2746: 4108mV 1083mA charge: 68/100 (2967 units)

radem205, are you working on anything?

rogro82, still around?
[Touch Cruise Android Development] miazza:
Perfectly working to me and also audio works correctly.

I can also connect TELNET from KUBUNTU.

I just have a trouble:

I cannnot close a conversation. The RED button is not working.

Furthermore, something is forscing a connection and in a couple of hours I had my credit (about 10 EURO) over:(.

Every time I boot Polaris I also receive a SMS from my provider that I have not sufficent credit to connect. But to connect to what ? :confused:

Before to charge again my credit I need to investigate this issue :rolleyes:.

Bye

miazza
[Touch Cruise Android Development] imfloflo:
You need a data plan to use android, else yuo will have big charge
[Touch Cruise Android Development] miazza:
WOW:eek:

I was not aware of this issue. Likely I have inserted a rechargable SIM and not my plan.

I think that this will limit very much my enthusiasm on Android.

Isn't there any possibility to configure Android for not connecting the web automatically ? This is a major limitation for those who do not have a data plan.

Ciao

miazza
[Touch Cruise Android Development] dzo:
Use my initrd, it doesn't connect automatically.

http://cs-alb-pc3.massey.ac.nz/vogue/files/initrd.gz
[Touch Cruise Android Development] miazza:
Thanks DZO.:)

This is working. Thanks very much.

I suppose that if I want to connect teporarly I need to connect via TOGGA.

miazza
[Touch Cruise Android Development] imfloflo:
Lastest DZO release working great :)
[Touch Cruise Android Development] marcelkordek:
is it also detecting ac or usb charging?

edit: works great but doesn't detect ac...

@exco: can you make a zimage with changes from dzo and yours ? thanks