yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Inkbeard:
Hi folks!

First of all, a

huge

thank you to both @dferreira and @damianmqr for their outstanding contributions. I liked my Hisense A9 before, but I love it now!

I have a quick question and possible bug submission, I'm clearly new here so do usher me along the right path / procedure. I'm currently running Damian's latest build on LineageOS21, and everything seems to be working as intended except I randomly / intermittently get the spinning logo wheel and then it just kinda sits like that until I have to force it to restart by holding the power button.

Few notes:

- Clean flash (using -w)

- The AOD isn't working, but that's not a biggie for me as I know it's a bit tricky and everything's a WIP. But I've left the setting disabled in Phh Treble to force it on, just in case that matters

Attached image to illustrate the above.

Anyway, again I really appreciate the amazing work. I'll also give Denzil's ROM a go after testing Damian's for a bit.

UPDATE: Also going to try and capture report using the adb logcat command and see if anything sticks out!
[Android Q&A, Help & Troubleshooting] Kandwo:
How

Yes, I'm using your Gapps build of AOSP (couldn't get microG to work reliably with calls from telegram) with the eink center.

How do I properly call/activate the function from within tasker? I tried the previous way of "call service com.hisense.einkservices.broadcasts.EinkClearReceiver", but that wouldn't work.
[Android Q&A, Help & Troubleshooting] dferreira:
See how to issue broadcasts on Tasker. I had a typo:

com.hisense.einkservice.broadcasts.EinkClearReceiver
[Android Q&A, Help & Troubleshooting] farfromrefuge:
Can i install your eink center on Damian's build ? i could use that broadcast.

BTW does the eink button works for you when the screen is off? It does not here even if the settings are set for it the clear the screen
[Android Q&A, Help & Troubleshooting] Inkbeard:
Follow-up: I've not been able to consistently recreate the issue (and capture the logcat), but so far the only conclusion I've reached is it's something to do with using the fingerprint reader to lock / unlock the device.

Last night I disabled fingerprint unlocking and so far no random reboots / logo loops. I've switched the custom AOD feature back on and that's also worked without issue now.

Will keep seeing if I can recreate it without fingerprint unlocking, but that seems to have been the cause thus far!
[Android Q&A, Help & Troubleshooting] dferreira:
You can install it https://github.com/denzilferreira/vendor_hisense/releases

If I recall correctly, 1.5.1 on LOS21 leaves the overlay for Damian's overlay and you can use the broadcast to clear the screen. I think you will need to enable the accessibility service so that it can register the broadcast receiver. You won't be able to use it for setting apps speeds though.
[Android Q&A, Help & Troubleshooting] dferreira:
Some more snaps using Gcam on Hisense A9!
[Android Q&A, Help & Troubleshooting] biodbl:
Nice quality! What country?
[Android Q&A, Help & Troubleshooting] dferreira:
Tallin, Estonia 😁 came here for a day on the ferry from Helsinki
[Android Q&A, Help & Troubleshooting] Kandwo:
I've been trying to find how to do it, but searching for Tasker and broadcast commands seems to return stuff to do with radio and other broadcasting stuff. 😅

What's the adb command to trigger that function? :)
[Android Q&A, Help & Troubleshooting] dferreira:
Sending intent to BroadcastReceiver from adb

I've got BroadcastReceiver class: public class IntentReceiver extends BroadcastReceiver { final String tag = "Intent Intercepter"; @Override public void onReceive(Context context, In...

stackoverflow.com

This should do it @Kandwo:

adb shell am broadcast -a com.hisense.einkservice.broadcasts.EinkClearReceiver
[Android Q&A, Help & Troubleshooting] Kandwo:
Unfortunately, that doesn't do it. Neither in adb through my computer nor in Tasker.

adb shell am broadcast -a com.hisense.einkservice.broadcasts.EinkClearReceiver
Broadcasting: Intent { act=com.hisense.einkservice.broadcasts.EinkClearReceiver flg=0x400000 }
Broadcast completed: result=0
[Android Q&A, Help & Troubleshooting] dferreira:
Did you enable the accessibility service?
[Android Q&A, Help & Troubleshooting] Kandwo:
Yes, both for Tasker and AutoInput.

Maybe it would be easier to try to emulate pressing the eink button to achieve the screen refresh? Do you know the code for the button (it doesn't seem to be 440 as in the stock ROM)? (Though pressing it doesn't always work for me within apps - sometimes it refreshes, sometimes nothing happens. The double press to set the speed seems to always work, however.)
[Android Q&A, Help & Troubleshooting] dferreira:
I meant the Eink Center one too!
[Android Q&A, Help & Troubleshooting] Kandwo:
Yes, of course! :)
[Android Q&A, Help & Troubleshooting] benru89:
@dferreira is there a way to go to the vanilla with microg from the gapps version without wiping everything?
[Android Q&A, Help & Troubleshooting] dferreira:
Weird. I'm away from the laptop at the moment but will get back to you when I do. The broadcast should work. Someone here has been using it!
[Android Q&A, Help & Troubleshooting] farfromrefuge:
@dferreira @damianmqr i just realized my "battery info" was not working on my a9. I use Damian's build with latest LOS 14 (from 3 weeks ago).

The battery usage screen always says battery usage will be available in a few hours once fully charged.

So i thought i would use BBS to get detect battery drain.

But it does not work either it reports an error "BatteryInfo Service could not be contacted".

Do you have an idea? Does any of them work for you?
[Android Q&A, Help & Troubleshooting] dferreira:
Not sure if it will work, there are many settings that are used by the Gapps and I'm not confident it will all work like that.
[Android Q&A, Help & Troubleshooting] dferreira:
Working on Ponce's Android 14 build. Maybe something broken on LOS21. There has been a lot of changes there. That's why I went with AOSP based build. Been running it since release, been happy with how it has been. Only thing to improve is the AOD to invert the colors and vibration working (wip).
[Android Q&A, Help & Troubleshooting] idonotbelonghere:
Where's the best place to add additional tweak requests to the list? ☺️

LOS20 had a rotate 180° option which was great when reading (volume button functions also flipped when the phone was upside down).
[Android Q&A, Help & Troubleshooting] farfromrefuge:
I do get that screen as you. But do you see per app battery usage? This is where i dont get anything
[Android Q&A, Help & Troubleshooting] Kandwo:
I appreciate it! I hope you enjoy your travels meanwhile :)

AOD (and the non-AOD black lockscreen) also seem to constantly emit a low level of light. Maybe there's already a fix for that? And don't forget a working nightlight slider ;)

I really appreciate the effort! Finally I can change the language of the OS and use KISS as my launcher with a working "recent app" functionality.
[Android Q&A, Help & Troubleshooting] dferreira:
Just tested. The correct command is:

adb shell am broadcast -n com.hisense.einkservice/.broadcasts.EinkClearReceiver

@Kandwo about the light when off, working on fixing that and inverting the colors too.
[Android Q&A, Help & Troubleshooting] dferreira:
Yeah, same here. Looks like something is missing on AOSP/Lineage for the Battery manager... my guess it's been Googled (requires some additional package)
[Android Q&A, Help & Troubleshooting] Skematica:
Meh. :sneaky:

I unlocked my bootloader successfully and then went to flash LOS 21. While flashing "fastboot flash system system.img" it reported the famous "invalid sparse header" error. I was able to proceed past that with more attempts and then had, IIRC, "remote: partition not found" error. I then exited fastboot thinking I could get back to it with a hardware key combo. Woops.

Now I've got a boot loop into recovery mode. When I go to wipe data menu it only has a cancel button. There is no wipe data button. I can boot into what appears to be fastboot menu but it's a black screen.

Am I firmly in EDL territory with the cable and all that or is this recoverable w/o a cable?

Edited to add: adb reboot bootloader reports "error:device unauthorized". I trashed my keys and killed/restarted adb server to no avail.

Final Edit: Fixed with a bit of mucking around blindly in the pitch black fastboot menu. Somehow recovered OS and kept unlocked bootloader intact! Now I'm off to buy a lotto ticket...
[Android Q&A, Help & Troubleshooting] dferreira:
We should update the guide. You are not the first one that faces this. The "adb reboot bootloader" should only be used for unlocking the bootloader. For flashing should occur on adb reboot fastboot (the black menu). This is because we have a AB device and the partitions only are setup on fastbootd (the black menu).
[Android Q&A, Help & Troubleshooting] dferreira:
Yesterday I fixed the light being on when locking the screen (the minimum brightness is 0, was 17 before). I tried as well to reverse the AOD colors but for some reason it did not work. I'll keep poking. The vibration, for some reason still says there is a name collision, so will keep digging. I feel I'm close.
[Android Q&A, Help & Troubleshooting] R0W3Y:
Do you mean on

https://www.reddit.com/r/hisenseA9/comments/1diqvv6
?

Step 5 is already Reboot your A9 into fastbootd mode using 'adb reboot fastboot' before flashing in step 6. I've used this way a few times and it's always been ok for me flashing from the black menu screen. But there have been a few comments that other people have errored here, then used 'fastboot reboot fastboot' instead:

https://www.reddit.com/r/hisenseA9/comments/1diqvv6/_/l9xzkht

https://www.reddit.com/r/hisenseA9/comments/1diqvv6/_/lb7z23z

So about a week ago rather than change the main guide steps I added a note to 6.2 for people with the alternative incase someone is erroring here.
[Android Q&A, Help & Troubleshooting] Kandwo:
Thanks! Everything works great now in Koreader and other apps! My mobile reading habits have been saved! :D

Another thing I noticed is that Revolut is missing from Play Store. Does this have something to do with missing certificates for this ROM? I remember there was something that needed to be done after rooting on the stock ROM. Anything I can do in Magisk or does it require an update to the ROM itself?
[Android Q&A, Help & Troubleshooting] Inkbeard:
Running your latest ROM right now - super excited for the updates!
[Android Q&A, Help & Troubleshooting] dferreira:
Yes, Google now requires ROMs to be signed as well for the device certification to pass. You can sideload it from apkmirror for example meanwhile.
[Android Q&A, Help & Troubleshooting] dferreira:
People are terrible at following guides 😜 maybe it's the GitHub guide that needs an update. As this thread has exploded, people skip pages and then miss info here and there. Maybe we should link the tutorial to our signatures here on XDA so that no matter what page we are in, if they see one of our signatures, they would know where to go?
[Android Q&A, Help & Troubleshooting] R0W3Y:
'People are terrible at following guides' True, me included first time around. I think not following the guide closely enough is the most common issue but I'm sure it can keep improving from feedback.

I've added a link to my signature...
[Android Q&A, Help & Troubleshooting] dferreira:
Will add to mine once on the desktop 👍
[Android Q&A, Help & Troubleshooting] farfromrefuge:
I dont think it is due to AOSP/LOS missing code. It works on my other LOS devices even on 14.

Plus BBS is known to work on LOS 21. I think something is missing either in our builds, or something makes the battery service fail on our devices. Will take a look at my logcats
[Android Q&A, Help & Troubleshooting] farfromrefuge:
@dferreira i found the related error in the logcat:

BatteryStatsProxy: An exception occured in BatteryStatsProxy(). Message: Didn't find class "com.android.internal.os.BatteryStatsImpl" on path: DexPathList[[zip file "/data/app/~~xNEMDX_t_O86ffnB8I5v4w==/com.asksven.betterbatterystats-CnL4OeRaB1jMLpF_PLC-EQ==/base.apk"],nativeLibraryDirectories=[/data/app/~~xNEMDX_t_O86ffnB8I5v4w==/com.asksven.betterbatterystats-CnL4OeRaB1jMLpF_PLC-EQ==/lib/arm64, /system/lib64, /system/system_ext/lib64]]

So we are missing com.android.internal.os.BatteryStatsImpl. I need to find where this is defined and why we dont have this

EDIT: i was wrong this is a BBS issue ! https://github.com/asksven/BetterBatteryStats/issues/929

I did go back to my other android 14 devices and i do see per app battery usage from system settings. So we do have an issue here. For now the logcat does not say anything for this
[Android Q&A, Help & Troubleshooting] einkys:
Thanks for the continued work, @dferreira ! Can I ask if it is possible to change the brightness level when the night light is turned on? I can not figure out if I am missing something.

Thanks!
[Android Q&A, Help & Troubleshooting] seijix0:
I am getting an error message at the step for unlocking. I am trying to do it on my Hisense Touch.

./fastboot Hisense unlock

fastboot: usage: unknown command Hisense

Please help. Thank you.
[Android Q&A, Help & Troubleshooting] dferreira:
Thanks for looking into it. I really appreciate you!
[Android Q&A, Help & Troubleshooting] dferreira:
It is possible, just haven't had time to solve this 🤪 summer vacation and kids at home makes it hard to sit at the desk 😅
[Android Q&A, Help & Troubleshooting] dferreira:
You need to use my fastboot binary because I added support for this command. You can get it here: https://drive.google.com/drive/folders/1jOT7YGWVHFiEt8eH_QLT4FtCIuvLMv-Y
[Android Q&A, Help & Troubleshooting] seijix0:
I have tried using your fastboot binary and I am still getting the same error message. Is the something that I missed?

My Terminal Window:

~/Downloads/linux-x86(4)/linux-x86/bin$ fastboot Hisense unlock

fastboot: usage: unknown command Hisense
[Android Q&A, Help & Troubleshooting] treff89:
maybe you need to try "./fastboot Hisense unlock" or "sh fastboot Hisense unlock" since the normal fastboot's in your system's $PATH?
[Android Q&A, Help & Troubleshooting] seijix0:
Thank you so much it worked! I am still very new to this as it's my first time rooting any sort of device. thank you
[Android Q&A, Help & Troubleshooting] Skematica:
I'm curious if flashing LOS to the device will increase signal coverage or do i need to fiddle with basebands independently? do you happen to know?

Sent from HLTE556N using ReLabs
[Android Q&A, Help & Troubleshooting] dferreira:
You are missing a dot :) ./fastboot inside that folder. Otherwise it will use your PATH fastboot!

Edit: just saw you got help 😀
[Android Q&A, Help & Troubleshooting] dferreira:
Independently. LOS doesn't change the modem partition, only system.
[Android Q&A, Help & Troubleshooting] shanytc:
It works only for L2037.6.04.06.00 no?
[Android Q&A, Help & Troubleshooting] Sheep888:
Yes it works, with wifi as well! I didn't use an Edl cable. If i understood Renate properly thats needed if you brick your device.
[Android Q&A, Help & Troubleshooting] shanytc:
So basically it works with either firmwares?
[Android Q&A, Help & Troubleshooting] Segnaro:
An EDL cable is optional but recommended.
[Android Q&A, Help & Troubleshooting] Kandwo:
I followed the instructions in post #175 using the boot.img from the latest firmware from post #192. It worked like a charm. I now have Google Play Store installed.

There's something weird going on, however. When searching for Brave (the browser) it doesn't turn up in Play Store. When trying to install from brave.com it redirects to Play Store, which tells me "Your device isn't compatible with this version."

Does anyone know why this is? I didn't get this error after rooting my A5 Pro. Is something messed up with the device ID or does it report the wrong Android version or something?

EDIT: An additional problem is that the "Latest apps/open apps" functionality still doesn't work in 3rd party launchers. Is there a way to solve that?
[Android Q&A, Help & Troubleshooting] dferreira:
You can install using APK mirror 😁
[Android Q&A, Help & Troubleshooting] shanytc:
When I do 'adb reboot bootloader'

I am getting a white screen with a "FastBoot Mode" on the top.

what now?
[Android Q&A, Help & Troubleshooting] TrippyPrimate:
If I back my phone then root and load the backup on after will this mean i can keep my data and apps?
[Android Q&A, Help & Troubleshooting] Threedollarbridge:
It should be fine, but I haven't personally tested it. Try using Hisense's backup app.
[Android Q&A, Help & Troubleshooting] TrippyPrimate:
Okay thanks ill give it ago.
[Android Q&A, Help & Troubleshooting] Threedollarbridge:
Though Brave doesn't show up in Google Play, I can confirm that it works. You should maybe try downloading it through APKMirror or on a secondary App Store of your choice.
[Android Q&A, Help & Troubleshooting] shanytc:
Whoho I got it rooted with google play. Well done guys. You are amazing.
[Android Q&A, Help & Troubleshooting] Segnaro:
You can get the latest apk from their github, if you want an official source.

Release Release v1.67.123 (Chromium 126.0.6478.126) · brave/brave-browser

Release v1.67.123 (Chromium 126.0.6478.126) Android Pick the APK suitable for your device's architecture. iOS brave-core-ios.* contains Brave for iOS. Linux DEB and RPM packages attached below, det...

github.com
[Android Q&A, Help & Troubleshooting] neoveau:
Hey everyone, I managed to root the phone! I had issues at first when using the factory boot.img since I was on the latest firmware. With the updated boot.img that had been shared earlier, I downloaded, patched and flashed it, which fixed the problems I was having with Wi-Fi, calling, media playback, and auto brightness adjustment.

I am now trying to install Google Play Services, but I'm having trouble with getting notifications to work. I firstly tried installing MicroG with LSPosed and FakeGapps signature spoofing, but I couldn't get it to work. I then tried to install [Magisk]LiteGapps_arm64_11.0_v2.5_official.zip, as it had been mentioned here earlier, but I had no luck with getting notifications working with any of the Apps which I installed.

If anyone has been successful with getting notifications to work reliably, I would greatly appreciate any guidance. Thank you :)

Another huge thanks to @dferreira, @Segnaro, and @Renate for your hard work. I'm honestly amazed at what you've accomplished and I am incredibly grateful for your efforts.
[Android Q&A, Help & Troubleshooting] TrippyPrimate:
my terminal is just saying waiting for any device after doing ./fastboot Hisense unlock

any idea how to fix? Please
[Android Q&A, Help & Troubleshooting] neoveau:
Have you installed the Google USB Driver? If you're on Windows, you can find it here https://developer.android.com/studio/run/win-usb

Once you have that downloaded, go into Device Manager and the Hisense A9 should show up under Portable Devices. Right click on the device and click on Update Driver Software. Select Browse my computer for driver software and click next. Click on Browse and locate the USB driver folder, and then hit next to install the driver.

You can then try running .\fastboot devices to list the devices available to fastboot. If it shows up, you should be able to run the previous command just fine.
[Android Q&A, Help & Troubleshooting] Segnaro:
Settings - Notifications & Status Bar - App Notifications

Check that your apps are enabled.
[Android Q&A, Help & Troubleshooting] TrippyPrimate:
my phone still just showing fast boot mode so in device manager it just says android under the other devices tab so do i need to get out of fastboot before i look for driver updates if so how do i leave fast boot safely.
[Android Q&A, Help & Troubleshooting] neoveau:
No, I did this while my phone displayed "fastboot mode" on the display. If the Android device in device manager shows a yellow warning icon, it needs the usb driver before you can continue.
[Android Q&A, Help & Troubleshooting] Inkbeard:
So, annoyingly I've still gotten the occasional random crash / reboot on both ROMS after testing each for a few days. The annoying part is I can't seem to reproduce it consistently -- it just happens out of nowhere: it'll reboot and show the individual ROM's logo booting and then I have to get it back on with the power button. Tonight I switched to the LOS21 and just let it left it plugged in running the logcat for a while (didn't install apps, just did the basic setup) then ran a "adb logcat --buffer=crash" to try and see what I could get (attached).

I've got the 6GB ram, 128 GB internal A9.

Excuse my ignorance, but is that the best way to get something for review? Is there a more accurate way to capture a crash event from Android? Let me know what else I should do (or what will be more helpful besides a huge logcat dump?!) and I'll try to capture some more tomorrow from either ROM, determined to get to a more stable solution, but totally appreciate the progress so far! 😁
[Android Q&A, Help & Troubleshooting] aws92:
Hi All, fantastic work on this project. I am currently working on @damianmqr ROM. Everything is working fine except for GPS - I cannot find a way around this at all. Same thing occurred with the vendor ROM too. Google Maps will grab my location initially, but will thereafter report 'GPS signal lost' and search for a GPS signal. I have switched on 'Force Full GNSS measurements' via developer settings to no avail. Checking the GPS signal via GPS Test app, which gives a 'GNSS status' as 'No Fix'. Work for me on my other phone fine... Appreciate any help you may be able to offer.
[Android Q&A, Help & Troubleshooting] Skematica:
Will do. I've got a couple of B41/66 towers in my area but I'e only got SOS or EDGE coverage. Thinking maybe i can fiddle around in the guts and see if i can greaten my chances of getting at least 3G. Thanks for sharing your extensive knowledge in this community!

Sent from HLTE556N using ReLabs
[Android Q&A, Help & Troubleshooting] dferreira:
Just out of curiosity, did you upgrade to the latest stock prior to unlocking and flashing a custom ROM? I do not experience random reboots like that. Could be an actual hardware problem with the device, memory chips do go bad.
[Android Q&A, Help & Troubleshooting] dferreira:
That's odd. I've navigated and driven without issues. Can this be just where you live and coverage there by satellite?
[Android Q&A, Help & Troubleshooting] aws92:
Nah, it's great for coverage over here, major city in the UK and not had issues prior with any other device (including other non-UK imported phones). The issue was present with the vendor ROM with google services preloaded. I have been in touch with the AliExpress vendor (Chosen Ereader), and they suggested a factory-reset and then return to them for a replacement if that does not work. My only issue is, I do not know how to go back to the vendor ROM with google services now! @dferreira - did you help out the vendor with this and is there any way to return the ROM back to original state? Thanks for any help/guidance you can provide!
[Android Q&A, Help & Troubleshooting] R0W3Y:
I'm on the same ROM, carrier (EE), and area (UK). I rarely use maps on my a9 but they seem ok. Running GPS test I'm getting '3D fix' as GNSS Status.

Regarding crashing, I've actively used LOS21 for a few hours a day for a few months and don't think the OS has ever crashed and rebooted itself (HRP, or 6GB A9).
[Android Q&A, Help & Troubleshooting] Inkbeard:
I don't remember if I did upgrade the stock before unlocking and flashing the ROM, so if that's a potential cause I can try and retrace my steps.

In that case, should I attempt to reflash to stock, upgrade to latest stock and repeat the process?

I guess that way I'll know if it's a hardware issue or me just being a muppet and missing a vital step 😂