Database Info

Trying to port kernel 3.0 for i9003, please help

Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.

crackerizer said:
Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.
Click to expand...
Click to collapse
Thank u very much! You could contact dhiru
Sent from my GT-I9003 using XDA

Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.

vishal24387 said:
Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.
Click to expand...
Click to collapse
That what I'm going to find out. For now, I'm trying to modify the init script and looking for help from some devs here to speed it up.

my wish- that you release it as fast as you can

R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success

sachin sharma said:
R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success
Click to expand...
Click to collapse
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.

vishal24387 said:
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.
Click to expand...
Click to collapse
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium

ephraim033 said:
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?

vishal24387 said:
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?
Click to expand...
Click to collapse
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium

ephraim033 said:
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, 10!

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!

@crackeziner is your 3.0 kernel booting ?

anuraagkochar said:
@crackeziner is your 3.0 kernel booting ?
Click to expand...
Click to collapse
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
what can do now??

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
Just give it try. Don't let it down guys
Sent from my GT-I9003 using XDA

sachin sharma said:
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!
Click to expand...
Click to collapse
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
u mentiond that u r getting errors while compiling right?
that means ur deconfig file is still not correct
all the codes needs to be changed according to "kernel 3.0"
not by porting codes from other kernels or previous kernels
n lastly all drivers are already given in the source code thers nothing to change in it except that u just have to compile!!!!!!

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
But did it boot?? Did u test that? When do u think u will be able to test that?

[Q&A] Cyanogenmod 10.1

This thread will be kept for troubleshooting issues with CM build by @KINGbabasula
Please report any bugs found in this thread and keep the Original thread clean.
Link to the thread will be posted here when build will be published
Do not ask for ETA.
Rom will be ready when it's ready !!!

ptothej said:
Hi all
I'm working on CM buil for our beloved i9105P a skullface has stopped the development for our device.
I've started to work on one with a big help from Skullface and a tons of tutorials found.
The thing is when it comes to compiling the build o got an error
No rule to make a target `/home/przemo/Source/out/target/product/i9105P/kernel', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/boot.img'. Stop.
Folder structure is set up as follows
kernel is in folder /home/przemo/Source/kernel/samsung/i9105P
and device files from github are in the folder home/przemo/Source/kernel/samsung/i9105P.
What i'm doing wrong ??
Any help appreciated
Click to expand...
Click to collapse
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"

panda00 said:
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"
Click to expand...
Click to collapse
But the out folder is being created when compiling CM build

ptothej said:
But the out folder is being created when compiling CM build
Click to expand...
Click to collapse
Oh sorry, I meant /home/przemo/Source/kernel/samsung/i9105P/kernel - put the zImage inside and rename it to "kernel".
Copied the wrong line
EDIT: Oops wait a second!

Will work on it tomorrow, to much computer screen for today
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2

Ok so kernel issue is done, was a typo in boardconfig file LOL.
Now ther issues
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libvpx_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_mpeg2ts_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_httplive_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_id3_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libFLAC_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libopensles_helper_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libOpenSLESUT_intermediates/import_includes
Export includes file: frameworks/ex/variablespeed/jni/Android.mk -- /home/przemo/Source/out/target/product/i9105P/obj/SHARED_LIBRARIES/libvariablespeed_intermediates/export_includes
Notice file: frameworks/av/media/libstagefright/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright.so.txt
Notice file: frameworks/av/media/libstagefright/colorconversion/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_color_conversion.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/mp3dec/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mp3dec.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/aacenc/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_aacenc.a.txt
Notice file: frameworks/av/media/libstagefright/matroska/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_matroska.a.txt
Notice file: frameworks/av/media/libstagefright/timedtext/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_timedtext.a.txt
Notice file: external/libvpx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libvpx.a.txt
Notice file: frameworks/av/media/libstagefright/mpeg2ts/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mpeg2ts.a.txt
Notice file: frameworks/av/media/libstagefright/httplive/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_httplive.a.txt
Notice file: frameworks/av/media/libstagefright/id3/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_id3.a.txt
Notice file: external/flac/libFLAC/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libFLAC.a.txt
Notice file: frameworks/av/drm/libdrmframework/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframework.so.txt
Notice file: frameworks/av/drm/common/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframeworkcommon.a.txt
Notice file: frameworks/av/media/libstagefright/omx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_omx.so.txt
make: *** Brak reguł do zrobienia obiektu `vendor/samsung/i9105P/proprietary/lib/libvorbisidec.so', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/system/lib/libvorbisidec.so'. Stop.
make: *** Oczekiwanie na niezakończone zadania....
Notice file: frameworks/av/media/libstagefright/yuv/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_yuv.so.txt
Any Ideas ?

Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer

ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
I m going to try cm10.1 soon
Bt I think I will wait for ur build.. good luck .

ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
BTW question. Is it with OC Or what ?

warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
It's Stock CM so to speak

warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P

panda00 said:
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P
Click to expand...
Click to collapse
As there is no custom kernel at the moment, neither do i have time or knowledge to compile custom kernel.
I've decided to compile GM build based on Skullface project.
As Panda00 said it's a long road ahead.

Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?

s2+user said:
Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?
Click to expand...
Click to collapse
You have a lot of questions. LOL.
Skullface's work is based on I9105P source , but he just misnamed it.
The stock boot.img cannot be used, you have to modify it (just a little bit) to work with CM. If you're using Skullface's work then that was done for you already.
I know that MEA is Middle East and Africa.. so yes they're regions.
Sent from my GT-I9105P

Kernel seems to have been built sucessfully :victory: but I didn't include pawitp's changes yet
Now I'm waiting for the rest to finish :fingers-crossed:

Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:

s2+user said:
Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:
Click to expand...
Click to collapse
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2

ptothej said:
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
Click to expand...
Click to collapse
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P

panda00 said:
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P
Click to expand...
Click to collapse
Could do

Well after all we need developers for everything else cause I'm no developer
I only wanted to try building CM and there is so much stuff that I want to know about the whole process of porting and building. But after all it's a little beginning :highfive:

[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1

This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download! ​
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!

Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.

whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...

mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess

got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build

rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.

Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4

scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.

vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app

scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.

vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!

TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.

scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.

mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.

scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.

scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.

[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc..

******* Hi all ********​I have developed this little tool containing a few utilities that should help anyone do a host of stuff like building Cyanogenmod..Compiling kernels..Play with ADB..GIt tools..etc​
DARK_Multitool1.0​
My tool is divided into five Modules(More to come in future if people find it useful)​
Module 1 : CyanogenMod Tools
- Installing the necessary libraries for compiling Cyanogenmod
- Initializing your repository and getting the Cyanogenmod source code
- Getting prebuilt apps/Device proprietary blobs
- Building Cyanogenmod for your device
Module 2 : ADB tools
- Creating logcat to debug your phone
- Installing apps via ADB
- Push/Pull stuff to/from your android device
Module 3 : Kernel tools
-Sony Kernel
Unpack Kernel Source
Create zImage of various devices(any Xperia)
Extract kernel.sin from ftf file
Unpack kernel.sin(to get zImage and ramdisk)
Make dt.img(For Xperia Z1 and Z ultra)
Make kernel.elf or boot.img depending on device
Test your kernel.elf/boot.img without flashing fully(Test run)
-Nexus Kernel
Getting the source code
Checkout the source code
Building zImage
-Samsung kernel
(Is under development as i develop for Xperia devices and not too familiar with samsung atm)
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
pearl script unpack or umkbootimg unpack
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Take kernel log : Thanks @ricky310711 for the commit
Module 4 : Backup TA partition for Sony or EFS partition on samsung
-Backup TA partition for Sony(By dd Method only)
-Backup or restore efs partition for Samsung(tar or dd method)
Module 5 : GIT tools
-Download GIT package on your linux
-Change directory where you want to initialize git
-Git repository setup(New git setup/Changes to old git setup)
-Update your local and remote git repository
-Commit your additions/deletions
-Push/Pull to/from your github repository
-Automatic push commits to your repository(After git setup is done)
-Download any repository using GIT
Download link
Dark_multitool1.0(With Update 1)
Update 2 added...Will upload soon..You can download this and update via tool to the latest version
Its better to download from XDA DevDB. You can either use the link above or click on downloads on top of the thread to download
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf dark_multitool1.0.gz
How to run it??
cd to the folder dark_multitool1.0 and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin(Tested on Cygwin by kevinrus123 : Some utilities are working)
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Sources
My github source : https://github.com/Smk1989/dark_multitool1.0
Mods : Please Move the thread if its in the inappropriate section
Updates
Latest update = Update 1
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc.., a Tool/Utility for the Android General
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-11
Last Updated 2014-01-03

FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition and EFS partition backup doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel or Cyanogenmod work directory?
Answer ; Navigate to the kernel or Cyanogenmod work directory and type in Terminal : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed. You can install from the tool itself under GIT tools
>Libraries missing while compiling kernel or cyanogenmod build errors on 64 bit machine??
Answer : Download libraries from cyanogenmod import libraries option( I will incorporate this in the next release) and for 64 bit compile error type : BUILD_HOST_32bit=1(Fixed and added in update 1)
Bugs and Suggestions
Please let me know

Changelogs
Update 2
>Added Xperia J in the build list of the tool
>Added Take kernel log in kernel options..Thanks @ricky310711 for the commit
>Added dry run option for Sony
-Lets you test your kernel.elf/boot.img(In case the kernel doesnt boot up..just restart phone and try again)
Update 1
>Cm-11.0 branch added while initializing repo(thanks mithun shanoj for the commit)
>Added umkbootimg unpack method
>Added import libraries option
>Added BUILD_HOST_32BIT=1 for 64 bit machines

Last one

No one tried??
Sent from my Micromax A110 using xda app-developers app

Maybe I am blind but where do I get the download?

Download Link?
Dude where is the download link???

I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
Dovidhalevi said:
Maybe I am blind but where do I get the download?
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal

Well well well.:beer: cheers.

Dovidhalevi said:
Maybe I am blind but I'll alwhere do I get the download?
Click to expand...
Click to collapse
rhar**** said:
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
Guys see the download tab on top of the thread.. I'll also add a download link if u want
Edit: Added a download link to the post

I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk

welcome to the world of kitchen creators goodjob!

Nice job man ?
Sent from my Nexus 7 using Tapatalk

Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:

Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..
i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
actually i learnt alot by viewing the content of tools, viewing it in raw format and learning how things work.
it encouaged me to find a way to make a kitchen for windows users and noobs.
so i guess im the perfect example

Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Click to expand...
Click to collapse
You have every right to express your opinion, but that being said, your post makes you sound like a real elitist, one who's upset that his elevated place in the exclusive club is about to be disrupted by those "filthy ruffians" who didn't earn their developer's chops by clawing their way up from the gutter. In my opinion, anything that brings in more developers to the community is a good thing. Sure, there are going to be plenty who use this tool as a shortcut to doing any hard work, but there are going to be those who use it as a starting point to further their knowledge of ROM building and modifying. Everyone needs a place to start, after all, but implying they'll never be "one of the boys" without beating their head bloody against a desk isn't at all helpful. Dark Wraith should be commended for creating a tool that will help bring new blood into the community.

Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
That's one side of the argument, if you re-read the first several pages of @championswimmer's kernel kitchen thread you'll be reminded just how strongly some people feel about this... I'm not in either camp by the way.
My point is that xda is not what it was, if we continue to post toolkits here it will only dilute the pool of serious development further. You just have to dive into an official CM Dev thread (N4 is a good example) at any point and browse, say, 25 pages to see exactly what I'm talking about...
For every one person that takes your tool, pulls it to bits to figure out how it works and goes on to do their own original work and contribute back, I feel sure that there'd be many more that just go ahead without any real understanding of what they're doing, expecting you and I to bail them out when it goes wrong... I hope that's overly cynical but, ironically, from evidence I don't think that is.
Your toolkit might have a place, and again all credit to you for putting it together. Personally I believe it's more hand holding (even more so than ROM or kernel kitchen) which ultimately helps no one.
Sent from my Nexus 4 using Tapatalk

hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss

Good stuff
Sent from my Nexus 5 using Tapatalk

Marsealdelo said:
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Click to expand...
Click to collapse
no bro..its not about support. Cm11 can run on ur device and you can build for it provided that you have the kernel source of your device available..For officially supported devices you will have the kernel source in cyanogenmod repository. For a device with no kernel source you cannot build cyanogenmod. What you are talking about is cyanogenmod porting to an unsupported device. Take a look around in cyanogenmod's wiki. I might add porting options in the tool in future but atm you can build only for offcially supported devices

[rom][d2303] pac-rom

PAC ROM for D2303
https://onedrive.live.com/redir?res...19&authkey=!AIAixlfmiDf-uR8&ithint=folder,zip
(unfortunately, I have no idea what happened with my Ubuntu, the build process doesn't create a .zip file, you'll have to flash it with fastboot boot/userdata/system)
of all the main things: wifi, mobile data, gps, voice calls working...camera not

installed on d2303 things that do not work.
Camera
proximity sensor
.During the call screen does Not turn off
handsfree speaker
* The data connection works 3G and 4G
themes CM WORKING FINE
everything else PERFECT
great job

Try putting this and the other roms in the right xda section shouldn't they be in the original Android development forum with cm+omni ect just a thought like few screenshots wouldn't go amiss either
D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more

[email protected] said:
Try putting this and the other roms in the right xda section shouldn't they be in the original Android development forum with cm+omni ect just a thought like few screenshots wouldn't go amiss either
D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
Click to expand...
Click to collapse
well, yeah, i honestly didnt know where to put them, because i didnt actually 'develop' them...the build process has errors that need to be fixed but i didnt think it is 'development' so i post them here

quake73 said:
well, yeah, i honestly didnt know where to put them, because i didnt actually 'develop' them...the build process has errors that need to be fixed but i didnt think it is 'development' so i post them here
Click to expand...
Click to collapse
So many roms..i bet your workspace is a mess right now
Local manifest you used for that rom? And can you post the errors? (use the "code" tag or paste them in pastebin and put link here)

Konstantinosj77 said:
So many roms..i bet your workspace is a mess right now
Local manifest you used for that rom? And can you post the errors? (use the "code" tag or paste them in pastebin and put link here)
Click to expand...
Click to collapse
xexe
about the errors that I had, I am more than glad to share them (I have a simple text file and write reminders there, to remember them and not "reinvent the wheel" every time)
For this one, PACROM, I think the only error was 'unsupported relloc 43', the cure is:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/x86_64-linux/bin/ld
(for a long time, i thought the cure was WITHOUT_HOST_CLANG=true)
the manifest is a mess but here it is...i also have created a file in vendor/pac/products and added cm.mk in device/sony/eagle...built it with "build-pac.sh eagle"

quake73 said:
xexe
about the errors that I had, I am more than glad to share them (I have a simple text file and write reminders there, to remember them and not "reinvent the wheel" every time)
For this one, PACROM, I think the only error was 'unsupported relloc 43', the cure is:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/x86_64-linux/bin/ld
(for a long time, i thought the cure was WITHOUT_HOST_CLANG=true)
the manifest is a mess but here it is...i also have created a file in vendor/pac/products and added cm.mk in device/sony/eagle...built it with "build-pac.sh eagle"
Click to expand...
Click to collapse
oh good old "unsupported relloc" i use arch linux and got it in every build.
It's fixed on AOSP master branch https://android-review.googlesource.com/#/c/223100/
CM13 uses this patch too

Konstantinosj77 said:
oh good old "unsupported relloc" i use arch linux and got it in every build.
It's fixed on AOSP master branch https://android-review.googlesource.com/#/c/223100/
CM13 uses this patch too
Click to expand...
Click to collapse
(mine is virtual Ubuntu 16)
i must admit, the 6.0 roms are building 'more flawlessly' than the 5.1 variants....and it seems that 5.1s are not getting any more fixes.
i dont know if you are trying to build any but...i tried building cm12.1 for 2 weeks, with every possible combination of device tree and vendor (SonyAOSP/SonyCM/xperiadev/CM, sony vendor files/Benevolent) and there is no mobile data connection, any ideas?

quake73 said:
(mine is virtual Ubuntu 16)
i must admit, the 6.0 roms are building 'more flawlessly' than the 5.1 variants....and it seems that 5.1s are not getting any more fixes.
i dont know if you are trying to build any but...i tried building cm12.1 for 2 weeks, with every possible combination of device tree and vendor (SonyAOSP/SonyCM/xperiadev/CM, sony vendor files/Benevolent) and there is no mobile data connection, any ideas?
Click to expand...
Click to collapse
Not a single idea...did you checked logcat or something?

Konstantinosj77 said:
Not a single idea...did you checked logcat or something?
Click to expand...
Click to collapse
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7

quake73 said:
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7
Click to expand...
Click to collapse
haha i suggest you to install ubuntu natively using dualboot
It's a lot faster

Konstantinosj77 said:
haha i suggest you to install ubuntu natively using dualboot
It's a lot faster
Click to expand...
Click to collapse
hehe, i had that crazy idea, too but....i'm a windows guy, the current setup is quite good...16gb ram (8 for ubuntu),
4 HDs, home/cache/out/swap distributed on different HDs, what more can I ask? It's an old pc, AMD x64 x4, 7-8 years but it serves me well...My heart doesnt let me replace it

What is jumpin in rom
quake73 said:
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7
Click to expand...
Click to collapse
Quake that is not taking in Rom?

i think the thing make this rom has no camera working is boot.img 3.10.x because every rom using this kernel has no camera working and please show me how to make 3.4.x kernel is working inside this rom

vinz156 said:
i think the thing make this rom has no camera working is boot.img 3.10.x because every rom using this kernel has no camera working and please show me how to make 3.4.x kernel is working inside this rom
Click to expand...
Click to collapse
thats a good idea. I'll try to build again with one of the older kernels from sonyxperiadev.

quake73 said:
thats a good idea. I'll try to build again with one of the older kernels from sonyxperiadev.
Click to expand...
Click to collapse
It's not gonna work...
Only stock kernel and stock camera blobs can make camera work....

Konstantinosj77 said:
It's not gonna work...
Only stock kernel and stock camera blobs can make camera work....
Click to expand...
Click to collapse
How about cm12.1 what's make camera inside that rom is fully working
Sent from my Xperia M2 (AOSP) using XDA-Developers mobile app

vinz156 said:
How about cm12.1 what's make camera inside that rom is fully working
Sent from my Xperia M2 (AOSP) using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock kernel and stock modules....
These are used for omni 5.1.1 with working camera
Code:
https://github.com/erikcas/android_kernel_sony_msm/tree/5.1-3.4
https://github.com/erikcas/vendor-sony/tree/r13-cam
https://github.com/erikcas/vendor-qcom/tree/r13-cam
Sometimes you have to make changes to the framework files of the ROM and to the device tree