[ROM][Pie][OFFICIAL]Resurrection Remix v7.0.2 [unified 3/3t]

[mvalda01]

The ROM is very stable and has lots of customizations. It boots without problems once updated to pie fw and battery life is quite good. Would love to have more theming possibilities, the white notifications panel is a punch in the eye. Maybe it's possible without using Substratum (I find it's quite a nonsense to use it on pie ROMs , which are more or less all themed)?

 

[nvertigo67]

why do you have to reply in a mean way?? yes i read and i tried this rom and the unofficial version and they both showed the same error, i posted the picture of the other rom by mistake here but its the same error.
anyway i want to tell you that i flashed the official 5.0.8 version from oneplus then when i tried to flash the rom again it didnt work and showed error 7 which says that this rom is for op3 or op3t and it didnt flash. i read that i can skip that error by deleting ''asserts'' files from the rom zip file. i did that then the rom flashed but something was weird because my phone was laggy and both my sim cards kept on disconnecting from the network completely every minute for around 30 seconds. the whole rom and phone was acting weird. now im back to the open beta oos i was on before after restoring the backup i did in twrp before doing all this. could you please help me out to find a way to flash the rom successfully? now im back to the same error you see in the picture.

The answer wasn't mean. He even marked what to read for you. The error message clearly states it's the wrong fw - now I write it down for you: "Modem firmware from OxygenOS 9.0.2 or newer is required[...]" You should start reading instead of complaining about the answer!

 

[mbl007]

The answer wasn't mean. He even marked what to read for you. The error message clearly states it's the wrong fw - now I write it down for you: "Modem firmware from OxygenOS 9.0.2 or newer is required[...]" You should start reading instead of complaining about the answer!

Im sorry guys, i wasn't complaining but i felt unneeded anger in the reply, i knew my question was dumb but i just wanted a quick answer because i messed up the phone and had no time to dig into what happened. Anyway everything is fixed now. Thanks everyone.

---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------

Is there a place where to control the light of the buttom buttons and to get them to light only for 1 second and only when they're touched and not everytime the screen is toucued? And could anyone tell me where the option to keep the screen off completely when i turn it off because it's always displaying some sort of a screen saver with the clock so the screen never gets turned off.
Thanks in advance!

 

[mbl007]

Im sorry guys, i wasn't complaining but i felt unneeded anger in the reply, i knew my question was dumb but i just wanted a quick answer because i messed up the phone and had no time to dig into what happened. Anyway everything is fixed now. Thanks everyone.

---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------

Is there a place where to control the light of the buttom buttons and to get them to light only for 1 second and only when they're touched and not everytime the screen is toucued? And could anyone tell me where the option to keep the screen off completely when i turn it off because it's always displaying some sort of a screen saver with the clock so the screen never gets turned off.
Thanks in advance!

I figured where to decrease the duration of the buttons but i don't know where i can disable the option of them lighting on every time i touch the screen. And how to get my screen to turn off completely i also still dunno..

 

[jesrani]

I'm refering to the passphrase needed to decryptdata (and therefor needed to boot up the device as "secured boot passphrase". With passphrase I refer to pin, password or pattern (which is just a special variation of pin).



Of course it's still possible - it's just a matter of effort. Security is never about possible or impossible. Security is about probability and effort. The longer, more random and the more special characters containing a passphrase is, the more effort is needed to break it. This means it's less pobable.

Or from the other side: the more rescources you can effort, the higher is the probability to break enctyption.

Can you suggest any solution for battery drain?

 

[KaiserSnorezay]

Can you suggest any solution for battery drain?

Number one trick, regardless of phone, ROM or Android version - turn down your screen brightness. It's the single biggest consumer of battery, and your eyes will thank you for it. I've seen people staring at screens that are brighter than a torch. Use the auto brightness feature and the live display/ night light (to save your eyes).
Other than this, there are battery usage apps like BetterBatteryStats or even the built in battery settings that will show you what's consuming power.
You can also try these -
Disable background sync selectively under data usage. For example you might want WhatsApp to sync always, but maybe not for Facebook or other social media apps.
Turn off the 'always allow Wi-Fi/Bluetooth scanning' under Security-> Location-> Scanning
Disable vibration and screen tap sounds. If you ask me, you don't need your phone to vibrate at all except for incoming calls or SMS. Nearly every app has a vibrate on notification feature, you'll have to disable it individually. Turn off keyboard vibration also.

 

[nvertigo67]

I'm refering to the passphrase needed to decryptdata (and therefor needed to boot up the device as "secured boot passphrase". With passphrase I refer to pin, password or pattern (which is just a special variation of pin).



Of course it's still possible - it's just a matter of effort. Security is never about possible or impossible. Security is about probability and effort. The longer, more random and the more special characters containing a passphrase is, the more effort is needed to break it. This means it's less pobable.

Or from the other side: the more rescources you can effort, the higher is the probability to break enctyption.

Can you suggest any solution for battery drain?

Why do you quote my posting? Your question doesn't relate to the quoted posting at all.

To answer your question: track down the reason(s) for the battery drain and eliminate it.

• check if device is entering deepsleep
• check the wakelocks
• check the main bat consuming apps and services, while screen is on

I use betterbatterystats for this.

 

[jesrani]

Why do you quote my posting? Your question doesn't relate to the quoted posting at all.

To answer your question: track down the reason(s) for the battery drain and eliminate it.

• check if device is entering deepsleep
• check the wakelocks
• check the main bat consuming apps and services, while screen is on

I use betterbatterystats for this.

Sorry about quoting the wrong post. I have downloaded betterbatterystats but it is not working properly. Is not collecting the stats. There is some solution given in the thread and I need to see how to do that. Right now getting "No stats have been collected yet" error.

 

[osrox]

Hi, just wanted to ask regarding boot passphrase. I am currently on RR and encrypted with 4 digit PIN which is asked at boot or even for entering recovery. Is this is the "Boot passphrase" you are referring to? Can I make it 6 digits or a passphrase rather than PIN? With this security, is it possible for someone to get my data if the phone is stolen?

I had formatted my phone, before flashing RR Pie.
Now my phone doesn't ask me encryption password on boot or recovery.
How do i enable it again ?

 

[nvertigo67]

I had formatted my phone, before flashing RR Pie.
Now my phone doesn't ask me encryption password on boot or recovery.
How do i enable it again ?

You need to encrypt your phone again. Tjen you can enable secured boot when setting a lockscreen passphrase.

 

[sandeep_kumar]

I had formatted my phone, before flashing RR Pie.
Now my phone doesn't ask me encryption password on boot or recovery.
How do i enable it again ?

Go to setting > security > Encryption
Plug your device while encrypting and then proceed. I have done it before on resurrection remix and it took less than 5 minutes while in the encryption screen it says it may take an hour

 

[jesrani]

To answer your question: track down the reason(s) for the battery drain and eliminate it.

• check if device is entering deepsleep
  
• check the wakelocks
  
• check the main bat consuming apps and services, while screen is on

I use betterbatterystats for this.

I have switched over to Havoc and betterbatterystats seems to work. However i am not sure how to interpret. Can i attach some log or screenshot here?
I have also disabled (ignored) boot up start for many user apps in Privacy Guard. Should I also disable background data usage and background battery for each app? Does all this really work?
My wife has an Honor 8 Pro, unrooted and she gets more than a day of battery time with more than 4 hours SOT, with default settings. She does not have many apps but battery eating ones like WhatsApp and Facebook are there. So why does are a debloated custom ROM not give better battery life with default settings? What is your view on this?

Sent from my ONEPLUS A3003 using Tapatalk

 

[kenny_cfc]

I have switched over to Havoc and betterbatterystats seems to work. However i am not sure how to interpret. Can i attach some log or screenshot here?
I have also disabled (ignored) boot up start for many user apps in Privacy Guard. Should I also disable background data usage and background battery for each app? Does all this really work?
My wife has an Honor 8 Pro, unrooted and she gets more than a day of battery time with more than 4 hours SOT, with default settings. She does not have many apps but battery eating ones like WhatsApp and Facebook are there. So why does are a debloated custom ROM not give better battery life with default settings? What is your view on this?

RR and Havoc are both feature rich roms. For me atleast they are not the roms with the best battery life. I found battery life to be better on SD and LOS16 as per my usage.
Edit: Also it depends on the condition of your battery.

 

[eddiehk6]

Hi all,

Updated to the latest 9th July ROM with modified bootloader, everything pretty much working as usual

One strange thing I've just come across: my NFC will not turn on, even after trying to manually switch it on several times, it never actually turns on.
As a result, things like Google Pay do not currently work for me. All was working fine before the update.

Anybody else experienced this?

Done a quick search before posting, so wanted to ask before diving deeper.

Thanks

 

[Dirk]

Hi all,

Updated to the latest 9th July ROM with modified bootloader, everything pretty much working as usual

One strange thing I've just come across: my NFC will not turn on, even after trying to manually switch it on several times, it never actually turns on.
As a result, things like Google Pay do not currently work for me. All was working fine before the update.

Anybody else experienced this?

Done a quick search before posting, so wanted to ask before diving deeper.

Thanks

Are you using a custom Kernel?

 

[eddiehk6]

Are you using a custom Kernel?

Yep, Franco R45
I have a habit of flashing this and my own custom zip to remove some system apps immediately after ROM flash, never seemed to do any harm.

Will try to reflash the rom to uninstall the kernel, see if that makes any difference. Thanks

Also noticed that my custom zip does not work this time despite appearing to flash in recovery (the unwanted system apps are unaffected)

 

[Dirk]

Will try to reflash the rom to uninstall the kernel, see if that makes any difference. Thanks

It will. Kernels need to be updated to work with Pie Blobs/Firmware otherwise NFC breaks. Stock Kernel is fine.

 

[eddiehk6]

It will. Kernels need to be updated to work with Pie Blobs/Firmware otherwise NFC breaks. Stock Kernel is fine.

Yep that worked thanks. NFC back on as normal. :good:

Still don't know why my other custom zip didn't flash. might have something to do with twrp being updated to 3.3.1. Not a big issue and unlikely ROM related anyway. Had to move and delete some system files manually

 

[Dirk]

Yep that worked thanks. NFC back on as normal. :good:

Still don't know why my other custom zip didn't flash. might have something to do with twrp being updated to 3.3.1. Not a big issue and unlikely ROM related anyway. Had to move and delete some system files manually

Busybox was removed in the newer TWRP builds. If you check the updater-script in your .zip you'll probably find it invokes Busybox to mount /system. Use this instead:

run_program("/sbin/mount", "/system");

and

run_program("/sbin/unmount", "/system");

 

[shadowam]

Tried searching but couldn't find anything recently...

Is anybody having problems with the notification light? Was working fine in the previous versions, but since flashing the latest OOS Beta and newest Resurrection, it's not working for me.