[ROM][11.0][OFFICIAL][guacamoleb] Descendant 11.5 [14-07-2021] - OnePlus 7 ROMs, Kernels, Recoveries, & Other Devel
{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page.
Sources
Github
Kernel
Same as any ROM.
Do the necessary wipes and flash the ROM.
No wipes are needed between updates from Descendant itself, unless specified.
If you're having problem with SafetyNet, please, install Magisk along the following modules:
SafetyPatcher, Magisk Hide Props or similar modules.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included along Kiwi Browser and Metro.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct
Android OS version: 11.0
Security patch level: March
XDA:DevDB Information
Descendant XI, ROM for the OnePlus 7
Contributors
Dil3mm4
ROM OS Version: Android 11
ROM Kernel: Linux 4.14.222
Based On: AOSP
Version Information
Status: Stable
Created 2021-03-13
Last Updated 2021-03-13
Thank you for keeping our device alive
Rom have beautiful UI, BUT it no have customization like CrDroid, poor speed via mobile internet, , hasn`t advanced power menu
Sakuma_Eitarou said:
Rom have beautiful UI, BUT it no have customization like CrDroid, poor speed via mobile internet, , hasn`t advanced power menu
Click to expand...
Click to collapse
Not every ROM looks for customisation. And this is by far best UI ROM I've been privileged enough to try out. If you look for customisation head over to Evo X or Kang OS.
@DigiGoon THREAD CLOSED as non-compliant with GPLv2 and download link removed.
Please check your conversations and advise the moderators team (best via the report function) to re-open the thread when ready to provide a link to your kernel source. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke
EDIT: @DigiGoon Thread has been re-opened.
Make a proper installation guide. "Neccessary wipes" and and following "ROM flash" resulted in my device deleting the os and rebooting to recovery ;/ This is by the way also not the way most custom roms get installed on this device. Most require an Oxygen flash before....
Alright for anybody facing issues like me...
1. Install CLEAN Android 10. I did come from Oxygen11 rollback when it did not work...
2. Unlock bootloader.... boot to TWRP with fastboot
3. Format data, reboot to bootloader, boot TWRP with fastboot
4. Flash ROM, reboot to bootloader, boot TWRP with fastboot
5. Flash Magisk, reboot to system
6. Finish Magisk installation by opening it... it will ask for additional installation, do it and ready ;D
-> Nevertheless... i really like the rom. It's as fast as Oxygen, has the few important customizations options i expect but finally a custom rom that is an innovation
-> Speakers sound off compared to Oxygen since Dolby Atmos is not included. However you can install this module and the speakers will sound just like on Oxygen: https://github.com/reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
-> Volume control on the side reacts poorly ... please move a little bit away from the side. Would be nice if the Oxygen Cam would be included for Pro mode or slow motion
trueToastedCode said:
Make a proper installation guide. "Neccessary wipes" and and following "ROM flash" resulted in my device deleting the os and rebooting to recovery ;/ This is by the way also not the way most custom roms get installed on this device. Most require an Oxygen flash before....
Alright for anybody facing issues like me...
1. Install CLEAN Android 10. I did come from Oxygen11 rollback when it did not work...
2. Unlock bootloader.... boot to TWRP with fastboot
3. Format data, reboot to bootloader, boot TWRP with fastboot
4. Flash ROM, reboot to bootloader, boot TWRP with fastboot
5. Flash Magisk, reboot to system
6. Finish Magisk installation by opening it... it will ask for additional installation, do it and ready ;D
-> Nevertheless... i really like the rom. It's as fast as Oxygen, has the few important customizations options i expect but finally a custom rom that is an innovation
-> Speakers sound off compared to Oxygen since Dolby Atmos is not included. However you can install this module and the speakers will sound just like on Oxygen: https://github.com/reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
-> Volume control on the side reacts poorly ... please move a little bit away from the side. Would be nice if the Oxygen Cam would be included for Pro mode or slow motion
Click to expand...
Click to collapse
I recomend DTSX Ultra, more better sound
trueToastedCode said:
Make a proper installation guide. "Neccessary wipes" and and following "ROM flash" resulted in my device deleting the os and rebooting to recovery ;/ This is by the way also not the way most custom roms get installed on this device. Most require an Oxygen flash before....
Alright for anybody facing issues like me...
1. Install CLEAN Android 10. I did come from Oxygen11 rollback when it did not work...
2. Unlock bootloader.... boot to TWRP with fastboot
3. Format data, reboot to bootloader, boot TWRP with fastboot
4. Flash ROM, reboot to bootloader, boot TWRP with fastboot
5. Flash Magisk, reboot to system
6. Finish Magisk installation by opening it... it will ask for additional installation, do it and ready ;D
-> Nevertheless... i really like the rom. It's as fast as Oxygen, has the few important customizations options i expect but finally a custom rom that is an innovation
-> Speakers sound off compared to Oxygen since Dolby Atmos is not included. However you can install this module and the speakers will sound just like on Oxygen: https://github.com/reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
-> Volume control on the side reacts poorly ... please move a little bit away from the side. Would be nice if the Oxygen Cam would be included for Pro mode or slow motion
Click to expand...
Click to collapse
If you aren't new then you would have known the common flashing procedure, over 11 you won't be able to install any ROM yet, and since I didn't mentioned specifically to flash OOS, its not necessary, if already on OOS 10.
Also volume panel is designed that way.
Thanks for the feedback though.
DigiGoon said:
If you aren't new then you would have known the common flashing procedure, over 11 you won't be able to install any ROM yet, and since I didn't mentioned specifically to flash OOS, its not necessary, if already on OOS 10.
Also volume panel is designed that way.
Thanks for the feedback though.
Click to expand...
Click to collapse
As a dev you ALWAYS have to think of the most stupid stuped user. Otherwise problems will always occur.
I know what the concept of the volume panel is. But this does not change anything that it could be reached easier while having the same concept.
trueToastedCode said:
As a dev you ALWAYS have to think of the most stupid stuped user. Otherwise problems will always occur.
I know what the concept of the volume panel is. But this does not change anything that it could be reached easier while having the same concept.
Click to expand...
Click to collapse
I don't wanna think man, I already have a group of people in TG who are polite enough to ask for the solutions of their problem rather than "ordering" around and are always up to try something new. I build it because I like it as it is, so it'll stay as it is, and no feature request or any other changes which aren't broken will be acknowledged, sorry for that.
Love the UI in this rom. There are thoughtful additions everywhere. Like for example the volume bar mentioned above can actually be tweaked a bit to show an expandable arrow. The options are a bit too hidden imo though, but that's personal taste.
Running the rom on GM1901. SystemUI crashes when a fingerprint authentication window is invoked. Here's the logcat crash:
Code:
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime FATAL EXCEPTION: main
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime Process: com.android.systemui, PID: 10601
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime android.view.InflateException: Binary XML file line #17 in com.android.systemui:layout/auth_biometric_fingerprint_view: Attempt to invoke virtual method 'void android.widget.Button.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.Button.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthBiometricView.onFinishInflateInternal(AuthBiometricView.java:639)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthBiometricView.onFinishInflate(AuthBiometricView.java:598)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.rInflate(LayoutInflater.java:1134)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1082)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.inflate(LayoutInflater.java:680)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.inflate(LayoutInflater.java:532)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthContainerView.<init>(AuthContainerView.java:286)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthContainerView$Builder.build(AuthContainerView.java:170)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.buildDialog(AuthController.java:490)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.showDialog(AuthController.java:403)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.showAuthenticationDialog(AuthController.java:318)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.statusbar.CommandQueue$H.handleMessage(CommandQueue.java:1195)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.os.Handler.dispatchMessage(Handler.java:106)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.os.Looper.loop(Looper.java:223)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.app.ActivityThread.main(ActivityThread.java:7660)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at java.lang.reflect.Method.invoke(Native Method)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
ashikns said:
Love the UI in this rom. There are thoughtful additions everywhere. Like for example the volume bar mentioned above can actually be tweaked a bit to show an expandable arrow. The options are a bit too hidden imo though, but that's personal taste.
Running the rom on GM1901. SystemUI crashes when a fingerprint authentication window is invoked. Here's the logcat crash:
Code:
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime FATAL EXCEPTION: main
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime Process: com.android.systemui, PID: 10601
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime android.view.InflateException: Binary XML file line #17 in com.android.systemui:layout/auth_biometric_fingerprint_view: Attempt to invoke virtual method 'void android.widget.Button.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.Button.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthBiometricView.onFinishInflateInternal(AuthBiometricView.java:639)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthBiometricView.onFinishInflate(AuthBiometricView.java:598)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.rInflate(LayoutInflater.java:1134)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1082)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.inflate(LayoutInflater.java:680)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.view.LayoutInflater.inflate(LayoutInflater.java:532)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthContainerView.<init>(AuthContainerView.java:286)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthContainerView$Builder.build(AuthContainerView.java:170)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.buildDialog(AuthController.java:490)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.showDialog(AuthController.java:403)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.biometrics.AuthController.showAuthenticationDialog(AuthController.java:318)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.systemui.statusbar.CommandQueue$H.handleMessage(CommandQueue.java:1195)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.os.Handler.dispatchMessage(Handler.java:106)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.os.Looper.loop(Looper.java:223)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at android.app.ActivityThread.main(ActivityThread.java:7660)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at java.lang.reflect.Method.invoke(Native Method)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
2021-04-01 18:10:39.636 10601 10601 Error AndroidRuntime at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Click to expand...
Click to collapse
Known issue, will be fixed.
can I only get this build from Android 10? or is it also from the latest openbeta4? flash via twrp is currently not feasible because twrp breaks.is there another way to flash this ROM?
mu1989 said:
can I only get this build from Android 10? or is it also from the latest openbeta4? flash via twrp is currently not feasible because twrp breaks.is there another way to flash this ROM?
Click to expand...
Click to collapse
Nop, from A10
[UPDATE 09-05-2021]
OnePlus 7 (guacamoleb) Changelog:
- Based on OOS11 blobs, from guacamoleb, so clean flash required
- Fixed: Signal strength issue for 5Ghz WiFi
- Fixed: HDR in Netflix
- Fixed: Widevine L1 (You should have L1 on OOS)
- Added: Alert slider UI
- Added: GCam & removed GCamGO
- Fixed: FOD speed and detection rate
- DeviceSettings cleanup as we have LiveDisplay now
NOTE:
You need to be on OOS 11, TWRP won't boot directly on OOS11, so you can follow the below procedure.
OnePlus 7 (guacamoleb) flashing instructions:
Case 1:
If you already are on Descendant or OOS 10 with TWRP.
- Boot to TWRP
- Format Data to F2FS
- Reboot to TWRP
- Flash latest stable OOS 11 + TWRP installer (it'll get flashed on slot 1)
- Reboot to TWRP
- Flash latest stable OOS 11 + TWRP installer (it'll get flashed on slot 2)
- Reboot to TWRP
- Format data to F2FS
- Reboot to TWRP
- Flash Descendant + TWRP installer
- Reboot to TWRP
- Flash DFE to stay decrypted so that TWRP stays
Case 2:
If you are on OOS 11.
- Do MSM Tool with your region specific build to get back to OOS 10 or downgrade to OOS 10 with downgrade package
- Follow Case 1
[UPDATE 16-06-2021]
Changelog:
- Updated blobs from OOS 11.0.1.1
- Build is now enforcing
- Switched to Galt's Kernel
- Kernel compiled with Proton Clang
- Optimized native executables for Cortex-A76 CPU
- Switched audio policy & volume tables from OOS
- Userdata uses f2fs now
- Added: Freeform windows
- Dropped: ext4 support
- Dropped: sdcardfs
NOTE:
Since sdcardfs is dropped normal flashing with TWRP won't work.
Steps:
- Boot to bootloader
- Boot to provided YAAP recovery
- Format data using YAAP recovery
- Boot to bootloader
- Boot to provided TWRP recovery
- ADB Sideload the ROM file
DigiGoon said:
[UPDATE 16-06-2021]
Changelog:
- Updated blobs from OOS 11.0.1.1
- Build is now enforcing
- Switched to Galt's Kernel
- Kernel compiled with Proton Clang
- Optimized native executables for Cortex-A76 CPU
- Switched audio policy & volume tables from OOS
- Userdata uses f2fs now
- Added: Freeform windows
- Dropped: ext4 support
- Dropped: sdcardfs
NOTE:
Since sdcardfs is dropped normal flashing with TWRP won't work.
Steps:
- Boot to bootloader
- Boot to provided YAAP recovery
- Format data using YAAP recovery
- Boot to bootloader
- Boot to provided TWRP recovery
- ADB Sideload the ROM file
Click to expand...
Click to collapse
What is the instruction for dirty flash?
Suman.Ghosh.218 said:
What is the instruction for dirty flash?
Click to expand...
Click to collapse
You can't dirty flash.
DigiGoon said:
You can't dirty flash.
Click to expand...
Click to collapse
Wasn't expecting that. I am on the previous build, clean flash will wipe all my data. So every time new build comes I need to clean flash?
Suman.Ghosh.218 said:
Wasn't expecting that. I am on the previous build, clean flash will wipe all my data. So every time new build comes I need to clean flash?
Click to expand...
Click to collapse
This time you need to.
Related
[Q] Whatsapp Keep Crashing in MIUIv5 For Huawei Ascend P6.
Dear Sir, I Am Using Huawei P6. Someone Recently Port MIUIV5 For Our Device ROM Is Working Properly Only This Missing Is Whatsapp Is Not Working. When We Open Whatsapp it Keep Crashing. I Installed Whatsapp+ Also Same Thing. i Clear Cache And Tried Everything i Can. Older Version Of Whatsapp Is Working. But Older Version Will Work For More 10 Days Then It Will Ask For Update. Please Help Me If YOu Can. Here Is Log : java.lang.VerifyError: com/b at com.whatsapp.App.onCreate(App.java:507) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java) at android.app.ActivityThread.handleBindApplication(ActivityThread.java) at android.app.ActivityThread.access$1300(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java) at android.os.Handler.dispatchMessage(Handler.java) at android.os.Looper.loop(Looper.java) at android.app.ActivityThread.main(ActivityThread.java) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java) at dalvik.system.NativeStart.main(Native Method)
[Q] No implementation found for native ResampleInputStream;.fir21:([BI[BII)V
I built my AOSP JB for a tablet, including all necessary customizations (project details discussed over here: https://groups.google.com/forum/#!forum/renesas-emev-osp). I'm now in the clean-up stage, with a list of "minor" issues being debugged and hopefully removed. One of these is the use of Google Voice Search, which fails with this message: Unfortunately, Voice Search has stopped I've attached the complete logcat at http://pastebin.com/K1ces0Ai. Latest lines are those from the failure above. I think these are the critical ones: W/dalvikvm( 1130): No implementation found for native Lcom/google/android/voicesearch/endpointer/ResampleInputStream;.fir21[BI[BII)V W/dalvikvm( 1130): threadid=16: thread exiting with uncaught exception (group=0x40a46300) E/AndroidRuntime( 1130): FATAL EXCEPTION: Thread-122 E/AndroidRuntime( 1130): java.lang.UnsatisfiedLinkError: Native method not found: com.google.android.voicesearch.endpointer.ResampleInputStream.fir21[BI[BII)V E/AndroidRuntime( 1130): at com.google.android.voicesearch.endpointer.ResampleInputStream.fir21(Native Method) I found this in JB source code: ./frameworks/base/media/jni/android_media_ResampleInputStream.cpp where fir21 is implemented, but it looks like it hasn't been compiled, or not correctly compiled. Could it be? I looked at http://developer.android.com/training/articles/perf-jni.html#faq_ULE too, but it's been of little help. Enabling debug logs I can see the library being loaded and methods registered: I/MediaPlayerJNI( 72): JNI_OnLoad registering functions... I/ResampleInputStream( 72): android/media/ResampleInputStream JNI registering So I don't understand why, when java requires "fir21" from ResampleInputStream JNI, it can't find it. Naming should be correct, I guess... (this is all OOB AOSP code). Any suggestions a bout how to debug this? Thanks in advance!
[Q] troubles with apktool
hello there, i'm trying to add translations to MiuiExpress APK (http://xitong.xiaomi.com/index) decompile and recompile went well, but when i launch the APK on my phone it crash with the following fc log :
HTML:
{"platform":"4.4.2","exception_class":"java.lang.RuntimeException","error_type":"fc","build_version":"9a658b46e5","imei":"","package_name":"com.miui.miuilite","device":"Nexus 4","stack_track":"java.lang.RuntimeException: Unable to create service com.xiaomi.mms.transaction.SmsService: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.app.Application.getPackageName()' on a null object reference
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2602)
at android.app.ActivityThread.access$1800(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5081)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:607)\nCaused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.app.Application.getPackageName()' on a null object reference
at com.xiaomi.mms.transaction.SmsService.onCreate(SmsService.java:36)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2592)
... 8 more\n","app_version":"1.0.1","network":"Orange F","exception_source_method":"android.app.ActivityThread.handleCreateService"}, processName is com.miui.miuilite
any idea what is the problem ? thanks you much
PS: even if i don't touch the APK after recompiling it i got the same error on my phone i use apktool 2.0.0 BETA 9
[20141217] Unofficial CM12
Use at your own risk - untested I am not responsible for bricked devices. Back up before doing anything Compiled using the following device tree: https://github.com/CyanogenMod/android_device_sony_z3c Working: Nothing, as far as I am concerned which is why you should use at your own risk.Not Working: Everything, as far as I am concerned which is why you should use at your own risk. The commands I used to make zip package was: Code: . build/envsetup.sh lunch make bacon (Brunch and Breakfast are for official devices only, I believe) Local Manifest includes: Code: <project name="CyanogenMod/android_device_sony_z3c" path="device/sony/z3c" remote="github" /> <project name="CyanogenMod/android_device_sony_shinano-common" path="device/sony/shinano-common" remote="github" /> <project name="CyanogenMod/android_kernel_sony_msm8974" path="kernel/sony/msm8974" remote="github" /> <project name="CyanogenMod/android_device_sony_qcom-common" path="device/sony/qcom-common" remote="github" /> <project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" /> <project name="CyanogenMod/android_device_sony_msm8974-common" path="device/sony/msm8974-common" remote="github" /> <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" /> File can be found in Downloads Tab And, Mirror: AndroidFileHost XDA:DevDB Information ROM compilation, ROM for the Sony Xperia Z3 Compact Contributors m0d Thank you to Kali- and chirayudesai for setting up device tree at: android_device_sony_z3c And, thank you to the people who spared the time in correcting my silly mistakes, and for responding to my even sillier questions. ROM OS Version: 5.0.x Lollipop Version Information Status: Testing Created 2014-12-15 Last Updated 2014-12-17
No clue how you managed to build, I've been trying for days! Anyhow, booted it up and it restarts repeatedly at the 'starting system apps' stage. Here's a logcat: Code: https://bpaste.net/show/6aaa730e0985 ---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ---------- Gairtial said: No clue how you managed to build, I've been trying for days! Anyhow, booted it up and it restarts repeatedly at the 'starting system apps' stage. Here's a logcat: Code: https://bpaste.net/show/6aaa730e0985 Click to expand... Click to collapse I should also mention that the installation initially failed. The device calls itself 'aries', not 'd5803'. Had to modify the script in the ZIP before flashing.
Gairtial said:
No clue how you managed to build, I've been trying for days!
Click to expand...
Click to collapse
Magic!
But, there is no magic.
Send me your build error,
And also the error for show commands and I will try to help.
As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks.
Gairtial said:
I should also mention that the installation initially failed. The device calls itself 'aries', not 'd5803'. Had to modify the script in the ZIP before flashing.
Click to expand...
Click to collapse
Yes, someone mentioned that before.
Not sure where to look.
I did find this in BoardConfig.mk,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c
And, in init.sony.usb.rc - this:
Code:
on boot
write /sys/class/android_usb/android0/iSerial ${ro.serialno}
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
The problem is sony calls the device aries, the code for the device is d5803, and the device tree by cm12 is z3c.
I like z3c but if anyone knows where, maybe one of the mk files, to make the changes?
Any help appreciated. I am learning as I go and as I said above:
Thank you to the people who take the time to correct my silly mistakes, and for responding to my even sillier questions
Click to expand...
Click to collapse
I only compiled device tree, no changes as of yet, other than small fixes for compilation.
m0d said: Magic! But, there is no magic. Send me your build error, And also the error for show commands and I will try to help. As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks. Click to expand... Click to collapse The build errors started with libtime_genoff.so being missing from the output directory so I manually copied it over and it continued on fine. There were some issues with AAPT but I manually fixed those (and submitted patches for review to Gerrit). Just waiting for the build to complete now. Are you on IRC/Hangouts or something? Mind if I PM you so we can talk a little more freely?
m0d said:
Magic!
But, there is no magic.
Send me your build error,
And also the error for show commands and I will try to help.
As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks.
Yes, someone mentioned that before.
Not sure where to look.
I did find this in BoardConfig.mk,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c
And, in init.sony.usb.rc - this:
Code:
on boot
write /sys/class/android_usb/android0/iSerial ${ro.serialno}
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
The problem is sony calls the device aries, the code for the device is d5803, and the device tree by cm12 is z3c.
I like z3c but if anyone knows where, maybe one of the mk files, to make the changes?
Any help appreciated. I am learning as I go and as I said above:
I only compiled device tree, no changes as of yet, other than small fixes for compilation.
Click to expand...
Click to collapse
Check your build.prop in your compiled build folder (/system) and look for the variables below:
"ro.product.device" "ro.build.product"
If you want to change the values, mount your system.img, make your changes and make new .img
(PM me if you need help with this..)
it's not hard to delect the first sentence in updater-script in zip,then we could get it flashed
Okay, did my own build using similar instructions and came up with the following issues: libtime_genoff.so wasn't copied during the build process, manually copying required manually copying a second time after the build. DPI was first set to 480 in build.prop. Reset it to 320 through ADB after booting and it works fine On the first boot the modem appeared to work (connected to my network), on the second it did not. Nothing I can understand in ADB that's relevant. Wifi appears to work properly Camera crashes GPS error message: Code: D/LocSvc_utils_cfg( 5088): D/loc_read_conf: using /etc/gps.conf D/LocSvc_utils_cfg( 5088): D/loc_set_config_entry: PARAM DEBUG_LEVEL = 2 E/gpsone_dmn( 5088): gpsone_glue_pipeget:46] /data/misc/gsiff_ctrl_q, mode = 2 E/gpsone_dmn( 5088): gpsone_glue_pipeget:50] pipe_name: /data/misc/gsiff_ctrl_q failed: 13 E/gsiff_dmn( 5088): W/gsiff_dmn_init: Unable to initialize Message Queue! E/gsiff_dmn( 5088): W/gsiff_loc_api_close: Improperly closing Loc API Client! E/gsiff_dmn( 5088): W/gsiff_dmn_destroy: Could not destroy loc api! E/gsiff_sp_glue( 5088): W/sp_destroy: Sensor provider not initialized. Sensor provider = 0 E/gsiff_dmn( 5088): W/gsiff_dmn_destroy: Could not destroy sensor provider rc = 0! E/gpsone_dmn( 5088): gpsone_glue_piperemove:92] fd = -1, /data/misc/gsiff_ctrl_q E/LocSvc_utils_ll( 5088): W/linked_list_destroy: Invalid list parameter! F/libc ( 5088): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 5088 (gsiff_daemon) I/DEBUG ( 263): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 263): Build fingerprint: 'Sony/D5803/D5803:4.4.4/23.0.A.2.105/lvf_Rw:user/release-keys' I/DEBUG ( 263): Revision: '0' I/DEBUG ( 263): ABI: 'arm' I/DEBUG ( 263): pid: 5088, tid: 5088, name: gsiff_daemon >>> /system/bin/gsiff_daemon <<< I/DEBUG ( 263): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8 W/NativeCrashListener( 732): Couldn't find ProcessRecord for pid 5088 I/DEBUG ( 263): r0 00000008 r1 93475f55 r2 93475f55 r3 93475f55 E/DEBUG ( 263): AM write failure (32 / Broken pipe) I/DEBUG ( 263): r4 00000008 r5 b4f539a4 r6 00000000 r7 b4f539a0 I/DEBUG ( 263): r8 00000003 r9 b6f9a098 sl 00000001 fp b6f94da0 I/DEBUG ( 263): ip b6c5dfbc sp be91f9b8 lr b6f116d1 pc b6f115b6 cpsr 600f0030 I/DEBUG ( 263): I/DEBUG ( 263): backtrace: I/DEBUG ( 263): #00 pc 000145b6 /system/lib/libc.so (pthread_mutex_trylock+3) I/DEBUG ( 263): #01 pc 000146cd /system/lib/libc.so (pthread_mutex_destroy+4) I/DEBUG ( 263): #02 pc 00002157 /system/lib/libgps.utils.so (msg_q_destroy+66) I/DEBUG ( 263): #03 pc 00001a85 /system/bin/gsiff_daemon I/DEBUG ( 263): #04 pc 00002af3 /system/bin/gsiff_daemon I/DEBUG ( 263): #05 pc 0000fbb9 /system/lib/libc.so (__libc_init+44) I/DEBUG ( 263): #06 pc 00001968 /system/bin/gsiff_daemon I/DEBUG ( 263): I/DEBUG ( 263): Tombstone written to: /data/tombstones/tombstone_ Camera messages: Code: E/cacao ( 7380): 1459692 cacao_chokoball.cpp (4914) 9002 E [CKB] ckb preCompile fail. keymgr create credmgr context. W/cacao ( 7380): 1459761 cacao_chokoball.cpp (4923) 9002 W [CKB] Post process preLoad(0xffffff90) E/mm-camera-sensor( 297): sony_sensor_power_up:1138,error E/mm-camera-sensor( 297): sony_sensor_power_up:1145,error I/Adreno-EGL( 7613): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: RGURRAM_AU_LINUX_ANDROID_LNX.LA.3.5.2.2_RB1.04.04.04.087.030+PATCH[ES]_msm8974_LNX.LA.3.5.2.2_RB1__release_ENGG () I/Adreno-EGL( 7613): OpenGL ES Shader Compiler Version: E031.24.00.15 I/Adreno-EGL( 7613): Build Date: 08/12/14 Tue I/Adreno-EGL( 7613): Local Branch: I/Adreno-EGL( 7613): Remote Branch: quic/LNX.LA.3.5.2.2_rb1 I/Adreno-EGL( 7613): Local Patches: 8b00bd16f3c1d9d35a2fa902df5e679888d2b2e3 Fixes an llvm crash with mini dEQP apk I/Adreno-EGL( 7613): 38bad22e162dead4e008444520a0144c78a347bd Fixes a potential dEQP crash. I/Adreno-EGL( 7613): ce345e1c45c2ae2d1fb2cb125c8d2574f1af5f95 Rev I/OpenGLRenderer( 7613): Initialized EGL, version 1.4 D/OpenGLRenderer( 7613): Enabling debug mode 0 E/mm-camera( 297): cpp_module_set_clock_freq:1015] clk:133330000, dim:0, stream_type:0, D/mm-camera( 297): mct_pipeline_process_set:command=800000e E/cammw ( 7380): E: void* cammw_util_msg_cli_open(const char*, int32_t, cammw_util_msg_callbacks_t, uint32_t, cammw_any_t, uint32_t, cammw_any_t): connect err -1 E/cammw ( 7380): E: cammw_link_isp_cli_open: msg_cli_open fail E/cammw ( 7380): E: cammw_camera_isp_create: isp create fail E/cammw ( 7380): E: cammw_camera_open: isp socket create error E/cammw ( 7380): E: cammw_camera_isp_destroy: invalid arg E/cammw ( 7380): E: cammw_camera_sensor_destroy: invalid arg E/cammw ( 7380): E: cammw_link_sensor_cli_close: invalid arg handle = 0x0 E/cammw ( 7380): E: cammw_err_t cammw_util_ashmem_free(cammw_buf_t*): Invalid Arg E/cammw ( 7380): E: cammw_err_t cammw_util_ashmem_free(cammw_buf_t*): Invalid Arg D/mm-camera( 297): mct_pipeline_process_set:command=800000b D/mm-camera-sensor( 297): module_sensor_stop_session:700 session 1 E/cald ( 7380): 1463787 excal_system.cpp (221) 7891 E [EXC] Camera can't open. E/cald ( 7380): 1463850 excal_system.cpp (447) 7891 E [EXC] system init is failed. General E/cald ( 7380): 1463930 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: DebugMgr is not found E/cald ( 7380): 1463984 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: BufMgr is not found E/cald ( 7380): 1464037 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: DB is not found I/cacao ( 7380): 1465315 pal.cpp (3383) 7891 I [INF] PAL_Delete I/cald ( 7380): 1470629 cald_client.c (2051) 7891 I [INF] Cald_Client_Create E/libcamera( 7380): failed to create Cald instance E/libcamera( 7380): createInstance: failed startCamera I/libcamera( 7380): HAL_openCameraHardware: X created hardware=0x0 E/CameraWrapper( 7380): vendor camera open fail E/CameraClient( 7380): Could not open camera 0: -19 E/CameraClient( 7380): initialize: Camera 0: unable to initialize device: No such device (-19) I/CameraClient( 7380): Destroying camera 0 D/NuPlayerDriver( 7380): reset(0xb460d040) D/NuPlayerDriver( 7380): notifyResetComplete(0xb460d040) D/NuPlayerDriver( 7380): reset(0xb460d1c0) D/NuPlayerDriver( 7380): notifyResetComplete(0xb460d1c0) W/CameraManager( 8386): Error querying camera device 0 for listing. I/CameraService( 7380): getCameraCharacteristics: Switching to HAL1 shim implementation... I/libcamera( 7380): HAL_getCameraInfo: E cameraId=1 I/libcamera( 7380): HAL_getCameraInfo: X I/libcamera( 7380): HAL_getCameraInfo: E cameraId=1 I/libcamera( 7380): HAL_getCameraInfo: X ---------- Post added at 06:15 AM ---------- Previous post was at 06:06 AM ---------- Sorry, noticed a few things were out of date. in my tree. Previous post may not be correct. I'll be doing another build tonight after extracting vendor blobs and syncing properly and I'll post with more results.
Uploading new build I made with following:
I added to check for aries as well:
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c,aries
Which updates update script to:
Code:
assert(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" || getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" || getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" || getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || abort("This package is for device: D5803,D5833,z3c,aries; this device is " + getprop("ro.product.device") + "."););
nelvinchi said:
Check your build.prop in your compiled build folder (/system) and look for the variables below:
"ro.product.device" "ro.build.product"
If you want to change the values, mount your system.img, make your changes and make new .img
(PM me if you need help with this..)
Click to expand...
Click to collapse
Build prop is not the problem, consistency is.
Code:
ro.product.name=D5803
ro.build.product=z3c
ro.product.device=z3c
CM uses the above. Sony uses aries.
So I guess checking for all three, and the variation(D5833) should work in the end.
jsscx said:
it's not hard to delect the first sentence in updater-script in zip,then we could get it flashed
Click to expand...
Click to collapse
No, but that is not ideal. It should check the for the correct device.
But, the problem is that there is no consistency so I guess checking for all four should do it - D5803,D5833,z3c,aries.
Gairtial said:
Okay, did my own build using similar instructions and came up with the following issues:
libtime_genoff.so wasn't copied during the build process, manually copying required manually copying a second time after the build.
DPI was first set to 480 in build.prop. Reset it to 320 through ADB after booting and it works fine
On the first boot the modem appeared to work (connected to my network), on the second it did not. Nothing I can understand in ADB that's relevant.
Wifi appears to work properly
Camera crashes
---------- Post added at 06:15 AM ---------- Previous post was at 06:06 AM ----------
[/COLOR]Sorry, noticed a few things were out of date. in my tree. Previous post may not be correct. I'll be doing another build tonight after extracting vendor blobs and syncing properly and I'll post with more results.
Click to expand...
Click to collapse
I am not sure if I had any problems with "libtime_genoff.so", I checked the proprietary files list and it is in none of them.
The aapt was fixed in a commit, z3c.mk is now
Code:
PRODUCT_AAPT_CONFIG := normal hdpi xhdpi
PRODUCT_AAPT_PREF_CONFIG := xhdpi
And it compiled fine.
DPI also had a commit to change to 320.
So doing a repo sync should fix those previous issues.
I believe there was an issue with proprietary files as the proprietary-files.txt has been updated.
And now I have no errors when extracting files, so maybe camera files now are getting tranferred.
Review with updated changes just for z3c - http://review.cyanogenmod.org/#/q/status:merged+project:CyanogenMod/android_device_sony_z3c,n,z
Maybe a commit will be needed to fix update script as mentioned above,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c,aries
I believe there is a pull request with that specific change as well.
Thank you all for responses
Added to OP: Mirror: AndroidFileHost Also, Please submit feedback. All issues are welcome
so here's quick test: boot with animation,when the app starting screen lasts a few seconds,then restart. https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
jsscx said: so here's quick test: boot with animation,when the app starting screen lasts a few seconds,then restart. https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0 Click to expand... Click to collapse The name of the zip package you used will be helpful, i.e. 20141215 or 20141219
19
jsscx said: so here's quick test: boot with animation,when the app starting screen lasts a few seconds,then restart. https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0 Click to expand... Click to collapse Maybe @jerpelea could help as more than one person has been encountering this issue. jsscx said: 19 Click to expand... Click to collapse Uploaded new build only on AFH, Mirror: AndroidFileHostThe repo sync includes these commits, http://review.cyanogenmod.org/#/c/82475/ http://review.cyanogenmod.org/#/c/82465/
I can confirm the issue with the start loop. Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off. EDIT - Also had to delete first line of updater script to get it to install - The built in recovery still didn't let me install using 'apply' update, i had to use CWM 6.0.5.0 from AndroPlus Kernel to flash it - Updater script recognized my device as 'Amami' when i don't have any reference to it in my build.prop, all value were D5803 Regards
spida_singh said: I can confirm the issue with the start loop. Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off. Regards Click to expand... Click to collapse I had the same problem and I could not test the rom
spida_singh said: EDIT - Also had to delete first line of updater script to get it to install - The built in recovery still didn't let me install using 'apply' update, i had to use CWM 6.0.5.0 from AndroPlus Kernel to flash it - Updater script recognized my device as 'Amami' when i don't have any reference to it in my build.prop, all value were D5803 Regards Click to expand... Click to collapse Not sure why it is recognizing your device as Amami. I added 'aries' to the assert so it should work. I am creating zip packages using "make bacon", by default CM uses CWM so it is not surprising that you must use CWM to flash it. As for built-in recovery, I am not sure, as it gets created automatically with the build. Maybe changes are needed. spida_singh said: I can confirm the issue with the start loop. Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off. Click to expand... Click to collapse Burakki said: I had the same problem and I could not test the rom Click to expand... Click to collapse I may have found why 'com.qualcomm.location.apk' was crashing, It seems devs are trying to move it from 'app' to 'priv-app': Code: -app/com.qualcomm.location.apk:priv-app/com.qualcomm.location/com.qualcomm.location.apk Changing 'proprietary-files.txt' from the above to Code: -app/com.qualcomm.location.apk might fix that issue. Compiling with change to see if it works.
m0d said: It seems devs are trying to move it from 'app' to 'priv-app' Click to expand... Click to collapse Any reason behind why this is trying to be done? Hasn't it always been inside app?
someone755 said: Any reason behind why this is trying to be done? Hasn't it always been inside app? Click to expand... Click to collapse No, not sure. On Stock ROM it is located in app; however, somewhere along the line CM devs are moving it to priv-app. The change I made does not seem to make a difference and I can not seem to find where are they moving it to priv-app Android.mk in 'vendor/sony/shinano-common' Code: include $(CLEAR_VARS) LOCAL_MODULE := com.qualcomm.location LOCAL_MODULE_OWNER := sony [COLOR="SeaGreen"]LOCAL_SRC_FILES := proprietary/priv-app/com.qualcomm.location/com.qualcomm.location.apk[/COLOR] LOCAL_MODULE_TAGS := optional LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX) LOCAL_MODULE_CLASS := APPS LOCAL_CERTIFICATE := platform LOCAL_PRIVILEGED_MODULE := true include $(BUILD_PREBUILT) And, it is being copied to: out/target/product/z3c/system/priv-app/com.qualcomm.location I am not sure if this is of any concern, but from the logs com.qualcomm.location.apk looks like the root of the issue as everything dies after it encounters: Code: E/installd( 269): DexInv: --- END '/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk' --- status=0x0100, process failed D/AndroidRuntime( 4634): Shutting down VM E/AndroidRuntime( 4634): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
I tested it's working great..
Just a heads up! Cyanogenmod now has an official nightly for the Sony Xperia Z3 compact. You can download their nighty builds from here: http://download.cyanogenmod.org/?device=z3c
[Xposed][MODULE][4.0+] XInternalSD [v4.8] Exception on Redmi Note S1
Here is log. OS: MIUI 8. Any fix or work around I can try? Appreciate in advance. --- Loading Xposed v54 (for Zygote)... Running ROM 'KTU84P' with fingerprint 'Xiaomi/gucci/gucci:4.4.4/KTU84P/6.12.22:user/release-keys' Loading modules from /data/app/com.pyler.xinternalsd-1.apk Loading class com.pyler.xinternalsd.XInternalSD java.lang.IllegalStateException: Unable to get package info for com.miui.securitycenter.dynamic; is package not installed? at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:368) at android.app.LoadedApk.getClassLoader(LoadedApk.java:321) at de.robv.android.xposed.XposedBridge$3.afterHookedMethod(XposedBridge.java:249) at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:645) at android.app.LoadedApk.<init>(Native Method) at java.lang.reflect.Constructor.constructNative(Native Method) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at android.app.ContextCompat.createLoadedApk(ContextCompat.java:58) at android.app.ContextCompat.createApplicationContext(ContextCompat.java:27) at com.miui.securitycenter.dynamic.ApkLoader.getDynamicContext(ApkLoader.java:164) at com.miui.securitycenter.dynamic.DynamicServiceManager.createOrUpdateManagerWT(DynamicServiceManager.java:145) at com.miui.securitycenter.dynamic.DynamicServiceManager.connectWT(DynamicServiceManager.java:127) at com.miui.securitycenter.dynamic.DynamicServiceManager.access$400(DynamicServiceManager.java:20) at com.miui.securitycenter.dynamic.DynamicServiceManager$DynamicWorkHandler.handleMessage(DynamicServiceManager.java:193) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:136) at android.os.HandlerThread.run(HandlerThread.java:61)
It has nothing with this module.