@matteo if the led support is build as a module then this module can be copied to the rootfs. If not I guess you can test a new kernel with
fastboot boot which boots the kernel without installing it first.
Posts made by wdehoog
RE: support for led notifications
@matteo in this link they mention a problem with the led driver your phone has (I don't have one so I could be totally wrong). And this link mentions how you could get it to show something (if it works).
So do you get any results with
find /sys/bus/i2c -name select_engineor with
find /sys/bus/i2c -name lp5562
RE: support for led notifications
@matteo to test your leds. It is also interesting to see the permissions. For example on opo:
phablet@ubuntu-phablet:~$ find /sys -name brightness -ls 13414 0 -rw-rw-r-- 1 system android_input 4096 Jan 5 20:48 /sys/devices/f9924000.i2c/i2c-2/2-0068/leds/red/brightness 13442 0 -rw-rw-r-- 1 system android_input 4096 Jan 5 20:48 /sys/devices/f9924000.i2c/i2c-2/2-0068/leds/blue/brightness 13428 0 -rw-rw-r-- 1 system android_input 4096 Jan 5 20:48 /sys/devices/f9924000.i2c/i2c-2/2-0068/leds/green/brightness 11561 0 -rw-rw-r-- 1 system android_input 4096 Jan 5 20:48 /sys/devices/mdp.0/qcom,mdss_fb_primary.169/leds/lcd-backlight/brightness 19339 0 -rwxrwxrwx 1 system android_media 4096 Mar 3 1970 /sys/devices/leds-qpnp-f6287e00/leds/led:flash_torch/brightness 19303 0 -rwxrwxrwx 1 system android_media 4096 Mar 3 1970 /sys/devices/leds-qpnp-f6287e00/leds/led:flash_0/brightness 19320 0 -rwxrwxrwx 1 system android_media 4096 Mar 3 1970 /sys/devices/leds-qpnp-f6287e00/leds/led:flash_1/brightness 17399 0 -rw-r--r-- 1 root root 4096 Jan 7 20:27 /sys/devices/leds-qpnp-f628c000/leds/kpdbl-pwm-2/brightness 17421 0 -rw-r--r-- 1 root root 4096 Jan 7 20:27 /sys/devices/leds-qpnp-f628c000/leds/kpdbl-pwm-3/brightness 17443 0 -rw-r--r-- 1 root root 4096 Jan 7 20:27 /sys/devices/leds-qpnp-f628c000/leds/kpdbl-pwm-4/brightness 17377 0 -rw-rw-r-- 1 system android_input 4096 Jan 5 20:48 /sys/devices/leds-qpnp-f628c000/leds/button-backlight/brightness 16275 0 -rw-rw-r-- 1 system android_input 4096 Mar 3 1970 /sys/devices/qcom,camera-led-flash.83/leds/torch-light/brightness 17292 0 -rw-r--r-- 1 root root 4096 Jan 7 20:27 /sys/devices/msm_sdcc.1/leds/mmc0::/brightness 17335 0 -rw-r--r-- 1 root root 4096 Jan 7 20:27 /sys/devices/msm_sdcc.2/leds/mmc1::/brightness
If 'phablet' is allowed you can try:
echo 1 > /sys/...../brightness
if not you must do it as root:
sudo bash -c "echo 1 > /sys/...../brightness"
(replace the dots with the full path) and try to echo different values (0,1,64,255)
Then it would also be interesting to show what other files reside in the same directories as the 'brightness' file. For example on opo:
phablet@ubuntu-phablet:~$ ls -l /sys/devices/leds-qpnp-f6287e00/leds/led:flash_torch/ total 0 -rwxrwxrwx 1 system android_media 4096 Mar 3 1970 brightness lrwxrwxrwx 1 root root 0 Jan 7 20:33 device -> ../../../leds-qpnp-f6287e00 -rw-rw-r-- 1 root root 4096 Jan 7 20:33 flash_blink -rw-rw-r-- 1 root root 4096 Jan 7 20:33 led_mode -rw-r--r-- 1 root root 4096 Jan 7 20:33 max_brightness drwxr-xr-x 2 root root 0 Mar 3 1970 power -rw-rw-r-- 1 root root 4096 Jan 7 20:33 strobe lrwxrwxrwx 1 root root 0 Jan 5 20:48 subsystem -> ../../../../class/leds -rw-r--r-- 1 root root 4096 Jan 7 20:33 trigger -rw-r--r-- 1 root root 4096 Mar 3 1970 uevent
And please post a
dmesglog somewhere. Maybe this is related: https://e2e.ti.com/support/power-management/f/196/t/421131
RE: Building an image
I followed http://docs.ubports.com/en/latest/porting/ubp-5.1.html so ended up with the same settings as the files you point me to.
Still I think this is not what is currently being build on the ubports server and installed by the official installer.
For example branch ubp-5.1 of http://github.com/ubports/android_device_oneplus_bacon-1 has init_wlan_bt.sh in '/' of the android rootfs while on the installer image it is located in '/etc'. As I cannot find any branch that contains this file in '/etc' the ubports build server probably uses another repo. Which one?
In my locally built /system/lib/hw/ there is camera.vendor.bacon.so and in the installer one there is camera.msm8974.so. The other lib files are present but seem to differ in contents.
The files you point to use The Muppets cm-12.1 which contains camera.vendor.bacon.so not the camera.msm8974.so.
So the ubports build server probably uses another repo or branch. Which one?
To be able to continue fixing issues I now have to update the installers system.img (mount loop etc.) and reflash that.
Building an image
I am trying to fix some issues for my opo and therefore need to build an image.
There are two documented methods I am aware of:
For me both do not work. The 'device-builds' one does not work at all. Building fails with various errors.
The 'docs' one builds and I can flash the boot.img and update the system.img and the phone boots etc.. However the camera stops working.
While cheking why the camera stopped working I noticed the system.img installed by the UBports Installer contains different files the the one I have built. So it seems there is yet another way to build an image.
So is there another 'howto' for building an image? Or do the before mentioned descriptions need a little bit of tweeking?
RE: Crossbuilder - mk-build-deps
@erlend This issue is caused by some multilib thing. I have this issue for other packages. It sometimes help to explicitely set the platform. I would try to edit the debian/control file and see if it works with dh-translations:all
Please don't think I understand this. I keep on changing stuff till it works.
And open an issue on github (for the app or for crossbuilder)