yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] dzo:
Looks like the recent changes I made broke something on polaris, try going back to the previous kernel.
[Touch Cruise Android Development] SuperJMN:
Hi DZO! I was not using the latest (today's), but the previous. With it is which I'm having audio input issues. I'm going to try the latest right now to see what happens.

I will tell you the results.

Edit: Confirmed, the sound input doesn't work with the current kernel + rootfs.
[Touch Cruise Android Development] aitsch:
i'm using

rootfs-23-10-09

zimage-23-10-09

i get only an edge data connection. UMTS (3G) does not work anymore, since the latest 2 or 3 kernel changes.

does anyone has the same issue?

aitsch
[Touch Cruise Android Development] osilvan:
I've tested almost every kernel posted and I've never got fully working audio input. :(
[Touch Cruise Android Development] freddycs:
I'm using the latest zimage and rootfs, i have no problem with the sound input. i manage to record sound and attach in mms.

i'm using Donut from Google ION, camera and wifi is working too. The image quality is better compared to the previous version.

I'm getting 3G connection also. one thing i notice, if you disable 3G in WM and only use GSM (EDGE and GPRS only), then in Android will only connected at EDGE only.
[Touch Cruise Android Development] SuperJMN:
I was using Android ION (1.5), but I'm now downloading the system image you linked to see what happens. I will report the results later :)

EDIT: I installed Donut and it runs as slow as hell! Is that lower in performance?

* Wifi working, for the moment.

* Shazam tagging only works the first time. Later it "listens" forever.

* 3G connection failed: the modem application says starting pppd, but after a while, it says connection failed and retries indefinitely.
[Touch Cruise Android Development] Mormy:
Just try it with the latest zimage and rootfs.

I saw the bar in 3G icon, but no connection at all. If I start modem, I saw it blocked.

I also have strange resolution. Which resolution do you use?? And which initrd??
[Touch Cruise Android Development] freddycs:
Please try to use the initrd from the latest basefiles. my resolution is 320X480.

I think we should continue the discussion at All you wanted to know about Android on Polaris and never dared to ask , as this thread is for kernal developement discussion only.
[Touch Cruise Android Development] aitsch:
i think it would not be bad to make clear what are kernel issues and what depends on rootfs or system image.

maybe bally can store this information an the first page.

also i would like to know which system.img is the best for testing. so if someone have problems, he can try the "master" system image and if the bug is always there then post. I use the approved ion image from "all you want to know....dare to ask" threat but cannot connect with adb and have some other problems. So which built in which version is the best to test? this can discharge this threat.

aitsch
[Touch Cruise Android Development] bbezja1:
with latest ZImage the keyboard doesnt pop up. at all

any ideas or move back to older
[Touch Cruise Android Development] Mormy:
I tried with the base file you suggest, but I haven't got better result.

I can't eve got the 3G icon. With a mix of basefile and the last rootfs and initrd.gz + the system you suggest, I got the 3G icon but no camera, no wifi and no data.

I tried to start modem but it's blocked with the words:"starting pppd..." :(

I don't know what happen in the last month, because some times ago I have data and wifi working :confused:
[Touch Cruise Android Development] thilinakasun:
Hi bally3,

Please let me know, where i can find a Android setup file to install and try in my HTC Polaris.

thnks.
[Touch Cruise Android Development] SuperJMN:
Please, check this out:

http://xdaforums.com/showthread.php?t=558062

This thread is not for help about installing Android, but for anything related to kernel development.
[Touch Cruise Android Development] freddycs:
problem with the kernal dated 24-oct-09

i downloaded the kernal zImage-24-10-09 and found the following problems:

- can't make and receive calls, it just freeze the system

- can't enable wifi

- no data connection

- no network (GSM) connected after wake up from sleep mode (occasionally, not all the time)

hence, i switched back to zimage dated 23-10-09 and everything is back to normal.

cheers!
[Touch Cruise Android Development] aitsch:
sorry, this depends on my provider. they reduce the speed after some download volume.

aitsch
[Touch Cruise Android Development] szsoftware:
usb connectivity

@dzo

Dear Martin,

would it be hard to implement a switch/detection of usb connection to the host without having connected usb cable when starting haret?

Also, when disconnecting usb cable after an adb session was established, one have to start winmo again for reconnecting.

Is USB host feature planned and if yes, which flavours of it?

Thanks a lot for the big progress,

CU Sven
[Touch Cruise Android Development] Michel82:
It is mentioned before, i just didn't had the time to test for myself earlier, but i too find strange and unstable radio behaviour since of the last versions. I have tried the last two zImages and the latest three ion systems (one cupcake and two donuts of which i know the first used to work). I'm unable to get a data connection at all, the data icons appear and disappear constantly, but the modem app doesn't create the connection. Calling doesn't seem to work sometimes, but i'm unable to determine when it does or doesn't work. When booted with usb connected airplane mode is on after boot and cannot be turned off, even if usb is disconnected afterwards. Haven't had time to test GPS yet. Hope this information will be helpful for the kernelgods (dzo and friends).
[Touch Cruise Android Development] SuperJMN:
zenulator said this regarding Polaris/Kaiser and the latest Donut build for Vogue:

Doesn't anyone know whether this is true? It might be related to the kernel. It has been told that older kernels work OK. Can somebody confirm this point?

Thanks.

EDIT: I've tried it with the zImage 23-10-09 -> http://vogue-android.googlecode.com/files/zImage-23-10-09 and it still doesn't work.

The description of this kernel says the following: Kernel (rename to zImage) - fix for audio crash when using the camera. Kaiser/Polaris users try this if your having data problems in donut.

Something if failing here :(
[Touch Cruise Android Development] Michel82:
This would the previous zImage:

http://it029000.massey.ac.nz/vogue/files/zImage-15-10-09

Guess if that would work with donut??
[Touch Cruise Android Development] Kiiv:
I've tried with an older kernel (zImage-26-08-09) and it's the same...
[Touch Cruise Android Development] SuperJMN:
My cellular data connection has to be established with roaming enabled (mine is a "virtual" provider that uses other provider's network). Could it be the problem why some people have problems connecting?

Any of you that are experiencing problems with the data connection are also roaming?

I have tested it lots of times.

default.txt has the required APN info. I created an APN into Android. I started the connection into Windows Mobile 6.5 (and also in 6.1) before starting Android with haret.exe.

@Yes! has been able to connect, but we don't know why, yet.
[Touch Cruise Android Development] Michel82:
@SuperJMN:

I don't have a virtual provider, and am not roaming otherwise. So that shouldn't be the issue. I'm very curious on how you managed to get data working!

It's been really quiet over here lately, are there any other polaris users besides SuperJMN that get data working with the latest files?
[Touch Cruise Android Development] aitsch:
i don't use roaming and i can get data connection.

my wifi connection is very unstable. my polaris is connecting to my accesspoint and show the signal quality on top but the connection is very unsable.

downloads from shop are nearly impossible.

anyone else has these problem?

i will try the last 3 or 4 kernel versions to see if this depends on the kernel changes.

aitsch

pola200, kernel-24-10-09
[Touch Cruise Android Development] SuperJMN:
Michel, I'm sorry, but I'm not getting data connection under Donut, too. I think I expressed myself wrong.

The one that seems that has a work data connection is @Yes!

I hope this will get fixed soon.
[Touch Cruise Android Development] aitsch:
i've downgraded from rootfs-16-10-09.img to rootfs-15-10-09.img and now wifi works better. downloads from shop are possible again now.

aitsch
[Touch Cruise Android Development] iseeka:
is this the end or we still will have more upgrades?
[Touch Cruise Android Development] DonDragon:
i still keep having the problem with my battery, it is empty within 1 day :( are more people having this problem. this is very announy
[Touch Cruise Android Development] whitealien:
in default.txt set pm.sleep_mode=1 to 1
[Touch Cruise Android Development] DonDragon:
its already on 1, i have checked it
[Touch Cruise Android Development] aitsch:
disable wlan connection and background data sync
[Touch Cruise Android Development] pananza:
And if you turn off your phone the batteries will last for over a week :)

The whole point of having a "SmartPhone" IMHO is continous background data sync. Windows Mobile is online with my works place's Exchange server and syncs email, contacs and calendar continous and in real-time. When running WinMo the battery lasts for 2-3 days. In Android I'm lucky to get a single workday.

(sorry for the sarcastic intro).
[Touch Cruise Android Development] aitsch:
maybe disabling wlan (wifi) and enabling background data has also an accepatle battery time. i've never tried out.

fact is, activated wlan kills the battery life time.
[Touch Cruise Android Development] DonDragon:
its nice to know more people have this problem. i don't use wlan much but data sync is always on and i don't like it to turn it off. bacause it takes some time to turn it on again.
[Touch Cruise Android Development] Michel82:
To inform you guys: There may be some light at the end of the tunnel of the dis-functioning data in donut. The people over at the kaiser forum are working on it, and have a clue of what might be wrong in the RIL.
[Touch Cruise Android Development] Kiiv:
Good news! Thanks :)
[Touch Cruise Android Development] Mormy:
I cross my fingers ;)
[Touch Cruise Android Development] vilord:
Michel82, who is working on it?
[Touch Cruise Android Development] Michel82:
There were some posts on 3rd of november here: http://xdaforums.com/showpost.php?p=4871699&postcount=8851 I don't see any more recent posts though. Enatefox was working on it a.o. The guess was that the problem has something to do with the APN name not being passed correctly.

I've also contacted DZO if he could help us out a little bit, but he hasn't got any spare time left at the moment. He does say that he hinted some people about a possible solution, but i don't know who and what that is.

I did some more testing myself and i feel like it has something to do with the way the RIL switches from radio to radio (phone to 3g data to wifi). Everytime i make or try to make a call or switch from wifi to 3g i notice strange behaviour.

I would love to help out here but i haven't got a clue to where to start searching; Enatefox makes some reference to the following file: /lib/donut/libhtcgeneric-ril.so is this where to start?
[Touch Cruise Android Development] vilord:
Yes, need to make changes to the source of that file (which is here: http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/ril;a=summary )

Unfortunately the donut branch (bottom) doesn't have the latest changes that actually make it work to the point it is at in donut... I'm working to get those in ASAP.

The next step for me will be to figure out why the APN is getting lost, then to switch over to internal pppd control.
[Touch Cruise Android Development] vilord:
Okay, found some of pmos' changes to make donut go, checked them into git. I'll have some more time on sunday night or monday to poke at this stuff, heading up to my mom's for the weekend, and no interwebs up there :)
[Touch Cruise Android Development] Michel82:
Great to have you aboard Jesse. Thanks for the link to the GIT, i don't know much about RIL's and stuff but i'll see if i can find something odd.
[Touch Cruise Android Development] z3eed:
How far have you come?

So how much is done?

Do you have a working Android ROM for Touch Cruise?

What functions are up and what functions are still not working?

Where can I and all other intressted people see a list or conclusion of the gathered information on how far you've developed this?

Would love to try out Android on my Cruise!

Can even be a testpilot if you need one?

As long as it can make calls and can sync with exchange.

Thats all I need for my daily needs, if thats is up, I can flash my phone over and over.

Best Regards // Jimi
[Touch Cruise Android Development] Kiiv:
@z3eed : begin here ;)

A lot of work as been already done (thanks again to the devs ;)).

Many things works depending of the build you use.

Cupcake builds works very well (call/wifi/data/camera).

Hero too, but still very slow.

Donut and tatto build has no data connection.
[Touch Cruise Android Development] vilord:
Since you're calling your phone a Cruise, just make sure that it really is a polaris, and not the newer touch cruise '09... that phone is fundamentally different and won't work at all with the stuff here.

Once I find a donut build I can poke at the data connection issues (starting on it tonight), can anyone point me to one? vogue-hero is gone, and that was where it all was...
[Touch Cruise Android Development] Kiiv:
I'm uploading one.
[Touch Cruise Android Development] imfloflo:
@dzo If you read this can you tell us what progress have been done ?

Thnaks
[Touch Cruise Android Development] Kiiv:
http://www.4shared.com/file/149031779/1e82da29/system-donut-102509.html
[Touch Cruise Android Development] DonDragon:
i found a problem with google maps, i don't know if you people already know it. but my location doesn't work like it should be, it only works with gps atm.
[Touch Cruise Android Development] z3eed:
No worries.. Its a Polaris. Flashed my phone several times so Im not a complete n00b ;).

I like to play around with Linux so Android is very intressting.

Not going to lie, Spotify is also a reason.

@kiiv, thanks for your reply...

Well how easy is it to flash back to WM if I cant use the phone-dists?

GPS? anyone tested that on the Android for Polaris out there.
[Touch Cruise Android Development] Kiiv:
You don't need to flash your phone at the moment. You boot Android from winmo. You just have to reboot to come back to winmo.

I didn' tried GPS yet but it should work.
[Touch Cruise Android Development] Michel82:
Does anybody know if there's a compiled version of the latest commit to the donut RIL zImage floating around somewhere? (The one by Pedro on the 6th) http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/ril;a=shortlog;h=refs/heads/donut

Or is there anybody that has a dev system avail to compile this?

Could be this solves the data issues on kaiser and polaris?!
[Touch Cruise Android Development] vilord:
that one is already in the wild, it has the needed changes for donut on vogue, but not polaris yet. Lemme make a few changes in the next hour and see how far I can get...

-Jesse
[Touch Cruise Android Development] vilord:
Okay, found the problem!

The new telephony layer uses a data[2] for the APN, and the old one used data[0].

Once I have my donut dev environment configured, I should be able to test... probably tomorrow evening at the rate my desktop is going...
[Touch Cruise Android Development] Michel82:
Great news!! Can't wait to test the new zImage. How did you find that so quickly? Seriously, i would love to help out with some kernel development, but i guess i have to gain some insight in the code in order to notice that data[0] changed to a data[2]...
[Touch Cruise Android Development] vilord:
this isn't in the kernel / zImage, it is in the RIL... separate code bits :)

The way I noticed it was that I looked at the changes in ril.h on android.git.kernel.org in the hardware/ril areas... still more work to do tho
[Touch Cruise Android Development] Michel82:
Ok, so if i understand it correctly; The ril code in the system should match the ril code in the kernel?
[Touch Cruise Android Development] vilord:
kernel has no ril code, it just opens a pair of serial ports, one for modem control and one for data connections (ppp).

The RIL is what talks to the serial ports, it was written by martin and heavily re-engineered by myself.

The telephony system in android talks to the RIL, and as the RIL specification changes (ril.h is the spec), we need to update our code to match the specification
[Touch Cruise Android Development] Michel82:
Thanks for clarifying that, always thought the RIL was an actual part of the kernel. Pieces are starting to make a puzzle now.

I notice you made some big changes yesterday to make you RIL match the donut specs. Any light at the end of the tunnel yet?
[Touch Cruise Android Development] miazza:
Hello to everybody

I continue to read this very interesting 3D.

I have installed a version of this Android at the beginning of the year but it was not yet mature for a daily use.

In order to have a clear picture of the several progress done in the last months, is there anyone that can update the wiki page that is out of date since July 2009 ?

Below the direct link.

http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux

Thanks

miazza
[Touch Cruise Android Development] vilord:
Made some progress, looks like there'll need to be a couple extra things added to the rootfs, but I'm still working out what that'll be.

Its not crashing, but no data just yet.
[Touch Cruise Android Development] niru1978:
Android 2.0 ?

Hello All

is there any progress on android 2.0 ??? I am waiting a release for my polaris.!!!

also, I am not into programming but I would love to know how do I compile / program the sdk !
[Touch Cruise Android Development] vilord:
nobody is working on 2.0 as far as I know... we'll wait until google releases a 2.0 build for the ion, then work from that.
[Touch Cruise Android Development] niru1978:
Android & Windows 7 adb issue

Hello all

I installed android on my POLA100 but I am not able to connect to my windows 7 laptop.

In the device manager I see my phone as Android Phone and I also got the drivers for adb usb. but I am not able to install the drivers.

always I get message "drivers not found" and even if I try to install the .inf file from the drivers, windows rejects.

please help. I found that most of the android phones that worked are G1 and dreams. is it something to do with the hardware ?

NOTE: usb debugging in on in the POLA100 android (donut build)

please reply

niranjan
[Touch Cruise Android Development] crazyboy1978:
hello ,

How can i read from my sd cart in android???

What drivers can i install for this??

thanks
[Touch Cruise Android Development] Michel82:
You own an sd cart ??? Would love to drive one of those sometime ... :rolleyes:

Serious there's a thread for android user questions: All you wanted to know about Android on Polaris and never dared to ask . This thread is for kernel development.
[Touch Cruise Android Development] vilord:
okay I posted a new rootfs with the RIL changes, it seems to work well on my polaris with both cupcake and donut systems for data. Wifi turns on with both 1.5 and 1.6 systems, and finds the access point, but I didn't seem to get data to come through it... anyone else have more luck?
[Touch Cruise Android Development] SuperJMN:
Could it be the DHCP client? I had problems with it in Donut with this image: http://xdaforums.com/showpost.php?p=4921036&postcount=1

It doesn't get the IP address, but in Cupcake, it does correctly.
[Touch Cruise Android Development] Michel82:
Great news, can't wait to get to test this. I notice this rootfs doesn't work with the old-style filesystem anymore?! Hmm now i have to figure how to create the partitions on my sd.
[Touch Cruise Android Development] Kiiv:
Thank you so much vilord, works very well!

But I've got the same problem with wifi data. I've tested the same donut build as SuperJMN, don't know if the problem append with others.

@Michel82 : this one works with the old system file
[Touch Cruise Android Development] Michel82:
Thanks for the link Kiiv, that one boots fine and i am able to get a data connection,, but it's not very stable. According the ril git that should be fixed in the latest release. I am going to try to create the partitions on my sd-card. What would be the best tool to do this from within windows?
[Touch Cruise Android Development] bbezja1:
may i ask for a word or two about what old filesystem are we talking about here? what in the filesystem is considered old and what about it is uncompatible ?

just to make things clear
[Touch Cruise Android Development] Michel82:
We've always been working with image files as emulated filesystems (the sqsh or img files). Real filesystems or partitions do obviously perform better. Therefore mssmisson created a solution where it's possible to use real ext2 partitions from your sd card. This solution has now been integrated in the latest rootfs by vilord. Simply replacing the old rootfs.img with the new one with fexed data didn't work for me this morning because it expects you have two ext2 partitions. I am about to create these two partitions for myseld, but am still wondering what would be the best way to do this from windows.
[Touch Cruise Android Development] vilord:
This shouldn't require partitions at all, if you don't have partitions it should just ignore the whole partitioning subsystem and just plain work. Can you give details of what you're seeing?

What specifically are you seeing with data?

Looks like there'll be another release tonight...
[Touch Cruise Android Development] Michel82:
With the latest rootfs i get a message that says it's unable to mount /dev/block/mmcblk0p3 to /data (which is correct since i only have one big 2Gb FAT partition).

With the previous version that Kiiv posted i am able to boot and i have an instant data connection, but it seems to disconnect after a while without reason with 3g icon still in the status bar. Some minutes later the 3g icon dissapears and reappears a minute after which my connection works again for a while.
[Touch Cruise Android Development] vilord:
does the disconnect cycle just repeat adnauseum?

I'll look into why you're getting that mount error when i get home tonight from work (8-9 hrs from now)
[Touch Cruise Android Development] Michel82:
The total connect - disconnect cycle takes about 10 to 15 minutes. It disconnected about 5 times in one hour, i stopped testing after one hour to get the partitions to work (which is a pain in the * without a live cd or linux box btw). But it seems to just keep repeating.
[Touch Cruise Android Development] vilord:
I fixed the partitioning thing, it'll now work without partitions. Sorry 'bout that!
[Touch Cruise Android Development] Michel82:
You're a god! Works like a charm now. 3g connection didn't disconnect over the last 30 min. Wifi also works, i got a dhcp address instantly.
[Touch Cruise Android Development] vilord:
So you're doing it without partitions, right?

Just checking because thekartus is having problems with his phone not booting at all.
[Touch Cruise Android Development] Michel82:
Yes that is without partitions. Does using the partitions make a big difference? I'm home from work now and i do have a linux box here and am wondering if it's worth the effort to create the partitions (even now the rootfs is working without).
[Touch Cruise Android Development] vilord:
my phone seems snappier, so if you have the time, go for it.

Use GPARTED though, not fdisk, and it'll be much easier.
[Touch Cruise Android Development] freddycs:
Hi Michel82, can you pls share with us on how to create the partition?

With vilord's latest basefiles i can get my android runs smoothly without the partition.

thanks vilord! great job. may i know is there anyone currently working on the BT?