Database Develop

HTC One NFC missing after Flashing ARHD 8.0

Hi,
I've installed ARHD 8.0, and am absoloutely loving it so far, it is running like a treat, a particularly beastly one mind you! . My only problem is, since I flashed 7.4, which was my first ever Custom ROM, I haven't been able to get NFC. I clean flashed 8.0, hoping that would resolve the issue, but unfortunately I still have no NFC capability on my phone. I have enabled it in the settings, and I have also checked in my list of apps in order to see my Tags, but unfortunately that seems to have been wiped from the phone also, with no hope of getting it back.
I am on an International HTC One, which was previously locked to EE, on an ORANG001 CID, unlocked bootloader and have installed the ARHD 8.0, and flashed the same kernel in the boot.img file of the .zip for ARHD 8.0.
If anyone could help, it would be greatly appreciated, I would have asked about this in the ARHD thread but unfortunately I don't have enough posts and this same post didn't get much love in the Q&A thread .
Many thanks,
Omar

My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?

joshoon said:
My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?
Click to expand...
Click to collapse
Hi,
Yeah, I attempted to put this in the ARHD thread, but unfortunately I don't have enough posts to make any contribution in that thread atm.
Yeah, I did a full backup aswell of my 7.4, and also a full system reset of the davlik cache, cache, data, before I installed 8.0...
I am totally at a loss as to why my NFC has just gone, its not a urgent matter but I would like to try and get it back as it is undoubtedly going to be an important feature as contactless payment becomes more prominent.

[Q] Phone is not usable with random reboots

I've been experiencing random reboots since I bought my Developer Edition but today I think it hit me real hard with the random reboots in short intervals.
this kind of reboots happened to me both on completely stock and custom rom but today heavy reboots occurred when I was on Insert Coin 2.0.3 (S-Off).
According to someone's advice, I installed catlog and try to record the events until the phone reboots. So I post my logs here and hope some one could save me from this misery.
the first file was recorded with "write to disk every 200 lines" so it may miss some very last event when phone rebooted. The next ones were recorded with "write to disk every 100, 20 and 10 lines". I hope some devs could have a clue on what is happening with my phone.
I also save the log file AFTER phone reboot but they were too big to attach. If you think those might helo, I'll post them somewhere else.

Might be something to do with Xposed

BenPope said:
Might be something to do with Xposed
Click to expand...
Click to collapse
Yeah, I've noticed that some custom ROMs got issues with Xposed on S-Off device. However, as I mentioned earlier, this happened to me while I was on completely stock rom, too.
I've made a few observations and found out that I haven't got a single reboot on AOSP for a whole day but AOKP still gave me random reboots (not as frequent as on InsertCoin but still).
Any help would be very appreciated

might be worth trying to install sense rom again stock or custom and do full wipe, cache and dalvik. strange that an aosp rom works fine. must be something caused by a sense rom, drivers or framework. was this problem introduced when you started using 4.2.2 roms? have you updated to the new firmware.zip?

well, my habit of installing new roms is always do a full wipe so I think the cause of reboot should not be related to that.
After getting no reboot on AOSP roms (carbon, cm 10.1), I decided to go back on custom sense roms but no luck. reboots just came back no matter what roms I was on (renovate rev 45, insertcoin rev36, rayglobe 4.3).
I went to stock again with RUU dev edition (.16 one). Phone gave me a reboot right after I finished setting up (as new phone). However, it has been running stable up to now (3 hours).
Should the reboot have any thing to do with Sense, i'm wondering. I would be very thankful if any devs can help me on this issue. I'm willing to make as many logs as required or install any custom, stock roms if neccessary.
Sincere

Has Anybody Experienced or Seen This Screen Phenomenon?

I've posted this in one of Mirek's threads and it's been lost in conversation. Hopefully someone has some ideas.
http://forum.xda-developers.com/showpost.php?p=64996639&postcount=685
My guess is its Mirek's ROM, but I can't conclusively confirm. I've tried flashing his 4.4, but touch doesn't work and his fix doesn't either. What I DO know is that no such thing occurs when I'm in Windows. In Android, the screen/reboot issue happens randomly. Sometimes it can go hours without an incident, sometimes every 10-15 minutes. So it can't necessarily be a hardware problem, right? Then again, it might be that Windows is using the GPU properly, while this version of Android is messing with it.
All said, this is getting rather annoying.
Thanks in advance!

same problem here, whenever I'm playing wordfeud. I got mirek rom 7.Extremely annoying, has anyone a fix for this?

After testing nearly the whole versions of Mirek's roms including lollipop and kitkat , I found that the best stable and performing rom is the stock kitkat rom and you can root it to remove the bloatware out of it and you'll have battery free bug and the other related complications .

melmarghaney said:
After testing nearly the whole versions of Mirek's roms including lollipop and kitkat , I found that the best stable and performing rom is the stock kitkat rom and you can root it to remove the bloatware out of it and you'll have battery free bug and the other related complications .
Click to expand...
Click to collapse
Stock Kitkat, as in from Teclast?

OnePlus 3T Update or flash a ROM?

Hi! So, for now I'm running OOS 3.5.4 because I hated the 4.0.1 (I downgraded from it). So, now I don't know if updating to 4.1.1 or getting a ROM. I heard a lot of discordant opinions about the new update of OOS and myself didn't like the first nougat update. If I'll flash ROM, what should I flash(without bugs and with a good camera quality, because seems that all the roms have ****ty camera quality)?

Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.

redpoint73 said:
Just my take: Asking for advice about the 4.1.1 update vs. custom ROM (and for that matter which custom ROM) is a matter of personal preference. As you've said yourself, opinions on the update are discordant (as will be true for any update). Just because someone gives your a particular response one way or the other, doesn't mean it will be the right answer for you. The only way to conclusively answer the question for yourself, is to try out the update and/or ROMs.
I would generally recommend updating firmware/modem in any case, whether you decide on the official update or a custom ROM. So it may make sense just to do the update (which will also update firmware and modem) then see if you like it. If not, try a custom ROM.
Alternately, even if you opt to go right to a custom ROM (after unlocking bootloader and flashing TWRP), I'd suggest at least flashing one of the updated firmware/modem zips posted in the 3T Guides, News & Discussion section.
Click to expand...
Click to collapse
Thank you. I will probably update then, and if I won't like it I'll go to a custom ROM. Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)? Thanks

_HaZaRD_ said:
Could you suggest me any good/stable ROM out there (especially without bugs and with a good camera quality)?
Click to expand...
Click to collapse
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.

redpoint73 said:
As I already mentioned, what I said about update vs. custom ROM, will also apply to asking for recommendations about a particular custom ROM. It depends on your personal needs and preferences. You have to make the decision yourself.
Further, I'm still on stock 7.1.1, rooted; and haven't tried any custom ROMs on this device yet. So I have no custom ROM recommendations.
Click to expand...
Click to collapse
Ok

I updated from 4.0.3 to beta 4 via local, but now I want to go back because of the battery drain problem. I tried several times via adb sideload to flash the zip but I keep getting the same error <cannot read 4.0.4.zip> over and over again. Even after installing the drivers, I got a little yellow exclamation triangle near the driver in device manager. Honestly I'm starting to give up, I think I wiped my phone more than 5 times in order to flash via sideload, only to get the same error continuously. as far as I know, I cannot go back to 4.0.3 via local from beta 4 right?
Please help...

GPS locks for Oreo Roms but will not follow when using navigation to go anywhere

Hi. I am at a loss on how to fix my GPS on my device. When using Lineage 7.1.2 I can use Google Maps without issue and use navigation to get me places. When I try and use ANY Oreo ROM I can get a GPS lock only on my current location however I can not use navigation; the device stays locked to the start point and will not follow me. When Oreo first came out I was able to upgrade to Oreo and use Maps without issue. I am somewhat a flashaholic and like trying different ROMS to see how they work day to day so I have flashed GZOP, Cardinal, Omni, Lineage 15. I have tried all different Firmware updates by Lord Boeffla trying 4.1.7 (Which I am currently using and Lineage 7.1.2 navigation works) 4.5.0 and 4.5.1 to try and rectify this but it does not matter. No matter what firmware I try and use the results are the same. Lock but will not follow At one point I even tried downgrading to Stock 3.5.4 firmware and software to which I was able to flash but the system would not boot only would bootloop. At this point I am not able to flash any stock OOS ROMS and I must use a custom built ROM such as Lineage to get the phone to boot. I have tried many GPS fix apps such as AGPS to try and force clear GPS cache and reset they system but the results are the same. Lock and no follow. Any ideas on what else can be tried to resolve this? I fear I may have damaged the device throuh flashing the firmware so many times and I will be stuck with Nougat forever with the current phone.

All Oreo ROM's are in Alpha/Beta build stages. I've experienced similar results on many Oreo ROMs. The best course of action you can take is providing logs to the developers of the consecutive ROM, and let them work.
Different firmware versions don't make any difference to the GPS. ROM's are built on top of the firmware, and such. Flashing different firmware's will not fix the issue. Go back to Nougat if you want a stable system.
The issue here is you're complaining about bugs on Alpha/Beta ROM's.

I have been facing the same problem in Nougat Roms too. I think it has been introduced in 4.1.7
The only course of action would be to get it fixed in Beta OOS by providing the logs to the devs.
Here's a related thread :
https://forum.xda-developers.com/oneplus-3t/help/poor-gps-oos-4-1-7-t3664864

Had same issue, refresh latest beta firmware.

I've no issue using gmaps on ob 17 I use it daily.