[ROM][All Quark][9.x]Resurrection Remix

fgl27

Recognized Developer
Feb 27, 2014
3,630
9,427
263
Brazil...South of the south
I am running 0306 and the newest Kernel (v9.28) since yesterday afternoon. I had it plugged in and charging overnight while I slept. This morning the phone now shows some deep sleep but is still showing hours of locks. I have attached more screenshots I am not sure if this is just normal activity or something else. Please let me know if I should supply logs.

Thanks again for all your help in this community and with this device!

Screenshots Below:
ALBUM LINK:
https://forum.xda-developers.com/album.php?albumid=15332
Image #1

https://forum.xda-developers.com/picture.php?albumid=15332&pictureid=58495

Image #2

https://forum.xda-developers.com/picture.php?albumid=15332&pictureid=58496

Image #3

https://forum.xda-developers.com/picture.php?albumid=15332&pictureid=58497
"plugged in and charging" equals always awake, device can't sleep on charger that is the smb135x_wake wakelock.
If you wanna to see the real number you need to do a reboot after it reach 100% then after it finishes booting up remove the charger, can takes around 15min for the device start sleep after first boot, then after that takes a few seconds (30 to 60s) unless you or something is using the device.
:good:
 

FlavioV

Senior Member
Jan 25, 2013
359
264
83
How I can back to mode swipe up to close apps? Now suddenly started this style like old Android 8.1-7...
Thx!
The new recents (Quickstep) is tied to Trebuchet launcher, if you use a different launcher as default (or uninstall/disable Trebuchet) it may revert to the old recents style.

You can use QuickSwitch to check if your launcher supports Quickstep, and if it does you can set it as default provider. Picking SystemUI as default provider will enforce the old recents on any launcher.

I use Pixel Launcher as default, the new overview mode is pretty great (see screenshot #2).
 

Attachments

Last edited:
  • Like
Reactions: EVNS

anirogz

Member
Aug 17, 2016
41
12
0
I have nothing against RR and I am really grateful as I was stuck on Marshmellow since many years :p my phone name is different and I didn't know that I can use these roms too. I really hope if you could come up with Lineage or Pixel Experience. I know it's really hard to keep up the quality and make rom bug free + so much processing time but really thank you man. Just want to confirm - I can use this rom directly after marshmallow right? no need to make any change to the kernel?
 

fgl27

Recognized Developer
Feb 27, 2014
3,630
9,427
263
Brazil...South of the south
ROM update! RR-P-v7.0.1-20190308-quark-Official.zip
Changelogs:
Device specific (Click Here)
Resurrection Remix OS - Pie source and Quark Changelog (Click Here)


Download Links :
ROM:
Main:
get.resurrectionremix.com - ROM Main Link Click Here (This is the server used by the Updates app in Setting>System>Updater)
Secondary:
Gdriver - ROM Mirror link Click Here (This contains current and previously version)
AFH - ROM Mirror link Click Here (This contains all old versions, but may not show last version as soon as update post comes up)


Gapps:
Open GApps:
Open Gapps Click Here
Choose Platform: ARM, Android: 9.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.

Open GApps old releases Click Here, in case latest version is NOK

Gapps recommendations from LineageOS Google apps options (click here)


TWRP For Quark:
TWRP Use laste Mod version that I release Click Here


Installation instructions:
  • Download the latest build and GApps.
  • Reboot to recovery (recommended make a backup)
  • Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
  • Wipe System*
  • Flash the latest build and GApps **
  • Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.
Always start a post with a bug report with @fgl27 and always attached a log .zip
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP
** If the device Random reboot also share the log made as sone as the device finished the random reboot

Bugs without logs, without @fgl27 will probably not be read, there is too much posts on the thread sometimes and I don't have time to read it all, anyone can post as much as is need of course as long is a things related to this thread
 

fgl27

Recognized Developer
Feb 27, 2014
3,630
9,427
263
Brazil...South of the south
I have nothing against RR and I am really grateful as I was stuck on Marshmellow since many years :p my phone name is different and I didn't know that I can use these roms too. I really hope if you could come up with Lineage or Pixel Experience. I know it's really hard to keep up the quality and make rom bug free + so much processing time but really thank you man. Just want to confirm - I can use this rom directly after marshmallow right? no need to make any change to the kernel?
build the ROM you wanna as I do, anyone can do I already released all my work whit instruction's on git and make it possible for anyone to build on a LOS base source.

the ROM has it's own kernel, flash via TWRP fallow the #1 post recommendations as "Coming from different ROM? Then Always wipe Data (without media aka without internal memory)"
 
Last edited:

EVNS

Senior Member
Apr 9, 2015
121
62
0
The new recents (Quickstep) is tied to Trebuchet launcher, if you use a different launcher as default (or uninstall/disable Trebuchet) it may revert to the old recents style.

You can use QuickSwitch to check if your launcher supports Quickstep, and if it does you can set it as default provider. Picking SystemUI as default provider will enforce the old recents on any launcher.

I use Pixel Launcher as default, the new overview mode is pretty great (see screenshot #2).
@FlavioV Thx u very much! Now I understand, my trebuchet was deactivated so i miss the recent style hehe! Liked ur style using the Switch!
 
Last edited:
  • Like
Reactions: FlavioV

Marky__Mark

Senior Member
Jan 26, 2015
644
183
63
Just a little trick i learned after googling about my delayed text message notifications by ten minutes or when i wake the phone. Apparently this is a common problem with pie. So if you're having issues like i was, disable doze. You can do this by enabling the terminal emulator in developer options or download a similar app. Open the app and type "su" without quotes and press enter. Then type "dumpsys deviceidle disable" again without the quotes. This appears to have fixed it for me and with no increase in battery drain.
 
Last edited:
Jul 27, 2018
9
6
0
Just a little trick i learned after googling about my delayed text message notifications by ten minutes or when i wake the phone. Apparently this is a common problem with pie. So if you're having issues like i was, disable doze. You can do this by enabling the terminal emulator in developer options or download a similar app. Open the app and type "su" without quotes and press enter. Then type "dumpsys deviceidle disable" again without the quotes. This appears to have fixed it for me and with no increase in battery drain.
I have noticed that my wife receives group texts quicker on her iphone than me so I am definitely going to give this a try. I tested it with the 'Deep Sleep' numbers in Aduitor and found that this change did NOT affect my deep sleep numbers. Thanks Mark!
 

fgl27

Recognized Developer
Feb 27, 2014
3,630
9,427
263
Brazil...South of the south
I have noticed that my wife receives group texts quicker on her iphone than me so I am definitely going to give this a try. I tested it with the 'Deep Sleep' numbers in Aduitor and found that this change did NOT affect my deep sleep numbers. Thanks Mark!
that cmd resets after a reboot.

I can make a switch in ka, there is more then one mode "deep" and "light", deep is default, I can also make a option so we can enable just the light mode for testing

dumpsys deviceidle options

Code:
dumpsys deviceidle -h
Device idle controller (deviceidle) commands:
  help
    Print this help text.
  step [light|deep]
    Immediately step to next state, without waiting for alarm.
  force-idle [light|deep]
    Force directly into idle mode, regardless of other device state.
  force-inactive
    Force to be inactive, ready to freely step idle states.
  unforce
    Resume normal functioning after force-idle or force-inactive.
  get [light|deep|force|screen|charging|network]
    Retrieve the current given state.
  disable [light|deep|all]
    Completely disable device idle mode.
  enable [light|deep|all]
    Re-enable device idle mode after it had previously been disabled.
  enabled [light|deep|all]
    Print 1 if device idle mode is currently enabled, else 0.
  whitelist
    Print currently whitelisted apps.
  whitelist [package ...]
    Add (prefix with +) or remove (prefix with -) packages.
  sys-whitelist [package ...|reset]
    Prefix the package with '-' to remove it from the system whitelist or '+' to put it back in the system whitelist.
    Note that only packages that were earlier removed from the system whitelist can be added back.
    reset will reset the whitelist to the original state
    Prints the system whitelist if no arguments are specified
  except-idle-whitelist [package ...|reset]
    Prefix the package with '+' to add it to whitelist or '=' to check if it is already whitelisted
    [reset] will reset the whitelist to it's original state
    Note that unlike <whitelist> cmd, changes made using this won't be persisted across boots
  tempwhitelist
    Print packages that are temporarily whitelisted.
  tempwhitelist [-u USER] [-d DURATION] [-r] [package]
    Temporarily place package in whitelist for DURATION milliseconds.
    If no DURATION is specified, 10 seconds is used
    If [-r] option is used, then the package is removed from temp whitelist and any [-d] is ignored
  motion
    Simulate a motion event to bring the device out of deep doze
:/ # 


 dumpsys deviceidle                                                        
  Settings:
    light_after_inactive_to=+3m0s0ms
    light_pre_idle_to=+3m0s0ms
    light_idle_to=+5m0s0ms
    light_idle_factor=2.0
    light_max_idle_to=+15m0s0ms
    light_idle_maintenance_min_budget=+1m0s0ms
    light_idle_maintenance_max_budget=+5m0s0ms
    min_light_maintenance_time=+5s0ms
    min_deep_maintenance_time=+30s0ms
    inactive_to=+30m0s0ms
    sensing_to=+4m0s0ms
    locating_to=+30s0ms
    location_accuracy=20.0m
    motion_inactive_to=+10m0s0ms
    idle_after_inactive_to=+30m0s0ms
    idle_pending_to=+5m0s0ms
    max_idle_pending_to=+10m0s0ms
    idle_pending_factor=2.0
    idle_to=+1h0m0s0ms
    max_idle_to=+6h0m0s0ms
    idle_factor=2.0
    min_time_to_alarm=+1h0m0s0ms
    max_temp_app_whitelist_duration=+5m0s0ms
    mms_temp_app_whitelist_duration=+1m0s0ms
    sms_temp_app_whitelist_duration=+20s0ms
    notification_whitelist_duration=+30s0ms
    wait_for_unlock=false
  Whitelist (except idle) system apps:
    com.android.providers.downloads
    com.android.vending
    com.google.android.gms
    com.google.android.apps.turbo
    com.android.shell
    com.android.providers.contacts
  Whitelist system apps:
    com.android.providers.downloads
    com.google.android.gms
    com.android.shell
  Whitelist (except idle) all app ids:
    2000
    10003
    10006
    10008
    10019
    10020
  Whitelist all app ids:
    2000
    10008
    10019
  mLightEnabled=true  mDeepEnabled=false
  mForceIdle=false
  mMotionSensor={Sensor name="Significant Motion sensor", vendor="Motorola", version=1, type=17, maxRange=1.0, resolution=1.0, power=3.0, minDelay=-1}
  mScreenOn=false
  mScreenLocked=true
  mNetworkConnected=true
  mCharging=true
  mMotionActive=false
  mNotMoving=false
  mLocating=false mHasGps=false mHasNetwork=false mLocated=false
  mState=ACTIVE mLightState=ACTIVE
  mInactiveTimeout=+30m0s0ms
 

Marky__Mark

Senior Member
Jan 26, 2015
644
183
63
that cmd resets after a reboot.

I can make a switch in ka, there is more then one mode "deep" and "light", deep is default, I can also make a option so we can enable just the light mode for testing

dumpsys deviceidle options

Code:
dumpsys deviceidle -h
Device idle controller (deviceidle) commands:
  help
    Print this help text.
  step [light|deep]
    Immediately step to next state, without waiting for alarm.
  force-idle [light|deep]
    Force directly into idle mode, regardless of other device state.
  force-inactive
    Force to be inactive, ready to freely step idle states.
  unforce
    Resume normal functioning after force-idle or force-inactive.
  get [light|deep|force|screen|charging|network]
    Retrieve the current given state.
  disable [light|deep|all]
    Completely disable device idle mode.
  enable [light|deep|all]
    Re-enable device idle mode after it had previously been disabled.
  enabled [light|deep|all]
    Print 1 if device idle mode is currently enabled, else 0.
  whitelist
    Print currently whitelisted apps.
  whitelist [package ...]
    Add (prefix with +) or remove (prefix with -) packages.
  sys-whitelist [package ...|reset]
    Prefix the package with '-' to remove it from the system whitelist or '+' to put it back in the system whitelist.
    Note that only packages that were earlier removed from the system whitelist can be added back.
    reset will reset the whitelist to the original state
    Prints the system whitelist if no arguments are specified
  except-idle-whitelist [package ...|reset]
    Prefix the package with '+' to add it to whitelist or '=' to check if it is already whitelisted
    [reset] will reset the whitelist to it's original state
    Note that unlike <whitelist> cmd, changes made using this won't be persisted across boots
  tempwhitelist
    Print packages that are temporarily whitelisted.
  tempwhitelist [-u USER] [-d DURATION] [-r] [package]
    Temporarily place package in whitelist for DURATION milliseconds.
    If no DURATION is specified, 10 seconds is used
    If [-r] option is used, then the package is removed from temp whitelist and any [-d] is ignored
  motion
    Simulate a motion event to bring the device out of deep doze
:/ # 


 dumpsys deviceidle                                                        
  Settings:
    light_after_inactive_to=+3m0s0ms
    light_pre_idle_to=+3m0s0ms
    light_idle_to=+5m0s0ms
    light_idle_factor=2.0
    light_max_idle_to=+15m0s0ms
    light_idle_maintenance_min_budget=+1m0s0ms
    light_idle_maintenance_max_budget=+5m0s0ms
    min_light_maintenance_time=+5s0ms
    min_deep_maintenance_time=+30s0ms
    inactive_to=+30m0s0ms
    sensing_to=+4m0s0ms
    locating_to=+30s0ms
    location_accuracy=20.0m
    motion_inactive_to=+10m0s0ms
    idle_after_inactive_to=+30m0s0ms
    idle_pending_to=+5m0s0ms
    max_idle_pending_to=+10m0s0ms
    idle_pending_factor=2.0
    idle_to=+1h0m0s0ms
    max_idle_to=+6h0m0s0ms
    idle_factor=2.0
    min_time_to_alarm=+1h0m0s0ms
    max_temp_app_whitelist_duration=+5m0s0ms
    mms_temp_app_whitelist_duration=+1m0s0ms
    sms_temp_app_whitelist_duration=+20s0ms
    notification_whitelist_duration=+30s0ms
    wait_for_unlock=false
  Whitelist (except idle) system apps:
    com.android.providers.downloads
    com.android.vending
    com.google.android.gms
    com.google.android.apps.turbo
    com.android.shell
    com.android.providers.contacts
  Whitelist system apps:
    com.android.providers.downloads
    com.google.android.gms
    com.android.shell
  Whitelist (except idle) all app ids:
    2000
    10003
    10006
    10008
    10019
    10020
  Whitelist all app ids:
    2000
    10008
    10019
  mLightEnabled=true  mDeepEnabled=false
  mForceIdle=false
  mMotionSensor={Sensor name="Significant Motion sensor", vendor="Motorola", version=1, type=17, maxRange=1.0, resolution=1.0, power=3.0, minDelay=-1}
  mScreenOn=false
  mScreenLocked=true
  mNetworkConnected=true
  mCharging=true
  mMotionActive=false
  mNotMoving=false
  mLocating=false mHasGps=false mHasNetwork=false mLocated=false
  mState=ACTIVE mLightState=ACTIVE
  mInactiveTimeout=+30m0s0ms
That would be awesome.
 
Jul 27, 2018
9
6
0
that cmd resets after a reboot.

I can make a switch in ka, there is more then one mode "deep" and "light", deep is default, I can also make a option so we can enable just the light mode for testing

dumpsys deviceidle options

Code:
dumpsys deviceidle -h
Device idle controller (deviceidle) commands:
  help
    Print this help text.
  step [light|deep]
    Immediately step to next state, without waiting for alarm.
  force-idle [light|deep]
    Force directly into idle mode, regardless of other device state.
  force-inactive
    Force to be inactive, ready to freely step idle states.
  unforce
    Resume normal functioning after force-idle or force-inactive.
  get [light|deep|force|screen|charging|network]
    Retrieve the current given state.
  disable [light|deep|all]
    Completely disable device idle mode.
  enable [light|deep|all]
    Re-enable device idle mode after it had previously been disabled.
  enabled [light|deep|all]
    Print 1 if device idle mode is currently enabled, else 0.
  whitelist
    Print currently whitelisted apps.
  whitelist [package ...]
    Add (prefix with +) or remove (prefix with -) packages.
  sys-whitelist [package ...|reset]
    Prefix the package with '-' to remove it from the system whitelist or '+' to put it back in the system whitelist.
    Note that only packages that were earlier removed from the system whitelist can be added back.
    reset will reset the whitelist to the original state
    Prints the system whitelist if no arguments are specified
  except-idle-whitelist [package ...|reset]
    Prefix the package with '+' to add it to whitelist or '=' to check if it is already whitelisted
    [reset] will reset the whitelist to it's original state
    Note that unlike <whitelist> cmd, changes made using this won't be persisted across boots
  tempwhitelist
    Print packages that are temporarily whitelisted.
  tempwhitelist [-u USER] [-d DURATION] [-r] [package]
    Temporarily place package in whitelist for DURATION milliseconds.
    If no DURATION is specified, 10 seconds is used
    If [-r] option is used, then the package is removed from temp whitelist and any [-d] is ignored
  motion
    Simulate a motion event to bring the device out of deep doze
:/ # 


 dumpsys deviceidle                                                        
  Settings:
    light_after_inactive_to=+3m0s0ms
    light_pre_idle_to=+3m0s0ms
    light_idle_to=+5m0s0ms
    light_idle_factor=2.0
    light_max_idle_to=+15m0s0ms
    light_idle_maintenance_min_budget=+1m0s0ms
    light_idle_maintenance_max_budget=+5m0s0ms
    min_light_maintenance_time=+5s0ms
    min_deep_maintenance_time=+30s0ms
    inactive_to=+30m0s0ms
    sensing_to=+4m0s0ms
    locating_to=+30s0ms
    location_accuracy=20.0m
    motion_inactive_to=+10m0s0ms
    idle_after_inactive_to=+30m0s0ms
    idle_pending_to=+5m0s0ms
    max_idle_pending_to=+10m0s0ms
    idle_pending_factor=2.0
    idle_to=+1h0m0s0ms
    max_idle_to=+6h0m0s0ms
    idle_factor=2.0
    min_time_to_alarm=+1h0m0s0ms
    max_temp_app_whitelist_duration=+5m0s0ms
    mms_temp_app_whitelist_duration=+1m0s0ms
    sms_temp_app_whitelist_duration=+20s0ms
    notification_whitelist_duration=+30s0ms
    wait_for_unlock=false
  Whitelist (except idle) system apps:
    com.android.providers.downloads
    com.android.vending
    com.google.android.gms
    com.google.android.apps.turbo
    com.android.shell
    com.android.providers.contacts
  Whitelist system apps:
    com.android.providers.downloads
    com.google.android.gms
    com.android.shell
  Whitelist (except idle) all app ids:
    2000
    10003
    10006
    10008
    10019
    10020
  Whitelist all app ids:
    2000
    10008
    10019
  mLightEnabled=true  mDeepEnabled=false
  mForceIdle=false
  mMotionSensor={Sensor name="Significant Motion sensor", vendor="Motorola", version=1, type=17, maxRange=1.0, resolution=1.0, power=3.0, minDelay=-1}
  mScreenOn=false
  mScreenLocked=true
  mNetworkConnected=true
  mCharging=true
  mMotionActive=false
  mNotMoving=false
  mLocating=false mHasGps=false mHasNetwork=false mLocated=false
  mState=ACTIVE mLightState=ACTIVE
  mInactiveTimeout=+30m0s0ms
I would like to test this out
 

LifeAsADroid

Senior Member
Sep 17, 2012
998
310
0
Awesomeville, USA
Is there a system app remover built in to the ROM? I tried Titanium Backup like I usually do, but it's not getting the job done (maybe a 9.0 Pie thing?) I'd like to remove things like Browser, Email, Messaging, Trebuchet, etc.