Please don't buy the OnePlus 7 Pro 5G (model numbers being GM1920 and GM1925). If you need 5G, get the OnePlus 7T Pro 5G McLaren Edition. If you have gotten this phone and can return it, please do so and get the normal OnePlus 7 Pro under the model numbers GM1910, GM1911, GM1913, GM1915 and GM1917. (The GM1915 which is the T-Mobile 7 Pro can be converted to the GM1917 international firmware for dual sim and faster updates)
If you already have the phone though and can't return it, it's not the end of the world. There are still things you can do on it!
So, what is the OnePlus 7 Pro 5G?
The OnePlus 7 Pro 5G was a carrier device. It was released on 3 carriers, Sprint (USA), EE and Elisa (EU). It is basically identical to the standard 7 Pro albeit with a different OxygenOS build path (GM27BA and GM25CC). Also, Sprint's 5G is now dead so that leaves EE and Elisa with working 5G.
Info about the Sprint OnePlus 7 Pro 5G and XDA thread on how to convert to the EU 5G firmware
It's very likely that as I'm updating this, the phone will now be EOL.
If you're on the Sprint firmware of the OnePlus 7 Pro 5G, you can update to the latest available release, the July 2022 OOS 10.0.15 patch. Oxygen Updater won't work obviously since it's carrier firmware. There is an easy fix, although you'll lose a couple of features (Dolby Atmos Equalizer, the About page in the phone is broken (can be fixed) and some other minor things) which is converting to EU firmware. If you are going to convert, read the entire thread and make a backup. It will wipe the device. Do note with this conversion, you'll be on a less bloated OxygenOS 10, but at the cost of an older (November 2021) security patch. The links to said threads can be found below.
To convert to the EU 5G firmware, click on me
If you want to return to the Sprint firmware, click on me
If you want to unlock the bootloader on the Sprint firmware, click on me
Why can't you convert to international firmware?
There are actually a couple of reasons. The main 2 are that the kernel is incompatible and the added X50 5G modem. I've tried to convert via any method I could, fastboot, MSM, etc. Fastboot let me flash all the .img files (that I payload dumped) but it didn't even show a splash, MSMTool just said param preload, and TWRP didn't even let me flash the OTA zip.
OFFICIALLY THE DEVICE DOESN'T HAVE ANDROID 11 OOS 11, NOR WILL IT GET ANDROID 12 OOS 12.1
As of a couple of months ago (March 2022), I did actually get OxygenOS 11 booted on the 7 Pro 5G (images can be found in the 7 Pro 5G Telegram). It has a broken modem, auto-rotation, and some other things and is identified as the IN2020 which is the OnePlus 8 Pro 5G in China. It's not worth flashing as we have Android 12.1 and 13 custom ROMs, but more on that is below.
What about some custom ROMs?
We have official YAAP! We bought a kernel developer (John Galt) the OnePlus 7 Pro 5G!
As of March 31st, we have an official YAAP build in the 7 Pro 5G Telegram. Everything is working. GPS, sim (single though), modem, etc. It'll be in YAAP group/commons channel (https://t.me/yaapop7, https://t.me/yaapupdates), or just join the 7Pro 5G Telegram chat (link found below) and scroll up a bit in the group, or ask.
^ We also had KOSP but that's EOL now on May 2022 security patch. Flamingo (the replacement for KOSP) is still unknown.
This method is outdated
As of March 2nd, 2022, it is now possible to boot custom ROMs based on Android 12 from the 7 Pro on the 7 Pro 5G. We have a list of fixes and such in the OP7P5G Telegram (this method is a little hacky)
broken actual GPS (works fine with WiFi scanning, etc)
sim is a little hacky on GM1920
some misc bugs
GSIs also work, albeit with some issues
Issues I found on phh treble
When will we get Android 11/OxygenOS 11 or Android 12/OxygenOS 12?
Well, we won't. That's about it.
What about Magisk modules?
Yes! These are working. If you're rooted, most Magisk modules should be working fine. There are special RiCE builds for the latest OOS 10 firmware for the EU 5G firmware for this device in their Telegram, so just ask or search there. Magisk modules on custom ROMs also work fine, as you're using AOSP rather than OxygenOS.
What about dual sim?
If you need dual sim, then it's best you move on from this device. It is very unlikely that the device will ever get it, but there were some small breakthroughs to try to get it working on the device.
dsdv working on A12 ROMs with modded EFS and modem. On stock nothing yet. dsds worked for 1 reboot for me before it stopped working, not sure why it's not working
^ Do note this info is outdated since I'm not caught up in dual sim support on the 7 Pro 5G. (This info was last updated in March 2022)
Additional Info and Edits
If you have any more questions about the phone, leave them down below, or message me in the Telegram group, and I'll try to answer them.
Telegram Group is dedicated to the GM1920 and GM1925 (OnePlus 7 Pro 5G). This channel isn't that active but has some discussion about the device and has guides and such for installing custom ROMs, converting to EU 5G, etc.
Thanks for the mention XDA!
Unfortunately, the Reddit link has died. Join the OnePlus 7 series YAAP group, or the OnePlus 7 series commons group on Telegram and it shouldn't be hard to join from there.
Can you tell what didn't work with LOS 18.1?
Also, I'm thinking appt replacing my 1925 with live of the other models, but came find a reliable horde to the difference between 1910, 1911, 1915, etc. Any suggestions?
Cheers
B2Pi said:
Can you tell what didn't work with LOS 18.1?
Also, I'm thinking appt replacing my 1925 with live of the other models, but came find a reliable horde to the difference between 1910, 1911, 1915, etc. Any suggestions?
Cheers
Click to expand...
Click to collapse
On the actual rom itself (from Lineage website) everything worked but location, modem and auto rotation. Couldn't get modem to work so I defaulted back to OOS 10.
On the GSI it booted but after setting 1440p90hz, brightness broke and I had to tick the alternative brightness scale in phh settings. Fingerprint, alert slider and popup are broken out of the box but I think fingerprint might be able to get fixed with a overlay. WARP might also be broken but I didn't test that. GSIs are really not meant for daily and I don't recommend you daily them as even battery is worse on AOSP GSIs. I didn't daily this GSI as I was mass testing them at 2 am in the morning on Telegram
The main difference between the GM1920/25 vs the GM1910/11/13/15/17 is the modem, and partition scheme. They're otherwise identical, but these 2 changes make it so that there's no international version to flash. I would personally sell your GM1925 and get a T-Mobile GM1915, convert to international, and have at it with custom roms.
adriantechguy said:
On the actual rom itself (from Lineage website) everything worked but location, modem and auto rotation. Couldn't get modem to work so I defaulted back to OOS 10.
On the GSI it booted but after setting 1440p90hz, brightness broke and I had to tick the alternative brightness scale in phh settings. Fingerprint, alert slider and popup are broken out of the box but I think fingerprint might be able to get fixed with a overlay. WARP might also be broken but I didn't test that. GSIs are really not meant for daily and I don't recommend you daily them as even battery is worse on AOSP GSIs. I didn't daily this GSI as I was mass testing them at 2 am in the morning on Telegram
The main difference between the GM1920/25 vs the GM1910/11/13/15/17 is the modem, and partition scheme. They're otherwise identical, but these 2 changes make it so that there's no international version to flash. I would personally sell your GM1925 and get a T-Mobile GM1915, convert to international, and have at it with custom roms.
Click to expand...
Click to collapse
Ok! And now I have a plan. Unfortunately, said plan does nothing wrt resolving my anger and disgust with tmobile/sprint...
BIG NEWS!!!!!
Telegram
t.me
PE WORKS THANKS TO JOE COWBOY, requires a lot of work to get booted and modem working but it works!!! Rotation wonky though
YAAP BOOTED
Same methods as PE but I had to pull boot.img with Dora installed since GulchR dumps on 7P5G
{
"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"
}
YAAP guacamoles builds are out and posted in the 7P5G Telegram. Official YAAP soon, DT and vendor on YAAP GitHub.
Just installed YAAP 12 test build 2 for GM1925, works pretty well.
Awesome!
Hello OP,
Only development thread is granted with Telegram group link, while this thread is not. So I remove the link.
Thanks for understanding.
Will they make a publication on how to install YAAP on Sprit GM1925?
I installed YAAP on the GM1920 model yesterday. Fingerprint scanner can be a bit of a hit or miss otherwise everything works as it should. Gonna give Pixel Experience a try on it at some point
Good afternoon.
To my country, brought a lot of OnePlus 7 pro gm1925 Sprint 8/256. Selling at a very low price, about $200. It was checked from the menu that they are all locked on sprint, for 1 SIM card, there are no native SIMs in the kit. I correctly understood that at the moment there is no procedure for the full use of the smartphone?
Or how can it be flashed so that this phone fully begins to function (calls, Internet, social networks, games, wireless Internet, navigation), a full-fledged smartphone, as well as not blocked? I have little experience in unlocking firmware for Samsung, Xiaomi, HTC smartphones.
Not a complete newbie, but after reading the threads of the forums I did not understand whether this is real. Some write that we get a cyclic reboot, others write that on the YAAP firmware it works fine.
Thanks for the answer and help.
Andrey*T said:
Good afternoon.
To my country, brought a lot of OnePlus 7 pro gm1925 Sprint 8/256. Selling at a very low price, about $200. It was checked from the menu that they are all locked on sprint, for 1 SIM card, there are no native SIMs in the kit. I correctly understood that at the moment there is no procedure for the full use of the smartphone?
Or how can it be flashed so that this phone fully begins to function (calls, Internet, social networks, games, wireless Internet, navigation), a full-fledged smartphone, as well as not blocked? I have little experience in unlocking firmware for Samsung, Xiaomi, HTC smartphones.
Not a complete newbie, but after reading the threads of the forums I did not understand whether this is real. Some write that we get a cyclic reboot, others write that on the YAAP firmware it works fine.
Thanks for the answer and help.
Click to expand...
Click to collapse
If the device is locked to Sprint, your only course of action is to contact Sprint and have them unlock it for you, although the success rate is pretty low from what I've read. You can still use the device for gaming, social media, etc, just not for anything cellular-related if it's locked/blacklisted. YAAP and KOSP are well and alive (Android 12.1) booting on this device. I have made previous posts in the past about this device but those aren't updated anymore, whereas this one and the Reddit thread linked are.
I got a gm1925 but yaaps has encryption that really admire. While my TMobile is unencrypted now wit oxygenOS12 I figured out yaaps in a few hours how to unencrypt it for.. I don't know mods twrp me being a user that breaks things. Anyways here's my boot.img a dtbo and vbmeta to dipper up. Just fla**** "boot.img"one a yaap13 you have encrypted, wipe and reboot. It's got the yaap-stock so if you want flash twrp. Here's ware it gets real. Checkout DFE-NEO. Yaaps13 in nicly done _sysencrypt and boot encrypted with a double minded kernel. So no orangefox dual booting but flash DFE-AFTER EVERY TIME YOU MOD THE MODE And do it in the name(selection of NEO) anyways I got TWRP no encrypt. Try it out. Litterly to began is tricky so take the boot.img or flash/wipe in magisk DFE-NEO UNENCRYPT. On any OS out their. Also a dual boot apps to help out swappen omg files if your like me.
Related
Hello XDA Community,
OnePlus is now pushing the incremental rollout of OxygenOS 10.0.4 for the OnePlus 7T Pro.
Changelog
Code:
System
* Optimized standby power consumption
* Improved system stability and general bug fixes
* Updated Android security patch to 2019.10
* Fixed the black bar issue while charging or playing a video
* Optimized the Bluetooth connectivity in automobiles
* Optimized the expanded screenshot feature
We appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum bug report forums.
Please use this thread to discuss all the bugs and possible solutions/workarounds with the community.
Do try out the new Feedback tool, it is now much easier and simpler for our community to report bugs and share feedback with us. If you have any questions or need help, please contact [email protected]
{
"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"
}
As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days. Your feedback is appreciated. I may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously.
This OTA will have a staged rollout, the OTA will be received by a limited number of users today and will have a broader rollout in a few days after making sure there are no critical bugs,
Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. I hope you enjoy and let us know how you feel about the update in the comments below.
Never Settle :good:
Funk Wizard :highfive:
XDA:DevDB Information
[Discussion & Feedback] OxygenOS 10.0.4 for OnePlus 7T Pro, ROM for the OnePlus 7T Pro
Contributors
Funk Wizard
ROM OS Version: Android 10
Version Information
Status: Stable
Current Stable Version: 10.0.4
Stable Release Date: 2019-11-14
Created 2019-11-18
Last Updated 2019-11-18
Feedback whether good or bad is extremely important to Me and OnePlus, as it is only on the receipt of such information, OnePlus can assess and improve on the software experience, so please don't shy away from sharing your experience.
I always recommend to take backup before you proceed or flash a new build. If this is your primary device you should have everything backed up before you start.
What OnePlus has achieved today is mainly because of its active community and early supporters and OP would like to keep it that way and maintain its focus on the community while building the software to enhance the user experience.
Thank you for your continued feedback and support.
Never Settle
Funk Wizard
OnePlus 7T Pro (Hotdog) Device ID & Build Tags
HD1911 Device - HD01AA (IN Build)
HD1913 Device - HD01BA (EU Build)
HD1917 Device - HD01AA (Global build)
Credits: @Some_Random_Username
Downloads:
HD1911 Device - HD01AA (IN Build)
OxygenOS 10.0.4 Full Zip
Official
MD5: 8e5325b0f828a8291a98cee7879b6e7e
OxygenOS 10.0.3 Full Rom
Official
MD5: 66b5314862dd366d5dddafc82f317945
HD1917 Device - HD01AA (Global build)
OxygenOS 10.0.4 Full Rom
Official
MD5: 13473B506670244A65B8E21B07CBF245
HD1913 Device - HD01BA (EU Build)
OxygenOS 10.0.4 Full Rom
Official
MD5: 8155a9e2a740581eca686c49b16b1d4e
Flashing Instructions
Download the necessary files from the post above and follow as below:
1. Download the Full Zip from the above link and move it from the Download folder to the root of your internal storage.
2. Navigate to Settings > System Update > Settings > Local upgrade > Select latest OOS Zip
3. Flash the Zip
4. Upon Successful Flash Reboot to Recovery manually and Wipe Cache for better performance.
5. Reboot System and Profit :good:
Device will reboot and your OnePlus 7T Pro is now running on the latest OxygenOS Firmware & OS based on Android 10
When will OnePlus actually out the 7T Pro ROMs on their website like the other OnePlus devices?
Device was released a month ago...
Sent from my OnePlus7TPro using XDA Labs
@Funk Wizard posting that here as I believe it is useful information:
In the same way as 7-series, OnePlus 7T Pro has different builds based on region. Note that however there isn't two builds this time but rather three.
HD01BA: European build: default build running on HD1913 device
HD01AA: Indian build (ro.build.version.ota line in build.prop contains letter I and filename of update zips does as well): default build running on HD1911 device
HD01AA: International build (ro.build.version.ota line in build.prop contains letter O and filename of update zips does as well): default build running on HD1917 device
Also please find for post 3 the following download links, md5sums and mirrors of 10.0.4 build (that I posted on my mirror thread)
HD01AA International: https://otafsg1.h2os.com/patch/amaz...O.08_OTA_008_all_1911061838_9862571d67cf8.zip
Mirror: https://androidfilehost.com/?fid=4349826312261632755
MD5: 13473B506670244A65B8E21B07CBF245
HD01BA Europe:
https://otafsg1.h2os.com/patch/amaz...n_14.E.08_OTA_008_all_1911061839_d196e40d.zip
Mirror: https://androidfilehost.com/?fid=4349826312261635128
MD5: 8155a9e2a740581eca686c49b16b1d4e
Okay, first of all hey funk! Reporting for duty with my new McLaren. Phone feels great. Loving it. I just have one issue at the moment with the app locker. It's glitched I think. Any more than two locked apps at the time and the rest won't lock, in the recents menu at least. They just open as if they're unlocked and they act glitched. Most evident with photos and OnePlus gallery.
Also when the backlight goes out the wallpaper appears a bit off
Nice to see you here @Funky Wizard
Some_Random_Username said:
@Funk Wizard posting that here as I believe it is useful information:
In the same way as 7-series, OnePlus 7T Pro has different builds based on region. Note that however there isn't two builds this time but rather three.
HD01BA: European build: default build running on HD1913 device
HD01AA: Indian build (ro.build.version.ota line in build.prop contains letter I and filename of update zips does as well): default build running on HD1911 device
HD01AA: International build (ro.build.version.ota line in build.prop contains letter O and filename of update zips does as well): default build running on HD1917 device
Also please find for post 3 the following download links, md5sums and mirrors of 10.0.4 build (that I posted on my mirror thread)
HD01AA International: https://otafsg1.h2os.com/patch/amaz...O.08_OTA_008_all_1911061838_9862571d67cf8.zip
Mirror: https://androidfilehost.com/?fid=4349826312261632755
MD5: 13473B506670244A65B8E21B07CBF245
HD01BA Europe:
https://otafsg1.h2os.com/patch/amaz...n_14.E.08_OTA_008_all_1911061839_d196e40d.zip
Mirror: https://androidfilehost.com/?fid=4349826312261635128
MD5: 8155a9e2a740581eca686c49b16b1d4e
Click to expand...
Click to collapse
Thank you, buddy, as always you are spot on.
With the release of the T Series OP now has some regional specific builds for IN region and you have rightly mentioned it here and on your thread.
I shall update the info as shared on the Download Post.
Keep up the good work:highfive:
skyknife93 said:
Okay, first of all hey funk! Reporting for duty with my new McLaren. Phone feels great. Loving it. I just have one issue at the moment with the app locker. It's glitched I think. Any more than two locked apps at the time and the rest won't lock, in the recents menu at least. They just open as if they're unlocked and they act glitched. Most evident with photos and OnePlus gallery.
Also when the backlight goes out the wallpaper appears a bit off
Click to expand...
Click to collapse
I tried it on my device which is HD01AA IN version and the locker works fine as it should as I have multiple banking, social media and moderation apps locked.
Also no issue with the wall at my end. I would request you to report the issue with the feedback app along with screenshot and logs and also wait for more McLaren users to confirm the same.
Thank you once again for your feedback :good:
Sent from my OnePlus7TPro using XDA Labs
I wanted just to report that the problem with the black bars while charging is still there.
skyknife93 said:
Okay, first of all hey funk! Reporting for duty with my new McLaren. Phone feels great. Loving it. I just have one issue at the moment with the app locker. It's glitched I think. Any more than two locked apps at the time and the rest won't lock, in the recents menu at least. They just open as if they're unlocked and they act glitched. Most evident with photos and OnePlus gallery.
Also when the backlight goes out the wallpaper appears a bit off
Click to expand...
Click to collapse
Apps will be kept unlocked until the phone is locked completely. Try it out
For those who were waiting :fingers-crossed:
OxygenOS 10.0.4 for the IN Version HD1911 Device - HD01AA is now available
Uploaded the incremental on my drive.
https://drive.google.com/file/d/1-8hpnShujWSKESPFJcdXSqj5vwx9RRSX/view
MD5: 8ab8449ec529e5b39d6c3c5b423fb261
Sent from my OnePlus7TPro using XDA Labs
10.0.4 India
Battery drains faster than previous update
Edit:- is it normal?
juliusedward said:
Apps will be kept unlocked until the phone is locked completely. Try it out
Click to expand...
Click to collapse
Yeah I know that. I've used a lot of OnePlus phones (3, 5, 6T McLaren) and I know how the app locker works. I'm saying that in this one (McLaren again) the app locker is a bit faulty for me. Let me explain
I keep some apps locked in the recents menu (the lock that makes them stay in the recents and not get killed) and as usual, I also lock a lot of apps with the app locker (banking, Messengers, gallery and photos etc)
The glitch is that sometimes, when I access the recents menu (after I unlock the phone not the app which is still locked) and tap on the app, instead of the usual unlock screen I'm greeted with how I left app before I switched (the last image I was looking at or the album or some page) and the nav bar doesn't work unless I hit the home button.
I thought it was a one-time thing and swiped the app away and it worked again, but it came back after a while. This never happened in any of the earlier phones' app lockers (even 6t McLaren on beta).
I'm willing to do a full reset, but I just wanted to check if this was more than something wrong with just my phone, because setting up again is a bit cumbersome.
@funkwizard, I'm only tagging so that you can see my explanation too man. Sorry if it's not necessary. I'll also try to grab a screen recording of it happening again.
My device is HD1911 btw
Funk Wizard said:
For those who were waiting :fingers-crossed:
OxygenOS 10.0.4 for the IN Version HD1911 Device - HD01AA is now available
Uploaded the incremental on my drive.
https://drive.google.com/file/d/1-8hpnShujWSKESPFJcdXSqj5vwx9RRSX/view
MD5: 8ab8449ec529e5b39d6c3c5b423fb261
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I've got the full package with me. Will be happy to help if you'd like to add it.
arpit_nnd said:
I've got the full package with me. Will be happy to help if you'd like to add it.
Click to expand...
Click to collapse
Sure.. Please upload and share the link and MD5 :good:
Sent from my OnePlus7TPro using XDA Labs
skyknife93 said:
Yeah I know that. I've used a lot of OnePlus phones (3, 5, 6T McLaren) and I know how the app locker works. I'm saying that in this one (McLaren again) the app locker is a bit faulty for me. Let me explain
I keep some apps locked in the recents menu (the lock that makes them stay in the recents and not get killed) and as usual, I also lock a lot of apps with the app locker (banking, Messengers, gallery and photos etc)
The glitch is that sometimes, when I access the recents menu (after I unlock the phone not the app which is still locked) and tap on the app, instead of the usual unlock screen I'm greeted with how I left app before I switched (the last image I was looking at or the album or some page) and the nav bar doesn't work unless I hit the home button.
I thought it was a one-time thing and swiped the app away and it worked again, but it came back after a while. This never happened in any of the earlier phones' app lockers (even 6t McLaren on beta).
I'm willing to do a full reset, but I just wanted to check if this was more than something wrong with just my phone, because setting up again is a bit cumbersome.
@funkwizard, I'm only tagging so that you can see my explanation too man. Sorry if it's not necessary. I'll also try to grab a screen recording of it happening again.
My device is HD1911 btw
Click to expand...
Click to collapse
Yeah screen record will be fine so I can replicate the same on my device as I also have HD1911
Sent from my OnePlus7TPro using XDA Labs
yo_honey said:
Battery drains faster than previous update
Edit:- is it normal?
Click to expand...
Click to collapse
Please clear cache from recovery once and let the rom perform after a couple of battery cycles
Sent from my OnePlus7TPro using XDA Labs
Funk Wizard said:
Please clear cache from recovery once and let the rom perform after a couple of battery cycles
Click to expand...
Click to collapse
Last full charge info is incorrect after update.
{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Newest firmware available for your variant
Based On: LineageOS
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15
Removed
Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?
How can I unlock bootloader, install TWRP and LineageOS on my XT1789-04 (AT&T)?
It is a beautiful day!
Although there's no download links.
A Sad Story said:
Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?
Click to expand...
Click to collapse
I downloaded and installed and everything is ok xD
bogante said:
I downloaded and installed and everything is ok xD
Click to expand...
Click to collapse
I cant find link. In download.lineageos no build of 17. Can u share it?
A Sad Story said:
I cant find link. In download.lineageos no build of 17. Can u share it?
Click to expand...
Click to collapse
Oh man, my upload speed is 50kb/s it will take forever
Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...
Jelixis said:
Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.
Click to expand...
Click to collapse
I'm facing same issue
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...
Click to expand...
Click to collapse
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues
ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
Click to expand...
Click to collapse
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
Shreeram02 said:
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues
Click to expand...
Click to collapse
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?
ph03n!x said:
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?
Click to expand...
Click to collapse
Yea incoming calls are fine btw normal messages don't work either
Yes in los 16 everything is fine
in los 17(not 17.1)(the September 21 unofficial build) calling is working fine camera has same bugs there too tho
But if u want everything working los16 is the option
@erfanoabdi @ThE_MarD @npjohnson not sure if you had a chance to review this - while this installs in LOS17.1, does not really control efficiency mode.
However we can still see the battery % of the Incipio Mod:
https://forum.xda-developers.com/z2-play/themes/motomodbattery-service-lineageos-15-1-t3895041/
https://github.com/devilsclaw/MotoModBattery
I was looking for a way to find the mod's battery % and stumbled on this...
no signal
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal
bogante said:
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal
Click to expand...
Click to collapse
Do you see your phone's IMEI in settings > about phone? Baseband version when you tap the Android version (10) in the same screen?
Magisk manager
I update LOS 16 to this 17.1 and everything seems to work fine, no real bugs. I've installed latest 7.2 google camera port from Arnova and picture/video/selfies are great. Phone calls no problems and it's a my impression but finally loudspeaker volume is higher than previous lineage versions. Only a question, maybe someone can help me, I've lost magisk root access, is it possible to install it with a temporaney twrp as in LOS 16 or is there any other method please?
[SOLVED] Maybe could be useful for someone. I tried the pie method: I've installed Magisk zip booting (not flashing) TWRP 3.3.1-0 (the 3.3.1-1 doen't boot on my device). Everything is working fine, I don't have any glitch and now my devices is rooted too
Getting Glitches when Playing Games Like Asphalt 9 also Same Camera Focusing Problem here too.
I'm seeing glitches in the home screen/ launcher too. Happens at random, gets psychedelic when unlocking - there are wavy lines (stock LOS17.1 wallpaper) on the image that move. Screenshot does not capture this, but I can take a photo if it helps figure the problem.
Messing with Developer Options (disabling overlay, etc) has not effect. Let me know if I can help troubleshoot...
Heyyo @ph03n!x, my nash is broken btw so I can't help too much.
Anywho, for the graphical glitches? Please try to go into your LiveDisplay settings and disable any special profile you have selected. I think those profiles are actually broken on nash hence the graphical issues when waking up the device after it sleeps.
Can you do me a favor please? Test my latest build of TWRP for nash. version 3.3.1-1 that contains a bunch of fixes and so far no feedback...
https://forum.xda-developers.com/showpost.php?p=82170641&postcount=590
{
"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"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.Has a refined Material Design 2 UI crafted by @SKULSHADY.Many useful features that provide a smooth premium experience.Just flash and enjoy...
Founder & Lead Developer:SKULSHADY (Anushek Prasal)DevOPS & Scaling:Irongfly (Sukeerat Singh Goindi)
If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Download ROM: https://havoc-os.com/device#sofiar
About Havoc-OS: https://havoc-os.com
Recovery: Vache's unofficial TWRP
Magisk: https://github.com/topjohnwu/Magisk/releases
FlameGApps: https://flamegapps.github.io/
Official Havoc-OS Telegram Group: https://t.me/havocofficial
Official Rav/Sofia-R-P Havoc-OS Telegram Group: https://t.me/+ioAiJwr1DKZiMjJl
Havoc-OS Announcements Telegram Channel: https://t.me/Havoc_OS
Code Review: https://review.havoc-os.com
1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.
2. Wipe System, Data, Dalvik, Cache.
3. Flash the ROM, GApps (Optional), Magisk (Optional).
4. Reboot and Enjoy.
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
Havoc-OS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Official
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help
Any plans to fix FM radio?
Leroy_Sparks said:
Any plans to fix FM radio?
Click to expand...
Click to collapse
Yeah I'll attempt a few things to try and fix it, worse case scenario I'll just remove it.
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
xStealth said:
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
Click to expand...
Click to collapse
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Funciona no a02s?
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
Yeah, I've been watching the Telegram. I'd been waiting on an update from Beetle but it appears they've stopped development on this device. I'd been using their most recent for over a month when suddenly Android system started using tons and tons of battery for no apparent reason so I shelved the phone and went back to my old one while waiting.
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
I installed Arrow to get FM radio (had been on Beetle's havoc before that). I'd like to have the radio but I do like havoc better. One thing I've encountered on the arrow ROM is a lot of stations have distorted audio (not all), even ones that usually have great reception on an old htc phone. I wonder if the moto radio is maybe not the greatest? Anyone notice similar? (I never tried fm radio while I had oem ROM).
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Thanks dude for ur work! UwU
luke.leheny said:
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Click to expand...
Click to collapse
Okay so I've tested your 4.10 build and pretty much all of these bugs are gone. Ambient display is still a little weird when trying to unlock but I tested on another phone and it seems like a Havoc OS bug rather than a bug with this build/phone. Haven't had a chance to check the bluetooth audio one yet. But the last 3 on this list all seem to be resolved by this build.
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
xStealth said:
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
Click to expand...
Click to collapse
Yeah LOS is having lots of issues with GApps lmao, I've been told a possible fix and i might try doing GApps included builds but im waiting for when I have a decent amount of time to try some of these. I did a Corvus build that has FMRadio fixed but thats only because Corvus is in SELinux Permissive and as i mentioned before you can likely fix FMRadio on every newer rom by setting it to SELinux Permissive via a magisk module.
@ph4n70m-404 I'll be keeping an eye to see if you somehow manage to fix the radio without having to go permissive. While radio isn't the most important of things, it's just a nice thing to have in case service goes down or I'm in the middle of nowhere.
Just wanted to add, overnight I only lost about 1.5% battery during idle (GApps version on 2.4GHz WiFi) in around 10 hours. That's absolutely astounding! Beetle's build did that to begin with, but after a few months Android System began to chew through battery nonstop. Excellent work!
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
jhford said:
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Click to expand...
Click to collapse
I'm the same builder as los one, the twrp image is just the same vache one everyone recommends so you just reinstalled the same twrp, los has been weird with getting gapps working so I've been trying to resolve that. The install instructions are just the ones the rom provides for their template and should really just be loosely followed, the only reason i dont change those is because i would probably write way too much about the install process and possible fixes to issues like the fact you should be on stock a10 before flashing when i and others provide far better support on telegram.
My advice is to use the vache moto flash tool, grab the firmware from lolinet, and flash back to stock a10, then after you make sure stock is working and everything install the twrp, wipe the data using wipe - format data on twrp, then proceed to just flash the rom via twrp.
JPutz said:
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
Click to expand...
Click to collapse
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
ph4n70m-404 said:
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
Click to expand...
Click to collapse
That's cool. I am happy where I am at. Rock stable and works flawlessly. I just think it is cool that I have a phone this old and it has recent updates on a custom rom.
I still say this should be stock. I had to redo my phone back to factory (flashed the update to the wrong slot. Oops!) and the stock rom was so annoying. I though I just hated iOS and the Samsung roms.
{
"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"
}
Credits
https://github.com/8890q/ for LineageOS 18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/NotKit for giving me very helpful hints about ubports/halium specifics
https://github.com/ExpressLuke for testing the edge on my behalf
these awesome people gave me useful pointers for https://github.com/Kethen/herolte_treble to come to fruition, and is used in this port:
https://github.com/ivanmeler
https://github.com/ExpressLuke
https://github.com/00p513-dev
Status
Samsung Galaxy S7 (Exynos) • Ubuntu Touch • Linux Phone
Flash your Samsung Galaxy S7 (Exynos) with the latest version of the Ubuntu Touch operating system, a privacy focused OS developed by hundreds of people.
devices.ubuntu-touch.io
There might be other instabilities that I do not know of, use at your own risk
while 20.04 development builds are available through ubport installer, note that 20.04 is still in heavy development
Installationubport installer now supports Galaxy S7 exynos
alternatively zips for the latest twrp can be found below, herolte for flat, hero2lte for edge
Downloadsnote that these releases are extremely outdated, for updated builds, use ubports installer
Releases · Kethen/samsung-exynos8890
halium 11 ubports for herolte, hero2lte and gracerlte - Kethen/samsung-exynos8890
github.com
Building and more information
GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
halium 11 ubports for herolte, hero2lte and gracerlte - GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
github.com
Reporting Issues
Issues · UBports / Porting / Community Ports / android11 / Samsung Galaxy S7 / samsung-exynos8890 · GitLab
Samsung Galaxy S7/S7 Edge
gitlab.com
Unofficial Waydroid ImagesThis is no longer required, waydroid has official h11 support and should be able to download official images during init. The waydroid helper app from openstore should be able to setup waydroid without using custom images.
Releases · Kethen/waydroid_build
personal waydroid build script. Contribute to Kethen/waydroid_build development by creating an account on GitHub.
github.com
Telegram discussion group
S7/Edge/NoteFE Exynos Ubuntu Touch
S7/Edge/NoteFE Exynos Ubuntu Touch discussions Use the bug tracker at https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-s7/samsung-exynos8890/-/issues if you have an issue Try to be nice to eachother and stay on-topic /notes
t.me
If you have an issue please use the bug tracker above instead
Hi, does Anbox work on this ROM?
Ex novo said:
Hi, does Anbox work on this ROM?
Click to expand...
Click to collapse
waydroid has no halium 11.0 support at the moment, but it should work once that is out
does sms out work
King081 said:
does sms out work
Click to expand...
Click to collapse
yes
Cool
I love this port and I've been able to pull off daily driver activities with it so far on my S7 edge. Still testing.
I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.
childoftext said:
I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.
Click to expand...
Click to collapse
some mitigations against random freezes were added last Friday, the issue is being tracked here https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/4
While I can do ussd codes consecutively without issues, a cellular issue fix was also added recently https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/2, and no one ever sends mms here so idk if that could get in the way
katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..
mcgragor said:
katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..
Click to expand...
Click to collapse
starting from https://gitlab.com/ubports/porting/...mmit/0342d2858fd431a8f0c5e4118141cad615a8c835, the halium bootscript will prefer booting from /data/ubuntu.img or /data/halium-rootfs/ if available
you can find the new boot.img on CI once that's ready, ubuntu.img is also available on CI
that should enable your use case of dual booting by swapping between halium boot.img and android boot.img, while having android system.img installed to partition and ubuntu.img installed to /data
note that this is not and will not be the default installation method so OTA will not work
katharinechuiThank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD
mcgragor said:
katharinechuiThank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD
Click to expand...
Click to collapse
If you know how to use adb, all you need to do after installing boot.img is adb shell mount /data; adb push ubuntu.img /data/ubuntu.img in recovery instead of splitting android-rootfs.img and rootfs.img from ubuntu.img then adding them to the zip. Unlike other halium 9+ ubuntu touch ports, the port for s7 provides it's own vendor image and does not use a vendor partition at all, ubports_GSI_installer_v10.zip is very very incompatible here and would likely cause you to pair a halium 9 system.img with the android 11 vendor inside ubuntu.img if you did not update system.img with a halium 11 one
Also note that since ubuntu.img contains it's own vendor image, you can use any device native roms without a vendor partition in this dual boot use case, without treble converting the device
On the other hand, E is rather questionable in my opinion
While I really respect their phone refurbish business and they do bring relatively hassel free installation and beyond official LineageOS device support to the table, their OS is often a month to three months behind LineageOS security updates, the built-in app store ships playstore apps from a shady french apk mirror, ships closed source magic earth that they've been saying "it will be opened source" for years and it's still closed source now, forked multiple open source applications to serve as their core apps but does not have the man power to keep them updated timely after the initial rebrand (you can see them getting mutiple releases behind on their gitlab), and all they really did towards privacy was to use another time server for ntp and another web server for checking whether internet is up, rebrand bromite and change the default search engine to not be google
They did all that rebranding to make a less secure LineageOS release that had very insignificant "degoogle" changes just to market and bundle their nextcloud fork ecosystem
I suppose they are capable of improvement, I'm very happy to see that their k9 fork has been pretty close to upstream as of late; but then overall they still put more effort into rebranding opensource projects rather than contributing to upstream, and are not keeping up with core things like keeping up with LineageOS security updates, stopping their iOS minic launcher from breaking deep sleep keeping your phone warm in your pocket and overnight draining battery, keeping their rebranded bromite fork up-to-date (current official release) (e bundled version)
If you don't use ecloud and don't need microg in your android dual boot, I'd really recommend Ivan_Meler's LineageOS builds; if you need microg and find it too cumbersome to manually install microg as system app on top, I'd recommend checking out Exodusnick's LineageOS for microG builds
Nowadays my main focus is being on the privacy of my data...
It's been a very difficult and complicated search, initially I thought of using /E/ for the data filter they claim to have, but your considerations about application repositories sparked an alert, even though I don't use the custom to install applications from stores, I always prefer to manually download apks, but this practice of them really opens up the security holes
about /e/ wake lock issue on 0.17-q, I tested version 1.4-q in the official repository and didn't report this problem, on the contrary, I noticed excellent battery life with no battery drop for long periods.
I will take your considerations and recommendations into consideration and I will check those lineage builds you mentioned, I intend to use android only when necessary but with microg, and ubuntu on a daily basis, but even in the short period of use of android I want to maintain a certain level of privacy.
Thank you very much for your advice
cant install 20.04
lentas said:
cant install 20.04
Click to expand...
Click to collapse
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall
katharinechui said:
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall
Click to expand...
Click to collapse
it worked with using linux app, windows app is buggy
Although an official MIUI 14 build is already available for our device, it does not show up while checking for updates for some users! (Don't wait for staged rollout ^^)
In my case (running MIUI 13.0.5.0) no update was found by Mi updater, so I decided to download the MIUI 14 Recovery ROM for my camellian (EU version) and to install it manually, but the server throws the following error message "Upgrade to stable version is not allowed"! WTF
However I managed to get the upgrade after updating manually to version 13.0.8.0 following these steps:
First of all make sure you are running the latest MIUI 13 build for your region by searching for latest firmware on this site: https://miuirom.org/phones/redmi-note-10-5g
If there is a newer version download and install it (OTA files worked for me - don't waste your mobile data plan)! Check updates again...
If MIUI upgrade notice is not showing up, even if you are on the latest build + option "recieve updates early" is enabled, then reset your updater by deleting its app data and cache. You can also experiment with newer/different versions of the updater app by installing + uninstalling (same as reset - worked on my second device).
(Download newer mi updater app from apkmirror) https://www.apkmirror.com/apk/xiaomi-inc/mi-updater/
Make sure you enable "recieve updates early" afterwards again by activating advanced settings (tap several times on the MIUI 13 logo in updater). Now check again... Bingo - the update message for MIUI 14 appeared and I was able to upgrade finally... (Proofed on 2 "Camellian", where no updates were offered before)!!!
Should work on other Xiaomi (Redmi, Poco) phones too - but your mileage may vary...
ტ Micefriendly ტ
Thank you very much! I was stuck on miui 12.5 without any updates available for almost a year despite of daily update check!? Today I discovered your howto and have cleared app data of the updater app and now there is an update to miui 13! Wow, it's magic - thumbs up.
Hello, it's me again! Upgrade to miui 13 worked like a charm and I like it so far. Do you recommend to upgrade to miui 14? Currently I'm on version 13.0.5.0 and need to update to 13.0.8.0 first to get it - right?
dubberruck said:
Hello, it's me again! Upgrade to miui 13 worked like a charm and I like it so far. Do you recommend to upgrade to miui 14? Currently I'm on version 13.0.5.0 and need to update to 13.0.8.0 first to get it - right?
Click to expand...
Click to collapse
I do not recommend MIUI 14, because it's lagging on both of my devices! In 60 Hz mode, which I prefer normally, lagging starts almost immediately and became unusable for me. 90 Hz mode lags often as well (while scrolling in browser, PDF-Reader or in miui settings), especially after intensive use. I don't have a PC anymore and can't downgrade. Wait until MIUI 14 becomes mature and the "refresh rate bug" is fixed - if this will ever happen...
dubberruck said:
Hello, it's me again! Upgrade to miui 13 worked like a charm and I like it so far. Do you recommend to upgrade to miui 14? Currently I'm on version 13.0.5.0 and need to update to 13.0.8.0 first to get it - right?
Click to expand...
Click to collapse
with what micefriendly say, miui 14 has nothing new besides wallpapers, step counter and new music widgets, new icons in the settings... and a change of the MIUI logo. + android 13
really, theres nothing new to miui 14. stay on 13 if you prefer, or update it and probably have a decrease on perfomance
@1lopes Nope, there are a lot of other changes in MIUI 14 - not only in the visible part (UI), but also under the hood.
Xiaomi MIUI 14 (Android 13) walkthrough
We take a deep dive into MIUI 14. See what's new, what's not and what's unique. Introduction Xiaomi's proprietary MIUI software matured quite a bit...
m.gsmarena.com
@dubberruck I disabled Miravision and the lagging decreased noticeable in 90 Hz. It's not completely gone, but a lot better and both phones are usable again. Lagging only appears after intensive use sometimes and with reduced intensity!? Very strange...
@ტ Micefriendly ტ I'm glad you partially solved the lagging, I think I will stay on miui 13 for now. BTW what is Miravision?
"MediaTek MiraVision is a suite of display-enhancing technologies designed to improve visual quality of displays and video playback."
AFAIK it was primilary created for enhanced video playback, but disabling it seems to have a positive overall effect in terms of "visual performance".
ტ Micefriendly ტ said:
@1lopes Nope, there are a lot of other changes in MIUI 14 - not only in the visible part (UI), but also under the hood.
Xiaomi MIUI 14 (Android 13) walkthrough
We take a deep dive into MIUI 14. See what's new, what's not and what's unique. Introduction Xiaomi's proprietary MIUI software matured quite a bit...
m.gsmarena.com
Click to expand...
Click to collapse
i see what you mean, but most of those functions are for MIUI China, or about the same
Xiaomi does almost nothing new for Global MIUI releases, or about the same as Chinese firmware, maybe frequently
but take note, that post tested a high end Xiaomi phone. comparing the Redmi Note 10 5G and its limitations due to its specs, that explains my opinion *
ive checked out MIUI 14 indo in my camellian, theres nothing new from that list, its all the same functions
all the perfomance improvements... no, its still the same. its just a game Xiaomi plays every MIUI release. if you want that perfomance improvement, get a higher end phone, youll probably see the difference
* MIUI likes to heavily limit 4GB RAM phones (likely most of what everyone uses in this forum), specially with an MTK 6833. due to the 4GB RAM, those functions wont be there for the sakes of the phone stability
now i respect your point of view in MIUI 14, but in my opinion, i recommend to not update. its no value of doing it, and you will probably slow down your phone if you have the 4GB variant, atleast for me
or really just do whatever you wish
after i waited for MIUI 13 thinking to myself it would have all of those new functions, but instead it just slowed down my phone, never again
@1lopes You are right, they reviewed MIUI 14 on a high end phone and not every super duper feature will find its way into all models and/or global versions. I don't like XIAOMI and their MIUI at all and bought the camellian only because it was a bargain. So, I don't care about announced features, which never show up.
But there are also often changes under the hood nobody will ever notice - that was my point. Only some new wallpaper, new icons, new widget etc. and thats it? No, there are also new bugs and I was affected - they definitively must have changed something.
Don't get me wrong, I understand that you are disappointed. They make promises and what you get is a slower phone after each upgrade. The same goes for Google!
For me it's too late - I'm already on MIUI 14, but I debloated and tweaked it, so it is running fine now despite of only 4 GB and there is no huge difference in performance to the previous versions - at least for me!
MEMORY/DISK/BATTERY Usage- and Perfomancetest under MIUI 14 (Android 13) after optimization!
{
"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"
}
ტ Micefriendly ტ said:
MEMORY/DISK/BATTERY Usage- and Perfomancetest under MIUI 14 (Android 13) after optimization!
Click to expand...
Click to collapse
Not that bad! I can't compete with that!
You can't compete with a geek's phone...