yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] blackhawk:
What is the battery voltage? This will tell you it's actual charge state.

Try discharging until it auto shutdowns then fully charge it; recalibrate the dumb Android. Maybe someone knows a better way to recalibrate this?

Hard resets rarely solve this kind of problem; you need to find the root cause and correct it otherwise even if the hard reset works it will most likely only pop up again down the road.

A hard reboot be the most I would try. Even needing to do that indicates a apk or potential hardware issue. A good running Android never needs this.
[General Questions and Answers] abt12:
Accubattery claims 4.227V at 69% charge, but lord knows how accurate that is. (Edit: I'm now up to 72% charge and it's claiming the same... So, yeah. Oh, and that +3% is without charging.)

Root cause is almost certainly some variable overwritten or system file corrupted during the Android system update, since it happened immediately after the update.
[General Questions and Answers] Deleted member 9635294:
So flashing a custom rom should work?
[General Questions and Answers] blackhawk:
Umm

I think 4.2 volts is near a 100% charge.

4.127 is about 75% on my 10+

Can't recall as I rarely go that high.
[General Questions and Answers] abt12:
Think that's my next step. Just tried running it all the way down to see if that would recalibrate it, no such luck. Died at 79%, now I'm charged "up" to 56%

¯\_(ツ)_/¯
[General Questions and Answers] blackhawk:
At what voltage did it die?
[General Questions and Answers] Deleted member 1890170:
Yes, this issue got several times reported in different forums.
[General Questions and Answers] blackhawk:
Was it a reporting error only or did it jinx the charging parameters too?
[General Questions and Answers] Deleted member 1890170:
The 1st
[General Questions and Answers] abt12:
Any idea if reflashing the factory ROM fixed it in those cases? Don't want to waste the time if not.
[General Questions and Answers] blackhawk:
If the firmware doesn't have the same error... either that or go into the existing one and correct the mistake.

This is one of the reasons I'm not rooted. Too many loose ends... and very time consuming.

Maybe someone here has can help you in detail, good luck.

If jwoegerbauer is correct this only effects the battery % reported, not charging parameters or actual battery capacity. So it shouldn't harm the battery.

The charge level can be calculated by battery voltage which appears to accurate. I saw a chart for this but can't find it now.
[General Questions and Answers] abt12:
Sad thing is I'm not even rooted. This is a completely stock phone. Since it's out of warranty google DGAF.
[General Questions and Answers] blackhawk:
My bad, sorry. You stated that.

It seems the update got corrupted or was badly coded.

I'm always afraid this will happen with auto updates as you have no control over the process or download.

You need to get it reflashed to the last working version for that phone. Or live with it as is.
[Touch Diamond, MDA Compact IV General] fyew-jit-tiv:
Hello all..... There is a rumour that t-mobile will be releasing an update Rom for the mda iv.... "Absolute rubbish" and even if they did it would probably be as bad as the current stock Rom...

For all those that are using the stock Rom.... Sort it out.. How dear you insult the diamond with this Rom. Thanks to the chief's here at XDA we can now benefit from this bad ass mobile...

I read a post buy someone (can't remember who) and they quoted that the chief's here at XDA have made the Diamond "A MANS BEST FRIEND" how true this statement is...!

On a serious note... If you want to see your Diamond sparkle then you have to polish it, and this can only be done by the guys here at xda...!

To Panosha, dutty, bepe and all the other chiefs that are keeping the diamond real...! I thank you sooooooo much...!
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
FEATURES AND ISSUES

- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
Will it work on the dual SIM version XQ-AU52?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Of course.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] flyl0:
i wish we can have it for our xperia 5ii lol
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] dreDREb13:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Flash directly, if you don't meet any issue, there is no need to wipe the data.

Coming.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] flyl0:
It would be even better Resurrection Remix 😍

But I'm glad LOS 18.1 is coming, can't wait to try it!
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] dreDREb13:
Sweet. This is great work, thanks so much!

Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
erasing 'metadata'...

FAILED (remote: Erasing is not allowed for partition)

...

sending sparse 'system' 1/2

OKAY [ 21.700s]

writing 'system' 1/2...

FAILED (remote: No such partition.)

I have that every time. What to do in fastbootd mode?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.

You should be in fastboot mode and not fastbootd mode,

If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KriiXOne:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
You should be in fastboot mode and not fastbootd mode,

If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Now it looks like this and I don't know whether to continue doing something?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A

LineageOS or stock Recovery?

If LineageOS Rec is broken, try stock rec plz.

BTW, also use latest adb fastboot tools from google.

FastbootD driver is also necessary.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] berkenpies:
Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
The problem is with stock recovery.

I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Run

fastboot getvar all

Post the result here plz.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
Is that the point?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] dreDREb13:
So I installed and everything booted up fine, but I hit a couple snags.

One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.

Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.

Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.

EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...

All looks good otherwise and this is turning out great!
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Yeah, you have to copy it into the firmware folder and run it from there.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Well, that would flash the stock ROM, right? And wipe out my data, right?

Can I flash only those vbmeta*? If i update this update.xml file and put there only those?

UPDATE: this doesn't work
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
It would not erase the data, it asks you if you want to but you don't have to. So you can then flash lineageOS again and everything should be in place.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
It doesn't seem to flash anything. I tried to run ./newflasher from the folder with the firmware:

❯ sudo ./newflasher
--------------------------------------------------------
newflasher v55 by Munjeni @ 2017/2020
--------------------------------------------------------

Determining available free space:

Available space to caller = 222484 MB
Total space on current drive = 479363 MB
Free space on drive = 246906 MB
found device with vid:0x0fce pid:0xb00b.

Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
y

Reboot mode at the end of flashing:
type 'a' for reboot to android, type 'f' for reboot to fastboot, type 's' for reboot to same mode, type 'p' for poweroff, and press ENTER.
f

Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that! But it is recommend to have dump in case hard brick!
y
Dumping trimarea partition 1.
Created ouput folder tadump.
./tadump/tadump_1.ta created.
Dumping trimarea partition 2.
Dumping trim area to tadump folder.
./tadump/tadump_2.ta created.
Sent command: reboot-bootloader.

Done.
Closing device.

After this it still boots into this "Your device is corrupted..."
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Yes, that is because you dumped the trim area, next time say no and it will work. (The trim area needs to be dumped at reboot).
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Nice :) It flashed vbmeta* (not the whole stock rom). I can now boot into the recovery by lineageos (the one in violet color and with LOS logo) .

Before I flash the stock and then LOS ROM, how can I have root access? The reason i flashed Magisk is to fix a bug in a prog (Syncthing). Or I should flash Magisk after those? How to avoid getting the same issue I just fixed?

Thanks!
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
If it boots up right now, you don't have to flash the stock firmware. As for root, you have 2 options: Use the updated TWRP or extract the lineageOS zip file, copy the boot.img, patch it with magisk, copy it to the PC and flash it.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
No, it doesn't boot into OS. It boots only to the recovery. I mean if I press power button it tries to load OS but fails and reboots into the recovery where there is "Can't load Android system. Your data may be corrupt. If you continue.. factory reset.." etc. Now I see these options

1. Build this TWRP, https://github.com/blackshibe/twrp_sony_pdx201. And flush it.

2. Remove Magisk as per https://topjohnwu.github.io/Magisk/faq.html. I see I can Enable ADB in Recovery. So I guess I can disable Magisk, then boot into OS, then patch boot.img, copy to PC, and flush it. UPDATE: it doesn't work: `/system/bin/sh: magisk: inaccessible or not found`

It looks that my initial mistake was that I flashed this Magisk without patching it first from inside Magisk Manager in Android.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Ok, then try to build the TWRP and see if it works.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Yeah, i now can't build it. What's `lunch` and `mka` there at 'Compilation' section at https://github.com/blackshibe/twrp_sony_pdx201. Thanks
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Lunch=Selects the device you want to build it for

Mka=make but uses all cores by default
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
And it won't build some merge conflicts for

❯ LANG=en git fetch https://gerrit.twrp.me/android_system_vold refs/changes/40/5540/13 && git cherry-pick FETCH_HEAD

# Won't succeed as merge conflicts.

> git status

...

(use "git add <file>..." to mark resolution)
both modified: FsCrypt.cpp
both modified: KeyStorage.cpp
both modified: Keymaster.cpp
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
OK, I will try to build it (I can't right now because fedora decided that anything to do with android builds uses way too much ram and kills it, so I will be installing arch).
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Hey, not sure what to do if this won't merge. Those conflicts are unclear to me how to resolve so I can't build locally. Files are in bootable/recovery/Android.mk and partition.cpp.

So I renamed magisk**.apk into uninstall.zip and flashed it. It then appeared this message "Your device is corrupt .. won't boot.." etc. I again tried to flash vbmeta*.sin only files (via ./newflasher). It didn't work, newflasher reported those files skipped. So I run newflasher for the whole stock os thus removing my LOS installation. Now I can boot into the stock OS.

With my data present. And apps installed. That's good
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Ok, well I am now trying to build lineageOS 19.1, and if it builds, you could use the recovery from it.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Do you say that if I install Magisk as per this guide https://topjohnwu.github.io/Magisk/install.html#getting-started I will have bootloop again? And I need this TWRP?

Now I have this stock ROM. No recovery. So I guess I flash this old recovery as here in this thread top post from Sjll. Then sideload their ROM. Then do Magisk as per the installation at the link above. And I guess I will have root, LOS and my data. Right?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KingProNoob2:
Yes, but you have to flash the rom, then reboot to recovery and then flash magisk, if you reboot to the system after flashing lineageOS, you will not be able to install magisk.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Hm, so full steps:

1. Have this boot.img from the stock firmware (it is ./boot_X-FLASH-ALL-E9C8.sin)

2. Boot into the stock ROM as I have now. Open Magisk (as I installed it before when I had LOS). There choose Install. Then Recovery Mode. Select the boot.img. Start the installation. Copy the file into my PC.

3. Flash recovery and rom as per this thread top post. Don't boot.

4. Then flash magisk: fastboot flash recovery /path/to/magisk_patched.img

5. Then boot into lineageos
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
Argh :( I did the above. Got the same issue: now can boot only into the recovery. The system won't load. In recovery it is "Can't load Android system. You data may be corrupt..." etc. What now? Again flash the stock rom. Then recovery. Then LineageOS. Not sure. I guess it is that LineageOS or Magisk doesn't work with other one.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
:( That's it. I don't know what to do. Looks like I can only wipe out data and reinstall. I tried flashing stock rom without removing data, flashing lineageos, flashing magisk, flashing twrp, flashing vbmeta* in different orders. I can't boot into the stock rom as I could before. I can't boot LOS: "your device is corrupt.." message. I can't build this updated twrp from "blackshibe/twrp_sony_pdx201". The best I can do now is to boot into twrp, then I can run `twrp decrypt ****` but my password doesn't work, it won't decrypt (yes, i tried other passwords I can think of). I guess this is another lesson for me not to flash something from internet without thinking twice (at the beginning i flashed this magisk apk renamed to zip into recovery without patching it as they say).
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] laakssim:
"Make sure you upgraded to Official Android 11.0 from Sony"

Does this mean it is not possible to use this ROM if I already have official Android 12 from Sony? I have understood it is not possible to downgrade back to official Android 11.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] AndreanXda:
My internal changed from 128 to 64 after flashing LOS 18.1, I flashed it to stock ROM, the result is still the same, how do I solve it?

XQ-AU52
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Your stock firmware might be too old.

Try this:

fastboot oem lock

Then repair your phone with Xperia Companion.

You will upgrade to latest stock FW After that, unlock your bootloader again, then try LineageOS again.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
I locked the bootloader, fixed my phone, updated to 59.0.A.10.5, unlocked the bootloader and again same as before. I don't know what to do anymore?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] wheal:
I had the same problem:

https://xdaforums.com/t/rom-unoffic...peria-10-ii-stock-based.4195181/post-84131293

1. be sure to have latest Platform Tools

2. boot into Fastboot, flash Recovery from first post

3. reboot into Fastbootd

(Be sure to be in Fastbootd mode now)

4. flash Lineage
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
Now LineageOS 18.1 already rebased on Stock Android 11 now.

This version will display "There's an internal problem with your device. Contact your manufacturer for datails."

Ignore this warning, this is because our kernel is still based on Android 10, I will solve it soon.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
If FastbootD of LineageOS recovery didn't work, try stock recovery again.

So sorry, I have no idea about this now. You might need to ask others for help.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] King_lilrowrow:
For some reason I can't get my bootloader unlocked, says "Cannot open fastboot HAL"

Running fastboot devices returns the device connected fine

adb also shows device is connected

ADB & Fastboot installed through android SDK along with the latest USB drivers, any ideas?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] KriiXOne:
did you follow the correct procedure and the latest adb tools? (https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/)
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
I have yes and what next?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
I still can't cope with installing LineageOS 18.1 and I have a few questions: 1.If I have fastbootd, do I have good drivers, if not, then I ask someone for a link to the drivers on which LineageOS 18.1 has installed 2. who has LineageOS 18.1 installed on the dual sim? 3.Xperia 1 II and 5 II have different ways to install LineageOS 18.1 - can you do this so as not to damage the phone Now I have 59.0.A.10.5 and magisk, but I would like LineageOS 18.1.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] dreDREb13:
I have personally installed and am running this on the dual sim. Have you extracted the zip and flashed the files the way described?

Only difference I see between the installations from the 1ii and 5ii is setting the active slots and not flashing dtbo.img.

I originally installed LineageOS 17.1 and simply flashed the 18.1 zip contents on top of my current install and it worked fine. Perhaps if you're having issues installing directly from stock you can try following all directions for flashing 17.1 and then dirty flash this ROM on top of that? It worked for me.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
New version uploaded. Kernel rebased, LineageOS 18.1 is stable again now.

Attention: Now LineageOS is based on stock Android 11 ffirmware. You need to upgrade to stock 11 at first.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
I have tried 17.1, 18.1 from SjII and there have always been the same bugs I have described in the posts. I used stock recovery and custom recovery and it didn't help. I am curious whether the Sony Xperia 10 II for the European market is the same as the others or different. I have no other ideas what to do, tomorrow I will try at a friend's for windows 7.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
How about run this command in stock system via adb tool:

adb reboot fastboot

------EDIT----------

You already boot into fastbootD right?

try this command in fastbootD mode

fastboot getvar all

Post the result here plz.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
adb reboot fastboot

error: no devices/emulators found
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] dreDREb13:
I upgraded from your previous LineageOS 17.1. Will I have to wipe and install the stock 11 firmware in order to upgrade again now, even though I'm currently on your LOS 18.1?
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] Sjll:
You don't need to wipe data if decrypt is fine. But vendor partition must upgrade to stock 11. You can flash stock super.sin with newflasher, then flash LineageOS 18.1.

adb reboot fastboot

This command needs to be run in Android system with adb debug enabled, not in fastboot mode.

About your picture, I said, you need to boot into fastbootD, NOT fastboot mode.

I wrote and said FastbootD many times，you still provide me the pictures of fastboot mode.

If you are in fastbootd mode, you will get something like:

sjll@sjll:~$ fastboot getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) super-partition-name:super
...
(bootloader) partition-size:system_a:0x930F2000
(bootloader) partition-size:system_b:0x10F05000
(bootloader) partition-size:product_a:0x5F56C000
(bootloader) partition-size:product_b:0x0
(bootloader) partition-size:vendor_a:0x237D2000
(bootloader) partition-size:vendor_b:0x0
(bootloader) has-slot:system:yes
(bootloader) has-slot:product:yes
(bootloader) has-slot:vendor:yes
(bootloader) security-patch-level:2021-01-05
(bootloader) vendor-fingerprint:Sony/XQ-AU52/XQ-AU52:10/59.0.A.8.33/059000A008003302956232951:user/release-keys
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] ig2205:
Everything works at last. My mistake was to misunderstand point 3, which made me always in fastboot mode. My bad English skills and my first encounter with fastbootd are also a problem. Thank you for your patience in translating.
[Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth] xdauserart:
I have LineageOS 17.1 for Xperia 10 II [OTA][SODP] (https://xdaforums.com/t/rom-unofficial-lineageos-17-1-for-xperia-10-ii-ota-sodp.4191601/) installed. To install this ROM, do I need to install Sony Xperia Companion on my PC and then flash the stock ROM from Sony?