yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] ikke008:
Thanks:) Nice, Did you install Nav Launcher 2.1.3 from the market?
[Touch Cruise Android Development] NeoS:
Polaris Android is finally getting somewhere. Great improvement guys, two thumbs up!

So, AFAIK, Android still isn't good enough for everyday use, because the calling funtion doesn't work. (at least, on my Polaris) And it crashes alot.

But still, Android is WAY faster than Winmo in alot of things, and I for one am thinking of getting an Android device and say farewell to Winmo.
[Touch Cruise Android Development] ikke008:
I use my Polaris Android every day :)

Cqlling function is working perfectly, and Android hasn't ever crashed..

I guess within a few months, Android will have no bugs anymore on the Polaris.

So, if i were you, I would wait.. :)
[Touch Cruise Android Development] w04g005:
For me calling also works BUT the IN CALL VOLUME doesn't work! It's very loud! Has anybody the same issue?
[Touch Cruise Android Development] snempaa:
Yes, I have the same thing, and the speakerphone doesn't work eighter! But anyway the progress has been so good! I've had my polaris on my desk for about half a year, doing nothing with it and now I'm using it again with Android running on it! Thanks everyone (who contributed!).

I was wondering but couldnt find it in this thread, is there already a test going on with a flashable rom? Some gave the vogue stuff a try? Let me know if somebody has more info on that, because it's a little bit annoying receiving text messages in WinMo (when my battery went dead and I had to reboot Android) before booting into Linux.

Thanks again!
[Touch Cruise Android Development] NeoS:
It seems i'm running a very old build then. The latest build according to the wiki is from 15-07-09, is that correct?
[Touch Cruise Android Development] Michel82:
No that is very old indeed. It's quite hard to get all the latest files, they're spreaded over the different fora and the web.

- Get the latest basefiles from here: http://code.google.com/p/vogue-android/downloads/list?can=1&q=

And overwrite the files with these newer versions:

- Get the latest zImage from DZO's webpage: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

- Get the latest rootfs with working GPS from this post: http://xdaforums.com/showpost.php?p=5125357&postcount=208

- Get on the vogue forum for a system. I'd recommend a 1.6 donut one. Haven't tried this one myself, but plemens build (based on zenulators work) seems to be pretty good: http://xdaforums.com/showthread.php?t=591104
[Touch Cruise Android Development] Michel82:
To do:

Polaris specific:

- Bluetooth

- Button mappings

General:

- GPS speed and direction

- Audio (in-call volume, speakerphone)

- FM radio

Please update ...
[Touch Cruise Android Development] w04g005:
I would recomend the "in call volume"! I think this isn't a great thing. What do you think? It really sucks when all people driving in one subway can hear what i'm talking about! ;-)
[Touch Cruise Android Development] Michel82:
Thanks, that's a good one. I've added audio as a more general term as there are more issues with audio as just the in-call volume.
[Touch Cruise Android Development] NeoS:
Thanks Michel, i'll try and see if this works.

edit:

nope. I'll have to retrace my steps here...

edit2: NVM, it's booting now. I d/l the wrong rootfs.img... Dumb.

edit3: I've created a rar which contains the files foor SD card. Is there any place I can put the working package for easy use?
[Touch Cruise Android Development] excogitation:
is there a package around with usb networking instead of adb?
[Touch Cruise Android Development] Michel82:
Vilord beat you to it and uploaded a new basefiles.zip to the sourceforge page:

http://sourceforge.net/projects/androidhtc/files/
[Touch Cruise Android Development] vorticerosso:
Hi Michel82,

I'd like to suggest the FM Radio, also if its not very important.

Thanks
[Touch Cruise Android Development] vilord:
when i last poked at polaris things, the button mappings were okay... what have they turned into now?

And for audio, has it always been that way? I thought volume/speaker control used to work? (it is fine on vogue, but I haven't had service on the polaris for a few weeks) I'll try calling 611 and adjusting the volume, turning on speaker when i'm looking at buttons...
[Touch Cruise Android Development] imfloflo:
last time i played with it, button mapping was good, volume control was working for me. All functions were working with the release of dzo.
[Touch Cruise Android Development] ZeGuido:
I am using ion built cbr43, and I confirm that I don't have volume control during call (works when not during a call). And speaker doesn't work either. In case it helps.
[Touch Cruise Android Development] Michel82:
Don't remember the last the mappings have changed, but it's like this for quite some time now. The mappings of the buttons aren't the biggest issue, the wake-up thing is a bigger thing. Powerbutton wakes the phone and you have to press end to sleep (powerbutton should sleep the phone also i.m.o). When you sleep the phone you have to leave it without touching a single button (and the wheel is quite sensitive) for a random amoiunt of time (can be seconds to about a minute) or it wakes again. This is pretty annoying if you want to leave and put the phone in your bag or pocket.

For as far as i know setting the in-call volume has never worked; the default is quite loud, but usable. I know the speaker was fixed by DZO at sometime when he worked on his big audio changes, could it be a donut thing this isn't working anymore? Would be very handy, it's illegal to drive calling hands-on in the netherlands ;)
[Touch Cruise Android Development] CruiseMod:
I run Android with that

http://sourceforge.net/projects/androidhtc/files/

and the system tha michael said 1.6.. and i have strange problem

in the screen where it say "Press menu to unlock etc...."

the green button doesnt click with result the lock screen do not unlock :S
[Touch Cruise Android Development] excogitation:
Agreed - and yes, in call volume is working perfectly fine with 1.5 so it's a 1.6 related problem.
[Touch Cruise Android Development] mc_joe:
any chance of making the eclair builds work on our beloved polaris? =)
[Touch Cruise Android Development] CruiseMod:
Guys .. any help here ?
[Touch Cruise Android Development] meknb:
The key below the green key use to unlock unless they changed the keymapping.Best post questions like this http://xdaforums.com/showthread.php?t=558062 this one's for kernel development.
[Touch Cruise Android Development] Michel82:
I've never used the FM radio myself but i've added it to the list. I guess this is a general thing.
[Touch Cruise Android Development] Michel82:
That's is not correct. I'll list all current button mappings:

Menu = explorer button (below red/end)

Back = Nav button (below call/green)

-----------------

Wake = power

Sleep = end

Power off = Long press end

-----------------

Keyboard = Long press explorer

Applist = Long press camera

Voice dial = Long press Call (gives a force close in donut)

-----------------

Rotatescreen = Memo button

Moving around = Wheel rotate / Wheel four point keys

Confirm/enter = Middle wheel button

-----------------

Call = Green call button

End call = Red end button

-----------------

Volume = volume (doesn't work in-call)

Single press camera button does nothing.
[Touch Cruise Android Development] Kiiv:
I'm not totally agree with you :/

For me, Power button do the same things as camera button : wake up the phone when in sleep mode, come back to home from an application, and a long press displays current opened apps.

To unlock the screen it's the explorer button.

EDIT : little mistake : camera button doesn't wake up the phone, only power button
[Touch Cruise Android Development] flaviusio:
Hi.I have a question!?

Looking on the http://sourceforge.net/projects/androidhtc/files/ I wonder if androidinstall.zip works for polaris too.It uses .nbh file to flash linux kernel
[Touch Cruise Android Development] manu33xtro:
Hi, I try to install Android to nand but I can't !! :( Impossible toi install kernel with RomUpdateUtility or with the boot mode phone... So I use with the SdCard...:D
[Touch Cruise Android Development] Michel82:
I wouldn't flash to your polaris yet. That is specificly made for vogue hardware. It will not initialise all your hardware.
[Touch Cruise Android Development] flaviusio:
even if you'll want to flash it,it won't let you because of the model ID
[Touch Cruise Android Development] SuperJMN:
There must be something bad with Wi-Fi:

Sometimes, with no apparent reason you will want to turn Wi-Fi on/off, but as the transition takes place, it hangs and the process doesn't complete. This is easily noticed if you go to Settings/Wireless/Wi-Fi. It's permanently "Turning off...".

I haven't found any relation of cause/effect. It happens from time to time. I also noticed that it could be the reason why my device doesn't sleep sometimes.

Please, take a look at this issue. I use Wi-Fi with WEP security enabled.

Edit: Yes, I confirmed it: after a few times toggling Wi-Fi, the device is not suspended when I press the End button. It seems that some process is blocked trying to turn it off (It says "Wi-Fi. Disabling..." grayed and the checkmark is checked, but also grayed).

Are you having problems with the device going to sleep? The orange LED should blink every 5-6 seconds. Did you found that your Wi-Fi was unable to start/stop? Please, provide feedback.
[Touch Cruise Android Development] vilord:
WIFI sleeping has issues still...

But just as a teaser, I got an almost fully functional tattoo build working on the polaris (doesn't work on vogue yet)... calls, text, data, web, music, etc all work out of the box. Some issues remain with accessing contacts from the SIM card, for example, but I should hopefully have it posted in the next few days :D (will also likely work on Kaiser/nike/etc, all the GSM phones)
[Touch Cruise Android Development] excogitation:
*dang* and I just bought myself a Magic ... ;-)
[Touch Cruise Android Development] osilvan:
Ohhhh!!! I can't wait for it, the best christmas gift. Could you tell us more? Is it based in dzo kernel? Did you use tattoo kernel sources?

Many tks vilord
[Touch Cruise Android Development] kulen:
Can't wait enough for that late christmas present. or early new year present :-)

Marry Christmas everyone!
[Touch Cruise Android Development] bally3:
One thing about Jesse.. he does like to tease us :)

Thanks for all your hard work matey..
[Touch Cruise Android Development] bbezja1:
Viloooord we pray to you every night before we go to sleep.

release what you got :eek:
[Touch Cruise Android Development] SuperJMN:
I feel like you.

* SuperJMN is lighting candles to offer to their Immensity, hoping that the sleeping issues are solved.
[Touch Cruise Android Development] vilord:
No kernel changes, just RIL changes... And I have no idea how it'll work with various SIM cards... I know that there will be a bunch of things more to be fixed, but I'll try and get something out tonight or tomorrow (been visiting family since I last posted, tonight too).

All I want to do before releasing is to clean up some debugging and to switch over from the Vodaphone tattoo sources to the WWE sources to get rid of the branding.
[Touch Cruise Android Development] ezman:
Nice one, really looking forward to trying this out :)
[Touch Cruise Android Development] SuperJMN:
Any news regarding Polaris?

Happy new year to everyone!
[Touch Cruise Android Development] vilord:
Okay, I finally cleaned up what I've been working on the past few weeks :)

Hopefully some folks out there can test! I'm really late for sleep.

New sqsh with tattoo senseui!

so this is senseui from the tattoo, so it runs at native resolution 240x320. I have not tested it at *any* other resolution.

I haven't done a lot of testing so I can't guarantee everything works... ie I think that bluetooth might be broken? who knows... other folks please post your experiences!

Please note: I *have* seen the whole thing crash due to WifiService dying on my vogue once... and I've also seen a hard lockup on the polaris once... not sure why or workaround, but it doesn't seem to be commonplace.

I use the tattoo.user.conf and I *don't* use rosie, and it runs nice and speedy... YMMV.

New rootfs that cleans up a *lot* of little things... required for tattoo.

Maybe I'll post some screenshots? who knows...

Everything is HERE
[Touch Cruise Android Development] SuperJMN:
Hey vilord! thanks for your work! I'm now testing it on a 3 partitions configuration

1 FAT32

1 Ext2 (256MB)

1 Ext2 (256MB)

The Ext2 partitions are just formatted to avoid problems. The FAT32 partition has the new Tattoo SQSH renamed to system.sqsh.

I press VolDown, as usual. Then I press it again to Upgrade. Later I don't make a backup and continue. When it tries to start it says:

Using partitioned system

e2fsck 1.41.4 (27-Jan-2009)

/dev/block/mmcblk0p2 is mounted. e2fsck: Cannot continue, aborting.

mount: Device or resource busy

Failed

Failed to mount /system

I'm using the latest DZO's kernel, the corresponding config file, and rootfs.
[Touch Cruise Android Development] Kiiv:
Thanks a lot Vilord! :)

The tattoo build of my dreams!

I'll try it soon. I hope I will not get the same problem as SuperJMN ;)

:p

EDIT : I've got the same error :(
[Touch Cruise Android Development] ezman:
can anybody post really simple to follow instructions on how to get this working - over on the vogue thread, there's an androidinstall.zip which seems easy enough. I just don't know what to do with all these files. I have had android working with haret, how do I get this flashed?

Sorry for being a dumb ass :p

ezman
[Touch Cruise Android Development] Kiiv:
Actually, you can't flash android on a polaris yet :p

Just use haret as usual.
[Touch Cruise Android Development] geopit:
Everything works without a problem on Polaris 200/XDA Orbit 2 /.
[Touch Cruise Android Development] geopit:
All without Bluetooth!
[Touch Cruise Android Development] SuperJMN:
I've had problems with the Wi-Fi. It wasn't able to turn off :( Is DZO working in a better kernel to avoid lockups?
[Touch Cruise Android Development] crucky:
geopit can you upload youre ready ² start packages ? would be perfect !! thanks every one involved to get a perfect android polaris :D keep up the good work
[Touch Cruise Android Development] Galdan:
i get a errormessage "The process android.process.acore has stopped unexpectedly. Pleaste try again. Force close". After I press "Force Close" the same message appears again after few seconds.

But what i can try between the few seconds of the errormessages looks amazing :)

Thank you!
[Touch Cruise Android Development] vilord:
did you start with a clean data image? if you're going from files, you might need to rename the data.img and reboot (will take a longish time)

Looking at the bootup issue now...
[Touch Cruise Android Development] vilord:
I don't know what could be causing the bootup issue :(

I'm dropping in some debugs and catchalls that might help, and I'll post to SF after a few minutes.
[Touch Cruise Android Development] Kiiv:
What have you done to resolve the "Failed to mount /system" problem ? :/

EDIT : ok, the installation seemed to be ok because, after booting android again without running the installation process, it works fine... don't understand :(
[Touch Cruise Android Development] w04g005:
Tested all with the new rootfs.img but couldn't get the mobile connection to work. Changed back to the former rootfs.img and now it works

OK I get following bug:

The process com.android.phone has stopped unexpectedly. please try again

i'm using this build without partitions and with haret
[Touch Cruise Android Development] Galdan:
i deleted my old data.img, bu i used a old initrd.gz

i changed it and now it works amazing!

one small annoying thing: when i change back from a application to the mainscreen the loading screen appears and it tages ages...

but i can life with it...

thank you again for the good work!
[Touch Cruise Android Development] iseeka:
thanks a lot!

tried on my pola100 and works very well.. a bit laggy

does it work fast partitioning the sd?

great work
[Touch Cruise Android Development] SuperJMN:
Hello my friend!

Doing that way, you just have booted up with the system.sqsh that you have into the root of your FAT32 partition. You didn't actually installed it into the Ext2 filesystem. So it worked flawlessly :)

Vilord has published a new rootfs. I will check whether it fixes the problem or not.

Report after using the build:

- SenseUI is a little hidden. You have to press the Home button (power) to pop up a menu which lets you select Home or HTC SenseUI. It worked for me just the first time :( It loaded the application icons really slow, but later it behaved smoothly and snappy.

- Wi-Fi lockups from time to time (it doesn't toggle)

- Calls are working, at least receiving :)

- Data works, but it's confusing. It shows a "G" when it's really "3G" (I've made some speed tests)

- I have been unable to manually select a Network.

- Camera pictures: no auto-focus, too blue.

- Some processes tend to fail, and I had a few "Force closes".

- Bluetooth not working.

- GPS not tested.

- FM Radio, doesn't detect the headset (and probably it also doesn't deal with the real hardware thingy)

I will report any other issues.
[Touch Cruise Android Development] Kiiv:
Thanks for your answer! But I don't think so ;)

At the first haret launch I've run the installation process, a the end of this boot I've got the previous error message.

I've reboot under winmo (no more system.sqsh in my android folder), run haret again, not run again the installation and I booted up under tattoo.

So I think it really run on the partitions :)

I've no problem of a "little hidden" senseui. Which resolution and density are you using? :/ I'm in 320x240.

The only problem for me at the moment is that sensui reload each time I came back to home from an application :( Even after rebooting the phone..

But it's a great job vilord, it's running very smoothly for now! :)
[Touch Cruise Android Development] bbezja1:
after the loading animations i only get white cursor in top left corner. im guessing it has to do with wrong resolution set in default, but it is 320x240 and 160 density
[Touch Cruise Android Development] SuperJMN:
Hi! I'm using 240x320, too.

It's true that SenseUI reloads the icons every time it's shown. It's annoying, so I set the default to the standard "Home". Now I cannot show SenseUI anymore, :(

About to the ext2 configuration, the new rootfs.img still doesn't make it bootable. I think that Vogue users are having the same issue: http://xdaforums.com/showthread.php?t=611672 Post #5
[Touch Cruise Android Development] Kiiv:
Go to "Settings/Applications/Manage applications" and search for "Home" application. Click on it and in the "Launch by default" try to click on"Clear defaults". Now it should ask you again for SenseUI ;)
[Touch Cruise Android Development] vilord:
okay, the rootfs booting issues are fixed! (i hope!)

And to get rid of the senseUI reload, try renaming the conf folder on your SD card and booting up, lemme know what you see :)

Thanks!

Edit: Oh yeah and thanks for all the notes! I'll work on it as I have time. FM radio seems to be attached to music iirc, so I'd have to get rid of both or neither...

hopefully once this is working nice and clean we'll have an eclair update for tattoo and I can reuse the work for that!
[Touch Cruise Android Development] Michel82:
Just got back from skiing holidays in Austria and I see great progress has been made since Christmas. Very exciting, I'll try as soon as I get home from work.
[Touch Cruise Android Development] SuperJMN:
Wow, vilord! ext2 booting is working now like a charm :D

Can you please refresh my memory with you PayPal donation link?
[Touch Cruise Android Development] vvsprog:
vilord you are the best..

nice work!
[Touch Cruise Android Development] vvsprog:
what do you mean ext2 booting?

now i'm runing tatoo with haret..
[Touch Cruise Android Development] vilord:
sd card partitions are definitely faster :) just pop your SD card into a computer, and resize the main partition, adding two approx 200 meg partitions at the end of the card, the installer will take care of the rest.

since you ask, the donation link is on http://androidhtc.sourceforge.net in the donations section... I'm not asking for it, but certainly won't object :)

I still have some issues to work out with the RIL, like the missing callerID name/picture, the 3G indicator, I haven't tested the commands to check available minutes, and AGPS is high on the list too (network location)
[Touch Cruise Android Development] SuperJMN:
10$ for your work! And for your great personality. Confimation: 0T319953C4863530V

By the way, I noticed that the system is a bit laggy and unresponsive when I renamed the "conf" folder. I think it uses a default configuration file when no specific config file is found. Can somebody do some benchmarks or tests to determine what parameters are the best for our devices? :)

Thanks a lot!
[Touch Cruise Android Development] SuperJMN:
Ext2 booting is a method that uses both haret and your SD card.

The most basic and oldest boot method is to use .img files that contain whole file systems into it. They are mounted during boot and treated like native partitions, but this has cost in terms of efficiency.

A better method is to partition your SD card into 3 partitions (widely common).

- The first has to be formatted with FAT32 in order to be recognized by Windows systems.

- The 2nd and the 3rd have to be Ext2 partitions about 200 MB in size.

Then, if you press VolDown when Android is booting (you will be prompted to do it), the installer will guide you through the steps to install the whole Android system images into real partitions. You've got to use a recent rootfs.img in order to do this.

When you have this done, you will notice that theres no system.img/.sqsh in the root of your FAT32 card, but your system will boot up since the contents are mirrored into the Ext2 partitions and it no longer needs to mount images, but real and native file systems.

The main advantage is that this improves performance :)

I'm not very good with English, but I hope you understand my explanation.
[Touch Cruise Android Development] imfloflo:
Thanks for your helpful message SuperJMN. I hadn't try this new method yet. Is the performance really differente ?

Should i have the partition before or just follow the guide?
[Touch Cruise Android Development] SuperJMN:
I'm glad you saw it helpful :)!

- I feel the system a little more responsive and less overloaded. But I didn't make any other tests, actually.

- Yes, I think it's necessary to have pre-existent partitions. I partitioned my SD card using Ubuntu. I think there are tools for Windows that will work OK, but I don't remember any free tool. Acronis Disk Director and Paragon Partition Manager are very good ones.

Hey, I was to Toulouse and it is GREAT!! My girlfriend and I were in the Ibis hotel near the train station. I'll recommend everyone to go there :D It's charming!
[Touch Cruise Android Development] mylostnick:
First of all thank u JMN for this lil tutorial!

It seems to be such an interesting thing!!!

Trying to do this I got an error... Here is my configuration:

I've a 1Gb test SD card in which I try the android builds.

Under a Mandriva Linux System I've partitioned it in three partitions:

- the first of about 500Mb formatted in FAT32

- the second of about 200Mb formatted in ext2

- the thirt of about 250Mb formatted in ext2

When I run Haret and push the volDown key I see the boot procedure but, after the creation of data.img file in the FAT32 partition I got an error in which it says can't find the system/ partition sayng perhaps partition has 0 length... I don't understand what's the matter... can u help me? I use the latest rootfs from the sourceforge space. It's correct or I've to use another one?

Your english seems to be better than mine!