{
"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"
}
PixelPlusUI for the OnePlus 7 Pro [guacamole]
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."
PixelPlusUI is another aftermarket AOSP ROM Minimal UI & close to Stock Android ROM. What differentiates us from the rest, you ask? LET'S FIND OUT. It has additional localized and personalized functionality while preserving the stock Android look by adhering to Material Design guidelines. Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience using PixelPlusUI will be butter smooth with added convenience and features. The main aim of this form is to give the user a better experience without compromising the quality of the Android experience so that no one struggles with any kind of difficulties while using their device. PixelPlusUI brings a better UI/UX to Android with a seamless experience coupled with customizations and user security. In short, it's perfectly balanced between Great Performance, Security, Stability, Minimal UI & Awesome features including pixel goodies But this doesn't mean we aim to provide all the customization available on the planet. So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy PixelPlusUI on your respective devices!
- Kostya Maslennikov - Founder
- Saurav - Co-Founder & Co-lead Developer
- Hamza - Co-lead Developer & Team
- And Also Our Hardworking Maintainers
// Checkout the latest changes you get //
Latest Changelog: Tap Here for changelog
NOTE : Well here you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
// A screenshot is worth of thousand words //
Latest Screenshots :
PixelPlusUI
ppui.site
NOTE : Well here you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- Official Download Server ! ---------
Note: You can check our Website for more details, guides , changelog etc related to build !
-- DEVICE UPDATE TELEGRAM CHANNEL --
-- SUPPORT/DISCUSSION TELEGRAM GROUP --
-- Visit our OFFICIAL Website
-- OUR OFFICIAL TWITTER HANDLE --
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH :
- Download the latest build
- Reboot to recovery.
- Take a backup.
- Format Data
- Flash the latest build
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work?
Nothing yet
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Others, I forgot to mention
- Android OS version: 13
- Security patch: October 2022
- Build author/Device Maintainer : @mhmdeveloper
- DEVICE: OnePlus 7 Pro
- DEVICE CODENAME: guacamole
Sources and Documentation
- ROM Source Code
- Kernel Source
- OFFICIAL DEVICES
// Giving little CAN HELP A LOT //
- As you know build is free but building ROM needs a server. And Maintaining source and device stuff needs a server and it's pretty expensive for a student.
- Do consider donating on Patreon for sustainable support and rewards or buying me a coffee if you want to appriciate our work.
- Thank you for your support !
* UPI ID: [email protected] (Indian Users)
* Paypal:
Pay Sourav Ghosh using PayPal.Me
Go to paypal.me/uglykid24 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
Nice Update
I can't find the rom in the download, only the A12.1 rom is there?
Epic028 said:
I can't find the rom in the download, only the A12.1 rom is there?
Click to expand...
Click to collapse
Uploading
Very nice rom, I like the settings design and there's a good amount of customization. Don't know about battery life but I'll test it.
How do you flash the rom? For me it said "to import more Zips I have to switch from A/B" tried everything
Is anyone else having screen flickering issue on dark theme? And is there a possible fix / solution for it? Thanks in advance. Haven't found any other bug so far, seems pretty stable and buttery smooth for everyday usage.
pranavhdc said:
Is anyone else having screen flickering issue on dark theme? And is there a possible fix / solution for it? Thanks in advance. Haven't found any other bug so far, seems pretty stable and buttery smooth for everyday usage.
Click to expand...
Click to collapse
Not sure if it would help here but I have noticed some other ROMs with this similar problem and it pertains to the screen refresh rate. In the display settings, try changing the "Min Refresh Rate" to 90Hz. Unfortunately, of course that means a slightly higher battery drain, but it might solve your flickering problem.
DJWavey said:
How do you flash the rom? For me it said "to import more Zips I have to switch from A/B" tried everything
Click to expand...
Click to collapse
It's simple, you just format data, reboot back to recovery, choose adb sideload then run "adb sideload file.zip" let it do it's thing then boot. You could try putting the file onto the internal storage as well if using TWRP but again, format data, reboot back to TWRP, upload file to internal storage, flash then boot.
The switching partitions (A/B) when flashing more zips is only if you want to flash a gapps package after the ROM. I do not believe you need to do that with this ROM, I'm pretty certain GApps are included. And you also don't usually need to manually switch from A to B (or vice versa), just a reboot back to recovery after flashing will automatically switch it for you.
theslam08 said:
Not sure if it would help here but I have noticed some other ROMs with this similar problem and it pertains to the screen refresh rate. In the display settings, try changing the "Min Refresh Rate" to 90Hz. Unfortunately, of course that means a slightly higher battery drain, but it might solve your flickering problem.
Click to expand...
Click to collapse
Thank you! This seems to have fixed the screen flickering issue.
I went from stock OOS to this tired of waiting for A12 and to try out Android 13 for myself.
So far after 24hrs it seems enough to stay with it for a while without worrying too much.
Some bugs/anomalies/features I miss:
- SmoothDisplay and min/max refresh rate 60/90hz works with a lag. There is a noticeable stutter when the screen is static and switched down to 60Hz when you try to scroll - it stutters when it needs to scroll and switch back to 90Hz. With smooth display on, the 3 gestures navigation was really bad - swiping from the edge to go back was a total hit or miss.
I have set the refresh rate to min/max 90Hz only, turned off SmoothDisplay and it all works without a problem.
- auto brightness as annoying AF like on stock OOS. It tries to force and lower my brightness from typical 60-70% to around half that.
Also I noticed the phone lowers light when the screen is static and unused for a while and then it goes back to higher brightness, like there would be some logic to conserve battery and lower light on static screen (for reading?). Anyway, lets hope there is actually something to learn in A13 and it will stop lowering brightness by such a huge margins that I need to manually swap it back to 70%.
- no temperature correction of display panel in options, only Natural, Boosted or Adaptive and full RGB, Contrast etc. sliders.
Also, Natural seems oversaturated a bit compared to OOS stock. Seems Adaptive is the most color accurate.
- volume center, when you change volume and tap menu icon to go to expanded sound menu with the sliders, entire menu is dimmed down, only "Done" button seem to have normal brightness
- slider switch on the phone does not mute Media sounds when all the wat to silent position. I think on stock OOS it did mute everything besides Alarms. Now it does not mute Media so if something start to playback in the phone, everybody will hear it. there is option in Device Extras to set it to DnD but after that, it mutes everything including Alarms. On stock OOS you could mute your phone for the night but still be able to hear the Alarms which was a nice feature.
- in Network->Sim settings->Preffered network type, you can choose from "LTE only", "LTE recommended" and "3G".
Choosing LTE recommended shows in the menu that it is also LTE only so not sure which option is which. Should be clarified like on stock OOS with 4G/3G/2G, 3G/2G etc.
LTE only and LTE recommended seems convoluted?
- no option to remove the built-in weather from Lockscreen.
Need to take a trip to check out BT audio in car, Android Auto etc. In terms of signal and wifi quality, everything seems to be working fine.
theslam08 said:
Es ist ganz einfach, Sie formatieren einfach die Daten, starten zurück zur Wiederherstellung, wählen adb sideload und führen dann "adb sideload file.zip" aus, lassen es tun und booten dann. Sie können auch versuchen, die Datei auf den internen Speicher zu legen, wenn Sie TWRP verwenden, aber formatieren Sie die Daten erneut, starten Sie zurück zu TWRP, laden Sie die Datei in den internen Speicher hoch, flashen Sie und booten Sie dann.
Das Wechseln der Partitionen (A/B) beim Flashen weiterer Reißverschlüsse erfolgt nur, wenn Sie ein Gapps-Paket nach dem ROM flashen möchten. Ich glaube nicht, dass Sie das mit diesem ROM tun müssen, ich bin mir ziemlich sicher, dass GApps enthalten sind. Und Sie müssen normalerweise auch nicht manuell von A nach B (oder umgekehrt) wechseln, nur ein Neustart zurück zur Wiederherstellung nach dem Flashen wird es automatisch für Sie umschalten.
Click to expand...
Click to collapse
theslam08 said:
It's simple, you just format data, reboot back to recovery, choose adb sideload then run "adb sideload file.zip" let it do it's thing then boot. You could try putting the file onto the internal storage as well if using TWRP but again, format data, reboot back to TWRP, upload file to internal storage, flash then boot.
The switching partitions (A/B) when flashing more zips is only if you want to flash a gapps package after the ROM. I do not believe you need to do that with this ROM, I'm pretty certain GApps are included. And you also don't usually need to manually switch from A to B (or vice versa), just a reboot back to recovery after flashing will automatically switch it for you.
Click to expand...
Click to collapse
Ok then I'll try it again like this
DJWavey said:
probieren
Click to expand...
Click to collapse
probieren
theslam08 said:
It's simple, you just format data, reboot back to recovery, choose adb sideload then run "adb sideload file.zip" let it do it's thing then boot. You could try putting the file onto the internal storage as well if using TWRP but again, format data, reboot back to TWRP, upload file to internal storage, flash then boot.
The switching partitions (A/B) when flashing more zips is only if you want to flash a gapps package after the ROM. I do not believe you need to do that with this ROM, I'm pretty certain GApps are included. And you also don't usually need to manually switch from A to B (or vice versa), just a reboot back to recovery after flashing will automatically switch it for you.
Click to expand...
Click to collapse
Funktionier immer noch nicht :/
DJWavey said:
probieren
View attachment 5742889
Funktionier immer noch nicht :/
Click to expand...
Click to collapse
I can only understand English.
But, that appears to be a computer user error. Here's a trick, type adb sideload then click AND DRAG the rom.zip file INTO the command window - it will auto fill the directory/location of the file. Because that is what you're missing. If the rom is in the "Minimal ADB and Fastboot" folder, I would guess it should say something like
adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\rom.zip
That should work.
theslam08 said:
I can only understand English.
But, that appears to be a computer user error. Here's a trick, type adb sideload then click AND DRAG the rom.zip file INTO the command window - it will auto fill the directory/location of the file. Because that is what you're missing. If the rom is in the "Minimal ADB and Fastboot" folder, I would guess it should say something like
adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\rom.zip
That should work.
Click to expand...
Click to collapse
I am now on OxygenOs
Why write her for India?
You need to rename downloaded file to "rom.zip" and put it in the same folder as adb program if you want to flash it with this command.
Long screenshot seems to be broken.
More bugs/errors pop during daily use. No sure if this rom qualifies for a safe daily driver.
Some apps work only on 4/5 of the screen height.
Battery drain is excessive, especially while on screen - its either refresh rate bug or auto brightness bug or both of them are draining battery. Running any app while using screen or maps or similar drains battery fast.
Not sure if it is worth to keep up with this rom. Probably will go back to stock.
Any updates in near future planned @mhmdeveloper ?
cavist said:
More bugs/errors pop during daily use. No sure if this rom qualifies for a safe daily driver.
Some apps work only on 4/5 of the screen height.
Battery drain is excessive, especially while on screen - its either refresh rate bug or auto brightness bug or both of them are draining battery. Running any app while using screen or maps or similar drains battery fast.
Not sure if it is worth to keep up with this rom. Probably will go back to stock.
Any updates in near future planned @mhmdeveloper ?
Click to expand...
Click to collapse
For me I haven't encountered any bugs yet and battery life is better than stock, you should've tried flashing the firmware before install just to be sure everything works right.
cavist said:
More bugs/errors pop during daily use. No sure if this rom qualifies for a safe daily driver.
Some apps work only on 4/5 of the screen height.
Battery drain is excessive, especially while on screen - its either refresh rate bug or auto brightness bug or both of them are draining battery. Running any app while using screen or maps or similar drains battery fast.
Not sure if it is worth to keep up with this rom. Probably will go back to stock.
Any updates in near future planned @mhmdeveloper ?
Click to expand...
Click to collapse
I have been on this ROM since the day it came out, honestly I've found no bug other than screen flickering if you've opted for auto 60/90hz refresh rate ( @theslam08 suggestion on changing the minimum refresh rate fixed that as well). Battery life is the best among all other A13 custom ROMs as of now, I would suggest you to do a clean flash as per provided instructions. I can confirm this ROM is stable for daily usage, really very impressed with it being one of the early A13 ROMs.
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"
}
Code:
#include
/*
* 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.
*/
We've done it! Thanks to the androidarmv6 team's work, and the great people over at Team Simplicit(Especially Olivier, as he got it working on the Wildfire S and a couple other devices),
we now have a functional KitKat rom for the ChaCha!
This rom SHOULD now be daily driver ready. Please leave feedback on any issues.
I will also note that it takes a rather long time to boot. I don't know if it will stay this way or not, so don't ask.
And lastly, I recommend leaving the device for at least a minute after first boot, before going through the setup wizard. Otherwise it will be very laggy.
NOT WORKING/BROKEN/ISSUES
Bluetooth
Screen video recording (I believe we have a fix in the works)
ART (doesn't support ARMv6)
SELinux
USB/WiFi tethering
Camera orientation is sideways
Phone takes a long time wake during call or alarm
Symbols/zero key bringing up the input method selection window, regardless of whether alt is pushed.
Arabic keyboard not working?
incoming call crashes ui. dialer crashes when you try to open it after ui crash.
Trebuchet launcher crashes repeatedly, making phone unusable
MTP and PTP Modes cannot be selected under USB Connection menu, Settings Crashes. Setting does not save.
Trebuchet unable to remove widgets due to missing "X"
CHANGELOG
Code:
[B][U]07/22/2014[/U][/B]
[LIST]Updated recovery to 6.0.5.3[/LIST]
[LIST]Fix for flashing older zips[/LIST]
[LIST]Fix for partitioning SD card from Advanced menu[/LIST]
[B][U]07/22/2014[/U][/B]
[LIST]Trebuchet now able to remove widgets(Temporary workaround)[/LIST]
[LIST]Version bump to 4.4.4_r2[/LIST]
[LIST]Kernel updated to 2.6.36.1 (as well as various tweaks)[/LIST]
[LIST]Changed default governor to SmartAssH3, as it seems to be stable now on the ChaCha[/LIST]
[LIST]Arabic keyboard SHOULD be fixed, please give feedback[/LIST]
[LIST]Symbols/Zero key should now bring up the Symbols menu, and allow FN+0 to type "0" (thanks [URL="http://forum.xda-developers.com/member.php?u=3517907"]WinSuk[/URL]![/LIST]
[LIST]"F"(Facebook) key has been re-enabled and now launches the Browser[/LIST]
[LIST]Re-fixed camera orientation[/LIST]
[LIST]Recovery updated to 6.0.5.2, Softkeys now work, Swipe should work, Lights removed(no need for it)[/LIST]
[B][U]06/13/2014[/U][/B]
[LIST]Dialer and Contacts List no longer crash on incoming/outgoing calls[/LIST]
[LIST]Trebuchet no longer crashes repeatedly[/LIST]
[LIST]Changed default CPU Governor to minmax[/LIST]
[B][U]06/08/2014[/U][/B]
[LIST]Fixed Camera Orientation/Rotation (thanks [URL="http://forum.xda-developers.com/member.php?u=5095490"]Kevinjoa[/URL]!)[/LIST]
[B][U]06/07/2014[/U][/B]
[LIST]CM/androidarmv6/Google/AOSP upstream (incl. Android 4.4.3)[/LIST]
[LIST]Disabled fading edges on text for a small speedup - [URL="http://winsuk.net/screens/liberty/fadingbefore.png"]before[/URL], [URL="http://winsuk.net/screens/liberty/fadingafter.png"]after[/URL][/LIST]
[LIST]Switched to gps.conf with SUPL (assisted GPS) support[/LIST]
[LIST]Changed default CPU Governor to ONDEMAND[/LIST]
[LIST]Changed default min. CPU frequency to 245 Mhz[/LIST]
[B][U]06/04/2014[/U][/B]
[LIST]Included additional Keyboard Layouts (the Symbols/zero key currently isn't behaving properly. fix for this soon I hope)[/LIST]
[LIST]Wifi Fix.[/LIST]
[LIST]New Simplicit-ULTiMATE kernel[/LIST]
[LIST]Included Bare Minimum GApps[/LIST]
[LIST]Disabled First Boot Setup Wizard[/LIST]
[B][U]05/30/2014[/U][/B]
[LIST]First Build.[/LIST]
CREDITS
TeamSimplicit (Olivier, izi501, feroxx, Kevinjoa, thehacka1, WinSuk, Mazer.One)
benjamingwynn, niks255
androidarmv6
JDevs and the OWL Team
luzifer1984, adlx.xda
CyanogenMod
DOWNLOAD
ROM | Mirror
GApps to Cache | Mirror - Thanks to WinSuk for this (original thread)
SCREENSHOTS
RECOVERY
Recovery gets built with rom, I will update this anytime the recovery is changed.
Current Version is 6.0.5.3
Download Here | Mirror
How to flash recovery:
Terminal Method:
Stick the "recovery.img" file on the root of your sdcard. Open a terminal emulator, and type:
Code:
su
flash_image recovery /sdcard/recovery.img
After typing "su" you'll want to allow terminal emulator root access.
Fastboot method:
Stick the "recovery.img" file in the same directory as your fastboot executable binary.
Put your phone in fastboot mode.
Open a command prompt and use the fastboot tool to type:
Code:
fastboot flash recovery recovery.img
PH06IMG.zip method:
Put your phone in fastboot mode, and use the fastboot tool to type:
Code:
fastboot getvar all
You'll want to make note of the "version-main" value, the "cidnum" value, the "modelid" value, and the "hbootpreupdate" value.
Stick the "recovery.img" file in a folder somewhere, and create a new text document called "android-info.txt"
Put the values you noted earlier into the "android-info.txt" in the following format(this one works for my device):
Code:
modelid: PH0613000
cidnum: TELUS001
mainver: 1.60.0.0
hbootpreupdate: 12
note that "mainver" is the value you noted earlier from "version-main".
Now zip the "recovery.img" and the "android-info.txt" together, and name it "PH06IMG.zip"
Put that file on the root of your sdcard, and reboot into the bootloader. It should detect the zip, and ask you to update. choose yes, and you're off to the races!
SOURCES
androidarmv6/android
androidarmv6/android_device_htc_chacha
androidarmv6/android_device_htc_msm7x27-common
androidarmv6/android_kernel_htc_msm7x27
androidarmv6/proprietary_vendor_htc
Removed
Finally CM 11 in HTC chacha, i will Test it as soon as i can
i Made this Key Character Map File for "Arabic", Please add it to your Build
chacha-keypad-ara.kcm.zip
Thanks kronflux, Olivier, and all the Simplicit Team for this Great Effort :good:
Will add that, thanks.
Gesendet von meinem Xperia S mit Tapatalk
I am Really Enjoying Kitkate right now
———
Installing Steps:
1) I Tried to install the Recovery using the boot loader method but it failed with an error "CID incorrect, update fail”.
So i used fast boot Method with my PC & this command "fastboot flash recovery recovery.img”
2) Installed The Rom
3) Installed “CronMod-INT2EXTV2+_signed.zip” (Great INT2ext mod to increase internal Memory form SD card, now 1.5GB) :angel:
The system Feels good, but i couldn’t live with it without updating the minimum CPU frequency to 245 MHZ
Problems i faced At my first look
System:
Wifi & Hotspot NOT working
Bluetooth NOT working
USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
3G Stop working after WAKE - I Must Manually disable and re-enable it
Battery Still Testing
Apps:
Camera image is rotated !
Phone app buttons really needs to be reorganised
Keyboard:
@ and ~ are misplaced , should be switched (FN+y) with (FN+p)
No Number “0”
Lang, & Facebook Keys are not Functional
No Arabic Keyboard
Overall, Very Good for a First Build. I am Excited to Test the Next Build and i am ready for Testing
Yehia2amer said:
[*]USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
Click to expand...
Click to collapse
I will say that mass storage mode works perfectly for me. but I will do some testing with other micro sd cards, and see what happens.
But thanks for testing!
((
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...
mortal19xx said:
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...
Click to expand...
Click to collapse
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.
[A]
kronflux said:
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.
Click to expand...
Click to collapse
Keep going... :good:
Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Gesendet von meinem Xperia S mit Tapatalk
thanks
i m glad to see our chacha reborn with new build and developers, thank you guys for the time you spend on this phone
keep up
i'll test and report
Olivier said:
Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Click to expand...
Click to collapse
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?
Flexmaen said:
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?
Click to expand...
Click to collapse
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with. I have found a patch used on a samsung device that uses the msm7227 like our device, so as long as it's similar enough, and still works with kitkat, it shouldn't be too hard.
No promises though
kronflux said:
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with
Click to expand...
Click to collapse
Ah ok great.
Anyway, the biggest downside of the custom roms for the Chacha is the bad keyboard integration. If you compare it with a Nokia E71, the original ROM is already bad. But if you use a custom ROM, than you are lacking even more keyboard shortcuts (especially when handling calls). So I guess improving this would be the best thing for this phone.
But let's see... whatever you decide it's great there there is still so much work going on for this phone!
Flexmaen said:
the biggest downside of the custom roms for the Chacha is the bad keyboard integration.
So I guess improving this would be the best thing for this phone.
Click to expand...
Click to collapse
Unfortunately, I can only judge by the English keyboard configurations, because I don't know any other languages xD
But the next build(which, if all goes well, will be later this afternoon/evening) will have the keyboard configs the same as the other recent custom roms, primarily the ones by adlx.xda, as it's his repos we got the configs from.
But after I release this new update, if you tell me what's wrong with the keyboard specifically, I may be able to help out a little.
ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot
mohabmoka said:
ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot
Click to expand...
Click to collapse
the next release(which is currently compiling. takes a LONG time xD) SHOULD have proper arabic support, and I believe it does support swap, but I don't know for sure.
good xD , and please if you can , attach pics of the rom
Is it mandatory to install recovery v 6 to flash this?
swashie said:
Is it mandatory to install recovery v 6 to flash this?
Click to expand...
Click to collapse
no, however it is recommended, and I can't guarantee that future releases of the rom won't require it.
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16
The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.
Thanks!!!
Tested and no issues found
Great Rom:good:
Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.
lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?
lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.
Works great so far. Thank you
PS: could unbrick my phone
Update in the OP. new beta release.
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.
Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Code:
/*
* 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.
*
*/
Hi,
here you can find my version of LineageOS 19.1 for our Samsung Galaxy S3 (I9305).
This is a beta build, also from the LineageOS side, there are typical functions still missing, so don't install it if you want a completely stable and completed ROM and don't report my already listet bugs!
Attention:
Sometimes it needs another reboot to find the sim card.
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
Random reboots
NFC
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
I9305 ROM
ROM Mega
Spoiler: Changelog
11.02.2022
14.02.2022
15.02.2022
08.03.2022
17.03.2022
25.03.2022
04.04.2022
19.04.2022
15.06.2022
27.09.2022
23.01.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][I9305][BETA] LineageOS 19.1, ROM for the Samsung Galaxy S3 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2022-02-10
Last Updated 2023-01-23
*reserved
Update 11.02.2022:
Fixed GPS completely
Some RIL-Work, still buggy, I'm working hard to find a solution
Update 14.02.2022:
Fixed APN setting problem at boot.
Update 15.02.2022:
Fixed GPS completely, including 3D fix
Fixed low signal for 3G and 2G network
Update 08.03.2022:
Synched with latest LineageOS sources
html6405 said:
Update 08.03.2022:
Synched with latest LineageOS sources
Click to expand...
Click to collapse
Thank you for the great job. Having 12 on our old SIII is amazing ! Have now a very limited use of this device with Build 0215 - but works like charm. Although tech is old, transitions and speed are more than acceptable, ...
Have tried update OTA but ended in bootloop on LOS logo.
Tried a clean install with 0308 build same bootloop.
Tried Magisk - stuck on Samsung logo
Restored build 0215
Captain Kangaroo said:
Have tried update OTA but ended in bootloop on LOS logo.
Click to expand...
Click to collapse
Did you have older bitgapps installed?
(If yes, you would have to reflash them)
It's hard to say why you're facing a bootloop, it did really work fine on my testing device.
html6405 said:
Did you have older bitgapps installed?
(If yes, you would have to reflash them)
It's hard to say why you're facing a bootloop, it did really work fine on my testing device.
Click to expand...
Click to collapse
I use my SIII gappless, same with my S5. => I ota over 0215 gappless !
Then I did several attempt: after full format:
- restore build 0215 + flash Magisk + Bitgapp didn't work
- flash build 0308 + Magisk 24.2 or 21.4 didn't work
- flash build 0308 + Bitgapp for 12 didn't work
- flash build 0308 + MindTheGapp for 12 didn't work
So far, its fine with 0215 for my limited use (no tel, no text, no mail client, few use of internet browser, few specific Apps installed: SDMaid, AllToolinONE, Mixplorer, MusicSpeedChanger. Except Mixplorer where I noticed some laggy transitions, the other apps work fine.
Sorry I did'nt logcat fo you
Captain Kangaroo said:
Sorry I did'nt logcat fo you
Click to expand...
Click to collapse
This would have pointed me maybe to the problem,
my device still works fine, but I may will try a factory reset.
(I'm using it with gapps at the moment)
Update 17.03.2022:
Switched to Android 12L , attention, this could not work with your existing gapps! (mindthegapps will work)
A clean installation is recommended.
html6405 said:
Update 17.03.2022:
Switched to Android 12L , attention, this could not work with your existing gapps! (mindthegapps will work)
A clean installation is recommended.
Click to expand...
Click to collapse
Clean install 19.1-20220317-HTML6405-i9305.zip, no gapp went very well. So far so good
Update 25.03.2022:
Synced with latest LineageOS sources
Created possibility to disable the HW navigation keys (not really needed for full gesture navigation)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
html6405 said:
Update 25.03.2022:
Synced with latest LineageOS sources
Created possibility to disable the HW navigation keys (not really needed for full gesture navigation)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Click to expand...
Click to collapse
Great job
OTA update done like a charm
HW keys disable is good as I use navigation bar
Will see for the 2 last item …
On previous version 0317, I succedded to flash magisk 24.3 but didn't work properly - device became very laggy or stuck, the permissions granted didn't stay, therefore I removed it
does volte works?
EeeK said:
does volte works?
Click to expand...
Click to collapse
No, never worked with any custom ROM,
Samsung didn't publish their proprietary implementation for VOLTE.
Maybe interesting!?
ComputerBase: Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones.
Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones
Samsung legt mit rückwirkend bis zu zehn Jahren Android-Updates für historische Smartphones wie das 2012 vorgestellte Galaxy S III nach.
www.computerbase.de
larswars said:
Maybe interesting!?
ComputerBase: Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones.
Samsung Galaxy S III: Android-Updates für bis zu 10 Jahre alte Smartphones
Samsung legt mit rückwirkend bis zu zehn Jahren Android-Updates für historische Smartphones wie das 2012 vorgestellte Galaxy S III nach.
www.computerbase.de
Click to expand...
Click to collapse
Good to know but April Fool's Day !!!!!!
@larswars @html6405 @rodman01
larswars said:
I encountered update 7 error when trying to flash the ROM in Tre, any idea?
Click to expand...
Click to collapse
Maybe wrong TWRP used.
{
"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 LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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 organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try some mods.Downloads Links
LineageOS 19:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-19.1/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 12.1 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Please install the latest version of TWRP to avoid further issues with recovery!
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 12.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Stable
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Ok
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Ok
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Ok
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
what the ...!?
i downloaded los18 just yesterday, installed it this morning and now i see los19 sneaked by
thank you so much chippa_a, i will try it out tomorrow
unbelievable what your doing to this oldschool device.
Gcam works perfectly on it. Thanks a lot for this device!!!
This works beautifully and is really smooth. Never thought I'd see another rom for the XC again.
Can confirm that GCam 8.x with HDR actually works! (No crashes, or stuttering) Unlike previous roms with the most recent kernel before this new one. I don't know what magic you pulled to make this happen but thank you!
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
decsimon said:
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
Click to expand...
Click to collapse
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
konstruktor said:
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
Click to expand...
Click to collapse
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
decsimon said:
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
Click to expand...
Click to collapse
You won't need to flash the kernel separately, it's included in the zip:
1. Boot to TWRP.
2. Install the Lineage zip file.
3. Reboot to recovery.
4. Optional: In TWRP, install/flash Magisk 24.1 and/or MindThe GApps.
That's it. No issues with Chrome lag either. I've tried a few browsers and they all work well.
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
how if i try nfc on ex japan S0-02 j ?
Little adventure said:
how if i try nfc on ex japan S0-02 j ?
Click to expand...
Click to collapse
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
betacrypt said:
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
Click to expand...
Click to collapse
First , thanks for this Rom I'm very happy to See Android 12 on my phone.
I have tried Encryption and it doesn't work for me. I have a bootloop.
Has anyone else tested it?
And on the Encrypt page , I had astrange bug : I wasn't able to access to the"Encrypt" button at the bottom of the page . I had to set the police size at the smallest size to see it.
Maciek602 said:
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
Click to expand...
Click to collapse
Agree, fingerprint detection and unlocking is incredibly fast, didn't think it could ever be improved this much.
betacrypt said:
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
Click to expand...
Click to collapse
thanks for the answer sir
I have ex japan status bootloader yes, now position in custom rom lineage 16.0 android pie, this rom very smooth in my old device , i try turn on nfc in this rom, nfc doesnt turn on , but nfc working fine in ex global
Maybe hardware nfc ex japan different with ex global , so that maybe build tree and config specific for ex japan , correct me if i wrong sir
my experience with gapps 12.1 12L
open gapps stock - not working (endless bootanimation)
open gapps pico - unusable (loop before setting up fingerprint)
flame gapps full - unusable (loop before setting up fingerprint)
flame gapps basic - unusable (loop before setting up fingerprint)
mindthegapps - working
nik gapps omni - working
nik gapps stock - working fine so far
I have this problem...my bank apk its OK with last magisk (and fingerprints setting and Hide zygisk), but gpay dont work when i insert my card code cvv, it say that is not possibile continue because possible root phone....i try to hide all with zygisk of magisk .....
OK i resolved with module safetynet....
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
decsimon said:
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
Click to expand...
Click to collapse
That's Android 12. I wouldn't hold my breath that someone could port an older System UI over. You would have to get used to it I'm afraid.
{
"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 12 (R), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Common tree source code: LineageOS/android_device_motorola_sdm660-common
Common tree source code: LineageOS/android_device_motorola_evert
Kernel source code: LineageOS/android_kernel_motorola_msm8998
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Crypto
Broken:
Nothing (?)
Downloads:
Official builds
Unnoficial with gapps builds
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Follow this instructions
Important notes:
* Required * Patience.
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Formatting data (all user data is wiped, including internal storage) when comming from other roms.
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Official wiki link
LineageOS 19.1, ROM for the Moto G6 Plus
Contributors
jro1979oliver
ROM OS Version: Android 12.1
ROM Kernel: Linux 4.4.x
ROM Firmware Required: latest stock
Version Information
Status: Official
Created 2022-04-25
Last Updated 2022-04-25
Can I upgrade from the unofficial build to the official - or do I need to wipe all and start from scratch?
I prefer you start clean, but you can try, if you flash mindthegapps as Gapps package, it will be the same as shipped on unnoficial build
works great
Unofficial builds are still the best
@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago
FlySwit Designer said:
@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago
Click to expand...
Click to collapse
You can press power button with vol - and enter recovery mode, then select format data (hint: you will loose your data), then things should work.
Make sure to follow wiki steps before install anything.
I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.
ew said:
I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.
Click to expand...
Click to collapse
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging
jeferson1979 said:
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging
Click to expand...
Click to collapse
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.
ew said:
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.
Click to expand...
Click to collapse
It's the annoying part of a release early days XD
Hi, I've installed both the mod and Gapps following the instructions on the website (I had a PixelExperience ROM before) and - from what I am seeing - all went smooth.
Thanks a lot for your effort.
P.S. Is there a Telegram channel for LineageOS?
edit: the only "weirdness" I've seen: two apps warn me that phone is rooted. For one I can continue the installation, for the other is not possible. Not a big issue, but this did not happen with the Pixel Experience ROM.
Thanks again.
Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.
I have been on this ROM for a day now - and it is very smooth. No major issues and thanks to the OP for the time and support!
A few small items that I have mostly found workarounds for but wanted to mention them for anybody that is interested:
I really like TWRP over the lineage recovery. On LOS 18.1 I was able to flash TWRP and use it. That doesn't seem to be an option for 19.1. Even though I have turned encryption off (so the encryption is not an issue) - it seems like it doesn't boot properly after installing TWRP. So, I guess I need to live with lineage recovery.
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Auto brightness - in dark my screen gets too dark. I have to raise it - and it doesn't seem to be learning to use a higher minimum - like some other versions of android.
Relatively speaking - these are minor and maybe just things that bug me. The ROM is very smooth, fast and much appreciated!
I also want to report what seems a minor bug: when the display auto-rotation is enabled, no icon is shown in the status bar, but instead an icon is shown when it is not. In stock version and Pixel Experience mod the feature had the opposite behavior (so an icon was shown only when auto-rotation was enabled).
Thanks again, all seems to work pretty well.
Mattew Rockstone said:
Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
View attachment 5604917
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.
Click to expand...
Click to collapse
Same issue for me and my evert.
For the guys with the "offline" issue: flash rom, then reboot to recovery, then flash mindthegapps. This will solve your connection issue
now, 3 month later finish guarantee, my charger burned out
happy, becase i was in the same room and stop fire, if i wasnt-maybe burnt all house!!!!!
be carefull-when are you charging everething
ew said:
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Click to expand...
Click to collapse
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com
the_15th said:
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com
Click to expand...
Click to collapse
Thanks for your help. I found that the switch in the developer options got reset after reboot.
The following is my solution as implemented in Tasker. I run this at system start.
Task: Green Dot Location Suppress (A12)
<need to have the following commands in the following sequence for it to work:
-device_config put privacy location_indicators_endabled false default
-device_config put privacy camera_mic_icons_enabled false default
-device_config put privacy camera_mic_icons_enabled true default
Per my testing, the commands need to be executed in the sequence listed above - otherwise it does not work.
see https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/
https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/>
A1: Anchor
A2: Run Shell [
Command: device_config put privacy location_indicators_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A3: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A4: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled true default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]