Develop Bugs

[ROM][CM10] CyanogenMod+

PLEASE HELP VOTING FOR THE FEATURES I COMMIT!
Current CyanogenMod has some bugs and limitations which I try to resolve. Some solutions were found by others. Some solutions I found.
I also try to put more features into CyanogenMod's kernel. So there is no need going for another one.
You want to see a new feature in CyanogenMod?
If you want to see a new feature in CyanogenMod please let me know. I only handle new kernel features at the moment. If you want to see new governors or new IO schedulers for example let me know and I will push them into the official repositories.
Approved commits
- Change Ic8722ac5: Added scripts to extract proprietary files to comply with the CM9 tutorial
- Change I7fc7c517: Fixed overclocking Power HAL module
- Change Ia93c111a: DPLL_CORE_M6_OPP100_RATE should be 266666666 (Ezekeel)
My patches for CM10
Here are my contributions listed. My changes will eventually arrive in every CyanogenMod based ROM. If they are denied to the official CyanogenMod kernel I might still include them here in my ROM. Note that I might discard the denied features at any time.
If you like my work feel free to buy me a beer. (Belgium has so many beers I'd like to try)
http://review.cyanogenmod.com/#/dashboard/4343
ROM Features
+ Custom Voltage v3 (Ezekeel)
+ I/O Schedulers added/modified:
----- BFQ v4
----- Deadline: fifo_batch 1
----- SIO v0.2
Downloads (CyanogenMod with pending or unapproved commits)
Cyanogenmod 10 Build 20120912
Cyanogenmod 10 Build 20120913 (NEW: change GPU OC from Settings application)
Cyanogenmod 10 Build 20120918
- MPU Undervolted (if you get a random reboot let me know and i will up all voltaged by 25mv until it's stable for everone.) Undervolted from 750mv (350mhz) to 1175mhz (1350mhz)
- Custom voltage from ezekeel.
- Disable MPU Smartreflex to use my custom voltages
- Make sure you have a rom backed up in case the mpu voltages are too low for you
Google Nexus Device Maintainers
- Robert Burns
- Kalimochoaz (Rafael Salas)
Documentation
- http://www.kernel.org/doc/Documentation/
Please vote and review my commits so they can be included faster in CyanogenMod, also motivate in your review why you would like to see it in the official CyanogenMod kernel

Updated thread. Please make a account at the link and vote +1 on every patch I have made. So we have these bugs fixed faster

add Rafael Salas (the cm galaxy nexus mantainer) and Steve Kondik (cyanogen) as reviewer, they will check, approve and merge ur patch..otherwise no one will care about ur patch..no need other people to signup
about the kernel upstream update, im not sure thats the way the cm team usually do it

Thank you. I added them as a reviewer.
Have you actually built the CM10 source? I am really confused on how to build it. I start screaming at the part with the proprietary files because there is no extract-files.sh
I have put the binaries in the correct folders like I did with AOSP ROMs but I get a boot loop at the bootlogo.

in the past i built cm9 using cm wiki here
I guess it should be something similar for cm10 (apart from the branch to be jellybean of course)
i don't know to much details anyway

andQlimax said:
in the past i built cm9 using cm wiki here
I guess it should be something similar for cm10 (apart from the branch to be jellybean of course)
i don't know to much details anyway
Click to expand...
Click to collapse
I used that one as a reference too, but this section is not applicable to cm10:
Copy Proprietary Files
So I was hoping for a workaround like this:
http://rootzwiki.com/topic/32731-how-to-get-the-proprietary-files-for-cm10-galaxy-nexus/
But I think there are erros in the guide
local_manifest.xml should be:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_maguro" path="device/samsung/maguro" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="jb" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="jellybean" />
</manifest>
Click to expand...
Click to collapse
then a repo sync and you will have everything. but it doesn'T seem to be working.
Then again I took the latest proprietary files from google as well

djjonastybe said:
Thank you. I added them as a reviewer.
Have you actually built the CM10 source? I am really confused on how to build it. I start screaming at the part with the proprietary files because there is no extract-files.sh
I have put the binaries in the correct folders like I did with AOSP ROMs but I get a boot loop at the bootlogo.
Click to expand...
Click to collapse
me too...same problem mate..try with THIS,is made by a guy (not found nick).It's for gsm maguro,if anyone want to use that on others gnex variants,some modifyes are needed.
after searching a lot,it seems that the extract-files it isn't available for cm10 yet and it doesn't sync with repo.place that in coreect folder and run it like every official scipts.
This,is the problems that i have from a month..tried without that,but build compile but don't works (same problems,no boot animation,and stuck at it.phone seems powered off)

there wont be a extract-files.sh in CM10 because it was changed to generate-packages.sh I believe.

generate-packages.sh looks like it.
I will try extract-files.sh as well. Together with:
https://github.com/CyanogenMod/android_device_samsung_maguro/blob/ics/setup-makefiles.sh
We need the stock OTA package and place it in the same dir as generate-packages.sh I think
We need this zip: yakju-ota-398337.zip
Googled it but no dice
btw: the 3.0.39-3.0.41 patches have been rejected already. Still no response for the real hotfixes yet

do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app

llohcyoing said:
do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did that. But I will end up with a boot loop anyway.
It's so depressing.
mbh87 you did realise you may have been missing setup-makefiles.sh ? You can copy that script from ics as well.
I am now compiling again.

Seen the reviews of your patches, I told you those changes to the PowerHAL would be problematic, PowerManager service ****s itself.

I built CM10 successfully with extract-files.sh he gave me. then I added another file and I have it.

franciscofranco said:
Seen the reviews of your patches, I told you those changes to the PowerHAL would be problematic, PowerManager service ****s itself.
Click to expand...
Click to collapse
I just noticed. I will try a different way. Thanks for telling me.
I removed the commit and changed it. This should work.
I also pushed extract-files.sh and setup-makefiles.sh for reviewing

flashed your cm10 0828, cpu settings set on but with your/cm10 kernel and trinity kernel (without their app). thx, nice work!

djjonastybe said:
I built CM10 successfully with extract-files.sh he gave me. then I added another file and I have it.
Click to expand...
Click to collapse
do you used mine extract-files.sh linked above?
QUOTE=llohcyoing;30811974]do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app[/QUOTE]
OP referred to "copying propriretary files" from phone...instead you refer to "copying proprietary drivers",both needed,but 2 distincts operations.me too did the drivers parts..but not the files part..

sert00 said:
do you used mine extract-files.sh linked above?
QUOTE=llohcyoing;30811974]do you have d/l and extracted proprietary files?
https://developers.google.com/android/nexus/drivers#magurojro03h
extract in android/system and execute the file...at the bottom of license write : i accept (or some that license requires )
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
OP referred to "copying propriretary files" from phone...instead you refer to "copying proprietary drivers",both needed,but 2 distincts operations.me too did the drivers parts..but not the files part..[/QUOTE]
Do a repo sync. extract-files.sh is now excluded along with another file required to build CM10:
http://review.cyanogenmod.com/#/c/22331/
This should now work for everyone ! No need to do additional work that is not mentioned in the tutorial. Just execute the commands and you will be alright.
http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_9_(Linux)

The feautures i'd like to have:
- no conversion sms in mms after 3
- battery percent (text only)
- navbar mods
- call icon in contacts that works
- back button pressed to eliminate background apps
Some of those are included in JellyBro. If anyone can do that i would be to the 7th sky
Inviato dal mio Galaxy Nexus con Tapatalk 2

HTCDevil said:
...
- back button pressed to eliminate background apps
...
Click to expand...
Click to collapse
back button kill should be already there, its under settings->developer options

andQlimax said:
back button kill should be already there, its under settings->developer options
Click to expand...
Click to collapse
I know...but never works in my case.
Inviato dal mio Galaxy Nexus con Tapatalk 2

[ROM] PARANOIDANDROID [2.54] CM10 Unofficial 11-14

I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest.
Sorry about the long wait but, until recently there were a lot of issues regarding the ParanoidPrefs App, they are now fixed.
If your new, follow this link to see a quick tutorial on how to use Paranoid Preferences.
http://forum.xda-developers.com/showpost.php?p=31610815&postcount=2
Install Instructions
Full wipe
Flash zip --->
Both MDPI and Large MDPI are now hosted on Google code
https://code.google.com/p/paranoidandroid-kfire/downloads/list
Flash GApps for 4.1.2 ----> http://goo.im/gapps
First Boot may take a while, may also restart once before loading the UI.
Expect the same bugs as in Hashcodes CM10
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode the Paranoid Android team and rohan32 for his Paranoid preferences guide.

Changelog
Code:
[B][U]PA Otter 08[/U][/B]
PA 2.54 Changes
* Fixed after breaking Phablet Mode Navigation Bar
* CM Bugfixes and updates
Full Changes can be seen in the ParanoidAndroid Github http://github.com/ParanoidAndroid
Device Changes:
Includes hashcodes latest kernel updates.
[B][U]PA Otter 03[/U][/B]
10/7
re-uploaded with calculator FC fixed
[U]Paranoid Android 2.17 Changes[/U]
New toggles style. They're unified now to all possible UIs
Navigation bar transparency (i9100)
Double token encryption for security
Double ime button fixed (aosp bug)
Gmail crashes fixed (app bug)
Google now hold-off delay fixed after sysUI restart (aosp bug)
Double notification ticket avatar fixed (aosp bug)
Memory leak fixed by CM! (i9100). Use only stock kernel for now, most of custom kernels won't boot at all untill changes made to fit new blobs / mali code.
[B][U]pa otter 02[/U][/B]
[U]Paranoid Changes[/U]
Button panel fixes, also in landscape
Transparent statusbar (navbar comes soon)
4.1.1_r6 from aosp
Lag fix for Nexus devices
Nexus 7 new hybrid properties
Backup/restore is 100% fixed
SuperSU instead of SuperUser
new ParanoidWallpapers app including solid color selection
Moar stuff!
[U]Device Changes[/U]
Charging is now fixed. Including basic OTG support.
Backlight / Panel driver updated. This was probably causing some of the battery drain.
Current CM10 and Kernel info can be found here.
http://forum.xda-developers.com/showpost.php?p=24665559&postcount=1
//These changelogs are from the respective posts from the Paranoid Android Team, and Hashcode

Waited for PA for the fire
Will test asap and report back.
Sent from my GT-I9300 using xda app-developers app

Reserved
Sent from my PC36100 using xda premium

I've been really excited about this one. Can't wait to see how it turns out.

johnwayne007 said:
I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest. So far it seems to work decently on the Fire although it is scaled kinda small more for a 10" tablet. If I can figure out how to change that and people are interested i'll keep posting these.
Install Instructions
Full wipe
Flash zip ---> http://www.mediafire.com/?6i49oip6klii5q0 MD5: C4D46F46C9F92CA374FAB2852F6F0309
Flash GApps ----> http://goo.im/gapps
First Boot may take a while
Expect the same bugs as in Hashcodes CM10
I have also noticed that when you make a change in the Paranoid Preferences app and it reboots, it reboots into recovery. I'll see if i can figure out why.
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode and the Paranoid Android team!
Click to expand...
Click to collapse
Thanks for your Rom!
Paranoid Android's Rom in Nexus 7 is Perfect!
Hope this perfect for Kindle Fire.

Thanks for this! I actually like the small bars, it makes the screen look bigger, but I loathe the extended notification.
Update: Somehow, I got it to normal.

wow, great news! I'll try this soon! ty

Is this with the latest kernel release.
Sent from my Amazon Kindle Fire using XDA Premium HD app

What's the score on antutu?

Solid-Dado said:
What's the score on antutu?
Click to expand...
Click to collapse
It is 6630.
Sent from my Amazon Kindle Fire using XDA Premium HD app

I synced the repos just before building so as far as i know it's current with with Hashcodes latest kernel source.
Sent from my HTC One XL using xda premium

johnwayne007 said:
I compiled this from source that was just recently released by the ParanoidAndroid Team, and with Hashcodes local manifest. So far it seems to work decently on the Fire although it is scaled kinda small more for a 10" tablet. If I can figure out how to change that and people are interested i'll keep posting these.
If your new, you can change the app size in paranoid preferences, in the apps part. Find the app in the list and change the size for the app there, its the first option. Screenshots in second post.
Install Instructions
Full wipe
Flash zip ---> http://www.mediafire.com/?6i49oip6klii5q0 MD5: C4D46F46C9F92CA374FAB2852F6F0309
Flash GApps ----> http://goo.im/gapps
First Boot may take a while
Expect the same bugs as in Hashcodes CM10
I have also noticed that when you make a change in the Paranoid Preferences app and it reboots, it reboots into recovery. I'll see if i can figure out why.
Also, i'm not responsible for anything that may happen to your device by flashing this rom.
Thanks to Hashcode and the Paranoid Android team!
Click to expand...
Click to collapse
Paranoid Android team told me the 2.12 isn't stable, but 2.13 is stable.
When i test the 2.12 Rom you provided, the Rom is surely not stable.
The font size is too small in the Setting. I can't run Antutu benchmark to test, can't run Goomanager to get update unless i reboot my KF.
Can change the sources to 2.13?
Thanks!
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Solid-Dado said:
What's the score on antutu?
Click to expand...
Click to collapse
I test it, the score is 6620.

Agreed, I'll resync and rebuild. But you may also want to change the size of the app where the font is too small, I did that in my settings in order to make it easier to read/use. Instructions to do so are in first post with Screenshots in the bottom of the second post.
Sent from my HTC One XL using xda premium

johnwayne007 said:
Agreed, I'll resync and rebuild. But you may also want to change the size of the app where the font is too small, I did that in my settings in order to make it easier to read/use. Instructions to do so are in first post with Screenshots in the bottom of the second post.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />

ive been waiting on this for a while. i attempted to port it a while back but i had absolutely no time and of course, no experience either. so thanks man! and our you please update it to the stable version on 2.13 this one is not as stable and has bugs

twa_priv said:
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />
Click to expand...
Click to collapse
Cool thanks for that, when I sync tonight I'll make sure to update the manifest.
Sent from my Amazon Kindle Fire using XDA Premium HD app

johnwayne007 said:
Cool thanks for that, when I sync tonight I'll make sure to update the manifest.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Click to expand...
Click to collapse
Looks awesome. I will have to give it a good try this weekend after exams. I had PA on my galaxy nexus and loved it. Will be awesome to mess with the DPI for some apps that could display a little better on the fire.

Very interesting. Sub'n to this thread. Pa on the fire actually makes sense.

twa_priv said:
If you want to have hashcode's latest kernel (charging fix) included in your build you will need to use the dev branches of his kernel and device repos:
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" revision="jb-dev" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" revision="p-android-omap-3.0" />
Click to expand...
Click to collapse
So, i changed that in my local manifest synced and built, now i get a bootloop and ADB wont recognize the device to get a logcat. Any suggestions?
http://pastebin.com/VYGMHV6Q
http://pastebin.com/YCYAk8sJ

[ROM][5.1.1][K920][kingdom_row]CyanogenMod 12.1 for Lenovo Vibe Z2 Pro ROW

Unofficial build of CyanogenMod 12.1 for international Lenovo Vibe Z2 Pro
DOWNLOAD
Google+ community
known bugs:
- HDR in Camera app not working
- flip cover not supported yet
- i had to "Format DATA" in recovery to be able to install this. it will delete everything from your phone so make a backup first if it's needed
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="cyanogenmod-cm-12.1" />
<project name="frantisheq/android_device_lenovo_common" path="device/lenovo/common" remote="github" revision="cyanogenmod-cm-12.1" />
<project name="frantisheq/android_kernel_lenovo_msm8974" path="kernel/lenovo/msm8974" remote="github" revision="cm-12.1" />
<project name="frantisheq/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-12.1" />
</manifest>
Click to expand...
Click to collapse

frantisheq said:
I am porting CyanogenMod to Lenovo Vibe Z2 Pro, wish me luck links to device tree on github are under the video on youtube.
https://www.youtube.com/watch?v=WWehoPOdpl0
Click to expand...
Click to collapse
Thanks bro porting for this device...
Im glad to here it...
Please share rom download...
Lets us try it...
:good:

Cant wait!

Go baby Go!. I don't own this device, but am keenly interested in how this goes. Seems like a very nice handset.

preview build with sim detected. you an make call but there is still no sound, no wifi, no mobile internet
https://copy.com/VaSU9CZfwfwnsLpz
EDIT: got wifi working

Please tell me your vibe z2 pro is european model or chinese version ? Will work on chinise phones because of hardware modification ?
Sorry, now I see is ROW version.

My prayers have been answered! Had to revert to KitKat because Lenovo can't even support the phone properly without bugs in their Lollipop build. I'm sure once you have a stable build like the dev that ported Lollipop for the K910, you will get a lot of support and donations!
frantisheq said:
preview build with sim detected. you an make call but there is still no sound, no wifi, no mobile internet
https://copy.com/VaSU9CZfwfwnsLpz
EDIT: got wifi working
Click to expand...
Click to collapse

n1tro said:
My prayers have been answered! Had to revert to KitKat because Lenovo can't even support the phone properly without bugs in their Lollipop build. I'm sure once you have a stable build like the dev that ported Lollipop for the K910, you will get a lot of support and donations!
Click to expand...
Click to collapse
kitkat best for this lenovo z2 pro...
i hope so that someone can make custom rom on kitkat...especially MIUI / aosp...

frantisheq said:
I am porting CyanogenMod to Lenovo Vibe Z2 Pro, wish me luck links to device tree on github are under the video on youtube.
https://www.youtube.com/watch?v=WWehoPOdpl0
Click to expand...
Click to collapse
what is the status now? is there any bugs in this rom? Thanks for rom

nothing new regarding functionality, i'm working on it. i have built cyanogenmod 12.1 for our device which is based on android 5.1.1 and i could get past the initial setting, everything worked as in CM12 but it crashed after few seconds so what do you think? should i work on CM12 or should i stabilize CM12.1?
i will post my local_manifest.xml later if somebody wants to build this rom and help me maybe

frantisheq said:
nothing new regarding functionality, i'm working on it. i have built cyanogenmod 12.1 for our device which is based on android 5.1.1 and i could get past the initial setting, everything worked as in CM12 but it crashed after few seconds so what do you think? should i work on CM12 or should i stabilize CM12.1?
i will post my local_manifest.xml later if somebody wants to build this rom and help me maybe
Click to expand...
Click to collapse
I thinks if it possible miui v6 is perfect rom for vibe z2 pro. But if it isn't possible you should choose which most stable rom CM12 or CM12.1.

i successfully stabilized CM12.1 so i will continue to work on it. we have android 5.1.1 i will post link to new build after i'll get wifi working automatically. it works but you have to load kernel module through adb
EDIT: local_manifest.xml added to OP

Glad to hear this news! I wish you the best luck and will be happy to send you a little donation when there is a version easy to install for me
Cheers!

Great job so far :good:
You should try to fix audio now.
I've been trying to build kernel by using stock official lenovo sources, but I couldn't manage to get the internal speaker working.
Maybe because of bad sources or because I'm stupid and I did something wrong.
Anyway, wish you best luck

kernel sources are ok because i have recompiled it and everything just worked with stock rom. for now the biggest headache for me is the init system. it looks like not all init rc scripts are executed, i'm not sure though. i'm missing something and i have no idea what, at least wlan.ko should be loaded at boot bu it isn't

CM 12.1 - still no sound
Download - https://copy.com/fdEvM0OizfT6ZSTZ
to get wifi working:
- enable Developer options
- in Developer options:
- enable Advanced reboot
- enable Root access for Apps and ADB
- enable Android debugging​ - run adb shell on your computer or Terminal on your phone:
- execute "su" command
- execute "insmod /system/lib/modules/wlan.ko"​ - hold Power button on your phone and slect Soft reboot
- activate Wi-Fi in Settings
i've had more stable build but it's a mess here and somehow i crippled it again it's usable though

both SIMs working? how about LTE?

both sims should work but there is no LTE, no 3G, no 2G. you can make a call but it's useless without sound

that's good. we waiting full stable version. I hope you will create it.

frantisheq said:
both sims should work but there is no LTE, no 3G, no 2G. you can make a call but it's useless without sound
Click to expand...
Click to collapse
Frantisheq, have you checked with team Superluminal? They ported over Cyanogenmod for the K910 and I'm sure they have encountered similar problems as you in the beginning.

[ROM][6.0.1][K920][kingdom_row]Mahdi ROM for Lenovo Vibe Z2 Pro ROW

Unofficial build of ROM made by Altaf Mahdi creator of Euphoria OS
DOWNLOAD
ROM - https://github.com/Altaf-Mahdi/android_manifest
known bugs:
- FM radio not working
- restart doesn't work
- echo - try to install latest stock ROM then install this ROM
...
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="cyanogenmod-cm-13.0" />
<project name="frantisheq/android_kernel_lenovo_msm8974" path="kernel/lenovo/msm8974" remote="github" revision="cm-13.0" />
<project name="frantisheq/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="cm-13.0-test" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
</manifest>
Click to expand...
Click to collapse

What the different from cyanogenmod?

Not really sure but Euphoria was always my favorite. It's something between CM and AICP and maybe it's just placebo because of faster animations but it looks more responsive to me then CM. Also it has more options in Settings.
Today I'll try to build a monolithic kernel and rework init system to make WiFi finally work.

frantisheq said:
Not really sure but Euphoria was always my favorite. It's something between CM and AICP and maybe it's just placebo because of faster animations but it looks more responsive to me then CM. Also it has more options in Settings.
Today I'll try to build a monolithic kernel and rework init system to make WiFi finally work.
Click to expand...
Click to collapse
I am now on Kingdom ROW Cynogen of yours. Is it OK if I flash this Euphoria ROM with TWRP without wiping the user data?

frantisheq said:
Not really sure but Euphoria was always my favorite. It's something between CM and AICP and maybe it's just placebo because of faster animations but it looks more responsive to me then CM. Also it has more options in Settings.
Today I'll try to build a monolithic kernel and rework init system to make WiFi finally work.
Click to expand...
Click to collapse
Okey bro good working to you I am waiting agog

I get stuck on the boot animation :/
TWRP 2.8.7.7 [K920_CN]

this is for ROW, not tested on CN
Sent from my Lenovo K920 using Tapatalk

new build up https://copy.com/uoKKBK8SyBW6GSIN

new build. should be on par with CM https://www.androidfilehost.com/?fid=24369303960685488

frantisheq said:
new build. should be on par with CM https://www.androidfilehost.com/?fid=24369303960685488
Click to expand...
Click to collapse
Thank frantisheq for your work!
I installed the latest build and noticed that now Reboot and Power off perform the same action - Power off. It does not depend if I select what action shall perform pressing the Power button or do the same from an application.

I can not record a call. When I press a button to record a call from Dialer I get the notification "Failed to star call recording". Any adviсes what is wrong - ROM, permissions of the PhoneRecorder directory or something else?

forget euphoria, Altaf is working on new rom. still uploading so wait

Installed the rom! Am witnessing a decrease in internet speed. The speedtest is fine, the internet works fine with the other phone connected through my hotspot, but its damn slow in mine

frantisheq said:
new build. should be on par with CM https://www.androidfilehost.com/?fid=24369303960685488
Click to expand...
Click to collapse
Ji,
Its wrong build in download is euphoria 1.1 on android 5.1.1

new build https://basketbuild.com/filedl/devs...ahdi/cm-13.0-20160330-NIGHTLY-kingdom_row.zip

Under Construction

I noticed official support for manta (Nexus 10) was dropped recently, and actually, all LOS13 builds are no longer supported officially which is shocking but I guess server space is tight. Seeing as a large portion of users still rock MM simply for the camera support, I decided to start working on Unofficial Builds. I also plan to use these as a new base for my Sailfish OS builds since LOS14.1 is proving to be an annoying base to work with especially with the audio issues it is having in SFOS.
Google Drive: LINK REMOVED
Gapps (courtesy of OpenGapps.org): https://opengapps.org/
I am rebuilding tonight, I am getting memory allocation errors, I increased the ram on my VC and will be configuring JACK too. *sigh* thanks to followmsi for the sources, I am very confident in things right now! Hopefully I'll have something to put here within 24 hours, until then, stay tuned!

Tx! Keep up the good work and this LOS ROM please ...

biontx said:
Tx! Keep up the good work and this LOS ROM please ...
Click to expand...
Click to collapse
completely redoing my environment on my PC, should crank something new tonight, for sure this weekend. I think I just accidently used the CM14.1 device repos with the actual CM13 rom repos. I goofed it : ( But it's an easy fix. no big deal.

We r following bro keep it doing thanx

murteci said:
We r following bro keep it doing thanx
Click to expand...
Click to collapse
I'm still trying to figure out why none of the old sources work, it doesn't make any sense...

Galaxyninja66 said:
I'm still trying to figure out why none of the old sources work, it doesn't make any sense...
Click to expand...
Click to collapse
Maybe followmsi "https://forum.xda-developers.com/ne...age-14-1-20170216-unofficial-t3557735/page86" knows more about

joh9 said:
Maybe followmsi "https://forum.xda-developers.com/ne...age-14-1-20170216-unofficial-t3557735/page86" knows more about
Click to expand...
Click to collapse
Honestly I might just try and rebuild using the 14.1 kernel or an old 13 boot image instead of making my own kernel

Galaxyninja66 said:
Honestly I might just try and rebuild using the 14.1 kernel or an old 13 boot image instead of making my own kernel
Click to expand...
Click to collapse
I just answered your private mail too .. there are no problems with lineage cm-13.0 sources.
You may did forget the vendor blobs for cm-13.0 branch ?
A few days ago I have made a fresh cm-13 build for testing some stuff ..
Based on stock lineage cm-13.0 sources and cherry-picked security updates for May 2018 -> no problems at all.
lineage-13.0-20180527-UNOFFICIAL-manta.zip
Good luck !

followmsi said:
I just answered your private mail too .. there are no problems with lineage cm-13.0 sources.
You may did forget the vendor blobs for cm-13.0 branch ?
A few days ago I have made a fresh cm-13 build for testing some stuff ..
Based on stock lineage cm-13.0 sources and cherry-picked security updates for May 2018 -> no problems at all.
lineage-13.0-20180527-UNOFFICIAL-manta.zip
Good luck !
Click to expand...
Click to collapse
Ha ha you stole my thunder linking that build there FollowMsi but I am incredibly thankful for your willingness to help, what a lad I say! :laugh:
Thanks for the tip, I can't wait to try it tonight. And worst case I fall down to LOS11 builds, I recently flashed CM11 on my N10 and damn do I love that classic Holo UI and stability of Kitkat, who knows, maybe I can build both! :fingers-crossed: :good:

Galaxyninja66 said:
Ha ha you stole my thunder linking that build there FollowMsi but I am incredibly thankful for your willingness to help, what a lad I say! :laugh:
Thanks for the tip, I can't wait to try it tonight. And worst case I fall down to LOS11 builds, I recently flashed CM11 on my N10 and damn do I love that classic Holo UI and stability of Kitkat, who knows, maybe I can build both! :fingers-crossed: :good:
Click to expand...
Click to collapse
To answer your latest private message ..
Here is the roomservice.xml for your .repo/local_manifests folder.
.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_samsung_manta" path="device/samsung/manta" remote="github" revision="cm-13.0" />
<project name="LineageOS/android_kernel_samsung_manta" path="kernel/samsung/manta" remote="github" revision="cm-13.0" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_audience" path="vendor/audience" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="github" revision="cm-13.0" />
</manifest>
Good luck !

followmsi said:
To answer your latest private message ..
Here is the roomservice.xml for your .repo/local_manifests folder.
.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_samsung_manta" path="device/samsung/manta" remote="github" revision="cm-13.0" />
<project name="LineageOS/android_kernel_samsung_manta" path="kernel/samsung/manta" remote="github" revision="cm-13.0" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_audience" path="vendor/audience" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="github" revision="cm-13.0" />
</manifest>
Good luck !
Click to expand...
Click to collapse
Yeah I only included like, 3 of those.

Thank you for posting this @Galaxyninja66 . It makes it so much easier to build with correct .xml file to start with as apposed to trying to manually add add in all the repos one by one. Thank you one again. I like to build my own roms for my device, if I can, and this was a massive help to me.
"Chance Favors the Prepared"
Sent from my Nexus 10 using XDA Premium HD app

glockman4519 said:
Thank you for posting this @Galaxyninja66 . It makes it so much easier to build with correct .xml file to start with as apposed to trying to manually add add in all the repos one by one. Thank you one again. I like to build my own roms for my device, if I can, and this was a massive help to me.
"Chance Favors the Prepared"
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Dont thank me, thank followmsi for that, and for the record, I am STILL getting build errors. ARGGG I don't even want to use LOS13 as a base anymore!!!

Galaxyninja66 said:
Dont thank me, thank followmsi for that, and for the record, I am STILL getting build errors. ARGGG I don't even want to use LOS13 as a base anymore!!!
Click to expand...
Click to collapse
Lol... Yes, I couldn't finish a build either. Oh well. I think in going to reinstall Ubuntu and start from scratch too.
"Chance Favors the Prepared"