yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
well i installed 3-12-09 build and im experiencing the constant network drop, and yes i did the ATT APN but it happens atleast every 15-20 secs, so i guess im back to 3-1-09..ughh
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Not even that, you'ld have to replace or delete data.img.

Actually, my provider doesn't need password and login, so I used * for both. I don't know why so many people have been trying to get an empty string in there?

Actually, the default.txt says 1 is best power savings. (And I think it's correct because with 0 the led is mostly green when in sleep and blinks red, but with 1 is stays red and sometimes goes green shortly and then red again.)

You're right in that setupmodem.sh uses them, but does setupmodem.sh connect you? No it doesn't (at least it didn't for me). This is because toggle.sh has to trigger it in order to actually start the ppp connection. This triggering is now accomplished by my start_ppp.sh script in the initrd-ppp.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Oh, and one big thing: When you use the initrd-ppp version, you must not start Togga because it messes the whole thing up (at least for me)!

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
Great work seidler that works :)

I was using \"\" in there as it was in previous roms and worked up until 27th.

looks like the * did the trick I have internet back. dont know where thats shown anywhere but does work

Thanks

Wombat

Update: This did not Work. I must have been running the old zImage. When I put the new one from 13-03-09 it is back to not working again.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Aximilation, your upload site still isn't working for me...

Can you add a realtime progress bar or something so I at least know something's happing? I get a connection reset error. You're using PHP, this is free: http://www.sibsoft.net/xupload.html

The new image seems to work but haven't tested audio. My old data.img file seems to corrupt the screen so back to importing my contacts I guess.. not a big deal though.

I've uploaded the latest build here: http://hyperfileshare.com/d/085823f3 since I can't use Aximilation's. You will hate the dancing animal ads but you will love the no download wait or premium access annoyances.

So can at least one person help me with customizing the kernel? Even just how to chroot into the build (x86 -> ARM) without getting a chroot: cannot run command `/bin/bash': Exec format error? I'm willing to work on Android, just not experienced in that area.
[Tilt, TyTN II, MDA Vario III Android Development] levanvy83:
I did, but when device came to sleep or i pressed RED button, the light turned on constantly :confused:.
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
I just tried this update and I still don't have Internet :~(

I thought using * as username/password in default.txt worked but it still doesn't work. I must have still had the old zImage (thought it was strange that I only had G icon again.)

the 3G icon now shows but only outgoing lights in the 3G icon rarely does the incoming light.

I am using the following in default.txt with Aximilations release

set cmdline "board-htckaiser.panel_type=0 ppp.apn=exetel1 ppp.username=* ppp.password=* pm.sleep_mode=1 mddi.width=312 mddi.height=416 no_console_suspend board-kaiser-keypad.atttilt=0"

When booting I no longer get waiting for PPP which appeared in 27-02-09 version

I get username=*

password=*

apn=exetel1

Also still getting the 1.5 Android Robot's (robot icon moves down)

Anyone got any other ideas?

Wombat
[Tilt, TyTN II, MDA Vario III Android Development] excogitation:
I suppose you already had a look at this.

Thanks for clearing that up.

About the battery problems ... are you sure it stops charging in Android?

On Polaris it is now in a state where it doesn't because 100% Win <-> 96% Android - but goes up to 97% when plugged in in Android (where imo it should stay at 96%).
[Tilt, TyTN II, MDA Vario III Android Development] y2it217:
If button lights are turned off when booting android, they will never again turn on, in my tilt..

pm.sleep_mode is 1 in my default.txt, If that might help..
[Tilt, TyTN II, MDA Vario III Android Development] levanvy83:
Thanks but i also using tilt and pm.sleep_mode=1 either, but the panel light came back when device went to sleep mode and some time the button light turned on constantly when i plug charge :confused:

Another question: where's default path for picture application in android?
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
Same for me.
[Tilt, TyTN II, MDA Vario III Android Development] coincoinlapin:
same here ... :p
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Hmm, when I was starting up lately I had removed the APN from the Android settings and it wasn't connecting for a minute or two. So I added the APN and instantly it was connected. edit:Actually, that's what it does: whenever ou remove the APN the 3G icon disappears, when you add it it shows up./edit

Another thought - are you on GSM network or CDMA? I'm on GSM.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Yeah, thanks, I still need to check, but it's not for calculating the R_SNS ;) Maybe we can use it anyway. I'll see.

Did you test my new kernel with the battery fix on Polaris (according to these instructions)?

Does it change anything about the battery behaviour? Do you even have the entries in "dmesg"?

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
Ok my post at http://xdaforums.com/showpost.php?p=3458994&postcount=4257 was not correct.

Can someone tell me what was changed in system.img since the 27-02-09 one?

Ive can have not connection to my mobile provider if i use the system.img after 27-02-09. Android tells my "No Service", i have not signal strength, can not make phone calls, not send sms and i can not connect to internet. But with 27-02-09 all this works and Android shows my provider "vodafone.de".

What i did to test it. I extracted all (expect the data.gz) from the new 12-03-09 image and replaced the system.img with the one from 27-02-09. And i have service. Then i extracted all from 27-02-09 (expect the data.gz and the default.txt) and replaced the system.img with the new one from 12-03-09 and i have NO service.

Specific for me is that i can not disable my SIM pin. Ive tryed it also with an old phone, but it tells my that it is not supported. But why i need to do this, when it can works as it did in the 27-02-09 image.

Anybody have an idea?
[Tilt, TyTN II, MDA Vario III Android Development] excogitation:
I didn't follow the steps (since I think it should just work without calibrating - or calibrating on the go).

Also we don't have an OSK atm and I don't trust charging to stop in Android (better safe than sorry).

It does work (dmesg.txt) - e.g. (booting with 44% displayed in Win):

[ 31.218005] ds2746: 3738mV -407mA charge: 100/100 (2643 units)
[ 45.100262] ds2746: 3745mV -410mA charge: 99/100 (2640 units)
[ 51.082536] ds2746: 3752mV -321mA charge: 99/100 (2639 units)
[ 57.240017] ds2746: 3767mV -229mA charge: 99/100 (2637 units)
[ 59.950039] ds2746: 3772mV -226mA charge: 99/100 (2636 units)
[ 62.889579] ds2746: 3772mV -216mA charge: 99/100 (2635 units)
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Ok, thats great news because it means it work on both polaris and kaiser.

It seems you know little about Li-Ion battery technology, but I can tell you: calibration on the go is not possible because the only fixed points are empty (3.0V) and full (4.2V). In between you can make guesses, but nothing is sure. And the charging is not software-controlled, it must be hardware controlled for safety reasons. So there is no difference between charging in WinMo and Android and with the phone turned off.

Anyway, the most important think about this patch even without calibration is that android will warn you/shut down properly when your battery is really empty (before it used to think that there is plenty power left and eventually the hardware would say no and just shut off).

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I left Android running overnight (phone is sleep mode) and in the morning there was no service. Don't know if it's a fluke, new issue or what but does anyone know how to restart the provider search? Under Android's system menu I was getting an error about finding providers maybe there's a way (terminal preferably) that I can force it to restart that service without rebooting?

To correct what I said previously about using my old data.img file causing the screen colors to be corrupted, that's not it. The new initrd.gz is causing corruption for me but I got it to work fine with the default settings in default-kaiser.txt however I can't get it to work again. Old initrd and default-kaiser.txt but new everything else is okay.

Most important however is that my phone signal seems to work with the old initrd.gz whereas the new one causes no signal every few seconds. Let me know if it's just me
[Tilt, TyTN II, MDA Vario III Android Development] aximilation:
Gah, it's because of a config where godaddy won't let php upload a file bigger than 2 megs, I changed the config, but it seems like it's still not working correctly, not cool. I'll take a look at that realtime progress bar, I was thinking of something like that, thanks!

In android news, I finally got a new micro SD card, so I'm going to start running android again, I haven't had a working card since we were running .08, I'm excited! Thanks all!
[Tilt, TyTN II, MDA Vario III Android Development] excogitation:
With on the go I meant that the data should be collected (and improved) while using it.

Some profile (for a standard 160 battery) should suffice to get started.

Glad to hear that.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
@aximilation, yea I spent like 2 Internet minutes (like 1/2 hour in real time) looking for something while it uploaded that didn't need ASP or patching the config files. Seems pretty spiffy and I didn't find anything else that was easy to implement.
[Tilt, TyTN II, MDA Vario III Android Development] graftark:
Awesome :D
[Tilt, TyTN II, MDA Vario III Android Development] iPirate:
Still using the 01-march-09 build and noticed a few things...

when i loose service, it doesnt come back :confused: i have to reboot

calls still iffy, others are not always able to hear me

just today android "crash" im not sure exactly what happened. I put the phone in my pocket, when I took it out it was on the loading screen and kept loading until i pulled the battery.

when I rebooted my login was not saved and i lost my contacts :confused:
[Tilt, TyTN II, MDA Vario III Android Development] excogitation:
4440 units Pola160 fully charged. (100% starts with 2643 units)
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
new build

using At&T tilt 1.7xxxxx radio .

anyway the echo issues i have always been complaining about is gone in the new build!

the only problem I have now is the lights on the hard keys and keyboard is always on when running android... the only way i can turn them off is by hitting the end call key... is there a fix for this ?

small issue- when talking on the phone with a friend i got another incoming call at the same time... i was able to switch over to the incoming call but when i switched back I could not hear my friend but he could hear me
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
For whatever reason I cannot download new version from rapidshare so I started playing around with what I got. I am currently using the 3.1.09 version BUT I overwrite the initrd.gz and zimage files from the 2.23.09 version. Now I have highly usable phone. My instant on data conection is back, I can make and recieve useable phone calls now, and I can download from apps from the Market. I love my phone. Now as a question can someon explain what the individual files that make up android do I want to know why this made what I've been wanting

Edit: I just copied over a newer version of the zimage haven't made or received any calls but it looks like the initrd.gz file has the connection stuff that I so desperately wanted back
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
battery folk: do remember that we can get temperatures from the touch screen - this'll probably be necessary for accuracy.
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
Hi Stefan

I have tried removing the settings from the default and it hasnt made any difference. The same thing happens in the android setup if I have an APN setup then the 3G icon shows. Looking at TOGA also confirms that the internet is connected and I have an IP. Even though it looks like it is connected there appears to be no incomming data but outgoing appears to be flowing (judging from the 3G icon only)

still no internet

Thanks

Wombat
[Tilt, TyTN II, MDA Vario III Android Development] krisje8:
I haven't followed the android updates for about 2 weeks, and I tried the latest dzo/seidler package.

It keeps bugging me about my data connection that it's turned off, and when I press ok (to ignore it, I don't want to turn it on) it will reappear in a few seconds.

How do I get rid of this? I do _not_ want a data connection. I'm waiting for wifi.

Also, and I think mainly because of this reconnecting thing, my phone connection in upper part of screen goes on and off and on and off...

Also, when on sleep mode 1, Neither of the screens work. The samsung screen displays stripes after waking up, and the 2 topoly's got strange graphics. sleep mode 0 works fine though.
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
Thats exactly what happened to me when i installed the latest one, my network signal came and went every few seconds so i went back, i couldnt stand it. lol ohh well
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
okay.. I really messed up my battery chip...

pretty sure it completely (or nearly) ran out of battery in android at some point - android said about 30% remaining (maybe - I forget exactly)

Booted into windows mobile (that said a few (4?) percent remaining), so I charged it. Left it overnight.

Next (this) morning, it said 21%. Went out bowling (without my phone), came back and it was at 18% (charging this whole time).

Took it to the library with me, and it quickly (maybe just a bit faster than it normally drops in % remaining/time) dropped to 8% - and hung there for a few hours. When I took my break, I used it (with the wifi) to browse some internet... from 8% it had dropped down to 4%, and winmo kept deciding to shut down (I kept restarting it).

By the end of that, it was at 2% (another place it hung for several hours)... it's now at 1%...

it seems that the battery is fine, it's the ds2746 that managed to completely bugger itself up...

what's the recommended practice for resetting this thing?
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
I was running 12.03.09 build for two days now.

1) Now ppp parameters in default.txt are being processed and phone connects on its own. Haven't noticed any issues, internet works fine. Haven't tested speed though.

2) Power saving works much better when pm.sleep_mode set to 1, as Stefan said. The only problem is that contrary to Stefan's words both wiki and default.txt say that best powersaving is when pm.sleep_mode set to 0. Actually, now only default.txt says that :)

3) Screen resolution - tried native resolution as well as whole bunch of non-native. Mostly out of boredom - haven't had at that moment access to network or anything else :( Nevertheless, I've found that native resolution work more or less fine for majority of apps with huge advantage of clear picture, no blur. But seems like only in native screen resolution rotation orientation is broken.

Sometimes notifications for events like vociemail and calls get broken - instead of melody phone just beeps and I can't change them. Probably due to battery dying before OS can properly umount filesystems?

Haven't checked in new bundle yet, but with kernels 09.03.09 and 10.03.09 people on other end could hear echo of their voices regardless direction of the call. On my end sound was good.

Upd: just got opportunity to test sound during call. Echo looks like is gone, but when getting second incoming call then phone beeps very loud, I think through back speaker, instead of quiet signal through phone. Now need to check sound in call through headset. Will give feedback when done.
[Tilt, TyTN II, MDA Vario III Android Development] freebornman:
i have a problem right now after using of android: after reset of device i can't get to any of my files on storage card.
[Tilt, TyTN II, MDA Vario III Android Development] anubius:
I had the same problem. I was using Android and then it restated. After restart in WM it was 4% so I've shut it down left it charging from USB, but have not done it completely. So when I turn it on I saw that battery in WM was at 50%. When I tried to charge it from wall charger it was refusing to do so. After that I plugged it to my PC and it have charged it to 100% and it looks like it is working fine now. So I have no idea what it was. Hopefully you will fix yours.
[Tilt, TyTN II, MDA Vario III Android Development] kolya82:
Pls help me!i dont know how to return to WM from android!thank!
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
Just do a soft-reset.
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
yup - drained it down all the way, charged it back up overnight (my AC charger has a dud wire, so I always charge by pc), and it's at 100% now.
[Tilt, TyTN II, MDA Vario III Android Development] agentofboom:
battery strangeness

I too have had the battery freak out in 3 diff ROMs and almost every Android release.

Its totally at random (it seems) . Not apparently related to time on, running apps, temperature, charge status pre-booting HaRET/Android, but the fact that we all have seen 21% and 4% is a little strange . What do those correlate to and why THOSE #s? Since it is common to so many with us that have experienced it i figure it probably points to the root of the problem.

Any ideas? wild speculations?:confused:

Usually I just remove the battery for a little while, then a couple of slow/strange restarts then somehow it just starts running like normal again.
[Tilt, TyTN II, MDA Vario III Android Development] iPirate:
I guess I will post my experience again...

Android thinks 10% actual battery life is 30%. When you get to 30% in Android, your phone will die soon.

After noticing 30% is empty, I typically reduce the use of my phone around 45-50% and I havent had any problems for the past week or more. Worst case, reboot into winmo if you need to use your phone for another 6 hours.
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
How to delete this message???
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
and also - what are we turning on and not off? it seems like: a. android uses a lot more battery than winmo and b. it uses the same amount of battery with ppp on or off.
[Tilt, TyTN II, MDA Vario III Android Development] iPirate:
I'm not sure what happened but now when I load android it goes to the "desktop" and then i cannot press any keys, then it reboots android. this continues until i pull the battery out...

01 march build:confused:
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
[offtopic]Just imagine what would've been if it was 01 april build :D[/offtopic]

Reload files on card. Try 12.03.09 build, worked perfectly on my Tilt. Also make sure that you don't just reset phone to go back to WinMo, but turn it off by holding red End Call button so that it will unmount file systems properly. I had problems with corrupted settings and some other glitches until I started turning it off instead of reseting, though true reason may be different from what I think.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Yeah, I think there's a lot to be done still in terms of power saving. I'm just now testing a kernel with cpu frequency scaling enabled. Also, I think for many internal parts the powersaving is not enabled/used.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
And also @poly_poly-man: WinMo and Android (new kernel) use completely different approaches to measure battery fuel gauge. I think even the WinMo drivers "simulate" the ds2476 behaviour, and I have seen more than once that WinMo also makes wild guesses.

However, when you stay in Android, discharge, then reboot into Android again and charge fully, it should be re-calibrated and stay like that. The ds2476 can detect very small currents, so it is supposed to be very accurate (and now that I've run it a couple of days, it works quite fine for me).

One thing I may add, and that is an initial "wild guess" as to what the gauge is when Android is first booted up.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
Hi all, can any developer give me a hint on what is going on with the cpld code? I'm getting crazy with this:

Take, for example, board-kaiser.h:

#define KAISER_GPIO_LED_FLASH (KAISER_GPIO_MISC1_BASE + 6)

#define KAISER_GPIO_SD_POWER (KAISER_GPIO_MISC2_BASE + 0)

That means KAISER_GPIO_LED_FLASH is 134 (128+6) and GPIO_SD_POWER is 136 (128+8), not?

What I would want to understand is why, if I replace 128+6 with 134 it get's another address.

I found someone had this very same problem and commented it on the board file:

//if i do KAISER_GPIO_MISC1_BASE + 5 (128 + 5 = 133) then it ends up the same as KAISER_GPIO_LED_RED

//i'll let someone else be clear about what is going on here and just get back to living my life

#define KAISER_USB_HEADSET_UNPLUGGED	(133)

#define KAISER_GPIO_KBD_BACKLIGHT (KAISER_GPIO_MISC2_BASE + 2)

My exact problem is with this same code on the nike. If I take the pin 138, and put it to 1, it lights orange. If I take the pin base (128), and add 10, it powers up the green led. And if I patch it so it does something like 136+2, disabling the green part, it lights red. What the h*** is going on please?
[Tilt, TyTN II, MDA Vario III Android Development] iPirate:
"This could be a temporary problem or your SIM card may not be provisioned for data services. If it continues, call Customer Care."

Whats up with this message?:confused::confused:

EDIT: I had to edit my APN :rolleyes: works now
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
New patch

Hi y'all

new patch: charging state is determined from GPIO, not from battery current. Works fine with USB charging, don't have a wall charger, so can't check with that.

Hope someone adopts.

I'll release a new version with improved battery capacity reading soon.

A big THANKS so far for your feedback!

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] bally3:
I think I mentioned this before but on my polaris, Android keeps trying to turn wifi on it seems if you click on Settings > Wireless Options. This would cause the battery to wear down very quickly, so maybe we need to look at what trying to switch on and turn it off until we have it working, like gps, wifi etc
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
If you go to linuxtogo.org, create an account, click projects then mobile-linux and ask to join, you will be able to push your changes to the git repo with:

git push ssh://username@linuxtogo.org/home/groups/mobile-linux/kernel.git htc-vogue
[Tilt, TyTN II, MDA Vario III Android Development] cmus:
Battery & Task Manager

One of my most used apps is the task manager that was posted here a while back. I was wondering if there is unnecessary power drainage being caused by some of my apps that seem to start themselves on their own. Specifically, imeem, Scoreboard, Touchdown, and a few others seem to always restart after I kill them. Is there any way to disable the autostart features of apps like these? Especially in the face of quick battery drainage issues that everyone is reporting.

You developers are fantastic. I got 20 bucks ready for the person who gets wifi working...