Develop Bugs

[SOLVED] 4.0.3 AOSP build stuck at google logo. Kernel problem?

Hey guys,
i have a problem when building 4.0.3 from source. When i flash the fresh compiled
OTA package to my device, the device ends in a bootloop stuck at the google logo.
Logcat says:
Code:
I/SystemServer( 238): Power Manager
I/SystemServer( 238): Activity Manager
I/ActivityManager( 238): Memory class: 64
I/SurfaceFlinger( 251): SurfaceFlinger is starting
I/SurfaceFlinger( 251): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/IMGSRV ( 251): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 251): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 251): :0: PVRSRVConnect: Unable to open connection.
E/IMGSRV ( 251): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 251): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open framebuffer HAL (Not a typewriter)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 251): Display subsystem failed to initialize. check logs. exiting...
I/ServiceManager( 109): service 'sensorservice' died
I/ServiceManager( 109): service 'power' died
I/ServiceManager( 109): service 'entropy' died
D/AndroidRuntime( 259):
D/AndroidRuntime( 259): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 259): CheckJNI is OFF
I don't know whats going wrong. Can it be a kernel problem? I have tried different 4.0.3 kernels from the dev section, but the result is the same.
The device is a GSM device with PRIMEKK15 unlocked bootloader and I9250XXKK6 baseband.
After pulling the latest 4.0.3 sources with repo and setting up the proprietary files i'have compiled the system without errors:
Code:
~/android/4.0.3$ . build/envsetup.sh
~/android/4.0.3$ lunch full_maguro-userdebug
~/android/4.0.3$ make -j4 otapackage
I really don't understand what i am doing wrong ...
Thanks for any suggestions or answers.

i got this problem when I updated my phone using fastboot.
for me, it was an application installed from market. after wipe everything and redo the flash procedure, everything was fine.
don't know if it is the same problem here.

Did you pull in the proprietary files needed for the build?

At least you've got to the boot animation, my ROM fails at the flashing with a status 7 error mentioning the boot.img

PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
with ./extract-files.sh .correct?

PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
Yes, the files are pulled from the device ( if you mean the extract_files.sh from the device folder), compilation finishes without errors.
No boot animation, nothing...
Sent from my Galaxy Nexus using XDA App

Now at this point too, bootloops all the time. I think the code is ****ed

Ok, dmesg gave me this:
Code:
<6>[ 5.367248] PVR: Installing MISR with cookie c0833f74
<6>[ 5.367828] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c79f5700
<6>[ 5.368255] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8be0000
<6>[ 5.368469] PVR: SysFinalise: Version string: SGX revision = 1.2.0
<6>[ 5.369171] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (785978)/device DDK revision (780209).
<6>[ 5.369537] PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [449, drivers/gpu/pvr/pvrsrv.c]
<6>[ 5.370025] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<6>[ 5.552337] max17040 4-0036: online = 1 vcell = 4007500 soc = 77 status = 1 health = 1 temp = 340 charger status = 0
<3>[ 5.643005] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns1
<3>[ 5.643737] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns2
<3>[ 5.644287] init: sys_prop: permission denied uid:1001 name:net.rmnet1.gw
<3>[ 5.645263] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns1
<3>[ 5.645812] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns2
<3>[ 5.646484] init: sys_prop: permission denied uid:1001 name:net.rmnet2.gw
<6>[ 5.707031] [MODEM_IF] misc_open : umts_boot0
<6>[ 5.707153] omap_hsi omap_hsi.0: HSI clock is now 96000000
<6>[ 5.723510] omap_hsi omap_hsi.0: Entering RX wakeup in 3 wires mode (no CAWAKE)
<6>[ 5.723602] [MODEM_IF] xmm6260_off()
<6>[ 5.723724] [MODEM_IF] xmm6260_on()
<6>[ 5.724456] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 5.724548] [MODEM_IF] umts_ipc0 state changed: OFFLINE
<6>[ 5.835540] [MODEM_IF] PA EVENT : reset =1, pa=0
<6>[ 5.979125] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c
<6>[ 5.980194] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
<6>[ 6.087188] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<3>[ 6.094604] init: untracked pid 118 exited
Anyone knows how to fix this issue?

Try reflashing the boot.img created by your build..

Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
I built my own AOSP rom too, but haven't tried it yet.
also
Cleaning up when adding proprietary binaries
In order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with
$ make clobber
Click to expand...
Click to collapse
http://source.android.com/source/building-devices.html
sorry if you did all this - I'm a noob to ASOP building

Did you wipe the device before installing the rom and kernel?

Luxferro said:
Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
Click to expand...
Click to collapse
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.

m0rph3us said:
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.
Click to expand...
Click to collapse
No problem. Glad I can help
I guess that hopefully means my build would work too if I ever tried it. Was hoping official 4.0.3 OTA would be out by now. I might just have to try my build too.
Sent from my Galaxy Nexus using Tapatalk

I ran the script under /device/samsung/toro/
is that the correct place to run it, or should I be running it somewhere else?
Nevermind, I'm dumb. I read the post and got it now lol

I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?

jab416171 said:
I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?
Click to expand...
Click to collapse
you don't need to excessively run make clobber. all it really does is delete the out/ directory.
Here's how I was able to get a fully functional build ($ANDROID_SOURCE is your build dir):
0) make clobber; # just for the initial cleansing
1) cd $ANDROID_SOURCE/device/samsung/toro && ./extract-files.sh
2) run extract-imgtec-toro.sh OUTSIDE of your build directory (in a temporary location)
3) copy the contents of $TEMPDIR/vendor/imgtec/toro/proprietary/* into $ANDROID_SOURCE/vendor/samsung/toro/proprietary/
4) cd $ANDROID_SOURCE; . build/envsetup.sh
5) lunch #pick your desired toro build. Probably full_toro-userdebug
6) make
The reality is that extract-files.sh does everything well, except it doesn't include the gpu drivers (so we copy them manually). The make files that extract-files.sh creates DOES reference the gpu drivers, they're just not extracted by the script.
Messing with extract-imgtec-toro.sh will give you make files that don't reference any of the other binaries. Your image will boot, but won't have much else working.
Good luck!

Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5

jab416171 said:
Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5
Click to expand...
Click to collapse
I think your cp needs a '/*' after the first proprietary. The object is to copy the contents of one proprietary directory into the proprietary directory of another. Unless I'm mistaken, your cp will copy the proprietary source folder into the proprietary destination folder resulting in a $TOP/vendor/samsung/toro/proprietary/proprietary. Either that or error out because you specified to cp a dir without a -R.
You should certainly run a make clobber after extracting new binaries if you have files from a previous build still lying around. if you've already cleaned it out, then its just redundant (and not hurting anything).
Otherwise it looks good to me! Good luck!

Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?

jab416171 said:
Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?
Click to expand...
Click to collapse
Just once. I usually just tar up my vendor/samsung/toro directory and keep the tar in a safe location. No more extractions once you have it.

how to fix errors in flyme6 patchrom

I'm trying to build a flyme6 ROM based on JUI, but there are some errors i can't fix. It seems that register v1 has a wrong type according to log. but i dont know where the method forEachRemaining locate. i tried $grep -r forEachRemaining but find nothing. what can i do to fix the errors?
device: http://www.github.com/jmxl/flyme_patchrom_device_cp_ares
here are the logs:
Code:
01-01 16:03:30.898 908 908 W dex2oat : Verification error in void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer)
01-01 16:03:30.898 908 908 W dex2oat : void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer) failed to verify: void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer): [0x1A] invalid argument count (5) exceeds outsSize (3)
01-01 16:03:30.898 908 908 W dex2oat :
01-01 16:03:30.898 908 908 W dex2oat : Verification error in boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer)
01-01 16:03:30.898 908 908 W dex2oat : boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer) failed to verify: boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer): [0x18] invalid argument count (5) exceeds outsSize (3)
01-01 16:03:30.898 908 908 W dex2oat :
01-01 16:03:30.899 908 908 W dex2oat : Verification error in void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer)
01-01 16:03:30.899 908 908 W dex2oat : void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer) failed to verify: void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer): [0x1A] register v1 has type Integer but expected Double (Low Half)
01-01 16:03:30.899 908 908 W dex2oat :
01-01 16:03:30.899 908 908 W dex2oat : Verification error in boolean java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.tryAdvance(java.util.function.IntConsumer)

With all due respect, flyme_LEX720_rogue_6.7.6.30R-beta.zip already exist. Why not just use it?
You probably have a non-printable character in there somewhere which is breaking it. Retype the code manually

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >

[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >
Hi.
I encountered a problem while trying to port AOSP Extended v. 4.1 (Android 7.1.2, kernel 3.10.65+, MTK 6753) on my device (VOYO Q101, 2GB/32GB, kernel 3.10.65+, MTK 6753).
After successfully started the booting process (after one week of research, and a stupid line in /system/build.prop: ro.setupwizard.enterprise_mode=1 which caused stucking at logo), I have managed to get a logcat via adb. LOG (it's 8MB)
It is booting.. and booting... forever. It is not stucked, nor bootlooping. It is just booting (the "Google dots" animations running forever).
I have attached the log. There are a lot of CANNOT LINK EXECUTABLE <....> cannot locate symbol < ... > referenced by <...> and also a lot of:
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Write 56 bytes to slot 0, CCCI_H(0x0)(0x38)(0x801D000F)(0x0)
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from FS device
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from slot 0, CCCI_H(0x0)(0x80)(0x801E000E)(0x0)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): CMPT File name:Z:/NVRAM/NVD_DATA/ULMH_000 opid_map:0x00000013 Flag:0x00000100 Offset:34 Whence:-229154332 Length:16384
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): O: [1010103F282D2C35](0x00000100): (7 1)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): F: 1: 1906 0
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): C: 1: 0
[What I did]
- just copying the kernel from stock ROM (tried also: stock kernel + stock ueventd.rc +/- stock fstab): all caused bootloop or even stucked at logo. Just kernel change works good (at least till the actual stage) .
- compared with old .rc files. No replaces needed (in my opinion)
- From system/build.prop file I have DELETED all lines from ADDITIONAL_BUILD_PROPERTIES section (especially ro.setupwizard.enterprise_mode=1) - which took me 4 DAYS !!! to understand why it was stucked at logo .
- tried with and without patching with init.d (from porting ROM's website)
- tried to put the stock binaries mentioned in errors <CANNOT LINK ...> (/system/bin/mtk_agpsd, xlog) - not booting at all (it even stucks at logo...). Should I try with stock linker.so lib(64) ? But I think it will not boot at all (It really can't).
I hope for your help . Thanks!

up

Unable to boot any GSI, i get bootloop

Hi,
i have unlocked bootloader and flashed official twrp, everything works, but i wanted to try some GSI so flashed havoc os 2.0 pie and got a bootloop with this error:
Code:
--------- beginning of system
04-16 11:44:38.751 596 596 I vold : Vold 3.0 (the awakening) firing up
04-16 11:44:38.752 596 596 V vold : Detected support for: exfat ext4 ntfs vfat
04-16 11:44:38.757 596 596 D vold : Tearing down stale mount /mnt/phh
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop3: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop0: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop7: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop1: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop6: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop4: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop5: No such device or address
04-16 11:44:38.759 596 596 I vold : [libfs_mgr]dt_fstab: Skip disabled entry for partition system
04-16 11:44:38.762 596 596 D vold : VoldNativeService::start() completed OK
04-16 11:44:38.763 596 600 D vold : e4crypt_init_user0
04-16 11:44:38.764 596 600 D vold : e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 1
04-16 11:44:38.764 596 600 D vold : Preparing: /data/vendor_de
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/vendor_de): Read-only file system
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/vendor_de: Read-only file system
04-16 11:44:38.764 596 600 D vold : Preparing: /data/system/users/0
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/system/users/0: No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare user 0 storage
04-16 11:44:38.780 601 601 I /system/bin/tzdatacheck: timezone distro dir /data/misc/zoneinfo/current does not exist. No action required.
04-16 11:44:38.784 596 599 I vold : Found disk at /devices/soc/7864900.sdhci/mmc_host/mmc1/mmc1:aaaa/block/mmcblk1 but delaying scan due to secure keyguard
04-16 11:44:38.985 610 610 I BOOT : MSM target '', SoC 'QRD', HwID '293', SoC ver '65536'
04-16 11:44:38.998 611 611 W DRM_BOOT: file: '/sys/module/drm/parameters/vblankoffdelay' or perms doesn't exist
04-16 11:44:39.542 675 675 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
--------- beginning of crash
04-16 11:44:39.630 701 701 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
04-16 11:44:39.631 714 714 E getcolorid: tp info = 31373201d1533101
04-16 11:44:39.631 714 714 E getcolorid:
04-16 11:44:39.631 714 714 E getcolorid: colorid = 32
04-16 11:44:39.644 676 676 I [email protected]/: [email protected]/backup: Hal starting main loop...
04-16 11:44:39.645 676 676 I [email protected]/: [email protected]/backup Hal is starting up...
04-16 11:44:39.647 717 717 I lowmemorykiller: Using in-kernel low memory killer interface
04-16 11:44:39.652 676 676 W ServiceManagement: Can't efficiently wait for [email protected]::IHealth/default, because we are called from the only binder thread in this process.
04-16 11:44:39.659 707 707 I irsc_util: Starting irsc tool
04-16 11:44:39.660 708 708 I rmt_storage: Shared memory initialised successfully.
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst1: 0x4a /boot/modem_fs1
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst2: 0x4b /boot/modem_fs2
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsc: 0xff /boot/modem_fsc
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsg: 0x58 /boot/modem_fsg
04-16 11:44:39.660 708 708 I rmt_storage: 4 GPT partitions found
04-16 11:44:39.661 708 708 I rmt_storage: Capset success!
04-16 11:44:39.666 707 707 I irsc_util: Num of entries:292
04-16 11:44:39.668 676 676 I ServiceManagement: getService: Trying again for [email protected]::IHealth/default...
04-16 11:44:39.668 707 707 I irsc_util: Ending irsc tool
04-16 11:44:39.669 676 676 W ServiceManagement: Waiting one second for [email protected]::IHealth/default
04-16 11:44:39.676 712 712 D PcbaConfigSet: Before, get, [ro.boot.hwversion=], [ro.boot.hwc=], [ro.boot.hwlevel=], [ro.product.cert=], [ro.product.name=treble_arm64_bvN]
Patched boot din't worked.
So, i reflashed with ./flash_all and tried again, flashing also magisk, this time asked me for password, hitted cancel and then selected factory reset.. stuck in twrp
Tried other combos with always flashing stock rom but nothing worked, every time i got bootscreen i get bootloop with the error above(tried also pixel experience, same issue).
This is my first device with treble so maybe i'm a bit noob, someone could help me?

Have you tried the GSI ROM posted in this forum? Also try to flash the stock ROM and see if you didn't broke something.
Does havok has A/B partition support?

SnoopDoggyStyleDogg said:
Have you tried the GSI ROM posted in this forum?
Click to expand...
Click to collapse
Yes, ive tried also pixel experience P because a thread said it's totally compatible.
SnoopDoggyStyleDogg said:
Also try to flash the stock ROM and see if you didn't broke something.
Click to expand...
Click to collapse
After doing exactly the same operation?
I've tried to switch slot(to the one that contain stock) but I got bootloop, so yes, I think the process I've done broke something.
SnoopDoggyStyleDogg said:
Does havok has A/B partition support?
Click to expand...
Click to collapse
Yes, I've downloaded arm64 a/b

Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
-internal storage showed as 8 gb
These are common to all GSI or only to havoc?

mac12m99 said:
Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
These are common to all GSI or only to havoc?
Click to expand...
Click to collapse
try and enable all permision for the camera app from settings if the error says can't connect to camera
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,

Jordan~Kurniawan said:
try and enable all permision for the camera app from settings if the error says can't connect to camera
Click to expand...
Click to collapse
Tried but nothing, i have black screen btw, no error is displayed
Jordan~Kurniawan said:
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,
Click to expand...
Click to collapse
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?

mac12m99 said:
Tried but nothing, i have black screen btw, no error is displayed
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?
Click to expand...
Click to collapse
maybe, for what I've understand we need to manually edit the system ui apk
I'm only trying the 8.1 GSI because i think that what would work the most
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it

Jordan~Kurniawan said:
maybe, for what I've understand we need to manually edit the system ui apk
Click to expand...
Click to collapse
ah ok
Jordan~Kurniawan said:
I'm only trying the 8.1 GSI because i think that what would work the most
Click to expand...
Click to collapse
trying RR Oreo..
Jordan~Kurniawan said:
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it
Click to expand...
Click to collapse
Ok thanks:good:
What about internal storage space issue?
PS
i've found that wiping data from twrp or fastboot cause always a bootloop, the right way is to flash userdata.img from stock rom.

After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.

mac12m99 said:
After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.
Click to expand...
Click to collapse
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time

Jordan~Kurniawan said:
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time
Click to expand...
Click to collapse
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first

mac12m99 said:
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first
Click to expand...
Click to collapse
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
edit:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9

Jordan~Kurniawan said:
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
Click to expand...
Click to collapse
Can be, i will look into this weekend, but oreo gsi works so i don't think.
Jordan~Kurniawan said:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9
Click to expand...
Click to collapse
Consider that in this thread a lot of people reported that camera work(and someone that don't).
I think all depends on phh patches version that the build use, but thats the first treble device i own so i don't know much about treble, sorry .

[BUILDING][OMNI9]Help building omni 9 for daisy

I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
ada12 and me made a Telegram group for mi a2 lite developing, who wants to join can pm me or ada12.

I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog

It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.

reujea0 said:
It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.
Click to expand...
Click to collapse
Whoa, thanks a lot i already have an idea on how to fix gnss and i will try to patch elf when i have time (tomorrow or so)

mac12m99 said:
I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog
Click to expand...
Click to collapse
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .

wertus33333 said:
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Click to expand...
Click to collapse
Ok, i got it,
so you are trying to create a ROM that don't use vendor partition and have all needed blobs into /system?
wertus33333 said:
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Click to expand...
Click to collapse
Which features do you mean?
As i know all hardware features have to be implemented in kernel (like dt2w and fingerprint gestures) and all software features have to be implemented in ROM (like long press for flashlight, dt2s in statustbar ecc..).
Am i wrong?
wertus33333 said:
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .
Click to expand...
Click to collapse
This happens when OEM forgot to move something vendor, as i know .
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but i think it could be built.

mac12m99 said:
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but I think it could be built.
Click to expand...
Click to collapse
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.

reujea0 said:
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.
Click to expand...
Click to collapse
Ok i got it, i hope you succeed

log interpretation
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
wertus33333 said:
I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
Click to expand...
Click to collapse
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug

Thanks for the answer, last time i could not find the v10.0.2.0 vendor anywhere but if it is officially avaiable now i'll defenitely switch.
A telegram group would defenitely be of help and easier to communicate than here. More people reviewing/contributing to the code on github (i don't always really know what i am doing ) would also be useful (i'd be happy to add more people, just pm me if u want to).
I dont have that much time for continuing with the rom in the next 1-2 weeks but i'll defenitely continue as soon as possible.
ada12 said:
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug
Click to expand...
Click to collapse