Swift Backupwhich will be the best app to restore apps onto this rom? I am currently on 9 and am using titanium, I will flash this rom tomorrow, will titanium restore all my apps and data from 9 to 10? if not which app do you guys suggest? thanks
Swift Backupwhich will be the best app to restore apps onto this rom? I am currently on 9 and am using titanium, I will flash this rom tomorrow, will titanium restore all my apps and data from 9 to 10? if not which app do you guys suggest? thanks
TB all the waywhich will be the best app to restore apps onto this rom? I am currently on 9 and am using titanium, I will flash this rom tomorrow, will titanium restore all my apps and data from 9 to 10? if not which app do you guys suggest? thanks
As I've been absent from the flashing scene for a long time, I've been using TB for years but only just now after the above comment I've installed swift, I'm also reading there's issues with TB on 10 builds, so just in case I've made backups with both, just getting everything ready for my flash tomorrow, otg drive ready and onto RR 10 finally...TB all the way
I tried Swift quite some time in the past. Now I don't remember what I did not like, but at that time I came back to TB. Looks like no further development is going on, but TB is still a solid choice. Still working, no issues on A10, both OOS and custom ROMs. I'm sure it will work on A11 as well.As I've been absent from the flashing scene for a long time, I've been using TB for years but only just now after the above comment I've installed swift, I'm also reading there's issues with TB on 10 builds, so just in case I've made backups with both, just getting everything ready for my flash tomorrow, otg drive ready and onto RR 10 finally...
Nice, I've made backups with both, I have noticed sometimes TB doesn't restore full data, esp with games and I'm balls deep into this game called Another Eden. Want to make sure that gets transferred over fully, hopefully with one or the other it willI tried Swift quite some time in the past. Now I don't remember what I did not like, but at that time I came back to TB. Looks like no further development is going on, but TB is still a solid choice. Still working, no issues on A10, both OOS and custom ROMs. I'm sure it will work on A11 as well.
Another flaw of Swift Backup, it cannot be used on vanilla ROMs as it needs google play services to run.Installed Swift and now I know what I didn't (and don't) like about it. I MUST to have an account with them plus all my data is flying to them.
There was a huge discussion with dev here on XDA. He provided the reasons for that, but me personally haven't been convinced that all that is really needed. So, I dropped the ball on the app.
For your steps - item 6. why you want to flash vanilla version and then flash gapps? just flash RROS with gapps and you're done.
Item 8 - you can flash magisk before rebooting th phone.
Other than that, looks fine to me.
Here we go.Another flaw of Swift Backup, it cannot be used on vanilla ROMs as it needs google play services to run.
RROS has gapps built in but the vanilla builds don't? That's what I've gathered here from info, going for vanilla as it's a lighter package and won't be bloated with Google stuff, the bare minimal of Google is good with me.Installed Swift and now I know what I didn't (and don't) like about it. I MUST to have an account with them plus all my data is flying to them.
There was a huge discussion with dev here on XDA. He provided the reasons for that, but me personally haven't been convinced that all that is really needed. So, I dropped the ball on the app.
For your steps - item 6. why you want to flash vanilla version and then flash gapps? just flash RROS with gapps and you're done.
Item 8 - you can flash magisk before rebooting th phone.
Other than that, looks fine to me.
java.lang.IllegalStateException: beginBroadcast() called while already in a broadcast
at android.os.RemoteCallbackList.beginBroadcast(RemoteCallbackList.java:241)
at android.os.RemoteCallbackList.broadcast(RemoteCallbackList.java:328)
at android.telephony.ims.stub.ImsRegistrationImplBase.onRegistered(ImsRegistrationImplBase.java:132)
at org.codeaurora.ims.ImsServiceSub.handleSrvStatusUpdate(ImsServiceSub.java:988)
at org.codeaurora.ims.ImsServiceSub.access$1800(ImsServiceSub.java:104)
at org.codeaurora.ims.ImsServiceSub$ImsServiceSubHandler.handleMessage(ImsServiceSub.java:1722)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7398)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
I gave up on that already. It recognizes my CC, everything is fine. I even make one payment successfully. After that, GPay loses access to the card and I have to add it again.Anyone else facing issues using Google pay? I do pass safety net. It usually works after a few attempts but it takes super long for the nfc to recognize that it's on a payment terminal.
I use the standard 3 button navbar so not sure..Running 8.6.6, but this started with 8.6.5:
Using gesture navigation, the first swipe up instantly snaps back to the bottom, forcing me to repeat the gesture. While in the same app, after it happens once, it doesn't happen again.
Also , is the Google Assistant always on function still broken? As in it causes horrible call quality?
Resurrection tools -> Interface -> Gaming -> Optimize refresh rate
which mentions "Optimize refresh rate when switching to gaming mode. 60hz is used preferably for a smoother gameplay" which I just assumed by that specific snippet that it could serve as a 60hz switch? But, apparently not. I'm not even sure what it does...Currently using gesture nav for the first time, but I'm not seeing this problem.Using gesture navigation, the first swipe up instantly snaps back to the bottom, forcing me to repeat the gesture. While in the same app, after it happens once, it doesn't happen again.
Appreciate the reply- it was due to a bug with Nova7 beta with the companion app. Constantly loading and crashing on swipe home.Always loved the customization RR provides, so glad to see this getting official support for the device.
So far, it's been completely smooth sailing - at least, after updating the stock OS base from Pie to the latest A10 builds (cellular didn't work prior to doing this). Bio auth is solid, and even the Google bloat is minimal; nice for someone who uses GMS/GSF as a necessity for some apps and nothing else.
My only qualm so far is that I'm not sure how this ROM handles refresh rate changes? For the first day, I've had it set to "auto" (which presumably should be 90hz when supported, 60hz fallback), but some apps that I want to use in 60hz are still locked at 90. As good as that may sound at first, emulators like Yaba Sanshiro (Saturn emu) will run at 1.3x speed, and will sound like it's misbehaving - because it is.
I've found the option inResurrection tools -> Interface -> Gaming -> Optimize refresh rate
which mentions "Optimize refresh rate when switching to gaming mode. 60hz is used preferably for a smoother gameplay" which I just assumed by that specific snippet that it could serve as a 60hz switch? But, apparently not. I'm not even sure what it does...
Is there an explanation as to what that feature does? And for that matter, how can I limit apps to a lower refresh rate while maintaining SystemUI smoothness at 90hz? Because until then, I'll probably continue to use 60hz until figuring this out.
Oh yeah, and maybe an option to disable the Custom Kernel warning? I'm using Kirisakura v2.0.0-custom which I'm perfectly happy with and works well with all the major device functionality, so (at least after doing my own testing to ensure everything's functioning as intended) I'd rather not get nagged for being a power user... in a power user's system image.
Also,
Currently using gesture nav for the first time, but I'm not seeing this problem.