Under Settings -> Battery -> Charging mode
(the last option, don’t know the exact option names in English or other languages) and change that so you can set the upper limit for the phone to stop charging.
Thanks, but for some reason that option is missing on the 10 IV. Is this a bug, or intentional? Is there a workaround?
I’ll also note I tried to use BatteryBuddy, and woke up to a phone that hadn’t charged at all, which was not ideal.
I actually had a look at this w.r.t. Battery Buddy as soon as I had flashed my X10V, and I couldn’t suitable files to control the charging. It looks like controlling the charger operation just isn’t currently exposed to userspace - that seems to be the reason why it’s missing from Settings as well. That’s all I could figure out from “outside” anyway.
Hello,
I understand that Sony is making things complicated by the delay of sending the blobs. But could you please compile a version for the DC72? it’s the same as the DC54 but with dual-sim. This will add more beta testers, and it will not cost you anything (just the disk space for the image). As we are many who bought the DC72 last August thinking that we could use them with SailfishOS, and they are still turned off in the drawers … Using them with bugs is better than not using them at all.
Thank you very much for understanding.
So how many are you? You seem to know!
What is the DC72 and DC54?
DC72 is the Asian version of X10V, with two more GB of RAM, and probably some other differences that might or might not interfere on the SFOS image.
i just could flash the dc54 image to the dc72 and it’s working fine so far. i just had to remove a check in the flash script.
Can you specify, please?
i don’t remember, unfortunately i deleted the files. it somehow checks what device is attached and if it matches a criterion. i think it was an if clause which i just deleted
Thank you very much @smatkovi could you please tell me how to do that? it’ll be a great step for me.
No worries, I found in flash-config.sh :
VALID_PRODUCTS=(“XQ-DC72”)
I will try to flash that and
I found the text “xq-dc54” several times in the binary image file sailfish.img001
Does anyone know if it’s safe to flash it anyway or there is a risk to break something?
I’m writing from a xq-dc72, so yes it’s safe. I didn’t remember the model number so i just deleted the check
Refer to the following:
I have been using a DC72 as a daily driver for over a month now, works just as well as the DC54 is reported to. Dual sim does not work, there are extra steps required to enable that but I haven’t bothered as I don’t require that function.
Thank you a lot @Sharks, indeed I didn’t know about it, so I will go for it now.
By the way, what are the extra steps to make the dual sim works please? as I need it (the reason why I bought the DC72 not the DC54 with esim)
Thank you again
Sorry, I’ve searched high and low but can’t find them. Someone had detailed how they edited a file in the system somewhere to re-enable the disabled SIM-2 slot, but I can’t find the post now. As I said, it wasn’t relevant to me so I didn’t bother to save it!
That said, the commercial versions of SFOS 5 will hopefully be out by the end of the year, so hopefully full support for the 72 variants will land with that.
Oh, thank you a million, sorry for the bother. I will continue searching for something, if I find I’ll post it here.
As I prefer to make this version work instead of the new version that might come with the latest blobs from Sony, in which we might have some backdoors and compromise the whole aim of our free product, it looks like the only reason why they are that late to deliver the blobs …
So then i also removed the md5-sum check
@savoep, just managed to spot it today. If you’re still interested, follow this rabbit hole: