Hello Guys,
I've been building find7 for one year (for crdroid tteam mainly) and since yesterday i'm facing a strange issue building:
error message:
----- Making boot image ------
error: could not load device tree image '/home/jejecule/crdroid2/out/target/product/find7/dt.img'
make: *** [/home/jejecule/crdroid2/out/target/product/find7/boot.img] Error 1
I downloaded pure cm12.1 source, made the same test and exactly the same error
Reverted last sepolicy cm-vendor commits, same issue, changed kernel, same issue...
Anyone facing the same with cm based rom with this device?
Thanks guys
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
suraj.das said:
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
Click to expand...
Click to collapse
Hey my friend, did not notice that Find7 had his own kernel...maybe it's why...
How are you? and you tipsy builds?
See U soon.
Cheers
Jerome
Oppo find7 can running cm ROM based use caf kernel and caf ROM?
Sorry for my English.
Related
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!
Hi Everyone,
I've built Cyanogenmod with CM made patches to include the latest kernel from Oppo's Project Spectrum, thereby supporting the new Find 7 LCD panels. Please make backups and let your fellow Android flashaholics know your results.
This build is for LVM storage only.
Known issues:
The standard CM updater will likely break this modified rom. Please only update by flashing builds from this thread.
Sources:
Cyanogenmod Github
Patch #1
Patch #2
Wuxianlin's LVM device tree
Download:
cm-13.0-20160303-UNOFFICIAL-find7s.zip - Current
cm-13.0-20160301-UNOFFICIAL-find7.zip
THIS IS AN EXPERIMENTAL AND POTENTIALLY UNSTABLE BUILD - ALWAYS BACKUP.
I'll keep uploading builds if there's enough interest. Please post feedback below.
So you have tested them or not?
maxwen said:
So you have tested them or not?
Click to expand...
Click to collapse
My results were that Cyanogenmod booted fine, but I'm on LVM so couldn't test properly. I haven't tested Nameless out yet but will next chance I get.
Slightly unrelated - Thank you for getting OmniRom on a kernel with the new LCD support so early, you've saved my Find7 for these past few months!
Pojiku said:
My results were that Cyanogenmod booted fine, but I'm on LVM so couldn't test properly. I haven't tested Nameless out yet but will next chance I get.
Slightly unrelated - Thank you for getting OmniRom on a kernel with the new LCD support so early, you've saved my Find7 for these past few months!
Click to expand...
Click to collapse
Hi, install and boot works fine, display works fine, but not LVM supported
Anyway thanks for your work, i will wait for new build with lvm support.
Thanks :good:
Since Nameless had a few issues I don't have the time to fix, I've decided to focus on Cyanogenmod builds.
The latest CM build (2015-03-03) fixes screen gestures and switches to LVM storage.
Could you build for x9007/6?
Отправлено с моего Find7 через Tapatalk
Pojiku said:
Since Nameless had a few issues I don't have the time to fix, I've decided to focus on Cyanogenmod builds.
The latest CM build (2015-03-03) fixes screen gestures and switches to LVM storage.
Click to expand...
Click to collapse
Yeah it works! I have found only a serious bug: i have no sounds of any kind: no music, notifications, etc.
Everything else works or seems to works fine: 4g, wifi, calls, everything.
Thanks so much for the rom, long time waiting for this.
Pojiku said:
Slightly unrelated - Thank you for getting OmniRom on a kernel with the new LCD support so early, you've saved my Find7 for these past few months!
Click to expand...
Click to collapse
You are welcome - if you have any more questions just contact me
I've flashed this rom and from my experience, the only real bug that is here is the fact that sound does not work at all unless using headphones. Could you by any chance port MaxxAudio from the original ColorOS onto this or the Camera?
Pojiku said:
...I'll keep uploading builds if there's enough interest. Please post feedback below.
Click to expand...
Click to collapse
Hi Pojiku.
Good job man. Don't wait if there wiil be interest to upload builds. Go my friend because i'm sure many find 7's owners are waiting for this impatiently in particular those who own a find 7 with new lcd panel like me. I m on omni, it s a very good rom with a very good dev. Today due to an incompatibility, i m forced to stay on an old omni build and cannot update. So i think that your rom could be a solution for me. I will wait a new build fixing the sound issue and be sure i will flash your rom to test it.
Thank you for your invest and your time.
Good luck.
---------- Post added at 05:54 AM ---------- Previous post was at 05:47 AM ----------
Thank you for getting OmniRom on a kernel with the new LCD support so early, you've saved my Find7 for these past few months!
Click to expand...
Click to collapse
that goes for me too. Without maxwen I'll still be on color os or spectrum both of which are bugged.
Thanks Max
Hi Pojiku
I ve tried the lastest build and i m vey exciting. Please continue your work and release a new build to fix the sound issue.
Can't wait lol.
Due to lack of Clear Kernel Source, this thread is in violation of GPL License as well as XDA Rules. Hence it is closed.
OP Check your PM and respond in order to get it reopened.
Hello, guys.
I have a problem with building Paranoid on my D855 device, here's a log: https://pastebin.com/raw/EUZfeFgg
I put https://github.com/xiaolu/mkbootimg_tools already and that fixed dt.img problem, but there's next one with ramdisk-recovery.img (or recovery.img).
Can you help me?
What was your first error, show your device and common tree, show your local_manifest.
ppajdek said:
What was your first error, show your device and common tree, show your local_manifest.
Click to expand...
Click to collapse
the first error was the same, but instead of ramdisk-recovery.img/recovery.img was just dt.img
https://github.com/LineageOS/android_device_lge_d855
https://github.com/LineageOS/android_device_lge_g3-common
https://github.com/LineageOS/android_kernel_lge_g3
https://github.com/TheMuppets/proprietary_vendor_lge
these are all that I use
You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it
ppajdek said:
You must make device tree compatible with PA source.
https://github.com/AOSPA/android_vendor_pa/tree/nougat-caf/products
https://github.com/AOSPA/android_device_lge_d855
https://github.com/AOSPA/android_device_lge_g3-common
its old brach but get you idea
compare it to ex. "bacon" and make necessary changes
Im syncing PA right now, will try to build it
Click to expand...
Click to collapse
wielkie dzięki, spróbuję. można jakiś bliższy kontakt (telegram, whatsapp)?
(thank you so much, I am going to try it)
Not asking for an ETA, but just wondering what we can expect in the future.
As of now, the only custom ROM in the Development section is the OOS-based FreedonOS.
A lack of AOSP-based ROMs is the only thing holding me back from using this as my daily phone.
I believe several groups are working on their AOSP firmwares for this phone. It's still pretty new and nobody wants to release a crap product out of the gate.
I know one very popular group for sure is (they're dirty ?).
I'm hoping for lineage and aospa support. Pretty sure lineage will reuse their oneplus5 rom. It's basically the same phone just with another display. With aospa we'll have to wait until the Oreo update is out. I don't expect anything new from them before that.
I am especcially waiting for Ressurection Remix
Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.
GZOSP just added a dumpling section for devices so there's some hope for Validus. We'll have to wait for full development though since I don't think we'll have unified builds.
x111 said:
Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.
Click to expand...
Click to collapse
The device is what, 2 weeks old? You expect development to be at the level of a 3 year old device? You may need to lower your expectations a bit.
Sent from my Pixel XL using Tapatalk
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Check with @darkobas, he got his kernel to boot.
varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:
DocRambone said:
Check with @darkobas, he got his kernel to boot.
Click to expand...
Click to collapse
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Tiz92 said:
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:
Click to expand...
Click to collapse
Yes I got my device 2 days back
varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/
DocRambone said:
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/
Click to expand...
Click to collapse
Thank you buddy .will give this a try
EDIT: got stuck with this annoying error
Code:
INSTALL usr/include/asm-generic/ (35 files)
/home/varun/RR/kernel/oneplus/msm8998/scripts/Makefile.headersinst:55: *** Missing UAPI file /home/varun/RR/kernel/oneplus/msm8998/include/uapi/linux/ashmem.h. Stop.
make[2]: *** [linux] Error 2
make[2]: *** Waiting for unfinished jobs....
INSTALL usr/include/drm/ (21 files)
INSTALL usr/include/misc/ (1 file)
INSTALL usr/include/media/ (21 files)
make[1]: *** [headers_install] Error 2
make[1]: Leaving directory `/home/varun/RR/out/target/product/dumpling/obj/KERNEL_OBJ'
make: *** [sub-make] Error 2
make: Leaving directory `/home/varun/RR/kernel/oneplus/msm8998'
[ 36% 930/2537] target C: libc_openbs...tream-openbsd/lib/libc/string/strspn.c
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
Maybe ask some of the big guys of LOS
varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
Nice to have you around... What device tree did you try use?
varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe
dcd1182 said:
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe
Click to expand...
Click to collapse
Hi do you have a working device tree ? Mines messed up
jgcaap said:
Nice to have you around... What device tree did you try use?
Click to expand...
Click to collapse
I tried the NastyAndroidDevs device tree from lineage 15.0 branch
I'm new to rom building. While I was trying to build roms on ubuntu 18.04, some errors occurred. I've cloned device, vendor, kernel and etc of z2 in the building directory and I've recynced the source code ofroms many times. Could anyone tell me what's wrong? Thx very much
And here's the screenshot: