I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
SaiyanGoku said:
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
adfurgerson said:
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
Click to expand...
Click to collapse
I'd suggest using the kernel you want since the beggining. Just Open up both files using winrar and delete boot.img from the GEE DU and replace it with the boot.img from the GEEB build that you like much.
Click to expand...
Click to collapse
so, does replacing the boot.img will do the job?
SaiyanGoku said:
so, does replacing the boot.img will do the job?
Click to expand...
Click to collapse
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
adfurgerson said:
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
Click to expand...
Click to collapse
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
jimbo77 said:
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
Click to expand...
Click to collapse
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
As stated earlier in the thread, No.
If you want to have HDR photos, you need to use a rom that's built on Mako/GEEB sources (like Vanir or PA or Carbon or Beanstalk or DU or 90% of the other roms on this forum.
CAF-based roms, including CM and Mokee use a completely different set of source code, so No, You Can Not add HDR to CM11 kernel.
If you want to learn about device development, sure, it might be possible. But just trying to Winzip Wizard everything into place is not going to accomplish Anything that you want it to.
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
jimbo77 said:
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
Click to expand...
Click to collapse
i learned C and C++ when i was in school. and about kernel coding, nothing yet.
i think i'm better using CM11 directly if ever wanted to switch from PA instead of nuking my phone experimenting on non-compatible kernels.
(i don't use HDR that often as post processing takes time and there isn't that much of a difference in image quality)
Related
Google has recently released the 3.10 linux kernel for Android. and CodeAurora has also got it. I was wondering if it's realistic to port in this phase. I tried to but I failed hard lol. Main reason to port the 3.10 series is that it should have a great battery life. I'm not sure whether it will run on KitKat since it's supposed to be for Android 5.0.
Links:
Google Kernel: https://android.googlesource.com/kernel/common.git/+/experimental/android-3.10
CodeAurora Kernel: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10
Anyone else attempted? If anyone could give me some more info about this I would be very happy!
Thread cleaned
How many times do we have to say it?
Keep this damn soap opera drama OFF XDA and stick to your Google +
How rude to bring all this crap in here to the OP's discussion
Next talk of secret kernels or banned members will be...trouble.
If you have no respect for XDA, then leave XDA...please!
Thank you for your cooperation
Friendly Neighborhood Senior Moderator
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
sorg said:
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
Click to expand...
Click to collapse
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
broodplank1337, what happens if you build a recovery and fastboot boot that?
xboxfanj said:
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
Click to expand...
Click to collapse
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
sorg said:
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
Click to expand...
Click to collapse
Yeah, there's a bunch of proprietary files specific to the SOC.
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
LLStarks said:
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
Click to expand...
Click to collapse
True. Caf does have some 3.10 device branches but none for 8960/8064, since those are not supported. Not sure why since they do support weaker chips such as 8226 and 8610. They do have some ramdisk changes for 3.10, but even with all that, I have no adb and no ramconsole on the optimus g (nexus 4).
Sent from my Optimus G using xda app-developers app
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
LLStarks said:
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
Click to expand...
Click to collapse
my s3 3.4-drm kernels supports it - patches came from here ==>
(s4 kernel is a WIP)
https://github.com/freedreno/kernel-msm/
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
LLStarks said:
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
Click to expand...
Click to collapse
We have offloaded all audio processing and mp3 decoding to the DSP. Thus allowing all 4 primary cores to sleep while playing audio. Media player app itself may use CPU cycles for UI updates when the screen is on. Working on WMA decoding...
Sent from my GT-I9505G using XDA Premium 4 mobile app
please make this kernel work with miui rom!
The reason I post my ROM here is because I'm soon starting with a new rom, broodROM KitKat which will also be available for the Note 3, So I figured why not test it on my current AOSP ROM (to see if there is any trouble on compiling, but no!). This AOSP is based on the real Google AOSP, no real further modifications (only thing is that it includes DeviceSettings from the S4 currently), and AppOps is exposed. that's all.
It includes the stock CM11 kernel (which is kinda crappy). but I don't have the device so cannot make decent kernel myself without testing. Also the ROM is 100% untested. but it compiled without any error with my sources (www.github.com/AOSP-S4-KK) so I think it's alright.
Working List
- You tell me I have no idea :silly:
Download Alpha 1
www.broodplank.net/files/AOSP-442-N9005-Alpha-1.zip
on alpha 01 you need to flash a custom kernel
SEND ME LOGCAT! BECAUSE CURRENTLY IT SEEM TO BOOTLOOP
The device name is listed as hlte in settings / build.prop, don't worry this is actually hltexx
Download Gapps Lite + SuperSU (yes it's not rooted by default, I recommend installing this package)
http://broodplank.net/files/gapps-4.4.2-lite-with-supersu-1.86.zip
Sources
- https://github.com/aosp-s4-kk
Download:
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u git://github.com/AOSP-S4-KK/platform_manifest -b kk-4.4
repo sync
Building:
Code:
. build/envsetup.sh
lunch
make otapackage
reserved1
Sweet man!! Thanks always looking for something new to flash lol downloading now
Sent from my iPad using Tapatalk
Downloading!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thankyou OP
anybody that has tried this, can you let me know if the temp/humidity sensors are still working after a few hours? as with other cm roms they stop working for me
Awesome Broodplank! Just switched from the Galaxy S Plus to the Note 3, always enjoyed your roms on there. Will try out this one! Keep up the good work
Sent from my SM-N9005 using xda app-developers app
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
radicalisto said:
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
Click to expand...
Click to collapse
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
broodplank1337 said:
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
Click to expand...
Click to collapse
OK - will try again now and let you know :good:
and new bootloader ?
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
radicalisto said:
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
Click to expand...
Click to collapse
ok good, could you open up adb shell, and send me the logcat, since I have no idea what actually could be the cause atm.
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
radicalisto said:
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
broodplank1337 said:
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
Click to expand...
Click to collapse
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
radicalisto said:
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
Click to expand...
Click to collapse
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
gianton said:
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
Click to expand...
Click to collapse
Ah I dropped the herp a derp then hahah, Nah reason I thought that was because of the CM kernel used to boot it up. Thanks for correcting :good:
---------- Post added at 08:56 AM ---------- Previous post was at 08:55 AM ----------
@gianton it'll boot into splash screen with temasek's kernel, if you wanna try and grab an ADB Logcat? - I'm having issues getting one :crying:
Sorry for not providing a good kernel, the thing is I cannot compile it decently with the ROM. it says I have to add module support and recontinue, thing is, the note 3 does not use it. but my build forces it.. Anyone have experience on CM with compiling the kernel? (the kernel is from CM after all)
You could try temasek or Yank555 or wootever for help with kernels as they're pretty decent at them - civato knows his stuff also, however I believe he has only worked with Stock samsung kernels and not CM stuff.
Still cannot get ADB logcat, phone won't recognise in PC
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder. Now dear friends left to adjust the kernel to work memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/9llrwW9ZSAPAM
sew this boot for camera operation https://docs.google.com/file/d/0B1e6YcHvyda_UEZBNjFSdno4TFU/edit
Many thanks Paulicat for the kernel
ananasic said:
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder, and then the boot folder. Now dear friends left to adjust the kernel to work the camera and memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/3-3klCFfRA2Fa
Click to expand...
Click to collapse
Did you try flashing a stock JB kernel afterwords for the E970?
johnwayne007 said:
Did you try flashing a stock JB kernel afterwords for the E970?
Click to expand...
Click to collapse
does not work
ananasic said:
does not work
Click to expand...
Click to collapse
Huh, well sadly I am no good at all with kernel anything. Do you know if the kernel source was released for the Korean variant?
We will have to wait for someone to get us a modified kernel or wait for an official KK rom for E970 , because of the difference b/w other variants. "Camera/SDCard"
But thanks a lot for getting a rom though.
There's apparently enough changes between JB and KK stock kernels, and the AOSP kernel source, that we can't get working camera or SD until LG releases the kernel source.
Dont mind my inquisitiveness , but Can't we get the camera codes ported from nexus 4 ? They share the same hardware when it comes to camera module ?
I am very skeptical about any KK release for our variant. AT&T has already given the release for G Pro , if our device were to get any update at least there would have been some word about it from ATT.
Sent from my LG-E970 using Tapatalk
Rishi. said:
Dont mind my inquisitiveness , but Can't we get the camera codes ported from nexus 4 ? They share the same hardware when it comes to camera module ?
I am very skeptical about any KK release for our variant. AT&T has already given the release for G Pro , if our device were to get any update at least there would have been some word about it from ATT.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
All we need is the F180 kitkat kernel source and we'll be fine.
LG is good at releasing their sources, just give it some time.
Thanks a lot mannn, for the ROM. We will wait for the kernel modification.
KK BELIEVE THE KOREA APPEARS ON OpenSource Code Distribution
ONLY THE G IS THE PRO
https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
ananasic said:
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder, and then the boot folder. Now dear friends left to adjust the kernel to work the camera and memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/3-3klCFfRA2Fa
Click to expand...
Click to collapse
Restoring fails on twrp 2.7.0 ... is this specific for 2.6.3.0 ??
PUT THAT ON PAGE BELOW FOUND SEVERAL THINGS TO CARRY AS A MANUAL FROM THE RON'S ROM KERNEL BUT NOT UNDERSTAND WHY THIS WELL IN RUSSIAN AND CHROME DO NOT TRANSLATE TO 100% OF SOMETHING I HOPE TO SERVE IN DEVELOPMENT
http://4pda.ru/forum/index.php?showtopic=502205
Nobody port to E970? =(
dark_nobody said:
Nobody port to E970? =(
Click to expand...
Click to collapse
Nobody read the threads? =(
Sent from my LG-GEEB using Tapatalk
already released from the kernel f180s f180k and LG
* https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
LG OpenSource Code Distribution
TOTAL WEIGHT OF THE KERNEL 118 MB
WHO CAN CHANGE THE MAGIC OF THE KERNEL?
lbertking said:
already released from the kernel f180s f180k and LG
* https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
LG OpenSource Code Distribution
TOTAL WEIGHT OF THE KERNEL 118 MB
WHO CAN CHANGE THE MAGIC OF THE KERNEL?
Click to expand...
Click to collapse
Kernel is badly packaged.
I emailed them to correct it.
Doesn't compile.
Paulicat said:
Kernel is badly packaged.
I emailed them to correct it.
Doesn't compile.
Click to expand...
Click to collapse
Yeah, I think JB was like that too for E970 as well, I can't remember
nygfan760 said:
Yeah, I think JB was like that too for E970 as well, I can't remember
Click to expand...
Click to collapse
JB for E971 is ok now, not sure upon initial release so you could be right.
Hopefully they fix it soon.
Hello OP,
Can you please post a link to the back up image of the boot only. My internet connection is too slow to download 1.5gb. Currently i am working on a zip. but boot looping. want to try with your kernel
Thanks in advance.:good:
could carry without the kernel or modify a kernel cm 11 for that fence watching the adjustments needed as recovery, translations of app, screen size, and go compacting the rom image of more?
porting this ROM would be easier? belongs to a f220k optimus gk
https://docs.google.com/file/d/0B57NNNkITzpjQkFOMjU4ZUhLNDQ/edit (rom)
https://docs.google.com/file/d/0B3dApvWjgNoKQWRtXzRSWW5SZlE/edit (recovery)
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=f220 (lg)
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
muximus said:
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
Click to expand...
Click to collapse
Will add it.
muximus said:
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
Click to expand...
Click to collapse
i will upload it for you as soon as i get a compiled kernel with recovery working. but right now kernel boots but recovery wont start and i dont understand why.
so may take 2 weeks...
also made a feature request for you here:
http://forum.xda-developers.com/devdb/project/?id=6484#featureRequests
Deutschland uber allez!
MusterMaxMueller said:
i will upload it for you as soon as i get a compiled kernel with recovery working. but right now kernel boots but recovery wont start and i dont understand why.
so may take 2 weeks...
also made a feature request for you here:
http://forum.xda-developers.com/devdb/project/?id=6484#featureRequests
Click to expand...
Click to collapse
Pl. help me with this Q:
It seems cm12 has not merged this commit yet.. but I could still flash a newer kernel meant for cm12 on a cm11 rom...... right? Thats the way it works on linux...
muximus said:
Pl. help me with this Q:
It seems cm12 has not merged this commit yet.. but I could still flash a newer kernel meant for cm12 on a cm11 rom...... right? Thats the way it works on linux...
Click to expand...
Click to collapse
im no kernel dev but i dont think it will work that way on android. mainly because of firmware blobs and selinux but im not sure.
wiimote support wont work
http://forum.xda-developers.com/showpost.php?p=58820839&postcount=203
MusterMaxMueller said:
im no kernel dev but i dont think it will work that way on android. mainly because of firmware blobs and selinux but im not sure.
wiimote support wont work
http://forum.xda-developers.com/showpost.php?p=58820839&postcount=203
Click to expand...
Click to collapse
I made the request to Mathias, who merged the patch in the cm11 branch.. Keeping fingers crossed that it gets merged soon!
Now patch uploaded for cm12 branch as well!
See the url here: http://review.cyanogenmod.org/#/c/89843/
Hi,
I would like to request some testers who are currently running stock MIUI to test the stock kernel. Feel free to comment below.
Instructions:
- You should be on CWM
- Download zip
- Flash kernel
- reboot
- cross your fingers
What to check:
- WLAN -> see if it works
Source:
https://github.com/emceethemouth/kernel_cancro/tree/mi-stock
WLAN:
git://codeaurora.org/platform/vendor/qcom-opensource/wlan/prima/
blah blah blah
Wifi not working after flashing the kernel.
Armin_van_buuren said:
Wifi not working after flashing the kernel.
Click to expand...
Click to collapse
Hold on I'm uploading a new one.
Edit:
Attachment updated
Wifi doesn't work, everything else does.
alphoz said:
Wifi doesn't work, everything else does.
Click to expand...
Click to collapse
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks to you, and all your hard work. I would also like to mention that the miband unlocking worked a lot better with your kernel than the MIUI stock one. Thanks again.
Wow. Thanks GNOME... Good to kernel for miui
Sent from my MI 3W using Tapatalk
Audahudi also build stock miui kernel. This also has same bugs, no WiFi, cit etc menu take while to open.
One bug I have doubt of is, whether all 4 cores work simultaneously. In my testing I saw most time 2 work, sometimes 3. Benchmarks also give scores like that. Also CPU performance control pro, which can set individual frequency of all cores could make 2 cores work together.
Any app you know which can monitor every core usage over period of time?
The 2nd bug is what I'm curious off, as I don't have WiFi lol.
Plus these miui kernel can be used in some custom Chinese KitKat ROMs. Iuni is 1 example, fiui I havent tested.
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Pepe.II said:
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Click to expand...
Click to collapse
That happened to me when I did all that.
I found no solution, so I left it.
@Pepe.II you should see the issues section, I'm always there.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/16
@Gnome
on what miui we should try stable or developer ?
Stable just to be safe.
Edit: @alexret, can you try the instructions on that misleading turorial but use my kernel source? Branch is mi-stable. I have a feeling it'll work
@Gnome anything with the bug I have doubt of?
@Gnome I tried to flash your kernel STX-MI-PRIMA-TEST-2015-06-24 from first post attachment.
Its only kernel, no modules included. This has a effect, that no modules are loaded while booting. When i try load module manually, it crashes with this message:
[email protected]:/ # insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)
Please, can you compile kernel with modules? Thanks
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Gnome said:
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Click to expand...
Click to collapse
As far as I understand it, you did not compile drivers as modules but compile them as part of the kernel?. Ok. But why, when I look in to kmesg log (/proc/kmesg), I find not a single mention about the WLAN. That's weird. Are you sure, that WLAN part is compiled correctly?
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Gnome said:
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Click to expand...
Click to collapse
Sorry, I only asking, because I do not understand how you work with drivers. Prima WLAN you set as a module but I do not see any module in a flashable zip. You assume that your kernel will use modules from stock MIUI kernel?
I do not criticize, just asking. if this sounds like criticism, so it is due to my poor English and i am sorry.