yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] Mormy:
I'm quite sure, this is my default.txt ;)

#alloctest 0x2000
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
# ppp.password - The password used to connect to the network when dialing
# ppp.apn	- Set apn of your provider
# ppp.nostart	- Set ppp.nostart=1 to disable starting the ppp connection on boot
# 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 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=tre.it ppp.username=none ppp.password=none msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend mddi_client_vogue.vsync=0"
boot
[Touch Cruise Android Development] radem205:
this is mine:

#alloctest 0x2000
#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
# ppp.password - The password used to connect to the network when dialing
# ppp.apn	- Set apn of your provider
# ppp.nostart	- Set ppp.nostart=1 to disable starting the ppp connection on boot
# 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 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htcpolaris.panel_type=1 ppp.apn=live.vodafone.com ppp.username=vodafone ppp.password=vodafone pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 clock-7x00.mddi=0xa51"
boot
[Touch Cruise Android Development] vilord:
Mormy, I'm sure you are not the only one... Just the only one who's spoken up. Your phone must have a 4th different screen type, or perhaps it interfaces in such a way that the standard code isn't working with it.

Have you tried setting board-htcvogue.panel_type= to 1, 2, or 3? It *may* work differently than the polaris panel types, but it also may not work at all...
[Touch Cruise Android Development] radem205:
Good job dzo! With this zimage the battery went down to 85% during one night (8 hours idle). The battery was fully loaded yesterday evening. Good job!
[Touch Cruise Android Development] worstenbrood:
Same here !
[Touch Cruise Android Development] imfloflo:
Nice found hope it will help devs to find issues.

Cause this week no many progress on wifi done :s

I propose to choose a theme to working on for each week

this week Wifi

next GPS

next camera :p
[Touch Cruise Android Development] Michel82:
I have no clue how difficult it is to fix that interrupt problem, but that looks very promising t me meknb!!! Great work
[Touch Cruise Android Development] bally3:
Nice one meknb :)

Can you post how you got to the this stage, what you had to do or change so I can bring i n others to take a look?

Thanks.
[Touch Cruise Android Development] radem205:
Battery management is now very good (thanks to dzo's latest work!!), but when I look in WinMo the difference between Android and WinMo is about 20%. So unfortunatly the battery indicator in Android isn't optimal yet. This explains why Android power offs the phone when it's between 15% and 20%.
[Touch Cruise Android Development] bally3:
RE: wifi and whats changes were made in the kernel.

Posted by Addisu on wifi thread:
[Touch Cruise Android Development] cbandarrinha:
Silly Question?

I'm almost afraid to ask but here it goes:

What's the difference between panels on Polaris?

The dzo's zImage was meant to test the panel, right? How does it improve the power consumption?

Probably these are just silly questions but I had to ask because I'm trying hard to understand the things that relate to Android on Polaris.
[Touch Cruise Android Development] vilord:
The panels are identical except that some are made by Sony, some by Topoly, some by Samsung, some by Hitachi. The only difference that we're running into is that the various manufacturers use different commands to turn on and off the panels.
[Touch Cruise Android Development] meknb:
Bally yes thats all i had to do Wireless extensions,i think the problem could be with the irq the error coming from esta_drv.c i'll post some more info when i get home.
[Touch Cruise Android Development] bally3:
1=Sony 2=Topoly 3=Topoly (according to our default.txt

I think 3=Samsung - I believe that Samsung make the POLA200 screens.

We need to do a bit of delving...
[Touch Cruise Android Development] worstenbrood:
I have a pola100 but i got my screen replaced some time ago because it was broken, i use paneltype 3 also ..
[Touch Cruise Android Development] imfloflo:
How to know which panel we have ?and if we have pola100 or pola200?

We must list all different combination to have all case.
[Touch Cruise Android Development] bally3:
As far as we know, the POLA200 are the XDA Orbit II's.

The others are POLA100.
[Touch Cruise Android Development] :
Hi Jesee,

On a random basis, either on incoming or ougoing calls (both) I have no sound and cannot hang up the call until a soft reset. I thought it was because of the "grid lock" feature, so I disabled it and keep testing.

I'm still using the bundle from 08-08-2009, do you recommend to move for zen-hero-090809.zip ?

Regards,

JM
[Touch Cruise Android Development] imfloflo:
Ok it was in the wiki at Polaris clone section

Now for identify the screen? is there any systeme cab under windows mobile? ?
[Touch Cruise Android Development] radem205:
Again I would say that the new zImage from dzo is very great!!! Batterylife is really improved!! This was one of the biggest issues of the working parts of android. Great job! Only calibration isn't optimal yet.

ADB is working now, but I have to connect the phone to the pc before running android (like Bally said earlier). Then it works fine!
[Touch Cruise Android Development] :
Im not an expert, there are several here that could confirm/verify my comment...

Your first line is "#alloctest 0x2000 " I believe that is the mistake, which also happened to me.

Instead, your first line may be only "#" which is not necesary but provides a better looking but you must make sure that "alloctest 0x2000" is there in a line before "set RAMSIZE..."
[Touch Cruise Android Development] imfloflo:
"#" in the first letter of a line is to comment the text so the line will no be read by haret.exe and other files
[Touch Cruise Android Development] Mormy:
well, I am "hard head" (italian way to say), so I decide that I MUST do some test. After a while I delete every android file, I didn't format the SD because I don't want to install all over again in winmo.

I put inside the 08-08-2009 package with dzo latest zimage and my STARTUP.txt, but...I change to polaris.panel 3:

Android works very well:

calls in/out, sms in/out, I set up my apn and data connection works without modem, neocore 22.8fps

But what surprised me most is: I could read network operator list :)

'til now, every time I tried to access to this menu I receive an error. Now I could see the carrier list, my carrier is always blank, but I don't mind so much.

I'll try to use this combination as long as the battery life, then I'll report you ;)
[Touch Cruise Android Development] Septavius:
Good work!

Looking at the return value from "request_irq", it's "-16" which equals "-EBUSY". According to the "request_irq" manual: "It's not uncommon for the function to return -EBUSY to signal that another driver is already using the requested interrupt line."

So it appears the interrupt line is already in use. Looking at the source code the "request_irq" call request sharing (IRQF_SHARED) the interrupt line, but that doesn't help if the device already registered with the interrupt didn't request irq sharing.

Guess we'll have to find which device already is registered with the irq.

UPDATE: Looking at the kernel code it seems like compiling a new kernel with "CONFIG_DEBUG_SHIRQ" should give us the information we need.

UPDATE 2: So here's what the kernel debug gives us:

Seems like the "polaris-gpio" doesn't want to share its irq with the wifi device. Hopefully someone with more kernel experience can get some more out of this.

UPDATE 3: The IRQ is defined in the wlan kernel module. "TROUT_IRQ = MSM_GPIO_TO_INT(29)". So "29" is the Kaiser wifi GPIO from http://wiki.xda-developers.com/index.php?pagename=Kaiser_GPIO. The question is if it's the same on the Polaris. We'll have to do some tracing.

(NB: IRQ definition :http://en.wikipedia.org/wiki/Interrupt_request)
[Touch Cruise Android Development] briggs81:
My data connection is still borked 50% of the time. Thinks it's connected but actually doesn't work.
[Touch Cruise Android Development] radem205:
Same here.
[Touch Cruise Android Development] freddycs:
Battery test

My phone was fully charged at 5am this morning and i've been on and off sending and receiving sms, emails, and making few calls. now is 3pm and the battery level is at around 46%. seems like improvement in battery management with dzo's zimage.

i'm using zen-hero-090809 version. still having problems like:

1. sometimes it become laggy but sometimes become very fast.

2. i have contacts sync with google. but when someone calls in, only caller's number is appearing, but not the name, although the caller is in my contact list.

3. when send out sms, it returned with status saying that sms failed to send out, but the receipient actually received the sms.

4. it is very hard to wake up from speep mode..... need to press a couple of buttons to wake it up.
[Touch Cruise Android Development] bally3:
Ok.. early morning info.. theres some info here for wifi:

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

and an interesting chat re: TROUT_IRQ MSM_GPIO_TO_INT(29)

might be worth a read:

http://ibot.rikers.org/%23htc-linux/20090117.html.gz

Also putting this up here if its any help:

http://android.git.kernel.org/?p=pl...ff;h=b625cb49a462741ce4550e9bd9d593d051af37c8

and this:

http://android.git.kernel.org/?p=pl...ff;h=24f0be0e9a23b41683dea619ead9739615c83fac
[Touch Cruise Android Development] bally3:
Interesting snippets of conversation from this log:

02:40.56ali1234i think there's a gpio on wizard that basically selects whether the SDIO sees the card or the wifi module

02:41.35ali1234it's definately GPIO related - i just copied *all* the regs from an EOL boot and wrote them from the mmc init

02:41.43BabelOali1234: megasim, i don't know

02:41.59BabelObut on arte, there is two gpio to swit mode 0 1 2 3

02:42.10ali1234i think we were missing some other init stuff too

02:42.12BabelOeach one have a specific function

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

03:12.50tmztand I think the wifi/sd gpios are actually chip selects, it's not expected to only use one or the other, only that only one will respond to commands

03:13.04tmztand the artemis probably doesn't have the megasim hardware

03:13.46ali1234only the GSM can talk to the sim using the normal way

03:14.06ali1234yes i agree about chip select: it's GPIO for CE

03:14.31tmztis the wifi spi or sdio?

03:14.37ali1234sdio it seems

03:14.59tmztwhat happened when you programmed the registers the same way as eol

03:15.20ali1234it worked perfectly

03:15.43tmztok, this is artemis not wizard?

03:15.48ali1234this is wizard

03:16.49ali1234i'm now searching to see exactly which gpio needs to be set

This is from:

http://ibot.rikers.org/%23htc-linux/20090227.html.gz

Interestingly this if for linux on the Wizard...and it mentions Artemis, but it may be similar.
[Touch Cruise Android Development] radem205:
With the latest files (ION) I have some problems with incoming and outgoing calls. Sometimes it works great, but sometimes when I want to pick up a phone call I don't hear the person on the other side of the line. That person doesn't hear me too.

@Vilord: Can I make a log for you to see what the problem is? I have ADB up and running :)
[Touch Cruise Android Development] worstenbrood:
same problem here
[Touch Cruise Android Development] Mormy:
Battery Test Result

Ok, this is the result of my battery test:

Yesterday I put a fully charged battery about at 18pm.

I setup 2 email account (autocheck every 30min), download with market 4/5 progs and set weather widget in autoapdate every 2h (but I don't think it works).

I made/receive some calls and send/receive sms. I used the browser a coupple of times to read some news (I don't understand how to close it :( ).

The phone shutdown itself at 14:30pm
[Touch Cruise Android Development] briggs81:
I think this happend to me too. Took awhile before I started having problems. I rebooted and it was fine. Might have had something to do with me screwing aroudn with sound settings though..d on't know. Have not had the problem for a day or so.. though data is still wonky. Keep forgetting to make logs!
[Touch Cruise Android Development] vilord:
Any logs are helpful... The no sound in/out issue could be in either of two places. First place is in the RIL where it turns on and off sound it might not be turning on sound.

Second place is in the kernel, since we don't really have a fully configured audio device yet it might sometimes ignore the command that comes from the RIL...

We'd have to do some more diagnosis, too bad it is only occasionally, otherwise it would be easier to fix...

Anyone having other radio related issues? I've heard rumblings that for some the phone app crashes just when trying to dial.
[Touch Cruise Android Development] radem205:
Thanks vilord for your answer! When I can't make a call due to an audio issue, is it better to create a logfile of the audio (if this is possible??) or the radio?
[Touch Cruise Android Development] vilord:
i'm not sure about an audio log.

Actually I think a dmesg and a radiolog would be good.

adb shell dmesg > dmesg.txt

adb logcat -b radio > radiolog.txt
[Touch Cruise Android Development] meknb:
Great work life.Thanks for the input Septavius.It's looking promising.

How did you manage to load the driver life did you change the gpio??

All these command timed out error's are they comming from wpa_supplicant ??
[Touch Cruise Android Development] freddycs:
battery test result

Based on Android ION 8-8-09 version.

1. Fully charged at 1am and put it on sleep mode.

2. Woke up this morning at 6am, battery level at 95%. Sync is off I believe, as I started with fresh Android, no data connection yet.

3. It's been a busy morning for me, a lot of incoming and outgoing calls and sms. Setup data connection and sync to my Google account. Downloaded couple of games and apps from market. At 12 noon, battery level at 50%.

4. Went back to winmo, battery level is only 35%.

Seems like the battery now lasts longer in Android, good work!

Btw, I did encounter phone dialer error once, the dialer program crashed and i need reboot android in order to make calls.
[Touch Cruise Android Development] pmcosta:
Im having the same radio/sound issues from start. While accepting or making the call sometimes the sound works, sometimes don't.

This happens to all sound, input and output.

I have a POLA100 with R 1.58.25.14, should i upgrade?

I miss so much the wifi feature!

Keep up the good work.
[Touch Cruise Android Development] bally3:
I think we are once again falling into this circle of different radios, roms and now, different Android builds in use.

Following conversations with life02 and vilord - both who are using 3lit3 VIII naked rom, I have now switched to that rom.

I am also using a 1.59 radio - mine is 1.59.44.02 - I know other users have had luck with 1.59.42 and 1.59.46 radios and I believe location plays a part in this as does varying reports of battery life.

For the testers of the kernel on this thread, I suggest that you also stick with this rom and radios for testing purposes UNLESS you are not experiencing any of the reported issues with calls and data issues.

I accept that it is equally important for us to know whether other or newer radios are better for Android use but I do feel that it is not fair on the devs if we decide to use different radios and roms and then report issues with Android which may be related to a rom or radio and expect the devs to fix it.

I have been testing a few roms myself, but I will be going back to my Android friendly rom for development use.
[Touch Cruise Android Development] radem205:
@Vilord: Attached you will find a log after a failed calling (I sent it via email too). After picking up the call I don't hear anything (like the audio is muted).
[Touch Cruise Android Development] SuperJMN:
New zImage available:

http://code.google.com/p/vogue-andr...+Filename+Summary+Uploaded+Size+DownloadCount

Testing.
[Touch Cruise Android Development] dzo:
Only kaiser changes in there I'm afraid.
[Touch Cruise Android Development] life02:
The kaiser gps changes will benefit the Polaris.
[Touch Cruise Android Development] iseeka:
Can anyone help me?

is there a file i should delete or something else i have to do before atempting to install a new version?

example: i installed android-1.5-2009-08-04 OK changed zimage OK ... but the every other version wont start... even coping again 08-04 doesnt start..

any clue?
[Touch Cruise Android Development] iseeka:
i deleted everything (except foldes) and no start ... i guess thats not the problem
[Touch Cruise Android Development] life02:
You shouldn't have any folders.. everything should be in the root of your sd card
[Touch Cruise Android Development] iseeka:
no entiendo nada..

i tried a lot of combinations.. i need a clue
[Touch Cruise Android Development] iseeka:
i meant i deleted all the files in /storage card trying to make a clean install, but kept folders i had as igo, etc

i copy all the files of a bundle ..android-1.5-2009-08-08.zip to /storage card

i use "Use my latest Default.txt for better 3D performance (Thanks dzo)" with panel 1

no start (with any bundle.. it reach nearly the end but no start)

tried latest zImage-14-08-09 and it is worse

e2fsck: superblock invalid (...)

e2fsck: bad magic number in superblock (...)

superblock could not be read or (...)

failed to mount data (...)

and stops
[Touch Cruise Android Development] iseeka:
tried android-1.5-2009-08-04 once more and booted..

maybe not being usb connected?

do i have to try several times untill one boots?

have done exatly the same (maybe usb connected cant remember) and didn boot

wnt touch anything untill i guess whta happens
[Touch Cruise Android Development] szsoftware:
@life02, @dzo

In the latest git commits a have seen changes on arch/arm/configs/{msm_defconfig vogue_defconfig}.

I always build the the zImage with vogue_defconfig.

It's a little confusing when different configs in the same context are maintained.

Life, is msm_defconfig always your default config?

Wouldt it be hard to have only one (generic) defconfig?

I suggest to cleanup the files in arch/arm/configs.

There was long time the absolutely obsolete htcpolaris_defconfig in it, while we had to use vogue_defconfig.

Since vogue_defconfig is used for vogue,polaris,kaiser, etc. it should not have that specific "vogue" in the filename.

Maybe you should merge the values into msm_defconfig, dzo?

Martin, don't be afraid that we forget the origin of many things you brought to a working state: the vogue branch of the kernel. We keep always in mind that many working things are derived from a lot of vogue stuff in arch/arm/msm :-)

Thanks and CU,

Sven
[Touch Cruise Android Development] vilord:
iseeka: It sounds like your data file didn't have a chance to finish creating, it takes a long time.

szsoftware, we all use vogue_defconfig too. it would make sense to change it to msm_defconfig or htcmsm_defconfig or something.

Those having problems with answering calls, I spoke with martin last night and it is definitely a problem in the audio code of the kernel. He may have time this weekend to look into it (it happens on his kaiser too).

In the meantime, the kaiser people say that if you make a call to voicemail first thing when you start up the phone, then the no-audio problems usually are not present.

-Jesse
[Touch Cruise Android Development] radem205:
It's true when you first call somebody the problem disappears. It's a good workaround!
[Touch Cruise Android Development] briggs81:
I seem to be ok lately with latest files. I get a cellular signal and data connection after i unlock home screen for the first time.

calls or data have not cut out on me. have not been thoroughly testing it lately though, but it defiantly was better then a few days ago!
[Touch Cruise Android Development] freddycs:
yeah~ the latest ION version is working very well. i'm currently using it full time and i'm loving it. when BT, camera and wifi start to work then it will be perfect.
[Touch Cruise Android Development] szsoftware:
Different Timesetting between WinMo and Android

Hello folks,

I have a very annoying problem concerning the timesettings.

In winmo I have "GMT+1 Berlin,Rom", time is e.g. 13:00

When I switch to Android the time is set to "GMT+2, Central European Summer Time" (Amsterdam,Berlin), time is 15:00

The setting in one of both OS inluences the other in the way that I never have equal timesettings in Android AND WinMo.

I also don't know, why in winmo is "GMT+1" for my timezone and in Android GMT+2. GMT+1 is normal (wintertime) and GMT+2 is European Summer Time. Maybe Winmo shows it incorrect but handles summertime switching correct.

However, setting it to GMT+2 (Kairo) in Winmo did not the trick.

Any solution hints?

Thank you,

Sven
[Touch Cruise Android Development] pananza:
I have the same problem. I think it's related to the two OS'es storing different times in internal hardware clock. Android assumes HW clock is UTC, while WinMo assumes HW clock is localtime, hence the two hours difference when you go from one to the other.

I think you'll just need to live with it.
[Touch Cruise Android Development] vilord:
Are you using the automatic timezone settings in android?
[Touch Cruise Android Development] bally3:
I have this too.. Mine chooses British Summer Time +1 but its an hour ahead, but if I get a data connection (and IF I get a data connection - I struggle to get data connection and when I do, I cannot connect to Market for life for me on any other build apart from the first themed ION build mssmison), It usually sets the clock back an hour and corrects itself.

Try it. :)

ps. Any help to understanding why I cant connect to Market with any other build apart from the one I mentioned above, would be greatly appreciated.
[Touch Cruise Android Development] iseeka:
how embarrasing.. lol

Now i´m going to use it regulary so.. iwant to DONATE to help improve (wifi,bluetooth...)

Who should i donate? I also want (again) to thank everybody for the effort

by the way wht is your opinion about " HTC Hero rom / Android+ Sense UI for HTC Polaris, WORKING!"?
[Touch Cruise Android Development] bally3:
Donate to dzo so he can purchase a Polaris and help us with the development work (also he can get camera working on the Polaris) :)
[Touch Cruise Android Development] freddycs:
yes, we have hero version with sense UI,but it's still buggy and slow.

by the way, I have just donated $15 to dzo.
[Touch Cruise Android Development] bally3:
Thanks freddy :)

Just seen the update on the donations thread. Hopefully we can get a Polaris to dzo soon!