FORUMS

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

What’s Next for Samsung and Its Flagships?

If we were to say that the Galaxy S6 was a leap of faith made by Samsung, we … more

The Ultimate Showcase of dBrand Skins

In the search for ways to protect, accessorize, and personalize; a user has many options. One … more

Battery at 14%

111 posts
Thanks Meter: 38
 
By drcyber, Senior Member on 31st January 2014, 08:48 AM
Post Reply Subscribe to Thread Email Thread
10th February 2014, 12:17 PM |#21  
Junior Member
Thanks Meter: 14
 
More
Red face 100 %
Just by the way, if interesting for anybody:
I had my FP1 stuck to 99% when charging it with a dedicated charger (which only delivers 850 mA, btw). Connecting it to a desktop computer, it charged to 100% (while downloading OSMand~ mapdata, so not exactly idle).
 
 
10th February 2014, 10:31 PM |#22  
Member
Flag Heidelberg
Thanks Meter: 62
 
More
Quote:
Originally Posted by haiag

Did you unload the battery before below 14% ? Than charge to less than 99%, afterwards the 14% thing shouldn't appear.
So 13% -> max 98% -> No 14% Stuck...

You're right (click to enlarge):



Thanks for the heads up. I already changed the info in my previous post.
17th March 2014, 08:06 PM |#23  
superdragonpt's Avatar
Recognized Developer / Recognized Contributor
Flag Lisbon
Thanks Meter: 8,030
 
Donate to Me
More
I actually had this problem with another MTK device.

Solution:

- Remove the mtk debugger PATH from kernel rmdisk.
- Disable (=Off) the aeed service on default.prop

(I don't own this device)

But if it haves an unlocked boot loader, its rather simple to to it.

Regards
The Following User Says Thank You to superdragonpt For This Useful Post: [ View ]
16th May 2014, 09:21 AM |#24  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by superdragonpt

I actually had this problem with another MTK device.

Solution:

- Remove the mtk debugger PATH from kernel rmdisk.
- Disable (=Off) the aeed service on default.prop

(I don't own this device)

But if it haves an unlocked boot loader, its rather simple to to it.

Regards

hey,
well, it seems like the battery issue was not solved by the last fairphoneupdate v1.3, unfortunately.
so, probably i'm not the only one who has that anoying problem - still.
although i'm absolutely not familiar with coding android stuff, i'd like to tackle the problem with your proposed solution...
however, i have no glue where to find the rmdisk kernel, and the default.prop.
you said an unlocked boot loader is preliminary. i didn't follow all posts over the last weeks. so is it unlocked (it think it wasn't ?!); and are u willing to help ?!
so long,
SnowTiss
16th May 2014, 09:52 AM |#25  
superdragonpt's Avatar
Recognized Developer / Recognized Contributor
Flag Lisbon
Thanks Meter: 8,030
 
Donate to Me
More
Quote:
Originally Posted by SnowTiss

hey,
well, it seems like the battery issue was not solved by the last fairphoneupdate v1.3, unfortunately.
so, probably i'm not the only one who has that anoying problem - still.
although i'm absolutely not familiar with coding android stuff, i'd like to tackle the problem with your proposed solution...
however, i have no glue where to find the rmdisk kernel, and the default.prop.
you said an unlocked boot loader is preliminary. i didn't follow all posts over the last weeks. so is it unlocked (it think it wasn't ?!); and are u willing to help ?!
so long,
SnowTiss

Hi

Well its easy to check if you have an unlocked boot loader:
- if you have an custom recovery ( like CWM or TWRP) your boot loader is unlocked ( its not possible to flash an custom recovery on an locked bootloader)

If so, then send me your boot.IMG ( find it on your rom.zip) and I change that for you.

Regards
20th May 2014, 09:58 AM |#26  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by superdragonpt

Hi

Well its easy to check if you have an unlocked boot loader:
- if you have an custom recovery ( like CWM or TWRP) your boot loader is unlocked ( its not possible to flash an custom recovery on an locked bootloader)

If so, then send me your boot.IMG ( find it on your rom.zip) and I change that for you.

Regards

hey,
sry it took me so long.
anyways, neither did i install clockworkmod from #chrmhoffmann http://forum.xda-developers.com/show....php?t=2615613 nor the other recovery project.
so seems like: now way.
however:
you mentioned besides CWM the TWRP https://play.google.com/store/apps/d...pmanager&hl=de. is it as easy as it pretends to be for installing with https://play.google.com/store/apps/d...0up.goomanager?
maybe it isn't a wise question...but can install TWRP afterwards i setup the whole system without the necessity to reinstall the rom?
moreover, if, can i install the original rom afterwards (prob not..)? any objections why this shouldn't work?
i assume you know, but in case you don't...the phone is rooted.

thank you in advanced!
cheers
SnowTiss
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes