yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario ROM Development] sliyk:
the fact of the matter is that ive been using this rom for so long without problems and this battery charger thingy just started a few days ago. could this be hardware problem?
[8125, K-JAM, P4300, MDA Vario ROM Development] Stinkfist:
Time for a new battery. Try nothing else until you have replaced it, with a new one, not one from another phone.
[8125, K-JAM, P4300, MDA Vario ROM Development] sliyk:
new battery really? u mean a battery from another phone doesnt do? and yes my battery dies very fast even my friends battery in my phone. cudnt this be a problem in my phone then? cause its his battery
[8125, K-JAM, P4300, MDA Vario ROM Development] Stinkfist:
Its definately a battery issue.

Check out this thread and I think you will relate: http://xdaforums.com/showthread.php?t=353780

Then go to eBay and buy an new OEM replacement for like $10 shipped. I think I paid $8 for mine.
[8125, K-JAM, P4300, MDA Vario ROM Development] corky_aloof:
I personally think it is a bug.

On three separate occasions using various roms, my battery would drain from 100% to 0% in an hour. I would reset everything, recharge and it would run normal without problems.

I do not know what causes this but it does appear to be a software glitch, at least in my case.
[8125, K-JAM, P4300, MDA Vario ROM Development] its right:
try to hard reset your device and then test (after backup your data).

this can give you the clear reason :) (in case of the rom was running well with you).

good luck
[8125, K-JAM, P4300, MDA Vario ROM Development] bachikho:
try another radio!
[8125, K-JAM, P4300, MDA Vario ROM Development] daishi17:
i had the same issue, but it stop draining after i ordered the new battery
[8125, K-JAM, P4300, MDA Vario ROM Development] licensedtoquill:
I suspect that it is not the battery or the unit.

Actually I am suddenly having the same problem with a brand new battery on a brand new Wizard.

I just loaded the newest Mfrazz Rom which seems to be fantastic in its applications, speed etc. however immediately on loading the ROM, my battery does get hot in normal use and drains to 30% in a normal day. I have even loaded the IRDA disable cab to no particular effect.

Is there some specific procedure to which you are referring for hard resetting the Wizard? I assume you don't just take out the battery?
[8125, K-JAM, P4300, MDA Vario ROM Development] mr.incredible:
Dead battery

Lithium batteries can be killed rather easily. I know from rc helis. Most mobile phones use lithium-ion batteries. Helis use lithum-polymer batteries but they have pretty much the same charactoristics. li-poly is a little more volitile, they can and will explode if you charge or discharge too much or too quickly. If you over charge, you kill it. If you over drain, you kill it.

If you are in a place where you get little or no signal turn off the radio. It will discharge quickly if it's searching for a signal. Also if you are not using the bluetooth or wifi turn them off, same thing. That's why they provided the Comm Manager. Try not to let your charge get below 20%. Definately don't let it run completely out or stay that way long.

A dead lithium battery will not hold a charge at all. Just like you see, the numbers dropping off quickly. It will charge fast too.
[8125, K-JAM, P4300, MDA Vario ROM Development] licensedtoquill:
(Snot the battery)

Looking at it afresh, it isn't the battery which is heating up on installation of this ROM, it is the unit itself. The battery seems to be remaining at a comparatively normal temperature though the heat generation does drain it very quickly as I said.

Not sure that this problem has ever been addressed before on these boards? It may be something to do with not flashing to a manufacturer's ROM before flashing to Mfrazz's new one?

Has anyone ever seen these symptoms before?
[8125, K-JAM, P4300, MDA Vario ROM Development] jtrash:
In addition to some of the other posts ,you could check this :

WM6 may need to "learn" the battery levels again.

Try FULLY discharging & recharging your battery 3-4 times.

If this doesn't make things better, maybe you should check if you are running anything strange in the background...
[8125, K-JAM, P4300, MDA Vario ROM Development] mr.incredible:
Lithium batteries don't recover like ni-cad. Spend the $10 and solve the problem. DONT EVER FULLY DISCHARGE A LITHIUM-ION BATTERY. That is the quickest way to kill it.
[8125, K-JAM, P4300, MDA Vario ROM Development] licensedtoquill:
As far as I am aware it is difficult to FULLY discharge one of those batteries in the Wizard? The unit starts giving error messages when it gets to the 15% level and some time thereafter shuts most of its functions down to prevent this. Whenever I have had problems with these units getting hot and even discharging and shutting down, the battery level never seems to be at 0% when I plug it in again. I have never thereafter found any permanent damage to the battery.

I think we should address the problem which seems to be in issue here which is that somehting in the OS is causing the battery to discharge as opposed to replacing the battery and watching the problem continue. At least, that was MY problem.

I am obviously not saying batteries don't die. All I am saying is that for a lot of users, the problem may lie elsewhere. Meanwhile I have flashed back to T-Mobile and re-flashed the newest Mfrazz which SEEMS to be quite VoIP friendly and overnight the unit doesnt seem to have heated up.
[8125, K-JAM, P4300, MDA Vario ROM Development] sliyk:
since i cant order a battery from where i live i tried reflashing my phone and memory card and i think that fixed it. maybe in my case its an os bug. and yes i definitely have been treating my battery badly on discharging and over charging. thanks for the info :)
[8125, K-JAM, P4300, MDA Vario ROM Development] mr.incredible:
They are not that delicate if you know what kills em it's pretty easy to avoid. They don't develop a memory like the older ni-cads. if you are going to store one charge it first. They don't power drain by them selves unless they are in a device. Just don't leave a battery drained. Also they wont over charge in the phone. The phone will stop charging when the battery is full, and 0% is not actually 0volts. There are built in safeguards for the average user.
[Samsung Gear S3] cyaclone:
Prior to my Gear S3, I would get a verbal for messages and calendar events, plus either the ringer on the phone would announce calls or I could get the name of the caller. Now I get none of these but a quick ring for calls and no verbal messages or calendar events except on my watch.

I like using the watch, but would like to hear my messages and calendar events being read out loud.

Is there a way to get both or must I remove these notifications from the watch?

My phone is a Galaxy S7e.
[Zenfone 5 Q&A, Help & Troubleshooting] nheolinkin:
As the title said, I'm gathering some information about screen on time (SOT) of Zenfone 5 1.2Ghz (from 100 to 1-5 percent)

I want to see how my battery is after years by how much time it can handle now. Hope you guys help me.

In comment section, please including your SOT plus:

- What rom are you using? (Kernel version if can)

- Most used network: Wifi or Cellular

- Network setting: Always on or Never (Manually)

- App ram usage (Running Service in Setting/Battery or Develop Options)

Thats all I want to know for now.

Thanks!
[Zenfone 5 Q&A, Help & Troubleshooting] mrsiri:
Using stock rom Kitkat newest version, cause it uses much less battery! :D

I mostly use more of the Wi-Fi on always on

what is mostly using my ram is the screen ( brightness) and android

I will send more information about RAM usage later, my phone is recharging :p
[Zenfone 5 Q&A, Help & Troubleshooting] vaibhavnarain11@gmail.com:
Using 1.6ghz variant.

rom- resurrection remix nougat. but channging of roms didnt had any great impact

only wifi always on.

ram- 40-50% or below free.

sot i get varies from 2hr- 3hrs. only texting and light stuff gives around 2hr 40mins.
[Zenfone 5 Q&A, Help & Troubleshooting] zeetsu:
im using latest kitkat on my 3 years old zenfone 5 single sim variant.

this one with 100% cpu usage all time + [ full screen brightness+ bluetooth + wifi+ gps on ] from 100% to 5%;

This one has only wifi on with full screen brightness 100% to 5%
[Zenfone 5 Q&A, Help & Troubleshooting] nheolinkin:
How long screen on time did you get? That's quite impressive battery graph with wifi and gps always on.
[Zenfone 5 Q&A, Help & Troubleshooting] zeetsu:
Screen was always on in both tests. i used battery drain app to make screen always on with full brightness and wifi in second test and i get 3h45m screen time.

in first test i pushed cpu 100% and activated all gps/bluetooth/wifi etc and i get 1h53m screen time. but phone was really overheated and i scare to do it again (it was burning my hand) :D

actually i was shocked myself when i saw 4 h screen time when i used my phone to only read ebook all day in home with half brightness and i decided to test my phone. Results were amazing i agree, i hope it keeps that way for one more year.

i tested overnight battery usage and it dropped to 85% from 100% within 7 hours with wireless open while android sleep. i guess it might be better to close all network overnights
[Zenfone 5 Q&A, Help & Troubleshooting] nheolinkin:
I wish I still kept the screenshot on Mashmallow to show you.

wireless is not the reason but the google play service. After disable a list of unneeded services, I let wireless enable all the time, gmail and other notification still can be recieved and battery drained 1% per hour (screen off). For specifically, after 6 hours over night, it will drain 6%.

screen on time is normally 3 hours but of course I have to tweak a lot to get this result. If not, battery just drains like hell.
[Zenfone 5 Q&A, Help & Troubleshooting] zeetsu:
i tried to close wifi yesterday , as you mentioned it does not effect the drain.

3 hours sot on marshmallow is great but unfortunately i cant use custom roms cuz i need Gps occasionaly and my simcard often keep loosing signal on thoose . i am considering to get a xiaomi mi or redmi phone by next year but until that i had to use asus zf5 with kitkat 4.4.2 and 3-3.5 sot is best i can wish for.
[OnePlus 5 Questions & Answers] jeweettoch:
.. And yes, 'Gaming do not disturb' is turned off.. I have no idea what the cause could be. Just drove 1,5h with Google Maps on, did some stuff on my phone when I arrived, an hour later I took my phone out of my pocket and no working buttons.. Any suggestions anyone? Oh, and fingerprint unlocking is still functioning.

Edit: weird, after playing around with turning on screen buttons on, off, on, off they suddenly started working again! Maybe this could help people with similar issues!
[Remix OS for PC] Deleted member 7257971:
Hi,

I have tried to install android-x86_64-7.1-rc1.iso on my Yoga Book Windows version I have done and booted to Grub I choosed install Android then everything turn to portrait mode I didn't understand anything.:crying:

My question is how to turn the screen to landscape so that I can install Android on my device

Thank you in advance;)
[Remix OS for PC] Yong73:
Post to a wrong forum

从我的 iPhone 发送，使用 Tapatalk Pro
[Remix OS for PC] Deleted member 7257971:
[MENTION=5977505]Yong73[/MENTION] where should I post, thank you
[Remix OS for PC] Yong73:
The place is where you downloaded it.

从我的 iPhone 发送，使用 Tapatalk Pro
[General Questions and Answers] Android_Dog_Walker:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].

I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following

"Fastboot boot TWRP.img"

to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.

I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;

downloading 'boot.img'...

OKAY [ 0.931s]

booting...

FAILED (remote: invalid kernel address: not lie in memory)

finished. total time: 0.947s

Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.

Can anyone help me please.

Thanks.
[General Questions and Answers] Android_Dog_Walker:
TWRP and Rooting a Cubot Cheetah 2 (Nougat)

I have done a lot of searching and found the following;

a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,

b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.

The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.

Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).

Thanks

Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.

rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.

The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.

This thread can now be closed

I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.
[General Questions and Answers] kaivalagi:
Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?
[General Questions and Answers] Android_Dog_Walker:
I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.

Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.
[General Questions and Answers] kaivalagi:
Gotcha, hopefully someone will

chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....
[General Questions and Answers] EpicFail2017:
Cubot Cheetah 2 Android 7 Root by EpicFail2017

Hi Guys i have a Cubot Cheetah 2 Android 7.

Sorry my english sucks realy!

I found only a soulution to Root it with Magisk 14.2 beta!

1 First Step Download only PC Flash Files V14 170719 and unpack it !

http://forum.cubot.net/viewtopic.php?f=21&t=1475

The ROM this FilePC Flash Files V14 170719

https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw

------------------------------------------------------------------------------------------------------------

2 Step Download and Install last version!

http://spflashtools.com/windows/sp-flash-tool-v5-1728

------------------------------------------------------------------------------------------------------------

3. Step

Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!

Latest Stable Magisk Version: v14.2

Latest Magisk Manager Version: v5.3.5

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

----------------------------------------------------------------------------------------------------------------------------

4 Step

Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !

https://mega.nz/fm/Q6YV3QrZ

http://www117.zippyshare.com/v/EiwE8p57/file.html

----------------------------------------------------------------------------------------------------------------------------

5 Step

Flash with SpFlash the Rom from Step 1 in Format +Download Mode.

Make a backup first from all your Stuff and Apps!

---------------------------------------------------------------------------------------------------------

6 Step

Start Android and make dev option enabel. Usb debug etc!

Install Latest Magisk Manager Version: v5.3.5 from SdCard!

Start and make under Options update beta kanal!

Install Magisk 14.2 Beta and rebot your Phone!

Wolla you have Root this ***** !

---------------------------------------------------------------

7 Step

Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!

For me this step was need after flashing root+room!

https://www.needrom.com/download/mauimeta-version-9-1724/

Mfg

EpicFail2017
[General Questions and Answers] TimeRider_uk:
Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?

I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?

I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?

What is the 'R' near the signal in your screenshots?
[General Questions and Answers] TimeRider_uk:
I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..

I was already on the same version of nougat as the download before I started.

1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).

* Note, install the drivers with the phone NOT connected via USB.

2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)

3. Move the patched boot.img from the magisk folder back to the computer.

4. Run the SPFlash tool load the scatter file, select DOWNLOAD and

untick

everything asides from boot.img

5. With phone switched off, connect it via USB

Flash

Wait until complete

Reboot

Rooted :)

No loss of IMEI or data.
[General Questions and Answers] Android_Dog_Walker:
It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.

Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.
[General Questions and Answers] TimeRider_uk:
That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/

Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!
[General Questions and Answers] Android_Dog_Walker:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).

https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
[General Questions and Answers] toBsucht Psp:
Anyone uploading a mirror of nougat TWRP, please.

Also i´m kind of shy flashing the recovery with patched boot.img, any experience?

Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"

Do you password protect your recovery?
[General Questions and Answers] Android_Dog_Walker:
I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.

An point worth noting is that if you are a new user on needrom, you

need

to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.
[General Questions and Answers] EpicFail2017:
Hi,

Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.

any can fix it on TWRP 3.1.1.1 ?
[General Questions and Answers] toBsucht Psp:
EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^

Still did not find a public nougat TWRP download ;)

Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?

Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://xdaforums.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943

EDIT: switched to supersu, busybox now working ;)

Yesterday xposed appsops was getting a fix it is still unoffical

https://xdaforums.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89

Edit:

updated to magisks unoffical xposed framework 3.1.4