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

[mrenda]

@fgl27 I seem to be having problems making or receiving calls. Neither me nor the person I call or receive the call from can hear one another.
Has anyone else experienced it?

Enviado desde mi Moto MAXX mediante Tapatalk

 

[pankaj72]

@fgl27 I seem to be having problems making or receiving calls. Neither me nor the person I call or receive the call from can hear one another.
Has anyone else experienced it?

Enviado desde mi Moto MAXX mediante Tapatalk

Experienced the same in 24th feb update and I am on 26 th Feb update now no such problem occurring. Clean installed the ROM both times.

 

[FlavioV]

@fgl27 I seem to be having problems making or receiving calls. Neither me nor the person I call or receive the call from can hear one another.
Has anyone else experienced it?

Experienced the same in 24th feb update and I am on 26 th Feb update now no such problem occurring. Clean installed the ROM both times.

I'm also having this issue, some calls are ok but most of them I can't hear anything. At first I thought it could be just bad signal.

My phone is on the latest build.

 

[zahids12345]

@fgl27 , the output from the speaker is very low in media and games as compared to the rr oreo,can you please fix that.
By the way, I'm a big fan of your work.

 

[fgl27]

@fgl27 I seem to be having problems making or receiving calls. Neither me nor the person I call or receive the call from can hear one another.
Has anyone else experienced it?

Enviado desde mi Moto MAXX mediante Tapatalk

Experienced the same in 24th feb update and I am on 26 th Feb update now no such problem occurring. Clean installed the ROM both times.

I'm also having this issue, some calls are ok but most of them I can't hear anything. At first I thought it could be just bad signal.

My phone is on the latest build.

made 12 call all OK.

if any one you have a way to reproduce the problem please share a way that works 100% with logs as I can't replicate the issue here.

@fgl27 , the output from the speaker is very low in media and games as compared to the rr oreo,can you please fix that.
By the way, I'm a big fan of your work.

tested youtube all fine here, maybe the app you use has global low volume or you didn't change the volume the right way there is a separated media volume.

 

[EVNS]

made 12 call all OK.

if any one you have a way to reproduce the problem please share a way that works 100% with logs as I can't replicate the issue here.



tested youtube all fine here, maybe the app you use has global low volume or you didn't change the volume the right way there is a separated media volume.

@fgl27 the ROM are 100% working, never got problem in actual ROM and old version of RR Pie, phone call perfect, media sound perfect... There's no problem with this ROM. They need make a clean install and later if no solve post here... But I doubt with a clean install the problem persist.

 

[fgl27]

ROM update! RR-P-v7.0.0-20190302-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

 

[jcarter3729]

Man I haven't had my droid turbo since last April and I've been force to upgrade to a s8+ through verizon insurion because they didn't carry the droid turbo anymore. But I always followed the RR thread even when I didn't have the phone anymore and it so amazing how far it's come. My S8+ is nice but I can't say it was the best phone I ever had. Yeah my S8+ is rooted but I'm stuck on nougat and can't upgrade to Oreo or Pie without loosing root, the screen is bigger and the graphics is better and the external SD card is great as well but it's just not the same. so today I bought a Droid Turbo on offer up for $75 after I lost a bid on ebay for $55 it's always tricky when you're trying to outbid someone with literally 5 seconds left on the clock but I found a way to get one. Idk why but it seems like the Droid Turbo is really like the last phone of its kind to be able to root and unlock bootloader while being on Verizon (I live in The US) so that's why I'm coming back. I look forward to joining you guys again. Keep up the great work fgl27 :good:

 

[nateify]

I seem to be having an issue with very high idle drain on this phone compared to the ROM I was using previously which is based on a more "stock" LineageOS: https://forum.xda-developers.com/moto-maxx/development/rom-t3812506

I leave my Droid Turbo on battery saver combined with airplane mode overnight, and after a clean install this Pie ROM drains 15% or more at idle over 8 hours but I didn't spot any wakelocks. Attached are some relevant screenshots and zipped logs from kernel auditor. Only thing I can think of is that there is an issue with the bundled BHB kernel, is there a closer to AOSP kernel for this device or any possible kernel options to tweak to extend idle life if so?

 

[fgl27]

I seem to be having an issue with very high idle drain on this phone compared to the ROM I was using previously which is based on a more "stock" LineageOS: https://forum.xda-developers.com/moto-maxx/development/rom-t3812506

I leave my Droid Turbo on battery saver combined with airplane mode overnight, and after a clean install this Pie ROM drains 15% or more at idle over 8 hours but I didn't spot any wakelocks. Attached are some relevant screenshots and zipped logs from kernel auditor. Only thing I can think of is that there is an issue with the bundled BHB kernel, is there a closer to AOSP kernel for this device or any possible kernel options to tweak to extend idle life if so?

That app screenshot show that the device didn't sleep at all.

That is only the case when the device is charging, if you unplugged it must not happen.

So were you charging?
can you share the screenshot from the kernel app frequency table and wakelock list?
As KA app can read the values the proper way, some of those third party app you install from play can't.

Attached my ss, as you can see the device only stay awake when I'm using it, I'm not doing anything special I don't enable battery saver I don't enable airplane I leave all enable as I like all the time, I don't use data that much so is always on wifi.

when the device is rebooted the frequencies table resets and that is way the battery and ka value are different, but if I hadn't rebooted the times would be almost identical.

There ins't a AOSP kernel just the Motorola kernel that you are using, it only has modification so it can work on Pie as you can see from my ss that isn't the issue.

 

[fgl27]

ROM update! RR-P-v7.0.0-20190305-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

 

[Marky__Mark]

I got the same thing. I had 70% battery then went on a hike for a couple hours with my phone in my pocket the whole time. Next time i checked my phone, it was at 15%. Oreo didn't have this problem and has much better battery life.

 

[fgl27]

I got the same thing. I had 70% battery then went on a hike for a couple hours with my phone in my pocket the whole time. Next time i checked my phone, it was at 15%. Oreo didn't have this problem and has much better battery life.

but I never had that issue.

So I need to know how to reproduce it in order to fix it or to inform how to prevent.

Is probably a simple conflict but we need to know were.
So lets try to find what sharing what we do.

 

[thatoneguy-tog]

Battery Life

That app screenshot show that the device didn't sleep at all.

That is only the case when the device is charging, if you unplugged it must not happen.

So were you charging?
can you share the screenshot from the kernel app frequency table and wakelock list?
As KA app can read the values the proper way, some of those third party app you install from play can't.

Attached my ss, as you can see the device only stay awake when I'm using it, I'm not doing anything special I don't enable battery saver I don't enable airplane I leave all enable as I like all the time, I don't use data that much so is always on wifi.

when the device is rebooted the frequencies table resets and that is way the battery and ka value are different, but if I hadn't rebooted the times would be almost identical.

There ins't a AOSP kernel just the Motorola kernel that you are using, it only has modification so it can work on Pie as you can see from my ss that isn't the issue.

My active wakelock list looks much worse than yours and I experience bad battery life as well. I put in a new battery about a month ago to replace the stock battery from 2014! How do I get my device to 'Deep Sleep'??
Please see my attached screenshots. I can provide other details if needed. Thanks!

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

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

https://forum.xda-developers.com/picture.php?albumid=15331&pictureid=58492
Thank you!

 

[EVNS]

That app screenshot show that the device didn't sleep at all.

That is only the case when the device is charging, if you unplugged it must not happen.

So were you charging?
can you share the screenshot from the kernel app frequency table and wakelock list?
As KA app can read the values the proper way, some of those third party app you install from play can't.

Attached my ss, as you can see the device only stay awake when I'm using it, I'm not doing anything special I don't enable battery saver I don't enable airplane I leave all enable as I like all the time, I don't use data that much so is always on wifi.

when the device is rebooted the frequencies table resets and that is way the battery and ka value are different, but if I hadn't rebooted the times would be almost identical.

There ins't a AOSP kernel just the Motorola kernel that you are using, it only has modification so it can work on Pie as you can see from my ss that isn't the issue.

@fgl27 u has long battery duration, day's... I already see it in others prints u showed here, u change something in adiutor? How many apps installed has u? I'm always with balanced battery and default kernel, I normally let adiutor deactivated so I never change nothing about kernel, just default kernel of ROM. I have in app notification 87 apps...
Thx bro

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------

but I never had that issue.

So I need to know how to reproduce it in order to fix it or to inform how to prevent.

Is probably a simple conflict but we need to know were.
So lets try to find what sharing what we do.

@fgl27 just for info i too no have this issue... ROM 100% here.

 

[fgl27]

My active wakelock list looks much worse than yours and I experience bad battery life as well. I put in a new battery about a month ago to replace the stock battery from 2014! How do I get my device to 'Deep Sleep'??
Please see my attached screenshots. I can provide other details if needed. Thanks!

Thank you!

Xda mess up the ss but I manage to see...
As we can see the msm_serial_hs_dma is acquiring a lock and never releasing it causing a 100% of the time wakelock.

But you can see from my ss it doesn't happens on my device, it releases and acquires and only accounts for 6 seconds of total wake time.
So I need the logs from KA to see if I can find what is going on.

Anyone with the same issue share, logs and screenshots so I can debug this...
screen shots like this:
https://forum.xda-developers.com/showpost.php?p=79045203&postcount=170

@fgl27 u has long battery duration, day's... I already see it in others prints u showed here, u change something in adiutor? How many apps installed has u? I'm always with balanced battery and default kernel, I normally let adiutor deactivated so I never change nothing about kernel, just default kernel of ROM. I have in app notification 87 apps...
Thx bro

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------


@fgl27 just for info i too no have this issue... ROM 100% here.

This battery of my is original so is old, but it behaves OK after all this years, so I didn't change yet even tho I have a new one.

I lately don't change much, I set core 0 and 1 to 1958, 2 to 2419 and 3 to max freq (simulating big/little on a none big/little cpu device, as we have all the other power tool to simulate/support this behavior), lower the voltage to a value that doesn't causes reboot (on my is -25mV, may vary on others) and disable crc (in misc) that is it.
I have very little app under 60 besides messaging apps I don't have any that runs on background, as I use messaging app that also works on computer, I manage to lower the SOT time from the device.

Apps that run in background are the one's to look for, for some reason disabling all apps access to notification improves battery (search for "notification access" in settings search).


:good:

 

[Marky__Mark]

but I never had that issue.

So I need to know how to reproduce it in order to fix it or to inform how to prevent.

Is probably a simple conflict but we need to know were.
So lets try to find what sharing what we do.

Sure. I got back on pie on 2/11/19 with a freah install. I dirty flashed every update until 3/2/19 where i had that issue i described earlier and reverted to my oreo backup. I never had as good battery life as oreo even after the fresh install on 2/11/19. I think i found it burned at least 15%-20% more during sleep than oreo during the course of a day. Oreo doesn't eat any battery during sleep. I thought maybe it was ambient display eating up more battery on pie. Especially when in my pocket. I think maybe theres a lack of pocket detection when on ambient display. So between the battery life and text message notifications being delayed by ten minutes or so, i decided to go back to oreo for a while till things are hashed out. I dont think this is you, @flg27. Its probably google.

---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------

but I never had that issue.

So I need to know how to reproduce it in order to fix it or to inform how to prevent.

Is probably a simple conflict but we need to know were.
So lets try to find what sharing what we do.

Oh yeah. And i have the exact same apps on Oreo that i did with pie and Oreo battery is noticeably better. Im on it right now so i know my battery isnt the issue.

 

[fgl27]

@nateify & @thatoneguy-tog or anyone with that odd wakelock issue

do you guys have bluetooth enable, I manage to reproduce the issue by enabling it.
I also find a fix to prevent the issue.

Will release a update in 12 to 24h but on the mean time try to disable that if is enable.

:good:

 

[nateify]

As we can see the msm_serial_hs_dma is acquiring a lock and never releasing it causing a 100% of the time wakelock.

@nateify & @thatoneguy-tog or anyone with that odd wakelock issue

do you guys have bluetooth enable, I manage to reproduce the issue by enabling it.
I also find a fix to prevent the issue.

Will release a update in 12 to 24h but on the mean time try to disable that if is enable.

:good:

I can confirm that msm_serial_hs_dma was the wakelock from the BHB kernel auditor. Once I blocked it, battery drained 3% some 6 hours, on par now with Oreo. And my idle goes to deep sleep instantly now when I run ForceDoze app. However in my original post, bluetooth was disabled the entire time combined with airplane mode when it was draining 15%+ in the same time frame originally.

 

[Marky__Mark]

I can confirm that msm_serial_hs_dma was the wakelock from the BHB kernel auditor. Once I blocked it, battery drained 3% some 6 hours, on par now with Oreo. And my idle goes to deep sleep instantly now when I run ForceDoze app. However in my original post, bluetooth was disabled the entire time combined with airplane mode when it was draining 15%+ in the same time frame originally.

Thanks. Ill have to get back on pie