Database Info

Upgrading kernel from 3.0.31 to 3.x (we need team)

i managed to upgrade the kernel to 3.0.33 without errors .. tried to upgrade to 3.0.101 or 3.4 ... i got errors .. and it is to much patches ..and it needs time so here is how to do it ..
we can upgrade our kernel via .. linux kernel patches you can find them here ..
https://www.kernel.org/pub/linux/kernel/v3.x/ linux for kernel .. and patch for patch ..
https://www.kernel.org/pub/linux/kernel/v3.x/incr/ those patch are small steps like from 3.0.31 to 3.0.32 ........
put in the source dir .. cd to source dir apply patch
there is two things reverse patch or patch
patch :
patch -p1 < ../patch-x.y.z
reverse patch :
patch -R -p1 < ../patch-x.y.z
we use reverse to undo to go to the first one like from 3.0.31 to 3.0 .. something like this ..
for more information go to kernel-source-dir/Documentation/applying-patches.txt
Good luck ..devs :good:

nanoteam said:
i managed to upgrade the kernel to 3.0.33 without errors .. tried to upgrade to 3.0.101 or 3.4 ... i got errors .. and it is to much patches ..and it needs time so here is how to do it ..
we can upgrade our kernel via .. linux kernel patches you can find them here ..
https://www.kernel.org/pub/linux/kernel/v3.x/ linux for kernel .. and patch for patch ..
https://www.kernel.org/pub/linux/kernel/v3.x/incr/ those patch are small steps like from 3.0.31 to 3.0.32 ........
put in the source dir .. cd to source dir apply patch
there is two things reverse patch or patch
patch :
patch -p1 < ../patch-x.y.z
reverse patch :
patch -R -p1 < ../patch-x.y.z
we use reverse to undo to go to the first one like from 3.0.31 to 3.0 .. something like this ..
for more information go to kernel-source-dir/Documentation/applying-patches.txt
simple kernel 3.0.33 via Odin.. to test .. wifi doesn't work it needs the new module because of the magic version
Good luck ..devs :good:
Click to expand...
Click to collapse
Did you use the new compiled wifi module ore just boot.img

succesfully upgraded to .101, wifi works.
Move the script I attached to your kernel root directory and execute it to automatically upgrade to .101.
If you get prompted, type "y".
Wow it's much better performance.

oh yehhhhh .. we can upgrade any version we want know ... did you see any perfermance improvement ... or any thing new .....and i think we need to upgrade to 3.4 ...
scripts didn't work for me ./script.sh: line 6: [: : integer expression expected

nanoteam said:
oh yehhhhh .. we can upgrade any version we want know ... did you see any perfermance improvement ... or any thing new .....and i think we need to upgrade to 3.4 ...
scripts didn't work for me ./script.sh: line 6: [: : integer expression expected
Click to expand...
Click to collapse
Oh sorry i will fix. I have the feeling performance is better. In 3.4 are bigger code changes than you think, even if it works there are some bugs. I will to upgrade to 3.4 soon.
Sent from my GT-I9105P using XDA Premium 4 mobile app

try this script
seems like hotplug could be compatible with .101 sources
didn't succeed with upgrading to 3.4..

i know there is big changes to 3.4 .. patche with 44 mg ..uncompressed ...it is a lot .......

nanoteam said:
i know there is big changes to 3.4 .. patche with 44 mg ..uncompressed ...it is a lot .......
Click to expand...
Click to collapse
I tink there is no patch, only the files, wich you can build based on. But I have a really good idea
Sent from my GT-I9105P using XDA Premium 4 mobile app

can you upload 3.0.101 kernel .. i got an error when compiling ... the same with direct patch ... L2cache... upload yours i wanted to try speed ..

nanoteam said:
can you upload 3.0.101 kernel .. i got an error when compiling ... the same with direct patch ... L2cache... upload yours i wanted to try speed ..
Click to expand...
Click to collapse
But it's built for aosp roms
Sent from my GT-I9105P using XDA Premium 4 mobile app

i ment the patched kernel .. 3.0.31 to 3.0.101 .. i patched it and it didn't for me so if u can upload urs ..

nanoteam said:
i ment the patched kernel .. 3.0.31 to 3.0.101 .. i patched it and it didn't for me so if u can upload urs ..
Click to expand...
Click to collapse
yes it's built for aosp roms. If you want try apply this commit https://github.com/CoolDevelopment/VSMC-i9105p/commit/46eef9999dc1a0d3fc58f8271699751d2bccb006 . You can try it on cm with flashing the zip i attached

no .. iment stock source kernel .. i'm testing the patches in the stock source not cm ...

nanoteam said:
no .. iment stock source kernel .. i'm testing the patches in the stock source not cm ...
Click to expand...
Click to collapse
Cm kernel is based on stock kernel with a some very small bug fixes
Sent from my GT-I9105P using XDA Premium 4 mobile app

seems like the compiled kernel wasn't updated, strange. I tried to apply the patches again and i got compilation errors, too. My fault :/

i have succefuly compiled 3.0.33 ... may i will try patches till i find patch that cause this .. good luck

https://android.googlesource.com/kernel/common/+/android-3.4 I think it could be useful
Sent from my GT-I9105P using XDA Premium 4 mobile app

the problem that doesn't include our device drivers like capri and kona ........ we can extract them and add them to the new kernel but we have to modife kconfig and make files it is long work looonnggg ...

nanoteam said:
the problem that doesn't include our device drivers like capri and kona ........ we can extract them and add them to the new kernel but we have to modife kconfig and make files it is long work looonnggg ...
Click to expand...
Click to collapse
I tried to copy the files from the git repo in our kernel sources and overwrite them, but it didn't boot(that's nothing wich wonders me).

I am trying to port 3.4 kernel for s advance and if i succeed i'll try with s2+ too. but it seems a very long work. Just to update from 3.0.31 to 3.0.32 took some time. Btw to apply patches is better to use git apply name-of-patch and if it says that there are conflicts type in git status and it'll show coloured in red the files with conflicts to fix
Sent from my GT-I9070 using xda app-developers app

[DEVS ONLY] CyanogenMod 11 for Samsung BCM21553 Development Discussion

WARNING: App2SD and Mounts2SD are not recommended for use with any OTA-enabled ROMs, as they break delta updates, and may cause problems during full upgrades. I suggest using my modified version of S2E, simple2ext_mod, instead.
NOTE 1: I recommend that everyone uses @Bhargav97's Google Apps package (cm11 v2.2 version or later). Other versions of gapps may cause issues or break delta updates.
NOTE 2: You must ensure that your phone is running the latest baseband available for your region, or else your device will not operate correctly when a SIM card is inserted. If you have a cooperve and tassve, you may need to flash the latest totoro baseband (which will work correctly on your device). Please see @marcussmith2626's stock ROM thread for links to the appropriate files.
Information for users:
This topic is intended only as a meeting point for other developers of the shared BCM21553 devices to discuss and solve issues related to development. If you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Thanks for your understanding.
First-time installation:
ClockworkMod v6.0.5.3 or later (MTD version) is mandatory to install CM11. If needed, download the latest recovery build here
Download the latest full OTA build for totoro from here
If necessary, flash the ClockworkMod v6 build, then reboot into recovery. If you can't flash the CWMv6 update package (.zip) in your existing recovery, use the Odin package (.tar.md5) instead.
Perform a data wipe - this is mandatory if upgrading from an older Android revision
Flash the OTA package and reboot.
How to update (via OTA):
Please consult the cm-ota instructions on Jenkins.
Current issues (06/10/2014)
OMX codecs (for accelerated audio/video - may never be solved)
SIM unlock doesn't work (you must remove your SIM lock in another device/ROM)
Video recorder
Summary of major work done:
Forked broadcomCM devices into androidarmv6 repository (forked from ics branches).
Initial changes needed for cm-11.0 have been committed to cooperve, tassve, totoro and bcm21553-common device trees.
All of Broadcom's code has been adapted for the cm-11.0 branch.
After some reverse engineering of the vendor binaries, "adbd" and "init" built from source now work correctly. ADB will now set the proper USB mode, can give a root shell, and no longer has a hardcoded dependency on /system/bin/sh, which should help a great deal with debugging. We also no longer need to use the init prebuilt binary - the source-built version is now compatible.
Implemented common kernel source for totoro, cooperve and tassve.
Implemented hybrid boot/recovery/charge ramdisk.
Fixed WiFi, Bluetooth, Bluetooth tether & mac addresses.
Fixed graphical performance regression on CM11 branch.
Fixed basic audio (speaker, microphone, software encoders/decoders)
Fixed GPS.
Fixed Gallery, wallpaper chooser, live wallpapers, RenderScript, and possible EGL crashes in other apps
Added workaround for SystemUI corruption
Fixed graphical corruption/stability issues (caused by buggy GL_EXT_discard_framebuffer extension)
Fixed RIL, telephony and audio routing to speakers, headset, earpiece, microphone and microphone mute.
Audio routing improvements/fixes, small graphics performance optimizations
Fixed camera
Fixed wifi tethering
Updated to newer bcmdhd wifi driver to resolve wifi instability
Fixed USB tethering (with caveats)
Improved audio routing and fixed BT headsets (SCO)
* = this code is work in progress, which means that it is not yet available in the OTA build.
XDA:DevDB Information
CyanogenMod 11 for Samsung BCM21553 series, ROM for the Samsung Galaxy Y GT-S5360
Contributors
psyke83
Version Information
Status: Testing
Created 2014-10-27
Last Updated 2014-10-27

I will update cooperve device tree as soon as I can. I guess @Alberto96 could adapt tassve (his device). Lets get some fun here
Enviado desde mi Xperia SP mediante Tapatalk

No problem First I'll try adb/init changes, and then adapt repo.

@psyke83 , I have created some threads regarding development of this BCM21553 devices with the information I was able to get while developing:
HW drivers: http://forum.xda-developers.com/showthread.php?t=2666566
Audio libs (source): http://forum.xda-developers.com/showthread.php?t=2682819
Enviado desde mi Xperia SP mediante Tapatalk

Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
I/DEBUG ( 4743): debuggerd committing suicide to free the zombie!
F/libc ( 4747): Fatal signal 13 (SIGPIPE) at 0x0000128b (code=0)
F/libc ( 4748): Fatal signal 13 (SIGPIPE) at 0x0000128c (code=0)
F/libc ( 4749): Fatal signal 13 (SIGPIPE) at 0x0000128d (code=0)
F/libc ( 4750): Fatal signal 13 (SIGPIPE) at 0x0000128e (code=0)
F/libc ( 4751): Fatal signal 13 (SIGPIPE) at 0x0000128f (code=0)
F/libc ( 4752): Fatal signal 13 (SIGPIPE) at 0x00001290 (code=0)
F/libc ( 4753): Fatal signal 13 (SIGPIPE) at 0x00001291 (code=0)
F/libc ( 4754): Fatal signal 13 (SIGPIPE) at 0x00001292 (code=0)
I adapted almost all, i wasn't able to adapt just property_service.c & property_service.h so recovery/charging mode isn't working yet.
Great job @psyke83 !

Alberto96 said:
Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
Great job @psyke83 !
Click to expand...
Click to collapse
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".

psyke83 said:
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".
Click to expand...
Click to collapse
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk

Good news: I just discovered that surfaceflinger works if I remove the hwcomposer.default library. However, there is some graphical distortion, and the colours are incorrect. Still, it's some progress. Will try to troubleshoot hwcomposer now.

android_native.h similiar with ANativeObjectBase.h without include <android/native_window.h>
updater-script cant run in cwm5 so need modified wanna force try to flash zip package but still not luck for boot coz messy ramdisk code.
temporary cwm6 still black screen so since its not working modified ramdisk is 1st think to do with old cwm5 (in my case) to running dualboot (stock cm) at least to make it boot 1st.
@psyke83 great work and still follow ur update from behind

Alberto96 said:
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Ashutos1997 said:
This means cm11 boots now ?
Click to expand...
Click to collapse
-CALIBAN666- said:
sorry for offtopic,but are you back????
Click to expand...
Click to collapse
There's a general thread for off-topic posts (linked in the first paragraph of my first post)... please use it in future. This thread is supposed to be for developers to collaborate and fix bugs only.

psyke83 said:
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Click to expand...
Click to collapse
No white screen bug here. (i'm using my ramdisk but with source built init/adbd)
It should a bug related to missing backlight permissions:
chown system system /sys/class/backlight/aat1401-backlight/brightness
chown system system /sys/class/backlight/pwm-keypad-backlight.0/brightness
I had this bug when i've removed these lines

@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.

psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
I will push cooperve kernel source this afternoon. Thanks for your work done, really appreciate. I hope I can upload tassve too, if Alberto dont mind. I will base it though on your tototo config, but on cooperve. As far as I know, cooperve need changes on its modules to get the kernel work good, as it have a different canera driver (updated one for 5 MP and flash)
Enviat des del meu Xperia SP usant Tapatalk

Kernel config source for cooperve has been updated. I'll push it gerrit as soon as I get home. I've updated on school, and I don't have the config of the server there. @psyke83 if you can take a look at it, I've made a pastebin, you can push to gerrit directly if you are OK with it, or make any changes you think are necessary:
http://pastebin.com/Svir6qtZ

psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
You can find my defconfig on github. It's updated.
https://github.com/Alberto96/androi...arch/arm/configs/cyanogenmod_tassve_defconfig
Sent from my GT-I9500 using Tapatalk

Thread cleaned. Please respect the dev's wish and do not post non development posts in this section

@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.

Alberto96 said:
@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.
Click to expand...
Click to collapse
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.

psyke83 said:
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.
Click to expand...
Click to collapse
Maybe I'll try something next week. I need to update first some stuff for another device (gt-i9500, samsung finally released 4.4.2 sources for it).
Sent from my GT-I9500 using Tapatalk

Alberto,
I'm up and running with ICS now. Performance is very good and I don't see graphics corruption, but it is unstable. I believe it's the same issue with bmem allocation that the alcatel code fixes.
Anyway, I'm about to test the built-in gememalloc, but something else that you can try is to disable loading of all modules in system/lib/modules with the regular kernel (no gememalloc built-in). I just tried it here on ICS, and I see absolutely no difference in graphics performance with or without the modules loaded. I suspect those modules are used for other things, possibly related to video decoding.

[KERNEL][3.10 PORTING][DEVS ONLY][S4][VILLE]

FOR DEVS ONLY
THIS IS A DEVELOPMENT THREAD FOR PORTING THE LINUX 3.10 KERNEL TO THE HTC ONE S (VILLE) S4 EDITION
MODERATORS PLEASE DELETE ANY POSTS THAT ARE NOT RELATED TO THE DEVELOPMENT OF THE KERNEL (OTHER THAN THESE FIRST POSTS USED TO CREATE SOME DOCUMENTATION)
XDA:DevDB Information
3.10 Kernel for the HTC One S, Kernel for the HTC One S
Contributors
javelinanddart
Kernel Special Features:
Version Information
Status: Testing
Created 2015-01-15
Last Updated 2015-01-15

This thread is a development thread for porting the Linux 3.10 Kernel to the HTC One S
All Devs are welcome to step forward
https://github.com/javelinanddart/android_kernel_3.10_ville
This will be done from the CM 12 Source Code
This IS NOT an easy task, it will take a lot of time and lot of things will need to be changed
CyanogenMod might have to be rebuilt from source to have this work properly
Look at the mergeconflicts.txt to look for things to fix, look at the fixedconflicts.txt for things that are fixed

Advantages:
-Officially Supported (3.10 is what the Nexus 6 & 9 and Android Wear Devices are Using)
-Future Android Compatibility (Android Framework and Kernel are Decoupled but Still Matters)
-Better Performance (Somewhat)
-Bragging Rights (xD this is a joke)
-Better and Newer Drivers
-More Features
-More Optimized
-Longer Support Date (Most Likely)
-Most Future Devices will Run 3.10 Kernel (Keeps our Device Current)
-Lower RAM Usage
-Support for F2FS (a faster file system for nand flash storage devices)

Contributor List
@intervigil (Ethan Chen)
@AKToronto
@mikronac.ns (Mikronac)

FAQ
Why?
Because I can (lol)
Check the Advantages list

Changelog
Initial Upload of Source
Merge tag v3.10

Resources
http://elinux.org/Kernel_3.4_to_3.10_porting_guide

A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product

javelinanddart said:
A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product
Click to expand...
Click to collapse
yeah, I am just looking in it...

mikronac.ns said:
yeah, I am just looking in it...
Click to expand...
Click to collapse
1 sec then, I'm merging with the aosp source rather than mainline linux because it includes some android specific changes
Look at the mergeconflicts.txt or try compiling it.....
My god... never seen THAT many errors in the Kconfigs

wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware

dd98 said:
wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware
Click to expand...
Click to collapse
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too

javelinanddart said:
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too
Click to expand...
Click to collapse
I'll gladly help but still only getting there on the kernel development, hope I have some free time

dd98 said:
I'll gladly help but still only getting there on the kernel development, hope I have some free time
Click to expand...
Click to collapse
What's your github username? I'll add you as a collaborator rather than pull requests. It works faster

@javelinanddart F2Fs already works on Ville I already ported it [emoji1]

Flashalot said:
@javelinanddart F2Fs already works on Ville I already ported it [emoji1]
Click to expand...
Click to collapse
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?

javelinanddart said:
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?
Click to expand...
Click to collapse
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp

Flashalot said:
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp
Click to expand...
Click to collapse
Thanks. If we can switch to F2FS and use a Universal TWRP, developers will have a better time on source-based ROMs. It will also help speed up the file system actions. I tried compiling twrp but I couldn't figure it out

What source are you editing the 3.4 kernel source or the 3.10 kernel source ?

Wahaj.47 said:
What source are you editing the 3.4 kernel source or the 3.10 kernel source ?
Click to expand...
Click to collapse
"3.10 porting"

[KERNEL][SOON] HakyKernel 3.1.2

Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.

haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?

rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:

thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone

SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app

haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?

cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.

haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up

[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.

Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu

Man, you do a lot of great work.

thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..

left it open haky..maybe they are busy for now..we need it bro

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work

why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others

3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.

3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance

haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...

no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.

[KERNEL] [MTD] [TW/CM9/CM11] [DEV] Watson Kernel (MTD support on Gingerbread!)

Hello guys,
This is a project I was working on for a kernel for our SGY.
I made it with a few things in mind:
>Improve it's performance
>Be universally compatible (after I nearly given up on trying to get a snappier CM11 and after the need for a snappier SGY, I decided to go back to GB. However, BML is terrible, and it is annoying to come back to. I decided to build a MTD kernel for Gingerbread then, and it works!)
>Experiment and upgrade as much as I can (thanks @robcore!!!!)
But since I lost my device, I cannot continue developing it. I am then releasing the source code (sorry, no flashable stuff, I deleted it long ago ) for any of you to continue(?) my work if your heart so desires.
If I ever get myself another SGY (or another BCM21553 device), I will gladly continue development (and support whoever does it too), but before I lose all my data and the kernel code alongside it, I am making it available.
This kernel features:
-OC up to 1040MHz (It's questionable even today if the bcm21553 OCs really work, but I tried hacking a way that works very similarly to MarocOS's one, maybe even better. Be warned though, the source around it is messy)
-GPU hacks for performance (Again, even I don't know if they do work, probably the values are just there to be seen, I'm not sure. I do know though that increasing the CPU speed will much likely increase the speed of V3D too)
-DVFS disabled (I found out DVFS is mostly the culpirit in the "832MHz crisis" where the kernel would forcefully scale itself to 832MHz, so I eliminated any reference to it in kernel code. Apparently DVFS on the processor is only available under the bcm21553 governor, but it is present on the other drivers as well. The idea for disabling DVFS came from my friend @robcore)
-A few additional governors and a buggy interactive governor (which is the default xd)
-MTD support for Gingerbread (Thanks Samsung Epic 4G! Although it only works on TouchWiz (I tried it with SL v2 and v2.1 and it works, but under NougatME(CM7) I got no success and loads of segfaults), it works ALMOST perfectly. See bugs for details )
-Some scraped source code from Samsung's FSR I found on the internet (barely compilable, though)
Bugs:
>Gingerbread version:
-IMEI won't appear in the Status screen, I also faced problems with non-working radio for calls. Data works just fine, but calling and receiving calls is unavailable. I believe it is EFS-related. My suggestion is backing up the EFS partition's file structure, then converting it to MTD, then restoring the backup.
-TWRP will crash and panic when exiting, a workaround is force rebooting
>ICS version:
-TWRP will crash and panic when exiting (I believe fixing it here will fix the bug above too)
>KitKat version:
-Flashing images fail randomly, you may also be unable to reboot normally if you do so. I tried addressing this but I couldn't get anywhere.
DOWNLOAD THE SOURCE: Here!
Thanks to:
 @robcore - his development on the Snapdragon S4 breathes life on my dev soul!
 @zman0900 - I saw his thread on an MTD TW kernel for the Samsung Epic 4G, which led me to believe MTD on GB is possible.

nice kernel
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source

vdhero said:
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source
Click to expand...
Click to collapse
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you

Building and fixing
sonickles9 said:
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you
Click to expand...
Click to collapse
I don't sure so I decided to build a kernel from your source and another cm9 version from Mohamad.Afaneh's source and I'll merge the audio on both of them for the best think to fix the bug.Thank you .

Link for kernel?
(img files...)(stock/cm9/cm11)

TheRealModder said:
Link for kernel?
(img files...)(stock/cm9/cm11)
Click to expand...
Click to collapse
Compile one for yourself,man. It only takes like 15-25 mins

vdhero said:
Compile one for yourself,man. It only takes like 15-25 mins
Click to expand...
Click to collapse
I don't know how to compile....

TheRealModder said:
I don't know how to compile....
Click to expand...
Click to collapse
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme

vdhero said:
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme
Click to expand...
Click to collapse
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version

TheRealModder said:
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version
Click to expand...
Click to collapse
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source

Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Click to expand...
Click to collapse
zlimage? We don't have that here, we only have boot.img for kernel

vdhero said:
zlimage? We don't have that here, we only have boot.img for kernel
Click to expand...
Click to collapse
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs
Click to expand...
Click to collapse
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed

vdhero said:
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed
Click to expand...
Click to collapse
Ok. If you want to install linux i recommend using ubuntu or linux mint.
Ubuntu official website:https://www.ubuntu.com/
Linux mint official website:https://linuxmint.com/
Sent from my Zenfone 2 Laser using XDA Labs

VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
vdhero said:
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source
Click to expand...
Click to collapse
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!

Assabtigle said:
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
Click to expand...
Click to collapse
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible

Be fast bro!!
vdhero said:
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible
Click to expand...
Click to collapse
BE fast BRO Love U and Your WORK!!
All Your DEVELOPMENT are Faster than The ORIGINAL one Please Buy a NEW one!
and Yeah install the Stock Rom in your Phone by ODIN it will be fine!:laugh: