yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] koberulz:
My phone charges obnoxiously slowly...sometimes. I'll plug it in at 77%, it'll tell me it's charging and will be full in 17 hours. Unplug it, plug it right back in, full in two hours. Even the fastest speed I can manage by constantly plugging and unplugging is pretty slow. The slowest speed is slow enough that the battery discharges faster than it charges, even with the screen off.

The fact that unplugging it and plugging it back in alters the charge time so dramatically points to it being an issue with the USB-C port, or possibly the USB-C cable. Except...my wireless charger is even worse. I cannot manage a net-positive charging speed when charging wirelessly.

On the other hand, if I plug my phone into an outlet offered on a train, using the same cable I use at home to plug it into the wall (minus the AC adapter bit), it charges incredibly quickly. It estimated 35 minutes to full charge from 64% this afternoon. I can't charge from 80% at home in less than an hour.

It would seem to me that:

- The problem occurring with the wireless charger as well as the cable eliminates the cable, the power adapter, and the USB-C port on the phone as a cause

- The problem not occurring on the train, and charge time changing so dramatically by plugging and unplugging, eliminates the battery as a cause

Having thus eliminated every possible cause save for the power outlets in my house, which are presumably just as capable of dispensing power as power outlets anywhere else, I'm very confused. Especially since this issue just started occurring in the last few weeks, on a phone I've had for years (and in which I replaced the battery a year or two ago).

It also seems to drain obscenely quickly when I'm out and about, but drains much slower at home. Might be a WiFi or Bluetooth issue, or maybe the ability to just throw it on a charger at home means I don't notice it as much when it runs down quickly. But if it is dropping in capacity - which it shouldn't, the battery itself is fairly new - then you'd expect charge times to also decrease significantly, as it has to supply less power to the battery to reach a full charge (and indeed when I replaced the battery, it was because I could charge it from 20% to full in like half an hour).

It's a Pixel, not sure off the top of my head what model it is, and it's in the other room right now because it's running low and I can't put it on the wireless charger in this room because that doesn't charge it.
[Android Q&A, Help & Troubleshooting] blackhawk:
Possible battery failure. 2-3 years is the normal lifespan for a heavily used device.

Erratic fast charging is a symptom of an Li failure. Do not charge with the display on.

Charging Li's below 72F can cause Li plating and premature failures. Once an Li reaches 80% of its original capacity it is degraded, has reached the end of its service life and should be replaced. Degraded Li's are more likely to fail and can fail in a variety of ways. Any battery swelling is a failure, replace asap and do not attempt to charge!

You may have multiple issues; not properly optimized, corrupt user partition (factory reset), corrupted firmware (reflash) or a failed mobo or C port daughter board if it has one.
[Android Q&A, Help & Troubleshooting] koberulz:
The battery was replaced 18 months ago.
[Android Q&A, Help & Troubleshooting] blackhawk:
They can fail at any time. Extreme operating conditions can cause failures. My first Note 10+ lasted about... 18 months.

Not saying it is the battery but it's a prime suspect. Heat and high cell voltage are the Li's biggest degradation factors.
[Windows 10, 8, 7, XP etc.] Samarimama:
It is possible to show milliseconds in Windows 10 taskbar? I don't care of accuracy. Just milliseconds on the taskbar.
[Windows 10, 8, 7, XP etc.] Renate:
Windows already warns you not to have seconds on the taskbar.
[Windows 10, 8, 7, XP etc.] Samarimama:
why
[Windows 10, 8, 7, XP etc.] Renate:
Because having to do something once a second, even when no one is looking is apparently a performance hit to poor little Windows.
[Windows 10, 8, 7, XP etc.] Samarimama:
Yeah but I have a problem with the screen: It shakes and flickers. Everytime something move, it stop. So now you know why I need milliseconds, seconds are not enough.
[Windows 10, 8, 7, XP etc.] Renate:
Well, milliseconds won't help you.

Just try some simple animation and see if it stutters.
[Windows 10, 8, 7, XP etc.] Samarimama:
Which animation you mean?
[Windows 10, 8, 7, XP etc.] Samarimama:
Any idea?
[Windows 10, 8, 7, XP etc.] kio0014:
Probably yes. I never tryed though

There is a video on YouTube showing how to add seconds on the taskbar, if you understand whats happening in the video i believe you will also be able to add milliseconds too in the same way

Hee is the video

Hopefully it will help you to fix your screen problem
[Samsung Galaxy Watch 6] disiadands:
Hi.

Could you please share the firmware for SM-R950? Best would be XSG (United Arab Emirates), but any with Google and Samsung Pay works.
[Samsung Galaxy Watch 6] Aethera:
Why do you need the firmware?
[Samsung Galaxy Watch 6] disiadands:
My watch is from Turkey (no Samsung Pay, no Google Pay). I actually just need to change CSC from Turkish to UAE or any supporting these services. The dial method doesn't work for me (just forwarding the call to the phone). So I suppose the only other way is to change firmware, isn't it?
[Samsung Galaxy Watch 6] disiadands:
Ok, it looks like I really don't need this firmware. Turned out that my watch is MultiRegional with OXM csc code (call *#1234# from the watch to check yours). Watches with OXM take any region from initial setup (or after factory reset) from your phone. I made factory reset and now Samsung and Google Pay services work fine.
[Samsung Galaxy Watch 6] Aethera:
That's great news!
[Samsung Galaxy Watch 6] yacoub9:
hello, please, did you get the firmware for R950 ? I am seriously in need. Please
[Samsung Galaxy F62 / M62] Vishnuisgod:
Hello Gentlemen,

I'm travelling this summer to Europe. I'm trying to determine if my M62 has Esim capability?

I'm reading conflicting items that say, yes it does, and or that it's too old.

Any help clarifying would be very welcome.

TIA

Zee
[OnePlus 9 Pro] Duvel999:
Hi,

I upgraded to latest Android 14 on my 9 pro phone.

(Rooted & Unlocked)

But I can only choose Roboto font, nothing else!

Strange or not?

Today I changed to language to English, it gave me more (3) options.

Changed the language, just 1 option.

Any idea?
[OnePlus 9 Pro] DeanR97:
it could be possible, that you selected language contain characters, which are not available in these fonts
[OnePlus 9 Pro] Duvel999:
What do you mean?

Is there a good & simple solution to add / use custom fonts?
[OnePlus 9 Pro] TheGhost1951:
Try this!
[OnePlus 9 Pro] Duvel999:
What do you mean?
[OnePlus 9 Pro] TheGhost1951:
You can use the Theme Store App to change fonts.
[OnePlus 9 Pro] Duvel999:
On OnePlus?
[OnePlus 9 Pro] Duvel999:
It works😉
[OnePlus 9 Pro] LTFOUND:
I'm using this module (for Magisk) by D4rK to enable Product Sans font:

https://github.com/D4rK7355608/GoogleProductSansFont

I know the repository is archived, it still works great though and it looks clean :)
[OnePlus 9 Pro] TheGhost1951:
install the Theme Store App and you will have all the fonts to change to through the wallpapers and themes and settings. select the more button!
[OnePlus 9 Pro] jammin6996:
Here is version 9.8.0. The most recent version I could find that still works and is in English.
[Google Pixel 7] shikotaro:
Hello, I am having issues with my gyroscope, acceleration, proximity, and compass sensors.

In a sensor test app, the gyroscope and acceleration sensor are not delivering any data at all, proximity and compass are recognized, but are not delivering any data (displaying always the same value).

I also used to have problems with the fingerprint sensor but was able to solve this using https://www.ifixit.com/Answers/View...+new+screen,+how+to+troubleshoot#answer769794

Now I tried flashing the Android 15 developer preview, Android 13.0.0, the latest official public build and the Android 13 Beta 3.2, none of them made a difference. Does anybody have any advanced ideas how I could troubleshoot and fix these sensors?

I bought it second hand and the guy claims he didn't know about these issues. It doesn't look like the cover had been removed, and the device meddled with...
[Google Pixel Watch 2] zyguo:
Not working after change /vendor/usr/keylayout/petc.kl with Magisk-KeyboardRemaps

Also tried /system/usr/keylayout/Generic.kl

Don't know what to do.
[Google Pixel Watch 2] zyguo:
After additional edit in gpio-keys.kl qpnp_pon.kl and qwerty.kl seems worked
[Android Q&A, Help & Troubleshooting] BotchedRPR:
Hello everyone

First of all - if i'd post this in Android general questions/discussion it would get lost in the depths of the general subject. And 9 Pro users are here (with their own threads) so why not.

As you've probably heard - Nubia went the ASUS way and fully locked the bootloader.

Here's what I know (owning this device and struggling with it since January):

No, no janky edl hacks will work. I tried. 9 Pro does NOT boot with 8 Pro abl.

No, you cannot unlock by writing to devinfo

No, you cannot patch abl.

No, we cannot bypass secureboot. Firehose has peekpoke disabled.

Seems like the only way is a zerofuse, or a leak from nubia. (or we beg them enough on their support email)

However - discuss! Maybe we will find something out together :)
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
Loosely based on this, I've just added some info about QSEE.

I believe this is how abl actually implements unlocking: https://git.codelinaro.org/clo/la/a...omModulePkg/Library/BootLib/DeviceInfo.c#L230

It appears to be using QCOM_VERIFIEDBOOT_PROTOCOL to write device info (is it doing something other than writing to devinfo partition though? Probably yes). It appears to be implemented in XBL.

There's a leaked code, so let's look at the implementation: https://github.com/David112x/qcom-e...rivers/VerifiedBootDxe/VerifiedBootDxe.c#L201

Apparently, unlocking the bootloader requires sending some specific commands to QSEE.

Here's the example on how to use it from Android: https://github.com/nccgroup/cachegrab/blob/master/server/jni/shim/shim.c#L130

Can we just send these commands? It can't be that simple, something will probably go wrong.

BTW, do you actually have firehose for 9 Pro? If so, can you get at least temporary root access?
[Android Q&A, Help & Troubleshooting] Andrologic:
I'm onboard with trying anything possible but don't have my hands on this device yet. I was going to, but since they pulled the ASUCKS trick on us, I refuse to buy directly from them.

To begin with, does anyone have the working firehose files for the 9/9 Pro?
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
@BotchedRPR and I have tried temporary root ideas, nothing booted. I have not tried any exploits while the OS is running (Not sure any publicly exists for SM8650 and A14 atm). Everything I have tried (Other SM8650s ABLs, XBLs, patched boot/boot_init) was thru bkerler using the provided firehose for NX769 by someone here on the forums.

The firehose that few have does not work with QFIL but does work with bkerler. Again, it was provided to me by someone here on the forums but asked it not be shared. I know that hinders development but it also stops people from bricking their devices without proper instructions being put together or a proper EDL package for each locale. I feel like that was one of the initial reasons they went back to locking the bootloader from all the RMA's (Side note: I also feel like that's Nubia's own fault for not providing a proper fastboot unbrick zip like Razer did with the Razer Phone 1 & 2, only using them as an example since I had both devices and used those to restock/recover, but I'm sure other manufacturers did as well).
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
I wouldn't bet on it, but sending those QSEE commands is at least worth trying.

It will be quickly patched even if there was one.
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
Unless I am misreading this or misunderstanding it, Cachegrabs method requires CONFIG_MODULES and CONFIG_MODULE_UNLOAD (I don't mess with Kernels so not sure if those are on any of the stock Kernels) or a rebuilt Kernel with those enabled and flashed? Thus if the OEM Kernels don't have these enabled we can't move forward and flashing any built Kernel results in device not trusted/corrupted with a boot to EDL mode following the corrupted message.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
Cachegrab is only an example of how to run QSEE commands, there is no need to run any modules (which isn't possible without root anyway). One'll have to write a program doing the same what XBL does (sending the same QSEE commands) with a hope that it'll unlock the bootloader.

If it's a message from AVB then we might try to build custom vbmeta image and flash it in EDL. Can it flash vbmeta and avb_custom_key (which appears to be in devinfo) though?
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
Like @BotchedRPR stated, peek/poke commands were disabled. This is above my knowledge at this point anyways so not sure if these commands (The QSEE ones, not standard edl commands) could be sent while the OS is booted.

I know I flashed (If memory serves) the vbmeta from OP12 when I was trying different combinations. I never touched devinfo knowing the issues that could occur if that failed to flash back the backup.

EDIT: I am at work and also trying to read up on CVE-2021-1961. The Qualcomm TrustZone (QSEE) is something I'm not at all familiar with in exploiting so learning as much as I can for ideas.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
They should be, this is literally what /vendor/lib64/libQSEEComAPI.so used for. However, I'm not sure whether it'll work without root (or even will be available for dlopen).

This is not what I'm suggesting. Here's the documentation for AVB: https://android.googlesource.com/platform/external/avb/+/main/README.md

Note that vbmeta partition actually contains hashes of other partitions and is cryptographically signed on top of that. It's signed by the zte key, but there's such thing as the custom AVB key, which might be possible to exploit here. Basically, what we need to do is to create a new vbmeta partition (with different hashes for i.e. boot.img or Magisk-patched init_boot.img), sign it with our own custom key and flash it via EDL. This key needs to be also flashed, and it appears to be in devinfo partition (unlike locked/unlocked state, which is only there for non-secureboot devices). So this partition needs to be dumped, altered with a custom key and flashed back.

Theoretically, this should get rid of that "corrupted message".
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
I flashed the ABL, XBL, and vbmeta from the OP12 in hopes I could boot to at least a fastboot with flashing commands (tried with a few other SM8650s as well), that was the reasoning behind that.

If you need and want to attempt doing this (vbmeta with the new key) and I'll flash them and see how it goes we can try. I got a spare device to fall on. If so, Ill send the stock vbmeta and a patched boot and boot_init so you can do your thing.

Also fun fact: I have all stock partitions again after all the attempts, and still have the "corrupted message" but it will let me boot to device. I didn't wipe after restoring the stock partitions though so I am assuming it tripped a persistent flag somewhere when I attempted booting with other manufacturer images.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
These images wouldn't work due to secure boot (even with unlocked bootloader), but the "corrupted message" is from AVB. I don't think we can do anything about secure boot without some 0-day vulnerabilities, but AVB exploiting might work.

I've attached a recovery image. It's was initially built for 8 Pro, but still worth trying.

Can you also send other stock images? You surely already have a backup, aren't you? They will help building custom recovery specifically for 9 Pro and performing some sanity checks.

Another fun fact: I had the same message quite some time ago and was able to fix it by running

reboot "dm-verity enforcing"

in Termux.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
I do. You can't gain temp root. Nice job finding OSEE commands. I couldn't :)

No, this device has disabled avb_custom_key. As usual.

Can we send the commands? YES, most likely. With a temporary root, that is.

What would that recovery image achieve? I tried to change a string in recovery - device is corrupted.

It works with QFIL for me.

Ah yes - my favorite exploit.

As for an exploit built in 2021, it does not crash our device.

That's about it for me. I can't test anything because my device is at warranty right now
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
"Its better to try knowing it shouldn't boot, then to not try without knowing whether it could have worked"

Sure, I'll try knowing it won't boot. I've also already built TWRP for the 9, but can't test it till unlock of the bootloader.

They have been dumped for sometime as well. If something is missing (Exception being partitions like modemst1/2, persist, etc.. for single device reasons) let me know, I'll send it. FYI I'm US Global variant.

I don't reboot often since no root and updating of modules for Lsposed/Magisk or flashing GSI updates, so I don't see it enough to be bothered.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
For this

might actually work.

UPD: it will not.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
I don't think abl will use anything from devinfo unless insecure.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
Yep, but I need the exact partitions you currently have flashed. Hashes need to match exactly for this to work, so I'll need to make sure they do.

UPD: this approach will not work, it's still necessary to run those QSEE commands. And at that point it's easier to unlock with them directly.
[Android Q&A, Help & Troubleshooting] DarkestSpawn:
I can't remember the error, but when trying to read partitions it threw an error. Didn't you say you got the same error?
[Android Q&A, Help & Troubleshooting] BotchedRPR:
I only had an error while flashing sparse images.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
Are you sure? https://git.codelinaro.org/clo/la/a...omModulePkg/Library/BootLib/DeviceInfo.c#L404

UPD: Oh, I think you're right. It still uses that ReadWriteDeviceInfo function.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
The abl release from codelinaro is dedicated to embedded (automotive, blah blah blah).

Usually on phones devinfo is only read when secureboot is off
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
It's actually for SM8550, but you're right.

So it all comes down to the ability to send those QSEE commands without root.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
Looking through that code - we'd not only need root, but also SELinux permissive.

:(
[Android Q&A, Help & Troubleshooting] RexSonic:
Damn
[Android Q&A, Help & Troubleshooting] ohaiibuzzle:
I wonder if Nubia locking its bootloader with no way to unlock also has something to do with that 2022 Chinese regulation on "Preset behavior of mobile software" where it does mention "take technical and management measures to prevent the replacement of operating systems and the installation of application software during product circulation" (Google Translated)

Regardless, really sucks that you can't easily unlock this thing anymore.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
Hi my phone is back from warranty:

- Service center flashed EEA firmware, really don't want to lose it for now so I won't be able to research FTM. Chinese 9pro owners reach out.

- No, they didn't leave in engineering rom (unfortunately) xD

Anyone think of anything new? FTM mode seems to be locked - PuTTY connected to port doesn't pick anything up.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
I sold my phone.

No new updates from me, ever for this device.

Good luck.
[Android Q&A, Help & Troubleshooting] aaa.bbb111222:
There seems to be a potential exploit for kernel 6.1.25: https://github.com/lrh2000/StackRot

It's only for x86 though, so it will require some adaptation for aarch64.
[Android Q&A, Help & Troubleshooting] mvikrant97:
So it seems like Unlock Tool has finally release Firehose for ZTE Nubia 9 Series devices.

I have the license to use Unlock Tool. If anyone interested to test EDL firmware backup and other things

for the community, I'm ready to test it.

I don't have the device but I can help with Unlock tool to backup the firmware using EDL mode.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
UnlockTool already worked beforehand for me.

Idk what they did now.
[Android Q&A, Help & Troubleshooting] mvikrant97:
Which other Nubia device has same Chipset?
[Android Q&A, Help & Troubleshooting] BotchedRPR:
z60 ultra
[Android Q&A, Help & Troubleshooting] mvikrant97:
So then Unlock Tool may already have a Firehose for this device which will work for Nubia 9 series devices as well.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
nope. the firehoses between redmagic 9 and z60 ultra use different signing keys, we tried the redmagic 9 pro firehose with z60 ultra (courtesy of @Dadovvv) and it didn't handshake

EDIT:

ah, does "add support" mean "add firehose"?

if so, then yeah i understand but i had a custom firehose to use
[Android Q&A, Help & Troubleshooting] mvikrant97:
yes I mean Unlock tool has added the firehose on their server which can be directly used within the tool now.
[Android Q&A, Help & Troubleshooting] Guybrush.d:
Hi, everybody i'm considering to buy this phone, and it's long time i don't install a custom rom, LineageOS "survived" long time on my LG G5. I read about unlock tool but i'm new to this software can you explain me what is a firehose and if with unlocktool is now possible to unlock the bootloader and install twrp? I don't what to spend so much money if i cannot take control of my smartphone, else i will by an S23Ultra and free the phone from bloatware, thanks!
[Android Q&A, Help & Troubleshooting] borygo77:
Don't expect custom roms for it even if someone will release tools to open bootloader...

I would go s23U if money doesn't matter...
[Android Q&A, Help & Troubleshooting] BotchedRPR:
No it's not

Buy a S23 ultra.
[Android Q&A, Help & Troubleshooting] BotchedRPR:
And dont expect anyone to release tools to unlock.

I made a promise of making lineage for this device if the bootloader would be unlocked

... yeah, right

P.S. Nice profile picture
[Android Q&A, Help & Troubleshooting] borygo77:
You should make one for rm8pro ;) I'll be really glad to see it one day!

I'm really big fan of this guy on my profile pic :D
[Android Q&A, Help & Troubleshooting] BotchedRPR:
I don't have 8 pro.

Kaczor? Haha
[Android Q&A, Help & Troubleshooting] borygo77:
Prezesunio :P
[Android Q&A, Help & Troubleshooting] Guybrush.d:
Thanks Guys, i wanted to start to learn how to cook a rom with this device, i think it has awesome specs, it just lacks about software, i was thinking also to buy a Z60 but i think it's the same situation, anyway every time i need a new phone and i found an interesting nubia one, i face against the software lacks, i think i'll move on this time too...Just last question, anybody knows if could be possible, at least, to root it to remove google apps? Thanks!
[Android Q&A, Help & Troubleshooting] BotchedRPR:
Nope, no bootloader unlock -> no root.
[Android Q&A, Help & Troubleshooting] ErdilS:
Redmagic 9 Pro / Plus firehose file if needed.

Tested.
[Android Q&A, Help & Troubleshooting] Dadovvv:
In changelog description says | Flash |

Can u tell me what exactly can flash ? Does UnlockTool provide full edl rom or u need to have rom to be able to use flash?
[Android Q&A, Help & Troubleshooting] mvikrant97:
You need to have ROM.

Also you can backup your device current firmware. Full dump,
[Android Q&A, Help & Troubleshooting] Dadovvv:
And when dump is created can u flash back?