[Q] What's up with this phone?! - One (M9) Q&A, Help & Troubleshooting

Hi guys. I recently purchased this phone from t mobile and so far it has been terrible. I cannot return it because I traveled to a different country and there is no T-Mobile here, so I am stuck.
Some issues I have are:
- extreme over heating while simply using the phone to browse the internet.
- battery draining extremely fast, lasting 4 hours Max (basic usage)
I am using the Android revolution rom on 5.1 lollipop and I thought it was supposed too fix these issues. Can someone please tell me how to fix these issues? I feel ripped off and wish I bought an s6 instead

I would say you have a faulty device... ?
Did you flash the new firmware aswell? Not just the rom?
Sent from my HTC One M9 using XDA Free mobile app

dannylow79 said:
I would say you have a faulty device...
Did you flash the new firmware aswell? Not just the rom?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
I wasn't aware that you had to install the firmware as well. where can I get it?

http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
latest firmware. Should help fix issues. If not, it's possible it is device related.
Do you use greenify or any other similar app to hibernate apps when the screen is off? Do you have a lot of apps that sync automatically throughout the day? Have you removed bloatware and other apps that run in the background that you dont use by using titanium backup or romtoolbox?
Simple things like resolving any issues with the above mentioned items can help prolong battery life by a fair bit. Kernel tweaks also help to reduce overheating / cpu usage if you dont require you're phone to run at top capacity.
with overheating you need to keep in mind this is an all metal casing on the phone ... this means it will naturally absorb a lot of heat which isnt always a bad thing as it takes some of the strain away from the phones core. Obviously if its so warm it's hot to the touch then thats definately not good. But doing a full wipe / reset / re-flash etc is worth doing to get you back to basics and then if the issue remains, and you have seen to the above tweaks like using greenify / uninstalling apps you dont need / changing apps sync frequency etc, then it is probably hardward related.

tomorio said:
http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
latest firmware. Should help fix issues. If not, it's possible it is device related.
Do you use greenify or any other similar app to hibernate apps when the screen is off? Do you have a lot of apps that sync automatically throughout the day? Have you removed bloatware and other apps that run in the background that you dont use by using titanium backup or romtoolbox?
Simple things like resolving any issues with the above mentioned items can help prolong battery life by a fair bit. Kernel tweaks also help to reduce overheating / cpu usage if you dont require you're phone to run at top capacity.
with overheating you need to keep in mind this is an all metal casing on the phone ... this means it will naturally absorb a lot of heat which isnt always a bad thing as it takes some of the strain away from the phones core. Obviously if its so warm it's hot to the touch then thats definately not good. But doing a full wipe / reset / re-flash etc is worth doing to get you back to basics and then if the issue remains, and you have seen to the above tweaks like using greenify / uninstalling apps you dont need / changing apps sync frequency etc, then it is probably hardward related.
Click to expand...
Click to collapse
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.

OfficialBlox said:
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.
Click to expand...
Click to collapse
as far as i know its a one kernel at a time kinda show.
I have only ever used the kernel that comes with the rom so far so cant recommend any others im afraid.
If after installing a different kernel you have the same issue and you have a set up like you've mentioned, it does sound like a hardware problem. With your setup it should very rarely get that hot unless you do a lot of flashing in a short space of time. My phone only ever gets hot to a point that i notice when i flash and set up a new rom, but it soon returns to normal.
good luck.

tomorio said:
as far as i know its a one kernel at a time kinda show.
I have only ever used the kernel that comes with the rom so far so cant recommend any others im afraid.
If after installing a different kernel you have the same issue and you have a set up like you've mentioned, it does sound like a hardware problem. With your setup it should very rarely get that hot unless you do a lot of flashing in a short space of time. My phone only ever gets hot to a point that i notice when i flash and set up a new rom, but it soon returns to normal.
good luck.
Click to expand...
Click to collapse
After installing the elitekernal my phone is stuck on the HTC logo.. it gets to the "optimizing apps" screen then restarts, and does it again.. bummer.

OfficialBlox said:
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.
Click to expand...
Click to collapse
While you were still on stock, did you update the phone through Software Updates? You're likely on the originally released version of the firmware, which is probably 90% of your problems. Mismatched firmware/ROM isn't helping either.
Either return the device to stock to be able to take the OTA update, or S-Off ($25 through sunshine) and flash the latest developer edition firmware (2.8.617.4).
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
OfficialBlox said:
After installing the elitekernal my phone is stuck on the HTC logo.. it gets to the "optimizing apps" screen then restarts, and does it again.. bummer.
Click to expand...
Click to collapse
Bro. you really got to do some reading before you just start flashing stuff. Elite is NOT compatible with 5.1 roms.
if you are on 5.1, you HAVE to use the stock kernel . There are NO custom kernels for 5.1 yet.
Restore the boot.img from the ARHD rom. Either by restoring from the backup you made before you flashed the elite kernel, by dirty flashing ARHD, or by extracting boot.img from the ARHD zip and flashing it with fastboot.

jollywhitefoot said:
While you were still on stock, did you update the phone through Software Updates? You're likely on the originally released version of the firmware, which is probably 90% of your problems. Mismatched firmware/ROM isn't helping either.
Either return the device to stock to be able to take the OTA update, or S-Off ($25 through sunshine) and flash the latest developer edition firmware (2.8.617.4).
Click to expand...
Click to collapse
I did not update the phones firmware. I was doing this whole thing in the first place because I thought updating to 5.1 android would update my firmware lol.
Right now I am trying to adb sideload the android revolution ROM but the phone says "Starting adb sideload feature" and gets stuck there. I have the correct drivers. Fastboot works fine, but I can only flash stock roms with fastboot. Do you have any link for the stock T-Mobile rom?

OfficialBlox said:
I did not update the phones firmware. I was doing this whole thing in the first place because I thought updating to 5.1 android would update my firmware lol.
Right now I am trying to adb sideload the android revolution ROM but the phone says "Starting adb sideload feature" and gets stuck there. I have the correct drivers. Fastboot works fine, but I can only flash stock roms with fastboot. Do you have any link for the stock T-Mobile rom?
Click to expand...
Click to collapse
This will wipe your internal storage, so back it up first, but it's going to be the easiest way to get out of the mess you've gotten yourself in.
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
FYI-You need to have HTC Sync Manager installed on your computer for the RUU to run (or at least you USED to). If you get error 155 it's likely because it's not installed.

I fixed it by putting android revolution rom on my sd card then flashing it via twrp.
Now I have a simple question:
Does Lolipop 5.1 include all those fixes that HTC introduced? Or do I need to wait for the firmware for that? I am talking about the fixes like camera, overheating, battery, etc.

OfficialBlox said:
I fixed it by putting android revolution rom on my sd card then flashing it via twrp.
Now I have a simple question:
Does Lolipop 5.1 include all those fixes that HTC introduced? Or do I need to wait for the firmware for that? I am talking about the fixes like camera, overheating, battery, etc.
Click to expand...
Click to collapse
Firmware fixes those issues, not the rom...or at least you need the firmware for any of the fixes to actually work And using the latest ARHD with 1.32 firmware is likely making some of your issues worse.
There should be one firmware update for T-Mobile right now. But like I said, you'll have to return to stock system image to get the update. Either that or S-Off your phone which will make it possible to update to the 2.8 developer edition firmware which ARHD would run awesome on. The only downside to s-off and using developers firmware is if you use t-mobile wifi calling. For that to work, I think you need official t-mobile firmware.

jollywhitefoot said:
if you are on 5.1, you HAVE to use the stock rom . There are NO custom roms for 5.1 yet.
Click to expand...
Click to collapse
Not to confuse the OP, but @jollywhitefoot what do you mean there are no custom roms for 5.1? Did you mean kernal? Another question, Is the new T-mobile update out already? I heard it comes out on the 17th.

bigp951 said:
Not to confuse the OP, but @jollywhitefoot what do you mean there are no custom roms for 5.1? Did you mean kernal? Another question, Is the new T-mobile update out already? I heard it comes out on the 17th.
Click to expand...
Click to collapse
Sorry. Thanks for bringing that to my attention. I meant to write kernel instead of rom. There are no custom KERNELS for 5.1 roms yet.
I've fixed my original post to avoid future confusion...but hopefully we'll see a custom kernel for this device in a couple of weeks.
You probably know more about T-Mobile update schedule than I do. I'm on AT&T and they're the worst about pushing updates, so I don't even bother keeping up with them.

We probably won't have any custom kernels for a few more weeks. Nothing can happen until HTC releases source, which has been coming a couple of weeks to a month after the OTAs.

Related

[Q] Concerns about Rooting

So I would like to get back into rooting, but I have some concerns from the last time I rooted a phone (HTC EVO 4G), that maybe you guys could help quell. :silly:
So the last time I rooted, everything went successfully and I made proper backups but unless I was using stock clockwork recovery mod I had some serious carrier issues, the biggest of which was I had absolute zero stock voicemail functionality only after a day of setting up a Google voice account I managed to get some Voicemail functionality in Cyanogenmod. The whole experience was unbelievably frustrating since the phone would also miss calls and not tell me (missed calls would show up out of the blue an hour or two after my friends had initially called). However I did have all the benefits of rooting. Maybe someone has an answer to what I ****ed up when I did this because other EVO users that were running cyanogen were clueless to what my problem was or what caused it.
Second I heard there's some strange IMEI bug that happens on galaxy s3s when rooting that I don't quite understand. I'm trying to get myself a list of successive steps to safely root my GS3. I noticed there's a lot of root guides but I'm wondering which is considered to be the most up to date and safest. found QB root guide if that's the most optimal.
Third, will rooting still let me wifi tether for free? This was a hugely important feature to me since my internet situation is more sketchy more often than not.
Fourth, I don't understand why CM10 is considered to be such a badass mod, is it performance optimization? Some killer feature that's going over my head? I assume it's a 4.1.2 version for S3 owners (one of the main reasons I'd like to root is so I can take advantage of the new multi-window feature).
Fifth, Can I still install OTA updates? Props to MikeWjF for the concise answer.
Is there any key things I'm missing out on, your advice is much appreciated guys!
Yeah I had weird quirky problems like that on my OG EVO as well on AOSP ROMs. I ended up sticking with Sense based ROMs and pretty much stayed problem free. AS far as this phone goes, i've only flashed Touch Wiz based ROMs so far and haven't ran into any problems.
MikeWjF said:
Yeah I had weird quirky problems like that on my OG EVO as well on AOSP ROMs. I ended up sticking with Sense based ROMs and pretty much stayed problem free. AS far as this phone goes, i've only flashed Touch Wiz based ROMs so far and haven't ran into any problems.
Click to expand...
Click to collapse
Alright stick to my original UI thanks for the advice!
As far as OTA updates go, no, not unless the ROM itself has an OTA updater in it that updates said ROM. When rooted you should never accept a factory OTA update. I don't think it's even possible on AOSP anyway.
MikeWjF said:
As far as OTA updates go, no, not unless the ROM itself has an OTA updater in it that updates said ROM. When rooted you should never accept a factory OTA update. I don't think it's even possible on AOSP anyway.
Click to expand...
Click to collapse
Thanks for the answer. Can you tell me why CM10 is all the rage? It is 4.1.2 right?
Semitoned said:
Thanks for the answer. Can you tell me why CM10 is all the rage? It is 4.1.2 right?
Click to expand...
Click to collapse
Couldn't tell you, I haven't tried it yet. I'm still weary of wasting my time falling in love with an AOSP ROM, only to have problems with it on the go.
MikeWjF said:
Couldn't tell you, I haven't tried it yet. I'm still weary of wasting my time falling in love with an AOSP ROM, only to have problems with it on the go.
Click to expand...
Click to collapse
Been trying root with Odin keep getting stuck on Get PIT for mapping, have tried swapping usb ports and reinstalling driver with no avail.
Semitoned said:
Been trying root with Odin keep getting stuck on Get PIT for mapping, have tried swapping usb ports and reinstalling driver with no avail.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1743780
Using odin 3.04
I followed this and hadn't an issue with Odin hanging at all. Took maybe 2 min max to get everything done.

1.40.401.8 overheating

Hello guys,
Since I updated to 1.40.401.8, I flashed viper latest rom. The phone heats up on minimal usage, and oh the battery....ultra drain. I can barrly make it to the middle of the day.
Anyone having the same problem after the update?
I tried to flash it again, factory reset but no use. Any ideas to fix this or should I flash the old firmware?
mr.dj26 said:
Hello guys,
Since I updated to 1.40.401.8, I flashed viper latest rom. The phone heats up on minimal usage, and oh the battery....ultra drain. I can barrly make it to the middle of the day.
Anyone having the same problem after the update?
I tried to flash it again, factory reset but no use. Any ideas to fix this or should I flash the old firmware?
Click to expand...
Click to collapse
Check over the apps you're restoring mate, keep the install clean, let it settle, set your CPU up right, install something to keep apps from starting up (auto starts) then see how the battery is, my guess is it'll be a lot better.
From that point just install the apps you need, followed by the ones you want.
Did you change up your firmware too? Obviously that should have been done but I thought I'd ask..
Hope this helps, seems obvious but its easily overlooked.
dladz said:
Check over the apps you're restoring mate, keep the install clean, let it settle, set your CPU up right, install something to keep apps from starting up (auto starts) then see how the battery is, my guess is it'll be a lot better.
From that point just install the apps you need, followed by the ones you want.
Did you change up your firmware too? Obviously that should have been done but I thought I'd ask..
Hope this helps, seems obvious but its easily overlooked.
Click to expand...
Click to collapse
what do you mean by change up the firmware? if the firmware and the rom didnt match it will fall into a bootloop . I flashed the latest firmware and a new rom with the new base. I didn't install any different apps I only use several app which are whats app, appy geek, 9gag,tasker and twitter that's almost all the app and I ran more apps in the older firmware.
I have 30% now from only 6 hours and 30 min. there is a huge difference. I will try ARHD since its almost stock but I really love viper rom its full of customization
.
Anyway, thanks a lot m8, ill flash and new rom and ill update you guys.
mr.dj26 said:
what do you mean by change up the firmware? if the firmware and the rom didnt match it will fall into a bootloop . I flashed the latest firmware and a new rom with the new base. I didn't install any different apps I only use several app which are whats app, appy geek, 9gag,tasker and twitter that's almost all the app and I ran more apps in the older firmware.
I have 30% now from only 6 hours and 30 min. there is a huge difference. I will try ARHD since its almost stock but I really love viper rom its full of customization
.
Anyway, thanks a lot m8, ill flash and new rom and ill update you guys.
Click to expand...
Click to collapse
I was under the impression that you could, some people had boot loops others didn't.
Leave all apps off, full wipe, then test.
If none of this works then I would try your luck in Viper thread.
dladz said:
I was under the impression that you could, some people had boot loops others didn't.
Leave all apps off, full wipe, then test.
If none of this works then I would try your luck in Viper thread.
Click to expand...
Click to collapse
Hey,
Its looks like an issue with viper rom, ARHD is way better, less heat and more battery for sure although I miss the customizations on the viper rom:crying:.
One thing I noticed, after flashing both roms I got the "android optimizing apps" for ARHD is was about 160 I think, while viper rom had like 240 -.-" There are a lot of things under that rom and i'm assuming they're causing the heat and battery drain.
ps. I always full wipe before flashing any rom
thanks
mr.dj26 said:
Hey,
Its looks like an issue with viper rom, ARHD is way better, less heat and more battery for sure although I miss the customizations on the viper rom:crying:.
One thing I noticed, after flashing both roms I got the "android optimizing apps" for ARHD is was about 160 I think, while viper rom had like 240 -.-" There are a lot of things under that rom and i'm assuming they're causing the heat and battery drain.
ps. I always full wipe before flashing any rom
thanks
Click to expand...
Click to collapse
Just pick the ones you need mate, I know about viper, it is a little heavy but that's just to ensure that people get what they need.
As for a different base with a different firmware its definitely possible as I'm running the 1.40 ROM with the 1.32 firmware, no overheating and no problems.
Glad your back up and running. Try leedroid too, that's the ROM I'm currently running.

Need S4 Rom advice!

Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.

How is your Nexus 5x experience with custom ROM/kernel vs. full Stock?

Wasn't sure if this would fit better under Q&A, but wanted to get the opinions of my fellow Nexus 5x users who spent some time with stock, unrooted, locked bootloader and then switched to the custom scene and learn just how much better (or worse) the experience was.
I haven't been in the mod game as much since my Galaxy Nexus and Motorola Droid days, when one click root/unlock, custom recovery, flash ROM and flash kernel all took just a few minutes. The guides for the 5x seem a bit more intimidating, especially when it comes to having all the right ingredients to keep Android Pay working. People seem to be saying some really great things about the Cataclysm+ElementalX combo, as well as other ROMs and kernels.
Anyway, before I dive in to the land of full data wipes and avoiding bootloops, I wanted to ask Nexus 5x nation - how's your custom experience, and was it worth it?
I'm using Cataclysm+ElementalX and this
Awesome battery life and screen on time and still very smooth.
Lossyx said:
I'm using Cataclysm+ElementalX and this
Awesome battery life and screen on time and still very smooth.
Click to expand...
Click to collapse
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?
Moonboots said:
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?
Click to expand...
Click to collapse
Fairly easy yes, I followed Heisenbergs guide , but if you want a more automated way you could try Wugfresh Toolkit, The systemless root is basically has the sam install process (flashable zip) and ElementalX doesn't conflict with system partition so Android pay should work. And, I don't use Android Pay as my country doesn't have (or maybe) Google Play yet. Didn't stumble to any issues at all.
Moonboots said:
That's the route I would be looking to take, I think. Response has been great for the interactive governor mods. Was the whole process (unlock, systemless root, ROM/kernel install) pretty easy, or did you run into a lot of issues? Also, Android Pay still working?
Click to expand...
Click to collapse
Unlock, Systemless root, ROM/Kernel is extremely easy. That's why I love Nexus Devices. You'll be able to do it in your sleep after the first couple of times. No issues should arise as long as you do everything in the correct order. Android Pay still works with Systemless Root, again, as long as you follow directions.
I'm running Ubermallow and Phasma Kernel, and after trying many different kernels and a few different ROMs, this is definitely my favorite combination. Fast, extremely optimized, just the right amount of customization and Phasma is one of the most feature-rich kernels out there for this phone. Feel free to experiment, though. Everyone has different tastes and usage patterns. So what works for me, may not necessarily be for you. Luckily flashing new ROMs and kernels takes 5 like minutes so you can give them all a shot!
I can safely say that you'll never want to go back to stock after finding the combination that works for you
Thanks for the thoughts and encouragement, all! I do recall the flashing addiction from the old Moto Droid days with Bugless Beast, AOKP and CyanogenMod. Good to know there are some great options here.
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.
Roms and updates
Moonboots said:
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.
Click to expand...
Click to collapse
This was my first phone that I modified, mainly because I use Linux, and my old phones seems to need Windows to do anything. I followed this guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930. It worked perfectly, and when I needed to apply the update, I followed step 10 of that guide; worked perfectly, with no loss of data or settings at all.
Then, I flashed Cataclysm over that update, without erasing anything other than cache, and when I finished and rebooted, I thought it didn't work until I checked settings and found the rom's single entry for settings. Nothing else changed.
Moonboots said:
Thanks for the thoughts and encouragement, all! I do recall the flashing addiction from the old Moto Droid days with Bugless Beast, AOKP and CyanogenMod. Good to know there are some great options here.
Another question I had regarding upgrading to new versions. When 6.0.2 drops, or one of the monthly security updates, etc., it used to just be a dirty flash over the current ROM, clear dalvik/cache, and reboot system. Am I correct in saying it's more involved this time around? The guides seem to point to a lot more steps for your basic ROM upgrades.
Click to expand...
Click to collapse
Rom upgrades are easy.
Download the factory image and extract boot.img, system.img, and vendor.img.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Tomyk89 said:
Rom upgrades are easy.
Download the factory image and extract boot.img, system.img, and vendor.img.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Click to expand...
Click to collapse
I assume fastboot flash radio radio.img if a new radio is included with the update, as well?
After reading through all the awesome resources and recommendations provided by you guys, I think I will unlock, root, install TWRP, decrypt, flash Elemental X, and toy with the interactive governor settings thread that's in the general forum.
That way I can keep Android Pay with systemless root and continue to stay up to date on the latest factory images using Tomyk's note above, is that correct?
Moonboots said:
I assume fastboot flash radio radio.img if a new radio is included with the update, as well?
After reading through all the awesome resources and recommendations provided by you guys, I think I will unlock, root, install TWRP, decrypt, flash Elemental X, and toy with the interactive governor settings thread that's in the general forum.
That way I can keep Android Pay with systemless root and continue to stay up to date on the latest factory images using Tomyk's note above, is that correct?
Click to expand...
Click to collapse
You are correct on the radio.img comment
I personally didn't go the systemless route but I think you're on the right track. I know that a lot of people in other forums have successfully kept Android Pay capabilities after everything so you may want to do a bit more digging. If i find the answer I'll post it for you.
Just as a counter point, stock is working well for me and I feel no need to root at this time. Performance and battery life are already top notch. :good:
N5x, EX kernel, unencrypted, systemless root:
much better performance (both due to EKm and no encryption, and to a lesser extent adaway), worse battery life due to issues with nlpcollectorwakelock from Google play services, which may or may not be related to the rom (Didn't have issues with googleplayservices on stock)
just flashed xposed in an effort to curb these wakelocks by means of Amplify.
2x4 said:
N5x, EX kernel, unencrypted, systemless root:
much better performance (both due to EKm and no encryption, and to a lesser extent adaway), worse battery life due to issues with nlpcollectorwakelock from Google play services, which may or may not be related to the rom (Didn't have issues with googleplayservices on stock)
just flashed xposed in an effort to curb these wakelocks by means of Amplify.
Click to expand...
Click to collapse
I've been having problems with Google Play Services battery drain. Since I still haven't taken the leap to unlock and root, I have no way of pinning the wake locks to nlpcollector but that could be my culprit too.
See attached pictures - This happens once every few weeks overnight, and I usually clear apps from memory before going to bed. So much for doze.
Moonboots said:
I've been having problems with Google Play Services battery drain. Since I still haven't taken the leap to unlock and root, I have no way of pinning the wake locks to nlpcollector but that could be my culprit too.
See attached pictures - This happens once every few weeks overnight, and I usually clear apps from memory before going to bed. So much for doze.
Click to expand...
Click to collapse
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.
2x4 said:
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.
Click to expand...
Click to collapse
Play Services goes through weird phases where it just destroys your battery, and without something like amplify to curb the frequent wakelocks, there's no way around it for the average user. It's a shame.
2x4 said:
it gives me some relief to see that, since that means it's not related to my custom rom, but instead your run of the mill google play services issues..... so hopefully an update to GPS will fix that soon.
Click to expand...
Click to collapse
FYI - it may have been a recent Snapchat update that made that app even worse than normal. Uninstalled it and smoothness and long battery have returned.
Moonboots said:
FYI - it may have been a recent Snapchat update that made that app even worse than normal. Uninstalled it and smoothness and long battery have returned.
Click to expand...
Click to collapse
Thanks for the heads up, I don't have snap chat installed though

Best ROM for S4 Mini?

Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.

Categories

Resources