Related
Good day Android world. I am (sadly) a noob trying to (nervously, excitedly) step my game up with a new Nexus 4. I have played around with the stock ROM and my smartphone experience for the last week+ transitioning from an ancient blackberry. Below are my preliminary questions/views based on research that I am posing to the community. Many thanks for your help and patience!
- I want to embrace the customization experience and root/flash accordingly. I downloaded the N4 toolkit from dev 'mskip' and the instructions have been very clear. I am just waiting on the update to the toolkit once my donation posts before I plunge in. First basic question: if I root/tinker and then relock bootloader/flash stock ROM, is my warranty still intact? Can't Google detect some trace/fingerprint of my activity that they can use to void my warranty or does relocking/flashing stock really cover me? Has anyone had a warranty experience tested on this basis?
- Can I use the toolkit to do a full NANDROID backup of my device as-is before any root? It mentions an insecure boot image, but when I run the backup, the code says 'adbd can't be run on production builds.' Any suggestions? I doubt I will use my current phone state, but I would love to have the full backup available (just in case) before I wipe the device during rooting.
- My view on performance optimization based on research and N4 use is that I am probably good with the stock ROM, albeit perhaps deodexed and zipaligned (thanks Android wikia for those definitions!), though I get the impression that the Matr1x kernel will help me get more performance and bang for my buck on battery, since my only gripe thus far is battery as I lean on the cloud extensively for music (mediaserver hits my battery, though still secondary to screen). Does anyone think there is a better battery optimizing kernel than Matr1x?
- If I have a slightly modified stock ROM, i.e. deodexed and zipaligned, will Google still provide me with auto-updates to the ROM/OS on a timely basis as with the pure stock users?
- Do I download the custom/stock ROMs to my PC for all customization? Or can I do customization through the phone directly once root is achieved through an app like ROM Manager?
- It sounds like the phone is still faster on stock ROM rather than at least the CM10.1 option? Are there any other custom ROMs that are stable and allow a superior phone performance than the stock? As I said, I will likely keep stock for now because I believe Google has a good handle on their software, but would love to hear your thoughts.
- I am a little hesitant about the overclocking/undervolting that certain custom ROMs/kernels afford based on a couple threads I have read on long-term hardware impacts. The no-frills CPU option does seem reasonable with the Matr1x kernel though. Can anyone share a configuration (deep sleep, etc.) that they think works best for the N4 battery without compromising hardware integrity/durability? I will dig into this once I flash the Matr1x kernel
- Apps: I like Juice Defender, but my battery improvement on stock seems to have regressed a bit since I switched to Go Launcher EX. Is this the reason? Maybe the Switch widget?
Sorry this is so long. Thank you for your time and willingness to help!
I have unlocked my bootloader, rooted with Magisk and flashed AsopExtended Rom. Very happy with the performance of my A2017U as it is right now. My question to ya'll is, What would be the pros and cons of returning to complete stock (for OTA updates) or sticking with rooted and custom rom and not being able to receive OTA updates?
whats the question here? Its on you... what you prefer
Lol that depends of your needs - I stick to stock because of audio (mostly) and somehow bcz of camera (as far as I know you can install stock camera app).
That's question is a little bit irrevelant when you was stock and now you are testing custom rom.
So the answer is simply - replay to your question by yourself and with margin to your needs.
Had to test the waters with custom roms on this phone, but was just wanting to hear other peoples thoughts on the subject. I've always tinkered with customizing my phones and enjoy doing so. Would like to hear different points of view and then see if it would make me change my mind. Sometimes custom roms have little bugs that people can or can't live with, and in some cases stock is best for total functionality. Just curious of others opinions.....
amaury48 said:
Had to test the waters with custom roms on this phone, but was just wanting to hear other peoples thoughts on the subject. I've always tinkered with customizing my phones and enjoy doing so. Would like to hear different points of view and then see if it would make me change my mind. Sometimes custom roms have little bugs that people can or can't live with, and in some cases stock is best for total functionality. Just curious of others opinions.....
Click to expand...
Click to collapse
IMHO custom ROMs are littered with bugs, but mostly overlookable. Take the phone bug or storage with SD card bug for example.
Stock works better in every regard (except substratum, damn you mifavor) and with MiFavor 5 this is even truer. But if you like your current ROM there's no reason to go back...
Choose an username... said:
IMHO custom ROMs are littered with bugs, but mostly overlookable. Take the phone bug or storage with SD card bug for example.
Stock works better in every regard (except substratum, damn you mifavor) and with MiFavor 5 this is even truer. But if you like your current ROM there's no reason to go back...
Click to expand...
Click to collapse
Yeah, I finally went back to stock B25 via the DrakenFx method to retain root and custom recovery. I came across the phone bug on my custom rom and that helped me make my decision to go back to a stock rom.....
Yep, used custom ROMs from the first week of owning the phone until about a month ago when I went back to B25 with Magisk. Couldn't be happier.
I was about to make a similar thread myself but saw this one. I have been running custom roms since day one but have been considering returning to stock.
A brief summary of the benefits:
Reasons to go with stock:
Fully functional ZTE camera app with no bugs - This is perhaps more important than you might think, ZTE haven't enabled the Camera 2 API which means its very possible we are going to get the best quality and feature-set by sticking with the stock app. If ZTE haven't released their blobs there could very well be reasons to stick with the default camera app...not only that but I like it. You can install the mod, but there are aspects that will never work and some roms and kernels play more nicely with the mod than others.
Dolby Atmos app. Similar to the camera on stock this would just mean less messing about, you can of course get atmos mods in magisk but whether they work as well as the stock ZTE app I am not sure. The strange thing is I have never had the stock ZTE Axon atmos magisk mod to work on a custom rom, even though I have an Axon!
Reliability, no need to worry about force closes or apps not working, everything pretty much just works. So much less stress if you use your phone as a daily driver.
Ease of use, less features makes the phone easier to use. In some cases even when you are a tinkerer like me its sometimes good to be able to forget about continuously tweaking stuff and digging yourself in to a never ending upgrade cycle.
Oreo, it looks like if you stay stock we will see Oreo sooner than custom roms.
Reasons to go custom:
Substratum, oh boy would I miss this going back to stock. The ZTE theme engine is pants compared and I love the work that goes in to my current premium theme.
Battery life, perhaps with the aid of also a custom kernel there are some very nice roms and kernels being worked on which allow you to fully customise and save battery life.
Features, you can set the phone up exactly as you want too, every small detail can be customised. You can choose exactly which rom you like based on the features you use.
Performance, you can get more performance out of a custom rom with custom kernel and find a nicer balance between battery and performance, whichever suits you.
Fun, its fun to flash different roms and get the flashing bug. You learn a lot and get to join in with a fantastic community where people help each other.
Third option, run a debloated custom rom.
Seems to be more and more popular, as an ex Nexus 5 user I loved Cataclysm rom for this very reason. You keep all the features associated with stock with added performance benefits, fixes and less bloat. There is a downside if you plan on keeping atmos as some stock roms seem to strip it away, but it is a nice compromise between the options above. Usually these roms are more reliable as they are based on stock too. If you want a lean rom that just works, this may suit you!
Its such a hard choice and one I still havent decided on, if I have missed anything please let me know!
Background info and summary:
My first smartphone was a ZTE blade 2 and it was a beast for the money, this phone is tremendous too. My GF owns a pixel and apart from the camera this phone trumps it for value no question...for less than half the price.
I have to say though, I do miss the days of my Nexus 5 and the larger mod community, I realise these days have gone now with google devices but perhaps next time I will opt to go to Oneplus just so I can trust a bit more that there will be less caveats going custom as if there is one complaint I have with ZTE it is their unwillingness to release their source code for the little tiny things like the camera api and atmos.
Dodgexander said:
I was about to make a similar thread myself but saw this one. I have been running custom roms since day one but have been considering returning to stock.
A brief summary of the benefits:
Reasons to go with stock:
Fully functional ZTE camera app with no bugs - This is perhaps more important than you might think, ZTE haven't enabled the Camera 2 API which means its very possible we are going to get the best quality and feature-set by sticking with the stock app. If ZTE haven't released their blobs there could very well be reasons to stick with the default camera app...not only that but I like it. You can install the mod, but there are aspects that will never work and some roms and kernels play more nicely with the mod than others.
Dolby Atmos app. Similar to the camera on stock this would just mean less messing about, you can of course get atmos mods in magisk but whether they work as well as the stock ZTE app I am not sure. The strange thing is I have never had the stock ZTE Axon atmos magisk mod to work on a custom rom, even though I have an Axon!
Reliability, no need to worry about force closes or apps not working, everything pretty much just works. So much less stress if you use your phone as a daily driver.
Ease of use, less features makes the phone easier to use. In some cases even when you are a tinkerer like me its sometimes good to be able to forget about continuously tweaking stuff and digging yourself in to a never ending upgrade cycle.
Oreo, it looks like if you stay stock we will see Oreo sooner than custom roms.
Reasons to go custom:
Substratum, oh boy would I miss this going back to stock. The ZTE theme engine is pants compared and I love the work that goes in to my current premium theme.
Battery life, perhaps with the aid of also a custom kernel there are some very nice roms and kernels being worked on which allow you to fully customise and save battery life.
Features, you can set the phone up exactly as you want too, every small detail can be customised. You can choose exactly which rom you like based on the features you use.
Performance, you can get more performance out of a custom rom with custom kernel and find a nicer balance between battery and performance, whichever suits you.
Fun, its fun to flash different roms and get the flashing bug. You learn a lot and get to join in with a fantastic community where people help each other.
Third option, run a debloated custom rom.
Seems to be more and more popular, as an ex Nexus 5 user I loved Cataclysm rom for this very reason. You keep all the features associated with stock with added performance benefits, fixes and less bloat. There is a downside if you plan on keeping atmos as some stock roms seem to strip it away, but it is a nice compromise between the options above. Usually these roms are more reliable as they are based on stock too. If you want a lean rom that just works, this may suit you!
Its such a hard choice and one I still havent decided on, if I have missed anything please let me know!
Background info and summary:
My first smartphone was a ZTE blade 2 and it was a beast for the money, this phone is tremendous too. My GF owns a pixel and apart from the camera this phone trumps it for value no question...for less than half the price.
I have to say though, I do miss the days of my Nexus 5 and the larger mod community, I realise these days have gone now with google devices but perhaps next time I will opt to go to Oneplus just so I can trust a bit more that there will be less caveats going custom as if there is one complaint I have with ZTE it is their unwillingness to release their source code for the little tiny things like the camera api and atmos.
Click to expand...
Click to collapse
Some comments about this:
-Stock still has RRO support, so while it is kinda craptastic to use substratum this way, it is doable. I have most of my apps with Swift Dark (the ones that don't force close anyways) and Lawnchair with black theme, on MiFavor 5 which already has a rather black quick settings screen. The result is awesome
While you might be getting more battery life from a custom ROM, I totally disagree on the performance part. Everything works just slower. But yeah, battery-wise I got 7h SOT once which is absolutely bonkers :silly:
If you want a nice modded stock try any MiFavor 5 modded ROM like RDX or ADM Team. Those keep Atmos and use MiFavor 5 B13, which seemingly have a new camera app?
Choose an username... said:
Some comments about this:
-Stock still has RRO support, so while it is kinda craptastic to use substratum this way, it is doable. I have most of my apps with Swift Dark (the ones that don't force close anyways) and Lawnchair with black theme, on MiFavor 5 which already has a rather black quick settings screen. The result is awesome
While you might be getting more battery life from a custom ROM, I totally disagree on the performance part. Everything works just slower. But yeah, battery-wise I got 7h SOT once which is absolutely bonkers :silly:
If you want a nice modded stock try any MiFavor 5 modded ROM like RDX or ADM Team. Those keep Atmos and use MiFavor 5 B13, which seemingly have a new camera app?
Click to expand...
Click to collapse
Thanks I will give ADM a try first since RDX seems to exclusively for the A2017 and I own the A2017U.
Frankly when I saw substratum without OMS support before I wasn't impressed but it sounds like it's worth a look.
Performance wise I loved running AOKP. It runs so much faster than resurrection remix and faster than my brief time on stock also.
It's a pain sacrifices have to made somewhere, but I guess you can't argue for the money!
Dodgexander said:
Thanks I will give ADM a try first since RDX seems to exclusively for the A2017 and I own the A2017U.
Frankly when I saw substratum without OMS support before I wasn't impressed but it sounds like it's worth a look.
Performance wise I loved running AOKP. It runs so much faster than resurrection remix and faster than my brief time on stock also.
It's a pain sacrifices have to made somewhere, but I guess you can't argue for the money!
Click to expand...
Click to collapse
I think you simply have to flash the univ bootstack and your modem file to install RDX, it just wasn't tested on other phones but the A2017. but yeah, just use ADM Team
If we don't get Oreo, I will root mine, debloat etc and unroot just to keep it stock but lean. Stock camera in Nougat is quite good IMO. Atmos is pants but I will leave it alone.
RobboW said:
If we don't get Oreo, I will root mine, debloat etc and unroot just to keep it stock but lean. Stock camera in Nougat is quite good IMO. Atmos is pants but I will leave it alone.
Click to expand...
Click to collapse
what's the downside of having it rooted?
Some apps don't work and it has to be secure for work use.
RobboW said:
Some apps don't work and it has to be secure for work use.
Click to expand...
Click to collapse
Magisk then...
Choose an username... said:
Some comments about this:
-Stock still has RRO support, so while it is kinda craptastic to use substratum this way, it is doable. I have most of my apps with Swift Dark (the ones that don't force close anyways) and Lawnchair with black theme, on MiFavor 5 which already has a rather black quick settings screen. The result is awesome
While you might be getting more battery life from a custom ROM, I totally disagree on the performance part. Everything works just slower. But yeah, battery-wise I got 7h SOT once which is absolutely bonkers :silly:
If you want a nice modded stock try any MiFavor 5 modded ROM like RDX or ADM Team. Those keep Atmos and use MiFavor 5 B13, which seemingly have a new camera app?
Click to expand...
Click to collapse
Just installed adm rom and substratum but can't get any themes to work at all. Substratum appears to work and let's me install them but after a reboot they don't work.
I tested with the Google app, gmail and chrome amongst others. I am using swift black.
I guess it's just a bug with the adm Rom? Magisk is working fine I think.
Dodgexander said:
Just installed adm rom and substratum but can't get any themes to work at all. Substratum appears to work and let's me install them but after a reboot they don't work.
I tested with the Google app, gmail and chrome amongst others. I am using swift black.
I guess it's just a bug with the adm Rom? Magisk is working fine I think.
Click to expand...
Click to collapse
It can't be because I had everything themed on ADM ROM too. Except system ui and that stuff since it can't be themed. no idea why that happens.
Choose an username... said:
It can't be because I had everything themed on ADM ROM too. Except system ui and that stuff since it can't be themed. no idea why that happens.
Click to expand...
Click to collapse
Were you using the new release with version 5 of mifavor?
What about systemless host list in magisk enabled to get adaway to work?
Only two things I have changed. I am using A2017U with the b13 bootstack.
Haven't changed anything else so no idea why it isn't working.
Dodgexander said:
Were you using the new release with version 5 of mifavor?
What about systemless host list in magisk enabled to get adaway to work?
Only two things I have changed. I am using A2017U with the b13 bootstack.
Haven't changed anything else so no idea why it isn't working.
Click to expand...
Click to collapse
i was using the old release with version 5 (ADM Team V3)
I would stick with stock unless you are an extreme power user. ZTE fixed 99% of the issues with MiFavor with 7.1.1 and custom ROMs are littered with SO MANY little bugs. MiFavor is extremely stable now. Audio and camera is also much worse on custom.
But hey whatever you prefer.
Do you have Stock or Custom Rom and why?
The vendor firmware landscape has been increasingly adequate for quite some time, providing multiple viable options for a satisfactory mobile experience - buying a device with the intention to separate from its out of the box experience as much as possible no longer makes a compelling case against the unique, and sometimes identity-forming, features provided as stock.
During earlier years, Android, and mobile firmware in general, was controlled by regulations and risks while expanding an entirely new platform. There is no alternative otherwise, and anything less conservative would border reckless abandon.
This paved the way for many enthusiasts under no control to have immersed themselves into the technology like the career engineers and developers were doing, but with the nearly full freedom to test ambitious ideas and solutions unlike their professional peers, who were often limited to free time and with no expectation of something even as simple as maintaining a message board OP exploring those ideas.
This allowed many of those ideas to manifest and be thoroughly tested by many and with an unmatched diversity of real-world usages and trending philosophies. This is when many projects helped form several of the early features unique to the Android platform, absorbing a substantial portion of the risks without fear of retribution, allowing the vendors to devote more time to polish and fine-tuning and less time devoted to brainstorming ideas and risk scenarios.
This afforded the hobbyists a custom platform having quite the head start and that could distance itself from the vendor experience in features, accessibility, and form.
Custom rom's had a different identity then than custom rom's do now, and that is with good reason as well.
Ignoring the few debatable exceptions, custom rom's are currently little more than variations or slight modifications of vendor firmware or AOSP. I exclude CM/LOS simply because CM was among the hobbyists described earlier.
With the feature gap as narrow as it currently is with Mr. Rom Dev and Mr. Lead Software Engineer, the professionals now enjoy an edge with often unlimited resources available providing an experience that is hard to match or exceed with limited time and resources, so users today understandably gravitate towards the familiar vendor experience with a manageable number of features or tweaks.
Of course, even in a market of no stock, consumer demand still determines the custom software landscape.
The benefit today is that ideas and solutions require an extraordinary amount of ingenuity and progressive thinking to stand out and enjoy active development for more than six months. The breakthroughs are far fewer but they are also more impactful in pushing the platform forward.
Having said all that, my purpose for exclusive use of vendor firmware is for hobbyist development reasons. I see no benefit a custom rom would provide for development. I mean, if it works, great. But, if it works only because of the rom, you have essentially prepared something to share among a fraction of one device's users.
If something fails to implement into the vendor firmware, I move on to something else. If it works great for some custom rom's, "Cool, man!", if not, a user has the choice to use the only firmware a developer could logically assume is in use.
So, put gh down for Stock! :good:
Yes, but with custom rom you can have better battery stats. You can also have fewer google apps.. And many more.
I use xXx NoLimits: a stock-based custom ROM. It meets all of my needs. Therefore, I have no reasons to try anything else.
lazostat said:
Yes, but with custom rom you can have better battery stats. You can also have fewer google apps.. And many more.
Click to expand...
Click to collapse
I'm getting 10-12 hours of screen on time and idle time is about .3-.6% drain let hour on stock on OOS. There isn't anything custom out there giving anything better.
Eric214 said:
I'm getting 10-12 hours of screen on time and idle time is about .3-.6% drain let hour on stock on OOS. There isn't anything custom out there giving anything better.
Click to expand...
Click to collapse
This.
Getting 10-11h SoT every cycle with stock ROM. Got 11ish hours the other day with almost 3 full days without charging.
Haven't seen anything better or much better then THIS.
lazostat said:
Yes, but with custom rom you can have better battery stats. You can also have fewer google apps.. And many more.
Click to expand...
Click to collapse
Stock firmware does not necessarily need to remain "untouched".
Perhaps, a more accurate answer would be that my preference for a foundation on which to tailor to my specific needs is the stock OxygenOS firmware. It is certainly rare for users with root access to refrain from making a single change to the installed rom, be it custom or stock. :good:
With this phone it is the first time I've had to come to accept that stock is king, no custom rom compares to it, I've tried them all (yes this is subjective). Stock + a custom kernel + viper4arise and off I go.
I dont know if you count it as stock or custom since it is both but i use HydrogenOS and my own modification of its stock kernel. Im used to 9 hours SoT+ with .2% standby drain per hour. No performance sacrificed. Ill vote in the poll once u verify which u factor hydrogen os as.
tWoBrO said:
This.
Getting 10-11h SoT every cycle with stock ROM. Got 11ish hours the other day with almost 3 full days without charging.
Haven't seen anything better or much better then THIS.
Click to expand...
Click to collapse
ok can you provide more insight? how you get it done......i average about 4-5.5 hours sot over two days........idle drain at1.33 and active at 12.55.
How I get it done? Everyone uses the phone differently, have different apps installed, etc.
Last few days I have used Wi-Fi 99% of the time, always on, Facebook, IG, Tapatalk (a lot), Gmail, Movies HD (a lot), Terrarium-tv (a lot), YouTube, a couple calls and sms here and there, but not much, Messenger, Chrome and app-like-Spotify with bluetooth on the car. I turn on location and bluetooth only when I need it.
Auto brightness is on, always on the low side, dark theme on, turned off vibration on touch (because of the double vibration bug in Oreo), turned vibration of on keyboard touch too (have sound on instead, I like the type writer sound when I type).
Let me see, I do have privacy fix module and sysconfig patcher installed on Magisk. This last one might gave you a boost in battery, but to be honest I don't even know if it actually works.
I would say that having a dark theme, screen brightness on the low side, and not having EVERYTHING turned on all the time are what makes the difference for me. I'm sure if I have bluetooth and location on, for example, all the time, when not needed it, it will cut a my time quite a bit.
Oh, I have notice that talking on the phone takes a lot battery. I don't talk that much on the phone, just those quick 30s-5m calls to ask a quick question or whatever.
I had great battery life out of the box with Nougat, but Oreo really made a huge difference. I'm talking about 2-3h of SoT on Oreo compared to Nougat.
Stock atw and ftw!
Finn the moment the phone I get breathes it's getting a custom ROM.
Always.
For a device like OnePlus 5, a custom ROM isn't really needed since the stock ROM is pretty much debloated and already offers a bunch of features.
Custom ROMs still offer many more features than any stock ROM though. They also get faster updates and for far longer. By the time OnePlus stopped providing updates to this device, custom ROMs will still be updated most probably.
I haven't flashed any custom ROM yet because the stock ROM has almost everything I need. The main reason I flashed ROMs was performance. The OnePlus 5 isn't lacking in this area.
Pure fusion, the Nougat version. It's the smoothest of all ROMs that I tried, has lots of settings and supports stock camera.
Codename Phoenix. Oreo 8.1, Very few bugs and for me a lot better than Stock. From the same dev making Pure Fusion.
CT-CRC said:
With this phone it is the first time I've had to come to accept that stock is king, no custom rom compares to it, I've tried them all (yes this is subjective). Stock + a custom kernel + viper4arise and off I go.
Click to expand...
Click to collapse
How a custom kernel can help? I installed bluspark but i dont see additional settings.. How to make us of it?
CT-CRC said:
With this phone it is the first time I've had to come to accept that stock is king, no custom rom compares to it, I've tried them all (yes this is subjective). Stock + a custom kernel + viper4arise and off I go.
Click to expand...
Click to collapse
Totally subjective and IMHO completely not true, you are hindered without root and without the ability to alter your phone in a positive way, not only for longevity of battery life but also in regards to performance, stability and stamina.
Stock does not compare to custom in any way for me.
Optimized custom rom could be great when the device is old, and no more supported.
Also, back in the days, let say with Gingerbread 2.3.x, not much nice/modded feature were present. Now, from what I can see, stock roms got almost everything.
OP5 is so fast rigt now, even if stock is heavier, we won't see much difference with a lighter rom.
But looking forward for custom roms in 2-3 years.
WELCOME TO THE SNAPPATCH[ Featured by DroidViews and XDA ]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME THINGS ARE DIFFERENT TO THE STOCK SNAPPATCH
PLEASE MAKE SURE YOU ARE USING THE RIGHT VERSION FOR YOUR DEVICE / ANDROID OS VERSION AND VARIANT
ABOUT THE PROJECTStarted on the Nexus 6, Years ago is the Patch the Result of evolving custom ROMs to something more. Instead of uploading My Changes combined with a OS, is the POM just delivering the wanted Edits. It can be applied on top of any OS, and makes Android Updates independently from My Work. The latest and already 5th Revision of the POM is called Snappatch, and made for Snapdragon Xperia Devices running the very latest AOSP Systems. Coming with a huge amount of exclusive Configs and Optimizations is the Patch unleashing Your Device on a unexpected Way. You will raise the Performance, Efficiency, and Quality of the whole System, besides adding Features and Services which are not available on unpatched AOSP ROMs. The POM comes also with a Rooting Solution, Busybox and the full set of needed GApps to provide a great Pixel like Experience with the barely minimum of needed Apps out of the Box. Based on 8 Years of research and testing, made with Passion! The Snappatch sets Quality over Quantity...
Already adapted by Others for Stock Firmwares is the Snappatch still the first and Original Patch System. You will face it all over XDA in the next Years! Be Part of the Patch Revolution, get Patched!
FEATURES
Latest Busybox with 400+ Applets
Magisk Stable Root included
SafetyNet Passing Changes
Pixel Stock Firmware Content
Xperia and Pixel UI Sounds
Added advanced VR Capabilities
Added Features and Services
Optimized Google Apps Set
Optimized Camera Handling
Optimized Display Handling
Optimized Rendering Handling
Optimized Storage Handling
Optimized Services Handling
Optimized Multitasking Handling
Optimized Audio Handling
Optimized Microphone Handling
Optimized 4K & HDR Handling
Optimized Hardware Handling
Optimized Software Handling
(Features are summarized to keep the overview)
(Don't trust Lists, try it out by Yourself)
SUMMARY OF THE DEVELOPMENT
-Camera Configs can be still improved (Implented not all Configs right yet)
-Some Camera Apps may not Work. Recommended are:
--Snap Camera HDR (Play Store)
--Open Camera (Included / Play Store)
--Google Camera Mods (Some are working, others don't)
-Some Equalizers don't Process (Audio is routed different)
SUPPORTED AOSP DEVICES (BLUE, EXCEPT NILE DEVICES)
Possible that the AOSP Patch works also on other Snapdragon Devices. Use at Your own Risk!
SPECIAL THANKS TO
@D daydream for buying Me the Daydream View 2017! No VR Development with You!
XDA:DevDB Information
[POM] SNAPPATCH, ROM for the OEM Cross Device Development
Contributors
Miustone, Miustone, Miustone, Miustone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: ANDROID 8.1 / SDK 27
Version Information
Status: Snapshot
Current Stable Version: 102
Stable Release Date: 2018-05-20
Created 2018-04-13
Last Updated 2018-05-20
Fundamental:
Feedback:
-Which Device are You using?
-Which Patch Version are You using?
-Which Android Version are You using?
Before posting:
-Read, read, read! Make sure You've seen the whole Thread
-Make sure You've followed the Instructions from Post 3
-Make sure You're using the right Patch for Your OS (STOCK / AOSP)
-Make sure You've not used other Mods which could cause Bugs
Infos:
Instructions:
-Can be found on the Snappatch Website
Additional:
-- Pixel Stock UI Overlay
-Download and install Substratum
-Download and install a Theme
-Apply the Theme over Substratum
-Go to Settings / Display Settings
-Search for the Design Option
-Tap the actual Option (Theme Name)
-Select the Pixel Option
-Done
(Works best with the open Source Pixel Theme App)
-- Kernel Optimization
-Disable Touchboost on all Cores
-Underclock Your Cores to Max. 2GHz and 1,5GHz (Big - Little)
-Set the CPU Governors to Interactive and Conservative (Big - Little)
-Set the GPU to Max. 401MHz
-Set the I/O Sheduler Read-Ahead to 1024kB (Internal)(External may be slower = 512kB)
Download:
Snappatch Website
Please consider a Donation if You like My Work! [PayPal.Me] [Gift Code]
Love the XZ Premium with My Snappatch and AOSP! Better as Stock, and i hope You will all enjoy it as much as i do! May the Journey begin...
New Version up in 10 Minutes! Happy flashing :angel:
link is not working:
https://goo.gl/SB2GH6 – this goo.gl shortlink has been disabled. It was found to be violating our Terms of Service. Click here and here for more information about our terms and policies respectively.
nevenx said:
link is not working:
https://goo.gl/SB2GH6 – this goo.gl shortlink has been disabled. It was found to be violating our Terms of Service. Click here and here for more information about our terms and policies respectively.
Click to expand...
Click to collapse
I'm sorry, here You go: https://sites.google.com/view/snappatch
Ubuntu font and Audio enhancements were awesome. I am going to miss them. Ubuntu font was working fine even in my car infotainment system when using Android Auto link. Are you going to release the removed patches as a separate patch?
Will it still be compatible with other non Sony devices such as the ZTE Axon 7 ?
Oki said:
Ubuntu font and Audio enhancements were awesome. I am going to miss them. Ubuntu font was working fine even in my car infotainment system when using Android Auto link. Are you going to release the removed patches as a separate patch?
Will it still be compatible with other non Sony devices such as the ZTE Axon 7 ?
Click to expand...
Click to collapse
Great to see You here! So since AROMA is removed and some ROMs and Apps are delivering a Font Changer have i just removed it for now (I still use the Font here with the Carbon ROM on the XZP). The Audio System will be redone a bit to work better with Xperias and less dependencies. Think i will add it back in some Weeks. Same for AROMA. Since it's buggy as Hell (3.0 is a Beta since 2015), and totally fails on the XZ Premium TWRP am i still looking around for a fix. Hopefully am i soon able to add it back, and with it comes another rework of it (Better Structures, Texts etc.).
And Your last Question. Yes, it will still work on the Axon 7 and other Devices. But there is One Thing i already discovered, the new Camera Configs are destroying the Camera Previews on Apps like Open Camera. It shows just some green Fields and may also have Problems on recording. Only way around it would be to remove all Lines containing the word "Camera" in the Snap Prop File. Unfortunately will it not be possible to inject Custom Props while installing since AROMA isn't included anymore, means You need to extract the File out of the ZIP and Copy it back after Editing (Or repacking the ZIP). Wish i could handle that somehow else, but like said, no AROMA no Options :/
Let Me know how it goes and what You think! Will do my best to help out!
EDIT: Default DPI is now 400, may be a bit small on the Axon 7 Think i will at least share a working Prop for non Xperia Devices in the next Days. Should be easy to handle that with Updates since i know what's needed to be changed and removed. Hope that Helps a bit...
Is it possible someone could link a video of this working please? Really interested in this and it may be what stops me from selling my xzp. Would really like to see if the camera is improved as its really not that good compared to others, that's the main reason I'm thinking of selling it. Thanks for all the hard work too
@Miustone
YOU ARE A GENIUS :cyclops:
Installed last Carbon and your patch without issues. My XZP is like having a new life now
Thanks a lot :good::good::good:
I'm waiting for reviews, bcs I think lossing warranty right now is not my opinion. If anyone can tell a little bit about battery life on custom roms, camera distortion and etc, I would be very thankful.
I just tried flashing this along with the Carbon (lastest file) all I get is stuck at the Sony screen.
Works great. Camera quality still isn't up to stock, but it's noticeably better. Can't speak too much for audio, since I use viper anyways, but there's no distortion. Phone is running very smooth and cool. G8142 running carbonrom btw.
Mjkb said:
Is it possible someone could link a video of this working please? Really interested in this and it may be what stops me from selling my xzp. Would really like to see if the camera is improved as its really not that good compared to others, that's the main reason I'm thinking of selling it. Thanks for all the hard work too
Click to expand...
Click to collapse
Well, i would keep the XZP. The Camera is better as on other Devices (ZTE, Xiaomi, One Plus, Essential, Wiko etc.) after patching AOSP. The only better working Camera i know will You find on HTC, or Samsung, but Samsung is out of the Race since they force Snapdragons to be not unloackable and Exynos without Sources for AOSP. After using a Nexus, a LG and a ZTE Device do i stick for the next Years with SONY again. They publish great Sources and Tutorials and are just delivering great Support for all kind of Android Stuff. That's also why i think that AOSP is better than Stock...
enricostella said:
@Miustone
YOU ARE A GENIUS :cyclops:
Installed last Carbon and your patch without issues. My XZP is like having a new life now
Thanks a lot :good::good::good:
Click to expand...
Click to collapse
Thanks for the Positive Feedback! Hope You will enjoy it and that we soon get more AOSP Goodness!
nevenx said:
I'm waiting for reviews, bcs I think lossing warranty right now is not my opinion. If anyone can tell a little bit about battery life on custom roms, camera distortion and etc, I would be very thankful.
Click to expand...
Click to collapse
Which Warranty? Software Warranty? You will just loose the free Service of unbricking Your Software on the Device after unlocking. 99% of the Hardware Damages will be still covered (Like failing Materials, Buttons, Ports etc.). Software Warranty is really something for People outside of XDA. As long as You have a PC, a unlocked Bootloader and Firmware is there almost no chance of turning Your Device into a Brick... Just saying, i buyed My Device just some Days ago and i haven't waited a single Minute to unlock it (Since SONY has fixed all the old Xperia Device Problems like non working Camera on AOSP, washed out Display Colors and all that). Doesn't regret it! The only real disadvantage could be that it will be hard to sell Your SONY after unlocking. But if You want to keep it forever...
beammer335d said:
I just tried flashing this along with the Carbon (lastest file) all I get is stuck at the Sony screen.
Click to expand...
Click to collapse
Flashed the OEM Image?
blweldon2 said:
Works great. Camera quality still isn't up to stock, but it's noticeably better. Can't speak too much for audio, since I use viper anyways, but there's no distortion. Phone is running very smooth and cool. G8142 running carbonrom btw.
Click to expand...
Click to collapse
Hard to compare, Camera2 API and RAW alone should be worth the Switch. I also think that there is more possible in the Future once the right Configs are found (Picture Quality). Unlimited 4K recording on higher Bitrates and Framerates besides less heat from the Recording is also good to have (And should look better than on Stock). And great to hear You noticed the Performance. One of the Reasons for loving AOSP on My XZP is the fact that we don't need or have the Stamina Mode. I faced heavy Lags with Stamina besides Graphical Glitches and incredible Heat (Not matter if On or Off). Not to compare with how it is now. I played Shadowgun Legends for around a Hour and the Device was just not Hot. Same Settings on Stock caused crazy Heat and Lags after some Minutes. It's really a difference like Day and Night. Sadly does it looks like that the Carbon ROM has not the best System Animations which kills a bit the UI Smoothness. Would really love to see more AOSP ROM's to have the Choice... Maybe do i start a own One in the next Time, let's see..
BR
Miustone said:
Well, i would keep the XZP. The Camera is better as on other Devices (ZTE, Xiaomi, One Plus, Essential, Wiko etc.) after patching AOSP. The only better working Camera i know will You find on HTC, or Samsung, but Samsung is out of the Race since they force Snapdragons to be not unloackable and Exynos without Sources for AOSP. After using a Nexus, a LG and a ZTE Device do i stick for the next Years with SONY again. They publish great Sources and Tutorials and are just delivering great Support for all kind of Android Stuff. That's also why i think that AOSP is better than Stock...
Thanks for the Positive Feedback! Hope You will enjoy it and that we soon get more AOSP Goodness!
Which Warranty? Software Warranty? You will just loose the free Service of unbricking Your Software on the Device after unlocking. 99% of the Hardware Damages will be still covered (Like failing Materials, Buttons, Ports etc.). Software Warranty is really something for People outside of XDA. As long as You have a PC, a unlocked Bootloader and Firmware is there almost no chance of turning Your Device into a Brick... Just saying, i buyed My Device just some Days ago and i haven't waited a single Minute to unlock it (Since SONY has fixed all the old Xperia Device Problems like non working Camera on AOSP, washed out Display Colors and all that). Doesn't regret it! The only real disadvantage could be that it will be hard to sell Your SONY after unlocking. But if You want to keep it forever...
Flashed the OEM Image?
Hard to compare, Camera2 API and RAW alone should be worth the Switch. I also think that there is more possible in the Future once the right Configs are found (Picture Quality). Unlimited 4K recording on higher Bitrates and Framerates besides less heat from the Recording is also good to have (And should look better than on Stock). And great to hear You noticed the Performance. One of the Reasons for loving AOSP on My XZP is the fact that we don't need or have the Stamina Mode. I faced heavy Lags with Stamina besides Graphical Glitches and incredible Heat (Not matter if On or Off). Not to compare with how it is now. I played Shadowgun Legends for around a Hour and the Device was just not Hot. Same Settings on Stock caused crazy Heat and Lags after some Minutes. It's really a difference like Day and Night. Sadly does it looks like that the Carbon ROM has not the best System Animations which kills a bit the UI Smoothness. Would really love to see more AOSP ROM's to have the Choice... Maybe do i start a own One in the next Time, let's see..
BR
Click to expand...
Click to collapse
man, I agree with you in most thing, but I'm waiting for examples of RAW photos, SOT battery and a lot of things... you should start building your own aosp with those features, I'm ready to donate some cash.
Can I use this patch with z2 rr 7.1.2 ?
matrix2012xman said:
Can I use this patch with z2 rr 7.1.2 ?
Click to expand...
Click to collapse
No sorry, added a List of supported Devices to the First Post now :angel:
Updated the Thread and started working on the next Version! AROMA is still not usable without a correctly working TWRP Recovery. Really sad about this. Maybe is someone willed to help out with this? (Fixing TWRP on Xperias)
EDIT: Check out the latest Changelog Entries:
Optimized GApps Script Handling
Optimized Patch Script Cleaning
Optimized Patch Texts / Infos
Optimized Face Detection Feature
Added back Audio Libraries / Configs
Added AR / VR System Services
Added Daydream Support
Added Camera Configs / Settings
Added more Pixel Content
Added “Now Playing” Pixel Feature
Added more background Services
Added more Service dependencies
There are awesome Things coming with the next Release! Stay tuned
I caused Bootloops, mailfunctions and flashed My XZP 100 Times to come to this Point. 7 Hours of Work, and the Camera Bugs around again... I'm done for now! Good Night Folks (03:30 AM here)!
can it help aosp support dual sim cards work at same time
loukky said:
can it help aosp support dual sim cards work at same time
Click to expand...
Click to collapse
Can You explain that a bit more?
Haven't slept a Minute since Yesterday. Camera is working again but it needs still further finetuning to get even better Quality. Same for the main Audio. The Microphones are working fast and precisely, but the Output could be better. Still a upgrade compared to 18413 but i will put more work into that...
Besides that are there some nice new Features coming. Including VR Support (With Apps and Options), some more Pixel Stuff (Sounds, Configs, Services) and better Display output (Colors are more natural + better HDR Playback). I merged a lot of content from the Pixel 2 XL and updated some HTC Things and it was really worth the Time...
I never got My SONY Nexus, but this is even better since we can enjoy the full AOSP goodness with all this nice extra Features.
Really happy with My decision to go back to SONY. The next Level will be a own AOSP based OS from Me. Planning this for a long Time but SONY is finally a good Base to start with (Easy like with Google Devices)...
Enough for now, i'm really tired :silly:
Soon back with more goodness! Keep an Eye on the Changelog to stay up to date!
Code:
/*
* Your warranty is now void.
*
* I am 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 kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Join our Telegram group for faster updates and news!
Check these kernels Popcorn Kernel or Stratoshphere kernel aswell
Enigma has been and always will be a FREE PROJECT.
Introducing Enigma Kernel for Nokia sdm660 platform. Born as a hobby and because of the intense desire for me to create a kernel with what I deem useful and what I want. I will not claim for you to have god-like battery life or legendary speed, But I can surely tell you'll have a fantastic and stable experience.
Use either Franco Kernel Manager or SmartPack Kernel Manager to tweak. If you find a sweet spot that you'd share with the community, please feel free to do so
Feature requests are welcome and encouraged but please refrain from silly requests such as dev increase pubg performance please!!!! .
For more information and F.A.Q, Please check the second post.
Features -
System
- Removed HMP
- Energy Aware Scheduling(EAS)
- Scheduler modified heavily to support EAS
- Scheduler improved
- Improved Schedutil governor
- Removed Unused CPU Governors
- Load Balancing across cores improved
Hardware
- GPU Tweaks
Drivers
- Qcacld-3.0 WiFi drivers from CAF Android 10 tag(LA.UM.8.2.1.r1-04300-sdm660.0)
- Tone down WiFi driver debugging
Memory Management
- Uses LZ4 algorithm as the default ZRAM compressor
- Improved efficiency
- Misc tweaks
Miscellaneous
- Kernel size reduced
- Compiled with Google's Clang v9.0.3
- CFQ I/O Scheduler improved
- Magisk retain present thanks to AnyKernel3. No need of flashing Magisk after every update.
- Improved system responsiveness
- Improved Fluidity
- Maybe even slightly improved battery life
Installation Instructions
- Download Kramel .zip from Github
- Store it on any storage you have on your phone
- Fastboot TWRP
- Flash via TWRP
- Reboot
- Profit!
-OR-
- Download Kramel .zip from Github
- Store it on any storage you have on your phone
- Open Franco Kernel Manager and navigate to Flasher section
- Select the kernel from storage
- Tap on reboot after flashing(Don't worry, Magisk will be preserved)
- Wait for the flashing process to complete and reboot
- Profit!
FOR FULL CHANGELOGS, PLEASE REFER TO THE RELEASES SECTION ON GITHUB.
Compatible with -
> Nokia 6.1 (PL2)
> Nokia 6.1 Plus/X6 (DRG)
> Nokia 7 Plus (B2N)
> Nokia 7.1 (CTL)
Downloads - Enigma Git Releases
Old Enigma Downloads - Enigma Git Old Releases
Kernel source - Enigma Git
Github Commits Advanced Changelog - Here
Have fun and enjoy Enigma!
Feel free to post suggestions and feedback below.
XDA:DevDB Information
Enigma Kernel for Nokia SDM660, Kernel for the Nokia 6.1, 6.1+ and 7+
Contributors
CarbonGTR
Special Thanks
@paul89rulez - For being my inspiration and encouraging me.
@theimpulson - For the LOS kernel sauce on which the early Enigmas were based on.
@Sahil_Sonar - For sharing his server and encouragement. Enigma wouldn't be here if it weren't for him and Paul.
@Sid127 - Mad tester, Great Friend.
@Nikhilkumar038- Goodest Boi. Encouragement.
All the devs whom I cherry-picked from.
Version Information
Status: Stable
Current Stable Version: Back2Basics
Stable Release Date: 2021-11-20
Created 2020-07-09
Last Updated 2021-11-20
F.A.Q
1. How do I install this kernel? What Do I gain from it?
- Flash Via TWRP or Use FK Kernel Manger's Flasher option. I will also soon provide users with a .json file that you can import into FK Manager to get updates directly!
As I said in the first post, I will not claim extreme speed or hyper Battery life. But you will have a stable, fluid and satisfying experience on your phone.
2. Requirements -
- A unlocked Nokia 6.1, 6.1 Plus or 7 Plus
- A PC with fastboot working
- Stock or custom ROM that boots
- A recovery or FK Kernel Manager
3. Device Heats up alot. Can you do something?
- If your phone heats up, then you should probably consider not playing PUBG: Mobile for 5 hours on a hot day or use LTE continuously.
4. PUBG: Mobile and CODM Lags like crazy. Phone heats and up Enigma kernel dev suck!!!!
- No. I don't suck.
Heavy games utilize every last bit of resource on your phone and your phone has to keep up with all that rendering, sound processing and AI/NPC Controls while keeping a check on your BG Apps. This heavy utilization requires the CPU, Memory Controller and GPU to run at their 100% and that believe it or not produces massive amounts of heat and use a lot of battery power.
I can increase thermal throtlling thresholds but am I gonna? Nope. It is stupid and dangerous.
5. Does GCam Work fine?
- Yes since I replaced the camera drivers from Android 9 sources, Gcam mods will not be affected from shutter button not working or similar. You just have to find a stable Gcam mod for yourself and you're done
6. What about Battery Life, Performance, Fluidity - All the good stuff?
- I put a lot of emphasis on fluidity vs battery or performance because it is just terrible to use a phone that lags, stutters and cannot hold a stable 60FPS throughout the UI. These Nokia bois are perfectly capable of stable 60FPS UI rendering. Next to fluidity, I focus on performance and battery equally.
What this means for end users is that, You have a smooth, lag-free and fluid experience with balanced performance and battery life across the board.
7. HMP vs EAS? Why EAS?
- They are just different ways via which the Kernel chooses which CPU to use for the different tasks you perform on a daily basis. HMP is almost deprecated at this point and all the new phones releasing with Kernel tag 4.9 and higher come with EAS by default.
EAS is smoother and with proper configuration, more performant and efficient as-well.
8. I want to create a kernel based on Enigma's sources. Where should I start?
- Nice! You could head over to Enigma's Git repository and fork it. I'd advice you to base your work over the STAGING branch as that's the cleanest and the most stable base of Enigma.
I'd consider Enigma's sources stable as on 29-09-2021.
For in-line ROM compiling, other devs have run into issues and as such, I WOULD NOT recommend you to build Enigma in-line. I will not support you in those cases. Standalone compilers however, would have my full support.
9. Donations and what not?
- You don't need to spend more money to bring out more out of your phone. This is a hobby, not a business. Let's keep it that way
-------------------------------------------------
For More Information on EAS -
- How EAS makes Google Pixel the smoothest phone
- How EAS makes Google Pixel the smoothest phone: Reddit Discussion - This is quite a technical dive, But is quite interesting and absolutely wonderous to see top devs from XDA and other blogs have arguments.
- Kirisakura Kernel for HTC U11: General Explanation on what EAS is.
- RenderZenith Kernel for OnePlus 3: Comparison between EAS and HMP and battery life and CPU usage is affected.
- RenderZenith Kernel for OnePlus 3: Difference between the different load tracking algorithms EAS uses(PELT vs WALT).
Pro af legendary xD
Will it work with Nokia 7.2
SHLD I try
happy3777 said:
Will it work with Nokia 7.2
SHLD I try
Click to expand...
Click to collapse
Nokia 7.2 is unfortunately not supported. They have a different code base than drg, b2n and pl2.
Just a quick update - Enigma now has an working EAS variant. Expect release soon. EAS is now released. HMP is discontinued for now.
Grt work man...
new update?
Tsuragi said:
new update?
Click to expand...
Click to collapse
Check here - Enigma Releases Git
is it possible to add support for usb wlan ralink 3070?
and.. nokia 6.1 is compatible with usb ethernet adapters? i mean, support for that would be great
Tsuragi said:
is it possible to add support for usb wlan ralink 3070?
and.. nokia 6.1 is compatible with usb ethernet adapters? i mean, support for that would be great
Click to expand...
Click to collapse
Lemme look
Edit - Looked into it, Seems like I will not be able add it via kernel
Hello, do you think you could look into why the minimum brightness in novatek screens, for 7 plus, is so bright?
I tried to mess with it using i2cset but I can't control it because it's being used by the driver
dicamarques said:
Hello, do you think you could look into why the minimum brightness in novatek screens, for 7 plus, is so bright?
I tried to mess with it using i2cset but I can't control it because it's being used by the driver
Click to expand...
Click to collapse
Brightness is usually affected in the vendor side of things. Kernel just hosts the touch drivers to power on the display and recognize touch inputs. I can suggest you to switch back to the stock rom/flash stock vendor if you feel brightness isn't enough.
I do not usually play on the phone but the battery lasts much much longer, in daily use (web browsing and messaging) the performance is perfect it is fluid and energetically very very efficient. your kernel it's great
Tsuragi said:
I do not usually play on the phone but the battery lasts much much longer, in daily use (web browsing and messaging) the performance is perfect it is fluid and energetically very very efficient. your kernel it's great
Click to expand...
Click to collapse
Really appreciate the feedback! Quite glad that you're enjoying Enigma!
If you don't mind, Can you tell me which phone do you own?
CarbonGTR said:
Brightness is usually affected in the vendor side of things. Kernel just hosts the touch drivers to power on the display and recognize touch inputs. I can suggest you to switch back to the stock rom/flash stock vendor if you feel brightness isn't enough.
Click to expand...
Click to collapse
I want to lower it xD but i think its in the kernel side. I link you the file I think needs some changing.
https://github.com/archie9211/android_kernel_nokia_B2N/issues/1
CarbonGTR said:
Really appreciate the feedback! Quite glad that you're enjoying Enigma!
If you don't mind, Can you tell me which phone do you own?
Click to expand...
Click to collapse
i have nokia 6.1 (pl2)
dicamarques said:
I want to lower it xD but i think its in the kernel side. I link you the file I think needs some changing.
https://github.com/archie9211/android_kernel_nokia_B2N/issues/1
Click to expand...
Click to collapse
If it's there, It's probably there for a reason or it's a bug. But seeing the amount of display issues with 7 Plus i don't it's a bug.
Anywho, Lemme see what I can do.
I have some screenshots of the full daily battery usage, I am in the pixel experience with Enigma-WAS 08-02-2020 for nokia 6.1
I hope they serve as a reference for your good work :good:
https://imgur.com/a/1CVKaWw
Tsuragi said:
I have some screenshots of the full daily battery usage, I am in the pixel experience with Enigma-WAS 08-02-2020 for nokia 6.1
I hope they serve as a reference for your good work :good:
https://imgur.com/a/1CVKaWw
Click to expand...
Click to collapse
They are pretty good for this phone!