• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

TESTING: global kernel with a lot of changes ...

Search This thread

camro

Senior Member
Apr 20, 2007
1,829
33
hi,
here a kernel, which we want to commit to kernel "msm-linux"
(the kernel should be for: raphael, diamond, blackstone, topaz, rhodium, kovsky) booting via haret

all credits to crazyvirus, alex, acl, jonpry, phh, oliwe, etc ...

BE CAREFUL ! best would be -> make backup before, beucase there a lotof changes and i tested only the blackstone !

changes overview:
1.) new battery algo for better display the VOLUME (for now blackstone is ajusted, the other devices battery devices could be, that we must do finetuning
2.) new USB driver (working also if not connected on boot)
3.) AC / USB charger detection
4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)

TESTING:
please test this kernel:
1.) battery - specially we need testing on battery -> please add the logging data from kernel... -> via kernel logging -> cat /proc/kmsg | grep battlog)
2.) USB
.) connecting USB after rebooting, then try to connect via win adb or linux
.) test mass data storage
.) DON'T click/test wlan hotspot !!! it could be, that you have problems after using it !
3.) AC / USB charger -> change the adapter and look on battery information if it will be changed correct.
4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)

please help on testing, because we want soon to commit this changes.

cu camel

PLS: as you know, this kernel is for multiple sys please add always:
Device: ??
Battery Type: Original or ????
Battery Volume: ???? mAh

############################
attached a new kernel V8

.) try now to fix the boot for kovsky (device think the batt is 70° hot ...)
.) cleanups for battery driver things
.) logging is now different
.) there is a new log option (only in startup.txt boot option like:)
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=1 ( 0 | 1 ) via bit (0 = OFF / 1=ON) (would fake to system, that it is always on USB charger)
+ htc_battery_smem.vol_min=5 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)

here an example of my startup boot option line:
set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"

EDIT9: kernel v9
.) fixing high temperature on kovsky & rhod (which does on startup autoamtically a shutdown, because android system is thinking the batt is too hot.
:> i made a mistake, which should be now correct. if it would be too hot (> 50°), then i set the temp to 499 = 49,9° -> so watch out if there is a value of 499 on temp

EDIT10: kernel_v10
.) now battery data for blackstone should be fine. (current + volatage, + % + 93% to 100%
.) kovsky adjustment for voltage, temp + current should be now better ...

EDIT11: kernel_v11
.) now battery data for raph should be fine. (current + volatage, + % + 93% to 100%)

EDIT12: kernel_v12
some device had problems with wrong values from battery driver, and then device shutdown by itself ..
-> should be fixed now

EDIT13: kernel_13
sorry, the kernel v12 was very bad, a lot of mistakes ..sorry
.) fixed a lot of things in alog, specially if charging, had wrong values, also fix temperature values, etc...
.) adjusted raph100 (hwboard_id=1)
fixed some errors on wrong values which shutdown the whole system

EDIT14: kernel v14
.) fixed some problems with charger devices
.) added corr for AC adapter if current is higher
.) adjust a lot of things on algo

EDIT15: kernel v15
.) made a stupid bug in autocorrection function (temp was never corrected), so the device shutdown the device if wrong values ..is fixed now :)

EDIT16: kernel v16
.) add addionally debug prints for kovsky (because no battery init)
.) diamond100-900 adjustments - for diamond100-900 we need a FINAL LONG TEST - see posting #2

EDIT17: kernel v17
.) added support for topa??-1100 vendor=2
.) removed extra debugging prints for kovsky

EDIT18: kernel v18
.) added support for kovsky, new rhod type
.) extreme values checking
.) adjustments for rhod + kovsky current, temp, etc..
.) extra recheck for INCALL
.) rhod: set POWER to HOME KEY (only for rhod)
EDIT19: kernel v19
.) try to write the temperature only once, if value is ok, so the auto shutdown shouldn't happen any more.)
.) adjustment for kovsky device
.) some other small fixes

EDIT 20: kernel v20 (battery driver on chip 2746 - experimental)
.) there is a new log option (only in startup.txt) boot option like
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=0 ( 0 | 1 )
+ htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)
+ htc_battery_smem.vol_max=100 ( integer value which will be the maximum value) if it is > then it will correct the volume to this value, so the battery won'T be charged by kernel, and the battery can switch off the charging by itself
.) adjustment on current + voltage for kovsky
.) alex patches: clock wince + kovsky battery support via ds2746 (no idea how it works - short test before a long time test makes sense and would be welcome
EDIT21: kernel v21
.) support for rhod300
.) changed back to calc the kovsky from kernel on normal way
.) removed the wince clock path from Alex (because users reported problems with flickering)
 

Attachments

  • 21_zImage.zip
    1.6 MB · Views: 3,920
  • 21_modules-2.6.27.46-01179-g9526abc-dirty.tar.gz.zip
    7.2 MB · Views: 4,118
Last edited:
  • Like
Reactions: HD69

camro

Senior Member
Apr 20, 2007
1,829
33
x.....OK
o.....IMPLEMENTED - FINAL TEST IS MISSING
t.....TESTING
n.....not supported
b.....buggy, not working
?.....no info about ..

Code:
BATTERY TYPES__:raph100-1340|raph100-1340|raph300-????|raph500-????|raph800-????|diam100-????|diam500-????|blstone-1350|topa100-1100|topa100-1100|rhod100-????|rhod210-????|rhod300-1500|rhod400-????|rhod500-????|kovsky1-????|
ExTRAINFO______:hwboardid=0_|hwboardid=1_|            |            |            |            |            |            |vendor1     |vendor2     |            |            |vref=1254   |            |            |            |
---------------:------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|
boot procedure_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______x_____|______?_____|______?_____|______x_____|
InCall Mic_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
InCall Earpice_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
USB Gadget_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
USB Mass Storag:______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|
temperature____:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______b_____|______b_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
voltage________:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on AC__:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on USB_:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on batt:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|


(updated -> 20.10.2010 10:59 GMT+2)

we need for every battery type and device a detail log, so that i can adjust the battery parameter

if you also want that your phone shows the real % volume, then you must log as described..if not -> your own fault :)


how to log:
at first you must activate logging:

short test:
========
1.) boot

2.) activate logging via:
dmesg >> /sdcard/kovskylog.txt
cat /proc/kmsg >> /sdcard/kovskylog.txt

preconditions: best would be if the phone is 10% -90% (not on 100% !!)

then do:
~2min charging via AC
~2min on battery
~2min charging via USB

################################################## ##

then send me this log file, then i can adjust the basisc...

################################################## ##

after that we can do the long time test:

################################################## ##

long time test: (needs ~10hrs)
(preconditions: best would be if the phone is 0% - 50%)
========
1.) boot
(for this test -> before booting to android -> you should add to startup.txt)
htc_battery_smem.debug=7
htc_battery_smem.vol_min=15
htc_battery_smem.vol_max=90

2.) activate logging via:
dmesg >> /sdcard/kovskylog.txt
cat /proc/kmsg >> /sdcard/devicename_log.txt

then do:
~30min charging via USB
~3min on battery
~3-4hrs charging via AC

after that prepare your device:
-> flight mode ON
-> SYNC data - OFF
-> 3G -> OFF
-> screen always ON
-> screen ~50% brightning

plug out the cable and let device run out of battery
(needs ~6hrs)

then send me the log
################################################## ##

.) there is a new log option (only in startup.txt) boot option like
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=0 ( 0 | 1 )
+ htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)

here an example of my startup boot option line:
set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"

1.) full charging of your phone, -> please to be sure, that it is really full -> charge it ~3hrs via AC adapter.
2.) kill all applications
3.) open terminal emulator:
-> then input: su
-> then input: cat /proc/kmsg | grep BATTLOG >> /sdcard/batterylog.txt
or if you want full logging -> then input: cat /proc/kmsg | grep BATT >> /sdcard/batterylog.txt
(for me it is very simple to grep my data for algo fine tuning
4.) switch to AIRPLANE mode
5.) set your device to: SCREEN ALWAYS ON (there are several tools on the market wher you can do that, 30 is not enough
6.) SET DISPLAY BRIGHTNESS to 50%
then plugout the AC Adapter - and let the phone run out o battery (mostly 5-8hrs)

after that please post the log data. which can be found in sdcard -> (called) -> batterylog.txt

PLS: special apps on market
for "STAY ALWAYS ON" -> you can use: "caffein" (from Syntaxa)
for disable "UNLOCK SLIDE SCREEN" -> you can use: or "screemodewidget"
or also "extended control" but cost some bucks ..
 
Last edited:
  • Like
Reactions: HD69

ho.angii

Senior Member
Apr 24, 2010
151
22
wow these changes sound so promising. downloading and soon to be testing. gettting ever so closer to have a fully functional android. =D

keep up the good work devs
 

dizzyman

Member
Aug 9, 2009
8
0
Device: Blackstone
Battery Type: Original
Battery Volume: ?

Detects usb conection, but can't use as usb storage...
Detects if is usb or ac charge...

mic, not perfect, have to pull volume down to activate.

i will do more tests

Sorry, my english... portuguese... to english....
 

Spidersoft

Member
May 19, 2009
44
7
1.) It says permission denied, what I'm doing wrong?
2.) USB connection is detected, but no mass storage detection
3.) AC / USB charger seems to be correct
4.) (only) reboot works

Device: Blackstone
Battery Type: Original
Battery Volume: 1350 mAh ???

Additional: no mic without pressing volume +/-,no speaker on incoming calls (also after pressing +/-)
 

x PIGI x

Member
Jan 17, 2009
26
0
Blackstone
Original battery
Wifi not working
Incoming call mic only works after you press volume down
 

joveen

Member
Mar 9, 2010
16
0
ac and usb charging detected properly.
switch from ac - usb - detects usb
switch usb - ac (with a delay after the battery info says unplugged) - detect.
switch usb - ac (quickly) - doesnt detect.
shutdown button reboots the phone to windows.
USB detected on PC.
USB mass storage didn't work.

Teethering detects USB as connected.
Turn on wifi - gets error with this image. with the 17 th build image it works.
Mic is mutted on receving call. We may need some state machine tweks to get it done.(guess)
Any one facing issue with re detecting signal once it is lost?
Enable GPS - battery level suddenly goes down. Disable GPS it comes back. Is it expected.



Device: Blackstone
Battery Type: Original
Battery Volume: 1350 mAh
 
Last edited:

kulwant

Senior Member
Jul 7, 2009
106
2
May sound weird but where to copy these files to test them..I'm a rookie at android..:)
 

dizzyman

Member
Aug 9, 2009
8
0
battery seems to be almost... fixed... i boot my phone and he says battery volume 42, 8 hours later... i have 14 of volume battery, no wifi, no calls, standby 8 hours with half battery...
in win mobile he says 20%, in android he says volume battery 14, nothing like before.
 

willcor

Senior Member
Oct 2, 2008
1,051
306
hi camro ,
i have a blackstone ,with stock ROM 6.1.........
overall FroYo 2.2 with your updated kernel , is running quite smoothly this morning.( lets hope it stays that way!! )
previously ( few days back ,till yesterday) had sound problems ,but change ...cmd line, accordingly to your suggestion , in you "fix for battery "thread (your post 89 )...yesteday morning and sound had been stable ever since.!
i have wifi , no problem.
battery is much better with your fix ....thank you

shutdown ..button ..
reboots the phone..(which is perfect for me )..better than switch off (,as i can get into windows... without taking cover off.. etc.etc..reset button.. )
plse, keep it like that !!!.. ?
but.....
i must add...
that yesterday before i made the relevant kernel changes i also notice
android battling with redetecting signal ..( i have good reception ..3g and gsm in my area..) as joveen in post 8, states "issue with re detecting signal once it is lost?) and after i replaced it with your updated kernels i still had these issues.
i tried replacing ,all old kernels etc etc ..no luck
( so i am convince the updated kernels... dont play a part in it..!!.. ?? )

but ..(and thats, the point i want to make...)
... i noticed every time ,
android... battled to "redetect signal " ..i had "deep sleep issues...???
and if i had constant signal ..i had nothing ..!!!android woke up every time
( just thought i will add it )
thank you.............. camro, alex, acl, jonpry, phh, oliwe..!!!!
good luck
willcor
 
Last edited:

joveen

Member
Mar 9, 2010
16
0
Regarding redetecting signal -
I tried at a place where the signal levels is not that good.
the battery doesnt seems to be consumed !! .. I doubt if the android is trying to detect the signal. If it had tried the battery consumption would have increased. (Not sure if this is valid.. It is just a guess from my side).
 

camro

Senior Member
Apr 20, 2007
1,829
33
battery seems to be almost... fixed... i boot my phone and he says battery volume 42, 8 hours later... i have 14 of volume battery, no wifi, no calls, standby 8 hours with half battery...
in win mobile he says 20%, in android he says volume battery 14, nothing like before.

normal, WM is not a hint for correct %vol.

@USER which are testing dlackstone: !!
if you have don't have a blackstone device, then i would need a log from real 100% to 0% - best would be, if you can hold the current stable (like: diplay always on, all other apps closed and sync deactivated), then do logging as it is describe on #1 posting.
 

camro

Senior Member
Apr 20, 2007
1,829
33
Regarding redetecting signal -
I tried at a place where the signal levels is not that good.
the battery doesnt seems to be consumed !! .. I doubt if the android is trying to detect the signal. If it had tried the battery consumption would have increased. (Not sure if this is valid.. It is just a guess from my side).

at first, thanks, your previous feedback was great, will try to take a look on different minutes ...

for your last feedback:
redetecting ? what do you mean ? usb or battery ?
please can you explain that more in detail ?

for usb mass storage -> maybe this you must activated somewhere in the phone, for USB, there must be 3 diff models of using... (tethering, usb mass storage, usb debugging, etc..) - but haven't found this - not yet tested
 

camro

Senior Member
Apr 20, 2007
1,829
33
hi camro ,
i have a blackstone ,with stock ROM 6.1.........
overall FroYo 2.2 with your updated kernel , is running quite smoothly this morning.( lets hope it stays that way!! )
previously ( few days back ,till yesterday) had sound problems ,but change ...cmd line, accordingly to your suggestion , in you "fix for battery "thread (your post 89 )...yesteday morning and sound had been stable ever since.!
i have wifi , no problem.
battery is much better with your fix ....thank you

shutdown ..button ..
reboots the phone..(which is perfect for me )..better than switch off (,as i can get into windows... without taking cover off.. etc.etc..reset button.. )
plse, keep it like that !!!.. ?
but.....
i must add...
that yesterday before i made the relevant kernel changes i also notice
android battling with redetecting signal ..( i have good reception ..3g and gsm in my area..) as joveen in post 8, states "issue with re detecting signal once it is lost?) and after i replaced it with your updated kernels i still had these issues.
i tried replacing ,all old kernels etc etc ..no luck
( so i am convince the updated kernels... dont play a part in it..!!.. ?? )

but ..(and thats, the point i want to make...)
... i noticed every time ,
android... battled to "redetect signal " ..i had "deep sleep issues...???
and if i had constant signal ..i had nothing ..!!!android woke up every time
( just thought i will add it )
thank you.............. camro, alex, acl, jonpry, phh, oliwe..!!!!
good luck
willcor
thanks for report,
redetection signal on data connection (3g, 3g, e,) - i'm wondering about, normally nothing changed for this part in kernel.
but if see something in the log.
if you can reeproduce this problem, then make catlog + dmesg, maybe we can find the problem. i never seen such problem on my device ...
have you played with the tethering ?
because since i tried it to activate, i can't disable the tethering/hotspot - maybe this is the problem ..
i must backup + delete my data again and then try it again - without tethering or hotspot .
 
Last edited:

joveen

Member
Mar 9, 2010
16
0
Hi Camro,

I meant "Redetecting the 3g/2g signals once it is lost".
In a place with low signal, the battery should be consumed more. I am not seeing that with my black stone.baterry almost remains same. Seems like android is not trying to redetect the signals once it is lost. Is there some logs/kernal message to see if it is searching for signals.
 

camro

Senior Member
Apr 20, 2007
1,829
33
DON'T click/test wlan hotspot !!! it could be, that you have problems after using it !
 

camro

Senior Member
Apr 20, 2007
1,829
33
Hi Camro,

I meant "Redetecting the 3g/2g signals once it is lost".
In a place with low signal, the battery should be consumed more. I am not seeing that with my black stone.baterry almost remains same. Seems like android is not trying to redetect the signals once it is lost. Is there some logs/kernal message to see if it is searching for signals.

catlog -> grep for "ConnectivityService", there you'll should a part of it ....
fori played with hotspot, and i can'T disable it -since now always "ConnectivityService" will try to set some part for wlan hotspot... must remove my data and install my apps again ..
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    hi,
    here a kernel, which we want to commit to kernel "msm-linux"
    (the kernel should be for: raphael, diamond, blackstone, topaz, rhodium, kovsky) booting via haret

    all credits to crazyvirus, alex, acl, jonpry, phh, oliwe, etc ...

    BE CAREFUL ! best would be -> make backup before, beucase there a lotof changes and i tested only the blackstone !

    changes overview:
    1.) new battery algo for better display the VOLUME (for now blackstone is ajusted, the other devices battery devices could be, that we must do finetuning
    2.) new USB driver (working also if not connected on boot)
    3.) AC / USB charger detection
    4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)

    TESTING:
    please test this kernel:
    1.) battery - specially we need testing on battery -> please add the logging data from kernel... -> via kernel logging -> cat /proc/kmsg | grep battlog)
    2.) USB
    .) connecting USB after rebooting, then try to connect via win adb or linux
    .) test mass data storage
    .) DON'T click/test wlan hotspot !!! it could be, that you have problems after using it !
    3.) AC / USB charger -> change the adapter and look on battery information if it will be changed correct.
    4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)

    please help on testing, because we want soon to commit this changes.

    cu camel

    PLS: as you know, this kernel is for multiple sys please add always:
    Device: ??
    Battery Type: Original or ????
    Battery Volume: ???? mAh

    ############################
    attached a new kernel V8

    .) try now to fix the boot for kovsky (device think the batt is 70° hot ...)
    .) cleanups for battery driver things
    .) logging is now different
    .) there is a new log option (only in startup.txt boot option like:)
    + htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
    + htc_battery_smem.fake=1 ( 0 | 1 ) via bit (0 = OFF / 1=ON) (would fake to system, that it is always on USB charger)
    + htc_battery_smem.vol_min=5 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)

    here an example of my startup boot option line:
    set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"

    EDIT9: kernel v9
    .) fixing high temperature on kovsky & rhod (which does on startup autoamtically a shutdown, because android system is thinking the batt is too hot.
    :> i made a mistake, which should be now correct. if it would be too hot (> 50°), then i set the temp to 499 = 49,9° -> so watch out if there is a value of 499 on temp

    EDIT10: kernel_v10
    .) now battery data for blackstone should be fine. (current + volatage, + % + 93% to 100%
    .) kovsky adjustment for voltage, temp + current should be now better ...

    EDIT11: kernel_v11
    .) now battery data for raph should be fine. (current + volatage, + % + 93% to 100%)

    EDIT12: kernel_v12
    some device had problems with wrong values from battery driver, and then device shutdown by itself ..
    -> should be fixed now

    EDIT13: kernel_13
    sorry, the kernel v12 was very bad, a lot of mistakes ..sorry
    .) fixed a lot of things in alog, specially if charging, had wrong values, also fix temperature values, etc...
    .) adjusted raph100 (hwboard_id=1)
    fixed some errors on wrong values which shutdown the whole system

    EDIT14: kernel v14
    .) fixed some problems with charger devices
    .) added corr for AC adapter if current is higher
    .) adjust a lot of things on algo

    EDIT15: kernel v15
    .) made a stupid bug in autocorrection function (temp was never corrected), so the device shutdown the device if wrong values ..is fixed now :)

    EDIT16: kernel v16
    .) add addionally debug prints for kovsky (because no battery init)
    .) diamond100-900 adjustments - for diamond100-900 we need a FINAL LONG TEST - see posting #2

    EDIT17: kernel v17
    .) added support for topa??-1100 vendor=2
    .) removed extra debugging prints for kovsky

    EDIT18: kernel v18
    .) added support for kovsky, new rhod type
    .) extreme values checking
    .) adjustments for rhod + kovsky current, temp, etc..
    .) extra recheck for INCALL
    .) rhod: set POWER to HOME KEY (only for rhod)
    EDIT19: kernel v19
    .) try to write the temperature only once, if value is ok, so the auto shutdown shouldn't happen any more.)
    .) adjustment for kovsky device
    .) some other small fixes

    EDIT 20: kernel v20 (battery driver on chip 2746 - experimental)
    .) there is a new log option (only in startup.txt) boot option like
    + htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
    + htc_battery_smem.fake=0 ( 0 | 1 )
    + htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)
    + htc_battery_smem.vol_max=100 ( integer value which will be the maximum value) if it is > then it will correct the volume to this value, so the battery won'T be charged by kernel, and the battery can switch off the charging by itself
    .) adjustment on current + voltage for kovsky
    .) alex patches: clock wince + kovsky battery support via ds2746 (no idea how it works - short test before a long time test makes sense and would be welcome
    EDIT21: kernel v21
    .) support for rhod300
    .) changed back to calc the kovsky from kernel on normal way
    .) removed the wince clock path from Alex (because users reported problems with flickering)
    1
    x.....OK
    o.....IMPLEMENTED - FINAL TEST IS MISSING
    t.....TESTING
    n.....not supported
    b.....buggy, not working
    ?.....no info about ..

    Code:
    BATTERY TYPES__:raph100-1340|raph100-1340|raph300-????|raph500-????|raph800-????|diam100-????|diam500-????|blstone-1350|topa100-1100|topa100-1100|rhod100-????|rhod210-????|rhod300-1500|rhod400-????|rhod500-????|kovsky1-????|
    ExTRAINFO______:hwboardid=0_|hwboardid=1_|            |            |            |            |            |            |vendor1     |vendor2     |            |            |vref=1254   |            |            |            |
    ---------------:------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|
    boot procedure_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______x_____|______?_____|______?_____|______x_____|
    InCall Mic_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
    InCall Earpice_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
    USB Gadget_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
    USB Mass Storag:______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|
    temperature____:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______b_____|______b_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
    voltage________:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
    current on AC__:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
    current on USB_:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
    current on batt:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|


    (updated -> 20.10.2010 10:59 GMT+2)

    we need for every battery type and device a detail log, so that i can adjust the battery parameter

    if you also want that your phone shows the real % volume, then you must log as described..if not -> your own fault :)


    how to log:
    at first you must activate logging:

    short test:
    ========
    1.) boot

    2.) activate logging via:
    dmesg >> /sdcard/kovskylog.txt
    cat /proc/kmsg >> /sdcard/kovskylog.txt

    preconditions: best would be if the phone is 10% -90% (not on 100% !!)

    then do:
    ~2min charging via AC
    ~2min on battery
    ~2min charging via USB

    ################################################## ##

    then send me this log file, then i can adjust the basisc...

    ################################################## ##

    after that we can do the long time test:

    ################################################## ##

    long time test: (needs ~10hrs)
    (preconditions: best would be if the phone is 0% - 50%)
    ========
    1.) boot
    (for this test -> before booting to android -> you should add to startup.txt)
    htc_battery_smem.debug=7
    htc_battery_smem.vol_min=15
    htc_battery_smem.vol_max=90

    2.) activate logging via:
    dmesg >> /sdcard/kovskylog.txt
    cat /proc/kmsg >> /sdcard/devicename_log.txt

    then do:
    ~30min charging via USB
    ~3min on battery
    ~3-4hrs charging via AC

    after that prepare your device:
    -> flight mode ON
    -> SYNC data - OFF
    -> 3G -> OFF
    -> screen always ON
    -> screen ~50% brightning

    plug out the cable and let device run out of battery
    (needs ~6hrs)

    then send me the log
    ################################################## ##

    .) there is a new log option (only in startup.txt) boot option like
    + htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
    + htc_battery_smem.fake=0 ( 0 | 1 )
    + htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)

    here an example of my startup boot option line:
    set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"

    1.) full charging of your phone, -> please to be sure, that it is really full -> charge it ~3hrs via AC adapter.
    2.) kill all applications
    3.) open terminal emulator:
    -> then input: su
    -> then input: cat /proc/kmsg | grep BATTLOG >> /sdcard/batterylog.txt
    or if you want full logging -> then input: cat /proc/kmsg | grep BATT >> /sdcard/batterylog.txt
    (for me it is very simple to grep my data for algo fine tuning
    4.) switch to AIRPLANE mode
    5.) set your device to: SCREEN ALWAYS ON (there are several tools on the market wher you can do that, 30 is not enough
    6.) SET DISPLAY BRIGHTNESS to 50%
    then plugout the AC Adapter - and let the phone run out o battery (mostly 5-8hrs)

    after that please post the log data. which can be found in sdcard -> (called) -> batterylog.txt

    PLS: special apps on market
    for "STAY ALWAYS ON" -> you can use: "caffein" (from Syntaxa)
    for disable "UNLOCK SLIDE SCREEN" -> you can use: or "screemodewidget"
    or also "extended control" but cost some bucks ..