Hi guys,
I've ported (or at least trying to) POSP to suzu (Xperia X) but I'm stuck in a bootloop caused by the audioserver service.
I've already tried changing the frameworks/av potato project to the aosp one (because aosp build and boot correctly with it) but I'm still stuck with the same error.
You can find the log taken from the bootloop device here.
If someone have an idea I'll be very grateful.
Thanks
Related
Hi mates
I am trying to port the AOSP 4.4.3.43.43.43 L-Preview branch for our phone it's generated 5.2gb of out/target/product/ancora folder but compilation still stuck on the following image
Code:
arget Symbolic: libstagefright_amrnb_common (out/target/product/ancora/symbols/system/lib/libstagefright_amrnb_common.so)
make: *** No rule to make target `out/target/product/ancora/obj/KERNEL_OBJ/usr', needed by `out/target/product/ancora/obj/SHARED_LIBRARIES/audio.primary.msm7x30_intermediates/AudioHardware.o'. Stop.
Should I remove audio configuration from ancora.mk?
what kind of commit should apply to fix that error, any help will be thanked .
Maybe will be ported a pure AOSP
OK the most of the source are compiled the only think i need to fix is boot.img creation now i replace the AOSP recovery with cm one because the aosp is based only for the devices that support fastboot where our phone doesn't support it, if any updates or got it booted I will notify .
Hi Guys,
I just tried to build the 3 Recoveries (CWM,TWRP,PHILZ) from Source using CM-11.0 Repo for my Xperia M. It was working fine and they are getting loaded, but I have this odd Bug on all 3 Recoveries:
The Images on Screen are getting somehow mirrored to the other half and some seconds later all looks ok again After that it starts again. mirroring. And this happens all the time while in recovery. So is there maybe some Option I have to add to BoardConfig.mk the make it work or is there another solution?
Thanks.
EDIT:
Luckily @[NUT] came across this Bug some time before. So he was able to point me in the right direction.
He solved this by the help of @rachitrawat, who modified the "graphics.c" File inside the recovery source to use correct buffer. For those searching for an Solution. Check the commits with the term "Half Screen Bug" on this repo:
https://github.com/McBane87/android_device_sony_nicki
http://julianwi.square7.ch/debian-on-smartphone/
Dear all,
I am thinking of doing this, but our device has an odd boot image format that combines kernel and recovery.
Did anybody try this? Do you have any special warnings for me?
Thanks!
hi all
my story:
i got my hands on a samsung galaxy a300fu (aka. a3ulte) 2015 and successfully installed twrp3.2.3 and a custom lineage build version 14.1. my goal however is to build, install and boot lineage 15.1 or lineage 16.0. the building is not the problem! i can build both versions (with help of the lineage wiki and the local manifest from the github user "Galaxy-MSM8916"). i can also install them however i'm unable to boot them.
what i tried so far:
- the mentioned github user offers multiple lineage 15.1 downloads for the device but none of them seem to boot (it crushed my PIT or something i needed to reflash the recovery image)
- since android 8.0 the debug mode is off so i needed to build an engineering version (another 4h) to get some kernel messages but i'm kind of overwhelmed with 11000 lines of debug (not counting the loops)
- on androidfilehost there is a lineage 16 build from the user vlw (also present here on xda) which strangely seems to be working! after checking its system properties file however it seems this build is kind of a hybrid (part a3lte, part a3ulte). also i'm unable to contact him that's why i'm writing here.
i'm pretty much out of ideas and would like to know if any of you has an idea how to proceed.
regards
edit:
related to github.com/Galaxy-MSM8916/android_device_samsung_gprimeltezt/issues/1
able to boot after renaming hardware/qcom/keymaster/Androir.mk to hardware/qcom/keymaster/Android.mk.nobuild
Hello, i just built 17.1 for an unsupported device (HMD Nokia 6 TA-1021) and I'm stuck at the boot animation.
This is my first build so I'm kind of a noob, I can see some errors in the logcat but I'm not sure what to do to fix them.
E.g.:
Code:
Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
Cannot find entry [email protected]::IThermal/default in either framework or device manifest.
Cannot find entry [email protected]::ISensors/default in either framework or device manifest.
Even if those HALs are present in my manifest.xml and device.mk. Am I missing something?
I get some "CANNOT LINK EXECUTABLE" too because of missing symbols, I think I'm missing some proprietary blobs but a Google search didn't help me. How can I debug this?
Here's the full logcat: https://pastebin.com/FM8CZp6f
Device tree used: https://github.com/sguerrini97/android_device_nokia_PLE/tree/lineage-17.1
Vendor tree used: https://github.com/sguerrini97/android_vendor_nokia_PLE
Kernel tree used: https://github.com/sguerrini97/android_kernel_nokia_msm8937
Thank you
I don't know much about rom development. But u can get some help from t.me/alaskalinuxuser_romdevelopment
sguerrini97 said:
Hello, i just built 17.1 for an unsupported device (HMD Nokia 6 TA-1021) and I'm stuck at the boot animation.
Click to expand...
Click to collapse
hi!
I have the same problem now with my samsung a5 2017(a5y17lte). i have flashed from v16.0 to v17.1 with twrp3.3. i am now constantly in the animation and after a while the phone restarts in twrp.
device is supported btw.
did you solved the problem?
best regards
fullnode said:
hi!
I have the same problem now with my samsung a5 2017(a5y17lte). i have flashed from v16.0 to v17.1 with twrp3.3. i am now constantly in the animation and after a while the phone restarts in twrp.
device is supported btw.
did you solved the problem?
best regards
Click to expand...
Click to collapse
I don't think here is the right place for your question. Follow the guide from wiki.lineageos.org