UPDATE
Initial OmniROM release for Athene out now:
omni-7.1.1-20170219-athene-HOMEMADE.zip
--- Original OP below ---
Hi guys, I have started the bringup for OmniROM on Athene:
Device
Kernel
It starts to boot up, but gets stuck in the bootanimation and restarts soon after. According to dmesg / logcat, the modem does not come up (see attached files). I compared init.rc files and blobs being used with other roms (lineage / aex), but couldn't identify the root cause for that error at this early stage:
Code:
[ 7.022888,0] Fatal error on the modem.
[ 7.022913,0] modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.
@rahulsnair, @Silesh.Nair (or anybody else): Can you guys please help out here, is that something you have come across in any of your bringups? Really would like to bring Omni to life on Athene.
Thanks in advance :good:
Looks like rmt_storage can't load the needed modem firmware :
Code:
09-21 03:07:13.861 342 342 D rmt_storage: GZFSG open /fsg/athene_dsds_emea.img.gz
09-21 03:07:13.861 342 342 E rmt_storage: Couldn't open /fsg/athene_dsds_emea.img.gz, trying default for product-radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/athene_emea.img.gz, trying default for radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/emea.img.gz, trying default
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/0.img.gz
09-21 03:07:13.862 342 342 I rmt_storage: rmt_storage_open_cb: Unable to open /boot/modem_fsg
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Code:
strace -fF -s 1000 rmt_storage > /sdcard/rmt_storage_strace.txt
vache said:
Looks like rmt_storage can't load the needed modem firmware :
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Click to expand...
Click to collapse
Good point, thanks. Haven't checked the mounts on boot yet. Eventually, fstab.qcom does not get parsed.
Making some progress: There is an issue with the ramdisk of the inline-built kernel: It is not picking up the correct .rc files. I don't get where these references to "recovery" are coming from:
Code:
<13>[ 3.022567,0] init: init second stage started!
<11>[ 3.207517,0] init: waitpid failed: No child processes
<11>[ 3.209434,0] init: property_set("ro.com.google.clientidbase", "android-motorola") failed
<11>[ 3.209584,0] init: property_set("ro.config.notification_sound", "Argon.ogg") failed
<11>[ 3.209599,0] init: property_set("ro.config.alarm_alert", "Helium.ogg") failed
<11>[ 3.209710,0] init: property_set("ro.config.ringtone", "Orion.ogg") failed
<13>[ 3.209803,0] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 3.210260,0] init: /init.rc: 12: invalid command 'setcon'
<11>[ 3.210326,0] init: /init.rc: 62: invalid command 'load_all_props'
<11>[ 3.210406,0] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<13>[ 3.210688,0] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 3.210735,0] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 3.210812,0] init: could not import file 'init.target.recovery.rc' from '/init.recovery.qcom.rc'
<13>[ 3.210827,0] init: (Parsing /init.recovery.qcom.rc took 0.00s.)
However, having flashed a Lineage kernel, it's booting up now.
@vache: /fsg indeed was not mounted. I think there is an issue with the mkdir, will amend that now.
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
golden-guy said:
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
Click to expand...
Click to collapse
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
vache said:
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
Click to expand...
Click to collapse
Thanks mate, I have done that yesterday to get RIL working (radio logcat showed that rild was complaining about that missing libqsap_sdk.so lib). All fine there already.
But I am still struggling with at least three things atm: Sensors, media playback and camcorder.
Sensors: I can see them initialized, but they don't return any values. According to logcat, e.g proximity gets disabled on screen on (sic!) Which sounds weird tbh
Media playback: Acodec cannot instantiate decoders upon ringtone playback and when music is to be played via bluetooth. mp3/mpeg playback does work when played via phone' speaker though. It could be a codec issue, but it could be audio policy / routing related. We are using a custom policy, aren't we?
Camcorder - didn't look into that yet. But is very likely related to media codec issue.
Will add some logs to further explain.
EDIT: Logs are added now.
PS: Device repo updated
Will cross-check with LineageOS, but the lack of sensor data might be permission related after all. All sensors seem to be up and configured, with their /dev and /sys entries being populated. Unfortunately, there is no error to be seen in the logs, giving no indication of the root cause...
Got the sensor issue sorted. It was selinux related again - what else. :silly:
Anyhow, one issue less.
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Sent from my Moto G4 Plus using Tapatalk
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
+1
1chrome said:
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Click to expand...
Click to collapse
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
vinylmeister said:
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
Click to expand...
Click to collapse
Sorry man my bad... smileys didn't show up on my Tapatalk!
Sent from my Moto G4 Plus using Tapatalk
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
golden-guy said:
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
Click to expand...
Click to collapse
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
vache said:
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
Click to expand...
Click to collapse
I tried with Snap and SnapDragonCamera. I wanted to do that with a fresh build. After having synched sources, mm-camera daemon keeps crashing and causing bootloops. Omni has updated their manifest to r14, also, lineage seems to have merged in fresh caf sources causing issues with qcom blobs. If I had known that earlier, I wouldn't have synched anew.
I see u uploaded to afh is it ready for testing I'm excited
joeeboogz said:
I see u uploaded to afh is it ready for testing I'm excited
Click to expand...
Click to collapse
????!!
Good catch! ?
Yes, it's up for testing now: https://www.androidfilehost.com/?fid=457095661767137952
Please note that this is an early ALPHA build: Media playback (ogg/mp4) and camcorder are still broken. But apart from that it seems to work just fine.
Related
poo706 presents... LIQUIDSMOOTH LOLLIPOP - UNOFFICIAL
Things to note
Same kernel as Ziyan's CM12 (EXT4 only)
F2FS supported on /data and /cache only, /system must be EXT4
For F2FS use one of the following Full_Auto kernels: R1, R4.5, R5, R6, R7, R8, R10, R10, R11
Linaro toolchains for both ROM and kernel
Liquid Optimizations
CM12 Theme Engine
Deodexed: First boot will take a long time!
Clear all recents on a regular basis to reduce lag, they survive a reboot!
Su binary is not included, install SuperSu from recovery: http://download.chainfire.eu/supersu
Use as small gapps as possible, I've had luck with the minimal edition from here: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
2/21: http://www.mediafire.com/download/xjpv7cdiqrea6fe/LS-LP-v4.0-2015-02-21-liquid_toro.zip
Old versions:
2/14: http://www.mediafire.com/download/anrm2e7utbpi743/LS-LP-v4.0-2015-02-14-liquid_toro.zip
2/11: http://www.mediafire.com/download/spspbpcg2r9h41t/LS-LP-v4.0-2015-02-11-liquid_toro.zip
1/28: http://www.mediafire.com/download/nu9tppot8xzl9yf/LS-LP-v4.0-2015-01-28-liquid_toro.zip
1/25: http://www.mediafire.com/download/az5s82692b7pqb3/LS-LP-v4.0-2015-01-25-liquid_toro.zip
1/19: http://www.mediafire.com/download/4olpmgsifq5qygc/LS-LP-v4.0-2015-01-19-liquid_toro.zip
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhX0s4WGpFMm1BWEk&usp=sharing
Click to expand...
Click to collapse
Changelogs:
2/21: Boot animation memory leak fix
2/14: Switched from Layers to CM12 Theme Engine (clean flash this build)
2/11: Resynced source
1/28: Reverted minor F2FS change, Linaro 4.8.4 for ROM, Linaro 4.9.1 for kernel, deodexed
1/25: Minor change regarding F2FS, HW decoding working again, YouTube working, navbar customizations
1/19: ROM (but not kernel) supports F2FS on /data and /cache, torch tile fixed, new APNs
Credits and thanks:
LiquidSmooth team: https://github.com/LiquidSmooth
@Ziyan: https://github.com/Ziyann
@MWisBest: https://github.com/MWisBest
@zzpianoman: https://github.com/zzpianoman
@musical_chairs
@bsmitty83 for the Full_Auto kernel: http://forum.xda-developers.com/gal.../lollipop-kernel-fullauto-r1-aosp-cm-t2994371
@Nautilus74 for repacking Full_Auto with ramdisks
My other projects:
LiquidSmooth-UNOFFICIAL LP: maguro, toroplus
LiquidSmooth-OFFICIAL KK: maguro, toro, toroplus
LiquidSmooth-UNOFFICIAL KK: maguro, toro, toroplus, grouper
F2FS Converter tools: Galaxy Nexus, grouper
APNs: Ting (LTE), Verizon (MMS)
Click to expand...
Click to collapse
[poo]
Thanks @poo706! Looking forward to this.
A few things I collected on the first build:
Logcat error and fatal events ("adb logcat *:E *:F") for camera crash when saving a picture:
Code:
E/AudioTrack(17751): AudioTrack::set : Exit
F/libc (17751): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xf3e0 in tid 18007 (NotificationThr)
E/DEBUG ( 133): AM write failure (32 / Broken pipe)
E/SharedPreferencesImpl( 537): Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
E/Camera (17842): Error 100
E/CAM_CamErrCallback(17842): Got camera error callback. error=100
E/AndroidRuntime(17842): FATAL EXCEPTION: main
E/AndroidRuntime(17842): Process: com.android.camera2, PID: 17842
E/AndroidRuntime(17842): java.lang.RuntimeException: Media server died.
E/AndroidRuntime(17842): at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:33)
E/AndroidRuntime(17842): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$ErrorCallbackForward$1.run(AndroidCameraAgentImpl.java:1099)
E/AndroidRuntime(17842): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(17842): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(17842): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(17842): at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AudioService( 537): Media server died.
E/MediaPlayerFactory(18162): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(18162): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/MonoPipe(18162): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/SoundTriggerHwService(18162): couldn't load sound trigger module sound_trigger.primary (No such file or directory)
E/AudioService( 537): Media server started.
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
Strace output of launching the rild daemon on liquid LP (non-working radio) ("rild -l /vendor/lib/libsec-ril_lte.so -- -d /dev/ttys0"): http://pastebin.com/pHGNC7k3
Strace output of launching the rild daemon with FML's working radio: http://pastebin.com/LL50FQux
Keep seeing this "Failed to get socket port [7777]" after "Opening tty device /dev/ttys0\n\0", by filtering the previous 2 outputs through sort, uniq, and diff. I think MWisBest fixed something similar by patching the kernel.
My 2 cents. Keep up the great work man!
7175 said:
Thanks @poo706! Looking forward to this.
A few things I collected on the first build:
Logcat error and fatal events ("adb logcat *:E *:F") for camera crash when saving a picture:
Code:
E/AudioTrack(17751): AudioTrack::set : Exit
F/libc (17751): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xf3e0 in tid 18007 (NotificationThr)
E/DEBUG ( 133): AM write failure (32 / Broken pipe)
E/SharedPreferencesImpl( 537): Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
E/Camera (17842): Error 100
E/CAM_CamErrCallback(17842): Got camera error callback. error=100
E/AndroidRuntime(17842): FATAL EXCEPTION: main
E/AndroidRuntime(17842): Process: com.android.camera2, PID: 17842
E/AndroidRuntime(17842): java.lang.RuntimeException: Media server died.
E/AndroidRuntime(17842): at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:33)
E/AndroidRuntime(17842): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$ErrorCallbackForward$1.run(AndroidCameraAgentImpl.java:1099)
E/AndroidRuntime(17842): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(17842): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(17842): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(17842): at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(17842): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(17842): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AudioService( 537): Media server died.
E/MediaPlayerFactory(18162): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(18162): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/MonoPipe(18162): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/SoundTriggerHwService(18162): couldn't load sound trigger module sound_trigger.primary (No such file or directory)
E/AudioService( 537): Media server started.
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
E/audio_a2dp_hw(18162): adev_set_parameters: ERROR: set param called even when stream out is null
Strace output of launching the rild daemon on liquid LP (non-working radio) ("rild -l /vendor/lib/libsec-ril_lte.so -- -d /dev/ttys0"): http://pastebin.com/pHGNC7k3
Strace output of launching the rild daemon with FML's working radio: http://pastebin.com/LL50FQux
Keep seeing this "Failed to get socket port [7777]" after "Opening tty device /dev/ttys0\n\0", by filtering the previous 2 outputs through sort, uniq, and diff. I think MWisBest fixed something similar by patching the kernel.
My 2 cents. Keep up the great work man!
Click to expand...
Click to collapse
Damn dude, your debugging abilities are far greater than mine! The device repos for maguro, toro, and toroplus were all set up in the same fashion : starting with googles latest source (jellybean) and applying a handful of commits authored by ziyan. All three boot. Everything works on maguro, no data on toro, and no voice or data on toroplus.
I gathered these commits from mw's github and figured I might need some or all to fix the radio issues on toro and toroplus. I would greatly appreciate your opinion.
https://github.com/MWisBest/android_bionic/commit/af1fc2a3051992897939980b38ef9da6455f2a73
https://github.com/MWisBest/android...mmit/8994231ced53c29b33200bc04275cafacf48025e
https://github.com/MWisBest/android...mmit/6d5cc7a2044335ee8c3cd042d173a5f4a66e520f
https://github.com/MWisBest/android_hardware_ril/commit/880e828a9424b469d27ec07b800efdb65cddc1af
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/android...mmit/f04c281e50ece48fc93dae62e4d5a5e4f982a567
https://github.com/MWisBest/android...mmit/b700091b6b5fc13b0b17e7fbc8ecb8083234dcea
https://github.com/MWisBest/proprie...mmit/9fc72185943049645c82dccd9f8f8791568d1444
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
[poo]
poo706 said:
Damn dude, your debugging abilities are far greater than mine! The device repos for maguro, toro, and toroplus were all set up in the same fashion : starting with googles latest source (jellybean) and applying a handful of commits authored by ziyan. All three boot. Everything works on maguro, no data on toro, and no voice or data on toroplus.
I gathered these commits from mw's github and figured I might need some or all to fix the radio issues on toro and toroplus. I would greatly appreciate your opinion.
https://github.com/MWisBest/android_bionic/commit/af1fc2a3051992897939980b38ef9da6455f2a73
https://github.com/MWisBest/android...mmit/8994231ced53c29b33200bc04275cafacf48025e
https://github.com/MWisBest/android...mmit/6d5cc7a2044335ee8c3cd042d173a5f4a66e520f
https://github.com/MWisBest/android_hardware_ril/commit/880e828a9424b469d27ec07b800efdb65cddc1af
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/android...mmit/f04c281e50ece48fc93dae62e4d5a5e4f982a567
https://github.com/MWisBest/android...mmit/b700091b6b5fc13b0b17e7fbc8ecb8083234dcea
https://github.com/MWisBest/proprie...mmit/9fc72185943049645c82dccd9f8f8791568d1444
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
[poo]
Click to expand...
Click to collapse
Thanks man, tryin to sharpen up my debug toolbox.
That's great you gathered up all the commits. I think you found exactly what we need.
I didn't see it in the commits, but there's also some toro-radio specific additions to build.prop I noticed in FML's build.prop, some of which may be needed.
Code:
# Set PREFERRED_NETWORK_MODE to GLOBAL in Database for this device
ro.telephony.default_network=7
# Set CDMA SUBSCRIPTION SOURCE to RUIM in Database for this device
ro.telephony.default_cdma_sub=0
# Enable code specific to toro's RIL
ro.telephony.toroRIL=1
# Default CDMA/LTE values from 4.2.2 OTA
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.cdma.otaspnumschema=SELC,1,80,99
7175 said:
Thanks man, tryin to sharpen up my debug toolbox.
That's great you gathered up all the commits. I think you found exactly what we need.
I didn't see it in the commits, but there's also some toro-radio specific additions to build.prop I noticed in FML's build.prop, some of which may be needed.
Code:
# Set PREFERRED_NETWORK_MODE to GLOBAL in Database for this device
ro.telephony.default_network=7
# Set CDMA SUBSCRIPTION SOURCE to RUIM in Database for this device
ro.telephony.default_cdma_sub=0
# Enable code specific to toro's RIL
ro.telephony.toroRIL=1
# Default CDMA/LTE values from 4.2.2 OTA
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.cdma.otaspnumschema=SELC,1,80,99
Click to expand...
Click to collapse
Thanks for the heads up about build.prop. I have a lot of stuff to try, I just need to find the time. Hopefully this weekend.
[poo]
Awesome news
Sent from my Galaxy Nexus using Tapatalk
There's no lag and I like the darker theme too.
I forgot to test the camera when I had it running though.
Did anyone get data to work? I think it just needs the proper apns.
See the unnificial thread. Poo posted a possible fix
nicotheandroidguy said:
Did anyone get data to work? I think it just needs the proper apns.
Click to expand...
Click to collapse
prbadboy69 said:
See the unnificial thread. Poo posted a possible fix
Click to expand...
Click to collapse
It's not an APNs issue, and I didn't post a fix. I think I know what needs to be fixed, but I'll have to put out another build.
[poo]
I saw a new build posted in maguro, excited to see if a new toro build is in the pipeline *waits patiently*
Either way backing up and converting my GNex back to ext4 for now, because I can't wait to try this. Really appreciate your work!
wkr.mky said:
I saw a new build posted in maguro, excited to see if a new toro build is in the pipeline *waits patiently*
Either way backing up and converting my GNex back to ext4 for now, because I can't wait to try this. Really appreciate your work!
Click to expand...
Click to collapse
My plan is to implement a couple of commits that will hopefully fix data and then put out a new toro build tonight or tomorrow.
[poo]
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
poo706 said:
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
Click to expand...
Click to collapse
Nice job man, data is working great with 3g! I'm in a weak area, so I haven't been able to test 4g yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could someone let me know which gapps has a working camera?
7175 said:
Nice job man, data is working great with 3g! I'm in a weak area, so I haven't been able to test 4g yet.
Could someone let me know which gapps has a working camera?
Click to expand...
Click to collapse
Score! Please keep me posted on the 4G situation. I thought our camera problems were because of the new GPU drivers, not anything to do with gapps.
[poo]
poo706 said:
Score! Please keep me posted on the 4G situation. I thought our camera problems were because of the new GPU drivers, not anything to do with gapps.
[poo]
Click to expand...
Click to collapse
Ok, I must have misread something about the gapps camera working. For anyone that needs a working camera on lollipop, I've been using "Camera ZOOM FX".
Also, Smitty's lollipop beta 3 kernel is working great with this new liquid. Details here at this post.
7175 said:
Ok, I must have misread something about the gapps camera working. For anyone that needs a working camera on lollipop, I've been using "Camera ZOOM FX".
Also, Smitty's lollipop beta 3 kernel is working great with this new liquid. Details here at this post.
Click to expand...
Click to collapse
New Smitty is working with LS? I know that it wasn't compatible with CM before and LS is largely CM. Interesting... Is it f2fs compatible? I take it you manually removed the gpu module?
[poo]
poo706 said:
12/27 added to the OP. I expect data to be fixed in this build, if someone could please confirm that.
[poo]
Click to expand...
Click to collapse
"no sim card" error on boot... i dunno....
might just be my phone...screenshots are the same as last build..CMDA-1xRTT...voice:in service/Data: out
arigr said:
"no sim card" error on boot... i dunno....
might just be my phone...screenshots are the same as last build..CMDA-1xRTT...voice:in service/Data: out
Click to expand...
Click to collapse
Hmm, so that makes two bad reports and one good report. Not sure what to make of that.
[poo]
This looks interesting. I'm charging up my toro now, gonna give this a flash and see if I can help with any info on data and signal.
Since fire phone doesn't have a bootloader unlock at the moment. There is no point in building a custom kernel. But By building a kernel we can build kernel modules which work on the stock kernel. And yes you can load unsigned kernel modules without a problem since fire phone doesn't use tz apps to verify kernel modules like Samsung does.
Setup
Source
Download the fire phone sources for firmware 4.6.1 from here. And extract the platfrom.tar inside the archive to somewhere(KERNEL_DIR).
toolchain
You can use the android ndk from google, But it requires some setup. I'm using linaro toolchain from here. You can use compiler version 4.7, 4.8 or 4.9. Kernel I'm using (Firmware 4.6.3 - Linux 3.4-perf-g280c96c) is built with gcc-4.7. But I'm using this gcc-4.9. Download it, extract is somewhere(TOOLCHAIN_DIR) and add the $TOOLCHAIN_DIR/bin to your PATH. Theoretically you would be able to build the kernel on windows using Cygwin or MSYS tools but using Linux is better.
config
Connect your phone trough adb and run
Code:
adb pull /proc/config.gz
zcat config.gz > $KERNEL_DIR/kernel/qcom/3.4/.config
With this config you will run into some problems because of a missing "trapz_generated_kernel.h". I don't know if this is an auto generated file when they build android as a whole or amazon removed this explicitly(can they do that without violating GPL?). Anyway It looks trapz is some low level kernel debugging function(comment here if you know more about it). We can safely disable it. Open $KERNEL_DIR/kernel/qcom/3.4/.config in a text editor and change the lines
Code:
CONFIG_TRAPZ=y
CONFIG_TRAPZ_TP=y
CONFIG_TRAPZ_TRIGGER=y
CONFIG_HAVOK=y
to
Code:
#CONFIG_TRAPZ=y
#CONFIG_TRAPZ_TP=y
#CONFIG_TRAPZ_TRIGGER=y
#CONFIG_HAVOK=y
building
Now edit the $KERNEL_DIR/kernel/qcom/3.4/Makefile and add this changes
Code:
EXTRAVERSION = -perf-g280c96c
This is at the top of the makefile. If we don't add this, vermagic for the modules will differ from stock kernel and they won't load.
ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf-
Click to expand...
Click to collapse
Here arm-linux-gnueabihf- is my cross compiler frefix. Look in $TOOLCHAIN_DIR/bin/ to find it.
Now cd into $KERNEL_DIR/kernel/qcom/3.4/ and do
Code:
make
The build will fail a few times complaining about missing headers. Most of the time it's just
Code:
#include <myheader.h>
instead of
Code:
#include "myheader.h"
Edit the source file where the build fails and change <>s to ""s. (maybe android ndk ignores the difference and include the headers anyway)
After kernel compiles, we are good to go. We can use this kernel sources to build kernel modules for stock kernel.
Kernel modules
To build the kernel modules, we basically need two things. An approximate kernel source and the Module.symvers file from the original kernel. We can get the Module.symvers file by building the complete kernel as explained above or Just extract it from our stock kernel.
To extract the Module.symvers from the stock kernel, extract the boot.img file from firmware update image. Get mkbootimg tools from here compile it and run
Code:
unmkbootimg --kernel zImage ---ramdisk ramdisk.cpio.gz -i boot.img
After you get the zImage. Download extract-symvers script from here and run
Code:
python2 extract-symvers.py -B 0xc0008000 zImage > Module.symvers
place this file in $KERNEL_DIR/kernel/qcom/3.4/ (You still have to do the changes mentioned above in kernel config and building section run make in the $KERNEL_DIR/kernel/qcom/3.4 and intrupt it after few seconds)
Now you can build loadable modules against this source. Here is a hello world kernel module.
Code:
//hello.c
#include<linux/module.h>
#include<linux/kernel.h>
#include<linux/init.h>
static int __init hello_start(void)
{
printk("hello to the world from module");
return 0;
}
static void __exit hello_end(void)
{
printk("heloo exit");
}
module_init(hello_start);
module_exit(hello_end);
Code:
#Makefile
KERNEL_DIR=<your kernel dir>/kernel/qcom/3.4
obj-m := hello.o
PWD := $(shell pwd)
default:
$(MAKE) ARCH=arm CROSS_COMPILE=armeb-linux-gnueabi- -C $(KERNEL_DIR) SUBDIRS=$(PWD) modules
Put this files in a folder and run make in it. Change the paths and cross compiler prefix according to your setup. and run make.
After the build push the hello.ko to the phone.
Code:
adb push hello.ko /sdcard/
adb shell
su
cd sdcard
insmod hello.ko
run dmesg and you'll see the message.
I'm currently trying to build kexec module from hashcode's sources and USB OTG modules.
I'm attaching a few thing helped me do this.
since they have released this version of the fire os they have to provide the source code
see
http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
you have just shown that the source code they releases for the kernel does not match the one used to build the kernel. This means it is a clear violation of the gpl and amazon is in breach and can be sued.
on another note.
are the drivers for the nfc and camera compiled as a module or into the kernel?
They have yet to provide 4.6.3 and 4.6.4 kernel sources too.
I don't know exactly but in order for NFC and camera to work drivers are required and they are in fact compiled into the kernel.
The problem we currently have with NFC and camera is proprietary hal (hardware abstraction libraries) They are a part of Android and does not subject to GPL. Amazon changed the original android way how hal works and didn't release the sources!
by looking at the kernel drivers maybe we would be able to implement hal from scratch. But I don't see that intense dev support for fire phone. If you are up for it camera sources are at $KERNEL_DIR/kernel/qcom/3.4/drivers/media/platform/msm/camera_v2/
Major MAJOR respect for all of you making the Fire Phone even better!
@madushan1000
Could we do something like this to install a custom boot.img?
http://forum.xda-developers.com/optimus-l9/general/guide-install-custom-roms-locked-t3249828
I don't own this device but has anyone tried to see if kexec works?
spudowiar said:
I don't own this device but has anyone tried to see if kexec works?
Click to expand...
Click to collapse
Nope, I was working on it. But then I got a job. It will be sometime before I can start working on it again.
Could someone please provide the config extracted from /proc/config.gz?
I can't find this on CM11 rom for some reason.
Building the kernel now.
Some bugs are in the code and -Wall and gcc-wrapper.py escalate the warnings.
I wonder if those errors are there on purpose XD
helloworld.ko loaded successfully
I was able to execute kexec without anything. Just the binary.
Will keep you posted - this hacking might take a while to figure it all out.
I already have 3.4 kernel from the amazon sources.
I have the kexec userland program.
What is left is a loadable kexec kernel module (if that is possible at all).
removed
Okarin said:
Are we even sure those Amazon Kernel Sources are correct?
Those errors caught by the wrapper scripts are giving me the creeps.
Git the kexec_load.ko build.
Currently hands on insmod.
Phone doesn't do a reboot any longer:
insmod kexec_load.ko
init_module(0xb6e6c008, 408241, "") = -1 ENOENT (No such file or directory)
write(2, "insmod: init_module '/sdcard/kex"..., 79insmod: init_module '/sdcard/kexec_load.ko' failed (No such file or directory)
) = 79
munmap(0xb6e6c000, 409600) = 0
mprotect(0xb6f8c000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0xb6f8c000, 4096, PROT_READ) = 0
close(0) = 0
close(1) = 0
close(2) = 0
futex(0xb6f6cd74, FUTEX_WAKE_PRIVATE, 2147483647) = 0
munmap(0xb6f8c000, 4096) = 0
exit_group(-1) = ?
First goal is to get module loaded.
Goal reached:
kexec_load 27813 0 - Live 0x00000000 (O)
procfs_rw 12770 0 - Live 0x00000000 (O)
wlan 3793980 0 - Live 0x00000000 (O)
Shouldn't be functional at all..
I disabled some function calls just to get the module loaded.
The missing symbols are:
soft_restart
arch_kexec
machine_shutdown
And the version I use does some insane function hooking ..
More rework is needed.
[email protected]:/data/local # ./kexec /sdcard/vmlinux
kernel: 0xaf12d008 kernel_size: 7e1354c
unrecoverable error: could not scan "/proc/device-tree/": No such file or directory
<6>[ 97.681256] Kexec_load: Replacement... :
<6>[ 97.681344] kexec_load : my_syscall_table : c0106244
<6>[ 97.681405] kexec_load : kexec_load before replacement : c01b346c
<6>[ 97.681480] kexec_load : kexec_load after replacement : bf3a5650
<6>[ 97.681546] kexec_load : reboot before replacement : c01a83f0
<6>[ 97.681616] kexec_load : reboot after replacement : bf3a6348
<6>[ 97.681675] Kexec_load: End replacement... :
<6>[ 202.694691] Kexec: - Starting kexec_load...
<6>[ 202.694849] Kexec: - ---- kexec_load - result : '0'
It gets better:
255|[email protected]:/data/local # ./kexec --dtb=/sdcard/zImage-dtb /sdcard/vmlinux
kernel: 0xaf1b1008 kernel_size: 7e1354c
kexec-zImage-arm : dtb.img BEFORE CUT : Start : '0xae66f008' - Length : '0xb411e9' - End : '0xaf1b01f1'
Segmentation fault
More tomorrow.
Click to expand...
Click to collapse
Where are you getting your kexec module sources from? BTW try using the original amazon kernal binary the phone is shipped with (we are sure it works). Don't use the custom kernel for the kexec tests (We don't know the custom kernel actually works)
madushan1000 said:
Where are you getting your kexec module sources from? BTW try using the original amazon kernal binary the phone is shipped with (we are sure it works). Don't use the custom kernel for the kexec tests (We don't know the custom kernel actually works)
Click to expand...
Click to collapse
Here is the thread I used as a starting point.
I will put up my "fork" on github after I get permission to do that
The userland part build like a charm once I took the compiler you recommended.
The kernel-module was tricky because the whole thing is modded like hell.
To be able to load I had to comment out some hard coded addresses and the calls to unresolvable symbols.
removed
Okay the kernel gets loaded.
But
kexec -e shuts off the device.
strace doesn't help.
On the plus side:
Devices are shutdown
Look promising
I need a way to tail dmesg ...
Okay a lot of digging around and I found out that the reboot syscall doesn't work properly..
It doesn't look like it hits the kexec_module it looks more like it hits the actualy sys_reboot
Okay reboot syscall hits my reboot-hook.
But the softreboot doesn't work now.
Okay there is some kind of watchdog runnig which doesn't like my kexec.
I need to kill it - that should happen tomorrow.
removed
I hit the same wall when I tried to isolate the kexec code from the kernel itself to a module. I stopped working on it because I lacked the time. BTW the error you are facing now
<3>[ 80.580644] BUG: scheduling while atomic: kexec/4067/0x00000002
Click to expand...
Click to collapse
is because memory allocator is trying to switch threads while you are in a syscall. it's because of lines like this
image = kzalloc(sizeof(*image), GFP_KERNEL);
Click to expand...
Click to collapse
Try changing GFP_KERNEL to GFP_ATOMIC. Other than that, I have another suggestion. Try to get the kernel to run in a single core mode before running kexec code. This might simplify things. I don't know how to do this though.
madushan1000 said:
I hit the same wall when I tried to isolate the kexec code from the kernel itself to a module. I stopped working on it because I lacked the time. BTW the error you are facing now
is because memory allocator is trying to switch threads while you are in a syscall. it's because of lines like this
Try changing GFP_KERNEL to GFP_ATOMIC. Other than that, I have another suggestion. Try to get the kernel to run in a single core mode before running kexec code. This might simplify things. I don't know how to do this though.
Click to expand...
Click to collapse
The atmic error is gone now. It went away after I disabled the watchtog.
smp_disable() is what you are looking for - but this causes the system to hard_reboot ATM XD
what happens if you kill every userlevel program before smp_disable()?
removed
#define tomorrow
Okay .. I worked out the preemption thing.
At least it does something.
Still a black screen and the MSM_WATCHDOG is a ***** again.
It needs to be suspended .. at least that what I get from the code I read here.
If I remove the driver too early the output in /proc/kmsg stops ..
If I try to remove it too late ... well it causes a resched while atomic.
ROM AOSP 7.1.1
Firmware is based on vendor blobs and kernel(3.10.96) Shield. The kernel was modified for compatibility with the main components of Nexus 9.
The test build for 32-bit versions contains Vulkan and CUDA.
Working:
WIFI, BT, sensors, battery, USB.
does not work:
Cameras, LTE, OTG.
The Date, Cache partition is only supported in the EXT4 format.
The system is 32 bits, which means that the GAPPS set the arm version, not arm64!
You need to reformat the data, Cache partition to remove encryption and change the format to ext4!
No GAPPS included.
ROM AOSP 7.1.1 version from 19-12-17.
Fix termal throtling
HACK slip Lp0. Unfortunately, the dream is not complete. After waking up, the battery charge drops. The indication of the charge value of the battery smoothly comes to the actual state. Battery discharge is about 3% per hour.
ROM Version-1912 Download
Updated the kernel 23-12-17:
- fixed the battery level during sleep.
- fixed the NFC.
Updated the kernel 31-12-18:
- Added support for the WiFi version of the tablet (not completed during the port).
- I altered the definition of interrupts for the panel and sensors.
Install through the recovery on top of the old boot, reinstall the root if necessary.
Download boot.img
AOSP version in the future will not support.
Source:
Device tree
###################################################################################
The ROM version is based on LOS14.1, 32bit, Android 7.1.2.
Firmware is based on vendor blobs and kernel(3.10.96) from Shield. The kernel was modified for compatibility with the main components of Nexus 9.
The build contains Vulkan and CUDA.
Installation through fastboot.
Working:
WIFI, BT, sensors, battery, USB, OTG.
Does not work:
Cameras, LTE.
The Date, Cache partition is only supported in the EXT4 format.
The system is 32 bits, which means that the GAPPS set the arm version, not arm64!
You need to reformat the data, Cache partition to remove encryption and change the format to ext4!
No GAPPS included.
ROM download
Kernel update for LOS 14.1.
Add OTG.
Changes in temperature protection.
Now all the main components should work fine. Including sleep should be less energy-consuming.
download boot.img 29-07-2018
Kernel update for LOS 14.1.
Changes will affect the regulation of supply voltages cpu, gpu, core.
Adding temperature protection.
Stability should be improved and I hope heating will decrease.
download boot.img 05-08-2018
ROM LOS14.1 15-08-2018 download
I think I solved the problem with an error in the game Carmageddon. Replaced a few more libraries in the drivers. Test it on your device.
Updated for the Vendor partition.
Recovery TWRP on 3.10.96 kernel
I recommend Gapps
Open Gapps for ARM 7.1.
Source:
Device tree
###########################################################################
Source:
Kernel
proprietary_vendor_nvidia
What is the recommended vendor image for this rom?
Huzaifa7755 said:
What is the recommended vendor image for this rom?
Click to expand...
Click to collapse
It does not matter what. This section is not used.
All drivers in the system partition.
Except for obviously enabling Vulcan, the fact that this ROM is a 32 bit build could help with the memory issues of this tablet. This is pretty exciting...
I'm going to install tonight and see if I can't get some insight on the situation. This rom crushes the api overhead test for vulkan. Its pretty ridiculous was sccored over 100000. I pulled a log from sleeping from power button. You can search sleep and you will see the input event and again when the screen is back on. There is a uid_cputime error coming up between the 2, don't know if that has anything to do with anything but il post the log.
Sent from my Huawei Nexus 6P using XDA Labs
10-14 02:32:43.538 D/hwcomposer(216): void hwc_blank_display(nvhwc_context*, int, int): display 0: [1 -> 0]
10-14 02:32:43.538 D/hwcomposer(216): Display 0 device size is 1536 x 2048
10-14 02:32:43.539 D/hwcomposer(216): Display 0 device clip is (0, 0, 1536, 2048)
10-14 02:32:43.539 D/hwcomposer(216): virtual int dc_display::set_blank(int): display 0, [1 -> 0]
I think when waking from sleep it is choosing the wrong resolution. I bet this is what is causing that wonkiness after wake. Im not sure if im right or not im just showing you what i am seeing.
didnt1able said:
I'm going to install tonight and see if I can't get some insight on the situation. This rom crushes the api overhead test for vulkan. Its pretty ridiculous was sccored over 100000.
Sent from my Huawei Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I apologize, I do not understand your English. Google translator gives something that is not understandable.
I'm talking about these two proposals.
didnt1able said:
This rom crushes the api overhead test for vulkan. Its pretty ridiculous was sccored over 100000.
Click to expand...
Click to collapse
uid_optime is disabled in the kernel configuration. I'll try to turn it on and see how this will affect the situation.
Vartom said:
I apologize, I do not understand your English. Google translator gives something that is not understandable.
I'm talking about these two proposals.
Click to expand...
Click to collapse
I appologize just testing your rom, if i can help at all i will do my best.
didnt1able said:
I appologize just testing your rom, if i can help at all i will do my best.
Click to expand...
Click to collapse
Could you rephrase this? Could you rephrase this? or write in more detail which tests you ran?
This rom crushes the api overhead test for vulkan. Its pretty ridiculous was sccored over 100000.
Vartom said:
Could you rephrase this? Could you rephrase this? or write in more detail which tests you ran?
This rom crushes the api overhead test for vulkan. Its pretty ridiculous was sccored over 100000.
Click to expand...
Click to collapse
https://www.futuremark.com/benchmarks/3dmark/android The test in this program "api overhead"
didnt1able said:
https://www.futuremark.com/benchmarks/3dmark/android The test in this program "api overhead"
Click to expand...
Click to collapse
Thank you. Now I understand.
Vartom said:
Thank you. Now I understand.
Click to expand...
Click to collapse
You are welcome
Scores I received, very high
This Rom looks promising. Hope the sleep feature will be working in the future versions.
Sent from my LG-D802 using Tapatalk
Vartom said:
Source:
Kernel
Click to expand...
Click to collapse
Default branch gtest+f2fs is what you compile for the ROM? Or V31096test? I'm interested into make some tests for my own with your kernel...
Thanks!
Edit: Someone can confirm if Google Play Games works? I have a message that says: "Google Play Games is having trouble with Google Play services. Please try again."
Code:
10-18 01:21:24.643 350 362 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.play.games/com.google.android.gms.games.ui.destination.main.MainActivity bnds=[18,1140][268,1469] (has extras)} from uid 10049 on display 0
10-18 01:21:24.688 2597 2597 W PopupManager: You have not specified a View to use as content view for popups. Falling back to the Activity content view. Note that this may not work as expected in multi-screen environments
10-18 01:21:24.694 2597 2597 W ActionBarDrawerToggle: DrawerToggle may not show up because NavigationIcon is not visible. You may need to call actionbar.setDisplayHomeAsUpEnabled(true);
10-18 01:21:24.713 2597 2597 I PowerUpApplication: gms version installed: 11530
10-18 01:21:24.999 350 379 I ActivityManager: Displayed com.google.android.play.games/com.google.android.gms.games.ui.destination.main.MainActivity: +346ms
10-18 01:21:25.056 1106 1119 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.083 1106 2647 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.184 1106 2647 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.220 2597 2597 I DestFragActivityBase: Connection to service apk failed with error 19
10-18 01:21:25.221 2597 2597 E GoogleApiAvailability: Unexpected error code 19
jolinnard said:
Default branch gtest+f2fs is what you compile for the ROM? Or V31096test? I'm interested into make some tests for my own with your kernel...
Thanks!
Edit: Someone can confirm if Google Play Games works? I have a message that says: "Google Play Games is having trouble with Google Play services. Please try again."
Code:
10-18 01:21:24.643 350 362 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.play.games/com.google.android.gms.games.ui.destination.main.MainActivity bnds=[18,1140][268,1469] (has extras)} from uid 10049 on display 0
10-18 01:21:24.688 2597 2597 W PopupManager: You have not specified a View to use as content view for popups. Falling back to the Activity content view. Note that this may not work as expected in multi-screen environments
10-18 01:21:24.694 2597 2597 W ActionBarDrawerToggle: DrawerToggle may not show up because NavigationIcon is not visible. You may need to call actionbar.setDisplayHomeAsUpEnabled(true);
10-18 01:21:24.713 2597 2597 I PowerUpApplication: gms version installed: 11530
10-18 01:21:24.999 350 379 I ActivityManager: Displayed com.google.android.play.games/com.google.android.gms.games.ui.destination.main.MainActivity: +346ms
10-18 01:21:25.056 1106 1119 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.083 1106 2647 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.184 1106 2647 W GamesServiceBroker: Client connected with SDK 11411000, Services 11530436, and Games 52250036
10-18 01:21:25.220 2597 2597 I DestFragActivityBase: Connection to service apk failed with error 19
10-18 01:21:25.221 2597 2597 E GoogleApiAvailability: Unexpected error code 19
Click to expand...
Click to collapse
V31096test of course.
I achieved a little progress in solving the problem with sleep. The CPU is now asleep and wakes up with no errors. Now the problem is different, something with a memory sleep mode.
I did not try Google Play Games.
I asked about progress with porting kernel in other Vartom thread. And you sad, that it's impossible. And a mounth - two after - i see this. Thank you very much for work) maybe one day we will see Mount and Blade on Nexus 9 ^^
Wondering if anyone else has done any further testing on this extremely promising ROM and what their findings are ?
Not having google play games working is unfortunately a deal breaker for me ATM but as soon as this is confirmed to be working I think I'll take the plunge and try to use this !!
the.teejster said:
Wondering if anyone else has done any further testing on this extremely promising ROM and what their findings are ?
Not having google play games working is unfortunately a deal breaker for me ATM but as soon as this is confirmed to be working I think I'll take the plunge and try to use this !!
Click to expand...
Click to collapse
Vartom says there's a bug in regards to memory when waking from sleep. So just wait until that is resolved
Unfortunately my knowledge is not enough to solve this problem. The sleep mode LP0 does not work.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Remarks:
This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
Once everything is mature, an official build may be possible.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Also make sure you've got the correct firmware installed before installing LineageOS.
More detailed instructions at:
Install LineageOS on crackling
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...
Donate to support development:
Donate via PayPal to LineageOS
Changelog
06.12.2021
updated lineage sources
11.09.2021
fixed livedisplay
updated lineage sources
22.07.2021
initial version
reserved
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
petexd said:
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
Click to expand...
Click to collapse
Livedisplay is not working at the moment.
I had to remove it because it wouldn't load my photos and I didn't have time to play around with it. It's actually my only phone. It did, however, instal basic flamegapps.
I also got error 255 when tryin to restore my backup but I'm up and running now with 17.1. I'll try 18.1 again soon when I have more time to mess around with it and if I can sort out error 255
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
ajjin0 said:
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
Click to expand...
Click to collapse
I've got so less time at the moment. I hope I'll find some to continue the work.
New build is up. Livedisplay is working now.
Download
Wow great work.
@115ek Thank you for the new build.
I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
Spoiler
Code:
01-01 21:28:58.399 4357 4357 I [email protected]: LiveDisplay HAL service is starting.
01-01 21:28:58.404 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.510 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.512 220 220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
01-01 21:28:58.512 4357 4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
01-01 21:28:58.513 4357 4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
01-01 21:28:58.514 4357 4357 E [email protected]: LiveDisplay HAL service is shutting down.
01-01 21:28:58.521 0 0 I init : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
01-01 21:28:58.521 0 0 I init : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
01-01 21:28:58.521 0 0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
01-01 21:28:59.391 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:28:59.391 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
01-01 21:28:59.393 219 4360 W libc : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
01-01 21:28:59.395 0 0 E init : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
01-01 21:29:00.392 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:29:00.392 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
My local manifest looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
<project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
<project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
<project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
</manifest>
Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.
mmustermann717 said:
Does your manifest look the same?
Click to expand...
Click to collapse
This should be fine, yes.
mmustermann717 said:
Are there any additional patches I have to apply to get it working?
Click to expand...
Click to collapse
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
Thank you very much! That worked.
I increased the system partition, a little while ago and backups were restoring OK so I've decided to try 18.1 again.
I must say, it performs really well for the stuff I need. I also like that I can now do calendar etc backups to my sdcard. Much more sensible IMO.
Thanks 115ek. A great job.
I'd like to have a go at building but I'm not sure where to start without the explicit menu like 17.1
Thanks to 115ek for the 18.1 set up and to mmustermann717 for his local manifest. I have managed to build 18.1 after a few errors which appeared to be out of memory problems.
I fixed that and was able to complete the build.
Thanks both of you
I was too quick to brag. Im getting a boot loop. I made the changes from 115ek's response #12, so I don't know where I've gone wrong.
Can either of you tell me please?
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
I've tried all of this several times. I get a successful build but a boot loop every time.
The lineage source says successful, it doesn't actually boot so I have no idea how to find any error? Is there anything I can look for? Or can you guess?
I'd appreciate the help if you can. Thanks.
Hey
petexd said:
how to find any error?
Click to expand...
Click to collapse
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
petexd said:
Or can you guess?
Click to expand...
Click to collapse
You could, but I'm not sure if that really helps.
petexd said:
Is there anything I can look for?
Click to expand...
Click to collapse
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
This is the line you asked about:
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.selinux=permissive
I've tried my build with your boot.img but it still bootloops.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I've tried again and the last 4 lines of the build are:
2021-10-18 16:11:33 - ota_from_target_files.py - INFO : done.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Compressing system.new.dat with brotli
warning radio-update: no radio image in input target_files; not flashing radio
[100% 24/24] build bacon
Package Complete: out/target/product/crackling/lineage-18.1-20211018-UNOFFICIAL-crackling.zip
#### build completed successfully
Is this OK? I thought bacon was another phone (oneplus?)
Hey
115ek said:
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I get this , just bfore the build completes successfully. Do you know if this has anything to do with the problem.
99% 463/464] Package OTA: out/target/product/crackling/lineage_crackling-ota-eng.pet
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/build.prop
Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com
09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse
MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.
MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.
12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse
Bug....the touch does not work and it seems to reboot intermittently
Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?
MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!
Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.
Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770
20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
Hello, what changes between this rom and the stock based roms ?