Related
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
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)
So this morning I went to check on lineage OS news oh, and I found out that they released today for all pixels. I am running it with no issues although I would recommend to download the micro gapps package cuz if you do the Nano or anything below it will give you issues with your phone reading SIM card. Aside from that I had successfully running the rom with magisk installed.
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
i42o said:
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
i42o said:
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
Click to expand...
Click to collapse
Is 90hz working??
ahoslc said:
Is 90hz working??
Click to expand...
Click to collapse
Read just one or two more posts above the one you quoted to find your answer.
bradical711 said:
Read just one or two more posts above the one you quoted to find your answer.
Click to expand...
Click to collapse
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
i42o said:
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
90hz works, 70% plus brightness on coral gives 90hz, below is 60hz. flame has some different tunings percentage wise, but same concept.
RefreshRate will work as soon as we have an official R image I can steal a single APK from.
We won't be implementing Squeeze or Soli most likely - it's RE, and given scrutiy over large projects and reverse engineered code, we likely won't see it unless it's reimplemented OSS (DU reverse-engineered it, but didn't clean room re-implement).
ahoslc said:
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
Click to expand...
Click to collapse
It works.
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Madjax2020 said:
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Click to expand...
Click to collapse
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
i42o said:
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
Click to expand...
Click to collapse
thank you sir for the reply. However i could not get it to be stable. The initial setup failed no matter what i tried. The error of data tansfer tool would fail. I want to run this as it seemed very smooth, however i think i need to wait for another update or something. i followed the OP to the t and nothing seemed to work properly for me.
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
I'll try again thanks for the info
Seems the wiki says you can sideload gapps right after sideloading the OS, the OP said doing that causes issues lol. But he'll I'll try it anyway
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
Got this running great, with gapps. Was wondering if you're getting the issue I am with google assistant. It seems to freeze up and not be usable.
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Madjax2020 said:
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Click to expand...
Click to collapse
You do remember I said micro right? I specifically explained that by using nano you would have no cell phone connectivity and upon transfer tool just put no transfer
XMayhem2099 said:
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Click to expand...
Click to collapse
Yes it is still there but much less now
Face unlock working?
As the title says, here's a list of some GSI's i have tested so far... but first for some story.
Bought the phone in summer, it's quite nice but has its own issues like no kernel source BUT since we can unlock the device and actually play around, oh boy it has been fun.
On the course of few hours and many downloads later I have a small list of GSI's that worked!
Every GSI I have mentioned REQUIRE device specific patch(es)!!!
For that you have to root.
----------------------WORKING GSI's-------------------------
BlissROM - It boots and functions quite fast
Cons: no included Gapps
Flashing any system editing patch results in "Phone is booting" homescreen.
https://sourceforge.net/projects/treblerom/files/BLESS/2020.09.21/
3.5 jack, VoLTE, Bluetooth, ComboFix patches are required, flash with Magisk manager
DO NOT USE FixLagSmooth
HavocOS 3.7 and 3.6 - Work and can be daily driven
3.6 requires FixLagSmooth patch
MUST root and apply all linked patches (don't use FixLagSmooth on 3.7, you can but no need)
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
AOSP Android 10 based - Also does work and requires patching
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
HydrogenOS Android 10 - Works
Has few bugs
No Google services
https://mirrors.lolinet.com/firmware/gsi/HydrogenOS/
----------------------COMMUNITY REPORTED GSI's-------------------------
Android 11 GSI - Reported to be functional by HumptyPotato47, thanks mate!
No Gapps as of now NikGapps exist for Android 11, search XDA for it!
Requires more testing...
https://github.com/phhusson/treble_experimentations/releases/tag/v300.f
----------------------MAYBE WORKING GSI's-------------------------
OxygenOS 10 GSI - Seems to work.. sorta
First boot after exiting fastboot causes the phone to reboot
Second boot will loop
https://mirrors.lolinet.com/firmware/gsi/OxygenOS/
----------------------NON FUNCTIONAL GSI's-------------------------
You tell me
...I did find a very nice list of GSI ROMs to try out more, here's the link:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
----------------------FLASHING GSI-------------------------
If you test one then don't hesitate with replying which one, about the experience, bugs and how you installed it.
My method of installing was this:
1. Make sure to have the new adb commandline that supports fastbootd mode
2. Drop the GSI .img file in /adb directory for ease
3. Make sure you're running MIUI with unlocked bootloader and USB debugging enabled
3.5 MAKE SURE you get a GSI ROM with Gapps as existing TWRP isn't fully functional
4. GSI you should have must be AB partition!!!
Once all set then follow the next commands
>adb reboot bootloader
>fastboot -w
>fastboot reboot fastboot
>fastboot erase system
>fastboot flash system "GSI-ROM-name-without-quotes".img
>fastboot reboot bootloader
>fastboot reboot
----------------------SETTING UP GSI-------------------------
Once all that is complete it should boot, if not then that specific GSI does not work.
Also a thing worth mentioning! Whenever I boot this phone to fastbootd Windows keeps forgetting what driver it was which requires
few extra clicks in device manager to set it up for fastbootd use. Including an image with simple to follow instructions if you have the same issue.
>fastboot boot twrp.img
Once in TWRP you should be able to access internal storage with your computer, drag Magisk.zip over and flash. Don't forget to wipe cache!
If it boots normally then root was successful, now apply the linked patch and reboot once again. Since we are playing with GSI:
Head to Settings
Find Phh Treble Settings
Misc features
Check Disable audio effect. -- DISABLE IT AFTER PATCHING!!!
IMPORTANT!!! I only tested Havoc and Bliss for a long period, IF one of my mentioned GSI's or others require more patches then I have linked headphone jack and Bluetooth audio patches too.
Combo fix should do the trick thought so your mileage may vary.
----------------------HELP US-------------------------
IF you find more working GSI's then tell us and I will make sure to add them to the main post so it won't get clogged under other comments!
Update on 05.10.2020 GMT+3
Bliss ROM GSI
As only a day or two have passed I already encountered few issues.
> You cannot remove screenshot sounds, even when fully muted
> Data drain is something interesting I've noticed, consumption compared to MIUI is higher.
> When using the gesture navigation it is a bit buggy when using quick side swipe for multitasking.
Positive notes!
> It is stupid fast
> Battery life is good
> GCam is amazing
> 99% of the customization options work perfectly
> Fast charging modes and such work perfectly
Neutral stuff...
> No FOD, thanks for closed source
> whenever you take a picture or a screenshot and have Blutetooth audio connected, it pauses and plays out loud via speaker. No music leaks out
this phone is born dead, no developer cares about it.
alsartawi said:
this phone is born dead, no developer cares about it.
Click to expand...
Click to collapse
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Kevin Soosaar said:
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Click to expand...
Click to collapse
i would pay to see a stable custom rom for this phone, i really loved it.
alsartawi said:
i would pay to see a stable custom rom for this phone, I really loved it.
Click to expand...
Click to collapse
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Kevin Soosaar said:
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Click to expand...
Click to collapse
does FOD works on Havoc OS?
edit: sorry i just read that it's not working.
alsartawi said:
does FOD works on Havoc OS?
Click to expand...
Click to collapse
FOD is not working as the driver sources are not public, reverse engineering is not possible too afaik. Everything else works.
Should i send this phone back to Amazon?
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
afigienas said:
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
Click to expand...
Click to collapse
Literally the main reason I made this post is to help others who are interested to use GSI ROM's on their devices. I do agree that MIUI has some decent features and I did use Xiaomu.eu before but it was so buggy. In the end I love customizing the device however I like it so MIUI is just not for me. Either way I might try to negotiate with Amazon to get a refund as touch and Bluetooth problems still persist. Fun fact, on Bliss the edge detection is pretty good and not as aggressive or straight out bad.
Simon_19 said:
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
Click to expand...
Click to collapse
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Is anyone try oos gsi ?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
can you give the link of the rom?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
Hi, there are gapps for Android 11, look for NikGapps here in XDA
Kevin Soosaar said:
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Click to expand...
Click to collapse
who said its cancelled?
Dr. DoubtReaper said:
who said its cancelled?
Click to expand...
Click to collapse
The mentioned Mi Note 10 Lite for India was supposed to be called Mi 10i or something like that. It quickly disappeared and is not happening.
Of course I might be wrong by this date but looking for now there is no 10i, only speculation videos and threads.
Mi Note 10 Lite for India would've been code named "tocoin", same hardware and everything else so just a rebadge in old Xiaomi fashion... :laugh:
anyone tried new version of blissROM? feedback?
GaryFisher88 said:
anyone tried new version of blissROM? feedback?
Click to expand...
Click to collapse
Not sure if the one I linked is up do date, give it a try yourself as my device went in for warranty repairs.
Hello, I am currently using Xiaomi.eu based on MIUI 12 and I would like to know how to flash HAVOC OS GSI. Should I flash back to Global Rom then flash the GSI as indicated? Answer is greatly appreciated.
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
UPD. Experimental version of Lineage OS 18.1 (Android 11) is also available by the attached GDrive link.
Hi, would you be willing to share the source repo and build instructions? Thanks!
lakkimsetty.baba said:
Hi, would you be willing to share the source repo and build instructions? Thanks!
Click to expand...
Click to collapse
Here you go https://github.com/Meetoul/android_device_Unihertz_Jelly2
Meetoul said:
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
Click to expand...
Click to collapse
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Gon112 said:
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Click to expand...
Click to collapse
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Meetoul said:
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Click to expand...
Click to collapse
NONE EEA
Gon112 said:
NONE EEA
Click to expand...
Click to collapse
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
1
Meetoul said:
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
Click to expand...
Click to collapse
1
Gon112 said:
1
Click to expand...
Click to collapse
The ROM is already built on top of the latest TEE binaries and it works on my Jelly2...
Probably, you have faced some issues during flashing the ROM. Please flash your Jelly2 back to stock ROM using SP Flash Tool and try again.
I have been using this ROM for couple of weeks now, it seems solid - didn't crash or had any issues.
The battery life however is very bad. I am using Magisk ACC module to limit the charge to 70% and it dropped from 70% to 34~37% within 8-ish hours (while I am asleep) consistently with all radios off (with regular cell network on for calls and texts, LTE off). The stock ROM used to drop at most 3% while I am asleep.
I think the stock ROM has aggressive app kill/ background process limit. I am going to try with those options enabled (in developer options) to see if there's going to be an improvement.
If anyone had issues like the above and has a conf, do let me know, thanks!
Edit: Forgot to mention that I also use AccuBattery and Greenify. Greenify is set to kill all user apps except for Magisk and AccuBattery.
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
beck.hannes said:
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
Click to expand...
Click to collapse
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hi
How many times have I tried to install LOS 17.1 it did not work,
Now I have tried to install LOS 18.1 and it works fine and perfect
Thanks!!
I'll be happy if you can add support for things you mentioned that are not currently supported,
Thank you good man.
Meetoul said:
AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
Click to expand...
Click to collapse
Would it help for you to have someone test VoLTE (and possibly WiFi calling?)
I'm considering picking one of these up and was just assesing what the community is behind it for custom ROMs. I had the original Jelly and the ROM community for that was very limited, and I was in over my head when trying to build it for myself. I would be glad to help however if you think you'll be using the device for a while
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software
Click to expand...
Click to collapse
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
beck.hannes said:
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
Click to expand...
Click to collapse
@Meetoul I installed the LineageOs 18 now which seems to be fine too.
2 Warnings appear after boot. Again the one with the public key, and a new one: "Serial Console active"
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Die Bruine said:
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Click to expand...
Click to collapse
Touch in recovery
Have you tried the latest release which includes fixes for both available touch panes (at least for TEE Jelly2)? If yes and it doesn't work anyway, could you please provide dmesg output from recovery and from normal boot? Output of dmesg should be collected as soon as ADB available. Also, please collect kallsyms using the following steps:
Code:
adb root
adb shell
echo 0 > /proc/sys/kernel/kptr_restrict
sysctl -w kernel.randomize_va_space=0
cat /proc/kallsyms >/sdcard/symbl.txt
exit
exit
adb pull /sdcard/symbl.txt
Annoying "Serial console is enabled" notification
You can just long press on the notification and disable notifications from Development Settings.
Thanks, this 'latest' release works! I am curious though, why do I get the message that there is no OS installed when I reboot from recovery? Or is that gonna be a long as reply .Also a few mount errors during flashing and reboot. But, my phone works for 99%.
Only thing not working in my banking app is the fingerprint sensor, also in the Ebay app (which I use once a year). Do you know why this is? Amazon video, Ziggo streaming app, even my banking app works. Fingerprint to unlock the phone also works. Just not in apps. Is this due to it being unlocked?
I come from a qx1000/Pro1 with LoS 18.1 which died on me Wednesday night. That's why I'm asking. That thing was also unlocked, but no error messages there. Also the Corona check app states that the J2 is rooted (which it isn't). Exactly the same configuration as my Pro1. But no warnings on that phone.
Not real complaints, just thought I'd share. This will be my daily driver for the next few months. So if you need a heavy tester, I'm your man.
@Meetoul
The battery drains in 24 hours, is this normal? I can't find any apps draining it. Could the enabled serial console be the culprit?
Edit2:
Hotspot not working for me. It connects but does not provide an IP address to clients. I tried several stock Android devices, without success. All four devices connect, but keep waiting for an IP address.
So now I'm typing this via Bluetooth sharing, which sucks I can tell you.
If you have any suggestions, I am more than willing to try them out...