[ROM][discovery][PIE] Resurrection Remix [DISCONTINUED]
- Thread starter AlaskaLinuxUser
- Start date
Alright, so I've noticed its not quite as snappy as the current lineage build, some apps are lagging from time to time, using latest pico opengapps and magisk. Boot takes a while longer, and bootanimation lags real bad.Also I have the sony smart case and it takes a bit for the screen to come on when opening it. Probably going to wipe and reflash just in case I missed something somewhere. Been working on it whilst cooking supper and getting kids on their homework lol. The smart case issue happened to me some time ago on lineage and then just sort of disappeared after an ota. Not sure what was done or what build.
Last edited:
alright so everything sorted out, rewiped, reflashed. everything so far seems ok though bootanimation still seems to hang on forever
Will not let me select a photo here, takes a bit for the screen to wake even without smart cover
Attachments
Last edited:
Thanks for the feedback. So the screen being slow to wake, is that with gapps and magisk installed? It seems responsive here, but I don't doubt it happens for you. Do you have any widgets on the screen? Or any lock screen options enabled that you could turn on/off to test speed?
Or could you pull a logcat after a slow wake up?
Is it every time, or when coming out of a deep sleep?
Thanks!
If the screen is off for more than about 30 seconds I'd say, did the same without root but haven't tried without gapps, I'm using the latest pico. I'll tinker when I get off work. Right now if takes me about 5 minutes of fiddle****in to get it to wake, otherwise totally responsive, i.e. I've been listening to to music /Bluetooth and the phone responds instantly to volume and track change using volume keys
I get off in about 5hours
This is what I get
---- Nov 6, 2019 2:53:09 PM ----
11-06 14:54:11.498 17185 17185 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@59cedec
11-06 14:54:33.771 17185 17185 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@d05d0b8
11-06 14:54:42.290 17185 17185 I Choreographer: Skipped 56 frames! The application may be doing too much work on its main thread.
11-06 14:54:42.880 17185 17206 I OpenGLRenderer: Davey! duration=1535ms; Flags=0, IntendedVsync=5057894829696, Vsync=5058828162992, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=5058840742391, AnimationStart=5058840774266, PerformTraversalsStart=5058840775829, DrawStart=5059403661974, SyncQueued=5059414382339, SyncStart=5059414477339, IssueDrawCommandsStart=5059419025672, SwapBuffers=5059427575516, FrameCompleted=5059429941662, DequeueBufferDuration=536000, QueueBufferDuration=721000,
11-06 14:54:46.108 17185 17185 I Choreographer: Skipped 195 frames! The application may be doing too much work on its main thread.
11-06 14:54:46.240 17185 17206 I OpenGLRenderer: Davey! duration=3382ms; Flags=0, IntendedVsync=5059408130319, Vsync=5062658130189, OldestInputEvent=5062504740000, NewestInputEvent=5062743321000, HandleInputStart=5062658327077, AnimationStart=5062762305515, PerformTraversalsStart=5062763069473, DrawStart=5062776154733, SyncQueued=5062781741348, SyncStart=5062781796765, IssueDrawCommandsStart=5062783571608, SwapBuffers=5062789564212, FrameCompleted=5062790845202, DequeueBufferDuration=409000, QueueBufferDuration=326000,
---- Nov 6, 2019 3:22:51 PM ----
---- Nov 6, 2019 2:53:09 PM ----
11-06 14:54:11.498 17185 17185 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@59cedec
11-06 14:54:33.771 17185 17185 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@d05d0b8
11-06 14:54:42.290 17185 17185 I Choreographer: Skipped 56 frames! The application may be doing too much work on its main thread.
11-06 14:54:42.880 17185 17206 I OpenGLRenderer: Davey! duration=1535ms; Flags=0, IntendedVsync=5057894829696, Vsync=5058828162992, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=5058840742391, AnimationStart=5058840774266, PerformTraversalsStart=5058840775829, DrawStart=5059403661974, SyncQueued=5059414382339, SyncStart=5059414477339, IssueDrawCommandsStart=5059419025672, SwapBuffers=5059427575516, FrameCompleted=5059429941662, DequeueBufferDuration=536000, QueueBufferDuration=721000,
11-06 14:54:46.108 17185 17185 I Choreographer: Skipped 195 frames! The application may be doing too much work on its main thread.
11-06 14:54:46.240 17185 17206 I OpenGLRenderer: Davey! duration=3382ms; Flags=0, IntendedVsync=5059408130319, Vsync=5062658130189, OldestInputEvent=5062504740000, NewestInputEvent=5062743321000, HandleInputStart=5062658327077, AnimationStart=5062762305515, PerformTraversalsStart=5062763069473, DrawStart=5062776154733, SyncQueued=5062781741348, SyncStart=5062781796765, IssueDrawCommandsStart=5062783571608, SwapBuffers=5062789564212, FrameCompleted=5062790845202, DequeueBufferDuration=409000, QueueBufferDuration=326000,
---- Nov 6, 2019 3:22:51 PM ----
Attachments
Last edited:
So far so good, as in no more problem?
The original logs about Choreographer and Davey are just warnings that some process is really eating up your CPU/ram and bogging down the system.
Unfortunately, there is not enough information to tell you what process causes the issue. It could be anything from an app that automatically looks for or downloads something when the screen comes on, like a widget on your home screen.
Or perhaps it could be an animation. Do you have any custom animations set? Or live backgrounds?
Custom animation yes, I set everything up exactly how I had it, I must've just missed something the first time
Still takes an unusual time to boot up, and wake, but waking is not nearly as bad as before. Before it would take 2 or 3 minutes to wake lol
Still takes an unusual time to boot up, and wake, but waking is not nearly as bad as before. Before it would take 2 or 3 minutes to wake lol
Last edited:
I'm still getting slow screen turn on from deep sleep. Especially when I'm using Spotify
Yeah Spotify seemed to make it way worse, something is eating ram like Cookie monster!
Interesting.
So here, it is working great, but I am gappless, nor do I have spotify. I'd be glad to try to make some changes, but I'd need something to work with. Are there any logs or hard data you could give me to work with?
Perhaps a route to go would be to remove apps, one at a time, testing the screen wake issues, to see if there are specific apps that cause problems? If that app was not the issue, you could put it back, after testing without it.
Also, turning off animations to see if there is an issue with a particular animation, or animations in general?
If you guys can pinpoint the problem, then there is hope for me to fix it.... :fingers-crossed:
ok
ill give her a go after bit, im about to play with 10 a bit, til its time for breakfast, the boys are wanting biscuits and gravy w/bacon lol perhaps closer to supper time ill dive into it again:silly:
Interesting.
So here, it is working great, but I am gappless, nor do I have spotify. I'd be glad to try to make some changes, but I'd need something to work with. Are there any logs or hard data you could give me to work with?
Perhaps a route to go would be to remove apps, one at a time, testing the screen wake issues, to see if there are specific apps that cause problems? If that app was not the issue, you could put it back, after testing without it.
Also, turning off animations to see if there is an issue with a particular animation, or animations in general?
If you guys can pinpoint the problem, then there is hope for me to fix it.... :fingers-crossed:
ill give her a go after bit, im about to play with 10 a bit, til its time for breakfast, the boys are wanting biscuits and gravy w/bacon lol perhaps closer to supper time ill dive into it again:silly:
ok so i had a change of heart , i went ahead and did a fresh flash with rr, no gapps no root etc. so far so good, i did enable the recents memory bar, so far she floats at about 2300mb free constantly, ima play around a bit more whilst food is cooking then ill do gapps, investigate, other stuff, investigate and see what happens
Ok so @lonewolfbtown my findings are that if I set up as a fresh device the issues aren't so bad, theres still a memory hole somewhere but I don't see much of a lag on screen wake unless someone is calling me. I tested for at least half the day, with/without gapps and root, changing settings like animations etc
Man I wish I was an expert in this but I have no idea where to begin to look for a memory leak.
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
Interesting.
So here, it is working great, but I am gappless, nor do I have spotify. I'd be glad to try to make some changes, but I'd need something to work with. Are there any logs or hard data you could give me to work with?
Perhaps a route to go would be to remove apps, one at a time, testing the screen wake issues, to see if there are specific apps that cause problems? If that app was not the issue, you could put it back, after testing without it.
Also, turning off animations to see if there is an issue with a particular animation, or animations in general?
If you guys can pinpoint the problem, then there is hope for me to fix it.... :fingers-crossed:
I would be willing to go gappless if I could figure out how to still use my Google account and aptoid. Haven't figured it out
Well, going gappless is not for everyone. But for the inclined, here is an article I wrote about how I went about it, still accessing my gmail, with Aptoid, F-Droid, my calendar from Google, etc.
https://thealaskalinuxuser.wordpress.com/2019/07/11/going-gapp-less-again/
This article was informative. But didnt really tell me if having your google account on your device still while going gappless. I personally just hate google playstore telling me what to do
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4Well, good news! Praise God! I was able to build Android 9.0 based off the Xperia opensource project with the 50.2 firmware. I flashed it to my 50.2 phone and it works - mostly. It also includes the 4.9 kernel as well (50.1 is still using 4.4 kernel), so that's great! Attached are a few teaser shots.
Everything worked: camera, bluetooth, gps, wifi, cellular, display, sound, fingerprint, etc. the only problem is it seems a bit buggy....
A few buggy examples are: When using the camera, I switched to selfie mode, then back to the back camera, and it shows up green tinted, you have to reboot to fix it. MTP transfers or PTP file transfers seemed to glitch every now and then, causing problems when moving files back and forth between the computer. And a few other items like that.
So it is not a daily driver yet for sure, but it is good progress! :highfive:4I checked the RR repository today, they still have not committed all of the security update changes for October. As soon as they do that, I will make a new (50.1 based firmware) build.
I am currently working on Android 10. It is booting and many things are working, but the 4.14 kernel is not very stable yet. I am also working on the best way forward to support those with 50.2 based firmware. I would like to find a path forward where everyone can legitimately upgrade to 50.2 firmware and have a good solid working custom rom. Thank you for your patience.3
To God be the glory, I finally finished a XA2 Ultra build of Resurrection Remix! It's Resurrection Remix, Pie flavored!
WARNING: This is for phones that are now using the 50.2 firmware base! There is still an old build for the 50.1 firmware base, but I recommend you upgrade to 50.2 firmware.
"We work to make your android experience elegant. Handpicked features beautifully packed into one ROM."
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
A huge thanks to the Resurrection Remix team!
Another huge thanks goes out to @LuK1337 for all of the great development that he does on the Sony Xperia XA2 Ultra! He did most of the heavy lifting by making a great LineageOS build, upon which this RR is based. Please note, this is an UNOFFICIAL ROM.
Disclaimer: Resurrection Remix is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make Resurrection Remix, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
This Unofficial Resurrection Remix Pie ROM was built for H3223 (discovery), but may work on some of the other variants, please try at your own risk. However, if you do try it on another variant, please be sure to let me know in the comments how it worked.
Downloads:
Installation instructions:
What works:
What doesn't:Code:So far everything that I have tried works, such as - Camera for pictures and video! - Phone calls - Data 3g/LTE - Bluetooth - WiFi - MTP - FM Radio etc....Code:- Nothing else that I know of, but if you find something, please let me know so we can try to fix it!
Source Code:
https://github.com/ResurrectionRemix
Official website:
http://www.resurrectionremix.com/
My device trees, vendor blobs, and kernel source:
https://gitlab.com/alaskalinuxuser/android_device_sony_discovery
ROM OS Version: 9.0 Pie
RR version: 7.0.2
ROM Kernel: Linux 4.4.153
Based On: The best of every ROM, but particularly based on LineageOS.
Created 2019-08-16
Last Updated 2019-11-0433Just checked again this morning, RR has still not updated their pie source code with the security patches. I believe that all of their "phocus" is on Android 10. I'll check next week and we will see about using Luk1337's 50.2 firmware for the build as well.
