yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] a.s.j:
Devs and Changelogs

Well I am trying to figure out how to build changelogs automatially based on the git logs. I know that it is possible, but I had a lot of problems solving some DNS issues, so I had not enough time so far...

Now I am for a weekend with my son, so I'll take a look at that one later. I was also trying auto mirroring pushing files by FTP to other servers, but there is also something weird, because it tries to do chmod then and does not have permissions...

Anyway I agree we need more devs onboard, but you'll not get them without having full support for them, cause this way they'll wait for dzo's work forever, cause they are not sure what to do...

That why I am still thinking about some knowledgebase, version and issue logging and tracking, some more things on separate site just to have full support and ease the work for the devs. Cause I am lost also now and I am not able to help with kernel development... so this is at last something I can do :D

It is just to show people what is done, what is not done, who is going to do what etc... perhaps that can be helpful, or you think different?
[Touch Cruise Android Development] excogitation:
Here's what to do - and if someone is not sure about what's being worked on (to not do it twice) - you can always ask on #htc-linux.

I'm keeping that wiki page updated for Polaris - so you can always check there what's working and what still needs to be done (or Regressions if there are any).
[Touch Cruise Android Development] a.s.j:
Great, at last somewhere we have a place to start :) thanx for your input pal..
[Touch Cruise Android Development] rogro82:
Ok finally found some time to get the battery charger working.... So you can now finally charge the phone while in Android.

No other changes made, but will try to do some more work this weekend.
[Touch Cruise Android Development] excogitation:
It sometimes takes about 2 mins to detect charging (or disconnect) in Android.

Does work with AC and USB (always states "Charging (USB)")

The battery level is still slightly off imo.

(Settings -> About phone -> Status)

Testing atm if it stops charging at 100% (or rather if it says so).
[Touch Cruise Android Development] rogro82:
Ive also noticed this... ill take a look at it.

I havent changed anything to the battery level... I guess when the actual level will be fixed for the kaiser it should be good for us also...
[Touch Cruise Android Development] excogitation:
The battery level max is 97% in Android when the light already is green in Win (full) -

so it might kill your battery if you leave it charging too long in Android

(don't know if it stops charging and just displays a wrong status - I had it for about 30mins on 97% because I didn't know it was full).
[Touch Cruise Android Development] bally3:
Just a word of caution to all none-testers of this project:

until the battery and charge levels are confirmed as working. i wouldi advise you not to leave your phone charging whilst using Android.
[Touch Cruise Android Development] radem205:
@Rogro: Thanks man! Same issue with charging. With the zimage from dzo I notice that the touchscreen is more responsive then with your zimage, can this be true?
[Touch Cruise Android Development] rogro82:
No... it cant... its the same and dzo didnt change anything for the polaris. Changes were made against the latest commit and the only thing added is the irq handling for the charger gpio.

Like stated before there is no personal zImage, the ones I build are most of the time one step ahead for the polaris because my code gets commited later on and if dzo or someone else builds one after that it will also have the same features as we are all working using the same repository.
[Touch Cruise Android Development] radem205:
Ok! In contrast to my previous message I can't charge my phone at all. After more then 15 min I don't see a chargable icon and the status shows the phone is not charging.
[Touch Cruise Android Development] excogitation:
Battery Status taken from here.

Charging does only work if you start with AC plugged in Win.

Battery levels with standard Pola160 battery (same as Kaiser).

These should help with battery status calibration:

(if you are satisfied with Win's battery status (non-linear))

Win <-> Android

04% <-> 28%

14% <-> 36%

24% <-> 42%

34% <-> 49%

44% <-> 57%

54% <-> 63%

64% <-> 71%

74% <-> 78%

84% <-> 85%

89% <-> 88%

94% <-> 91%

100% <-> 96% but in Android goes up to 97% so it seems it doesn't stop charging!

Btw can someone confirm that the device (touchscreen?) gets

unneccessary warm in Android when booting with wlan enabled in Win?

The ds2746 also has a temp sensor...
[Touch Cruise Android Development] rogro82:
Thanks exco... Ill try to recalculate the values in the i2c driver based on your findings.

Bally3 has also been mentioning the heat issue and a lot of pages back i already suggested that it could be because of the wlan. I never have wlan on when booting Haret, but Ill give it a shot to see if its heating up.
[Touch Cruise Android Development] bally3:
I can confirm this exco, the heat issues

i reported were related to this it seems as rogro suggested - im a big wifi user so its mainly on - but switching wifi off in winmo has resulted in cooler android system.
[Touch Cruise Android Development] excogitation:
Can shutdown be changed to reboot easily? (or better: added as additional choice?)

Not to give you a reason to get all randy - but: initial wifi support - nice!
[Touch Cruise Android Development] radem205:
I think it's good to let all the other elements work properly, for example the LED's and the battery indicator (charging), before working on the new elements (WIFI, etc.). Is it possible in the future to charge the battery without first plug in the usb in WinMo?
[Touch Cruise Android Development] imfloflo:
lastest zimage DZO works well but not wifi for polaris :s muist wait, like radem205 said i prefere charging and usb support before
[Touch Cruise Android Development] sblaster:
Working on SFR in France with last version. You have to disable the PIN on the sim before launching android. The default.txt is this one

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd.gz

#

# The following kernel parameters are useful

# ppp.username - The username used to connect to the network when dialing #777

# ppp.password - The password used to connect to the network when dialing #777

# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

# pm.sleep_mode - The mode used when the phone is off

# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,

# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

# Default is 0, use 3 if you have an old radio

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung

#

set cmdline "ppp.username= ppp.proxy=195.115.25.129 ppp.port=8080 ppp.apn=wapsfr ppp.password="

# This is what I use: "msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"

boot

Strange thing is that in the Android setting, i have to empty (or likely) APN, which do not refers to SFR...

Cannot synchronize with gmail account (due certainly to the SFR Illimythics), i think i will be worth to try to go from wapsfr to sl2sfr (seems to unlock IMAP on POP port), since wapsfr only open 80 & 8080 port

Thanks @ all you guys, nice work.

Ps: after booting 3 times or plus, the engine seems to work more efficently, such as the rom on Polaris ;)
[Touch Cruise Android Development] bally3:
Wifi support would be nice though!

I thought I read somewhere that the bluetooth and wifi could be fixed easily? I'll try to hunt down the post in the kaiser forum.

I must say with the speed of development and daily releases from rogro and dzo, the last couple of days have seemed very quiet in comparison - just goes to show how spoilt we all are on here! :)
[Touch Cruise Android Development] bally3:
Here's the post I was referring to from Borkata81 on the Kaiser thread, dont know whether it will help or not.
[Touch Cruise Android Development] imfloflo:
What happens no news since 3 days :s

Little break, holidays?

I don't understand why android is so long to boot, it seems he try to unzip system and data img each time.

Cause the 2nd, 3rd,... boot are long too :s
[Touch Cruise Android Development] bally3:
Rogro's busy I believe and since we dont have any more devs we'll just have to be patient. Though its gone quiet on the vogue AND the Kaiser thread today for some reason..

Dont know why yours is unzipping each time.. sounds like data.img isnt saving? Check your card for a 64mb data.img file in winmo.. if its there, check when booting into Android when its starts extracting to see whether its creating a new image file. Barring that, a delete and new files may cure it.
[Touch Cruise Android Development] radem205:
Is it true that the power management isn't working well yet? Because the battery on my phone is empty after 7 hours (normal use).

It would be nice when we are able to charge the battery without first plug in the charger in WinMo.

BTW: The news of dzo in his last post is great! (http://xdaforums.com/showthread.php?p=3341433#post3341433)
[Touch Cruise Android Development] Michel82:
WOW !!! That's is the best news since the powermanagement. Have been waiting for this since i first installed android on my phone. Actually use Gmail and market and sync calendar and contacts!

I do wonder though if the cupcake keyboard is integrated in this version 1.1?!
[Touch Cruise Android Development] excogitation:
...which isn't yet working on Polaris, is it? (my battery lasts 12 hours with screen off)

I'm fairly certain the cupcake osk is now integrated.

Rogro, where are you! ;)
[Touch Cruise Android Development] bally3:
Just tried the experimental build from dzo, couldnt get past start up because of keyboard but looks very promising - cant wait for a soft keyboard addition to see it working! :)
[Touch Cruise Android Development] marcelkordek:
tried newest release from dzo with updated system.img... all works fine, but without a softkeyboard =( hope he will add it in his next update.
[Touch Cruise Android Development] Michel82:
Me three, looks promising. Shame they keyboard doesnt work yet. Also the scaling makes the visuals somewhat blurry.
[Touch Cruise Android Development] bally3:
I appreciate people calling for rogro, But he is a very busy developer outside of xdevs and it is unfair to rely solely on his input to this project.

Are we really saying rogro82 is the ONLY developer left in the Polaris forum??? I do not understand after the many calls made on the old thread by so many for the project to be managed that despite of the hard work by so many on here to support the development that we find that there is only one developer for the Polaris now that the kernel is actually up and running It seems there were more devs present when the project was in decline!

Without anyone coming forward with answers I'm now starting to wonder whether we chased off the other devs by getting involved and somehow making them feel like we were taking over.

COME ON DEVS, WE NEED YOU! :(
[Touch Cruise Android Development] dubbeld00:
Don't know what to do... Want to rewrite the ts driver (already suggested it to do it), but rogro was also planning to do that... also wanted to do some changes DZO also made for the kaiser, but... you might guess it... rogro might do it also.

Also wanted to do some changes related to the wifi driver (only include it in our base) but... rogro might do it also and I don't want to do things twice, that's a waste of time. If we can split some tasks, I'm willing to help, but I really don't know what he is doing and what I can do to help.
[Touch Cruise Android Development] bally3:
hi dubbeld00, thanks for the input. :)

rogro already mentioned a few posts back that he has committed all his changes and that devs should just pick what they want to do and commit their changes also. It is highly unlikely that you would be stepping on his shoes if you decided to do some thing, bu if you are unsure, just post here what you're working on and ask exco to update the wiki to show what driver you're working on and its progress.

We're all aware of what needs to be done, we may differ on whats important in the short term depending on our individual needs, but it all needs to be done whether its sooner or later.

The bluetooth, wifi, gps drivers all need to be worked on. I would just do it personally.
[Touch Cruise Android Development] dubbeld00:
Yes, well I wanted first to create a stable base... Since we are still using a crappy ts driver, that is crappy ported from a crappy first alpha version of the HTC Vogue touchscreen.

My focus isn't on the big things, but the small, create a base, adjust some small settings to get it running smoothly.

The other 3 things will most likely be developed at the kaiser thread (they've more devs over there) so I really wanted to focus on porting (like the battery driver) those things to our device :) also since my time is very limited, and can't test all day to get wifi running.

Btw also thank you for getting/keeping us motivated and make us do things!
[Touch Cruise Android Development] bally3:
Try this apk file to enter the userame and password.. its tricky but works .. just copy and paste into the fields whilst leaving the keyboard program open.

Managed to at least sign into google this way.
[Touch Cruise Android Development] radem205:
@Bally: I have tried your buggy solution and it's working. It is very promising indeed!! Syncing is working fine!

I hope dzo and Rogro will bring us an update soon with a working keyboard and hopefully the system will working as fast as it was with a less buggy screen.

Edit: When I change the resolution in default.txt to 320x240 (right polaris resolution) HaRET hangs during "Booting Linux...". Anyone have the same experience?
[Touch Cruise Android Development] imfloflo:
Yes with the lastest DZO package unable to boot android :s
[Touch Cruise Android Development] radem205:
@imfloflo: When you change the resolution to 320x480 then it's working
[Touch Cruise Android Development] Michel82:
Probably a stupid question, but how did you guys manage to remove the pre-filled password data in the initial setup with this keyboard?
[Touch Cruise Android Development] radem205:
That's not a stupid question, because it was very difficult to understand how to do it exactly :).

First I have cancelled the initial setup. I opened the keyboard application and typed in my e-mailaddress (without @gmail.com at the end). Then I copied the e-mailaddress and launch the gmail application. After that I pasted my e-mailaddress to the correct box and launched the keyboard application again (you can find it in the notification bar) and type in my password. Copy this to the right box (maybe you have to select first the content in the password input box).

When you aren't able to get it working I can explain it in dutch (by pm) so maybe that clear things up.
[Touch Cruise Android Development] Michel82:
Thanks for your help, but i'm having trouble with this last step; There's already some dummy password in the password box. But i can't seem to get rid of it. I have my password on the clipboard and i can append it somewhere to the dummy password, but as soon as i select the password already in the box the paste option doesn't pop up anymore.
[Touch Cruise Android Development] bally3:
hehe.. seriously.. it was a pain.. a good tip.. use the wheel and wheel button more than the stylus to do the tips given above by radem :p

I managed to get it to Google trying to log in - but it gives me server errors.
[Touch Cruise Android Development] radem205:
As far as I know you could select (all) the value by tap and hold on the input box and select "select all". When you launch the keyboard and copy your password you have to tap and hold on the input box again and select paste (the text in the input box have to be selected, so it would be overwrite with the copied one).

I think you have to try something out to let it work, because for me it takes some time too to let it work.

Calendar and gmail works great, except the google market applications ('Unsuccesfull download').
[Touch Cruise Android Development] Michel82:
Using the wheel did the trick. Thanks a thousand! Strange that with the stylus its not possible to paste something as soon as you have a selection whilst you can with the wheel.
[Touch Cruise Android Development] bally3:
Glad it worked for you. :)

At this time its just to keep us poor Polaris users entertained as we've come to a bit of a grinding stop this last week or so. I'm hoping we can get the momentum back next week. In the mean time I'm posting in the kaiser thread to get some co-ordinated effort going again.
[Touch Cruise Android Development] radem205:
Yes, syncing is working great! Actually, I love the resolution (except that the screen is a bit blurry and the ratio isn't correct).
[Touch Cruise Android Development] bally3:
I cant get google mail to sync at all, I get a server error "There is a problem communicatig with the Google servers". But I have found that I can now connect to the internet without togga or APN (now added), which I couldnt do before.
[Touch Cruise Android Development] radem205:
with the latest files from dzo google market is working great, but unfortunatly without a keyboard for the polaris :(
[Touch Cruise Android Development] Michel82:
Maybe some light at the end of the tunnel for us polaris users. Just read an article on engadget about cupcake being available for the dev phone.

As for as i know this last experimantal version from DZO is based on the dev phone romdump. Maybe this new cupcake-read-keyboard-included-dev-phone-rom-dump can be used to create a version for ourselves ...
[Touch Cruise Android Development] radem205:
And the vogue users needs an onscreen keyboard too, so I think (and read something about in dzo posts) dzo will working on it. (http://xdaforums.com/showthread.php?p=3355997#post3355997 and http://xdaforums.com/showpost.php?p=3355319&postcount=2962)
[Touch Cruise Android Development] imfloflo:
Just try the lastest DZO 23-02 package the screen is a little blurry and this is the most probleme i think very disappointing,

boot logo is OK, battery charge seems ok

I see the screen Welcome to the android Dev and the Sync screen to setup sync connection.

Call works, sounds ok.

I find this build a little slow

How can i clear the password fields to setup mine with Q&Dkeyboard
[Touch Cruise Android Development] radem205:
@imfloflo: Look a few post back how to input the password. The screen is blurry and the system slowly because of the scaling.
[Touch Cruise Android Development] rogro82:
Sorry for not being able to post the past week or so, but i have 2 major projects at work which are eating all my available time and most of my spare time... And besides that my gf also needs some attention now and then :)

Hopefully I have a lil more time soon so i can continue my work on this... and have some more free time.

As for some info:

The 1.1 version doesnt include a virtual keyboard ( at least the RC33 release on the G1 doesnt ) and i dont think it will be easy to use the one from Cupcake as it isnt just a small change if im correct.
[Touch Cruise Android Development] radem205:
Nice to hear something from you Rogro. It don´t mind if it takes a little longer to release an update!

I think it's an advantage for the polaris users that the vogue doesn't have a physical keyboard, so I think dzo is working on it (see http://xdaforums.com/showpost.php?p=3355319&postcount=2962)
[Touch Cruise Android Development] rogro82:
Thanks for understanding... Time is my worst enemy at the moment :D

I see DZO is working on wifi / screen scaling etc... is everything working on the polaris?
[Touch Cruise Android Development] radem205:
Yes, everything is working (the scaling the screen is blurry and android works much slower through). With the latest files I notice the following differences compare to the kaiser:

- On the polaris charging is only possible when you charge in WinMo before booting Android

- The leds are nog right yet (already known I think)

- Power management on the polaris hasn't the same results than the kaiser (polaris has more battery drain)
[Touch Cruise Android Development] T1663R:
Hey,

nice release, i tryed nearly every release the last weeks/montzhs and this is the first which gives me a radio signal with my provider simply.

Anyways the screen is back to front but if i did understand everything right this is like this for all you guys right ? or did i do anything wrong ?

Also could someone please post his new default.txt contant for the polaris please ?

greetings
[Touch Cruise Android Development] imfloflo:
@Rogro82 hey

Wifi not working for me but haven't error when i try to activate it like on bluetooth where i had error.

Is it hard to code the automatique network detection ?
[Touch Cruise Android Development] radem205:
Dzo has worked on the wifi support, but isn't working yet on all devices (like he said).
[Touch Cruise Android Development] radem205:
With the latest zimage from dzo the power collapse isn't working very well on my polaris. When I turn the screen off and on again the screen is displaced :s. Anyone else has this problem?

Ps: Try the resolution 336x448 (in default.txt). The blurry screen is almost gone now (and the speed is better (not optimal, but better))
[Touch Cruise Android Development] Michel82:
That is a nice resolution, very workable. I also have the screen displacement. Strange problem, i remember i've had this before with a (much) older version.
[Touch Cruise Android Development] venom035:
Network problems

Hi,

Everything Works great, except the network connection. I think android doesn’t recognize my sim card. (so no contact list, sms, calls, …). Does anybody know what the setting are for my network Mobistar(Belguim).

Do i need to change the default.txt?

Or do I need to update my radio rom (1.58.32.33).

I ‘ve already tried set cmdline "ppp.username=mobistar ppp.password=mobistar" in the default.txt.

My version of Android is 01-02-09_polaris-package and the zImage of 14-02-09.

Thanks!
[Touch Cruise Android Development] rparslow:
Posted this this from my polaris using mobistar

will post my default.txt for you.

default.txt in root of SD card

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

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd.gz

set cmdline ppp.username=mobistar ppp.password=mobistar msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=1

boot

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

Android settings

that need to be added is the Proxy server IP: 212.065.063.143

Proxy Port : 8080

Use Togga to make the ppp connection like in my video and surf.

http://www.ukit.be/android/MOV00920.MPG

For the PIN issue, You need to set in Windows Mobile, "Start, Settings, Phone, PIN, uncheck "Require PIN when phone is used."

I'm using radio 1.65.30.09 Polaris radio in 3LIT3 VI ROM Suite (http://xdaforums.com/showthread.php?t=459826)
[Touch Cruise Android Development] Swifty:
I think there is an issue with no Sim access if you have a Sim Pin set in Windows Mobile, do you have a pin code ?

Take a look in the support thread.. I'm sure I read something about it somewhere
[Touch Cruise Android Development] venom035:
I only need to give in my pin wen I do a full reset of windows mobile not everytime I want to make a call. If this is what you mean
[Touch Cruise Android Development] bally3:
dont think its pin related - maybe radio? can anyone confirm that they have connection with the 158. radios please.
[Touch Cruise Android Development] rparslow:
I managed but, not good, better with new rom, that happen to have 1.65....

re-read my updated post http://xdaforums.com/showpost.php?p=3385801&postcount=848
[Touch Cruise Android Development] agtmxx:
i haven't connections with 158 radio,
[Touch Cruise Android Development] venom035:
Thanks a lot

It works ! I just needed to change the PIN issue