Database Users

[Q] horrendous battery life--memory full

My wife just got the phone...goes from 100% at 10pm to 0% at 6am.
From 100% at 7am to 30% at 12pm...
Simple use (phone call, screen on while searching for stuff on the phone, not online) will bring the battery down about 1% a minute...
What's the deal??? It's been doing this straight out of the box...
what have you guys (and gals) done to truly stretch the battery out?
I can run my HD2 with Android, and it lasts me at most 2 days without charging...she can't go 1/2 day without the battery arleady telling her it's low.
also, she's been getting these "memory full" messages--again, we haven't loaded any programs other than maps, jorte, something simple...
how much memory does this phone come with, and why would a message not allowing her to even send a text message come about? No. she's not a heavy texter--but even then, her 5 year old Jitterbug of a phone did just fine with over 1 1/2 years of texts...
Getting pretty frustrated with the phone--battery life, full memory, and all...
By the way, I did root the phone, and went to the systems folder to try and delete bloatware, but it didn't allow me to...tips?
Thank you for reading my rant...

Same problem here
I have the same problem with my FlipSide. Had it for about a month before I got the "Low memory" warnings, but definitely the battery life sucks ... lasts a day if I'm lucky. At first I was doing soft resets to get rid of the memory warnings, but then they became more and more prevalent, until finally I had to do a factory reset. Fortunately, motoBlur (using gmail account) backed up all of my contacts and most of my preferences. All I had to do was re-install the apps from the Marketplace and update a few remaining prefs. But I would certainly not rec this phone to anyone.

telegraph0000 said:
My wife just got the phone...goes from 100% at 10pm to 0% at 6am.
From 100% at 7am to 30% at 12pm...
Simple use (phone call, screen on while searching for stuff on the phone, not online) will bring the battery down about 1% a minute...
What's the deal??? It's been doing this straight out of the box...
what have you guys (and gals) done to truly stretch the battery out?
I can run my HD2 with Android, and it lasts me at most 2 days without charging...she can't go 1/2 day without the battery arleady telling her it's low.
also, she's been getting these "memory full" messages--again, we haven't loaded any programs other than maps, jorte, something simple...
how much memory does this phone come with, and why would a message not allowing her to even send a text message come about? No. she's not a heavy texter--but even then, her 5 year old Jitterbug of a phone did just fine with over 1 1/2 years of texts...
Getting pretty frustrated with the phone--battery life, full memory, and all...
By the way, I did root the phone, and went to the systems folder to try and delete bloatware, but it didn't allow me to...tips?
Thank you for reading my rant...
Click to expand...
Click to collapse
I don't know what your exact issue is.... but if you search thru the market and find link2sd... and follow the instructions... you can deal with the memory issue...
Second... i use juicedefender... it lets me get thru most of the day on one charge... though if i use slacker or pandora i have to charge during the day...
Sent from my MB508 using XDA App

Awesome. link2sd works wonders. Thanks.

YES - juicedefender works wonders .... on my second day of battery life now and still "in the green" !!

what settings do you have to make it last that long?
I'm amazed that with so many people that made the choice for a Flipside (based on thread views) that no one has come up with a Blur free rom as of yet...

try using something called links2sd too....helps with memory issue

The problem with the memory filling up, aside from the dreadfully small amount we have to start with, is there's some bug in the rom that steadily builds /data/local.prop.bak until it fills the entire /data partition. As far as I can tell, the process that does this is using a pretty ridiculous amount of cpu as well, the phone often is physically hot to the touch because of it.
My workaround, which isn't for everyone, is to just open a command line when I first boot the phone, erase local.prop.bak and replace it with a 0-bye file, change the permissions to 000 and owner to root, and then kill the process. It only takes a minute, and can be done from a terminal app on the phone. On a reboot, it needs to be done again, but I rarely have to reboot my phone, and I often go 36-48 hours between charges now.
I'm extremely frustrated that we haven't seen a software update, either to address this common issue or upgrade us to something newer than 2.1. 168mb of app space is simply unacceptable, especially on a phone with no option to move stuff to SD built in. My poor original MyTouch 3G had more space, it's just ridiculous.

Do you have an exact walkthru on how to do this?
Sent from my MB508 using XDA App

Sure! Open a terminal on the phone, or adb shell into it.
su
cd /data
rm local.prop.bak
echo > local.prop.bak
chown root.root local.prop.bak
chmod 000 local.prop.bak
I find that this sometimes makes a related process run away with 100% cpu. From the command prompt, run "top" and check to see if there's something eating all the cpu, I forget the exact name of the process but I'll edit this next time I reboot my phone. Mine typically has a PID of 1499, but individual phones may be different. Once you find the PID, run "kill <pid>" (ie, "kill 1499") and it shouldn't restart.
(edit)
So, a bit of an update... I noticed my local.prop was something ridiculous like 16mb, so I decided to take a look at it... It seems like it's getting corrupted also, so I wiped out everything unreadable, and this solved my issue with the growing local.prop.bak file. It seems like it's growing again, so it's something that'll need to be dealt with on a regular basis, but at least it's not needed on every reboot. I'm tempted to do a fresh reinstall from the .sbf and back up the original file, so I can see what exactly should be there.

Nook Battery Usage

Hi...
So, I've opened up Nook Color Tools and clicked All Settings in order to find out more about my Nook.
Are these findings normal?
Attached scr...
The battery seems to drain quite quickly too, yesterday I've fully charged it, now this? Using wifi all the time, I've sent some emails with gmail and tried browsing web and failing
Stock 1.1.0, FT1.5-beta5'ed.

From my experience that is normal for a nootered nook. I unrooted my nook and did a manual root and did not install any Google apps, or any other un-need junk. Now granted i have ADB install stuff but my battery life is unchanged. What ever get installed with the Gapps and other just runs the battery use threw the roof.
So to answer you question yes that is normal for the automated roots.

Thread being moved to general.
This is not a mod, ROM or kernel.

I disagree; the issue seems related to nootering. but I could've started this in the nooter thread so maybe you could move this into the MinimalTouch1.5-beta5 thread for I believe it's clearly a mistake - how can there be 70% battery usage of cell standby, if the nook doesn't have a cell radio?
How does this application measure it's battery usage, what is "cell radio" - is it an app, like Phone.apk ?

Is it registered?
If found that my nook only lasted a couple of days unregistered, three weeks ago I registered it, haven't charged it since.

from what i learned what ever nootering does or installs makes android look for cell signal or maybe just try to send signal. I tried all the suggestions i delete the phone.apk plus a dozen others. but what i learned was these apk were always there. the issue was that once you nootered something starts to try to use them or keeps them awake. My battery life was about 3 days.
I tried the registration thing as well.
All i know is i unrooted my nook. then did a manual root. turned on adb wireless. Installed superuser, busybox, then manual installed apps by adb installing them, and my battery life is that of an unrooted nook. I have no Google apps installed. or any of that other junk. I'm not sure which app causes the issue but what ever it is it is part of the nooter not because of it being rooted.

betterbatterystats
rm phone and dialer apks
freeze gapps when not in use and anything else if possible
bad apps prevent sleep - analyse with bbs
all this due to Google's dalvik, which isn't handling wakelocks or enabling us to do it manually. only way is to guess and disable things at the moment. effects all android phones and the main reason why iPhone with its crippled single tasking works better
ciao

Since a Cell Radio doesn't actually exist, there is no actual data for Cell Radio, therefore Battery Statistics displays the wrong info, however the reason your nook is dying so fast if I had to reason based on your screen shots, is because you're leaving your Wifi on which is taking up a good portion of your battery.
Nootering doesn't make the device actually try to use the Cell Radio or any such thing, the stuff has always been there, and if you manually rooted by using a hacked APK and installing nook color tools, you would find that "Cell Radio" still contains the most "Battery" usage despite the fact it's not actually using any battery.
Another thing to keep in mind is when you've used Nooter and installed Gapps and stuff (and you leave your Wifi on) you'll have significantly less battery life, because it's doing all the data updates for Gmail, and any other apps you've also installed. This therefore causes it to use your Wifi more, and waste battery life. This isn't just a "Nook" thing, this is true for all android devices, if you have Apps that need to use Data to get updates, and they're getting the updates all the time you'll find you have significantly less battery life.
Normally on a normal android device we'd have access to Accounts & Settings, which would allow us to access options for setting when Data Sync happens, but on the nook you don't have such options. So therefore they happen (probably) every 15 minutes. This causes your battery life to go down.
To remove the "Cell Radio" from the battery statistics bit you can delete/freeze/rename Phone.apk and TelephonyProvider.apk
Note: This has no affect what so ever on your battery life, it only removes Cell Radio from battery statistics so you get a more accurate reading.
Move them using this:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
To undo this use:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.OLD /system/app/Phone.apk
adb shell mv /system/app/TelephonyProvider.OLD /system/app/TelephonyProvider.apk
adb reboot

I figured as much, and wanted to share this info here, but you already beat me to it
Nonetheless, like you wrote above, I do not need Phone.apk and TelephonyProvider.apk - there's com.android.phone running in the background which I do not need.
It could however be waking up the device from deep sleep a lot, and it's not necesarily WiFi - B&N claims 3 weeks of WiFi on usage so with background processes, I think I should be able to pull at least a week.
Bear in mind that WiFi turns itself off with screen off, at least that's how it's configured out of the box.
So far, I kicked Phone and TelephonyProvider, will see if anything improves.
ps shows this:
app_31 1218 1205 636 328 c0246930 afe0c74c S /system/bin/logcat
app_31 1220 1205 636 328 c0246930 afe0c74c S /system/bin/logcat
How can I check what app is app_31 ?

imachine said:
app_31 1218 1205 636 328 c0246930 afe0c74c S /system/bin/logcat
app_31 1220 1205 636 328 c0246930 afe0c74c S /system/bin/logcat
How can I check what app is app_31 ?
Click to expand...
Click to collapse
The parent PID of 1218 and 1220 is 1205 (third column).
When you check that it will undoubtedly show /sbin/adbd, the ADB demon.

Anyone experiencing heat issues and fast battery drain?

Apologies for cross-linking threads, but I feel it's important enough for people to not miss and see if this fixes their battery and heat issues:
http://forum.xda-developers.com/ver...p-s7-rooted-battery-drain-phone-heat-t3453130
It would be great if anyone has a few minutes to run the adb logcat tests as a way of better proving that in fact those were the issues.

Actually I would be very curious if anyone with heat/battery issues could post the following after running adb logcat for a few minutes (~5 would be good) -- if you are familiar with the grep command I would run this after collecting the logs: grep -e 'Scheduling restart of crashed service .*$' to see how many times this log appeared.

I need dmesg and logcat/boot information from either the CN or US LePro3

I have what I needed, thanks!
Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell df -P > df-P.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:
Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:
Run "adb shell"
Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"
Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.

I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.

secXces_debaki said:
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
Click to expand...
Click to collapse
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.

dr4stic said:
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
Click to expand...
Click to collapse
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.

secXces_debaki said:
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
Click to expand...
Click to collapse
Well, don't get yourself into any trouble. I'm not in the business of ending relationships None of the commands modify anything, they just read information and dump it into a file. Other than rebooting, your device won't need to go offline. Also, if you HAVE modified your device in terms of ROM or whatever, please include a list of your mods or whatever in the message you send me with the text files zip.
PS> I've visited your area, or at least the one listed with your profile on XDA. It's a beautiful place. If I could get a visa worked out, it's on my list of places in europe I'd love to move to, possibly in retirement

U are planing to get one x720/7?
There are some way beautiful places around in Germany.
Can u maybe help me with my meta-inf?

secXces_debaki said:
U are planing to get one x720/7?
Click to expand...
Click to collapse
I'm giving it some very serious thought. I'm in the US and the x727 will be on sale on wednesday at US$300, which is very compelling for a device with an msm8996pro, even if the camera is average at best, the screen is less than impressive, and it's missing a headphone jack. My G2 is starting to act up and I need something cheap for the short term.
In any case, I'm doing my research now. I've downloaded the ROMs for 17s (both the stock CN version and the modified IT version). The kernel sources are released for x727, and I imagine the x720 kernel can likely be built from the same sources, in fact I wouldn't be surprised if everything about the kernel was the same. So I wanna see if I can get a kernel and rom building. I may attempt a TWRP build first, since I'd want that anyway, and it's simple enough to boot from fastboot and see if things work. But, I need help understanding the system. And that's where the information gathering in this post comes in.
secXces_debaki said:
Can u maybe help me with my meta-inf?
Click to expand...
Click to collapse
I have no idea what you're referring to with the meta-inf.

I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^

U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?

secXces_debaki said:
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
Click to expand...
Click to collapse
I would really like the logcat and logcat-radio to be running from the moment just after the hardware logos on the screen start showing up, once EUI starts to boot. The logcat is circular and has a limited buffer. Once it reaches the end of it's buffer, it starts overwriting itself, therefore it only keeps a certain amount of the logs in memory before they're gone. Your logcats were therefore incomplete. In more basic terms, I don't see where the system started booting up, that part of the log had already been overwritten when you took the log.
I also sent you a response requesting additional information, and for you to re-run one of the other commands that also errored out.
I do appreciate the help, I really do, thank you

Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.

secXces_debaki said:
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
Click to expand...
Click to collapse
Yeah, that doesn't help at all. Meta-inf to me is a file included in a flashable zip. It isn't even a main file, and it isn't even particularly important. It certainly wouldn't damage the baseband. The baseband, otherwise known as the modem or radio, controls your phone. It's like the brain stem, it controls the most basic automatic responses. Generally if your radio was broken, your phone would be hard bricked, there would almost certainly be no recovering from that.
Did you flash a modified radio/firmware to your device?
secXces_debaki said:
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
Click to expand...
Click to collapse
Heh, thanks
That actually lines up similarly to other things I've head about the device. Your assessment of the screen seems more positive than some, but then that sorta thing is a bit of personal preference. Frankly I don't game (much) to the point where I want a QHD or 4K display, and I don't intend to do VR. The reason I wanted a msm8996 is for the other advanced capabilities. The thing I'm looking forward to most is getting WiFi Calling working for T-Mobile, my reception isn't always great and that would be fantastic for me
As for the sound, I learned a long time ago to accept disappointment there. And I'm OK with that. I really wanted a headphone jack. Adapters tend to be bulky and/or break, and I don't like to be restricted to a single pair of headphones just because they have the right connector. You also can't easily share headphones with a CDLA connection. I have heard that the speaker output is nice, and I'm looking forward to that.
Mostly I'm excited that the kernel is not much modified from the CAF sources. Once I've verified that whatever it is I'm working on will actually boot, I will be able to upgrade to a newer revision of the kernel (with security fixes) and possibly even jump to the UM branch for the kernel, which is unifying for the Nougat release. I'm using the op3 as a template for my cm device and at the moment just gathering information. I don't even know if I'll buy the device yet or even make a rom. But it's what I'm looking into. This is a side project for me, and I desperately need to find a job, that takes priority.

secXces_debaki said:
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
Click to expand...
Click to collapse
I don't know how fast the phone boots, but usually I have the command already typed into the window, then I reboot and as soon as the first logo appears on the screen I hit enter. The command may not see the device immediately, and it'll say "awaiting device" and that's fine, it'll start logging as soon as the device appears. Then do CTRL+C 30 seconds after all the final connections to the cellular network are done

Managed to fix my standby drain..
U got a pm with the last logs. Hope it's good

Stock kernel core control

Maybe everyone already know this but it is possible to turn off any core(bit or little) without installing any custom kernel. But your phone have to be rooted. I tried this on stock nougut but will probably work on marshmallow. /sys/devices/system/cpu/cpu0/core_ctl/
/sys/devices/system/cpu/cpu4/core_ctl/
In those two folder there are files that controls cpu (cpu0 for little cpus and cpu4 for big cpus)
(Try with your own risk ,i wont be responsible for any damages to your phone)
For an example:
echo "0" > /sys/devices/system/cpu/cpu4/core_ctl/max_cpus
If you execute this code in terminal emulator with root permission the big cores of your cpu will shut down.
To turn on big core :
echo "2" > /sys/devices/system/cpu/cpu4/core_ctl/max_cpus
You can control load_theshold to turn off or turn on cpus.
This post maybe won't be much helpful for newbies. But maybe experts can come up with some ideas to use this to control cores for better battery life and performance.
And sorry for my bad english.