Remove radio out of Kit Kat? - Droid X General

First of all, thanks to everyone who brought Kit Kat to the droid X. I can't post in the actual thread so here I am.
As the title says, is there anyway I can take the radio out of the build without breaking anything. I am using this as a wifi device only and even when I put it in airplane mode, cell standby kills the battery real fast.

No I don't think so...
Sent from my Amazon Kindle Fire using Tapatalk

Related

[Q] Battery drain. Any solutions so far?

Hey guys,
As prolly most of you I came accross some serious battery lifespan issues (during night I drains about 20% of battery and during the day I have to charge it every couple of hours).
Have you heard of any known solution to this problem apart from turning of wi-fi in sleep mode, lowering brightness of the screen etc? To me all of these are just reducing collateral damage while the real problem lies elsewhere.
I've heard that 4.2.1. android worked very good with battery. Is it possible to downgrade it to this version from 4.2.2. without having to root it and thus loosing guarantee?
anachronis said:
Hey guys,
As prolly most of you I came accross some serious battery lifespan issues (during night I drains about 20% of battery and during the day I have to charge it every couple of hours).
Have you heard of any known solution to this problem apart from turning of wi-fi in sleep mode, lowering brightness of the screen etc? To me all of these are just reducing collateral damage while the real problem lies elsewhere.
I've heard that 4.2.1. android worked very good with battery. Is it possible to downgrade it to this version from 4.2.2. without having to root it and thus loosing guarantee?
Click to expand...
Click to collapse
I don't think you have to root to change builds. Of course, if you are unlocked, you can just go and flash a 4.2.1 ROM
If you're rooted than try a custom Rom, Franco kernel, or factory reset.
I'm stock, rooted with Franco kernel on the nexus 4.
Sent from my Nexus 4 using xda premium
Seems similar to what happens with me, only sometimes though. Others is just fine dropping a few percent over night vs a few percent per hour. Not sure what causes it but it does happen. Best right now is about 1% every 30 min or so. Typically its much quicker than that.
Sent from my Nexus 7 using xda app-developers app
I do want to root things cause I just a few weeks ago bricked my Infinity...
How can I get 4.2.1 build back without rooting?
anachronis said:
I do want to root things cause I just a few weeks ago bricked my Infinity...
How can I get 4.2.1 build back without rooting?
Click to expand...
Click to collapse
use the google nexus tool or wugs toolkit. instead of selecting the 4.2.2 build select the 4.2.1 build and select download and install factory rom.it will install the build you selected and will completely wipe out your whole device making it back to the day you bought it.before using any toolkit be sure to save important data from your device to your pc,nandroid backup,or any type of backup you use.its really simple.
---------- Post added at 10:26 AM ---------- Previous post was at 10:20 AM ----------
oh and btw. my battery life is superb.overnight it doesnt drop even 1%.maybe it could be an app that you have installed.i used to use dxtoolbox and for some odd reason battery life was poor.no longer using it and i get the most outta my n7.
Yup, I'm on 4.2.2 stock, rooted. I get days out of a charge. Lose maybe 1 percent over night.
Sent from my cell phone telephone....
Mine just suddenly started doing this. I have been using AOKP Milestone 1, and then updating to the nightlies. But the power drain is huge. Even on the charger, it was charging for 6-8 hours, and is only up to 53%?? I have CPU Spy, and Better Battery Stats, and I can't see anything causing the massive power drain. It ran fine a week ago. Maybe it started with AOKP Nightly 05-21-2013. Going to try flashing back to the one prior to that one.
podagee said:
use the google nexus tool or wugs toolkit. instead of selecting the 4.2.2 build select the 4.2.1 build and select download and install factory rom.it will install the build you selected and will completely wipe out your whole device making it back to the day you bought it.before using any toolkit be sure to save important data from your device to your pc,nandroid backup,or any type of backup you use.its really simple.
---------- Post added at 10:26 AM ---------- Previous post was at 10:20 AM ----------
oh and btw. my battery life is superb.overnight it doesnt drop even 1%.maybe it could be an app that you have installed.i used to use dxtoolbox and for some odd reason battery life was poor.no longer using it and i get the most outta my n7.
Click to expand...
Click to collapse
Where can I get these tools from? Play/Google Store hasn't got any of them in stock.
If you don't need it then set Wi-Fi to turn off when the screen is off. I lose 1-2% overnight that way
Sent from XDA app
anachronis said:
Where can I get these tools from? Play/Google Store hasn't got any of them in stock.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1809195
another thing that is good for adb drivers is pdanet.http://pdanet.co/a
Is drain unique to Wi-Fi 3G Models?
I'm pretty new to android, but I started having this problem too after 4.2.2. It's randomly worse, and other than the usual workarounds you already mentioned, the one thing I noticed that's weird is looking at battery usage stats, the 2nd highest user (after screen) is sdcard app (which displays with an icon showing it's part of the android os, and usage varies between 13-14%). A Google tech tried to convince me that's the AT&T Sim card, but it's not, it started after the update to 4.2.2. Nexus 7 doesn't even have sd card capability...does anyone know what's going on? It seems to me this drain issue should be hugely affecting Nexus 7 users, and I can't find much about it. I'm not rooted and don't really want to 'cause I just wanted a simple little tablet to carry around with me, since the iPad mini isn't great yet.

tried many roms still powering down, I'm lost!

Nexus 4 16gb White
bought off ebay used but in mint condition.
received it with 4.2.2 kitkat, started powering off an losing signal an data so I rooted/unlocked and started with a installing roms, from rooted kitkat roms then back down to 4.2.2 with franco kernel, 27 hybrid radio with various roms and all get the same results of the phone powering off, and earlier today I could barely keep the phone powered on while connected to usb to my pc.
no I do not have the netflix app installed either.
I have done tons of reading and some say it could be a battery issue but my dilemma is that Im about to send this back to the ebay seller and dont want to crack this phone open to check the battery connection or battery itself with the possibility of sending it back.
just hate to return this phone cause I love the looks of the white LG Nexus 4.
From my search of reading endless threads through google that no one has found a definite answer to the phone popwering off, yes found the franco kernel to help with signal along with the 27 hybrid radio.
please chime in if im missing something in my search or is this a sitting duck situation awaiting on google to send a new update??
I pulled the back cover off an noticed towards one end of the battery it had a crease along the top of it kind of sunken in, I checked the connection an put back together. but when I check the battery status is said "good or okay" cant remember which one
Battery's probably screwed
Sent from my Nexus 4 using xda premium
THEBANDIT420 said:
Battery's probably screwed
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Would defective battery also cause signal issues? Im sure it causes the powering down problems of course.
Cheeva316 said:
Would defective battery also cause signal issues? Im sure it causes the powering down problems of course.
Click to expand...
Click to collapse
No but the antenna could be have been damaged when you were looking at the battery
Sent from my Nexus 4 using xda premium
The mention problems were on going prior to me touching the phone

Moto X not built for kit Kat

I've owned a moto x for 1 week now. When I got it, I immediately ignored the kit Kat update, tried using jelly bean for 2 days, I had good to above average battery life.
3rd day, I updated it to kit Kat, my battery life took a big hit!!
Yesterday I received a nexus 5 as a gift, I love it.
I performed an experiment with both phones, I wiped both in recovery (stock, both phones are completely stock) I wiped cache. I then took my SIM out of the moto x. Turned on, only Wi-Fi on both. Then installed the exact same apps on both phones.
Whole time I was doing this I was charging both of them.
One 100% hit both of them I unplugged then at same time and turned screen off, let them sit.
After 6 hrs of sitting, the nexus 5 was at 98% the moto x was at 89%!! That's LOCATION turned off on both. And on the motto x the active screen and hands free control.
I think the nexus is built for kit Kat, most phones have quad core nowadays, I'm thinking that kit Kat just runs better.
The battery life difference is a shocker to me, and fit that reason alone, I'm using the nexus 5 and selling my moto x.
If I could downgrade the moto x, I would for sure, but I need battery life.
EDIT...
I've just redone my test with the same results, I will post pics later.
Sent from my Nexus 7 using XDA Premium 4 mobile app
markdexter said:
I've owned a moto x for 1 week now. When I got it, I immediately ignored the kit Kat update, tried using jelly bean for 2 days, I had good to above average battery life.
3rd day, I updated it to kit Kat, my battery life took a big hit!!
Yesterday I received a nexus 5 as a gift, I love it.
I performed an experiment with both phones, I wiped both in recovery (stock, both phones are completely stock) I wiped cache. I then took my SIM out of the moto x. Turned on, only Wi-Fi on both. Then installed the exact same apps on both phones.
Whole time I was doing this I was charging both of them.
One 100% hit both of them I unplugged then at same time and turned screen off, let them sit.
After 6 hrs of sitting, the nexus 5 was at 98% the moto x was at 89%!! That's LOCATION turned off on both. And on the motto x the active screen and hands free control.
I think the nexus is built for kit Kat, most phones have quad core nowadays, I'm thinking that kit Kat just runs better.
The battery life difference is a shocker to me, and fit that reason alone, I'm using the nexus 5 and selling my moto x.
If I could downgrade the moto x, I would for sure, but I need battery life.
EDIT...
I've just redone my test with the same results, I will post pics later.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You must have a bad moto x. I've let mine sit overnight multiple times and after about 8 hours my battery is still 100%. Three email accounts synced, Wi-Fi, location on.
Either that or you have a really good moto x!!! I find it hard to believe after 8 hrs still at 100%!!
I understand this is a moto x thread and people will defend their phones, I think there is a lot of people experiencing this after updating to kit Kat.
Sent from my Nexus 5 using XDA Premium 4 mobile app
markdexter said:
I've owned a moto x for 1 week now. When I got it, I immediately ignored the kit Kat update, tried using jelly bean for 2 days, I had good to above average battery life.
3rd day, I updated it to kit Kat, my battery life took a big hit!!
Yesterday I received a nexus 5 as a gift, I love it.
I performed an experiment with both phones, I wiped both in recovery (stock, both phones are completely stock) I wiped cache. I then took my SIM out of the moto x. Turned on, only Wi-Fi on both. Then installed the exact same apps on both phones.
Whole time I was doing this I was charging both of them.
One 100% hit both of them I unplugged then at same time and turned screen off, let them sit.
After 6 hrs of sitting, the nexus 5 was at 98% the moto x was at 89%!! That's LOCATION turned off on both. And on the motto x the active screen and hands free control.
I think the nexus is built for kit Kat, most phones have quad core nowadays, I'm thinking that kit Kat just runs better.
The battery life difference is a shocker to me, and fit that reason alone, I'm using the nexus 5 and selling my moto x.
If I could downgrade the moto x, I would for sure, but I need battery life.
EDIT...
I've just redone my test with the same results, I will post pics later.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Find out, in about phone, if dev option is on. Tap many times on build # to enable. Then be sure both phones are set to ART runtime!! You will need lots of time & battery.I think the x will do much better then.
No, I think you should get that checked out. I've yet to have mine die on me in less than a day with normal use. Usually is only at 40-50% when I go to bed, and uses almost no battery while idling overnight, I'm guessing due to the architecture. I'm not saying the moto is better than the nexus, just a shame to hear you're having a bad experience with yours. Good luck with it!
Screen shots from gsam would help see what's happening.
But, I had phenomenal battery life on my x.....til my wife got it. Lol avid facebook user....she lost a good chunk of battery life from it alone. Cause its still setup exactly how I had it....but she's always on facebook (pics constantly loading) and she uses the "phone" way more...another drain.
However.....standby time for me never got much lower that 1 percent per hour. My n5....0.4 per hour. I assume active and touchless must keep the x standby drop higher, or radio maybe? Something anyway. I stopped worrying, since overall the x got great battery life. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I took the KitKat update the day I got my phone on 3/7/2014 and the battery life is better than my old Nexus. I put the phone on charge at 1600 take it off around 2000 when I wake up at 600 and the phone is at 97%. By the time I get home from work at 1500 it's down to 60%. It'll go 24 hours on one charge easy but I charge it every 12, or so. Some days I'm on it all the time.
Then again, I do have an unlocked boot loader, I'm rooted and I've got Greenify hibernating most of the apps I don't constantly use.
markdexter said:
I've owned a moto x for 1 week now. When I got it, I immediately ignored the kit Kat update, tried using jelly bean for 2 days, I had good to above average battery life.
3rd day, I updated it to kit Kat, my battery life took a big hit!!
Yesterday I received a nexus 5 as a gift, I love it.
I performed an experiment with both phones, I wiped both in recovery (stock, both phones are completely stock) I wiped cache. I then took my SIM out of the moto x. Turned on, only Wi-Fi on both. Then installed the exact same apps on both phones.
Whole time I was doing this I was charging both of them.
One 100% hit both of them I unplugged then at same time and turned screen off, let them sit.
After 6 hrs of sitting, the nexus 5 was at 98% the moto x was at 89%!! That's LOCATION turned off on both. And on the motto x the active screen and hands free control.
I think the nexus is built for kit Kat, most phones have quad core nowadays, I'm thinking that kit Kat just runs better.
The battery life difference is a shocker to me, and fit that reason alone, I'm using the nexus 5 and selling my moto x.
If I could downgrade the moto x, I would for sure, but I need battery life.
EDIT...
I've just redone my test with the same results, I will post pics later.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
With everything on, GPS,location, ect and on WiFi all Verizon bloat removed. At three months on kitkat I drop 3-4% average at ten hours off charge. Once I got 1% drop over 8 hours and another 2% also at 8 hours. So not knowing if your nexus is new but the more the X settle in the better it gets.
Eclipsed X
ghostt021 said:
With everything on, GPS,location, ect and on WiFi all Verizon bloat removed. At three months on kitkat I drop 3-4% average at ten hours off charge. Once I got 1% drop over 8 hours and another 2% also at 8 hours. So not knowing if your nexus is new but the more the X settle in the better it gets.
Eclipsed X
Click to expand...
Click to collapse
Maybe so, I can't be waiting a couple of months for it to settle in.
Sent from my Nexus 5 using XDA Premium 4 mobile app
markdexter said:
Either that or you have a really good moto x!!! I find it hard to believe after 8 hrs still at 100%!!
I understand this is a moto x thread and people will defend their phones, I think there is a lot of people experiencing this after updating to kit Kat.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had another Moto X that didn't keep the chrge well. It would drop about 5% in hour after unplugging. So it happens. I didn't take into account about your stock. I have all the verizon crap removed and some unwanted moto apps. Very debloated on my set up.
I have found the solution for power management wakelocks on Kitkat. Many of you might be seeing that Wakelock detector shows phone is staying awake for 40-50% of the times since kitkat update.
Most of these wakelocks are thanks to Power manager service and pm8921_chg wakelocks. After removing the phone from charger these wakelocks causes phone to stay awake when it shouldnt.
I think I have found a solution.
When your battery is 100% switch off the phone. Remove the charger. Let it go to blank screen and then power it back on. Now when phone boots without charger connected to it, use it normall and you will see the wakelocks are no longer keeping phone on for 40-50% of the time. It is back to normal 10-11% or lower depending on use and phone gives great battery life.
I am yet to do lot of testing or reading on this, but this is just an observation. Worth giving it a try.
I get high calenderbackupstorage wake up triggers. Almost 400 to 500
I had this problem in my other phone too.
I have turned off sync , but still the problem persists.
Freezing the app also does not help
DaRkRhiNe said:
I get high calenderbackupstorage wake up triggers. Almost 400 to 500
I had this problem in my other phone too.
I have turned off sync , but still the problem persists.
Freezing the app also does not help
Click to expand...
Click to collapse
If you are having the same issues on 2 phones, then it must be one of the apps that you have on your phone. Use AppOps to see which apps are using calender and turn off them if not needed.
Funkym0nkey said:
I have found the solution for power management wakelocks on Kitkat. Many of you might be seeing that Wakelock detector shows phone is staying awake for 40-50% of the times since kitkat update.
Most of these wakelocks are thanks to Power manager service and pm8921_chg wakelocks. After removing the phone from charger these wakelocks causes phone to stay awake when it shouldnt.
I think I have found a solution.
When your battery is 100% switch off the phone. Remove the charger. Let it go to blank screen and then power it back on. Now when phone boots without charger connected to it, use it normall and you will see the wakelocks are no longer keeping phone on for 40-50% of the time. It is back to normal 10-11% or lower depending on use and phone gives great battery life.
I am yet to do lot of testing or reading on this, but this is just an observation. Worth giving it a try.
Click to expand...
Click to collapse
This works!! Thanks buddy, it reminds me of an issue I had back in the froyo days!! Good find
Sent from my Nexus 5 using XDA Premium 4 mobile app
kj2112 said:
...and she uses the "phone" way more...
Click to expand...
Click to collapse
What is this "phone" thing you speak of? Some kind of special app or some hidden feature built into the X? I'm not familiar with this concept.
I had my first Moto x run 4.2.2 and battery life sucked. upgraded to Kit Kit and everything was awesome like everyone mentioned.
My 2nd Moto X and it had great battery on both 4.2.2 and 4.4. I've had 3 and all had weird issues. I do think Moto X has some quality control issues. I've closely examined the phones and there were little inconsistencies between the 3. Going to a Tmobile store even confirmed they are using really old outdated SIM cards.
All 3 of mine had Loss of signal bug and MMS bug. no matter what I did.
Some people have no issues at all don't know what to make of it.

Is there a way to disable the cell radio?

Basically I am going to upgrade to the Droid Turbo the moment it is announced and start using my Razr M as a wifi only iPod device (now that OTG works to power my headphone amp).
Can I disable the cell radio somehow to save battery life? I'd like to keep wifi and bluetooth.
Thanks!
I just pulled the sim on my M. I didn't want to disable or delete anything, just in case I need the phone in an emergency.
Sent from my HTC6525LVW using Tapatalk
This is what I used on my droid 4 back in the day... Not sure if it works on KitKat tho
We cannot teach people anything; we can only help them discover it within themselves.
Coronado is dead said:
Basically I am going to upgrade to the Droid Turbo the moment it is announced and start using my Razr M as a wifi only iPod device (now that OTG works to power my headphone amp).
Can I disable the cell radio somehow to save battery life? I'd like to keep wifi and bluetooth.
Thanks!
Click to expand...
Click to collapse
This works
http://forum.xda-developers.com/showpost.php?p=55350515&postcount=2

Wakelock Detector

Anyone with a rooted Moto X Pure running Wakelock Detector yet? I managed to tweak my HTC M8 via Tasker and Xposed down to about 7-10% awake time and am just curious how much wake time the Moto Assist awareness modules cause. On the surface we're all concerned about the SoT of the 3000 mAh battery with the 1440p LCD, but what really gets under my skin is when an Android device drops 20-30% overnight or sitting on an office desk while not plugged in.
demi9od said:
Anyone with a rooted Moto X Pure running Wakelock Detector yet? I managed to tweak my HTC M8 via Tasker and Xposed down to about 7-10% awake time and am just curious how much wake time the Moto Assist awareness modules cause. On the surface we're all concerned about the SoT of the 3000 mAh battery with the 1440p LCD, but what really gets under my skin is when an Android device drops 20-30% overnight or sitting on an office desk while not plugged in.
Click to expand...
Click to collapse
I've also got an M8, and it also drops 15% or more overnight. I'd be interested to hear some details about the Pure also.
demi9od said:
Anyone with a rooted Moto X Pure running Wakelock Detector yet? I managed to tweak my HTC M8 via Tasker and Xposed down to about 7-10% awake time and am just curious how much wake time the Moto Assist awareness modules cause. On the surface we're all concerned about the SoT of the 3000 mAh battery with the 1440p LCD, but what really gets under my skin is when an Android device drops 20-30% overnight or sitting on an office desk while not plugged in.
Click to expand...
Click to collapse
jonathanbailie said:
I've also got an M8, and it also drops 15% or more overnight. I'd be interested to hear some details about the Pure also.
Click to expand...
Click to collapse
No one with the moto X has reported they have officially rooted. Also since this is a question shouldn't it be posted in the Q and A section?
jonathanbailie said:
I've also got an M8, and it also drops 15% or more overnight. I'd be interested to hear some details about the Pure also.
Click to expand...
Click to collapse
To clarify, this is just a pet peeve of mine, not my current situation. On screen off, Tasker a) disables location services b) sets location mode to off c) sets wifi scanning to disabled. Idle drain is very low when the phone is unable to acquire it's own position constantly, maybe 3-4% overnight.
As far as root is concerned, shouldn't it be as simple as unlocking the bootloader, replacing it with TWRP, and installing the SuperSU zip via TWRP? Or is a new SuperSU needed for a new phone model?
demi9od said:
To clarify, this is just a pet peeve of mine, not my current situation. On screen off, Tasker a) disables location services b) sets location mode to off c) sets wifi scanning to disabled. Idle drain is very low when the phone is unable to acquire it's own position constantly, maybe 3-4% overnight.
As far as root is concerned, shouldn't it be as simple as unlocking the bootloader, replacing it with TWRP, and installing the SuperSU zip via TWRP? Or is a new SuperSU needed for a new phone model?
Click to expand...
Click to collapse
Yeah it is that simple, however someone who knows how to migrate TWRP will need to receive their phone and start building the TWRP using the system structure for our device.
joshuadjohnson22 said:
Yeah it is that simple, however someone who knows how to migrate TWRP will need to receive their phone and start building the TWRP using the system structure for our device.
Click to expand...
Click to collapse
Ah so it is not a new SuperSU that is needed but a new TWRP, thanks!
demi9od said:
Ah so it is not a new SuperSU that is needed but a new TWRP, thanks!
Click to expand...
Click to collapse
It's the easiest way. With our bootloader being unlocked, there is no work around to install a custom recovery just a few adb commands to flash it. So once a custom recovery is built for us rooting is as simple as flashing SuperSU in recovery...that's it!!
Actually asked about how to turn this off. Hopefully a custom ROM becomes available to disable these features and make it truly just pure android.
Sent from my Nexus 7 (2013) using XDA Free mobile app
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
Also does anyone who has this, did yours get really hot for the first few hours. I'm afraid to unlock bootloader until I know I don't need to exchange it.
Sent from my Nexus 7 (2013) using XDA Free mobile app
I've honestly never bought a brand new smart phone. I've always waited for root to be confirmed first, so I wasn't aware TWRP needed to be built per device.
Half the fun of owning one in my opinion is tweaking it with root and xposed.
Ironically the phone that makes it the easiest to access root may need the least tweaking to optimize it's performance.
demi9od said:
I've honestly never bought a brand new smart phone. I've always waited for root to be confirmed first, so I wasn't aware TWRP needed to be built per device.
Half the fun of owning one in my opinion is tweaking it with root and xposed.
Ironically the phone that makes it the easiest to access root may need the least tweaking to optimize it's performance.
Click to expand...
Click to collapse
Porting TWRP is quite easy. Someone will port a phone with 808 or Nexus 6 TWRP with ease within a week.
Sent from my XT1575 using XDA Free mobile app

Categories

Resources