How To Install GSIs on Galaxy M20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bugs:
- Volte (will never work)
Requirements:
- Must be on OneUI 2.0.
- Unlocked Boot-loader & TWRP 3.4.0-0 or newer version installed.
Instructions:
1) Boot into latest TWRP.
2) Download any Android 10 ARM64-A/B variant GSI. (From here)
3) If its not in .img format extract it to .img format.
4) Flash it as system image.
- Optional: Resize system partition if you want to flash gapps.
5) Do factory reset.
6) Flash following 3 patches
- Magisk (Necessary to boot)
- dm-verity and forced encryption disabler (attached below)
- The-Phix (Fixes Camera, Media playback, MTP, Screen Lock) (Download from here)
7) Reboot
Tested GSIs :
- AOSP
- LineageOS
Credits:
SamarV121 - Fixing the bugs and TWRP.
XXXTC3X - Testing
XDA:DevDB Information
Q GSIs on Galaxy M20, ROM for the Samsung Galaxy M20
Contributors
Haridhayal
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-07-01
Last Updated 2020-07-03
- reserved
lineageos booted but automatic restart evrey 10 min
eltahir said:
lineageos booted but automatic restart evrey 10 min
Click to expand...
Click to collapse
You didn't flash the Phix .zip
MTP, fingerprint, wide-angle cam, lockscreen, PIN, sdcard are still not working on Phhusson build even after flashing the-phix.zip.
Bugs on lineage os: mtp, fingerprint, cam, lockscreen, bootloop, sd card, PIN, browser are not working.
sunnatter said:
MTP, fingerprint, wide-angle cam, lockscreen, PIN, sdcard are still not working on Phhusson build even after flashing the-phix.zip.
Bugs on lineage os: mtp, fingerprint, cam, lockscreen, bootloop, sd card, PIN, browser are not working.
Click to expand...
Click to collapse
yes i did it like 10 times currently on havoc os 3.7
and the only things that dont work are MTP and Lock Screen even after the phix.
alfadyn said:
yes i did it like 10 times currently on havoc os 3.7
and the only things that dont work are MTP and Lock Screen even after the phix.
Click to expand...
Click to collapse
You didn't get bootloop after the second boot?
sunnatter said:
You didn't get bootloop after the second boot?
Click to expand...
Click to collapse
nope. but i switched to vanilla android aosp from phhuson. and the only thing i need a lock screen fix. mtp is also not working but it s not that important for me.
alfadyn said:
nope. but i switched to vanilla android aosp from phhuson. and the only thing i need a lock screen fix. mtp is also not working but it s not that important for me.
Click to expand...
Click to collapse
Cool. Before i tried gapps from phhusson and lineageos 17.1 but lineage seemed to have more bugs.
I also want to test uport (unbutu touch port) later on.
alfadyn said:
nope. but i switched to vanilla android aosp from phhuson. and the only thing i need a lock screen fix. mtp is also not working but it s not that important for me.
Click to expand...
Click to collapse
Aosp from phhusson has the same issue is bootloop after i reboot. Is havoc a better option?
I would like to switch to custom rom instead of stock rom, since sometimes i got annoyingly bizarre reboot without any reason.
sunnatter said:
You didn't get bootloop after the second boot?
Click to expand...
Click to collapse
I think the reason why your phone is bootlooping is because you tried setting up a lockscreen. You have to delete the keystore.mdfpp.so file in /vendor/lib64/hw/ for the fingerprint sensor to work and not cause bootlooping issues.
---------- Post added at 07:02 AM ---------- Previous post was at 06:56 AM ----------
sunnatter said:
Aosp from phhusson has the same issue is bootloop after i reboot. Is havoc a better option?
I would like to switch to custom rom instead of stock rom, since sometimes i got annoyingly bizarre reboot without any reason.
Click to expand...
Click to collapse
Try using the most recent aosp/lineage gsi update. The random app crashes and other issues (like camera not working) have been fixed
To fix mtp flash this in twrp: drive . google. com/file/d/1YoBxX--hI_WC43isSrLghOQnb5wW6-QZ/view?usp=sharing (I'm spacing out the link cause I'm not allowed to post links yet)
xxxtc3x said:
I think the reason why your phone is bootlooping is because you tried setting up a lockscreen. You have to delete the keystore.mdfpp.so file in /vendor/lib64/hw/ for the fingerprint sensor to work and not cause bootlooping issues.
---------- Post added at 07:02 AM ---------- Previous post was at 06:56 AM ----------
Try using the most recent aosp/lineage gsi update. The random app crashes and other issues (like camera not working) have been fixed
To fix mtp flash this in twrp: drive . google. com/file/d/1YoBxX--hI_WC43isSrLghOQnb5wW6-QZ/view?usp=sharing (I'm spacing out the link cause I'm not allowed to post links yet)
Click to expand...
Click to collapse
Thanks man, i appreciate it. I will try it out soon.
Device doesn't boot
I've followed all the above instructions but the device doesn't boot past Samsung Logo screen.
What could I be doing wrong
xxxtc3x said:
I think the reason why your phone is bootlooping is because you tried setting up a lockscreen. You have to delete the keystore.mdfpp.so file in /vendor/lib64/hw/ for the fingerprint sensor to work and not cause bootlooping issues.
---------- Post added at 07:02 AM ---------- Previous post was at 06:56 AM ---------
Click to expand...
Click to collapse
And how do you fix the lockscreen?
---------- Post added at 06:39 AM ---------- Previous post was at 06:38 AM ----------
Siddharthkumar195 said:
I've followed all the above instructions but the device doesn't boot past Samsung Logo screen.
What could I be doing wrong
Click to expand...
Click to collapse
Pls describe more detail or else we can't guess what you did wrongly.
Tried this on my M20, but as above it does not go past the Galaxy M20 Splash screen. Stuck there and does not progress. Will update if I find a fix.
Everything works fine bro
---------- Post added at 02:18 AM ---------- Previous post was at 02:17 AM ----------
thes3usa said:
Tried this on my M20, but as above it does not go past the Galaxy M20 Splash screen. Stuck there and does not progress. Will update if I find a fix.
Click to expand...
Click to collapse
What gsi did you use?
has anyone tried and got a stable working device? i wanna try, but im too afraid because this phone is my only daily driver
sunnatter said:
What gsi did you use?
Click to expand...
Click to collapse
I tried most GSIs but only PHH based GSIs boot. A few issues like Camera are still there for some reason.
thes3usa said:
I tried most GSIs but only PHH based GSIs boot. A few issues like Camera are still there for some reason.
Click to expand...
Click to collapse
You are right. Recording has some problems and the phone speaker is softer than on stock rom.
tanle2702 said:
has anyone tried and got a stable working device? i wanna try, but im too afraid because this phone is my only daily driver
Click to expand...
Click to collapse
update: tried havoc (v3.7), lineage (17), blissOS 12.10, CAOS, AOSP. Stayed on havoc 3.7, no magisk.
Everything is working, havent tried volte yet, but:
-fingerprint
-screenlock
-camera (back and front, no ultra wide angle)
-face unlock
-speakers
-wifi
-bluetooth
-fast charging
are working.
There are a few bugs: wifi doesnt automatically connect after first time entering password, wifi sometimes disconnect when browsing google photos (other apps are fine), no auto brightness, choppy scrolling in chrome (firefox is smooth).
p/s: M205G variant
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Resurrection Remix
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
New download: https://www.mediafire.com/folder/5a97vbv93k24n/tate
Old download: https://www.mediafire.com/folder/w9nh7oyabwvww/tate
(backup before flash, gapps need for upgrade, don`t flash SuperSU)
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
CURRENT KNOWN ISSUES:
Bootloop with app optimize
Thank you so much!!! Downloading and flashing this now!! I'll report any bugs I find, if any.
So far it flashed ok, (Clean) and flashed Open Gapps (Pico), booted thru the animation, set up all 87 apps, and now it's been sitting on "Starting apps" for about 10 minutes or so... I'm thinking about powering it down and trying to reboot.
Update2: Tried reboot- stuck at Starting apps
Tried reflash w/o gapps- Still stuck at Starting apps.
Anyone else get past this point?
Wait... Marshmallow? For the Tate? What!!!!
vasolini said:
Thank you so much!!! Downloading and flashing this now!! I'll report any bugs I find, if any.
So far it flashed ok, (Clean) and flashed Open Gapps (Pico), booted thru the animation, set up all 87 apps, and now it's been sitting on "Starting apps" for about 10 minutes or so... I'm thinking about powering it down and trying to reboot.
Update2: Tried reboot- stuck at Starting apps
Tried reflash w/o gapps- Still stuck at Starting apps.
Anyone else get past this point?
Click to expand...
Click to collapse
Are you able to pull a log?
xWolf13 said:
Are you able to pull a log?
Click to expand...
Click to collapse
I would love to. Is there an easy way to do it? (sorry, noob here!)
vasolini said:
I would love to. Is there an easy way to do it? (sorry, noob here!)
Click to expand...
Click to collapse
i`ll checking on jem this trouble, maybe RR-team updated this trouble
transi1 said:
i`ll checking on jem this trouble, maybe RR-team updated this trouble
Click to expand...
Click to collapse
Sounds good. Just so they know, I have the latest TWRP installed, and did a full wipe except internal sd. Looking forward to getting this going! :good:
Update: turns out I didn't have the latest TWRP. I had 2.8.3.0! Just updated it to 2.8.7.0 and tried again..... still stuck at "Starting apps".
vasolini said:
Sounds good. Just so they know, I have the latest TWRP installed, and did a full wipe except internal sd. Looking forward to getting this going! :good:
Update: turns out I didn't have the latest TWRP. I had 2.8.3.0! Just updated it to 2.8.7.0 and tried again..... still stuck at "Starting apps".
Click to expand...
Click to collapse
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
monster1612 said:
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
Click to expand...
Click to collapse
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
monster1612 said:
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
Click to expand...
Click to collapse
I would love to contribute to the kernel. Can you link me to the source of your kernel? Vanilla CM13 is on my list for this device. As I have yet to flash this, has anyone bypassed the Starting Apps screen?
vasolini said:
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
Click to expand...
Click to collapse
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
xWolf13 said:
I would love to contribute to the kernel. Can you link me to the source of your kernel? Vanilla CM13 is on my list for this device. As I have yet to flash this, has anyone bypassed the Starting Apps screen?
Click to expand...
Click to collapse
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
Click to expand...
Click to collapse
Any problems that have come up on the jem? I don't own the device, but I reckon that whatever the bugs are in jems may come up on the tate.
xWolf13 said:
Any problems that have come up on the jem? I don't own the device, but I reckon that whatever the bugs are in jems may come up on the tate.
Click to expand...
Click to collapse
So far, there are some issues. Among these:
1) the AOSP camera app doesn't work; however, accessing the camera through another app such as Snapchat works fine. [SIDE NOTE: this is listed as a known issue in the jem port's thread.]
2) the camera has a yellow tint. I'm guessing it's a driver issue.
3) when I watch Snapchat stories with video, the audio is really choppy about half the time.
These are some of the major bugs I felt were worth listing. Also, I'm not sure if RRO/layers works, as I haven't been able to thoroughly test it.
vasolini said:
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
Click to expand...
Click to collapse
today i`ll uploading new build, trouble fixed in RR
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
I did do an advanced wipe. The only thing I didn't wipe was the internal SD card since that's where the image is. I always do a clean flash, especially when I am going to a different version of Android.
Click to expand...
Click to collapse
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
Click to expand...
Click to collapse
I also have the 8.9 (jem) and that one is working great! Now if I can get the 7 (tate) to be like it's big brother, we'd be set!
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
transi1 said:
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
Click to expand...
Click to collapse
(that was fast!) Downloading it now...
transi1 said:
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
Click to expand...
Click to collapse
Any chance you could compose another build for jem? I would, but I'm not too certain as to how to obtain and build the RR sources.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 12.1 for LG L Fino
THIS ROM IS CURRENTLY BEING COMPILED FOR D290N ONLY! IF YOU FACE ANY PROBLEMS ON A DEVICE OTHER THAN THE D290N DON'T COMPLAIN.
DO NOT INSTALL THIS IF YOU'RE UNAWARE OF WHAT YOU ARE DOING! ANY QUESTIONS LIKE " what's flashing" AND "how to wipe" WILL BE REPORTED SINCE THEY DO NOT CONTRIBUTE TO THE THREAD.
Notice:
This ROM is very WIP. Don't expect it to be a daily user.
Because the ROM is only tested on D290N, only this variant of L Fino is supported by me (since I only have this variant to test on).
Functionality can be broken on other variants.
The ROM theoretically can be installed on:
D290TR
D295
D295F
G2 Lite
Disclaimer:
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Click to expand...
Click to collapse
Problems/Bugs:
When in system and connected to a Windows PC via USB. The PC goes to BSOD. (Appears to be caused by LG drivers. Uninstalling them fixes the problem but also stops any ADB access.)
NFC
Some phones have spots on back camera (This is due to them using a different sensor)
Audio not balanced properly
Other small things
People involved:
@proudlytm - Providing his device for testing.
@christpp - Main kernel dev. Everything we have now is because of him. This ROM would not be possible without him.
Me - Fixing bugs and system related code.
@kylevessPL - Creating TWRP
@vm03 - Creating msm8610 kernel
Special thanks:
The CyanogenMod team for creating CyanogenMod
Google for creating Android
LG for creating L Fino
Additional information / resources:
Change logs: see 2nd post of this thread
Google apps: http://opengapps.org/ - Get the nano package!
Download (stable - milestone builds):
Latest build: 18.07.2016 D290N
Older:
18.05.2016 D290N
====
20.03.2016 D290N
====
28.02.2016 D290N
====
19.02.2016 D290N patched
====
17.02.2016 D290N
====
11.02.2016 D290N
====
02.02.2016
====
01.02.2016
How to install:
1) You must have custom recovery installed on your device. I recommend TWRP: http://forum.xda-developers.com/android/development/recovery-twrp-recovery-lg-l-fino-t3308436/
2) Download ROM .zip
3) Download Google apps
4) Put both .zip files on your device (either internal or external storage)
5) Boot your device into recovery mode
6) Make nandroid backup (if needed)
7) Wipe data/factory reset
8) Install the ROM .zip file
9) Install Google apps
10) Reboot
11) Done.
Bug reporting:
https://github.com/geekydoc/android_device_l70pn/issues
1) Visit the above link
2) Click on "New issue"
3) Enter title that explains the problem
4) Explain your problem very clearly with as much details as possible
5) Attach logs and screenshots (if needed)
Don't report a bug if it's already reported.
Don't report a bug if you:
1) have restored apps with Titanium Backup or similar software
2) are using any kind of task killer
3) are using any 3rd party tweak/hack
Name what device you're using: d290 or d295 or l70pn or l70pds
Name CM version you're using: 12.1, 13, 11 etc.
Use proper English, try not to make any spelling errors so I and other people can understand you correctly.
Click to expand...
Click to collapse
Want to help?
If you are a developer you can help us out with debugging and building over at https://github.com/geekydoc/android_device_l70pn
If you are a user you can help us out by telling us about bugs and providing information (Screenshots, logcats)
Screenshots:
Changelogs:
18.07.2016----------------------------------------------------------
Double Tap To Wake fixed.
18.05.2016----------------------------------------------------------
Camera should now be fixed. Small bugs persist but will
be flushed out
Selinux activated again. Should fix storage issues.
20.03.2016----------------------------------------------------------
Fixed rotation sensor.
Fixed magnetic sensor.
Deactivated SELinux for now.
28.02.2016----------------------------------------------------------
Fixed GPS.
21.02.2016-----------------------------------------------------------
Fixed screen flicker, burn-ins and similar problems.
19.02.2016-----------------------------------------------------------
Swapped out GPU driver. Artifacts and weird burn-ins
should be gone.
17.02.2016-----------------------------------------------------------
Fixed battery not being recognized
11.02.2016 -----------------------------------------------------------
Fixed device Power button. It can now be waked.
Fixed RAMDUMP's, the device will no longer enter them.
02.02.2016-----------------------------------------------------------
Fixed softkeys not appearing.
31.1.2016 -------------------------------------------------------------
Initial build.
####---------------------------------------------------------------
i will try it in my 290g
ValenBe said:
i will try it in my 290g
Click to expand...
Click to collapse
so i have install it and it send me to a purple screen. "DBI apps watchdog Reset"
ValenBe said:
so i have install it and it send me to a purple screen. "DBI apps watchdog Reset"
Click to expand...
Click to collapse
Does this happen every time your reboot your phone? Look what @meganukebmp wrote in the description about that problem.
proudlytm said:
Does this happen every time your reboot your phone? Look what @meganukebmp wrote in the description about that problem.
Click to expand...
Click to collapse
yes! i saw it ty, but the buttoms arent showing so when i enter in a app i have to take off my battery
So..The NFC is working? (I won't use it, I'm just curious )
ValenBe said:
yes! i saw it ty, but the buttoms arent showing so when i enter in a app i have to take off my battery
Click to expand...
Click to collapse
That's what I meant. Did it boot after you put your battery back?
I think I made a mistake with pulling out the battery...I was done with the flashing, when the TWRP is freezed...I waited, and waited, and waited. After a while it's been annoying... So I removed the battery.. It said: Boot clarification (I can't remember very well) error+ some texts..
So I have to flash the stock ROM, and reflash the CM
Guys! Do not remove the battery if it's stuck!
LimePanda said:
So..The NFC is working? (I won't use it, I'm just curious )
Click to expand...
Click to collapse
Can't really tell if it's working. I will try the ROM today.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
LimePanda said:
I think I made a mistake with pulling out the battery...I was done with the flashing, when the TWRP is freezed...I waited, and waited, and waited. After a while it's been annoying... So I removed the battery.. It said: Boot clarification (I can't remember very well) error+ some texts..
So I have to flash the stock ROM, and reflash the CM
Guys! Do not remove the battery if it's stuck!
Click to expand...
Click to collapse
Hmm.. Never experienced TWRP freezing on my phone. Good luck when you're flashing next time though
proudlytm said:
Can't really tell if it's working. I will try the ROM today.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Hmm.. Never experienced TWRP freezing on my phone. Good luck when you're flashing next time though
Click to expand...
Click to collapse
Thank you!
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
I think the ROM recognizes my phone as D295, because when I could boot it, it displayed in the settings 2 SIM card slots..Weird..
LimePanda said:
Thank you!
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
I think the ROM recognizes my phone as D295, because when I could boot it, it displayed in the settings 2 SIM card slots..Weird..
Click to expand...
Click to collapse
Weird... So it booted after all? No bootloop?
proudlytm said:
That's what I meant. Did it boot after you put your battery back?
Click to expand...
Click to collapse
Yes, But There was not buttons
proudlytm said:
Weird... So it booted after all? No bootloop?
Click to expand...
Click to collapse
Nothing..It's still stuck at the TWRP...I'm using the TWRP what you recommended (recovery.img, flashify, flash, done)
It think it's the problem...
So..Yeah, no bootloop
ValenBe said:
Yes, But There was not buttons
Click to expand...
Click to collapse
Wait, what did you download? You can clearly see that in the bottom build.prop file the soft keys are enabled.
LimePanda said:
Nothing..It's still stuck at the TWRP...I'm using the TWRP what you recommended (recovery.img, flashify, flash, done)
It think it's the problem...
So..Yeah, no bootloop
Click to expand...
Click to collapse
Uh..Not clarification.*Certification
LimePanda said:
Nothing..It's still stuck at the TWRP...I'm using the TWRP what you recommended (recovery.img, flashify, flash, done)
It think it's the problem...
So..Yeah, no bootloop
Click to expand...
Click to collapse
I will give you aboot and recovery img after 15 minutes (the ones I use)
proudlytm said:
I will give you aboot and recovery img after 15 minutes (the ones I use)
Click to expand...
Click to collapse
It would be good Thank you!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
LimePanda said:
It would be good Thank you!
Click to expand...
Click to collapse
I think it's my 10th post so I can post links
Just to write something about the ROM:
I really love it..It's very cool.
Yep. I'm not able to boot my phone, but when I was, it was so cool
Thank you guys for your hard work
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
LimePanda said:
It would be good Thank you!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I think it's my 10th post so I can post links
Just to write something about the ROM:
I really love it..It's very cool.
Yep. I'm not able to boot my phone, but when I was, it was so cool
Thank you guys for your hard work
Click to expand...
Click to collapse
No it's the 9th
proudlytm said:
Wait, what did you download? You can clearly see that in the bottom build.prop file the soft keys are enabled.
Click to expand...
Click to collapse
Sorry i dont know what are you talking about, but now i have restored a backup. I can tell you what a i saw. The virtual buttons were gonne. When i connected my phone to my PC it did not show. I can reinstall it in like 5 or 6 hours, If you tell me what to do i would like to help
This is an adaptation of @ottmi's work to OmniROM (64bit). Feature-wise it is not as rich as LineageOS, but it is an open source friendly project.
Credits go to @ottmi (obviously!), @arvinquilao (for the omnirom seed device tree, my starting point), @lolmaxlik_ru (for the 32bit device tree I used when trying 32bit) and @dev_harsh1998 (Bluetooth loop fix).
The kernel is based on CAF kernel, with changes for the Trunk from @ottmi's kernel. Kernel source is here:
https://github.com/omnirom/android_kernel_elephone_msm8916
I think it's usable: essential features seem to work. A minor issue is long press for home button, which does not work as expected.
I managed to upload on xda the build now. Bluetooth has been fixed.
The OmniROM team has accepted trunk as an official device. So, you can download the ROM directly from OmniROM website:
http://dl.omnirom.org/trunk/
If you do so, you will be able to receive ROM updates (weekly).
You are welcome to report any problem!
XDA:DevDB Information
OmniROM 7.1.2 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
siljaer, ottmi, arvinquilao, lolmaxlik_ru, dev_harsh1998
Source Code: https://github.com/omnirom/android_device_elephone_trunk
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: OmniROM
Version Information
Status: Snapshot
Created 2017-05-25
Last Updated 2017-12-14
Reserved
Reserved
Changelog
20171021: update kernel to LA.BR.1.2.9-03710-8x16.0. Security fixes (Blueborne and KRACK).
20170820: New GPS blobs from crackling. In my case, it resulted in improved GPS precision. People with overheating problem, please let me know if it improves the issue.
20170730: New Thermal blobs from crackling. New thermal engine configuration. Hopefully, that should prevent overheating.
20170709: New GPU blobs from crackling. Because of a case of reported overheating, several drivers were added in kernel config. Some related SELinux denials were addressed. Something strange was also found in Trunk's DTs: GPIO pins for the tps65132 were wrong, leading to failed driver probe (however, that happens in stock rom too). Correct values for them was added. However, real effectiveness for those changes in preventing overheating is to be proved.
20170618: Fixed reboot to recovery (and automatic updates). Using again Trunk's Camera HAL.
20170603: now compatible with 64bit opengapps, fixed start recording sound at beginning of video recordings, SELinux fixes (by @ottmi), long press of home key now shows recent apps.
20170529: update kernel to LA.BR.1.2.9-02910-8x16.0
20170526: first build
@siljaer
Happy for your new job I'll let you know my impression after installing and testing it. I am currently using the "aicp_peach_n-12.1-NIGHTLY-20170526.zip" rom with great efficiency with up-to-date OTA updates at the same time as the Open Gapps update. It's just 32bit and has been made for "ARK Benefit A3" and not for our Elephone Trunk. It would be interesting, for the many extra functions of this rom, its fluency, the OTA updates, to recover all that has good and transfer it to your rom, even that I saw that something you used as a contribution from "lolmaxlik_ru". In any case thank you for your work and I apologize if I have been able to give you that imput.
Hi siljaer, I would like to test your ROM. I'm using ottmi's ROM but I have some problems: i.e. focus problem on the camera, camera works only for photo and non for videos, sometimes I have random reboots.... So I would like to try: which TWRP should I use? may I use gapps? what are the wipes that I need: can you describe me a sequence? TKS
ve66 said:
Hi siljaer, I would like to test your ROM. I'm using ottmi's ROM but I have some problems: i.e. focus problem on the camera, camera works only for photo and non for videos, sometimes I have random reboots.... So I would like to try: which TWRP should I use? may I use gapps? what are the wipes that I need: can you describe me a sequence? TKS
Click to expand...
Click to collapse
Sorry for the delay. You can use the same TWRP you're using now. The sequence is exactly the same one described by @ottmi for his rom. And you can use gapps, 64bit. Your feedback will be very appreciated!
As for the wipes, I am afraid that you have to wipe everything except internal sd card For later flashings, you don't have to wipe anything.
First time boot takes several minutes, wait some time.
Thanks!
opengapps 64/32 bit!
siljaer said:
And you can use gapps, 64bit. Your feedback will be very appreciated!
Click to expand...
Click to collapse
Actually there's a problem and you can only flash 32 bit gapps. I have fixed this and I am uploading the build later.
siljaer said:
Actually there's a problem and you can only flash 32 bit gapps. I have fixed this and I am uploading the build later.
Click to expand...
Click to collapse
I uploaded the fixed build. Now you can install 64bit opengapps. Since the previous builds were 64bit but they used zygote32 (a mistake) I deleted them.
siljaer said:
I uploaded the fixed build. Now you can install 64bit opengapps. Since the previous builds were 64bit but they used zygote32 (a mistake) I deleted them.
Click to expand...
Click to collapse
Ok, now I will download this new build. Tomorrow I think to install and then I'll send U my feedback
Inviato dal mio trunk utilizzando Tapatalk
OMS/Substratum working
BTW, for those interested in theme engines, I have tested Substratum and it works without root.
ve66 said:
Ok, now I will download this new build. Tomorrow I think to install and then I'll send U my feedback
Inviato dal mio trunk utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks!
siljaer said:
Thanks!
Click to expand...
Click to collapse
Ok, my feedback:
I wiped cache, dalvik, data and system, then I flashed the ROM and after I flashed the gapps. After reboot I didn't reach to configure the telephone: it appeared me this message "L'app Configurazione guidata si è interrotta" and there isn't a way to configure the telephone. I'm writing from the PC 'cause the phone is out of service. I see the BT icon opened on the right-top of the screen, I don't know if this can help (you told you had problems with BT....). What do you suggest me to do?
EDIT: I flashed the ROM once again without Gapps, I did it two times but without any success, I also had a couple of random reboots
ve66 said:
Ok, my feedback:
I wiped cache, dalvik, data and system, then I flashed the ROM and after I flashed the gapps. After reboot I didn't reach to configure the telephone: it appeared me this message "L'app Configurazione guidata si è interrotta" and there isn't a way to configure the telephone. I'm writing from the PC 'cause the phone is out of service. I see the BT icon opened on the right-top of the screen, I don't know if this can help (you told you had problems with BT....). What do you suggest me to do?
EDIT: I flashed the ROM once again without Gapps, I did it two times but without any success, I also had a couple of random reboots
Click to expand...
Click to collapse
What do you mean with "without any success?"
siljaer said:
What do you mean with "without any success?"
Click to expand...
Click to collapse
I had to power off. I want to say that to make my telephone works I had to reinstall otttmi's ROM. In fact, also if i did a backup just after flashing your ROM, it was impossible to reload the backup. I think it's because - wiping all cache, dalvik, data and system - I deleted also parts that could contain parts of the backup. I reached to have some screenshot, tomorrow I'll post here
This is what happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Inviato dal mio trunk utilizzando Tapatalk
ve66 said:
I had to power off. I want to say that to make my telephone works I had to reinstall otttmi's ROM. In fact, also if i did a backup just after flashing your ROM, it was impossible to reload the backup. I think it's because - wiping all cache, dalvik, data and system - I deleted also parts that could contain parts of the backup. I reached to have some screenshot, tomorrow I'll post here
Click to expand...
Click to collapse
When did you do a backup? Did you backup your data online? From the screenshot, it looks like the restore application failed.
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
Bizen-Ya said:
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
Click to expand...
Click to collapse
Ok i have reformated my /data from f2fs to ext4, it's ok now.
Bizen-Ya said:
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
Ok i have reformated my /data from f2fs to ext4, it's ok now.
Click to expand...
Click to collapse
Yes, f2fs is not enabled. I don't know enough about its reliability with CAF kernel.
gapps and camera
siljaer said:
Yes, f2fs is not enabled. I don't know enough about its reliability with CAF kernel.
Click to expand...
Click to collapse
BTW, if you're installing gapps I would suggest a flavour that does not replace default applications. Otherwise you will lose Snapdragon Camera that in my opinion is much better than google (legacy, as we use an old HAL) camera.
@ siljaer
Tried the ROM using TWRP-3.0.2-20161108-trunk.img, without installing gapps as recommended. Pretty fluid without breaks and quite complete without so many customizations. Problems with Smart Launcher does not activate the home key for shutdown or recovery commands. Weekly update to switch to version 20170611 all OK download but failed restart for flash with recovery. Tried several times but nothing to do. Obviously using either Launcher 3 or OmniSwitch. Installed TWRP manual and all OK. By the way, with the first installation I installed Supersu, which I did not find after updating. This is my first impression.
CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
DOWNLOAD Official
DOWNLOAD oos camera
Kernel source:
Source
Selinux Status:
Enforcing
MAJOR BUGS:
VoWifi
flash on your own risk.
FLASHING
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE SUPPORTED by US, But flash what you want)
reboot (if you still have trouble with understanding a/b just repeat whole procedure once again).
If phone doesnt boot format userdata.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
OOS camera work with portrait mode, 60fps, all 3 cams, etc.
Android auto works fine.
If you dont mess with magisk, rom will always pass safety net out of the box.
Device Maintainers
@vache, @darkobas,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: [url]https://github.com/omnirom/[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.5.11
Version Information
Status: Stable
Created 2019-07-19
Last Updated 2019-07-28
reserved
nice!
any plans to support 5g variant?
Nekromantik said:
nice!
any plans to support 5g variant?
Click to expand...
Click to collapse
probably not before q..... even then we would need a experienced tester if we wanted to make things work as no1 in team has a 5g. dunno even what the current issues with it are
group
Is there a telegram group?
Yes! Thank you! Hopefully will have time to flash today.
darkobas said:
probably not before q..... even then we would need a experienced tester if we wanted to make things work as no1 in team has a 5g. dunno even what the current issues with it are
Click to expand...
Click to collapse
The hardware is identical apart from Modem so things like vendor and modem files will be different.
I flashed AOSiP with 5g supported kernel and it boots and camera bluetooth etc works. Just no SIM detected.
Before people ask yes when it boots up it is on 60 fps mode. To change go to settings --> omni gears---> display modes and put it on 3120x1440 90.0000. The 1080p mode seems to break fingerprint and gives you a weird screen off animation.
---------- Post added at 02:39 PM ---------- Previous post was at 02:38 PM ----------
joemossjr said:
Before people ask yes when it boots up it is on 60 fps mode. To change go to settings --> omni gears---> display modes and put it on 3120x1440 90.0000. The 1080p mode seems to break fingerprint and gives you a weird screen off animation.
Click to expand...
Click to collapse
Edit. Also fingerprint seemed to be pretty hard to setup. Had to press pretty hard to get it to recognise. Works fine now.
Rom working well so far! 90hz initially wasn't working but switching to 60hz then back to 90hz fixed it for me. I can't seem to get UnifiedNlp working with MicroG though. I already removed com.qualcomm.location as the NanoDroid wiki says it could conflict, but to no avail. Could it maybe be that the rom doesn't look for com.google.android.gms as a location provider?
gigatex said:
Rom working well so far! 90hz initially wasn't working but switching to 60hz then back to 90hz fixed it for me. I can't seem to get UnifiedNlp working with MicroG though. I already removed com.qualcomm.location as the NanoDroid wiki says it could conflict, but to no avail. Could it maybe be that the rom doesn't look for com.google.android.gms as a location provider?
Click to expand...
Click to collapse
Just dont remove qcom location and location will work fine
Love the ability for custom fingerprint Icons
joemossjr said:
Love the ability for custom fingerprint Icons
Click to expand...
Click to collapse
If anyone's wants some hit me up and I'll see what I can do
joemossjr said:
If anyone's wants some hit me up and I'll see what I can do
Click to expand...
Click to collapse
Could you create a zip of them all and make a theme post for it? Or drop it here since i think this is the only rom right now with custom icon ability.
So if coming from another ROM do we format data boot back to TWRP wipe but don't wipe internal, system are vender then flash ROM bla bla bla done ?
Hunter3U said:
Could you create a zip of them all and make a theme post for it? Or drop it here since i think this is the only rom right now with custom icon ability.
Click to expand...
Click to collapse
You can find some files here : https://t.me/s/OP_fps
Here's a zip of ones I made
I m on 9.5.10 with magisk and unlocked bootloader..what should be flashing method?should I go with method said in op( oos-omni-reboot to b/l-twrp-oos-omni method)or any other method?
punit1708 said:
I m on 9.5.10 with magisk and unlocked bootloader..what should be flashing method?should I go with method said in op( oos-omni-reboot to b/l-twrp-oos-omni method)or any other method?
Click to expand...
Click to collapse
I used the same method as op6 and op7pro in previous roms works perfectly and I formatted data prior and same wipe method as previous roms
joemossjr said:
Here's a zip of ones I made
Click to expand...
Click to collapse
How to use the zip. I am on OOS renovate rom
Edit.. Found it
Dbj.Dhaval said:
How to use the zip. I am on OOS renovate rom
Click to expand...
Click to collapse
Try using same method as you woruld with other real roms not gsi mess search xda read up one post
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps. The device tree is heavily based off of sumire's lineage 18.1 device tree with only the device specific modifications required for Satsuki (Z5 Premium).
Download:
Android File Host: ROM | 79d9c9ef9ac3a30d92b4fcea3dd7bd17
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-18.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- A few camera related issues (laggy front cam recording and qr code)
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Kernel
Device Tree (Satsuki | kitakami-common)
XDA:DevDB Information
LineageOS 18.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220120
Beta Release Date: 2020-12-27
Created 2020-12-13
Last Updated 2022-01-20
Change-logs:
20220120:
- Upstream lineage 18.1 sources.
- December security patches.
- New camera wrapper ported from chippa's loire device tree. (Camera issues still exist however unfortunately)
Spoiler: Old change-logs
20210811:
- Upstream lineage 18.1 sources.
- August security patches.
- Updated sdcardfs (may fix Play store app with .OBB installation issues)
20210614:
- Upstream lineage 18.1 sources.
- May security patches.
- LiveDisplay is now fixed.
- FM Radio is back.
20210414:
- Upstream lineage 18.1 sources.
- April security patches.
- WiFi mac address and tethering fixes.
- Switch to AOSP finger print HAL 2.1
- Fixes "failed to find /misc partition" when trying to reboot to recovery.
20201213
- Initial Release
20201227
- Updated to lineage 18.1 sources.
Been waiting , thanks bro Gonna test it later.
I'm on lineage os 17.1 so I can just factory reset and wipe data and install this Rom
Thx Joel. anything can br done about signing keys to prevent security error?
Absolutely beautiful, thanks for continuing to support the z5 premium. You're the only dev left.
One thing I would change is I would rather not have the ROM force the LineageOS recovery on us. I'd much rather have TWRP (Also thanks to you for developing, and if you have the time to update it to TWRP 3.4.0 that'd be great)
Stuck on Booting, infinite Booting on E6883
Volmond said:
Stuck on Booting, infinite Booting on E6883
Click to expand...
Click to collapse
Did you wipe dalvik/ART, Cache, System, and Data before flashing the rom?
Volmond said:
Stuck on Booting, infinite Booting on E6883
Click to expand...
Click to collapse
Just to be sure this is a bootloop? The phone isn't stuck on the white Sony splash screen? Can anyone else with an E6883 device confirm that if this is happening? I only own the E6853 variant.
Also @HouseOfBricks I will look into getting TWRP updated at some point. Also I believe in the setup it asks if you wish to use lineage's recovery or not.
Joel16 said:
Just to be sure this is a bootloop? The phone isn't stuck on the white Sony splash screen? Can anyone else with an E6883 device confirm that if this is happening? I only own the E6853 variant.
Click to expand...
Click to collapse
I'm running on an E6833, and it works totally fine. Realistically those two variants are exactly the same, with the only difference between the E6883 and E6833 being the LTE bands.
Joel16 said:
Also @HouseOfBricks I will look into getting TWRP updated at some point. Also I believe in the setup it asks if you wish to use lineage's recovery or not.
Click to expand...
Click to collapse
Yeah, I just looked into it! My bad, I think I was just too excited to focus when installing
EDIT: Also Just wanted to let you know that I linked this post on the XDA Android 11 Custom Roms list, I hope you don't mind
Volmond said:
Stuck on Booting, infinite Booting on E6883
Click to expand...
Click to collapse
I have an E6833 and was on 15.1. I have tried to load 17.1 a couple times with no success, but I was able to get 18.0 just fine. The stuck on a boot loop issue is what I had when trying to load 17.1, so maybe try to install 15.1 and see if you can get that to work.
New Release 20201227
Change-log:
- Updated to lineage 18.1 sources.
Another thing I noticed is that the snap camera isn't as bugged as it was in the previous 18.0 release. This release seems more towards the "stable" side of things for me although I didn't extensively test it (do let me know if you come across any issues). I'll wait for reports of any other issues before marking it as stable. Lineage also hasn't started rolling any official builds for 18.X either, so I would like to wait on that as well.
Download:
604.82 MB file on MEGA
mega.nz
Great.
Keyboard disappears instantly in one of my bank account apps.
so i can't enter numbers.
And Hotspot doesn't seem to work.
Also some apps that are root granted can not do superuser operations.
like copying a file into Android/OBB with ES File Explorer.
error 1 :/
hi!
my headphone jack is broken so i have to use sound switcher apps lesser audioswitch but android 11 does not support these apps
is there any apps that android 11 support?
HI dear joel16
Thanks for your hard work
I want to say, please zoom in one ROM,
You are working currently on 4 ROM,
and bugs of all 4 ROMS are same each other,
Fm radio and camera
But in this version, 18,1, also advanced restart option don't work,
And other third party camera apps don't have original camera quality,
Once again, thank you for your hard work,
You are only dev in xda who support Xperia z5 premium
I have been testing this rom, phone(6833)
-wifi seems to work better than 17.1
-Spanish language is not 100% translate
-camera works but is not very good, camera17.1 is better(quality in the photos)
-sim1 wokrs(calls,sms,etc)
-sim2 is detected but does not works, when making a call (network not available)
-Apparently the phone does not go completely into sleep state
-its temperature rises quickly in moderate use
-sometimes the battery drains quickly
that's all so far
Hi, THX for your Grest work, rom Is good but Is not yet complete, Do you update It again in future?
jcgc28 said:
I have been testing this rom, phone(6833)
-wifi seems to work better than 17.1
-Spanish language is not 100% translate
-camera works but is not very good, camera17.1 is better(quality in the photos)
-sim1 wokrs(calls,sms,etc)
-sim2 is detected but does not works, when making a call (network not available)
-Apparently the phone does not go completely into sleep state
-its temperature rises quickly in moderate use
-sometimes the battery drains quickly
that's all so far
Click to expand...
Click to collapse
Hey.
Did you had problems with chrome?
It will freeze after a min of using it.
It was the same with other browsers based on chrome.
Only firefox was working good.
I test yandex browser and it was buggy to.
Ps:i never tried without flashing gapps.
Omidbabadi11 said:
Hey.
Did you had problems with chrome?
It will freeze after a min of using it.
It was the same with other browsers based on chrome.
Only firefox was working good.
I test yandex browser and it was buggy to.
Ps:i never tried without flashing gapps.
Click to expand...
Click to collapse
chrome and mozilla work fine, I installed gapps (android 11) and they work fine, unfortunately the phone can suffer a lot with this rom
jcgc28 said:
chrome and mozilla work fine, I installed gapps (android 11) and they work fine, unfortunately the phone can suffer a lot with this rom
Click to expand...
Click to collapse
I installed nikgapps an flame gapps and both was same.
I I guess most issues are because of s810 it self