yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] SuperJMN:
Oh dear! Maybe it would solve all of our problems ;) Nexus One, ahhhh :eek:

Paris... ahhh :) I've been to Paris only one time, and I'm definitely going again.
[Touch Cruise Android Development] raist1976:
have .... to ..... resist ..... :)

I still don't understand why I have this problem of beiing able to call only once...

maybe the new nbh ? will try the old one tonight...
[Touch Cruise Android Development] osilvan:
I've experienced this problem in every build i've tested
[Touch Cruise Android Development] raist1976:
I guess it's time to say bye bye to android until this get fixed... I need a phone that can phone ... will put back wmo until I get a nexus

too bad :(
[Touch Cruise Android Development] dzo:
This has nothing to do with phone audio, it's just audio input for things like voice search that don't work. It used to work but I've obviously made some changes and broken it. When I have some time I'll look into fixing it.
[Touch Cruise Android Development] raist1976:
Well yes indeed it's the audio part ... but still it's hard to phone without audio :D

Maybe a problem with audio buffer not beeing closed properly ? I remember having such problems looong ago when I was programming some stuff ... (on amiga) :)

For now I'm still trying to find an android configuration that will get me audio on phone calls more that once... and I start to wonder if it ever worked ...:confused:

Thanks for your involvement anyway. If I could help I would gladly :)
[Touch Cruise Android Development] osilvan:
Thanks dzo, if you need someone to test it, don't bother to ask me, I can provide logs or whatever you need.
[Touch Cruise Android Development] osilvan:
As dzo said before, I've never had problems with audio in-call. they only appear with audio input in some apps (Shazam, Audio Recording, Voice Search, ...)

Which build are you using?
[Touch Cruise Android Development] raist1976:
I just tried again with haret install dated 2010-02-14, nbh 320x480 from sourceforge, same date, and with myn's warm donut of 2002-02-02 ... after first call (my answering machine for example), the phone is mute ! no sound anywhere.

So I guess this was either a problem since the begining and the WOW effect of android made me more using applications than the phone "call" function....

OR something got broken in my phone :p

Anyway, we'll see. I'm trying a winmo 6.5 (last winmo I had was 6.1) and I'll see if the sound it better or not...

I don't know if I'll try again any build before buying a real android phone ...
[Touch Cruise Android Development] iseeka:
i have no problems with sound
[Touch Cruise Android Development] Polarfuchs:
Perhaps, you should compare which radio rom version you use.
[Touch Cruise Android Development] raist1976:
That was my fear in fact and I realized it was my radio when the prcharvelo extreme 6.5 just gave me the same effect (no sound after first call is ended).

I've updated to 1.59.44.02 and sound it ok on winmo 6.5.

Going back to kaiserDroid with nbh & haret install from 2010-02-20 and will update this post in a few minute with results :)

BTW, my rom was 1.70 olinex ... but couldn't see that as it's not showed anywhere when we boot android :p (not like winmo)

CONFIRMED !!! MY PROBLEM IS GONE ... DAMNED RADIO !

TAKE radio 1.59.44.02 it'll fix your problem of no sound after first call !

http://xdaforums.com/showthread.php?t=453190
[Touch Cruise Android Development] Polarfuchs:
I could have told that to you. I use radio rom 1.59.44.02 since win mobile 6.1

But I just got the android running and didn't make a call since then. :D
[Touch Cruise Android Development] SuperJMN:
:) Good to know! But I think that it won't fix the audio input in applications. Am I wrong?
[Touch Cruise Android Development] raist1976:
I think I might have got this incompatible radio when I reinstalled the HARD-SPL before testing android one month ago...

I'll test the other audio functions but of course it won't fix the other problem as I now have same radio...

However, this whole story my be the start of an hint to get a fix ? Maybe it's something related to the radio we use...
[Touch Cruise Android Development] Polarfuchs:
With my Rom 1.59.44.02 and 2.1 eclair on sd card I can here sound when I start a game.

I will test a little more, play some mp3. And then I let you know.

I think Audio works fine with my radio rom.
[Touch Cruise Android Development] Kiiv:
I think the problem is with audio input, not output ;)
[Touch Cruise Android Development] Polarfuchs:
Ah ok, I overlooked that. :o
[Touch Cruise Android Development] raist1976:
Oh boy...

now back with donut, to get back to better speed until Warm works out a fast eclair (if ever possible), my phone shut down because of battery.

Now I'm getting infinite loop message : "android_power: wakeup (0->0)" ....

Is there a way to fix that beside reinstalling everything ?

I tried removing the battery for 5/10 minutes... didn't help.

What does this message actually means ?????

Edit : "Clear Dalvik cache" did the trick... dohhh. Better than nothing.... but I think I really have to be carefull not let the phone die :(
[Touch Cruise Android Development] Arkish:
Just had the same problem, "Clear Dalvik cache" did not fix it for me - ended up doing a full re-install.:rolleyes:
[Touch Cruise Android Development] SuperJMN:
These days I have seen development for Vogue and for Kaiser, but no progress for Polaris. Any news about new kernels? new files?
[Touch Cruise Android Development] reiteravi:
poly's new one works fine on polaris
[Touch Cruise Android Development] SuperJMN:
Faster and snappier? I tried it a week ago and it was frustrating :S
[Touch Cruise Android Development] iseeka:
much faster ... very close to donut now

still no camera
[Touch Cruise Android Development] Polarfuchs:
Hi,

now I try it here.

I posted already in the polyrythmic thread but I can't get help there, it could be a polaris specific problem they say.

First I installed 2.1g with zImage-eclair on a 2 partition ext2 SD Card but I get "msm_i2c:error waiting for notbusy".

Then they said I should try it with only one fat32 partition. I did that but same error. Then they said I should try it with an older kernel. I tried the zImage (non eclair) from 20.02.2010 but still the same error.

Can you help me here in the Polaris thread?
[Touch Cruise Android Development] iseeka:
... still no new polaimg... hope we get improvements soon
[Touch Cruise Android Development] reiteravi:
try dzo's zImage-04-03-10
[Touch Cruise Android Development] Polarfuchs:
was that comment for me? Is dzo's runnable on a SD card too?
[Touch Cruise Android Development] reiteravi:
zimage is just for sdcard
[Touch Cruise Android Development] Polarfuchs:
Where can I find dzo's image?

I search this whole thread and the polaris rom dev. forum but found nothing.
[Touch Cruise Android Development] iseeka:
i guess http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
[Touch Cruise Android Development] reiteravi:
i meant this one though never tried myself as i used nand
[Touch Cruise Android Development] Polarfuchs:
Great with this one it immediately started and I could acces the installer. No msm-i2c error any more.
[Touch Cruise Android Development] maroe007:
i'm new

hello i'm new a little new with this android and i don't understand what i should do.i hav (somehow) manged to install instal android (1.5) on my polaris but the wifi isn't working can someone show my were to download the files and install android with wifi and gps

question2: is there android 2.0 for the polaris

thanks
[Touch Cruise Android Development] Polarfuchs:
There you can get Android 2.1 (g) http://xdaforums.com/showthread.php?t=600154

Wifi is a known problem. And that could be a fix http://xdaforums.com/showpost.php?p=5670646&postcount=1557
[Touch Cruise Android Development] maroe007:
.img file ??

oke thanks for the fast reply;)

i tried to download it (haretinstall.zip) but it hasn't rootfs.img and i think thats the most impotant file

in the readme it also says Put the androidinstall.tar of the build you want to run in /sdcard/andboot but i don't have androidinstall.tar :( (search doesn't help me either)

thanks
[Touch Cruise Android Development] Polarfuchs:
You need this file (haretinstall.zip) http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download

There you have the andboot folder.

And then you need to edit the default.txt to fit your paneltype and edit the "set Kernel zImage" to "set Kernel zImage-eclair"

And then you need the android it self:

light skin: http://www.ponack.net/poly/2.1g/polymod_2.1g.zip

or darker skin: http://www.ponack.net/poly/2.1g/polymod_2.1g-dark.zip
[Touch Cruise Android Development] raist1976:
Had to full reinstall just now after my polaris battery dying in the middle of playing a game....

Letting android autoshutdown seems to often mess the system :( (this time I was back on myn's warm donut)
[Touch Cruise Android Development] ReMix3D:
Hello everyone,

I'm having troubles with making android work on my polaris, I think I have correctly placed the files on my SD card : andboot folder with the files from the haret zip, the good default.txt that loads up zimage-eclair and the androidinstall just linked before.

Well, when I tried to launch android, my phone freeze for some seconds and then just crashes with a messed up screen (look like a multicolor gaussian noise ...)

I already had android working a while ago, with haret and an other method (haret on the root af the sd card, and many more file, don't ask the names, i don't remember), and it almost booted one time but ended on "Failed to reach system.img on SD Card", and since, I can not boot on android, always the same exploded screen.

I deleted and re-copied the files, but it hasn't resolved anything.

Thanks.
[Touch Cruise Android Development] scramiro:
polymid or myn

Hi,

I've used both polymid (kaiser) and (myn) from vogue. What do you think is better and why?

From my experience, polymid is slowlier than myn (guess because eclari needs more ram than donut form myn). In the other hand, phone responsive in myn is slow... Anyway, i use myn's.

What you thing?
[Touch Cruise Android Development] niabi:
I am having the EXACT same problem i tried all of the panels, and panel 1 gives this strange screen (colored noise like...) panel 2 colored noise screen short after blank screen, panel 3 same as 2

any ideas ??

Thanks!
[Touch Cruise Android Development] paipo:
Problem in board-htcpolaris.c

Hi all,

I never got to boot my Polaris 100 with the latest kernels. I allways got the msm_i2c notbusy error. I also noticed that my touchscreen stop responding, but buttons kept working.

So I decided to dig into the kernel code to see if I managed to identify the source of the problem. And I found the problem lies in the instructions to do the double vibration at boot.

In board-htcpolaris.c lines 815-820 we have this:

for (i=0; i<2; i++) {
while(msm_proc_comm(0x4,0,0xb22)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(0x5,0,0xb22)==-EAGAIN);
mdelay(75);
}

They vibrate the device two times, but also mess with touchscreen detection. With them I have the error. I removed them, compiled the kernel and managed to boot my polaris properly.

Does anyone have an idea how to work around this?

Could some kernel maintainer check this?

Thanks in advance
[Touch Cruise Android Development] Polarfuchs:
@paipo that is some great news. Because I have this problem too, at least when running Haret method.

So there is a work around. Now some one needs to do a fix as you said. I'n not good at programming stuff at all.
[Touch Cruise Android Development] paipo:
This is the kernel I built. I made a git pull from the main repository and commented those lines. Can you test it?
[Touch Cruise Android Development] Polarfuchs:
I will but not today, now I go to bed. ;)
[Touch Cruise Android Development] Polarfuchs:
I tried it and the two vibrations don't appear and yes it works instantly.

So you got a fix.
[Touch Cruise Android Development] reiteravi:
i second that - important fix

prevents many from giving up endless boot trials
[Touch Cruise Android Development] radem205:
Rogro82: I was wondering if it is possible to make phone calls (without audio, I know) with your new build, including the new commits from DZO?
[Touch Cruise Android Development] bally3:
hey Rogro, is the radio working with this version?
[Touch Cruise Android Development] rogro82:
Just got home from work but im on it :)

Edit:

Somehow my vmware Ubuntu died so Ill have to revert to an old snapshot.... will take me a bit more time to get things up and running again :(
[Touch Cruise Android Development] meknb:
I've been following this thread for a while waiting for a working radio.I finally took the plunge this morning and give it a go.Then i tried to flash the NIKI-radio from my security unlocked polaris (says security unlocked on the top of spl screen) error.Is my polaris security unlocked? AT@SIMLOCK?AA tells me my polaris is still locked @secu_flag:1 0 and mtty rtask a setinfo tells me SECU_FLAG=1 im wondering if this is stoping me flashing the NIKI-radio?
[Touch Cruise Android Development] dubbeld00:
Ehm why would you flash to the NIKI radio... DZO has fixed the SDcard driver to work on all radio's, as far as he could test... rogro is creating a ROM with the current progress DZO made.
[Touch Cruise Android Development] radem205:
Does Rogro create a full ROM or a new zimage?

BTW: Somebody in the kaiser thread have made a call with full audio (http://xdaforums.com/showpost.php?p=3182496&postcount=2009). Your guys doing a awesome job together!!
[Touch Cruise Android Development] dubbeld00:
SMD was already working on kaiser and polaris, but I agree that they are doing an awesome job making the SDcard working (due to DZO). And no, we aren't making real roms (yet) of Android, think we are stuck to booting using Haret, but I don't mind doing that... But I'm waiting for Rogro now for his zImage :) (good luck with that btw Rogro!)
[Touch Cruise Android Development] bally3:
Sure wish we could have a zimage to try this, I assume we would also need to change the MTYPE and set the phone settngs. I'm on 3 network in the UK which I havent found any settings for so far unfortunately, Lets hope Rogro is able to get back up to speed with his Ubuntu or we're in for a wait. Wonder what happened to Dwaradzyne?

Dubbeld00 you're able to make zimages arent you?
[Touch Cruise Android Development] radem205:
I know that the smd code was working on the kaiser (thanks to DZO), but I thought DZO said that the audio isn't working with his latest commit(s).

For now Android is working like a charm (10.000 x better than Windows Mobile), but it would be very nice when we can make calls :)
[Touch Cruise Android Development] rogro82:
The audio in android to play music etc doesnt work but for making calls it does....

Oh wait ill upload a new image so you can see for your self :D

I didnt have much time and needed to fix my pc so its a dirty hack to make things work on the Polaris, but i can confirm i can browse and use google maps and make calls... So its a start.

If i find some more time today ill try to create a clean build but for now this will do...
[Touch Cruise Android Development] rogro82:
Use included zImage combined with the latest files from DZO

http://it029000.massey.ac.nz/vogue/android-16-01-09.zip

Make sure you have an active data connection in WinMo and run Togga in Android to connect
[Touch Cruise Android Development] makboy:
I all, i can't install android on my polaris.

I have:

-android-16-01-09 files whit zImage for polaris, but haret search other file on my sd and dont install it.
[Touch Cruise Android Development] radem205:
It is true that this is not working. You have to edit the default-kaiser.txt and remove the /storage card/ at some lines.

@Rogro: With the files you mentioned all elements in Android are messed up (TS, keyboard, etc.). I think extract all the files in android-16-01-09.zip isn't right! Some files made in earlier posts have to be exist in this version (but I don't know exactly which files).
[Touch Cruise Android Development] rogro82:
Did you use the zImage i included? Or did you use the one from dzo?

And dont use the default-kaiser because I still use the vogue machtype for the ts... Just use the default.txt and you will be ok. I fixed all code needed for the smd to work on the vogue mach type for now.
[Touch Cruise Android Development] makboy:
zImage i included.

"failed to find data.img on sd card"
[Touch Cruise Android Development] radem205:
Thank you Rogro (and DZO!); It's working now :). Is it right that the signal strength bar doesn't work?
[Touch Cruise Android Development] rogro82:
K... ive created a new zip with the zImage and the default.txt

Copied straight from my sdcard which works.

@radem205:

There are no more files, but does the data.gz extract else you can extract it by hand and rename it to data.img.

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

See you got it to work. Signal strength isnt working because of the RIL that needs to be changed I guess.

Biggest problem i have now is that the power collapse isnt working anymore, while it was before :S
[Touch Cruise Android Development] radem205:
I think the power collapse is an mapping issue, right? Because when I press the power on/off button it will call a number, so it has the wrong reference (or something like that :) ).

When I didn't used the phone for 1 minute the screen will go off and I can't get it on... :S (this has also to do with the power collapse, right?)
[Touch Cruise Android Development] makboy:
sorry, but i put the file in my directory or in my sd card?
[Touch Cruise Android Development] rogro82:
No its not a mapping issue... I just mapped the button to the call button to see if it was a mapping issue :)

Ill remap the button to the normal power menu and try to see if i can make it work normally again...
[Touch Cruise Android Development] paipo:
I've checked around and found that Nike users have the same problem.

I hope some dev (Dzo, Vilord, are you listening?) sees this thread, and remove that code from polaris source.
[Touch Cruise Android Development] iseeka:
maybe we can get a nbh updte... and who knows even with bluetooth lol

i think polaris is getting forgoten
[Touch Cruise Android Development] Polarfuchs:
I posted the problem and fix in the Polyrhythmic polymod 2.1g thread, maybe someone notices it.
[Touch Cruise Android Development] ReMix3D:
Well, I really don't understand all this ...

I added the zImage-polafix posted before, and android started to boot with harret.

It asked to push on up on the d-pad for installation menu (Hey, I don't want to install it, just run and test !), then again, couldn't not find system.img ...

I soft-reseted and restarted harret, jsut to look at this installation menu, and know what ? Just had the messed up screen again :(.

How do you guys manage to make harret run android ? What have I done wrong ?
[Touch Cruise Android Development] Polarfuchs:
Did you edit the default.txt? You have to change the "set KERNEL zImage" to "set KERNEL zImage-polafix". Otherwise Haret takes to "old" zImage without the fix.
[Touch Cruise Android Development] ReMix3D:
Yup, I did it.
[Touch Cruise Android Development] Polarfuchs:
Hm, I can give you my default.txt so you can compare:

#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage-polafix
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 pm.sleep_mode=1 board-htcpolaris.panel_type=1 lcd.density=120 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
boot
[Touch Cruise Android Development] paipo:
These are the steps I took:

Partition your card (FAT32 + ext2 + ext2) - search the forum

Go here and download the 240x320 version under NoMoRootFS Instructions for SDCard

unpack the file into the root of your SD card (FAT32 partition). You should have a folder named andboot

rename default-polaris.txt to default.txt

put zImage-polafix inside /andboot

edit default.txt and change zImage to zImage-polafix

run Haret

I usually use the center dpad key to launch the menu.
[Touch Cruise Android Development] Polarfuchs:
correct, because volume up doesn't work
[Touch Cruise Android Development] niabi:
I too have the messed up screen and no matter what I do I can't make it run :( I have followed directions and formatted my card, used another card, changed every setting on the default.txt and I can't get pass that screen :(
[Touch Cruise Android Development] dzo:
I haven't forgotten you, I'm working on Bluetooth now.
[Touch Cruise Android Development] SuperJMN:
Hi DZO! I tested the latest files on my Polaris and BT isn't working for me.

I used these files (NAND boot. Data and System on NAND):

http://ponack.net/poly/BT_Update/polymod_2.1g-BT_Update.zip

http://ponack.net/poly/BT_Update/Po...IR-POLAIMG-PANEL1-320-03-13-10-22-14(CET).NBH

All over polyrhythmic's 2.1g. It tried to start it, but the checkbox remains unmarked.

Thanks for you hard work!
[Touch Cruise Android Development] iseeka:
Same here

i think the update is just the fix for some polaris users with panels....or something like that

no bluettoh here

BUT JUST KNOWING STILL WORKING IN OUR DEVICES DESERVE A

THANK YOU!!
[Touch Cruise Android Development] kulen:
I agree

Thank you all that contribute in Android development for Polaris (and other devices)

Can somebody tell me what is status with battery life on Polaris?

I remember there were some great improvements with vogue battery. Was something like that done for Polaris too?
[Touch Cruise Android Development] paipo:
Do you have a folder with a name started with Inbox?

I found that WinMo always created that folder when I boot with the card inserted. And haret crashed with the funky screen. Is so, just remove that folder and run haret.
[Touch Cruise Android Development] Polarfuchs:
Do you have

initrd.gz

haret.exe

zImage

default.txt

in root folder?

So far as I know it hast to be also in /andboot.
[Touch Cruise Android Development] niabi:
no, I only have them inside nandboot, nothing on root, let me try puting them in the root and in nandboot...

edit: no, same thing :(
[Touch Cruise Android Development] niabi:
is it safe to assume that since the only panel that gives me a bootlog.txt is number 2 this is the panel for my device? or does it have anything to do ?

I tried again flashing on NAND and the this is the bootlog I get... any ideas?

** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 1276 KB for FAT
Attempting to allocate 1276 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
5 files, 1214992 free (303748 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argument
[Touch Cruise Android Development] iseeka:
.........................................................