Related
I decided a few days ago to downgrade my phone from 5.1 version of android to CM12. Did so successfully by flashing 5.0 bootloader and radio, then CM12. As soon as it booted I noticed the processor or battery mode is stuck on power saver and will not switch. Yesterday I updated to the new 12.1 nightly and still same problem. Would like to be able to toggle to balanced or performance. Is this a known problem or does something cause the bug?
Clean flash. If it still happens then it may be a ROM/kernel issue, or just user error.
Clean installed, went as far as formatting /system. Problem still persists. What can I do to report this bug?
KentuckyGuy447 said:
Clean installed, went as far as formatting /system. Problem still persists. What can I do to report this bug?
Click to expand...
Click to collapse
No point formatting /system since it does that in the flash script anyways.
Report it in the CM bug tracker if you are certain it doesn't work. I recall others having the same issue previously, maybe they just haven't fixed their profiles yet.
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!
XC/KUGO/F5321 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device crashes and reboots (mostly happens on demanding tasks)
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-06-16
Last Updated 2019-06-16
so are the micro lags fixed or still happening? there were slow downs and microlags on on games like clash royale etc... not as smooth as stock
This is excellent news! For those of us coming from 8.1 should we dirty flash (along with dsp-label-fixer) or is full data wipe required?
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Bluestar01 said:
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Click to expand...
Click to collapse
yes
official builds are signed and hence not really compatible with homemade
oshmoun said:
yes
official builds are signed and hence not really compatible with homemade
Click to expand...
Click to collapse
thank you, clean flash and is working
Great work! thanks for taking time to upgrade this ROM to Pie.
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
EDIT: GPS works
EDIT 2: GPS has a mind of its own and will not work except for the time when it does, currently investigating (probably something wrong with my phone)
ardylemon said:
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
Click to expand...
Click to collapse
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
droncheg said:
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
Click to expand...
Click to collapse
Thank you, I also got it to work after waiting a while, enabling mobile data as well as derping around with A-GPS settings in the process appears to have worked (not sure which, though). For future reference, my phone locked in after detecting at least 8 satellites with ~20% signal.
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
I've not this problem, for me all is working well and smooth (the only problem is quickswitch magisk module not working).
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
The Unofficial version of OmniROM by HarryHarryHarry had a similar issue, the fix was to first flash the latest stock ftf image (ends with .118), flash twrp and do a clean install of the rom. I would think this fix is going to work for this version too.
I'm currently running the Omnirom 8.1, and I just got a pushed message from OpenDelta on the phone itself:
Update ready to download
omni-9-20190616-kugo-WEEKLY
Click to expand...
Click to collapse
Can I update to Omnirom 9 from the phone itself by running that? Or must I download the rom on my computer and install it the normal way?
Great I will try this very soon!
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
In regards to the device crashing/rebooting issue. Does underclocking help at all?
lapucelle2 said:
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
Click to expand...
Click to collapse
Did that work? I've got the same issue
After updating to the latest weekly today, some apps got uninstalled again. I dad this behaviour also with the test builds before.
can't find stock rom yet i gave up upgrade to 9.0
Mietjelan said:
Did that work? I've got the same issue
Click to expand...
Click to collapse
can't find stock rom yet i gave up upgrade to 9.0
lapucelle2 said:
can't find stock rom yet i gave up upgrade to 9.0
Click to expand...
Click to collapse
I can't find how to install it either, all that flashtool crap isn't working...
I have just installed LineageOS 16 on my phone after I thought it crashed.
Waas the volumebutton that got stuck. Had LineageOS 15.1 before.
Now to the things I need help with
1. When I used version 15.1 I had to use a custom kernel to even be able to charge the phone when it's on.
it's the same problem here. Is there any custom kernel for version 16? [Seems to be SOLVED]
2. Preparing setup wont finish after installing gapps. Just says: "Preparing for setup... You can finish seeting up your a0001 soon. [SOLVED]
3. Gmail wont sync so I cant see my messages. [SOLVED]
I hope someone can help me with this three problems.
Sorry if it has been asked before.
Problem two and three did I solve by reinstalling LineageOS and using opengapps instead of mindthegapps.
But I do still need help with the charging problem.
*UPDATE*
It seems that the charching problem got solved after the latest nightly build update.
I hope it stays that way.
So everything seems to have been solved.
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.