[ROM][FULL-MOTO-MODS][GRIFFIN]Resurrection Remix 5.8.5

Loader009

Senior Member
Jul 6, 2012
711
197
63
After you have installed or downloaded adb.exe somewhere; right click on a free place in the directory where adb.exe is, open the command line interface and type in
Code:
adb.exe logcat -d > moto-mods-crash.log
your log is in that moto-mods-crash.log file, which you can upload.
Though, you might check something; is the build time after or before 15:00 CET in your ROM?
If it is before, then you might have gotten a faulty update. I replaced it as fast as I could, so I actually though no one downloaded it.

A sidenote, RR oreo has been released and I built it: https://griffin.hidingin.space/RRoreo/
If you want to give it a try. I didn't test it intensively though, it boots up and no FCs. No OTA for this one at the moment, just forgot it, will be added in future builds.
 

znappyG

Member
Dec 29, 2010
14
3
0
Berlin
A sidenote, RR oreo has been released and I built it: https://griffin.hidingin.space/RRoreo/
If you want to give it a try. I didn't test it intensively though, it boots up and no FCs. No OTA for this one at the moment, just forgot it, will be added in future builds.
Very interesting indeed! I guess it is recommended to wipe before install?
Since it is probably "just" the default RR I am assuming there is no Mod-support and specific Moto Z gestures are not supported, right?

cheers
 

Loader009

Senior Member
Jul 6, 2012
711
197
63
Very interesting indeed! I guess it is recommended to wipe before install?
Since it is probably "just" the default RR I am assuming there is no Mod-support and specific Moto Z gestures are not supported, right?

cheers
Clean flash is always recommended, but it booted with dirty flash (I forgot to deactivate the screenlock, so I don't know if there were errors).
Mod support is the same as LineageOS because I still use erfans repos. Dunno about specific Moto Z gestures, didn't test anything intensively.
Just booted, worked, so I uploaded it for interested parties.
 

Conkerts

Senior Member
Jul 4, 2006
64
24
0
Magisk is not included in this ROM and root can be disabled in developet settings.

But if your Banking App needs SafetyNet to pass, you must install Magisk and enable Magisk Hide. Then you can check if SafetyNet is passed.
Awesome, thanks for continuing the builds.

So, just to make sure: If I want magisk,
I have to go to https://forum.xda-developers.com/apps/magisk
and e.g. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
and just flash the zip after flashing the rom zip ?
 

Loader009

Senior Member
Jul 6, 2012
711
197
63
Are all Moto Mods supported?
Are there any known bugs?
What about battery life?
Same as LineageOS
Dunno about bugs, please report if you notice any.
Didn't test the ROM yet, because it had no microG compatibility. I am using RR oreo from now on.
But I still think the battery life is good, as no one complained about in in the Telegram group.
 

The Marionette

Senior Member
Jun 27, 2011
5,146
2,678
113
Zagreb
Same as LineageOS
Dunno about bugs, please report if you notice any.
Didn't test the ROM yet, because it had no microG compatibility. I am using RR oreo from now on.
But I still think the battery life is good, as no one complained about in in the Telegram group.
On the 14.2. build the battery life is horrible.
I don't know why, though, I never experienced this kind of drain on other oreo-based roms.
 

Loader009

Senior Member
Jul 6, 2012
711
197
63
What is the microG?
Did you try google or xda-search?

---------- Post added at 18:41 ---------- Previous post was at 18:39 ----------

On the 14.2. build the battery life is horrible.
I don't know why, though, I never experienced this kind of drain on other oreo-based roms.
Well, without a log, I cannot say what the problem was.
As I am using RR oreo myself now, I will see if there is some kind of drain...
 

alexander255

Member
Feb 18, 2012
7
2
0
Thanks! I've been setting this up and tweaking this for the last few hours and it works awesomely! Very happy with this! (Also my first Oreo-based ROM – looks like Oreo may be the first post-4.x Android version I'll actually like :))

MicroG setup was arduous as usual, but all features (including custom geolocation / UnifiedNLP & SignatureSpoofing) work according to the self-checker UI – I didn't test it through.

The Substratum theme engine worked great in Legacy mode with OMS, but it tells me I shall recommend you to add Substratum patches to make it rootless and faster (it's hard to believe that it could be faster through).

What is the microG?
See https://microg.org/ (The website is somewhat outdated, but you get the point.)

Dunno about bugs, please report if you notice any.
Didn't test the ROM yet, because it had no microG compatibility. I am using RR oreo from now on.
But I still think the battery life is good, as no one complained about in in the Telegram group.
Can't comment on battery yet, but I noticed that the controls in AudioFX doen't seem to do anything (at least when streaming over Bluetooth) and JamesDSP mod crashes (probably related to the former issue, but may have other cause). Log of that crash, just in case:

02-22 23:31:37.943 31837 31837 I JamesDSPManager: Bluetooth mode
02-22 23:31:37.954 510 1185 E EffectFactoryHAL: Error querying effect descriptor for f27317f4-c984-4de6-9a90-545759495bf2: No such file or directory
02-22 23:31:37.954 2016 4618 W AudioFlinger: createEffect() error -2 from EffectGetDescriptor
02-22 23:31:37.955 31837 31837 E AudioEffect: set(): AudioFlinger could not create effect f98765f4-c321-5de6-9a45-123459495ab2 / f27317f4-c984-4de6-9a90-545759495bf2, status: -2
02-22 23:31:37.955 31837 31837 E AudioEffects-JNI: AudioEffect initCheck failed -3
02-22 23:31:37.955 31837 31837 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
02-22 23:31:37.955 31837 31837 D AndroidRuntime: Shutting down VM
02-22 23:31:37.956 31837 31837 E AndroidRuntime: FATAL EXCEPTION: main
02-22 23:31:37.956 31837 31837 E AndroidRuntime: Process: james.dsp, PID: 31837
02-22 23:31:37.956 31837 31837 E AndroidRuntime: java.lang.RuntimeException: Unable to create service james.dsp.service.HeadsetService: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3349)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.app.ActivityThread.-wrap4(Unknown Source:0)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1677)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at james.dsp.service.HeadsetService$JDSPModule.<init>(HeadsetService.java:73)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at james.dsp.service.HeadsetService.onCreate(HeadsetService.java:459)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3339)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: ... 8 more
02-22 23:31:37.956 31837 31837 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance0(Native Method)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance(Constructor.java:334)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at james.dsp.service.HeadsetService$JDSPModule.<init>(HeadsetService.java:68)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: ... 10 more
02-22 23:31:37.956 31837 31837 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: f98765f4-c321-5de6-9a45-123459495ab2 Error: -3
02-22 23:31:37.956 31837 31837 E AndroidRuntime: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
02-22 23:31:37.956 31837 31837 E AndroidRuntime: ... 13 more
02-22 23:31:37.960 2245 3830 V RescueParty: Disabled because of active USB connection
02-22 23:31:37.960 2245 3830 W ActivityManager: Force finishing activity james.dsp/.activity.DSPManager
02-22 23:31:37.964 31837 31837 I Process : Sending signal. PID: 31837 SIG: 9
02-22 23:31:37.980 2245 2603 W InputDispatcher: channel 'bbf243e james.dsp/james.dsp.activity.DSPManager (server)' ~ Consumer closed input channel or an error occurred. events=0x9
02-22 23:31:37.980 2245 2603 E InputDispatcher: channel 'bbf243e james.dsp/james.dsp.activity.DSPManager (server)' ~ Channel is unrecoverably broken and will be disposed!
02-22 23:31:37.980 2245 3830 I ActivityManager: Process james.dsp (pid 31837) has died: pers PERU
02-22 23:31:37.980 2245 3830 W ActivityManager: Scheduling restart of crashed service james.dsp/.service.HeadsetService in 0ms
I also miss the „Doppelhacken für Taschenlampe“ (whatever that's in Englisch) gesture and the “fingerprint as home button” feature. :p

Good job on this! :good:
 
  • Like
Reactions: s1ck-IT

Loader009

Senior Member
Jul 6, 2012
711
197
63
The Substratum theme engine worked great in Legacy mode with OMS, but it tells me I shall recommend you to add Substratum patches to make it rootless and faster (it's hard to believe that it could be faster through).


Can't comment on battery yet, but I noticed that the controls in AudioFX doen't seem to do anything (at least when streaming over Bluetooth) and JamesDSP mod crashes (probably related to the former issue, but may have other cause). Log of that crash, just in case:


I also miss the „Doppelhacken für Taschenlampe“ (whatever that's in Englisch) gesture and the “fingerprint as home button” feature. :p

Good job on this! :good:
You can find Chop-chop and fingerprint as Home-button in the moto gestures.
Settings -> System -> Moto Gestures -> look at my screenshot

The other two are ROM dependent, not device dependent (I think).
I will take a look into it but mainly this means that we need to wait until the RR team fixed it.
 

Attachments

  • Like
Reactions: s1ck-IT

znappyG

Member
Dec 29, 2010
14
3
0
Berlin
Coming from the last N RR I am having trouble dirty flashing. In TWRP I get error 7 with something that reads like "this device is ."
I looked up my build.prop and everything seems as it should (device=griffin, model=xt1650). Is there another place where my device name should appear? Just reflashed the 20180205 build without any issues. Are the checks different in the O build?

Thx
 

Loader009

Senior Member
Jul 6, 2012
711
197
63
Coming from the last N RR I am having trouble dirty flashing. In TWRP I get error 7 with something that reads like "this device is ."
I looked up my build.prop and everything seems as it should (device=griffin, model=xt1650). Is there another place where my device name should appear? Just reflashed the 20180205 build without any issues. Are the checks different in the O build?

Thx
Same as with lineageOS, update TWRP.
 
  • Like
Reactions: znappyG

TobiPeter

Senior Member
Apr 24, 2017
358
108
53
Brandenburg
I own a Moto Turbo Power Pack and a Moto Gamepad.

Are they fully supported? (I know, same as LOS, but I didn't use LOS for half a year now)

And if not I could flash this ROM and send logs of crashes to make the Oreo version fully compatible to the Moto MODS (at least I could help with these two).

Or should I ask in the LOS thread instead?
 

Benni:)

Senior Member
Jan 18, 2012
141
57
48
Karlsruhe
I own a Moto Turbo Power Pack and a Moto Gamepad.

Are they fully supported? (I know, same as LOS, but I didn't use LOS for half a year now)

And if not I could flash this ROM and send logs of crashes to make the Oreo version fully compatible to the Moto MODS (at least I could help with these two).

Or should I ask in the LOS thread instead?
You should ask in the LOS thread, as RR is based on it
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone