[EOL][OP3][ROM+KERNEL] Unofficial CyanogenMod 13.0 with custom kernel [Apr 30, 2017]

Skippyjan

Member
Aug 31, 2010
26
15
0
I am wondering whether XPrivacy is working ok or not on the Sultan Nougat version with XPosed. Has anyone here already tried?
Xprivacy doesn't work or is at least not reliable on nougat. You can just build your own lineageOS 13 including the manifest from the start post so that you have the custom kernel and the modifications. I successfully generated a rom with the security patch of November.

I really like this great rom :)
 
  • Like
Reactions: lammpat

itrystuff

Member
Jul 27, 2016
10
2
0
Would be great if this ROM would receive one final update to fix the terrible KRACK vulnerability. So we could continue to use it if we want to. But with unpatched KRACK it's very unsafe.
 
  • Like
Reactions: lammpat

lammpat

Senior Member
Apr 9, 2013
562
266
0
Would be great if this ROM would receive one final update to fix the terrible KRACK vulnerability. So we could continue to use it if we want to. But with unpatched KRACK it's very unsafe.
+1 I will too come back to this if it get final version with latest security fixes. @Sultanxda please spare some time bro, and release a finale version. ?
 

ryanmw

New member
Apr 11, 2018
1
0
0
NEOS OnePlus 3 image in AVD emulator

Hello,

I apologize if this is the wrong place for this question, I haven't posted in XDA before and I'm not very knowledgeable about android development.

Has anyone successfully loaded the CM13 image for the OnePlus 3 in the Android SDK provided emulator?

I work with a team that's porting the Comma NEO and OpenDrive platform to a Kia Soul. The NEO is an open source device based on the OnePlus 3, it provides an interface for CAN messages to the usb port on the phone and OpenDrive uses the camera from the phone to make decisions about control of steering, acceleration etc...

I'm trying to emulate the provided system.img as an AVD in the Android SDK. It looks like the image provided by comma is for CM 13 so I thought maybe someone in this thread would be able to help.

The primary reason for exploring emulation is that we currently only have one device built so it becomes a bottleneck if we want to do development across the team.

Initially I tried creating an AVD with the following settings:

kernel.path = ~/Android/Sdk/system-images/android-23/default/x86//kernel-ranchu
disk.ramdisk.path = ~/Android/Sdk/system-images/android-23/default/x86//ramdisk.img
disk.systemPartition.initPath = ~/.android/avd/NEO_Test_Device.avd/system.img

Currently when the emulator starts is will remain in a black screen, even after a couple hours it will not boot. When closing the emulator it says the device had not finished booting. Additionally there's an error when trying to use adb shell that /system/bin/sh wasn't found even though the device is listed. When I mount the system.img in linux there is a bin folder with sh so my best guess is that the ramdisk/kernel I'm using is not compatible.

Has anyone used this particular CM13 image for the OnePlus 3 with the Android SDK emulator and what ramdisk.img / kernel worked? Comma provides a boot.img and I've seen discussions about repackaging that into a separate kernel and ramdisk for emulation. I appreciate any recommendations on best path or resources I should be looking at.

NEOS OS Image (NEOS v3 zip download page):
https-github-com-commaai-neo-releases-tag-swag

Cat /etc/CHANGELOG-CM.txt

CyanogenMod
===============

Visit http-github-com-CyanogenMod for full source and git access.

Visit http-review-cyanogenmod-org for our Gerrit instance.

CHANGELOG (notable new features)
---------

### 13.0 ZNH5Y
* Common: Android 6.0.1 (Google)
* Android Security Bulletin - August 1st update
 

Jdhal21

New member
Apr 17, 2018
2
0
0
My one plus works fine, but after a phone call I lose touch function until u restart, what can fix this problem. I got a new screen installed from a shop and ever since that its been acting up.