AOSIP 9.0 shamu - Nexus 6 Android Development

Hello everyone I managed to build Aosip 9.0 rom for our shamu but the build need some work when I flashed my build I get bootloop so DON'T FLASH IT please only if you know how to help me fix this probleme
DOWNLOAD LINK :
https://mega.nz/#!DmZwEAwJ!mkwTswDbaAkciFIF6rIyNr6y__LQom5aAb6-qmKYvvU
DMESG LOG TXT LINK :
https://gist.github.com/RinGooDz/60569c21d30da4b707735efa2859dd93#file-dmesg-bootloop
@electroshmok told me that the probleme from the dmesg log txt is here :
[ 2.770511] init: Command 'start configstore-hal-1-0' action=late-fs (/init.shamu.rc:72) took 0ms and failed: service configstore-hal-1-0 not found
[ 2.770577] init: Command 'start gralloc-2-0' action=late-fs (/init.shamu.rc:73) took 0ms and failed: service gralloc-2-0 not found
so please to all developers and all who know how to fix this can you please help
- this rom still doesn't boot up so please don't flash it -
help please my first build i tried to fix this myself but this strong for me I'm new to android development @camcory @nitin.chobhe @Wajdi Muhtadi @Neo
Rom source :
https://github.com/AOSiP
Device tree code :
https://github.com/RinGooDz/AOSIP-Device-Tree-for-shamu.git
Kernel tree is from Nitrogen os without any changes : https://github.com/nitrogen-os-devices/android_kernel_moto_shamu.git
Vendor tree is also from Nitrogen os without any changes :
https://github.com/nitrogen-os-devices/android_vendor_motorola.git

You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin

nitin.chobhe said:
You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin
Click to expand...
Click to collapse
I will do it now sir

AmirHRC said:
help please my first build i tried to fix this myself but this strong for me I'm new to android development
Click to expand...
Click to collapse
Perhaps you should do something easier then porting a ROM if you have no experience/skill in doing that.
Judging from your past endeavours this is probably going to lead nowhere if you don't start trying to understand the code and how stuff works.
I can help, but I won't port the ROM for you as I have zero interest in another short lived ROM for shamu.
So as long as you're not going to do serious development with proper links to code and doing own work please refrain from asking me stuff and mentioning me in your threads.

Elektroschmock said:
Perhaps you should do something easier then porting a ROM if you have no experience/skill in doing that.
Judging from your past endeavours this is probably going to lead nowhere if you don't start trying to understand the code and how stuff works.
I can help, but I won't port the ROM for you as I have zero interest in another short lived ROM for shamu.
So as long as you're not going to do serious development with proper links to code and doing own work please refrain from asking me stuff and mentioning me in your threads.
Click to expand...
Click to collapse
you also start from zero bro okey so don't be so serious like this everyone start like this and android development doesn't need a lot of code I managed to build the rom but its stuck at the bootanimation i tried to fix the probleme myself but no success so you will not help okey and its not a shorten lived rom belive me this is my first time building and ineed help from experienced developers like nitin and you if you don't wanna help me its okey but don't broken me

nitin.chobhe said:
You should add the github links for ROM source, your device, kernel, vendor trees.
Nitin
Click to expand...
Click to collapse
sir here you go
Rom source :
https://github.com/AOSiP
Device tree code :
https://github.com/RinGooDz/AOSIP-Device-Tree-for-shamu.git
Kernel tree is from Nitrogen os without any changes : https://github.com/nitrogen-os-devices/android_kernel_moto_shamu.git
Vendor tree is also from Nitrogen os without any changes :
https://github.com/nitrogen-os-devices/android_vendor_motorola.git

AmirHRC said:
you also start from zero bro okey so don't be so serious like this everyone start like this and android development doesn't need a lot of code I managed to build the rom but its stuck at the bootanimation i tried to fix the probleme myself but no success so you will not help okey and its not a shorten life rom belive me this is my first time building and ineed help from experienced developers like nitin and you if you don't wanna help me its okey but don't broken me
Click to expand...
Click to collapse
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.

Elektroschmock said:
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.
Click to expand...
Click to collapse
i did efforts the past 3 day I was trying to fix this but no success if I didn't try I will not tell you help me and you don't want its okey just don't tell me you cant or something like this its my first time and I did what ican to fix this but no success

AmirHRC said:
i did efforts the past 3 day I was trying to fix this but no success if I didn't try I will not tell you help me and you don't want its okey just don't tell me you cant or something like this if you can help me help me its my first time and I did what ican to fix this but no success
Click to expand...
Click to collapse
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104

Elektroschmock said:
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104
Click to expand...
Click to collapse
thank you sir I will start working now thank you very much
sorry for all this I'm still learning and learning from developer like you its amazing

hello every one no luck with aosip but ifinished building havoc os 9.0 the build run smooth but I have some problems when try to make call the phone make system ui reboot iwill try to fix it now if someone can help please help
and also the rom compiled without bootanimation
so give me some time iwill post it as soon as i fix those

Elektroschmock said:
Okay then one Protip from me: You are using a Android O device tree. You are lacking about 50 of my commits to be even bootable on P.
Starting around here: https://github.com/LineageOS/androi...=ff0d752ee1ef7bf3eeed3393475a5451c1e13a62+104
Click to expand...
Click to collapse
i tried what you sad but no chance i think the probleme is from aosip source itried every thing every soulution but no boot
so itried building havoc os 9.0 the phone booted fine from the first try and its run smooth only some problems I will try to fix them

I like aosip, so I build aosip for nexus 4/5 6P.
Yesterday, shamu was also build and booted.
What is the reason you start with o-tree?

Elektroschmock said:
First of all I'm not your bro!
Of course I started at zero. I started as translator for CyanogenMod. Then I learned how to compile stuff, do smaller changes, maintain a already brought up ROM and then finally port Android 8 and 9 for shamu.
I had a lot of people which I could ask for help, but usually I only asked them if I didn't make any progress for days.
You on the other hand try to start on 100 % that is not very promissing to be a success.
I said short lived ROM because I saw a lot of people come and go and most of them were not very persitent.
I never said that I don't want to help at all. I usually try to be helpfull ( I guess some of the other devs know it), but I want to see some efforts from the one who is asking for help.
Click to expand...
Click to collapse
sir can you help me with this
iam trying to make call the phone reboot here is the logcat :
https://gist.github.com/RinGooDz/48c745ad5eb5b3bae541ccd165c535d1
ithink the probleme is here how ican fix it please sir
07-01 21:48:15.210 665 665 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now com.android.dialer: [email protected]
07-01 21:48:15.211 665 665 I Telecom : MissedCallNotifierImpl: reloadAfterBootComplete: user=0: [email protected]
07-01 21:48:15.310 665 665 I Telecom : PhoneAccountRegistrar: SimCallManager queried, returning: null: [email protected]
07-01 21:48:15.452 1594 1594 I TelecomFramework: : Carrier-config changed, checking for phone account updates.
07-01 21:48:15.493 1594 1594 I TelecomFramework: AccountEntry: reRegisterPstnPhoneAccount: subId: 1 - no change
07-01 21:48:15.519 1594 1594 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.android.internal.telephony.GsmCdmaPhone) {53a6f62}
07-01 21:48:15.605 665 1786 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]
07-01 21:48:15.611 1594 1594 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true}] GroupId: ***] with handle: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
07-01 21:48:15.612 1594 1594 I TelecomFramework: PstnIncomingCallNotifier: Registering: Handler (com.android.internal.telephony.GsmCdmaPhone) {53a6f62}
07-01 21:48:15.625 1594 1594 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
07-01 21:48:15.647 665 1835 I Telecom : PhoneAccountRegistrar: Modify account: [ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}]: [email protected]

Caused by: java.lang.ClassNotFoundException: Didn't find class "org.codeaurora.internal.IExtTelephony" on path: DexPathList[[zip file "/system/priv-app/Telecom/Telecom.apk"],nativeLibraryDirectories=[/system/priv-app/Telecom/lib/arm, /system/lib, /system/vendor/lib, /system/lib, /system/vendor/lib]]

voidz777 said:
I like aosip, so I build aosip for nexus 4/5 6P.
Yesterday, shamu was also build and booted.
What is the reason you start with o-tree?
Click to expand...
Click to collapse
Where is Nexus 4 build?
Nitin

nitin.chobhe said:
Where is Nexus 4 build?
Nitin
Click to expand...
Click to collapse
It's sleeping deep in my heart.
...Oh, what a mess. The screen shot is flat.

voidz777 said:
It's sleeping deep in my heart.
...Oh, what a mess. The screen shot is flat.
Click to expand...
Click to collapse
Nice, may be you can share it
Nitin

Related

CM build: "breakfast olympus" fails (Xoom kernel build attempt)

Hi guys,
My Atrix -> Xoom kernel port is complete. This is the nvodm version.
Right now I am trying to make a build of CM 9 based on my kernel and running into lots of hiccups
Yeap I am a noob so please bear with me. I am following the steps from http://wiki.cyanogenmod.org/w/Build_for_olympus, and got stuck at the step "Prepare the device-specific code"
Code:
$ breakfast olympus
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
Device olympus not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_motorola_olympus
CyanogenMod/android_device_motorola_olympus already exists
Syncing repository to retrieve project.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
Fetching projects: 100% (1/1), done.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_olympus'
** Do you have the right repo manifest?
I figure that the script is reaching out to the wrong repo at https://github.com/CyanogenMod/android_device_motorola_olympus
It should probably go to https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Am I right?
How to I correct this problem?
Thanks in advance..
Follow This
http://forum.xda-developers.com/showpost.php?p=21499412&postcount=1
I think that the best way to solve this problem is pm someone that already build a rom from source as you wanna do.
Try to reach MMontuori or EPinter (both really kind and will help for sure) by pm, just a tip hehe.
Hope you can build it, best of luck.
Sorry but this mean that we have a new kernel to get full cm9/10/10.1 roms? W/o All the bugs like the videocam...?
Thanks for the hard work!
from the (M)ATRIX...
Ask epinter, he is such a great guy and he have helped other devs,
Sent from my MB860
Your kernel is booting?
Its a full port from Xoom or you are using the leaked Kernel?
Able to retrieve logs from USB?
Whats your status?
This is very important, because there is another porting project running (http://forum.xda-developers.com/showthread.php?t=2016837) and maybe your kernel source is better to keep up than the one they are trying to port.
Please... communicate!
Thanks!
matbarni said:
Your kernel is booting?
Its a full port from Xoom or you are using the leaked Kernel?
Able to retrieve logs from USB?
Whats your status?
This is very important, because there is another porting project running (http://forum.xda-developers.com/showthread.php?t=2016837) and maybe your kernel source is better to keep up than the one they are trying to port.
Please... communicate!
Thanks!
Click to expand...
Click to collapse
Hey matbarni; take it easy and read the first post, not only the title.
It's not a matter of communication; If you can see the thread of the porting, you'll see some posts from user toyota86, which said he was working but in other branch because he has his reasons for it.
Please don't jump into conclussions and try to help, we all are struggling for an usable kernel; and EVERY help is welcome.
I'm sure any of the developers have contacted him by now or he tried to contact the developers, but he wants to see if anyone can give him a quick tip.
Enough. I'll shut my mouth off
Sorry guys. My mind was hazy when I posted that late last night.
What I meant by "complete" was that it simply built. That's it
Some early sanity testing of my kernel with CM7 resulted in a hang. Yes, I agree with most of you that the next logical thing to do is to flash That ROM and fastboot with my kernel. This can be a quick test. But I am a little suspicious the Bionic libraries may need to be rebuilt as well.
I have already sought advice from our Guru mmontuori and he has told me Kernel modules need to be rebuilt.
SO... lets build the whole she-bang
Raafat said:
Follow This
http://forum.xda-developers.com/showpost.php?p=21499412&postcount=1
Click to expand...
Click to collapse
Thanks!
you will need a build without the errata hack in board config, like the cm10 based on the leak. or build using my jb-olympus-new branch.
you can remove all the kernel modules if your defconfig follows android standard...
jhonnyx said:
Hey matbarni; take it easy and read the first post, not only the title.
It's not a matter of communication; If you can see the thread of the porting, you'll see some posts from user toyota86, which said he was working but in other branch because he has his reasons for it.
Please don't jump into conclussions and try to help, we all are struggling for an usable kernel; and EVERY help is welcome.
I'm sure any of the developers have contacted him by now or he tried to contact the developers, but he wants to see if anyone can give him a quick tip.
Enough. I'll shut my mouth off
Click to expand...
Click to collapse
I did not jump into conclusions.
As you can see, all I posted was questions. And yes, I read what toyota86 posted.
Like "Right now I am trying to make a build of CM 9 based on my kernel and running into lots of hiccups".
The way I am helping is to try to clarify to all users what this post is about.
Thanks for all the support guys
As much as I don't want you guys to be dissapointed, but dont put too much hope as to the outcome of my effort.
Now I have lots on my plate. I will update as I make progress.
thank you
Glad you have been working on this.I tried but abandoned due to insufficient knowledge. atrix was the best buy I've made in years.had it for 3 yes now and thanks to you and others it will live on. Im a trigger happy tester i try every ROM I see and can't wait to try yours.
epinter said:
you will need a build without the errata hack in board config
Click to expand...
Click to collapse
Thank you sir. One question though..
Which errata hack were you referring to? Errata 657451 in the motorola's version of the bionic library? Eg...
In motorola's bionic, we see workarounds like this:
Code:
/* BEGIN MOT GB UPMERGE, a5705c, 12/21/2010 */
# ifdef HAVE_TEGRA_ERRATA_657451
# define __munge_tls(_v) ( ((_v)&~((1ul<<20)|1ul)) | (((_v)&0x1)<<20) )
# else
# define __munge_tls(_v) (_v)
#endif
/* END MOT GB UPMERGE */
Description of this errata:
Code:
config TEGRA_ERRATA_657451
bool "Store bit 20 of CP15 TLS register c13,3 in bit 0"
depends on ARCH_TEGRA_2x_SOC && HAS_TLS_REG
default y
help
This option enables a workaround for the 657451 Tegra 2 errata
which causes unreliable reads from bit 20 of the thread storage
register c13, 3 (used by the __set_tls system call). It stores the
value intended for bit 20 into bit 0 instead; in most user-space
environments, the value saved by __set_tls is an aligned address,
so repurposing bit 0 will not cause ill effects.
In my noob'ish understanding, there is a hardware related bug in our Atrix Tegra 2 SOC that causing data corruption in Thread Local Storage (TLS). Researching this on the net, some ppl were talking about a possibility of a buggy version of this hardware in Atrix. It is also worth noting that this workaround however is NOT present in Stingray's kernel & bionic.
I don't think I remember seeing this workaround in CM's bionic, which is one of my initial concerns..I will look further at home tonight..
Errrrm... Isn't the Bionic a TI OMAP device?
can you post your kernel so others can test it? i have minimal knowledge but would love to help with testing
(Deleted)
quetzalcoatl2435 said:
Errrrm. Isn't the Bionic a TI OMAP device?
Click to expand...
Click to collapse
Bionic is Android's standard C library. Don't worry
toyota86 said:
Hi guys,
My Atrix -> Xoom kernel port is complete. This is the nvodm version.
Right now I am trying to make a build of CM 9 based on my kernel and running into lots of hiccups
Yeap I am a noob so please bear with me. I am following the steps from http://wiki.cyanogenmod.org/w/Build_for_olympus, and got stuck at the step "Prepare the device-specific code"
Code:
$ breakfast olympus
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
Device olympus not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_motorola_olympus
CyanogenMod/android_device_motorola_olympus already exists
Syncing repository to retrieve project.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
Fetching projects: 100% (1/1), done.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/olympus/cm.mk]]: "device/*/olympus/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_olympus'
** Do you have the right repo manifest?
I figure that the script is reaching out to the wrong repo at https://github.com/CyanogenMod/android_device_motorola_olympus
It should probably go to https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Am I right?
How to I correct this problem?
Thanks in advance..
Click to expand...
Click to collapse
How did you solve this? I am trying to build for coconut (SE Live With Walkman) and stuck at breakfast.

Help make kernel for samsung Wave

Please Help make kernel training
and tools needed to put it in this section.
First of all thanks for all Developers ( Oleg_k, Volk204,Rebellos,Tigrouzen, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra,Alberto96
and many others)
Wonderfull tuto by mylove : http://forum.xda-developers.com/showthread.php?t=2276481
There is also one in all badadroid thread, but some links are dead (you have to use their manifest.xml though)
You need : linux 64 bit=>64bit processor (all recent pc have it) (Ubuntu 12.04 64 bit work great)
Some 30Gb on your hard drive (there is 10 Gb to download for whole sources, less for kernel only, and lot of space for /out)
Patience, and knowing code
all recent pc have it
Click to expand...
Click to collapse
In theory... if you have only old Hardware for tests...
I need workaround for 32 bit...
Thanx.
Best Regards
adfree said:
In theory... if you have only old Hardware for tests...
I need workaround for 32 bit...
Thanx.
Best Regards
Click to expand...
Click to collapse
Something interesting i just found https://groups.google.com/forum/#!topic/android-building/xFtX6K42BDE
Compile the compiler, smart
And another,maybe less easy https://github.com/yath/android_prebuilts_gcc_linux-x86-32_arm_arm-linux-androideabi-4.6
BenzoX said:
Something interesting i just found https://groups.google.com/forum/#!topic/android-building/xFtX6K42BDE
Compile the compiler, smart
And another,maybe less easy https://github.com/yath/android_prebuilts_gcc_linux-x86-32_arm_arm-linux-androideabi-4.6
Click to expand...
Click to collapse
Hey benzoX
Step 3 : Preparing Repo
-Run these commands (each line is a command)
erorr not found link >> https://dl-ssl.google.com/dl/googlesource/git-repo/repo > repo
Please give me a new link
meysam.ir said:
Hey benzoX
Step 3 : Preparing Repo
-Run these commands (each line is a command)
erorr not found link >> https://dl-ssl.google.com/dl/googlesource/git-repo/repo > repo
Please give me a new link
Click to expand...
Click to collapse
try to replace "https://dl-ssl.google.com/dl/googlesource/git-repo/repo" by "http://commondatastorage.googleapis.com/git-repo-downloads/repo"

[Developer Only] - L Port [Broken/WIP]

OKay So I thought I would try to port the latest beta of L to our OnePlus One. Never really ported before and mainly followed this thread here: http://forum.xda-developers.com/showthread.php?t=1908008
Currently I have it installing and booting to the boot animation and playing the boot animation (whooo) but thats as far as it goes. Unfortunately usb isn't recognized when I plug it in. Is there any way I can get some sort of log?
Its based on the latest nexus 5 L rom.
here is the zip file. Its broken, under no circumstance should you install this unless you are a developer.
Code:
DO NOT INSTALL IF YOU AREN'T A DEVELOPER
AOSP BASE
PA BASE
Current logcat on boot for PA:
http://pastebin.com/c5J0cmQ8
Can't get logcat on boot for AOSP base
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Nice of you that you even tried it! Maybe you developers should port this together in teamwork? Everybody has problems with L on the OPO, maybe together you can solve them
Did you tried it with OnePlus AOSP?
You guys might benefit from the discussion here:
http://forum.xda-developers.com/showthread.php?t=2829974
Transmitted via Bacon
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
phoenixita said:
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Click to expand...
Click to collapse
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
aeppacher said:
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
Click to expand...
Click to collapse
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
eugenioxx said:
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
Click to expand...
Click to collapse
yes I am. I am posting my attempt at the aosp port with the LPX13D as well. Adb isn't grabbing a logcat for me unfortunately
Hopefully devs can help this would be sweet
Hit Thanks if I Helped
-_-NAMELESS ROM 1+1-_-
Hey man i'm no dev, but I just shared your post on Reddit (r/Android and r/oneplus) hopefully more devs will see this and come assist you I would love a port!
Just like previously mentioned I think you guys would benefit from the discussion in the thread previously posted. Better yet pm the developer who recently tried so you at least rule out some things that may have been previously attempted. Good luck guys
You cant port different version of Android by drag-and-droping system folders.
It'll probably be easier once retail Lollipop is out and open sourced on AOSP project. But TBH Cyanogenmod historically has put out builds really fast for nexus devices and ours is nexus-ish. I'll try my luck with kanging CM once they put something out for the N5 or N6.
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
Ha, no.
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
This
Sent from my X9006 using XDA Free mobile app
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
suraj.das said:
This
Click to expand...
Click to collapse
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Alzoids said:
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Click to expand...
Click to collapse
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
Should have included a "/s" I guess.
Sorry man, but when you are making this big of a switch. Especially different device AND different version of android, there is more that the drag and drop tutorial to this. You actually need to know the languages its developed is so you can find what's wrong with it and in turn, you can create your own fix. (Simple terms here)
Basically, you need to be able to write a compliant device tree and kernel that can compile with the new source.
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
sorry to go off topic but your DP suits the situation lol

[Team Up] [Only Devs] Cm11 for zenfone 5

I have tried to manage to make a build of cm11
Links : http://d-h.st/tuND
But i get status 7 error for this
so i edited my tree a little bit and tried to build again
here's my tree : https://github.com/missesmr/android_device_zenfone5
Kernel : https://github.com/ZenfoneArea/android_kernel_asus_zenfone5
i used X86 deconfig
If anyone can help me , i would be happy
Great! I tried to build with shakalaca's tree, succeed but didnt past the asus oem splash will try today. Will let you know.
deleted
sai dev said:
I have tried to manage to make a build of cm11
Links : http://d-h.st/tuND
But i get status 7 error for this
so i edited my tree a little bit and tried to build again
here's my tree : https://github.com/missesmr/android_device_zenfone5
Kernel : https://github.com/ZenfoneArea/android_kernel_asus_zenfone5
i used X86 deconfig
If anyone can help me , i would be happy
Click to expand...
Click to collapse
http://www.mediafire.com/download/x33wtk1w9ohgm4z/A500CG_PHILZTOUCH_RECOVERY_WW-2.21.40.44.7z
Try this recovery with external sdcard support(ext4 formatted).
If you get status 7, try to wipe data.
X AnwarMov said:
hy @sai dev i'm succesfully build CM 11 from your source
i using asus Zenfone 4 A400CG
THANKS mate , but i found bugs . systemUi has stoped , telephony stoped .
how to fix it mate . ?
anyone can help me ?
Click to expand...
Click to collapse
Can you post logcat please? If you dont know you can search it on google.
deleted
X AnwarMov said:
hii @smgdev logcat in attachments
. i hope anyone help me
Click to expand...
Click to collapse
E/hwcomposer( 177): int hwc_eventControl(hwc_composer_device_1*, int, int, int): unsupported event 1
This is your error. Same as cm11 zenfone 5. Hwcomposer is broken in intel patches so you can try to replace hwcomposer.so file from your original rom and try to flash it again. It is something like hwcomposer.devicecode.so device code is a400cg I guess. I will update you on this. Good luck.
smgdev said:
E/hwcomposer( 177): int hwc_eventControl(hwc_composer_device_1*, int, int, int): unsupported event 1
This is your error. Same as cm11 zenfone 5. Hwcomposer is broken in intel patches so you can try to replace hwcomposer.so file from your original rom and try to flash it again. It is something like hwcomposer.devicecode.so device code is a400cg I guess. I will update you on this. Good luck.
Click to expand...
Click to collapse
Any updates?

Help!! error in choosing lunch omni_device and building the image

hi guys and good day everyone please i ask you help how to solve this error, im building twrp for my phone oppo a71 cph1717 everything is good from syncing to . build/envsetup.sh
and when i enter lunch i got this error
[email protected]:~/twrp$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. omni_CPH1717-user
8. omni_CPH1717-userdebug
9. omni_CPH1717-eng
Which would you like? [aosp_arm-eng] 7
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Cph1717/omni_CPH1717.mk]]: "device/oppo/CPH1717/device.mk" does not exist. Stop.
File "/home/osboxes/twrp/build/tools/roomservice.py", line 109
except IOError, ES.ParseError:
^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: multiple exception types must be parenthesized
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Cph1717/omni_CPH1717.mk]]: "device/oppo/CPH1717/device.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_CPH1717'
** Do you have the right repo manifest?
[email protected]:~/twrp$
its the same error when i pick 8 and 9 please help guys im using
Ubuntu 22.10 Kinetic Kudu please help guys any answer will be appreciated
Hi @Anonymous V
Based on your build logs, it's clearly that you did not provide device-tree in your building environment.
Device-tree including kernel and vendor bloobs are required to build TWRP.
Anonymous V said:
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Cph1717/omni_CPH1717.mk]]: "device/oppo/CPH1717/device.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_CPH1717'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Kindly read this guide carefully from the official site of TWRP
How can I get TWRP for my device? (how to compile TWRP)
We can’t afford to buy every device made and many times certain devices are only available in other countries. TWRP is fully open source, so you can port TWR...
twrp.me
khusika said:
Hi @Anonymous V
Based on your build logs, it's clearly that you did not provide device-tree in your building environment.
Device-tree including kernel and vendor bloobs are required to build TWRP.
Kindly read this guide carefully from the official site of TWRP
How can I get TWRP for my device? (how to compile TWRP)
We can’t afford to buy every device made and many times certain devices are only available in other countries. TWRP is fully open source, so you can port TWR...
twrp.me
Click to expand...
Click to collapse
thanks for reply sir my phone doesnt have a device tree so i created a twrp compatible device tree using the tool Twrpdtgen and i succsessfully created one and i created this first device tree and its seems its alright when i enter lunch and enter 7 it runs successfully but not 8 and 9 because is gives me error, i first did it with kali linux machineand its alright but when i enter mka recovery i got error in building regarding in ninja so i switch into Ubuntu 22.10 Kinetic Kudu and now when i did what i did in the kali linux machine i got this kind of error i follow all the instruction but it really gives me an error and also i tried the pre created twrp compatible device tree in github but it still give error pls help me to fix it sir thanks for your reply.
this the link of the Twrpdtgen -------> https://github.com/twrpdtgen/twrpdtgen
and this one is for the pre created twrp compatible device tree for my device ---------> https://github.com/twrpdtgen/android_device_oppo_CPH1717
khusika said:
Kindly read this guide carefully from the official site of TWRP
How can I get TWRP for my device? (how to compile TWRP)
We can’t afford to buy every device made and many times certain devices are only available in other countries. TWRP is fully open source, so you can port TWR...
twrp.me
Click to expand...
Click to collapse
and this is the tutorial that i followed branch 7.1

Categories

Resources