yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] eza:
as this is my first post, i'd like to begin by thanking dzo for his sterling work on the kernel for android on polaris.

i too am experiencing the white screen with the latest panel 3 polaimg.nbh files (march 31st and 29th)

i also experienced the no audio issues that were reported by others in this thread with other polaimg.nbh files released in march, and am currently running with one from february

(my setup: polaris 200 (o2 xda) with mssmison's eclair v7 (upgraded from an earlier eclair build of his without wiping the data.img)
[Touch Cruise Android Development] st_voss:
I can confirm that your zImage-20100328-polafix works nicely with

Poly's build. It's the only recent kernel I know that works with the wlan.ko from

Poly's build and your androidupdate_wifi110.zip.

I am following dzo's kernel tree and can compile zImages from that repo.

However my self compiled kernels don't work with the wlan.ko from Poly's build

resp your androidupdate_wifi110.zip. Self compiled wlan.ko modules don't

make Wifi work with newer kernels either.

Paipo, did you do anything special to make your kernel work with the "standard" wlan.ko? What gcc are you using for your kernel build? Sourcery G++ Lite? The prebuilt gcc from the openeclair repo?

Regards,

Stefan
[Touch Cruise Android Development] meknb:
Have a look at your dmesg after loading your wifi and see what errors are stopping wlan.ko.
[Touch Cruise Android Development] st_voss:
I have already tried but so far couldn't identify a dmesg entry that would

show why wifi would not load. I also tried the steps

insmod wlan.ko

/etc/wifi/loadit

wpa_supplicant (with parameters like in sysinit.rc)

dhcpdc (with parameters like in sysinit.rc)

from the cli as root. Insmod and loadit worked ok but Android frooze

at the wpa_supplicant call. When using the GUI to start wifi Android

is not calling wpa_supplicant as root but as a different user. I have

figured out how to do this from the cli. With a normal Linux I would try

su <user> -c "wpa_supplicant (with parameters like in sysinit.rc)"

but Android's su command does not seem to know the -c option.

Does anybody know how to run a command from the cli as a different user?

Regards
[Touch Cruise Android Development] meknb:
Not all shells can use the -c "command" switch maybe you can login as as the user and run the command?

So the wifi module is loading ok just check "lsmod" the problem seems to be with wpa_supplicant,sorry cant do any testing till sat havent got my polaris with me.
[Touch Cruise Android Development] monderald:
Greetings! Whether I will be made support USSD of inquiries? In that on the Russian operators it gives out not clear symbols.
[Touch Cruise Android Development] GriloVirante:
I had the same, then I resolved, either by using an "old" kernel, or by usng Paipo's revision of the zImage, you can fin it here.
[Touch Cruise Android Development] aitsch:
thx. at the moment i use exactly these kernel, but i cannot charge my phone battery in Android and sometimes i loose the phone signal (after the phone wakes up).

Question to all Pola200 users:

what is the best kernel for the moment with:

- stable phone support (in-/outgoing calls, sms, ...)

- working wifi and 3G (BT doesn't work - i know)

- charging battery

- stable enough for dayly work?

at the moment i am a littlebit frustrated :o

aitsch
[Touch Cruise Android Development] SuperJMN:
@polyrhythmic has released a new version of his Polymod: http://xdaforums.com/showthread.php?t=600154

Has anyone got it to work?

What method? HaRET or NAND?

By the way, any progress in wifi, BT, audio input, and data connection reestablishment?
[Touch Cruise Android Development] DmK75:
I installed this on SDCard.

First i tested WiFi but it not working with any kernels.
[Touch Cruise Android Development] solvga:
I just tried it with Haret, fat32/ext2/ext2, using paipo's zImage.

Wifi could be enabled but still unable to scan.

Is there any way to enable wifi in mssmison's eclair? Coz It's still smoother than Poly's.
[Touch Cruise Android Development] paipo:
Hi Stefan,

The only changes I did were those I told dzo. As for my build environment, I use gcc 4.4.1 on Linux Mint 8 (Ubuntu 4.4.1-4ubuntu9). To build the kernel I followed these exact instructions...

I've been away for awhile, I'll try to catch up next weekend.

cheers
[Touch Cruise Android Development] st_voss:
I was able to install Poly's 2.1d release (haret install with two ext2 partions)

on my Pola200 using Paipo's kernel. To use wifi you have to exchange /system

/etc/wifi/wlan.ko with the older wlan.ko from Poly's 2.1g release. This is

probably also needed with mssmison's V8 eclair build.

Overall I'd say 2.1d feels a little slower than 2.1g. Cannot say much about

BT cause I'm not using it regularly.

regards
[Touch Cruise Android Development] st_voss:
The only difference that I could spot was that you're using the 2008q3

release of codesourcery's cross toolchain. I was using the 2009q1 release

but my kernels wouldn't work with the wlan.ko either way.

regards
[Touch Cruise Android Development] DmK75:
Update to enable WiFi for mssmison's eclair v8.

Only for old or paipo zImage.
[Touch Cruise Android Development] solvga:
It works. Wifi functions well.

I use paipo's zImage.

Thank you. :)
[Touch Cruise Android Development] osilvan:
Does bt work with this update?
[Touch Cruise Android Development] eza:
hi, i can confirm that the latest polaris panel 3 nbh (08 april 2010) does not work on my polaris 200. no white screen this time - it just hangs on the power-on screen. i've reverted back to an earlier version.

i'm going to have a look for information on how to build my own linux kernel nbh from source and see if i can get anywhere with it.
[Touch Cruise Android Development] Badgerfan:
Hi Eza,

I've got the Polaris 200 and the same issue as you with the 8th April NBH. Also had some issues with the screen whiting out when booting with previous NBHs. I'm currently on 20th Feb NBH. Let me know if you find a fix - good luck!
[Touch Cruise Android Development] aitsch:
i found a workaround for battery charging problem with paipos kernel (zImage-20100328-polafix.zip).

charging is possible after have connected my phone to power supply or USB cable at boot time.

but sometime it doesn't notice when it is disconnected.

phone signal makes still problems

aitsch
[Touch Cruise Android Development] aitsch:
follow this link
[Touch Cruise Android Development] SuperJMN:
We all are looking for a .NBH that has all the latest changes and Wifi working :( Is that so difficult?

I'm staying in WM 6.5 for some weeks due to a not working Wifi. DZO didn't reply my last message. Help!
[Touch Cruise Android Development] osilvan:
Don't worry, dzo is on holidays and I'm sure he will continue the work when he returns.

The most important problem in polaris development is that we don't have devs that could help dzo in specific issues or try to adapt builds to our needs.

I've been following this forum for two years and I've seen a lot of progress thanks to dzo work, but I think that now is time to help him. A few months ago I set up a building environment and build a kernel successfully, but it's all: I don't know almost anything about the internal architecture and don't have experience in this field.

Maybe I could provide logs and haret memory/gpio dump. What could we do to help?

Regards
[Touch Cruise Android Development] kulen:
Maybe we should find some developer that is willing to help us and has time to do that, and buy him/her a Polaris.

We already bought them to DZO and Vilord. and they did (are doing) a great job. and thank them for that.

but they have private life and some other interests and they can't do it alone. and job they do (with some help - don't want to be ungrateful to anyone) is just great. they did what whole teams, full work time, do in companies.

So, perhaps they need some help.

I'm willing to donate 5 EUR if somebody is willing to organize the whole thing (find developer and buy him a Polaris).
[Touch Cruise Android Development] aitsch:
i already spend 20 $ for one of these 2 Polaris and it was worth it.

I would also spend again money for a new developer device but i think the main problem is to find an adequate person with desire, knowledge and time to do all these open things.

at ebay (germany) a used polaris is between 80 - 110 euro + shipping.

depends on how much the single donator will spend we need round about 20 - 25 persons (á 5 €). but who could be our dev?

aitsch
[Touch Cruise Android Development] w04g005:
I think i will buy a desire at the end of this month....if i keep the desire, i have to ask if somebody in my family wants (needs) my polaris, and if not i will donate my polaris to the xda dev community!

i will inform you as far as i know a little bit more!

greetings
[Touch Cruise Android Development] ReMix3D:
Hello again everybody,

I recently retried to install Android (polymod 2.1g), but I really can't manage to get it work.

I created an ANDBOOT folder on the root of my SD card with all needed (haret files and android installation files). I created 3 partitions on the SD card, one 6 GB fat32 and two 2 GB ext2.

I run haret on WinMo, the phone reboots, I press the center button an get the installation menu. I Select the two options for installation on ext2 and launch the installation. It look ok. The I quit, but the process seems freezed. Here is what I got on screen :

sh: 2: unknown operand
e2fsck: 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
e2fsck: while trying to open /dev/block/loop1

The superblock could not be read or does not describe a correct ext2 filesystem. If ther device is valid ans it really contains an ext2 filesystren (and not swap of ufs or something else), then the superblock is corrupt, and you might try running e2fsck with and alternate superblock: e2fsck -b 8192 <device>

e2fsck:
mount: mounting /dev/block/loop1 on /system failed: Invalid argument
Failed
Failed to mount /system

(crap, had to retype all this, why not copy paste ?)

Must I have to run the described command on my ubuntu ? I'm not a very high user of linux, I created all my partitions with GParted, I'm not so friedly with the terminal.
[Touch Cruise Android Development] ReMix3D:
Nobody is comming here anymore ?

Please, help me get the droid to work on my polaris :(
[Touch Cruise Android Development] DmK75:
You correct selected in menu install paths for partitions?

(*) Sys on SDCard Partition

(*) Data on SDCard Partition
[Touch Cruise Android Development] ReMix3D:
As I said before, I selected :

(*) Sys on Ext2 Partition

(*) Data on Ext2 Partition

It should work, no ? Cause a have two Ext2 partitions on the SD Card.

I used THIS tutorial.

Or should I better create only one big Fat32 partition ? Or multiple Fat32 ?
[Touch Cruise Android Development] DmK75:
I also used this tutorial.

If EXT2 partitions created and recognized, installer automatically select options for this:

(*) Sys on SDCard partition

(*) Data on SDCard partition

For install to standard non-partitioned SDCard (FAT32):

(*) Sys on EXT2 system.img

(*) Data on EXT2 data.img
[Touch Cruise Android Development] ReMix3D:
Yippee, I just got it to work !

I try to make short :

1rst : sometime when I create a new partition on the SD card and plot the card in the phone, WM wants to format it, I simply click ok, but it also re-partition my card with one extended full size partition, and one logical Fat32 partition.

What I understood is that I must not name the partitions I create, so I just created : 6GB Fat32, 1GB Ext2 and 1GB Ext2.

2nd : I run harret, and everything seems ok, but when I hit installation (with the configuration you just told me), the texts scrolls fast, but I could read : "could not find AndroidInstall.tar".

I look at my "andboot" folder, and gess what, there is an AndroidInstall.TGZ.

Ok, just go in ubuntu, open the file, save as tar ...

Run haret, install ... quit ... Hey IT WORKS !

Well, almost, android is running, as expected I don't have camera, but mi surprise is : I can not install applications from the android market ?

I got an error saying that I don't have enough memory ... WTF, in the memory parameters it says 4,5 GB free on SD and 0,9 GB free in memory ...

Any idea ? :D

Anyway, thanks DmK for your help :)
[Touch Cruise Android Development] ReMix3D:
Well, there's a time since i've poste this, but no response.

I have an other problem with my android, I don't have sound when calling, no very usefull for a phone.

I searched on the forum, but can't find again the solution for this.

Can a good soul help me again (and for the app installation :D) ?

Thanks
[Touch Cruise Android Development] raist1976:
Use the nbh from sourceforge... if you're like me, no dzo nbh are working atm :(
[Touch Cruise Android Development] SuperJMN:
DZO released today a new .NBH. I think it fixes the no caller sound problem.

I tested it this morning and it doesn't have wifi, but with the androidupdate.tar by paipo, BT is working.

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

That's the website where you can download the available versions of it, as usual. I notified DZO that wifi is not working yet.
[Touch Cruise Android Development] chourmovs:
do you have data connection with 3g?

i can't have it working with kast dzo kernel
[Touch Cruise Android Development] SuperJMN:
Yes, I do. I'm using Myn's Warm Donut Release 5. The APN came preconfigured.
[Touch Cruise Android Development] l1q1d:
@SuperJMN: could you please prepare a step by step guide?
[Touch Cruise Android Development] SuperJMN:
Of course I can do it. This is a brief step by step guide:

1º Create a folder into your SD Card (FAT32 partition) called andboot.

2º Put into it the Myn's Warm Donut R5 file called androidinstall.tar.

3º Flash the newly released .NBH by DZO with the appropriate display type*

4º When you device is booting, press D-pad center when prompted and don't release it until the installer appears.

5º Choose install to NAND both.

6º Choose install system.

7º Soft reset when it finishes installing (the menu will appear again).

8º Let it start and your fully-fledged build will pop up after some minutes.

* it's recommended that you clear the flash ROM after this step to avoid problems. You can do it using a hacked flashing tool available for download in this thread: http://xdaforums.com/showthread.php?t=666033, more especifically in post #3. You have to put a dummy .nbh file (a radio .nbh or a NAND boot .nbh) to make it work.
[Touch Cruise Android Development] manu33xtro:
Very good. Thanks.

Do you use the very latest of kernel : 070510 ??

I test now the incubus build (RLS4) with zImage and it works very good but no wifi : Incubus works a lot for us (I hope he can make a version who work for Polaris user's) :)

Cheers.
[Touch Cruise Android Development] SuperJMN:
Not at all! My pleasure.

Yes, I use the latest version. I applied the update for wifi+BT, but only BT is working at the moment for me (Myn's Warm Donut). I didn't try Incubus' build yet. Is it working as fast as Myn's?
[Touch Cruise Android Development] manu33xtro:
Hi SuperJMN,

I don't know if incubus build working faster, I think yeah but it's only my sensation...

I prefer the Eclair version (skin, toolbar, manage of contacts : you can import from vcard file :), live wallpapers and many other things...) ;)

Cheers.
[Touch Cruise Android Development] dzo:
For working wifi you just need to recompile the driver for polaris, the kaiser driver won't work since the gpio is different. Search through this thread and you should find details.
[Touch Cruise Android Development] SuperJMN:
I will try to find out how, but I think it will take me long time. I never compiled a driver, nor I am very good using Linux :( If you give me some brief instructions, I'll do my best to get it working.
[Touch Cruise Android Development] Badgerfan:
Hi guys,

Bit of an issue after flashing the latest ROM (polaimg-panel3-320-07-05-10.nbh). My touch screen has basically stopped working. All the pyscial buttons seem to work OK, but the touch screen is out of action. It also seems to have had the effect of stopping me getting into bootloader moder to reflash!

I actually had a similar problem to this with a WinMo ROM I flashed a while back, where touch screen died and I couldn't get into the bootloader. I basically stopped using my Polaris but then tried it out of curiosity about 2 months later and managed to get into bootloader and reflash.Touch screen then started working 100% OK, which is why I think it's ROM related. I don't want to wait 2 months this time! Any ideas? :(

Thanks
[Touch Cruise Android Development] meknb:
SuperJMN

After building your kernel

cd ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32

export KERNEL_DIR=$HOME/mydroid/kernel

make

then copy the wlan.ko to your device
[Touch Cruise Android Development] SuperJMN:
Then, I should start learning how to build the kernel :S Any link to do that, please? Thanks!
[Touch Cruise Android Development] vvsprog:
SuperJMN how about battery life in Myn's Warm donut?
[Touch Cruise Android Development] SuperJMN:
It's worse than in WM, but you've got to have into consideration that Android performs faster, and that I have my Polaris overclocked to 504 MHz.

Anyways, it's not bad.
[Touch Cruise Android Development] dzo:
Don't worry, I built one for you, see attached:

Just replace /system/lib/modules/wlan.ko from the kaiser update with the one in this zip.

It works for me.
[Touch Cruise Android Development] SuperJMN:
Woohooo! It works! I feel that my years programming in C/C++, JAVA, VB and C# are useless, but you definitely have talent and an uncommon sense of device programming. Now, we can only hope that things like headset and camera work at last.

Thanks a lot!
[Touch Cruise Android Development] dzo:
The wired headset won't work, I had to disable it to get audio working, camera works for me.
[Touch Cruise Android Development] SuperJMN:
I know :) Camera works for me, too. But it's taking pictures smaller than in Windows Mobile, more blurry, darker and without auto-focus. Don't take me wrong :) I'm not taking picture every now and then. It's OK for now.

I hope to get the wired headset in the short term, because I listen to my podcasts at night with my Polaris.

Thanks again. Wifi is working great with your wlan.ko!
[Touch Cruise Android Development] l1q1d:
I flash to nand! It works great.

This is a new androidupdate with the new wifi kernel module and old bt/wifi fixes. :D
[Touch Cruise Android Development] trouble2000:
Thank You all!!!
[Touch Cruise Android Development] osilvan:
Do you know if our old problems have been solved? I mean audio input, battery drain and not sleeping correctly with wifi turned on.

I want to try last kernel but don't want to flash my device, do you know if there is a 2010-05-07 zimage kernel available?

Thanks to everybody and specially to dzo for not abandon this project
[Touch Cruise Android Development] kulen:
Thanks DZO. you're doing better job than entire HTC company :-)

if we had just one more developer with 1/10 of your knowledge and a little more time to follow your steps it would be great. it would speed up things, for polaris, a bit and it would take some preasure of off you.

thanks for keeping dream of Android on our phones alive!

And thanks all the others that contribute.

and one question. could somebody create this update and post it here?
[Touch Cruise Android Development] meknb:
just go back a couple of posts l1q1d created one.
[Touch Cruise Android Development] kulen:
Thank you.
[Touch Cruise Android Development] kulen:
Can somebody please upload latest zImage. Or point me where I can find one?

There are only .nbh files on DZO's site.

Thank you!
[Touch Cruise Android Development] meknb:
Tryhttp://84.23.71.227/kerneloftheday/ it's updated every hour and it's patched for the nike but should work for the polaris.
[Touch Cruise Android Development] l1q1d:
Any chance to fix button mapping? (i use this nbh) and power button and call off are inverted...
[Touch Cruise Android Development] SuperJMN:
Does somebody know whether DZO is still trying to fix the know problems we have with sound input/output (especially the handset) and if he's working on a .NBH customized for Eclair (I've heard about different .NBHs for Donut and Eclair, and I don't know the different).
[Touch Cruise Android Development] osilvan:
I think we have to help dzo to fix our specific problems. Maybe if we provide him with logs or something else.... I want to help but I need a kernel zImage to test, do you know if someone has built latest kernel?
[Touch Cruise Android Development] dzo:
I did spend some time today looking at polaris and audio works fine for me (except the headset). I was mostly looking at getting some better battery life and I made some changes to the touchscreen that should help. I'll push the changes and make an nbh later tonight after some more testing. The only difference between the eclair and donut nbhs is the hw3d driver but I would stick to donut for now if you just want a stable system.
[Touch Cruise Android Development] osilvan:
Hi dzo

I have collected polaris main problems from SuperJMN post (Myn's RLS5 build) (http://xdaforums.com/showthread.php?t=625200):

Things that DON'T WORK:

USB Storage Mode

USB debugging is unstable.

Tethering

Camera (in Eclair)

Headset

Bugs/Issues:

Sometimes Wi-Fi hangs while is being disabled and prevents the device from suspending correctly (it won't sleep and the screen will turn on every time you press a button).

Data connection goes down from time to time and it won't reconnect until you go to the Modem application, disconnect, connect again and wait it to connect.

Audio Input: faulty and unusable with most of applications that use it, like Shazam.

I haven't experienced all of them, only wifi preventing suspend and audio input.

Could you build also a zImage kernel? Thanks for all your effort and not leaving us
[Touch Cruise Android Development] dzo:
usb storage mode should work under linux, for windows you need to use "dual-sd-widget", read the vogue forum about this, I haven't tried it.

usb debugging works fine on recent kernels.

tethering will work on linux

camera works in donut. even on vogue it doesn't work in eclair.

I'll be able to get the headset working but it's not a priority.

I've put a new nbh and zImage on my site, it probably won't fix most of your problems but might have better battery life.
[Touch Cruise Android Development] SuperJMN:
Hey dzo! the Android Installer (replimenu) is almost unresponsive to the buttons and sometimes it hangs! Like it's consuming a lot of CPU (using your latest .NBH just released paneltype1-240x320.

I managed to reinstall my Myn's Build. I will see if it boots normally. Now testing.
[Touch Cruise Android Development] chourmovs:
:( the same here

no key response in nandboot installer with paneltype1-240x320

how did you managed to reinstall jmn ?
[Touch Cruise Android Development] SuperJMN:
Hi! I crawled around the installer, moving the cursor slowly until it reaches the option. It eventually hung, so I reset the device and entered the installer again until I completed the steps. It's a bit annoying, but I did manage to install it and, yes, it's working.

I first installed the system. Later I applied the update. I had to reset because it didn't move the cursor anymore. And later, I entered it again to "fix permissions".

I hope it works for you until DZO makes a new fixed .NBH.

Thanks again, DZO!
[Touch Cruise Android Development] dzo:
Try today's NBH, it should fix this.
[Touch Cruise Android Development] manu33xtro:
IT WORKS.

Hi DZO,

I use the nbh (18-05-2010) and I upgrade the radio for Polaris to 1.65.30.09 and now it's much better :)

It takes again a little time between when I press the green button and I see the phone call... But now all of the in call are ok. And I don't lose anymore the network ;)

I tested also the GPS (I think you use all the last build of kallt_kaffe) with Igo and it works perfectly...

Thanks, thanks and again thanks.

Cheers.
[Touch Cruise Android Development] iseeka:
Trying nbh(19-05-2010).. everythnig ok for the moment

thanks DZO

Should i go for 1.65.30.09 or should I stay 1.59.44.02??

.

.