Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Juanito216 said:
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Click to expand...
Click to collapse
i have a similar problem... i rooted my nexus and flashed a custom rom (PACman) when it boots wifi is disabled, also bluetooth doesnt work neither any sounds, no music, no speaker, nothing, so i flashed Paranoid android (both based on 4.3) and i had the same problem
so then i flashed stock, everything ok, then CrDroid (based en 4.4) everything ok, then OmniRom (Based on 4.4) everything ok too...
i posted it here and got no replies, hope someone could help
Yes, right now I'm running an unofficial CM 11, and no issues. I wonder if something needs to be downgraded, in order for things to be okay again. I would still like the option to be able to run 4.2/4.3 based roms. Maybe I could try flashing to stock 4.2 or 4.3, then reroot, and test my results
Sent from my Nexus 4 using Tapatalk
What radio/baseband version are you using?
Hi, I'm using AOKP last nightly builds and since 2013-10-18 Wi-Fi started to stuck, settings ui errors and other problems. So I just tried franko kernel with official AOKP releases and Wi-Fi now is working fine. But i've faced skype problems). After 4 minutes it hangs and i need to restart my phone.
Greetings,
I'm not salty enough to post in the Dev threads, so here I am.
I'm usinging the vs980 on the latest Mahdi release in combination with the dorimanx kernel, and ART. So far everything seems stable except for Bluetooth. Streaming media works just fine, but when I pair it with my vehicle, which has phone and media, it goes into a pairing crash loop.
I've searched the forums and haven't found anything related to my problem. Someone mentioned disabling the hardware buttons, but that's not an option I have under settings->buttons.
Any other suggestions? I thought about making a backup and then do a clean install on the stock kernel using dalvik but I don't know why that effect BT.
-Phillip
I currently have the last temasek cm11 build on my phone. GPS works fine. No problem at all. If I switch ROMs and restore my data, GPS still works fine.
However, the GPS will NOT work AT ALL on *any* other ROM I try. Whether it's AOSP cm11 or cm12. Whether it's a samsung build. Whether it's a stock samsung build. GPS will NOT lock. I run GPS Status apps and it just sits trying to get a lock, forever. Nothing.
Flash back my current ROM. BOOM. GPS Works fine.
IF I flash another AOSP build and DON'T wipe data/cache/etc.. GPS will still work fine. It only breaks when I do a clean install.
So, wtf? What could possibly be on my /data that is keeping my GPS working, and some how not even touchwiz ROMs also contain? It's an 900T, and currently on AOSP, so the codes I see floating around don't work. Granted, I could flash a touchwiz ROM and try them again, but right now GPS is working as long as I'm on one ROM, I'm afraid to use the code and completely break GPS. It just doesn't seem to be something at that deep of a level as flashing back to my current ROM always fixes it. Which tells me it's some simple config that I need.
Anyone know what the heck could be causing the problem? My cm11 build is sooo dirty from xposed and massive tweaking that bluetooth and other things lock up daily, so I really want to run another ROM or at least do a clean install, but I can't lose my GPS. It's used daily.
The game will play fine, but during certain card animations (turning pages in collection, playing battlecry cards, etc) the game will lock up. Sometimes the music can still be heard, but the game's graphics are frozen. I am able to trigger the notification drop down and swipe for the navbar when the game is frozen.
How do I go about diagnosing what is causing the problem? I know that this did not happen on 6.0.0 with stock or franken kernel. I've tried a number of different memory configs, governors, and gpu settings. Turning KSM and zRAM off/on, running/not running optimization scripts. The only thing I cannot do is try the stock kernel, as there has not been an official xt1575 stock rom released.
Phone: xt1575
ROM: Stock xt1572 Asia 6.0.1 March Sec Patch
Kernel: 0.12 Frankenkernel
Rooted/Not rooted: Systemless Root
App Crashing: Hearthstone
Are there any diagnostics I can run to capture a log of what happens? Then ask for some help deciphering the logs?
*aside* I could go back to stock 6.0.0, but then the bluetooth and my headset and car would be bugged again. I have stayed off of CM/AOSP because I like the moto gesture/display stuff and google camera doesn't capture panorama/photosphere correctly (had same issue on LG G2).
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.