[REQ] Custom kernel for SM-915G - Note Edge Q&A, Help & Troubleshooting

Hello developers,
Just a kind request, there are custom kernels for exynos version of note edge but no custom kernel for SM-915G snapdragon model.
Need to activate init. scripts which is not possible on stock kernel
devs and mods please help to make the powerful tweaked custom kernel.

Hi.. I would love for 915f .. I have downloaded and setup build environment for the kernel but the code as is from Samsung has problems .. references a driver for fc2350 or something like on initial 'make clean' .. on checking the file is defiantly not included.. if I amend referencing file either remove or change to duplicate the file that is there I still get another missing file
.
So really need a Dev to setup a working code base... please

Related

Adding Swap support to JB 4.1 kernel

Hi developers
I want add swap support to my MTK android 4.1 kernel 2.6.35 thanks to members of the forum to tell me how
Compiling the kernel from source adding the line CONFIG_SWAP=y in config file. and them swaon script (am I right?)
I'm following ubuntu terminal tutorials for it.
But What should I do if I dont want use a open source kernel code??
I mean if I wanna use the same kernel from the phone, IS there
any way to open and modify the existing kernel??
I read its can be dangerous for a MTK use another kernel, and I found a mtk6575 open source kernel but it isn't specific to my phone
so, I dont wanna use another!
I hope I can use my original kernel and add it swap support
by the way I have 2 diferents backup from my phone, If I can use it wich one?

[Windows Kitchen Development] Adding multi-device support

Hey guys, i know this is abit unproffesional of me but im asking people(anyone) to comment their device(ro.product.device) and there kernel block path for me! the kitchen currently has universal support and is COMPLETELY automatic apart from installing the kernel, that has to be manually added, but hopefully after this it wont be for most devices!
To get the information required you can get the ro.product.device value from /system/build.prop
as for the kernel block, if you dont know how to get it id rather you not guess as peoples devices could be at risk.
So heres what i need(just an example of the Galaxy S3)
Samsung Galaxy S3
ro.product.device=m0
dev/block/mmcblk0p5
thanks guys, the kitchen is COMEPLETELY noob friendly and anyone can use it(when i say that i honestly mean ANYONE)

[Completed] Partially building a custom rom

Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
crazydude10 said:
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
Click to expand...
Click to collapse
Greetings,
Please read the Sticky threads for XDA Assist. This is not a help desk. XDA Assist is for helping new members or visitors navigate this site. You are a Senior Member and therefore you should know how to use the search feature and find the correct thread to ask your questions.
Thanks for understanding.
Thread closed.

New to XDA and need some guidance.

Hello everybody,
I am pretty new to the forums and want to learn how to make my own ROM. However, I want to learn how to do it from scratch. I have been reading the AOSP pages and my current knowledge is that I understand a bit about the Kernel and about the HAL. My question is about drivers. From my understanding Android's Kernel contains the driver for your particular device. Do I have to obtain a Samsung Kernel for a custom ROM for the S6 and S6 Edge from Samsung? Or can I simply find the Samsung drivers for each different model and integrate them into the standard Android Kernel (and tweak the driver to fix any bugs that come along the way). The Kernel distribution really confuses me. I feel as if every OEM should have to provide an archive of drivers in order to use Android to make the AOSP stronger. Am I constrained to Samsungs Kernel explicitly?

How to port rom from HTC sensation?

I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)
Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!

Categories

Resources