Develop Bugs

[Kernel](007) N1 (KK444) CM(UV/Sound/intelliactive/Hybrid Linux 3.4+)[Aug-02] - Oppo N1

Here it is:
CM Kitkat 4.4.4 Change Log:
http://faux.romhost.me/n1/kk44/changelog.txt
Cyanogenmod Edition Kernel: Compatible with CM 11 ROMs
http://faux.romhost.me/n1/kk44/
Betas:
http://faux.romhost.me/n1/beta/
CWM Installable:
Instructions: (Pre-requisite: CWM recovery or equivalent)
1) Reboot to Recovery
2) Select "install zip from sdcard"
3) Choose zip from sdcard
4) select n1-kk-kernel-xxx.zip
5) select yes
after flash
select reboot system... DONE!
GPL compliant source:
Kitkat 444 source: https://github.com/faux123/android_kernel_oppo_n1
Video Review of FauxClock by hackarchive!

reserved 1

reserved 2

reserved 3

can i install it with twrp
faux123 said:
Here it is:
CM Kitkat 4.4.2 Change Log:
http://faux.romhost.me/n1/kk44/changelog.txt
Cyanogenmod Edition Kernel: Compatible with CM 11 ROMs
http://faux.romhost.me/n1/kk44/
Betas:
http://faux.romhost.me/n1/beta/
CWM Installable:
Instructions: (Pre-requisite: CWM recovery or equivalent)
1) Reboot to Recovery
2) Select "install zip from sdcard"
3) Choose zip from sdcard
4) select n1-kk-kernel-xxx.zip
5) select yes
after flash
select reboot system... DONE!
GPL compliant source:
Kitkat 442 source: https://github.com/faux123/android_kernel_oppo_n1
Video Review of FauxClock by hackarchive!
[/QUOTE
I am on twrp recovery and omnirom... Can i flash it? Thanks for the kernel
Click to expand...
Click to collapse

giuliano rigon said:
faux123 said:
Here it is:
CM Kitkat 4.4.2 Change Log:
http://faux.romhost.me/n1/kk44/changelog.txt
Cyanogenmod Edition Kernel: Compatible with CM 11 ROMs
http://faux.romhost.me/n1/kk44/
Betas:
http://faux.romhost.me/n1/beta/
CWM Installable:
Instructions: (Pre-requisite: CWM recovery or equivalent)
1) Reboot to Recovery
2) Select "install zip from sdcard"
3) Choose zip from sdcard
4) select n1-kk-kernel-xxx.zip
5) select yes
after flash
select reboot system... DONE!
GPL compliant source:
Kitkat 442 source: https://github.com/faux123/android_kernel_oppo_n1
Video Review of FauxClock by hackarchive!
[/QUOTE
I am on twrp recovery and omnirom... Can i flash it? Thanks for the kernel
Click to expand...
Click to collapse
I've only tested with CM 11.. so I can't say if other alternatives would work or not.
Click to expand...
Click to collapse

faux123 said:
giuliano rigon said:
I've only tested with CM 11.. so I can't say if other alternatives would work or not.
Click to expand...
Click to collapse
OK.. I will try it with cm11 but would you flash it with twrp recovery? I would flash cm 11 set up reboot to twrp recovery and flash your kernel .. Or is cwm recovery necessary? Thanks for your time
Click to expand...
Click to collapse

giuliano rigon said:
faux123 said:
OK.. I will try it with cm11 but would you flash it with twrp recovery? I would flash cm 11 set up reboot to twrp recovery and flash your kernel .. Or is cwm recovery necessary? Thanks for your time
Click to expand...
Click to collapse
Either recovery should work
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse

faux kernel fails on omni and codefireX

_r2 version is out. Updated cm ramdisk for compatibility. No source changed.
Sent from my One X using Tapatalk

faux123 said:
_r2 version is out. Updated cm ramdisk for compatibility. No source changed.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
So r1 did not work on omni ROM or codefirex.. No news on aokp.. Do you think release 2 is more compatibile or should we stick with cm11 thanks giuliano rigon

giuliano rigon said:
So r1 did not work on omni ROM or codefirex.. No news on aokp.. Do you think release 2 is more compatibile or should we stick with cm11 thanks giuliano rigon
Click to expand...
Click to collapse
I DON'T HAVE this device. I released this kernel because CM has unified the kernel source for N1 and Find5. So this kernel is effectively free as result of it. The support will be very minimal for this kernel.

faux123 said:
I DON'T HAVE this device. I released this kernel because CM has unified the kernel source for N1 and Find5. So this kernel is effectively free as result of it. The support will be very minimal for this kernel.
Click to expand...
Click to collapse
It seems like the n1 panel and the gamma/temperature changes, doesn't work well together. Makes weird colors on screen, like out of no where a part if the screen is more blue, and sometimes it turns all colors very bad. Everytime it needs a hard reboot to get it rolling. Just a note for you
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
It seems like the n1 panel and the gamma/temperature changes, doesn't work well together. Makes weird colors on screen, like out of no where a part if the screen is more blue, and sometimes it turns all colors very bad. Everytime it needs a hard reboot to get it rolling. Just a note for you
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the feedback. There's no way for me to troubleshoot this said issue at all. I don't have this device.
Sent from my XT1053 using Tapatalk

faux123 said:
Thanks for the feedback. There's no way for me to troubleshoot this said issue at all. I don't have this device.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
No I know and kmsg or logcat says nothing bad when it happens.
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
No I know and kmsg or logcat says nothing bad when it happens.
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
kernel FB/GPU drivers are identical to find5, the only difference are in the actual mipi drivers specific to N1''s display. But without device in hand, it is impossible to debug (even with logs and such).

faux123 said:
kernel FB/GPU drivers are identical to find5, the only difference are in the actual mipi drivers specific to N1''s display. But without device in hand, it is impossible to debug (even with logs and such).
Click to expand...
Click to collapse
Yes I know doing android in blind ain't easy
Sent from my Find 5 using XDA Premium HD app

kernel 002u is out!
details here:
https://plus.google.com/u/0/109078966818501160423/posts/5GP7DrnW8Gc
Enjoy!

Could someone give me the default governor settings for intelliactive please?
I'm getting random stuttering while playing back youtube HD video from the app, only while using this gov, and I'd like to put back in the default settings through trickster, but don't know where to find the default values
Screen cap works just fine :good:

yeah i try right now

Related

Information​This kernel is forked from the CyanogenMod Kernel and i have added a few additional changes of my own and more to come. My builds of AOKP and Gummy have this kernel pre-installed with the Kanged Gummy Kernel but when i release 1.0 it will have a few more tweaks so you would need to upgrade.
There will be 4 files you can download. The boot.img and zImage can both be flashed using Heimdall. The Flashable zip and Odin tar.
Bugs​
Deep Sleep works but when using LiveOC it does not so i recommend only using this when playing games or maybe make a script to disable this when you device locks in the time being.
Differences​
LiveOC
More Frequencies (100MHz, 200MHz, 400MHz, 600MHz, 700MHz, 800MHz, 900MHz, 1000MHz, 1100MHz, 1200MHz, 1300MHz, 1400MHz)
Lulzactive v2 Governor (My preferred choice)
Tiny shmem
Working on more!
Using Features In The Kernel​LiveOC​Here is information on it This is configurable using a tool known as NSTools on the PlayStore. When using this 100% means the bus frequency is at 100% try not to get confused. So 100% of 100MHz would be 100MHz so if you increase it to 120% so it would be 120% of 100MHz would be 120MHz and this value applies to all CPU frequencies, GPU ect.
Lulactive​This is like other governors for the CPU and can be configured using applications like Voltage Control, SetCPU, NSToolsand built-in tools from CM9/10 and AOKP ect.
Downloads​
All Devices - http://goo.im/devs/henryedwardrose/Kernel/ICS
P1 - zImage - Boot.img - Flashable.zip - Odin.tar
P1L - zImage - Boot.img - Flashable.zip - Odin.tar
P1N - zImage - Boot.img - Flashable.zip - Odin.tar
Installation​
zImage or boot.img​
Use command line tool known as 'heimdall' (for people comfortable with the command-line)
Flashable.zip​
Installed using CWM (the easiest methord)
Odin.tar​
Put this file in the PDA section on Odin (Windows only)
Special Thanks​The TE4M - Nice work on developing the kernel and getting our device officially supported by CyanogenMod!
Dizgustipated - Nice Guy, Excellent Roms and Kernel!
Technomancer - The Guy who originally ported CM7 to our tab

Sources​My Github
Building​You can build this kernel yourself in two ways
The First Methord​Is by adding it into your manifest in your android build environment which supports integrated kernel building like CM9/10 and AOKP.
If you want it in your own Rom then simply just perform the regular build commands
If you just want to build a boot.img then apply the following commands
source build/envsetup.sh
lunch cm_p1-userdebug (change this depending on what device you would like to build)
make out/target/product/p1/boot.img
Click to expand...
Click to collapse
The Second Methord​Before the integrated kernel building system you used to build a kernel outside of this in it own separate environment so i have made it possible without have to download the android build environment to build any kernel for this device and you just have to run a build script and tell it what device you want to make.
Firstly you want to use the following commands
mkdir Kernel
cd Kernel
repo init -u https://github.com/henryedwardrose/Kernel_Manifest.git -b master
repo sync
Click to expand...
Click to collapse
Ok when synced you will see that there are three directories. Two of which are what you need. The 'Files' directory
is where all of the other files go that are necessary to build the kernel. The build.sh is a nice bash script which
you can open and easily understand what commands are being executed and how the files are being used.
Anyways here's how you build:
Firstly in the terminal go to the Files directory
cd Files
Click to expand...
Click to collapse
Now run this following command to extract the ramdisks (you only have to do this when i have uploaded a new ramdisk)
./RUNAFTERSYNC.sh
Click to expand...
Click to collapse
Then you want to build the kernel and at the end you will end up with the following flashable files 'zImage,
boot.img, .tar, .zip'
Now you need to initiate the building process
./build.sh
Click to expand...
Click to collapse
Now follow the commands on screen and you will end up with the kernel located in the out directory and you can flash
via Heimdall (zImage and Boot.img), Odin (.tar) and CWM (.zip)
Enjoy!

Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..

a-vista said:
Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..
Click to expand...
Click to collapse
oops! forgot this information lol :silly: Of course, well except for P1C atm

thanks for kernel. love your work bro.
i flashed on my p1. im trying and write back here for bugs etc.

can someone post some screen shots..???? PLEASEEE...

[email protected] said:
can someone post some screen shots..???? PLEASEEE...
Click to expand...
Click to collapse
ScreenShots from what???
This is a kernel, nothing changes visually...
Just performace, battery..etc..

hi
thanks again your work.
i tried kernel but it doesnt going into DEEP SLEEPtab working always 1200.
my options is smartassv2 and sio.

Used this kernel can be used camera 360 ?

It feels smooth indeed. Quadrant score at 1300 MHz with Cm9 is around 2600-2700.

Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S

Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!

I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's

Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium

MarlX said:
Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Yes it does, yer you can and will install but it will NOT boot unless you have ICS on your device.
vince_junior said:
Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!
Click to expand...
Click to collapse
Thank you for your report its always appreciated It has worked for me and i have a p1 but i will test it soon again to see if i have any issues
chickygamon said:
I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's
Click to expand...
Click to collapse
There is no need to install it but if you install this one it won't hurt its the same.
Gpsrisk said:
Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I will upload it to goo.im soon but working on jb atm

henryedwardrose said:
I will upload it to goo.im soon but working on jb atm
Click to expand...
Click to collapse
Wow!

New Link
Hey, Uploaded All files to Here now;
http://goo.im/devs/henryedwardrose
Click to expand...
Click to collapse
enjoy!

henryedwardrose said:
Hey, Uploaded All files to Here now;
enjoy!
Click to expand...
Click to collapse
Something wrong with goo.I'm server. ?
Sent from my GT-P1000 using Xparent ICS Tapatalk 2

well this sucks all links are broken

tohno said:
well this sucks all links are broken
Click to expand...
Click to collapse
Goo.im are down atm i am going to upload them again when they are back up. In the mean time i am working on a few things and i may rebuild the kernel with gcc 4.6 check the op are the links still working on rapidahare?
Sent from my GT-P1000 using xda app-developers app

Since Many of you people will be needing this kernel. I uploaded this Thread.
This also Works with CM10
Arco Kernel.zip- Only works with cm9 and cm10 Alpha1
CM9 Beta 4 Kernel- Only works with CM9
Cm10 alpha version 3.0 kernel- In slim bean...the WiFi didn't work for me. Works only with jelly bean ROMs
Cm10 ARCO kernel build 3 version 2.6 with camera working. Works properly in SlimBean
Camcory's SlimBean Kernel- People say that it has Very GOOD BATTERY LIFE. I haven't tested in CM10( Hopefully there won't be problems)
I wont upload build 4 kernel of cm10 since 4.1 is just an updated version of build 4
CM10 Build 4.1- Never tested. Version 3.0 and 2.6 Uploaded. Only works on Jelly bean based ROMs
CM9 RC1 and RC2- Never tested. Version 2.6 Uploaded. Only works of ICS Based ROMs
Instructions:
Download Attachment
Flash Via CWM.
Clean Cache
Wipe Dalvik.
Reboot.
I will update his kernel as soon as he updates his builds.

jassim007 said:
Since Many of you people will be needing this kernel. I uploaded this Thread.
This also Works with CM10
Instructions:
Download Attachment
Flash Via CWM.
Clean Cache
Wipe Dalvik.
Reboot.
I will update his kernel as soon as he updates his builds.
Click to expand...
Click to collapse
It's 3.0 kernel ?
Doesn't boot, after flashing this zip file.

Mikyno said:
It's 3.0 kernel ?
Doesn't boot, after flashing this zip file.
Click to expand...
Click to collapse
No its not 3.0. It worked for me with cm9b3.

Mikyno said:
It's 3.0 kernel ?
Doesn't boot, after flashing this zip file.
Click to expand...
Click to collapse
Which rom?

jassim007 said:
Which rom?
Click to expand...
Click to collapse
Cm10...

Mikyno said:
Cm10...
Click to expand...
Click to collapse
Currently...I only test on cm9. I will test on cm10 .

jassim007 said:
Since Many of you people will be needing this kernel. I uploaded this Thread.
This also Works with CM10
Instructions:
Download Attachment
Flash Via CWM.
Clean Cache
Wipe Dalvik.
Reboot.
I will update his kernel as soon as he updates his builds.
Click to expand...
Click to collapse
Is it necessary to clean cache and wipe dalvik?

AzizWahid said:
Is it necessary to clean cache and wipe dalvik?
Click to expand...
Click to collapse
Recommended. If you don't want to...its OK.

Which arco's kernel? is it OC/UV or not? what tweaks are added on it or is it just plain? you need to give us some information bro.

Mikyno said:
It's 3.0 kernel ?
Doesn't boot, after flashing this zip file.
Click to expand...
Click to collapse
Im very sorry for your bootloop. I have uploaded CM10 Alpha2 kernel

7amada100 said:
Which arco's kernel? is it OC/UV or not? what tweaks are added on it or is it just plain? you need to give us some information bro.
Click to expand...
Click to collapse
Just the kernel he made. No tweaks and no OC/UV

I have uploaded Version 3.0 kernel from Arco.

will this work in galaxy s plus?
Sent from my GT-I9001 using xda app-developers app

Ezekiel1998 said:
will this work in galaxy s plus?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure of that. Mostly it won't work and your might get soft bricked or hard bricked. So be carful what you're doing.

jassim007 said:
I have uploaded Version 3.0 kernel from Arco.
Click to expand...
Click to collapse
Great job. These popular kernels simplify the job of swapping kernel of our choice. :thumbup:
Note: the traditional method of changing kernel is using CWM's advance restore from the boot image.
Sent from my GT-I8150 using xda app-developers app

wong.izzat said:
Great job. These popular kernels simplify the job of swapping kernel of our choice. :thumbup:
Note: the traditional method of changing kernel is using CWM's advance restore from the boot image.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
next time, you can do it in easier way though.
things you need : 1. kernel flashable zip( you can use the one from this thread) 2. boot.img you wanted to flash 3. win rar or 7zip or etc you prefer
the steps
1. extract boot.img you wanted from the rom flashable zip
2. open your kernel flashable zip
3. drag the kernel you just extracted to the kernel flashable zip content
4. voila the boot.img in the kernel flashable zip will be changed to the one you dragged
sorry, OP i'm just helping him, rather than using traditional time wasting method this one is lots faster

hadidjapri said:
next time, you can do it in easier way though.
things you need : 1. kernel flashable zip( you can use the one from this thread) 2. boot.img you wanted to flash 3. win rar or 7zip or etc you prefer
the steps
1. extract boot.img you wanted from the rom flashable zip
2. open your kernel flashable zip
3. drag the kernel you just extracted to the kernel flashable zip content
4. voila the boot.img in the kernel flashable zip will be changed to the one you dragged
sorry, OP i'm just helping him, rather than using traditional time wasting method this one is lots faster
Click to expand...
Click to collapse
Thanks for the advise brother.

I have uploaded Arco Kernel Build 3 Version 2.6 with Camera Working

jassim007 said:
I have uploaded Arco Kernel Build 3 Version 2.6 with Camera Working
Click to expand...
Click to collapse
Oh nice, so I will use kernel 3.0 daily and only flash kernel 2.6 if I need use of camera

Thanks for the post,
using v2.6 in slim bean everything fine.

So, i started building CM10.1 using androidarmv6 sources which are known for working with msm7x27a. I modified my device folder and it builds.
Any help would be apreciated.
If anyone is intrested in development please join #Lproj on freenode to exchange ideas
Current status:
- It boots to GUI [L5&L7]
- Camera works [L5&L7]
- ril partially works (no outgoing calls)
- sdcard works
TODO:
- outgoing calls
- video rec
- audio routing in calls (l7 only?)
And the thank you award goes to the following: @PecanCM @cybojenix @adfad666
device folders

here speaks of cm10.1, but I tried it and I can not figure out if there are any differences or not :/ :http://forum.android.com.pl/f759/cm10-avatar-rom-extreme-291710/

michelemascia7 said:
here speaks of cm10.1, but I tried it and I can not figure out if there are any differences or not :/ :http://forum.android.com.pl/f759/cm10-avatar-rom-extreme-291710/
Click to expand...
Click to collapse
Go to Settings > System > About phone and make a screenshot please.
I want to see if it really is CM10.1

CM10.1
It is not clear cm10.1 just my version of the beta, made by me cm10.1 and avatar rom from nexus 4 and firmware LG optimus G.
My version cm10.1 not publish.

crinca15 said:
Go to Settings > System > About phone and make a screenshot please.
I want to see if it really is CM10.1
Click to expand...
Click to collapse
I have now flashed the pac rom of Metallica, and can not do a screenshot :/
evidently it is not 10.1 as confirmed @szymel0

I just tryed RC7 of it! Works nice. I jumped from PACman Rom to Avatar CM10.1 without wipe cache or data...
But do I need CM10.1 gapps ?

crinca15 said:
I just tryed RC7 of it! Works nice. I jumped from PACman Rom to Avatar CM10.1 without wipe cache or data...
But do I need CM10.1 gapps ?
Click to expand...
Click to collapse
i had flashed cm10 gapps but careful not to go off topic :silly:

Please stay ontopic

michelemascia7 said:
i had flashed cm10 gapps but careful not to go off topic :silly:
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=0B2Yt4LYuF0UuNDdEUXZYSmtxTFU&usp=sharing
RC9 Exists (Just to say, sry for off topic, had to say it)
EDIT : And I think you should ask some experience users of this, because they can help you (or not xD), I can´t help you, Since I entered on xda, I just did a ROM for galaxy gio, so a little of experience.

friends, i didn't understand one thing, i can flash Avatar EXTREME RC7 CM 10.1 , for my LG P700? or not is for our phone this rom? question by the read in this topic.
sorry for offs topic

your logcat say you are using normal qcom_display folder not legacy one and that's created this problem and which kernel you are using ? because
E/hwcomposer( 4290): FATAL:vsync_loop:not able to open file:/sys/class/graphics/fb0/vsync_event, No such file or directory

PecanCM said:
your logcat say you are using normal qcom_display folder not legacy one and that's created this problem and which kernel you are using ? because
E/hwcomposer( 4290): FATAL:vsync_loop:not able to open file:/sys/class/graphics/fb0/vsync_event, No such file or directory
Click to expand...
Click to collapse
I use qcom legacy from android armv6 and still get this error. Also I tried to use a branch from legacy droid that user adfad666 pointed me to and still getting the same error. I use stock 3.4.0 cm10 kernel. Are there any modifications I should make to kernel?
second logcat http://pastebin.com/6JGw1fvy
Sent from my LG-P700 using xda app-developers app

Maybe a problem with the drivers adreno 200?

I am not a developer (yet) but maybe try porting files from a device silmilar to ours and start modifying from there ??
Good luck on your work and hope you succeed
Sent from my LG-P700 using xda app-developers app

tudorsirb said:
I use qcom legacy from android armv6 and still get this error. Also I tried to use a branch from legacy droid that user adfad666 pointed me to and still getting the same error. I use stock 3.4.0 cm10 kernel. Are there any modifications I should make to kernel?
second logcat http://pastebin.com/6JGw1fvy
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
so 1st logcat with adfad666 display folder and 2nd logcat with androidarmv6 display folder right ? and i asked because it's strange you using stock cm10 kernel and vsync_event node not created

PecanCM said:
so 1st logcat with adfad666 display folder and 2nd logcat with androidarmv6 display folder right ? and i asked because it's strange you using stock cm10 kernel and vsync_event node not created
Click to expand...
Click to collapse
First is from a bad build where I forgot to add legacy. Second is from adfad's repo. with legacy I get the same errors.
EDIT: I use adreno blobs from cm10 should i use different ones for cm10? i also tried referece blobs from Qualcomm
Sent from my LG-P700 using xda app-developers app

tudorsirb said:
If anyone is intrested in development please join #p700 on freenode to exchange ideas
Click to expand...
Click to collapse
is this channel not being used then?
this morning I uploaded my device config for l5 which seemed to solve the egl error, however I haven't tried it since the last kernel, so don't even know if it boots (I was messing with the boot.img from alpha firmware, and source of the l3 ii)
hope this helps

cybojenix said:
is this channel not being used then?
this morning I uploaded my device config for l5 which seemed to solve the egl error, however I haven't tried it since the last kernel, so don't even know if it boots (I was messing with the boot.img from alpha firmware, and source of the l3 ii)
hope this helps
Click to expand...
Click to collapse
thanks, i fixed egl with it Now i'm stuck at boot animation with some weird errors.

tudorsirb you are my god!! I pray to you and hope cm10.1 will be finnished after the summer vacations!!
Sent from my LG-P700 using xda premium

ubuntuh said:
tudorsirb you are my god!! I pray to you and hope cm10.1 will be work after the summer vacations!!
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
Thank cybojenix beacuse i'm getting loads of help from him

Introduction
First time,I want to say THANKS !!!! to @Tasssadar because he's the creator and he helped me a lot !!!MultiROM is one-of-a-kind multi-boot mod for Galaxy S4(international). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=SCYh14Zwl3s You can also watch a video which shows it in action.​
Warning!
####### MUST READ !! ######
Installation tutorial video :
https://www.youtube.com/watch?v=xEYmDV6YAjE&feature=youtube_gdata_player
1.The mod is different than the Nexus 7 mod because we have a different kexec hardboot patch.
So,everytime you flash a secondary ROM,you need a patched kernel.You will find them in 2nd post.
How to flash it?Right after you flashed the secondary ROM,go to advanced -> MultiROM -> List ROMs -> click on your ROM -> Flash zip -> Select a patched kernel from 2nd post.If the ROM doesn't work with any patched kernels,request me to patch the ROM's kernel.
Some of new CM,Carbon etc builds won't work with a custom kernel because of a CAF mess,so I patched their kernel.You can find it in 2nd post.To flash,go into advanced -> MultiROM -> List ROMs -> select your ROM -> Flash zip -> Flash the ROMname_patched_kernel_MultiROM zip
2.At boot,the MultiROM needs 3-4 seconds to initiate the touchscreen drivers.So when the auto boot screen will appear,the touchscreen won't work for 3-4 secs.I recommend to disable the auto boot in advanced -> MultiROM -> Settings or increase the auto boot time to 15 seconds.
3.It will not work with sdcards yet.Also,when it will work *not sure when*,you will need a high speed SDCard to have a smooth ROM.
4.The recovery is still beta.If the screen goes off,you have to reboot again into recovery.And it needs some resizing,but it's acceptable.I am working on it.
Click to expand...
Click to collapse
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Click to expand...
Click to collapse
Installation
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
[*]MultiROM (multirom-YYYYMMDD-vXX-jfltexx.zip) - download the ZIP file from second post and flash it in recovery.
[*]Modified recovery (TWRP_multirom_jfltexx_YYYYMMDD.zip) - Flash the zip in your already installed recovery or extract the recovery.img and flash it with Flashify.
[*]Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
Click to expand...
Click to collapse
You current rom will not be erased by the installation.
Download links are in the second post.
Click to expand...
Click to collapse
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.Flash the patched kernel.
Click to expand...
Click to collapse
2. Other Systems
Unfortunately, no other systems are available as of now. But, MultiROM _theoreticaly_ supports them - the principle should be the same as on grouper, we just need the systems. That's why the options in "Add ROM" menu in recovery are there, but do not flash systems for old Nexus 7 (grouper)!
Click to expand...
Click to collapse
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Click to expand...
Click to collapse
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Click to expand...
Click to collapse
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Flash the patched kernel.
Click to expand...
Click to collapse
Source code
MultiROM - https://github.com/oblikas/mr_device_jfltexx
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Click to expand...
Click to collapse
XDA:DevDB Information
MultiROM,a multi boot solution for Galaxy S4 I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
oblikas, http://forum.xda-developers.com/member.php?u=4870917, Tasssadar
Version Information
Status: Beta
Current Beta Version: v16a
Beta Release Date: 2013-10-20
Created 2013-10-20
Last Updated 2013-10-20

Downloads
1. Main downloads
MultiROM: multirom-20132010-v16a-jfltexx.zip
Modified recovery (TWRP 2.6.3.0): TWRP_multirom_jfltexx_20132010.zip
Click to expand...
Click to collapse
Patched kernels :
For AOSP 4.4 ROMs;
KT Kernel AOSP4.4
For AOSP 4.3 ROMs:
KT Kernel 4.3 17.09
Chronic Kernel 4.3 2.1.1
PAC 4.3 kernel
Carbon 4.3 kernel
AOKP 4.3 kernel
CM10.2 kernel
For AOSP 4.2 ROMs
KT Kernel 4.2
For TouchWiz ROMs:
KT 4.3 TouchWiz kernel
KT 4.2 TouchWiz kernel
Click to expand...
Click to collapse
Donations
If you want to donate me,use the "Donate to me" button.
Indiegogo campaign : http://igg.me/at/multiroms4/x/6262625
Donate to @Tasssadar. You can use either paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated ​
Click to expand...
Click to collapse

Wow.this is so cool.
Sent from my GT-I9505 using xda premium

Sweeeeet!!! ^^
Sent from my GT-I9505 using app: XDA Premium and rom: CgoastINC Rom v14

Great work ! So,no need to patch gapps?

AMAZING downloading needed files now
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
Would i be able to do a touchwiz nandroid and then share kernels?

ktetreault14 said:
AMAZING downloading needed files now
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
Would i be able to do a touchwiz nandroid and then share kernels?
Click to expand...
Click to collapse
TouchWiz ROMs are not yet supported.

Just Flashed. Nandroid didnt work because i didnt have a patched kernel but I love the GUI at boot. Real nice on my tmobile s4

Am i correct in assuming that this will work on jflteatt if I flash loki doki after flashing MultiROM and recovery?

rushi.1986 said:
Am i correct in assuming that this will work on jflteatt if I flash loki doki after flashing MultiROM and recovery?
Click to expand...
Click to collapse
I am not sure.This mod it's for jfltexx.
Also,I got the patched kernel for TouchWiz ROMs.I succesfully booted TW 4.2 ROM + PA + CM10.1 + AICP.

oblikas said:
I am not sure.This mod it's for jfltexx.
Also,I got the patched kernel for TouchWiz ROMs.I succesfully booted TW 4.2 ROM + PA + CM10.1 + AICP.
Click to expand...
Click to collapse
I glanced through the scripts. It does not seem like you are messing with the boot loader at all. All the modifications are in the kernel and the recovery. Is that right?
If yes, I m gonna go ahead and try it. The only difference between jfltexx and jflteatt is the boot loader (the sbl partitions and the aboot partition.) Other than that, they are identical.
The Loki doki patch patches the ramdisk of the recovery and the kernel to fool the boot loader into believing that an official Samsung binary is being used as kernel or recovery.
So the only thing I am worried about is your ramdisk modifications interfering with the Loki patch ramdisk modifications.
I have attaches the zip file for the Loki doki patch. Can you please take a look at the scripts and see if there are conflicts?
Thanks.
Loki doki: https://db.tt/F6q4dKhm
EDIT: never mind.. The zip I posted just has binaries and script just executes the binaries. The source and description of what Loki patch does is here:
http://forum.xda-developers.com/showthread.php?t=2292157
If you have spare time and if you want to support jflteatt, you can look through that..
Thanks again.
Sent from my SGH-I337 using Tapatalk

Uploaded patched kernels for TouchWiz ROMs.
Tested with EchoSlim ROM and worked.

rushi.1986 said:
I glanced through the scripts. It does not seem like you are messing with the boot loader at all. All the modifications are in the kernel and the recovery. Is that right?
If yes, I m gonna go ahead and try it. The only difference between jfltexx and jflteatt is the boot loader (the sbl partitions and the aboot partition.) Other than that, they are identical.
The Loki doki patch patches the ramdisk of the recovery and the kernel to fool the boot loader into believing that an official Samsung binary is being used as kernel or recovery.
So the only thing I am worried about is your ramdisk modifications interfering with the Loki patch ramdisk modifications.
I have attaches the zip file for the Loki doki patch. Can you please take a look at the scripts and see if there are conflicts?
Thanks.
Loki doki: https://db.tt/F6q4dKhm
EDIT: never mind.. The zip I posted just has binaries and script just executes the binaries. The source and description of what Loki patch does is here:
http://forum.xda-developers.com/showthread.php?t=2292157
If you have spare time and if you want to support jflteatt, you can look through that..
Thanks again.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I will try when I will have some free time.
L

Where does this actually boot the rom from? Also could you post a little clearer instructions? Some people might get confused due to the layout. Also this mod is amazing, will we see any Ubuntu we could put through it.

ktetreault14 said:
Where does this actually boot the rom from? Also could you post a little clearer instructions? Some people might get confused due to the layout. Also this mod is amazing, will we see any Ubuntu we could put through it.
Click to expand...
Click to collapse
I posted a video with the instructions.
Sent from my GT-I9505 using xda app-developers app

oblikas said:
I posted a video with the instructions.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks
Sent from my GT-I9505

Can you Please patch the MIUI Kernel? Btw, thanks for the awesome work!

shiro1811 said:
Can you Plesse patch the MIUI Kernel? Btw, thanks for the awesome work!
Click to expand...
Click to collapse
Use the AOSP 4.2 kernel for it.
Sent from my GT-I9505 using xda app-developers app

oblikas said:
Use the AOSP 4.2 kernel for it.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
The BOOTCLASSPATH variable is different for MIUI, so a separate kernel is needed

chenxiaolong said:
The BOOTCLASSPATH variable is different for MIUI, so a separate kernel is needed
Click to expand...
Click to collapse
oh.I didn't know.
I will patch the kernel 2moro after school
Sent from my Optimus G Pro using xda app-developers app

Hi everyone!
This is my first Kernel. I hope you will like it. I'm not a developer. I am still learning...
FEATURES
*Kernel 3.4.74
*Build with Linaro GCC 4.8.3 2013.11 toolchain by Christopher83
*O3 Optimization
*Overclock up to 1.8 GHz
*CPU voltage control VDD sys interface
*Lowered display panel voltage
*Lowered wifi voltage
*Fast Charge support
*Battery Life eXtender support
*Increase audio loudness
*Con Kolivas' CK3 Tweaks
*Fast Random generator (frandom) support
*Dynamic management of dirty page writebacks
*Dynamic management of the minimal slack
*Dynamic file sync
*LowMemoryKiller management of not killable processes
*370MB Ram
*Governers : lulzactive, interactive, powersave, smartassV2, performance ( default smartassV2 )
*I/O schedulers : noop, row, sio, cfq, bfq ( default sio )
INSTALLATION GUIDE
Reboot To Recovery Mode
Flash the kernel
Wipe Cache & Dalvik Cache
Reboot System
CREDITS
arco68
Christopher83
educk
madridii
arsradu
and all github users for their commits
<<DOWNLOAD>>
Code:
You can use [URL="http://forum.xda-developers.com/showthread.php?t=2401988"][COLOR="DeepSkyBlue"]Performance Control[/COLOR][/URL] to edit all features.
CHANGELOG
v1
initial release
v1.1
fixed battery icon stuck problem
Click to expand...
Click to collapse
XDA:DevDB Information
CM 10.2 - 4.3.1 - Khan Kernel, a Kernel for the Samsung Galaxy W I8150
Contributors
lafactorial
Kernel Special Features: Overclock Support
Version Information
Status: Beta
Current Beta Version: v1.1
Beta Release Date: 2013-12-16
Created 2013-12-15
Last Updated 2013-12-16

Wow thanks guys...can you also make for cm 11? If you free time?
Sent from my GT-I8150 using Tapatalk

Very thanks brother.
Success and ease.
Cwm 6.0.4.5 used

heloo, when i flash it, i got installation aborted, i think my downloaded file is corrupt and then i download it again, and when I flash it, i got installation corrupt again. i don't know why, i'm using cm10.2 build 4 by arsradu and using cwm 6.0.4.5.

ianfebriyanto said:
heloo, when i flash it, i got installation aborted, i think my downloaded file is corrupt and then i download it again, and when I flash it, i got installation corrupt again. i don't know why, i'm using cm10.2 build 4 by arsradu and using cwm 6.0.4.5.
Click to expand...
Click to collapse
Similar problem before.
Dev @arsradu Quote
The kernel was tested. So...no, I don't think that's from the kernel. Make sure you downloaded it entirely. And...I don't know, make sure you don't have any funny stuff like custom recovery or something like that installed on your phone. Other than that...it should work.

ali7557 said:
Very thanks brother.
Success and ease.
Cwm 6.0.4.5 used
Click to expand...
Click to collapse
Great, how u got touchwiz on 4.3.1 ?, ok thanks

ali7557 said:
Similar problem before.
Dev @arsradu Quote
The kernel was tested. So...no, I don't think that's from the kernel. Make sure you downloaded it entirely. And...I don't know, make sure you don't have any funny stuff like custom recovery or something like that installed on your phone. Other than that...it should work.
Click to expand...
Click to collapse
yeah, my bad. i don't know, this is my recovery or something else that weird. i try flash stock kernel by arsradu I got installation abort. i flash it when i using cwm 6.0.4.4 it's ok, no problem. I think this is not the file that corrupt. I'm using cwm 6.0.4.5 that hadi posted in his cm11 section, and install it by ATE.

ianfebriyanto said:
yeah, my bad. i don't know, this is my recovery or something else that weird. i try flash stock kernel by arsradu I got installation abort. i flash it when i using cwm 6.0.4.4 it's ok, no problem. I think this is not the file that corrupt. I'm using cwm 6.0.4.5 that hadi posted in his cm11 section, and install it by ATE.
Click to expand...
Click to collapse
Look, my dear brother
He uses the hadidjapri 6.0.4.5 with cwm.
My similar problem had been.
Dev asked him to Arsradu.Had given the answer to the above.
I don't know what the problem is.
6.0.4.4 try to install with.

sigprof said:
Android developers changed the format of the shared memory area used to store system properties in the kitkat branch, then made some further changes (1, 2, 3, 4). Then they added backward compatibility with the older format, but only in one direction — now an executable linked with the new bionic libc can work even if the init process is from an older version (the commit log mentions the case when an older recovery is used to install an update.zip for a new version), but an executable linked with the old bionic libc will not work with a new init process. The latter case is what happens when you try to install a baseband zip file using the recovery built for kitkat — every update.zip file contains its own update-binary inside, and in this case update-binary is statically linked with the old (pre-kitkat) bionic libc. Because of this incompatibility getprop() calls in the updater-script do not return the expected values, and the compatibility check fails.
I could try to update at least my baseband zip files with a new update-binary, but this will take some time to check whether this could really work with different recovery versions, and then to upload all those files and update links to them.
BTW, the CWM recovery 6.0.4.5 image from this thread seems to be built in the 4.3.1 (JB) environment, therefore baseband update zips should be installable with this recovery version (however, I'm not sure about compatibility with kitkat ROMs).
Click to expand...
Click to collapse
maybe this is the answer to our problem.
Someone could try arco cwm 6.0.4.5, it is built in 4.3.1 enviroment the others should be 4.4.1 enviroment

i have a bug to report with this kernel: it's almost 1hour and a half that i'm surfing the web, using facebook app and playing, and my phone battery's percentage stuck at 23%!! (the percentage that was when i rebooted the device after flashing this rom)

jam90 said:
i have a bug to report with this kernel: it's almost 1hour and a half that i'm surfing the web, using facebook app and playing, and my phone battery's percentage stuck at 23%!! (the percentage that was when i rebooted the device after flashing this rom)
Click to expand...
Click to collapse
Thanks for the report. I think I used the wrong zImage while compiling. I will fix it when I get home.

lafactorial said:
Here is anykernel version attached. You can flash it.
Click to expand...
Click to collapse
And remember that you can successfully flash "anykernel" version if you're running the stock kernel by Radu. Other than that you can face some system apps FC.
One can easily flash "anykernel" version over the stock kernel only once. The reason is the ramdisk.
Sent from my GT-I8150 using Tapatalk

LeroViten said:
And remember that you can successfully flash "anykernel" version if you're running the stock kernel by Radu. Other than that you can face some system apps FC.
One can easily flash "anykernel" version over the stock kernel only once. The reason is the ramdisk.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
Yes you are right. I will make a boot.img version when I get home from work.
Sent from my GT-I8150 using XDA Premium 4 mobile app

What's this "anykernel"? A simple stock kernel, or a modified one by you without that bug?
Sent from my GT-I8150 using xda app-developers app

jam90 said:
What's this "anykernel"? A simple stock kernel, or a modified one by you without that bug?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Anykernel only flashes the kernel zImage and modules not the ramdisk. So this is a modified one and there is no battery stuck problem.
Sent from my GT-I8150 using XDA Premium 4 mobile app

lafactorial said:
Anykernel only flashes the kernel zImage and modules not the ramdisk. So this is a modified one and there is no battery stuck problem.
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so this is your kernel but without the ramdisk. And what this will mean? If this is a modified one without battery stuck problem, why don't you post directly this in your first post? Just for knowledge

jam90 said:
so this is your kernel but without the ramdisk. And what this will mean? If this is a modified one without battery stuck problem, why don't you post directly this in your first post? Just for knowledge
Click to expand...
Click to collapse
I already changed the first post.
Sent from my GT-I8150 using XDA Premium 4 mobile app

lafactorial said:
I already changed the first post.
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok, thanks, but i asked you antoher thing. Just for my knowledge, don't take it like an offense or something else rude, please!
What's the difference between the first kernel you posted and this? what the ramdisk less mean? i repeat, not for criticize you, just for my knowledge

fdc77 said:
maybe this is the answer to our problem.
Someone could try arco cwm 6.0.4.5, it is built in 4.3.1 enviroment the others should be 4.4.1 enviroment
Click to expand...
Click to collapse
yes right, i flash latest cwm from arco and it work.
---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------
ali7557 said:
Look, my dear brother
He uses the hadidjapri 6.0.4.5 with cwm.
My similar problem had been.
Dev asked him to Arsradu.Had given the answer to the above.
I don't know what the problem is.
6.0.4.4 try to install with.
Click to expand...
Click to collapse
thanks bro, the problem is the rcovery. i flash it with latest arco recovery and it work.

jam90 said:
ok, thanks, but i asked you antoher thing. Just for my knowledge, don't take it like an offense or something else rude, please!
What's the difference between the first kernel you posted and this? what the ramdisk less mean? i repeat, not for criticize you, just for my knowledge
Click to expand...
Click to collapse
ramdisk is a small partition image that is mounted by the kernel at boot time. It only contains init and a few config files. It is used to start init which will mount the rest of the system images properly and run the init procedure.
Just googled it as I dont know the exact definition...
Sent from my GT-I8150 using XDA Premium 4 mobile app