Database Info

[dev][kernel][sgp512] 17.1.1.a.0.402

SGP512 Kernel, first attempt since I just got the device yesterday.
- close to stock
- disabled a few modules which are rather not going to be used
- disabled debug
- integrated wlan driver & configured so that it loads properly
- integrated exFAT
Instructions:
- unzip contents, copy over the modules to /system/lib/modules (remember to set the correct permissions)
- reboot into bootloader & flash the kernel
Code:
fastboot -i 0x0fce flash boot boot.img
fastboot -i 0x0fce reboot
Download binaries: https://drive.google.com/file/d/0B8rpJsF4EG0YMFNHYWZhSHQ5VW8
source

Er... nice that someone starts developing for this device... but:
- what is wrong with the stock WiFi driver? I don't see any problems...
- exFAT is already integrated, no need of special kernel...
Doesn't seem very flash-worthy

I would really appriciate a custom kernel for the Tablet so that we can undervolt the cpu and change frequencies and governors.
But wouldn`t it be the best and easiest way to port (of course with the approval of doomlord) his already existing doomkernel from the Z2 phone?

hasenbein1966 said:
Er... nice that someone starts developing for this device... but:
- what is wrong with the stock WiFi driver? I don't see any problems...
- exFAT is already integrated, no need of special kernel...
Doesn't seem very flash-worthy
Click to expand...
Click to collapse
You won't be able to use the stock modules if you start messing too deep with the kernel & there is no in-kernel (3.4.0) driver for the bcm4339 which the Z2 uses, unless you want to mess with the brcmfmac driver.
Try using the compiled kernel I attached without copying over the associated wifi driver.
Frankus99 said:
I would really appriciate a custom kernel for the Tablet so that we can undervolt the cpu and change frequencies and governors.
But wouldn`t it be the best and easiest way to port (of course with the approval of doomlord) his already existing doomkernel from the Z2 phone?
Click to expand...
Click to collapse
You can already change the freqs & governors with tools like PerformanceControl.
The only part which would need coding is UV control & a sysfs interface for it.
I'll do it sooner or later in my free time, but seeing as I don't have much of the latter, you'll surely see the features being implemented by other devs. Or you can code/port it yourself ;]
This post was never intended to being a starting point for developing a kernel for the community. I got the device 2 days ago & prepared my base for private kernel development & since I didn't see any posts related to a kernel base for the Z2 Tablet I wanted to share it so that interested parties could have a good starting point.
It was NEVER intended for end users.

adwinp said:
You won't be able to use the stock modules if you start messing too deep with the kernel & there is no in-kernel (3.4.0) driver for the bcm4339 which the Z2 uses, unless you want to mess with the brcmfmac driver.
Try using the compiled kernel I attached without copying over the associated wifi driver.
You can already change the freqs & governors with tools like PerformanceControl.
The only part which would need coding is UV control & a sysfs interface for it.
I'll do it sooner or later in my free time, but seeing as I don't have much of the latter, you'll surely see the features being implemented by other devs. Or you can code/port it yourself ;]
This post was never intended to being a starting point for developing a kernel for the community. I got the device 2 days ago & prepared my base for private kernel development & since I didn't see any posts related to a kernel base for the Z2 Tablet I wanted to share it so that interested parties could have a good starting point.
It was NEVER intended for end users.
Click to expand...
Click to collapse
ok, sony released the kernel code on git some time ago, any news with your kernel?

spider623 said:
ok, sony released the kernel code on git some time ago, any news with your kernel?
Click to expand...
Click to collapse
I release this kernel since there were none at that time, at least none integrating the wifi driver & exfat.
Till then, the kernel development for the Z2 tablet took off, so there's no need to keep this post updated.

adwinp said:
I release this kernel since there were none at that time, at least none integrating the wifi driver & exfat.
Till then, the kernel development for the Z2 tablet took off, so there's no need to keep this post updated.
Click to expand...
Click to collapse
really? i haven't seen any other kernels around

spider623 said:
really? i haven't seen any other kernels around
Click to expand...
Click to collapse
Uhmmm.... me neither to be honest.
However, it's extremely nice to see people taking part in kernel development. It's not so easy as one thinks. It's a lot of "trial and error" before something can be released to the public.
(patiently awaiting my Z2 tomorrow)

[DEV] Porting kernel 3.10.x to d2 for Lollipop

As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!

Does your kernel compile and boot on cm11? If it does, there shouldn't be much problems in getting it working on L.

Any news? Does it compile?

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y

Ivan_Meler said:
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Click to expand...
Click to collapse
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
ztotherad said:
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
Click to expand...
Click to collapse
I know samsung does things like that (i have few other devices from them) but hey thats samsung and they are lazy so they dont want to update kernel version after device is relesed so they do this not to feel outdated on softwere side

Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works

frap129 said:
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
Click to expand...
Click to collapse
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
I was planning on working on that as well over the weekend.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays

Ivan_Meler said:
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Click to expand...
Click to collapse
I'm very new to the AOSP build process and didn't have much luck last night getting the CM device sources to play nicely with AOSP. I'm finding it difficult to find any relevant guides on porting over the CM device trees to pure AOSP. If you or anyone else can help by explaining the process or pointing to a guide that I may have missed, I'd be grateful. Plus the more people we have collaborating on his, the better our chances of getting Lollipop on our devices.

I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy

Restl3ss said:
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Click to expand...
Click to collapse
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?

polarEskimo said:
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
Click to expand...
Click to collapse
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)

Restl3ss said:
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Click to expand...
Click to collapse
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.

polarEskimo said:
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
Click to expand...
Click to collapse
I'll push what I've got to github after this experiment

Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much

Ivan_Meler said:
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Click to expand...
Click to collapse
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS

Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!
Build currently hangs at this:
Code:
host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night

Restl3ss said:
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Click to expand...
Click to collapse
I'm with you on that, I'd rather have pure AOSP than buggy CM nightlies. Also interesting choice of ROM name lol. Thanks for your hard work and I'm looking forward to pulling down your repos so I can take a stab at these compile-time issues.

[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.

[Discussion] Porting Nougat kernel to Oreo.

Okay so we have nougat kernel source code and oreo will be released soon(hope so)
Let it be noted that this post isn't asking anyone to port kernel to Oreo.
I just wanted to know what kind of work it takes if a determined dev is trying to port nougat kernel to oreo.
What are the major roadblocks?
Just give your 2 cents.

alkesh95 said:
Okay so we have nougat kernel source code and oreo will be released soon(hope so)
Let it be noted that this post isn't asking anyone to port kernel to Oreo.
I just wanted to know what kind of work it takes if a determined dev is trying to port nougat kernel to oreo.
What are the major roadblocks?
Just give your 2 cents.
Click to expand...
Click to collapse
Most of the needed commits are binder related
Plus you need some extra defconfig flags..you can extract defconfig from stock boot.img....

kernel j4 j400

kernel j4 oc to 1.9ghz
XXXXXX MOD EDIT: Link removed
XDA:DevDB Information
j4 kernel j400, Kernel for the Samsung Galaxy J4+
Contributors
minhka98, av.
Source Code: https://github.com/minhker/android_kernel_samsung_j4lte
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2.4
Stable Release Date: 2018-11-29
Created 2018-11-29
Last Updated 2020-02-20

nice but how should i flash it without twrp
1.12.2018k i flashed the boot.img in odin and the error can't validate tree table occured.It seems that your modified boot.img does not function,but hey you tried it.

HEROMEROHD said:
nice but how should i flash it without twrp
1.12.2018k i flashed the boot.img in odin and the error can't validate tree table occured.It seems that your modified boot.img does not function,but hey you tried it.
Click to expand...
Click to collapse
do it with twrp

minhka98 said:
do it with twrp
Click to expand...
Click to collapse
It worked with twrp,it seems that odin doesn't flashed it right.Sorry that i blamed your kernel.

I didn't understand so it is galaxy j4 kernel for galaxy j4+ or it is a kernel for both of them??

Hello. Is it for J4+? not J4? It will be appreciated to let me know how to be back stock clock. Then I will try it.

deleted

Exynos 7570
Please, can you develop the same kernel for the Galaxy J4 SM-J400M? It's my model...

kapmino269 said:
Source code link doesn't work , please link.
Click to expand...
Click to collapse
Changed the name.
MOD EDIT: Link removed

kapmino269 said:
Thanks ashyx but which name I should change
and it is exynos and j4+ is snapdragon
And please in addition to
Do you know how to fix ril ?
Click to expand...
Click to collapse
Yeh you're right. Apologies the repository is for the J4.
Looks like the repository was removed for some reason.

So does the kernel remain valid for j4+ if the source is for exynos ?

Geckyn said:
So does the kernel remain valid for j4+ if the source is for exynos ?
Click to expand...
Click to collapse
no, don't flash this kernel on j4+

I need j4+ kernel source code...cant download from samsung opensource keeps failing midway. Any links?

Geckyn said:
I need j4+ kernel source code...cant download from samsung opensource keeps failing midway. Any links?
Click to expand...
Click to collapse
source code of j4+ kernel is probably unavailable, i also need source code because i want try make a oc kernel for this phone

KaroloBC said:
source code of j4+ kernel is probably unavailable, i also need source code because i want try make a oc kernel for this phone
Click to expand...
Click to collapse
Was able to download it finally just keep on trying on the Samsung opensource site

Geckyn said:
Was able to download it finally just keep on trying on the Samsung opensource site
Click to expand...
Click to collapse
you also trying to build custom kernel for j4+?

KaroloBC said:
you also trying to build custom kernel for j4+?
Click to expand...
Click to collapse
Yhhh just for fun and learning....I dont really trust the whole rooting process for this phone so I cant test out my builds...I'm waiting for a more reliable rooting and twrp then I'll test them out.

Geckyn said:
Yhhh just for fun and learning....I dont really trust the whole rooting process for this phone so I cant test out my builds...I'm waiting for a more reliable rooting and twrp then I'll test them out.
Click to expand...
Click to collapse
A more reliable twrp? Please explain.

ashyx said:
A more reliable twrp? Please explain.
Click to expand...
Click to collapse
Flashing one thing after the other....it seems like the least mistake you end up with a bricked device. I'm used to the usual simple methods since this my first Samsung device. Too many securities here and there. Some followed the steps and not having proper root. I'm actually glad you made one for this device actually but it's like its in the risky initial stages

Geckyn said:
Flashing one thing after the other....it seems like the least mistake you end up with a bricked device. I'm used to the usual simple methods since this my first Samsung device. Too many securities here and there. Some followed the steps and not having proper root. I'm actually glad you made one for this device actually but it's like its in the risky initial stages
Click to expand...
Click to collapse
I'm still not sure where you're coming from? It's working just fine as confirmed by many others and so is root.
It's not the fault of twrp, myself or anyone else that there are hurdles to overcome put in place by Samsung.
It's the same for every other recently released Samsung device.
Also its highly unlikely you could brick a Samsung device by simply flashing a custom recovery.