AlldocubeM8 wich GSIversion is more stable - Treble-Enabled Device Questions and Answers

Hi, I have an Alldocube M8 (on android8.0) I tried to root it but its not worked so apparently I can install a GSI release even if its not rooted or have trwp app install.
Wich release version of GSI is the more stable I need to have GPS working properly wifi bluethoot... ???

Related

Problem with Netflix app

Hi.
I've a problem with a Netflix app (last version) error 5.2, in my nexus 7 (flo)
With android stock by google (6.0.1) and root SU or Magisk no error and all works but if i try a custom rom lineage os 14.1 or RR (android 7.1.2) with and without root does't work.
The file liboemcrypto.so don't esist in these custom rom.
Can you help me?
nobody?
I think you have the same problem as another poster... here's what I believe is your solution:
If you want to run Netflix, you need to run an older version of NetFlix. The ROM developer for Pure Nexus created a signed version (I think avoids you receiving app updates). Here's a link to the download: https://androidfilehost.com/?fid=529152257862715472 Thank the developer (his ROM and any other info is located here: https://forum.xda-developers.com/nex...ratum-t3576447 ).
I've been using this version on mine for the last month. Works Fine.
"com.netflix.mediaclient_4.16.1_build_15145-15145_minAPI19(armeabi-v7a)(nodpi)_apkmirror.com"
Allows downloading as well.
On lineage 14.1 only 4.8.5 works for me 4.16.1 does not.
Running magisk rooted Lineage 14.1 (02/28) here on flo and deb Nexus 7s. Netflix v5.14.0 (which downloaded from playstore this week after rooting w/Magisk). All works fine, including downloading.
Installing 4.8.5 worked. Thank you.
Although being signed, it did still ask me of I wanted to update.

Samsung Galaxy A5 2017 Custom ROM and Issues with Fixes

So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.

Well, i'm confused for the Android Pie update.

Ok, well.
I saw that i can install android pie on my already rooted oneplus 5t (android oreo 8.1, OxygenOSS 5.1.7).
I downloaded the file from xda, updated TWRP at last version, downloaded also last Magisk version for rooting after updating my android version.
I got "Zip treble compatibility error" That i didn't know what is it so i searched and i found out that i had to remove the "compatibility" zip in the zip of that downloaded update.
I did it and it didn't worked again.
What is happening why i can't get android pie?
Also, are there any problems with this build? In searchings i read that the phone doesen't recognize the 100% of batterylife and keep get charged and can be ruined.
What if you download the android pie beta from the oneplus.com website. ive been using this for a month or so and it worked fine for me, especially when you're used to OOS.
So if i download the rom from there, i got no "Zip treble compatibility" error?
i can speak only for blu_spark software but this worked for me:
use TWRP 9.85 (https://forum.xda-developers.com/devdb/project/dl/?id=30332) to update FROM 5.1.7 to pie (remove compatibility.zip for this update)
once you are ON pi, install
TWRP 9.91 (https://forum.xda-developers.com/devdb/project/dl/?id=31102) for any update from now onwards (no need to remove the compatibility.zip any more)
use the rom from this post https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
official rom: http://otafsg.h2os.com/patch/amazon...TOxygen_43_OTA_045_all_1901072301_6ada5c1.zip
I am going back becouse xposed framework is not supported on android pie
by the way i post here how i got pie from oreo becouse i faced lot of problems!
-First of all download the official update
-then, the only twrp i found that work is this: https://eu.dl.twrp.me/dumpling/twrp-3.2.3-0-dumpling.img.html the 3.2.3.1 didn't worked for me.
-i had to flash magisk uninstaller and then install magisk, i got bootloops before doing uninstall and then install.
Btw i am downloading another rom for 8.1 becouse xposed don't work for now on 9.
Any suggest for changing the rom? I am searching what to get
thanks anyway guys

Stable Custom ROM for XT1952-1?

Hi,
I'm a beginner to installing custom ROMs so forgive me if I'm asking dumb questions.
I'm thinking of buying a used G7 play and would like to install a custom ROM on it. It is the XT1952-1 version and I can't seem to find much information on running custom ROMs on it. The LineageOS page only lists XT1952-2 and -3 as supported models.
Is there a stable custom ROM I could use on this device as a daily driver where everything is working (including VoLTE and fingerprint sensor) and I will get security updates?
Thanks a lot in advance,
Tobias
I am also interested, because I have got an XT1952-1 phone which gets no system updates anymore. :/
I've got an XT1952-3 (US version) with Lineage 18.1 and it's fully stable, way smoother than with the stock firmware. It still receives system updates, despite the Motorola security updates are stuck at some mid-2021 version.

Wich LinageOS is the most uncomplicated Version for T525 ?

Hello
I was happy to found your Forum, because i have an Samsung Tab Pro 10.1T525 LTE with Android 4.4.2 and i will flash it to a newer Version. Actually i rooted the Tablet and installed TRWP 3.0.2.0 and make Backup. Now i will install LineageOS but read often about different problems after that . So i will search for the most stable / uncomplicated Version of it. Wich is the Version with the best Result of working without problems ? It must not be the newest for me. Especially the LTE Feature i will not loose. And wich Gapps i need for wich Processor ?
Thank you
Actually i think i will use LineageOS 17.1 latest and OpenGapps ARM64 10.0 stock. Do you think thats ok and is the Google Playstore included ?
FrankLinke said:
... OpenGapps ARM64 10.0 stock. Do you think thats ok and is the Google Playstore included ?
Click to expand...
Click to collapse
not at all as you need ARM having a 32bit device.
Imo its better to use pico version for eliminating errors by google stuff.
I use either that or the even smaller Bitgapps.
Everything else you need from google can be installed later from the store.

Categories

Resources