We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
As we are growing on our list of supported devices in each release, we require of a stronger build environment so we can speed up the compilation process for releases. Based on the actual Quartz 4 list, we support over 30 devices, which takes between 2 and 3 days for all the builds to be completed without counting possible compilation issues or rebuild needs, based on our current specs.
We kindly ask all of you that are in position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate here
Device-specific issues
Initial FOD related bugs.
Auto brightness reversed.
Dimensions are not perfect.
There are likely many other issues, these are just the most prominent to me. Don't come into this with the expectation any issue you come across will be fixed in a timely manner.
Note: Custom kernels are NOT supported unless the kernel says it supports PA and GMS is included!
Requirements
My preferred logging format is:
adb logcat -b all -d *:E > logcat-err.log
adb logcat -b all -d > logcat.log
adb shell dmesg > dmesg.log
Then you can upload them to https://del.dog and send me the link for each one.
Downloadhttps://drive.google.com/drive/folders/1IqLRSj3voyvKR18SovdA1z6fUi2lo0Pn?usp=sharing
Instructions
Paranoid Recovery:
Apply update from ADB
"adb sideload package.zip"
Wipe userdata from recovery.
Reboot into system.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android, ROM for the OnePlus 8
Contributors
ZVNexus, xboxfanj, Vishalcj17, coderzstas
Source Code: https://github.com/ZVNexus/android_kernel_oneplus_sm8250
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest OOS
Based On: CAF
Version Information
Status: Beta
Current Beta Version: Quartz 4.0.5
Beta Release Date: 2020-09-02
Created 2020-06-23
Last Updated 2020-11-23
https://github.com/AOSPA/android_device_oneplus_oneplus8
https://github.com/AOSPA/android_kernel_oneplus_sm8250
Wow
Well done mate
Thanks for bringing this great rom here
One of my fav Rom
This is very good news, thanks man, and thanks aospa team !
The first ROM compatible with this device is quite a good ROM!
C:\Users\Frankie\Desktop\New folder>fastboot flash system system.img
target reported max download size of 805306368 bytes
sending sparse 'system' 1/2 (786428 KB)...
OKAY [ 23.991s]
writing 'system' 1/2...
FAILED (remote: Partition not found)
finished. total time: 24.000s
I did a full MSM restore before flashing, also i unlocked, i will post a log soon, Cannot wait start using this rom!
frankieuk said:
C:\Users\Frankie\Desktop\New folder>fastboot flash system system.img
target reported max download size of 805306368 bytes
sending sparse 'system' 1/2 (786428 KB)...
OKAY [ 23.991s]
writing 'system' 1/2...
FAILED (remote: Partition not found)
finished. total time: 24.000s
I did a full MSM restore before flashing, also i unlocked, i will post a log soon, Cannot wait start using this rom!
Click to expand...
Click to collapse
You're not flashing according to the instructions. The "fastboot reboot fastboot" part doesn't reboot back into bootloader, which is what you're doing. It reboots into "fastbootd" aka fastboot daemon which lives in recovery. You can only flash system/product from there.
EDIT. Nope its not working.. I know what i am doing.. I wouldn't install if anyone is considering. you will need MSMtool to restore your device, be careful.
frankieuk said:
EDIT. Nope its not working.. I know what i am doing.. I wouldn't install if anyone is considering. you will need MSMtool to restore your device, be careful.
Click to expand...
Click to collapse
You are in bootloader, not in fastboot. This is what we see by command output
Got this flashed with no issues but noticed during setup the finger print sensor isnt lighting up to register my finger. Is this intended?
frankieuk said:
EDIT. Nope its not working.. I know what i am doing.. I wouldn't install if anyone is considering. you will need MSMtool to restore your device, be careful.
Click to expand...
Click to collapse
Even if you mess up the install, you don't need MSMTool. Just flash factory images extracted from payload.
kangta05 said:
Got this flashed with no issues but noticed during setup the finger print sensor isnt lighting up to register my finger. Is this intended?
Click to expand...
Click to collapse
No, it lights up for me. Weird. Send logz and I'll look.
ZVNexus said:
No, it lights up for me. Weird. Send logz and I'll look.
Click to expand...
Click to collapse
Can you point me to a guide on how to pull logs. I can stumble me way through installing but I've never had to pull logs and I want to make sure I get you want you need.
kangta05 said:
Can you point me to a guide on how to pull logs. I can stumble me way through installing but I've never had to pull logs and I want to make sure I get you want you need.
Click to expand...
Click to collapse
I gave instructions in OP. Something else to note though is that you want to reboot, then reproduce right away or the logs will be huge.
ZVNexus said:
No, it lights up for me. Weird. Send logz and I'll look.
Click to expand...
Click to collapse
ZVNexus said:
I gave instructions in OP. Something else to note though is that you want to reboot, then reproduce right away or the logs will be huge.
Click to expand...
Click to collapse
Here we are
https://drive.google.com/file/d/1PxzalTDdse3Mv0ecCAgHXAc0Xh2HtOmj/view?usp=sharing
in the new trwp format date, then everything according to the instructions
kangta05 said:
Here we are
https://drive.google.com/file/d/1PxzalTDdse3Mv0ecCAgHXAc0Xh2HtOmj/view?usp=sharing
Click to expand...
Click to collapse
You need to provide access, for some reason GDrive switched to making it a restricted link by default.
ZVNexus said:
No, it lights up for me. Weird. Send logz and I'll look.
Click to expand...
Click to collapse
ZVNexus said:
You need to provide access, for some reason GDrive switched to making it a restricted link by default.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PxzalTDdse3Mv0ecCAgHXAc0Xh2HtOmj/view?usp=sharing
Try this
Thanks so much for all your hard work!
I had thought there would be many custom roms for this phone but does not seem to be the case at the moment, haha. PA would've been top 3 for me no matter how many options there were, though, so really happy this worked for me!
Is there any way to get magisk/xposed/(ultimately ViperAudio is what I'm after) working with this rom?
I'm hesitant to do any flashing without knowing whether success is a possibility!
thanks again!
slimbrady said:
Thanks so much for all your hard work!
I had thought there would be many custom roms for this phone but does not seem to be the case at the moment, haha. PA would've been top 3 for me no matter how many options there were, though, so really happy this worked for me!
Is there any way to get magisk/xposed/(ultimately ViperAudio is what I'm after) working with this rom?
I'm hesitant to do any flashing without knowing whether success is a possibility!
thanks again!
Click to expand...
Click to collapse
Magisk is broken IIRC and I have no interest in fixing that. I will not support any other mods either.
ZVNexus said:
Magisk is broken IIRC and I have no interest in fixing that. I will not support any other mods either.
Click to expand...
Click to collapse
Fair enough, good sir. Was merely curious, not expectant =)
Thanks again for all your efforts!
Related
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!
According to Project Treble lead Iliyan Malchev,
Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work.
Click to expand...
Click to collapse
Now that there's an Oreo beta for the Essential Phone that supports Treble, perhaps this can be used to further development on the device.
/u/foremi on Reddit confirmed that simply flashing a Pixel 2 system and boot image to the device is not enough, as it fails to boot, so the question is what constitutes a generic AOSP build?
I don't have Linux installed right now or I'd build it myself, but I suspect that building it with the simple target device of "generic" might be what Malchev is referring to.
If any devs would like to test this theory or give their input as to how they think this actually works I think it'd be incredibly useful for not just Essential phone development, but Android development as a whole.
EDIT: @phhusson confirms that the target device should be aosp_arm64_ab
FWIW "generic AOSP build" is really what it says it is.
I have access to the "Google certification generic AOSP build" (that's weirdly not public, I don't know why), so I gave it a try. (Edit: So if the ROM was Treble-certified, it would work)
I get the Android bootanimation, but that's all (I have to say that's still a big step forward compared to other Android versions
Looking at the logs, I see a loop of crash because of: /vendor/bin/hw/[email protected]
Which I guess is the HAL for the accessories, but that doesn't seem to be the reason for the crash
The reason of the crash, seem to be this:
11-15 12:59:04.491 5331 5331 F MediaProfiles: frameworks/av/media/libmedia/MediaProfiles.cpp:329 CHECK(quality != -1) failed.
in CAF, frameworks/av/media/libmedia/MediaProfiles.cpp we see vendor-specific (i.e. not in AOSP) quality attributes, like "vga"
And it is defined by Essential's framework (in vendor/etc/media_profiles_V1_0.xml)
Considering there are media_profiles xml files, I'd guess that _V1_0 is supposed to only contain AOSP-capable qualities
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Edit3: the generated fingerprint is too long to build, needs to do make BUILD_NUMBER=4412360
Edit4: To make the situation more clear:
- NO, current ROM is NOT Treble capable
- BUT, almost everything is available for that. Every HAL is using "hwbinder" which is the basis, and most work needed for Treble
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
phhusson said:
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Click to expand...
Click to collapse
I was gonna link to the aosp_arm64 make file but it said it was specifically for the emulator so I wasn't sure, that's good to know though.
phhusson said:
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
Click to expand...
Click to collapse
Thanks for this, I suspected such but couldn't find a clear answer from Google on the matter so I suggested trying the boot.img as well just in case.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2. I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
For what it's worth I only have a LG V20 right now which currently doesn't support Treble, so I'm pretty useless as far as testing anything goes, but if this is figured out it'll greatly influence what device I go with when I eventually upgrade.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2.
Click to expand...
Click to collapse
Yup. I feel like Treble deserves its own "device" section in XDA
I'm afraid I'm working on something that other people already did on other devices...
I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
Click to expand...
Click to collapse
That's my guess as well.
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
MishaalRahman said:
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
Click to expand...
Click to collapse
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
PhantomGamers said:
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
Click to expand...
Click to collapse
Google Pixel/Pixel 2 will do, yes?
MishaalRahman said:
Google Pixel/Pixel 2 will do, yes?
Click to expand...
Click to collapse
Yeah they should be fine
PhantomGamers said:
Yeah they should be fine
Click to expand...
Click to collapse
Alright, I'll find you some testers
MishaalRahman said:
Alright, I'll find you some testers
Click to expand...
Click to collapse
Here's the system image if you find anyone, it's a straight fresh build of aosp branch 8.0.0r34
If it doesn't work it's possible that I messed the build up, but it should be fine.
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
PhantomGamers said:
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
Click to expand...
Click to collapse
Hero you go
TheDethEgineer said:
Hero you go
Click to expand...
Click to collapse
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
PhantomGamers said:
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
Click to expand...
Click to collapse
That's true only for new devices, not for devices upgrading for nougat to oreo.
I wasn't aware there was an AMA yesterday... Too bad we could have asked.
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
How about flashing the system image directly from a Pixel 2 XL?
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
PhantomGamers said:
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
Click to expand...
Click to collapse
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
MishaalRahman said:
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
Click to expand...
Click to collapse
I believe it should work as normal
fastboot flash system system.img
EDIT: Apparently with the A/B partitions you'd do fastboot flash system_b system_other.img to flash the b partition, but the aosp build didn't include a system_other.img so I'm assuming perhaps it's not necessary
So far I still can't find anyone willing to flash this on their Pixel haha. People are really hesitant to flash stuff on the Pixel it seems. Times are not like they used to be =\
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
Hit thanks if you like my work.
Downloads : "removed by moderator"
Gapps :== "removed by moderator"
Nano recommended
Twrp :== "removed by moderator"
Don't flash magisk, right now root not supported.
What's working ---
WiFi
Mobile data
bluetooth
mobile data
hotspot
gcam
magisk
If you want to root your pie rom
just simply flash the magisk zip file via twrp.
then install the magisk manager apk manually and open that then you can the installed magisk version.
also you can check your rooot via rootchecker apk
Test this build and let me know the issue, so we could fix those issue.
Special thanks to all oxygen team and all group mates, who provides logs.
Testing thanks
@Cirno
@remicaa
@luciano Henrique
@Mario Resurrected
Credits:
MactavishAO
Hard_rock83
Mokee Development Team
LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Mokee Open Source Project
Version Information
Status: stable
First android 9? Things are coming! Thank you for the hard work.
Android-9.0(Pie)
It's just first build which booted properly. So there would be lots of bugs.
Let me know the bugs, so we could work on fixing bugs.
fgaurano said:
First android 9? Things are coming! Thank you for the hard work.
Click to expand...
Click to collapse
It's just first build, so there would be lots of bugs, let me know the bugs, so we could fix them.
Gapps?
MI MAX 2 cihazımdan Tapatalk kullanılarak gönderildi
OTA uptades avaible?
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
not
finger print,
double click open the screen
not blutouth
not xposed
Theseusperse said:
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
Click to expand...
Click to collapse
GCam 6.1 working on oreo
Which twrp to be used?
ridershahmir said:
GCam 6.1 working on oreo
Click to expand...
Click to collapse
How?!?! What APK are you using for the Mi Max 2? I've tried everything, even wiped my phone and used every ROM out there and can't get anything to work. I'm specifically talking about the latest 6.1 GcCam from the Pixel 3 (Pixel3Mod) with the latest low light enhancement features from the new photo core. I'd love to know how you got it working on the Mi Max 2 on Oreo.
None of the ones on this list work for me so far:
https://www.celsoazevedo.com/files/android/google-camera/
And that's literally all of them as far as I know, including highly specialised device variants. As far as I'm aware it's Pie only.
cem_uar said:
not
finger print,
double click open the screen
not blutouth
not xposed
Click to expand...
Click to collapse
What can you expect from an alpha build .lol. isn't it enough you got pie.
scissordragonboy said:
What can you expect from an alpha build .lol. isn't it enough you got pie.
Click to expand...
Click to collapse
Is camera working on pie?
reversegear said:
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Click to expand...
Click to collapse
If you want to handle this Pie project you can compile from source.
My trees are open on GitHub.
Downloading. Is there a problem with IMEI?
Hucksley said:
Downloading. Is there a problem with IMEI?
Click to expand...
Click to collapse
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
Camera? Totally not working?
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
I'm already using rom and I want to thank you for your great work.
I will use it until the next updates come out and I will notify any unknown bug so far.
Thanks again for the work!
(Sorry for the English)
hard to download
I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
LinuxForExynos Group PresentsA WONDERFUL NON WORKING LINUX DISTRO THAT DOESNT EVEN TRY TO BOOTANYWAYS TO FLASH IT:First, flash TWRP or OrangeFoxSecondly, flash Astrako's Partitioner Script from here https://forum.xda-developers.com/t/...epartition-script-for-vendor-support.4143541/ . What this does is it makes your system partition to 4GB, which is good for PostMarketOS. Flash this and reboot to recovery. WARNING: ALL DATA WILL BE GONEThirdly, download PostMarketOS from the links given below and flash it via PBRP. it is automatic and please do NOT opt in for Full Disk Encryption as it will break the phone.Fourth, reboot and enjoy! For now this only has a terminal with a touch keyboard. The login is `user` with the password `12345`.If it works for you or doesn't PLEASE let me know and please do note that this is alpha build software and you should not use it as a daily driver or expect your phone to be stable. Thank you.
Contributors:
@Astrako for his repartition script
@Parthib and DedSec#3307 for their VPS
@zpunout and @thinhhdk for their time and effort and testing the product
@thinhhdk for patches
AFH and GitHub for letting me host the files
Download V1.1:
pmos-on7xelte-31JAN.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Release Boots initramfs, no networking yet, includes LXDE. · LinuxForExynos/pmos-samsung-on7xelte
This build now has a booting initramfs and working usb. Networking and display and other stuff isnt working.
github.com
Download V1:
pmos-samsung-on7xelte.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
https://files.catbox.moe/fxphum.zip
pmos-samsung-on7xelte.zip
drive.google.com
I am working on a pmOS port to G610F. Currently there is a port for the J710F (https://wiki.postmarketos.org/wiki/Samsung_Galaxy_J7_(2016)). This new port will be based on that. Due to me breaking my grandma's phone, she actually has the G610F, also yes she is outstation so I don't have the phone, so, basically I need testers for the new port. Every single development enhancements, milestones and builds will be provided here. As of now, I have the source at https://github.com/LinuxForExynos/pmos-samsung-on7xelte. If you have any suggestions or are interesting in developing or testing, please reply to this thread or hit me a dm at Otus9051#5971 in discord. This project won't be possible without you. Also, I am developing Halium for it too, so this thread will also have this too.
Requirements for testing:
Knowledge with Linux (atleast upto knowing how to cd or cp, the more the better)
Time (a lot)
My PBRP build (https://forum.xda-developers.com/t/...-pitch-black-recovery-project-v3-1-0.4287985/) [actually any twrp build but this one has a better terminal ui and looks cool]
A G610F, with my pbrp
Requirements for development:
why am i putting this but anyways
Knowledge with Alpine Linux and Linux Kernels
Knowledge with DTBs and stuff and android ofc
A laptop/pc with Linux (not wsl) and atleast 6gb ram and a dual core processor
-------------
Otus9051 said:
MODS PLEASE SEE THIS!!!
Click to expand...
Click to collapse
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50
Badger50 said:
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50
Click to expand...
Click to collapse
It's ok man
I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.
zpunout said:
I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.
Click to expand...
Click to collapse
I will be releasing the first release of pmOS (probably non-booting) in a couple of weeks. Thanks for your interest and help!
@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up
Otus9051 said:
@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up
Click to expand...
Click to collapse
Matrix works for me. I just set up an account
zpunout said:
Matrix works for me. I just set up an account @zpunout:matrix.org
Click to expand...
Click to collapse
DMed ye
Ran into a big problem: pmbootstrap is broken
its workin'
@zpunout get ready with latest stock, DO NOT BOOT PLEASE I BEG YOU, and flash my recovery instead of stock recovery at the time of flashing. and do not boot to system.
still compiling
See the Main Post for Links
> (doesn't work lol[if you thought it would well no your dreams are gone])
Can confirm, doesn't boot, stuck at samsung splash screen, charging doesn't show percentage so maybe kernel problems.
Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...
Otus9051 said:
Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...
Click to expand...
Click to collapse
I want to be a tester, i sent a friend request on discord
It might seem that development is dead but its not. It takes more than a year to complete each port. Please have patience. You can track our progress at https://github.com/LinuxForExy7870/
failed to mount /system_root
serelafo said:
failed to mount /system_root
Click to expand...
Click to collapse
Its a common problem. It has still installed nonetheless.
FYI, project still alive, working on Android 12 currently.