Related
CodeName Android is now officially supported on the Vibrant so this thread's life is at an end.
Go here:http://codenameandroid.com/cna-1-5-0-add-multiple-devices-and-nightly-builds/ to get the latest nightly build.
or in XDA here for sixstringsg's build:http://forum.xda-developers.com/showthread.php?t=1531135
HERE WE GO with CodeNameAndroid 1.4.0 Nightlies for my (or your) Vibrant. This is pure CNA. It is from a I9000 (nightly) build made by Bubble-be from the 02-26-2012 source.
Bubble-be’s thread: http://forum.xda-developers.com/showthread.php?t=1512938
It is a straight build from source, nothing added, nothing changed. I have only ported it to the Vibrant. GAPPS is not included so you will need to flash GAPPS after flashing the rom. I have removed the asserts in the update script so be sure you have a T-Mobile SGH-T959 Vibrant before flashing.
Please visit and donate at the CodeName Android Development Site @ http://www.codenameandroid.com
This is a port that I personally made for myself. I liked it so much I decide to share with all here.
If you are an experienced user try it out. As I made this for me, what you see is what you get.
Do not expect support, although I will try to help if you have problems. Please visit the pages linked above to get info and change logs etc.
Additional issues fixed in the 02/26 nightly besides those in the below change log.
* RIL issue (not correctly registering signal strength and taking a long time to get a signal after reboot) has been fixed.
* External SdCard now mounts properly on the PC
1.4.0 Changelog
* common: CNASettings has been merged into settings and has been completely re-writen to work better on both phones and tablets
* common: removed google apps from compile
* common: added the file manager back
* common: wait to lock screen (romanbb)
* common: webos style recents (Zaphod-Beeblebrox)
* common: better rotation control options (Team Eos)
* common: Added CombinedBar Auto Hide (Flemmard)
* common: all lockscreen graphics have been improved and resized (androiduser)
* common: root is now option (cyanogen – in developer options)
* common: faster transition animations in the launcher (nebkat)
* common: Hiding media from folder with .nomedia file. (cyanogen)
* common: all battery and clock customizations now work on tablets
* common: enabled the Notification Power Widget Enable on tablets (TDR)
* common: improved scrolling chache for much smoother scrolling (pawitp)
* common: zRam and Kernel samepage merging (cm – performance -> memory management)
* common: option for always enabling battery percentage on the lock screen (whitehawkx)
* common: improvements made to the lockscreen to work better on both phones and tablets (codenamedroid)
* common: phone target is now replaced with browser when compiled for tablets
* common: camera unlock target is now always accross from the unlock target to emulate the stock android lockscreen layout
* common: Increase Zygote preload GC threshold to half the heapgrowthlimit for faster boot times (Vijay Dandiga)
* common: fully configurable power menu (romanbb for screenshot and codenamedroid for reboot and airplainemode – Interface -> General)
reboot and screenshot options disabled by default to be more in line with stock
* common: made clock on big clock a tab bit smaller: looks nicer and works better on phones with smaller screens
* common: Profiles – Quiet Hours – gives the ability to have certain sounds, vibrations, and notifications to mute a specific times (DvTonder)
* common: fast torch – enable flash light from lockscreen by holding down on the power button while the screen is off (Zaphod-Beeblebrox – Interface -> Lockscreen)
This port includes:
CNA 1.4.0 nightly(I9000)-02/26/2012, Thanks to Bubble-be
Icy Glitch V14b5 Kernel, Thanks to sixstringsg
KB5 modem, Thanks to scrizz
GPS files compilation, Thanks to hurtz777
Keylayout files, build.prop edits, updater-script edits
CNA 1.4.0 nightly (02/26): http://dl.dropbox.com/u/17980900/cna_1.4.0_nightly_02-26_vibrant.zip
GAPPS 02/24/2012: http://dl.dropbox.com/u/17980900/gapps-ics-20120224-signed.zip
A full wipe Flash is recomended for the first install.
My installation method:
Wipe data/factory reset
Wipe Cache
Format /system
Flash rom
Flash GAPPS
Wipe Dalvik
Fix permissions
reboot recovery
reboot system, wait 10 min for Dalvik cache to build
reboot system
Older ports
CNA 1.4.0 nightly 02/23
Rom: http://dl.dropbox.com/u/17980900/CNA_4.0.3_v1.4_2-24-2012_Vibrant.zip Kernel is Nelsons v12 b8 for ICS Passion
GAPPS 02/15/2012: http://dl.dropbox.com/u/17980900/gapps-ics-20120215-signed.zip
DaxINFINITY ported the CodeNameAndroid rom from the Nexus S to the I9000. http://forum.xda-developers.com/showthread.php?t=1485734. 1.3.2 and 1.3.3 are ports of ports. GAPPS are included.
Here's the flashable zip of CNA 1.3.2 ported to the Vibrant (includes gps fix also) http://dl.dropbox.com/u/17980900/CNA_4.0.3_1.3.2_Vibrant-signed.zip
Here's the flashable zip of CNA 1.3.3 ( GPS works but it does not survive deep sleep) http://dl.dropbox.com/u/17980900/CNA_4.0.3-1.3.3-Vibrant-signed.zip
No Wipe needed over CNA 1.3.2, full wipe is OK and probably recomended if you are using a kernel other than stock.
Do a backup, try it out.
Best ICS if used!
I've been using this for about 4 hours and I have to say this is the smoothest most customizable ics rom I have used.
And thank you for posting all the need files, would have been nice when I flash this earlier.
jeremy2420 said:
I've been using this for about 4 hours and I have to say this is the smoothest most customizable ics rom I have used.
Click to expand...
Click to collapse
Yeah, It's pretty sweet. I haven't run into any bugs yet.
The only thing I found is that the signal bars are full when you have service but nothing in between. So it shows either you have no service or full service but that's not a big deal.
jeremy2420 said:
The only thing I found is that the signal bars are full when you have service but nothing in between. So it shows either you have no service or full service but that's not a big deal.
Click to expand...
Click to collapse
I also have a no go on GPS. I need to find the right GPS files to insert.
edit: Flashed the Passion v9+gps kernel then then Passion b8 kernel on top of it rebooted and now gps locks.
edit: I put full rom up for download with gps fix in the OP.
bobshute said:
I also have a no go on GPS. I need to find the right GPS files to insert.
edit: Flashed the Passion v9+gps kernel then then Passion b8 kernel on top of it rebooted and now gps locks.
edit: I put full rom up for download with gps fix in the OP.
Click to expand...
Click to collapse
Nice work, just a heads up I'm using the latest glich(b3) and got black screen after unlocking. But then I just locked then unlocked again and it was fine.
Edit: oh and by the way I don't think I'll go back to another ics rom, it has been that good!
The bomb
This rom is the bomb.....thanks Bob
WOW.
This is a pretty damn smooth rom. Smoother than the experience i've had with Passion.
Bob, I want you to make a [PORT] thread in the dev section. This is a really good ROM that you've ported. and I thank you.
I came directly from V13 Passion, no wipe. Did follow instructions from OP.
Some notes: The Bootanimation looks really low quality and pixelated.
Are you using the same kernel as Passion? It has the same image for the kernel loader.
The rom boots up REALLY fast.
Errors:
Currently my Market is NOT working. Rebooted, and I will perform OTHER things to try and fix it, but the error is "SERVER ERROR =RETRY="
I tried Wiping DATA,CACHE etc.
I will now try to push another VENDING.APK from the actual rom into this.
Cancel that, tried it, did not work. Also I looked in this ROMS System/APP and there is no Vending.apk ...?
=====================================================
I TRIED TO FLASH FROM ABSOLUTE WIPE market still does not work.
Another problemo: External SD does not show up mounted on computer.
Another: It takes a LONGGGGGGGGGGGGGGGGGG time to get signal for me.
Haven't tested if its just the signal not updating itself or not...
If nothing works, i'll wipe data(format) and then try again. This seems like a good rom to try out. I'll let others know as well.
*so far recommended to try by me, the smoothness is amazing.
xriderx66 said:
Errors:
Currently my Market is NOT working. Rebooted, and I will perform OTHER things to try and fix it, but the error is "SERVER ERROR =RETRY="
I tried Wiping DATA,CACHE etc.
I will now try to push another VENDING.APK from the actual rom into this.
Another problemo: External SD does not show up mounted on computer.
Click to expand...
Click to collapse
Not sure about the market mine is working, but the external sd is a know problem. They are working on a fix in the next release over in the i9000 forum.
Mine also takes a while to get service, about a min if not more after boot.
xriderx66 said:
WOW.
This is a pretty damn smooth rom. Smoother than the experience i've had with Passion.
Bob, I want you to make a [PORT] thread in the dev section. This is a really good ROM that you've ported. and I thank you.
I came directly from V13 Passion, no wipe. Did follow instructions from OP.
Some notes: The Bootanimation looks really low quality and pixelated.
Are you using the same kernel as Passion? It has the same image for the kernel loader.
Errors:
Currently my Market is NOT working. Rebooted, and I will perform OTHER things to try and fix it, but the error is "SERVER ERROR =RETRY="
I tried Wiping DATA,CACHE etc.
I will now try to push another VENDING.APK from the actual rom into this.
Another problemo: External SD does not show up mounted on computer.
If nothing works, i'll wipe data(format) and then try again. This seems like a good rom to try out. I'll let others know as well.
*so far recommended to try by me, the smoothness is amazing.
Click to expand...
Click to collapse
Thanks, Things I've noted.
External SD does not show up on computer but works on phone.
It sometimes takes awhile after reboot to get phone service, but it comes. toggling wifi usually turns it on.
In the reboot menu it looks like reboot is selected but it's actually recovery. select reboot again and you're fine.
I'm using the Passion v12 b8 kernel. I tried Glitch but didn't like.
My market worked fine, but I have either upgraded from Passion v12 or did a wipe and started from scratch.
GPS works fine after a boot but IDK if will continue after deep sleep.
After a clean wipe, market is still not working, and it is not my wifi connection, i tried browser and went to other websites, and it works.
Anyone mind giving me their Vending.apk or something and tell me where to put it i thought it was system/app
Or anyone know what to do about Market problem?
jeremy2420 said:
Not sure about the market mine is working, but the external sd is a know problem. They are working on a fix in the next release over in the i9000 forum.
Mine also takes a while to get service, about a min if not more after boot.
Click to expand...
Click to collapse
I've been working on a 1.3.3 port but they changed a lot. and GPS is hosed so far, won't stop pinging, will probably drain the battery fast. If I can figure it out I'll post it.
xriderx66 said:
After a clean wipe, market is still not working, and it is not my wifi connection, i tried browser and went to other websites, and it works.
Anyone mind giving me their Vending.apk or something and tell me where to put it i thought it was system/app
Or anyone know what to do about Market problem?
Click to expand...
Click to collapse
Here's the latest gapps. Try flashing it. It has vending.apk.
http://dl.dropbox.com/u/17980900/gappsv7.zip
Here's the bootanimation I use. Blueplasma from Nexus S. tired of expolding rainbow.
http://dl.dropbox.com/u/17980900/BluPlazmaII-Nex.zip
ignore my issues about market, i rebooted for the... 6th time and then it decided to finally let me into Google Market. haha
Anyways i'll give it a shot for a day, and regarding the post above the one you posted, I don't have a data plan, so I don't ever use GPS anyways. Is there a way I can shut it off from pinging so much? remove gps files itself or something??
thanks for the great rom bro.
aww it doesn't have ICS style blue checkmarks
xriderx66 said:
ignore my issues about market, i rebooted for the... 6th time and then it decided to finally let me into Google Market. haha
Anyways i'll give it a shot for a day, and regarding the post above the one you posted, I don't have a data plan, so I don't ever use GPS anyways. Is there a way I can shut it off from pinging so much? remove gps files itself or something??
thanks for the great rom bro.
aww it doesn't have ICS style blue checkmarks
Click to expand...
Click to collapse
The Gps is fine in the 1.3.2 Rom posted. It's the 1.3.3 that I'm trying to port where it's fudged up.
bobshute said:
The Gps is fine in the 1.3.2 Rom posted. It's the 1.3.3 that I'm trying to port where it's fudged up.
Click to expand...
Click to collapse
Hey bob if its giving you that much trouble, 1.3.3.1 is going to be released tomorrow with some fixes, so maybe wait till then. And a quick Q; where do you replace the kernel files in the rom zip so i dont have to flash it afterwards?
Alright thanks man, bootanimation goes in system/media correct?
Also, MAKE A THREAD FOR THIS RIGHT [email protected]$#@%[email protected]
IDK if you're going to keep the same name from ported rom or make a new one, but if you decide on a new one, make it something interesting something thats fun to say
xriderx66 said:
Alright thanks man, bootanimation goes in system/media correct?
Also, MAKE A THREAD FOR THIS RIGHT [email protected]$#@%[email protected]
IDK if you're going to keep the same name from ported rom or make a new one, but if you decide on a new one, make it something interesting something thats fun to say
Click to expand...
Click to collapse
The boot animation is a CWM flashable. or pull bootanimation.zip out and put in system/media.
Any ideas about the bit of lag i'm getting? It's mostly in the Settings app, I for example, uncheck/check something, it just holds for like 5 seconds and then registers my touch.
xriderx66 said:
Any ideas about the bit of lag i'm getting? It's mostly in the Settings app, I for example, uncheck/check something, it just holds for like 5 seconds and then registers my touch.
Click to expand...
Click to collapse
I'm not sure. I get it sometimes too, then it goes away. Something must be running in the backround. Try closing out apps in the app switcher and see if it helps.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
ROM:http://d-h.st/myfiles?fld_id=28773#files (just look for the one with the newest date on it
Gapps:http://forum.xda-developers.com/showthread.php?t=2012857
use what ever gapps you want but i personally use these ones since its just the basic stuff and its art compatible
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
No access to TV-Out menu
Layout issues in lockscreen
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Privacy guard icon not disappearing when exited app
Broken layout of quick message popup (SMS)
Cannot set value via custom brightness "Edit" menu
If back button is pressed during incoming call, you can't answer the call.
FC when changing image sharpness
Pressing "menu" unlocks swipe lockscreen
Browser: FC in incognito mode and Advanced -> Website settings)
Quick Access Ribbon gone when switching from Quick Settings
2G/3G toggle does not work
Cannot flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Is there a changelog for gapps?
I did not create the packages and do not know. (Please don't annoy the original developer of the packages by asking him either.)
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
the above gapps are what i personally use you can use what ever ones you would like though
Thanks to
pawtip
CM team
FaultException
Kasper_h
anyone else who i forgot pm me and il add you
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
n205des said:
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
Click to expand...
Click to collapse
Deleted
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
ankamar92 said:
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
Click to expand...
Click to collapse
Basicly
New build soon with some kernel modifications to make it even smoother
All the post is C&P from Pawitp i9000 post lol (except links and credits)
But, whatever, I'll download the rom right now, and will try it later..
BTW, gapps links doesn't work.
And..
cannondaleV2000 said:
Deleted
Click to expand...
Click to collapse
What do you mean with "DELETED"? Fixed?
Thanks for your work ^^
When i installed this, all i got was the little cyanogen robot with the rotating arrow, that lasted for about an hour until i got frustrated with it and just went back to my old rom, any ideas on why this is happening?
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Link gapp error ,file not found
cannondaleV2000 said:
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, ok, but that not answer my question, the problem with the speaker on receiving call, is fixed?
You answered that to another user --> "Deleted", Deleted == Fixed?
Thanks.
should be. i have not run into the isue so far been running since lastnight.
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
cannondaleV2000 said:
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
Click to expand...
Click to collapse
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
OK will fix
Sent from my SGH-I897 using xda app-developers app
Sorry guys I just realized I uploaded the wrong file. Il fix it tomorrow and post a new link
ManaSV93 said:
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
Click to expand...
Click to collapse
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
mohammad.afaneh said:
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
Click to expand...
Click to collapse
Yep noticed that will fix after school. Because I also uploaded the wrong file top
Downloaded first version, and, have to say that the performance is awesome.
Ram: constant 170 mb free, using BBM, and listening some music.
Web Browser performance was better on CM 10.1
And, with all the KK builds I have tried on the cappy, Every time I turn ON the phone, When OS is completely loaded, I get a message, of invalid IMEI, and that, I can have some problems..
How can I solve this? If I go back to stock rom, and then to CM 10.1, I don't have any problem with this, but when I update to CM 11, I have this error, and don't know wich errors can this give me on future.
Any screenshot ?
SlimJB4.3 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in Jellybean 4.3, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz6.07.9 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of SlimBean4.2, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimBean4.3 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). This is the latest SlimBean4.3 and has all of the features of a SlimRom that you've come to love. Don't forget to download the special gapps package to get the full SlimBean experience while using "The Real Dark Slim" feature.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THE PAGE
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files. You can still view these mp4 files, but you must open them with a file manager directly into the video player instead of using the gallery to access them.
* The camcorder records just fine, but when playing back the video, it's just a distorted video. Audio is fine, and I have not tested video with a third party app. If you test one and it works, please post that here so that others may benefit from your findings.
This seems to have been fixed as of the 20140121 build
* The latest Google Drive seems to be missing classes and will not open. This may be due to a missing content provider or may be a bug with the Google Drive app itself.
Solution: The solution for this is to uninstall the latest version of Google Drive, then go to Settings -> Security and enable Unknown Sources. Then open the Play Store and turn off automatic updates or it will end up overwriting the older version and you will be left with a non-working Google Drive again. Once all that is complete, download and install this Google Drive instead:
com.google.android.apps.docs.apk (8.4MB)
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 or Philz Advanced/Touch Recovery flashable zip which is compatible with SlimBean4.2/SlimBean4.3
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (or the Philz one) that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140121 (Latest)
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20140121-0353.zip (114MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20140121.zip (147.3MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20131228
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20131228-1427.zip (126.1MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20131228.zip (160.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with SlimBean4.2/SlimBean4.3/SlimKat
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with SlimBean4.2/SlimBean4.3/SlimKat
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with SlimBean4.2/SlimBean4.3/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]January 21, 2014 - Build 20140121[/B]
* Synced with upstream sources (CyanogenMod/SlimRoms)
* Added SystemUI memory management fix
* Removed 91fixoverlays init.d script as it's no longer required
* Implemented fix for the char dev driver - fixes the vibrator not loading on boot
[B]January 03, 2014 - Build 20131228[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. There is a script that has been included with this ROM in the init.d that sets that on every boot so you shouldn't have to.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* SlimRoms Team - ROM Base
Without all of the hard work and efforts of the SlimRoms team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* @dsixda - Initial port of CM9/CM10 for SGH-I757M
* @Strange Peer - Continued development of CM10
* @rukusx7 - Contributor
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL SlimJB4.3 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimBean
Version Information
Status: Alpha
Created 2014-01-03
Last Updated 2014-01-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Reserved
Yay a slim bean of 4.3! Woot.
Sent from my SGH-I757M using xda app-developers app
Hi Shouldn't this be in the development forum
Awesome! Was hoping for a new slim build! Thanks so much TF! Great job!
Sent from my SGH-I757M using xda premium
68544455 3521
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Hey
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
JayR_L said:
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Click to expand...
Click to collapse
I'll add back the mdnie settings. They are supposed give you control of the temperature
GrAt_On said:
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
Click to expand...
Click to collapse
Only difference is in features and it's been slimmed down.Other than that, it's the same ROM. I just posted it for those who like the slim features check this page out for the list of slim features:
http://www.slimroms.net/index.php/slim-bean-features
Sent from my SGH-I757M using XDA Premium 4 mobile app
The Iron Man said:
Hi Shouldn't this be in the development forum
Click to expand...
Click to collapse
I've only posted or ROM's here since that's where dsixda was told to post them back when he started with this device. If the mods would prefer I post them in the dev section, I'm more than happy to oblige
Sent from my SGH-I757M using XDA Premium 4 mobile app
Amazing
I just flashed it, its amazing! Especially "The Real Dark Slim"! However, I did notice Google + doesn't work properly asking me to re install it at the play store. Had to uninstall using Titanium Backup and then install it back via app store, not sure now whether it has the the real dark slim feature integrated in google +. Other than that, it's really smooth so far Great port.
UPDATE: Google drive also doesn't work as it force closes continuously even after wiping dalvik's cache. I'll try redownloading the gapps tomorrow, might have a corrupt downloaded file.
I Fashed latest slim as well. It is running really well so far. I had the same issue with Google+ until I uninstalled using TB then reininstall from play store.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Can confirm issue with Google+..
Thank you t_f for looking into mdnie. Also, flashing the unmodified lock screen handle available on Slim's website did not work, I still see the Slim logo. Aaah I wish I had time to figure out the android build environment.. I mean its probably just ant lol
Sent from my SGH-I757M using Tapatalk
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
manfromgta said:
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It is intentional. Disabling the hw overlays is a performance hit, and it seemed that slim didn't need that hack because the overlays are working correctly
I know, the latest ROMs are running smooth and battery is much better since I tweaked the kernel for both.
I'm also really enjoying my new computer so much that I'm playing with paranoid android too. Got it booting with a bunch of hacks and to my suprise, it's running quite well. I'll post that after I test it more and clean up the build process. Then we have choice of which ROM too use. That was the problem before, no choice strange though, there is no branch for kk in paranoid android's repo.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Just a word of caution to everyone using philz latest 6.07 cwm recovery. There is a know issue where the update-binary has now been updated as of kk and the recoveries built with kk like the new philz 6.07 are now giving assert errors (error 7).
There are two ways to fix this:
1) Revert to the older 6.01 version of philz.
2) extract the updater-script from the rom zip file, delete the assert lines and replace the old updater-script with the new one.
If you're new to all this, or consider yourself inexperienced, I recommend you go with option 1 and revert to the older philz as it's a less risky method of doing things
Sent from my SGH-I757M using XDA Premium 4 mobile app
Here's the link to the older philz 6.01. You can use either the 6.01.0 or 6.01.2.
http://d-h.st/users/philz_touch/?fld_id=29076#files
Sent from my SGH-I757M using XDA Premium 4 mobile app
Please check out this post if your not flowing the 10.2 thread and provide your opinion if you have one
http://forum.xda-developers.com/showthread.php?p=49171164
Sent from my SGH-I757M using XDA Premium 4 mobile app
ParanoidAndroid for SGH-I757M Released
Alright, for those of you who are waiting for my PA build, it's up. This is a JB4.3 build of ParanoidAndroid and I have added back the performance settings from CM to allow changing the governor and io scheduler as the defaults have sucky performance.
[ROM][PA-JB4.3][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M
Enjoy!!!
It's saying that slim isn't rooted?
{
"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"
}
Jump to...
ROM Index (#2) | Kernel Index (#3) | Changelog (#4)
Whaddup, XDA? ^_^
This began as a modest little post, aptly named Post#3333 in the Resurrection Remix thread to help keeping the thread clean. Many thanks to @varund7726 for his support and making it the official RR Bacon FAQ!
It gained more attention than I thought it would so I decided to make a more general version in a dedicated thread.
This is not my work but a collection of answers by amazing people that roam these digital lands. Of course, I do appreciate you clicking that Thank you button . I hope people looking for answers will find their way here. If someone has any input, feel free to drop it in the thread or send me a PM and I'll update the post if needed. It may be best to not ask new questions here, you'll find more satisfying answers in the appropriate threads of the custom ROM you're using or in the general Help thread.
Now, let's get this out of the way first:
Code:
What are you reading this for? There isn't a single Bacon owner with valid warranty anymore. Anyway, here's the original disclaimer:
You have the [U]right[/U] to unlock your device, not the [U]obligation[/U] to do so.
Anything you flash can and will be used against you in a court of technical dispute.
If you get your device bricked, you will [B]not[/B] be provided with a new one.
If your mother in law disappears as a result of something mentioned in this thread,
I will happily take your donations to thank me but I will not be held responsible!
Mind that this is – and probably will continue to be – a work in progress.
This is an attempt to collect general solutions, which will not always work in every case.
Please DO NOT QUOTE THIS ENTIRE POST! Thanks.
▂▃▅▇█▓▒░INDEX░▒▓█▇▅▃▂
New items are indicated with
; Updated items are indicated with
GENERAL
How can this FAQ help me? Why did you make this?
Why isn’t anyone helping me?
Creating a logcat
PREPARING
EXT4 vs. F2FS
What else do I need? (Prerequisites)
C6 or C7, which is the best firmware? (troubleshooting network issues)
What kernel should I use?
FLASHING
Installing TWRP
How to flash (with links!)
I'm seeing two red errors in TWRP while flashing
I'm getting an error while flashing Gapps
I dirty flashed and something doesn't work anymore
CRITICAL
My screen is going black, I can only see notifications
My device just exploded!
The other person (nearly) can't hear me during a call
I have another audio/microphone problem
Can't read or write to internal storage (/sdcard)
QUICK FIXES
The camera app can't connect to the camera
Google Assistant isn't working or "OK Google" detection fails
QS toggle 'drops' when trying to add it
OTHER
How do I apply themes and which ones can I use?
Fast/Quick Charge isn't working
MODS
ViPER4Android
Camera mods
1. GENERAL
1.a. How can this FAQ help me? Why did you make this?
My goal is to maintain a one-size-fits-all thread where people can find answers to the most common current problems for the OnePlus One a.k.a. Bacon. It also serves as a detailed guide through the flashing process. The reason I'm doing this is threefold: 1) Despite the fact that this is a 2014 device, the 1+1 community is still booming. Best proof of that is that our very own Bacon is by far the most popular device for LineageOS with currently over 80,000 installs! I'd love to honor that fact. 2) This is my first support thread, I hope to learn a great deal from it. 3) I honestly enjoy helping people =)
1.b. Why isn’t anyone helping me?
Keep in mind that XDA is not your personal tech support. The idea is that we help each other as a community, not to expect an immediate answer to your problem. If you do not add any useful technical information to your query, your post may not be considered, this is even more so the case in development threads.
There are three ways (that can be combined) to achieve a technically sound post:
Attach a logcat! See 1.c. on how to do this.
Provide screenshots, especially handy with aesthetic issues.
Provide the exact steps to reproduce the problem (be VERY specific).
Tip: use the time that you’re waiting for an answer to find it yourself. If you managed to resolve it yourself, follow-up on your own post and explain how you did it, it may be helpful to other users in the future.
1.c. Creating a logcat
This'll only take a minute and may provide invaluable information for any developer or someone trying to help. There are a number of ways to create them, this tutorial explains a remote technique. I do believe this is the easiest way:
Download CatLog from the Play Store
Make sure you have a dedicated 'menu' button (CatLog is old skool)
Run the app, give it root rights, [optional] pause the current flow with the pause button and then clear the window tapping the circle with the X in the middle top right (this will provide peace of mind, the constant stream can be a bit overwhelming)
Tap the menu button, press Record followed by OK. Any activity is now being recorded
Press your home key and launch the app that's giving you trouble, let the crash happen and repeat it a few times
Drag down notifications and tap the cat, it'll state "select to stop recording"
CatLog will now show you what it has recorded, use the search feature to check if no privacy sensitive information (your e-mail, a phone number etc.) has been collected, you can edit this out manually with a text editor if needed
You can simply tap the menu key again and select Send to share the log, this feature will also add device info (brand, model, Android version ...)
If you'd like to share it manually or want to make some edits first, you'll find the file in [internal storage]/catlog/saved_logs
2. PREPARING
2.a. EXT4 vs. F2FS
A lot can be said about filesystems but I won't go into any technical debates on here. The main difference boils down to this:
F2FS is arguably faster than EXT4; EXT4 is arguably more stable than F2FS.
In real use performance, not much difference will be noticed in terms of speed. Since the release of Oreo for Bacon, however, stability on F2FS has decreased drastically or it is unsupported entirely. If you have never changed this yourself, the system will most likely be formatted to EXT4. You can check with DiskInfo or in recovery. In case you want to run Nougat on F2FS or you want to return to EXT4 but forgot how, here's a refresher:
In recovery, go to Wipe > Advanced Wipe
Select a single partition
Tap “Repair or Change File System” (if you see “Invalid partition selection” appearing, it means the partition’s file system cannot be changed
On top you can see the current file system, tap “Change File System” followed by the one you want (stick to either EXT4 or F2FS)
Swipe to confirm
I found this XDA article (interview with Francisco Franco) quite interesting on this topic.
2.b. What else do I need? (Prerequisites)
A good working TWRP
The ROM zip of your choosing
Gapps (ARM/8.1/nano, there are plenty alternatives, check with your ROM maker which one is advised)
last CM13 snapshot (only if you didn't have CM13 before)
You should place all downloaded files in the root of your internal storage (/sdcard). It's stongly recommended to check md5 hashes! In case of Gapps, download the md5 checksum file and place it together with the zip.
2.c. C6 or C7, which is the best firmware? (troubleshooting network issues)
None. There are mixed results on both, depending on which network(s) you use. Which one works best for you? The only way to find out is by flashing one of the three versions below (that differs from your current version, check under About phone > Baseband version. The recommended one for most users is C6-00241 (the most likely one you currently have).
Here are three very common firmwares and a Frankenstein release:
Download DI.3.0.c6-00241
Download 4.0.1.c7-00013 (2016)
Download 4.0.1.c7-00011 (2016)
@MrSHME's Frankenstein Release
[instructions and credits]
There's a whole load of them available in this thread. I've done some elaborated testing there, read my findings here.
Important note when flashing firmware: backup your modem and EFS partitions first! It may happen that the system hangs in boot animation after a firmware flash (I experienced this a few times). Give it some time and it should automatically boot back to recovery. In recovery, reboot back to system (don't do any wiping or anything) and it should boot just fine. If the system keeps hanging for over 20 minutes, manually force a shutdown (long press power) and try booting regularly again. Still no luck? Boot to recovery and flash other firmware or restore your modem backup.
2.d. What kernel should I use?
You don't have to use any. Want to take the plunge anyway? Sure, check out post #3 for a list. You can make a backup of your kernel/blobs with Flashify
Read (much much) more about tweaking in this excellent guide by @Saber
3. FLASHING
Always make a nandroid backup before you flash anything!
3.a. Installing TWRP
Before flashing anything, make sure you are using a compatible TWRP! You'll find a download link to the one I'm using in this FAQ, I'll keep it updated. I know this is basic information but to avoid any mistakes, I'm providing all needed steps:
Download a TWRP .img file
Move it to the adb (official download) folder where adb and fastboot exe's are located
[this is no requirement but let's do this for the clarity of these steps] rename it to recovery.img
Reboot device into fastboot via advanced reboot menu, 'adb reboot bootloader' command or – if the device is off – press and hold "Power + Volume UP" until "Fastboot Mode" appears
Setup the correct drivers and connect the device to the PC/Mac
Open a command line (terminal on Mac I guess) in the adb folder
type "fastboot devices" to see if the system picks up the device
type "fastboot flash recovery recovery.img" to flash TWRP
Disconnect the device from the PC
Press and hold power until the device turns off
Hold "Power + Volume DOWN" to boot into the newly flashed TWRP recovery
3.b. How to flash
Always make a nandroid backup before you flash anything!
Clean Flash:
In TWRP, wipe by swiping factory settings. If you're experiencing issues, it's best to do a full wipe (Advanced > select System + Data + Cache + Dalvik-ART Cache)
[optional] Flash last CM13 snapshot and do another full wipe. This step is crucial when you've never been on CM13 before. This flash will fix/prevent a wide variety of issues! You only need to do this once.
Flash the ROM zip
[optional] Flash a custom kernel
Flash Gapps (ARM/nano, version should be the same as ROM), check Gapps compatibility in ROM thread.
[optional] If root is desired, flash Magisk (stable or beta)
[optional] Flash other mods
Wipe Cache/Dalvik-ART Cache and reboot
Dirty Flash (update):
Reboot to TWRP
Flash the ROM zip
Wipe Cache/Dalvik-ART Cache and reboot
Semi-Dirty Flash:
This is basically the clean flash procedure but you backup the /data partition before wiping and restore it afterwards (or don't wipe /data at all). I do not recommend this method.
Example (my flashing procedure for a specific Oreo ROM):
Download ROM and Open Gapps to root. Check ROM md5 hash with MiXplorer
Backup all user apps + a few system elements (messages, call logs etc.) with TitaniumBackup (+pro key)
Copy the TitaniumBackup folder to my PC
Reboot to latest TWRP, create Nandroid backup of System and Data (sometimes copy that one to PC as well)
Wipe /system + /data + /cache + /art-dalvik cache
Flash ROM + Gapps + OP5 camera mod + iYTBP + Magisk beta (all in one go), wipe caches after flashing and reboot
I let Google setup install all apps, then restore app data with TiBu, this feels more clean
Restore system elements with TiBu + apply AdAway lists + restore Android ID (for my banking app) and reboot
Enjoy awesomeness!
This seems like a lot of work but it doesn't take more than an hour. Since releases are currently pretty far apart, it's only a small effort for many days of smooth sailing. If release frequency would increase, I wouldn't make a Nandroid and wouldn't copy everything to PC every single time. If I don't have Wi-Fi for some reason, I restore all apps + data with TiBu instead of using Google setup.
3.c. I'm seeing two red errors in TWRP while flashing
They are LOS related and have no effect on the flash procedure, don't worry about it, you can safely ignore them.
3.d. I'm getting an error while flashing Gapps
Error 70: You're trying to flash a package that is too large such as Stock. Try a smaller package.
Error 64: Wrong architecture, you need an ARM package, not ARM64/x86/x86_64.
Error 20: Wrong version, you need 6.x for Marshmallow, 7.x for Nougat
3.d. I dirty flashed and something doesn't work anymore
Please do not inquire about issues after (semi-)dirty flashing. The first step for you to take is to perform a clean flash. If the issue is still present and it hasn't been posted before (PLEASE use search!), then post your inquiry in the ROM thread.
4. CRITICAL
4.a. My screen is going black, I can only see notifications
This behavior is caused when a profile has lock screen disabled. The only way to recover from this condition is to clean flash, or restore a backup that was made prior to setting up the profile. It may be possible to reboot successfully if one is in a location or situation that triggers a profile that doesn't have lock screen disabled, then change the problem profile settings (unconfirmed).
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
4.c. The other person (nearly) can't hear me during a call
Can't be heard
In /system/build.prop, change
ro.qc.sdk.audio.fluencetype=fluence
to
ro.qc.sdk.audio.fluencetype=none
Edit /system/etc/audio_platform_info.xml (in Oreo this file moved to /system/vendor/etc)
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />
to
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
Audio comes out low
remove
ro.qc.sdk.audio.fluencetype=fluence
change
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
(flashable version)
Reboot.
Still having problems? Test your sensors and mic more thoroughly with an app like this, there may be a hardware failure. Before opening her up, you can do a last software check by trying another ROM or by returning to 100% stock.
4.d. I have another audio/microphone problem
Please refer to the OnePlus One Audio Mods Collection, a genious collection of all sorts of fixes and workarounds to achieve fully featured audio on the OPO.
4.e. Can't read or write to internal storage (/sdcard)
Your /sdcard partition is most likely corrupt! Now what? When this happens to /system or /data we can simply perform a clean flash. Wiping our internal storage, however, means wiping a lot of precious data that is not included in a Nandroid backup so it's crucial to make regular backups manually. A lot of trouble can be avoided with cloud syncing (Dropbox, Google Photos, etc.). When read/write errors present themselves (camera can't save photos, not enough space errors while there's plenty, folders disappear, etc.) it's important to work fast before all your data becomes unavailable indefinitely. Here's how you can reset your internal storage in a non-destructive manner:
Copy the entire content of your internal storage (/sdcard) to an external location (PC or OTG drive). Make sure the real important things are immortalized (e.g. your cat photos/videos are synced with Google Photos and/or are trending on YouTube)!
Reboot to TWRP
You may want to create a nandroid backup at this point but do not forget to copy the backup to your PC or make the backup via OTG as we're about to wipe the internal storage (and with it, all internal backups)
Go to Wipe > Advanced and select only Internal storage, confirm to wipe (you may experience some discomfort at this point, this is normal)
Reboot to TWRP (from recovery to recovery, that's right)
Now copy all content back from the folder on your computer to the internal storage. You should be able to do this simply over USB while TWRP is active. If you don't, go to the main TWRP menu, tap 'Mount' followed by 'Enable MTP'
When the copy is complete, reboot to System and your trouble should be gone!
We're doing the wipe AND the restore inside recovery because if you would boot your device with an empty /sdcard partition, the Android system and all running apps would start freaking out and get going on all sorts of crazy, recreating their folders and files.
Tip: this is the perfect opportunity to sieve through those files! I recommend not just copying everything back but only the things you still need. Exclude folders of apps that aren't installed anymore and skip unused media files. This will decrease the chance of future corruption. Take some time to make your internal storage shipshape!
5. QUICK FIXES
5.a. The camera app can't connect to the camera
If you flashed something like OxygenOS Blobs, your camera will not work unless you set SELinux to Permissive. You should find this in your ROM settings (e.g. for RR this is under Settings > Configurations > Miscellaneous > Selinux mode > Permissive) or you can easily do this with SELinuxModeChanger.
Why this is a bad idea: SELinux or Security Enhanced Linux prevents malicious apps from gaining unlimited system level access by exploiting security holes. By setting it to Permissive, you’re disabling this extra layer of security. Infections due to this are rare but do happen, you’ve been informed.
5.b. Google Assistant isn't working or "OK Google" detection fails (this may be obsolete by now, please notify me if it is)
See 4.c., “Audio comes out low”.
5.c. QS toggle 'drops' when trying to add it
This may happen when attempting to add one of the lower QS toggles. There are two ways to work around this bug:
By lowering the display size: go to Settings > Accessibility > Display size (or under custom ROM configurations) and change it to Smaller or Smallest
By messing around: move icons from the top to the QS panel until you're able to slide the QS toggle you need without 'dropping' it
This video shows it works fine:
6. OTHER
6.a. How do I apply themes and which ones can I use?
OMS compatible ROMs only! To start, install Substratum from the Play Store, open it and grant it root rights (both substratum and masquerade). Then search the Play Store for substratum themes that are compatible with your Android version. Some will cost you something but most are really worth it and there are some great free ones as well. After installing a theme, apply it in Substratum. Don't forget to read the theme creator's instructions, some combinations can cause trouble!
6.b. Fast/Quick Charge isn't working
That's because the OnePlus One doesn't support it. You can, however, tweak charging rates with kernel tweaks (which is still limited, don't expect dash charge speeds). Equip yourself with proper hardware. A ‘smart’ charging station and quality cables can go a long way. Mind that faster charging is not better charging per se. You may shorten the lifespan of your battery when pushing it to the limits. Charging with the official charger/cable (which should take about 2 hours from 0 to 100%) is still the best way to treat your battery. Also note that if you got your device back in 2014, there's a good chance your battery doesn't have its full capacity anymore, longer charge rates and shorter lifespans can be expected. That being said, the OPO was equipped with a kickass quality battery, even after abusing it for all these years, many users have reported it still works great!
7. MODS
7.a. ViPER4Android
Since Magisk is more widely adopted, installing V4A has become very easy.
In Magisk Manager, tap the three lines top left
Tap Downloads
Scroll down to ViPER4Android FX and tap the download icon
Tap Install followed by Reboot
Once booted, go into Magisk > Downloads again
ViPER will now be on top, tap it
You'll find a link to the latest APK, download and install it
That's it. Open it and change all the settings you want, then reboot once more to make sure it all runs fine.
7.b. Camera mods
The OnePlus 5 camera software has been ported (download here) to Bacon and it works great, this is my current favourite.
Great camera mod: CameraNextModV2. It's just a simple flash away.
Not much of a mod but a Camera app optimized for our OPO: Bacon Camera!.
And good to know: Google Camera 4.1.006.135988111 is the last compatible version for Bacon.
Thank you for contributing, @venky716 @bdwilk @Baldesarra @Mr.Ak @Silverview @abhi08638 @tazzkiller @Genericxx @Turpb (PM me if your name should be here!)
Bacon ROM INDEX
For your convenience, I've listed *most* (maybe all of them, who knows) Nougat+ Bacon ROMs below. Please feel free to post in the thread if you found one not mentioned below. Cheers!
Original Android Development
PIE!!!!!
[ROM][9.0.0_r3] POSP v2.0 - BETA [OFFICIAL]
Oreo
[ROM][8.1.0_r29] AOSP Oreo for OnePlus One [Discontinued][23/05/2018]
[ROM][OPO][8.1.0_r43] Candy8.1 [OFFICIAL][SUBS]
[ROM] [UNOFFICIAL][8.1.0] Dot OS v2.x [BACON [30/03/2018][DISCONTINUED]
[ROM][8.1.0_r33] POSP v1.0 [OFFICIAL]
Nougat (not updating this list anymore)
[OFFICIAL][7.1] LineageOS 14.1 - OnePlus One [bacon]
[ROM][7.1.1_r13] Android Open Source Project | NOF26W [DATE]
[ROM][OPO][7.1.1_r26] Slim7 - Bacon [OMS][NOF27C][Nougat]
[ROM][OPO][7.1.1_r26] Candy7 - Bacon - OOS+Sultan camera [NOF27C][OMS][Nougat]
Android Development
PIE!!!!!
[ROM][9.0.0_R8][PIE] PixysOS [BACON][OFFICIAL]
[OFFICIAL] [AOSP] [WEEKLY] Arrow OS [Pie] [9.0.0_r8] | Bacon [2018-09-22]
[ROM][LineageOS][Android 9.0.0r6]] TugaPower™ 0.6 Beta
[ROM][9.0.0][UNOFFICIAL][Alpha] LineageOS 16.0 for Oneplus One [bacon]
Oreo
[ROM][8.1.0_r4][OMS] LineageOS-15.1 [bacon][BETA][UNOFFICIAL]
[ROM][BACON]RESURRECTION REMIX 6.0[OFFICIAL]
[ROM][LineageOS][Android 8.1.0r36][OMS] TugaPower™ 23.0
[ROM][8.1.0_r36][OFFICIAL] AospExtended ROM V5.7 [DUI]
[ROM][BACON][8.1][OMS] hyperUnicorns - Optimized Dirty Unicorns (discontinued?)
[ROM][8.0.0_r17] halogenOS 8.0 OREO [Testing] [UNOFFICIAL] (unavailable for now)
Dirty Unicorns 12.2 (20180513) (download only). No XDA support! Contact @deadlyindian for a Telegram invitation.
Crdroid ROM for OnePlus ONE crdroid-4.6 (TOP PICK!)
[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
[ROM][8.1.0_r42] AOSiP 8.1 [OPO][OFFICIAL]
Validus (shared by @pratikone1 here, have yet to check this) (newer version, still have to check it )
[ROM][8.1.0][OFFICIAL] Cosmic-OS v3.1 - Universe[BACON]
[ROM][8.1.0][UNOFFICIAL] BootleggersROM 3.0-STABLE [BACON]
Nougat (not updating this list anymore)
LineageOS[OMS][DATE][Make CM great again!][Optimized]
[ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0]
[7.1.1] [ROM] Android Ice Cold Project [Official Nightlies] [OMS]
[ROM][7.1.1][OFFICIAL]Android Open Kang Project[AOKP][NIGHTLIES][OMS7]
[DATE][OFFICIAL] 7.1.1 || Ground Zero ROMs || Validus - Tesla - Tipsy
[ROM][OFFICIAL][7.1.1_r6]CypherOS 3.5.1 Jamocha[Bacon]
[OFFICIAL][7.1.1_r9][BACON] XenonHD 7.1[OPTIMIZED][OMS]
[ROM] [7.1.1_r9] [OFFICIAL] [OTA] XOSP - Xperia Open Source Project 7.2
[ROM][OFFICIAL][7.1.1_r4] Zephyr-OS V6.2 [AOSP/Substratum/DUI]
[ROM][7.1][NOUGAT][NIGHTLY] Official Mokee Open Source Project
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI]
[ROM][Bacon][7.1][OFFICIAL] Cosmic OS for OnePlus One
[DATE] Unofficial LineageOS 14.1 [OMS7][OPTIMIZED][PERFORMANCE]
[ROM] [bacon] [7.1.1] [LOS-based] **crDroid**v2.0
[ROM][7.1.1_r13] AOSPlusone 7.1 [SultanXDA's Camera HAL][OMS] | 22
Nitrogen OS ► [7.1.1 ► NMF26O] [OMS7] [DATE]
[ROM] [UNOFFICIAL] FLIVERCOD'S CUSTOM AICP-12.1 Android 7.1 [NOUGAT - Bacon] [Linaro]
[ROM/KERNEL][UberTC4.9/Linaro4.9] NucleaRom[Android 7.1.1_r6
[ROM][LineageOS-14.1][7.1.1_r9][OMS7] LegendROM
[ROM][Android 7.1.1]Unofficial Okeys Builds[LineageOS 14.1][OMS7]
[NIGHTLIES] idprophecy's unofficial optimized LineageOS 14.1 builds
[ROM][LineageOS][Android 7.1.1][OMS7] TugaPower 15.1
[ROM] [7.1.1] DarkobasROM [OMNI-ROM]
[ROM][7.1.2][UNOFFICIAL] AIM ROM v2.5 [OMS/DUI][Bacon]
[OFFICIAL][NOUGAT]dotOS-v1.0[Bacon] (this is probably the best one...)
CAF
[ROM][CAF][DATE] halogenOS 7.0 for OnePlus One
Kernel Index
Thunder (Oreo), click here!
FrancoKernel (N + Oreo), click here!
ab123321 Kernel, click here!
Boeffla official, click here!
Boeffla unofficial, click here!
Lightning, click here!
[Changelog]
2018-08-23
Howdy! I've been away (or at least very inactive) for a few weeks due to family vacation and other stuff – including two quite tragic events. That's life I guess
Anyway, interesting development seems to be never ending for this amazing device. The immortality of Bacon has yet again been confirmed with the release of PIE! This was predicted by my teenage antiheroes "Weebl and Bob" back in 2002; they are true visionaries :')
That's not one (KitKat), not two (Lollipop), not three (Marshmallow), not four (Nougat), not five (Oreo) but SIX (PIE!) major Android iterations that have seen light on this chunck of awesomeness. At this rate we might even see Android Queijadinha on the OPO! But let's not get ahead of ourselves. Let's celebrate and enjoy Pie's release first. Time to take a P (Captain Underpants, anyone?). Tra-la-laaa!
Created "PIE!!!!!" section
Added POSP to both Oreo and Pie sections
Added PixysOS
Updated Oreo titles.
2018-05-25
Added Cosmic-OS
Updated all ROM Index Oreo titles
The legendary AOSP by the equally legendary @Agent_fabulous is being discontinued more to come, though?...
Disclaimer: while you are reading this thread, I am shamelessly collecting your personal data. Including but not limited to your shoe size, favourite colour, romantic preferences, how many times you've shouted my username, your failure to use search properly (yes, again!), social security number, blood type, flash habits, flash hobbits (for "precious" ROMs), cookies (both edible and non-edible), the way you're hovering this text with a cursor, etc. You have no right to view, alter or delete this data in any way, I will gain massive profits from it and there's nothing you can do about it. (...) Of course I'm kidding! #GDPRday -_-
2018-04-01
Added CrDroid ¯\_(ツ)_/¯
Added [8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
Added [ROM] [UNOFFICIAL][8.1.0] Dot OS v2.1 [OMS] [BACON [30/03/2018]
Updated all ROM Index Oreo titles
Free Bacon pr0n: click here (warning: explicit content!)
Happy Easter everyone! ?
2018-03-29
Added RR Oreo added to the ROM Index! LoL, I was so occupied with that ROM today I totally forgot to add it to this list
2018-03-18
Added DU v12.0 Oreo unofficial to the ROM Index because it's just so awesome (and because dev allowed me, lol). There's no XDA thread so don't expect any support. So just.. eh.. #staydirty I guess ^_^
Check out my new animated sig! Created it myself in Photoshop. Let me tell ya, it was a long night
2018-03-15
Added thread jumper on top of OP for people who really hate scrolling :silly:
Oh and a late happy bday, little thread of mine!
older
2018-02-28
Updated Oreo ROM list @ post 2
Moved Franco Kernel up in kernel list (now Oreo compatible) @ post 3
Added CM13 snapshot step in flashing procedure (3.b.)
Updated prerequisites (2.b.) to complement flashing procedure
Added more elaborate info and resources on firmware flashing (2.c.)
Updated all TWRP links to direct download for 3.1.1-5-TugaPower (last stable release of my preferred recovery)
Fixed 'how to check MD5 hash link (was censored?)
Updated file info in 4.c. as audio_platform_info.xml moved to /system/vendor/etc in Oreo
Updated To Do list below
Getting pretty 'ultimate' looking back on first release below, nearly one year since I launched this
2017-12-4
Added 4.e. Can't read or write to internal storage (/sdcard)
Removed changelog bits in OP
Added changelog reference and new/updated legend in index
2017-11-21
Added '1.c. Creating a logcat'
2017-11-15
Reworked the disclaimer
Changed 1.a. stat: from 50,000 to 80,000 installs!
Added Frankenstein Release to firmware (using it myself, quite happy with it)
Replaced "can't find the current release of a ROM" with "EXT4 vs. F2FS"
Updated TWRP links to thread instead of direct download
Made a reference to post #3 instead of listing kernels again
Added link for SDK Platform Tools
Removed optional LOS flash suggestion (obsolete)
Reworked flashing procedure (kernel doesn't need in-between reboot anymore)
Added Magisk reference as root solution
2017-11-12
Updated ROM and Kernel section for Oreo (and Mr.Ak, naturally)
2017-06-27
Added kernel index (post3)
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
2017-03-12
Post #2 is now a Nougat ROM index!
2017-03-12
Added '5.c. QS toggle 'drops' when trying to add it' + video
2017-03-05
First release, not very "ultimate" YET
[To Do]
Elaborate more on kernels (kinda given up on this as Oreo doesn't offer the same freedom we once had in Nougat)
Meh, you tell me!
@Timmmmaaahh
Thanks mate for your helping nature...
I don't know anybody feel or not but you're one of the most helping people of XDA at least for me. I have GOOD memory of your help when my BACON has died and then you helped me a lot, Many people helped me but your help I can't forget...
Thanks mate keep it up..[emoji120]
Unbeatable!
This is going to be fun.
Thanks! @Timmmmaaahh
Edit:
Add Q. What is the codename of Oneplus One?
A. Bacon.
Q. How is this device in over all usage and stuff?
A. Two Word- Bacon FTW!
For those who want TL;DR
There you go
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
nachomagic said:
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
Angel? Lol.
Added 5.c. QS toggle 'drops' when trying to add it + video
[Post#3333] for RR is now the official FAQ.
Nougat ROM INDEX now live!
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
cfedata said:
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
Click to expand...
Click to collapse
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
How much fat there is in 1kg of bacon?
Timmmmaaahh said:
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
Click to expand...
Click to collapse
Don't forget to add roms compiled by me,though.Kthnxbye.
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
Fatsodonkey said:
How much fat there is in 1kg of bacon?
Click to expand...
Click to collapse
The same amount of fat as in 1kg of v0lte.
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
This made me laugh! :good:
2017-11-12
Updated ROM and Kernel section for Oreo (and @Mr.Ak, naturally)
Mr.Ak said:
Don't forget to add roms compiled by me,though.Kthnxbye.
Click to expand...
Click to collapse
romS? as in plural?
Did I miss any Oreo releases? I'm sure I did...
I'll refresh the OP later, more procrastination first!
Timmmmaaahh said:
romS? as in plural?
I'll refresh the OP later, more procrastination first!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/rom-aim-rom-v2-5-t3693630
I can see you're not as active as before sur.You need to get some v0lte in your life.
{
"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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), 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 Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended LineageOS recovery in the official installation instructions link below.
You can use TWRP for installation, however it is no longer officially supported since we do not have full control of its update cycle and potential issues.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-12.1
NikGapps-SetupWizard
NikGapps-AndroidAuto
Or
MindTheGapps-12.1 (Google Drive mirror)
Root Access:
Magisk v25.2 (more stable experience)
Magisk v26.1 (more updated build)
Recommended Useful Add-on:
p2oggle-1.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to @mikeioannina for his hard work regarding kuntao and to all other Lineage OS developers
Special thanks to @Astridxx for the device tree sources and for helping me out and to @en666 for early testing the initial build
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk ,@Sohit5s, @mikeioannina
ROM OS Version: 12.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-02-22
Last Updated 2023-06-11
Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you must perform a clean flash. Clean flash instructions:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
Update Instructions
NOTE: Dirty flash from any of the aforementioned builds is not supported, device trees were changed. You have been warned!
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues- Storage encryption is partially broken (if your /data partition is unencrypted, trying to encrypt it using ROM menu will result in a dead OS; if already encrypted, storage encryption may or may not work. IFAIK, it's a kernel side issue)
- Device may not go to deep sleep
- Storage forceencrypt flag is disabled (to encrypt /data partition follow the instructions below)
- TWRP backups are broken (read notes below)
- You tell
Google Play Store Update Bug
If Google Play Store app keeps failing to find updates for apps with message "Something went wrong. Try again.", just clear its data and then it should work again
SafetyNet Check Fails
If your device is rooted, please, follow the instructions contained here
Magisk is Gone After First Boot
Please, just reflash Magisk again (i.e. Reboot to recovery > Flash ZIP > Reboot back to system)
How to encrypt data partition
0- Backup your files (this process will erase everything)
1- Boot to TWRP recovery
1.1- Wipe > Format data > Reboot to system
2- Settings menu > Security > Encryption & credentials > Encrypt phone
3- Reboot to system again
Error restoring TWRP system backups
It looks like TWRP backups are broken for now, so please, if this is a must have for you, you can try to install OrangeFox recovey and follow these instructions (thanks @Zdeslav for that)
ROM Change logs
Code:
02/22/2023
- Initial release
02/27/2023
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
03/29/2023
- Fetch latest Device Tree sources
-- vendorsetup.sh: Add Trebuchet patch
-- AOSP WFD doesn't support protected Wi-Fi Display buffers
-- Overlays:
--- Enable voWIFI support
--- Disable IMS features for Turkiye networks
-- Don't warn user about FC in Vanced microG
-- DT rootdir:
--- Add cpuset for the camera daemon
--- Remove permission restrictions to the socket file
--- Restore iio sensor device6 on boot
-- Bump graphene camera version to 60
-- Don't force enable ims features
-- sepolicy: Address sensor hal denials
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/09/2023
- Fetch latest Device Tree sources
-- Add navbar enable/disable support
-- fs: Revert sdfat update for OTG
-- block: Add zen io scheduler
-- dts: Decrease BCL low battery threshold to 5%
-- DeskClock:
--- Wallpaper based text coloring for digital
--- Adapt digital clocks to S style
--- Remove night mode
-- Trebuchet:
--- Kill haptics in recents
--- Make overview scrim transparent again
-- Nfc: Fix Mifare Classic reading
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
04/19/2023
- Fetch latest Device Tree sources:
-- sepolicy: Silence tracingproxy_service neverallow denial
-- sepolicy: Allow system_app to access storaged via IPC
- Sync latest LOS source
- Merge April security patch
05/09/2023
- Fetch latest Device Tree sources:
-- Bump graphene camera version to 62
-- devicesettings: Protect broadcast to fingerprint gestures
-- rootdir: Remove permission restrictions to the socket file
- Sync latest LOS source
- Merge May security patch
06/11/2023
- Fetch latest Device Tree sources:
-- parts: Update few parts icon
-- vendorsetup.sh: Use depth=1
-- Remove pixel_2016_exclusive
-- Bump graphene camera version to 63
- Sync latest LOS sources:
-- Additional zstd cmdline tools
-- zstd compression support for rsync
-- 2023-06 ASB patching: packages/apps/Traceur
- Merge June security patch
ROM Screenshots
Attached below. Others are available here.
February 27th 2023 Release
Changelog:
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
Download URLs: GDrive | SF
Dirty flash still not supported (tree changed), please make a clean flash
Thank you so much for keepng Lineage alive, its very much appreciated.
@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!
p2a42, twrp 3.7, rooted, unencrypted
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
bidulez said:
automatic update is possible after install ?
Click to expand...
Click to collapse
No
bidulez said:
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
Click to expand...
Click to collapse
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Tried quickly this ROM yesterday. In general all working, but didn't test much.
Few feedbacks:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Impressed that you could integrate also some lenovo features, even if of course not all of them
If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.
Cheers!
leo_97 said:
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Click to expand...
Click to collapse
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?
Zdeslav said:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Click to expand...
Click to collapse
So,
Resolved issue of bootloops:
after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.
But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier .
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Zdeslav said:
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Click to expand...
Click to collapse
Hello,
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
MKbis said:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Click to expand...
Click to collapse
I'm not sure if it's possible to "fix" the brightness slider.
If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.
Regards
Leo_97
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Click to expand...
Click to collapse
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.
But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad .
Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
Click to expand...
Click to collapse
Yes after a while it is returned back without reboot. weird.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
Click to expand...
Click to collapse
Didn't know about P2oggle v1.2 app, thx
March 29th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.
Enjoy!
Big Thank you for this release. Will try it. - test
Great job, dude.
Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.
Somehow this problems seems to be gone in your build and that is awesome.
I've been using the build for about 2 weeks now and so far everything seems to be working fine.
April 09th 2023 Release
Change log:
- Fetch latest Device Tree sources (lots of changes)
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Dirty flash is unsupported for this build, please make a clean flash
Enjoy!