yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] cherokee45:
dennis.l

OnYa Mate!!

Loaded this yesterday and everything is spot on, nice to see great stuff coming from Downunder :D
[Hero, G2 Touch Android Development] robocik:
apns are located in /system/framework/framework-res.apk

when you open the apk, you find the apns in /res/xml/

open the file with the apns you want and just drag it to the file you want it to, to the proper directory ofcourse.
[Hero, G2 Touch Android Development] dennis.l:
Excellent.. Thanks robocik. You are a champ!!
[Hero, G2 Touch Android Development] robocik:
No problem ;)

remember do not unpack the apk, just open both files in a archiwer and drag the file from one to the other ;)
[Hero, G2 Touch Android Development] guy_smiley:
Trying this ROM now. Good to see someone release a ROM with Australia as a locale. Anyone having issues with the market? I can connect on Wifi but not on 3G on Telstra. APN seems to be fine (same as previous).

EDIT: furthermore has anyone tried the new HTC Sync with this ROM? Any success?
[EVO 4G Q&A, Help & Troubleshooting] dguidry12:
Could someone please help.

I am trying to root using the Unrevoked Beta 3.21 to root my phone. I get to the end in Unrevoked and it states "failed to flash recovery image"

This is what I have done:

1. Installed all drivers - Device manager does stat ADB Interface just like the guide states.

2. Installed the Relfash packgage

3. Phone is in "debbuging mode"

4. Charge Only is selected

5. Using Windows xp

One strange thing that I do notice is that when the Unrevoked program tells you to select the Hboot usb on my phone and when I do so it flashes blue or green wording that says "no Image" when it looks like its trying to load an image. Afterwards the phone goes into the reboot phase and then states "Failed to flash recovery image". Help is much appreciated.
[EVO 4G Q&A, Help & Troubleshooting] bbowenx:
drivers

i'd mak esure you have everything else uninstalled, every doubletwist, htc software and drivers get it all off, then reboot install unrevoked drivers, then 3.21

thats what i did last night, and it worked.
[EVO 4G Q&A, Help & Troubleshooting] Punchatron:
Uninstall HTC Sync if you have it installed.
[EVO 4G Q&A, Help & Troubleshooting] dguidry12:
Hey folks thanks for the help you all gave. I finally got it to work last night. What I did was unistalled everything that I had downloaded and started fresh from the beginning of the directions. It was all good after and worked flawless. Now im moving on to see what "root" actually is and how it benefits me.

Thanks,
[EVO 4G Q&A, Help & Troubleshooting] pedrodog69:
I have a similar problem, I down loaded from IRC and few others on other thread tried them all and I get the same results. in the flash it says killing adb bug then waiting for device debug usb and stays that way. what am I doing wrong I deleted everything HTC, drivers ect. I used usb tethering on pdanet to get everything do I delete that as well? is there a more precise guide in detail from start to finish for noob as there is one for the 1.26.561.6 version.

thanks
[EVO 4G Q&A, Help & Troubleshooting] gotan:
hi guys

i just upgraded to 2.2

i also followed everything. but whenever i start 3.21 , it will not detect my htc desire. im using windows 7.

i never installed sync programs etc. evrytime i plugged in my phone to 3.21, i can see the yellow ! ADB. is it normal? and can u guys help unrevoked my phone. thank you guys.
[EVO 4G Q&A, Help & Troubleshooting] Jimmy2Gunz:
evo help please

I'm currently trying to root my Evo for the first time and as afar as the software goes i downloaded everything that i needed to when i comes time to go to the device manager i cant find the Android 1.0 in other devices i followed the guide to the letter but it still wont show up does anyone know why??????? and what do i need to do to get it to show....(android usb devices shows up when it's plugged in from usb and when i click the drop down it just says my HTC if that helps any i'm also using windows xp...)
[Legend General] recyap:
please i really need your help about this when i turned off my legend i can't charge at all and then when i turned it on i can't open, i did some battery remove then charge it, it works though and i overnight charge it (phone is turned off) then when i finally turned it on it won't open again and still now it won't open

i notice i frequently have force close applications...i don't have my htc bookmarks widget and htc clock widget and some of my uninstall applications was there and some of my recent installed application were gone....what's the meaning of this???

and one additional question how will you know if your legend is rooted or not?
[Legend General] recyap:
i think my htc sense applications is gone?? any solutions to bring it back? my phone is not rooted i just updated it to android 2.1 then force applications starts popping
[Legend General] Ns_:
try make a Hard reset on the phone. Make sure to backup all your data.
[Windows Mobile Themes] sprucas:
i'm trying to track down some more wp just like these pics

somehow i think they might be an anime character or a game character

any ideas??
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
NOTE: I don't post kernels here anymore: look for my changes in the standard kernel now.

This thread is still useful for battery discussion, if you like.

I have gotten tired of seeing my battery go from 90% to 15%.

Why can't it go smoothly from 100% down to 5% or less, and back up again?

Why does nbheditor have to apply a 1.6 multiplier for battery capacity?

Can we get the temperature sensor working?

I'd like to get this fixed, and would welcome discussion.

First, in the new or old kernel, the battery status is managed by the file:

kernel/arch/arm/mach-msm/board-kaiser-battery.c.

I have several proposals:

a) Change the default KAISER_BATTERY_RATING to 1350, since the equations really do work out correctly, that the rating should match in mAh. Note: in the kernel, that's 2160 = 1350 * 1.6.

b) Add a thirty second maximum for voltage and current, before using them to guess the battery level. At first I used averaging, but maximum works better for old batteries.

c) When booting from HaRET, scale the battery level because Windows does it different. I don't understand how Windows does it, but I have figured out a scale factor that works.

d) When the ds2746 reports that it has lost power, assume that the battery may have been changed, and do a coarse recalibration based on voltage and charge current.

e) Eliminate the minimum of 15%: let the meter go all the way to zero.

f) Allow battery level to be set to any value at any time.

g) Report what the kernel thinks the capacity should really be.

h) Use ds2746 units directly since nbh-editor already scales mAh to units.

Also, questions:

1) How to convert the thermistor resistance (I think it is aux0r) to temperature?

2) Would be nice if the dynamically-adjusted capacity could be stored in flash. I don't know how to do that, but I know how to report it.

3) Should we have an option on the boot menu to manually set the battery level?

I have edited the new 2.6.34 kernel to act as I propose.

Since the modules must match the kernel version you are using, I have included modules separately.

Warning though that, although it seems to work properly for me, it might do bad things for you, especially to your phone's battery. In particular, the Polaris needs to be tested since I don't have one.

NBH file: for NAND install. Use nbheditor to edit, but put your battery's capacity under "advanced settings". For attempt #6, you can use the standard setting.

ZIMAGE: for HaRET install. Edit your default.txt to contain:

board-kaiser-battery.battery_capacity=2160 (your true battery capacity in mAh * 1.6)

board-kaiser-battery.haret_divisor=2200 (use a WinMo -> android scale factor of 1000/2200)

CAUTION: The 2.6.25 NBH images probably don't work. I'll have to learn how to make them!

NOTE: Attempt #7 and later are in the standard kernel, so are no longer posted here.
[Tilt, TyTN II, MDA Vario III Android Development] zPacKRat:
just setting this up on Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS15] [9/3/10]. I will let you know how it goes.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
WOW, I´m glad somebody finally took this matter as serious as it is I´m not saying that others guy in here haven´t provided advice on this, it is just that nobody, afaIk hadn´t come with a "downloadable" solution, the only thing close to a real fix to me was to use the nbh editor and put the recommended capacity for my battery, it helped a lot to be honest cuz I used to get no more than 15 minutes of battery life, and after that I can use it for a few hours, unless I turn wifi and bluetooth of course, then it gets down to 15%, well I hope this really works cuz I´v been strugling with this for more than a month and I love android so much that I flashed on nand even though I knew about this problem, and I was about to give up on this, (was I?), thanks for this, I hope we get good results!!!
[Tilt, TyTN II, MDA Vario III Android Development] ebautista:
Isn't it that the latest kernel for froyo is 2.6.32? Is that your own build?

I wanna try your version. So far, how does all features? How is it compared to DZO's kernel?

More power!
[Tilt, TyTN II, MDA Vario III Android Development] zPacKRat:
Ok so I had lockups with Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS15] [9/3/10], I am loading up dzo's current Froyo and his 9-9-10 kernel for some base testing then I will install your kernel and updates and test again.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
So, how do I install this? i mean, do I:

1- flash the new nbh.

2- install theandroidupdate.tar

done? I mean, do I have to do the whole "calibration dance" with it again or something? Or after i do this it will (in theory) perform as normal as it should? btw my battery is about a month old, so I guess if i put 2000 in advance mode, (not mah) it would be ok, right?

ps: I have donut installed, so I guess it might not work, but heck I´ve got to try this anyways, so I´ll go ahead and install it, in case it works, would you be able to tweak a donut kernel for us?. thanks in advance.
[Tilt, TyTN II, MDA Vario III Android Development] ebautista:
zack, how is it?
[Tilt, TyTN II, MDA Vario III Android Development] zPacKRat:
so far with dzo's latest froyo build and the attached kernel and update things have been very stable, however the battery is at 100% constantly. hopefully this will change as the battery is drained and recharged.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
The kernel is dzo's with the experimental battery file.

Not ready for prime time. If your configured capacity is wrong, it gets calibrated as you run, but the calibration is not remembered when you reboot.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I'm looking for opinions on the individual questions in the first post. Especially, does anyone know how the kernel can store battery_capacity s it remains persistent after reboot?

If you search dmesg output for ds2746 you can see what the current capacity is.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I´ve installed it and after a while of letting both wifi and bluetooth on, it finally died and showed me 1% left and powered down all by itself, I had never seen 1% left on android, so that´s a good thing I guess, but after I connected the charger it started charging just fine, but in the console after typing dmesg it tells me that the battery has 4079mv and 54/3200 units, but I think that if the battery has 4079mv, it means it is fully charged, am I wrong? if anybody reads this please confirm this because I put it is still charging I don´t want my kaiser to blow up on me, lol. thanks.

ps: while charging it isn´t showing the amber led, but it has a red blinking led as when the battery is completely empty and not charger is connected (but in android the battery icon has the charging animation).
[Tilt, TyTN II, MDA Vario III Android Development] Millence:
Do not worry. Nothing will happen to your phone. Electronic circuits inside the battery takes care of it. You have to repent attention to the current charge (mAh). When the value falls below 200mA, then the battery is full.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I've had two crashes (phone totally frozen, unresponsive) when on charger and full battery. Probably a coding error somewhere in this experimental file.

I'm also wondering which phone models use this source file?

Do some of them perhaps have different resistor values?

Do we have any historical information about why 10M Ohm was chosen as a resistor value, rather than 15 or some other value?
[Tilt, TyTN II, MDA Vario III Android Development] elander:
Thanks for replying, I know that the battery has some sort of sensor built in that tells the OS when it is full, but since we are dealing with calibration here (a.k.a I don't know when it is full or empty) I kinda freaked out a bit there, but thanks to your answer I feel (a little) relieve, the thing is that it's been plugged for more than two hours (I had to unplugged it cuz I had to return home from work) and dmesg still says something like: 4180 mv 145mah 50/100 (1604/3200 units) so when you told me about the current charge below 200mah you meant the number that appears on dmesg right after the (4180)mv? in this case it is 145mah, if so, does that means that the battery is already fully charged? cuz according to android it is only like 52% full. should I leave connected or should I unplug it (it is already unplugged just in case,lol). thanks.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
It depends. It looks like your battery currently has 1002 mAh of charge, out of 2000 mAh. I doubt that you have a 2000 mAh battery. If you really have a 1350 mAh battery, you are more like 75% full.

I chose a lower limit than 200 mA for when the kernel thinks you are 100% full based on charge, since my phone charges at under 200 mA when connected to a computer, regardless of how full it is.

Please include what kind of phone you have. Otherwise I will assume you have a Kaiser.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I do have a Kaiser, and I do have a 1350mah battery, and as you said on the first post I edited the nbh to 2000 capacity using the nbh editor, so did I misunderstand first post and instead of 2000 capacity in advance mode I should have put 1350mah in simple mode, or should I have put 1350mah in advance mode in order to make android recognize the capacity of my battery? cuz as I see it now it seems it is the other way around now, cuz before android used to think that the battery was full when in fact it wasn't and now even when full android thinks it is not.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Put the battery rated capacity (1350) in the advanced setting, so it won't be multiplied by 1.6.

The conversion from dmesg units to mAh is: 625 x units / 1000 = mAh. Probably dmesg should show mAh so we don't have to calculate.
[Tilt, TyTN II, MDA Vario III Android Development] spaic:
I am trying to use this kernel with cyanogen build, but it does not boot.

When I start haret it hangs. It moves the staus bar to the bottom of the screen and then freezes. (I can only reset via stylus os sim card cover)

The files I have in andboot are:

zImage-2.6.32-froyo-06-09-10_22 - the original zImage

initrd.lzma

zImage - the zimage with the battery fix

androidinstall.tgz - cyanogen install pack

androidupdate.tgz - update for the battery fix

startup.txt - modified for the battery test (zImage name and battery capacity)

haret-for-kernel-2-6-32.exe - haret

my startup.txt file is:

#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# 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-htckaiser.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 "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=2 board-htckaiser.panel_type=1 hw3d.version=1 board-kaiser-battery.battery_capacity=1350 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=500"
boot

do I need to use another haret or initrd?
[Tilt, TyTN II, MDA Vario III Android Development] elander:
yesterday I left the phone connected to the charger all night and when I woke up (about 5hours and 30 minutes later) it had the green light turned on so it means that it got charged full, and dmesg gave something like this: 4180mv 28mAh and 100/100 (2076/2076 units) I gotta tell you, I had never seen such "low" values on units, its kinda strange, anyways I unpluggued it and went to work, so here I am, I´ll report back in a few hours after I stress this thing a bit to see if it really got all the "juice" the battery can take.

ps: I haven´t tried putting the 1350 (MAh) in advance setting, because since it says that it is charged (I know it may still be wrong) I decided to give it a go to see how it works with the current settings, after finishing testing this, I´ll try with 1350.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I don't know the HARET problem, sorry. Everything you are doing looks right to me. Perhaps you need to wait until this experiment is mature enough to be in a dzo kernel. Sorry!
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
update atools 1.0.3 with large limits!
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
I did just that a few days ago, quoting:

Yet i think i saw a MUGEN 3000mAh battery, so perhaps other values should be inserted. Perhaps:

self.WidgetsLeft.WidgetsLeftBSettings.SpinBattery = Spinbox (self.WidgetsLeft.WidgetsLeftBSettings,values=(1350, 1600, 2800, 3000),width=4,state = DISABLED)

AND

self.WidgetsLeft.WidgetsLeftBSettings.SpinBatteryAdvanced = Spinbox (self.WidgetsLeft.WidgetsLeftBSettings,from_=1350,to=4800,width=4,state = DISABLED,increment=10
[Tilt, TyTN II, MDA Vario III Android Development] object3d:
So do I need to multiply 2800 by 1.6/2 or should I just write 2800 (in my case)?
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
in advanced (not simple) write 2800 x 1.6 and you will be fine. That is if you have a 2800 mAH battery.
[Tilt, TyTN II, MDA Vario III Android Development] object3d:
In Advanced Battery settings, I updated it to 4400 and saved the file. When I open it again, it still shows 1350 and Advanced setting is disabled. Is it normal?
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Someone asked that before, I think atools just defaults to that whenever it opens an nbh. Best to just set it and test it in android. At least in android it can tell you what you set and what it is callibrating it to.
[Tilt, TyTN II, MDA Vario III Android Development] object3d:
fair enough. I will test it amd see how this goes. Thanks a lot.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
First, 2800 mAh * 1.6 = 4480. Dont waste 80 units :D

Second, i've had mixed results. Sometimes i get something in the line of (1500/4146 units, 2160 adjusted ) in the logs, other times i get the (1500/4480 units, 2160 adjusted).

So i don't really know what the hell does a-tools write to the nbh :D
[Tilt, TyTN II, MDA Vario III Android Development] object3d:
Mind you power and performance are major parts of kernel too. So we need to look at these seriously.;)
[Tilt, TyTN II, MDA Vario III Android Development] xnakeg:
i hav a question when i make a call of 2 -3 minutes my battery drains almost 5% - 6 % per call

this is normal or is just the radio ???
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Updated first post with second attempt.

The main change is that instead of using the average voltage and current over the past minute, I now use the minimum and maximum values over the same period. For example, to detect that the battery is nearly empty, the maximum voltage has to be less than or equal to 3.1V, and the maximum current has to be negative.

More importantly, to detect that the battery is charged, the first attempt checked that the average voltage >= 4.15V and average current is positive but less than 50mA. The second attempt checks that the minimum voltage >= 4.15V, minimum current >= 0, and maximum current < 50mA. I made the change because several times my battery indicator jumped to 100% 30 seconds after I plugged in the charger. It turns out that the voltage was high enough, but the since the current changed from negative to positive, the average current was nearly zero.

Also, the dmesg output now shows the capacity (mAh) values in addition to the raw ds2746 units.

The fastest way to "calibrate" the battery meter is still to discharge the battery, but I don't recommend doing that, since it is poor for battery health. For the next attempt, I'll try to switch the calibration point to the high end, so we can calibrate by fully charging the battery.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
Ok, DOwnloading it now, I´ll post my results, (I still need to put 1350 in advance settings,right?).
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Yes, put the actual battery capacity in the advanced settings. I'll ask to LoserSkater and Liqid about changing nbheditor once we have confidence in how this all works.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I am testing the new nbh, however I think I have a problem with the nbh editor, because I´ve seen that although I put 1350mAh in advance settings, dmesg keeps telling me that I have 3200 units, which is about 2000 MAh, in fact this new nbh confirms it by showing it in dmesg (nice touch by the way), anyways the thing is that it seems that nbh editor won´t allow a value lower than 2000 for battery capacity(it does let me put the 1350 in the text field but it doesn´t seem to edit the nbh with that number), as 3200units=2000mAH, so according to this I assume that after editing it to 1350 in advance mode it should go something like 2150 units. (which is 1350mAh)

Ps: I left the phone charging for about two hours and now it says it is only 48/100 1549/3200 units and 967/2000mAh.

should I drain it in order to make it read x/1350mAh or do you think as well it may be something related to the nbh editor?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I did a port of your patch for 2.6.25 and i'm doing some test now.

all battery modification on kaiser battery affected also polaris battery.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
by the way, do I need to use the board kaiser capacity.c? cuz I have only used the .nbh so far, if so, that might explain a lot....lol.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
the .c is source part (only for developers)
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
With Polaris, as I understand, the results of the .c file are more than just affecting the battery meter. I think the battery.c actually enables and disables charging in software based on things obtained from the file we are changing. So, polaris users who aren't developers might want to avoid experimentation.

I found the same issue with nbheditor.. it didn't want to let me enter 1350 as an advanced value. I used brute force, editing nbheditor.py to change its default to the value I need.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Which box has this problem?

Pm me if you want.