Related
I am in need of a kernel with loop enabled. I am in the newest OTA, if one doesn't exist I could use some help compiling one from the newest source, I have everything I need to do it on my Linux machine I am stuck trying to find which makefile to edit and where the .config file containing CONFIG_DEV_BLK_LOOP is located.
If it matters at all I would much rather compile my own kernel so I can learn something new.
Thanks for any help guys!
Sent from my White Evo 4G
Really!? I am not lazy or dumb, I have gone through a lot of kernel threads and it is not stated wether or not loop is enabled, all I am looking for is a kernel close to stock with loop enabled, come on guys I know someone here knows of one, if not is ANYONE willing to work with me while I learn to make one?
matthewjulian said:
Really!?
Click to expand...
Click to collapse
LOL. I'm on the more technical side, program for a living and have compiled a share of Linux kernels in my life, and I'm not quite sure what you are referring to. Sadly most of the sharper devs pretty much handle these forums in a one-way manner, they put out stuff, but they rarely read other people's posts. There are plenty of people that like to help out, but most of those folks aren't going to know anything about compilation.
The makefile you need to edit is in the root of the kernel source. The very first one that you see.
I am referring to loop devices support, this enables me to boot ubuntu on my Evo, it is one line of code that needs to be un-commented and changed to "CONFIG_DEV_BLK_LOOP=y
I am just lost,I was following this tut here http://htcevohacks.com/htc-evo-hacks/how-to-build-your-own-htc-evo-4g-android-kernel/
but the directions seriously slack off from step 11 onward, any ideas?
Do you by chance want to install Ubuntu on your phone? I think I saw something pertaining to that in some instructions I browsed over a while back.
lithid-cm said:
Grab the latest HTC source code:
edit the makefile:
Code:
CONFIG_DEV_BLK_LOOP=y
Then compile the kernel. There are plenty of how tos for kernel compiling. Let me know if you need more direction.
Click to expand...
Click to collapse
I have all the files I need, I was following the tut at htcevohacks.com but the instructions seriously slack off & there are numerous makefiles in multiple folders on top of that I can't seem to find what file contains the line config_dev_blk_loop, could you point me to a more complete walk-through please, oh and I am on the latest OTA with the newest kernel and radios.
Bump for desperation,chewed up almost 3 days of my time...
Sent from my White Evo 4G
Bump for this simp
Ok, well I guess I am gonna just have to PM each Dev individually about each individual kernel, damn all I need is a how-to or tut on kernel compiling (which the search function apparently can't find) or someone that knows of a 2.2 kernel with loop devices enabled. Oh well.
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
nukedukem said:
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
YAAY! LMFAO, I will ask there, sorry I'm excited but I have been trying to get this working for a while; I would much rather learn to build it myself but I will take what I can get for now.
IF ANYONE knows where there is an in-depth tutorial on how to compile a kernel from the newest source I would be extremely appreciative, THANKS
Did you ever find or get your Complie to work? I tried for a while to compile the stock Kernel, then gave up. I took a stab in the dark and flashed a stable netarchy kernel. unfortunatly that Kernel didn't have Loop devices enabled (Pulled Config file and Unzipped it) I like the Kernel I am running but need to find a way to get ubuntu running.
Netarchy does have loop enabled, I am running Netarchy ___(will find which version later can't remember) but yeah I am running Lakia Linux
now(network security testing, think Backtrack 3) as well as another new Linux image from a guy here, anyways I think you need Netarchy universal cfs havs less no sbc 4.2.2
Sent from my White RLS5 Evo
I have looked and been unable to find any links to source for CM6.1.2 WiMax Alpha 3. A tar.gz would be ideal but git-hub works as well as I can pull the tar from there. The reason for the request is to create a CM6/WiMax/HDMI release with full HW acceleration for those that need the pointer support that 6.1.2 provides.
I have tried the one SZ kernel that's available but it has the USB bug and HW accel detect issues and would rather start from a clean slate. Any help on source would be great. Thanks.
Lokifish Marz said:
I have looked and been unable to find any links to source for CM6.1.2 WiMax Alpha 3. A tar.gz would be ideal but git-hub works as well as I can pull the tar from there. The reason for the request is to create a CM6/WiMax/HDMI release with full HW acceleration for those that need the pointer support that 6.1.2 provides.
I have tried the one SZ kernel that's available but it has the USB bug and HW accel detect issues and would rather start from a clean slate. Any help on source would be great. Thanks.
Click to expand...
Click to collapse
It's the same kernel that is being used for CM7. You can roll that back if you want.
Also, why would you want a CM6 ROM when CM7 RC3 just came out?
ViViDboarder said:
It's the same kernel that is being used for CM7. You can roll that back if you want.
Also, why would you want a CM6 ROM when CM7 RC3 just came out?
Click to expand...
Click to collapse
So Alpha3 Froyo is actually a GB kernel? Didn't know that.
I'll check the RC3 change log to see if BT KB/mouse issues have been fixed. If not then still stuck at 6.1.2.
(update) Can find no mention of pointer support on CM7 other than requests. Nothing listed in change log.
Lokifish Marz said:
So Alpha3 Froyo is actually a GB kernel? Didn't know that.
I'll check the RC3 change log to see if BT KB/mouse issues have been fixed. If not then still stuck at 6.1.2.
(update) Can find no mention of pointer support on CM7 other than requests. Nothing listed in change log.
Click to expand...
Click to collapse
The android-x86 project doesn't even have this working yet so it will be a while before cm7 gets it.
spiicytuna said:
The android-x86 project doesn't even have this working yet so it will be a while before cm7 gets it.
Click to expand...
Click to collapse
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.
Lokifish Marz said:
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.
Click to expand...
Click to collapse
Merge the patches from the CM7 kernel in to your CM6 kernel then if you don't like the CM7 kernel.
That's the source...
Lokifish Marz said:
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.
Click to expand...
Click to collapse
Why would you want to do this? The kernel from cm7 will boot cm6. The cm7 kernel is not specific to gingerbread.
spiicytuna said:
Why would you want to do this? The kernel from cm7 will boot cm6. The cm7 kernel is not specific to gingerbread.
Click to expand...
Click to collapse
Was having mouse cursor issues when I tried that but not on the stock alpha3.
Also... Rather than wasting time porting HDMI back to an old rom, why not work on a patch for pointer support in CM7?
Lokifish Marz said:
Was having mouse cursor issues when I tried that but not on the stock alpha3.
Click to expand...
Click to collapse
ahh; then merge the patches from the CM7 hdmi opensource kernel into your CM6 kernel and you'll be golden...but then the question starts to be why not work on porting the hid/mouse support from cm6 to cm7 which seems like the more logical choice of time to benefit all as most people aren't going to want to fall back to cm6.
spiicytuna said:
ahh; then merge the patches from the CM7 hdmi opensource kernel into your CM6 kernel and you'll be golden...but then the question starts to be why not work on porting the hid/mouse support from cm6 to cm7 which seems like the more logical choice of time to benefit all as most people aren't going to want to fall back to cm6.
Click to expand...
Click to collapse
I agree that it does make more sense try to port hid/mouse to cm7 but I still haven't found/seen a real fix to the slow usb issue on the new kernel. My linux is also a bit rusty.
As a reminder, since that build is no longer distributed, the source no longer needs to be made available. The GPL only requires source availability on distribution. If you didn't retrieve the source when the distribution was made available, there's no requirement for kernel devs to go and find a valid point of reference after the fact.
When the alphas were released, the kernel source was made available. The links to the source were removed at the same time the primary distribution link was removed.
agrabren said:
As a reminder, since that build is no longer distributed, the source no longer needs to be made available. The GPL only requires source availability on distribution. If you didn't retrieve the source when the distribution was made available, there's no requirement for kernel devs to go and find a valid point of reference after the fact.
When the alphas were released, the kernel source was made available. The links to the source were removed at the same time the primary distribution link was removed.
Click to expand...
Click to collapse
Oh well. Back to square one.
My memory is a little fuzzy, but I'm pretty sure that we were recommending a 2.6.34 kernel with Alpha 3. It took me but a few minutes to come up with:
https://github.com/toastcfh/cm-kernel/tree/android-msm-2.6.34/
Of course, this kernel has it's own "sleep bug" in that it doesn't let the phone go to sleep at all. Not exactly good for battery life, but you're welcome to fork it and make your own changes.
Use the switch branches dropdown if you want to try one of toastcfh's various 2.6.35 branches instead, but I'm pretty sure those have the USB bug.
Dees_Troy said:
My memory is a little fuzzy, but I'm pretty sure that we were recommending a 2.6.34 kernel with Alpha 3. It took me but a few minutes to come up with:
https://github.com/toastcfh/cm-kernel/tree/android-msm-2.6.34/
Of course, this kernel has it's own "sleep bug" in that it doesn't let the phone go to sleep at all. Not exactly good for battery life, but you're welcome to fork it and make your own changes.
Use the switch branches dropdown if you want to try one of toastcfh's various 2.6.35 branches instead, but I'm pretty sure those have the USB bug.
Click to expand...
Click to collapse
Sounds like a game of pick your poison....what do you want more and what can you live with?
spiicytuna said:
Sounds like a game of pick your poison....what do you want more and what can you live with?
Click to expand...
Click to collapse
That's my kinda game!
[ 02/09/2012: Screen Flicker / Brightness is an issue. I'll be looking at it. ]
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time and built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Moving forward into CM9/ICS, some changes need to happen to the kernel over time. The migration kernel is found in a branch: "L27.13.1-ICS". The END result of this will be a kernel / source that fully support hw codecs for ICS.
[02/08/2012] FLASH ZIP FOR THOSE RUNNING NIND'S BUILDS: http://bit.ly/xYOf0V
The following ROM is built from the sources at GitHub under the KFire-Android org. Many of those files and configurations are the result of countless hours of development by JackpotClavin. I don't want there to be any confusion as to who put in a ton of time getting this to work.
[02/09/2012] FULL ROM INSTALL: http://bit.ly/ygVvQB
Changelog:
- Screen flicker IS an issue right now. Digging into it
- Touchscreen "Slop" set to 16. This should help touches register on the touchscreen.
- Working Data usage stats (xt_qtaguid / xt_quota2 kernel modules)
- TUN, CIFS support
- USB mounting fixes
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
nind said:
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
Click to expand...
Click to collapse
If you want to follow a very good step by step guide for setting this up the same way TI (the CPU maker) intended, then follow this:
http://www.omappedia.com/wiki/PandaBoard_L27.12.1-P2_Release_Notes#Setting_up_build_environment
Obviously, that's for PandaBoard, but the Toolchain source and setup are very good.
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Hashcode said:
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time nd built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter2_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Tonight, I'll go back to both of my in-progress kernels and do some testing to see if they'll boot.
EDIT:
Current issues being looked at with this kernel:
- Power off doesn't really power all the way down. It goes to a black screen, but requires long press to turn off.
- Deep sleep isn't happening. The backlight is on a tad while the screen should be off.
But this config is still MUCH better than trying the original.
Click to expand...
Click to collapse
So does this boot cm7 or anything? My kernel builds boot stock kindle but not cm7
Its something to do with netd/dnsproxyd. Just finding a fix that works is a PITA common issue, but then people dont say how they fixed it..
Right now ive only tested this with CM9
Sent from my DROID RAZR using XDA App
touch points
Any chance you're looking into enabling more than 2 touch points in this kernel?
foxdog66 said:
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Click to expand...
Click to collapse
I'm running nind/sitic's cm9-02-04 build with this kernel baked in. I, too, have Stay Awake disabled in Developer Options, and my Kindle is going into deep sleep. I am experiencing the power down issue, though.
It's something I'm absolutely willing to live with for the time being. This is good stuff. Thanks Hashcode!
jabdo79 said:
Any chance you're looking into enabling more than 2 touch points in this kernel?
Click to expand...
Click to collapse
Thats really the future of this kernel. I needed a solid base to start from.
Sent from my DROID RAZR using XDA App
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Right now the difference between this kernel and stock is:
- About 8 ip6 netfilter modules were added
And that's about it.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
wdfowty said:
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
Click to expand...
Click to collapse
ill look into insectraven's cm kernel thanks!
Edit: That worked! Thanks!
he starts the dnsproxyd differently than what I've seen. But it works!
So I noticed that /mnt/ is mounted read-only which causes issues with apps installing to the sdcard and probably the issue people are having with mounting the sdcard to the computer. Some apps insist on installing to the sdcard (I hate that)
Edit: or do I have this all wrong? Lol I'm no dev remounting it r/w gets the job done.
Is there any websites or anything that you guys would recommend to learn about the Linux kernel and development of it?
Tonight, I went back through and cleaned up my config some more. Removed extra power controls, usb mtp settings and omap mmc host controller (for sd card slot boards).
From my tests, everything deep sleeps correctly and the power off issue is fixed.
https://github.com/KFire-Android/kernel_omap
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
foxdog66 said:
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
Click to expand...
Click to collapse
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Hashcode said:
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Yeah that's cool.
foxdog66 said:
Yeah that's cool.
Click to expand...
Click to collapse
Here's an updated boot.img for nind's 2/5 build:
[ UPDATED OP W/ FLASH.ZIP FILE ]
-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.
Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip
----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.
Good job.
Sent from my Nexus 7 using Tapatalk 4
hello
anyone tried this out ?
feedbacks ?
thanks in advance
pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium
Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!
So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app
I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!
It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.
Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Are you going to try to make CM 10.2?
LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.
LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Thank you for this. I have been flashing RIN kernel after any cm12 I've installed since installing MultiROM. Seems to work too, but the hour long wait to flash a 7mb kernel really bugs me.
Next time I flash a cm12 as secondary I'll give this a go.
Eliminater74 said:
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Click to expand...
Click to collapse
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
aclegg2011 said:
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
Click to expand...
Click to collapse
Yes from what I have tested it works with any Compatible flashable Kernel that unzips and has a boot.img..
The above kernel that I listed on post #1 is Stable but is overclockable, If you dont want that.. Then dont use that one, It was only listed as an Example.
I use that kernel with no problems.. I dont OC my phone, but its nice to have the option to do so.
Ill test out the tootie-pop kernel the next time I feel like messing with my phone.
Now isnt a good time, Im sick, and I have already messed up my linux system and my windows system (windows 10 Enterprise build 9926).. Had to do a fresh install on windows.. my linux doesnt want to let me mount my own drives in gnome.. Says I dont have access do to some error, But I am running Ubuntu Vivid 15.04.. so thats to be expected..
So touching my phone isnt a good idea right now.. I might just end up blowing it up the way my luck is going.
Thanks to the OP. This was a quick and simple fix to a frustrating issue.
Sent from my LG-D851
After doing a little research, and finding out that the MultiRom is pretty much dead. I decided to delete it all together and stick with the one rom that seemed
very stable and likable for me. I wont say what rom that was as to respect all developers on this forum.. So I stopped all testing and experiments dealing with MultiRom..
If the Developer once again decides to post updates and fixes. I will again. try it.. but for now.. I will no longer post any workarounds or help with this MultiRom section anymore...
As you know that thread was closed in the ROM Development section..