Develop Bugs

any good news for cm11?

if cm11 out i will buy one
Sent from my Moto G using Tapatalk

I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.

Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)

TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel

Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:

u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...

We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???

Can't wait to try CM

kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards

I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a

Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available

@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.

Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img

Nope, doesn't seem to boot :/

munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse

munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!

Sweet, with or without display?

crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.

munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!

[ROM][For GEEHRC][GPROJ][5.1.1][UNOFFICIAL] CM 12.1 + Nitrogen project (NPROJ) ALPHA

The project is based on Cyanogenmod 12.1.
At the moment, compiled alpha version of the firmware 12.1 CM + NPROJ.
Place it just after you make a backup of all data.
What is now present in the firmware:
Driver stock camera, no differences photos from photos taken at the drain, everything works, panorama, skype, etc. The runoff when you press the shutter release triggers auto-focus, so now it is 12.1 CM!
New initlogo.
I actually Russian, and accordingly made Russian the default language (forgive me for that please )
Disabled ADB secure.
Tweaks build.prop (to improve the quality of the photos).
Disabled block Assembly firmware, easily installed on the system, which has a size less than 2 GB (Yes, you can pick zip).
Bugs, jambs (it's not I made them):
Not working cyanogen setup wizard.
Crash software.
You can see the green demigod "AP Watchdog bark detected!" (crash software).
If you see a black demigod (this is the crash kernel), let me know.
Incorrectly read Bluetooth MAC address (Skite how to fix if anyone knows, my brain is not enough).
Source code: https://github.com/nitrogen-project
Attention! Immediately after installation to put Nitrogen Kernel!
Download: https://yadi.sk/d/GqqvKSddenX5R/Cyanogenmod/Cyanogenmod 12.1/Alpha

Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.

Nice work @Mr.MEX, you've really got the point with this ROM.

akahroba said:
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Click to expand...
Click to collapse
Well or through twrp to delete CyanogenSetupWizard.apk
Loller79 said:
Nice work @Mr.MEX, you've really got the point with this ROM.
Click to expand...
Click to collapse
Thanks
P.S. Now compile the version from today, let's see, did they issue the green demigod's.
Well, fix WiFi (From mako N4) added.

Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?

@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.

If I disconnect the cellular network and WiFi lose imei ... how come?

I often appears green screen "AP watchdog detected shoulder." What causes this error?

guidoido004 said:
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
Click to expand...
Click to collapse
Yes, but this alpha no the second alpha will be delivered.
akahroba said:
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
Click to expand...
Click to collapse
The fix does not work on version 5.
zed923 said:
If I disconnect the cellular network and WiFi lose imei ... how come?
Click to expand...
Click to collapse
But from now on more.
st4ik said:
I often appears green screen "AP watchdog detected shoulder." What causes this error?
Click to expand...
Click to collapse
Curves hands of the guys from CM.

I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it

akahroba said:
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
Click to expand...
Click to collapse
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.

Mr.MEX said:
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Click to expand...
Click to collapse
Can you also send a pull request to cm team to add the camera libs?

Attached Wallpaper, initlogo, bootanimation - will be in the next version.

akahroba said:
Can you also send a pull request to cm team to add the camera libs?
Click to expand...
Click to collapse
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.

Mr.MEX said:
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Click to expand...
Click to collapse
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/

It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]

akahroba said:
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
Click to expand...
Click to collapse
So he's euphoria compiles, CM hates...

dadi11 said:
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
Click to expand...
Click to collapse
Um for one thing, they don't add a vendor for the devices in the source - this may be the reason why they don't add fix for camera + need to make commits to the kernel (the driver from the runoff).

[KERNEL] -> tegra-3.18_unified_dragon_kernel_11_v201218 (DISCONTINUED)

Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy

flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.

dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14

followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.

Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!

New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers

followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/

redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers

Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.

nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks

followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/

followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.

redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.

nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img

redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.

NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:

NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?

redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !

followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!

Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers

Building CypherOS for Pixel xl

I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.

cm11noob10 said:
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
Click to expand...
Click to collapse
Any news on this awesome rom?

Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.

cm11noob10 said:
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk

liam_davenport said:
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.

cm11noob10 said:
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
Click to expand...
Click to collapse
What linux distro are you using?

liam_davenport said:
What linux distro are you using?
Click to expand...
Click to collapse
Ubuntu. I have problems running Arch in a VM without scaling issues.

cm11noob10 said:
Ubuntu. I have problems running Arch in a VM without scaling issues.
Click to expand...
Click to collapse
Try this: sudo apt-get install linux-headers-generic

liam_davenport said:
Try this: sudo apt-get install linux-headers-generic
Click to expand...
Click to collapse
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.

I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).

If you get it working I could try my hand for the sailfish

YTSec said:
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
Click to expand...
Click to collapse
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
ChongoDroid said:
If you get it working I could try my hand for the sailfish
Click to expand...
Click to collapse
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.

cm11noob10 said:
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
Click to expand...
Click to collapse
I'll give it a try tonight when I can, and see if I get anywhere. Would be nice to at least get the music detection working somehow.

U may need to use a newer kernel tree to compile I did but I also had to update toolchain its what I did

cm11noob10 said:
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
Click to expand...
Click to collapse
Have you been able to get it compile and boot?

Zehlek said:
Have you been able to get it compile and boot?
Click to expand...
Click to collapse
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.

cm11noob10 said:
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
Click to expand...
Click to collapse
Maybe you and @joeeboogz can work together. It would be an awesome rom

U have to update toolchain to ur computer then compile and add zip to tree then add toolchain line to board config I think I forgot which file to edit

Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.

YTSec said:
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
Click to expand...
Click to collapse
do you have aoscp.mk in your device tree?
i came across this tread because i want to use a prebuilt kernel and im getting the error "ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/sixohtew/bliss/out/target/product/taimen/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it" and saw someone had a previous error.. im trying to build for taimen obv which is the pixel 2 xl and it has an aosp prebuilt kernel and my rom wont compile any other kernels so i was looking for some help

[Kernel][LOS/CAF][M/N] Linux 3.10 custom kernel v3

Linux 3.10-based kernel for Oneplus One (bacon)
Info:
use this kernel at your own risk. Flashing it the wrong way might brick your device. I'm not responsible for any software/hardware damage.
This kernel is based on top of erorcun's 3.10 kernel. erorcun has spent an enormous time working on this project and he deserves a huge "Thank you" for having succeeded in one of the most difficult tasks in Android development: upgrading a device to a newer Linux release.
Features:
v3 (12th December)
built with O3 optimizations
CAF CPU boosting driver (replaces cpu_input_boost - might be a temporary switch)
kernel code base updated to Linux 3.10.60
sdcardfs updates
minor miscellaneous improvements
old releases:
v2.1
minor stability fix
v2 (12th November)
kernel code base updates reverted, then re-applied only up to 3.10.54
compiled with an improved set of GCC flags
tuned AIO for SSD-only machines
v1 (30th October)
built with GCC 5, UBER Toolchain and the optimal compiler flags for Krait CPUs
kernel code base upgraded to Linux 3.10.88
power-efficient workqueues
sound control by francisconfranco
CPU voltage control
cpu_input_boost by Sultanxda
sdcardfs & f2fs support
support for both LineageOS's and Sultan's camera HALs
Compatibility
The kernel is compatible with all the Marshmallow/Nougat ROMs that use either LineageOS's camera HAL or Sultan's (a.k.a. CAF's). Just make sure you download the right version
Currently, the kernel has been tested only on LineageOS 14.1, but I'm sure the CAF build is safe to flash and works properly as well.
The kernel doesn't work on Oreo (yet)!
Download
The kernel can be download from AFH: 3.10 kernel on AndroidFileHost
Thanks to:
erorcun, franciscofranco, Sultanxda, CAF & UBER, Mecca EL.
XDA:DevDB Information
Tom's Linux 3.10 kernel, Kernel for the OnePlus One
Contributors
Tomoms, erorcun
Source Code: https://github.com/Tomoms/neon_kernel_bacon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2017-12-12
Created 2017-10-30
Last Updated 2017-12-12

thanks man! any plans on oreo version?

criminality said:
thanks man! any plans on oreo version?
Click to expand...
Click to collapse
Everything will come in due time
It's one of the things I'll work on soon. Be patient, and you'll eventually get what you want

Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.

Fatsodonkey said:
Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.
Click to expand...
Click to collapse
Could you tell me the exact resolution you used?

Tomoms said:
Could you tell me the exact resolution you used?
Click to expand...
Click to collapse
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.

Fatsodonkey said:
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.
Click to expand...
Click to collapse
I'll compare the camera driver present in this kernel and the one in Sultan's kernel, then try to fix this. Unfortunately at the moment this is the best thing we can achieve, CAF camera support had always got some small problems even in erorcun's build if I recall correctly, and these problems are inevitably "inherited" by my kernel.

Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.

Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
What about encryption? Are your TWRP able to decrypt data with this kernel?

Tomoms said:
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.
Click to expand...
Click to collapse
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
TbMa said:
What about encryption? Are your TWRP able to decrypt data with this kernel?
Click to expand...
Click to collapse
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.

Mecca EL said:
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.
Click to expand...
Click to collapse
Well i am using encryption since early MM and not a single problem if developer of rom and kernel did his work fine. Biggest payoff its hit battery.
Unfortunately you cant revert encryption without formating whole internal storage, so its a little bit complicated with backups and etc

MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.

SirSoviet said:
MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.
Click to expand...
Click to collapse
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?

Tomoms said:
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?
Click to expand...
Click to collapse
I never record videos, so I don't know. I'll check later today.

@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).

Mr.Ak said:
@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).
Click to expand...
Click to collapse
Thank you for letting me know. I'll immediately update the thread.

SirSoviet said:
I never record videos, so I don't know. I'll check later today.
Click to expand...
Click to collapse
Nothing wrong with video recording here.

SirSoviet said:
Nothing wrong with video recording here.
Click to expand...
Click to collapse
Hmm... I'll try it myself soon. In the meantime, my main concern will be fixing MTP, and it won't take me too much, fortunately.