yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] xduser1:
Tried Nitrogen and Beltz, and experienced on both.

In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.

20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16

20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)

20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone

20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210

20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)

20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'

20:03:10.590 F/DEBUG (15485): Revision: '0'

20:03:10.590 F/DEBUG (15485): ABI: 'arm'

20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<

20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'

20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008

20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c

20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0

020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030

20:03:10.634 F/DEBUG (15485):

20:03:10.634 F/DEBUG (15485): backtrace:

20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)

20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)

20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)

20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)

20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)

20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)

20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)

Sometimes different packet type (i.e. 104).

Any help appreciated...
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] xduser1:
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
[Nexus 6 Q&A, Help & Troubleshooting] kgiri247:
I have the same issue with every 8.1 build I have tried. I think LOS is less problematic and I have fewer disconnects reconnects. Glad I'm not the only one with the issue. I was going to flash back to stock to see if the issue persists, but I'm pretty sure Bluetooth is incomplete for the N6 and 8.1. Every ROM i have tried also misreports Bluetooth battery drain.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
I can say, I use a Bluetooth headset and external gps and connect to my ODBII port all simultaneously without any disconnects. I'm using ABC for shamu and it's been rock solid. I also do not get misreported numbers.

If that's one of the rooms you've tried, and you've clean flashed, then think about trying inn safe mode. Maybe some app is interfering. Safe mode will reset your settings and desktop. You probably want to take a nandroid first.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] xduser1:
Several data points:

On 8.1, I only experience this issue with this one car, all other bluetooth devices and cars that I've tried worked perfect.

I do not experience this issue with this car on 7.1.2..

All ROMs were clean flashed.

Also tried friend's Pixel 2 with stock 8.1, and it worked with this car without any issues.
[Moto G5 Plus Questions & Answers] bird412:
hello all,

i purchased the US variant with 4/64 gb, unlocked the bootloader, installed twrp and magisk, and installed OMNI rom this morning. i decided to go back to stock shortly after, so i flashed the stock zip that is flashable with twrp, and i failed to wipe it. it then would not boot, so i followed this guide: https://xdaforums.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396

it worked and i have the stock os back, but now it will not connect to the Verizon network at all. ive done at least two OTA updates, and I am now on NPNS25.137-93-4.

does anybody have any solutions or fixes?
[Moto G5 Plus Questions & Answers] gumpysitruc@gmail.com:
Go to the end of this thread.https://xdaforums.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396/page2
[Moto G5 Plus Questions & Answers] bird412:
That was me, thank you very much!
[Fire HD 8 and HD 10 General] 1ofamillion:
Definitely looking forward to trying this!
[Fire HD 8 and HD 10 General] oscarcx:
Still waiting for part 2. Also wondering if it's possible to modify the framework so that we can customize the power options.
[Fire HD 8 and HD 10 General] DragonFire1024:
Got a little busier this weekend than I predicted. I will try to get part 2 up today or tonight.

Is it possible? Yes. However I'm having a difficult time with it. Those settings are a bit scattered and butchered so I'm having trouble figuring out which xml to edit. Amazon created their own xml files to override some of androids. It also doesn't help that a lot of values from the bools are repeated then scattered across various system apps. I know one issue is the power profile. Amazon did a good job of butchering that setting and it's proving difficult reconstruct. In other words the power profile is almost non existent.
[Fire HD 8 and HD 10 General] oscarcx:
No need to hurry. These are great discoveries so take your time to write the tutorial:D

In my opinion, your tutorial is kind of way too detailed. I know it's great for tech newbies, but by simplifying it a little bit could effectively save your time.

For the power option, if it's way too hard to customize it, maybe spending time on other stuff will be a better choice.

Anyways, thanks for your amazing work!
[Fire HD 8 and HD 10 General] DragonFire1024:
I think it's more of putting pieces back in the right spots, for example, settings fragments. Some things are directed with Amazon's fragments and it's just a matter of finding the right android fragment and replacing it. In other cases, Amazon blocks out some features in an 'assets' file. Some things are also set in smali files/java and I know very little about smali, so have been reading up on that. Sometimes the fix is just a simple word change like the DayDream. I also recently discovered other settings or at least "project defaults " set by mediatek. I'm able to change some of those and supposedly add them to the build prop for more activation, but so far I haven't seen a difference.
[Fire HD 8 and HD 10 General] DragonFire1024:
Change your lock screen wallpapers everyone :D Part 2 is out!
[Fire HD 8 and HD 10 General] oscarcx:
Brilliant! Never thought of replacing those default wallpapers. At least this is a temporary solution.

I am wondering how the lockscreen wallpaper works and correct me if I am wrong. The app called "Special offer" is included in stock Fire OS and it has the ability to either change the wallpaper or overlay the wallpaper. Maybe it's a good idea to start from there but I am not sure about the legitimacy issue.

The lockscreen itself is weird though. Using Gravity Box, I can change some of the features but not all of them. Someone here told me that the lockscreen is deeply integrated into Fire OS.
[Fire HD 8 and HD 10 General] lakitu47:
There's a line in the build.prop file called "curlockscreen" with a value of 1. I have no idea exactly what it's for, but it might be related to disabling and/or modifying the lock screen.
[Fire HD 8 and HD 10 General] oscarcx:
Just did a quick search on it and looks like it's the default lockscreen style
[Fire HD 8 and HD 10 General] GamerOfRassilon:
I decided to give Part 1 a try.

I got up to step 15 successfully, including having the Daydream tile.

I'm presuming that — to install BasicDreams.apk (in step 16) — you need to have another round of "adb remount"

Unfortunately, although "adb remount" worked when I did it the first time, trying to do it now results in an error:

remount of system failed: Invalid argument

remount failed

Trying to copy (with the "adb push BasicDreams.apk" command) results in an error:

adb: error: failed to copy '[PATH]/BasicDreams.apk' to '/system/app/BasicDreams.apk': remote Read-only file system

(Unsurprisingly, this is the same error if I try to do the "adb push BasicDreams.apk" thing without trying "adb remount")

In all cases, I'm re-enabling the "Enable insecure adbd" option from the "adbd insecure" app.

Any ideas how to fix this?
[Fire HD 8 and HD 10 General] DragonFire1024:
Make sure box is checked in adb insecure. After a reboot, you need to check the box again.
[Fire HD 8 and HD 10 General] DragonFire1024:
Yes but broken up internally. I do have a fix but I have to consult a developer before I announce it as it uses a piece of software from another rom.
[Fire HD 8 and HD 10 General] Supersonic27543:
How about,

adb shell

su

mount -o rw,remount /system

Instead of adb remount? It looks like an error in adb remount.
[Fire HD 8 and HD 10 General] DragonFire1024:
You can do that I suppose. I haven't tried. I side stepped that method because adb will make sure the APK has the permissions assigned properly amongst other anomalies I've come across. These are old APKs from original sources I work with. Most of the time i keep them safely inside their zipped ROM and sometimes you only get so many uses out of them if you move them around outside the system too much without proper permissions. In a matter of speaking they get lost and stop working. So I try to minimize the amount of time they remain away from home. With that said, it shouldn't be a problem.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
To follow up here:

1) I was certain I re-enabled adb insecure.

2) I tried "mount -o rw,remount /system", and got a similar error: "mount: Invalid argument". I also tried a command that worked in the past (that I'm pretty sure is doing the same thing): "mount -w -o remount /system" (no quotes, obviously), and also got the "mount: Invalid argument" error.

3) The error I had in this circumstance was similar to one I had on an unrelated matter regarding getting FlashFire working.

What I suspect is that somehow /system gets tired of being written to, and it "locks me out" for some reason. (There are two points when I have traditionally made use of "mount -w -o remount /system" — when I copy over the initial /system image via "dd if=/sdcard/system.img of=/dev/block/mmcblk0p13; sync" and when I disable OTA updates with "mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_" )

Another possibility is that I had somehow made a mistake in following this tutorial originally, typing "adb push [SOURCE]\framework-res.apk /system/framework-res.apk" instead of "adb push [SOURCE]\framework-res.apk /system/framework/framework-res.apk"

I deleted the errant framework-res.apk from /system, but I wonder if that somehow tripped up some kind of "don't muck with this" flag that wouldn't let me remount it.

4) Speaking of which, are you sure about this command in Step 16?

I can't get it to work. In fact, if I use a file browser to go to /system , I just have a non-folder file named "app" that happens to be the same size as BasicDreams.apk . . .

I reflashed my /system and confirmed that I don't seem to have a folder named "app" in /system , so I can't quite figure out what that command is doing . . . Does it need to be:

adb push BasicDreams.apk /system/priv-app

? (I have a 2017 HD10, if it matters.)

5) For my second attempt, I tried to do as "clean" a re-install of my system as I could, avoiding the two instances of when I would remount /system in the past (flashing a straight system.img extracted from an update and freezing the OTA app with Titanium Backup). This time, remounting worked both times, as did the rest of the procedures (with the exception of the "BasicDreams.apk" problem, directly above).
[Fire HD 8 and HD 10 General] DragonFire1024:
I am not too sure why this is happening. I presume you edited the framework-res.apk? If so, use a root explorer, I use the actual Root Explorer, and navigate to /system/priv-app and create a folder named BasicDreams. If using root excplorer, Long press the folder, tapp three dots at top right, tap permissions, set to 0755 (rwxr-xr-x). Place the APK in the internal storage of your tablet. Open your root explorer and go to your internal storage. CUT the APK FIRST to /system then CUT it to the BasicDreams folder in /system/priv-app you just made. When done, if using root explorer, long press the APK, tap three dots on upper right and tap permissions. set permissions to 0644 (rw-r--r--). Reboot then go to settings, display, and see the Daydream menu.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
I did edit the framework-res.apk, yes.

I jumped through all those hoops, it it is — indeed — working! (I interpreted the instructions as "Cut and paste into /system, then cut and paste it from /system into the folder on /system/priv-app" . . . is that because the file needs to "touch" /system to work correctly? And I just COPY/pasted the first time into /system, to keep the original backed up on my SD card.)
[Fire HD 8 and HD 10 General] DragonFire1024:
It touches the system just as a precaution. I've read in places it a way for the system to better accept APKs as a system app when you force install it like this. I don't know if it's true, but when manually adding a file, i take this step as a just in case route.
[Fire HD 8 and HD 10 General] 1ofamillion:
So I finally got around to doing post 2, and it worked great! It's nice to finally have a custom lock screen.
[Fire HD 8 and HD 10 General] DaRkNesss363:
Hey thanks for putting this together super excited to get it up and running!

I get to step 10 and I get some errors that result in it not compiling the APK. So I started over and same result.

Here is what I get when I run b framework-res

c:\apktool>apktool b framework-res

I: Using Apktool 2.3.3

W: Could not find sources

I: Checking whether resources has changed...

I: Building resources...

brut.androlib.AndrolibException: brut.common.BrutException: could not exec: [C:\Users\NSIEGF~1\AppData\Local\Temp\brut_util_Jar_15669223788725523207.tmp, p, --forced-package-id, 1, --min-sdk-version, 22, --target-sdk-version, 22, --version-code, 22, --version-name, 5.1.1-40.6.0.5_user_605485120, --no-version-vectors, -F, C:\Users\NSIEGF~1\AppData\Local\Temp\APKTOOL3190588099959971311.tmp, -x, -0, arsc, -0, png, -0, res/drawable-hdpi-v4/ab_bottom_solid_dark_holo.9.png, -0, res/drawable-hdpi-v4/ab_bottom_solid_inverse_holo.9.png, -0,.............................................................................

It goes on for quite a while. Thoughts on getting past this?

Thanks in advance!
[Fire HD 8 and HD 10 General] DragonFire1024:
You have to make sure you install the framework apk into apktool:

apktool if framework-res.apk

delete the folder apktool created (framework folder) when you've done the above. Decompile again, change the setting, save, recompile and complete the rest of the guide :)
[Fire HD 8 and HD 10 General] DaRkNesss363:
Same Result.....:( I will say that I had to deviate from the steps slightly as I got this error when trying to install APK Framework.

c:\apktool>apktool if framework-res.apk

S: WARNING: Could not write to (C:\Users\nsiegfried\AppData\Local\apktool\framework), using C:\Users\NSIEGF~1\AppData\Local\Temp\ instead...

S: Please be aware this is a volatile directory and frameworks could go missing, please utilize --frame-path if the default storage directory is unavailable

I: Framework installed to: C:\Users\NSIEGF~1\AppData\Local\Temp\1.apk

So I manually created the folder in the /APPDATA/Local folder and it completed with no errors but I don't believe its putting it in the right directory. is it?

It ends up putting "1.apk" in the new folder
[Fire HD 8 and HD 10 General] DragonFire1024:
You need to create an apktool directory in C:\. If on Windows, this needs to be done with administrator rights. So would be C:\apktool. Once that is created, then install apktool, and reboot. That should create the app/data directory. I can't tell you to try the finished product you speak of, because if it fails, you'll have to flash stock. So that would be up to you.
[Fire HD 8 and HD 10 General] DragonFire1024:
Change Log (framework-res)

oops
[Fire HD 8 and HD 10 General] DragonFire1024:
Change Log (framework-res)

July 8, 2018

- HD 10 FireOS 5.6.0.1 ONLY! Added framework code to make AGPS "functional". Greatly improves location accuracy. No visual user interface. Apps from the Play Store and elsewhere that claim to 'fix' or 'clean' AGPS will not work properly and using them may break this function. To 'potentially' turn off AGPS, please see this thread and install my re-written FireTabletSettings.apk Must have Google Location Services/Accuracy active. If having trouble activating Google's services, please see this thread for a fix on ALL Amazon tablets.
[Fire HD 8 and HD 10 General] DragonFire1024:
Will be posting an improvement to this soon. I have configured the framework so the screensaver acts as a real screensaver. In other words, combined with my FireTabletSettings.apk while disabling the lock screen, the screensaver will display after the user selected timeout. For example, if you selected 5 minutes for your screen to turn off, instead of going to sleep, it goes into doze mode and the screensaver displays instead of the lock screen.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've been trying to build a ROM for this tablet and I'll be honest, I'm not sure its possible. I have tried several methods and none of them seem to want to work. I have a few more ideas, but its not looking good. I think amazon has removed specific commands that have to do with meta reclusive and a few other needed commands for the updater script and if so, I'm not sure there's a way to fix this. I'll start a thread tomorrow and post then errors I received. I'm sure I'm not doing something right.
[Fire HD 8 and HD 10 General] TechNash:
Why not convert a TWRP Nandroid Backup into a flashible zip?

Just backup everything except internal storage.
[Fire HD 8 and HD 10 General] DragonFire1024:
Forgive me for sounding dumb, but we don't have TWRP. Assuming its not needed, how do I go about doing that?
[Fire HD 8 and HD 10 General] TechNash:
As long as you have a full NANDroid backup, and can develop a meta-inf file you can do it.

If we dont have TWRP then why are you attempting to develop a ROM.

Anyways, I'm porting a version of TWRP from the Kindle HD 2, since it is still actively developed.
[Fire HD 8 and HD 10 General] DragonFire1024:
Without a custom recovery, can only do a nandroid of the system partition. I found an app that did just that and figured out how to get the system image using dd. Problem now is, I can't edit the system.img.

Edit: the app is online nandroid backup. It creates a system.ext4.win file. I can edit it and what not after extracting it, but I've no idea how to make it into a system.img
[Fire HD 8 and HD 10 General] DragonFire1024:
Updates (for 5.6.0.1 ONLY)

Daydream Screensaver -

Added Photo Tables. Now you can use photographs as screensavers. Simply place some pictures/images into your internal storage in the pictures folder. Go to settings > display > daydream and you can set up your images through the services. Install PhotoTables.apk just like you did BasicDreams (instructions in the OP).

Modified some settings that allows the screensaver to actually act like one. When combined with my FireTabletSettings.apk to choose *NO* lock screen, the tablet goes into 'doze' mode when the screen turns off instead of sleep mode. This allows the screensaver to be on until the screen is touched. If you don't have the FireTabletSettings.apk installed, when your screen times out, and the lock screen activates, the screensaver shuts off. Don't forget to install BasicDreams.

Wifi Optimization - Combined both the screensaver and wifi modifications into one update. Before each framework apk was modified for one or the other so you wouldn't have both modifications.

In the OP - Added the framework-res and PhotoTable APKs to the OP.
[Fire HD 8 and HD 10 General] TheRealIntence:
I think the focus should be on the BL. I have heard that the BL gets verified by the PL which gets verified by a SoC. I will try to dump the PL and check how the PL verifies the BL. This is very hard to find out and it will take a lot of time but i hope I can get something to work with. Next step would be to dump the BL and modify it the way that the PL will accept it. If everything works fine, we will have a custom oreo Rom soon. But i cant promise anything!
[Fire HD 8 and HD 10 General] DragonFire1024:
Funny you mention SoC. Take a look at /system/bin at amzn_dha_tool and amzn_drmprov_tool. Open terminal emulator or ADB and run them. The DHA tool when you input:

amzn_dha_tool -d

Outputs a few interesting things. One of them being an SoC number that is alpha numeric and its 16 characters. Isn't the unlock code supposed to be 16 characters? I couldn't find any info on this tool.
[Fire HD 8 and HD 10 General] TheRealIntence:
I don't think thats the unlock code or something related to it. They wouldn't investigate so much time and ressources preventing anyone cracking the BL if there's just one command to unlock it...
[Fire HD 8 and HD 10 General] DragonFire1024:
Maybe not. But I've seen some things in FireOS that just don't make sense. Like how Amazon did so much to stop widgets, but left the instructions, script and ability to use them, literally in front of our faces. Another example is taking a social network sharing app and giving it a weird uid which allows that app to uninstall system apps if you run-as it. The HD 10 has its .mk file on board too. So I wouldn't be surprised if those tools in /system/bin just gave us the unlock codes, though not on purpose. I don't know if the .bin tools exist on the other tablets (I haven't looked yet), but you do need to be SU to execute them I think. So with the luck of having root on the HD 10, amazon may have gotten sloppy with the cleanups post os build.
[Fire HD 8 and HD 10 General] TheRealIntence:
You could be right by the fact that they didn't cleanup BL related stuff. I will take a deeper look into /system/bin... This one might be another approach: Since the BL somehow has to know what kind of OS it's booting into, there might be some signature stuff on the system. Maybe /system/bin will help us here too.
[Fire HD 8 and HD 10 General] DragonFire1024:
I have a hunch about /system/bin. If they modified something as little as the bootanimation bin, then I suspect they made those amzn tools for whatever purpose they serve, and didn't clean up after using them. I'll post a screen shot in a few minutes.
[Fire HD 8 and HD 10 General] DragonFire1024:
Here ya go. I'm a little excited
[Fire HD 8 and HD 10 General] DragonFire1024:
Attached both screen shots. [MENTION=7617234]TheRealIntence[/MENTION]