Database Users

[HELP] thread for custom ROMs

Hello everyone.
This is a
HELP thread
for asking questions regarding custom ROMs and the issues that you might have with them for this device. Before you post, please read the FAQs at the bottom, and then proceed to ask your question.
Note - the members may or may not provide you a step by step solution, and will provide you links, please check those links carefully, and if you still do not understand, ask your question again.​
If the community notices real issues (which are different from the usual "Does this work, does this not?" questions), it will be forwarded to the respective ROM thread (or we'll request you to forward).​
Help us in keeping the custom ROM threads clean and help the developers to focus on important issues.​

Device Specific Information
Codename athene in development circles. Here, we often use G4 and G4 Plus interchangeably with athene. That's why ROM titles have the word ATHENE in them. Don't be confused.
Device names according to manufacturer - XT16xx. The xx in the end changes as per region. For instance the Indian version is XT1643.
For more information regarding the device, and the availability of ROMs, etc, go to this [INDEX] thread.
Yes, the INDEX thread is mine, I'm not self promoting, I'm linking this because the older one has not been updated in a long time, and no amount of messages to moderators seems to have any effect. If you wouldn't mind, please send a message to the moderator to make this the sticky INDEX thread to help Moto G4 Plus users.
​

Note: this information is out of date.
Common bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use. You can also (although the developer still won't accept bug reports) rename the fingerprints to add more (credits @mason2smart). Also, try this as mentioned by @__Maddy.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings > Display > Display Size) to the default one.
Video playback issues. Please use this thread by @strongst for providing logs and other details. The only OS that doesn't seem to be affected by this is Vanir.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage. Credits @smitharro, here.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
VoLTE issues. Follow the instructions on this thread, if that doesn't help we need logs, or we really can't help.
Mobile data intermittently stops working. See this post.
CyanMod/RR bugs​
Camera issues. Update in next build.
CypherOS bugs​
Video Recording doesn't work. Use Footej/Cameringo Lite for now.
External SD read error in inbuilt file manager. Use another file manager.

LOGS
(and why we keep asking for it.)
Imagine you make a cake. And you give it to a person, who says he doesn't like it. And then leaves. You have no idea what went wrong with your food, why that person doesn't like it, what that person would see as an improvement in your cake. You eventually go mad as more people keep saying they don't like your cake, and leave without further information.
This is exactly what happens when you state your bug (that the developer cannot easily reproduce) and then leave it at that. The developer cannot figure out what went wrong. So, to find out what could possibly have gone wrong, (s)he requires a log. The log tells the developer what all errors have occurred, and what could be done to possibly fix them.
Logs are also known as logcat (and other types). Find a helpful tutorial on how to take logs here.
Best way to present logs is to either upload the file to a hosting site, or paste the contents on pastebin, or hastebin, and share the link here.​​

How to report issues here​The aim of this thread is to become a source for all members to ask questions on issues they face in all ROMs. So report your bug after specifying the ROM, and the build date. For instance, if I am using CyanMod from Silesh.Nair, which he uploaded for use on 21st April 2016, then I start my issue as
CyanMod 20160421
and we'll help you sort out your issues as much as we can, and if we are stumped, the developers will help you out. ​​

Okay, last one, stop.

Solution For Single FP over MM baseband
If anyone don't want to Flash Nougat Soak or Modem, follow this procedure ( I'm using 5 FP over MM baseband )
** Firstly you will need Fresh start **
On fresh start complete setup wizard process, DON'T add security and FP when asked..
After seting up device go to
settings > security
Add your preferable unlocking option,
Now for FP,
Add your 1st FP, it will get successfully enrolled,
And now you have 4 FP left to add..
** Follow common procedure for remaining 4 FP **
Now add next FP ( add one FP only)
Obviously you will get "Enrollment Error" on any next FP..
After every Enrollment Error Close Setting app completely ( Force stop is preferable, or better do reboot)
Now open Setting again and do same...
*** Note ***
Don't add next FP directly without closing Setting app otherwise you will get "GHOST FP"
You will be not able to remove those FP unless getting Fresh Start again...!!
Count how many FP you have added, i haven't tried adding 6th FP, so better to count 5 FP only..

__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
Much appreciated. Please do.

When I disconnect from WiFi after extended use on CM 14 my phone tells me I'm offline. I have to reboot to use network even though it was still connected... On xt1644...
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
If you rename each fingerprint after adding then you can add more than one

zeomal said:
Common Custom ROM bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings → Display → Display Size) to the default one.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
Click to expand...
Click to collapse
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.

zeomal said:
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.
Click to expand...
Click to collapse
In 20161117 It's Work Perfectly

@mason2smart updated my post with long procedure, will try your suggestion and add to my post...?
Sent from my Moto G4 Plus using XDA-Developers mobile app

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
Click to expand...
Click to collapse
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?

mason2smart said:
If you rename each fingerprint after adding then you can add more than one
Click to expand...
Click to collapse
Tried and had issue that i described in my post "GHOST FP" ...!
For that procedure i described for remaining FP must be followed...?

swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
About your second question: I can't reproduce that.
{
"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"
}
Are you sure you're on the latest (N) baseband?
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)

smitharro said:
About your second question: I can't reproduce that.
Are you sure you're on the latest (N) baseband?
Click to expand...
Click to collapse
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.

velosa said:
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.
Click to expand...
Click to collapse
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)

Silesh.Nair said:
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?
Click to expand...
Click to collapse
I'm Only Use Cm14.1 , Not Try other roms

smitharro said:
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Click to expand...
Click to collapse
You are right, but I install everything as it should be and even when I restart the device not to the sign of the sim card.I'll try again and see if it's some mistake I made.

[ROM][UNOFFICIAL][vince] LineageOS 16.0 [2019-03-14] STABLE

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Changelog :
March security patch(Android-9.00 r34)
Upstream kernel to 4.9.162 use Genom
Use MIUI camera as default
Add QC ril service blobs
Improve stability
Network monitor
Enable WiFi calling
CAF WiFi implemented
Enforced selinux
Fingerprint act like button fix
Live Display fix
More realistic padding
Fix fmradio
Update LOS newer source
And minor changes
LineageOS issue:
You can tell in comments
Instructions :
Download and Use Orangefox latest recovery. (Recommended)
Download the latest build GApps (if needed)
Reboot to recovery
Flash the latest build GApps (if needed)
Reboot
If on setup wizard system ui fc, just bypass it.
Downloads :
LineageOS-16.0-2019-03-01~3.18.136Kernel
LineageOS-16.0-2019-03-14~4.9.162Kernel
Sources :
Device tree :https://github.com/wufixx/android_device_xiaomi_vince
Kernel :https://github.com/Vince-Beast/kernel_xiaomi_msm8953
Vendor :https://github.com/Vince-Beast/vendor_xiaomi
Thanks to :
Vince-Beast Github
rama982
LineageOS
If you like Genom Kernel, stay tune on their channel~GenomKernel Channel
Last update: 2019-03-14

Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?

msssm said:
Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?
Click to expand...
Click to collapse
What are you talking about? This entire forum is for Vince not for whyred. Xiaomi made a big mess with phone names indeed...
But I assume this ROM is for Vince... If not, it should be removed and thread closed.
Sent from my Note 5 / 5 Plus using XDA Labs
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
msssm said:
Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?
Click to expand...
Click to collapse
Anyway, Vince is not treble originally, but thanks to MIUI partition scheme its perfectly treble compatible and most Pie ROMs ARE treble.
Sent from my Note 5 / 5 Plus using XDA Labs

Yes, the Xiaomi Codenames are a bit messy. I understand now that it was a confusion about my Redmi Note 5 global, which actually is a whyred and not a vince, as vince is only Redmi Note 5 and 5 Plus (this forum) but not the Redmi Note 5 global. The Redmi Note 5 glbal actually is equal to the Redmi Note 5 Pro (whyred). This was not clear from all the Codename threads from Xiaomi forums. Please correct if I'm wrong.
Beside that, both the whyred and the evince seem to have Treble projects meanwhile, while there are still native custom roms maintained. Treble for me is a big step for the future not having custom roms per device but GSI only, with Treble /vendor projects per device, mostly stripped from the stock images. But as far as there is a native rom maintained I would rather go for that. All the Treble still sounds under development and inofficial. Or would you say the opposite?

Treble is indeed something positive. But its not the panacea you think.
MIUI is not treble but uses a partition scheme that can be converted to treble if you flash a vendor on it. This is what most pie ROMs do. Of course, you can have an A only treble support, no A/B.
Unfortunately, a GSI does not work out of the box most of the times. So its always a SGSI (semi-SGI). Hopes to flash any SGI and having it work perfectly are very slim.
Treble does not offer you a free pass to try any ROM you like, just a simpler way for manufacturers to implement android on their phones.
Sent from my Note 5 / 5 Plus using XDA Labs

been using for a week. no problem so far. great rom

very nice rom for me but i have a small bug. when it comes to screen fit. i mean the edge of the screen is curve but the layout was simply straight. not a big deal but nice rom!

Great ROM, thanks dev!

I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.

niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
use orangefox recovery

niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
Use orangefox and clean flash

JR Bautista said:
use orangefox recovery
Click to expand...
Click to collapse
I am using Orange fox.

niels_kievits said:
I am using Orange fox.
Click to expand...
Click to collapse
I don't wipe the vendor. working perfectly for me

niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
Same here. It seems to be a common problem of all ROMs using mdeejay device trees. Only for certain vince versions tho. The Only ROM that works for me is Pixel Experience CAF Version. I hope this will get fixed at some point. I really like Lineage! Sadly reboot of the phone happens within maybe half a minute after first boot, so taking logs is impossible.

Does it charges the battery to 100%?

Djeypi said:
Does it charges the battery to 100%?
Click to expand...
Click to collapse
Yes it does.
If your battery does not charge to 100%, it's a known defect and you should SEARCH xda forums for the solution. There is one.
Sent from my Note 5 / 5 Plus using XDA Labs

gardiol said:
Yes it does.
If your battery does not charge to 100%, it's a known defect and you should SEARCH xda forums for the solution. There is one.
Click to expand...
Click to collapse
I already tried cleaning battery stats, calibration and even unplugged the battery and fingerprint sensor.
Still charges to 82%. If I recharge it in recovery mode, only then, it reaches 100%.
When I Flash a MIUI rom, it functions normally.
Thanks for the reply and for helping!

Djeypi said:
I already tried cleaning battery stats, calibration and even unplugged the battery and fingerprint sensor.
Still charges to 82%. If I recharge it in recovery mode, only then, it reaches 100%.
When I Flash a MIUI rom, it functions normally.
Thanks for the reply and for helping!
Click to expand...
Click to collapse
1. Open the back cover of your phone carefully (/watch?v=TuK5LYgPuKA)
2. Unplug your battery for about 5 - 10 mins
3. Re-plug the battery and re-attach back cover
4. Test if it will charge to 100%

yirmex said:
1. Open the back cover of your phone carefully (/watch?v=TuK5LYgPuKA)
2. Unplug your battery for about 5 - 10 mins
3. Re-plug the battery and re-attach back cover
4. Test if it will charge to 100%
Click to expand...
Click to collapse
Yes... I've done that twice... Waited 15 minutes the first time, 30minutes on the second time. The problem persists.
I have just flashed this ROM.
Charged to 100%.
Will be with it for a few days... Will Tell how it is then!
Thanks for helping!

TMooV said:
Same here. It seems to be a common problem of all ROMs using mdeejay device trees. Only for certain vince versions tho. The Only ROM that works for me is Pixel Experience CAF Version. I hope this will get fixed at some point. I really like Lineage! Sadly reboot of the phone happens within maybe half a minute after first boot, so taking logs is impossible.
Click to expand...
Click to collapse
I found the fix (well, workaround) for this, at least for me: If you disable the "Enhanced 4G LTE mode" in Settings > Network & Internet > Mobile Network, it works just fine without losing 4g/lte connectivity speeds (as far as I can tell now).

Seeking Android 9 ROM rec & best practices for Note 4 TMO

Requirements:
• Android 8 or 9
• Pie's "Recent Apps" UI
• Pie's Volume Slider
• want to use Samsung's GoodLock or SystemUI for enhanced Notifications
• want to use ACR Pro (Automatic Call Recording) and I don't understand if Android 9 ROMs all block call recording apps per Google policy, or if variants exist that enable call recording.
• I intend to run Nova Launcher Prime and FNG (Fluid Navigation Gestures)
• would like to assign BACK navigation function to a gesture (is that doable?)
Though I've been long-time XDA member, am actually a noob in rooting & flashing and very blind to the whole best practices concept these days: do people nowadays just root, install their preferred OS version, then just a la carte all apps? Or are there hybrids that bake in various added features & functions? For example how would I get S Note software?
• Recommended rooting method/thread?
Thanks

quicksite said:
Requirements:
• Android 8 or 9
• Pie's "Recent Apps" UI
• Pie's Volume Slider
• want to use Samsung's GoodLock or SystemUI for enhanced Notifications
• want to use ACR Pro (Automatic Call Recording) and I don't understand if Android 9 ROMs all block call recording apps per Google policy, or if variants exist that enable call recording.
• I intend to run Nova Launcher Prime and FNG (Fluid Navigation Gestures)
• would like to assign BACK navigation function to a gesture (is that doable?)
Though I've been long-time XDA member, am actually a noob in rooting & flashing and very blind to the whole best practices concept these days: do people nowadays just root, install their preferred OS version, then just a la carte all apps? Or are there hybrids that bake in various added features & functions? For example how would I get S Note software?
• Recommended rooting method/thread?
Thanks
Click to expand...
Click to collapse
Interesting list. The last Samsung Touchwiz ROM we have is Marshmallow (Android 6.0.1). Nobody can make an Android Touchwiz version higher than that for our note 4.
We do have AOSP ROMs available for android 8 and 9, and you can find them in the main note 4 snapdragon forum. Those come with some limitations. The heart rate/O2 sensor doesn't work on those ROMs. You also won't be able to run anything that requires the TouchWiz framework, so goodlock, s-note, air command all will not work. (I'm assuming good lock requires touchwiz, but I am not certain.). Oddly enough, Samsung health works great aside from the body sensors.
That being said, the S-Pen does in fact work, and there are alternatives to pretty much all those pieces of software. They might not function the same way or be as pretty as Samsung software, but they can do the job.
My recommendation is Resurrection Remix 7.0.2 (android 9-pie). It has most of the features you are looking for already (pie recents, volume slider, button mapping, and gestures). Plus it is very stable.
Otherwise, there are like 7 different pie ROMs for the note 4, each with their own features and quirks. Try them out and see what you like. Most of them do not come with google apps, but you can always download one of the opengapps packages. Then install whatever apps you want from the play store. You can also search play store for SPen and try out some note apps and other utilities.
CM SPen works well for automatically switching keyboards when you pull out the SPen. Google handwriting keyboard works well, if you like that kind of thing.
As for unlocking the bootloader and installing custom recovery and ROMs, you should be able to find instructions in this forum if you search. Otherwise, all the development is being done in the note 4 snapdragon forum now. All the AOSP ROMs are now unified development, so the same ROMs runs on different devices (International, T-Mobile, Verizon, Sprint, etc.)

Thank you so much for your comprehensive answer, sorry I missed notifications that someone had replied. I really appreciate the help!

clewis.it said:
(I'm assuming good lock requires touchwiz, but I am not certain.).
Click to expand...
Click to collapse
{
"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"
}
just looked up two articles here at XDA. Could you pls help me understand apples to apples and oranges to oranges re different OS flashing options? First article: "With Android Oreo, Samsung brought Good Lock back with a whole lot more features." Second article, pretty current, March 7, 2019: Samsung Good Lock gets updated to support Galaxy devices running One UI
Samsung’s Good Lock was first released in 2016 and it allowed users to tweak how TouchWiz looked on Android Marshmallow. With Android Oreo, Samsung brought Good Lock back with a whole lot more features. Last week, Samsung posted on their official forums that they would be updating Good Lock for One UI just in time for the launch of the Galaxy S10 family. Today, Samsung released that update.
The update doesn’t bring many new features, but it brings support for the older modules to One UI.
Click to expand...
Click to collapse
EDIT: Adding this additional article on Good Lock for 2019 by Kingshuk De of XDA: (March 5, 2019)
[Update: Available now] Samsung Good Lock app getting One UI (and Android Pie 9.0) compatibility in upcoming update
Update (8 March, 2019)
Samsung engineers pushed the update earlier than expected. You can now grab Good Lock 2019 directly from the Galaxy Store. Most of the modules have got One UI support, although some of them are still not optimized for Galaxy S10. No need to worry though, as future updates should fix them eventually.
Samsung has not removed the regional restrictions, which means the apps may not be available in your region. You can, however, sideload them easily.
Click to expand...
Click to collapse
I really am embarrassed by how clueless I am about rooting & flashing for Note 4, but better I ask than make a mess of things and waste my time: With respect to clewis.it's first answer above, I'm guessing the ROMs you recommend for the Note 4 would still not enable me to use these 2 newer releases of Good Lock, is that right? My read of the articles, and i could be very wrong, is that the Android Oreo version of Good Lock is only available to Samsung devices that were released with Android Oreo and the One UI version of Good Lock is only available for Samsung devices released with One UI. Is that right?
This goes to your question about whether Good Lock (version on 6.0.1) requires Touchwiz or not. But I'm still confused: Is it correct that in order for me to get Good Lock running on, for example, your recommended ROM Resurrection Remix 7.0.2, it would still require that someone (a) somehow extracted the GoodLock application and (b) found a way to run the GoodLock apk on rooted Samsung devices, without some kind of underlying Samsung softwre framework, is that right? (I am way out of my depth here).

Well I just found two other threads that shed light on the ability to run Good Lock on various devices. If anyone can help me figure this out, much appreciated:
(1) [APP][8.0+][V2.0][BADLOCK][GOODLOCK LAUNCHER FOR ALL Tw OREO DEVICES]UPDATED 24/06/18
It Is Meant For Alternative launcher for GoodLock apps. No need of activity manager.
.... Samsung retired the app after the release of Android 7.0 Nougat. Now the company has decided to revive the Good Lock app, with the launch of a new version in its home country of South Korea supporting Touchwiz Oreo.
INSTALLATION INSTRUCTIONS-----
This App Has Different Installation Directory/App Name/Package Name From The Original Goodlock App
This Was Not Done To Steal/Disguise This App But To Prevent Conflicts If You Choose To use Goodlock with Activity Manager method Its Ur Choice
NOTE-----
This App is just Launcher For GOODLOCK 2018 APPS [So install all the Apps given in the Zip]
CHANGELOGS-----
[V1] - INITIAL
[V2.0] -
**Integrated All the GoodLock 2018 Apps To Badlock**
**Updated Task Changer To v1.3.01.52**
**Updated LockStar To v1.0.00.22**
**Added New Clock Face (AddON For Always on Display/Lock Screen clock design)**
**Included Latest Version Of Always On Display For ClockFace To Work**
**Added Supported For ClockFace **
**Added Support For M Egg**
**Added Support For Media Volume**
**Some Optimization and Fixes**
FEATURES-----
This App is Launcher For GOODLOCK 2018 APPS [So install all the Apps given in the Zip]
Q- What Badlock Does ?
A- Its An Alternative Launcher for GoodLock apps. No need of activity manager.
You can launch these four hidden apps under one shell just like GoodLock.
Click to expand...
Click to collapse
and then this article (June 16, 2018 )
How to get the latest Samsung Good Lock on any Samsung Galaxy phone running Oreo
Today Samsung released the updated version of Good Lock that works on any Samsung Galaxy device running Android Oreo like the Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy Note 8, and Samsung Galaxy S9. It was showing up in the Galaxy App store in South Korea but not in other regions. Fortunately, it was extracted from existing devices and is now available for all. Unlike the older version of Samsung Good Lock for Android Marshmallow, getting it up and running requires more than just installing a single APK file. We’ll show you what’s new and how to set it up.
Click to expand...
Click to collapse
Enjoy the updated version of Samsung Good Lock! It’s a great app for customizing your Samsung Galaxy phone without root. Let us know below if you enjoy the app on your Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy Note 8, Samsung Galaxy S9, or other Galaxy smartphone on Android 8.0 Oreo.
Click to expand...
Click to collapse
This second article seemes to confirmn that one needs to have a Samsung Galaxy S7 thru Samsung S9 to run Good Lock. But the first article above suggests to me that whoever created "Bad Lock", it is meant to run on other Android devices. Can anyone explain to me if that means I could root my Note 4, let's say then flash Resurrection Remix 7.0.2, then install one of the "Bad Lock" apk's, and essentially get something very close to the Samsung Good Lock Notification UI ? That's my main reason for wanting it— that and scrolling screenshots which seemed to be a feature of Good Lock?
Thanks again.

Hi,
Needed help to flash the ROM Pie 9 on my note 4. Dowloaded the latest version 'RR-P-v7.0.2-20190714-trlte-Official.zip' and put on my external sd card.
This is my first time changing my OS. Rooted the device, was able to get all the steps to reboot in TWRP, but it failed to flash the ROM.
Error code:
E3004: This package is for device: trlte,trltedt,trltecan,trltespr,trtletmo,trtleusc,trtlevzw,trtlexx; this device is .
E:unknown command "log"
E:Error executing updater binary in zip '/external_sd/RR-P-v7.0.2-20190714-trlte-Official.zip'
Anyone can help to get beyond this point? Much appreciated.

Candroid2019 said:
Hi,
Needed help to flash the ROM Pie 9 on my note 4. Dowloaded the latest version 'RR-P-v7.0.2-20190714-trlte-Official.zip' and put on my external sd card.
This is my first time changing my OS. Rooted the device, was able to get all the steps to reboot in TWRP, but it failed to flash the ROM.
Error code:
E3004: This package is for device: trlte,trltedt,trltecan,trltespr,trtletmo,trtleusc,trtlevzw,trtlexx; this device is .
E:unknown command "log"
E:Error executing updater binary in zip '/external_sd/RR-P-v7.0.2-20190714-trlte-Official.zip'
Anyone can help to get beyond this point? Much appreciated.
Click to expand...
Click to collapse
Couple thoughts:
Make sure you have the right TWRP for your device—not just for the phone model but the carrier-specific version.
Check the ROM forum for the recommended TWRP version, and make sure you have that version. Some ROMs just recommend the latest TWRP while others specify a version.
The error message sounds similar to when I've simply had a bad download. Did the download pause/restart or go through spans of little/no activity or endure bad signal? If any of those, you might just want to re-download it.

What is this crDroid mystery build?

TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
{
"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"
}
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?

install telegram and contact dev

Totesnochill said:
TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
View attachment 5552979
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?
Click to expand...
Click to collapse
yeah I know AaronPhilips101, it's on the gprime group on telegram. i don't know if he built something else but yeah it's weird that he didn't create any thread for that
I remember one day he asked me to use my source trees, probably to build this rom. so it should be safe I think.
Well on how to build a rom there is a good starting guide here https://itexpert120.github.io/blog/building-android/

Gabboxl said:
yeah I know AaronPhilips101, it's on the gprime group on telegram. i don't know if he built something else but yeah it's weird that he didn't create any thread for that
I remember one day he asked me to use my source trees, probably to build this rom. so it should be safe I think.
Well on how to build a rom there is a good starting guide here https://itexpert120.github.io/blog/building-android/
Click to expand...
Click to collapse
The Android build how-to article is especially interesting. Thanks a lot for the tips! Just one more question pls - what is that gprime telegram group you've mentioned? Is it public or invite-only?

Totesnochill said:
The Android build how-to article is especially interesting. Thanks a lot for the tips! Just one more question pls - what is that gprime telegram group you've mentioned? Is it public or invite-only?
Click to expand...
Click to collapse
No problem, if you have any questions just ask : )
You can join the group at @grandprimedev. it's a little dead as of now, I think the gprime community had its time already haha ; )

Gabboxl said:
You can join the group at @grandprimedev.
Click to expand...
Click to collapse
Thanks again! I'll check it out.
Gabboxl:
it's a little dead as of now, I think the gprime community had its time already haha ; )
Click to expand...
Click to collapse
Hahah, makes sense. Still, worth checking out. Gprimes were resilient little phones. Mine still stubbornly works no matter how much abuse (and water damage) it has been subjected to over the years. Guess just like the phone, the community around it still refuses to fully die out XD.

Totesnochill said:
TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
View attachment 5552979
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?
Click to expand...
Click to collapse
Hello there, Sorry for the late reply
1. Yes the rom is completely safe to use and i built it using Gabriel's trees which you can find here https://github.com/Gabboxl/local_manifests
2. I mainly built this for my personal use so that's why I didn't bother creating an XDA thread for it .

[OFFICIAL] LineageOS 20 for the Nokia 6.1 (2018)/6.1 Plus

{
"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"
}
Nokia 6.1 (2018)/6.1 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Nokia 6.1 (2018)/6.1 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Nokia 6.1 (2018)​
PL2 - Official builds​
PL2 - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
Nokia 6.1 Plus​
DRG - Official builds​
DRG - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.​
Find any? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_nokia_sdm660

Is this rom based on Android 13?

ardwivedi16 said:
Is this rom based on Android 13?
Click to expand...
Click to collapse
yes

very excited waiting

worked my phone, yesterday i tried clean flash but not boot, and today i tried update with sideload and worked

I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.

Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.

kazekiri said:
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
Click to expand...
Click to collapse
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload

backspace123// said:
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
Click to expand...
Click to collapse
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).

kazekiri said:
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
Click to expand...
Click to collapse
on my device worked, i tried update using lineageos19.1 official

schwedenespresso said:
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Click to expand...
Click to collapse
Hello, regarding the camera, it is quite likely that it is the kernel as such, in fact, in previous versions, LOS 18.1, 17.1, the flash worked from the camera application, but now it does not work, at the time it was published Official LineageOS for this device, the flash has never worked correctly as such (other applications were not able to take the picture with the flash on the camera due to failure in its execution) as if it did with the manufacturer's version, it is possible that the manufacturer has kept some hidden details at the code level or that the driver has not been fully released on the devices so that the developers themselves have difficulties to achieve a 100% functional version (without errors so to speak), the only solution to this problem is install a custom kernel, it seems some users with knowledge in programming found a way to solve the problem with the flash in the camera + the zoom failure as such, I have not found out if the developer would have adapted the kernel for the versions of android 13 for this specific device than if it is available for versions prior to the unofficial LOS 20 available.
Best regards

Hello everyone, for all those who have problems with their recovery (nothing is displayed, but it feels like it works internally), I will leave you a post that I made months ago, the recovery options should be the same for the latest versions, hopefully It is useful for you, remember that the installation process of LineageOS can last more than 4 minutes.
LineageOS recovery instructions for use build 2022-08-30 -When starting the recovery, 4 options will be presented, which are these.
Reboot system now.
Apply update
2.1)For this step I recommend selecting the first option with the power button of the device, which is by ADB
3)Factory Reset
3.1)Format data/factory reset
4. Advance
4.1) advanced options, with this image it will serve to guide you in how many clicks you have to press to access the option with the power button of the device to access one of these options.
Best regards

backspace123// said:
on my device worked, i tried update using lineageos19.1 official
View attachment 5763487
Click to expand...
Click to collapse
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.

kazekiri said:
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
Click to expand...
Click to collapse
are you on android 9 or 10 firmware?
And no, no kernel changes coming.

npjohnson said:
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
Click to expand...
Click to collapse
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.

kazekiri said:
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
Click to expand...
Click to collapse
Figured it out - next build should work. give it like, 4 hours.

npjohnson said:
Figured it out - next build should work. give it like, 4 hours.
Click to expand...
Click to collapse
Yep. Whatever you did worked! Booted on my DRG. Haven't tested everything yet, but so far seems great.
Thanks! You are one dedicated dev!

So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)

I have the same camera issue, any solution for DRG?

kazekiri said:
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
Click to expand...
Click to collapse
Weird, works on PL2. got logs?