[RC-FAQ]>> CM12 Frequently Asked Questions for Motorola Moto G [Updated: 2015/09/08]
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] Motorola Moto G
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/SIZE]
Read Before Asking Please
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
You may search in Motorola help topics too
Table of content :
FAQ part #1
[SIZE=+1]Q1: How do i Install CM12?[/SIZE]
From CM11 or CM12: simply download ROM zip and gapps, then Flash
From other ROM:
download ROM and gapps
Reboot to recovery
Format /system, /data (data content will be lost, but should not impact /data/media), /cache and wipe dalvik-cache.
==> this is for CWM, on TWRP, better use the factory-reset option.
Sideload from Computer or install from storage depending on where the download was completed)
wait
Reboot
wait (may take more than 3 minutes)
enjoy!
Rq:
For Falcon, Nightly releases on official CM12 are reported working on XT1032, XT1033 and XT1034 and GPE XT1032. The XT1028/XT1031 (non-LTE 3G CDMA) are not able to get data, calls and SMS
For Peregrine: ?
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: How to set SELinux state to Permissive?[/SIZE]Open terminal (see Q3), type :
Code:
su
Code:
setenforce 0
Done!
An app does it too : SELinux Mode Changer
More about SELinux :
SElinux and Android
SELinux explained for Gentoo systems
script to enforce Permissive SELinux state for GS5
[SIZE=+1]Q6: Having Issues with minfree settings and RAM management?[/SIZE]
Get this script by @attack11
Paste it to /etc/init.d, set permissions to -rwxr-xr-x and edit extension to .sh to file manager can execute
Execute the script manually at each boot if your SELinux state is anything above Permissive (init.d scripts are not granted SU rights when in Enforcing mode).
[SIZE=+1]Q7: Having issues with GPS?[/SIZE]Erase modems as explained on this post:
Plug device to PC
Code:
adb reboot bootloader
Code:
fastboot erase modemst1
Code:
fastboot erase modemst2
Reboot
[SIZE=+1]Q8: Why can't i install Xposed on CM12?[/SIZE]Take some time to read rovo89's post about his own project and why Xposed isn't supposed to work (yet)
[SIZE=+1]Q9: Why do i get screen flickering (until i turn off/ON screen) and how to get rid of it? (nightlies 20150315-->20150324)[/SIZE]The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide
[SIZE=+1]Q10: Why does the installation abort? (nightly 20150324+)[/SIZE]If the error message you are facing is the following,
Code:
this package support bootloader(s): 0x4118: this device has bootloader 0x4113.
E: Error in /data/media/0/cmupdater/cm-20140324-NIGHTLY-falcon.zip
(Status 7)
Installation aborted
then The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide
If for some reason you can't (or don't want to) update your bootloader, then read this post by @wskelly
[SIZE=+1]Q11: How do i report an issue to get some help?[/SIZE]Here is a nice example of how to report an issue:
geekasm said:
Hi,
XT1033: bootloader unlocked, rooted, stock rom 4.4.4
TO: 5.0.2
Flashed 4118 bootloader, as detailed in http://forum.xda-developers.com/moto-g/help/rc-faq-cm12-frequently-questions-t2996087
It was successful.
Followed http://forum.xda-developers.com/moto-g/general/guide-how-to-flash-root-cyanogenmod-12-t3090805
formatted system, data, cache, wipe-cache (recovery: clockworkmod-6.0.4.7)
installed CM, Gapps
CM: https://download.cyanogenmod.org/?device=falcon
Gapps: https://www.androidfilehost.com/?fid=96039337900114916
After rebooting, the phone is stuck on the Cyanogenmod boot icon (blinking cat face) since past half hour.
Please guide how to debug/recover.
Thanks,
Click to expand...
Click to collapse
It says the device model, the Bootloader version, the ROM (the one coming from and the one where the problem occures), and some more informations about the process.
[SIZE=+1]Q12: Why Ambient display and gestures are gone and how to get it back?[/SIZE]Ambient display and gestures were handled by motodoze which conflicted with Android's way of turning screen On and Off, this application from motorola has its sources closed and thus cannot be modified by CM team to handle the conflict.
Motodoze has been nuked (20150903)
But we have a new king to rule the kingdom: AcDisplay !
(or its fork, built by @luca020400 who modified the way proximity sensor is checked to get closer to motodoze's way)
Here the fork : http://forum.xda-developers.com/showpost.php?p=62668999&postcount=4587 (using motodoze implementation for gestures)
Here is the official app : https://play.google.com/store/apps/details?id=com.achep.acdisplay&hl=en (using @AChep 's implementation for gestures)
Play with settings and tune the app to get either the closest experience possible you were used to, or make it fit better to your own needs.
[SIZE=+1]Q13: Having issues with your partition table?[/SIZE]When installing CM you may experience being stuck at "Patching system image unconditionally..." mainly if you device was converted to GPe.
This happens because the recovery tries to write a block that exceeds the partition size (/system of the GPe partition table seems to be smaller than the CM one) ==> this also happens when you want to upgrade a MotoE (Condor) from stock 4.4.4 to CM12.1
In that case the following may help you (Falcon ONLY): http://forum.xda-developers.com/mot...-gpe-stuck-t2970842/post57444986#post57444986
If you are running any other device than a Falcon, then download a stock firmware (Lollipop), extract the gpt.bin and flash it:
Code:
fastboot flash partition gpt.bin
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum. A special thanks to everyone who contributed to the production of this FAQ
reserved
reserved 2
If you have a problem with the management of RAM install this device "pimp my rom" everything can be set up
I´ve read that a lot of users have problems flashing any lollipop rom due to "cant mount system" error while installing.
Maybe this could help:
http://forum.xda-developers.com/and...error-cm12-t2992195/post57929278#post57929278
It would be nice if someone could look into it!
I'm having issues with the camera. Both the cyanogenmod camera and the good camera aren't taking any pictures. Both apps open and otherwise function properly, but whenever I try to take a picture it just doesn't work: the animation of a taken picture occurs, but then nothing happens. What can I do? This had been a persistent problem for the last couple of nightlies.
Marco_Mena said:
I'm having issues with the camera. Both the cyanogenmod camera and the good camera aren't taking any pictures. Both apps open and otherwise function properly, but whenever I try to take a picture it just doesn't work: the animation of a taken picture occurs, but then nothing happens. What can I do? This had been a persistent problem for the last couple of nightlies.
Click to expand...
Click to collapse
You can try this, read on from post #255: http://forum.xda-developers.com/mot...ficial-cyanogenmod-12-nightly-t2994749/page26
Can anyone tell me how to fix VoIP issue. Hangouts and viber works fine but line messenger didn't work for me.
Ok I just came back to my Moto g. And now that I would like to flash a cm12 rom I don't know which one because theirs more than 5 cm12 roms out there!!!.. Can anyone point me to the one that is best to flash plz.
jglm4u said:
Ok I just came back to my Moto g. And now that I would like to flash a cm12 rom I don't know which one because theirs more than 5 cm12 roms out there!!!.. Can anyone point me to the one that is best to flash plz.
Click to expand...
Click to collapse
I suggest you to try the official one first: http://forum.xda-developers.com/moto-g/orig-development/rom-official-cyanogenmod-12-nightly-t2994749
Some camera issues but usable and quite stable, IMHO.
aa
I think swipe doens't work.
It's not working for me.
On cm11 was perfect.
AmyPP said:
I think swipe doens't work.
It's not working for me.
On cm11 was perfect.
Click to expand...
Click to collapse
if you are talking about keyboard, then, that's a known issue (try to use google keayboard instead, available on playstore), i will try to make a "know issue chart" ASAP but i don't have enough time right now
camera
Shub77 said:
You can try this, read on from post #255: http://forum.xda-developers.com/mot...ficial-cyanogenmod-12-nightly-t2994749/page26
Click to expand...
Click to collapse
Initially the camera seems to work. I can reboot and the camera works for a few hours. After a few hours it stops working. It takes a pic and then doesn't save it...This has been the case since the first official nightly.
I'm sure it will get ironed out! So far, working mostly great otherwise!
XT1045 & cm-12-20150114-NIGHTLY-peregrine.zip
mystic0101 said:
Initially the camera seems to work. I can reboot and the camera works for a few hours. After a few hours it stops working. It takes a pic and then doesn't save it...This has been the case since the first official nightly.
I'm sure it will get ironed out! So far, working mostly great otherwise!
XT1045 & cm-12-20150114-NIGHTLY-peregrine.zip
Click to expand...
Click to collapse
Ok, phase 2 Me and others are trying out this one: http://forum.xda-developers.com/showpost.php?p=58171653&postcount=296
I just flashed it, and I will try not to reboot for a day or so, 'cause the problem seems to arise after some time, as you said in your post. Right now camera is working well.
Shub77 said:
Ok, phase 2 Me and others are trying out this one: http://forum.xda-developers.com/showpost.php?p=58171653&postcount=296
I just flashed it, and I will try not to reboot for a day or so, 'cause the problem seems to arise after some time, as you said in your post. Right now camera is working well.
Click to expand...
Click to collapse
Got it :good:
Downloading and reflashing now! I'll report back!
---------- Post added 15th January 2015 at 12:16 AM ---------- Previous post was 14th January 2015 at 11:30 PM ----------
mystic0101 said:
Got it :good:
Downloading and reflashing now! I'll report back!
Click to expand...
Click to collapse
That kernel doesn't seem to be working for my...wasn't able to boot for some reason
Don't know what's up.
Reverted back to the latest nightly. Maybe have more time to play with it later...
camera?
Please, i'm having issues with the camera since i was trying to use early versions of CM12 ...
Camera loads up, but when i click to shoot a photo, the picture freezes, and nothing happens. Tried with Google Camera ( and updated version) , with Motorola Camera ( and updated version) and several apps, like Whatsapp,Snapchat,etc...
Anyone knows how to fix that, or a previous version where the camera works?
--
for taking a pic when its not saving
just press and hold befolre hitting the capture button
I'm using moto camera
& i press & host the screen for about 1 sec & it captures the pic and saves it
Homigura said:
Please, i'm having issues with the camera since i was trying to use early versions of CM12 ...
Camera loads up, but when i click to shoot a photo, the picture freezes, and nothing happens. Tried with Google Camera ( and updated version) , with Motorola Camera ( and updated version) and several apps, like Whatsapp,Snapchat,etc...
Anyone knows how to fix that, or a previous version where the camera works?
Click to expand...
Click to collapse
Read a coupl of messages before yours...
mystic0101 said:
Got it :good:
Downloading and reflashing now! I'll report back!
---------- Post added 15th January 2015 at 12:16 AM ---------- Previous post was 14th January 2015 at 11:30 PM ----------
That kernel doesn't seem to be working for my...wasn't able to boot for some reason
Don't know what's up.
Reverted back to the latest nightly. Maybe have more time to play with it later...
Click to expand...
Click to collapse
Sad I've been using version 01.14 of the nightly, and it seems no problem (of that kind at least) on my XT1032.
Devs suggest to use TWRP latest (2.8.some.thing) as custom recovery.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial OmniROM OREO for Z3C (aries)Brought to you by @nailykKnow someone with a Z3? Send them over to this threadClassic disclaimer:
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Features:
OTA Updates:
We've activated OTA updates, so you can be sure to get the latest updates for your device!
Unique, customizable features with OmniGears:
Control the brightness by swiping across status bar!
Set your own actions for hard- and software buttons!
Change the style of your device, thanks to substratum support! (dark theme already included)
Crop your screenshot right after you took one!
...and much more!
Switch your apps with OmniSwitch
Forget the recents drawer, you can switch your apps by swiping from the edge of the screen!
Customizable, with cool extra features!
And of course completely OPTIONAL! Switch it on the go without restarting your device!
...
Prerequisites:
Sony Z3 Compact (aries)
UNLOCKED Bootloader
Latest TWRP release
Install guide:
Still on stock fw?:
Make sure you're on 23.5.A.1.291, if not, download and flash it with Flashtool.
Flash the latest TWRP (3.1.xx) in fastboot (fastboot flash FOTAKernel twrp_***.img)
When you're done, follow the next points below this spoiler.
Enter recovery mode (HOLD VOL DOWN + POWER while device is off)
WIPE /system, /data, /cache, dalvik cache
SELECT the ROM zip and flash it
(Optional) Flash GApps: (http://opengapps.org/)
(Optional) Flash any other extras (root: look below the guide)
Reboot into system and wait for boot (it'll take some time, don't worry)
Root:
For root, we suggest that you use phhSuperUser, as it is fully open sourced and it works fine with OmniROM: phhSuperUser thread
Alternatives are Magisk (Click here) and SuperSU.
Downloads:
Latest build:
Read post #2 to check what bugs are currently on the latest build!
2018-06-16:
Direct: https://releases.nailyk.fr/omnirom/omni-8.1.0-20180616-z3c-nailyk.zip
Changelog at post#2
Previous builds:
2018-03-20:omni-8.1.0-20180320-z3c-nailyk.zip
2018-01-01:omni-8.1.0-20180101-z3c-nailyk.zip
2017-11-03: omni-8.0.0-20171103-z3c-nailyk.zip
2017-11-01: omni-8.0.0-20171101-z3c-nailyk.zip
2017-10-29: omni-8.0.0-20171029-z3c-nailyk.zip
TWRP:
https://releases.nailyk.fr/twrp/twrp_z3c_O_2018-06-16.img
Want to report bugs?
Give us logs using dmesg or logcat (clear logs first before reproducing the problem with "adb logcat -c")
Rebooting problems? Provide last_kmsg
Written explanations only with a way to reproduce the bug
XDA:DevDB Information
OmniROM, ROM for the Sony Xperia Z3 Compact
Contributors
devil188, nailyk, Dobsgw
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2017-10-29
Last Updated 2018-03-27
Changelog:
2018-06-16 release:
REQUIRES A FULL WIPE!
TWRP dirty fix for zip flashing.
Attempt to fix camera record (not working!)
Solve reboot to recovery
Periodicals updates
Switching to enforce mode (selinunx)
Click to expand...
Click to collapse
2018-03-20 release:
Partial Changelog
Lot of audio changes,
Video record fixed (some problems remain, like format, green bar, etc),
Some not-fully-tested power patches.
Click to expand...
Click to collapse
2018-01-01 release:
Lot of code cleaning,
some fixes about audio, & gps.
New issue about 4G connection: you need to connect to a wifi network before it became available (if you do not have nearly trusted wifi, turning on AP works too. )
Click to expand...
Click to collapse
2017-12-07 release:
Lot of change for camera (video record still broken)
Lot of sepolicy changes (next release will be enforcing so please report your denials logs)
Change for GPS. Should work but expect problems anyway.
SystemUI tuner should be working again.
Small change to make external sd mountable while using unix file-system. Still not able to write on it for now.
Click to expand...
Click to collapse
2017-11-03 release:
Multiple merges:
2017-10-31:
OTA updates
2017-11-03:
Fix video recording (26562)
Fix aries bootanim size (26515)
Click to expand...
Click to collapse
2017-11-01 release:
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
Click to expand...
Click to collapse
Currently known issues and their fixes:
ERROR 7 while flashing in TWRP
- Flash the correct TWRP or delete the getprop() in updater-script.
Video recording not working
- Now partially working, some bugs may occur!
Problems with MicroG
- https://forum.xda-developers.com/showpost.php?p=74341878&postcount=9
5GHz Wi-Fi networks not working
- There are reports that 5GHz Wi-Fi networks not getting detected, we can't reproduce this problem though. Currently looking into this.
Sources:
https://github.com/nailyk-fr/local_manifests/blob/android-8.0/x-roomservice.xml
https://github.com/omnirom
https://gerrit.omnirom.org/
How to report
How to post
Reports without logs or step to reproduce are useless (read contribute).
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to report any typo, error, etc...
Try to keep thread clean as a dev reference. Thanks in advance.
How to report problems
To report problem, please provide logs.
It is always better to include reference to the Installed version. This guide is really detailed and explained everything about bug reports.
If you have any doubts, take the most logs. There is never enough logs
How to get logs
If your device is not booting at all, we need information about how you flash and all the handling you do, the display status, light status, and if available a dump of /proc/last_kmesg*
If you have a non working peripheral (non-working radio/wifi/etc...) please provide a full logcat and full dmesg, example:
Code:
adb reboot
adb wait-for-device
adb shell dmesg > dmesg.log
adb logcat -d > logcat.log
If you have a non working app please provide a partial logcat:
Code:
adb reboot
adb wait-for-device
adb logcat -c
<launch your app>
adb logcat -d > logcat.log
On this rom, there is a script who detect device at install time and provide the right functions for single or dual sim. If you have modem problems (like data not working or no signal) please also provide the /tmp/recovery.log.:
If you have ADB access to your device in twrp just use
Code:
adb pull /tmp/recovery.log .
after flashing omnirom.
If you do not have ADB access use the 'copy to SD' button in the advanced tab, then transfer it the way you like.
then upload your files to a service like pastebin.com / paste.omnirom.org
How to contribute
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Based on stock sony kernel?
Amazing, I'm testing right now.
-It's quite fast (maybe a bit laggy in Settings app)
-Calls/SMS ok
-Wi-Fi working (both 2.4 and 5 GHz)
-Camera taking pictures, but not videos (as stated in post #2)
-Mobile data working (2G, 3G, LTE)
-Bluetooth working! I successfully connected to my JBL Go
-DoubleTapToWake not working
-Auto brightness not working here, good Night Mode
-Audio is quite loud, very good! (good inCall and loudspeaker volumes too)
-Screen rotation working
-64GB microSD correctly detected
-only around 5.5 GB occupied (without gApps)
-just 23 seconds to boot
-30 minutes of SOT drained about 7% of battery
I'm really tempted to keep this ROM, but I'll wait for it to get even more stable than now.
Oreo seems a way better than Nougat.
Thanks dev for this :good::good::good:
When video recording gets fixed I am installing this ROM,I already see good reviews so hoping it gets fixed soon.
Great job dev!
Awesome work guys, bluetooth works.
Hope we got Lineage or AOSP ROM soon.
Testing,so far so good.
So far so good... What I've noted:
- 'unknown sources' option in security settings is done away with. Now is a pop-up dialog included in pkg mgr.
- Settings layout is different. Main dashboard more condensed, with several options now in sub-settings.
- Signature spoofing ability included without patch, but Micro G still showing not active. Not sure what to do to activate it. SELinux already permissive; I don't see any option in settings...
- phh's Superuser working fine, (my preferred root).
Thanks
---------- Post added at 08:24 PM ---------- Previous post was at 07:55 PM ----------
Figured out the Micro G issue, (feel stupid because I already went through this with another ROM and forgot about it...) Just tap on the unchecked box in Micro G settings and allow permission in the pop-up box.
Now Micro G working fine...
Very Good!
Please add control with one hand as on LOS, my top of the sensor does not work.
Awesome work guys, thanks for all the hard work @devil188 @nailyk @Diewi @xkeita @rcstar6696
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
Awesome work guys, thanks for all the hard work @devil188 @nailyk @Diewi @xkeita @rcstar6696
Already approx 24h on. I am really pleased surprise, she isn't perfect but come on!! ,is Alfa release, and come so early after officially released!
Normally installed, on get gaps I have same treble, usually use aroma install, but don't past a way,finely successful with pico, magisk , and now I am a happy campers.
Tks a loot for this!
Stock camera working, no recording.(just flash)
I guess they cut button rearrangement out of system ui tuner in Oreo. Found this app that can restore it - https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner. I have a feeling it's easy to do with apktool also, but apktool not ready for O yet, so haven't been able to test, (https://forum.xda-developers.com/showpost.php?p=74347058&postcount=5108)...
Tried the rom. Many congrats for the good work and thank you.
I cannot get the 5ghz networks to show up.
Also double tap to wake does not work.
And, the camera, even if does not FC when taking video, it does not store it anywhere.
Finally I get an error message as soon as the phone boots up to android. "Cell broadcast has stopped".
I will be following closely this thread. Keep up the good work!!!
I flashed again this rom to check if "Nougat Sony Camera Port" could work on Oreo too (I cannot live without that camera).
The result is YES (obviously Video recording still broken and some camera mode like AR Fun are force closing) and Cyberian Camera 8.0 works too.
So proud of this phone, it does not want to give up :good:
madvinegar said:
Tried the rom. Many congrats for the good work and thank you.
I cannot get the 5ghz networks to show up.
Also double tap to wake does not work.
And, the camera, even if does not FC when taking video, it does not store it anywhere.
Finally I get an error message as soon as the phone boots up to android. "Cell broadcast has stopped".
I will be following closely this thread. Keep up the good work!!!
Click to expand...
Click to collapse
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
devil188 said:
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
Click to expand...
Click to collapse
Apologies for the noob question. How can I take a logcat?
devil188 said:
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
Click to expand...
Click to collapse
5Ghz working for me too, but not DT2W.
I've seen a new build on androidfilehost (too late ), has it been fixed in that build?
2017-11-01 release
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
And a surprise coming.
Link will be added to OP in a few.
nailyk said:
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
And a surprise coming.
Link will be added to OP in a few.
Click to expand...
Click to collapse
You mean right now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.
These are my UNOFFICIAL builds of LineageOS-17.1 for LG G5 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a rs988 variant, so other variants might have some issues.
This now runs System-As-Root. Ie.. / and /system are merged, so /system is really /, and /system is /system/system.
For broken issues see 2nd post
Issues:
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
5Ghz tether not working due to "error"
Install
You can upgrade from 15.1 (UNOFFICIAL) to 16.0 to 17.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recovery before upgrade, not reboot into system).
Flash to-x86cpu.zip if needed. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
Reboot and wait....
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the rs988 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great. (See post #3)
Please indicate what G5 variant you have (h830, h850, rs988) and the dated version. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@Rashed97 for continuing
@Blaises[/MENTION] for Bluetooth and WiFi static hax if all 00s.
@npjohnson for help along the way.
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 10.0
Sources
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_g5-common
h830
h850
rs988
What is working:
WiFi
Camera
GPS
NFC
2.4 Ghz Hotspot
USB OTG
What is NOT working:
VoLTE and WiFi calling do not (and most likely never will).
5.0 Ghz Hotspot
Encrpytion is untested, so it may fail.
Anything else NOT listed above might or might not work. I will adjust as necessary and reports. If anyone has any knowledge and can troubleshoot and fix the NOT working items, let me know.
Here is how I capture logs. You need to ensure you can do this right at boot and will need to setup ahead of time.
You need to have root, either su, or "adb root". Verify you can get root quickly.
Here are the steps I do to accomplish this. This is a Linux system, so windows will vary slightly.
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb root ; adb shell
Once connected, immediately paste the following (to capture logs).
Code:
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
If you have root installed via Magisk as "su":
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb shell
Once connected, immediately paste the following (to capture logs).
Code:
su
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
Once Phone reboots, or boots up. The needed files are in /cache "lc" and "dm", and are available in TWRP even.
Thank you for your efforts and support. I will try as soon as possible
Sent from my LGE LG-H850 using XDA Labs
Thanks, @x86cpu I'll start working on my new threads for Havoc OS and Pixel Experience. I was also curious about this commit does this have anything to do with going Official.
ROMSG said:
Thanks, @x86cpu I'll start working on my new threads for Havoc OS and Pixel Experience. I was also curious about this commit does this have anything to do with going Official.
Click to expand...
Click to collapse
That's just the wiki getting added.
https://review.lineageos.org/c/LineageOS/hudson/+/267517
That above is more what you might be looking for.
x86cpu said:
That's just the wiki getting added.
https://review.lineageos.org/c/LineageOS/hudson/+/267517
That above is more what you might be looking for.
Click to expand...
Click to collapse
Ok kind of a noob question, but what is the wiki sorry for asking.
ROMSG said:
Ok kind of a noob question, but what is the wiki sorry for asking.
Click to expand...
Click to collapse
The wiki page is just information about the device, how to install Lineage, etc..
Preview: https://harryyoud.co.uk/lineage-previews/217514/11/devices/rs988/
hudson is the build server repo, and what order and how often to build for, like "N"ightly, or "W"eekly. Once 17.1 is official, most 16.0 goes to Weekly builds, and 17.1 goes to Nightly.
x86cpu said:
The wiki page is just information about the device, how to install Lineage, etc..
Preview: https://harryyoud.co.uk/lineage-previews/217514/11/devices/rs988/
hudson is the build server repo, and what order and how often to build for, like "N"ightly, or "W"eekly. Once 17.1 is official, most 16.0 goes to Weekly builds, and 17.1 goes to Nightly.
Click to expand...
Click to collapse
Ok Thanks so much, sorry for the Noob question I'm still learning.
i tries gapps and nikgapps and bit gapps no one is letting me go after final touch screen. even i skip setup wizard still setup wizard crashing errer popups continusly. i now removed setup wizard from twrp and started the rom...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
it has same bugs as romsg 17.1.
google camera processing hdr stucks at 100%
after reboot lockscreen takes 1 minute to accept password.
battery life is a bit bad
till now i saw these issues.
rest is perfect
thank u sir for this rom..
just perfect
just did a dirty flash, coming from 16.0. -->
wiped davlik and cache before, and then... everyhting went perfectly fine
all settings and apps still alive and functional.
quick check... wifi, bluethooth working fine, camera as well.
I'm very happy, thank you! :victory: :highfive:
Also i started the new oc kernel for Android 9 and 10. Hope i will release soon.
Sent from my LGE LG-H850 using XDA Labs
Tried doing a clean flash and I can't seem to get past the setup screen. When I get to the last screen where it asks to set up a few more things, when I tap finished for now, I get a FC and I can't finish the setup.
Using RS988 with opengapps 10 nano 1.24.2020 and magisk 20.3.
Steps used:
Wipe data, cache/dalvik and system
Flash LOS17
Flash Gapps
Flash Magisk
Reboot
I'll try gapps 1.23.2020 and report back.
This is a buggy setup wizard. Try to delete the setup wizard via twrp and it should boot up normally.
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
I have no NFC. Can only turn it on via Quick settings. No menu in network settings. Turning it on in quick settings has no effect. Prior to this ROM I had Romsg's version installed. But with the same behavior. Does anybody know a solution?
djskribbles said:
Tried doing a clean flash and I can't seem to get past the setup screen. When I get to the last screen where it asks to set up a few more things, when I tap finished for now, I get a FC and I can't finish the setup.
Using RS988 with opengapps 10 nano 1.24.2020 and magisk 20.3.
Steps used:
Wipe data, cache/dalvik and system
Flash LOS17
Flash Gapps
Flash Magisk
Reboot
I'll try gapps 1.23.2020 and report back.
Click to expand...
Click to collapse
fscout42 said:
This is a buggy setup wizard. Try to delete the setup wizard via twrp and it should boot up normally.
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
I have no NFC. Can only turn it on via Quick settings. No menu in network settings. Turning it on in quick settings has no effect. Prior to this ROM I had Romsg's version installed. But with the same behavior. Does anybody know a solution?
Click to expand...
Click to collapse
I ended up just flashing LOS16 and dirty flashing to 17.1.
Everything seems to be working except NFC and the camera seems really buggy, even after reboot. Can't save to external sd card, and recorded video can't be played. Also as mentioned above, gcam doesn't work either. Using arnovas advanced 1.7 that worked great on los16.
Roboxl said:
just did a dirty flash, coming from 16.0. -->
wiped davlik and cache before, and then... everyhting went perfectly fine
all settings and apps still alive and functional.
quick check... wifi, bluethooth working fine, camera as well.
I'm very happy, thank you! :victory: :highfive:
Click to expand...
Click to collapse
BT calls works? Or only music?
Wysłane z mojego LG-H850 przy użyciu Tapatalka
Trying out the new build on my H830 and it's good so far. I've dirty flashed from 16.0 using NikGapps core and Magisk 20.3.
I want to note some bugs along with some workarounds:
1. Camera is buggy on first boot (restarting seems to fix this)
2. Recorded videos fail to play (keep pressing play and will play eventually though audio isn't working, videos from previous versions play fine, it's possible that other camera apps don't have this)
3. Gcam not working (use urnyx05's gcam v2.1, works fine on both 9 & 10)
4. Interactive governor is maxing the CPU (gave a decent boost in battery in 16.0)
5. Powersave governor can freeze the camera when in video mode/recording (use default governor)
6. Lockscreen pin is slow on boot (just wait a little it will unlock)
7. Brightness slider still needs adjusting (Turn off autobrightness and use values between 70-90% for decent indoor screen brightness)
8. Google Play downloads can be slow regardless of GApps package and when on wifi/mobile data (Been happening to me since 15.1 and only happens to some, just pause and resume a few seconds later is the workaround I do)
9. Audio files can take a while to load when switching between audio sources like wired & wireless headphones (no workaround will began playing in a bit)
thanks a lot:victory::victory:
Sent from my LG-H830 using XDA Labs
inhave a solution delete lineagesetupprebuilt from twrp and setup will succed lineage setup is causing problem....
delete system/priv-apps/lineagesetupprebuilt...
Ismrocks1234 said:
inhave a solution delete lineagesetupprebuilt from twrp and setup will succed lineage setup is causing problem....
delete system/priv-apps/lineagesetupprebuilt...
Click to expand...
Click to collapse
You can delete every system and user app in OrangeFox recovery.
Sent from my LGE LG-H850 using XDA Labs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Nightly
Created 2020-02-08
Last Updated 2020-05-06
My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
Using TWRP 3.3.1-z3c-20191212-sar from here
Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
About 700MB of RAM free just after boot, with stock launcher.
Battery drain fast, but my battery is very old, no complain.
Pros:
+ reliably fast
+ everything works including GPS, BT, calls/data, hotspot and all my apps
+ no problems with audio routing and mic sensitivity
+ camera is ok but I use OpenCamera anyway
Cons/bugs:
- still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
- ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
- broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
- ringtone sound become a bit quieter after half a second from start of incoming call
- overall loudspeakers volume is not loud enough
Features I'd like to have in this ROM:
1) choose clock position in statusbar (only at left in CR8.0)
2) brightness control by sliding in statusbar without opening it
3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
6) restrict/disable power menu while phone locked
7) disable notification panel while phone locked
8) set minimal time between notifications on per app basis
9) wake by volume rocker buttons
10) increasing ringing volume
11) debugging over network (settings in devs options, absent in CR)
Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.
Thank you @Myself5 for continue work with our lovely z3c.
Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.
Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1
Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.
yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.
New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.
Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip
Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..
Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?
the "cant connect to the camera" returned unexpectedly..
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works
Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:
okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.
[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now
lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !
[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo
Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.
Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.
mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse
&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.
@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD
Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
reserved
reserved
What is different between this build and your previous one ?
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.
builds have been removed from the lineage os website?
Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week
Does the build support hardware encryption or software encryption?
You should put what models this is for as to avoid confusion
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine
Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with
Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else
Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!