yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
Hi milas, thanks for you answer:

No it says "Enter PIN" "3 attempts remaining" and if i enter my pin it says "Warning: Invalid old password. Please try again.". The 3 attempts dose not decrease then. May this is a bug in the Hyperdragon ROM i use currently. But the better question is, why it works before 01-03-09.

Dose not work, it says "Waiting for data connection". But the download are working in windows mobile without restrictions.
[Tilt, TyTN II, MDA Vario III Android Development] bally3:
What pin are you enterng? is it one that you set? If you have another handset like a nokia, you should try the sim in there to see whether its showing locked or not.

I always get the Enter Pin and Invalid password errors but I dont need to put a pin in when I switch on my Polaris nor do I remember ever setting one but android works fine for me.

As far I know the pin is to do with the sim, so as a last resort, try another sim and see whether it works with that.
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
@Stefan

I unloaded my battery completly. I plugged the adapter into the GKaiser and waited until it was fully charged.

On a certain moment I saw çharge' was below 10mA and the units value was 4103.

I added [...] board-kaiser-battery.battery_capacity=4103 [...] to the cmd-line.

Then I booted Android again. The strange thing is that the battery level was 61% from the first moment.

ds2746: 4101mV -575mA charge: 61/100 (4058 units)

Did I something wrong :eek:?

Edit: In Windows my batt level is about 80% (only some stupid blocks and no numbers which shows me the level)
[Tilt, TyTN II, MDA Vario III Android Development] roadhead:
Yeah there is definitely something fishy going on with this Kernel and its idea of battery capacity.
[Tilt, TyTN II, MDA Vario III Android Development] chaososiris:
No outgoing call

Hi guys i need help in can recieve text messages and incoming calls, i can even text people but for some reason i cant makes outgoing calls though if i put my friends sim it does outgoing calls perfectly can someone help me btw its tmobile
[Tilt, TyTN II, MDA Vario III Android Development] erandhawa:
Make sure u have the correct radio installed. If the problem persists try reformating the sd card and loading all the android files back on then try running it.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Sorry guys, but you misunderstood me there: the kernel param (cmdline) is in mAh, which you can read from /sys/module/board_kaiser_battery/parameters/battery_capacity

In your case tembares it should read 2564 or the like.

In your case, roadhead, it seems that WinMo

does

temper with the values. I will need to check. That would be bad, although if we know it always sets an offset of about 1200, that could be worked around. not optimal, though :-/

I will report back.

By the way, what batteries do you guys have? Standard 1350mAh or larger? And Tilt or Kaiser? That quite important to know.

Thanks so far!!!

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
@Stefan: I have a 1350mAh batt in my GKaiser. Jeeee, do I need to put that in my signature, also :D

I changed the value to 2564. I will have a look at the batt level in the next days to see how accurate it is.
[Tilt, TyTN II, MDA Vario III Android Development] y2it217:
Bug Note

Bug note: When charger is inserted into the phone while in WM and then if android is booted, other person cannot hear my voice.

Not a big thing, but just to let you know.

Build:

03/01/09	Now shows 3G icon, detects carrier name	dzo	android-1.1-01-03-09.zip	post #3840

Thanks for the great work. :)
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Ok seems that the 3rd party battery I used has a R_SNS which is totally off. The KAIS160 battery might even be 20mOhm (then your capacity of 2564 would translate to just below 1300, which is almost a perfect match for a used battery).

Need to see if I can find a way to read that stupid value.

I checked with WinMo btw. and absolutely fine. My "units" stayed where they should stay.. dunno what is wrong @roadhead...

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] AngryUndead:
WinMo has some sort of calibration algorithm. The first time i used android it said 30% battery, WinMo said 18%. Then, it restarted and WinMo said 0%.

Later, I chargedl in Android overnight and it only said 61%. WinMo said 61%. I was upset. I went away for a few hours, left it on the charger, and it said (lo' and behold) 100%.

Later, and another kernel version later (mine own), it seems to stop charging at 85%. I've not gone back to WinMo long enough to fix it. I don't really care.

I can tell you now that having a pre-set value on the command line is probably not the way to go. I will read over the thread again, and maybe the code, and see If I can't do some testing of my own.

It seems obvious to me that the battery knows when to stop and start charging itself because if I watch it when I'm at 85% now (full) it charges for ~30sec then stops, then starts again. At this point we could infer that we're at 100% and set that as the calibration point... this presents one problem. How do we know where 0 is?

I appreciate your efforts to solve this, I'm just trying to stumble my way across problems that you've probably already considered.

Just thinking...
[Tilt, TyTN II, MDA Vario III Android Development] chaososiris:
So i changed a couple of radios some of them got my neot to work but i cant dial or call anyone people can text me and call me and i could text them but i cant call them atleast not with my sim card, when i use my friends sim card calling works just fine someone please help can it be my sim or ? what do i do
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
Hi all,

Now that my nike is fixed (really bad flash ;)) I'm back to work and I've seen dzo has made a first attempt at bluetooth, and I don't know if we're facing a little problem. First, there's no firmware on the system image. I don't know if it's due to restrictions on redistributing the binary file, like it seems to be with the wifi driver (as far as I can read, 421 pages is a little hard), but if it's not, it would be good to integrate it on the image, so people don't have to to modify system.imgs everytime there's an update. Another thing about the bluetooth is... does anyone know if the libraries are the same and it's qemu wich emulates the bluetooth or are there differences between g1 libraries and sdk's?

Regards! Biktor
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Actually, it's really not that difficult, and (if I may say that) I think my approach is good. The thing is:

There's the sensing chip in the battery, which actually counts the current that goes in and out. So there's no need to do that. Then, we know that when we hit 3.3V we're about 5% charge or so and below 3.1V should be considered empty (there's a rapid voltage drop starting from 3.3V and at 3V the battery is supposed to shut off completely to avoid overdrain). When charging, we hit 4.2V+x (x being small) eventually, and when the charge current goes below a certain level (better: is zero, but I think we can't expect that) we know the battery is full.

So: the chip can store lower bound for us, but it cannot store the upper bound.

When we don't know the upper bound, we have to guess (kernel param). Once we have hit a full charge, we can adjust, either we estimated too low (then we will find the chip capacity counter higher than expected and adjust our expectations) or to high (more difficult, because we need to watch out for the 4.2V && <10mA situation).

Anyway, the whole problem is that for the calculation to be correct, you must not reboot, because then the upper bound will be lost (what I was trying to fix with the param) and WinMo might temper with the chip (but I don't think so).

And actually, with this kernel, my phone shows very precise charge percentages as long as I stay in Android and don't reboot.

The previous kernels were assuming that the charge counter in the chip is correct - which is not the case because WinMo doesn't care about it (seems it has some own counting in the HTC drivers). That is why you were seeing a phone die at 25% and charge to only 96% for example.

As with the charging starting and stopping - this is a problem at a higher level I think. The charge current varies a bit and it seems currently the power status is derived from that (positive current == charge, negative == discharge). It should however be possible to fix this because there is a GPIO port telling us the charging status. But anyway, this is just a cosmetic issue.

Hope that wasn't too much text.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] roadhead:
AT&T Tilt, recently purchased on a Refurb special (3 months old maybe) with stock (I believe 1350 mAh) battery.
[Tilt, TyTN II, MDA Vario III Android Development] rogeriojames:
My provider?(Brazil)

Hi all,

That's strange!!

I'm still with problems to do a call

I try all workaround things in my phone like:

Format SD card, Update kernel files, clear data.img, remove pin/pin2, change the radio/rom, etc..

But today i tried something new...i changed de sim card to the another service provider AND THE CALL WORKS!, ALL WORKS, 3g, sms and call!!

My service provider in Brazil is called "OI" and i change the sim card to the provider "VIVO"!!

It's something with my provider?

I changed the sim card to another provided by "OI" too, and, the same crash, the outbound calls don't work...

Any idea? Is something with the frequency band?
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
@Stefan: When I put the value on 1300, with a really empty battery Android says the batt level is 100% :confused:

2564 was better :D

Suggestions?
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
@tembares: how often do you switch to WinMo?

And I say it again - the kernel param is in mAh, and in your case set it to 2564 (the max "units" value * 0.625, or read it from the /sys/module/... file when the battery is fully charged)

With a really empty battery it should say 1% at some point - did it say 100% all the time until it shut off??

Again, it doesn't matter what the numbers are - as long as you let the bat run down once, then charge fully the percentage should be correct for all the use after that (until you reboot, that is).

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] clujalolo:
sorry to go off topic here, but a few pages ago i posted up that my received text messages were going to the top of the screen, and i would always have to scroll to the top. Also it shows on the time stamp that the msg was received 4 hours ago??? Thats what im guessing is causing the problem. I had this time stamp issue in windows 6.1 but i just fixed it. And Last night i re-installed android and it was showing me everything correct. even the time stamps, but the second i went back into windows and came back to android it got all messed up.:mad:
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
your timezone is set incorrectly.

In winmo, say that you are "visiting" london (GMT), and the time should be at GMT time then. Then boot into android, and fix your timezone.
[Tilt, TyTN II, MDA Vario III Android Development] milas:
In Android, go into the Settings app. Choose Date & time. Uncheck the Automatic network time setting. Set all of the time info below - make sure you also choose the correct time zone from the Set time zone menu. After doing this, new text messages should show up correctly.

The problem is that Windows Mobile stores the time in your local time zone, but Android/Linux stores the time in GMT. Android is therefore perceiving that messages are being received 4 hours early because when it thinks YOU are in time 15:00 GMT, a text message is arriving saying it was sent at 15:00 EST (GMT-4), so Android calculates the difference between the two timezones.

You will need to fix the clock whenever you switch between Android and Windows Mobile or you'll have this issue.

I posted this fix when you first asked about it several pages ago, but you've just continued to repost even though other people have explained it as well.

EDIT: I also added this to the troubleshooting page of the wiki: http://www.androidonhtc.com/troubleshooting#text_message_timestamps_are_off and went through the issues on the page and added updated information for many of them
[Tilt, TyTN II, MDA Vario III Android Development] rm2jcp3:
Boot Error

Hey guys,

I have been searching for a post on this for about a month now, and decided I would ask after having no luck with it.

I have an At&t Tilt with WM 6.1, and whenever I boot Android, the black screen with the penguin and all of the little white text shows up and goes down the list, but it stops before it will boot. The last thing it says [ 2.110075] Kernel panic - not syncing: Attempted to kill init!

I have tried installing and uninstalling many times, replacing the zImage with other ones, and other various thing I have read about doing.

I could really use your help with this.

Thanks so much,

Charlie
[Tilt, TyTN II, MDA Vario III Android Development] jerich007:
I'm running Hyperdragon III Raphael ROM dated 9/30/08 with radio 1.65.24.36. Noticed the following things:

- 3G Data connectivity works intermittently. Even I connect successfully vi Toggo, sometimes the browser fails to connect. When it does work, it's great.

- Sometimes calls don't connect, even when the phone is idle.

- Market app downloads work, but I had to re-format my SD card for it work.

When it does work, it's really nice, but just not stable enough for everyday use.
[Tilt, TyTN II, MDA Vario III Android Development] adamc118:
WIFI

When will the wifi be available I have been waiting for a long time!
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
Be patient and it will come !!
[Tilt, TyTN II, MDA Vario III Android Development] clujalolo:
ooo i know this, i tried ur fix. But in my texts it still shows me the wrong time stamp. But its alright, cus now it everything works in sms, shows my msg's properly just the wrong time.
[Tilt, TyTN II, MDA Vario III Android Development] milas:
Oh wow, that's weird. How off are the time stamps? What timezone are you in? (Just trying to figure out a likely cause)
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
Please, do not do this again !

In the long time you are waiting, you could learn this all by yourself and could contribute the WIFI solution to us, the one who are just patient and are very happy with the (small) progress the developers made in their own free time, without asking a dime for all their work.

So, when can we expect your WIFI solution :rolleyes:? I will start waiting for that from now :p
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
There's a new kernel here:

http://it029000.massey.ac.nz/vogue/files/zImage

This fixes the headset audio.
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
board-htctitan.c is missing on the git. I patched the makefile so it compiles again for the rest of the phones, but if anyone can upload the file to the git I guess titan users will be glad to be able to use it :)

Regards!
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
OK, I fixed it.

Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
First, while reading dmesg output I've found out that kernel doesn't recognize parameters ppp.apn, ppp.username and ppp.password. When I've removed them Togga still connects just fine and Internet work perfectly. BTW, haven't noticed any problems with inet whatsoever, though haven't tested speed. I know that AT&T has rather good coverage in my area, maybe that's why Internet is stable on my device.

Second, again while reading dmesg output found that when battery is discharging current is >300mA, which explains why it dies so quickly. Bad radio ROM? I'm using 1.65.24.36 which is in HyperDragon IV IOLITE from 4 February. Haven't had time to search through forum yet, but hint or link how to prolong battery life with Android will be appreciated.
[Tilt, TyTN II, MDA Vario III Android Development] billington.mark:
Guys,

Your all doing an awesome job! Keep it up.

Mark
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Yeah, the mA value might be wrong. I don't really know what to do about it, because the charging current seems correct, but discharge is quite high. Anyway, my Kaiser lasts about 2 days with standard battery, that is ok for me. Maybe we could tune the idle parameters and even use cpufreq (there is a module for MSM processors I think).

The kernel parameters apn, username and password are not in effect with the standard initrd.gz, however, with my patch (I have attached an patched initrd.gz because I see that people are more likely to test then) they work. Unless you use that, they are just ignored, and Togga uses the APN settings from Android. I wonder why no-one ever noticed...

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] philfred:
battery

Hi All,

I have had something stange happen and I am not sure if its Android that did it or not...

I was hammering android the other day and it turned off - I think the battery was flat...

So I plugged my phone in and charged it.

Ever since, it may be coincidental, my phone charges fully - but lasts less than a day - I have ordered a new battery incase - but could Androiod have fubbared my battery?

Thanks in advance

Phil
[Tilt, TyTN II, MDA Vario III Android Development] levanvy83:
The battery is ok for me, i can use 2 or 3 day but the most inconvenience things are the front panel light is always turned on and i cannot sign in to google even i can connect to internet by Togga.
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
Well ive been using android for 2 weeks, and at the sart my battery would be around like 70% after work ,couple text messages throughout the day, now ive been coming home and checking it, its at around 40%, so im lucky if i can get a day out of it,but i mean its still in the works.

Keep up the good work guys!
[Tilt, TyTN II, MDA Vario III Android Development] revolution42:
levanvy83 when you start android from haret make sure the light are off before you boot and they wont stay on
[Tilt, TyTN II, MDA Vario III Android Development] rogeriojames:
Any Help!!
[Tilt, TyTN II, MDA Vario III Android Development] graftark:
Quick question;

Is Togga necessary?

I just loaded up a fresh Android install on my phone and find that I can make and receive calls as well as use the browser with out using togga. My calls go straight to voicemail if the network is active but if I am not using data the calls work.
[Tilt, TyTN II, MDA Vario III Android Development] AngryUndead:
dzo: Any chance of telling us what you merged back in? I'm looking for a sort of more technical discussion so I can try and pick up some of this kernel stuff from you developers so I don't just drop nasty hacks in. Getting the headset to work initially was more blind luck than anything else in the world.
[Tilt, TyTN II, MDA Vario III Android Development] milas:
I combined seidler2547's ppp initrd.gz and dzo's new zImage and posted a new bundle. Unfortunately, aximilation's file hosting script threw errors for me in both Safari/Opera, so I stuck it on Rapidshare. You can find it at http://www.androidonhtc.com/kaiser/latest_builds#bundles (if someone wants to mirror it, feel free to update the link on the Wiki to a non-rapidshare link)
[Tilt, TyTN II, MDA Vario III Android Development] Speaking_On:
This bundle caused a very unusual result for me. It boots android, but when you get the "press menu to unlock" screen, android seems to reboot. I wouldn't have expected that to be possible (since any real reset should dump it into winmo). At one point, it gave me a screen I've not seen before with a set of choices "Complete this activity using provisioning activity, set up wizard" etc. It also apparently has a strange effect on resolution, because the reboot shoes the Android robot, plus half of the head of the robot, just on top.

Mysterious.

This is on a tilt that worked fine with the March 9th. set up. I'll be reverting to that.
[Tilt, TyTN II, MDA Vario III Android Development] aximilation:
Sorry about that, if you remember any of the details I'll look into that and do what I can to resolve that. (doing a little testing myself...)

Edit: I found the issue was due to a max filesize, I just made a fix and am testing it right now. Any file up to 500 Megs should work, I'll update this when it goes through.
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
Build 3-1 seems to be the best for me so far..the resolution scaling helps a lot for gettings apps to work and fit on the screen. I noticed the animations on 1.1 with a lower res is faster than the 1.5 builds as well.
[Tilt, TyTN II, MDA Vario III Android Development] bally3:
Did you use the 1.5 sdk then?

I never got any answers to my posts about whether it was any use, unless I missed them. :confused:
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I just changed the adrc parameters that are sent to the adsp (http://www.faqs.org/patents/app/20080269926) to the defaults. This applies to speaker audio too but it seems ok to me.

To people saying that ppp.username and ppp.password are not used, this isn't true. They aren't kernel parameters I put them there because that's the easiest thing to do. The kernel complains that it doesn't know about them but they are parsed by the setupmodem script. If it works without them then perhaps your carrier doesn't need any authentication.
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
Stefan, in WinMo my battery last with average use around two-three days, that is calls, some browsing, some music. If I'm listening about an hour or two to internet radio through HSDPA instead of music on SD then it last up to day and a half. But on Android it dies within 12 hours even if I keep it turned suspended. Kernel parameter pm.sleep_mode set to 0, which in androidonhtc wiki stated that provides best power saving. >300 mA for discharge seems to be ok, as long as it goes down when device goes to sleep. But from the time that it takes to go down looks like discharge current stays the same when asleep.

Now I see what those kernel params for. My stupid :) Stefan, dzo, thanks for explanation. Fixed back. Will add more info regarding them in wiki after I'll test script on my device.
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
Hi DZO

I have an ISP that does not have username/password (blank). In all of your latest zImages since 27/02/09 setting the username password in default.txt has no effect. originally it didn't show it in the bootup sequence but using the new initrd-ppp.zip file it shows but shows the Username as \ and again does not have internet. (with it set to "\"\)

Toga shows disconnected and then when you connect it shows connected but still no internet.

Also the screen scaling does not work either. (mucks up the robot icon during boot)

When I go back to the 27/02/09 zImage all works again and I have internet.
[Tilt, TyTN II, MDA Vario III Android Development] SpiderX1016:
I see that an update/build came out today. I already have the 03/01/09 on my phone, how would I update to 3/12/09.

Will I lose my files/settings?
[Tilt, TyTN II, MDA Vario III Android Development] bally3:
Just copy the new image over the current one and ignore the rest of the build if you want to keep your settings, at least it will give you usb audio.

I've copied the new initrd.gz over the current one as well but I dont know if that has any effect. I havent lost my settings, I believe that only happens if you replace system.img, correct me if I'm wrong anyone?
[Tilt, TyTN II, MDA Vario III Android Development] mgrom:
PIN

Hi there,

Its my first post in this topic.

Is it a big problem to give a possibility to enter PIN to SIM card ? I realy like Android, but my $#%@#%!! operator blocked sim unlocking....

So I can only call 112 :)