yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] dferreira:
Hum... When I tested LOS20 -> Ponce's A14, I had just installed LOS20 and didn't have much installed. However let's see, have you tried clearing cache on Chrome? Since you were on LOS20 and your data was being backed up to Google, you should be able to restore your apps and some of them includes the credentials etc (some do require you to login again). My opinion, but since these are ultimately different codebases that store preferences and settings on different places which can cause unfortunate side effects. Try installing a different browser - if it works, clear storage on Chrome. Clear storage on Trebuchet as well to fix the widgets.
[Android Q&A, Help & Troubleshooting] treff89:
I had the same Internet issue going from LOS21->Ponce. I tried quite a few things but in the end had to wipe everything.

I've had to give up on Ponce AOSP as despite the incredible battery life, it doesn't have the customisability I'm looking for.

Trying dferreira's LOS 20 for the first time, so far so good!
[Android Q&A, Help & Troubleshooting] dferreira:
I confirm, AOD only shows icon. Lock screen does show notifications
[Android Q&A, Help & Troubleshooting] Frost015:
I've identified the issue I reported as buggy E-Ink button behavior. In Ponce's Android 14 build apps will go back to balanced e-ink speed mode whenever you press the volume up/down key. The only apps which won't act this way are those which have balanced mode set as default via eink center. In apps where you usually don't use the volume keys it's not a problem and you may even miss this issue altogether. Also apps that let you remap volume keys (Moon Reader for example) the bug is "bypassed".
[Android Q&A, Help & Troubleshooting] dferreira:
Set on Eink Center the System UI to have a different speed :) to add System UI to the list, expand the notification tray and double press the refresh button and set the speed to fast for example. You should see the entry on Eink Center. I keep System UI, Trebuchet, Gboard keyboard with the same speed. Basically what is happening is that the system ui (like all the popups of the OS) is using the speed that was set on Eink Center as that is the currently focused app.
[Android Q&A, Help & Troubleshooting] Frost015:
Dang! Of course it was that! Thank you boss
[Android Q&A, Help & Troubleshooting] dferreira:
Building a test ROM that includes both the driver + these set up during boot. Will report back if it works and if we are on the right track :)
[Android Q&A, Help & Troubleshooting] dferreira:
I'm seeing this when compiling with this vendor driver. I'm thinking if this to tell me that they won't include android.framework.vibrator but will include vendor.qti.hardware.vibrator.service 🤔

INFO: Removing HAL from the manifest because it is declaring V1 of a new unfrozen interface which is not allowed in this release configuration: android.frameworks.vibrator
[Android Q&A, Help & Troubleshooting] dferreira:
Hum... "Led vibrator renamed to vibrator_1" I think this is why. I'll try to do a symbolic link of vibrator_1 to vibrator to test. Then I need to figure out why there was a vibrator already.

PS: this vibration talk sounds all very dirty 😆
[Android Q&A, Help & Troubleshooting] einkys:
Hi @dferreira . Thanks again for all the work on this. I’ve just flashed your latest rom but am having issues with the overlay I think. The rom boots but I can’t interact with the screen well at all. Hence I can’t get past the setup menu - maybe just to wifi settings and that’s it.

I have seen that you suggested using something like Vysor. The issue I have is I think the use mode is not setup to PTP and hence the phone is not detected either by Vysor or adb.

Any suggestions appreciated!
[Android Q&A, Help & Troubleshooting] Frost015:
That's what happened to me and my phone was definitely recognized by my PC in the vysor software app. Are you using the installed software?
[Android Q&A, Help & Troubleshooting] Kuratius:
[Hisense a9] Root - Reward Offered (Snapdragon 662)

The Hisense a9 is an e-ink 4g smartphone that I want to use as my own Frankenstein light phone. I would like to root mine and use this custom launcher to create a minimalist phone that isn't quite as useless as the Light Phone concept (i.e...

xdaforums.com

Can someone please look into why that happens? And if there is someone on unrooted stock, can they check if it happens there too? This seems very weird.
[Android Q&A, Help & Troubleshooting] dferreira:
Enable ADB and see what the log says when it crashes? Sounds like a bug on InkOS, not related to root. When on stock, I remember a fair amount of crashes due to their crappy memory and battery manager. Couldn't even have notifications working reliably!
[Android Q&A, Help & Troubleshooting] dferreira:
adb is enabled by default on my ROMs. Check the USB cable or could be permissions... If you are on Linux, try scrcpy
[Android Q&A, Help & Troubleshooting] Hadi99:
Only happened to me while rooted. Factory reset is not enough. Restoring stock img in the GDrive folder doesnt work. Only fix is restore the system to a state where it can receive OTA. Firehose restore does the trick.
[Android Q&A, Help & Troubleshooting] dferreira:
From the logs, it seems the code is making an assumption regarding what is the theme you have:

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.hmct.hmcttheme5.preference.Preference.setSummary(java.lang.CharSequence)' on a null object reference

Can well be because you are using a different launcher? The stock ROM is really bad in how Hisense intertwined the OS and the Eink features. It really doesn't handle well changes. An example, you can't set Google Assistant as default for the voice assistant, it keeps resetting. And other settings as well.
[Android Q&A, Help & Troubleshooting] Hadi99:
It's pure stock. Clean reset + magisk
[Android Q&A, Help & Troubleshooting] dferreira:
It's a bug on the stock ROM 🤷‍♂️
[Android Q&A, Help & Troubleshooting] bumblar:
Dear all,

I built my own system.img using the patcher v 1.41 and from andyyan's GSI files (lineage-21.0-20240526-UNOFFICIAL-arm64_bgN.img). It patched like a breeze, installed like a breeze, and everything works but SMS/text messaging

90% of the time I could neither send nor receive text messages. If I took the phone to airplane mode and back, sometimes I managed to be able to send or receive a message or two, but after just minutes, it went back to refuse to send messages.

I then tried to replaced the messaging app with Google messages. This fixed my issue of not being able to send texts. I can now do that very reliably. I still did not manage to receive texts reliably.

I have searched around in forums for a solution but I am quite lost. The A9 was supposed to be my exit from Apple to Android but has now been shelved for the time being, so my apologies if I have overlooked something simple. Any idea of what may cause my issue?
[Android Q&A, Help & Troubleshooting] farfromrefuge:
@damianmqr do you think it would be possible with patch script to enable signature spoofing for microg ? Not sure it is possible without building an img
[Android Q&A, Help & Troubleshooting] damianmqr:
Should be possible, I would need to research what the current most reliable way to dissemble and patch the framework is.
[Android Q&A, Help & Troubleshooting] mangamojo:
Hi everyone,

I'm very new in this community and not sure if this is the right place -so if am in the wrong place, I hope you will bear with me and send me in the right direction instead:

TLDR; How can I UNroot my Hisense A9?

Context:

I have a Hisense A9 running Android 14, following this guide and LineageOS 21 A9 ROM by DamianMQR (both really great and easy to get started with!).

However, as I did not foresee that government official apps are not supported on rooted phones (hindsight is glorious), I'd like to unroot it and see if I can use it with the Google Play version that it came with and then try to delete all the C-apps, etc.

Are there any ways for me to do this?

I have tried the following without luck:

- Look for a originial InkOS / A9 firmware - no luck.

- Any of the suggestions on https://www.androidauthority.com/how-to-unroot-android-phone-tablet-652905/

I hope some of you can point me in the right direction!

Thank you in advance :)
[Android Q&A, Help & Troubleshooting] farfromrefuge:
Ok thanks Will try to investigate it too

EDIT: I will try that https://github.com/ale5000-git/tingle could be enough
[Android Q&A, Help & Troubleshooting] damianmqr:
I think there is an option to just remove root in the magisk manager. I haven't tried it on A9 myself but it should work.

You can also just flash the original boot image you used, probably the one from here https://drive.google.com/drive/folders/1lSOJqfIWaUJ9EnchshKYnNoZNrFZNY9g

Here you can find the entire stock OS (in HLTE_rar folder) to flash with edl mode if you want to go back https://drive.google.com/drive/folders/1kS2hGDuQdH83WwcK_dzCFvA-ZCEpwXxo

Otherwise you can try to keep the root and just hide it from these apps by adding them to the Magisk Deny List and using a SafetyNet Fix/PlayIntegrity Fix module. You might need to look up which one works now, I haven't used them in a while.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
how can i extract my boot.img (to root) without having and edl cable?

Actually it seems i should be able to get it from the rom i installed but i cant find it
[Android Q&A, Help & Troubleshooting] damianmqr:
Did you update to the latest stock OS version before changing ROM?

If so you can just use L2037.6.08..01.00 from https://drive.google.com/drive/folders/1lSOJqfIWaUJ9EnchshKYnNoZNrFZNY9g
[Android Q&A, Help & Troubleshooting] farfromrefuge:
No i did not. I bought my a9 it was already on your build. I just made a fresh install with a build without gapps. That mean i cant use the one you shared?
[Android Q&A, Help & Troubleshooting] damianmqr:
Interesting. My guess would be you can just use the L2037.6.08..01.00 boot.img from the link above (just patch it in MagiskManager apk first if you want root). You can always go back to stock OS with a normal usb cable, edl mode is bootable from adb.

An edl cable is only really needed if you really mess something up and have no access to the OS at all.

Sidenote: You can make a normal usb cable you don't mind cutting into an edl cable pretty easily, which is what I use. Look it up online, but it just involves stripping two wires inside the cable (which is only tough because they might be easy to accidentally cut) to make contact with them, or if you feel like going further you can even add a button.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
thanks i ll try :D

EDIT: @damianmqr thanks a lot it worked!
[Android Q&A, Help & Troubleshooting] treff89:
think it's already working, microg morks 100% for me on damianmqr's LOS 21, as well as DF LOS 20 and AOSP 14
[Android Q&A, Help & Troubleshooting] damianmqr:
I do think LOS supports it internally since quite recent? I may be wrong
[Android Q&A, Help & Troubleshooting] kevji:
Hi all, thanks for all the work everyone's done. This is my first time trying to root a device, and I think I might have bricked my Hi Reader Pro. Any help would be greatly appreciated.

I followed the steps in this thread #209, and used the boot.img and vbmeta.img from #336. That all seemed to work--my device rebooted and seemed fine. Here are the commands if it's any help: https://pastebin.com/E8pLRBFP

The next step is where I think I went wrong. I followed #209 again, with "Prepare Dependencies step 4" which explained how to install LiteGapps. They said to download the [MAGISK] version but I didn't find it in the link they listed, so I downloaded the one called `AUTO-LiteGapps-arm64-11.0-20240615-official.zip`.

I moved the zip onto the Hisense, opened Magisk, selected install module on the Gapps zip, and pressed reboot after it appeared. On reboot, my device gets stuck on the following screen:

I'm guessing I didn't install Magisk / LiteGapps properly (I see the LiteGapps installation steps now and it's not entirely clear what I was supposed to follow).

I tried getting into recovery mode by holding down power + volume up, which didn't change anything. Holding power + volume up instead reaches a different screen that it gets stuck on:

Does anyone have any suggestions or ideas?
[Android Q&A, Help & Troubleshooting] farfromrefuge:
So i finally have my a9:

installed damianmqr build with magisk/microg

I already see one issue with @damianmqr which i could not find if it was already reported. Everytime i reboot the phone the refresh mode goes back to clear, which is quite annoying

i use a white wallpaper which looks great. Still the lockscreen is "grayed" even with a white background. Does anyone know if we can solve this?

I tried to enable accessibility color mode to put the phone to grayscale without success. Does anyone know if we can get this to work? (it would also use less battery as the gpu as less work to do)

I will use forcedoze, batterytool and AppManager to disable as much as possible tosave battery. Will report on this

as @dferreira mentionned i see sometimes when i turn of the screen that the last image stays visible. It happens randomly either when i turn off manually or when it does after a time out.

i cant get the eink button to work when the screen is off. Am i the only one?

Thanks a lot for everything you ve done for us! The phone is quite big but i really like it.
[Android Q&A, Help & Troubleshooting] R0W3Y:
Regarding inconsistency when turning off and lock screen not being white, does the format look like this?

If not fully enable the custom AOD. You might need https://xdaforums.com/t/hisense-a9-root-reward-offered-snapdragon-662.4495809/post-89540430 plus checking the A9 accessibility settings AOD section.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
I dont use AOD as i dont want any battery usage while the screen is off. So it does not look at like that. I am talking about the android lockscreen which applies a "gray" overlay on the background. Trying to see if i can get rid of it.
[Android Q&A, Help & Troubleshooting] R0W3Y:
Ah, ok. Without the AOD I get inconsistent behaviour when locking the screen. I only use the AOD as otherwise I'm not sure the device is really locked without interacting with the screen.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
@damianmqr @dferreira I have some apps crashing with microg installed. Especially niagara.

Looking at the log i can see:

06-26 11:47:50.730 6048 6048 D nativeloader: Configuring clns-10 for other apk . target_sdk_version=34, uses_libraries=ALL, library_path=/system/priv-app/microG/lib/arm64:/system/priv-app/microG/microG.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand
06-26 11:47:50.733 6048 6048 D AndroidRuntime: Shutting down VM
06-26 11:47:50.734 6048 6048 E AndroidRuntime: FATAL EXCEPTION: main
06-26 11:47:50.734 6048 6048 E AndroidRuntime: Process: bitpit.launcher, PID: 6048
06-26 11:47:50.734 6048 6048 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libcronet.102.0.5005.125.so" not found

The issue is that this path /system/priv-app/microG/microG.apk!/lib/arm64-v8a does not seem to work even though it does exist. Feels like it does not read "inside" the apk. Do you have any idea?

I can solve it by extracting in /system/priv-app/microG/lib/arm64 but it does not persist upon reboot.

Do you have any idea?
[Android Q&A, Help & Troubleshooting] farfromrefuge:
yes it is an issue not knowing if it is actually locked.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
Actually @treff89 is right. It works out of the box with latest LOS! pretty awesome.
[Android Q&A, Help & Troubleshooting] treff89:
Nice. I purely use it for battery life, so will be interested to hear how your testing goes with the apps you mentioned above to save battery. I mentioned earlier in the thread that I also use Magisk module Universal Kernel Tweaks (have to make a file in /data/soc.txt containing "sdm660") to try to decrease the clock speeds when idling with screen on.
[Android Q&A, Help & Troubleshooting] mangamojo:
Thank you for the fast response!

I've been been fumbling around for some time - so I need to reach out for help again:

My goal

Get back to the original stock OS / inkOS(?) with Google store (for official government apps) and without any or as little bloatware as possible.

I am curious on your thoughts on general security and safety of the original OS as it runs on Android 9 vs a rooted Android 14 LineageOS?

Unsuccessful tries:

- Using magisk deny list doesn't seem to make a difference - I have tried restarting the phone, etc.

- A complete uninstall of Magisk where it reinstall the original firmware doesn't seem to work either - I just end up with the same LineageOS and all user data still there?

- Haven't found any unroot in Magisk?

- I never made a boot.img before doing the root and flash to LineageOS .... big mistake???

Thoughts/questions on Magisk and boot.img

I followed a guide that did not include Magisk, meaning I haven't installed it until I had flashed the phone with the LineageOS ROM (am I using the right words in the right order by now?). Does that mean Magisk can only "go back" to unroot since I installed it on a version that was already rooted? Or is it possible to give it another boot.img (e.g. the stock OS aka. InkOS?) instead? When installing it, I passed it "latest-boot.img" from https://drive.google.com/drive/folders/1fhx-5ERUJEzVI3SppzDw7br0hdpaYhgU - can I pass another one?

Questions about the files in the G-drive in general:

- Are the two .img files in the L2037... folders LineageOS or are they InkOS/stock OS? That is a little unclear to me, though I get the impression that they are lineageOS?

- How should I use the .rar files from the HLTE_rar folder? Install them one at a time? Do they hold .img files as well? When I try to look inside them with WinZip (I am on a Mac) I cannot see anything? The documentation in the folder does not mention the rar files either?

InkOS is still there???

If I try to go into recovery mode the phone goes back to the orginial InkOS screen but only gives me two options for restarting the device or erase user data? Does it mean inkOS also runs somewhere on the phone - or is it a part of the lineageOS ROM? Added a picture (with Google translate on top) for context and an image of the bootlader always displaying "FastBoot Mode" instead?

It is quite new for me and since I haven't been able to find screenshots on how things should look I am unsure if I've ended up in a weird state or if this expected?

Thank you for your help so far already!
[Android Q&A, Help & Troubleshooting] damianmqr:
stock OS doesn't have Google services what exists with some vendors is hacky solution to include it but I've heard it caused quite a few issues, haven't tried it myself. The OS itself is pretty bloated, you can remove a lot of stuff with adb and if you root you can use AFWall or similar with deny list to block out system apps from communicating with the internet that you cannot fully remove. This will result in an okay state, but I personally prefer GSI which works without the need for such workarounds. Also I am not sure what the government app in question expects from a device to run, but if it's using play integrity it might not even work on stock.

Not sure I understand the question. The guide you provided doesn't include rooting instructions so I'm not sure you're rooted. You can be on custom ROM without root. Flashing latest-boot.img would unroot you if you were and shouldn't do anything otherwise.

These are stock boot images, not related to LOS. Since we use a GSI image which just replaces the system partition these do not get modified with a custom ROM at all.

https://www.reddit.com/r/eink/comments/16tpr96
see the Q: Things have gone terribly wrong. How do I get back to stock after bricking my phone? section in that reddit post. You don't need an edl cable if you can boot to the OS. Just enable USB debugging if you haven't already, connect to your PC and run adb reboot edl after which you can just use a regular cable.

Neither, recovery is seperate from system and in A/B devices is a part of the boot image. InkOS might still be installed in a different slot but since data partition is shared it would probably be broken unless you wipe the data, but at this point it's better to just go with the EDL method to fully restore stock.
[Android Q&A, Help & Troubleshooting] ext23:
@damianmqr, I have been using your ROM without any hiccups for a couple of weeks now, it's so good!

Battery life is fantastic for me, even with AOD on, wifi and mobile on, no other special tweaks. I lose maybe 4-6% overnight which I think is perfectly acceptable. With light usage I am getting 3-4 days off a single charge easily. Battery stats however say "Battery usage data will be available in a few hours once fully charged," but it doesn't update even after a full charge or a reboot.

The one bug-type thing I have noticed is that the phone often reverts to full brightness when waking up from AOD. I have it set to auto brightness but it always seems to jump back to 100% and I have to manually slide it back down. I don't have one shot brightness on either, because that means that auto brightness won't adapt over time (right?). I also don't have any of the phh options turned on (alternative brightness curve/linear brightness curve/force alternative backlight scale/allow lowest possible brightness). Would any of these fix it?
[Android Q&A, Help & Troubleshooting] damianmqr:
Glad you like it!

Not sure if it would fix it, my guess is not but you can give it a try! It shouldn't break anything, but try to remember what you changed so you can revert back later and don't touch "Disable HW overlays" as it will stop screen refresh from working
[Android Q&A, Help & Troubleshooting] farfromrefuge:
@damianmqr any idea why refresh always reset after reboot? Does it works for you?
[Android Q&A, Help & Troubleshooting] damianmqr:
Not sure, it should be set per app so reboot affecting it is weird. I will see if I can replicate it.
[Android Q&A, Help & Troubleshooting] farfromrefuge:
Could it be an issue with my launcher then? I use Niagara Launcher. Will try to see what happens with trebuchet
[Android Q&A, Help & Troubleshooting] damianmqr:
I doubt it as it's treated as any other app, probably some bug with the service itself. I'll investigate when I get a bit more time to work on this project, hopefully soon.
[Android Q&A, Help & Troubleshooting] OwlTec:
EDIT
[Android Q&A, Help & Troubleshooting] meh.:
@dferreira for some reason with your latest ROM the Contacts app (or any other app trying to deal with contacts) ends up freezing and then crashing, have you seen this happen before?
[Android Q&A, Help & Troubleshooting] dferreira:
Working fine for me 🤔 calling, WhatsApp, Google Contacts, all working! Try clear data on the contacts app. Since it's synced with Google, should restore just fine?
[Android Q&A, Help & Troubleshooting] meh.:
I didn't add a Google account, I'm using the vanilla version, the Clock app also freezes and crashes, it was flashed from a completely clean EDL reset.

Just tried with clearing storage and cache and still crashes.