Develop Bugs

Building roms for Oppo N1

I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.

That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:

Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.

Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475

nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.

I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk

Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.

Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:

viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums

I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank

You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick

Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk

I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.

ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.

mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank

[ROM][WIP][5.0]Android L System Dump Port

Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me

+1 For quick start on this! I currently use toro so it is much appreciated. Just say if you need anything. :highfive:

KShion619 said:
Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me
Click to expand...
Click to collapse
hello can we flash this now?plus it says in build prop that its for maguro

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
I'm sorry, but did you even READ the post you quoted? it says "currently will reboot back to recovery"
so it's not really USABLE, but it's a START towards logs and figuring out what needs to be changed IF it can get to the point of boot& run

its awesome that you got it this far i tried to but it did what you said it rebooted into recovery thank you

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
Its stated as maguro for comparability with apps Verizon blocks, forgot I did that until now technically you can test it til it boots really on any Galaxy Nexus, you just won't gave data

What I've Deducted as of far
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting

^its possible but you need a skilled kernel dev. What I'm thinking (but I'm no dev) would be to decompile the n5 (android L) kernel, compare it to the n5 (kk) kernel, and apply similar changes to the gnex source and compile the kernel.
Just my 2 cents.

http://forum.xda-developers.com/galaxy-nexus/general/porting-android-l-lpv81b-to-tuna-help-t2796203/page3

wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?

KShion619 said:
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting
Click to expand...
Click to collapse
Why not just copy over some of the apps that make up the ui of L and edit the build prop so they act as if they are in an actual l installation?

dreamwave said:
wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?
Click to expand...
Click to collapse
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.

shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
good luck, it would be fantastic to at least get a bit of a port before the official launch so we know what to expect kind of. and are you sure you mean July? That's like a week
---------- Post added at 05:13 PM ---------- Previous post was at 04:56 PM ----------
shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
also if you tell me what the libs are I can try and make a couple decisions for you

Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
I could at least beta test so long as I am allowed to show it off to my friends
also, how is it coming so far? BTW I have the sprint galaxy nexus, so how hard is it to change it from verizon or gsm to sprint after you port them?

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
approximately how far are you two days of?

dreamwave said:
approximately how far are you two days of?
Click to expand...
Click to collapse
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.

I've been working on this as well, from what I can tell, there are unmet dependencies in libc.so, and there are some additional libraries that were added in KK AOSP that don't seem to be in any of the roms I've checked so far, libunwind.so is the major one.

shwise said:
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.
Click to expand...
Click to collapse
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?

dreamwave said:
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?
Click to expand...
Click to collapse
Any progress on this guys?

[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).

[Rom][6.0.0/5.1.1(Not Sure)][DM][OMNIROM Build Modified][BigPart][Alpha]

Hi And Welcome To a Non-Tested Version of Android 6.0.0 on the xoom (Maybe 5.1.1 Not Sure) But back to the topic
This is mostly 5.1.1 but maybe with new of fixed features (I've never tested it as I said)
Here is how to install (I found this on another area)
1. ROOT YOUR DEVICE
2. Install BigPart TWRP
3. Wipe your system and flash the zip file
Here is the zip file
(I'm having Issues of Attaching The File So Please Wait)
XDA:DevDB Information
Android 6.0.0 or Android 5.1.1, ROM for the Motorola Xoom
Contributors
MichaelTech, Schischu, dreamcwli, michie
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
ROM Firmware Required: Rooted BigPart
Based On: OmniRom
Version Information
Status: Alpha
Created 2015-11-19
Last Updated 2015-11-19

so is this rom 5.1.1 or 6.0? id love to try it out...

I just resurrected my old xoom and converted it to bigpart.
waiting for the zip....

Waiting for test it.

Did you build this rom? If so, how can you not know what version of Android it is?

MichaelTech said:
(I've never tested it as I said)
Here is how to install (I found this on another area)
Click to expand...
Click to collapse
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!

sdthelord said:
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
Click to expand...
Click to collapse
Based on this post, I think that, best-case scenario, he just kanged Schischu's 5.1.1 build and maybe themed it to look like 6.0. But I'm betting we never see a zip file.

As with everyone else I am curious to this. [6.0.0/5.1.1(Not Sure)] <--- this seems a little strange. It can only be one Android version. If it's 5.1.1 with some cherry picks and tweaks, that's great but just say.
Also some source would be good so we can establish what it actually is. Upload to androidfilehost or something similar if you can't attach.

P.S OmniRom wanted me to make a rom so perfectly fine

MichaelTech said:
P.S OmniRom wanted me to make a rom so perfectly fine
Click to expand...
Click to collapse
Look we shouldn't be fighting about whos rom it is It's just code that matters

MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Here is the error I keep getting
 vBulletin Message
Invalid post specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
but nothing happened to this page so what is this problem

MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?

brewer75 said:
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
Click to expand...
Click to collapse
I can when you solve my problem I keep having

MichaelTech said:
I can when you solve my problem I keep having
Click to expand...
Click to collapse
The Download is now available in the downloads tab
here is info
Modified Launcher3
Modified SoundRecorder
Modified PackageInstaller
Android 5.1.1 with tweaks
gapps and super su are not included so please download them

If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.

michie said:
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
Click to expand...
Click to collapse
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder

Download not possible. File not found.

MichaelTech said:
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Click to expand...
Click to collapse
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.

michie said:
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
Click to expand...
Click to collapse
I mostly belive its android 5.1.1

MichaelTech said:
im a level 8 of 10 coder
Click to expand...
Click to collapse
How many more XP do you need before you level up to 9?
What a joke...

Question Has Anyone Compiled AOSP 13 and Booted It?

I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.

GrapheneOS has test builds up for A13, which should be buildable using the normal approach. Also hardened with some extra security features.

Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.

I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com

Schnedi said:
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help

liggerz87 said:
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
Click to expand...
Click to collapse
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it

Schnedi said:
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Click to expand...
Click to collapse
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}

alvin14 said:
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
Click to expand...
Click to collapse
Update on this for ArrowOS. After removing connectivitythernmalmanager that fixed the issue as i am getting selinux denials with it, everything works, been testing for a few days.

alvin14 said:
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
Click to expand...
Click to collapse
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot

Schnedi said:
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Click to expand...
Click to collapse
Do a logcat during boot, will definitely help with that.

card13 said:
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
Click to expand...
Click to collapse
There is a build of Hentai which is very good. You can even dirty flash from stock

alvin14 said:
Do a logcat during boot, will definitely help with that.
Click to expand...
Click to collapse
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?

Schnedi said:
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Click to expand...
Click to collapse
Adevtool. The other one works as well however i need to clean it up a bit.

hi guys,
@Schnedi what gapps package are you using for prime?
And does udfps work on your raven with your prime base?

Well, after a dozen of test builds, I finally made it work
Still have to fix things tho

Schnedi said:
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Click to expand...
Click to collapse
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?

ny-hardcore said:
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
Click to expand...
Click to collapse
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it

Schnedi said:
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Click to expand...
Click to collapse
Thanks for the reply, i spark gapps too by the way haha
i picked udfps myself so had it working already
i like your vendor /vendor/extras very clean setup.
i know how to fork, but no need for now