{
"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:
* 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.
*
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
To know additional features, click on the link https://bit.ly/2UmsqER
What's working and Known issues
Almost everything works except camera hangs for a few seconds and video recording does not work.
Recovery:
https://dl.twrp.me/logan2g/
Backup
Take a backup of entire ROM, important files and folders from internal memory to your PC or memory card before flashing this build.
NOTE: As of now, only TWRP 3.0.0 or newer are able to flash CyanogenMod 11. Other recoveries does not extract the ROM fully.
Installation of CyanogenMod 11
Download and copy attached CM11 file to sdcard
Boot into TWRP recovery
Wipe
Advanced Wipe
Check -> Dalvik, Cache, System, Data, Internal Storage
Swipe to Wipe
Back to Install
Install
Browse and select cm-11-20170522-UNOFFICIAL-logan2g.zip
Swipe to Confirm Flash
Reboot System
Downloads
CyanogenMod 11
https://www.up-4ever.org/ivhl1gkj5cv7
Open GApps (Google Apps)
Download Variant depending on your requirement. Below is the PICO variant.
OpenGApps (Pico): http://opengapps.org/?api=4.4&variant=pico
Source
https://github.com/ItsAnilSingh
Credits
@Unjustified Dev and @Doc_cheilvenerdi.org @versusx @regalstreak @andii_nr @ngoquang2708 @Corphish @dhinesh77 @pawitp and others.
XDA:DevDB Information
CyanogenMod 11 For Samsung Galaxy Star Pro/Plus GT-S7262, ROM for the Samsung Galaxy Star
Contributors
ItsAnilSingh
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: S7262CM110V2
Beta Release Date: 2017-06-04
Created 2016-09-06
Last Updated 2020-01-07
F.A.Q
Q. I have faced some issues, which is not mentioned in the 'Not Working' list........?
A. For bug reports, the least we can expect from you is a logcat taken during the issue. Or atleast, you could tell us how and when did you face the bug, how can we reproduce the bug to fix it. Reports without any of these will be ignored.
Q. I got a status 7 error when flashing the CM11 zip...? / My device is stuck at boot logo after flashing CM11...?
A. Please use the recovery that is mentioned. It is recommended to use TWRP as it is known working for all.
Q. I put the ROM zip in internal memory while I was in stock ROM, but when I go to TWRP and try to flash it, the zip is not there, help!
A. TWRP uses psych.half's storage hack that he did in CM10.1. You will need to mount /data (its generally done by default), and then go to /data/media and there you can find the zip.
Q. Can you add XYZ feature to the ROM?
A. No!
Q. Can I use your ROM/any part of ROM and modify it and release it separately?
A. Yes you can. But please mention proper credits.
Q. I flashed this ROM, but I dont find any Google App, where can I find it?
A. Flash gapps mentioned in OP.
Q. Are any 3rd party utilities/kernels/themes/mods supported?
A. No, not yet. If they are supported, it will be clearly mentioned in their respective threads.
Q. If no mods are supported, how can we customize our experience?
A. This is CyanogenMod, a completely different ROM from stock. As of now, no kernels are supported, but you can customize the looks using CM11's highly customizable theme engine.
Bug reporting
How to report a bug?
First off all, check the 'not working' list and see if the bug you are facing is already mentioned or not. If it is, stop right away because the concerned people working on the ROM are aware of the issue.
If the bug/issue is not mentioned in 'not working' list, check the Frequently Asked Question (F.A.Q) and see if issue is resolved already.
If the issue you face is not in FAQ either, you would probably post a reply in this forum, and not PM anyone, about the bug.
Attach a logcat.
If not possible, mention a proper way how you encountered the bug.
Also mention any 3rd party stuff you installed. (Like mods, themes, kernels etc)
Following things WILL NOT be considered as bugs. So please do not post such bug reports, they will be ignored.
Low benchmark scores. Even if Stock results better.
Poor performance in gaming. Even if Stock results better.
High RAM usage/low RAM available.
Various kernel control app crashes.
Crashes of various UI elements when a custom theme/mod is applied.
Random reboots, and other issues caused by flashing custom kernel.
Reserved for changelog
ItsAnilSingh said:
Reserved for changelog
Click to expand...
Click to collapse
Now the development begins!
Will test and report any bugs if found.
Cheers!
Really nice work keep it up
Some SS...
Hb20032003 said:
Some SS...
Click to expand...
Click to collapse
could you tell me what this launcher name
hamzaeid said:
could you tell me what this launcher name
Click to expand...
Click to collapse
Stock Trebuchet Launcher. Its a theme btw
Hb20032003 said:
Stock Trebuchet Launcher. Its a theme btw
Click to expand...
Click to collapse
TY pro i was just asking cuz im Still one CM10 and gonna wait for Stable CM11 release
Hb20032003 said:
Now the development begins!
Will test and report any bugs if found.
Cheers!
Click to expand...
Click to collapse
:good:
hamzaeid said:
Really nice work keep it up
Click to expand...
Click to collapse
Thanks. Keep watching.
Hb20032003 said:
Some SS...
Click to expand...
Click to collapse
:good::good::good:
hamzaeid said:
TY pro i was just asking cuz im Still one CM10 and gonna wait for Stable CM11 release
Click to expand...
Click to collapse
Stable - will take time
Beta 2 - Soon
@ItsAnilSingh When will the next version be released? Plz fix camera and network related bugs.btw good work.
Do I have to wipe SYSTEM before flashing? (Last time I did then I got error "No Os installed" and then installed lollipop v4 stable it doesn't booted, then I restored my phone to stock rom then wiped without SYSTEM then it worked so I think SYSTEM should not be wiped)
@ItsAnilSingh white screen after flashing? (I didn't wiped system)??
Physicist Tallal Hashmi said:
@ItsAnilSingh white screen after flashing? (I didn't wiped system)??
Click to expand...
Click to collapse
Were you using kernel 3.0.101 before? If yes, then you have to install latest stock rom through odin and then flash cm rom.
Physicist Tallal Hashmi said:
@ItsAnilSingh When will the next version be released? Plz fix camera and network related bugs.btw good work.
Do I have to wipe SYSTEM before flashing? (Last time I did then I got error "No Os installed" and then installed lollipop v4 stable it doesn't booted, then I restored my phone to stock rom then wiped without SYSTEM then it worked so I think SYSTEM should not be wiped)
Click to expand...
Click to collapse
While flashing cm rom the installation script will eventually format system partition. So, its an optional step. But you need to clear the data, cache partitions. They are mandatory. Which can be simply done by "factory reset" option.
@ItsAnilSingh Hi I solved the white screen issue:
with that white screen I rebooted into recovery mode and flashed star kernel v3 and WHITE SCREEN IS GONE, now the cyanogen logo appears and the arrow goes around and doesn't do anything, I AM STUCK AT BOOT ANIMATION!!
---------- Post added at 08:01 AM ---------- Previous post was at 07:58 AM ----------
ItsAnilSingh said:
Were you using kernel 3.0.101 before? If yes, then you have to install latest stock rom through odin and then flash cm rom.
Click to expand...
Click to collapse
No,My kernel is now 3.0.8(I also tried star kernel v3 and beast pro)
Physicist Tallal Hashmi said:
@ItsAnilSingh Hi I solved the white screen issue:
with that white screen I rebooted into recovery mode and flashed star kernel v3 and WHITE SCREEN IS GONE, now the cyanogen logo appears and the arrow goes around and doesn't do anything, I AM STUCK AT BOOT ANIMATION!!
---------- Post added at 08:01 AM ---------- Previous post was at 07:58 AM ----------
No,My kernel is now 3.0.8(I also tried star kernel v3 and beast pro)
Click to expand...
Click to collapse
Those kernels wont work on cyanogenmod as they are for stock rom. Their ramdisks are entirely different and also the kernels too.
You need to update your stock rom first via odin as it will update the minimum baseband requirement for the kernel to work. Download latest stock rom and flash it via odin, then flash cm.
@ItsAnilSingh I am already on the latest stock rom....
@ItsAnilSingh
Video Recording does not work
Otherwise the ROM is excellent
ohhh great bro....good work...
dear @ItsAnilSingh
can exepct that mobile data and audio recording will be fixed in next build?
give me quick replay waiting......
when will beta2 release....just proper expectations...
thank you it's work very well hope you fix the video and audio recording
and is there any way to update to CM12 ? thank u again.
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:
[SIZE="7"][CENTER]MoKee ROM with TWRP-2.8.7.0[/CENTER][/SIZE]
Introduction
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
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.
*
* /
Root InfoRoot is now disabled by default on MoKee. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
Installation instructions
Coming from 5.0 or less
--> Format system, data, cache & dalvik cache
--> Install ROM
--> Install Gapps if required
--> Reboot
Coming from previous build
-->Wipe cache
-->Install ROM
-->Reflash Gapps
-->Reboot
Code:
[SIZE="3"][U]Changelog[/U][/SIZE]
[U]26/06/2015[/U]
Updated MoKee sources to 5.1.1_r3
TWRP updated to 2.8.7.0
Fixed offline-charge animation
Fixed video seeking forward/reverse
Compiled ROM & Kernel with SABERMOD Toolchain
Downloads
#include<ROM.dl>
#include<GApps.dl>
Video Review
XDA:DevDB Information
MoKee Lollipop, ROM for the i9100
Contributors
arnab, Lysergic Acid, MoKee Dev Team
Source Code: https://github.com/kularny
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2015-05-09
Last Updated 2015-08-15
Stock CM Kernel with TWRP-2.8.7.0 in Odin flashable format
I am attaching here the stock cm kernel with twrp-2.8.7.0 in odin flashable format along with the 1Gb-system/4Gb-Data pit file and Odin-3.09. Use this to recover from soft bricks and also the kernel can be used with other lollipop based ROMS. Flash the kernel with odin after installing the ROM of your choice. If you have used this kernel to repair a soft brick, you will have to again reflash the kernel after installing the ROM if you want to continue using this kernel. Happy flashing.
Love the boot animation! But oy... optimization phase text is in Chinese
sreinst1 said:
Love the boot animation! But oy... optimization phase text is in Chinese
Click to expand...
Click to collapse
Its only for one time during first run...you can uninstall the chinese stuff if u want to....btw plz check the new twrp recovery and plz report back if it functions properly and the ROM too.
Some first impressions
1. The ROM seems to have all the options that I like.
2. The initial setup automatically selected my language (Hebrew) so I didn't have to scroll through the list of languages at all - that was very nice; most ROMs start with English selected and I have to scroll half the list to get to Hebrew.
3. When switching screens during the setup, there's garbage at the bottom bar. I initially thought that was a CM problem, but since it exists also here and in PA, it's probably AOSP problem. It's not a real issue, just strange.
4. Networks speeds: After disabling it, it stops updating but the last status remains displayed in the status bar; I probably have to reboot to stop seeing it there.
sreinst1 said:
1. The ROM seems to have all the options that I like.
2. The initial setup automatically selected my language (Hebrew) so I didn't have to scroll through the list of languages at all - that was very nice; most ROMs start with English selected and I have to scroll half the list to get to Hebrew.
3. When switching screens during the setup, there's garbage at the bottom bar. I initially thought that was a CM problem, but since it exists also here and in PA, it's probably AOSP problem. It's not a real issue, just strange.
4. Networks speeds: After disabling it, it stops updating but the last status remains displayed in the status bar; I probably have to reboot to stop seeing it there.
Click to expand...
Click to collapse
I will now start working on DirtyUnicorns
arnab said:
I will now start working on DirtyUnicorns
Click to expand...
Click to collapse
Thanks, but I hope you will continue to publish Mokee builds as well... BTW, would it be difficult to have Mokee for i9100 official?
sreinst1 said:
Thanks, but I hope you will continue to publish Mokee builds as well... BTW, would it be difficult to have Mokee for i9100 official?
Click to expand...
Click to collapse
Ya definitely..I will also release a kernel in odin tar format containing latest twrp recovery and latest CM kernel that you can use with lysergic acid's builds.
arnab said:
I will now start working on DirtyUnicorns
Click to expand...
Click to collapse
Great, I would love to see DU 9.2 on my I9100.
arnab said:
Ya definitely..I will also release a kernel in odin tar format containing latest twrp recovery and latest CM kernel that you can use with lysergic acid's builds.
Click to expand...
Click to collapse
I don't understand, what's the relation of Mokee and Lysergic's builds?
How about my 2nd question - what would it require for your builds to become official?
Can you please upload some screenshots?
I meant with the twrp recovery...u can use cm12.1 with twrp
I can't say about official as the maintainers of i9100 repo are not updating the sources...I chose to work on mokee coz its unique soon to be implemented multi window feature.
Sent from my GT-I9100 using XDA Free mobile app
Ya ya...I will..jst gv me some time...by tonight I will upload screenshots.
Sent from my GT-I9100 using XDA Free mobile app
Thanks, donwloading
FYI, the phone just hang now, after ~7 hours of work... it was connected to charger and reached 100%. Came to take it from there, it didnt wake up - it hang.
arnab said:
Its only for one time during first run...you can uninstall the chinese stuff if u want to....btw plz check the new twrp recovery and plz report back if it functions properly and the ROM too.
Click to expand...
Click to collapse
Haven't yet checked the restore part but during backup I get a red error:
E: Unable to locate '/efs' partition for backup process.
Edit: Note that the backup continues. It seems to just skip the efs partition.
sreinst1 said:
FYI, the phone just hang now, after ~7 hours of work... it was connected to charger and reached 100%. Came to take it from there, it didnt wake up - it hang.
Click to expand...
Click to collapse
Il test and see the problem...thanx for reporting.
sreinst1 said:
Haven't yet checked the restore part but during backup I get a red error:
E: Unable to locate '/efs' partition for backup process.
Click to expand...
Click to collapse
I tested it...backup and restore works just fine...I purposefully disabled efs partition backup in twrp....it contains imei...radio info...ril info and many sensitive stuff..if during backup or restore process it gets messed...it will render your phone unusable.
just backup system, data & boot....I tested it. and after backing up...power off once before restore...the partitions get freshly mounted. And do not use backups of old twrp with the latest one...and backup with default selections.
To know the dangers ... read here EFS Dangers.
arnab said:
I tested it...backup and restore works just fine...I purposefully disabled efs partition backup in twrp....it contains imei...radio info...ril info and many sensitive stuff..if during backup or restore process it gets messed...it will render your phone unusable.
just backup system, data & boot....I tested it. and after backing up...power off once before restore...the partitions get freshly mounted.
To know the dangers ... read here EFS Dangers.
Click to expand...
Click to collapse
That's great then... can you make it skip efs completely and avoid the error?
sreinst1 said:
That's great then... can you make it skip efs completely and avoid the error?
Click to expand...
Click to collapse
I just now backed up...there is no error. see for yourself...plz partition your phone properly with 1gb system , 6gb data pit.
{
"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"
}
WELCOME TO CYANIDE L
ROM INFORMATION
Cyanide L is the brainchild of XDA member @rogersb11. Based on CyanogenMod, and packed full of features from the wonderful custom ROM teams we have all come to know and love. This ROM is just getting started and I will update frequently as things progress along into the beast we know this will be.
I (aniket.lamba) will hold no responsibility if you didn't flashed the ROM properly and are facing bugs due to your modifications to the system files.Want to help me with something? You're welcome for helping out with bugs and issues - - but make sure you have that logcat with you before posting in this thread.Post all your questions/requests/screenshots in the Q/A thread.I won't tolerate any OT posts in this development thread.
FEATURES LIST
Code:
App Circle Bar
*Gesture Anywhere
*Gesture Lockscreen
*Heads Up Notifications
*Shift Kernel by @rogersb11 built with Linaro
*Cyanide L Material Dark UI (Work in Progress)
*CustomToast, System, and ListView Animations
*Custom Power Menu Options
*Custom Quick Settings Tiles
*Colorized Statusbar Icon Options
*Colorized Notification Headers and Icons Options
*Screen Recorder
*Custom Navbar with custom actions and shorcuts
*Theme Engine
*PIE Controls
*MIUI Style Custom Carrier Label in Statusbar
*Long Click Support in Statusbar Header
*Cyanide Dungeon
*Much Much MUCH More...
GOOGLE PLUS COMMUNITY - This is where you will find the latest changelogs and other info and discussion about Cyanide L ROM. Device specific changes I will always list right here in the thread. But general changelogs will always be posted in the G+ community.
DOWNLOADS
**Special note to stock SII users: Please root your device and flash a custom recovery before flashing this ROM or else you'll have to face the consequences.**
CYANIDE L ROM for Galaxy SII (i9100) - Get the latest build here. (Current build RC-20) ... Older builds can be found in the same folder. Just click CyanideL and you can see all previous builds.
Gapps - Use the Minimal Gapps from this link - Minimal Gapps for 5.1.x
DISCLAIMER
You are choosing to install this ROM on your own merit. It is up to you to know the ins and outs, and know how to properly handle issues that may crop up. Neither Cyanide, your neighbor, or the Starbucks barista can be held liable for the following including, but not limited to: Exploding batteries, spontaneous combustion, soft brick, hard brick, one brick, two brick, red brick, blue brick.
ROM INSTALLATION
IF COMING FROM ANY OTHER ROM
1) WIPE DATA/FACTORY RESET
2) WIPE SYSTEM
3) Wipe Cache/Dalvik Cache
4) Flash the ROM and Gapps.
5) Reboot and PROFIT!!!!
6) Enjoy
IF UPDATING FROM OLDER VERSION OF CYANIDE
1) Wipe Dalvik, Cache
2) Flash ROM & Gapps
3) Reboot and PROFIT!!!!
KNOWN BUGS
Same as CM and also THIS POST RIGHT HERE - Please also read Post #2 before reporting bugs.
NOTE: ALSO NEEDS TO BE NOTED that yes, apparently Xposed for Lollipop is a thing now. BUT PAY ATTENTION TO THIS PART RIGHT HERE: Under NO CIRCUMSTANCES should I ever see a bug report or complaint if you are using Xposed. It is well known that Xposed doesn't always play nicely, and if you are using it and complain about some kind of bug, I will laugh you out of the thread. I hate being crass, but after dealing with so many repeat moronic questions, I felt like I should go ahead and state this now.
Thanks to Tarun Kapadia for providing me the fix for statusbar FC.Cheers buddy!
Special thanks to Lysergic Acid for providing Galaxy SII with the CM12.1 ROM and being open source.
Thank you and enjoy!!
XDA:DevDB Information
Cyanide L, ROM for the i9100
Contributors
aniket.lamba
Source Code: https://github.com/Lysergic-Acid & https://github.com/CyanideL
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Stock pre-rooted,TWRP recovery,ROM zip and minimal Google apps.
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: R2
Stable Release Date: 2015-09-19
Created 2015-05-23
Last Updated 2015-09-19
Reserved
Reserved
Frequently Asked Questions
Q: Why aren't my CM12 themes looking right?
Answer: Theme Chooser is still in its early stages and more and more items are being exposed for theming. So it's possible that some things may not look quite right still when applying a theme. Try going to the default system theme, reboot, apply your CM12 theme, and reboot once more.
Q: When will the next update be out?
Answer: When it's out and the OP is updated. Do not expect nightly builds or even weekly builds. I'm not going to run a build a day when it will make virtually nothing different. When I update, there will be good reason and timing for it. So please, don't ask.
Q: Can I use a custom kernel with this ROM?
Answer: You may run other kernels instead. HOWEVER, please pay attention to the troubleshooting section below concerning kernel use.
Q: Can you add [insert feature here]?
Answer: We are always open to feature suggestions. HOWEVER: Keep in mind that feature you have come to love in previous iterations of Android may not be ported forward for use in Lollipop yet. If you see a feature you want, and can point to somewhere that it's being used in a Lollipop rom, then we can definitely look into it. Otherwise, patience young grasshopper.
TROUBLESHOOTING
This ROM is still in the early stages of development, so you can expect some bugs to pop up here and there. Here are some guidelines to remember when reporting bugs to this thread. Please read carefully.
**Before reporting a bug, be sure you have tried the following:
1) If you dirty flashed, go back and clean flash first.
2) If you are running a custom kernel, flash the CM12.1 kernel from the and see if that solves your issues.
3) If the issue seems app related, uninstall the app and reinstall from the PlayStore. I won't give any help if your apps mess up from using TiBu. This doesn't constitute a clean install of an app.
4) Read through the thread to see if your issue has been addressed before and if their is currently a solution for it.
BUG REPORTNG
**I WILL NOT LOOK AT BUG REPORTS THAT HAVE NOT TRIED THE PREVIOUSLY LISTED STEPS OR LOGS THAT COME FROM A COMBINATION OF ANYTHING OTHER THAN THE ROM AND THE GOOGLE APPS.**
When you report a bug, be detailed about it. Simply stating "This is not working right" does not help me any at all, and I will probably just ignore the post. Be prepared to grab a logcat if asked or to provide me with the steps to reproduce the issue on my own device. If you don't know how to get a logcat, Google is your friend and there are multiple ways to do so. Also, search the thread, and search it again before reporting a bug, to be sure it hasn't already been addressed. No need to clog the thread with 10 people saying "This isn't working right".
PLEASE REFRAIN FROM PERSONAL GRIEVANCES IN THE THREAD. WE HAVE HAD RECENT ISSUES WITH THIS AND IT HAS BEEN SHOWN THAT IT WILL NOT BE TOLERATED ANYMORE.
Thx
Thx, will give it a try :good:
boot loop
ASRock86Cro said:
boot loop
Click to expand...
Click to collapse
Shouldn't happen.Do a dirty flash with full /system wipe and then report
thanks again
First let me know if the ROM boots for you or not so that I can fix the 'no bootup' issue as reported by ASRock86Cro.
Thanks again anekit.lamba
i install this rom with dirty flash, and still stay on boot loop
---------- Post added at 03:28 PM ---------- Previous post was at 03:27 PM ----------
aniket.lamba said:
Shouldn't happen.Do a dirty flash with full /system wipe and then report
Click to expand...
Click to collapse
i install this rom with dirty flash, and still stay on boot loop
ASRock86Cro said:
i install this rom with dirty flash, and still stay on boot loop
---------- Post added at 03:28 PM ---------- Previous post was at 03:27 PM ----------
i install this rom with dirty flash, and still stay on boot loop
Click to expand...
Click to collapse
Give me some logs.
Does your CM12.1 ROM by Lysergic boot up with SELinux set to permissive? I'm guessing so to be the cause of the 'bootloop' you're facing.
Me either on bootloop, try dirty flash,clean flash, on cm12.1 by lysgercic didnt get bootloop.
GreekDragon said:
Me either on bootloop, try dirty flash,clean flash, on cm12.1 by lysgercic didnt get bootloop.
Click to expand...
Click to collapse
Show me the screenshot of SELinux in about phone.
Maybe i didnt let time to your stock kernel version to boot your build, but now i flashed and use Apolo Beta9 CM version kernel, your rom boot fine now.
just have systemui FCs and bootloop.
at this step, i formated system/data/cache with twrp v2.8.5.0 and i reflashed your build + supersu 2.46 and rom never booted, i forced reboot but no boot
i retry apolo (CM version) and rom booted but still FC on SystemUI.
i try apolo OMNI version and its same FC on SystemUI.
finaly i patch your zip with boot.img and recovery-from-boot.p files from last CM12.1 (15/04 build) and dirty reflash over all that i have done before now and i can say (after 67 app optimied) that ALL IS FINE NOW (except some soft reboots, i hope its because i have 6% battery only)
this is my test and report .
Perfect,a new LP ROM wil be up by tomorrow.
aniket.lamba said:
Perfect,a new LP ROM wil be up by tomorrow.
Click to expand...
Click to collapse
i "cant" enable wifi Man, switch always return to OFF position, and it seems i have no data connection my device soft-rebooted 2 times when it tryied to receive one SMS (without receiving and notification but i ask my son to send me one ATM)
Troubadour666 said:
i "cant" enable wifi Man, switch always return to OFF position.
Click to expand...
Click to collapse
Strange,I guess there's an issue with the kernel.I'll look for a fix for all these issues soon.
aniket.lamba said:
Strange,I guess there's an issue with your kernel.I'll look for a fix for all these issues soon.
Click to expand...
Click to collapse
i hope its my config better than your build about data trouble (and wifi) , but it seems no-one have tested yet to see any <>cies VS me
bootloop
{
"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"
}
Rom Website!
Google+ Community!
Code:
/*
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Features:
Code:
Current Status:
Rock Solid
CM13 based
Custom Blur Launcher
Multi app split screen (enable in dev settings)
Kernel Config updated
Zip align
Odex
add my own version number to settings app
chromium (has ad blocker)
Build.prop
BUGS SMASH
CM changes
Custom Blur Status bar
Custom Blur Multitasker
Updated Launcher Blur
Original CM browser removed
Marshmallow open app animation (not built in cm13...)
Blur
Screen Recorder
LockScreen Colours
Custom Carrier label
Marsh Blur Settings
And some more features to check out.
Current list of changes to add:
More transparency
Status bar text greeting when you unlock the device
Something about addresses (read MAC address)
Amoled colors (postponed)
Downlaods! Hurray! :laugh:
MARSH-2.0-M-20160618-ghost.zip
Instructions!
Download and flash it like a MAN!
Credits!
And the credit goes to
Serjar for blur code and CyanogenMod!
and @Aaahh
Please hit that THANKS Button! It keeps me going! :good:
XDA:DevDB Information
[ROM][6.0.1_r46][BLURRED UI] Marsh 2.0 [CMTE][17/06/2016] [ghost] [INCENERATOR], ROM for the Moto X
Contributors
abinsur279
Source Code: http://github.com/MarshROM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Current Beta Version: 2.0
Beta Release Date: 2016-06-19
Created 2016-06-19
Last Updated 2016-06-19
Marsh rom by me,
Features list is incomplete, there's more to discover.
MOD EDIT: Do NOT spam or post the same comment in multiple threads!
are bugs same as in CM?
@abinsur279 are you God?
diegomartinezlovey said:
@abinsur279 are you God?
Click to expand...
Click to collapse
this rom have the same issues?? or is fixed?
diegomartinezlovey said:
@abinsur279 are you God?
Click to expand...
Click to collapse
Nope, Human xD
omy4069 said:
this rom have the same issues?? or is fixed?
Click to expand...
Click to collapse
This is CyanogenMod based ROM and has CM bugs (torch and others)....
Lock screen options make FC :/
Enviado desde mi Moto X mediante Tapatalk
Hi.
I tried at the weekend and the rom is awesome.
I will do it again at the next weekend.
Thanks to your work on our moto x1.
Enviado de meu Moto X usando Tapatalk
vijayid_94 said:
If you have Error like: "error executing updater binary in zip", than You'll require TWRP 2.8.7.2 that you can get Here.
Don't Forget to Factory Reset Before Flashing.
Thanks
Click to expand...
Click to collapse
Or delete the first line of updater script. If you want the original 2.8.7.0 recovery provided by twrp.
---------- Post added at 02:48 PM ---------- Previous post was at 02:25 PM ----------
If you tap on lock screen in settings app it crashes. I don't know if it is a bug related to cm or not.
All new ROMs do not boot for me
FalconDark4 said:
Or delete the first line of updater script. If you want the original 2.8.7.0 recovery provided by twrp.
---------- Post added at 02:48 PM ---------- Previous post was at 02:25 PM ----------
If you tap on lock screen in settings app it crashes. I don't know if it is a bug related to cm or not.
Click to expand...
Click to collapse
Even after updating TWRP I am unable to flash new roms, the version of TWRP still shows 2.8.7.0.
Could you please help?
Thanks.
update: no worries it is done, thanks.
kenosis said:
All new ROMs do not boot for me
Click to expand...
Click to collapse
Wipe Internal Memory :good:
abinsur279 said:
Wipe Internal Memory :good:
Click to expand...
Click to collapse
Also cyanide 5.0 detoxified boots?
abinsur279 said:
Wipe Internal Memory :good:
Click to expand...
Click to collapse
I wiped it but still cannot boot. Stuck at boot animation.
What I did is...
1. Wipe everything (Data, Cache, Dalvik, System, Internal Storage)
2. Install ROM & Gapps
3. Wipe Cache & Internal Storage
4. Reboot.
Edited: It can boot with Gapps from opengapps.org. Previously, I used Banks Dynamic Gapps and it did not boot.
stefanowall said:
Also cyanide 5.0 detoxified boots?
Click to expand...
Click to collapse
Better now its actually boots (bootloops at bootanimation) unlike the later builds which get stuck at boot logo! This bug may be reason for other ROM's like OWN and other ROMs not booting!
kenosis said:
I wiped it but still cannot boot. Stuck at boot animation.
What I did is...
1. Wipe everything (Data, Cache, Dalvik, System, Internal Storage)
2. Install ROM & Gapps
3. Wipe Cache & Internal Storage
4. Reboot.
Edited: It can boot with Gapps from opengapps.org. Previously, I used Banks Dynamic Gapps and it did not boot.
Click to expand...
Click to collapse
Glad that helped out! Can you tell me which date of BanKs Gapps you used? and did it boot without the GApps? That would help me a lot!!!:laugh::laugh::good::good:
abinsur279 said:
Glad that helped out! Can you tell me which date of BanKs Gapps you used? and did it boot without the GApps? That would help me a lot!!!:laugh::laugh::good::good:
Click to expand...
Click to collapse
I used Banks Gapps 24/06 build. I tried without Gapps but I did not boot.
I am currently on Turbo Rom
abinsur279 said:
Better now its actually boots (bootloops at bootanimation) unlike the later builds which get stuck at boot logo!
I understand you...yesterday, I tried to flash Cyanide 5.0 once again, obviously without success! I flashed it with Banks gapps...with opengapps, does it boot? ?
Click to expand...
Click to collapse
stefanowall said:
abinsur279 said:
Better now its actually boots (bootloops at bootanimation) unlike the later builds which get stuck at boot logo!
I understand you...yesterday, I tried to flash Cyanide 5.0 once again, obviously without success! I flashed it with Banks gapps...with opengapps, does it boot? ?
Click to expand...
Click to collapse
I will try to flash Cyanide later and will update.
Sent from my Moto X using XDA-Developers mobile app
Click to expand...
Click to collapse
stefanowall said:
abinsur279 said:
Better now its actually boots (bootloops at bootanimation) unlike the later builds which get stuck at boot logo!
I understand you...yesterday, I tried to flash Cyanide 5.0 once again, obviously without success! I flashed it with Banks gapps...with opengapps, does it boot? ?
Click to expand...
Click to collapse
No it doesnnot
Click to expand...
Click to collapse
{
"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"
}
Android. Infused with magical unicorn bytes
The unicorn eats nougat and oreo and farts rainbows
Hi,
Here is AOKP 7.1/8.1 for the Lenovo Vibe K5/K5 Plus
Requirements:
- TWRP 3.0.3+ build: Recovery TWRP 3.0.3-n1 for K5
- You can now use the Official TWRP builds
How to install:
From stock
Copy the ROM zip on your phone
Reboot in TWRP Recovery mode
Backup your phone!
Format/Wipe system, cache, dalvik, data
Flash/Install ROM
Flash Install Gapps (OpenGapps ARM64 Mini or smaller is recommanded)
Reboot
Upgrade from previous build
Copy the ROM zip on your phone
Reboot in TWRP Recovery mode
Format/Wipe only cache, dalvik
Flash/Install ROM
Reboot
Official Nightly builds Downloads:
http://xfer.aokp.co/?developer=AOKP&folder=A6020
https://basketbuild.com/devs/aokp/A6020
Old Beta builds Downloads:
https://moto.shreps.fr
XDA:DevDB Information
[ROM][OFFICIAL][7.1/8.1][A6020] AOKP-ROM - Lenovo Vibe K5/K5 Plus | OMS/Substratum, ROM for the Android General
Contributors
Shreps, scritch007
Source Code: https://github.com/AOKP/device_lenovo_A6020
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP 3 Recovery
Based On: AOKP
Version Information
Status: Nightly
Created 2016-11-15
Last Updated 2018-07-25
Reserved
AOKP Gerrit: http://gerrit.aokp.co/#/q/status:merged
This ROM now implements OMS.
What is OMS ?
OMS: (Overlay Manager Service) was designed by google. It's a layer/theme service which is used by Substratum: https://play.google.com/store/apps/details?id=projekt.substratum&hl=fr
So basically, if you install Substratum, you will be able to apply any theme on the ROM UI because OMS has been implemented.
For the record, on PAC MM or AOKP MM, they were using CyanogenMod Theme Engine for theming the UI, but since CMTE has not been implemented for Nougat, many choose to use OMS & Substratum instead.
Good job. BTW, where the list of what is working and not?
romulocarlos said:
Good job. BTW, where the list of what is working and not?
Click to expand...
Click to collapse
I don't own the device anymore. You will have to help me guys to create this list
Shreps said:
I don't own the device anymore. You will have to help me guys to create this list
Click to expand...
Click to collapse
Downloading Now !
later i edit this post with update. :
I think same as CM 14.1
In ROM control there is only one option.
Shreps said:
I don't own the device anymore. You will have to help me guys to create this list
Click to expand...
Click to collapse
Hello, thanks for the ROM
Issues that I have found
Auto brightness is changing itself for no aparent reason.
Bluetooth is not working (I will test a modification to build.prop to see if it fixes that)
Video recording( I will do more tests too)
The weird noise at boot(every custom ROM have it on l36)
Thats all for now.
After my tests I will update this post.
Oki doki I'm back
These chances to build.prop seens fo fixes some problen
# Bluetooth
qcom.bluetooth.soc=smd
This fixes bluetooth on cm14.1 and aokp
But this onde, it fixes video recording on cm14.1 without problens but Idk why it dindt worked on aokp
#Fix for l36 variant 1080p recording issue, special thanks to marchetto96
camera.disable_zsl_mode=1
persist.camera.HAL3.enabled=0
persist.camera.cpp.duplication=false
My device is a A6020l36
These changes on the build.prop where recomended by the k5 brazil(A6020l36) dev group, it may not work on other variants(only testing to know).
soon going to test it.
thanks for rom buddy any guess it will work for A6020a46 3GB variant too? or i have to test and check my self.
Making a backup right now of my PAC rom, to try AOKP.
So many ROM options Thanks for your hard work. I'll apply @BlueReptile post fixes and try if there is any left.
For Brazilians users "ro.product.model=A6020l36" should be enough to solve 1080p video play.
Anybody test if charging screen works? Or it has the same bug that cm has?
I'm facing a bootloop during the Setup Wizard: After a full wipe, i get the loop error "Configuration Wizard has failed - X Close app", and i can't proceed to boot up AOKP and finish it's setup.
Code:
[[email protected] AOKP]$ ls -l
-rw-r--r-- 1 risthel users 499274693 nov 10 17:55 aokp_A6020_nougat_unofficial_2016-11-10_1622.zip
-rw-r--r-- 1 risthel users 82 nov 15 15:05 aokp_A6020_nougat_unofficial_2016-11-10_1622.zip.md5sum
-rw-r--r-- 1 risthel users 117639063 nov 11 04:47 open_gapps-arm64-7.1-pico-20161111.zip
-rw-r--r-- 1 risthel users 73 nov 15 19:06 open_gapps-arm64-7.1-pico-20161111.zip.md5
The ROMs and gapps are sane(recovery matched the md5).
Also tried to reboot, clear Dalvik/Art and boot again without success
Ironmaniaco said:
I'm facing a bootloop during the Setup Wizard: After a full wipe, i get the loop error "Configuration Wizard has failed - X Close app", and i can't proceed to boot up AOKP and finish it's setup.
The ROMs and gapps are sane(recovery matched the md5).
Also tried to reboot, clear Dalvik/Art and boot again without success
Click to expand...
Click to collapse
You should try without Gapps with a system wipe to check if it's not because a Gapps issue.
Shreps said:
You should try without Gapps with a system wipe to check if it's not because a Gapps issue.
Click to expand...
Click to collapse
pushing aokp to phone through adb(already did the full wipe)
Meanwhile, ill download gapps-nano arm64 for further testing.
---------- Post added at 08:46 PM ---------- Previous post was at 08:24 PM ----------
Shreps said:
You should try without Gapps with a system wipe to check if it's not because a Gapps issue.
Click to expand...
Click to collapse
Hi @Shreps. Sorry for the double posting/flooding.
Did my homework, AOKP flashed fine. Meanwhile, i was researching and found that opengapps can have this issue as explained here
Since i'm not dirty flashing neither upgrading this was my workaround for this situation:
Installed AOKP
Booted without gapps
Created this script file(i'm using Arch Linux as main desktop) and push it using adb while running AOKP
adb shell to run this script
reboot into recovery
clear dalvik/cache
push opengapps to /sdcard and flash it
reboot to system
profit?!
System wizard working as expected. Can't say for sure if the problem is with gapps-pico on 11 november build, cause the script seems to solve the permission issues.
gonna test today downloading now,
but here are something all the user of A6020a46 3GB variants may know that, bluetooth is fixed after apply this to build.prop
Code:
qcom.bluetooth.soc=smd
red border already fixed also brightness is fixed temporary through brightness pacher, now major thing is Video Recording which not work for me in any 7.1 based ROM(CM14.1, AICP,BeanStalk,crDroid and i guess same for AOKP) so if you guys fixed any new or old bugs please reply soon to related thread about it so many can solve their problems.
flashed AOKP 16.11.2016 build i. e. latest one, everything working except video recording, it is not working no matter how much camera app i tried :'(
BHARDIK said:
flashed AOKP 16.11.2016 build i. e. latest one, everything working except video recording, it is not working no matter how much camera app i tried :'(
Click to expand...
Click to collapse
Have you tried this fix?
Code:
camera.disable_zsl_mode=1
persist.camera.HAL3.enabled=0
persist.camera.cpp.duplication=false
Ironmaniaco said:
Have you tried this fix?
Code:
camera.disable_zsl_mode=1
persist.camera.HAL3.enabled=0
persist.camera.cpp.duplication=false
Click to expand...
Click to collapse
yeah tried not working for me, i guess as because i have different variant then yours, mine is 3GB Variant with FHD and Spandragon 616 , i guess you have A6020a40 with 2 GB RAM and snapdragon 415 ,while i have A6020a46 :'( any way thanks for info
Regard,
Hardik
OK. Had to change my daily ROM to CM-14.1.
AOKP crashed hard after upgrading(build day 11 to build day 15), and the fix_permissions script didn't solve this time. Google related apps kept crashing even after a cache/dalvik wipe... Could be something mainstream of AOKP. I'll search for info on it's repos.
Spent last night trying CM14, AICP and BeanStalk. Clear flashed all of them, and the only one that didn't accepted gapps without fixing permissions was aokp unfortunately. Last thing i did was to upgrade aokp with gapps installed, and it reproduced the same problem.
Thanks again for your hard work guys. I'll keep testing all your roms
Hello. Installed version of yesterday, writes setup wizard is broke and can not move into recovery.
What changed in the last build?
tinti1998 said:
Hello. Installed version of yesterday, writes setup wizard is broke and can not move into recovery.
Click to expand...
Click to collapse
you have to flash AOKP then reboot your device once its rebooted to normal mode tick advance reboot on from developer settings >then reboot recovery again and flash gapps pico version, then its fine.
Regard,
Hardik
NOTE: these builds are EXPERIMENTAL. Use them at your own risk!
{
"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 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
These builds contain a working HWComposer based off @tdcfpp's work. Note that currently the HWC only reliably works in portrait mode. Landscape is more complex, and getting a smooth UI would involve some work on the kernel (adding sync_fence support to the kernel drivers for FIMG2D and FIMC). In the majority of use-cases you should see improved UI fluidity, especially once apps are already loaded into RAM.
Installation
You cannot "dirty flash" from official weekly builds. You have to factory reset before installing. If you need more instructions, you shouldn't be installing this build
Download
2017-10-29
Known issues
HWC is disabled in landscape mode
Building from source
Assuming you already have a source tree set up, and all the official repos downloaded, you need to add a file like this to your local_manifests and cherry-pick these commits. Then, just "brunch i9300".
What is the HWComposer?
The HWComposer is a library that allows Android to use display hardware to render multiple 'layers' on screen, such as the status bar, the wallpaper, and the home screen. By default, Android uses the GPU to manage this rendering, which is considerably less efficient than using the dedicated display hardware.
Found a bug?
If the bug happens on official builds as well, please don't report it here. The main issues I'm interested in are:
Hardware not working at all (e.g. GPS is broken)
Media encoding/decoding issues (e.g. Netflix)
Display issues (e.g. screen turns black and won't turn back on, or some parts of the screen turn black)
Please use this template, and attach a logcat. (A rough timestamp of when the issue occurred is also useful)
Code:
What is the issue?
How did you cause the issue?
Output of "adb shell dumpsys SurfaceFlinger" while the issue is on-screen (in the case of display issues)
I don't have a huge amount of time to spend doing this at the moment, but I will try and keep up with any major issues.
XDA:DevDB Information
Experimental LineageOS 14.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444, tdcfpp
Source Code: https://github.com/fourkbomb/android_kernel_samsung_smdk4412/tree/cm-14.1-rebase
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2017-10-29
Last Updated 2017-10-29
Reserved
Finally the dream become true , you are a great person @forkbomb444..
Testing ..
so will hwcomposer works with custom kernel such as boeffla kernel?
Another question: hwcomposer was broken since cm9 or cm10 until now?(unless nameless rom) but last time i had tried cm12 rom by trafalgar square the ui was smooth
I am soo happy!!!
i.am.newbie said:
so will hwcomposer works with custom kernel such as boeffla kernel?
Another question: hwcomposer was broken since cm9 or cm10 until now?(unless nameless rom) but last time i had tried cm12 rom by trafalgar square the ui was smooth
Click to expand...
Click to collapse
It will work only with this kernel.
Option58 said:
It will work only with this kernel.
Click to expand...
Click to collapse
so there is no difference with nameless rom bcuz needs stock kernel support?
i.am.newbie said:
so there is no difference with nameless rom bcuz needs stock kernel support?
Click to expand...
Click to collapse
HWC required forkbomb to make changes in the kernel. So no custom kernels.
Hmm seems like i can't boot it up. I am stuck at "Samsung galaxy s3" and the phone turns off and back on at the same screen.
I wiped Data,system,cache.
Then i tried flashing one after another:
This build, gapps, boeffla kernel and addonsu.
Then i read i shouldn't use a custom kernel and did all of this over again but i just flashed the build and nothing else. Still the same, phone loops at the first screen.
LuciferIII said:
Hmm seems like i can't boot it up. I am stuck at "Samsung galaxy s3" and the phone turns off and back on at the same screen.
I wiped Data,system,cache.
Then i tried flashing one after another:
This build, gapps, boeffla kernel and addonsu.
Then i read i shouldn't use a custom kernel and did all of this over again but i just flashed the build and nothing else. Still the same, phone loops at the first screen.
Click to expand...
Click to collapse
me too having bootloop at Samsung Galaxy SIII logo @forkbomb444 any idea.
Yessssss !!!!!!!! ????????
hi guys, I wanted to flash this experimental on my s3 i9300, can you use it daily? someone tried it?
in any case this I try
thanks ×forkbomb444×
I hope soon to have her official lineageos 15 on my i9300
lollo.21 said:
hi guys, I wanted to flash this experimental on my s3 i9300, can you use it daily? someone tried it?
in any case this I try
thanks ×forkbomb444×
I hope soon to have her official lineageos 15 on my i9300
Click to expand...
Click to collapse
Just in case you missread something, this is not Lineage15.
LuciferIII said:
Just in case you missread something, this is not Lineage15.
Click to expand...
Click to collapse
I wonder why I'm not expert, this is not Android Oreo experimental?
lollo.21 said:
I wonder why I'm not expert, this is not Android Oreo experimental?
Click to expand...
Click to collapse
No, this is experimental build that has HWcomposer working.
In a nutshell, HWcomposer will make us get better performance and battery, and its related to display making it smoother.
Until Simon fixes the HWcomposer for Lineage14.1, we probably won't get a Lineage15 build.
The fact that we got a experimental build for HWcomposer probably means it won't take long until Simon fixes the Hwc completly and he starts working on Lineage15.
Also, Simon = Forkbomb444
Bootloop issues are solved / not experienced if you wipe everything but internal storage and do a completely clean flash. I used aroma open gapps and lineage su. Later I used black substratum theme, so far so good. Did some changes to build.prop to support 60fps and the phone is smooth as butter. Thanks Simon! I think we finally have a 99% fully functional HWC!
Edit: Also it made a noticable battery life improvement and the blacks are deep & full now!
(System font used is Product Sans (from Pixel 2, flashable zip) and Lawnchair Launcher);
LuciferIII said:
No, this is experimental build that has HWcomposer working.
In a nutshell, HWcomposer will make us get better performance and battery, and its related to display making it smoother.
Until Simon fixes the HWcomposer for Lineage14.1, we probably won't get a Lineage15 build.
The fact that we got a experimental build for HWcomposer probably means it won't take long until Simon fixes the Hwc completly and he starts working on Lineage15.
Also, Simon = Forkbomb444
Click to expand...
Click to collapse
ok, now I have all the information, curious to hear this experimental hwc, thank you
Elton47 said:
Bootloop issues are solved / not experienced if you wipe everything but internal storage and do a completely clean flash. I used aroma open gapps and lineage su. Later I used black substratum theme, so far so good. Did some changes to build.prop to support 60fps and the phone is smooth as butter. Thanks Simon! I think we finally have a 99% fully functional HWC!
Click to expand...
Click to collapse
explain me what to change or add in the build.prop to have 60fps?
Elton47 said:
Edit: Also it made a noticable battery life improvement and the blacks are deep & full now!
(System font used is Product Sans (from Pixel 2, flashable zip) and Lawnchair Launcher);
Click to expand...
Click to collapse
link download zip? so I try
Elton47 said:
Bootloop issues are solved / not experienced if you wipe everything but internal storage and do a completely clean flash. I used aroma open gapps and lineage su. Later I used black substratum theme, so far so good. Did some changes to build.prop to support 60fps and the phone is smooth as butter. Thanks Simon! I think we finally have a 99% fully functional HWC!
Click to expand...
Click to collapse
Thats what i did
LuciferIII said:
Then i tried flashing one after another:
This build, gapps, boeffla kernel and addonsu.
Click to expand...
Click to collapse
Sorry, I thought this is what you did earlier (flashing Boeffla).
That might've caused the bootloop.
---------- Post added at 09:54 PM ---------- Previous post was at 09:51 PM ----------
lollo.21 said:
ok, now I have all the information, curious to hear this experimental hwc, thank you
explain me what to change or add in the build.prop to have 60fps?
link download zip? so I try
Click to expand...
Click to collapse
60 FPS:
add this to the bottom of build.prop
persist.sys.NV_FPSLIMIT=60
Product Sans font (for LineageOS, any LOS Version, just flash it and no need to wipe any cache / dalvik):
https://forum.xda-developers.com/attachment.php?attachmentid=4314287&d=1509009279
Cheers!