[ROM][OFFICIAL][STABLE][10.0] NitrogenOS

Status
Not open for further replies.
Search This thread

pawel0301

Member
Apr 24, 2015
10
3
Okay guys, i fixed a problem, turned out i had to manually enable camera2 api in Buildprop Editor app, because flashing in twrp didnt enable it, know all of gcams you suggested works fine.

---------- Post added at 10:11 AM ---------- Previous post was at 10:06 AM ----------

I have tried all gcam suggested (even that version) and no one works. The camera preinstalled take green photos. I have cam2api. I don't know what to do :crying: I can't take any photo... Help me please

Download Build.prop editor app -> hit Edit -> at the end type "persist.camera.HAL3.enabled=1" -> save and restart you phone
 
  • Like
Reactions: XxXxXx121212

YASANdev

Senior Member
Jul 10, 2016
431
207
25
I have some call related issues on this rom

When someone calls me they can't hear me anymore after like the first 10 seconds and I have to call them back in order to be able to actually talk with them

I come from EU MIUI so I have the latest firmware too

Any ideas how I can fix this? Haven't seen anyone else talk about such a problem here, I don't have this problem on MIUI or Android 9 ROMs

EDIT: also another bug that I've noticed is that the screenshots are not added to gallery fast, the file is saved but the gallery doesn't add them for like hours so it's not possible to take a screenshot and send it to someone right away
 
Last edited:

San Cigo

Senior Member
May 27, 2018
78
12
I have tried all gcam suggested (even that version) and no one works. The camera preinstalled take green photos. I have cam2api. I don't know what to do :crying: I can't take any photo... Help me please
https://f.celsoazevedo.com/file/cfiles/gcm1/PMGC_7.0.009_BudgerigarVersion_V13.apk
This specific gcam works for sure.
If not, u probably didn't enable camera2api. Use Camera2Probe from Play Store to check it.

---------- Post added at 11:36 PM ---------- Previous post was at 11:19 PM ----------

camera.hal1.packagelist is not working. I set packages like com.pack1,com.pack2 but it doesn't work. This is the best solution I've found to solve green photos problem.
 
  • Like
Reactions: XxXxXx121212

San Cigo

Senior Member
May 27, 2018
78
12
I have some call related issues on this rom

When someone calls me they can't hear me anymore after like the first 10 seconds and I have to call them back in order to be able to actually talk with them

I come from EU MIUI so I have the latest firmware too

Any ideas how I can fix this? Haven't seen anyone else talk about such a problem here, I don't have this problem on MIUI or Android 9 ROMs

EDIT: also another bug that I've noticed is that the screenshots are not added to gallery fast, the file is saved but the gallery doesn't add them for like hours so it's not possible to take a screenshot and send it to someone right away
It's so strange. I don't have any of your problems. Maybe the gallery bug, because gallery app is really bad but using mi file explorer I see the screenshot (also u can share the screenshot with the share button on the notification that appears when u shot a screenshot)
Wich passages did u followed during installation?
 

YASANdev

Senior Member
Jul 10, 2016
431
207
25
It's so strange. I don't have any of your problems. Maybe the gallery bug, because gallery app is really bad but using mi file explorer I see the screenshot (also u can share the screenshot with the share button on the notification that appears when u shot a screenshot)
Wich passages did u followed during installation?

I checked again and it's kinda working but still very strange. Something is just not working properly here and it's causing weird issues. Now that I checked, I can see them in the gallery (wouldn't update before but now it's working fine) and can access new screenshots on some apps but still some apps like Twitter don't show any of the new screenshots.

The share option isn't useable for everything, but still better than nothing.

It's actually working better now somehow, I used to not even be able to open the screenshot notification, it would just show me an error that the file can't be found it something like that. But now it opens and my new screenshots are on most of my apps.

About the call issue, it's so annoying. I know it's not a hardware issue since it works fine on MIUI and custom ROMs below Android 10. And other than that, when I call them it's no problem, but when I get a call the mic cuts off in like 15 seconds.

I was on the latest EU MIUI. So I just wiped everything and flashed NOS, Pico GApps and Magisk. I only use Magisk to make some apps work (bank apps etc). No modules installed. The call issue also happens on the new AICP for me, even flashing the latest firmware doesn't do anything. Although I am already on the latest.
 

San Cigo

Senior Member
May 27, 2018
78
12
I checked again and it's kinda working but still very strange. Something is just not working properly here and it's causing weird issues. Now that I checked, I can see them in the gallery (wouldn't update before but now it's working fine) and can access new screenshots on some apps but still some apps like Twitter don't show any of the new screenshots.

The share option isn't useable for everything, but still better than nothing.

It's actually working better now somehow, I used to not even be able to open the screenshot notification, it would just show me an error that the file can't be found it something like that. But now it opens and my new screenshots are on most of my apps.

About the call issue, it's so annoying. I know it's not a hardware issue since it works fine on MIUI and custom ROMs below Android 10. And other than that, when I call them it's no problem, but when I get a call the mic cuts off in like 15 seconds.

I was on the latest EU MIUI. So I just wiped everything and flashed NOS, Pico GApps and Magisk. I only use Magisk to make some apps work (bank apps etc). No modules installed. The call issue also happens on the new AICP for me, even flashing the latest firmware doesn't do anything. Although I am already on the latest.
Mh. It seems u did the installation correctly. I used BiTGAPPS but probably this is not the problem. If I remember well, I was on the latest MIUI EU beta, the last one before the support was ended. Were u on the stable?
Anyway, the only thing that I could suggest is to do a clean flash again and see if it works.
 
  • Like
Reactions: YASANdev

YASANdev

Senior Member
Jul 10, 2016
431
207
25
Mh. It seems u did the installation correctly. I used BiTGAPPS but probably this is not the problem. If I remember well, I was on the latest MIUI EU beta, the last one before the support was ended. Were u on the stable?
Anyway, the only thing that I could suggest is to do a clean flash again and see if it works.

I already did a clean flash tho, I tried NOS 2 times already and AICP once. They all had this issue. The call problem is really annoying. I'll try flashing the latest firmware again, last time it didn't do anything. I was on the latest EU MIUI for Vince which is a stable one.
 

Wattapak

Member
Jun 1, 2020
8
1
Hi @Prateek Punetha why is that in the op it is required to wipe vendor and system?
usually in other rom page i found they only mention data, cache and dalvik? i am just curios.

thanks
 

Sahin420

Senior Member
Aug 4, 2016
216
46
Murshidabad
I already did a clean flash tho, I tried NOS 2 times already and AICP once. They all had this issue. The call problem is really annoying. I'll try flashing the latest firmware again, last time it didn't do anything. I was on the latest EU MIUI for Vince which is a stable one.

Tick the vendor during wiping.
Are you using any types of magisk module or exposed module..?

---------- Post added at 03:06 PM ---------- Previous post was at 03:03 PM ----------

Hi @Prateek Punetha why is that in the op it is required to wipe vendor and system?
usually in other rom page i found they only mention data, cache and dalvik? i am just curios.

thanks

Wipe Delvik, cache, data, system.
Vendor (if required)
Then flash the rom
 
Hello, I have a problem. I have already the update of the 4 of June, but it still asks me to do this update. Thanks.
 

Attachments

  • Screenshot_20200618-162430_1.jpg
    Screenshot_20200618-162430_1.jpg
    47.1 KB · Views: 151
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    nitrogen_accent.png



    mSx8lRG.png

    Based on AOSP

    ZpXJzKd.png

    xyyx (Max) - main developer
    Prateek Punetha - vince bringup, some device specific features etc etc

    IxVVRiE.png


    Download the ROM, GApps (Optional), Magisk (Optional)
    • Reboot to recovery
    • Wipe Data, System,Vendor and cache
    • Flash ROM , GApps (Optional), Magisk (Optional).
    • Reboot
    • Enjoy


    C8vWqi4.png

    Rom: https://sourceforge.net/projects/nitrogen-project/files/vince/
    Recovery: https://sourceforge.net/projects/orangefox/files/vince/
    Open GApps: https://sourceforge.net/projects/opengapps/files/arm64/beta/
    Magisk: https://github.com/topjohnwu/magisk_files/blob/canary/magisk-release.zip
    NnOP1ox.png

    Nitrogen Project

    XDA:DevDB Information
    [ROM][OFFICIAL][STABLE][10.0] NitrogenOS, ROM for the Xiaomi Redmi Note 5 / 5 Plus

    Contributors
    Prateek Punetha, xyyx, wight554

    Source code:

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Latest
    Based On: AOSP

    Version Information
    Status: Stable
    Stable Release Date: 2020-09-16

    Created 2019-09-24
    Last Updated 2020-09-16
    24
    Changelog 16 September 2020

    • Merged September Security Patches
    • Minor Nos Upstream Changes
    • Build with latest Genom kernel
    • Other Fixes and Improvements

    Changelog 6 August 2020

    • Merged August Security Patches
    • Add feature IMS/VoLTE icon on status bar
    • Build with latest Genom Kernel
    • Other Fixes and Improvements

    Changelog 7 July 2020

    • Merged July Security Patches
    • Build with latest Genom Kernel
    • Other Fixes and Improvements

    Changelog 4 June 2020

    • Merged June Security Patches
    • Build with latest Genom Kernel
    • Other Fixes and Improvements


    Changelog 28 May 2020

    • Switch to device/qcom/sepolicy-legacy-um policy
    • Build with latest Genom Kernel
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 10 May 2020

    • Merged May Security Patch
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 22 April 2020

    • Set Rounded corner radius to 22
    ( as the corners were too much round, specially noticable on those devices with white colour so decreased little bit. )
    • Build with latest Genom Kernel
    • Added dotted circle battery style
    • Bring back good old circle battery style
    • Other Fixes and Improvements

    Changelog 10 April 2020

    • Merged April Security Patches
    • Port face unlock feature
    • Bypass Safetynet
    • Build With Latest Genom Kernel
    • Increased Rounded Corner Content Padding & Radius
    • Other Fixes and Improvements

    Changelog 27 March 2020

    • Build with latest Genom kernel
    • Add Screen Off Power Button Torch
    • Other Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 20 March 2020

    • Disable Camera2Api by default
    • Hide OEM unlock by default in Developer Settings ( The "OEM unlocking" toogle should not be visible on any device running Aosp or Lineage based custom Roms, for obvious reasons. Allow it only to show up for Google devices, such as Pixel, that set
    ro.oem_unlock_supported=1. )
    • RingtoneManager: Don't crash if the ringtone doesn't have a numerical ID
    • PhoneWindowManager: Allow torch during ambient
    • Update qti-telephony-common from DRG
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 8 March 2020

    • Merged March Security Patches
    • Add option to disable auto brightness icon in brightness slider
    • Add simple iconpack support in launcher
    • Add Simplified Chinese translation
    • Updates to various icons
    • Add a new screenrecord icon for statusbar
    • Fix dull AOSP accents with dark theme
    • Screenrecord: use H264 codec for low quality
    • Correctly display notification title for screenrecord
    • Implement better partial screenshot
    • Built with latest Darky Ages Kernel
    • Other Fixes and Improvements

    Changelog 15 February 2020

    • OTA: Fix Prop
    • Built with latest Darky Ages Kernel
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 4 February 2020

    • Merged February Security Patch
    • Add "Built-In (Back) Mic" to "primary input" sink
    • Use AOSP SurfaceFlinger
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 31 January 2020

    • Added OTA support
    • Update Framework Config overlay
    • Update Graphics & Media Blobs
    • Build with latest Darky Ages Decimo Kernel
    • Increase ZRAM Size to 1GB
    • Other Fixes and Improvements

    Changelog 14 January 2020

    • Update CarrierConfig overlay from LA.UM.8.6.r1-02900-89xx.0 ( So basically now Volte in Airtel && Vodafone SIM works )
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 08 January 2020

    • Merged January Security Patches
    • Fix overlaying max notification icons after r20
    • Stop hiding LTE+
    • Avoid casting network traffic to StatusBarIconView to prevent crash
    • Other Fixes and Improvements

    Changelog 22 December 2019

    • Update WFD blobs from LA.UM.8.6.r1-01900-89xx.0 ( So basically now wireless display/cast/mirror cast works )
    • Add aptX blobs from crosshatch QP1A.190711.020
    • Other Fixes and Improvements

    Changelog 21 December 2019

    • Fix black screen for pulse and AOD
    • Allow to disable lockscreen media artwork
    • Other Fixes and Improvements

    Changelog 12 December 2019

    • Merged December Security Patches
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 26 November 2019

    • Upstreamed kernel to 4.9.199
    • Fixed Hiding of Statusbar Clock
    • Fixed Double Tap to Wake on Ambient Display
    • Added Call Recorder
    • Added ScreenRecorder
    • Added Dark Mode in Dialer
    • Added Dark Mode in Message's
    • Allow to suppress notifications sound/vibration if screen is On
    • Added Option for Answering Call by pressing Volume keys
    • Other Fixes and Improvements

    Note: To Enable Call Record Go to Phone --> Settings --> Other Settings --> Auto Call Recording

    Changelog 6 November 2019

    • Merged November Security Patches
    • Nos upstream changes
    • Other Fixes and Improvements

    Changelog 23 October 2019

    • Show bluetooth battery level when available
    • Do not disconnect profile till bluetooth is off
    • Fix Bluetooth carkit position issue when music app is killed
    • Audio: Fix flac offload not working
    • Audio: Extend platform parser to allow device name alliasing
    • Other fixes and improvements

    Changelog 13 October 2019

    • Add Support for exfat & ntfs ( should work fine now )
    • Nos upstream changes
    • Other Fixes and Improvements

    Changelog 10 October 2019

    • Merged October Security Patches
    • Fixed Double tap to wake
    • Fixed QS autobrightness icon tint
    • Fixed brightness slider animation on qs expand
    • Use OnePlus drawables for autobrightness icon
    • Added auto brightness toggle to Quick Settings
    • Added Double tap to sleep on lockscreen
    • Added Double tap to sleep on statusbar
    • Added Launcher 3
    • Added switch for vpn, data saver and roaming icons
    • Added tuner pref for qs brightness slider position
    • Correct colors for icons in "Search settings" for dark theme
    • SettingsProvider: cleanup leftover logspill
    • Quick statusbar tiles header: expand panel on longpress for details view
    • Other Fixes and Improvements

    Changelog 30 September 2019

    • Fixed Goodix Fingerprint, so basically now both goodix & fpc works )
    • Updated Keylayouts
    • Blacklist camera on goodix
    • Nos Upstream Changes
    • Other Fixes and Improvements


    Changelog 26 September 2019

    • Fixed Fpc fingerpint
    • Fixed Bluetooth Audio
    • Fixed Internal Problem Error on Boot
    • Enabled Camera2Api by default
    • Nos Upstream Changes
    • Other Fixes and Improvements

    Changelog 24 September 2019

    • September Security Patch
    • Increased In-call earpiece volume (will fix low voice during calls)
    • Used 4G icon instead Of LTE
    • Increased corner content padding
    • Set default hotspot name
    • Show DocumentsUI internal storage by default
    • Enabled clearkey drm plugin v1.2 (fixes lag issues in drm apps like chrome)
    • Other fixes and improvements
    15
    By the way new build is Up Guys )
    12
    Because people won't get it any section. All Roms are full of bugs and will be.

    The reason why devs are telling you, no bugs cause they just hit up the home screen without any modifications.

    Lineage os, aosp. No official drivers, no official stuff anyway.

    They don't optimize kernels expect havoc rom, but this guy is also arrogant.

    We're having the baddest phone for xda.

    In many cases we loose root, random freezes, bootloops, lot of of fcs and error.

    They are just taking bases and implementing regular stuff.
    I can understand your frustration though I think it's possibly misplaced.

    Xiaomi are the reason for most, if not all, the issues afflicting custom ROM users. It was the same story on the last Xiaomi device I owned - they don't keep sources that developers rely on up-to-date.

    Vince hasn't had the smoothest ride when it comes to bugs - even as I type this my touchpanel goes unresponsive here and there. But it's the same in MIUI. Xiaomi have pretty much orphaned the Redmi 5 Plus. Updates were repeatedly stopped and eventually dried up completely. They never fixed the issues with this device. If they'd taken the time to fix them and release the fixed code to developers, the story might be different.

    With that said, the few developers here on XDA have worked to make Vince usable as best they can with the expertise they have and the time they have. Vince isn't as popular as the mainline note series or a Snapdragon-based flagship. There's less owners and likely less devs than in the sub-forums for other devices.

    They also work on these ROMs as a hobby in their free time, for free (with likely very few donations). They're not accountable in the same way Xiaomi is - their developers are paid a salary and it's much fairer to expect a working product from them and complain when that isn't delivered.

    Now back to bugs - for the most part Vince is in good working order. Camera issues have been around for a while and that's entirely down to Xiaomi not releasing fixed drivers. There's a few other known issues highlighted in the thread - but for the most part, things work.

    Then there's "bugs"; I use quotations because there's too many users not following best practices when flashing ROMs. A lot of issues encountered just cannot be replicated on a clean installation of most ROMs. The amount of users who don't understand how to push a stock image is worrying - but also OK in that this is a community and we should be open for all levels of expertise.

    You mentioned developers hit the home-screen without any modifications. But the issue here is that when you combine other code from other projects things can go wrong. V4A for example is outdated and just wasn't made to run on Q. It's been repeatedly ported forward using hacks and whatever can be done to just get it working. The same can be said of many projects which are still barely getting things right so shortly after Pie. It's not a ROM dev's responsibility to make sure anything else (such as a custom kernel or a random Frankenstein vendor image) works unless their code is implicated.

    On a final note it's worth taking the time to understand that ROMs might not be so easily compiled as you might think - that is, I don't think they're simply 'taking a base' and applying regular stuff.

    I tried myself and it's not straight-forward or easy to understand; if it was we'd have every other user doing it. Once you start trying to figure out what everything means within the Android documentation for compiling ROMs you'll find you're in way over your head and a bit frazzled.

    That doesn't mean devs should be revered as the all-knowing gods of custom ROMs (no one is better than anyone here) but they do deserve your gratitude. Things like "this is broken/fix it now" would probably get you grizzly after hours of working on and testing out a new nightly.
    11