yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 Questions & Answers] Saswata Chakraborty:
I have been facing lag on PUBG mainly while driving a vehicle. I thought it was happening due to using miui beta (open) rom. But I see even stable users and custom rom users are also facing occasional lags. Infact I was going through reddit and I saw people using Galaxy S10/ OnePlus 6T complaining the same. So I think there must be something wrong with the game only.

---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------

Lol. Changing the server to a different region may end up with high pings and more lags.

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

Everyone thinks the same way buddy. We think other devices run the game without lag. Other device users think our device runs the game without lag. The main problem is, PUBG is still not well optimised for smartphones (atleast for Android).
[Xiaomi Poco F1 Questions & Answers] shuvo030:
Hello sir, since you have tried many ROMs and Kernels, may I ask which rom is the best for heavy gaming? which rom has the best gaming performance?
[Xiaomi Poco F1 Questions & Answers] ttreddy2210:
I think MIUI EU Beta ROM have good gaming performance try this roms which can be the match for your taste
[Xiaomi Poco F1 Questions & Answers] shuvo030:
Did you try Malakas kernel? Just heard it's very good for gaming
[Xiaomi Poco F1 Questions & Answers] ttreddy2210:
No bro which version is best
[Xiaomi Poco F1 Questions & Answers] shuvo030:
Not sure which version, but maybe latest? You can ask "santiagoruel13" on this post: https://xdaforums.com/poco-f1/help/best-version-miui-gaming-t3920449/post79317681#post79317681

He's using it.
[Xiaomi Mi A2 / 6X Accessories] leonardcoutinho:
Mi A2 has usb 3.0 port? Anyone tested usb c 3.0 cable? I not find anything about this.
[Xiaomi Mi A2 / 6X Accessories] maniekkrk:
usb 2.0 type c
[Xiaomi Mi A2 / 6X Accessories] aniruddhdodiya:
Mi A2 has USB 2.0, Type-C 1.0 reversible connector
[Huawei Mate 20 Pro Questions & Answers] Krazuto:
How do you guys charge your phone? Overnight? Until 100 or using charging cycle of 30 80 rule or such? I'm curious
[Huawei Mate 20 Pro Questions & Answers] zolaisugly:
I just plug in at end of day when going to bed regardless of battery and unplug in morning at 100%
[Huawei Mate 20 Pro Questions & Answers] steadly2004:
Same here
[Huawei Mate 20 Pro Questions & Answers] Krazuto:
So basically charging it overnight?
[Huawei Mate 20 Pro Questions & Answers] zolaisugly:
Yes
[Huawei Mate 20 Pro Questions & Answers] Koong1:
Keep my charges between 30% and 90%. But then again, Huawei official service center can reply the battery for around 19SGD. So that is very cheap even if your battery were to deteriorate very fast.
[Huawei Mate 20 Pro Questions & Answers] Hazzay88:
Charge it overnight regardless
[Huawei Mate 20 Pro Questions & Answers] kilometers4:
I charge mine only in the morning while I get ready for the day. It rarely reaches 100 or below 25%
[Huawei Mate 20 Pro Questions & Answers] jhs39:
I keep mine charged between 40% and 80%. Charging your battery overnight hasn't been a recommended practice for at least 5 years. Multiple Pixel owners also found out the hard way that it voided the warranties on their phones when any damage resulted because Google considers the practice abuse of the device.

---------- Post added at 10:37 PM ---------- Previous post was at 10:24 PM ----------

There also is no possible legitimate reason to charge your phone overnight given the various types of quick charging technology used on even many lower end phones. You're just ruining your battery and possibly damaging your phone for no reason other than because that's what people did when the Galaxy 3 was state of the art.
[Huawei Mate 20 Pro Questions & Answers] Koong1:
Well said! I always keep my battery between 90% and 30%. Once a month I will let it drop to single digit percentage and then SLOW charge it up all the way to 95%.
[Huawei Mate 20 Pro Questions & Answers] jhs39:
I'm just shocked this is even still a discussion. I purchased the Nexus 6P when it launched and there were multiple apps in the Play Store to help keep your battery betweer a chosen range back then.

Many people who charged that phone overnight had to replace their battery after a year. After 4 years Better Battery Stats reported my Nexus 6P battery health at 90%.

Since these phones technically have non-replacable batteries making the battery last is basic common sense to me.
[Huawei Mate 20 Pro Questions & Answers] Darkat70:
Not true, Mate 9 I had for 2 years was charged overnight always, I still managed a Sot of 7+ hours after 2 years or easy day n half of normal usage, there was no battery degradation whatsoever.
[Huawei Mate 20 Pro Questions & Answers] themissionimpossible:
I agree, and had the same results with all my phones always slowly charged overnight.

IMHO slowly charging overnight is by far better than any quick charging that heats more the battery and eventually shortens its lifespan.
[Huawei Mate 20 Pro Questions & Answers] kai84m:
I never charge over night and i'm never charging to 100% (at least not intentionally ;)).

I'm also avoiding to use the 40W Charger but the first Gen. Supercharger (5V 4,5A) instead.
[Huawei Mate 20 Pro Questions & Answers] steadly2004:
I've done it with every phone I've had since smart phones stared. And never had issues. Maybe had to replace one when the battery door used to come off. But I had 3-4 to swap in and out back then.

Phones now stop charging at full and don't damage stuff. I also had the pixel XL and 2 XL.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Unbricking

If Recovery OR FireOS are still accessible there are other means of recovery, don't continue.

If your device shows one of the following symptoms:

It doesn't show any life (screen stays dark)

You see the white amazon logo, but cannot access Recovery or FireOS.

If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).

Make sure the device is powered off, by holding the power-button for 20+ seconds

Start bootrom-step.sh

Plug in USB

In all other cases you will have to open the device and partially take it apart.

Follow this guide by [MENTION=3497316]retyre[/MENTION] until (including) step 8..

At Step 6. you will replace

sudo ./bootrom.sh

with

sudo ./bootrom-step.sh

Should the script stall at some point, restart it and replug the USB-cable (Shorting it again should not be necessary unless the script failed at the very beginning).

If the script succeeded, put the device back together.

When you turn it on, it should start in hacked fastboot mode.

You can now use

sudo ./fastboot-step.sh

This will flash TWRP and reset your device to factory defaults, then reboot into TWRP.

Checking USB connection

In lsusb the boot-rom shows up as:

Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone

If it shows up as:

Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader

instead, you are in preloader-mode, try again.

dmesg lists the correct device as:

[ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Changelog

Version 1.1.2 (26.03.2019)

Fix regenerating GPT from temp GPT

Version 1.1.1 (26.03.2019)

Fix unbricking procedure

Version 1.1 (25.03.2019)

Update TWRP-sources to twrp-9.0 branch

TWRP uses kernel compiled from source

Add scripts to use handshake2.py to enter fastboot/recovery

Features.

Uses 5.6.3 LK for full compatibility with newer kernels.

Hacked fastboot mode lets you use all fastboot commands (flash etc).

Boots custom/unsigned kernel-images (no patching needed)

TWRP protects from downgrading PL/TZ/LK

For the devs: sets printk.disable_uart=0 (enables debug-output over UART).

NOTE: Hacked fastboot can be reached via TWRP.

NOTE: Hacked fastboot doesn't remap partition names, so you can easily go back to stock
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Source code:

https://github.com/chaosmaster/amonet/tree/mt8173-suez

https://github.com/chaosmaster/android_device_amazon_suez

https://github.com/chaosmaster/android_kernel_amazon_suez

https://github.com/chaosmaster/android_bootable_recovery
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
First unreserved !!! :D
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You are quick ;)
[Fire HD 8 and HD 10 Original Android Development] Murcielagoz99:
Now we need custom kernels and/or roms, any advice where to start?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Download Lineage OS Sources, create device tree, create kernel tree, create vendor tree and compile ROM.

---------- Post added at 09:04 PM ---------- Previous post was at 08:58 PM ----------

@k4y0z in the ReadMe of the amonet source code says that the exploit is for the fire hd8 2018.

Is it correct or is it an error?

On the other hand, very good work!
[Fire HD 8 and HD 10 Original Android Development] Michajin:
sudo ./step-1.sh

"command not found"

Got the script to run using chmod. But it doesn't reboot,

"PL version 5

LK version 2

TZ Version 263

press enter to continue...

(doesnt reboot)

Dumping GPT

....

Modifying GPT (still hasnt reboot)

What am i am missing?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
BRAVO!! Fantastic work, my friend! I'm looking forward to the customization and ROMs that will soon follow.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Or start with the (minimal) TWRP device tree I linked to.

I just forgot to update the Readme :p fixed it.

What OS are you using?

Is there no other output?

Try running

modules/gpt.py

Does that give any errors?
[Fire HD 8 and HD 10 Original Android Development] Michajin:
i had permission errors on my ubuntu 16.04. IT rebooted into recovery but nothing happened.

Testing root access...

uid=0(root) gid=0(root) context=u:r:init:s0

PL version: 5 (5)

LK version: 2 (2)

TZ version: 263 (263)

Your device will be reset to factory defaults...

Press Enter to Continue...

Dumping GPT

tmp-mksh: dd if=/dev/block/mmcblk0 bs=512 count=34 of=/data/local/tmp/gpt.bin: not found

tmp-mksh: chmod 644 /data/local/tmp/gpt.bin: not found

199 KB/s (17408 bytes in 0.085s)

Flashing temp GPT

246 KB/s (17408 bytes in 0.068s)

tmp-mksh: dd if=/data/local/tmp/gpt.bin.step1.gpt of=/dev/block/mmcblk0 bs=512 count=34: not found

Preparing for Factory Reset

tmp-mksh: mkdir -p /cache/recovery: not found

/system/bin/sh: can't create /cache/recovery/command": Permission denied

/system/bin/sh: can't create /cache/recovery/command": Permission denied

Rebooting into Recovery

Recovery, nothing happens.

I have root.....
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
What are you using for root?

it seems like your "su" doesn't like the commands my script sends, what su are you using?

You could try disabling root/ungrant root access and use mtk-su.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
SuperSU Pro v 2.82
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Interesting, it seems it interprets all the arguments as one command.

I'll see if I can find a workaround to work with SuperSU, but it will take me a moment.

What should work however is if you disable root-access in SuperSU-app.

And place mtk-su into bin-folder.

Then just let it do it's thing using mtk-su.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
It is showing

new UID/GID: 0/0 (over and over)

then UID/GID: 2000/2000 ( occasionally)

Then did not find own task_struct (237)

This normal? It has been about 10 minutes
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Then abort it and try again.

Make sure the screen is unlocked.

Is there no other output?

Did you use arm or arm64 mtk-su?

Also I just tested with SuperSU 2.82 su-binary, and it worked as expected.

I'm not sure why you are getting this issue.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I factory reset, no luck, I tried it on my Raspberry pi3 and it worked. Something with my ubuntu i guess? What version of magisk? i flashed 18.1 and it seems to be looping (or taking a really really long time). Rebooting into recovery is easy though (right volume and power).
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Great you got it to work. Not sure why it didn't in Ubuntu.

Did you end up using mtk-su or SuperSu?

Magisk 18.1 is working fine for me, what FireOS-Version are you on?
[Fire HD 8 and HD 10 Original Android Development] DB126:
Outstanding 'win' presented with clarity and humility. Not to mention timely given the short time you've had the target hardware. A fantastic ROI for those who underwrote the device and for uncounted others who will benefit from your work (along with those of several others noted in your full post) for years to come.

:good:
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Fastboot and recovery are completely different things, and if you use fastboot to flash stock-recovery you'll lose TWRP.

Thats probably not what you want.

Apparently you didn't read the OP properly, as that is exactly what you should do:

Nah, use adb sideload from Amazon Recovery
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Cool, do I need to change the extension or rename the file?
[Fire HD 8 and HD 10 Original Android Development] ffstudios:
I think the wording of this sentence in the OP was a little ambiguous to me at first:

From that line, I misunderstood and thought you meant that I should not flash FireOS images directly in TWRP, which made sense at the time given that you have instructions for going back to stock just above it. Your clarification has helped, thank you. Also, I was not referring to the recovery/unlock as garbage, I was talking about the problems I had caused within the OS lol
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
No need to rename anything.

I have added some clarification to that sentence, I hope this helps.

Going back to stock as described there will remove TWRP.

I wouldn't recommend doing that at all, It's just mentioned there, should someone (for whatever reason) decide to do that.
[Fire HD 8 and HD 10 Original Android Development] DV8:
Use this framework if you are on the HD10 for the extended power menu and on 5.3.6.4
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
What?
[Fire HD 8 and HD 10 Original Android Development] SingleMalt69:
Either way works. I did it by installing TWRP then updating. Apparently updating first then installing TWRP works as well.

Pick your poison.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I tried to start this but Ubuntu didn't install the driver for my WiFi adapter, even though it's listed when I run "lpci" from the terminal, meaning it recognizes it. How do I get the driver installed, if there IS one?

Never mind, I realize this isn't a Linux help thread. I'm gonna try it with VirtualBox instead.
[Fire HD 8 and HD 10 Original Android Development] DV8:
I used this framework on my hd10 for the extended power menu it worked fine for me.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I think you're quoting the wrong person.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I can't get VirtualBox to attach my Fire.

Says it's "busy with a previous request," whatever that means.

Tried this, repeatedly. Even rebooted the host multiple times. Help?
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
After getting both scripts to run successfully without any errors or unusual events, then having my Fire HD 10 recover into TWRP, I thought everything was good. However, I've now spent 2 whole days trying to get Magisk to install correctly without success. During that time I've had to reflash back to stock FireOS 5.3.6.4 and start over four times. Clearly something didn't work right during the unlock and root operations, so I now want to go back to total stock. I really want this all to work, so I'd like to have a clean slate before I start the whole process again.

I want to make sure I understand what you meant in your "Going back to stock" section. First, you wrote "Extract the attached zip-file "amonet-suez-v1.0-return-to-stock.zip" into the same folder where you extracted "amonet-suez-v1.0.zip" ". By that, did you mean to merge both extractions into the same directory or have 2 subdirectories, one for each extraction, under a common directory ? Second, do I run both pieces of code or just the last one ? Last, does it matter if the code is run in a Terminal window in Windows or Linux ?
[Fire HD 8 and HD 10 Original Android Development] DV8:
Yep fat fingered. LOL
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
How do I get VirtualBox to connect my Fire HD? This is extremely annoying.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I kept trying to figure that out too. I finally just said to heck with it and use Linux now. Best switch I ever made.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I can't because most of my games wouldn't work then. lol

Also my WiFi adapter just doesn't work. It won't install a driver for it, apparently. And the manufacturer's website doesn't have a Linux version of the driver.
[Fire HD 8 and HD 10 Original Android Development] nujak:
This seems to be a common issue. Try this:

1.	Create a USB filter in your guest settings while the device is plugged in the host. Delete all values except VendorID and ProductID.

2.	Unplug the device.

3.	Start your guest.

4.	Plug your device. The filter should capture it and pass control to your guest.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Create a bootable Ubuntu USB, that's what I did. It is very easy and works right away. Than you have an Ubuntu installation ready and always at hand.

https://www.howtogeek.com/howto/14912/create-a-persistent-bootable-ubuntu-usb-flash-drive/
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I'll try that as soon as I get back home from work!

Yup, I do that with Rufus, which now has the ability to directly download official images of Windows 10 and 8.1 as of v3.5. I use it with all kinds of bootable images, Windows, Linux, WinPE, and so on. Although this method you've linked seems to have a dynamic partition designed for expanded storage. Sounds like that just might be what I need! .... If if actually installs my WiFi drivers, that is.
[Fire HD 8 and HD 10 Original Android Development] frankieuk:
I cannot thank you enough for this!, well done!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Depending on your hard drive space, you can use the bottable USB to shrink drive C: and create a partitiona for Ubuntu and dual boot. If you use anything lower than I think Ubuntu 16 (someone else can verify this) you will run into an issue with grub aka the boot menu. On Ubuntu 14, it doesn't properly create the boot menu to include Windows.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Just tried this multiple times. No dice. Still giving me that "previous request" error.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Excellent guidance. Doesn't need to be Ubuntu if you prefer another flavor. Using anything Linux based eliminates most connectivity issues.

BTW - I'm not a Linux snob. My life is built around Windows with no regrets. That said, sometimes a different tool is needed to get the job done most efficiently.
[Fire HD 8 and HD 10 Original Android Development] Newt182:
Go on Amazon live chat and say 'hi, would you mind removing the adverts from my tablet please?'. It's as simple as that
[Fire HD 8 and HD 10 Original Android Development] Michajin:
ADB shell

su

pm disable com.amazon.kindle.kso
[Fire HD 8 and HD 10 Original Android Development] DB126:
Yep. One's local, the other upstream. Both are equally effective. I opted for the latter on an unrooted 2018 HD 8 (slightly different command syntax) and now enjoy an ad-free lockscreen with the wallpaper of my choosing.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Let me be clear, if TWRP is working, there is no good reason to go back to stock using these scripts, as that won't magically fix anything that "clearly didn't work right during the unlock". It's also an unnecessary risk, since it will modify the GPT again.

If you have any issues that can all be fixed using TWRP.

What issues are you having?

You can do the following:

Do a factory reset

Wipe System

Install the 5.6.3.0 update-bin using TWRP

Install Magisk and MagiskManager APK

To answer your questions:

You need to merge both zip-files.

You can run either of the two commands.

The first one will only flash stock recovery but won't restore the GPT.

The second one will also restore the GPT.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I was finally able to run the scripts and flash Magisk, but for some reason I didn't see it in my app drawer. So I sideloaded it (adb sideload MagiskManager-v7.1.1) and sure enough, Magisk is installed, and I was able to test it by running the command from three posts above to disable the ads, and indeed, it asked for root perms. Command was successful as well. Though I didn't see ads on my lockscreen before this to begin with, though then again, I still haven't connected to the net yet.

Now, the question is, what is the best way to go about blocking system updates and getting Google Play Store and such on here, without destroying what Amazon has already installed? I don't want to remove anything this time around, just push it aside, if that makes sense. I want to use Default App Manager (https://play.google.com/store/apps/details?id=app.defaultappmanager.pro) to set my apps to the Google variants. Because as Davey and others have stated, it's not entirely stable to remove a lot of the Amazon bloat to begin with. Is this feasible?
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Here is a link of files that i used to disable anything i didn't want and block updates, etc....

I don't remember who created this list but i have found is useful and still work. It also gives risks of the disable, i use disable so i can re-enable it i have issues,

https://docs.google.com/spreadsheets/d/1GLb_1xIWz1uGVEJEikwEaqRF0rhMVQI5vlMQcUm6m8U/edit?usp=sharing

These are the ones i used for ads and OTA disabling.

pm disable com.amazon.kindle.kso

pm disable com.amazon.kindle.otter.oobe.forced.ota

pm disable com.amazon.settings.systemupdates

pm disable com.amazon.device.software.ota

As for google play - this is the guide that worked for me, 4 apps, easy

https://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
This was what eventually worked in the end. I still couldn't get WiFi working, but I DID get an internet connection tethered from my phone via USB/Bluetooth and was able to install the dependencies needed to run the scripts as well as the binaries and scripts themselves. So thank you for this tip.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
That worked for me! I just downloaded them on my PC, shortnamed them, and installed via adb, shut off, and powered back on. Was able to sign into Play Store after it updated, and now I'm downloading apps! Thanks!