Related
Hello Comm. and Devs,
For our Archos there are now many custom rom-images and experimental distris of linux and so on and every "rom" has its own kernel and init which have to be flashed and it seems it is only possible to have one kernel and one init.
I want to test as many roms, plasma, ics alpha, ubuntu, 3.2.80 with busybox and adobe, etc. for shorter or for everytime. And when Archos brings ICS finally i want to upgrade of course, without losing apps and settings etc.
Now i am on rooted 3.2.79 with chainfire 3d and i dont know if it makes senes to upgrade to 3.2.80 custom rom from surdu. Okay, vibrator and so on and some goodies, sounds nice, therefore i want to test and perhaps revert it later.
Which roms are compatibel with each other and which not?
Which rom is how much recommend?
What are the differences between these inits (kernel seems often to be the same seen by its size i think) - is there the possibility and the evidence to merge the inits somehow?
Or is there a kind of general initramfs one could take for most roms?
What rom has which kernel in which version and same for initfs?
What are there for possibilities that every image gets it adequate kernel and initfs?
Many of us want multi boot which i think is not really (?) supported for gen9 .
What should be done for compatibility if i want a kind of multiboot?
It would be nice if this would give a set of infos for us all.
Well, no, kernels are not the same. We're not 100% sure for Archos ones, they're currently closed source, but looking at what they fixed in the different releases, I believe there have been changes. Plasma is definitely using a different kernel, ics will require a completely new 3.0 kernel and probably require clear data.
So what you're looking for is not really possible, not matching kernel with firmware is not a good idea. The only exception would be Ubuntu, but that's it.
what about multi-boot menu from open aos?
There are roumors that people have it work but it is not supported.
Dont want to mess all up.
Do you know something or have experiences?
svennimann said:
what about multi-boot menu from open aos?
There are roumors that people have it work but it is not supported.
Dont want to mess all up.
Do you know something or have experiences?
Click to expand...
Click to collapse
Sorry - about this with multiboot i see there is already a thread.
-- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED --
Please follow this link to the new thread for the Semaphore Kernel for the I9000B, now maintained by rubervalrfl. This thread and builds herein are now deprecated and kept here for historical purposes only. Thanks for your support!
-- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED --
----
This is stratosk's Semaphore JB kernel compiled for the GT-I9000B (Latin america variant of the I9000). Stratosk doesn't support this variant, and being an owner of this device, I thought I'd share my efforts on compiling his excellent kernel for the I9000B variant.
With that said, here comes the disclaimer: By flashing this kernel, you accept that it comes without any support, neither mine and even less so from stratosk, since he doesn't support this variant on his own releases. So please don't bother him with support questions regarding this specific build. IOW: you'll use this kernel at your own risk.
There were reports of data loss during testing on early builds of the 2.8.x (kernel for Android 4.2) series - there were no more bad reports on later versions, but this needs to be said: Always do a nandroid backup before installing or updating any of the kernels posted here. I won't be held responsible if you lose data while using these kernels!
I *may* be able to help depending on whatever problems you might have, but don't expect timely answers, or any answers at all if I'm not technically able to figure out your problem - I'm a beginner on kernel development, all I did with this really was just some slight tunings and then recompile it for the I9000B. Also, I'm doing this on my free time, which is not much these days, so for now I'm just going to focus on following stratosk builds and recompile them for the I9000B as they come. I can say though, as far as problems, I don't have any with it on my device - it works fine and fast for me, at least the builds prior to 2.8.x, i.e.: kernels for Android 4.1 - I don't use Android 4.2 (yet) and hence I haven't / don't test the 2.8.+ builds myself - I rely on rubervalrfl's report for this; if the kernel boots without problems or data loss for him, then I deem it stable enough for release. Hence the glaring warning above about backups.
Now, on to the goodness:
This kernel is exactly the same as stratosk builds (hence, the exact same features and changelogs, including compiler versions and configuration), but with the following modifications:
Swap enabled;
ZRAM enabled as module (To configure it (on CM10), go into Settings / Performance / Memory Management);
KSM support enabled (Disabled on system by default, to enable it (on CM10), go into Settings / Performance / Memory Management)
Note about build version 2.7.0
Stratosk is no longer maintaining the 2.6.x builds that are meant for Android 4.1. But I was using Android 4.1 before I sold my SGS (yeah, I'll soon be retiring from compiling this kernel, read recent posts on this thread for more information), and looking at some of the latest 2.9.0 features I felt like having some of its features on the 2.6.x builds, and so I did it. Those features are really just some cherry-picks from Stratosk's 2.9.0 branch on his repository, so all credits to him, as always. Since there are quite some important changes I thought it would be better to bump the version number to 2.7.0 - I suppose it shouldn't be a problem to anyone, since the original 2.6.x builds are no longer maintained anyway, and it still sets it apart from the newer 2.8/2.9 builds. The 2.7.0 build contains the following cherry-picks from 2.9.0:
Reduce number of frame buffers for more RAM (on my ex-SGS I'm now at 383Mb, up from 377Mb);
Updated Interactive governor;
ROW I/O Scheduler
Known issues
The kernels posted here are compiled exclusively with BLN support, whereas stratosk's put out a 2.6.5 version with CM LED support. I haven't built versions with CM LED support because they simply didn't work on my own testing - the LEDs wouldn't light up at all with it, which effectively broke LED notification for the I9000B. Because of that my builds are compiled exclusively with BLN, which at least lights up the LEDs for notifications.
Blinking LEDs with BLN doesn't work (?) - they just keep alight: I'm still not sure why, although I suspect it may be something specific to my own phone because it doesn't work on DerTeufel's Hellybean kernel either. Feedback is welcome on this (let me know if it does in fact work for you). I've read in a few places that that's how it's actually supposed to work (blinking only actually works with the BLN Control App, "Pro" version), but I'm still not sure, so PLEASE DO GIVE A LITTLE FEEDBACK, PEOPLE!
What works
Everything else, as far as I could see.
Usage
Just flash it on CWM like any other kernel. Normal version and 's' version are provided just like on stratosk's release. Use the Semaphore Manager app on Google Play, from stratosk, to setup the kernel features.
All instructions and documentation from stratosk's original Semaphore kernel applies to this one, so look into his own thread for more information.
Source
Github repository
Thanks
To stratosk, of course, for his awesome work on his kernel, and for letting me post this here for I9000-B users;
Everyone who is/was involved on the development of the Semaphore kernel - basically, anyone on stratosk's "thanks" list
rubervalrfl, for testing the 2.8.0 version. If you want a 4.2 ROM for the I9000B to go with the 2.8.+ kernels, check out his CM10.1 Preview for the I9000B over here.
I'm sooooooo happy
Work on 4.2?
I don't think so.
I think just devil works on it
Dimabr10 said:
Work on 4.2?
Click to expand...
Click to collapse
I haven't tested, so feel free to. If stratosk's release works on it, then this most likely will too. I'm not a "bleeding-edge" kind of guy, though - I've upgraded to CM10 only a couple weeks ago (from CM7), and I see many other kernels don't yet work with 4.2, and if the other kernel devs around here are anything like me, they're probably not going to bother getting their kernels working on 4.2 until CM10.1 gets out of alpha status, since most kernels around here are derived or use parts of the CM kernel, and CM is the most popular Android anyway.
Thanks for this, cronot.
I'm happy that I9000B users can have Semaphore kernel.
Although, I can't official support I9000B, due to lack of free time, I'll do my best for any help.
stratosk said:
Thanks for this, cronot.
I'm happy that I9000B users can have Semaphore kernel.
Although, I can't official support I9000B, due to lack of free time, I'll do my best for any help.
Click to expand...
Click to collapse
Thanks for your support, Stratos
I still hope your help isn't needed specifically with my build, though. You've already got your hands full with your own releases Apart from the Known Issues list on the OP, I have no problems at all with your kernel, it's working really nice! The only problem I would report for 2.6.0 is something that's mentioned here in your thread (hence, not something specific to my build), about some stuttering during video recording - I do have some of those too (although when the record is played back, there's no stutter, so I figure the problem is only in preview), but I'm not sure if this problem started on 2.6.0 or if I had it before and didn't notice - I'd have to rollback to 2.5.0 and take a look, but then I'd have to rebuild that version also since I've deleted the previous version, and I can't spare the time to do it right now; I'll post back on your thread once I can confirm this.
Thanks! , i will install it to give feedback
My congratulations, sent a mp for you.
Nice to see new kernels around here! thanks!! .
This kernel is awesome! The best I've tested in my i9000b !!!
Any chance of a version designed for Android 4.2 ?
wanna know if us is gonna get semaphone for 4.2
@Gurx & @Dimabr10:
Check the OP.
Thanks! We're here to help! Take a look at my website for a fresh version updated for I9000B.
@cronot thanks!!!
I'll test this kernel with some 4.2 version.. Maybe the one from @rubervalrfl !! But I only can do that at night, I'm at my work now....
Thanks!
i'll be glad in receive feedback for my port ROM for i9000B on site.
There is a updated from 12/03/12 cyano's repo version there.
OMG thanks alot
Thanks for your hard work in owr i9000b I would be glad if you can take a look why the mic on the wired headset doesnt work only in owr i9000b :/. Thanks soo much
dancris said:
Thanks for your hard work in owr i9000b I would be glad if you can take a look why the mic on the wired headset doesnt work only in owr i9000b :/. Thanks soo much
Click to expand...
Click to collapse
I am now without the microphone, but once you get home, you can pass a test and feedback, ok?
The wired mic doesnt work on calls or programs. I dont know if the problem have to be solve in the kernel or in rom:/. Hope you can help xD. Thanks.
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
@eousphoros is working on porting CM right now. Why don't you PM him and see if you can put your heads together on it?
jasonfxp said:
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
Click to expand...
Click to collapse
The big problem I ran into is with gralloc/hwcomposer. The hwcomposer that ships with the device is 1.3 whereas the opensource is currently only 1.1. While the initial thought of just copying gralloc.exynos5.so hwcomposer.exynos5.so as propertietary blobs seems like it a good one, they are unfortunately linked to a ton of libraries in /system/lib that makes bringing them over troublesome at best. Though that being said that is the hack I used to get my one and only bootable rom up and running.
Going further the issue with the exynoshwc 1.1 that I have been fighting with is after opening up /dev/graphics/fb0 it trys to send it an ioctl that I assume is the S3C_WIN_CONFIG pointer and gets an ENOTTY back from the device. If you are interested in helping out please checkout the cyanogenmod porting thread in general where I have linked my local_manifests.xml with my git repo's and a blog of my progress.
Cheers.
EDIT: Has anyone ever requested source from samsung? What seems to be the most succesfull method?
http://www.droidforums.net/threads/...al&utm_source=twitter.com&utm_campaign=buffer
I'm at work so can't test
I searched through /sys/devices and there doesn't appear to be any kernel interfaces for "wake_gesture". Will probably require a custom kernel.
agentdr8 said:
I searched through /sys/devices and there doesn't appear to be any kernel interfaces for "wake_gesture". Will probably require a custom kernel.
Click to expand...
Click to collapse
This was my conclusion as well. However, I *think* the same Synaptics touch interface is used for both devices? Or at least a variant. So perhaps it is just a matter of configuring the kernel module correctly? I haven't tinkered directly with kernels for Android devices myself
http://www.synaptics.com/en/press-releases/google-nexus.php
Edit: more hunting, found this commit to angler (6P) kernel to enable dt2w: https://github.com/flar2/angler/commit/a58e4a277bf62a8366561192b25677e2043dd722 . May be relevant for bullhead, not sure if touchscreens are there same and therefore have the same sensors and events.
It might be something @flar2 can add to a future release of the EX kernel.
hi guys
i finally was able to make a custom kernel with permissive selinux
it seems that my previous roms were having some missing files thats why the kernel did not function well with them
anyway, now it is working properly and so far no problems
i already included the V1 in my rom
so i made a different thread so that it will not be confusing
changelog:
V1: initial release
permissive selinux
V2: 06/02/2016
added init.d support
links to the kernel
mediafire
http://www.mediafire.com/download/l6cuhlevy799l8g/Teflanzy_Kernel_P905XXUABOL2_V2.zip
google drive
https://drive.google.com/file/d/0B_-JMtGLOAd3LU9pRS1iUXhKdGc/view?usp=sharing
MD5 checksum: E958AAD584A25FFB395249CDF8A7D116
kernel source on github
https://github.com/Teflanzy/viennalte_p905_kernel_source
kernel ramdisk with init.d support on github
https://github.com/Teflanzy/viennalte_p905_kernel_ramdisk
use this program from @osm0sis for create boot.img from ramdisk and zimage
http://forum.xda-developers.com/showthread.php?t=2073775
please report back with any problems you are facing
Glad to be the first to thank you for your great job @Teflanzy ?
Really happy to see the P905 getting the attention it deserves!
ADM!RAL said:
Glad to be the first to thank you for your great job @Teflanzy
Really happy to see the P905 getting the attention it deserves!
Click to expand...
Click to collapse
thanks for your reply
but do not expect much from me
I am just a beginner and wanted a permissive kernel for my device
I will try to add more features but it might take a long time for me to apply them
Teflanzy said:
thanks for your reply
but do not expect much from me [emoji14]
I am just a beginner and wanted a permissive kernel for my device
I will try to add more features but it might take a long time for me to apply them
Click to expand...
Click to collapse
Great things don't have to be big and bulky bro [emoji4]
I made a post when i first bought the device asked how to make rom deodexed so xposed could be installed and how hard is the process!!
What I'm trying to say is we just wanted the simplest of things [ofc i don't mean it's easy but things that are straight to the point]
Your kernel is just doing that [emoji111]
Opens the door to further mods!
Best of luck bro [emoji106]
Thank you very much for your work, I'll try.
Hello. First, I wanted to thank you for a job well done!
I am using the kernel for something like one and half a month with KOKO ROM and it is *stable*. And I mean stable as hell! - I don't remember even a single random reboot so far! Of course, switching selinux mode with setenforce command is working like a charm, as well as init.d support. Great, great job!
I personally find P905 (and probably other qcom-based variants) *still* the best tablet on the market so far (in my opinion, ofc ).
I am also really *not* interested in custom CM13 developement as stock ROMs has far more Sammy's specific features like *stable* MultiWindow support or S-Pen stuff and even if it is a good experience, I still find using it a waste of device's potential...
That is why I was personally thinking about adding some most popular custom features, like smartmax governor (which I personally find the best option for Snapdragon 800 devices, but opinions may vary ofc...), some custom hotplug driver (MPDecision sucks...) and first of all - enabling CPU overclock/undervolt (I find default maximum horsepower a little too short for handling more advanced tasks on this awesome but resource-hungry QHD screen; also battery-life is not as awesome as it was two years ago...).
So, I wanted to ask you if you are considering further developement of this stock-based kernel?
Also, if you don't have time/will/attitude to continue this great job, I wanted to ask if you have released any sources on github or something which one may sync and continue the developement?
Thank you in advance for the answer.
Best regards.
esgie said:
Hello. First, I wanted to thank you for a job well done!
I am using the kernel for something like one and half a month with KOKO ROM and it is *stable*. And I mean stable as hell! - I don't remember even a single random reboot so far! Of course, switching selinux mode with setenforce command is working like a charm, as well as init.d support. Great, great job!
I personally find P905 (and probably other qcom-based variants) *still* the best tablet on the market so far (in my opinion, ofc ).
I am also really *not* interested in custom CM13 developement as stock ROMs has far more Sammy's specific features like *stable* MultiWindow support or S-Pen stuff and even if it is a good experience, I still find using it a waste of device's potential...
That is why I was personally thinking about adding some most popular custom features, like smartmax governor (which I personally find the best option for Snapdragon 800 devices, but opinions may vary ofc...), some custom hotplug driver (MPDecision sucks...) and first of all - enabling CPU overclock/undervolt (I find default maximum horsepower a little too short for handling more advanced tasks on this awesome but resource-hungry QHD screen; also battery-life is not as awesome as it was two years ago...).
So, I wanted to ask you if you are considering further developement of this stock-based kernel?
Also, if you don't have time/will/attitude to continue this great job, I wanted to ask if you have released any sources on github or something which one may sync and continue the developement?
Thank you in advance for the answer.
Best regards.
Click to expand...
Click to collapse
Thanks for your words
As i said before
I am a beginner so i do not know how to add the features like other governors or enabling volt control
Furthermore i deleted my source but i can remake it because there are small changes that i made and i remember them
I am currently trying to port features from other snapdragon 800 devices kernels like note 3 and note 10.1 2014 edition
But i still get error on compiling
I will prepare the github source then post a link for it
@esgie
i just uploaded the kernel source with ramdisk each in seperate link
hope it is useful to you
i need help with adding synapse support to the kernel
if you know how to do let me know
Thank you.
I have just configured my developement environment.
I will try to proceed with compilation this weekend. I will also check how to implement synapse support
Hear you soon.
Hi.
I want you to know that I am absolute kernel-beginner, too.
Anyway, I have managed to add some basic features to the kernel.
Here you can download img file and test:
https://drive.google.com/folderview?id=0B2TnsPjj6dl4dHNZN3dBb3o1Zlk&usp=sharing
(as of TWRP 3 img files can be flashed directly to boot partition from recovery; P905 only!!!).
Features:
- setenforce working + init.d support (by Teflanzy)
- some custom schedulers (bfq, fiops, sio)
- custom governor (zzmoove with hotplugging support - I recommend to tune it with Kernel Adiutor using profile_number = 5, disable_hotplug = 0 and disabling mpdecision).
So not much at the moment.
It looks like it's hard to automatically cherry-pick a lot of interesting CM12-compatibile commits, as the samsung kernel source differs a lot from the CM one... I failed to add synapse support as for now but I am looking into the issue. Also, I will post and sync my sources not later than tomorrow.
Sorry, my time is limited and experience is not very big.
I am posting a test version here and if there will be enough feedback we may think about creating a separate topic and try to start some constant developement
Sources:
https://github.com/esgie/viennalte_p905_kernel_source
esgie said:
Hi.
I want you to know that I am absolute kernel-beginner, too.
Anyway, I have managed to add some basic features to the kernel.
Here you can download img file and test:
https://drive.google.com/folderview?id=0B2TnsPjj6dl4dHNZN3dBb3o1Zlk&usp=sharing
(as of TWRP 3 img files can be flashed directly to boot partition from recovery; P905 only!!!).
Features:
- setenforce working + init.d support (by Teflanzy)
- some custom schedulers (bfq, fiops, sio)
- custom governor (zzmoove with hotplugging support - I recommend to tune it with Kernel Adiutor using profile_number = 5, disable_hotplug = 0 and disabling mpdecision).
So not much at the moment.
It looks like it's hard to automatically cherry-pick a lot of interesting CM12-compatibile commits, as the samsung kernel source differs a lot from the CM one... I failed to add synapse support as for now but I am looking into the issue. Also, I will post and sync my sources not later than tomorrow.
Sorry, my time is limited and experience is not very big.
I am posting a test version here and if there will be enough feedback we may think about creating a separate topic and try to start some constant developement
Sources:
https://github.com/esgie/viennalte_p905_kernel_source
Click to expand...
Click to collapse
nice work
now I can check your commits and understand how to add extra governors
gonna download your version and test and report back after usage for a couple of days