hi!!
I have a HTC M8 dual sim, with a custom 7.1.2 ROM; I have not upgrade or install any other radio file than the stock.
It happens that when I get far away from my city, i lost all my signal. and in general it doesn't come back until I reboot the device (a soft restart works). and then I get signal again, but only for several minutes; then it all repeats.
from time to time it gets signal and stays like that, so I suspect that my device is not been able to get signal for the other operators of my country (here the cells are shared between the operators.. and I suppose that it works that way worldwide).
this is pretty annoying because I love to travel, and virtually do it without phone capability.
could it be that I have upgraded my phone that far from stock that the radio firmware got obsolete? or it may be a hardware problem?
tthanks ^^
xxopiumxx said:
could it be that I have upgraded my phone that far from stock that the radio firmware got obsolete? or it may be a hardware problem?
Click to expand...
Click to collapse
I don't know what you mean that the radio "got obsolete". Receptions issues may be possible with a custom ROM (which ROM?). But it's impossible to say whether the ROM is the issue or not, unless you go back to the stock ROM, and see if the problem persists.
redpoint73 said:
I don't know what you mean that the radio "got obsolete". Receptions issues may be possible with a custom ROM (which ROM?). But it's impossible to say whether the ROM is the issue or not, unless you go back to the stock ROM, and see if the problem persists.
Click to expand...
Click to collapse
I meant that the part of the hardware firmware that manage the modem, may be too outdated respect of the rom . i am just taking a guest.
until yesterday i was runing Lineage OS 14.1; but it had a horrible issue that after a call it kept in "hanging" until I restarted. so, i went back to CM13.
xxopiumxx said:
I meant that the part of the hardware firmware that manage the modem, may be too outdated respect of the rom . i am just taking a guest.
Click to expand...
Click to collapse
The firmware is stuck on Marshmallow, since HTC doesn't support this phone with updates anymore. All the ROMs will work with Marshmallow firmware, since there is no other firmware for it to work with for this device.
redpoint73 said:
The firmware is stuck on Marshmallow, since HTC doesn't support this phone with updates anymore. All the ROMs will work with Marshmallow firmware, since there is no other firmware for it to work with for this device.
Click to expand...
Click to collapse
good. so i wanted to know if this that you tell me could cause something like the mentioned issue; or if i should be looking into hardware ones.
xxopiumxx said:
good. so i wanted to know if this that you tell me could cause something like the mentioned issue; or if i should be looking into hardware ones.
Click to expand...
Click to collapse
Back to stock is probably your best bet, and see if the problem persists. Really not much else you can do, especially since I think Lineage or CM are the only custom ROMs for the dual sim?
If you do back to stock, and still have problem, it may be a hardware issue. Might be a network issue, as well.
Related
So, I rooted my S4 Mini LTE. then I flashed it with KK version of Carbon Rom (not intended). I have then reflashed it to Carbon rom JB version. Everything seems to be working except the data connection. It works sometimes, but more often not. I have reflashed it to Pacman, available here, internet connectivity is still the same...
The fact that it sometimes works excludes a lot of things. APN is fine, I checked it and it wouldn't work at all otherwise. Could it be that I messed something up when I flashed it with KK rom?
What could I do to fix it?
I'll try unrooting it and returning to stock to see if it will fix it, but I have my doubts....
Do you have any suggestions? All I want is my data connections working reliably again, device rooted or not...
EDIT:
I have reverted my phone to stock. It's the same as it was when I got it, except for thw KNOX and warranty part. Since my warranty is void anyway, it's really a shame to use stock rom with all the crapware on it.
Do you have any ideas that would cause mobile data to work on stock, but not on any other rom?
Karlovsky120 said:
.
Do you have any ideas that would cause mobile data to work on stock, but not on any other rom?
Click to expand...
Click to collapse
Maybe your KK ROM was made from ROM with modem that was intended for other country. Often modems, intended for one country/region, work badly or don`t work in other countries due to differences in service providers' settings.
djtyta said:
Maybe your KK ROM was made from ROM with modem that was intended for other country. Often modems, intended for one country/region, work badly or don`t work in other countries due to differences in service providers' settings.
Click to expand...
Click to collapse
How can I check that? Is there anything I can do to fix it?
For some reason, every time I try to install a sense based rom, it never boots.
I'm fairly new to flashing, and have flashed 4 or 5 aosp roms. Every time I install one of those, it always works correctly, no issues.
I have tried to flash several Sense based roms, such as ARHD 20.1, Insert Coin, and nv, and each time, it never works. I always do a factory wipe beforehand as well as a wipe in the aroma installer. It will go thru the process and install, and then prompt me to reboot, which it does. Once the screen comes back onm however, it just hangs on the white htc screen with the red development text. When i get back to the hboot, itll show nothing for os.
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom. Also, I just tried the NV rom which is based off my firmware, and it still gives me the same trouble. Does anyone know what I'm doing wrong?
I'm running an ATT Htc One m8, rooted, unlocked, s-off with sunshine, twrp recovery
mattprice86 said:
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom.
Click to expand...
Click to collapse
Give the ROMs about 10 minutes, and I bet they will boot. The extremely long boot time, and lack of boot animation (another symptom of this issue) makes a lot of folks believe the phone is stuck/frozen, when in fact its just taking a reeeeeally long time to boot.
If its true that the ROMs in fact never boot, it might just be an issue with your recovery. fastboot erase cache and either re-install recovery, update to the latest version, or try another recovery (Philz).
Even if the Sense ROMs boot, you might find some serious things are broken with your outdated firmware, such a broken WiFi. So I suggest either update your firmware or stick or ROMs based on your present firmware.
Ok thanks, i will try again. Ive read a bunch of threads about updating my firmware but couldnt find an answer to a question I have about it.
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
mattprice86 said:
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
Click to expand...
Click to collapse
Firmware includes the radio baseband, so it may cause issues with reception on AT&T. It seems at least a couple folks have been flashing the 3.28 firmware, but I haven't seen enough reports to give me a warm and cozy feeling. With S-off (which is required to flash the firmware, anyway) you can always revert. But still, basic reception is more important to me than a couple updated features. Personally, I'll probably wait until the 3.x firmware specific to AT&T starts rolling out.
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Leads me to believe that the radio does not matter like the N5 where the 820 and 821 radios were interchangeable.
HTC One M8
Thanks redpoint, you were right, I gave it some time and it did come on. You always seem to be the one answering my questions, I appreciate it.
As for the new fw, I was thinking that would happen too from what I've read, I just needed someone more experienced to confirm that. I think I'll wait as well.
Thanks again
Elisha said:
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Click to expand...
Click to collapse
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
mattprice86 said:
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
No probs.
redpoint73 said:
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
Click to expand...
Click to collapse
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former. For the record, my M8 is a "whelp", and I had to pay for Sunshine.
OMGMatrix said:
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former.
Click to expand...
Click to collapse
My guess would be the former as well. Keep mind that AT&T uses five different bands for LTE depending on your market region. Also keep in mind that travelling to another location may result in losing LTE reception (when you otherwise would have LTE on a AT&T specific radio).
Although none of this explains why I've seen some folks get NO SIGNAL whatsoever on AT&T's network after flashing the international firmware (2.x version, haven't seen any complaint yet on 3.28). Even if no LTE, those folks still should have been able to get HSPA and/or GSM since those AT&T bands appear to be supported by EMEA specs. So it leads me to believe there is something else going on aside from just band compatibility. Such as the network not falling back properly to HSPA/GSM.
I certainly don't have an issue if folks want to experiment with the 3.28 firmware on the AT&T network (as long as you know what you are doing, and are aware of the possible issues). Its certainly tempting with the 3.x based custom ROMs coming out. I might even experiment myself if I free up some time. But that spare time is a bit of a premium for me right now; and I also can't really afford ATM to have the possibility of reception issues or no service.
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
mattprice86 said:
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
Click to expand...
Click to collapse
You could always restore the backup you should be making before you do any mods on your phone. That would be the safest way.
So if I upgrade my fw then restore a backup, I will lose my fw changes?
I make nandroid backups before I do any, so I have approximately 60gb of backups on an external HD, and I always keep 1 or 2 on my internal and external storage
Hi everyone! I need some help or guidance here. I think I may know why this is happening but not sure . I'll explain in detail below:
Anyway, so the long awaited Lollipop was apparently released on April 7th for the T-Mobile LG G3. I've been waiting for it for a while just as many other probably have been. Well, none of the updates ever showed up on my phone via OTA or the LGMobile Support Tool.
The only thing I can think of as to why this MIGHT be happening to me (unless nobody else has been able to update yet because T-Mobile delayed the update) is because my IMEI has been reflashed to a Galaxy Note 2. However, I'm not sure that a different IMEI on my phone would prevent it from being updated since the firmware is obviously still a D851 LG firmware...
My phone is NOT rooted. It's all stock by the way.
Anyway, I guess what I need to know is:
1) Has everyone else with the T-Mobile Lg G3 been able to successfully update to Lollipop yet?
2) Will the different IMEI on my phone affect whether or not my phone is detectable as a D851 G3?
Thanks everyone in advance!
Bump. Anybody?
I'm really not sure that IMEI have any effect on the update center , have you tried to do a factory reset ?
another thing I can think of is just root your device and install a stable fast stock rom that uses LP on it ( like cloudy ).
MrFishiz said:
I'm really not sure that IMEI have any effect on the update center , have you tried to do a factory reset ?
another thing I can think of is just root your device and install a stable fast stock rom that uses LP on it ( like cloudy ).
Click to expand...
Click to collapse
Yeah I'm not sure it does either. I talked to a friend of mine that works at T-Mobile and he said a mismatched IMEI shouldn't make a difference. However, worst case scenario I'll have to manually flash it to Lollipo once the official ROM has been uploaded somewhere on the internet. I haven't tried to do a factory reset. Not positive on this but I think the IMEI is stored in memory that won't change whether it's factory reset or not especially since the original one was wiped and replaced.
I'll try to stick to the stock ROMs on this phone to avoid any issues with the custom stuff. Although, I was never able to successfully tether via WiFi on this phone. It works via USB cable. Still annoying hehe.
SaMirakle said:
Yeah I'm not sure it does either. I talked to a friend of mine that works at T-Mobile and he said a mismatched IMEI shouldn't make a difference. However, worst case scenario I'll have to manually flash it to Lollipo once the official ROM has been uploaded somewhere on the internet. I haven't tried to do a factory reset. Not positive on this but I think the IMEI is stored in memory that won't change whether it's factory reset or not especially since the original one was wiped and replaced.
I'll try to stick to the stock ROMs on this phone to avoid any issues with the custom stuff. Although, I was never able to successfully tether via WiFi on this phone. It works via USB cable. Still annoying hehe.
Click to expand...
Click to collapse
There is already a firmware on the forum: http://forum.xda-developers.com/showthread.php?t=2785089
I don't know if you can do this guide though since you never rooted your phone, better if you ask there.
MrFishiz said:
There is already a firmware on the forum: http://forum.xda-developers.com/showthread.php?t=2785089
I don't know if you can do this guide though since you never rooted your phone, better if you ask there.
Click to expand...
Click to collapse
Thanks for the link. I don't think the OP has the D851 Lollipo version uploaded. I only saw it for D855. I guess I'll just wait until everyone else gets the official update and flash it manually. From what it sounds like people have been having issues minor issues with Lollipop anyway. Maybe that's why T-Mobile is delaying the OTA updates. Who knows
I have Lg F240-EUR version, which is running on 4.1.2.but the software/os that came with the phone is slightly different from the original firmware.And the signal is sometimes dropping like showing x mark for 3-5 times a day.and the main problem is it cant be updated to any version.I checked in the IMEI website and found that my model is f240s.If I upgrade thehpone,i will loose signal forever as some people mentioned that they lost signal after upgrading their phone through custom roms or official firmware in other forums.I want to upgrade my phone to either official 5.0 or any custom 5.0 rom. please help me in upgrading my phone so that i shouldn't loose the signal even after the update.
krishna13 said:
I have Lg F240-EUR version, which is running on 4.1.2.but the software/os that came with the phone is slightly different from the original firmware.And the signal is sometimes dropping like showing x mark for 3-5 times a day.and the main problem is it cant be updated to any version.I checked in the IMEI website and found that my model is f240s.If I upgrade thehpone,i will loose signal forever as some people mentioned that they lost signal after upgrading their phone through custom roms or official firmware in other forums.I want to upgrade my phone to either official 5.0 or any custom 5.0 rom. please help me in upgrading my phone so that i shouldn't loose the signal even after the update.
Click to expand...
Click to collapse
I bought a similar refurbished phone from Aliexpress and the system information is the same as yours. I think they just messed with the build.prop so the build information looks ready for Europe. I will advise you to install the kdz so you have the Stock ROM and firmware. That was what I did anyway. The only porblem is that you will get some Korean apps but the phone is stable anyway. And when flashing, use "CSC" not "Normal" flash.
By the way, my phone was lagging very much before I installed the Stock ROM.
lallolu said:
I bought a similar refurbished phone from Aliexpress and the system information is the same as yours. I think they just messed with the build.prop so the build information looks ready for Europe. I will advise you to install the kdz so you have the Stock ROM and firmware. That was what I did anyway. The only porblem is that you will get some Korean apps but the phone is stable anyway. And when flashing, use "CSC" not "Normal" flash.
By the way, my phone was lagging very much before I installed the Stock ROM.
Click to expand...
Click to collapse
So after upgrading ,is ur phn showing signal normal?many mentioned that after upgrading they lost their mobile signal and their imri number to all zeros.so are u sure this wont happen to me?i am frm india.so there will be no problem with the bandwidths for networks in india?
At present even my phone running on 4.1.2,whenever i enable my data,after disabling it my signal shows x mark for 2-4 seconds then i will get back again.also some cals cant connect to my phn.so after upgrading,are there any chances of loosing my phone signal?
krishna13 said:
So after upgrading ,is ur phn showing signal normal?many mentioned that after upgrading they lost their mobile signal and their imri number to all zeros.so are u sure this wont happen to me?i am frm india.so there will be no problem with the bandwidths for networks in india?
At present even my phone running on 4.1.2,whenever i enable my data,after disabling it my signal shows x mark for 2-4 seconds then i will get back again.also some cals cant connect to my phn.so after upgrading,are there any chances of loosing my phone signal?
Click to expand...
Click to collapse
I cannot reaqlly gurantee your phone being messed up but mine works perfectly after installing the kdz. I installed the 4.4.2 version although there is lollipop version as well. I just want to try the kitkat version for some time.
lallolu said:
I cannot reaqlly gurantee your phone being messed up but mine works perfectly after installing the kdz. I installed the 4.4.2 version although there is lollipop version as well. I just want to try the kitkat version for some time.
Click to expand...
Click to collapse
I am unable to install custom recovery on my f240s.can u pls help me with the steps and links inorder to take backup of my current version. Also one doubt.If anything goes wrong after upgrading to lollipop (like if i lost signal in my phone) then after restoring the backup rom,can i get the signal back?? Also which is better? Some complained that after upgrading to lollipop they got signal issues.is installing kitkat= installing lollipop or is there any difference considering to the signal prblm?
(sorry for my bad english but i need help.pls suggest me)
Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Balian67 said:
Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Click to expand...
Click to collapse
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
dhplap said:
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
Click to expand...
Click to collapse
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Balian67 said:
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Click to expand...
Click to collapse
So you're on the CPD1 bootloader?
dhplap said:
So you're on the CPD1 bootloader?
Click to expand...
Click to collapse
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Balian67 said:
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Click to expand...
Click to collapse
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
dhplap said:
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Click to expand...
Click to collapse
I will keep this in mind. I am currently on Resurrection Rom and I have ZERO issues. I don't want to mess with it. When I start to mess with stuff is when I spend 12 hours fixing something that should have only taken an hour to do to begin with. As the comment below you said...he has the same camera issue on CPD1
bagery77 said:
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
Click to expand...
Click to collapse
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Balian67 said:
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Click to expand...
Click to collapse
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
bagery77 said:
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
Click to expand...
Click to collapse
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Balian67 said:
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Click to expand...
Click to collapse
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
bagery77 said:
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
Click to expand...
Click to collapse
I am so busy lol. I have 2 Sprint Note 4's that I am trying to root and I ran into ODIN/USB Driver issues. MAYBE I will worry about this next weekend haha. I will keep all this in mind. I will keep this post till then.
Thanks everyone.
I wanted to report that after I did all that stuff yall said, I restored my MODest Rom backup and the camera is now focusing. Maybe that will fix all the other issues with the other roms I tried using. I appreciate it Gents.