SlateDroid.com: X5A/X6D Battery Problems - Work Around - SlateDroid.com

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

X5A/X6D Battery Problems - Work Around

#1 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 25 June 2011 - 10:32 PM

Firstly, this information is not my own, and was compiled from various sources including XDA, and Slatedroid forums, (including battery problem discussion). If anyone spots any errors, or thinks I’ve missed anything important, or would just like to make a suggestion - please let me know asap, so I can edit this post.

Special thanks got to digrobot, starfighter, alva21, and everyone who took part in the battery problem discussion.

Before I begin, please can I ask people to contribute proven and tested and results for all models this has been tested on so I can include a table of results here. Can I suggest the following format, (please feel free to suggest other formats)?

    [01] Model:
    [02] Rom #
    [03] Power on %
    [04] Run time at 90%, (and if possible, at every 10% drop until 5. (I May skip this if people don’t want to include).
    [05] Run time at “charge warning” with %, if possible
    [06] Run time at “system shutdown”
    [07] Usage (Light, medium, heavy)
    [08] Wi-Fi usage during run time, (Off, light, medium heavy – for rough guide)


This work around is just that, and should not be regarded as the final solution.

Background.
Android battery calibration is not generally optimised by default, and usually requires some kind of manual user intervention. Simply charging to 100%, then wiping data or flashing only sets the maximum battery level, the minimum is only guessed. THIS gives the faulty reports and makes us think the device drains too fast. So the key is to show the phone the battery's minimal capacity too, by using it till it is on null.

The X5A's in particular are bad at battery management, both because of poor android implementation, and hardware that is not optimised for long run-times on these devices. This work around attempts to optimise battery run-time and make these devices report battery levels more accurately with respect to the android os only, and does not address hardware limitations, which requires a completely different solution. Users who have tried this work around have reported more reliable battery levels and average run times of 3.5 to 5hrs plus between charges, depending on usage.

Requirements:
    [01] Root.
    [02] Root Explorer file manager.
    [03] "Battery Fix" (only required for method 1), thanks to digrobot
    [04] autostart.apk (only required for method 2), thanks to alva21

Work around Part 1 - Android fix.

Method 1 - digrobot's "Battery Fix"
    [01] Download the file "tcc_modbattery.ko" from digrobot site (check the thread to get the link), and copy it to your sdcard.
    [02] Open Root Explorer and navigate to: /system/etc
    [03] At the top of the Root Explorer window, press R/W (to get write access).
    [04] Click on "Menu" button (top right hand side), select "more", then "New File", then type install-recovery.sh in the dialogue box. Click on "OK".
    [05] Open install-recovery.sh in the embedded text editor, by long pressing on the file, scrolling down, and selecting "Open in Text Editor".
    [06] Type, or paste, the following:
    #!/system/bin/sh
    insmod /system/tcc_modbattery.ko hi=2665 low=2230
    (Note; the lower limit of the battery mod determines when the tablet shuts down).
    [07] Click on "Menu" button (top right hand side), select " Save and Exit".
    [08] Set permissions to chmod 755 (-rwxr-xr-x), by Iong clicking on autostart.sh and select "Permissions", then set the following:
    owner: TTT / group:TXX / other:TTT (T = ticked, X = unticked)
    [09] Copy tcc_modbattery.ko from your sdcard and paste into /system.
    [10] Press R/W again
    [11] Turn off, and begin Part 2.


Method 2 - autostart
    [01] Install autostart.apk (if not already installed).
    [02] Open Root Explorer and navigate to: data/opt/
    [03] At the top of the Root Explorer window, press R/W (to get write access).
    [04] Click on "Menu" button (top right hand side), select "more", then "New File",then type autostart.h in the dialogue box. Click on "OK".
    [05] Open autostart.h in the embedded text editor, by long pressing on the file, scrolling down, and selecting "Open in Text Editor"..
    [06] Type, or paste, the following:
    insmod /system/tcc_modbattery.ko hi=2665 low=2230
    (Note; the lower limit of the battery mod determines when the tablet shuts down).
    [07] Click on "Menu" button (top right hand side), select " Save and Exit".
    [08] Set permissions to chmod 4755 (-r--rwxr-x), by Iong clicking on autostart.sh and select "Permissions", then set the following:
    owner: TTT / group: XTX / other: XTT (T = ticked, X = unticked)
    [09] Press R/W again
    [10] Turn off, and begin Part 2.


Work around Part 2 - Battery Recalibration.
Strongly recommended, especially after wiping data or flashing.

    [01] Charge until FULL, while the device is off.
    [02] Start in RECOVERY and WIPE battery stats in the "advanced" menu.
    [03] RESTART android (yes, it may already report 98% or less).
    [04] USE phone heavily, don't worry if it appears to drain quickly. Use it untill the Android system turns OFF automatically. If you are only getting two hours or so before shut down, then try rebooting the tablet after it closes down, and repeat this until the tablet no longer boots at all -- the battery is now drained to the point where the tablet will not boot. An alternative method is to boot into clockwork recovery at this stage and leave the Tablet to shut down automatically. (Note; NOT discharging the battery fully may prevent the battery mod from working properly.)
    [05] PLUG IN your charger, TURN ON android and wait till it is FULLY charged again. (It is better if you don't use the device at this charging up).


A few suggestions for battery run-time conservation. (Feel free to suggest some more).

• Turn off “Network Notification”, in Wi-Fi settings.
• Turn off “Use Packet Data”, in Mobile Networks, (if available).
• Turn off “Wi-Fi”, when not required. In fact turn off any thing comms related when not required, as constant scanning is a big battery drain.
• Considering using a start up manager to stop applications from automatically loading until you want them, (this option will also free up some run-time memory).


(Tired now - I need to go to bed) :-)

This post has been edited by tiberian: 25 June 2011 - 11:27 PM

X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#2 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 25 June 2011 - 10:33 PM

Reserved for Battery stats / results.

It would be good to find out just how tablets this will work on! :-)

Thank you. :-)

This post has been edited by tiberian: 25 June 2011 - 10:54 PM

X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#3 User is offline   gunner49 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 2
  • Joined: 18-July 11

Posted 18 July 2011 - 12:40 PM

Thanks for this information
0

#4 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 19 July 2011 - 10:13 PM

View Postgunner49, on 18 July 2011 - 12:40 PM, said:

Thanks for this information


Cool, thanks very much - you're very welcome. :-)
X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#5 User is offline   Rughalt 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 4
  • Posts: 22
  • Joined: 28-July 10

Posted 31 July 2011 - 04:02 PM

Hi,
I have not conducted full tests yet (and I have HaiPad M701-R), but I have re-calibrated battery yesterday, and I used my tablet today, and I must say I'm surprised by the results. Before recalibration, device turned off after approx. 6h standby time (and virtually no usage). After recalibration I've got 2h medium/light usage (ebooks and angry birds), and 10h on standby, with 20% battery left.

Thanks tiberian!

So, data in proposed format:
[01] Model: HaiPad M701-R 2GB
[02] Rom #? - 2.3.1 from HaiPad site
[03] Power on 98%
[04] Not able to calculate, battery level fluctuated
[05] 13h (2h medium usage, 11h standby)
[06] No data yet
[07] No data yet
[08] No data yet

Edit: I think new firmware fixed sleep problems with this tablet, and combined with battery recalibration, I've clocked 15h idle time (with 30% battery left, and 1h wifi on).

This post has been edited by Rughalt: 01 August 2011 - 04:05 PM

0

#6 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 01 August 2011 - 07:09 AM

Thanks for your contribution Rughalt. I hoped this thread would be useful, but as I said earlier, I only put it together and the credit belongs to the original source contributors. :-)
X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#7 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 18 February 2012 - 02:34 PM

I have done the CM7 and clockworkmod to my X5A, but I cannot complete the battery fix, when i try to copy the ".ko" file to /system, I get an error about no access. If someone is following this thread, and can help, I'm listening. Thanks

The step 8 of method1 directions are wrong for setting the permissions, it was fun figuring that out. LOL

This post has been edited by fast96: 18 February 2012 - 02:41 PM

0

#8 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 18 February 2012 - 07:41 PM

View Postfast96, on 18 February 2012 - 02:34 PM, said:

I have done the CM7 and clockworkmod to my X5A, but I cannot complete the battery fix, when i try to copy the ".ko" file to /system, I get an error about no access. If someone is following this thread, and can help, I'm listening. Thanks

The step 8 of method1 directions are wrong for setting the permissions, it was fun figuring that out. LOL


Hello mate. I've messaged you about the battery fix. If you intend to use it with _fun's CM7 Gingerbread, I don't think it will work, as the module was compiled for the Eclair kernel, but there's harm trying. You will need R/W access to place the module in the /system folder. I know that in Root Explorer, you just click on the button at the top when you enter the folder. :-)

This post has been edited by tiberian: 18 February 2012 - 07:44 PM

X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#9 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 18 February 2012 - 11:40 PM

I just tried both methods again, no luck. Thanks for the help.

Next, the X5A doesn't have cell service, but apparently the wifi is considered cell standby, because that's where most of the battery usage goes, gonna try without leaving wifi on and see how fast it drains.
Is there any way to load the "hi and low" battery settings directly?
0

#10 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 19 February 2012 - 07:48 AM

When you say you've had no luck with either method, can you be more specific? Usually, one method, or the other works. :-)
X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#11 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 19 February 2012 - 12:21 PM

OK, tried some more stuff.

First

method 1, install-recovery.sh should be autostart.sh

the permission ticks should be TTT, TXT, TXT (or the permission stated should be different)

If I execute the autostart.sh file, my battery widget starts listing better increments, but when I restart the tablet, it reverts to the old 10%-20% increments. So I believe it does not autostart on boot. Any ideas on how to fix this in CM7?

Thanks for your patience and help.
Dan
0

#12 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 19 February 2012 - 12:35 PM

Now this seems to work, but only if I execute the r/w permissions and the autostart.sh file through Root Explorer. Rebooting won't allow the autostart.sh or it won't execute it.

Would autostart.apk fix this? How do I use Autostart.APK?
0

#13 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 19 February 2012 - 03:07 PM

At 2.5 hours it shut down, restarted and it shows 10%. This is definitely working. :yahoo:
0

#14 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 19 February 2012 - 04:02 PM

Couldn't live with having to start the autostart manually, so I tried Autostart (Root) by blank-online.eu, available from the market free. It specifically states that it will start the autostart.sh. I had to use root explorer to add a folder called "opt" to the data folder in the root directory, then add the edited autostart.sh file from method #2. The permissions ticks for this are wrong like the ones in method #1, they go by columns, not rows. Just look for the resulting permission. After restarting, I had to give superuser permission to autostart.sh

TADA!! it works! 8)

This post has been edited by fast96: 19 February 2012 - 04:05 PM

0

#15 User is offline   tiberian 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 19
  • Posts: 148
  • Joined: 13-September 10

Posted 19 February 2012 - 06:19 PM

View Postfast96, on 19 February 2012 - 04:02 PM, said:

Couldn't live with having to start the autostart manually, so I tried Autostart (Root) by blank-online.eu, available from the market free. It specifically states that it will start the autostart.sh. I had to use root explorer to add a folder called "opt" to the data folder in the root directory, then add the edited autostart.sh file from method #2. The permissions ticks for this are wrong like the ones in method #1, they go by columns, not rows. Just look for the resulting permission. After restarting, I had to give superuser permission to autostart.sh

TADA!! it works! 8)


Cool! As far as I know, you're the only one who has got it working with a Gingerbread kernel. :-)
X5A Team Telechips Froyo 2.2.1
X5A-G #157
Fujitsu Stylistic ST5112 XP Tablet Edition.
0

#16 User is offline   fast96 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 6
  • Posts: 53
  • Joined: 26-October 10

Posted 19 February 2012 - 07:43 PM

Here are some corrections... I am not a programmer, but this worked for me.

This is for CM7 Gingerbread on the X5A-G (but some corrections apply to Eclair)

I recommend Method #2


Work around Part 1 - Android fix.

Method 1 - digrobot's "Battery Fix"

[01] Download the file "tcc_modbattery.ko" from digrobot site (check the thread to get the link), and copy it to your sdcard.
[02] Open Root Explorer and navigate to: /system/etc
[03] At the top of the Root Explorer window, press R/W (to get write access).
[04] Click on "Menu" button (top right hand side), select "more", then "New File", then type autostart.sh in the dialogue box. Click on "OK".
[05] Open autostart.sh in the embedded text editor, by long pressing on the file, scrolling down, and selecting "Open in Text Editor".
[06] Type, or paste, the following:

#!/system/bin/sh
insmod /system/tcc_modbattery.ko hi=2665 low=2230 (space after insmod and ko)

(Note; the lower limit of the battery mod determines when the tablet shuts down).
[07] Click on "Menu" button (top right hand side), select " Save and Exit".
[08] Set permissions to chmod 755 (-rwxr-xr-x), by Iong clicking on autostart.sh and select "Permissions", then set the following:
owner: TTT / group:TXT / other:TXT (T = ticked, X = unticked)
[09] Copy tcc_modbattery.ko from your sdcard and paste into /system.
[10] Press R/W again
[11] Turn off, and begin Part 2.



Method 2 - autostart

[01] Install autostart.apk from blank-online.eu (if not already installed)Link to Autostart(Root) app.
[02] Open Root Explorer and navigate to: data/opt/ (if there is no opt folder, create one)
[03] At the top of the Root Explorer window, press R/W (to get write access).
[04] Click on "Menu" button (top right hand side), select "more", then "New File",then type autostart.sh in the dialogue box. Click on "OK".
[05] Open autostart.sh in the embedded text editor, by long pressing on the file, scrolling down, and selecting "Open in Text Editor"..
[06] Type, or paste, the following:

insmod /system/tcc_modbattery.ko hi=2665 low=2230 (space after insmod and ko)

(Note; the lower limit of the battery mod determines when the tablet shuts down).
[07] Click on "Menu" button (top right hand side), select " Save and Exit".
[08] Set permissions to chmod 4755 (-r--rwxr-x), by Iong clicking on autostart.sh and select "Permissions", then set the following:
owner: TXX / group: TTT / other: TXT (T = ticked, X = unticked)
[09] Press R/W again
[10] Turn off, and begin Part 2.
(11) You will need to apply Superuser permissions at restart.



Work around Part 2 - Battery Recalibration.
Strongly recommended, especially after wiping data or flashing.

[01] Charge until FULL, while the device is off.
[02] Start in RECOVERY and WIPE battery stats in the "advanced" menu.
[03] RESTART android (yes, it may already report 98% or less).
[04] USE phone heavily, don't worry if it appears to drain quickly. Use it untill the Android system turns OFF automatically. If you are only getting two hours or so before shut down, then try rebooting the tablet after it closes down, and repeat this until the tablet no longer boots at all -- the battery is now drained to the point where the tablet will not boot. An alternative method is to boot into clockwork recovery at this stage and leave the Tablet to shut down automatically. (Note; NOT discharging the battery fully may prevent the battery mod from working properly.)
[05] PLUG IN your charger, TURN ON android and wait till it is FULLY charged again. (It is better if you don't use the device at this charging up).

This post has been edited by fast96: 19 February 2012 - 09:00 PM

0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users