Related
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
hjrry said:
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
Click to expand...
Click to collapse
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Nitefire77 said:
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Click to expand...
Click to collapse
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
hjrry said:
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
Click to expand...
Click to collapse
Try a different GAPPS package, maybe a larger one. Just to see. For one, some people complained of missing features like notification bar pulldown with the very smallest GAPPS package. Now this isn't a reason it shouldn't install, but try a different package to see if it make a difference in completing the installation.
hjrry said:
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Click to expand...
Click to collapse
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
plasticdoc said:
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
Click to expand...
Click to collapse
First, restore your backup. You did make a backup, right?
Then re-flash after you download a different GAPPs package. Some say Open Gapps works great for them, while others say Slim GAPPS is best. We don't know why some don't work for some people but work for others.
If that doesn't fix your issue, then try this:
Download the unofficial CM13 found here in this forum and try it.
Also, download Resurrection Remix (Marshmallow) and try it.
Both are variants of CM13 anyways. Just trying to see if something is wrong with your phone and you can't flash any ROM whatsoever or if it's something your phone doesn't like about official CM13.
The unofficial CM13 is CM13 with just a few of the Resurrection Remix tweaks thrown in, like permissions to download Moto apps from the Google Store, etc. It's 90% CM13, 10% RR.
If none of those CM13 variants work, you can alway try AOSP Mokee (Marshmallow).
IF NONE of those work, either your phone is severely messed up or you are doing something wrong.
ChazzMatt said:
Download the unofficial CM13 found here in this forum and try it.
Click to expand...
Click to collapse
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
plasticdoc said:
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
Click to expand...
Click to collapse
I don't know. Not everything with our phones is completely logical. Occasionally more of an art than science. Same reason one GAPPs package works well for someone but won't install for another person. Open GAPPS vs Slim Gapps.
Here's a personal example... My wife and I both have XT1225 with CM12.1 and yet hers can't run BHB27 kernel. Occasionally I'll get it to install, and run OK for a day or two but then next time I reboot it it does endless bootloops. I even tried different governors and I/O schedulers. Nada.
Mine is a Puerto Rico (unlocked Claro) XT1225 I flashed to India 5.0.2 before flashing to CM.
Her's is a Mexico direct-from-China-Motorola factory XT1225 I flashed to India 5.0.2 before flashing to CM.
Later I flashed Puerto Rico XT1225 radio over both.
There's just some difference there in her XT1225 which does not like BHB27 kernel.
Maybe if I did an exhaustive formatting of the entire internal memory and reinstallation of everything on her phone, it would work. But instead I take the easy way out and she's just running CM12.1 with default CM kernel, and that's running well. So, I go with what works.
phone app not working
unfortunately telephone has stopped working.
wajid1213 said:
unfortunately telephone has stopped working.
Click to expand...
Click to collapse
What does that have to do with this thread? > cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)
I don't even think you are using this phone, to be honest. So, why did you post here? You posted same thing in another thread, for ANOTHER PHONE, not even related to Quark.
You seem to be using this phone: Xiaomi Redmi 2 -- since all your other posts before this and after this are over there.
http://forum.xda-developers.com/search.php?searchid=422491957
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
grshnckh said:
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
Click to expand...
Click to collapse
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Mr.Ak said:
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Click to expand...
Click to collapse
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
grshnckh said:
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
Click to expand...
Click to collapse
https://www.cmxlog.com/14.1/bacon/
Mr.Ak said:
https://www.cmxlog.com/14.1/bacon/
Click to expand...
Click to collapse
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
grshnckh said:
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
Click to expand...
Click to collapse
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Mr.Ak said:
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Click to expand...
Click to collapse
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
grshnckh said:
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
Click to expand...
Click to collapse
Yes but the whole thread not just a single post.
Mr.Ak said:
Yes but the whole thread not just a single post.
Click to expand...
Click to collapse
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
grshnckh said:
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
Click to expand...
Click to collapse
Well,you can post your issues there or move on to unofficial lineage os by @idprophecy or sultan.
Sent from my A0001 using Tapatalk
I am too facing this issue. Did you get it working @grshnckh ?
CedArctic said:
I am too facing this issue. Did you get it working @grshnckh ?
Click to expand...
Click to collapse
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
grshnckh said:
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
Click to expand...
Click to collapse
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
CedArctic said:
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
Click to expand...
Click to collapse
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
grshnckh said:
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
Click to expand...
Click to collapse
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
CedArctic said:
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
Click to expand...
Click to collapse
Thanks for your advice. I already lost everything while trying to get back to LineageOS the last time. Fortunately I had up to date backups.
Have you flashed any ROMs or other stuff before that could cause the problems?
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
CedArctic said:
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
Click to expand...
Click to collapse
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
grshnckh said:
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
Click to expand...
Click to collapse
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
CedArctic said:
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
Click to expand...
Click to collapse
I read about a similar issue: https://forum.xda-developers.com/showpost.php?p=69837921&postcount=3
Highly would appreciate when you keep us up to date here. Good luck!
HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.
bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.
I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.
Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.
Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.
StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.
Thanks you very much
I will test
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Just a question, does StatiXOS have slim recents included?
Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.
Is anyone else having issues with sending a text message with this rom?
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
Double Post
Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.
chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..
The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.
SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.