yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I prefer a more hands on option. You can flash a zip from lineageos to disable it's root so supersu will work...but it doesn't. https://download.lineageos.org/extras

The only one that will flash is 2.46, but it just hanges at the boot animation for eternity. Of the few times I managed to manually install supersu, it wouldn't even try to update the binaries. It will say unsuccessful and to reboot, only to repeat the process with no end.

Root was built in to cm 12 too. but SuperSU managed to flash perfectly fine without any complications whatsoever. What changed between then and now where It can't detect the boot image?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Why SuperSU? It's old and deprecated.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Because I'm still working on things that require editing the system here and there. And using magisk when trying to do those things is just too much of a pain for my liking. either forget to turn off toggles or turn them on. there are still things that don't work in the kernel that we are still trying to get to work. So I'm just not comfortable with using such a extravagant system.

Also this kind of fits in with the discussion. No magisk installed on this tablet currently with cm 12. How I got this or how it happened I have no idea. I just happened to notice it about 5 minutes ago. Screenshot below.....

.... Can we say certified? Why yes we can.
[Fire HD 8 and HD 10 Original Android Development] chemengire:
DragonFire1024, what exactly are you working on now? ?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Oh for example trying to get GPS to work maybe NFC. Tracking down files for the actual GPU which is called Power Rogue. Found a few today. I'm working on any number of things at any given time, when I have it.
[Fire HD 8 and HD 10 Original Android Development] OptimisticShaggy:
Are OMX & Camera still the only things not working?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Possibly the microphone as well. If anybody else can confirm or deny that please.
[Fire HD 8 and HD 10 Original Android Development] sga999:
Casting to a TV with Miracast also fails. But that may fall under being an OMX problem.

---------- Post added at 12:11 PM ---------- Previous post was at 11:59 AM ----------

@ggow, Court TV problem may be an OMX problem, but I don't know enough to say that for a fact. I just thought I would mention it again here since I haven't reported it in this thread. I did report it in the 12.1 thread in post #38. You fixed it in your August 11 release.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
You know that mt8173 doesn't have NFC no;)?

Take a look here you need it:

https://www.mediatek.com/products/tablets/mt8173

Enviado desde mi Aquaris M8 mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] Michajin:
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------

[/COLOR]

How can i get youtube working? or should i wait for update?
[Fire HD 8 and HD 10 Original Android Development] sananth:
I can confirm that the mic works fine, just casting the screen, and camera don't seem to work.
[Fire HD 8 and HD 10 Original Android Development] ggow:
Wait for an update. Needs fixed up selinux policies
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Mediatek uses their own framework for it. You can specify the parameters in the ProjectConfig.mk, and in the BoardConfig.mk in the device tree. I never had issues getting the drivers installed on the kernel end, but haven't had a ROM that was built with NFC to be able to test it. It has to be built alongside the kernel during the whole build process if I'm not mistaken. Much like I'm assuming with GPS as well. All the hardware is there, just can't seem to get the thing to turn on.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
PS. NFC https://github.com/Goayandi/vendor_mediatek_proprietary_hardware-mt8173/tree/aosp-7.0/nfc
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Okay. If you want to waste time trying to get working a thing that is not supported you can.

I will not discuss more. This is Offtopic
[Fire HD 8 and HD 10 Original Android Development] :
I installed LOS 14.1 today and I'm having issues with Netflix again :/ It doesn't show up in the Play Store, so I downloaded the APK from Netflix's website and that just throws me an error 0013. I installed SafetyPatch and I now Magisk and Google Play both show no errors, still doesn't work. I installed liboemcrypto disabler, still nothing. Anyone have any ideas? I kinda need Netflix to work...
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Does OP says that OMX is working?
[Fire HD 8 and HD 10 Original Android Development] :
I don't think so. I couldn't get it working on LOS 12.1 either though so I'm still not sure of the reason. I'm going to try LOS 12.1 again but AFAIK, SafetyPatch doesn't even work on there so Google Play just detects it as uncertified.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
we've been sitting here saying that GPS isn't supported for months yet at the link shared above it clearly says GPS among other protocols connected to it are supported. I'm not arguing actually this turned into something off topic when my question was redirected. I was asked what else I could be working on that I would rather use SuperSU over magisk? And that's quite simple changing things in the system etc. And then I followed up with a continuation of my question to ask what changed so drastically between two boot images, one where SuperSU flashes 100% perfectly fine, to a situation where not a single SuperSU zip will flash (doesn't detect boot image and the one zip that does flash the system, leaves it in a never ending replay of the boot logo) nor can it be installed manually (fails to acknowledge a binary is ever installed)? Given this has to do with this specific ROM on this specific tablet, I would say this is pretty on topic.
[Fire HD 8 and HD 10 Original Android Development] :
Tried LOS 12.1 again and thankfully all is well on there. Except for the headphone jack that is, and SafetyNet fails entirely (Magisk can't even check it?). Has anyone tried using a micro-USB to headphone adaptor to see if that works?
[Fire HD 8 and HD 10 Original Android Development] chemengire:
If 5GHz WiFi could be enabled then that would be cool...

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

I managed to get my battery idle consumption down to 0.2% per hour using Naptime and Servicely. That's 4.8% per day battery consumption while idle
[Fire HD 8 and HD 10 Original Android Development] smithbill:
5GHz WiFi is enabled and working. I think you need to read post #30
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
sigh you really need to find another device

super su is dead unsupported do not use SafetyNet exists for a reason a properly build rom will pass safety net with magisk, it will not with supersu meaning most apps that give a crap about root status are not going to run

the gps modem is physically disabled on this particular SOC you have been told that before and yet you continue on and on about it nobody cares we don't need gps support on this device it is never going to work period amazon cut the lines to the chip internally
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Supersu was doing just fine for me. I don't really care about safety net or certification and this particular tablet never had magisk. I don't need to get another device, but if you're basically telling me it's Magisk or nothing, then perhaps that needs to be highlighted somewhere in large bold text. But that doesn't mean I should be forced to use one specific root option. No one should. You saying supersu is dead is a matter of your opinion.

GPS being sliced is news to me. But that's beside the point and I'm not going to argue about it. My concern is the above stated.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Yes, SuperSU is viable on this platform albeit not without a struggle given the lack of community support. No, you (almost certainly) are not going to get hardware GPS working on this gizmo despite some spec sheet that suggests otherwise. Yes, another OT, thread hijack parade MCed by DragonFire. Seen this movie way too many times in the land of Amazon. Must be the water.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I didn't hijack anything thank you very much. I was asked the question I gave an answer and everyone chose to ignore my legitimate concerns and questions to continue on with a conversation I didn't even start. Why is it when legitimate concerns come up the peanut gallery has to respond? If you got nothing nice to say don't say it. do you guys have some kind of alarm that goes off specifically when I say something just so you can have a smart aleck sarcastic reply? Because so far my concerns have not been addressed. I simply asked what was such a significant change between one ROM to the next to which superuser flash perfectly on the 1st and on the 2nd won't even install regardless of the version?
[Fire HD 8 and HD 10 Original Android Development] zed011:
I would like to see this ROM compatible with apps or games that require gps since fireos didn't have any issues when I played GPS games whether that's with some workaround or the real thing
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Location services are Hit or Miss at the moment. There was no actual GPS on fire OS. They even remove Google's framework settings 4 fuse location and GMS to favor their own which was not very good. Android use this, if a device does not have active GPS, their own integrated aGPS protocol. Most of that is built into Google play services along with maps and a few added settings to the framework. I have tried with stock Fire OS to get a more accurate representation of this feature perhaps visually but it doesn't seem like there are strong enough capabilities within your ecosystem to support such a thing. Mediathek on the other hand implements their own aGPS feature somehow, which also includes an application for visuals and contains additional settings. I've managed to get the application to build a few times in the past, but without having a full-on mediatek device available or at least one that protocol activated, the application was useless. AGPS has another feature I am trying to get working on these things. By the way aGPS has nothing to do with GPS. There are two entirely different protocols.
[Fire HD 8 and HD 10 Original Android Development] x8LHiiIB:
I had this issue with a different app when I was using gapps. Once I switched to aurora store (along with microg via nanodroid), it became available
[Fire HD 8 and HD 10 Original Android Development] rohanhole:
I got cts profile verified , solution is I changed my device fingerprint to tab s.there is magisk module for that. MagiskHide Prop config.

But I am not sure what difference does it gonna make :)
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
How do you use that, though? I couldn't figure it out.
[Fire HD 8 and HD 10 Original Android Development] TheDevil259:
To pass SafetyNet you can just install the Magisk module "SafetyPatch"
[Fire HD 8 and HD 10 Original Android Development] rohanhole:
See , CTS failed because your device fingerprint is not matched with any from google. So basic idea is spoof fingerprint, which is the main idea of this module. Now , they have given predefined list of fingerprints so you dont need to find anywhere and it will save your time , off-course if you want to set custom fingerprint , then also you can do that.

How to set ?

Once you install module, go to terminal and need to execute >prop [ enter ] , It will ask options to set , ( self explainatory) for more detailed please see

https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props

---------- Post added at 07:05 PM ---------- Previous post was at 07:04 PM ----------

Nice to know. Thanks.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I still don't know how I did this on this tablet.
[Fire HD 8 and HD 10 Original Android Development] TheDevil259:
Mine is certified as well. It was a byproduct of the SafetyPatch module.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
This Tablet has never had magisk on it. It came out of the box, I unlocked it and flashed the ROM. And here I am today.
[Fire HD 8 and HD 10 Original Android Development] Zwitterion:
Out of curiousity, why do you think the headphones not work? As such a basic and mature piece of hardware that is likely supported by the SoC, I am surprised they aren't functional. Just asking as a learning point.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
driver or mixer path problem likely
[Fire HD 8 and HD 10 Original Android Development] retora:
How did you figure that out?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Since the question is asked, I will chime in. There is on some of this trip set separate GPS chips it appears. Then there is some kind of implementation mediated uses with the connectivity combo AKA combo chip. That chip is mt66XX. On some mediatek devices this might be a little more specific for example on the HD 10 it mt6630.and in the case of that specific driver there is no one specific build for it when talking about the connectivity combo. This specific library of drivers is called upon in the board configuration in the common tree. However when using a common build configuration, the generic run-of-the-mill Wi-Fi driver call the upon is not acceptable. However if you change that to a mediatek specific hardware configuration, you have to use the specific build files for that driver or library of drivers. I know this because I have come across this problem dozens and dozens of times before I finally figured it out. So although this device may possibly have a physical GPS chip it is not necessarily implemented only through that chip. Because if the chips or chip we're physically caught with anything we would not have Wi-Fi or Bluetooth. Because in the connectivity combo where the implementation of mediatek GPS is located, clearly works because we do have Wi-Fi and Bluetooth. Anyway that is my take on it.
[Fire HD 8 and HD 10 Original Android Development] 911medic:
[MENTION=5749760]ggow[/MENTION] I think it's important to note that as of right now, if your HD10 is on 5.6.4.0 build 9820, the required unlock method linked in the first post in this thread (next to "EVEN MORE IMPORTANT") does NOT work.

The creator of that method needs to update the "temporary brick" downgrade step to work with that build, and he has not yet done so.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
That's already warned in the unlock thread.

And you can still unlock it opening the tablet;)

k4y0z has life and is busy, when he can he will upgrade the brick.

---------- Post added at 09:38 PM ---------- Previous post was at 09:32 PM ----------

Agreed. Add NFC with GPS:p
[Fire HD 8 and HD 10 Original Android Development] Shadow Death:
You care. In fact you care so much that you and others keep coming in here and doing this same thing over and over despite the fact that every time you do the mods have to show up and clean up this sub-forum. I'm getting sick of seeing this ****. The dude wants to learn for himself and you guys keep are all over him. So the guy doesn't listen to you when you say something... Oh well. Grow up and deal with it. This isn't Reddit. The Android community used to be about learning and developing.. Now I'm starting to see a bunch of people everywhere scoffing at people who don't know something or they wave the insult stick around.

Yeah I'm aware that my post may attract a mod, I'm ok with that.. but this ****.. I'm so damn sick of it.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Learning is fine; we all start somewhere. Location and frequency are at issue. I have 'defended' members right to wander OT in threads designated for that purpose. If one wants to discuss random topics best start a dedicated thread.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I have been continuously told by some people over the course of many years on XDA that I was/am wrong about any number of things, only to be blindsided by the impossible by some of those same people. I keep quiet about those various things because as is stated, some people are just pretentious and can't stand the thought of someone else being right about something or someone else getting credit for something. So its not worth the argument. I've said what I needed to say. Anyone who really cares about my track record, can Google me or search xda for the past 5 years.
[Fire HD 8 and HD 10 Original Android Development] yuera:
Is there any reason to use the 12.1 from the other thread instead this 14.1?
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
Edit: Confirmed fixed in Oxygen OS 10.0.1

I have been struggling since Saturday with data issues on my OP7P after upgrading to Oxygen OS 10.

With Google Fi, I was able to activate the SIM in OOS 10, but the mobile data would stop working. It would work for a little while, but then I would get an exclamation mark on the signal bar and no data services would work. Reactivating the SIM by clearing the storage and cache for the Fi application would work temporarily, but the issue will just happen again. If you are on WiFi, you will not get an exclamation mark and no data services. It only appears when not connected to WiFi.

For Visible, the phone sees that a SIM has been inserted and after opening/authenticating in the Visible application, you will get a message that says it needs to check them SIM. After hitting OK, you get prompted to give permission to the application to make and receive phone calls. After that, nothing happens. The SIM never activates and service is not available.

In both instances, Google Fi and Visible support were not able to figure out how to get their respective services working on Oxygen OS 10. I reverted back to Oxygen OS 9.5.13 (last revision of OOS 9) and both services work flawlessly. My hunch is that this is a problem on OnePlus' side, considering it is happening with both providers, but either way, I hope this gets fixed because it sucks not being able to upgrade.
[OnePlus 7 Pro Questions & Answers] TacoTuco:
Idk if it should be a PSA because my Google Fi works perfectly fine for me and I've been on OOS 10 for almost a week now
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
Did you upgrade manually or did you get the OTA? I flashed 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051 and had nothing but problems.
[OnePlus 7 Pro Questions & Answers] TacoTuco:
I manually installed it cause I was impatient ?. I was originally using magisk and Twrp for a couple days and had no problems with Fi or the OS. I did a factory reset to my phone and used the fastboot rom in order to completely wipe it just cause I felt like using stock for a couple days and still didn't have any problems on the OS. If I were you I'd try to use the fastboot rom for OOS10 just so you can start with a clean slate, maybe it'll help ¯\_(ツ)_/¯
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
I had originally flashed the ROM that I downloaded from Oxygen Updater through TWRP while trying to preserve root w/ Magisk. After I couldn't resolve the issue with Fi, I flashed the Fastboot ROM for OOS10 like you. I still had major problems with both Fi and Visible. I flashed the Fastboot ROM for 9.5.13 and all of the problems magically went away. I am not the only person having these issues, so it seems pretty widespread. Visible does not work at all with OOS 10.
[OnePlus 7 Pro Questions & Answers] TacoTuco:
Oh man that's weird sorry I couldn't help. Good luck, hope this thread gets some traction and more people see it
[OnePlus 7 Pro Questions & Answers] tdamocles:
You guys need to get in oneplus's feedback bug threads on their web forum and report it. Also chat with them and show them your concerns because they have no idea right now. Same problem here. 9.5.13 works but Android 10 doesn't.
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
https://forums.oneplus.com/threads/...e-with-google-fi-and-verizon-visible.1109497/
[OnePlus 7 Pro Questions & Answers] svntsvn:
Selecting the second apn helped, also enabled all Google fi permissions, not sure if both helped or just the apn selection. I probably threw a network reset and cache clear on play services apps for good measure since I was trying it all. Definitely try the second apn I've been good since I did that, no other combination previously seemed to work.
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
Has anybody gotten Visible to work on OOS 10 yet?
[OnePlus 7 Pro Questions & Answers] cobrajet7:
Lame
[OnePlus 7 Pro Questions & Answers] ageesm:
Same deal here. I just got my phone last week, upgraded to Android 10 before activating Google Fi or setting anything up. I had no problems activating on 10 and everything worked, but I would lose mobile data probably 2 or 3 times a day depending where around town I was. After selecting the 2nd APN like your screenshot I haven't had any more issues.

Obviously I can't speak to Visible, seems something worse is going on there...
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Yes. I was able to get visible working on oos 10 and Omni 10. I edited all the normal Verizon apns in the config file to visible instead and everything works, calls, texts, mms and data. I'm attaching the apn config needed to get it to work. This will work on oos 10 and Omni 10 and possibly other Android 10 ROMs. You either need root or twrp to get it to work. In twrp, mount system and use file manager to copy file to /system/system/etc and chmod to 0644 or use root file explorer to copy file to /system/etc/ and give 0644 permissions.

Edit: I forgot to mention, after you replace the file you need to go into networks and apn and click the 3 dots on top right and click reset to default for the visible and to show up and then select the VSBLINTERNET as the one selected.
[OnePlus 7 Pro Questions & Answers] tdamocles:
Tell me step by step because I can't get the visible apn to show. Followed everything you said and it did not work. On oos 10.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Are you trying to do using a root file explorer or from twrp? Also are you on OOS or custom rom?

Method 1 (using root file explorer):

1. Download the attached apns-conf.xml

2. Using root file explorer browse to /system/etc and rename apns-conf.xml to apn-conf.bak to have a backup.

3. Copy the downloaded apns-conf.xml file to /system/etc

4. Using root file explorer change permissions of the new apns-conf.xml to 0644

5. Go into networks settings and click on your visible sim card (probably shows as Verizon) and then click access point names.

6. Click on 3 dots in upper right hand corner and click on reset to default.

7. The visible apns should now be visible and you should select the VSBLINTERNET apn.

Method 2 (using TWRP):

1. Download the attached apns-conf.xml file.

2. Boot into twrp.

3. Click on mount and select system.

4. Click advanced and then file manager.

5. Browse to /system/system/etc

6. Locate the current apns-conf.xml and rename to apns-conf.bak

7. Browse to downloads folder and copy the new apns-conf.xml to /system/system/etc

8. Browse to /system/system/etc and click on the new apns-conf.xml and click chmod and type 0644 to change permissions.

9. Reboot

10. Go into networks settings and click on your visible sim card (probably shows as Verizon) and then click access point names.

11. Click on 3 dots in upper right hand corner and click on reset to default.

12. The visible apns should now be visible and you should select the VSBLINTERNET apn.