Database Develop

[ROM][6.0][Read OP!]Official nightly Cyanogenmod 13 for Peregrine

Please search the thread and read the OP before postings to reduce the numbers of unneeded reposting by everyone.
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0(MM), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed. Micro gapps is recommend as it fits and provides everything in a base package you will need for gapps support you can install the other google apps from the store as want later on.
Remember nightly builds are experimental they can and will be broken from time to time. Always have a backup at hand.
Storage in Marshmallow is dynamically mounted. That means you will get a prompt at boot to mount as either portable storage or internal storage. Use portable storage to continue using it as like in previous versions of android.
To transfer file to PC when plugged in you will get the charging mode prompt status in the status bar click it to change from charging mode to transfer files.
TWRP cannot read internal formatted sdcards at the moment in order to flash a new nightly try one of these suggestions -
Adb sideloading - http://forum.xda-developers.com/showpost.php?p=64194455&postcount=398
USB OTG - http://forum.xda-developers.com/showpost.php?p=64194957&postcount=401
Using PC file manager to place the file where TWRP can see it - http://forum.xda-developers.com/showpost.php?p=64194157&postcount=397
TWRP 3 now supports internal formatted sdcards - http://forum.xda-developers.com/moto-g/4g-development/unofficial-twrp-3-0-0-0-moto-g-lte-t3310450
If you want to use Supersu see here for non-systemless root. For systemless root use a zip from the SuperSu page othwerwise inbuilt superuser from development settings works fine.
Having issues with Titanium Backup? This should help - https://www.youtube.com/watch?v=DrOuUtlqz9w&ab_channel=AbhinavSrivastava
Want to mount system as read write for apps like Adaway use this(For builds before 29 Nov 2015)
Builds 29Nov 2015+ from a terminal app use
Code:
su
mount -o rw,remount /system
then after changes use
Code:
mount -o ro,remount /system
to mount it back as read-only or reboot.
what doesn't work:
-You tell me as am not sure atm [emoji14]
Downloads:
Older Unofficial builds
Official builds nightly builds
Install instructions:
IMPORTANT! When coming from older builds to CM13 24 Nov+ builds if you have FCs with phone
LuK1337 said:
From now after flashing 20151121 build you will have to remove /data/data/com.android.providers.telephony/databases/telephony.db file due to db scheme updates. Otherwise com.android.phone crash will happen.
You can use TWRP file manager to do it.
Click to expand...
Click to collapse
Contrary to popular belief(me included) wiping between versions is not needed - https://plus.google.com/u/0/+DanPasanen/posts/GKnirTFjojg
Coming from an official CM12.1 rom
Reboot to recovery
Install Rom
Optional Gapps, Kernel, etc
Reboot
Make sure to install Gapps before booting are you will have FCs with Setup wizard.
Coming from a different rom or stock
Wipe data and cache
Flash the CM13zip
Install opengapps or any other perffered gapps if you want
Reboot
Profit
Changelog - http://www.cmxlog.com/13/peregrine/
Source:
base: https://github.com/CyanogenMod
kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-13.0
Device: https://github.com/CyanogenMod/android_device_motorola_msm8226-common/tree/cm-13.0, https://github.com/CyanogenMod/android_device_motorola_peregrine/tree/cm-13.0
Vendor: https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-13.0
Rest of the stuff is all unmerged stuff from gerrit
Credits:- (not in a order)
AOSParadox team @h2o64
@luca020400 @LuK1337
@srisurya95 for helping me spot my error with compiling.
CM Team
Google
Motorola
And any one else that I forgot to mention [emoji14]

Thanks a lot for this, I'll test on weekend
Enviado desde mi XT1040 mediante Tapatalk

keep up the good work

Whoa, thank you! <3

First of all, thanks! Just installed it.
In the first boot, when cm confugration wizard started, I tried to change language, and system soft rebooted, never to boot up again. Tried it a couple of times with same result. Wiping data/cache solves the issue. So using it in english for now. I will report if more things come up!
Edit: After installing cm, installed gapps, and upon booting the "setup wizard had to close" (or similar xD) message appeared once and again. This happened the 2 times I tried.

gartzen said:
First of all, thanks! Just installed it.
In the first boot, when cm confugration wizard started, I tried to change language, and system soft rebooted, never to boot up again. Tried it a couple of times with same result. Wiping data/cache solves the issue. So using it in english for now. I will report if more things come up!
Edit: After installing cm, installed gapps, and upon booting the "setup wizard had to close" (or similar xD) message appeared once and again. This happened the 2 times I tried.
Click to expand...
Click to collapse
Same here

I have the same problem when i try to change language. Is someone also having a problem of fc with titanium backup ?

Nice work, the only issue i have ran into at the moment is when you go Under More in settings and go into Mobile networks you get an FC on com.android.phone posted the logcat below for you
Code:
10-22 20:06:34.340 646 656 I art : Background partial concurrent mark sweep GC freed 22291(1385KB) AllocSpace objects, 6(120KB) LOS objects, 33% free, 23MB/35MB, paused 2.507ms total 133.930ms
10-22 20:06:34.341 31441 31441 D AndroidRuntime: Shutting down VM
10-22 20:06:34.350 31441 31441 E AndroidRuntime: FATAL EXCEPTION: main
10-22 20:06:34.350 31441 31441 E AndroidRuntime: Process: com.android.phone, PID: 31441
10-22 20:06:34.350 31441 31441 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=13; index=13
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.ListPreference.getEntry(ListPreference.java:220)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.ListPreference.getSummary(ListPreference.java:165)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.Preference.onBindView(Preference.java:558)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.Preference.getView(Preference.java:495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.PreferenceGroupAdapter.getView(PreferenceGroupAdapter.java:246)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.AbsListView.obtainView(AbsListView.java:2346)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.makeAndAddView(ListView.java:1875)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.fillDown(ListView.java:702)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.fillFromTop(ListView.java:763)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.layoutChildren(ListView.java:1684)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.AbsListView.onLayout(AbsListView.java:2148)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1586)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutHorizontal(LinearLayout.java:1732)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1497)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1586)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:336)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:273)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.widget.ActionBarOverlayLayout.onLayout(ActionBarOverlayLayout.java:493)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:336)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:273)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.policy.PhoneWindow$DecorView.onLayout(PhoneWindow.java:2678)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:2171)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1931)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1107)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6013)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:858)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:670)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:606)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5417)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
10-22 20:06:34.356 646 1619 W ActivityManager: Force finishing activity com.android.phone/.MobileNetworkSettings
10-22 20:06:34.359 646 1619 W ActivityManager: Force finishing activity com.android.settings/.SubSettings
10-22 20:06:34.365 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.407 8632 8632 I art : Explicit concurrent mark sweep GC freed 2328(136KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 13MB/22MB, paused 708us total 41.399ms
10-22 20:06:34.414 646 882 I OpenGLRenderer: Initialized EGL, version 1.4
10-22 20:06:34.431 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.466 8632 8632 I art : Explicit concurrent mark sweep GC freed 584(33KB) AllocSpace objects, 0(0B) LOS objects, 39% free, 13MB/22MB, paused 594us total 34.252ms
10-22 20:06:34.466 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.499 8632 8632 I art : Explicit concurrent mark sweep GC freed 5(160B) AllocSpace objects, 0(0B) LOS objects, 40% free, 13MB/22MB, paused 555us total 32.508ms
10-22 20:06:34.537 8632 8706 E Surface : getSlotFromBufferLocked: unknown buffer: 0xb90366d0
10-22 20:06:34.538 8632 8706 D OpenGLRenderer: endAllStagingAnimators on 0xb9328d68 (ListView) with handle 0xb90440e0
10-22 20:06:34.860 646 663 W ActivityManager: Activity pause timeout for ActivityRecord{b1c66fa u0 com.android.phone/.MobileNetworkSettings t133 f}
10-22 20:06:35.004 8632 8632 D DashboardSummary: rebuildUI took: 88 ms
10-22 20:06:37.131 6307 6434 D audio_hw_primary: out_standby: enter: stream (0xb8446ac0) usecase(1: low-latency-playback)
10-22 20:06:37.182 6307 6434 D hardware_info: hw_info_append_hw_type : device_name = speaker-lite
10-22 20:06:38.408 253 367 I ThermalEngine: Sensor:xo_therm_pu2:25000 mC

• Camera crashes (Cannot connect to the camera error) right after you take a picture
• Facebook crashes as soon as you start to write your username on the login screen
• File Manager crashes (some kind of "no privileges" error)

I also don't have the option to set Google Now launcher as default launcher, like if it wasn't installed, but it works with Nova Launcher.
edit : problem solve after rebooting sorry

Camera has already been fixed on Falcon's build... so it's just a mater of time @Kayant merges it!

I have also seen the issues with camera, file manager, TB. Can't really say too much because my limited knowledge doesn't give me too much insight into what exactly is going on but am going through some logs and will see what I can understand from them. @ebol94 I already had the camera fix merged in but maybe is because I don't have an updated lib which is why it's not completed fixed? Will test that in a build later.

Kayant said:
I have also seen the issues with camera, file manager, TB. Can't really say too much because my limited knowledge doesn't give me too much insight into what exactly is going on but am going through some logs and will see what I can understand from them. @ebol94 I already had the camera fix merged in but maybe is because I don't have an updated lib which is why it's not completed fixed? Will test that in a build later.
Click to expand...
Click to collapse
You need to add this branch to your repo in order to use the new libs
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" revision="cm-13.0" />
By the way, I managed to get working data but not LTE on my build, but I'm not quite sure the state of yours since I haven't flashed it. Could anybody tell me? :silly:
Nevermind, LTE is working good here too . So far there's pretty much everything working, the only thing left is that I'm not having my sdcard partition mounted (at least on my build). Maybe it can be forced through terminal, I'll try later. How about on this build?
Regards!

beeeto said:
You need to add this branch to your repo in order to use the new libs
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" revision="cm-13.0" />
By the way, I managed to get working data but not LTE on my build, but I'm not quite sure the state of yours since I haven't flashed it. Could anybody tell me? :silly:
Nevermind, LTE is working good here too . So far there's pretty much everything working, the only thing left is that I'm not having my sdcard partition mounted (at least on my build). Maybe it can be forced through terminal, I'll try later. How about on this build?
Regards!
Click to expand...
Click to collapse
I already have the necessary things. The only thing that may have changed is h2o64's lib being newer than luk1337's one
There's how SDcard works in MM now because you can choose to use it as internal storage so how it mounts at boot has changed - http://source.android.com/devices/storage/config.html
You need to click the notification and choose which option you want.

Kayant said:
I already have the necessary things. The only thing that may have changed is h2o64's lib being newer than luk1337's one
There's how SDcard works in MM now because you can choose to use it as internal storage so how it mounts at boot has changed - http://source.android.com/devices/storage/config.html
You need to click the notification and choose which option you want.
Click to expand...
Click to collapse
My lib is based o, the 5.1 blobs, and Luk's one is based off 5.0.2.
So if you wanna use mine, you must have all the other libs from 5.1
PS : I like the "not in order" xD :justkidding:

h2o64 said:
My lib is based o, the 5.1 blobs, and Luk's one is based off 5.0.2.
So if you wanna use mine, you must have all the other libs from 5.1
PS : I like the "not in order" xD :justkidding:
Click to expand...
Click to collapse
Hey you should hunt srisurya95 down for that
Thanks for the heads up.

Great work guys! I love it
One quick question: is the mobile radio active bug still present? On Lollipop, Chrome and Google Play Services are killing my battery for no apparent reason.

I have a question, if I install this Alpha build on my Motorola Moto G when the nightly builds start would it be a case of simply upgrading to this from the device via Cyanogenmod updates?

also, what recovery did you guys use? I am currently running CM recovery but its very basic and no options for nandroid backup so looking to do this before trying out CM13

ceanth said:
also, what recovery did you guys use? I am currently running CM recovery but its very basic and no options for nandroid backup so looking to do this before trying out CM13
Click to expand...
Click to collapse
I am using the TWRP-v2.8.7.0 from here - http://forum.xda-developers.com/mot...ection-somcom3xs-experimental-corner-t2996266

[ROM][WIP][AOSP][01/12/2015][6.0]Android Open Source Project for Yureka

{
"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"
}
This is a initial Work in Progress AOSP release for Yu yureka. It is bound to contain small bugs and you are warned about it at the start. So read what works and what doesn't below.
Release notes :
Initial AOSP release based on latest google release tag r26
This is pure AOSP and as u know it won't contain any sort of feature stuff ! ( this includes basic apps like messaging,file manager,etc.. You will have to download them from playstore )
What works ?
Wifi
Bluetooth
All functionality of RIL
Camera
All other basic functionalities ( Basic apps seem to be working )
Titanium backup works fine
You say more !
Broken stuff :
None as far as i know ( unsure about data connection mode switch )
Flashing procedure :
General steps ( Wipe cache/data and wipe dalvik )
Flash ROM zip followed by gapps
Reboot and have fun !
Downloads :
AOSP for Yu yureka
XDA:DevDB Information
AOSP, ROM for the YU Yureka
Contributors
Santhosh M
Source Code: https://github.com/sandymanu/sandy_lettuce_8916
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2015-12-03
Created 2015-12-03
Last Updated 2016-05-01

Reserved
Reserved

Wow! Great. I will try it shortly

Bug report:
com.android.phone has stopped working
Sim is detected for a second and then the phone process crashes
Logcat
Code:
12-06 22:33:20.787: E/Telecom(1025): : getUserSelectedOutgoingPhoneAccount
12-06 22:33:20.787: E/Telecom(1025): java.lang.NumberFormatException: Invalid long: "89910397390154602114"
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.invalidLong(Long.java:124)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parse(Long.java:366)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parseLong(Long.java:353)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parseLong(Long.java:321)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.PhoneAccountRegistrar.getUserSelectedVoicePhoneAccount(PhoneAccountRegistrar.java:245)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.PhoneAccountRegistrar.getUserSelectedOutgoingPhoneAccount(PhoneAccountRegistrar.java:226)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.TelecomServiceImpl$1.getUserSelectedOutgoingPhoneAccount(TelecomServiceImpl.java:102)
12-06 22:33:20.787: E/Telecom(1025): at com.android.internal.telecom.ITelecomService$Stub.onTransact(ITelecomService.java:82)
12-06 22:33:20.787: E/Telecom(1025): at android.os.Binder.execTransact(Binder.java:453)
12-06 22:33:20.789: E/AndroidRuntime(5935): FATAL EXCEPTION: main
12-06 22:33:20.789: E/AndroidRuntime(5935): Process: com.android.phone, PID: 5935
12-06 22:33:20.789: E/AndroidRuntime(5935): java.lang.IllegalArgumentException: Invalid long: "89910397390154602114"
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Parcel.readException(Parcel.java:1603)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Parcel.readException(Parcel.java:1552)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.telecom.ITelecomService$Stub$Proxy.getUserSelectedOutgoingPhoneAccount(ITelecomService.java:640)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.telecom.TelecomManager.getUserSelectedOutgoingPhoneAccount(TelecomManager.java:462)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry.setupAccounts(TelecomAccountRegistry.java:466)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry.-wrap0(TelecomAccountRegistry.java)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry$1.onSubscriptionsChanged(TelecomAccountRegistry.java:283)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.telephony.SubscriptionManager$OnSubscriptionsChangedListener$1.handleMessage(SubscriptionManager.java:386)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Handler.dispatchMessage(Handler.java:102)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Looper.loop(Looper.java:148)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.app.ActivityThread.main(ActivityThread.java:5417)
12-06 22:33:20.789: E/AndroidRuntime(5935): at java.lang.reflect.Method.invoke(Native Method)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

chiragjn said:
Bug report:
com.android.phone has stopped working
Sim is detected for a second and then the phone process crashes
Logcat
Code:
12-06 22:33:20.787: E/Telecom(1025): : getUserSelectedOutgoingPhoneAccount
12-06 22:33:20.787: E/Telecom(1025): java.lang.NumberFormatException: Invalid long: "89910397390154602114"
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.invalidLong(Long.java:124)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parse(Long.java:366)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parseLong(Long.java:353)
12-06 22:33:20.787: E/Telecom(1025): at java.lang.Long.parseLong(Long.java:321)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.PhoneAccountRegistrar.getUserSelectedVoicePhoneAccount(PhoneAccountRegistrar.java:245)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.PhoneAccountRegistrar.getUserSelectedOutgoingPhoneAccount(PhoneAccountRegistrar.java:226)
12-06 22:33:20.787: E/Telecom(1025): at com.android.server.telecom.TelecomServiceImpl$1.getUserSelectedOutgoingPhoneAccount(TelecomServiceImpl.java:102)
12-06 22:33:20.787: E/Telecom(1025): at com.android.internal.telecom.ITelecomService$Stub.onTransact(ITelecomService.java:82)
12-06 22:33:20.787: E/Telecom(1025): at android.os.Binder.execTransact(Binder.java:453)
12-06 22:33:20.789: E/AndroidRuntime(5935): FATAL EXCEPTION: main
12-06 22:33:20.789: E/AndroidRuntime(5935): Process: com.android.phone, PID: 5935
12-06 22:33:20.789: E/AndroidRuntime(5935): java.lang.IllegalArgumentException: Invalid long: "89910397390154602114"
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Parcel.readException(Parcel.java:1603)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Parcel.readException(Parcel.java:1552)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.telecom.ITelecomService$Stub$Proxy.getUserSelectedOutgoingPhoneAccount(ITelecomService.java:640)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.telecom.TelecomManager.getUserSelectedOutgoingPhoneAccount(TelecomManager.java:462)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry.setupAccounts(TelecomAccountRegistry.java:466)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry.-wrap0(TelecomAccountRegistry.java)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.services.telephony.TelecomAccountRegistry$1.onSubscriptionsChanged(TelecomAccountRegistry.java:283)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.telephony.SubscriptionManager$OnSubscriptionsChangedListener$1.handleMessage(SubscriptionManager.java:386)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Handler.dispatchMessage(Handler.java:102)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.os.Looper.loop(Looper.java:148)
12-06 22:33:20.789: E/AndroidRuntime(5935): at android.app.ActivityThread.main(ActivityThread.java:5417)
12-06 22:33:20.789: E/AndroidRuntime(5935): at java.lang.reflect.Method.invoke(Native Method)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
12-06 22:33:20.789: E/AndroidRuntime(5935): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Click to expand...
Click to collapse
Did u clean flash with full system wipe ?

Santhosh M said:
Did u clean flash with full system wipe ?
Click to expand...
Click to collapse
Yes ,Twice ,Same result
Wipe System
Wipe Data + Cache
Flash Rom
Reboot

chiragjn said:
Yes ,Twice ,Same result
Wipe System
Wipe Data + Cache
Flash Rom
Reboot
Click to expand...
Click to collapse
Definitely not possible :/ There are more than a hundred people using the ROM and have seen no one reporting the issue. ( the activity of the ROM is more in yu forums. You could come there and post ur query and u would surely get help ). BTW, i have released a new build today which you can try and see if u again end up here ?

ntfs canot mount and there in no usb mass storage option

How to get root access in this rom ? Any specific version of supersu which works?

can anyone revert on battery backup of this rom please !!

rApt0r7 said:
How to get root access in this rom ? Any specific version of supersu which works?
Click to expand...
Click to collapse
If possible I should install custom recovery with adb & fastboot (my favorite is TWRP).
Booting into custom recovery and install supersu 2.61

I was able to get AICP 6.0 rom working on my yureka. CM 13 never booted for me. Problem with aosp is it does not have on screen navigation keys ( I am too used to that ).
Does anyone have problem of facebook app crashing everytime? I have this problem on aosp as well as aicp roms for marshmallow.

first of all thanks a lot man!! really smooth experience.
i wanted to ask about the sd card fix. what is its purpose and where i can find the file.
the link provided no longer has the file.
thank you in advance.

YUreka AospExtended-v6.0-tomato-20180913-0401-ALPHA.zip
i try to install the AospExtended-v6.0-tomato-20180913-0401-ALPHA.zip rom but ended with error with error : 7
pls help

[ROM][6.0.1_r68][Official] Exodus Android 6 for Onyx

{
"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"
}
ABOUT:
Team Exodus brings you EXODUS Rom, coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new, original improvements and coding with the highest standards.
INSTALLATION:
Take necessary backups
Be rooted w/ a custom recovery
Download EXODUS Rom & Gapps for your device and move them to your phone
Reboot to Recovery
Wipe (full wipe if coming from another Rom)**
Flash the Rom
Flash the Gapps**
Reboot to System
Setup and Reboot System
These directions are not necessary after the first install if you use the Exodus Updater, included in the ROM. It can notify you of updates, download, and install them for you automatically.
**This is automated if coming from a previous Exodus build (Dirty Flashing).
We recommend using our stock (preinstalled) kernel for best results and usage of all features!
SOURCES:
Exodus official build:
http://exodus-developers.net/exodus-6.0/onyx/
GApps:
Any 6.0.x GApps of your choice, we recommend opengapps.org
----- Advanced Developers/Users Section----
Rom source:
https://github.com/TeamExodus
Kernel source:
kernel_oneplus_onyx
Gerrit code review system:
http://review.exodus-developers.net
COMMUNITY
For additional support, info, and updates please join us in the official Google+ community:
https://plus.google.com/communities/106801227383087889476
Crowdin project:
Help us with translating to support your native language!
CREDITS:
Thank you to all the members, contributors, and maintainers on the Exodus Android team.
Please see our source for an unabridged list of contributions, authorship, and cherry-picks.
SUPPORT/DONATION:
If you would like to thank us for our work or help in support server costs you can do so here:
Primedirective (Team Leader / Project Owner / Server hosting)
MartinRo (Project Owner / Server hosting)
Raja. M (Senior Developer / Project Owner)
Alex (Kernel Developer / Project Owner)
Jorge (Developer / Overall Project )
Adrian (Developer / Overall Project )
&
TEAMExodus Team
XDA:DevDB Information
Exodus Android for Onyx, ROM for the OnePlus X
Contributors
Raja.M, TheCrazyLex, Martin_Ro, primedirective, Raja.M
Source Code: http://github.com/TeamExodus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP, CAF Mixed
Version Information
Status: Nightly
Created 2016-03-11
Last Updated 2016-09-24

Reserved

It gives error 07 installing ROM with twrp 3.0. Where I can find opx latest firmware?

Great, best room ever

Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X

mousse04 said:
Great, best room ever
Click to expand...
Click to collapse
Cris7ianO said:
Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X
Click to expand...
Click to collapse
Great to here enjoy exodus android experience !
Sent from my ONE A2003 using XDA Free mobile app

Can you add Screenshots to OP? And what about a bug list?

It's good to see Exodus on onyx. Thanks! Smooth rom so far, most stable layer rom in my opinion and I like it. haha. Only small issues with the model number being unknown and the user profile picture can't be changed.

Thanks for the ROM, very good work. Daily rom for me for sure.
Some questions, remarks however:
I enabled system ui tuner but can't find the menu ...
Would you plan to add network speed in status bar?
Updater doesn't seem to recognize this onyx version.
Keyboard gesture doesn't seem to work ...

Excellent ROM!! I really liked it, installed it as a daily driver.
One bug though... even though I did a clean flash, Uber app for some reason force closes on me... I'll do a logcat when I arrive home.
Sent from my unknown using Tapatalk

Installed it just now and it's running like a charm so no bugs encountered yet.

@Raja.M In the exopdus updater app, onyx is not included in the list. Thus giving message 'unsupported device found'.

This is the logcat of the Uber app crash, anyone can help me understand this error please? Thanks!
(I've tried cleaning cache, data, uninstalling and re-installing... the app opens, but after I log-in the app crashes before the map to order an uber appears).
03-11 23:10:52.964 30224 30224 E AndroidRuntime: FATAL EXCEPTION: main
03-11 23:10:52.964 30224 30224 E AndroidRuntime: Process: com.ubercab, PID: 30224
03-11 23:10:52.964 30224 30224 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.util.ResolutionOverride.<init>(ResolutionOverride.java:56)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.init(SurfaceView.java:207)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.<init>(SurfaceView.java:187)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.aq.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.ao.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.ag.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.bu.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.r.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.internal.j$a.onTransactcom.google.android.gms.alldynamite:66)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Binder.transact(Binder.java:387)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bcq.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbs.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$2.b(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$1.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.f(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.MapView.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at cry.a(SourceFile:115)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.android.map.MapView.a(SourceFile:153)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.client.feature.receipt.EnhancedReceiptDialogFragment.onViewCreated(SourceFile:415)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1086)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1248)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.BackStackRecord.run(SourceFile:738)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:1613)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl$1.run(SourceFile:517)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5445)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

hey dev...
f*****g awsome rom.i have tried so many on my onyx till date.never have i found a rom which is this bug free at first go.
The only error i found is
"Invalid Number".
Fix that and i guess the rom will look perfect.Thanks a lot!!

Finally !! The wait is over. My favourite ROM has arrived. Thank you Raja for bringing exodus to onyx.?

Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.

laav said:
Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.
Click to expand...
Click to collapse
Do you speak about HW button?

mousse04 said:
Do you speak about HW button?
Click to expand...
Click to collapse
Yes, or do I miss something?

Could you link me to a list of features, guys?
I have searched in google and G+ and haven't found it...
Thanks!!

laav said:
Yes, or do I miss something?
Click to expand...
Click to collapse
Go into setting, hardware, define action or something like this.
Then, you can re define hardware button action

[DEV] CyanogenMod 13

UPDATE: The ROM is now available: http://forum.xda-developers.com/one-mini-2/orig-development/cyanogenmod-13-one-mini-2-t3429360
UPDATE: 30.07.16 1:40Uhr: The camera HAL works now!
UPDATE: 16.07.16 22:02Uhr: Slow SD Card and audio playback fixed!
UPDATE: 16.07.16 21:15Uhr: Data link works now!
UPDATE: 16.07.16 18:30Uhr: Looks good. The modem works now! I could just make the first call. However, I still have problems with the data link.
UPDATE: 11.07.16 18:50Uhr: Good news! CM13 is now booting!
There are still difficulties with the camera, mobile radio, external sdcard and music playback. Pictures can be found here: http://forum.xda-developers.com/showpost.php?p=67699525&postcount=8
UPDATE - 10.07.16 19:05Uhr: Nope, Camera HAL does not work. I fix this later.
UPDATE - 09.07.16 21:04Uhr: Camerawrapper is now working! It was an incorrect kernel HAL configuration. My misstake :laugh:
Unfortunately we still stuck in bootloop...
UPDATE - 09.07.16 20:31Uhr: The CameraWrapper is now starting! However, still with problems:
Code:
07-09 19:33:03.638 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.638 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.658 750 750 I CameraService: Loaded "Memul Camera Wrapper" camera module
07-09 19:33:03.658 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.658 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.658 750 750 V CameraWrapper: camera_get_number_of_cameras
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.659 750 750 I CameraFlashlight: Opening camera 0
07-09 19:33:03.659 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.659 750 750 V CameraWrapper: camera_device_open
07-09 19:33:03.659 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.786 750 750 E CameraWrapper: vendor camera open fail
07-09 19:33:03.786 750 750 E CameraFlashlight: Could not open camera 0: -19
07-09 19:33:03.786 750 750 E CameraFlashlight: connectCameraDevice: initializing camera 0 failed
07-09 19:33:03.786 750 750 I CameraFlashlight: Destroying camera 0
07-09 19:33:03.786 750 750 E CameraFlashlight: findFlashUnits: failed to check if camera 0 has a flash unit. No such device (-19)
07-09 19:33:03.786 750 750 I CameraFlashlight: Opening camera 1
07-09 19:33:03.786 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.786 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.787 750 750 V CameraWrapper: camera_device_open
07-09 19:33:03.787 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.926 750 750 E CameraWrapper: vendor camera open fail
07-09 19:33:03.926 750 750 E CameraFlashlight: Could not open camera 1: -19
07-09 19:33:03.926 750 750 E CameraFlashlight: connectCameraDevice: initializing camera 1 failed
07-09 19:33:03.926 750 750 I CameraFlashlight: Destroying camera 1
07-09 19:33:03.926 750 750 E CameraFlashlight: findFlashUnits: failed to check if camera 1 has a flash unit. No such device (-19)
07-09 19:33:03.926 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.926 750 750 V CameraWrapper: check_vendor_module
07-09 19:33:03.927 750 750 V CameraWrapper: camera_get_camera_info
07-09 19:33:03.927 750 750 V CameraWrapper: check_vendor_module
UPDATE - 09.07.16 15:19Uhr: I got fixed the initialization. Now I put unfortunately steadily for 2 days at the CameraWrapper. We're here still firmly in bootloop. At the moment I have no idea how to fix it :/
UPDATE - 05.07.16 20:38Uhr: The Boringssl-compat wrapper does not resolve the problem but the new Adreno driver for 3xx / 4xx works fine! I come now to the bootanimation. However, the boot process gets stuck.
Hey,
I'm from Germany and my English is unfortunately not the best. Sorry
For several weeks I try to get cm13 on my memul to run.
I want, as long as I get to run CM13, share the finished rom with you.
I managed yesterday to compile the rom.
Unfortunately, I was stuck in a bootloop.
The Adreno driver still makes problems:
Code:
07-05 04:25:48.238 2395 2395 F libc : page record for 0xb6f0d02c was not found (block_size=16)
07-05 04:25:48.251 2399 2399 F libc : page record for 0xb6ee702c was not found (block_size=16)
07-05 04:25:48.254 2398 2398 F libc : page record for 0xb6f3b02c was not found (block_size=16)
07-05 04:25:48.261 2397 2397 F libc : page record for 0xb6ed102c was not found (block_size=16)
07-05 04:25:48.342 2393 2393 I SurfaceFlinger: SurfaceFlinger is starting
07-04 04:25:48.343 2393 2393 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
07-04 04:25:48.346 2393 2393 E libEGL : load_driver(/vendor/lib/egl/libEGL_adreno.so): dlopen failed: cannot locate symbol "RSA_verify_PKCS1_PSS" referenced by "/system/vendor/lib/egl/libEGL_adreno.so"...
07-04 04:25:48.346 2393 2393 F libEGL : couldn't find an OpenGL ES implementation
07-04 04:25:48.346 2393 2393 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2393 (surfaceflinger)
07-04 04:25:48.346 248 248 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-04 04:25:48.346 248 248 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-04 04:25:48.346 248 248 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-04 04:25:48.447 248 248 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-04 04:25:48.447 248 248 F DEBUG : CM Version: '13.0-20160704-UNOFFICIAL-memul'
07-04 04:25:48.447 248 248 F DEBUG : Build fingerprint: 'htc/htc_europe/htc_memul:4.4.2/KOT49H/355312.1:user/release-keys'
07-04 04:25:48.447 248 248 F DEBUG : Revision: '0'
07-04 04:25:48.447 248 248 F DEBUG : ABI: 'arm'
07-04 04:25:48.447 248 248 F DEBUG : pid: 2393, tid: 2393, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
07-04 04:25:48.448 248 248 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
07-04 04:25:48.453 248 248 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
07-04 04:25:48.454 248 248 F DEBUG : r0 00000000 r1 00000959 r2 00000006 r3 b6fc7b8c
07-04 04:25:48.454 248 248 F DEBUG : r4 b6fc7b94 r5 b6fc7b44 r6 00000002 r7 0000010c
07-04 04:25:48.454 248 248 F DEBUG : r8 00000000 r9 ffff51ea sl 00000000 fp beda6a2c
07-04 04:25:48.454 248 248 F DEBUG : ip 00000006 sp beda64b0 lr b6e13c41 pc b6e16030 cpsr 400f0010
07-04 04:25:48.464 248 248 F DEBUG :
07-04 04:25:48.464 248 248 F DEBUG : backtrace:
07-04 04:25:48.464 248 248 F DEBUG : #00 pc 00044030 /system/lib/libc.so (tgkill+12)
07-04 04:25:48.464 248 248 F DEBUG : #01 pc 00041c3d /system/lib/libc.so (pthread_kill+32)
07-04 04:25:48.464 248 248 F DEBUG : #02 pc 0001b837 /system/lib/libc.so (raise+10)
07-04 04:25:48.464 248 248 F DEBUG : #03 pc 000189e9 /system/lib/libc.so (__libc_android_abort+34)
07-04 04:25:48.464 248 248 F DEBUG : #04 pc 000167c4 /system/lib/libc.so (abort+4)
07-04 04:25:48.464 248 248 F DEBUG : #05 pc 00008af7 /system/lib/libcutils.so (__android_log_assert+86)
07-04 04:25:48.464 248 248 F DEBUG : #06 pc 00047b8b /system/lib/libEGL.so
07-04 04:25:48.464 248 248 F DEBUG : #07 pc 00013e5d /system/lib/libEGL.so
07-04 04:25:48.465 248 248 F DEBUG : #08 pc 00014975 /system/lib/libEGL.so (eglGetDisplay+24)
07-04 04:25:48.465 248 248 F DEBUG : #09 pc 0001cdef /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+46)
07-04 04:25:48.465 248 248 F DEBUG : #10 pc 00000ecb /system/bin/surfaceflinger
07-04 04:25:48.465 248 248 F DEBUG : #11 pc 00016671 /system/lib/libc.so (__libc_init+44)
07-04 04:25:48.465 248 248 F DEBUG : #12 pc 00000d90 /system/bin/surfaceflinger
07-04 04:25:48.543 248 248 F DEBUG :
07-04 04:25:48.543 248 248 F DEBUG : Tombstone written to: /data/tombstones/tombstone_05
I will keep you up to date!
This is my first rom here on xda. Should I do something wrong, I am grateful for a hint

Hi And Thank You. Great news. I hope you manage in your project.

nightcore500 said:
UPDATE - 05.07.16 20:38Uhr: The new Adreno driver for 3xx / 4xx works fine! I come now to the bootanimation. However, the boot process gets stuck.
Hey,
I'm from Germany and my English is unfortunately not the best. Sorry
For several weeks I try to get cm13 on my memul to run.
I want, as long as I get to run CM13, share the finished rom with you.
I managed yesterday to compile the rom.
Unfortunately, I was stuck in a bootloop.
The Adreno driver still makes problems:
I will keep you up to date!
This is my first rom here on xda. Should I do something wrong, I am grateful for a hint
Click to expand...
Click to collapse
Welcome! Good to see somebody else porting CM13 for Memul. I tried it myself in the last couple of months, but didn't get it to build the kernel... Great job! Would you mind sharing your source? I really like to know what i did wrong in my device tree adjustments. Did you create the device folder(s) from the scratch? I used Soenisti's source as skeleton - https://github.com/Aronar?tab=repositories

I'm smiling already...

Siluxsept said:
Welcome! Good to see somebody else porting CM13 for Memul. I tried it myself in the last couple of months, but didn't get it to build the kernel... Great job! Would you mind sharing your source? I really like to know what i did wrong in my device tree adjustments. Did you create the device folder(s) from the scratch? I used Soenisti's source as skeleton
Click to expand...
Click to collapse
Yes, I will share the source with you as soon as I get the ROM stable. No, i use dogaozkaraca's configuration for beginning and changed many things. I had the kernel problems also. The kernel config for memul is outdated. Here are some changes needed to compile the kernel.

I have now solved the biggest problems! But we still stuck firmly in bootloop.
The system server is crashing. Looks like a right trouble. If there is no big problem to be fixed that.

I'm stuck here:
Code:
07-10 15:13:27.134 1219 1240 I ServiceManager: Waiting for service sensorservice...
07-10 15:13:27.856 1219 1379 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1379 (system_server)
07-10 15:13:27.857 247 247 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-10 15:13:27.857 247 247 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-10 15:13:27.857 247 247 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-10 15:13:27.958 247 247 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-10 15:13:27.958 247 247 F DEBUG : CM Version: '13.0-20160710-UNOFFICIAL-memul'
07-10 15:13:27.958 247 247 F DEBUG : Build fingerprint: 'htc/htc_europe/htc_memul:4.4.2/KOT49H/355312.1:user/release-keys'
07-10 15:13:27.958 247 247 F DEBUG : Revision: '0'
07-10 15:13:27.958 247 247 F DEBUG : ABI: 'arm'
07-10 15:13:27.958 247 247 F DEBUG : pid: 1219, tid: 1379, name: system_server >>> system_server <<<
07-10 15:13:27.958 247 247 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
07-10 15:13:27.980 247 247 F DEBUG : r0 00000000 r1 00100472 r2 705cf8b8 r3 a09b1610
07-10 15:13:27.980 247 247 F DEBUG : r4 00000000 r5 00000008 r6 b894c570 r7 00000008
07-10 15:13:27.980 247 247 F DEBUG : r8 a09b16b4 r9 a09b1680 sl 00000000 fp b897e978
07-10 15:13:27.981 247 247 F DEBUG : ip b6e6a440 sp a09b1600 lr b6e1112f pc b6e0d2d2 cpsr 600d0030
07-10 15:13:27.989 247 247 F DEBUG :
07-10 15:13:27.989 247 247 F DEBUG : backtrace:
07-10 15:13:27.989 247 247 F DEBUG : #00 pc 000852d2 /system/lib/libandroid_runtime.so
07-10 15:13:27.989 247 247 F DEBUG : #01 pc 0008912b /system/lib/libandroid_runtime.so
07-10 15:13:27.989 247 247 F DEBUG : #02 pc 000199b1 /system/lib/libbinder.so (_ZN7android7BBinder8transactEjRKNS_6ParcelEPS1_j+60)
07-10 15:13:27.989 247 247 F DEBUG : #03 pc 0001b857 /system/lib/libbinder.so
07-10 15:13:27.989 247 247 F DEBUG : #04 pc 000198bb /system/lib/libbinder.so (_ZN7android13AppOpsManager18permissionToOpCodeERKNS_8String16E+26)
07-10 15:13:27.989 247 247 F DEBUG : #05 pc 000472c3 /system/lib/libgui.so (_ZN7android6SensorC1EPK8sensor_ti+882)
07-10 15:13:27.989 247 247 F DEBUG : #06 pc 00008cb7 /system/lib/libsensorservice.so
07-10 15:13:27.989 247 247 F DEBUG : #07 pc 0000ac7d /system/lib/libsensorservice.so
07-10 15:13:27.989 247 247 F DEBUG : #08 pc 0001592f /system/lib/libandroid_servers.so (_ZN7android10sensorInitEPv+82)
07-10 15:13:27.989 247 247 F DEBUG : #09 pc 0004153f /system/lib/libc.so (_ZL15__pthread_startPv+30)
07-10 15:13:27.989 247 247 F DEBUG : #10 pc 0001906b /system/lib/libc.so (__start_thread+6)
Looks like the sensorservice don't work. Maybe someone has an idea?

Good news! CM13 is now booting!
There are still difficulties with the camera, mobile radio, external sdcard and music playback.
{
"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"
}

Congrats man for your efforts, Im spreading the word, hopefully someone will show up who might be able to help..

Hey this looks very cool!
There is hope for our memul!

Finally someone with will and skills.
I hope you don't give up....
It's a nice phone but dev support sucks at whistle

Looks good. The modem works now! I could just make the first call. However, I still have problems with the data link.
Update: We have an internet connection!

I'm smiling more now...Keep it coming, keep up the good work...
Thanks man...I'm quite hopeful...

I have just fixed the camera problems. I think we are now ready for the first CM13 build. I now begin the last recompile and will publish the finished rom after a short test tomorrow here in the forum. I look forward to tester.

nightcore500 said:
I have just fixed the camera problems. I think we are now ready for the first CM13 build. I now begin the last recompile and will publish the finished rom after a short test tomorrow here in the forum. I look forward to tester.
Click to expand...
Click to collapse
I'm game for testing. But I do have one question. If you have used any CM12.1 build, how does the camera perform compared to it? One of the reasons I have stuck to the stock ROM is that the camera froze a lot.

I use the camera proprietary files from the a5 device. The hardware of the devices is almost the same

The ROM is now available: http://forum.xda-developers.com/one-mini-2/orig-development/cyanogenmod-13-one-mini-2-t3429360

I've got the following problems:
-There are stutters sometimes ~After reflashing, the stutters disappeared
-Using headphones via AUX, there is a crackle on the right side; with stockrom it worked just fine
Anyway, it's a great ROM

error274 said:
I've got the following problems:
-Sometimes there is a stutter for about an half second
-Using headphones via AUX, there is a crackle on the right side; with stockrom it worked just fine
Anyway, it's a great ROM
Click to expand...
Click to collapse
Sounds like there is some dirt in the headphones port.
Try to blow in the hole or use some other tools to clean it.
But be carefull.
Have not such issues with this rom.

Okay, I will try

[Help]Op3T reboot several times when charging after installing Xposed v88 sdk25

After installing Xposed v.88 SDK 25 for Nougat, my Oneplus 3T reboot several time when charging. Here are the logs:
Logcat:
10-12 05:27:04.745 1498 1513 V OPConfig:ConfigProvider: Module:BackgroundOptConfig
10-12 05:27:04.748 1112 16498 D BackgroundDexOptService: blacklist add : com.chinamworld.main
10-12 05:27:04.749 1112 16498 D BackgroundDexOptService: blacklist add : cn.kidyn.qdmedical160
10-12 05:27:04.749 1112 16498 D BackgroundDexOptService: blacklist add : com.paic.zhifu.wallet.activity
10-12 05:27:04.749 1112 16498 D BackgroundDexOptService: blacklist add : com.pingan.paces.ccms
10-12 05:27:04.749 1112 16498 D BackgroundDexOptService: blacklist add : cn.damai
10-12 05:27:04.749 1112 16498 D BackgroundDexOptService: [OnlineConfig] BackgroundOpt updated complete
10-12 05:27:04.753 1112 16498 E art : No implementation found for java.lang.String dalvik.system.DexFile.getOatFileCompilerFilter(java.lang.String, java.lang.String) (tried Java_dalvik_system_DexFile_getOatFileCompilerFilter and Java_dalvik_system_DexFile_getOatFileCompilerFilter__Ljava_lang_String_2Ljava_lang_String_2)
10-12 05:27:04.754 1112 16498 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: BackgroundDexOptService_IdleOptimization
10-12 05:27:04.754 1112 16498 E AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String dalvik.system.DexFile.getOatFileCompilerFilter(java.lang.String, java.lang.String) (tried Java_dalvik_system_DexFile_getOatFileCompilerFilter and Java_dalvik_system_DexFile_getOatFileCompilerFilter__Ljava_lang_String_2Ljava_lang_String_2)
10-12 05:27:04.754 1112 16498 E AndroidRuntime: at dalvik.system.DexFile.getOatFileCompilerFilter(Native Method)
10-12 05:27:04.754 1112 16498 E AndroidRuntime: at com.android.server.pm.PackageDexOptimizer.getOatFileCompilerFilter(PackageDexOptimizer.java:167)
10-12 05:27:04.754 1112 16498 E AndroidRuntime: at com.android.server.pm.PackageManagerService.getOatFileCompilerFilter(PackageManagerService.java:19895)
10-12 05:27:04.754 1112 16498 E AndroidRuntime: at com.android.server.pm.BackgroundDexOptService$3.run(BackgroundDexOptService.java:373)
10-12 05:27:04.755 1112 16498 V MDM_DropBox: record:system_server_crash
10-12 05:27:04.760 1112 16498 W oemManager: Try to OEMExService Instance! times = 3
10-12 05:27:04.760 1112 1465 D OSTracker: OS Event: system_server_crash
10-12 05:27:04.762 1112 16498 E OemExService: jint android::android_server_OemExService_getPhoneHistoryRecord(JNIEnv *, jobject, jint) type: 1, val: 41
10-12 05:27:04.763 1112 16498 E OemExService: int android::android_server_OemExService_setPhoneHistoryRecord(JNIEnv *, jobject, jint, jint) type: 1, val: 42
10-12 05:27:04.763 1112 16498 D DropBoxManagerService: incrementPhonehistoryRecord TYPE_ABNORMAL_REBOOT ret : 0
10-12 05:27:04.764 2358 2680 D OPReportService: addMonitorFolder onEvent [email protected]_27_04_763.txt, event:128
10-12 05:27:04.766 2358 16500 V LogWarehouse: Create Warehouse
10-12 05:27:04.783 1112 1176 I ActivityManager: Start proc 16501:net.oneplus.odm.provider/u0a22 for content provider net.oneplus.odm.provider/.PayloadProvider
10-12 05:27:04.789 2358 16500 V BugReportLogBuilder: date:1709212050
10-12 05:27:04.790 2358 16500 D BugReportLogBuilder: Properties.txt
10-12 05:27:04.793 2358 16500 V BugReportLogBuilder: date:1709212050
10-12 05:27:04.793 2358 16500 D BugReportLogBuilder: Meminfo.txt
10-12 05:27:04.808 2358 16500 D BugReportLogBuilder: CPUinfo.txt
10-12 05:27:04.818 2358 16500 D BugReportLogBuilder: Properties.txt
10-12 05:27:04.824 16501 16501 W System : ClassLoader referenced unknown path: /system/priv-app/OPDeviceManagerProvider/lib/arm64
10-12 05:27:04.855 1112 16498 D DropBoxManagerService: file :: /data/system/dropbox/[email protected]_27_04_763.txt
10-12 05:27:04.864 2358 16500 D BugReportLogBuilder: KernelLog.txt
Click to expand...
Click to collapse
Could anyone help me to analyze these logs to find outs what had happened with my phone ?
Thanks very much !!!

https://forum.xda-developers.com/showthread.php?t=3687603