yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] damianmqr:
Copied from reddit

https://www.reddit.com/r/eink/comments/16tpr96

All of the needed files should be in the 3 links provided, the rawprogram in the rar file in the first link
[Android Q&A, Help & Troubleshooting] scarletya:
There was an error when I perform unzip RAR

Now I got it

Thank you!
[Android Q&A, Help & Troubleshooting] ext23:
I'm a bit confused. I just discovered that there is Lineage for the A9 (awesome!) but where is the latest image? The only one I can see is the one announced on Reddit which is from the start of April.
[Android Q&A, Help & Troubleshooting] treff89:
Have patience mate, the developers (predominantly dferreira and damianmqr) are doing it out of goodwill, both have had life getting in the way of late, as keen as we are to see the next release!
[Android Q&A, Help & Troubleshooting] benru89:
try reading the thread from the start like until page 8-9 to see how to backup/restore backup, how edl works...etc. After that you can go directly to unlock your bootloader and flash either damianmqr lineageos 21 or dferreira lineageos 20. I didnt try both so i dont know how different they are but the one im on is working fine for me. First week with my HIsense A9 and enjoying it.

I wouldnt bother getting root, everything works fine without it for me.
[Android Q&A, Help & Troubleshooting] bigwigs:
@dferreira

Ethos - Crypto Ethereum phone Build for android devices based on LineageOS :)

GitHub - EthereumPhone/android

Contribute to EthereumPhone/android development by creating an account on GitHub.

github.com
[Android Q&A, Help & Troubleshooting] ext23:
How do I install the custom fastboot?? I am in fastboot mode on my A9. I have downloaded and installed the Android SDK for Windows to

C:\Program Files (x86)\Android\android-sdk\

This is the default directory.

I copied/overwrote the custom fastboot from the Google Drive but after rebooting to fastboot I get:

AdbWinAPi.dll was not found.

??!?!?!

EDIT: OK, so you just need to download the latest platform tools from this link, then overwrite the fastboot.exe in that folder with the ones inside the \bin folder of the custom fastboot.zip file. Then the fastboot Hisense unlock commands should work. This was not spelled out anywhere so I hope this helps other users.
[Android Q&A, Help & Troubleshooting] ext23:
OK I'm up and running with LineageOS! Thanks so much everyone!!

...but even though I didn't root, Apple Music is saying "Only Available on Unrooted Devices." This device is important for me as a music player so I need to get this working (don't need banking apps though).

YASNAC says it passes basic integrity, but failes CTS profile matching. It says ADVICE: LOCK_BOOTLOADER.

What can I do? I'm not planning to root or go back to stock, so could I just relock the bootloader? If so, how?
[Android Q&A, Help & Troubleshooting] damianmqr:
Apple music seems to be using something similar to https://github.com/KimChangYoun/rootbeerFresh to detect root. You can see what it complains about by installing that app, it might be fixable through build.prop or counterintuitively actually rooting the device and using a module to hide it.
[Android Q&A, Help & Troubleshooting] ext23:
OK well this is what the app readout says...

Any ideas?? Like I said, I definitely didn't root the phone myself...
[Android Q&A, Help & Troubleshooting] Mike(Ger):
I guess you're phone isn't rooted as we would call it, otherwise probably some other green check marks would be red Xs, like the Magisk specific ones. But it's probably modified enough so that RootbeerFresh and Apple Music recognize it as "not out of the box" which they immediately seem to call "rooted".

I can't really help you achieve using Apple Music and having LineagOS running. But as it looks it's not easily possible to have both.
[Android Q&A, Help & Troubleshooting] damianmqr:
Doesn't seem too bad. I might be able to fool it in the next release of my patched OS and the patching script, not sure yet when that's going to be but I will let you know if it works.

EDIT: One more thing you could try until then is to just downgrade the apk to an older one. I'd suggest looking for it on apkmirror and scanning the apk on virustotal just to be safe if you do end up going with this way.
[Android Q&A, Help & Troubleshooting] ext23:
I installed version 4.5.0 and it works! I did a search and it seems Apple started doing this around March this year (edit: it was version 4.7.0). So I thought I'd jump back a bit further.

Anyway, the apk works now, but it might stop working in future, so a patch or script would be most appreciated. Thanks so much for all your work so far, let's make this device excellent for everyone!
[Android Q&A, Help & Troubleshooting] artelse:
The SE Linux flag is not set, so it is reported as rooted (at least this is what I read about it).
[Android Q&A, Help & Troubleshooting] ext23:
OK, how can we toggle it?
[Android Q&A, Help & Troubleshooting] artelse:
Don't know if you need real root for this, but I think Zygisk installable via Magisk allows to do this. Don't take my word for it, am an Android novice.
[Android Q&A, Help & Troubleshooting] einkys:
thanks for all the hard work on this - I have been away for a while so am a bit lost as to where progress has been made. I had @dferreira 's first build working, and was hoping an update to allow the warm light to work would be released. Am I correct this hasn't been solved yet?
[Android Q&A, Help & Troubleshooting] damianmqr:
I think I was able to fix it in a new version, at least rootbeer no longer reports root.

At which point did the Apple Music app report the root for you? I don't have an account but I was able to get to login screen. If it was after the login, let me know and I'll make an account to test, otherwise it should be good to go and I'll plan a release soon.

The vibration issue still won't be fixed in this version as it'll mostly focus on AOD features, but it's one of the next issues on my list along with trying to overlay the brightness file for better yellow light control.
[Android Q&A, Help & Troubleshooting] ext23:
Wow awesome! Thanks! Yeah I think it was before the login screen.

What is the process to flash an updated ROM when it's available?
[Android Q&A, Help & Troubleshooting] damianmqr:
Which OS are you on? If it's LOS21 you should be able to just flash system through fastboot with a single command

"fastboot flash system system.img" where system.img is the unzipped img file I send, if it's LOS20 you would unfortunately also need to wipe userdata with "fastboot -w", I suggest making a backup anyway.

If you want to stay on LOS20 and not reflash you could edit build.prop through the root shell, but it also carries some small risks if you break the file.
[Android Q&A, Help & Troubleshooting] R0W3Y:
Late here so haven't had chance to play with it much yet, but that's a brilliant update. Thank you so much

damianmqr!​

Hope your finals went well.
[Android Q&A, Help & Troubleshooting] damianmqr:
Thanks R0W3Y! I hope you get a chance to try it out soon, I haven't tested much myself yet if I'm honest but I will keep using it for the next few days. There may be some minor changes to the apk, but I don't imagine the system service itself will be affected so no reflashing before the next major version at least.

The finals went good! I'm just waiting for the results now so I have time to focus on personal projects.
[Android Q&A, Help & Troubleshooting] einkys:
Thanks for the hard work. If I am on @dferreira last version - can I switch directly to yours ?

Can I also ask - does your version support the warm backlight?

Many thanks!
[Android Q&A, Help & Troubleshooting] damianmqr:
You can switch, but since it's different LOS version (21 vs 20) you also need to wipe user data (with "fastboot -w") so a backup of data is necessary.

And yes, warm backlight is supported with one minor issue that it doesn't automatically dim when moving it close to your ear on a call, otherwise I didn't have issues with it.

I'm working on a fix for that but it isn't that straightforward, I want to include it in one of the next major updates.
[Android Q&A, Help & Troubleshooting] ext23:
Wow! Amazing work!!

This is amazing!!!

@damianmqr, I'm on LOS21 already, so is it safe to assume that it's your build?

I have one feature request...Koreader has the option to use the current book's cover as the screen saver image. Is there a way we can get that working?

Please let me know if there's a way to donate!
[Android Q&A, Help & Troubleshooting] damianmqr:
If you're on LOS21 you should be fine without wiping data, but as I mentioned try to have a backup just in case anyway ;)

You can manually set a background of the AOD to any image you want through e-ink settings, I could try to automate that to take cover from specified e-reader app.

I haven't taken donations before, so I'm not entirely sure about the best way to handle them. However, I have set up a Ko-fi page if anyone would like to support the project with a one-time donation. Thank you for considering it! :)

https://ko-fi.com/damianmqr
[Android Q&A, Help & Troubleshooting] ext23:
Koreader is pretty customisable in the way it lets you save covers to use as screensaver. You would just need to tell LOS to always load a particular file when the screen turns off, rather than storing one user-defined image somewhere.

Stealth edit: here's a screenshot of the relevant bit in Koreader in case you're not familiar with it.
[Android Q&A, Help & Troubleshooting] ext23:
Here's what I've noticed!

The Now Playing on AOD screen sometimes only displays white text without background art (really hard to read). Pausing/skipping to the next song while on the AOD screen will show the art.

The AOD image is automatically stretched to the screen aspect ratio (824×1648). I manually resized my image on PC.

E-ink settings are in the app list now (great!) but it would be even better if you could bring them up with a Quick Settings tile...as well as maybe a screen refresh tile.

I'm not sure if temperature and backlight strength are supposed to auto-adjust together, but I don't think they are. Enabling night mode is too yellow. At the moment I'm using auto backlight with the manual temperature slider.

Thanks so much! This device is incredible now.
[Android Q&A, Help & Troubleshooting] damianmqr:
Great suggestions, thanks! It shouldn't be too hard to implement these.

quick edit: Which app do you use for music playback? It could make debugging a bit easier. I have noticed some of them don't give good callbacks or even drop them all together after a while. I did find and implement some ways to mitigate this but they probably need to be adjusted further.

Night light makes the device use yellow backlight only, to achieve something in-between you need to use the temperature silder. I wanted to first figure out the overlay which could allow me to have more proper yellow light handling (so proximity sensor dimming works as expected).

Adding a mode to change it automatically based on time-of-day is in the plans. Maybe even based on sensor reading like adaptive brightness, but I would need to test how well that would work.
[Android Q&A, Help & Troubleshooting] ext23:
Spotify mainly, but also Apple Music and Soundcloud. I noticed the same bug with both Spotify and Apple Music (thanks for the login fix by the way!).

Also this is perhaps going into too much detail, but I think the Now Playing on AOD should disappear after eg. 10 minutes on pause (mine is constantly showing music even though I stopped playback and started listening on my other phone). And there should probably be the option to hide Now Playing on AOD in e-ink settings for those who don't want it!! (edit: I realised you can just turn off the notification permissions, but this might effect other relevant notifications).
[Android Q&A, Help & Troubleshooting] dferreira:
Awesome 🙌 I’ve been too busy with end of school/season events that I couldn’t spend time on the computer to sort things out. If I find out how to solve the vibration issue, will let you know.
[Android Q&A, Help & Troubleshooting] bigwigs:
Is LOS21 branch fixed? Last time, both me n @dferreira were having issues loading it?

Can u share what build scripts r u using ?
[Android Q&A, Help & Troubleshooting] dferreira:
I think it is AndyCYan prebuilt that is extracted and repackaged?
[Android Q&A, Help & Troubleshooting] damianmqr:
I'm just using the patching script that's in my github repo and the previous build of LOS21 by AndyYan.

The latest source is still broken so I am waiting for a newer release to test if it's resolved.

Correct
[Android Q&A, Help & Troubleshooting] dferreira:
Ponces AOSP Android 14 does build and that is what I left running on my A9. It contains MicroG signature spoofing and Play Store as well. May be a better stable build base than LineageOS 21 at this point.
[Android Q&A, Help & Troubleshooting] Mike(Ger):
Do you mean this one? I'm about to receive my A9 and I want to flash it as soon as I get it to also help with testing :)

[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
[Android Q&A, Help & Troubleshooting] bigwigs:
No, that’s old image. Checkout @vbhai recent post where he has the image details[/url]
[Android Q&A, Help & Troubleshooting] Mike(Ger):
Ahh I think I found it. Posting it here in case anyone else is looking for it:

[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
[Android Q&A, Help & Troubleshooting] einkys:
@damianmqr - is it possible to run your script using windows / osx or is Linux necessary? Thanks!
[Android Q&A, Help & Troubleshooting] damianmqr:
On windows you would need to use WSL to run it. On MacOS you might be able to just run the script the same way as on linux, maybe with some modifications.

But I haven't tried it on MacOS so I cannot guarantee if it will succeed. WSL on windows should be fine as it's just linux under the hood.
[Android Q&A, Help & Troubleshooting] ferlanero:
And you're not using your LOS20 compilation? I've been doing this for almost a month now and I find it particularly pleasant to use on the A9 with your eink Center implemented
[Android Q&A, Help & Troubleshooting] vbhai:
Legend!

I am on stock at the moment. Haven’t been using any of the GSIs till the vibration is fixed. Let me know if you need anything from the stock ROM to fix vibration in the GSIs.
[Android Q&A, Help & Troubleshooting] dferreira:
Yeah I currently have Ponces installed but I’m not daily driving the A9 at the moment - I just compiled Ponces Treble Android 14 to see if it booted successfully. Then I sideloaded my Eink Center to make sure all was ok with it on Android 14 and it does work. I’ll have some free evening time Monday-Thursday so I’ll try to first fix vibration and then make Googless and Googled versions of Ponces AOSP Android 14.
[Android Q&A, Help & Troubleshooting] dferreira:
Can you share the build.prop and system.prop from /system/vendor folder?
[Android Q&A, Help & Troubleshooting] vbhai:
There you go, mate. default.prop and build.prop attached from stock.
[Android Q&A, Help & Troubleshooting] damianmqr:
Minor Version Release (v1.4.1) of my E-Ink Service apk​

This version is an extension to the latest Major Release and brings some bug fixes and quality-of-life changes recently proposed by @ext23

The latest release of the patching script with the new apk is under https://github.com/damianmqr/A9PatchingService/releases/latest

But since this is just an application update I will also post the apk here as an attachment.

Once you install it, you might have to

1. Go to App Info of the app

2. Press three dots in top right

3. Select "allow restricted settings"

(Using 'adb install' and a PC you might be able to skip this first section)

Later, you also need to go into Accessibility in settings and enable "A9 Accessibility Service", the app should now be fully updated.

The Latest Changes​

Fix MusicView Album Cover retrieval on AOD

If an album isn't passed along with the title the first time the app is notified of music change it will be re-queried (from my experience it usually retires at most once or just works).

There is also a placeholder in case no album cover exists at all or can't be retrieved.

Add optional timeout for MusicView

E-Ink settings now allow users to specify after how many minutes of pause should the music view disappear even if the music session is still active (can be set to instant or never as well)

Add quick setting tiles for clearing screen and accessing E-Ink settings.

Add support for dark colors in AOD

When a background is updated the service will automatically set each AOD view's color to white or black based on the luminance (perceived brightness) of its background. This allows the background to not only be dark, but even mixed color.

Allow saving the AOD background in External Storage for KOReader

Once you enable "All Files Access" (shortcut to which is in the E-Ink settings) the AOD will read the background file from "a9_comp_service" folder in external storage (otherwise it uses internal storage). This allows apps like KOReader to save to it automatically.

You can do this in KOReader by following these steps

While in any book, go to the "Settings > Screen > Cover image"

Use "Set Image path", press "OK" and go into the "a9_comp_service" folder

Once there, if there is a file called "bgimage" you can just select it. Otherwise, long-press to choose current folder, type in "bgimage" as a filename and press save.

Once back in the "Cover Image" settings, enable "Save cover image" and it should now be automatically setting AOD background based on currently read book.

No warranites provided. Check GitHub repo for license.

Want to support the project? You can buy me a coffee at https://ko-fi.com/damianmqr or just provide feedback and suggestions here, both are greatly appreciated! ;)
[Android Q&A, Help & Troubleshooting] todd-scoops:
For the life of me I can't find "a9_comp_service" on my phone even after enabling full file access and rebooting. Am I missing something? Love your work on this! It's amazing!
[Android Q&A, Help & Troubleshooting] ext23:
Wow! Incredible work, as always, thank you.
[Android Q&A, Help & Troubleshooting] R0W3Y:
I'm still having some weird AOD issues, that I think I've just partly isolated.

On my A9 I've tried many different settings, but:

When I press the power button to standby it always either goes to a solid black screen or shows a static version of the last screen (no AOD)

If I quickly single click the power button to avoid the fingerprint scan from standby I can see what I should have as the AOD

Starting or stopping charging shows the AOD

The strange thing is, I also have a Hi Reader Pro as a backup that's running the same software and is pretty much setup the same (currently damianmqr's latest version, but this has been an issue for me on previous versions). But the AOD works fine on the HRP.

I think the problem is that in the Lock Screen settings the HRP has the option 'Always show time and info'. With this off, I get the same behaviour as the A9. With it on the AOD works as expected. Any ideas why this option isn't present on the A9, or how to add it?

I've also tried restarts, 3rd party AODs (they work on the a9, but require 2 fingerprint scans to get past both AODs), and checking the battery saving / scheduling settings are off.
[Android Q&A, Help & Troubleshooting] damianmqr:
You could try setting a background manually first through the E-Ink settings app to any photo on your device, it should ensure the folder is created then. It should be on the same level as dictionaries like "Downloads" "Pictures" etc.

If that still doesn't help, let me know and I can look into this further.

This is strange, can you confirm if the "Force allow Always-On-Display" is enabled in "Phh Treble Settings > Misc"?

You could try toggling it off, rebooting, back on and rebooting again.

Have you flashed the latest version without wiping data?

As a last resort you could try flashing the latest version with "fastboot -w" after to clear user data, I'll try to think of what else could be causing this so you can avoid that but I'm not really sure I'll find it yet.
[Android Q&A, Help & Troubleshooting] vbhai:
What a coincidence that you’re reading the Count of Monte Cristo. I just downloaded it as well a couple of days ago haha.
[Android Q&A, Help & Troubleshooting] R0W3Y:
'This is strange, can you confirm if the "Force allow Always-On-Display" is enabled in "Phh Treble Settings > Misc"?' Confirmed

'You could try toggling it off, rebooting, back on and rebooting again.'

Already tried this

'Have you flashed the latest version without wiping data?'

Yes, wiping is my last resort :)
[Android Q&A, Help & Troubleshooting] R0W3Y:
''You could try toggling it off, rebooting, back on and rebooting again.''

Just tried this again and the setting has appeared :) Seems to be working ok. Thanks again for your help @damianmqr
[Android Q&A, Help & Troubleshooting] damianmqr:
Nws, glad you got it working! And thanks for your support for the project :)
[Android Q&A, Help & Troubleshooting] todd-scoops:
That fixed it! Thank you so much for your amazing work.

Has anyone else had problems with rapid battery drain? Recently I've been able to watch the phone loose a couple of percentage points just sitting on the lock screen every 15 minutes or so. I'm about to try wiping it and reinstalling the OS, but I wanted to check to see how everyone else is doing first.
[Android Q&A, Help & Troubleshooting] damianmqr:
On my HRP the battery works rather well. I've not been using it for any heavy tasks, just reading for the past day during the day so the backlight wasn't on but the Always on Display was turned on the whole time. Now it's showing me it will last another 4 days 2 hrs on ~83% battery, but I will try to use it more and report back.

Sometimes the kernel may get messed up with a GSI when swapping between OSes, not sure why. For me it broke wifi twice but I was flashing A LOT when trying different options. What I did to resolve it was flash stock via EDL, update it to the latest version again (it takes a few incremental updates, unfortunately Hisense doesn't provide cumulative updates) and reflash GSI from there.

Also, "Battery Usage" section in settings may provide more context.

I suggest also enabling "Remove animations" in "Accessibility > Color and motion", you don't need view animations on an e-ink and it can help a bit.