Related
New thread:
Why did you made a new thread?
mDroidd said:
Hello
first: I want to release this public, but to start I decided to share it with some known guys
I'm into android for a while right now, and tried many things.
A few examples:
theming
build from kitchen
adb
build from source
To do these things, you need to do some steps. If you don't know what they are, or how you should do 'em, then you're in the right place
I teached myself (and my father teached me) some bash scripting.
ATM, I use it for resizing images.
I'll upload a screen tomorrow, together with more detailed specs.
For now, it's an easter egg for you to find out
FEATURES:
DOWNLOAD:
HOWTO:
Remember, many features will come later.
You kids have fun.
Click to expand...
Click to collapse
Wow! That would be cool!! HDPI>MDPI conversion would be very easy!! Thanks!!
Sent from my LG-P500 using XDA App
You're welcome, I had the problem first also
It uses a package called "imagemagick" and a few others, with a nice combination of commands
And don't say thanks only, also thank me
mDroidd said:
You're welcome, I had the problem first also
It uses a package called "imagemagick" and a few others, with a nice combination of commands
And don't say thanks only, also thank me
Click to expand...
Click to collapse
Good work!
Il have to try it asap...!
Updated first post, updated app, updated link.
It's now a direct link, just give it a shot!
And from now on, if people are not grateful (but they don't have to thank me) OR do not give comment on how I could improve it, I will keep this private and for my friends only.
Nice tool!
Will take a look at it and if I have some more ideas to include, I will let you know ; )
Sent from my LG-P500 using XDA App
mDroidd said:
Updated first post, updated app, updated link.
It's now a direct link, just give it a shot!
And from now on, if people are not grateful (but they don't have to thank me) OR do not give comment on how I could improve it, I will keep this private and for my friends only.
Click to expand...
Click to collapse
You might wanna release this in the General Android Development section where more people will be interested, since here there are quite few who are new to developing on android and there are more full-fledged developers who basically dont use such tools... releasing this in the general development section will encourage more newbies who are fairly new to editing apps n stuff or building an environment... this tool is great, but you need to make it public to get the 'actual' response u want...
Anyway, all the best for this tool, sadly now i dont have my pc, jus an old crappy netbook which is jus nuff fo browsing... shall try this in march after my final exams...
RockR172 said:
You might wanna release this in the General Android Development section where more people will be interested, since here there are quite few who are new to developing on android and there are more full-fledged developers who basically dont use such tools... releasing this in the general development section will encourage more newbies who are fairly new to editing apps n stuff or building an environment... this tool is great, but you need to make it public to get the 'actual' response u want...
Anyway, all the best for this tool, sadly now i dont have my pc, jus an old crappy netbook which is jus nuff fo browsing... shall try this in march after my final exams...
Click to expand...
Click to collapse
Thank you also, and you Arjen also.
I will release it there, and also in Android Chef Central. There will more people be intersted, I know.
But for now, I think you people would be nicer to me iwth suggesting idea's, just becuase some of you may know me
Anyways, after someone made a suggestion and I was able to include it and include cpfr, I will release it there
OK, done. included some more things.
I think I will be trying to PORT APK MULTI-TOOL to Linux
Should not be too hard. I'll include it in my script when it's done and submit it to the DEV to publish it.
But I want you to make a request, just to keep myself busy!
Is there ANYTHING that takes you too long, seems too hard for you, or something you want to automate?
If not, I'll continue with building from source.
Please comment within 3 days
mDroidd said:
OK, done. included some more things.
I think I will be trying to PORT APK MULTI-TOOL to Linux
Should not be too hard. I'll include it in my script when it's done and submit it to the DEV to publish it.
But I want you to make a request, just to keep myself busy!
Is there ANYTHING that takes you too long, seems too hard for you, or something you want to automate?
If not, I'll continue with building from source.
Please comment within 3 days
Click to expand...
Click to collapse
Maybe, automate the setting up of build environment for various versions of android...
So it would be like just start ur tool, go into the menu, select the build environment for the version your gonna build and it all does it by itself...
Downloading/installing packages etc..
I havent tested your tool so dunno if u have already included it in your tool...
Also, you might wanna create a directory of different types of custom roms and their github source codes link... like for example, cyanogenmod, omfgb, omgb, oxygen, aokp, codename android and so on...
So i open your tool, select the source i wanna download and it will do it...
Just my 2 cents...
Sent from my LG-P500 using XDA App
RockR172 said:
Maybe, automate the setting up of build environment for various versions of android...
So it would be like just start ur tool, go into the menu, select the build environment for the version your gonna build and it all does it by itself...
Downloading/installing packages etc..
I havent tested your tool so dunno if u have already included it in your tool...
Also, you might wanna create a directory of different types of custom roms and their github source codes link... like for example, cyanogenmod, omfgb, omgb, oxygen, aokp, codename android and so on...
So i open your tool, select the source i wanna download and it will do it...
Just my 2 cents...
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
+1 I think that would be a great addition.
Sent from my LG-P509 using xda premium
Lol, the first thing about installing packages is already included.
I sent you a PM about smthing, pkease watch.
I am busy including the next step: build environment.
Expect it to work within 2 days, if you click the first link it'll be one
Greets!
If you need a Hans with anything let me know
Sent from my PC36100 using Tapatalk
tommytomatoe said:
If you need a Hans with anything let me know
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Sure, I will Thank you.
Btw, tge post is now also at Chef central ;(
Greets!
Updated first post with FEATURES tab
Now everyone who will read this will answer?
mDroidd said:
Updated first post with FEATURES tab
Now everyone who will read this will answer?
Click to expand...
Click to collapse
A small typo??
Should'nt it be 'prepare build FROM source' and not 'form' source??
Leaving it, its come out great... n thx...
Did u add the directory stuff??
Sent from my iPad 3 using XDA App
RockR172 said:
A small typo??
Should'nt it be 'prepare build FROM source' and not 'form' source??
Leaving it, its come out great... n thx...
Did u add the directory stuff??
Sent from my iPad 3 using XDA App
Click to expand...
Click to collapse
Directory stuff: mik: done, oxygen: done, AOSP: done.
But adfad has multiple sources... I am gonna ask him
And yeah, typo, I'll edit right away!
Greets!
mDroidd said:
Directory stuff: mik: done, oxygen: done, AOSP: done.
But adfad has multiple sources... I am gonna ask him
And yeah, typo, I'll edit right away!
Greets!
Click to expand...
Click to collapse
Wait, this tool isnt just for O1...!
Its should me made for every phone out there... so maybe you should add the official sources and not ported sources... cuz if you start including port sources, it will be too much hassle trying to keep the source links updated, sometimes they change, too many ports for every available android device etc...
Also, u will b flooded with requests to add this source, add that source..
Do it like:
CyanogenMod- full official source from CM, github.com/cyanogenmod
Oxygen- full official source by oxygen team, (i dont remember the links)
AOSP
AOKP
CodeNameAndroid
OMGB
OMFGB
Etc etc
Add the official repo's n not ports...
It will help in keeping the sources more update as the official teams work more on their sources than individual porters do on their own sources...
Sent from my iPad 3 using XDA App
RockR172 said:
Wait, this tool isnt just for O1...!
Its should me made for every phone out there... so maybe you should add the official sources and not ported sources... cuz if you start including port sources, it will be too much hassle trying to keep the source links updated, sometimes they change, too many ports for every available android device etc...
Also, u will b flooded with requests to add this source, add that source..
Do it like:
CyanogenMod- full official source from CM, github.com/cyanogenmod
Oxygen- full official source by oxygen team, (i dont remember the links)
AOSP
AOKP
CodeNameAndroid
OMGB
OMFGB
Etc etc
Add the official repo's n not ports...
It will help in keeping the sources more update as the official teams work more on their sources than individual porters do on their own sources...
Sent from my iPad 3 using XDA App
Click to expand...
Click to collapse
I did
I am making funtions like this in bash:
function AOSP
{
repo init -u blablabla
}
and downstairs the script
AOSP
So you can edit it above
I am now making an LG Specific and a stock android one
Updated
Changelog:
Code:
#v1b4:
[^]Added copyright
[^]Updated Animation
[^]Added second section; looks better
[^]OOPS! I added CopieFrom under the option "c" wich is already changelog!
[^]Improved other than home directory - was not working
[^]ICS Blue characters <3
[^]Added BUILD FROM SOURCE option
[^]Custom animation speed :)
[>]To try if this works, please go into terminal and type:
cat --help
if it tells you the manual for "cat", then you are fine.
Option D from the main menu.
Have fun
The /system/etc/custom_backup_list.txt file prevents CyanogenMod based ROMs from overwriting selected files within the /system directory when flashing or updating a new ROM. This could be useful when you're using custom system files, like a custom Mms.apk, ringtones stored on the /system drive, etc. This simple yet effective app provides an easier way to manage the custom_backup_list.txt file.
Background info
I started developing this app for my own use, just because I wanted to learn how to write apps for Android. Halfway the development somebody motivated me into bringing this app to the public, and here I am, releasing it ad-free on XDA only.
Features
Read the current custom backup list
Add new entries
Remove entries
Undo all actions
Manually refresh list
Save new custom backup list
Localizations: English, Dutch
Permissions
Root access needed; R/W access to the custom_backup_list.txt file
Feedback
Although I've spend weeks into carefully developing this app, it may still contain some bugs, mainly because it's my first Android app. If you encountered any problems while using this app, I'm really sorry and would like to ask you to PLEASE report these problems in this thread. Suggestions and/or other feedback are, of course, also more then welcome.
Screenshots
Please click the thanks button if you find this app useful and/or leave some feedback after trying this app. Trust me, this will make my day.
Very good idea! I will try it at my next rom update, w8ing for temasek! Good job m8 :thumbup:
Sent from my Optimus 2X using xda app-developers app
I think I've made a mistake by posting this in the Optimus 2X subforum only, as this should work on any CM powered device. I expected a little more feedback (especially conformations about the functioning) by now. But I was afraid that if I posted it somewhere else it wouldn't reach the part of the community who I love the most.
Venox85 said:
Very good idea! I will try it at my next rom update, w8ing for temasek! Good job m8 :thumbup:
Sent from my Optimus 2X using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, if you got any feature requests just let me know.
It works beautiful! Everything as it should and i don't have to recopy-repaste and fix permissions for 5 apk!
Very good job
Sent from my Optimus 2X using xda app-developers app
Worked great on CM7 on my Nexus thanks for this but any chance you could make this compatible for CM newer addon.d method?
Genius
Works flawlessly. Thanks.
dsixda's Android Kitchen - Now for Samsung Galaxy Note GT-N7000
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy Note GT-N7000 custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy Note GT-N7000 ROMs with the kitchen.
To my surprise, since the file structure is very similar to that of the Galaxy SII GT-I9100, I only had to make a very minor update to the kitchen (one blank file) to allow GT-N7000 support.
Special thanks to long-time XDA user Ameet for testing and providing feedback!
I have already posted an equivalent guide for the Galaxy SII I9100, so no need for redundancy. The same steps will work for your device:
CLICK HERE FOR KITCHEN INSTRUCTIONS FOR YOUR GALAXY NOTE GT-N7000.http://forum.xda-developers.com/showthread.php?t=1227549
NOTE: This guide does not apply for the other models of the Galaxy Note; there is a separate thread for the SGH-I717.
Since the above link is for I9100 discussion only, please post all N7000 talk in the thread right here. Enjoy!
So good to see you here. Welcome.
chasmodo said:
So good to see you here. Welcome.
Click to expand...
Click to collapse
Thanks, I don't have the device but I have its little brother, the Exynos-based Galaxy SII GT-I9100
Thanks for coming over. I have actually been using it on the Note for a long time. Its a great tool. Thanks for developing it mate
Thanks for this...
Sent from my GT-N7000 using Tapatalk 2
Awesome work as always Dsixda, as always.. Am sure this will be of great help for Note users
Sent from my GT-N7000 using xda premium
---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------
Am surw many know this still thought I'll post an observation as a note
"You have to extract the CSC from cache.img and copy it to system folder to avoid the keyboard null error after flashing"
Sent from my GT-N7000 using xda premium
was waiting for this
Thanks a lot.
Nice to see you thanks mate
Sent from my GT-N7000 using Tapatalk 2
Awesome
I'm here at work, setting this up instead of working. Don't tell anyone...
Great.
Thanks:thumbup::thumbup:
Von meinen Project-ReVo Black Beast gesendet.
Nice I will try it as soon as possible
Heyyyy! Thx read all about the kitchen in another thread . Glad it is here . Time to cook.
Sent from a secure institution......
Great to see official NOTE support. :laugh: You're amazing dsixda...A HUGE Thanks from all the XDA members!! :good: :fingers-crossed:
Thank you!
Welcome Here, Master,
We had Pleasure using the Kitchen in S2, now I don't find the words !!!! :fingers-crossed:
THANKS A MILLION.
this is so cool...too bad i dont have my ubuntu now...and i dont like using cygwin.but this is good to know.. it exists:cyclops:
@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?
asf58967 said:
@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?
Click to expand...
Click to collapse
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick
not-i said:
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick
Click to expand...
Click to collapse
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip
asf58967 said:
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip
Click to expand...
Click to collapse
Copy the preload folder into working folder before you deodex or do any mods. Thats what I have done anyway. I would then cut all apks from prelaod/app and paste into system/app for the deodex. Then when that is done copy those back that you want in preload.
The program will create the zip for you when you build it. I have found I need to modify updater script 9 out of 10 times though for it to flash. If yoour having trouble let me know and I'll forward you a script that works.
Make sure when you go through the process that the rom zip also includes create_preload_symlinks script. It should put this in for you in the process though.
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.
this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app
tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much
*EDIT* This thread is now based upon the work by @fattire and @slayher, who got it up on the 910T. For that phone see this thread: http://forum.xda-developers.com/not...nt/unoffcial-cm-12-0-t-mobile-note-4-t2964887
This thread is for dev's interested to help out porting CM12 to our device. I've researched for info regarding CM ports and good information is actually quit scarce. A dev might post something like 'hmm stuck at boot anim' and then the next day 'got it, booting now !' without explaining what he did to solve it. I want to change that, so this thread can serve as a guide for other first time porters too (this is also my first porting project), documenting every step as in much detail as possible.
For ROMS: http://forum.xda-developers.com/not...official-cm-12-0-910f-note-4-trltexx-t2987412
Please use this thread for R&D/development ONLY !!!
Ok, I'm really starting from scratch and never done any phone ROM porting. I've just made a new virtual disk running ubuntu and am currently downloading the CM12 repo. I figured, how to get even started here. I figured that the goals we need to attain in this order:
1) compile the kernel samsung supplied
2) make sure we can boot into kernel
3) get ADB up and running
4) get CM12 starting up, even the bootanim alone would be a nice goal to reach
5) Booting into homescreen
6) Fixing all stuff like modem, wifi etc etc etc
Anyway, I'm currently downloading CM12 sources as we speak ...
This is by the way a link I found very useful: http://www.androidenea.com/2009/08/init-process-and-initrc.html It describes the Android init process, cause I was wondering, how to even start all this ? How to get from kernel to CM booting: that's where init.rc should come into play of course
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
KaptKeefmenneke said:
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
Click to expand...
Click to collapse
I'm not sure I understand what you mean ? If the phone already has support, then what's there to port ? Or do you mean building CM itself ? That I've done quite a few times already, did quite a bit of work on the i9500, fixing RILD issue's, kernel issue's and other stuff.
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Shouldn't this thread be in general?
jdidtht said:
Shouldn't this thread be in general?
Click to expand...
Click to collapse
yes it really should being as there is no development only discussion...but thats the moderators job not mine
spleef said:
yes it really should being as there is no development only discussion...but thats the moderators job not mine
Click to expand...
Click to collapse
Threads regarding R&D belong in development, so I guess it really belongs here. Even more so cause if it's moved to general, tons of n00bs will join in and destroy the thread. please keep this developers only.
Anyway thanks to see you join in Spleef, much appreciated !! Still setting up my environment myself ...
spleef said:
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Click to expand...
Click to collapse
Great addition to the thread ! Hmm I haven't done any porting myself. I figured once we have a kernel up (compiling it should be easy), then what's stopping us from booting CM ? I mean of course RILD won't work if we don't have a JNI (or what's it called on ART, ANI ? ) interface to the modem. Of course we won't have NFC, internet, telephony, all that. But merely booting a graphical interface that should be doable with Nexus 6 source code, right ? I mean all we need is SoC sources so we have cpu & graphics working, right ? So That was what I had in mind myself but your approach actually is quite the same now I think of it
Thread is moved to general AGAIN. Hehe. Starting a development thread ON XDA and have it in the developer section seems harder than porting CM12 Anyway I guess it doesn't matter in which section it is, as long as n00bs and trolls stay out and we can focus on development only.
Anyway, downloading kernel sources as we speak ...
BTW, here is Nexus 6 source code: http://www.xda-developers.com/android/google-nexus-6-factory-images/
Going to down that right now too ...
Ok, building kernel as we speak. I just installed the arm-eabi-4.7 toolchain, like this:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/
And then edited the makefile and issued the 3 commands all as specified in README_Kernel.txt from the Samsung Kernel. So far so good
And yes, as expected, build breaks:
drivers/scsi/ufs/ufs_test.c:25:19: fatal error: ../sd.h: No such file or directory
compilation terminated.
make[3]: *** [drivers/scsi/ufs/ufs_test.o] Error 1
make[2]: *** [drivers/scsi/ufs] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
Hehe, Samsung wouldn't be Samsung if they would supply a kernel that actually builds from the start Going to investigate ...
Actually that seems like an easy fix, just linked the file correctly
And a new break:
In file included from drivers/gud/MobiCoreDriver/logging.c:21:0:
drivers/gud/MobiCoreDriver/main.h:24:22: fatal error: platform.h: No such file or directory
I'd say it's looking for the file in platforms/MSM8960_SURF_STD, going to link it correctly ...
And building again ...
n file included from drivers/video/msm/mdss/mdss_mdp_trace.h:255:0,
from drivers/video/msm/mdss/mdss_mdp.c:61:
include/trace/define_trace.h:79:43: fatal error: ./mdss_mdp_trace.h: No such file or directory
Include should point to kernel includes, fixing it again
And building again ...
Code:
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
LZO arch/arm/boot/compressed/piggy.lzo
AS arch/arm/boot/compressed/piggy.lzo.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Kernel ready Of course that was the easy part, hehe, but still, progress. Tomorrow going to start with the difficult part, getting CM up
I've ported before but only tw where it was mainly framework edits. Never worked with cm before but like the op I'm keen to learn. If i can help at all just let me know, I use linux mint myself rather than Ubuntu but they're very similar
So, just downloaded Nexus 6 sources. It seems that directory /device/moto/shamu contains the device hardware stuff we need ! Going to research some more today ...
*EDIT* also mind the propietary-blobs.txt in that directory. I'm still waiting for my Note 4 myself (hopefully friday), but this needs to be compared with the files on the device, cause if they exist, they will be blobs of course and we need them.