Hi guys, I was using AHRD 33.1 and everything was working perfectly till once morning all my apps forced closed one by one and the phone started rebooting and got into a bootloop. Whenever I used to charge it, it used to switch itself on automatically and reboot constantly from the 'HTC quietly brilliant' screen.
I erased cache too. In the recovery I sometimes got the message that the cache can't be mounted. Then I completely erased my sd card, reverted to android 4.1, updated the hboot ( from 1.36 to 1.73) and installed AOSPA kitkat. Still the apps force close and the phone restarts. I'm confused as to if the cache is at fault or the sd card isn't working properly. Help if you get what I have put forth.
napster_nagrath said:
Hi guys, I was using AHRD 33.1 and everything was working perfectly till once morning all my apps forced closed one by one and the phone started rebooting and got into a bootloop. Whenever I used to charge it, it used to switch itself on automatically and reboot constantly from the 'HTC quietly brilliant' screen.
I erased cache too. In the recovery I sometimes got the message that the cache can't be mounted. Then I completely erased my sd card, reverted to android 4.1, updated the hboot ( from 1.36 to 1.73) and installed AOSPA kitkat. Still the apps force close and the phone restarts. I'm confused as to if the cache is at fault or the sd card isn't working properly. Help if you get what I have put forth.
Click to expand...
Click to collapse
Make a full wipe, flash some rom, flash custom kernel (via recovery and via fastboot). Don't restore apps, and see how's that going.
nikola016 said:
Make a full wipe, flash some rom, flash custom kernel (via recovery and via fastboot). Don't restore apps, and see how's that going.
Click to expand...
Click to collapse
already done that, no luck.
I installed AOSPA again, with FAUX kernel. At first I didn't flash gapps just to check what was causing the problem. The phone was working fine. As soon as I installed gapps, one more reboot and now the phone is stuck on the HTC logo screen.
Edit: Okay so I went into fastboot and erased the cache. It switched on but now the apps crash.
Now it says 'Type password to decrypt storage' . What is happening? I got this same message in twrp yesterday.
napster_nagrath said:
Now it says 'Type password to decrypt storage' . What is happening? I got this same message in twrp yesterday.
Click to expand...
Click to collapse
Seems like you are flashing wrong gapps, make a full wipe again, try with this rom : http://forum.xda-developers.com/showthread.php?t=2583037
and this gapps:
http://wiki.cyanogenmod.org/w/Google_Apps
You need cm11 version gapps.
After flashing these everything should work fine.
nikola016 said:
Seems like you are flashing wrong gapps, make a full wipe again, try with this rom : http://forum.xda-developers.com/showthread.php?t=2583037
and this gapps:
http://wiki.cyanogenmod.org/w/Google_Apps
You need cm11 version gapps.
After flashing these everything should work fine.
Click to expand...
Click to collapse
I'll report back, but then why did I get the same error and force closes in ARHD?
Working for now, thanks man. But I'll get back to you in a while again.
Everything was working fine till yesterday night. Then as soon as I opened whatsapp, I got and error saying there is no space left on the device.! All the aspps force closed and now I'm back to square one! The SD card is at fault right?
napster_nagrath said:
Everything was working fine till yesterday night. Then as soon as I opened whatsapp, I got and error saying there is no space left on the device.! All the aspps force closed and now I'm back to square one! The SD card is at fault right?
Click to expand...
Click to collapse
Well....you really have strange issues...
Try with connecting your device to computer and than copy everything from storage to HDD, format storage and than copy everything to your phone....And yeah, why don't you try sense rom just for day-2-3, see if you have issue on sense too, if you have it's or your device or your fault.
nikola016 said:
Well....you really have strange issues...
Try with connecting your device to computer and than copy everything from storage to HDD, format storage and than copy everything to your phone....And yeah, why don't you try sense rom just for day-2-3, see if you have issue on sense too, if you have it's or your device or your fault.
Click to expand...
Click to collapse
I have issues on sense too. And now I can't reinstall my adb drivers because as soon as I switch off my phone and connect it to the computer, it either boots into recovery or reboots. Yeah it might be something which I did but I was using the same rom for more than a month without any issues. Anyway thanks!
Related
I hab ic 12.0.1 running perfectly on my phone. I flashed 12.1.0 over it without a wipe and it worked perfectly. I then thougt why not full wipe it with the 12.1.0 and have fresh start? Thats when the problems began. Twitter Facebook and a bunch of other apps kept fc. Then i thought i install another rom. the maximus 8. WIth that Rom i couldn't even complete the process where you set up your phone because everything kept restarting. even the gapps. i reloccked and locked my bootloader, i flashed everything with a tool, i even tried the firmware update tool again ( i'm on Hboot 1.31) , i flashed the boot.img manually. and i cant get any rom working. i don't know what to do?
daria55 said:
I hab ic 12.0.1 running perfectly on my phone. I flashed 12.1.0 over it without a wipe and it worked perfectly. I then thougt why not full wipe it with the 12.1.0 and have fresh start? Thats when the problems began. Twitter Facebook and a bunch of other apps kept fc. Then i thought i install another rom. the maximus 8. WIth that Rom i couldn't even complete the process where you set up your phone because everything kept restarting. even the gapps. i reloccked and locked my bootloader, i flashed everything with a tool, i even tried the firmware update tool again ( i'm on Hboot 1.31) , i flashed the boot.img manually. and i cant get any rom working. i don't know what to do?
Click to expand...
Click to collapse
did you flash their boot.img??
matt95 said:
did you flash their boot.img??
Click to expand...
Click to collapse
of course. with various methods. it seems that the prgramms can't write, or mount on one particular. but i'm really out of ideas. i don't know how to fix this. the only thing i would do next is a ruu. but because of the hboot 1.31 there is no ruu available.
the weirdest thing happend. it seems to be working again. i switsched back to cwtr. wiped everything. and did a clean install with a full wipe with ic 12.2.2 so far no issues. weird thing. because thats the same thing i did the last 2 days.
daria55 said:
the weirdest thing happend. it seems to be working again. i switsched back to cwtr. wiped everything. and did a clean install with a full wipe with ic 12.2.2 so far no issues. weird thing. because thats the same thing i did the last 2 days.
Click to expand...
Click to collapse
DAMNIT! after 3 min in the system it starts again with the force closes!
daria55 said:
DAMNIT! after 3 min in the system it starts again with the force closes!
Click to expand...
Click to collapse
are these ROMs meant to work with hboot 1.31? i know ARHD14.2 works.
try that rom. clean wipe and no other add.ons first
after more searching i came across this: http://forum.xda-developers.com/showpost.php?p=28401190&postcount=2
and this seemed to work. the contact data seems to be the rpoblem? im really lost. but it works for now.
damnit. the phone worked for 1h after that i'm now where i started where nothing works. :/ anyone got a suggestion?
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.
dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.
I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.
Hey guys Im running stock rooted and for some reason my phone SD is saying im full. I have literally nothing on it. Any ideas?
I tried once to install a ROM but it borked so I went back to a backup I had and it was fine.
Via windows it says my SD only has around 8 gigs used but android is saying 24?!?!?!?
WTF MATE?
Try wiping userdata in twrp.
Illogi.xbone said:
Try wiping userdata in twrp.
Click to expand...
Click to collapse
thanks, I was about to try and just redo the device with a ROM. Clear cahces and such.
I was actually wrong, every time I go into the phone in windows its giving me different storage use #'s. One time its 8 then 17 then 23 then 9. its weird. I think when I tried dirty flashing it just screwed it all up. I have nothing on the SD I care about really so maybe Ill just back up what I want (TWRP backup and titanium apps) and start from scratch if I Cant solve this.
That might be the best. Try backing up to an OTG then completely wiping and installing a fresh ROM. After backing up apps and such.
ugh IM having trouble using any roms on my 5x. No matter the way I install the phone always boots to "internal problem with device"
Ive tried installing different roms (I only like stock style ones) and the vendor.zip and it just doesnt work for me. Ive gone back to my backup for the moment until I figure this out. Never had these issues with my nexus 5
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
tevil said:
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
Click to expand...
Click to collapse
Try 1st: Completely wipe device, System, data etc. Including Internal Storage and flash a new rom. If that does not fix the issue try flashing stock firmware and start from scratch. Use THIS guide to flash the stock images.
Flash vendor.img that matches your rom base. MMB29Q is the February OTA base. February AOSP roms are based on MMB29U master code but MMB29Q vendor file works fine.
For password issues after TWRP restore, do this: http://forum.xda-developers.com/showthread.php?t=3245070
Sent from my Nexus 5X using Tapatalk
SERIOUS ISSUE!
Bricked the phone!
CRAP, this whole thing went downhill. Can get into TWRP, and get the android crash logo (triangle) was trying to restore back to stock to start fresh and it bombed completely!
Any tips!!!
Been a while since I used ADB or fast etc, but man if I have to relearn I will
I have followed the instructions from Max at galaxynote4root http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/5/. I got all the way through to the final step which is go into TWRP recovery, install the Oscar kernel and SuperSU zip files. I did not extract these files. Once I did that I got into a boot loop. I get by the Verizon logo to the UI and then it starts rebooting. Since there is not much discussion activity at Max's site, I thought if anyone here could help me.
After the UI comes up and before it goes in the boot loop, I get messages saying "Unfortunately xxxx has stopped." It varies about sometimes it is Knox. S Pen, Google Play, etc.
Try a factory reset by going into recovery and wiping delvik, cache, and data
MonstaSaleens said:
Try a factory reset by going into recovery and wiping delvik, cache, and data
Click to expand...
Click to collapse
That improved the situation. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says "unfortunately KNOX has stopped running." It was doing that before, too.
I have confirmed I have root and and unlocked bootloader.
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.
codydixon said:
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Click to expand...
Click to collapse
Just followed your instructions. Everything was fine until I installed the kernel and supersu. I hate to be stuck when I'm so close.
ssj4gogeta2003 said:
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.[/QUOTE
OK, tried that, and it worked--once. When I reboot with the SD card out, it either won't start or goes back into a boot loop.
Click to expand...
Click to collapse
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
MrNetwork said:
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
Click to expand...
Click to collapse
You'll need to connect the micro sd card itself to the computer and format it there. I have used Rufus (https://rufus.akeo.ie/) in the past to do this, but you may use any formatting program that you are familiar with. I recommend FAT32 as your format unless you move files over 4 GB to and from the card.
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
MrNetwork said:
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
Click to expand...
Click to collapse
It will depend on what version of firmware you are currently running. Most 6.0 ROMs require that you are using N910VVRU2CPD1 or N910VVRU2CPF3 for proper use. Please go into About Phone in Settings and check the Baseband Version field to make sure that you have one of those two in there. Flashing a 6.0 ROM with 5.1.1 firmware will cause issues with mobile signal and can make it impossible to use wifi.
If you find that you are running 5.1.1 firmware, then you have two choices: Flash a 5.1.1 ROM and call it a day or go through the process of unlocking the bootloader for 6.0.1 firmware. It's important to note that this will be a different process than the one you just went through. Be sure to research it thoroughly before attempting it. Hsbadr is a great developer and I believe he has a process for that, but it's been a while since I did it myself.
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
MrNetwork said:
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
Click to expand...
Click to collapse
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
ssj4gogeta2003 said:
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
Click to expand...
Click to collapse
Thank you. I finally figured it out. The problem was with oscar_kernel_v0.2. Instead I am using Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P. I'm going to stay with 5.1.1. The only trouble I am having now is with My Tracks not showing the map. I know it's been deprecated by Google, but it still is working on my LG G4. However, I'm not trying to hijack this thread. I'll start a new thread for this issue.
This is now the fastest phone I've used after deleting bloatware and running Nova Launcher.
Good to hear. Enjoy the phone.