Related
I got my OPO a week back, unlocked bootloader, installed TWRP and flashed OxygenOS right out of the box. I have been getting pretty good battery life for my needs except a problem. The phone randomly hot reboots. It may be while I am using it or maybe while it is lying in my pocket. No significant increase in temperature was noticed. I have attached the last_kmsg for the phone to this post. Can someone please help me in finding out what's up with my phone ?
abesh said:
I got my OPO a week back, unlocked bootloader, installed TWRP and flashed OxygenOS right out of the box. I have been getting pretty good battery life for my needs except a problem. The phone randomly hot reboots. It may be while I am using it or maybe while it is lying in my pocket. No significant increase in temperature was noticed. I have attached the last_kmsg for the phone to this post. Can someone please help me in finding out what's up with my phone ?
Click to expand...
Click to collapse
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
mijkz said:
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
Click to expand...
Click to collapse
@mijkz thanks for chiming in I am relieved to see that I am not the only one. I have never been on any of the CM roms. Flashed OXOS right out of the box. Clean install. I have a niggling doubt though that this might be hardware related, specifically the internal memory (after seeing the last_kmsg logs)
mijkz said:
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
Click to expand...
Click to collapse
If it helps, you can find your old last_kmsg logs in the following folder : /data/system/dropbox.
They should be in the following format : [email protected]
abesh said:
If it helps, you can find your old last_kmsg logs in the following folder : /data/system/dropbox.
They should be in the following format : [email protected]
Click to expand...
Click to collapse
Great, thanks
Now with LineageOS 14.1 Nougat
builds
sources (github) PATCHES STRONGLY ENCOURAGED
local_manifests for building
current branch is cm-14.1 (LineageOS 14.1 with Linux 3.10.x)
Instructions:
Unlock bootloader
Flash TWRP from kugo/twrp/recovery.img or from https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
Do not use AndroPlus's, it does not handle /system writing very well (in my experience)
Do not use my recovery build for stock, it does not handle /data encryption
Flash zip in recovery
SELinux: Permissive (I haven't updated the sepolicy in a while, enforcing makes the camera panic which causes bootloop. I may fix this later.)
Lineage 14.1
WORKING:
WiFi
Data/Cellular (you may want to jot down APN settings from stock before flashing)
Fingerprint reader (a bit unreliable, will fail sometimes)
FMRadio
Camera
NOT WORKING:
AudioFX (the built in equalizer thing; just disable it from the apps menu)
SELinux (sepolicy needs update)
Bluetooth (system seems to crash when turning it off)
Whatever isn't working in AOSP/Omnirom (e.g. in-call volume control)
UNTESTED:
NFC (it turns on, but I have no NFC devices)
Keep in mind that I am not really a developer but will do what I can to help with issues
Special thanks to the Sony-Kitakami team for serving as a base to port changes from suzuran/kitakami to kugo/loire
Additional thanks to humberos for porting omnirom to kugo and serving as a base to port to kugo
...and thanks to Sony for allowing us to unlock our bootloaders and for porting AOSP to their phones (unlike some other manufacturers)
Recent Changes:
Rebased device trees off of omnirom trees, updated everything
I'll go first and say thank you for developing for this device.
Hope that this encourages other devs to build their ROMs too.
Great job! :good:
Nice
as soon as audio playback is fixed i will flash and try to post logcats !
A little love for the XC
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
ardylemon said:
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
Click to expand...
Click to collapse
Not to mention greater adoption of ROM flashing now that we have a way to get back to stock.
thanks for the update!
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Micka84 said:
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Click to expand...
Click to collapse
I would go with cm-13.0 honestly unless bluetooth is that important (which is next on the to-do list for cm-13).
CM-14.1 is pretty incomplete upstream, so it's missing some features (like theming).
It's also still running the marshmallow kernel, so things like vulkan probably won't work either, and
I don't plan on releasing a build with the nougat kernel until we at least get prebuilts for it.
howdid said:
as soon as audio playback is fixed i will flash and try to post logcats !
Click to expand...
Click to collapse
Audio playback should be "fixed" now, for both 13 and 14.1
How is camera quality and battery life?
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
ammarr said:
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
Click to expand...
Click to collapse
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
tlxxxsracer said:
How is camera quality and battery life?
Click to expand...
Click to collapse
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
EliWallace said:
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
Click to expand...
Click to collapse
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
ammarr said:
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
Click to expand...
Click to collapse
It was enough to get through a day, but I would end up with 30-50% instead of 60-75% (I have mail checking constantly, so that was a big drain)
Thats in comparison to a CM build with a newer kernel and audio offloading not disabled,
I haven't used stock at all so I don't know how the battery life is on it
Why not use an existing msm8956 tree for kenzo and hydrogen and make Sony additions to a car kernel source and boot cm. It will bring much lesser issues.
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
NL_henk said:
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
Click to expand...
Click to collapse
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
NL_henk said:
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
Click to expand...
Click to collapse
I also noticed that the mobile does not charge however at the laptop over USB load it
Ps. i use not Costum Kernel
This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)
Hello everyone,
I am creating this post because I would like to know if someone has already installed Ressurection Remix on a Galaxy A8 ?
I saw some tutorials that are explaining this is possible,but when I go to the Ressurection Remix official download page, I cannot find which file is specific to the galaxy A8. Actually, I have some difficulties to understand the files names : Raphael, Sakura, Jason,... Are theses names code names for différents phones ?
I may add that the bootloader of my phone is unlocked, and I am using TWRP to flash zip files.
I didn't treblelize my phone thought.
If you have some other custom rom suggestions, please do not hesitate to advise me.
You can install RR through GSI, by this link
You will have to trebelize your device
Because it's a gsi android 10, you can use vendor quack
Treble Guide
Vendor Quack
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse
Treblizing the phone itself does not cause any problem rather it enables you to install different GSIs. Regarding GSIs, each have there own bugs and you have to find them on the GSI thread if available or if they have telegram or github support.
Hey, just made an account to respond to this as I just discovered there are per-device pages on these forums and saw this post, I have done exactly that and been running it for 2+ years now, so far I have had no majour problems wih it, the only majour caviat is that after trebblimg it and installing resurrection remix It seems to freeze when trying to display the charging animation if the phone is off and it plugged in, it still charges without any problems, tho to boot it when in this situation you need to force shut it down using the volume_down + lock buttons and then immidiately after use volume_up + lock buttons to boot into recovery, then you can boot to the normal system from there, I have a TWRP recovery but I think the stock one also allows to resume booting the normal system.
In these last months I had a few weird bugs like the screen brightness beeing locked to automatic but that went away after a reboot and only happened 1 time.
I also installed magisk and a few other small tweaks and things and everything works great, also all resurrection remix customization options.
Actually in the last few months something broke because the safetynet checks fail for the ctsProfile, (most apps like my banking app tho still work fine by using magisk hide (i think it's because the safetynet basicIntegrity check still succeds) and the update page seems also broken (tho no idea about when this broke exactly as I haven't checked it in years), everything else is still fine tho, I might try re-flashing it to update to the new majour resurrection remix when i have time and the will to backup and move everything, something could have corrupted or maybe an update broke it, no idea.
My phone reports resurrection remix 7.0.2 and Android 9.
Hope this is still helpful.
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse