yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] bigwigs:
@dferreira

Based on https://medium.com/@daltonfury42/building-lineageos-for-your-device-a7d26ab50549 , below are 4 things needed to build Lineage OS for unsupported devices

Lineage Source — This is the android source code from Lineage OS project.

The kernel source for device — It’s released by the manufacturer, thank you, Xiaomi.

The Device Tree — A device tree is the description of a particular hardware to the OS/Kernel

Device Vendor files. — The proprietary binary drivers from Xiaomi

Did you get kernel source code for Hisense A9 too from Chose E-Reader Store or just binary files?
[Android Q&A, Help & Troubleshooting] vbhai:
He was referring to building the Lineage GSI, kernel source is not required for that.
[Android Q&A, Help & Troubleshooting] bigwigs:
Ok, thanks.

Can you provide more details of GSI ? How does it replace the need of kernel source?
[Android Q&A, Help & Troubleshooting] bigwigs:
For those who are interested in GSI - https://developer.android.com/topic/generic-system-image
[Android Q&A, Help & Troubleshooting] bigwigs:
If anyone is interested, Free Android Internals Course - https://8mantech.thinkific.com/courses/android-internals

WIll teach you Android 12 Internals and build Android Cuttlefish VM. ( on my todo list to learn)
[Android Q&A, Help & Troubleshooting] bigwigs:
Good news, even after IMEI mess due to LTE Band changes, it seems IMEIs are intact. As i was able to activate new number on 2nd sim of the phone.

So, i guess there is something happening at hisense library level where imei information is not visible via UI and somehow even with QXDM and QSPT.(weird).

As long it works, all good :)
[Android Q&A, Help & Troubleshooting] ntindle:
How'd it go?
[Android Q&A, Help & Troubleshooting] zxczxc4:
Thanks Renate - I've just played around a little with that a9epd.jar you uploaded, trying to make a little app that can call some methods in the epd service, but logcat's showing errors when I try to actually call one of the methods.

Something about a blacklist, and your points 1 and 2 mention that :D

Any advice on how can we remove the blacklists in within framework.jar? Searching online, I couldn't find much. I guess it involves decompiling the framework jar, making a few changes(?), and then recompiling and replacing the file on the system?

If that's true, I guess that means it's not really possible to make an app that interacts with the service on a stock/non rooted rom?

I imagine it's possible to copy/reimplement the functionality the services use, in your app, and thus not needing to reference the original service anymore?

To be transparent, my goal is to try to make an app that sets the shutdown wallpaper / image when powered off, using the updateShutdownWallPaper method.

And hopefully being able to use it on the future LineageOS rom.

I'm not sure / don't want to be demanding and expect that dferreira's rom will support this, and so wanted to try to do it myself :)
[Android Q&A, Help & Troubleshooting] Renate:
Isn't there a stock shutdown wallpaper already? Can't you just locate it and replace it?

Yes, you'll probably need to delete a few blacklist in framework.jar and services.jar.

The good part is since they are jars (and not apks) you don't have to worry about signing.

The errors in logcat should be specific enough for you to find where to fix.
[Android Q&A, Help & Troubleshooting] zxczxc4:
Ah yes, that makes sense! Thanks

Thinking a bit more, maybe the method in the epd service that I'm trying to call only literally copies an image somewhere, and the actual code I'm interested in is how the android shutdown event is hooked and how the image is then drawn to the screen.

(Assumption on how it works)
[Android Q&A, Help & Troubleshooting] bigwigs:
Hi @Renate ,

I'm trying to follow ur post :- https://xdaforums.com/t/decompile-kernel.1711643/post-88439087

and trying to decompile kernel from latest-boot.img from @dferreira 's google drive.

I'm getting error trying to use kallsyms /b256 /a64 /l0 kernel kernel.sym - "Could not find names" Tried couple of combinations with /b and /a. Still no luck.

So, question i have is, what is command to decompress kernel, using imgutil., if the error is due to file not being decompressed.

thanks!
[Android Q&A, Help & Troubleshooting] Renate:
Link for the image you're talking about?
[Android Q&A, Help & Troubleshooting] bigwigs:
here link to kernel image that got created using imgutil - https://drive.google.com/file/d/1Rv4pTLs2eC_ZFsBr8suuNTnHIignbFdO/view?usp=sharing

link to boot image - https://drive.google.com/file/d/1enAcvyd_Ixvt_zOWomDov74BddSGAP44/view?usp=sharing
[Android Q&A, Help & Troubleshooting] bigwigs:
Weird it is my google drive.

try this link - https://drive.google.com/drive/folders/1fhx-5ERUJEzVI3SppzDw7br0hdpaYhgU

This is original link.
[Android Q&A, Help & Troubleshooting] bigwigs:
attached, just in case
[Android Q&A, Help & Troubleshooting] Renate:
I'm just zipping along here at a speed of 60.

60 Mbps?

No, 60 kbps. :(
[Android Q&A, Help & Troubleshooting] Renate:
imgutil latest-boot.img /x payload
kallsyms payload /b256 /r /m64 kernel.sym

(kernel = raw kernel/dtb, payload = uncompressed kernel)
[Android Q&A, Help & Troubleshooting] bigwigs:
thanks!

is this normal for all boot.img? or this is specific to hisense?

i.e. (kernel = raw kernel/dtb, payload = uncompressed kernel)
[Android Q&A, Help & Troubleshooting] Renate:
Many kernels today are gzip'ed, some lz4'ed, some uncompressed.

Version 0 images had the DTB following the kernel (without any explicit size).

Old images even had a stub for ungzipping, a payload and a footer.

Any wacky thing you can think of has been found in boot images.
[Android Q&A, Help & Troubleshooting] zxczxc4:
Maybe common knowledge, but once rooted, I'd recommend using the Noto Emoji font - it's black and white, as well as being opensource!

Noto Emoji - Google Fonts

Noto Emoji is an open source font that has you covered for all your emoji needs, including support for the latest Unicode emoji specification. It has multiple w

fonts.google.com
[Android Q&A, Help & Troubleshooting] andruyd:
Does this have a discrete DAC for audio hires|hifi music playback?
[Android Q&A, Help & Troubleshooting] zxczxc4:
Yes I have read online that the A9 has the ES9318 chip.

(Not that I can find a lot of details about it though!)
[Android Q&A, Help & Troubleshooting] bigwigs:
There is an option for Hi-Fi under sound & vibration in settings. Though one under developer settings is disabled.
[Android Q&A, Help & Troubleshooting] andruyd:
How's the battery life? Does it have fast charge?
[Android Q&A, Help & Troubleshooting] bigwigs:
I haven't use the phone fulltime but battery life looks good.

About fast charge, it did complain when i used my ipad mini charger about charging slowly, so i guess it does support fast charge, i guess.
[Android Q&A, Help & Troubleshooting] zxczxc4:
I saw the same until I connected some bluetooth headphones, then the checkbox was enabled.

After disconnecting the headphones it was disabled again :)

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] strann0:
I have the Hi Pro model and battery is nothing special. But I guess screen hasn't been the Android's biggest battery issue for a long long time, so e-ink won't probably improve it much. Even the LTPO screens don't make much difference.
[Android Q&A, Help & Troubleshooting] bigwigs:
looks like @dferreira is testing more rigorous than Hisense b4 doing a release ;)
[Android Q&A, Help & Troubleshooting] zxczxc4:
I tested out APatch (v 10474), when flashing the boot image it patched I got a bootloop.

Magisk v27.0 worked fine (as expected)
[Android Q&A, Help & Troubleshooting] dferreira:
🤣 sadly no. My previous attempt did not work and I’ve been super busy at home and work. I’ll see if I can make some progress this weekend!
[Android Q&A, Help & Troubleshooting] bigwigs:
Let me know if I can help with anything. Have a long weekend here
[Android Q&A, Help & Troubleshooting] TrippyPrimate:
Its okay your doing gods work imo, I'm patiently waiting impatiently, but seriously keep up the good work its really apricated :).
[Android Q&A, Help & Troubleshooting] dferreira:
Another attempt is building at the moment. I made a few discoveries as I was exploring existing system services and fixes along the way.

*SystemServer.java*

This class is responsible for the boot process of Android. I was missing importing the package com.android.server.EpdManagerService, which led me to understand that I need to place the smali files in the correct place otherwise it won't find it and fails to start the service. This is now fixed.

*EpdManager*

This is an Android app, that needs to be installed with system privileges and talks with EpdManagerService and is supposed to be in the vendor folder so it's placed, installed and available for apps to interface with. I've removed all the blocklist keyword so that I can then use this service to build a quick tile application later to control the speed modes, change color temperature and so on.

I will not give up until I get this working. If you'd like to donate to compensate for my efforts, you can do so with Cardano's ADA. You can get ADA with Coinbase or other crypto exchanges and send it to this address:

addr1qx0lcalsuxcl37zsvstppftaqm2f2dpyxdsc2jwmvacjmwjufkfpj0rgq7cahq5jwkpzky80j9cw3gpkue0tk8lw04fsq9ejft
[Android Q&A, Help & Troubleshooting] dferreira:
I just had a breakthrough: I was able to successfully recover the source code in Java from the smali files using JADX! Amazingly, Hisense did not obfuscate their code, so success rate is 100% and fully transparent code now. This is HUGE.
[Android Q&A, Help & Troubleshooting] bigwigs:
Cool, when u get chance, can u post it to drive or GitHub? I want to see if their ui code has anything to do with efs partition being blocked.
[Android Q&A, Help & Troubleshooting] dferreira:
I don’t have their UI code, only the service that interfaces with the eink screen hardware 👀

The build failed. However now with the actual Java files, I can see what line, what the issue is and I can fix them. There are some references to some apps and classes that don’t exist on Lineage, so I’ll have to dig them out of the stock ROM or completely get rid of that code if it’s not important. A few of the errors are about the launcher app. Progress!
[Android Q&A, Help & Troubleshooting] dferreira:
So... I found another class we need :) T1000Service, which writes and reads from the kernel itself! And looking at the code... looks like we can just use this class to change the eink screen via the kernel itself! Looking at the code, it only has Android APIs which means I could get away with just using T1000Service + an Android app to read and write to "/sys/devices/platform/soc/soc:ap-apb/70400000.i2c/i2c-1/1-0006/mode"
[Android Q&A, Help & Troubleshooting] Renate:
Interesting. Could you cat the uevent, please?
[Android Q&A, Help & Troubleshooting] zxczxc4:
I was going to but interestingly, there's no `soc:ap-apd` directory for me in `/sys/devices/platform/soc`:

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] bigwigs:
Here is good repository for scripts to backup/restore and other things u can do with phone-

Adebar

Android DEvice Backup And Report, using Bash and ADB.

codeberg.org

using one of scripts - getapk - you get all apks from phone or u can ask for user or system apks.

attaching screen shot of com.hmct.einksettings.apk and apk file itself. Also, attaching some hcmt apks. let me know if u want any other apks.
[Android Q&A, Help & Troubleshooting] Renate:
Eh, how about this (but 1-0006):

# cd /sys/bus/i2c/devices/6-0038
# cat uevent
DRIVER=lm3630a_bl
OF_NAME=lm3630a
OF_FULLNAME=/soc/i2c@c1b6000/lm3630a@38
OF_COMPATIBLE_0=onyx,lm3630a
OF_COMPATIBLE_N=1
MODALIAS=i2c:lm3630a

(I'm inordinately fond of LM3630As.)
[Android Q&A, Help & Troubleshooting] bigwigs:
As suspected there is some weird IMEI Display code in com.hmct.imeidisplay.apk.

Looking at this apk and other apks with baidu libraries all over similar to google with location, wonder what location info is being passed to baidu.

Can't wait to get rid with atleast these apks. Now we don't know what the hell is in kernel itself :)
[Android Q&A, Help & Troubleshooting] bigwigs:
don't have device - 1-0006. here is screenshot of list of devices
[Android Q&A, Help & Troubleshooting] Renate:
Eh, that's only a popup info dialog.

You should look if Util.getMeidAndImei() is used elsewhere.

Well, then whatever referred to it was dead code.

An I²C interface would surprise me as most Eink is a direct connection to the SoC (except for Boox Super Refresh).

I don't mean the actual image data but modes.

Edit: How about:

# cd /sys/bus/i2c/devices
# for f in *00*; do echo $f; cat $f/uevent; done

(Please just copy/paste as text.)
[Android Q&A, Help & Troubleshooting] bigwigs:
Well, the reason i said is because , the UI doesn't show anything whenever i try to look at System-> About Phone -> Status.

It just refreshes to About Phone screen. (this behavior is after rooting). Before rooting, it would go to Status screen but all information would be displayed as Unavailable.

Here is code which is interesting:-

if (operatorStr != null && (PROP_OPERATOR.equals(operatorStr) || Util.PROP_OPERATOR_TELCEL.equals(operatorStr))) {

this.mDisplaySVStr = Util.getImeiSV(this);

this.mDisplayStr += "\n" + this.mDisplaySVStr;

}

Below are hardcoded values:-

public static final String PROP_OPERATOR = "IUSACELL";

public static final String PROP_OPERATOR_TELCEL = "Telcel"; (this is in Util class)

And in util class, there is all this custom code to view IMEI. Not sure why would one need the same.

Doesn't Android provide all this capability. Instead they are using all this custom code functionality.
[Android Q&A, Help & Troubleshooting] bigwigs:
here is output of the above script-

***************************

HLTE556N:/sys/bus/i2c/devices # for f in *00*; do echo $f; cat $f/uevent; done

0-000f

DRIVER=tc358767

OF_NAME=tc358767

OF_FULLNAME=/soc/i2c@4a80000/tc358767@0F

OF_COMPATIBLE_0=dz,tc358767

OF_COMPATIBLE_N=1

MODALIAS=of:Ntc358767T<NULL>Cdz,tc358767

0-0035

DRIVER=ktd3137-bl-4

OF_NAME=ktd3137

OF_FULLNAME=/soc/i2c@4a80000/ktd3137@35

OF_COMPATIBLE_0=ktd,ktd3137-4

OF_COMPATIBLE_N=1

MODALIAS=of:Nktd3137T<NULL>Cktd,ktd3137-4

0-0036

DRIVER=aw99703-bl-2

OF_NAME=aw99703-bl-2

OF_FULLNAME=/soc/i2c@4a80000/aw99703-bl-2@36

OF_COMPATIBLE_0=awinic,aw99703-bl-2

OF_COMPATIBLE_N=1

MODALIAS=of:Naw99703-bl-2T<NULL>Cawinic,aw99703-bl-2

0-0048

DRIVER=fp9929a

OF_NAME=fp9929a

OF_FULLNAME=/soc/i2c@4a80000/fp9929a@48

OF_COMPATIBLE_0=fiti,fp9929a

OF_COMPATIBLE_N=1

MODALIAS=of:Nfp9929aT<NULL>Cfiti,fp9929a

0-005a

DRIVER=haptic_hv

OF_NAME=haptic_hv

OF_FULLNAME=/soc/i2c@4a80000/haptic_hv@5A

OF_COMPATIBLE_0=awinic,haptic_hv

OF_COMPATIBLE_N=1

MODALIAS=of:Nhaptic_hvT<NULL>Cawinic,haptic_hv

1-000c

DRIVER=i2c_pmic

OF_NAME=qcom,smb1355

OF_FULLNAME=/soc/i2c@4a84000/qcom,smb1355@c

OF_COMPATIBLE_0=qcom,i2c-pmic

OF_COMPATIBLE_N=1

MODALIAS=of:Nqcom,smb1355T<NULL>Cqcom,i2c-pmic

1-0035

DRIVER=ktd3137-bl-3

OF_NAME=ktd3137

OF_FULLNAME=/soc/i2c@4a84000/ktd3137@35

OF_COMPATIBLE_0=ktd,ktd3137-3

OF_COMPATIBLE_N=1

MODALIAS=of:Nktd3137T<NULL>Cktd,ktd3137-3

1-0036

DRIVER=aw99703-bl-1

OF_NAME=aw99703-bl-1

OF_FULLNAME=/soc/i2c@4a84000/aw99703-bl-1@36

OF_COMPATIBLE_0=awinic,aw99703-bl-1

OF_COMPATIBLE_N=1

MODALIAS=of:Naw99703-bl-1T<NULL>Cawinic,aw99703-bl-1

1-0042

DRIVER=fsa4480-driver

OF_NAME=fsa4480

OF_FULLNAME=/soc/i2c@4a84000/fsa4480@42

OF_COMPATIBLE_0=qcom,fsa4480-i2c

OF_COMPATIBLE_N=1

MODALIAS=of:Nfsa4480T<NULL>Cqcom,fsa4480-i2c

1-0048

DRIVER=HiFi-dev

OF_NAME=hifi-es9218

OF_FULLNAME=/soc/i2c@4a84000/hifi-es9218@48

OF_COMPATIBLE_0=ess,hifi-es9218

OF_COMPATIBLE_N=1

MODALIAS=of:Nhifi-es9218T<NULL>Cess,hifi-es9218

1-0058

DRIVER=aw87xxx_pa

OF_NAME=aw87xxx_pa_58

OF_FULLNAME=/soc/i2c@4a84000/aw87xxx_pa_58@58

OF_COMPATIBLE_0=awinic,aw87xxx_pa_58

OF_COMPATIBLE_N=1

MODALIAS=of:Naw87xxx_pa_58T<NULL>Cawinic,aw87xxx_pa_58

2-0010

OF_NAME=elan

OF_FULLNAME=/soc/i2c@4a88000/elan@10

OF_COMPATIBLE_0=elan,ekth3500

OF_COMPATIBLE_N=1

MODALIAS=of:NelanT<NULL>Celan,ekth3500

2-0038

OF_NAME=focaltech

OF_FULLNAME=/soc/i2c@4a88000/focaltech@38

OF_COMPATIBLE_0=focaltech,5x06

OF_COMPATIBLE_N=1

MODALIAS=of:NfocaltechT<NULL>Cfocaltech,5x06

2-004b

DRIVER=atmel_mxt_ts

OF_NAME=atmel_mxt_ts_336u

OF_FULLNAME=/soc/i2c@4a88000/atmel_mxt_ts_336u@4b

OF_COMPATIBLE_0=atmel,mxt-ts

OF_COMPATIBLE_N=1

MODALIAS=of:Natmel_mxt_ts_336uT<NULL>Catmel,mxt-ts

HLTE556N:/sys/bus/i2c/devices #

***************************
[Android Q&A, Help & Troubleshooting] Renate:
Thanks, interesting.

They always put a lot of drivers and can't even decide which bus it's on!.

I was surprised that this device supports DisplayPort over USB Type C.

Has anybody tried that?
[Android Q&A, Help & Troubleshooting] bigwigs:
Nope, i have usb c cable which i use for my mac with monitor. I don't see any screen mirror options. There is Cast option under Settings --> More Connections & Sharing but it doesn't do anything.
[Android Q&A, Help & Troubleshooting] bigwigs:
FM Radio support - there two jar files with FM radio support but i haven't been able to use the same with any FM radio app.. I always get error, that device may need kernel with working FM driver.
[Android Q&A, Help & Troubleshooting] zxczxc4:
I also tried, plugged into my monitor using a usb type c cable, used normally for my laptop -- I believe using DP Alt mode. Nothing seemed to happen, no display magically appearing on the monitor :D

Maybe worth checking logcat to see if anything of note was logged.

That would be a cool bonus if we can get display out on this thing!!
[Android Q&A, Help & Troubleshooting] Renate:
Well, they load up a lot of drivers. It's no proof that the hardware is there. That's why I was curious.
[Android Q&A, Help & Troubleshooting] dferreira:
Happy to see more people poking around 💪 will continue more later today to bring the epd system service up to talk with the kernel. If I can, will stay away from any apk from Hisense main OS as they seem to have plenty of hooks to send data somewhere else, and also make many assumptions on what is available on the ROM. Pretty sure those apk will either crash or not work as intended at all. I can take a look to see if I find the source for the launcher so we can pull out the native rom bottom drawer overlay to our own apk.
[Android Q&A, Help & Troubleshooting] bigwigs:
more eink launcher apk
[Android Q&A, Help & Troubleshooting] dferreira:
Yeah, there is also no such soc devices... so dead-code.
[Android Q&A, Help & Troubleshooting] dferreira:
LOOK WHAT I FOUND:
[Android Q&A, Help & Troubleshooting] dferreira:
IT WORKS to clear the screen directly!

echo 1 > /sys/devices/platform/soc/soc\:qcom,dsi-display-primary/epd_force_clear
[Android Q&A, Help & Troubleshooting] dferreira:
Screen temperature (the yellow tint, 0-100):
[Android Q&A, Help & Troubleshooting] dferreira:
Display mode:

so we got everything we need to change the eink display settings! 😁
[Android Q&A, Help & Troubleshooting] bigwigs:
If u still need overlay apk
[Android Q&A, Help & Troubleshooting] Renate:
I think that is the panel ambient temperature, 23°C, important for waveform selection.

You want frontlight (which is usually called "backlight").

Hey, anybody brave (and rooted) want to try out my I²C scanner so we can see about actual hardware?

I'd rather PM than post it right now. Any volunteers?
[Android Q&A, Help & Troubleshooting] dferreira:
Linux? Send it over to me :)
[Android Q&A, Help & Troubleshooting] bigwigs:
Would devicetree file help? If not, send it over to me too.
[Android Q&A, Help & Troubleshooting] bigwigs:
i can do both windows and linux
[Android Q&A, Help & Troubleshooting] Renate:
Actually, the file I sent @dferreira is an Android executable.
[Android Q&A, Help & Troubleshooting] biodbl:
If I can help, tell me what I need to do. I'm not a programmer and I don't really understand some of the things you write here, but if it's something simple... My hisense is rooted
[Android Q&A, Help & Troubleshooting] Renate:
This is what I'm talking about (on an Onyx Poke3):

# ./i2cscan
/dev/i2c-2
60 R/W
/dev/i2c-4
1f In use qcom,camera i2c_camera
38 In use focaltech fts_ts FocalTech touch screen controller
/dev/i2c-6
09 wacom Wacom digitizer
38 In use lm3630a lm3630a_bl TI LED controller
/dev/i2c-8
0b In use tc358762 tc358762 Toshiba display interface bridge
68 In use tps6518x tps6518x TI Eink power management

So we can see some things bound to drivers.

Also one driver in the dtc with no hardware, Wacom.

Also one device neither with driver or in use, 2-0060

And I wonder what that camera is doing since it doesn't have one!

By contrast, the stock i2cdetect just says:

# i2cdetect 2 -y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
# i2cdetect 4 -y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
# i2cdetect 6 -y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
# i2cdetect 8 -y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- UU -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Heck, I don't understand some of the things I write here. :p
[Android Q&A, Help & Troubleshooting] zxczxc4:
Thanks to Renate! i2scan output:

HLTE556N:/data/local/tmp # ./i2cscan
/dev/i2c-0
0f In use tc358767 tc358767 Toshiba display interface bridge
35 In use ktd3137 ktd3137-bl-4 Backlight controller
36 In use aw99703-bl-2 aw99703-bl-2 Backlight controller
48 In use fp9929a fp9929a FitiPower Eink power controller
5a In use haptic_hv haptic_hv
/dev/i2c-1
0c In use qcom,smb1355 i2c_pmic
35 In use ktd3137 ktd3137-bl-3 Backlight controller
36 In use aw99703-bl-1 aw99703-bl-1 Backlight controller
42 In use fsa4480 fsa4480-driver USB Type C multiplexor
48 In use hifi-es9218 HiFi-dev
58 In use aw87xxx_pa_58 aw87xxx_pa
/dev/i2c-2
10 elan
38 focaltech FocalTech touch screen controller
4b In use atmel_mxt_ts_336u atmel_mxt_ts
[Android Q&A, Help & Troubleshooting] Renate:
Between the tc358767 and the fsa4480 it seems to imply that it could do DisplayPort.
[Android Q&A, Help & Troubleshooting] bigwigs:
This works for Hisense a5- https://www.hardreset.info/devices/hisense/hisense-a5/faq/faq/remote-control-android/ Should try for Hisense A9
[Android Q&A, Help & Troubleshooting] bigwigs:
doesn't work other way
[Android Q&A, Help & Troubleshooting] bigwigs:
@Renate

Need help in opening kernel.sym file in ghidra.

Can u pls recommend what options should i choose?

Format : Raw Binary ?

Language:

Processor - Dalvik Variant - Dex Android 11

or

Processor - ARM Variant - ??

thanks!