[ROM] [6.0.1] Resurrection Remix M v.5.7.4 FINAL [ODIN]

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
I'm using RR M 5.6.6 (0403) now.
Here are the issues I face:
(Higher priority)
- No root, even can't flash SuperSU with TWRP 3.0.1.
- No HDR in all cameras.
- Double-tap-to-wake doesn't work.
- Bad quality of voice recording.
(Haven't tested the fixed mixer_path.xml coz I don't have root permission.)
(Lower priority)
- A bit warmer than CM12.1 nightly, but just a bit.
- Opening camera takes more time than CM12.1.

Other things I don't mention, they are better than CM12.1 nightly, thank you for giving us such an awesome MM rom! :victory:

------------
@xkeita Your xml file is cool! The noisy bug gets fixed.
I flash it as a zip file with TWRP.
Hope @Chippa_a merge it with next release!
(Anyone needing it could download the zip file below.)

What I mention about root, I've tested with both superuser (built-in) and SuperSU. Both don't work. And BTW, my TWRP shows error:2 (see the image below) after I upgrading to RRM, don't know why…
Screenshot_2016-04-05-14-26-42.png

------------

Well, root issue is solved, it caused by flashing SuperSU manually.
Don't flash SuperSU then no trouble.
Tap-to-wake can be enabled in Kernel Adiutor.
Hope it can be enabled by default.
 

Attachments

Last edited:

xkeita

Senior Member
Mar 18, 2012
608
1,633
0
Santiago
@xkeita Your xml file is cool! The noisy bug gets fixed.
I flash it as a zip file with TWRP.

And BTW, my TWRP shows error:2 (see the image below) after I upgrading to RRM, don't know why…
Glad to see it's working fine bro! I'm currently porting the whole Audio mixer and adding patches that are on builds for other phones to see what comes out.

And I think the the error you mention is related to recovery build. Because when I boot up the recovery installed to my FOTA-Kernel (TWRP) partition it doesn't have any problems.
 
  • Like
Reactions: Dragonkind

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
Glad to see it's working fine bro! I'm currently porting the whole Audio mixer and adding patches that are on builds for other phones to see what comes out.

And I think the the error you mention is related to recovery build. Because when I boot up the recovery installed to my FOTA-Kernel (TWRP) partition it doesn't have any problems.
Sorry, I forget something…
I used your mixer on CM12.1 nightly which performed awesomely.
But it seems to be less effects on Marshmallow.

About TWRP, I downgraded to v3.0.0-0, but it still got error2.

------------
@Chippa_a I found a new issue.
The adaptive brightness increases too fast.
And the lowest brightness isn't 1% but about 20% now.
 

Attachments

Last edited:

xkeita

Senior Member
Mar 18, 2012
608
1,633
0
Santiago
Sorry, I forget something…
I used your mixer on CM12.1 nightly which performed awesomely.
But it seems to be less effects on Marshmallow.

About TWRP, I downgraded to v3.0.0-0, but it still got error2.
On Marshmallow it still needs work, I only fixed a "little" on the sound recorder. It still needs a fine-tune as is a WIP.
 
  • Like
Reactions: Dragonkind

Kran007

Senior Member
Aug 24, 2015
120
55
0
Bacoor City
Done flashing 5.6.6 build 0403 and it was good so far. Only the image quality of taken is not good compare on the build 0322. Also tried the XtremeMusic soundmod and it was awesome. No Root status problem, heating is the same as old build but not quite warmer, flash yesterday
 

Attachments

juniorhxcx

Senior Member
Mar 14, 2012
643
117
0
São Paulo
Done flashing 5.6.6 build 0403 and it was good so far. Only the image quality of taken is not good compare on the build 0322. Also tried the XtremeMusic soundmod and it was awesome. No Root status problem, heating is the same as old build but not quite warmer, flash yesterday
How to install it? (XtremeMusic soundmod)
 

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
And I think the the error you mention is related to recovery build. Because when I boot up the recovery installed to my FOTA-Kernel (TWRP) partition it doesn't have any problems.
I believe it is a rom issue, coz I update my TWRP to 3.0.2 this morning, the issue is still there. There are two recoveries, one is TWRP 3.0.1 (rom built-in, to replace Cyanogen Recovery), the other is what we flash into FOTA. You can check the issue by pressing navbar button "≡" in TWRP 3.0.x.
 

xkeita

Senior Member
Mar 18, 2012
608
1,633
0
Santiago
I believe it is a rom issue, coz I update my TWRP to 3.0.2 this morning, the issue is still there. There are two recoveries, one is TWRP 3.0.1 (rom built-in, to replace Cyanogen Recovery), the other is what we flash into FOTA. You can check the issue by pressing navbar button "≡" in TWRP 3.0.x.
Not rom related but kernel build related instead.
Kernels do include some sbin files which are loaded on boot and then unloaded to follow up with system. Thus, that's why it appears on TWRP logs.

If you flash another kernel the error will disappear but since there's no CM13 custom kernel it's just a waste of time as anyways the error won't make any harm to the system itself.
 
  • Like
Reactions: Dragonkind

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
Not rom related but kernel build related instead.
Kernels do include some sbin files which are loaded on boot and then unloaded to follow up with system. Thus, that's why it appears on TWRP logs.

If you flash another kernel the error will disappear but since there's no CM13 custom kernel it's just a waste of time as anyways the error won't make any harm to the system itself.
Got it, thank u for answering!

Btw, after these 4 days, I found RRM was still overheating and laggy. Maybe there is a ram leakage, coz I got lags after a long time using, and it can be improved by rebooting… Let's wait for the next build. www
 

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
@Chippa_a
2 issues is confirmed on 0408 release:

- Lockscreen
1. Currently I need to unlock my lockscreen before accepting/denying incalls and pausing/stopping alarms.
2. Currently I need to swipe up after I opening the bottom shortcuts (which can't be opened without unlocking). In CM12.1 nightly, I only need to draw my pattern after starting bottom shortcuts, don't need to swipe up again.
3. Location QS tile doesn't hide before unlocking lockscreen. It would hide on CM12.1, coz it was a private tile.

- SU (root)
There's no root management app inside this build, I need to download superuser from Play Store by myself. The root option in development options doesn't work at all.
 
Last edited:
  • Like
Reactions: Kran007

xkeita

Senior Member
Mar 18, 2012
608
1,633
0
Santiago
@Chippa_a
2 issues is confirmed on 0408 release:

- Lockscreen
1. Currently I need to unlock my lockscreen before accepting/denying incalls and pausing/stopping alarms.
2. Currently I need to swipe up after I opening the bottom shortcuts (which can't be opened without unlocking). In CM12.1 nightly, I only need to draw my pattern after starting bottom shortcuts, don't need to swipe up again.
3. Location QS tile doesn't hide before unlocking lockscreen. It would hide on CM12.1, coz it was a private tile.

- SU (root)
There's no root management app inside this build, I need to download superuser from Play Store by myself. The root option in development options doesn't work at all.
Su root is working, just did a clean install and everything is fine. also bottom shortcuts. so is alarm and calls.
Haven't tested the third error you mention.

Anyways before updating wipe data, cache, dalvik cache and system. (clean install)
 

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
Su root is working, just did a clean install and everything is fine. also bottom shortcuts. so is alarm and calls.
Haven't tested the third error you mention.

Anyways before updating wipe data, cache, dalvik cache and system. (clean install)
Well, I need to keep my data…
I wiped system, cache, dalvik and data.
My last phone was SP, the dev told us it didn't need full wipe to update to CM13 from CM12.1.
I did a full wipe, but restored data after flashing RRM.

Maybe I can only clean data of lockscreen?
In CM12.1, it was named as KeyGuard.
What's its name on RRM?
 

navin4vin

New member
Aug 11, 2012
4
3
0
Hi,
A big thanks for bringing MM to ZL. It works great though I face few problems. Not sure if it is specific to my phone.

1. Volume seems to be lower than usual.
2. The phone seems to suffer from lack of memory at times. When the free ram is less than 1000 MB the phone is very slow.
Apart from this I am enjoying the rom.

Regards,
Pradeep
 
Last edited:

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
Hi,
A big thanks for bringing MM to ZL. It works great though I face few problems. Not sure if it is specific to my phone.

1. Volume seems to be lower than usual.
2. The phone seems to suffer from lack of memory at times. When the free ram is less than 1000 MB the phone is very slow.
Apart from this I am enjoying the rom.

Regards,
Pradeep
About volume I have no idea…
It's just a bit lower than CM12.1, not so obvious.
But for noisy voice recordings, u can use the zip file here to solve it:
http://forum.xda-developers.com/showpost.php?p=66200825&postcount=41
This fixed file has not been merged yet.
And it's compatible for both CM12.1 and CM13 based rom.

I noticed ram issue, I think 0408 is much better than 0403.
But it charges too slowly, and overheats.
If u are using 0403 build, I'm highly recommend to update to 0408!
 
  • Like
Reactions: navin4vin

ryanrudolf

Senior Member
Nov 12, 2012
263
148
0
using as a daily driver for 2days now.

Xposed works
Printing works, able to print to wifi printer using printershare app
NFC works, able to transfer photos via NFC
Screen cast works
i tried creating 256MB swapfile on /cache maybe it will improve some intermittent lag

bugs? or maybe things i cant figure out -
1. i flashed the latest supersu beta / stable via TWRP, it errors out that system is already patched. upon reboot, root access is lost.
2. screen cast works but audio stays on the phone. on previous ROM im using (PA) screen cast and audio goes to TV. for this build of RR, the audio does not go to TV, it stays on the phone.
3. screen turns ON when charging the phone in an OFF state.

awesome build! will keep on providing feedback. thank you!
 
Last edited:
  • Like
Reactions: Dragonkind

Dragonkind

Senior Member
Aug 4, 2012
700
346
93
Chureki
1. i flashed the latest supersu beta / stable via TWRP, it errors out that system is already patched. upon reboot, root access is lost.
Well, I can only answer this issue…
Don't flash SuperSU manually, it's pre-built in the rom.
Look at the TWRP log, it shows that SuperSU is being flashed.
Without flashing SuperSU, you may find it in Settings.

Something I really care about.
I need to unlock screen first before starting apps from lockscreen shortcuts (except camera).
And there is no HDR in our camera module…
Above all, it overheats actually, and battery drains faster than CM12.1.
Hope future releases can improve them! :highfive:
 
  • Like
Reactions: ninguem98