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

[LOLLIPOP] Xperia AOSP Project

hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
PS.
in case latest software does not appear just press "all Services"
flash latest software available and on top new loader

Custom ROM We Want! (Xperia T3 D5102)

jerpelea said:
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
feel free to fork, build, fix and push back
Br
J
Click to expand...
Click to collapse
Good news for T3 devices!

All we need now is cwm/twrp recovery and the show may begin!!
great lollipot binaries... so android 5.0 will finally come to T3 ;p

updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

How do we set up?

Berkant Ayhan Karabudak said:
How do we set up?
Click to expand...
Click to collapse
if you read the guide you will see

jerpelea said:
if you read the guide you will see
Click to expand...
Click to collapse
I am in turkey. My english is not so good.

Do you make installation guides?

AOSP 5.0.2 is published
http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/

http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/
- updated L build guide published
- new blob zip
- wifi is built into kernel
- media is built from source now
- NFC built from source
- audio built from source
- GPS built from source
enjoy
J

Error in sony.xml
<project path="device/sony/kernel" name="kernel" groups="device" remote="sony" revision="aosp/LNX.LA.3.5.2.2-03010-8x74.0 " />
Click to expand...
Click to collapse
You have a space after 8x74.0 and the "

jerpelea said:
hi all
we have included this device in open devices project
...
feel free to fork, build, fix and push back
Click to expand...
Click to collapse
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.

lalotche said:
It seems to be fine idea before (or instead?) official release will come.
How much unstable is it?
Ok. Checked.
Git fetched 32GB of data. The laptop wheezed ~9 h but finally it is done.
The system itself works fine. But.
It is completely nude. I've been trying to insert Google Play Services. Defeat.
So. There is no possibility to connect it with Google account and services.
I'm afraid aosp is going to be always to
experimental for regular use. As it is development version.
Click to expand...
Click to collapse
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J

build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
br
J

jerpelea said:
AOSP is intended to be a stable base for custom ROMs and developers
you can make your own ROM with all the apps you desire
br
J
Click to expand...
Click to collapse
That sounds better.
I have not enough time to make it seriously and full time but I've got a few ideas to try and of course - I'm going to check new aosps and new GServ. releases.
As Google services are essential for android functionality until I get it stable I won't try to build more complex set.
Sent from my D5103 using XDA Free mobile app hurray

First shot.
So. It was little trouble for google made geek.
After a few hours of hard fight (I mean hard googling) I've got rooted system and gaps working.
I decided to root it to easier play with system apps. I did not want to hack source tree as well.
Curious - make_ext4fs changes file privileges (I've needed to add some stuff into system.img).
I had to add some lines to init.rc to correct it.
There are some minor issues appearing in dmesg - could live with that.
And the one major problem - internal speaker is dumb.
Ear phones works right, but speaker is necessary - this is my only phone
l

custom rom for sony T3 D5102
please port custom rom for sony xperia T3 D5102:good::good::good::good:

So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
I'm considering install an AOSP ROM because I love pure android but I guess I'll give a try to Sony's one until this ROM is perfectly stable.
Have nice day!
Enviado desde mi XT1032 mediante Tapatalk

gbueno6 said:
So, considering I'm a new owner of a Xperia T3, we can say that 5.0.2 ROMs are working "ok" except from speaker and camera that are not working?
Click to expand...
Click to collapse
Yes. It looks, that everything else for D5103 is ok.
I checked headphones, microphone, gps and wi-fi.
I did not check bt, nfc and others (accelerator?) but nobody reported its faults.
For me speaker is necessary but if you like I've got even rooted 5.0.2 with gaps (git 2015-02-15).
l

[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

[ROM][5.1.1][K920]AICP 10.0 for Lenovo Vibe Z2 Pro ROW

Unofficial build of AICP 10.0 for international Lenovo Vibe Z2 Pro ROW (K920)
DOWNLOAD
Google+ community
known bugs:
- HDR in Camera app not working
- flip cover not supported yet
- your TWRP may be replaced with Cyanogen recovery, DO NOT USE CYANOGEN RECOVERY to install anything for now! just reinstall TWRP from running CyanogenMod or in fastboot mode
- 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>
<remote name="codeaurora"
fetch="git://codeaurora.org" />
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="aicp-lp5.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_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-12.1" />
</manifest>
Click to expand...
Click to collapse

what is different between CM12.1 and AICP?

Very good rom. Please built more stable rom under AICP

Hi frantisheq, please buitl more AICP ROM and fix bugs like CM12.1 ROM for K920.
Thank alot.

new build will be here in 20 minutes https://mega.nz/#F!oFB0yKaS!Li8FbeZjcRKn2iO0wbfUZQ
it's uploading, i'm going to sleep

Thank you very much

frantisheq said:
new build will be here in 20 minutes https://mega.nz/#F!oFB0yKaS!Li8FbeZjcRKn2iO0wbfUZQ
it's uploading, i'm going to sleep
Click to expand...
Click to collapse
thanks!!! i will install this build instead cyanogen... how many bugs in this rom? :victory:

can you update this rom with cyano fixes (28 december) ?? thanks!!!!

Please update like CM12.1 and fix more bugs..

Yes, please update!!

i will but you know, new year just wait a few days
Sent from my K920 using Tapatalk

waiting for update
been using this rom for a week
few bugs like
home button no haptic feedback/ phone power on when plugged/ reboot is only power off but not rebooting
should i wait for this AICP update or just flash the CM12.1 rom from your other post?
thanks a lot!!!

Should wait frantisheq update AICP rom for K920

His k920 got hard bricked while trying cm13 and all methods of reviving are futile as of now. We are looking for 30 donaters so that he can continue his good work.
Interested users please email JohnSparrow
[email protected]
I'll try to copy paste the whole idea that JohnSparrow posted on original thread.
JohnSparrow said:
Ok. I propose the next:
1) Everybody who wants to help frantisheq to buy the new K920 in order to express the gratitude for his work and/or give him the ability to continue it, can mail me to [email protected].
2) Then I get 30 letters on the email above I will sent to the frantisheq 15$ (15$ х 30 participants = 345$, it will be enough for the http://www.gearbest.com/cell-phones/pp_184526.html).
3) I won't post the list of the emails which owners mailed me, but I will post the cheque which will prove my donation to the frantisheq. This little payment will be only the sign of gratitude for the work which is already done, it doesn't commit frantisheq to anything.
4) If another emails authors from the (1) will repeat my step (2), the frantisheq will have the ability to buy the new K920. If he decide not to buy it, well, it's current ROM (my version is dated 22/12/2015) much better than the Stock, I think, it worth 15$.
Happy holidays,
Click to expand...
Click to collapse

If another K920 to built CM13 and nee K920 brick again, I think frantisheq have to know how unbrick K920, the mothod unbrick very easy if know way do.
Remember Download mod K920 only 3 second, we press enter after K920 into Download mode.

new build with latest commits from CM https://www.androidfilehost.com/?fid=24369303960687391

frantisheq said:
new build with latest commits from CM https://www.androidfilehost.com/?fid=24369303960687391
Click to expand...
Click to collapse
thanks for this new build

I have 4-6 hours of work is loaded.. the animation speed is very quiet.

When i push restart ..The Phone goes off..can you fix it?? Thanks!! This bug doesnt exist un your cyanogen rom
Enviado desde mi K920 mediante Tapatalk

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"