{
"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-15.1 for LG G6 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 us997 variant for testing, so other variants might have some issues.
Known items
VoLTE and WiFi calling do not work yet
Other known issues (same as OFFICIAL too):
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
5Ghz tether not working due to "error"
Install
You can upgrade from 14.1 (UNOFFICIAL) to 15.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
Flash to-x86cpu.zip if you want. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
Reboot and wait....
Notes
To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
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 have a us997 variant for testing. 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.
Please indicate what g6 variant you have (h870, h872, us997) and what you are running (OFFICIAL or UNOFFICIAL) and date. 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
Downloads
ROM: UNOFFICIAL downloads (Note date and variant)
Gapps: arm64 nano 8.1
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_g6-common
h870
h872
us997
What is not working or problematic
What is not working or still wonky:
Encryption -- Works.
USB OTG -- Should be working.
Ambient display -- Disabled now.
Livedisplay -- Should be working.
IR will work, then timeout, then work again.
Video recording -- Should be working. Works sometimes, appears to record, but playing back audio is at the beginning, video at the end, and the duration is messed up.
5g tether -- Not working still.
No FM driver.
TBD
Thank you for making this! Waiting for a list of working/non-working feature before install.
Bugs on H870:
* Preferred network type in default is WCDMA
* Data isn't working on LTE
* Blackscreen issues
Wysłane z mojego LG-h870 przy użyciu Tapatalka
dom133 said:
Bugs on H870:
* Preferred network type in default is WCDMA
* Data isn't working on LTE
* Blackscreen issues
Wysłane z mojego LG-h870 przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you able to change preferred network time to get to working? What's the blackscreen issue?
x86cpu said:
Are you able to change preferred network time to get to working? What's the blackscreen issue?
Click to expand...
Click to collapse
I can change preferred network to GSM/WCDMA/LTE but lte isn't working. Screen some time is going black and after second is back to normal
Wysłane z mojego LG-h870 przy użyciu Tapatalka
x86cpu said:
Are you able to change preferred network time to get to working? What's the blackscreen issue?
Click to expand...
Click to collapse
If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:
https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40
I've got that reverted on my builds.
natemckn said:
If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:
https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40
I've got that reverted on my builds.
Click to expand...
Click to collapse
Thanks, I'll have to check into that. Unfortunately, I cannot revert it on Lineage builds, the kernel is the same for g5/g6/v20, and this works good for the v20. Does anyone have logcat's and more specifically dmesg output from this occuring?
natemckn said:
If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:
https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40
I've got that reverted on my builds.
Click to expand...
Click to collapse
The black screen I had with your build seemed to happen after the screen would lock up, it would flash black quick, in place of what you would expect the ROM to go back to bootanim during a soft crash.
Other times, harder to explain, but basically turning the screen on, off, on too fast would result in it acting like the screen was on, but it would be off. Slowing down the same process would restore it.
It is possible the first half was the system mis-recognizing a pinch touch but I don't think thats quite it. Sadly, I didn't think to look at dmesg/logcat, and I'm back on stock-based for the moment. Even then probably going the treble/GSI route. But I'll try to help where I can.
zefie said:
The black screen I had with your build seemed to happen after the screen would lock up, it would flash black quick, in place of what you would expect the ROM to go back to bootanim during a soft crash.
Other times, harder to explain, but basically turning the screen on, off, on too fast would result in it acting like the screen was on, but it would be off. Slowing down the same process would restore it.
It is possible the first half was the system mis-recognizing a pinch touch but I don't think thats quite it. Sadly, I didn't think to look at dmesg/logcat, and I'm back on stock-based for the moment. Even then probably going the treble/GSI route. But I'll try to help where I can.
Click to expand...
Click to collapse
The plan is getting Lineage OS 15.1 to treble too..... Thanks, still looking into it.
x86cpu said:
Thanks, I'll have to check into that. Unfortunately, I cannot revert it on Lineage builds, the kernel is the same for g5/g6/v20, and this works good for the v20. Does anyone have logcat's and more specifically dmesg output from this occuring?
Click to expand...
Click to collapse
I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:
https://hastebin.com/awuhonuzum.vbs
natemckn said:
I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:
https://hastebin.com/awuhonuzum.vbs
Click to expand...
Click to collapse
Yeah, I checked and this was supposed to fix it: https://github.com/LineageOS/androi...mmit/09ae5fbb4f3c69146ef022914f0f789133c57c78
I see, there's new firmware for the touch that might help and it not in Lineage, but it in in LG's Oreo... or it could make touch not work either, I'll try to get a build and see if anyone might be willing to flash it to see it if helps to fix it.
x86cpu said:
Yeah, I checked and this was supposed to fix it: https://github.com/LineageOS/androi...mmit/09ae5fbb4f3c69146ef022914f0f789133c57c78
I see, there's new firmware for the touch that might help and it not in Lineage, but it in in LG's Oreo... or it could make touch not work either, I'll try to get a build and see if anyone might be willing to flash it to see it if helps to fix it.
Click to expand...
Click to collapse
Yeah Rashed pointed to that same commit, but it wasn't the answer for me. Before that commit, the screen would go black randomly when just scrolling through stuff which was super annoying. After that commit, the scrolling/random black screen was fixed but I still had the pinch to zoom black screen issue. The dmesg I got was from a build I did on 4/29 that did have that commit.
natemckn said:
I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:
https://hastebin.com/awuhonuzum.vbs
Click to expand...
Click to collapse
dmesg was helpful, make some kernel adjustments that affect that area, so new builds incoming. BUT.. it might cause no-touch at all. It might fix the black screen. It'd be helpful to know. I usually test myself, but have no G6 (if you know where to get a us997 boot-loader unlocked cheaply .. even screen cracked, let me know).
lineage-15.1-20180513-UNOFFICIAL
New build, but a warning, this has firmware updates and kernel update for touch screen. Hopefully to resolve the back screen issue. If someone can try and if it fails, please grab as much dmesg as possible. You might also loss touch screen, so be prepared to adb in, and reboot to recovery if needed to go back. Thanks.
x86cpu said:
New build, but a warning, this has firmware updates and kernel update for touch screen. Hopefully to resolve the back screen issue. If someone can try and if it fails, please grab as much dmesg as possible. You might also loss touch screen, so be prepared to adb in, and reboot to recovery if needed to go back. Thanks.
Click to expand...
Click to collapse
https://hastebin.com/uvogumamin.vbs
I flashed your 0513 build and can still replicate the screen going black when i pinch to zoom.
Also the colors are washed out which I think means you need these:
https://review.lineageos.org/q/topic:"hdr-extra"+(status:open OR status:merged)
natemckn said:
https://hastebin.com/uvogumamin.vbs
I flashed your 0513 build and can still replicate the screen going black when i pinch to zoom.
Also the colors are washed out which I think means you need these:
https://review.lineageos.org/q/topic:"hdr-extra"+(status:open OR status:merged)
Click to expand...
Click to collapse
Thanks, the g6 I believe I have, the qcom one may not get applied, I sometimes wait on them figuring things out. I see the dmesg, some errors have changed. Any way to try to get a dmesg sooner, more specifically when it loads the firmware? ( img references) ? Thanks.
all camera works fine ? and what about bluetooth speaker, is too good ?
lineage-15.1-20180620-UNOFFICIAL
lineage-15.1-20180620-UNOFFICIAL
New build up. I believe almost everything is in working order. Anyone please test and report.
Related
OmniROM is a free, community built, aftermarket firmware, which is designed to increase performance, reliability and features over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/
OmniROM 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.
Features
0. Nearly all from OmniROM and KitKat
1. Nearly everything works. Headphone detection, accurate touchscreen, microphone, GPS (no reboot required)...
2. Capacitive keys on the top of screen. (Outside of display area)
In the upperleft corner of screen is Back key,closely beside it is Home key. The upperright corner is Menu key. As the picture shows:
{
"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"
}
Enabled keys can be changed in /system/etc/init.d/01touckeys . Values are described in that file.
0 - disable keys
1 - enable menu key only
2 - enable home, back and menu keys
Click to expand...
Click to collapse
3. Dual-boot support built-in. See this thread.
4. More to be seen
Source:
OmniROM system : GitHub
Kernel for this ROM : GitHub and DooMLoRD's https://github.com/DooMLoRD/android_kernel_sony_msm8960
Device repo : GitHub
Vendor repo is on the same GitHub account
Official OmniROM Wiki:
http://docs.omnirom.org
First time installing OmniROM to your Xperia TX, or coming from another ROM:
- Read known issues and FAQs
- Copy GApps and OmniROM ZIPs to your SDCard
- Flash the kernel in the zip first using fastboot
- Reboot into Recovery
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM ZIP to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Issues:
1. Some camera settings such as ISO, HDR are missing. Can't be set even via 3rd-party apps.
2. Sometimes there are pops when playing music.
3. Contacts and SMS on SIM card can't be read. Try this patch. http://forum.xda-developers.com/showpost.php?p=52938188&postcount=35 Note that this patch will cause mobile data to stop working on DC-HSPA+ networks
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
Download:
20141018
http://pan.baidu.com/s/1eQEKJmE
ART Fix(put into /system/lib): http://pan.baidu.com/s/1c0y9N1m
OLD BUILDS:
20140930
http://pan.baidu.com/s/1mg2wSze
Mirrors by Antiga Prime. Thanks as always!
http://www.mediafire.com/download/hibbcc1hfzvvpyc/omni-4.4.4-20140930-hayabusa-HOMEMADE.zip
https://mega.co.nz/#!A5pF2TJS!hd5zapnUlKNoe9RXrea8ZYG0Yx_2c3VNfEdmRvYohnU
20140912
http://pan.baidu.com/s/1pJNoXez
Mirror by Antiga Prime. Thanks!
http://www.mediafire.com/download/5293r997upi1kvu/omni-4.4.4-20140912-hayabusa-HOMEMADE.zip
https://mega.co.nz/#!lkhDXYRY!WxUyzN6WJ1yucGGOV5Tm16M8qK-Y2D6R6YUaF2RuRoM
20140812
http://pan.baidu.com/s/1c0CfQk4
Mirror: http://uploaded.net/file/kxjx635q
The following mirrors are provided by Antiga Prime. Thanks!:
https://mega.co.nz/#!xlBgjRhR!qQ8QMiQTB39sUhYiPIdMq5_MbvxgvtWN-luv8_VFHbw
http://www.mediafire.com/download/gayu2nqdysm1og5/omni-4.4.4-20140812-hayabusa-HOMEMADE.zip
20140622
http://pan.baidu.com/s/11sXdW
Camera settings fix (put to /system/lib/hw): http://pan.baidu.com/s/1hqstoUC
Mirror by Antiga Prime. This link includes the camera fix already.: http://www.mediafire.com/download/5l...a-HOMEMADE.zip
20140619
http://pan.baidu.com/s/1i37QmQp
20140607
http://yun.baidu.com/s/1bnaSoGn
Kernel update: http://pan.baidu.com/s/1qW38gm4 (contains an ELF file. Fastboot it. Then extract the lights.qcom.so to /system/vendor/lib/hw, replace the original file)
Kernel modules: http://pan.baidu.com/s/1qWlrgvE (extract this to /system/lib/modules)
20140531 (published 20140601)
http://pan.baidu.com/s/1kToOReZ
(Mirror by Antiga Prime, thanks!) http://www.mediafire.com/download/q0t0qdv5dx8pzdz/omni-4.4.2-20140531-hayabusa-HOMEMADE.zip
20140518
http://pan.baidu.com/s/1o6I3ZJW
http://www.mediafire.com/download/tlb7i296kpwb65f/omni-4.4.2-20140518-hayabusa-HOMEMADE.zip
The mediafire mirror is provided by Antiga Prime. Thanks!
This is a clean build. No promotion app, no integrated root app, no stat app.
All the patches before have been merged into this build.
Just one new feature: kexec hardboot / dual-boot . More on this later...(much later since finals are coming)
NOTE: Not pre-rooted. Flash SuperSU if you need root.
Changelog:
20141018
Fix the bug that cause SIM_IO fail. Now SIM contacts, mesaages, my phone number, voicemail number etc are all working. DC-HSPA+ is working too.
TrueType fonts are supported in TWRP, with anti-aliasing feature.
Used JustArchi's optimization (http://forum.xda-developers.com/showthread.php?t=2754997) THANKS!
Dialler supports T9 in Chinese and some other languages
20140930
Native support for tinted status bar
20140912
Update Adreno drivers from Xperia Z (2014/03)
MTP support in Recovery, but not working...disable it in Mount menu
(Upstream fix) Reduced SystemUI FCs (This fix is more important than others...)
20140812
Hopefully fix audio glitch when screen is off (Don't keep too many programs running in background)
WiFi MAC address is the phone's actual address
Vibrator intensity setting in Settings > Advanced
Screenshot in Recovery available (Pwr+Vol Down, check console for detail)
Brightness adjustment and screen timeout in Recovery work
20140622
Android 4.4.4
20140619
intergrated pulsing Xperia logo light (if you don't like it, replace /system/vendor/lib/hw/lights.qcom.so with the one from previous builds)
lags when playing music offscreen possibly fixed (upstream)
ISO, HDR etc is adjustable with Camera FV-5 or anything like that
20140607
Android 4.4.3
nearly nothing else...
How come I forget to edit the title...
added Xperia logo as "breathing light" (how shall I express this in English?)
possibly fixed lags when playing music offscreen (echo 0 > /sys/module/auto_hotplug/parameters/allow_suspend_offlining , can be added as init.d script)
20140531 (published 20140601)
possibly fixed the LED misbehavior (not tested on Email app...)
possibly fixed time being reset on (re)boot and not syncing with network
fixed: Performance Control only changes the governor and frequency of only one CPU core
new: some features by DooMLoRD. Original thread is here http://forum.xda-developers.com/showthread.php?t=2170580 .As for the source, look at the "source" section above.
new: distinguish HSPA+ and DC-HSPA+ (QuickSettings tile, statusbar icon and phone status screen) Cherry-picked from OmniROM gerrit.
Questions:
Feel free to post here
Credits:
OmniROM team
tilal6991 for porting 4.3 kernel source for OmniROM (His original thread for Xperia T is here)
DooMLoRD for awesome kernel features
Sony
and a lot more who did tests and so on... Thank you all!
To Kangers:
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open Source doesn't mean Out of Respect!
@updateing
It's tilal6991
Not tital
=)
Yenkazu said:
@updateing
It's tilal6991
Not tital
=)
Click to expand...
Click to collapse
Oops my fault. Corrected now
Is this build different than the build you posted in the Kexec thread?
In any case, I can confirm that the annoying WiFi battery drain is fixed on that build.:good:
Antiga Prime said:
Is this build different than the build you posted in the Kexec thread?
In any case, I can confirm that the annoying WiFi battery drain is fixed on that build.:good:
Click to expand...
Click to collapse
Yes. And this one is a little bit newer...
Amazing work bro, keep the awesome post
awesome work !!!! anyone tried it yet?
New clean build arrived.
ravijokhun said:
awesome work !!!! anyone tried it yet?
Click to expand...
Click to collapse
I'm using the first build @updateing put out in the Kexec thread. Considering the fact that I sort of dislike any type of stock ROM, and this ROM has been working flawlessly, i.e., no random reboots, camera works, vibration works, calling works, even while on loudspeaker (haven't noticed any whistling yet, but then again, I never had that problem so...), I don't see a reason to ever go back to a stock Sony ROM; and I'm assuming the new build probably behaves the same.
It just feels so much better to have an operating system that has everything working off a 200mb installation zip, when compared to the near 700mb of a Sony stock ROM.
updateing said:
Finally there is a stable KitKat ROM for our TX...Thanks OmniROM team and tilal6991! I made some small adjustments to make OmniROM run on TX and (re)ported the kernel source from 9.2.A.0.295. Most of the work is done by tilal. Original thread for Xperia T is here.
Click to expand...
Click to collapse
Hi, is for unlocked bootloader?
augustox said:
Hi, is for unlocked bootloader?
Click to expand...
Click to collapse
Yes.
Does Anyone know how to change DPI Settings to get Smaller Icons?
ravijokhun said:
Does Anyone know how to change DPI Settings to get Smaller Icons?
Click to expand...
Click to collapse
Edit build.prop in /system:
ro.sf.lcd_density=number (default is 320)
I use 280
augustox said:
Hi, is for unlocked bootloader?
Click to expand...
Click to collapse
yes
matt4321 said:
yes
Click to expand...
Click to collapse
Thanks. I have locked bootloader :/
Is it me or this ROM feels really smooth.
Will provide feedback as time goes
Sent from my Xperia TX using Tapatalk
I noticed something weird with the notification light behavior...
Lets say the mobile is charging, giving a yellow led and whenever you get a mail, message, whatsapp or watever, the notification blinks white (quite normal) and yellow is off
After clearing the notifications, i loose the charging led...meaning it does not get the yellow light back on...even if charger is unplugged and plugged back again, notification light for charging does not light up..
Anyone experienced the same?
ravijokhun said:
I noticed something weird with the notification light behavior...
Lets say the mobile is charging, giving a yellow led and whenever you get a mail, message, whatsapp or watever, the notification blinks white (quite normal) and yellow is off
After clearing the notifications, i loose the charging led...meaning it does not get the yellow light back on...even if charger is unplugged and plugged back again, notification light for charging does not light up..
Anyone experienced the same?
Click to expand...
Click to collapse
It's only you. It's working fine on my phone.
On the other hand, I let my battery die, and when I connected my phone to the charger while off, I expected to see the charging screen, except that the screen stayed dark with the Sony logo lit up, and when I pressed the power button to turn on the screen, it had actually booted up to Android, showing a "system is not responding" message, and then shutdown due to low battery, as expected. I think there might be something wrong with charging while off.
The good news is the battery still charges while in TWRP, so I just left it there for two minutes then turned it back on.
about the out screen capacitive buttons
I am curious about the out of the screen capacitive buttons on XTX. is there any way to use them in 4.3 roms or is there any patch ??
coz in opening post it said there is a patch in download section but I am not seeing any :crying:
please let me know . I am very much astonished to know about these buttons and eager to use em
Antiga Prime said:
It's only you. It's working fine on my phone.
On the other hand, I let my battery die, and when I connected my phone to the charger while off, I expected to see the charging screen, except that the screen stayed dark with the Sony logo lit up, and when I pressed the power button to turn on the screen, it had actually booted up to Android, showing a "system is not responding" message, and then shutdown due to low battery, as expected. I think there might be something wrong with charging while off.
The good news is the battery still charges while in TWRP, so I just left it there for two minutes then turned it back on.
Click to expand...
Click to collapse
These problems do exist. I'll look into this...
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About this Q&A thread for CyanogenMod 13.0
Use this area to ask anything you want related to CM-13.0,
but try not to spam everyone, always search for an answer before.
General Questions & Answers
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes completely. Nightlies and OpenGApps recommended.
Can I flash CyanogenMod NIGHTLY and UNOFFICIAL without wipes ?
Yes you can.
Should I flash SNAPSHOT builds when I'm on NIGHTLY ?
No, the Nightlies are already more up to date.
You can flash SNAPSHOT builds when you don't want to update often.
Is the device encryption supported ?
Yes it is, but if you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Marshmallow,
due to a stronger security logic regarding unauthorized data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
Nightlies before the 4th June 2016 suffered from an incomplete CyanogenRecovery image,
therefore the recovery fails to starts, the display fades out and the device reboots.
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Against advices, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not ok, try this : CM Wiki
If still not, then I advise a clean factory-reset reinstallation...
Does anyone know a way (or an App) to get back the quick start function while long pressing the home button? I really miss it.
Hey Adrian, ty for all you hard work on the XSP. I just wanna know if there is a way to fix High Touch Sensitivity. On both cm 12.1 and cm13 it keeps turning off after some time of usage.
Is there a problem if I use nano Gapps instead of Micro or pico?
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Everything seems to work fine on build 20162903. The only things that need fixing (so far), for me, are the lackluster gaming performance and the Duolingo app not registering when I talk to it (it worked fine on stock) even if it has the permissions to use the microphone.
Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
I had a similar problem, maybe you hit the same cm upgrade bug as I did. I solved it without loss of data as described here:
http://forum.xda-developers.com/showpost.php?p=66101184&postcount=5
juliomb179 said:
Is there a problem if I use nano Gapps instead of Micro or pico?
Click to expand...
Click to collapse
should be fine ....but u can try for sure and report back
Ungewiss said:
I had a similar problem, maybe you hit the same cm upgrade bug as I did. I solved it without loss of data as described here:
http://forum.xda-developers.com/showpost.php?p=66101184&postcount=5
Click to expand...
Click to collapse
Maybe, but I did a clean install :I
flash- said:
should be fine ....but u can try for sure and report back
Click to expand...
Click to collapse
I'm on Delta Gapps base (0323) for marshmallow , no problem... :good:
Adrian, ty for all your hard work on the Relaese.
With the last Version cm-13.0-20160329 it works nice (before alot of Loop´s)
1 point of Question.
SP. MHL - HDMI OUT - now its works (perfect) only in 720p.
is there any posibility to get it work on 1080p ?
like here : xxxx//xxx.3g.co.uk/PR/March2014/how-to-connect-sony-xperia-mobile-devices-to-a-tv.html
THX alot
PIT
Krawzer said:
Hey Adrian, ty for all you hard work on the XSP. I just wanna know if there is a way to fix High Touch Sensitivity. On both cm 12.1 and cm13 it keeps turning off after some time of usage.
Click to expand...
Click to collapse
Has been fixed since my Glove Mode service, can't see how you still have the issue,
nobody reported anything related to that since the improvement.
http://review.cyanogenmod.org/#/c/117930/ (November )
Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
First time reported or heard off, might be something wrong with an app or mod you used, I don't know.
pitps said:
SP. MHL - HDMI OUT - now its works (perfect) only in 720p.
is there any posibility to get it work on 1080p ?
like here : xxxx//xxx.3g.co.uk/PR/March2014/how-to-connect-sony-xperia-mobile-devices-to-a-tv.html
Click to expand...
Click to collapse
1080p should be broken in 12.1 & 13.0, it is known but hasn't been fixed since,
but obviously there are more important things to look at for the moment.
Adrian DC said:
Has been fixed since my Glove Mode service, can't see how you still have the issue,
nobody reported anything related to that since the improvement.
http://review.cyanogenmod.org/#/c/117930/ (November )
Click to expand...
Click to collapse
well this is strange , I have this problem with every recent build of any ROM, cm13 or cm12.1
Can I use open gapps aroma with this version?
Sent from my Xperia SP using Tapatalk
Krawzer said:
well this is strange , I have this problem with every recent build of any ROM, cm13 or cm12.1
Click to expand...
Click to collapse
same here
joaovitorgirotto said:
Can I use open gapps aroma with this version?
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
I think so, I am using them right now and I don't have any bugs.
Adrian DC said:
Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
First time reported or heard off, might be something wrong with an app or mod you used, I don't know.
Click to expand...
Click to collapse
No way, I wasn't installing any app that requires root, no Xposed or something like that, so it's impossible.
I updated from cm12.1 unofficial build .
Everything is great, but i noticed two issues:
I set priority mode for next 4 hours, but it was active after 4 hour , and i couldn't even deactivate it manually. Restart solved the problem.
It happened one time so i couldn't take log.
Another one is audio glitch when I'm listening music with the cm music player. With musixmach it's OK.
Sent from my Xperia SP using Tapatalk
mrskyou said:
I'm on Delta Gapps base (0323) for marshmallow , no problem... :good:
Click to expand...
Click to collapse
i'm always on delta since cm12.1 ....but i just told him to report back for other users...but thanks for the tip
how's the game performance in this rom?Is the clash of clan running smooth ?
[FunTalks] I don't know about that, but me who really never plays games at all since years,
I have Rayman Adventures & Clash Royale working great . [/FunTalks]
Latest update (8/13): I've been busy recently and haven't had the time or motivation to spend much time on this. Personally, I flashed over to x86cpu's builds (https://forum.xda-developers.com/lg-...lg-g6-t3789468) as they're almost the same as what I was building anyway and he definitely knows what he's doing more than I do. If you decide to move from mine to his, make sure to flash the "to-x86" conversion zip, as his are signed differently and will corrupt your data if you flash directly over mine. Feel free to use my old builds if you want, I'll keep the thread and download links up for now in case I decide to resume development at some point in the future. Thanks for the support, it was fun, hopefully 15.1 for G6 goes official soon
{
"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"
}
DisclaimerYour 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.
Project descriptionLineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
With the help of many in the Telegram channel, I have build LOS 15.1 from source for the US997.
I’ve been using these builds for a few weeks and have been happier than when I was using 14.1 official builds, but of course your mileage may vary.
How to install:
Wipe Data/Factory reset.
Format System.
If you're coming from stock Oreo, flash the nougat bootloader or fingerprint won't work on this ROM
Flash the ROM.
Flash 8.1 Gapps.
(Optional) Flash root method of choice. (As of 0325, you can use magisk, superSU or other root methods)
Known Bugs:
5 GHz Wi-Fi hotspot broken
4K video recording broken
Always on display doesn't use the low power screen - it will drain battery quickly when its on
USB MTP (file transfer) is broken (it works in recovery so you can switch to that to copy file if needed) **
VoLTE broken
Encryption - Reports that enabling encryption leads to bootloops - Needs further testing
CDMA on Verizon must make call out after reboot in order to have incoming calls/txt working
Poor mic quality when using speakerphone
Possibly more
Working Features:
Oreo 8.1 with June security update
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth playback and mic (I made a call successfully and until proven otherwise, it seems the BT mic issues are isolated to H870 and does not affect US997)
NFC
GPS
Camera, including Gcam, and wide cam in apps that support it like the built-in LOS Snap cam and Open Camera (except 4k video recording)
Video Playback (L1/HD DRM playback working, unlike 14.1)
Audio (Audio levels have been tweaked but may still need further adjusting)
Fingerprint (currently only works on Nougat bootloader)
Flash
Quick charging (PD and QC and wireless chargers)
Off-mode charging (plugging the phone in when its off/dead properly boots into charging only mode)
SD cards including exfat
No CPU stuttering bug like 14.1 has
Downloads:The ROM - lineage-15.1-20180618-NateVM-UNOFFICIAL-us997.zip changelog
https://www.androidfilehost.com/?fid=962339331459001292
md5: d97392e7f7b9f91cce760ee572483d5b
Older versions available here
**Modded TWRP recovery - recovery_melina-TWRP_v3.2.1_18-03-10_NateVM_LGUS997_CacheAsVendor_rel1.img
ecb5f0a062bd26e87eaa0e206ec71d6e
**As of 0325, this is unneeded and likely to cause different issues, use any other us997 compatible recovery.
http://opengapps.org - ARM64
CStark27’s GCam mod recommended (and supports wide angle)
**Fixed in 0618 release
Screenshots:https://imgur.com/a/2T7pd
Credits:
Lineage OS team
Rashed97 and x86cpu, the official LOS maintainers
EvilHowl
Rc420Head
J0SH1X
CPL593h
Imaginovskiy
Zefie
And everyone else in Telegram helping test builds and report bugs
About Me:
I am very much a newb at ROM building. I've been using CM/LOS for years and one of the main reasons I bought the us997 was that it is "officially" supported by LOS. But I was disappointed to find that the official 14.1 builds for G6 had some major issues (like CPU performance) and after using it for a few months it felt like I took a big step backwards when I upgraded from my Nexus 5x. So I started searching around to see if anyone had been able to fix those issues and found Evilhowl's unofficial H870 14.1 builds had CPU performance fixed. Since nobody seemed to care about building a version for us997, in January I took it upon myself to attempt to learn how to compile the ROM myself.
While learning how to do my first build, Evilhowl and others in telegram started making some breakthroughs on getting 15.1 builds to run. Since I was attempting to build from source anyway, I decided to see if I could build LOS 15.1. After many attempts of trial and error, I got 15.1 to build and worked with the H870 guys to get some additional fixes merged. By cherry-picking specific fixes from h870 and other devices on the LOS gerrit, I got a ROM that I'm happier with than the 14.1 official release.
Since I've been using this ROM as my daily driver for a few weeks and multiple people in telegram had been asking about it, I figured I would post it here on xda to share once I got everything uploaded to github. I'll do my best to keep the list of features/bugs in this post up to date, and I'll see what I can do to try to fix some of the things, but since I'm still quite new at this, I can't promises I'll actually be able to fix much myself. If anyone has any clues or potential fixes from other devices that may help fix any of the known bugs, please let me know. I'm just hoping some things get fixed upstream by the LOS team or some of the H870 devs figure out a fix and I can copy stuff from them.
LineageOS 15.1 unofficial, ROM for the US997 LG G6
Source Code: https://github.com/natemckn/android_kernel_lge_msm8996/
https://github.com/natemckn/android_device_lge_msm8996-common/
https://github.com/natemckn/android_device_lge_g6-common/
https://github.com/natemckn/android_device_lge_us997/
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.18.102
Based On: LineageOS 15.1
Version Information
Latest Version: lineage-15.1-20180618
Created 2018-03-11
Last Updated 2018-06-18
FAQ
Q. First time setup wizard crashes:
A. Get latest official gapps from opengapps.org. Older unofficial gapps are known to crash setup wizard.
Q. All the H870 Oreo releases talk about flashing a kernel after the ROM, do I do that here?
A. Everything is in the built in kernel now.
Q. Wifi and/or BT don't work! In about system, mac address shows as all 0s
A. You wiped your /misc which overwrote your mac address. Other LG devices have been able to fix this with the follow procedure, but I have not tested it on G6: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
Q. How do I know if I'm using your old modded recovery? You're dumb for not making any interface changes to identify it!
A. You're right, in hindsight that was dumb to release a modded version with no distinguishing features. Go to the Mount menu in TWRP. Look for "Cache" or "Vendor". If your TWRP version shows "Vendor" then you have my old modded one, switch to a different TWRP in order for any new builds to flash properly. If your TWRP version shows "Cache" as a mountable partition then you have a normal good recovery
Q. Fingerprint doesn't work! The option is missing from the menus
A. This ROM assumes you have the Nougat baseband/firmware since we were working on this before Oreo became available. If you updated to stock Oreo prior to flashing this ROM, then you have the Oreo baseband/firmware, which is known to break fingerprint. The only fix right now is to flash back to Nougat baseband in order for this ROM to work properly. You can flash the 17A (Nougat) baseband from here:
https://files.persona.cc/zefie/files/cell/LGG6/US997/ROMs/bootloader-only/
Using the US997 , updated today but phone wont charge while on, i have to charge in twrp, any idea? last version was fine.
Raidel™ said:
Using the US997 , updated today but phone wont charge while on, i have to charge in twrp, any idea? last version was fine.
Click to expand...
Click to collapse
I noticed when I first switched to this type of build my battery stats were really messed up for a bit and when I plugged it in it wouldn't act like it was charging. After using it for a few hours and doing a restart, I noticed the started working correctly again and when I plugged it in it charged as normal and has worked fine since. So I think give it a few hours and a restart or two to re-calibrate and see if it starts charging?
I see you already edited OP, but just wanted to document that SuperSU does not work in this version. Is the link for the last version still up somewhere? Specifically for US997?
sc4s2cg said:
I see you already edited OP, but just wanted to document that SuperSU does not work in this version. Is the link for the last version still up somewhere? Specifically for US997?
Click to expand...
Click to collapse
Here's the download link for the last no treble build I did from a few weeks ago:
https://www.androidfilehost.com/?fid=673956719939826837
natemckn said:
Here's the download link for the last no treble build I did from a few weeks ago:
https://www.androidfilehost.com/?fid=673956719939826837
Click to expand...
Click to collapse
Thanks!
Couple things to report on the build in OP for US997: booting up goes straight to bootloop unless I manually go to twrp and make it do a system reboot from there. So far that method worked 1/3 times. When it doesn't work it goes into a bootloop once and then just turns off. Also, it might be turning off at random times (turned off during class while charging) and if I try to turn it back on it says that it doesn't enough power to boot. Plugging it into a charger will let it turn on (again, into a bootloop until I go to twrp manually) and once in the OS it showed 75% battery level.
sc4s2cg said:
Thanks!
Couple things to report on the build in OP for US997: booting up goes straight to bootloop unless I manually go to twrp and make it do a system reboot from there. So far that method worked 1/3 times. When it doesn't work it goes into a bootloop once and then just turns off. Also, it might be turning off at random times (turned off during class while charging) and if I try to turn it back on it says that it doesn't enough power to boot. Plugging it into a charger will let it turn on (again, into a bootloop until I go to twrp manually) and once in the OS it showed 75% battery level.
Click to expand...
Click to collapse
Damn, sorry that its not working for you. I did a couple wipe and flash tests over the weekend to make sure things were working as expected before posting here and I never had a problem getting it to boot (except when I tried Magisk). I did notice some battery stat weirdness for a while but it went back to working normally and charging normally after about an hour and a reboot and hasn't been a problem for me since.
Can you try the 0208-noTreble build linked to see if the same problems happen there, or if its related to the experimental changes that were added since then?
natemckn said:
Damn, sorry that its not working for you. I did a couple wipe and flash tests over the weekend to make sure things were working as expected before posting here and I never had a problem getting it to boot (except when I tried Magisk). I did notice some battery stat weirdness for a while but it went back to working normally and charging normally after about an hour and a reboot and hasn't been a problem for me since.
Can you try the 0208-noTreble build linked to see if the same problems happen there, or if its related to the experimental changes that were added since then?
Click to expand...
Click to collapse
Actually I've been using the February version for a couple weeks with no major issues, just some minor bugs like sometimes the screen turns on blank (just turn off and on again) and the touchscreen is not responsive if the phone turns off b/c of battery levels (just reboot again).
sc4s2cg said:
Actually I've been using the February version for a couple weeks with no major issues, just some minor bugs like sometimes the screen turns on blank (just turn off and on again) and the touchscreen is not responsive if the phone turns off b/c of battery levels (just reboot again).
Click to expand...
Click to collapse
Same boat here; been using the 2/8 build for a while with no major issues. Wasn't able to get the new build to boot yesterday, but now that I know there's an extra step or two I'm going to try flashing the new build again sometime this week.
OK, I've got a lead on the battery weirdness. It seems that every time you boot into this recovery, it does something to the battery stats, so when you boot into system it bugs, and for me appears stuck at 50%. A single reboot seems to fix it (until you go into recovery again). I'll poke around the recovery some more to see if I can get that fixed since I'm pretty sure its a result of something I did.
What bugs are fixed in this new build compared to the Feb build?
Thanks again for bringing 8.1 to the us997. Be awesome if u or somebody else capable got the time to build a ResRemix Oreo for us997
So, oddly enough I wasn't having any issues with battery weirdness (I've been using the latest build for about 5 hours now) but wireless charging doesn't seem to work; the phone goes from charging to not charging on a second-to-second basis. Charging via cable seems to be working fine. Also, not sure if this is a Modded Gcam specific issue, but it seems like accessing the front facing camera causes crashes.
BigBrad75 said:
What bugs are fixed in this new build compared to the Feb build?
Thanks again for bringing 8.1 to the us997. Be awesome if u or somebody else capable got the time to build a ResRemix Oreo for us997
Click to expand...
Click to collapse
Changes in 0311 build:
offmode charging fixed
broke camera, then fixed it again
updated graphics blobs. feels smoother, but might be placebo since benchmarks are the same
fixed time sync bug
encryption is enabled, but I have no clue if it works
merged a bunch of experimental treble stuff Rashed posted on gerrit
some haptics related fixes
march security patch
upstream stuff from LOS, too much to list
KaLiBLeeK said:
So, oddly enough I wasn't having any issues with battery weirdness (I've been using the latest build for about 5 hours now) but wireless charging doesn't seem to work; the phone goes from charging to not charging on a second-to-second basis. Charging via cable seems to be working fine. Also, not sure if this is a Modded Gcam specific issue, but it seems like accessing the front facing camera causes crashes.
Click to expand...
Click to collapse
I guess wireless charging is broken, so I put it in OP as known bug. I don't have a charging pad to test with. Can you grab a logcat when its happening? Maybe that'll give a hint as to whats broken.
natemckn said:
I guess wireless charging is broken, so I put it in OP as known bug. I don't have a charging pad to test with. Can you grab a logcat when its happening? Maybe that'll give a hint as to whats broken.
Click to expand...
Click to collapse
I've attached a partial LOGCAT here. Let me know if there's enough information here to work with, or if I should pull another.
does it support exfat tf card？
VoLTE? pls? sir?
ErickG233 said:
does it support exfat tf card？
Click to expand...
Click to collapse
Not sure. If you test it let me know and i'll update op.
Anyone have a link to the 14.1 LOS SU addon? Tried to find on XDA but couldn't. As listed, SuperSu lets me boot back into system, but not installed or rooted.
Sobek5150 said:
Anyone have a link to the 14.1 LOS SU addon? Tried to find on XDA but couldn't. As listed, SuperSu lets me boot back into system, but not installed or rooted.
Click to expand...
Click to collapse
https://mirrorbits.lineageos.org/su/addonsu-14.1-arm64-signed.zip
{
"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... and at CarbonROM Gerrit.
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!
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! 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.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
For this ROM to work you need to use the latest ODM Images. If you need additional guidance on how to do that, please refer to Sonys Guide on how to flash an ODM Image.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
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 XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-03-31
Last Updated 2018-07-19
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
LuthfiKun said:
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
Click to expand...
Click to collapse
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Dual sim support?
Myself5 said:
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Click to expand...
Click to collapse
Alright format it is.
agentsandy007 said:
Dual sim support?
Click to expand...
Click to collapse
No it isn't. At least out of the box. You can find a patch on Sony AOSP Build thread.
Volte Supported??
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Klaus N. said:
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Click to expand...
Click to collapse
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Can you upload screen recording of rom from home to settings and other functions.
I plan on flashing this soon, but I figured I'd tell you, your link to the Carbon FAQ is broken.
ilininja said:
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Click to expand...
Click to collapse
The battery consumption while in use is ok. But my device doesn't go into deepsleep while the screen is off. So I had lost about 23 % in 10 hrs - leaving the device untouched!
Video recording works; I haven't noticed that bug.
Saroj11488 said:
Can you upload screen recording of rom from home to settings and other functions.
Click to expand...
Click to collapse
Sorry, I went back to stock for now, as there's a new stock fw (41.3.A.2.107).
I have a few bugs to report. First, the fingerprint sensor is extremely slow, about half or even one third of the speed compared to stock. Second, could you guys please fix the deepsleep? That one is not working for now. And third, Night Light does not work at all...
Thank you for updating the XZ to Android 8.1 I am glad to see carbon rom on this device although it is not that stable for now.
Really nice ROM and I'm looking forward to make this my daily driver, I tried it for two days and these are the bugs I found:
1: GPU performance is really bad with 2d games and google maps lagging all the time when they never do on stock
2: CPU performance is inferior compared to stock, especially single threaded
3: enabling 120 hz display won't do anything and the settings or UI will crash when leaving the page
4: fingerprint seems to be sometimes less responsive, usable but can be improved
Camera is not so bad and the modded google camera works well, hopefully this will become the first proper AOSP based platform for this device that has only seen failures until now, keep up the good work.
Can I dirty flash this rom for just update?
I use Carbon Rom 3/31 version, but I can't use delta update because my device cannot receive the stock script.
I must change the rom script with Notepad+.
So...can I use dirty flash or....could you manage it?
Thanks for continously updating this rom and thank you for fixing the bug with the fingerprint sensor.
I'm not sure if deepsleep has been fixed but there is a big problem with playing music. I can't even play any music track at all...
Hello, looking forward to make this my daily driver, is it possible ?
What I would want is decent battery life and camera.
Hello. I tried to listen to music after installing the ROM, but the earphones are disconnected as soon as they are connected to the smartphone.
The earbuds pfe 132 and are made up of earphones with an iphone microphone.
L'ily said:
Clean flashed the 10th build along with Rytekk's dual-SIM patch, Pico Open GApps and Magisk 16.3 to my F8332 and other than that annoying SD notification (which can be banished to the notification drawer by making System UI notifications low priority) and Night Light not working, the only other major issue raised ITT of the CPUs not entering Deep Sleep is fixed according to Adiutor.
Great stuff. I haven't been able to standardise on one ROM since the CM days (interesting side note, it looks like you built the kernel for the NOCT build on my Z2 tablet).
I recommend this to anyone for daily use. Also, lower your expectations to realistic levels guise. I remember when XDA threads were for flagging major broken functionality, not complaining that a few amateur enthusiasts weren't putting out work that competed on every indicator against the finished product of a multibillion-dollar for-profit international conglomerate.
Sent from my Sony Xperia XZ using XDA Labs
Click to expand...
Click to collapse
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Hello, with the 10th build I have a problem with the installation, it keeps telling me that Google services framework stopped.
Any help ?
(V11 vendor image odm, formated data)
BigMixman said:
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Click to expand...
Click to collapse
Add these lines in build.prop, and reboot.
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0
{
"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 18.1 for the Galaxy Z Flip 4G
Code:
/*
* Your warranty may be void depending on the place you live.
*
* 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.
*/
Working:
- Wifi
- Sound
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data, calls, sms etc)
- Sensors
- Bluetooth
- Wifi and USB tethering
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (both of them)
- HWcomposer (HWC)
- Screens (both of them)
Issues:
- VoLTE and VoWIFI (and won't be implemented anytime soon)
- SELinux is set to permissive in this first build.
- Small outer cover screen has touch x and y axis swapped. (to swipe left, you must swipe up etc)
- Opening the fold wakes the phone up, but closing it doesn't put it to sleep (android does this assuming you want to use it with outer screen, but on flip this is impractical)
- Wireless Powershare (not implemeted yet)
Instructions:
Make sure you are on OneUI3.1 F700FXXU4DUB4 firmware (latest at the time of writing this). Older or newer ones may or may not work, this it what's tested.
- Carefully follow all instructions flashing the LineageOS recovery image in this thread, including decrypting the filesystem.
- Format data from los recovery again.
- Download and ADB sideload LineageOS zip, and (optionally) opengapps & Magisk(yes, the .apk). You can push them into internal storage but after decrypting that won't be accessible until first reboot so to avoid a mess it's best to sideload. Hit yes if the recovery asks you anything about missing signature verification.
- Reboot and profit?
Video Demo
Notes:
- It may be possible to not have to decrypt the filesystem in order to use this, but personally i've never tried it.
- If you run into any issues regarding the rom itself (bootloops, crashes etc) try a clean flash without gapps or magisk and see if they occur again. Some meme versions of gapps and/or magisk can sometimes cause problems. If you still have them, post about it here.
- In the same downloads folder i have uploaded a kernel with the cover screen's touchscreen disabled since accidental touches can start getting annoying.If future me got lazy and uploaded it in .img format, place the kernel on the root of /sdcard/ and run this command from adb shell in los recovery (after enabling it in advanced tab)
Bash:
dd if=/sdcard/disabled_covertouch_F700F.img of=/dev/block/platform/soc/1d84000.ufshc/by-name/boot
- Upon first boot you may want to go into settings and switch preferred connection mode from 3G to 4G
Downloads :
Goodies folder
Kernel source code
Credits:
Big thankies to @Vaughnn for his S10e sources this was largely based upon and for general help in the process of this rom's development. It wouldn't have been possible without him.
@Ivan_Meler for being a great friend, a great seal, and for suffering through my various...mishaps regarding this and many other endeavours.
reserved 1
reserved 2
You should apply for official
Hi, Rainbow_Dash! Thank you very much for your work!
May I know where I can get the source code for your bloomq build?
I want to customize LineageOS source code for myself a bit.
Metalor said:
Hi, Rainbow_Dash! Thank you very much for your work!
May I know where I can get the source code for your bloomq build?
I want to customize LineageOS source code for myself a bit.
Click to expand...
Click to collapse
The device trees were made in collaboration with other people who want it private, so it's not upto me if/when they're made public, sorry.
Rainbow_Dash said:
The device trees were made in collaboration with other people who want it private, so it's not upto me if/when they're made public, sorry.
Click to expand...
Click to collapse
Have you tried GSI builds on this phone? Do they work?
Metalor said:
Have you tried GSI builds on this phone? Do they work?
Click to expand...
Click to collapse
I briefly remember trying to flash a phh android 11 gsi and it crashing into fastboot. Never got around to troubleshooting as to why tho. But i've had issues with those on other devices too, so android 10 ones might work if you manage to downgrade platform.
Rainbow_Dash said:
The device trees were made in collaboration with other people who want it private, so it's not upto me if/when they're made public, sorry.
Click to expand...
Click to collapse
How I can contact those people?
F700n Can Korean models be flashed in?
Overallllll said:
F700n Can Korean models be flashed in?
Click to expand...
Click to collapse
Don't see why not. Give it a try and report back if it works.
Overallllll said:
F700n Can Korean models be flashed in?
Click to expand...
Click to collapse
It works just fine. Claims to be F700F, but that's about all that seems wrong.
Metalor said:
Have you tried GSI builds on this phone? Do they work?
Click to expand...
Click to collapse
i've tried GSI, especially Pixel Experience Plus. Everything is worked fine
Anybody got problems with the Touchscreen? After reboot in LOS, its not working. I can not touch on NEXT>
I see one time in the left bottom corner "SAVE MODE" pop on the screen. Maybe this is the problem?
Does it work with OneUI5 update (F700FXXSAIWA5)? Or it's a no-go for newer versions than 3.1?
PhantomUser2002 said:
Does it work with OneUI5 update (F700FXXSAIWA5)? Or it's a no-go for newer versions than 3.1?
Click to expand...
Click to collapse
No, it won't work with versions other than what's in the first post. I've long since sold my z flip (kinda regret doing so too), otherwise i could've updated it.
Hi, @Rainbow_Dash This is the only post that I could find that includes a custom privacy ROM for the Samsung Flip phone. I bought a Samsung Galaxy Z Flip 4 SM-F721B months ago and still searching and waiting for one to pop up. Do you perhaps know or maybe have seen anyone post about this that you can share with me? It would mean a lot. Thank you for your help. Cheers, Teddy
Since nobody has made any video on YT about it... What's even showing on the secondary screen?
I've always been curious how a custom rom would look on these foldables. Congratulations on making the first one.
I suppose nobody has attempted making any rom for any of the other ones because they have two "fully functional" screens on both sides. This is more of a ticker display.
Myrmeko said:
Since nobody has made any video on YT about it... What's even showing on the secondary screen?
I've always been curious how a custom rom would look on these foldables. Congratulations on making the first one.
I suppose nobody has attempted making any rom for any of the other ones because they have two "fully functional" screens on both sides. This is more of a ticker display.
Click to expand...
Click to collapse
I did make and link a video demo, it's on the first post. Basically it's a mirror of the main screen.
Rainbow_Dash said:
I did make and link a video demo, it's on the first post. Basically it's a mirror of the main screen.
Click to expand...
Click to collapse
That's hilarious. Too bad the touch direction is for some reason inverted. It would have been a fun way to use it.
Now i really want to buy one of those, just to play DOOM on the small display.