Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk
cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.
Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!
SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...
Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.
Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Man, you are the best! And what about sensors?
And where did you find this solution?
hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.
How to make this logs? i know nothing in programming (
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Pd. There a bootable cm13 rom that i'm using to write this :v
I'm sorry if i had a bad engish, i'm a mexican :v
armando121504 said:
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Click to expand...
Click to collapse
Yeah... I have just flashed it, but it has been in a bootloop for 20+ minutes already. Needless to say, this is probably a test/WIP CM14.1 build that @karthick mostwanted is testing for the Galaxy Fame to see if it will work at all. From what I am aware of, later CM ROMs (CM13, 14, and 14.1) will not work as well as they should on this device as it is low-end and doesn't have the RAM or processing power that is required, however, CM13 is fairly usable from what I have tried, but I still find the CM11 (KitKat 4.4.4) ROMs to be the best. Then again, it is always good to keep and eye on and test the latest builds that the developers release, as I have seen some older devices get ROMs which shouldn't work on them because of their hardware, but do, because the developer is able to configure it to make it work.
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
karthick mostwanted said:
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
Click to expand...
Click to collapse
Fair enough, but I assumed that since it was publicly available to view and download, then it should be okay to publicly discuss about the development surrounding the ROM/s, but I guess not.
Thank you for the time and effort you put into these builds and the continuation of custom ROM development for this device.
Thread Closed.
Reserved 1
Reserved 2
Reserved 3
Bugs on G920F, build 23042017:
* Wireless charging is much worse as on stock, on stock you could charge your phone with display on. Here you can't with display off!
* ANT service isn't working
* HR sensor isn't working
Please list them on bugs, thanks.
Battery performance is not as good as on stock rom
Performance is very good!
Ram management is much worse as on stock rom
Donation for the team:
16T354192M119622E
Thanks for this awesome ROM. Just wanted to be the first to tell you
---------- Post added at 12:08 PM ---------- Previous post was at 12:05 PM ----------
I was able to successfully dual boot stock ROM and LOS. There is an app on github named DualBootPatcher which is compatible with our device and if anyone wants to use it just pm me. I won't discuss this here as we want to keep this thread clean.
C0qRouge said:
Bugs on G920F, build 23042017:
* Wireless charging is much worse as on stock, on stock you could charge your phone with display on. Here you can't with display off!
* ANT service isn't working
* HR sensor isn't working
Please list them on bugs, thanks.
Battery performance is not as good as on stock rom
Performance is very good!
Ram management is much worse as on stock rom
Donation for the team:
16T354192M119622E
Click to expand...
Click to collapse
ANT Service will not work as this is a stock TouchWiz Feature. HR sensor will also not work ever.
Why did you make a new thread? Is it because this will become the thread for official lineage? And if so where will the other ROMs be posted? On the nexus7420 site? Sorry for the questions but hopefully the answers clear everything up.
customrus said:
Why did you make a new thread? Is it because this will become the thread for official lineage? And if so where will the other ROMs be posted? On the nexus7420 site? Sorry for the questions but hopefully the answers clear everything up.
Click to expand...
Click to collapse
For being official, we need a "clear" thread. That means that we need to have a thread only for LOS and separate ones for other ROMs.
Congrats on going official team :good:
Wouldn't it have been best to wait till you're given the greenlight or does a topic need to be made first (then turned official)?
Reboot
Hello,
I have this rom on my phone, galaxy s6 flat.
At the beginning, the rom was functionnal, but now, when I connect my phone to the wifi or the 4G, my phone reboot.
Please somebody can help me ?
Thank you.
And this rom is very cool, good luck for the developpers :good:
VictorLMRT said:
Hello,
I have this rom on my phone, galaxy s6 flat.
At the beginning, the rom was functionnal, but now, when I connect my phone to the wifi or the 4G, my phone reboot.
Please somebody can help me ?
Thank you.
And this rom is very cool, good luck for the developpers :good:
Click to expand...
Click to collapse
There is a very clear section in the OP on how to report bugs. Follow it if you wish to be addressed
Hi,
To be honest I don't get the situation with official /unofficial yet. Didn't you post yesterday, that you pushed/moved your sources to the lineageos github project itself? So then why is there a build server and your own github link here? Shouldn't that lead to official builds on the lineageos page?
My second question is: you ask for donations especially for a build server for you own nexusrom which seems to be a fork of lineageos. I'd really like to donate there to support your further work, but you don't describe how that works.
Finally : I'm currently on your april/23 build and with the audio patch you provided that is working great. The only problem open is, that VoLTE is not working for me. Do you have any plans for this? If you need someone to debug there let me know, though currently I'm not able to even activate it.
Finally : thank you very very much for your great work.
Br
Johannes
orgler said:
Hi,
To be honest I don't get the situation with official /unofficial yet. Didn't you post yesterday, that you pushed/moved your sources to the lineageos github project itself? So then why is there a build server and your own github link here? Shouldn't that lead to official builds on the lineageos page?
My second question is: you ask for donations especially for a build server for you own nexusrom which seems to be a fork of lineageos. I'd really like to donate there to support your further work, but you don't describe how that works.
Finally : I'm currently on your april/23 build and with the audio patch you provided that is working great. The only problem open is, that VoLTE is not working for me. Do you have any plans for this? If you need someone to debug there let me know, though currently I'm not able to even activate it.
Finally : thank you very very much for your great work.
Br
Johannes
Click to expand...
Click to collapse
It clearly states in the title that these are UNOFFICIAL builds.
No word of donations is mentioned on the thread.
VoLTE will not work as this is not implemented by LineageOS.
Thank you guys for all your hard work. Im going to try this out on g925t with duelboot. Hope calling works now?
Setup wizard force closes on rr and lineage on mu g926t. I flashed them with duelboot and it happened so i tried a clean install and it still happened.
Stonkers said:
Setup wizard force closes on rr and lineage on mu g926t. I flashed them with duelboot and it happened so i tried a clean install and it still happened.
Click to expand...
Click to collapse
Please read again the title: only for G920F and G925F. No G926T...
Edit: Did you mean dualboot? If yes then you need to know that it may create instability in the multibooted ROMs. For me everything works
I got it working with duelboot. I just flashed the ROM without gapps, booted it and then went back and flashed gapps. Thanx again developers!
Great rom, i love it, except for the obvious bugs. Anyway, i can't turn on my bluetooth speaker remotely anymore. The manufacturer website says you need BLE (Bluetooth Low Energy) for that, does anyone know if that's a LOS bug?
Stonkers said:
Thank you guys for all your hard work. Im going to try this out on g925t with duelboot. Hope calling works now?
Click to expand...
Click to collapse
Calling still likely won't work. There's binary blobs missing and we need a different kernel.
Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/
Mine mineminemineminemineminemine
Another one
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.
Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.
working like a champ but having issue with the figer print
karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.
Download link is not working
Link is not working bro. Send me link
Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.
Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.
Enjoying the new build so far! Pretty good for me.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip
Would anyone be interested in this for our device? I'm thinking of building it for myself. It seems pretty straight forward
GrapheneOS build documentation
Building instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
abadasstanker69 said:
Would anyone be interested in this for our device? I'm thinking of building it for myself. It seems pretty straight forward
GrapheneOS build documentation
Building instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Click to expand...
Click to collapse
im very interest
I'm interested too
Me too
Yes please, very very interested.
Yes please, I was really hoping someone to do this build.
Would be really great. Thank you
Can it be?
Sorry boys. I was working on it but I saw Jaguar Rom and decided that was about as good as it was gonna get. I own a company and it would have taken me an eternity to do it on my own with what little free time I have to dedicate to it. Jaguar does a fantastic job of keeping your data safe. Just download the vanilla version without Google crap. Install Aurora store if you need to restore any apps you got from Google. I've been using it as my DD now for a few months and I have to say, it's legit. I'm not gonna list my credentials or anything as most people on XDA know me by now, but I would say that if you think I'm wrong, please download the rom and try to find a problem that Graphene would fix. Hell they even let you relock your bootloader on Jaguar. The phone can die and your alarm will still go off if there is enough battery to start it and sound the alarm. The dev ( @optimumpro ) is super cool and was very helpful with some of the things I needed help de-goggle-fying. I highly recommend it. I'm sorry if I got anyone's hopes up. I will be asking for the thread to be closed now as I have no intentions on developing this rom as I feel it's redundant.
abadasstanker69 said:
Sorry boys. I was working on it but I saw Jaguar Rom and decided that was about as good as it was gonna get. I own a company and it would have taken me an eternity to do it on my own with what little free time I have to dedicate to it. Jaguar does a fantastic job of keeping your data safe. Just download the vanilla version without Google crap. Install Aurora store if you need to restore any apps you got from Google. I've been using it as my DD now for a few months and I have to say, it's legit. I'm not gonna list my credentials or anything as most people on XDA know me by now, but I would say that if you think I'm wrong, please download the rom and try to find a problem that Graphene would fix. Hell they even let you relock your bootloader on Jaguar. The phone can die and your alarm will still go off if there is enough battery to start it and sound the alarm. The dev ( @optimumpro ) is super cool and was very helpful with some of the things I needed help de-goggle-fying. I highly recommend it. I'm sorry if I got anyone's hopes up. I will be asking for the thread to be closed now as I have no intentions on developing this rom as I feel it's redundant.
Click to expand...
Click to collapse
Where to download Jaguar for 7T?
Another rom similar to grapheneos available for op7t is divestos.org which is based on lineageos but implements several privacy and security measures and allows you to re-lock the bootloader
Agree about Divest OS, but since OP discussed Jaguar rom which is brand new, I wanted more details about Jaguar
HueyT said:
Agree about Divest OS, but since OP discussed Jaguar rom which is brand new, I wanted more details about Jaguar
Click to expand...
Click to collapse
I am the developer for Jaguar rom. Unfortunately, it is not available for Oneplus 7 series, although, I can build one for 7s, if there is sufficient interest.
Also, Jaguar for Oneplus 5, 6 , 8s and 9s has been available for many years and certainly long before DivestOS and GrapheneOS ever appeared. Just look at my profile: you don't get 14700+ 'thank yous' in a year or two. (not bragging, but rather stating the fact).
Sure, OP was discussing Jaguar of op7t which doesn't exist. That's why I was asking about it. Besides e OS, LOS18 with microg, DivestOS (fork of LOS19), yaap vanilla, flamingo vanilla, op7t does not have any other degoogled rom
HueyT said:
Sure, OP was discussing Jaguar of op7t which doesn't exist. That's why I was asking about it. Besides e OS, LOS18 with microg, DivestOS (fork of LOS19), yaap vanilla, flamingo vanilla, op7t does not have any other degoogled rom
Click to expand...
Click to collapse
I have built a trial version of Jaguar for Oneplus 7T. Please test it, since my phone is Oneplus 8.
OOS-11 (not 12) is required in both slots. Installation is the same as Lineage. Don't forget factory reset before the first boot.
Rom: Here
Recovery: Here
Kernel Source: Here
May or may not boot, but even if you boot, submit a logcat (let it run for a few minutes).
optimumpro said:
I have built a trial version of Jaguar for Oneplus 7T. Please test it, since my phone is Oneplus 8.
OOS-11 (not 12) is required in both slots. Installation is the same as Lineage. Don't forget factory reset before the first boot.
Rom: Here
Recovery: Here
May or may not boot, but even if you boot, submit a logcat (let it run for a few minutes).
Click to expand...
Click to collapse
Hi, thanks for sharing. As part of the XDA rules and GPLv2 requirement, could you please also post your kernel sourcel link? All ROMs posted on XDA must have the kernel source code available. Thank you.
jerryhou85 said:
Hi, thanks for sharing. As part of the XDA rules and GPLv2 requirement, could you please also post your kernel sourcel link? All ROMs posted on XDA must have the kernel source code available. Thank you.
Click to expand...
Click to collapse
For this test release I am using Lineage's kernel without changes: Here
Will try tonight. Thanks
optimumpro said:
For this test release I am using Lineage's kernel without changes: Here
Click to expand...
Click to collapse
Works great except no camera (can't connect to camera, changing camera app won't help). See matlog zip and screenshots
HueyT said:
Works great except no camera (can't connect to camera, changing camera app won't help). See matlog zip and screenshots
Click to expand...
Click to collapse
Logcat.txt doesn't have enough entries. You should run it for a few minutes at least and try to open/close camera a few times.
optimumpro said:
For this test release I am using Lineage's kernel without changes: Here
Click to expand...
Click to collapse
Thank you very much!
If you feels OK, I could move your release posts to a dedicated new thread. Do let me know if you want to do that.
Thanks.