[ROM][OFFICIAL][9.0]POTATO OPEN SAUCE PROJECT [POSP v2.3][WEEKLIES]

[kush57]

@kush57

Hi, thanks for this ROM.

1) Are there any build instructions available for it?
2) Can it be compiled with su baked in, i.e. "export WITH_SU=true" like LineageOS seems to?

If you're going to try build for yourself those would be unofficial builds so u might lose some official features . Except tht there's no specific instructions and nope there's no su support in official builds

 

[kush57]

All the best for your exams:good:

Can you pl add vibrator strength option in future builds?
Tnx.

Thanks man ? yep I'll put it on the list

 

[Kenaestic]

Really love seeing this device still supported. You're the hero we need but don't deserve. Keep it up!

 

[stef204]

If you're going to try build for yourself those would be unofficial builds so u might lose some official features . Except tht there's no specific instructions and nope there's no su support in official builds

Thanks for quick answer.
Any builds I would make from source code would obviously be unofficial., not a problem, I would not redistribute.
Re. root/su. the question is not can the official rom be built with "export WITH_SU=true" but can an unofficial build from source be built that way?
What "official features" would I lose? Is it not all the same source code?

 

[stef204]

Building from Source - local_,manifests.xml

@kush57

Hi,
I've downloaded the POSP source, following this.
Could you please provide guidance as to this step:

Define all relevant device repositories in .repo/local_manifests/local_manifests.xml

I've used this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="PotatoDevices/device_oneplus_onyx" path="device/oneplus/onyx" remote="github" />
  <project name="PotatoDevices/kernel_oneplus_onyx" path="kernel/oneplus/onyx" remote="github" />
  <project name="PotatoDevices/vendor_oneplus_onyx" path="vendor/oneplus/onyx" remote="github" />
</manifest>

Not sure if this is enough--and not sure about the vendor--I have already extracted the blobs from my device running LOS--but perhaps using the ones defined above is best?

Thanks, much appreciated.
PS If this is not the proper forum for advice for building from source for this device, please let me know which you prefer (I am not a Telegram user at the moment which is why sticking to this forum. I have now joined the Telegram channel.)

 

[kush57]

@kush57

Hi,
I've downloaded the POSP source, following this.
Could you please provide guidance as to this step:

I've used this:



Not sure if this is enough--and not sure about the vendor--I have already extracted the blobs from my device running LOS--but perhaps using the ones defined above is best?

Thanks, much appreciated.
PS If this is not the proper forum for advice for building from source for this device, please let me know which you prefer (I am not a Telegram user at the moment which is why sticking to this forum. I have now joined the Telegram channel.)

Local_manifest looks okay even if it fails roomservice will kick in and check the dependencies . If you need any help pm me . And using the pre defined blobs works if you want you can try yours too tht won't make much of a difference

 

[stef204]

Local_manifest looks okay even if it fails roomservice will kick in and check the dependencies . If you need any help pm me . And using the pre defined blobs works if you want you can try yours too tht won't make much of a difference

For it to actually work, I had to modify the local_manifests.xml to:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="PotatoDevices/device_oneplus_onyx" path="device/oneplus/onyx" remote="github" revision="baked-release" />
  <project name="PotatoDevices/kernel_oneplus_onyx" path="kernel/oneplus/onyx" remote="github" revision="baked-release" />
  <project name="PotatoDevices/vendor_oneplus_onyx" path="vendor/oneplus/onyx" remote="github" revision="baked-release" />
</manifest>

i.e. add the revision (received that tip in the TG channel.)

Posting that for the sake or accuracy, for anyone which may read this thread (at least that's what worked for me.)
Also, while I had no trouble at all downloading the LOS source, for POSP I had to do this:

sysctl -w net.ipv4.tcp_window_scaling=0

And use

repo sync -j1

Not sure if it's because I tried too many times and my IP got throttled by Google's servers at the time or something else. My connection was stable and very fast but still failed when using

-j8

until I used the above 2 "tricks", taken from here.

I also understand now that, unfortunately, the variable

WITH_SU=true

is NOT an AOSP implementation but an LOS one. So that seems to answer my previous question above in the thread.

I will end off on this "building from source issue" as this is the OFFICIAL thread and I do not want to digress and go off-topic. I will PM you to get some feedback/assistance if I have questions or hit a snag I cannot debug during build (will keep it very succinct.)

Thanks again. :good:

 

[kush57]

For it to actually work, I had to modify the local_manifests.xml to:



i.e. add the revision (received that tip in the TG channel.)

Posting that for the sake or accuracy, for anyone which may read this thread (at least that's what worked for me.)
Also, while I had no trouble at all downloading the LOS source, for POSP I had to do this:


And use

Not sure if it's because I tried too many times and my IP got throttled by Google's servers at the time or something else. My connection was stable and very fast but still failed when using until I used the above 2 "tricks", taken from here.

I also understand now that, unfortunately, the variable is NOT an AOSP implementation but an LOS one. So that seems to answer my previous question above in the thread.

I will end off on this "building from source issue" as this is the OFFICIAL thread and I do not want to digress and go off-topic. I will PM you to get some feedback/assistance if I have questions or hit a snag I cannot debug during build (will keep it very succinct.)

Thanks again. :good:

That's a very rare case . I had never faced tht issue during repo sync. But still if it works for you then well & good ?. And yep for build issues PM . ?

 

[Kenaestic]

Edit: wrong thread, sorry.

 

[Mchasard]

I just Saw a New build dd 280519 ...whabout batterry life?

 

[Darren Lim]

I just Saw a New build dd 280519 ...whabout batterry life?

Battery life is decent.
Thanks Kush!

 

[kush57]

Is anyone facing any errors in the latest build? Sorry for the delay
This thread will be updated soon

 

[kush57]

I want to have a poll how many of you guys want an enforcing build or is permissive okay for you guys?

 

[Darren Lim]

Is anyone facing any errors in the latest build? Sorry for the delay
This thread will be updated soon

Been using for a day. Didn't really experience any bugs. Overall is smooth

 

[Mchasard]

Battery life is decent.
Thanks Kush!

Really décent battery compare to thé previous build thanks but no swipe for keyboard pity

 

[koi1843]

Did a clean flash.
Flashlight ain't working for me. It's greyed out.

 

[tmq_one]

Did a clean flash.
Flashlight ain't working for me. It's greyed out.

Not only flashlight. Every app which uses camera. Face unlock also doesnt work. Any solutions?

 

[Mchasard]

Not only flashlight. Every app which uses camera. Face unlock also doesnt work. Any solutions?

I confirm whatapps could not work with camera mode pity back to bootleggers rom

 

[Entry_Plug]

Hi.

Am I the only one with camera issue ?
I've just installed the ROM (its perfect !). When I launch the camera app, I have the permission windows that pop. I accept the four permission and then black screen.
Now, when I want to launch the app, its crash with this popup : Unkown error.

Any idea to fix it ?

 

[tmq_one]

Can someone also tell me how to fix google sounds? I tried to downgrade version to 2.0 and even 1.0 but i have apps arent installed.