yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] rogro82:
Never said that ;) just a hint...

Just change the "machine_is_htckaiser()" into "machine_is_htckaiser() || machine_is_htcpolaris()"

That way you can create a working diff for both devices and add it to the git, without breaking stuff.

We can add the charging pretty easy... i guess its gpio 5,1 or 5,4... but i dont think it belongs in the keypad driver ( atleast not in my opinion, eventhough its a gpio input... either the driver should be renamed or it should be handled somewhere else ).

I think it should be put in board-htcpolaris-generic ( theres already an empty polling driver in there which was used for the backlight before i took it out because it was put in vogue_hw )... I created this file to handle basic stuff like vibrate/leds/keypad backlight etc which are pretty device specific but the handling isnt actually big enough to create a complete new file for.
[Touch Cruise Android Development] excogitation:
because vogue-hw.h isn't included?

Sounds like a system.img problem. (didn't we have that before?)
[Touch Cruise Android Development] rogro82:
Not being able to find images etc in android on the sd is most of the time a system.img problem...

The sdcard is working properly else you couldnt boot android :D
[Touch Cruise Android Development] dubbeld00:
Haha alright,

Still the timing of the TS isn't great (or the left is still 0, or bottom is still 0), btw DZO moved it from the driver to the keypad so I guess we have to do it somewhere within mach-htcpolaris* (which in my opinion is correct, since every mobile has another gpio to see if it is inserted, and might have to set up other things)

Will give the TS a go
[Touch Cruise Android Development] rogro82:
I edited my post so i dont know if you read it :)

But this is my idea for all the machine specific stuff:
[Touch Cruise Android Development] rogro82:
I think we should recreate the Touchscreen driver to be a irq triggered driver... I guess this will make the input a lot more accurate.

Ill give that a try as soon as i get back home and post up a diff file so you can play with it.
[Touch Cruise Android Development] dubbeld00:
Yep saw it and I'm reading it wrong... I didn't saw the last part of your post... reading now

blablabla

I'll try to fix the ts (just for fun)
[Touch Cruise Android Development] Michel82:
Als still having the TS problems with your changes. Btw. i cannot seem to get a data connection with these latest files ?!?! I have always been able to connect with togga with every version so far. Strange ...
[Touch Cruise Android Development] radem205:
With this zimage I notice that the virbrator doesn't work anymore. And one time I notice when I push the phone out of sleepmode I get always the popup "Sound off / Power off the phone" (which is displayed when you hold the power on/off key.
[Touch Cruise Android Development] dubbeld00:
Vibrate is working here... only applied 3 fixes:

- load the battery driver

- in battery.c => added mach_is_htcpolaris()

- called the battery driver

and ts:

- larger sleep before checking the position on the TS

please also use the latest 10-2-'09.zip from DZO

__

Hmmmm 2 voicemails... maybe also have to buy another phone, to develop on this one ;)

No more time:

- To rogro, DZO made a very nice touchscreen (vogue-ts) which use a timer, and check the IRQ's to see if it is a valid "touch" on the screen.

btw can you please add this line: input_set_abs_params(data->idev, ABS_PRESSURE, 0, 256, 0, 0); (testing to see if it is getting any info)
[Touch Cruise Android Development] radem205:
After a reboot the vibrator works. It seems like, what dubbel00 already said, the battery in Android is fuller then the battery in Windows (WM: 39% and in Android more then 50%).
[Touch Cruise Android Development] rogro82:
Ill gues ill just create a new ts driver from scratch... Theres not that much to it, ill add an irq rising/falling trigger for the screen press event..

Better to start on a clean base... The touchscreen driver is the only one that I kept almost completely intact ( besides the osk ) and I guess its about time to create a new one..
[Touch Cruise Android Development] radem205:
Good to see that you are working on an good working android version on the polaris, while you having a beautiful G1 :).

Is it difficult for you to work first on holding power on/off button to get the popup to power off the phone? Because the touchscreen is working well for the moment, sometimes it doesn't register right but that's not very annoying.
[Touch Cruise Android Development] dubbeld00:
If you got plenty of time, why not ;),

btw radem about the battery state... the battery code is still in active development, so it might differ, will get better (or worse... hopefully not) in feature versions ;)
[Touch Cruise Android Development] imfloflo:
rogro82 will do that in one WE :p supercoder inside ;)

what about the release of the 1.1 SDK? is it good to or lastest system.img already based on a leak version of it ?
[Touch Cruise Android Development] peciss:
Hello,

can somebody help me with installing Linux on my Polaris?
[Touch Cruise Android Development] dubbeld00:
Click here this might help you.
[Touch Cruise Android Development] imfloflo:
Just read the first page, go to other thread and on the wiki not very hard todo.

this thread is for development not for installation.
[Touch Cruise Android Development] peciss:
I found something here http://xdaforums.com/showthread.php?t=473102

Thanks a lot
[Touch Cruise Android Development] Michel82:
With the latest files i have the following issue:

Directly after boot i have the G icon on top, but no connection (cannot browse to a page directly saying the page cannot be found). When i connect through togga i do get an IP (used to take up to three attempts with the previous version). But the G icon dissapears and i cannot browse to any page it tries to load a page but it just takes forever and never loads. When i disconnect from Togga, the G icon appears again, but browsing to a page directly says i have no connection. Very strange, any1 else with similar problems or a solution?!?

Also, in random cases, i'm unable to hear the person on the other side and the person me. I'm having this last issue since DZO changed the system.img to create a connection on boot.

Another strange thing: when i connect through togga it drops radio connection completely (indicated by the cross through the connection strength bars) and then reconnects instantly.
[Touch Cruise Android Development] dubbeld00:
Guess it wants to connect to a 3g network, and the only network around is 2g :) so it will lose the connection... It's working great here.
[Touch Cruise Android Development] radem205:
I have noticed the same issues before (all of them), randomly (also with the latest files). I have noticed that everytime you boot android, something doesn't work very well, until rebooting and then other things don't work very well.
[Touch Cruise Android Development] dubbeld00:
Maybe check your radio version... because I boot loads of times to android, and never saw strange things... sometimes togga needs 3 attempts to make a connection, but never failed... (on system.img files which CAN successful make an internet connection).

So if you take the 10-2-09 build of the kaiser, and take the latest zImage + default.txt for the polaris, it should work fine.

Btw my radio version: 1.58.32.33.

Apps can't reach SD-Card, thats the only bug at the moment with this system.img
[Touch Cruise Android Development] xdadeverik:
Kudos & Donating!

I can confirm this works well. Less noisy output on the console during boot. Nicely centered android logo. Boot took quite long (90-120 seconds). Battery meter working! Net works after togga. Other things seem the same compared to 4-02-09. Touch screen registers correctly and responds pretty well (though I had one incorrect registration after playing with it for 20 minutes). Calling works OK. The terminal screen gglitch you see when powering up for a very short while, seems to appear only about half the times. It's low priority, but it seems that it's improved compared to last time (or I may have missed it).

Excellent work guys!

To whoever gets the camera or GPS working, my company (http://www.BudgetDedicated.com/ will another donate (10 euros for the first, 20 euros for fixing this last important functionality)! The phone is close to getting fully functional! For WIFI we'll offer just 5 euros (not useful to us personally) for stimulation. We invite others to join in with sponsoring this development to reward the excellent development work being done! PM me to suggest other work, I can consider donating.
[Touch Cruise Android Development] rogro82:
Ok i have some work done and ill upload a new zImage in a few...

Things done:

Changed the keypad handling ( all is now done in one single driver and is on another base then it was ), the power button should now work normally.

I had to remove the Lid switch ( which sets landscape mode )... Ill re-implement this later on, but its not very usefull for now as most of the apps are not shown normally this way.

Also changed the keypad backlight... Its now handled in userland... So the keypad backlight is controlled from within Android and isnt set using an inactivity timer anymore.

Besides that I added the battery driver and cleaned up some stuff.
[Touch Cruise Android Development] excogitation:
If more people join (Kaiser/Vogue/Niki people?) in it's probably a good idea to start a new thread with somebody updating the first page also with:

The donation list (sorted by amount) and some suggestions

GPS

10-20€ xdadeverik

main Camera - back

10-20€ xdadeverik

Wi-Fi

5€ xdadeverik

15€ excogitation

headset RC E100

10€ excogitation

USB networking

power management

battery status and charging

bluetooth

videophone camera - front

appstore
[Touch Cruise Android Development] rogro82:
Changes send to Martin (DZO) so they should be available to everyone soon...

Edit:

Does anyone know what the chipset of our camera is? :)
[Touch Cruise Android Development] imfloflo:
thanks rogro82 for the new zImage are you using lastest DZO other files ( system,img, data.gz intrd.gz default.txt)

Is it possible to use the default.txt in dzo package and just change the mtype cause their are unknow other values different from polaris.

i find lastest release very long to boot... during the android boot logo
[Touch Cruise Android Development] rogro82:
Yes you can... I just had to reformat my sd card because it wasnt mounting in linux. After that i just went to Martins site and took the latest package and changed the default-kaiser.txt to default.txt and changed the mtype to the polaris and I was all set :)
[Touch Cruise Android Development] bally3:
A new thread in the general forum for all three devices does sound like a good idea, I did consider it a few days ago, but to be honest its going to cause more aggro than its worth.

The better idea as far as I'm concerned is to create a group which is used by invite only - so only users involved with the development - and if dzo and rogro agree to post all dev posts and images there, we can use the existing threads for general development discussions to complement this.

If the devs go for it, and only if they go for it, it can work. Users will follow the devs.

I suggest a get together by a few of the active participants to discuss how best to manage it. a group of users who take the first 10 or so posts immedietely and then title them accordingly (Latest News, Central File Storage, TODO list etc) which they use to update.
[Touch Cruise Android Development] imfloflo:
With the lastest release i'm not able to make a call everytime it says on a popup : "not registered on network"

just the mtype not change this strange value

EncFiltLog.menc file appears on my SD ? what is it?
[Touch Cruise Android Development] bally3:
The problem with threads are well known and a general thread for all three devices is likely to cause more problems as users get annoyed at incorrect support request postings etc. The kaiser thread hit its 3000th post today so imagine how big a three device unmoderated thread will be and how quickly that will grow out of control.
[Touch Cruise Android Development] excogitation:
I put it on the wiki so you can add yourself if you feel like supporting the devs (or I will if you tell us here).

It could be the same one Kaiser uses Cam1 Cam2

as quite some parts seem to be identical.

To be sure we would need high res pics of a disassembled unit

- does by any chance someone have those -

or a broken unit to disassemble

or is someone willing to disassemble his and take good pictures?

(if no one steps up - and we gain from it I will take mine apart within a few days)

Sounds good to me - if we can just delete the unneded posts and if devs think it's a good idea.

I don't know how groups work on this board.

Users don't care as long as they know where to get the latest stuff

and where to go for support (which seems to be the problem to me - as a lot just post in every thread they find).

I don't want to preach ... but wouldn't it be easier to just do exactly that on the xda wiki?

As I see it most posts are for support - even though the answers

have been posted over and over again - just that many are too

lazy to even read back the last couple of pages.

Is there a system.img around based on 1.1 SDK with working google login?
[Touch Cruise Android Development] TomAngel:
Hi,

can confirm the following with latest zImage (rogro82) and DZO latest 10-2-09 :

- Internet working with initial Networkconnection under WinMo. (first use Togga)

- Make/Recieve Calls in good audio quality over internal speaker

- Battery Indicator works

- Screen does not lock on long press Powerbutton to switch off device

- Send/Recieve SMS

- Can access SIM-Card Contacts

- Can access Pictures and Audio Files on SD-Card (view and play)

Needed to set up APN Settings for E-Plus Germany and delete others.

Using Polaris under M-Anime 2.0 RTM Custom ROM, Radio 1.59.44.02.

BTW. You guys are awesome!!!!!!

Will donate as soon as GPS is working... (most important for me)

Many many many thanks for your great work.
[Touch Cruise Android Development] imfloflo:
LED working ( blink green )

Battery indicator working

call not working for me :s

network icon topbar show "x"

togga don't work with lastest rogro zImage :s

dissassembly polaris:

http://www.pdacenter.ru/razborka/razbor_htc_touch_cruise/

pict http://xdaforums.com/attachment.php?attachmentid=89644&stc=1&thumb=1&d=1212337761 p°84 interesting

Link removed - no longer valid

Futur steps:

need to have PIN request and the automatique network detection
[Touch Cruise Android Development] excogitation:
No need for a connection in Win anymore.

The leds keep doing what they were doing in Win.

Battery indicator "works" but isn't accurate yet.

Togga works with rogro's latest kernel (maybe not with some recent system.img).

The pics are nowhere near good enough (went through those some weeks ago).

The manual is for sure excellent for someone willing to disassemble his device (like me ;-)

Could you ask the one who posted that pic (don't know which thread)

if he by chance took a lot of high-res pics and is willing to send them to us?
[Touch Cruise Android Development] TomAngel:
Hi excogitation,

tried again, but for me Togga only can access if there was a dataconnection under WinMo before using haret.exe .

Elseways Togga fails to connect. Don't know why...

Battery indicator "works" means it is not simply 100% but shows nearby the same as under WinMo.
[Touch Cruise Android Development] imfloflo:
We really need to fix this problem with all different system.img version.

What version are you using ?Exco ?

the pic comes from this post http://xdaforums.com/showpost.php?p=2257331&postcount=17
[Touch Cruise Android Development] TomAngel:
I load up my working Package including edited default.txt to Rapidshare.com

Link will follow...

Here it is : http://rapidshare.com/files/196603874/Android2-10-09.zip

ppp - Parameters in default.txt are set for E-Plus Germany...
[Touch Cruise Android Development] imfloflo:
TomAngel very thanks ;)

could you tell me what file are you used cause your package works great

bootlogo OK

call OK - with good speaker ( i call my vocal voice messagerie)

receive SMS OK - (to test it goto here and type your number http://www.google.com/intl/fr_ALL/latitude/intro.html)

send SMS NOK -

in call volume NOK - don't work

french menu OK - set local to french So my android is in French now :)

during boot strange message appears normal ?? : "waiting for ppp"

i change the ppp settings in defalut.txt for Orange france, and i must delete all APn in android and add mine after that i see a G icone with ↑↓

i don't launch togga cause haven't a data plan for the moment

calling the #123# *#123# to know my account and it says "connection probleme or invalid MMI code"

Seems good, alright let's go, tomorrow i will wake up by android on my polaris, give a try hope the battery is good :p

edit: DZO made change and release another package and zimage which should be good for polaris
[Touch Cruise Android Development] TomAngel:
I used last zImage by rogro from Post #724 with latest DZO Files from 10-02-09 Release.

I got ppp Message too on first boot, and could not get a data connection.

I had to establish a connection in WinMo first then on second boot got only 4 ppp lines.

Think it tested internal modem routing because of universal kernel...

From second boot on all worked for me as discribed.

But I had first to connect under WinMo to get a data connection in Android.

In-Call-Volume haven't tested, send SMS worked for me (Text to Speech SMS)
[Touch Cruise Android Development] radem205:
With the latest files from dzo (http://cs-alb-pc3.massey.ac.nz/vogue/files/android.zip) the touchscreen seems to working better, but when I hangup a call (with audio) audio doesn't work anymore :(

Edit: I think it has to do with the radio upgrade I've made yesterday. Because also with the zimage from dubbel00 audio doesn't work well.

Edit 2: No problems using new radio anymore (1.59.44.15 or something like that)
[Touch Cruise Android Development] rogro82:
Changes are commited to the git:

http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=94eb41c005b312439f3c49eaeab5d74ea25610ba
[Touch Cruise Android Development] imfloflo:
Just test lastest DZO release all working good for me. but

Bootlogo is NOK - wrong size

French language is NOK - not in the list anymore
[Touch Cruise Android Development] rogro82:
These problems all come from the system.img and dont have anything to do with the actual kernel...

Maybe it would be better to seperate this from the package, so people can choose as they like... But then again, if something is changed in for example the ril, people will never understand why it isnt working..

If you have a working system.img you can just stick with it until there are major changes made to the system.img... Just backup your working old one and if the new one is working ok just stick with it else just revert back to the older one...

I never touch the system.img because there isnt much work at that part. Most stuff is already worked out ( as being part of the Android image ) and only "minor" changes have to be made, like the ril.

The actual reference between the system.img and the kernel is done through spaces like /sys/class/leds, which should be used in the kernel to actual change things like brightness / keypad on/off / led on/off etc , so that the states are actually set/notified from within Android ,instead of settings them from the kernel..

Ive already done this for the backlight and the keypad backlight ( So these are now actually working the same as the G1 ).

Edit:

And as from now there isnt a personal build anymore... It doesnt matter who builds the zImage as we are all working on the same code base. So as soon as I or someone else makes a change and they are commited to the Git any build will incorporate these changes.

The only thing is that most of the time I post a new zImage up here so I know everything is working as it should. After that I send the diff files to Martin/Dcordes so they can be checked if it didnt break anything else on another device and then they will be commited.
[Touch Cruise Android Development] imfloflo:
Thanks for the info, i will just change the zImage in the future so.

The battery level decrease speed during the night :s

Charging battery must be implement if we want to use it everyday.

I find lastest DZO package more responsive when i touch the screen.

great job guys.
[Touch Cruise Android Development] dubbeld00:
We can use the other thread to give pro and cons of the different system.img files... so what is working and what isn't. This way it is clear to all what to use, and what isn't.

Btw why don't you use your own account... easier for me to track down your files. "if(is_msm7200()) {" jeeej!

I like the progress btw!
[Touch Cruise Android Development] excogitation:
Full ACK

Google login would still be nice.

Since dzo replaced your machine_is_htcpolaris with machine_is_htckaiser - backlight doesn't switch off anymore ;-) (-> is_msm7200)

I just noticed that we're (I am) having the same problem as mentioned in the Kaiser thread - if you receive a call first then audio doesn't work anymore.

If you place a call first - after that receiving a call works as well (don't know if that problem is new).
[Touch Cruise Android Development] radem205:
@exco: I noticed some issue with the audio too after I had changed the radio rom down to a 1.58... version. So I switched back to the Radio ROM 1.59.42.15 version and everything seems to be normal.

I have rebooted android and immediately have called with another phone to the android phone and audio is working as it should be (also after I have made the phone call).

So give it a try...

It seems that for the polaris the power management isn't optimal yet. In the kaiser thread I read that someone have experienced a battery drain of 60% during one night (maybe he sleeps very long :) ). When I wake up my phone is powered off :)
[Touch Cruise Android Development] imfloflo:
I read in kaiser threade someone success to charge her battery but for me not owriking on polaris
[Touch Cruise Android Development] radem205:
Indeed it isn't working yet, they working on it (because the settings aren't right for the polaris yet)

Edit: With the new files from dzo I notice that the gps button (bottom left) also works as an end button. Maybe this was already in other releases.
[Touch Cruise Android Development] Jackal21:
TomAngel

Thanks.Works fine.But can you tell me, what does DS.store do?

It saves some files in Main Storage and when Android starts up, there is notification, that I haven´t enough disk space.

And in WinMobile, takes about 2MB in Main Storage left. Do you know where is these files in Main Storage? I want delete them, after trying Android.
[Touch Cruise Android Development] rogro82:
:D continues struggle...

I told Martin he could use the same function to control the kaiser keypad/backlight. Guess he changed it instead of addingthe kaiser support :)

Ill go and fix it tonight...
[Touch Cruise Android Development] imfloflo:
@Jackal21 .DS.Store files are mac oSX files you can delete it without problem

Already in previous version the chat button not gps button on the top left, top off volume button ?
[Touch Cruise Android Development] briggs81:
I have done what you have suggested and having better success. Changed radio too,b ut phone keeps losing connection as it needs to have data roaming turned on, whcih i have turned on.. but it says its not. I get random things too, soemtimes there is a g wtih up and down arrow, whcih i am assuming means active connection, but then it dissapears.

Togga says I am connected.

Sigh.

Also tried to make a call, couldnt hear anyone, he couldnt hear me, and I couldn't end the call, had to take out battery. Power didnt even work :(