yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] bigwigs:
below is my log ( i renamed android aosp file from vbhai's link:-

D:\A9\root\A9_Fastboot\windows-x86\bin>fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.003s]

< waiting for any device >

Finished. Total time: 9.734s

D:\A9\root\A9_Fastboot\windows-x86\bin>fastboot flash system aosp-android14.img

Invalid sparse file format at header magic

Resizing 'system_b' OKAY [ 0.007s]

Sending sparse 'system_b' 1/14 (262116 KB) OKAY [ 6.569s]

Writing 'system_b' OKAY [ 2.152s]

Sending sparse 'system_b' 2/14 (262116 KB) OKAY [ 6.549s]

Writing 'system_b' OKAY [ 1.034s]

Sending sparse 'system_b' 3/14 (262104 KB) OKAY [ 6.574s]

Writing 'system_b' OKAY [ 1.027s]

Sending sparse 'system_b' 4/14 (262128 KB) OKAY [ 6.541s]

Writing 'system_b' OKAY [ 1.050s]

Sending sparse 'system_b' 5/14 (262120 KB) OKAY [ 6.563s]

Writing 'system_b' OKAY [ 1.038s]

Sending sparse 'system_b' 6/14 (262128 KB) OKAY [ 6.549s]

Writing 'system_b' OKAY [ 1.021s]

Sending sparse 'system_b' 7/14 (262124 KB) OKAY [ 6.555s]

Writing 'system_b' OKAY [ 1.047s]

Sending sparse 'system_b' 8/14 (262124 KB) OKAY [ 6.534s]

Writing 'system_b' OKAY [ 1.006s]

Sending sparse 'system_b' 9/14 (262124 KB) OKAY [ 6.526s]

Writing 'system_b' OKAY [ 1.032s]

Sending sparse 'system_b' 10/14 (262128 KB) OKAY [ 6.551s]

Writing 'system_b' OKAY [ 1.069s]

Sending sparse 'system_b' 11/14 (262084 KB) OKAY [ 6.574s]

Writing 'system_b' OKAY [ 1.035s]

Sending sparse 'system_b' 12/14 (262120 KB) OKAY [ 6.546s]

Writing 'system_b' OKAY [ 1.030s]

Sending sparse 'system_b' 13/14 (262140 KB) OKAY [ 6.534s]

Writing 'system_b' OKAY [ 1.056s]

Sending sparse 'system_b' 14/14 (101932 KB) OKAY [ 2.551s]

Writing 'system_b' OKAY [ 0.566s]

Finished. Total time: 111.633s

D:\A9\root\A9_Fastboot\windows-x86\bin>fastboot -w

Erasing 'userdata' OKAY [ 2.195s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Erasing 'cache' FAILED (remote: 'Partition doesn't exist')

fastboot: error: Command failed

D:\A9\root\A9_Fastboot\windows-x86\bin>fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.003s]

< waiting for any device >

Finished. Total time: 9.734s
[Android Q&A, Help & Troubleshooting] vbhai:
It flashed correctly, mate. Dunno why you ran fastboot reboot fastboot again after wiping the userdata. Just reboot normally with:

fastboot reboot

And you should boot into A14.
[Android Q&A, Help & Troubleshooting] dferreira:
Building A13 Lineage with screen density and hw enabled as I’m typing this. Will share it as soon as I verify all is working. Just in case something is still broken on A14 since it’s very fresh.
[Android Q&A, Help & Troubleshooting] bigwigs:
i think i fat fingered it,.

dpi settings needs to be done with image for sure.
[Android Q&A, Help & Troubleshooting] bigwigs:
touch screen is slow.
[Android Q&A, Help & Troubleshooting] vbhai:
Aren't we disabling HW acceleration and disabling HW overlays?

Yeah, for now you can run this command:

adb shell wm density 360 && adb reboot

You can also add this line to build.prop at the end to take care of that:

ro.sf.lcd_density=360
[Android Q&A, Help & Troubleshooting] vbhai:
Use vysor to interact with your phone to set it up:

Vysor

www.vysor.io
[Android Q&A, Help & Troubleshooting] bigwigs:
this is life saver !!!!!!!
[Android Q&A, Help & Troubleshooting] bigwigs:
with 8GB of RAM also, android 14 feels slow. atleast the setup
[Android Q&A, Help & Troubleshooting] vbhai:
That is the e-ink screen playing tricks on you, mate. Setup is quite straightforward and fast for me. Thoug in all honesty, I just skip everything and go straight to the home screen.
[Android Q&A, Help & Troubleshooting] dferreira:
If on Linux/Mac, you can install `scrcpy` and use it too :)
[Android Q&A, Help & Troubleshooting] dferreira:
This is taking forever 😭
[Android Q&A, Help & Troubleshooting] vbhai:
Aye, I just installed yours trusty Fedora on my laptop and just found this today.

The correct build.prop flag should have been:

debug.hwui.disable_hw_overlays=true

But adding this still does not disable hardware layers by default -.-
[Android Q&A, Help & Troubleshooting] dferreira:
LineageOS 13 with the right density out of the gate and Gapps: https://drive.google.com/file/d/1gSFuN2jgmE3h435KKoG5QUE-b2f4ePON/view?usp=sharing

There is no root on this because I want RCS to work. Use scrcpy/Vysor to set it up initially and disabling HW overlays. You can start scrcpy so you can see boot animation and such. At the beginning screen is blank. The screen is also blank when it asks for a pin (turn the screen off and back on and you'll see it)
[Android Q&A, Help & Troubleshooting] bigwigs:
android 14 was working well with atleast my phone. so going to use this one.
[Android Q&A, Help & Troubleshooting] vbhai:
Have you been able to figure out a way to disable hardware overlays on boot? I just have not been able to make it persistent across boots no matter what I try.
[Android Q&A, Help & Troubleshooting] dferreira:
That's a fight for another day ;) 0:23 am here.
[Android Q&A, Help & Troubleshooting] vbhai:
Ahh, no worries. Did not realise Finland was 2 hours ahead of GMT.
[Android Q&A, Help & Troubleshooting] dferreira:
A demo of it running on my device:

Dr. Denzil Ferreira :fedora: (@denzilferreira@techhub.social)

Attached: 1 video LineageOS 13 on Hisense A9. Some progress!

techhub.social
[Android Q&A, Help & Troubleshooting] bigwigs:
I'm getting msg, that device is not Play Protect Certified. So, do we need to root it ?
[Android Q&A, Help & Troubleshooting] dferreira:
No, just need to preset the device prop signature to one that has passed the certification. I will get to it. Also hw overlay works but the refresh rate is the default, so the UI does not refresh fast yet.
[Android Q&A, Help & Troubleshooting] dferreira:
Is this A14? A13 is not showing that 👀
[Android Q&A, Help & Troubleshooting] bigwigs:
nope, it is ur img from google drive- Android 13.

Go to sleep. U can look at it later.
[Android Q&A, Help & Troubleshooting] dferreira:
I see now, you get that after signing into Google. Yeah we need to fix the device sig.
[Android Q&A, Help & Troubleshooting] bigwigs:
don't know whether it is my phone or something but with android 14 gsi, lineage 20 gsi, there were issues with accessing my phone settings. i was not able to access wifi calling with android 14 g and then with lineage 20 gsi, i was not able to access my call and sms settings.

with both images, the data network defaulted to 3G network.

so, im heading back to hisense images for now to see if i can get settings back
[Android Q&A, Help & Troubleshooting] damianmqr:
I ended up adjusting the style after setting correct DPI on my phone, Here's the new release

Release v0.2 · damianmqr/A9PatchingService

Fix style Add persistance

github.com

Also added persistance to temperature and brightness and better handling of root commands, this is how it looks like so far.

To get this working on non root devices you would need the system service to interact with kernel, but for rooted ones this is an okay solution.
[Android Q&A, Help & Troubleshooting] vbhai:
For the A14 image I shared with you, there were Phhusson IMS settings. You just have to enable those and you get VoLTE, and VoWiFi working. And as for 3g, you just need to go to network settings and change mode from 3g to LTE.
[Android Q&A, Help & Troubleshooting] vbhai:
Hey, great work! I was trying this out but I ran into an issue where the disable hardware overlays setting would get reverted. Need a persistent solution for that.

There are lots of other problems with the device right now in regard to the colour temperature and brightness, etc. For example, when you are on a call, the backlight does not turn off when you place the call on your ear but it actually just becomes yellow. The backlight also tends to become weird sometimes where at the bottom it starts showing a weird circle and the screen is not lit up properly.
[Android Q&A, Help & Troubleshooting] bigwigs:
trying to reflash hisense images via edl. i'm stuck in fastboot loop :(
[Android Q&A, Help & Troubleshooting] dferreira:
Yeah, I was reading more about this, it's not so simple to add a device signature. We may have to install Magisk and MagiskHideProps to get it verified.
[Android Q&A, Help & Troubleshooting] dferreira:
- I've added a small script that runs as root on init in device/lineage/gsi/init folder:

#!/system/bin/sh

(while :
do
sf=$(service list | grep -c "SurfaceFlinger")

if [ $sf -eq 1 ]
then
#Disable HW overlay
service call SurfaceFlinger 1008 i32 1
#Set EPD mode to speed at boot
echo 521 > /sys/devices/platform/soc/soc:qcom,dsi-display-primary/epd_display_mode
break
else
sleep 2
fi
done
) &

- Updated the device.mk to include it on the build:

PRODUCT_COPY_FILES += \
$(DEVICE_PATH)/init/init-gsi.rc:$(TARGET_COPY_OUT_SYSTEM)/etc/init/init-gsi.rc \
$(DEVICE_PATH)/init/treble-post-fs.sh:$(TARGET_COPY_OUT_SYSTEM)/bin/treble-post-fs.sh \
$(DEVICE_PATH)/init/treble-prop-handler.sh:$(TARGET_COPY_OUT_SYSTEM)/bin/treble-prop-handler.sh \
$(DEVICE_PATH)/init/disable-hw-overlay.sh:$(TARGET_COPY_OUT_SYSTEM)/bin/disable-hw-overlay.sh

- Updated init-gsi.rc to run this script as root after treble fs is complete:

on post-fs
exec - root -- /system/bin/treble-post-fs.sh
exec - root -- /system/bin/disable-hw-overlay.sh

EDIT: didn't work :-/ for some reason it's not being executed as root. Installed Magisk and ran the same script and it worked.
[Android Q&A, Help & Troubleshooting] vbhai:
Yeah, this is exactly the same issue I've been facing. It just does not want to run on boot. I'm guessing it's to do with SELinux issues or something.
[Android Q&A, Help & Troubleshooting] dferreira:
Smooth scrolling:

Dr. Denzil Ferreira :fedora: (@denzilferreira@techhub.social)

Attached: 1 video And we now have smooth scrolling 😎 #eink #lineageos #hisense #a9 #android

techhub.social
[Android Q&A, Help & Troubleshooting] dferreira:
https://xdaforums.com/t/how-to-run-a-script-at-every-boot-using-magisk.4454493/ this may work
[Android Q&A, Help & Troubleshooting] vbhai:
Well, Magisk scripts do not run until the phone is unlocked. I already tried an init.d application which runs scripts at boot. But add a screen lock, and the script won't run until the phone has been unlocked.
[Android Q&A, Help & Troubleshooting] dferreira:
We will figure it out 😉
[Android Q&A, Help & Troubleshooting] vbhai:
Phhusson's treble ROMs have lots of tweaks baked into them. The A14 ROM I shared already has those and in Settings > Phh Treble Settings > Misc Features, there is already an option to disable HW overlays. This persists on boot. But again, does not execute until the phone is unlocked.
[Android Q&A, Help & Troubleshooting] bigwigs:
Would adding monochrome theme settings from android 14 work? can we borrow some settings from pixel?
[Android Q&A, Help & Troubleshooting] vbhai:
This was an issue in the implementation of the accessibility service I believe. I think it is modifying brightness with another method? Using the default brightness slider in android does not cause this issue.

Also, I just reached out to phhusson on telegram and he told me how to implement the fix for persisting disabling hw overlays on boot. Just building the GSI image now. Shall update in a few minutes.
[Android Q&A, Help & Troubleshooting] dferreira:
How do you make it persistent? Please share 😉
[Android Q&A, Help & Troubleshooting] vbhai:
Are you using the GSI with phhusson's mods? I shared the link before. It has a setting like I mentioned before.

I'm experimenting with how to make it execute before unlocking now though.

Phhusson has an SU daemon I believe which runs scripts as superuser.

I just added the script in vndk.rc file. It works...but something else reverts the setting back. Need to check.
[Android Q&A, Help & Troubleshooting] dferreira:
I'm using Andy's LineageOS GSI -td branch build sources, which use some, but not all Phhusson's mods.
[Android Q&A, Help & Troubleshooting] vbhai:
I am using Andy's Lineage 21 GSI build myself. It does have the setting I am talking about.

Enabling it makes the setting persistent on boot but it does not execute before the lockscreen.

Playing around with /system/etc/init/vndk.rc:, added this to the on boot complete directive:

exec_background u:r:phhsu_daemon:s0 root -- /system/bin/service call SurfaceFlinger 1008 i32 1

It executes this and hw overlays are disabled by default on boot but something else turns them back on.
[Android Q&A, Help & Troubleshooting] vbhai:
Alright! There we go. Had to make sure that this line was added and the phhusson GSI setting was ALSO turned on! Have it working reliably now.

So, instructions:

Flash the ROM as usual:

1. Boot into fastboot

2. Run the command fastboot reboot fastboot

3. fastboot flash <name_of_image>.img

4. fastboot -w

5. fastboot reboot

Make sure you are setting this up with Vysor or Scrcpy initially.

After setting it up, go to Settings > Phh Treble Settings > Misc features > Disable HW overlays

Hardware overlays should be disabled reliably on boot now every time.

To get LTE, etc working fine, just go to Phhusson settings again, go to IMS features and then:

1. Install IMS APK for Qualcomm vendor

2. Reboot

3. Go back to the same settings and enable Request IMS network and force presence of 4g calling setting

4. Go to your SIM card/network settings and make sure that the mode is set to LTE instead of 3G.
[Android Q&A, Help & Troubleshooting] vbhai:
Uploaded the uncompressed version by mistake. Here is the compressed file:
[Android Q&A, Help & Troubleshooting] bigwigs:
does this include app-settings.apk? or we need to download it separately? also, do we need to install it or we can make it work without it?
[Android Q&A, Help & Troubleshooting] vbhai:
The accessibility service? No this does not include that. You can install that separately. The ROM works fine without that.
[Android Q&A, Help & Troubleshooting] bigwigs:
Ok, I’m working with this for a week or until @dferreira comes up with epd manager service similar to stock Hisense rom.

I’m using ponce rom that @vbhai shared yesterday. -

https://github.com/ponces/treble_aosp

Using this one: https://github.com/ponces/treble_ao...2.27/aosp-arm64-ab-gapps-14.0-20240227.img.xz

-Disabled dark theme

- enabled monochrome settings similar to various Android 14 videos on Google. - https://www.pocket-lint.com/how-to-turn-on-monochrome-theme-in-android-14/

- enabled themed icons settings

- enabled phhusson settings for ims and overlay. (Rebooting is not impacting settings somehow as I have disabled hardware overlay in both phhusson and developer settings)

- High contrast text enabled under display size and text

- smallest width in developer settings- 481

- android white logo - https://www.peakpx.com/en/search?q=android+white+logo
[Android Q&A, Help & Troubleshooting] bigwigs:
@vbhai - are u able to use fingerprint etc

i will try these settings later today - https://xdaforums.com/t/how-to-configure-a-treble-gsi-properly.4564191/
[Android Q&A, Help & Troubleshooting] vbhai:
Yeah! Everything is working fine. Also, I noticed you're using Ponce's GSI from the link I shared earlier. Try using the Lineage 21 I attached later. It reliably disables the hardware overlays on boot.

You can do it in your installed ROM as well by changing the files directly. I already documented what changes I made to make sure overlays stay disabled on boot.
[Android Q&A, Help & Troubleshooting] damianmqr:
I addressed these issues with brightness in the latest release here

Release v0.3 · damianmqr/A9PatchingService

Add possibility to not use temp control but rely on system for brightness (should be more stable but temperature can't be set) Remove brightness slider from regular release and use system read value.

github.com

Now you have two APKs to chose from

The one named app_release_no_temperature.apk relies on system for adjusting the brightness but has no temperature controls (so only refresh modes and clear with double tap) so screen dimming should work as expected in different scenarios.

The one named app_release.apk provides temperature control and prevents system from writing brightness directly and features only a slider for temperature, taking brightness from system. This may not work in all cases (for example the one where proximity sensor would dim the screen) but should be an overall improvement over last iteration.
[Android Q&A, Help & Troubleshooting] vbhai:
Awesome! Shall give this a shot. Possible to invert the double tap and the single tap functions? Would rather have the single tap clearing the screen- seems like that is the more used function.

Also, trying to create an overlay to enable automatic brightness in the GSI ROMs using these instructions:

How to create an overlay?

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

It did not enable automatic brightness for me sadly :(

Pulled the res values from the FrameworkCommon apk in system/product/overlay which seems to enable automatic brightness. Attached the config.xml I created according to the instructions.
[Android Q&A, Help & Troubleshooting] bigwigs:
1. Download and install the apk

2. Go to app info. Press 3 dots and choose "allow restricted settings".

3. Enable it in accessibility settings.

4. Grant root access when prompted.

5. Use e-ink button to launch menu and give "Display over other apps" permission when settings open

6. It should now be working, use e-ink button to confirm

when i go to step 2, i dont see 3 dots to choose "allow restricted settings"

im going settings ->apps -> then selecting ha9_comp_service.

is there any other way to access app info?
[Android Q&A, Help & Troubleshooting] bigwigs:
nvm this link helped me - https://support.google.com/android/answer/12623953?hl=en

thanks for taking time creating two versions of app.
[Android Q&A, Help & Troubleshooting] damianmqr:
You can try skipping this step, maybe you can already enable the service in accessibility menu, if it's not grayed out you should be good.

Also I do recommend using the version without temperature for now, there are still some weird bugs when using the other one. I might make it so you can either use a fully yellow or fully white backlight as a switch as that from testing seems more stable.

I might add a simple settings app later which will have a few customizations, for now I can just compile one with it swapped and put it in next release
[Android Q&A, Help & Troubleshooting] vbhai:
Place this in /system/product/overlay to enable automatic brightness, etc. Created this overlay for the Hisense based on the instructions provided here:

How to create an overlay?

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com
[Android Q&A, Help & Troubleshooting] vbhai:
Video showcasing @AndyYan 's Lineage 21 build running on the Hisense A9.

Hardware overlays disabled by default on startup. Thanks @phhusson

With the Hisense A9 product overlay- automatic brightness is working and the correct brightness and screen temperature values set for this phone. I attached the overlay before.

Always on display looks quite cool on this phone!
[Android Q&A, Help & Troubleshooting] bigwigs:
Is there any way to change how google sees the device? Currently, it is showing up as LG Nexus 5X when i'm using LineageOS GSI build from @vbhai

Yesterday, using android14 ponce build, it was identified as Builtt Group S60.

Damn, gave me scare ,if my account was hacked or what.
[Android Q&A, Help & Troubleshooting] vbhai:
Hahaha, you'd need to change the device fingerprint for this. But play integrity is broken right now, changing your fingerprint and passing play integrity checks is highly unlikely right now. You can look into a magisk module like hideprops to change your fingerprint but I don't think that would achieve anything really. Enjoy a Nexus 5X :P
[Android Q&A, Help & Troubleshooting] bigwigs:
When I was using hideprops with magisk, device was correctly showing up as HLTE556N.
[Android Q&A, Help & Troubleshooting] vbhai:
Thanks a ton for this. Works quite well from my initial testing.

Everything is looking great now!

The hisense is ready to be a daily driver!

EDIT: Though I would still recommend swapping the double tap and single tap functions :p

EDIT 2: With so much dev happening, we really ought to have a dedicated forum for the Hisense.
[Android Q&A, Help & Troubleshooting] vbhai:
Requested a forum here:

*** New Device Forum Requests ***

Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...

xdaforums.com

Upvote and reply there for it to get attention :P
[Android Q&A, Help & Troubleshooting] damianmqr:
Release v0.4 · damianmqr/A9PatchingService

Remove slider, make switch instead Improve structure

github.com

There's a new release, now the double and single click functionality has been swapped

The normal APK also has a toggleable switch instead of slider to enable "night mode" in which the backlight is yellow, which seems way more reliable.

When the toggle's disabled the system has full control over brightness so it should work just as well as the apk-release-no-temperature.apk. it shouldn't be needed, but I did provide it anyway just in case anyone prefers not to have the toggle on the bottom.
[Android Q&A, Help & Troubleshooting] vbhai:
Amazing! We can look into making this into a system service next.
[Android Q&A, Help & Troubleshooting] vbhai:
I thu

There is a bug with this version on boot. The screen is weirdly lit when the phone boots. Turning the toggle on and off again fixes it.

Also, I thought that the slider from the previous version worked quite well without any issues.

Attached the video.
[Android Q&A, Help & Troubleshooting] damianmqr:
I'll investigate this bug when I have a bit more time but it doesn't seem to happen on my device, I do have Hisense Hi Reader Pro, not A9, tho so maybe there's a difference?

I had weird bugs on the older version with temperature slider where the brightness values wouldn't adjust sometimes when using the system brightness slider, this doesn't happen for me anymore with the toggle and I only use either fully yellow or fully white light anyway. To make the slider work properly it would probably require some change to the OS itself and I haven't changed and compiled Android before so for now I will leave it as is.
[Android Q&A, Help & Troubleshooting] dferreira:
I have a working system service now 😉the API is different from Hisense EpdManagerService, so it’s not compatible with their .apks
[Android Q&A, Help & Troubleshooting] vbhai:
Plz share thx
[Android Q&A, Help & Troubleshooting] dferreira:
Will do, don’t worry. Just need to get some time to sit down on the desktop 😩
[Android Q&A, Help & Troubleshooting] bigwigs:
are u going to share apk or whole image with epdmanager service?
[Android Q&A, Help & Troubleshooting] biodbl:
I prefer the full rom
[Android Q&A, Help & Troubleshooting] bigwigs:
@vbhai - im having issues with phone call.

while making or receiving calls, I can hear other people but they have trouble hearing me. can anyone direct me to solution?
[Android Q&A, Help & Troubleshooting] bigwigs:
i have tried factory reset but no luck.
[Android Q&A, Help & Troubleshooting] vbhai:
Anyone know where to find the kernel source for this phone? 🤔
[Android Q&A, Help & Troubleshooting] vbhai:
Check out the phh treble settings. There are Qualcomm settings there specifically like a separate audio profile, etc. Turn those on.
[Android Q&A, Help & Troubleshooting] vbhai:
I had an issue where sound would be very high pitched during a WhatsApp call. Turned on the Qualcomm settings I was referring to in my previous post and enabled another setting which disabled stereo sound during VoLTE calls and everything worked fine.

Haven't faced any trouble so far where my mic isn't working.
[Android Q&A, Help & Troubleshooting] bigwigs:
no luck.