yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] dysolve:
good work peoples.

with the lastest,

I can

send/receive SMS

receive phone calls ( but no audio)

play mp3's

play videos ( but black and white)

i cannot

Make calls, it just hangs up once I dial number

hang up calls, nothing seems to stop the call other then second party hanging up

browse the interwebs

but the progress is awesome. I wish I could help but with work and starting uni part time its just too much. when I get some time I will try and help.
[Touch Cruise Android Development] imfloflo:
It seems there is 2 categorie of people some of them can call but no sms and other can send sms but have no sound for sms.

Warning when you want to call someone you must use the + <international indicatif> number without 0

for exemple if i want to call 0123456789 in france i must enter +33123456789

but not working for sms
[Touch Cruise Android Development] Scalap:
I noticed the same Imfloflo and I think it may be related to the country we're from. We are both from France and we experience the same problems !

Maybe i am completly false about the country and the differences are coming from the radio (or the ROM, but i can't see why...). Mine is 1.59.42.23 (and ROM : M-Amine 2.0)
[Touch Cruise Android Development] excogitation:
with rogro's latest kernel and dzo's latest system image

- SMS work

- audio works

- calling works (both directions) but audio from xxx -> Polaris doesn't work.

- internet works

(if you want those files without searching - check the wiki)

Btw are the kaiser people already able to connect to the internet without setting up a data connection in Win?

I just checked my last O2 invoice and realized that those ****ers switched me from charging per 100KB to per minute when I extended my plan - nice one §$@!"# - anyways I think it's a good idea to get some flatrate data plan when Android is ready for daily use - which doesn't seem to be that far away when you look at last weeks progress ;-)

Also, rogro82 I think I can help out tracing all buttons/events - maybe we can meet up on IRC sometime.

One more thing - I read that some people allegedly destroyed their SD card running Android from it - how high of a risk are we running there? and if any - would it be a good idea to put the system image on a jffs2 partition on the SD card?
[Touch Cruise Android Development] imfloflo:
When dzo release 21-01 a new package he release just a new zimage and default.txt the others files are the same like in 19-01???

For me

- SMS doesn"t work

- audio works

- calling works (both directions) but audio from xxx -> Polaris works bad ( sync voice probleme).

- internet don't test.
[Touch Cruise Android Development] excogitation:
In the 21-01 package there isn't the latest system.img from here because according to dzo here "it doesn't have a working data connection" - that's why I asked about kaiser earlier.

On Polaris data works ... the complicated way. (and you need to setup your APN in Android)

I'd love to see how a 3d game like this perform on our device - unfortunately I haven't found one that runs with 1.0/cupcake.

According to dcordes here "acx100 driver for wifi. but that doesn't work at all yet. I don't know the kaiser/polaris wifi base address. that value is in drivers/net/wireless/acx100/htckaiser_acx.c . maybe somebody knows it or can figure it out?"

Wouldn't that be nice ;-)
[Touch Cruise Android Development] imfloflo:
A 3D game? just see the earth rotation and its not very fluid for the moment. I 'll try this new system.img thx

edit: test the vogue systeme.img working but when i enter a new APN how i select it after? cause when i try to call it says " no network registered"
[Touch Cruise Android Development] excogitation:
I don't think it's supposed to run any faster than this.

I just deleted the predefined ones. (open - menu - delete)
[Touch Cruise Android Development] imfloflo:
Open menu delete so i set a new apn Orange....

and how i can apply it ?

I think we must speak about this on the other topic

btw when the screen goes off, and i presse power button i can see haret boot screen during 0,5 seconde before seeing the screen lock is it normal?
[Touch Cruise Android Development] berczo:
The same in my Polaris ;-)
[Touch Cruise Android Development] rogro82:
Ok ive extracted the gpio/keypad code from the original board code and written a complete new keypad driver for the polaris.

Its not completely done (still some timing issues), but i have the gpio column working... this basically means that i can finally identify the call/hangup button ( they both share the same gpio ).

Ive also cleaned up the touchscreen driver ( stripped out all on screen keyboard code and some other stuff ) and am going to recreate it from scratch so that we can finally have a normally working touchscreen..

Basically what im trying to accomplish is a clean Polaris code base which can be easily extended.

So a lot of work... Still not 100% but as soon as its stable enough ill post it up here..
[Touch Cruise Android Development] radem205:
Good job Rogro! I know it's a difficult job!

Tonight, Exco has created a wiki with the gpio settings used by the polaris. Through haretconsole he tried to figure out how the wheel works (see the wiki for results). Maybe it's interesting for you (?).

Wiki: http://wiki.xda-developers.com/index.php?pagename=Polaris_GPIO
[Touch Cruise Android Development] rogro82:
Would have spared me sometime, but finally a nice looking wiki... :)

The buttons exco (call etc) cant find are dependant on the column gpios (IN1_17,18,19) They control the state for call and hangup/ie and nav. if 18 is set then left is pushed else right should be used. ( Thats also where i have a timing issue, somehow gpio 18 and 19 arent always triggered in the irq polling ).

The sound button almost works the same but if i remember right this uses 17 or none set.

In the keypad code i created a function that will create a fix gpio nr from bank nr and bit this way anyone with haret can easily update the code :)
[Touch Cruise Android Development] dcordes:
hey rogro can you provide patches so we can merge polaris with htc-msm-2.6.27 or .25 ?
[Touch Cruise Android Development] rogro82:
As soon as things are a bit more mature ill post them to you... Best to send complete new files because there is not much left of the original by then i guess..
[Touch Cruise Android Development] Michel82:
Great step! Seems like progression is really increasing. Big steps were made last week. Maybe we'll actually have a functional android in the near future.

One remark though; I replaced my zImage with the latest one of today and i don't seem to have any radio at all. It cannot find my network (t-mobile nl), where the prior version was quite usable (both calling and gprs worked).
[Touch Cruise Android Development] excogitation:
Sounds similar to how the wheel works (I think I got that one right - took some thinking).

Do you want me to try to figure out the rest of the keys - I just didn't want to do it in vain if you already figured it out.

If I can help (specific tasks) let me know - or maybe it's easier if you talk to me on #htc-linux.

Also - does that mean we could get wlan working easily?

I'm putting together things that need work on / aren't working as expected - if I missed things anybody is welcome to contribute - just to have it in one place for everybody to join in (well as soon as you push your changes/new files to ltg)/fast status check.
[Touch Cruise Android Development] rogro82:
Ill make a list of todos tomorrow... im laying sick in bed so have some time to think things through..

My goal is to make development as easy as possible for others, im thinking about re/creating the polaris code as following:

Board-htcpolaris basic code to setup all necessary things.

Board-htcpolaris-generic leds, vibra etc

Board-htcpolaris-keypad keypad functionality

Board-htcpolaris-ts touchscreen

Board-htcpolaris-osk onscreen keyboard

The board-htcpolaris is almost the same as the kaiser and i stripped out all keypad related stuff and created a keypad driver based on irq polling ( this way we can also implement things like double click features etc in the future ).

I cleaned the complete ts driver and put all necessary code in board-htcpolaris-ts. I dont want any onscreen keyboard code in there because else everytime you want to implement a new keyboard you'll basically have to mess with all ts stuff. Better way i think is to make a loosely coupled setup where the osk code is in another file (board-htcpolaris-osk).

I think this way it will be the easiest to update code and let multiple people work on things.

As far as things that can be done at the moment:

Documenting all gpios/proc_comm calls etc would make development take giant leaps... Else everyone has to find out over and over again.
[Touch Cruise Android Development] cr1960:
Off topic, BUT - thanks for your great efforts and hope you're feeling better soon
[Touch Cruise Android Development] kensou.8:
Health is the most important. Take care of you. ^^
[Touch Cruise Android Development] adderz91:
Mod edit.....please think what you say before you post
[Touch Cruise Android Development] xdadeverik:
Hi rogro82,

Have I donated too much beer? If so, sorry for that. Next time I'll donate some asprines with it :)

You and all the others have done such a great job. Just by trying it I almost find Android more usable. Surely I would find things that I will miss in daily usage. But I can send and receive e-mail, use google maps. I love the keyboard, it type really easily! I'm really sick of Windows Mobile. 6.1 is a bit better but it's also become slower. Trading of responsiveness for some small incremental improvements is not what I was looking for. The device has enough muscle to be responsive AND to run software that is designed to be usability.

Anyway, rogro82, hope you get well soon (Beterschap!)!
[Touch Cruise Android Development] rthunstrom:
Telenor does not work but I´m happy nevertheless

I applaud you! Great work!

My new startpage in Google Chrome is http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux :)

I´m from Sweden and I have Telenor as carrier. Sadly I can not get my phone to connect when searching for networks. As I understand there some lucky ones who actually can make calls and send SMS´s and so.. I´ll just have to wait for a newer version of this or?

Keep up the good work!
[Touch Cruise Android Development] Michel82:
Stupid question maybe: Would it be possible to merge the working radio parts (calling, gprs) of the older release, with the working audio and sms parts of the newest?
[Touch Cruise Android Development] biktor_gj:
Hi all,

I come from the Nike forum asking for some... diffs? We're trying to port linux to the HTC Touch Dual, and found the Polaris is very similar, got the last zImage and with surprise saw the 1.0 sdk boot cleanly, but with all the gpios messed up (wich was predictable anyway).

Anyway, I have the git tree downloaded, but, at least the version I have cloned, doesn't seem to have some important changes wich prevent me from compiling a kernel with a working sd driver. I guess changes haven't been commit-ed to the tree yet, but I was wondering if there's some patch I can commit to check it out...

Thanks!

...and sorry for the bad english :)
[Touch Cruise Android Development] radem205:
It is true Rogro didn't add commits to the tree. I think you have to wait until Rogro release his latest files and extract these files to have the latest commits.
[Touch Cruise Android Development] rogro82:
Thank you all for the kind words and the beer of course. Ill stick with tea for now, but ill surely think of you when im feeling a bit better and drinking a cold one ( hopefully this weekend ) :D

Ok i couldnt lay in bed all day and do nothing so I did the following today:

Finished the keypad driver.

Created an extra keypad driver which is based on a matrix. Its basically a 3x3 matrix for the buttons that werent working correctly (phone->hangup, ie->nav, vol_up->vol_down->voice recorder). I mapped the nav and the voice recorder to the Home button. We can change this later on, but i couldnt think of anything usefull to map the voice recorder button to and is also supported by Android. ( Maybe someone can make a list of all android keycodes )

Added an fake lid switch to the keypad driver coupled to full press of the camera button ( this way we can also enjoy Android in landscape mode )

Stripped down the touchscreen driver completely so no more onscreen keyboard stuff in there, just plain touchscreen related and it just makes calls to the osk and the generic file for onscreen kbd stuff.

Created a file that handles all osd/osk stuff ( this is where the actual onscreen keyboard will be handled ). We really need a new keyboard ( at least thats what i think... kinda hate the small buttons ). If someone can create a new gimp image like the one there is now it would surely help :) Later on we can even create a complete osd menu or something... Wouldnt be too hard now..

Create a generic file which should cover all general stuff ( vibra/leds/etc ) and saves the state for things like if the osk should be drawn etc.

And some more random stuff...

Ill upload a new zImage in a few minutes first im going to grab something to eat :)
[Touch Cruise Android Development] imfloflo:
Why just don't we use the wiki and having table with state like in the Diamond page ?

Good :)
[Touch Cruise Android Development] Michel82:
Would it be possible to extract the images from the cupcake keyboard somehow? I'll check if i can find them somewhere on the internet, or how to extract them.

Great! Looking forward to it. Calling functions are still the same? Cause gprs and calling is impossible since the last update. Could that be due to the latest system.img? In that case i'll revert to the previous...
[Touch Cruise Android Development] rogro82:
Yes its because of the new Ril code in the new system.img.

I also have the same problem ( T-Mobile Nld ). Some people can get a phone connection and some even a data connection but most of them cant. For me it wont find an operator so i guess well have to add it to the phone db.

Ok

The included zImage is still work in progress so I hope all is ok, but youll never know.

I let out the keyboard because im still working on the complete osd/osk handling. (this will become cam half press)

To change from landscape to portrait mode and vice versa use the cam button full press. I know a lot of the programs in Android arent looking very good in landscape mode but maybe someone will port them for our resolution..

It doesnt seem like a lot has changed but believe me in code it has. Almost everything is stripped down or rewritten. Finally I think there is some structure in things, which wasnt really the case before... As soon as I have all basic stuff covered ill commit the new code. If someone is dying to see what I did then ill post a zip with all changed files, but like i said it isnt completely done.

Next up:

Finish the osd/osk stuff

Make the battery code work

Make the leds work

Make the wheel work
[Touch Cruise Android Development] Michel82:
Great i'll try right away.

Searching for keyboard related images i found some information on boot logo's (which is still to big for our polaris) i'll see if i can adjust them to QVGA soon. I've added the images.

I also found the closed source *.apk's amongst which is Gmail.apk and Sync.apk. I'm not sure if i can add them legalwise though. They're closed source but free. Anyone knows a thing about licensing?

Continuing my search for the cupcake keyboard images
[Touch Cruise Android Development] excogitation:
android.view.KeyEvent
[Touch Cruise Android Development] rogro82:
These are the actual Android codes if im not mistaking... We need the raw codes which are later on converted by android..

If someone can find out if there are raw commands for the following in can map them:

SMS

Browser

I dont know if the G1 has quick buttons for that but if they have them there should be raw commands i gues...
[Touch Cruise Android Development] radem205:
Nice to have you here Rogro. I hope that you are on the better hand.

I've test your zimage and I see an impovement at the screen sensitivity and landscape is working really nice, instead of some apps (also volume and call button are working correctly!). Only when I open the browser I get an unexpected error.

You did really a amazing job! I hope dzo will release a fix for the audio soon, but until then, and offcourse after it too, you are our man for android on our polaris!! Thank you!!

Beterschap!
[Touch Cruise Android Development] excogitation:
* wheel cw

in1-20(212)=1

in1-15(207)=1

in1-20(212)=0

in1-15(207)=0

in1-20(212)=1

in1-15(207)=1

...

* wheel ccw

in1-20(212)=1

in1-15(207)=0

in1-20(212)=0

in1-15(207)=1

in1-20(212)=1

in1-15(207)=0

...

if you switch turning direction just the last one gets negated in this case the next lines would look like this:

in1-15(207)=1

in1-20(212)=0

...

so you just need to read the state of pin 20 bank 1 and 15 bank 1 and check against e.g. the cc algorithm

e.g. 20/1=1 and 15/1=1 then it either becomes 20/1=0 15/1=1 which means it is turning cw or it becomes 20/1=1 15/1=0 -> ccw.

Hope that helps (or did you already know?)

The G1 only has 6 buttons on the front:

menu

call home trackball back end

on the sides vol up/down | power

and the keyboard

g1 large image

no SMS/Browser keys

I'd opt for mapping end somewhere since that is a G1 key and we don't have it mapped yet (obviously the associative one would be end - but then we'd need a different back key)

Also you can give each key a different long press action if there's the need to.
[Touch Cruise Android Development] adderz91:
So what will it take to implement a keyboard such as this?
[Touch Cruise Android Development] berczo:
Hello, i have still no network connection after ne zimage from 22.1. by rogro82 :confused:
[Touch Cruise Android Development] agtmxx:
What radio are you using, with 1.59 - all ok with connection., but with 1.58 i had problems.
[Touch Cruise Android Development] xonx:
Problems booting - SD Partition not recognized

Hi,

I have a Polaris and i'm having problems booting Android.

It says it can't find the partition table on the SD card:

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

mmc0: new SD card at address b368

mmcblk0: mmc0:b368 ST128 124160Kib

mmcblk0: unknown partition table

Failed

No partition found on SD card

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

Any idea on how to resolve this issue?

Many thanks,

Cosmin

PS: I'm using latest zImage from RoGro82 released on 20.01.2009 and the Vogue package from 19.01.2009. I also tried with older versions and i get the same error.
[Touch Cruise Android Development] rogro82:
Ill need to make a release timer to make a long press. Because the other long press actions are initiated by Android and i can only make them for the non-matrix keys for now because they are handled with an irq rising-falling method, so i can catch the up and down state.

The end call button in the G1 is normally mapped to 0x6b. Our power button is mapped this way... You can set the end call button (power button) behaviour in "Spare parts" if im correct.. Can you try ending a call with pressing the power button? I could map the back button to the nav button set the "End call" as the real "end call" and make the voice recorder our home button...

Me neighter but its not zImage dependant, it depends on which system.img you are using ( one from DZO is using a new Ril, which should some people give the right network connection, but i guess the telephony.db isnt complete or something, because ive heared no one from The Netherlands with T-Mobile can. )

Just revert back to and older system.img and you should be able to make a call/gprs connection
[Touch Cruise Android Development] xdadeverik:
Hi rogro82,

I actually liked the keyboard very well up to now. I've never been able to type with my two big thumbs, but with this keyboard you get hints about which key you are over and if you press harder, you type it. I don't know why, but I can type a lot better and faster with it than the WM OSKs. Slightly bigger keys would be okay, I guess, but don't write the keyboard off as useless for all. I actually wonder how it could be even better. I can't wait for the phone app to work. That would definitely be worth a couple of beers ;). To bad we can't cheersch (proosten)!

Anyway. I've been trying to test the changes you make every time (and confirm working/non-working states of various todos), but from HaRET it usually stops after the progress bar is full. I'm still not shure what makes it run about 1/4 of the times. I can't find a pattern, was looking for GPS and/or UMTS being in use while HaRET starts, or something like that. If you can help me with that I'd be a better tester.

Best regards,

Erik
[Touch Cruise Android Development] rogro82:
Erik,

The keyboard i mentioned was the one you got when you half pressed the camera button ( its a keyboard to use on places where the Android OSK isnt working yet, like the terminal ), the one from Android will not be removed. This one is actually part of the new Android code. ( And i also think its much better then the winmo one ).

What radio version are you running and did you try updating it? Mine always runs no matter what i have on, so i think you should look in that direction. Maybe something rom/radio related.

Edit:

Call me stupid just seen the radio mentioned :) 1.59.44.02 so i guess you should try to update it.
[Touch Cruise Android Development] radem205:
It's very strange, but when I use your latest zimage I can setup a data connection (vodafone NL) but when I launch the browser I get an unexpected error, so I won't be able to browse the internet (google maps works).

But the keypad and touchscreen are working very well (big improvement!). Only the missing audio (during calls) keeps me from daily use.
[Touch Cruise Android Development] berczo:
I can confirm, that old system.img from 19.1 and new zImage by rogo82 ... with this i can get network connection ... i can make call but without sound ...
[Touch Cruise Android Development] Quilapvd:
Qvga has a size of 240x320?

I can resize the picture's if needed (photoshop).

Greetings.
[Touch Cruise Android Development] rogro82:
DZO is working on the audio_path to work properly... the audio path is responsible for switching the audio profiles between calling/speaker etc.

So hopefully this will work soon as well as the ril-code, which is reponsible for all phone network/call/sms related stuff.
[Touch Cruise Android Development] Michel82:
That's right. the big picture is the background the other are the overlays for the blinking effect. If you could resize them, that'd be great!
[Touch Cruise Android Development] Swifty:
I know this will probably a long way down the road but it would be great to have a keypad like the phonepad from the HTC Diamond.

I'm guessing there is probably nothing like T9 in the Android system though, so might be hard to do..

I love this keypad under WM since I can type really fast without needing to pull out the stylee..
[Touch Cruise Android Development] Michel82:
I've also reverted to the previous cuase of the non working RIL. If DZO could make both audio and the RIl correct that'd be awesome.

Btw If tried installing the closed source android applications on my phone (by putting the *.apk's in AndroidApps). They did install (can see 'em in stalled programs) but didnt create any icons. So i have no idea of how to start gmail for instance.