[ROM | 4.4.4 | FALCON | CM11 | UNOFFICIAL] CyanogenMod 11 with OpenPDroid - Moto G Android Development

Code:
#include
/*
*
* [COLOR="Red"]Your warranty is now void[/COLOR]
*
* 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.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm
* app failed.
*/
{
"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"
}
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for a selection of Android devices. Based on the Android Open Source Project, CyanogenMod is designed to increase customizability, performance and reliability compared to the stock Android-based firmware supplied with devices by vendors and carriers such as Google, T-Mobile, HTC, etc. CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
CyanogenMod 11 (CM11) is the customized version of Android Kitkat 4.4.x. While this build is heavily optimized, it is also capable of pushing your phone much harder. CyanogenMod and it's team hold no responsibility for any damage caused to your phone, any loss of earnings as a result of damage to your phone or anything else that is connected to the development of this rom.
What is OpenPDroid?
OpenPDroid is a set of modifications to the Android framework and libraries which grants you some control of the level of access to your data by applications and services installed on your device. You are able to influence which applications are able to retrieve data about your device, your account, your messages, and more. Specifically, it is a Privacy service provider (using the PDroid 1.51 interface) forked from CollegeDev's PDroid 2.0, which is itself an extension of Syvat's PDroid. PDroid's tagline was The Better Privacy Protection. In many ways, PDroid/OpenPDroid remain the better privacy protection even today when Android 4.4.x and CM11 offer alternatives such as AppOps and CM Privacy Guard.
When configured using the PDroid Manager app, OpenPDroid intervenes in API interactions by apps (e.g. when an app attempts to retrieve your location, phone number, or contacts) and provides either real data, empty data, fake data, or random data, depending on the user setting. Unlike apps which actually remove permissions, OpenPDroid does not actually modify the permissions that an app has and - as a result - is threfore much less likely to cause the app to crash as a result of data access being denied.
Unofficial CM11 with OpenPDroid​Quick reminder:
Create a Nandroid backup before trying out any new rom
Post a short message about your experience with the rom
This is a build of CyanogenMod 11 patched with OpenPDroid for the single- and dual-sim versions of the original, 2013 1st gen Moto G (falcon). Please do not flash this on any generation of the Moto E, Moto X or Moto G 4G/LTE as they are NOT compatible with this rom. It is also NOT compatible with the 2014 2nd gen Moto G (and later generations of the Moto G) either.
This rom is based on what an official cm-11-20151124 nightly would have been as official CM11 nightlies no longer exist. This rom has been stable enough to be considered a daily driver but, your experience may differ. Now, as far as differences to the hypothetical CM11 20151124 nightly rom, this rom has only been patched with OpenPDroid. Since there are no longer any official CM11 releases for the Moto G, feel free to treat this rom as a recent CM11 build even if you have no need for OpenPDroid. It will work just as well.
To activate and use the privacy controls the OpenPDroid framework provides, you will need to install the PDroid Manager app too. You can read more about the app here.
The AFWall+ firewall is a good counterpart to OpenPDroid. Support the developer by buying the donate version if you find that you like and keep on using the AFWall+ firewall.
NOTE: OpenPDroid for CM11's maintainer @Lanchon has released generic, device-independent OpenPDroid for CM11 distributed as overlays to the official CyanogenMod releases - currently M9, M10 and M11 are supported at the time of this release. To use you first flash the official "M" snapshot corresponding to the OpenPDroid overlay you want to flash, then flash the overlay (and optionally, GApps for new installs).
Thanks to @Lanchon, OpenPDroid (and hence this rom) is now compatible with both the Davlik and ART runtimes.
DOWNLOADS:
File: cm-11-20151124-UNOFFICIAL-OpenPDroid-falcon.zip
CRC-32: d6ba49da
MD4: 2ac724f330ce2df24982c9e90e433fc2
MD5: 4d78716b612229b3f1443cdd5362b2b9
SHA-1: 0287476d7eb8116165a5fae9894c3e879ca5ebef
Issues:
REMINDER: Any and all issues reported for (an hypothetical) CM11 nightly build from 2015-11-24 for Moto G (falcon) will also apply to this rom
OLDER RELEASES:
File: cm-11-20141016-UNOFFICIAL-OpenPDroid-falcon.zip
CRC-32: 26e59df7
MD4: b2f0adbe8232fe089dfc87cfb16fe5b1
MD5: 86a91b98289e0e8c28f41c80d0ddc576
SHA-1: 92d6f8d7f61db8bfa5038aa8b456ac53de03f330
Issues:
A user reported an issue with Profiles and vibrate setting
WARNING: For roms below this message, OpenPDroid is not compatible with the new ART runtime. Please disable ART before flashing any of these roms. If ART is not disabled, your device will fail to boot and you will need to flash an official build of CM11 temporarily to be able to fix this issue (this will likely result in privacy leaks while the official CM11 is active). Alternatively, if you have ADB access in android (USB debugging enabled) or recovery, you can disable ART by using setprop or editing a file (please search the forums for instructions).
File: cm11-20140721-OPENPDROID-falcon.zip
CRC-32: 6e683aff
MD4: 47696d7245cb60701973aeaf5055ea5e
MD5: d0902ac383f946192fe895f4bb7b79c8
SHA-1: 56b4e1b19cac137048f9f1244d415da152b8e747
XDA:DevDB Information
UNOFFICIAL CM11 + OpenPDroid, ROM for the Moto G
Contributors
MiyagiSan, Lanchon, mateorod, FFU5y, CollegeDev, Syvat, dhacker29, Ethan Chen, CyanogenMod, AOSP, Google
Source Code: https://github.com/Lanchon/OpenPDroid-patches
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Snapshot
Created 2015-11-25
Last Updated 2015-11-30

Reserved

Reserved
Reserved

Ohhh first to post!
Sent from my Moto G using Tapatalk

Sweet thanks man

Doesn't work, bootloop..

boros2222 said:
Doesn't work, bootloop..
Click to expand...
Click to collapse
Were you running a version of CM11 previously?
Did you have the ART runtime set as your default? (that WILL result in problems as stated in the OP)

MiyagiSan said:
Were you running a version of CM11 previously?
Did you have the ART runtime set as your default? (that WILL result in problems as stated in the OP)
Click to expand...
Click to collapse
My runtime is Dalvik.
I was on Gummy rom. I wiped everything and I tried clean flash.

boros2222 said:
My runtime is Dalvik.
I was on Gummy rom. I wiped everything and I tried clean flash.
Click to expand...
Click to collapse
Not sure what the problem is. Had a quick look at original thread by @dhacker29 and did not get any sense that 20140721 is prone to bootloops. He did say this in response to a report of bootloops on a much earlier version. Perhaps it helps you?
How is Gummy rom? Is @dhacker29 helping to make it super stable over there?

MiyagiSan said:
Not sure what the problem is. Had a quick look at original thread by @dhacker29 and did not get any sense that 20140721 is prone to bootloops. He did say this in response to a report of bootloops on a much earlier version. Perhaps it helps you?
How is Gummy rom? Is @dhacker29 helping to make it super stable over there?
Click to expand...
Click to collapse
Actually, I restored 4.4.4 stock firmware to update my bootloader.
I flashed custom recovery, custom rom again.
After I checked everything is ok, I installed your rom.
Now it booted up, but com.android.phone force closes constantly.

boros2222 said:
Actually, I restored 4.4.4 stock firmware to update my bootloader.
I flashed custom recovery, custom rom again.
After I checked everything is ok, I installed your rom.
Now it booted up, but com.android.phone force closes constantly.
Click to expand...
Click to collapse
Did you format everything before wipe like @dhacker29 recommended in that post I linked to
NOTE: he warns that EVERYTHING including the internal sdcard will be wiped so, BACKUP EVERYTHING
This rom only makes one change to the official, it patches it with OpenPDroid. I've had no issues with it (for my use case). Here are a few general troubleshooting steps you could try:
- doublecheck ALL the file checksums to make sure there was no error in downloading the file
- use the latest stable version of whatever recovery you are using (Philz/CWM had issues with restored nandroid and keeping time in earlier versions for instance)
- follow the steps given by @dhacker29 for total wipe before flashing rom (remember BACKUP first!)
- test rom before restoring anything to ensure problem isn't with restored bits (even before flashing Gapps)
- try to find and test the official 20140721 nightly that this is based on (any non-OpenPDroid isues in this rom likely originates from that rom)

MiyagiSan said:
Did you format everything before wipe like @dhacker29 recommended in that post I linked to
NOTE: he warns that EVERYTHING including the internal sdcard will be wiped so, BACKUP EVERYTHING
This rom only makes one change to the official, it patches it with OpenPDroid. I've had no issues with it (for my use case). Here are a few general troubleshooting steps you could try:
- doublecheck ALL the file checksums to make sure there was no error in downloading the file
- use the latest stable version of whatever recovery you are using (Philz/CWM had issues with restored nandroid and keeping time in earlier versions for instance)
- follow the steps given by @dhacker29 for total wipe before flashing rom (remember BACKUP first!)
- test rom before restoring anything to ensure problem isn't with restored bits (even before flashing Gapps)
- try to find and test the official 20140721 nightly that this is based on (any non-OpenPDroid isues in this rom likely originates from that rom)
Click to expand...
Click to collapse
My data was wiped by restoring stock firmware, so I don't think, I should do it again with dhacker's method.
I'm using latest Philz Touch.
I'm actually trying new roms that have come for Moto G lately (Broken, Dirty Unicorn).
Probably, I'm gonna restore stock firmware again, because GPS stopped working..

UPDATE: OpenPDroid is now compatible with ART!
get the new generic overlays here. enjoy!

UPDATE: CM11 M11 OpenPDroid overlays for all devices released!
(no further notifications of updates will be posted to this thread; please subscribe to the device-independent thread.)
enjoy!

UPDATE:
New build based on CM11 20151124 nightly with OpenPDroid posted. Updated first post.

This ROM is stable ?

:good:
lcosta2 said:
This ROM is stable ?
Click to expand...
Click to collapse
It is equivalent to a nightly build. That has consequences for any expectations of stability of course but, it is used as a daily driver with no issues to report.....yet.
It is only day 2 since this rom was built....so, YES, it has been stable so far. :victory:
And it has all the StageFright fixes released so far included... :good:

MiyagiSan said:
UPDATE:
New build based on CM11 20151124 nightly with OpenPDroid posted. Updated first post.
Click to expand...
Click to collapse
using this rom. excellent work buddy. pretty stable. :good:

nnayak said:
using this rom. excellent work buddy. pretty stable. :good:
Click to expand...
Click to collapse
What about battery??
Sent from my XT1032 using Tapatalk

DeryckNS said:
What about battery??
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Battery is fine for me. You?

Related

[GearOMNI][i9500][4.4.4] OmniROM for Samsung Galaxy S4 [20140829]

Use > this other thread < to ask questions or to discuss about something​
{
"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"
}
OmniROM 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
/*
* 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.
*/
OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. OmniROM does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for OmniROM is available in the OmniROM Github repo. And if you would like to contribute to OmniROM, please visit out Gerrit Code Review.
Downloads
20140829 Build: https://www.androidfilehost.com/?fid=23622183712463976
Previous Releases:
20140828 Build: https://www.androidfilehost.com/?fid=23622183712463710 Ignore this release
20140804 Build: http://www.androidfilehost.com/?fid=23578570567723074
20140802 Build: http://www.androidfilehost.com/?fid=23578570567722138
Google Apps (Dalvik & ART): http://forum.xda-developers.com/showthread.php?t=2397942
Installation
3-button-combo = "Volume Up/+" + "Home/Center" + "Power/Lock"
- First time flashing OmniROM to your Galaxy S4 (or coming from TouchWiz/Stock Based ROMs)?
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 + format /system partition)
Install the ROM from internal/external sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from CM10.2/CM11?
Reboot into Recovery using 3-button-combo
Do a Nandroid Backup!
Install latest ClockworkMod Recovery. (if needed)
Reboot into new Recovery using 3-button-combo (if needed)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from internal/external sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from another build of OmniROM?
Reboot into Recovery using 3-button-combo
Do a Nandroid Backup!
Install latest ClockworkMod Recovery. (if needed)
Reboot into new Recovery using 3-button-combo (if needed)
Install the ROM from internal/external sdcard using ClockworkMod Recovery
WIPE Dalvik/ART Cache (wipe cache partition + wipe dalvik cache)
Done! You can now reboot the phone to enjoy the rom
Known Issues
Please do not report bugs if it is already listen in the list of known issues
Random Call Audio Quality
Touchkeys backlight isn't working yet (Feedbacks are welcome)
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):
OmniROM version:
OmniROM 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:
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:
Changelog
20140829:
Updated OmniROM sources
Cleaner
Using proper Bluetooth permissions
Finally fixed IR (Infrared used for Remote Control, tested with Smart Remote)
Using MPEG2 and VP8 (WEBm) hardware codecs
Reduced screen brightness while booting and while charging to save energy and reduce heat
No more video lags related to sound card crashes (Feedbacks are welcome)
Should solve all ext.sdcard issues (thx @Arch9 for reporting)
Fixed Offline Charging for ALL devices
Noise Suppression should work perfect now
Better audio values (almost 90% Stock-Like)
New Offline Charging images
All WiFi issues with lost networks and anything else are now fixed
Increased UI Resposiveness
Improved GPS Performance
Faster Dalvik creation using multi-threading (this means faster boot after clean install or dalvik wipe)
Fixed no incall-audio on boot (thx @D_black84 for report)
Fix some overlay problems, now all is set correctly (see new working dock settings)
New charging images
Fix Chromecast support
Updated kernel to NG3 sources + many optimizations (whole rework)
Previous Releases:
20140828:
Ignore this release
20140804:
Updated OmniROM sources
Fix some wrong setting (restoring keys settings)
20140802:
First Release
The OmniROM team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[GearOMNI][i9500][4.4.4] OmniROM for Samsung Galaxy S4, ROM for the Samsung Galaxy S 4
Contributors
Alberto96
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 20140829
Stable Release Date: 2014-08-29
Created 2014-08-02
Last Updated 2014-08-29
Reserved
Reserved
I haven't tested a lot the ROM but all seems to be working as should I need to make a big backup to switch definitely to OmniROM from CM.
Wow ! Good work ! Is camera working better than cm based rom ?
Wwwhhaaatt?? This is awesome!
Gonna try soon!
Excellent! downloading right now!
Does Bluetooth headset profile work? what about the camera?
Thanks!
Thanks @Alberto96 for another awesome ROM. Are you going to port theme manager over to omni rom?
Air-真心为你 said:
Wow ! Good work ! Is camera working better than cm based rom ?
Click to expand...
Click to collapse
It is working as on CM.
pedodroid said:
Thanks @Alberto96 for another awesome ROM. Are you going to port theme manager over to omni rom?
Click to expand...
Click to collapse
Nope.
There is no doubt as an individual u r the only Dev who has contributed so much for I9500 and brought it to the current level where we have official support from almost all the ROM's.
Only a few months back we had no options no Rom to try, but as an individual you contributed tremendously and helped us get official CM support. Then what in just a few days we had every other Rom team giving support to our device.
If u remember u were first trying to bring Omni but eventually landed giving us unofficial CM build.
It was a big surprise that we did not have Omni for so many days even after development for I9500 came to this high level.
Many Dev tried to build Omni but in vain, a Man who had real blood in his veins was required to get it working and who else other than you was there to do it.
I sincerely congratulate you and thank you for this development.
Sent from my GT-I9500 using XDA Premium 4 mobile app
nagpalkapil said:
There is no doubt as an individual u r the only Dev who has contributed so much for I9500 and brought it to the current level where we have official support from almost all the ROM's.
Only a few months back we had no options no Rom to try, but as an individual you contributed tremendously and helped us get official CM support. Then what in just a few days we had every other Rom team giving support to our device.
If u remember u were first trying to bring Omni but eventually landed giving us unofficial CM build.
It was a big surprise that we did not have Omni for so many days even after development for I9500 came to this high level.
Many Dev tried to build Omni but in vain, a Man who had real blood in his veins was required to get it working and who else other than you was there to do it.
I sincerely congratulate you and thank you for this development.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome.
Thank you all for supporting me.
Official support with nightly release coming soon
Alberto96 said:
Official support with nightly release coming soon
Click to expand...
Click to collapse
Good news ?
Thanks for The rom :good:
Yeah Alberto96, I think you are the best developer for i9500 devices, I like you work very much. We owe you respect for all the evolution we got. Please keep this awesome work forever.
This ROM isnt rooted? Cuz when i try to change LCD density with root explorer it gives me a error! And there is no superuser option on settings.. How do i root it?
leokak said:
This ROM isnt rooted? Cuz when i try to change LCD density with root explorer it gives me a error! And there is no superuser option on settings.. How do i root it?
Click to expand...
Click to collapse
Flash Super SU!
jgfernog said:
Yeah Alberto96, I think you are the best developer for i9500 devices, I like you work very much. We owe you respect for all the evolution we got. Please keep this awesome work forever.
Click to expand...
Click to collapse
Don't forget @intervigil
New build is up!
Enjoy
Alberto96 said:
New build is up!
Enjoy
Click to expand...
Click to collapse
Thanks but there is no theme support.
pedodroid said:
Thanks but there is no theme support.
Click to expand...
Click to collapse
If i remember well OmniROM doesn't have Theme Support

[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/d2vzw/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_d2vzw
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod/
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightlies
Created 2015-12-12
Last Updated 2015-12-12
Clean flashed earlier today and seems to be running great. Haven't found anything that doesn't work yet, camera, video, phone calls, GPS all seem to be working fine. Might be the best first nightly for any CM release on this device.
Sent from my SCH-I535 using Tapatalk
So installed Stock Gapps and the 1st nightly. So far so good, though I didn't get any of the stock CM software like messaging and the browser.
The default google camera gave me the typical "camera has failed" error that I got non stop on 12.1. My solution was always going with Open Camera. Never had issues but in a blue moon.
Any clue why?
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Shakes The AssClown said:
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
Click to expand...
Click to collapse
I remember CyanogenMod said a dirty flash from 12.1 is possible, but just not tried it yet
Do we need any special version of TWRP to flash this for 6.0?
Samsung.Galaxy.S3 said:
Do we need any special version of TWRP to flash this for 6.0?
Click to expand...
Click to collapse
Nope, flashed it with the latest twrp image from their site on my old s3 and it booted up just fine
Sent from my SCH-I545 using Tapatalk
So what exactly is working right and what still needs tweaking? Is this a daily driver at this point?
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
All Hail to @invisiblek!
{
"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"
}
pogeymanz said:
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
Click to expand...
Click to collapse
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Master Cylinder said:
All Hail to @invisiblek!
Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
Click to expand...
Click to collapse
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
pogeymanz said:
Yeah, I hate to clean flash, too. It's almost never actually necessary.
However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.
I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
Click to expand...
Click to collapse
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Master Cylinder said:
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from @Stealth111's thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.
This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.
Front facing camera will lock the app when clicked. Logcat to come.
Click to expand...
Click to collapse
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
pogeymanz said:
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.
I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.
I'll probably end up doing both strategies because neither will work...
Click to expand...
Click to collapse
I used 11/25 which didn't need the zip and have just kept going.
Here's the new changelogs for CM13 builds: http://www.cmxlog.com/13/d2vzw/
Thanks to invisiblek and CM Team for keeping us current!
Great work!
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invisiblek back in the d2 saddle. Thanks!
The d2vzw must have 9 lives because this is gonna make it last quite awhile longer!!
Let's give it up for @invisiblek once more!
Darn! Gif animation doesn't work on the XDA phone app.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see @invsiblek back in the d2 saddle. Thanks!
Click to expand...
Click to collapse
Mine seems to do better in battery saving mode than the other 2 - puts my address across the street but the dot is next door.
AyUaxe said:
Anyone try navigation with this rom and 6.0 gapps?
Click to expand...
Click to collapse
I haven't tried it while driving, but I've used it while walking, biking, and hiking. I have no idea what the difference is, but GPS is flawless on MM whereas I couldn't get a lock since KK. I usually get GPS fix in ~30-40s to ~5m accuracy. [[EDIT: That's actually in GPS only mode.]] My experience is that Mapquest is better for handling navigation purposes than Maps. Idk. Personal preference.
I follow in the footsteps of those before me, and hail the mighty invisiblek!
does anyone have a list of what currently doesn't work? I accidently flashed this when doing the weekly updates..
From what i noticed when just quickly messing with it..
Video Camera did not work (said couldn't access camera)
Front Facing camera froze (took picture but then would not let me click anything)

[ROM][i9305][6.0.1][GELLO] Temasek's UNOFFICIAL CyanogenMod 13 [UNOFFICIAL]

{
"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"
}
INTRODUCTION | DOWNLOAD AND CHANGE LOGS | FAQ, BUGS, AND KNOWN ISSUES | CREDITS AND THANKS
temasek's UNOFFICIAL CM13 BUILDS
This is an unofficial maintainer thread for all current and future unofficial builds of CM13 created by @temasek. This thread was created on his behalf and will be maintained accordingly. Please report any bugs or issues that you see; when applicable, please follow the bug reporting format found in post #3. Download links, changelogs and other important information can be found in post #2. Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
STOP!
If you do not read EACH and EVERY "OP" POST made by me (i.e. the first 5 posts) and post rudely, report bugs incorrectly, or ask for ETAs/feature requests, you WILL be called out for it.
You have been warned. Most, if not, any information you may be looking for can be found either in among these 5 posts or by performing a simple search using good key words. Think before you post. Thank you.
Download Links and Changelog
FAQ and Trouble Shooting
Credits and Thanks
The lastest version TWRP (3.0.2-1) is recommended.
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Dirty Flash/Update
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK.
3. Install the update zip from recovery.
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
3.2. FLASH AGNI AGAIN IF YOU ARE USING SUPERSU INSTEAD STOCK SU due to update zip flashing stock kernel.
3.3. Right after flashing ROM zip, flash updated GApps package. Flash the GApps right after to prevent "Setup Wizard has stopped working"
4. WIPE DALVIK/CACHE (for good measure).
5. Reboot Device.
[email protected]
Also consider donating to @PartimusPrime for making our amazing boot animation!: http://forum.xda-developers.com/donatetome.php?u=4620435​
Source Code:
https://github.com/limjh16/roomservice/blob/temasek13.0/roomservice.xml
XDA:DevDB Information
Temasek's UNOFFICIAL CyanogenMod 13, ROM for the Samsung Galaxy S III I9300
Contributors
limjh16, rodman01, p.a.n, Temasek, Trafalgar Square, Arter97, and whoever else who helped me!
Source Code: http://github.com/temasek/android
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.8
Stable Release Date: 2016-08-15
Created 2016-05-22
Last Updated 2016-08-15
Reserved
My AFH Folder for Temasek ROM
My Google Drive Folder for Temasek ROM
Open GApps [6.0.1]
MD5 file for ROM can be found on AFH.
Flash this to enable root access
SuperSU
CM13 Build
Build Version: v10.8
Android Version: 6.0.1_r61
For the most up to date changelog please visit:
Temasek’s CM13 Github Commits
I will also be including my own changelog in future builds.No difference from Temasek changelogs.​
Reserved
Multiple RIL Implementation
Since I am using @p.a.n sources multiple RIL implementation is active. However changes were made to both device, kernel and vendor sources which may have broken some things, because it did break RIL for me (Sometimes).
Multiple RIL implementation
In this ROM, there are more then one RIL implementations. None of them is perfect, but you can choose, which one of them works better for you. The first RIL implementation is the usual CM 12.1 based one (this is the default one), the second one is based on proprietary files extracted from stock 4.4.4 ROM downloaded from sammobile.com (I9305XXUFOB2_I9305PHNFOB2_I9305XXUFOA1_HOME.tar.md5), the third is based on proprietary files from TheMuppets, with one small change (see here for details). To switch between them open shell (over adb, or using the build in app, or whatever you like) and execute command ril. You will see something like this:
Code:
Select RIL implementation:
* 1 - CM 12.1 based
2 - Stock 4.4.4 based
3 - TheMuppets based
x - quit
?
I recommend you to change and play with the different implementations, however do keep in mind some things:
1. Stock 4.4.4 based IS NOT WORKING. You will notice RIL dies after reboot.
2. I personally use TheMuppets, but CM 12.1 is occasionally better. Do note that this is my personal preference, so do play with both implementations.
Titanium Backup - External SD Card problems (This Folder is NOT Writeable)
http://www.titaniumtrack.com/kb/tita...-not-writeable
Q: Is this ROM Stable?????? A: Yes. Unless stated as experimental.
Q: F2FS PLSSSSSS???? A: No.
Q: WHY NOT BOOT??? / WHY BUG???? A: Read below, and under "known issues"
Q: NEW BUILD PLS PLS PLS???? A: The weekend when Temasek finishes a new version
Some other issue?​You can't just say 'x is broken!' and expect me to magically find the bug and fix it.
Here's what I need:
Steps to reproduce - I don't care if "it's simple". I want to know exactly what you were doing at the time of the bug. How'd it happen? Does it only happen on Tuesdays when watching a specific YouTube video? Include it *all*
What happened - in what way is this *not* the expected behaviour? Don't just say "it didn't play/upload/whatever". Did the entire phone crash? Did it show an error? Did it just show an endless progress indicator? Again, I need specifics here.
Logcat/last_kmsg - Include the whole thing please, and if your phone's been running for a while, give me a rough region of time when the issue happened. Use last_kmsg if your device reboots unexpectedly, otherwise use a logcat.
For more FAQ, please visit @p.a.n 's thread here and read the OP as I used his sources.
HOWEVER PLEASE DO NOT POST QUESTIONS THERE. Just check whether your question is already answered.
I will answer all bug reports/questions to this ROM on this thread however please read above and adhere.
If you want SuperSU instead stock SU, Please flash Agni Kernel smdk4412 version or Boeffla Kernel.
If you want to install GApps after bootup, please follow the steps below:
1st method
Go to recovery and wipe /system
Flash ROM, then GApps
2nd method (If you want to update GApps)
Go to recovery and follow dirty flash instructions above
Tell me​
Reserved
@rodman01 @Trafalgar Square I did it haha
@p.a.n Thanks so much for source code
@temasek @arter97 for being creators of the ROM
and of course, to CM Slim AOKP Omni and whoever else helped in this ROM​
Last one, just in case.
What are the differences compared to normal CM?
dawidd6 said:
What are the differences compared to normal CM?
Click to expand...
Click to collapse
Check the change log. There are a lot of features kanged from other ROMS
Why not try it out and see for yourself?
with f2fs support will be Perfect
So many roms for our beloved s3. This is awesome.
I think that bug with gapps "setup wizard" crashing is depending on the gapps package and not the roms fault. :good:
JD. A said:
So many roms for our beloved s3. This is awesome.
I think that bug with gapps "setup wizard" crashing is depending on the gapps package and not the roms fault. :good:
Click to expand...
Click to collapse
Yeah it only happens with open gapps, but I don't recommend bank or Delta gapps because it's not tested haha... apparently the updater script is in the ROM, but I'm outside so I'm lazy to post instructions... will do when I get home
M4tEUSh said:
with f2fs support will be Perfect
Click to expand...
Click to collapse
Nope I'm sorry. I'm not a supporter of f2fs, I can't test it due to me being lazy to backup data/media )) and lastly it doesn't compile (main problem)
Thanks!
Add this to cm.mk
Code:
# Custom unofficial build tag
TARGET_UNOFFICIAL_BUILD_ID := temasek
Then you ZIP name will be cm-13.0-20160522-UNOFFICIAL-temasek-i9305-V8.6.zip
Trafalgar Square said:
Thanks!
Add this to cm.mk
Then you ZIP name will be cm-13.0-20160522-UNOFFICIAL-temasek-i9305-V8.6.zip
Click to expand...
Click to collapse
Why thank me? Anyways noted, will do that in next build.
@limjh16 root access works without flashing supersu. Just enable in developer options. The rom seems to be working fine.
JD. A said:
@limjh16 root access works without flashing supersu. Just enable in developer options. The rom seems to be working fine.
Click to expand...
Click to collapse
Yeah I did mention if u want to opt for SuperSU instead stock su
limjh16 said:
Yeah I did mention if u want to opt for SuperSU instead stock su
Click to expand...
Click to collapse
Oh I must have misunderstood then. The rom works great, had some random reboot at startup when selecting language. Other than that it's cool. I really like that you used p.a.ns multiple ril implementation too. It seems to be working better for me than the other roms.
JD. A said:
Oh I must have misunderstood then. The rom works great, had some random reboot at startup when selecting language. Other than that it's cool. I really like that you used p.a.ns multiple ril implementation too. It seems to be working better for me than the other roms. ????
Click to expand...
Click to collapse
Well, if that's so enjoy your stay! I will be regularly providing builds though don't expect any optimisations as I'm busy with another rom now haha
I will not be providing v8.8 due to problems in kernel by cm sources which disallows wifi to be connected.
congratulations @limjh16 been waiting for you to release your temesek:good:
alias_ z3d said:
congratulations @limjh16 been waiting for you to release your temesek:good:
Click to expand...
Click to collapse
Thanks! Finally fixed my errors lol

[ROM] LineageOS-14.1 for T31x

I am creating this thread as a place to discuss development of unofficial LineageOS14.1 builds for the T31x devices. Those of you that have been around here for a while already know that I tend to get busy with other stuff and disappear a times. So, with that said, if you would like to contribute to the development of this rom, please feel free to do so. I can make you a contributor and you will have the ability to modify this OP as required.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Standard Disclaimer
#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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
All the source code for LineageOS is available in the Lineage Github repo. And if you would like to contribute to LineageOS, please visit the Gerrit Code Review.
What Doesn't Work:
- flash it and see
==============================
If you want to use this tablet for phone calls, see THIS post before installing.
==============================
==============================
WIFI WORKS - BUT, If you have an issue with wifi not working AND your mac address shows a value starting with 02:00:00, do not post about it UNLESS you take a dmesg log (immediately after a reboot) and post it with your message. Google can tell you how to take dmesg log or see THIS thread.
==============================
INSTALLATION
- Make sure you're running latest TWRP version
- Copy GApps and rom ZIPs to your internal or external SDCard
- Boot into Recovery
- Perform WIPE:
In TWRP, select Wipe --> Advanced Wipe.
Check Dalvik/ART Cache, System, Cache, and Data
Swipe to Wipe
- Flash rom zip
- Flash GApps zip
- Reboot
Updating to a newer version of THIS rom ("dirty" flash)
- Boot into Recovery
- Flash rom zip (no need to re-flash gapps or wipe anything)
- Reboot
If you have any issues after doing a "dirty" flash, do a clean install before reporting any problems.
Downloads
gr8nole no longer builds. tigger 2014's builds pass safetynet and cuberio1 builds only occasionally.
LineageOS
Old Builds by gr8nole : https://www.androidfilehost.com/?w=files&flid=140570
Builds by cuberio1 : Google Drive
Builds by tigger2014 : https://androidfilehost.com/?a=show&w=files&flid=281549
Google Apps
OpenGapps: http://opengapps.org (use an ARM, 7.1 zip) I use nano.
HEADS UP: Be sure you flash the gapps package when flashing your rom. If you boot your rom, then try to flash gapps later, you will have issues.
CHANGELOG
For a list of LineageOS source changes, you can review the i9300 nightly changelog located HERE.
The i9300 is a similar platform to ours, so much of what is listed there will be applicable for us, unless it is i9300 device specific.
DEVICE SPECIFIC SOURCES
- Kernel: https://github.com/gr8nole/android_kernel_samsung_smdk4x12
- Common T31x device: https://github.com/gr8nole/android_device_samsung_lt01-common
- SM-T311: https://github.com/gr8nole/android_device_samsung_lt013g
- SM-T310: https://github.com/gr8nole/android_device_samsung_lt01wifi
- SM-T315: https://github.com/gr8nole/android_device_samsung_lt01lte
- Vendor files: https://github.com/gr8nole/proprietary_vendor_samsung
CONTRIBUTORS
- LineageOS Team, CyanogenMod and AOSP contributors.
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
XDA:DevDB Information
[ROM] LineageOS-14.1 for T31x, ROM for the Samsung Galaxy Tab 3 8.0
Contributors
gr8nole, cuberio1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: KitKat Firmware
Based On: LineageOS
Version Information
Status: Beta
Created 2016-11-04
Last Updated 2019-03-24
Reserved
Make sure you follow the installation instructions.
Do not ask about dirty flashing.
This is a very early build, so please don't start reporting a bunch of little bugs. I know there are things that don't work.
Wifi does work
Screenshots
Great work. Thank you!
Thanks for all the hard work!!!
Sent from my SM-G935T using XDA-Developers mobile app
Whaoo Thanks.
I tried it, wifi working, bluetooth also. I had difficulties with flashing because TWRP was not seeing my filesystem, so I flashed first with flashify, then formated my sd card, then reinstalled.
More details coming
Edit :
Internet, YouTube, Facebook, Dropbox, GPS, downloads working :
Not alpha anymore
You are the man!!!!
Awesome! Thanks!
Thanks for all the gr8t & hard work. I have flashed to CM14.1 on my Galaxy Tab 3.
What is working on my tab 3:
Wifi, bluetooth, gps, camera/video recorder!!!
All seems to be in order. Thanks again Gr8nole!!!
First build for T311 is up.
Give it a test and post logcat with any error reports.
gr8nole said:
First build for T311 is up.
Give it a test and post logcat with any error reports.
Click to expand...
Click to collapse
Can I have a dirty flash from cm13? I know should have a clean but just curious.
Thanhtho96 said:
Can I have a dirty flash from cm13? I know should have a clean but just curious.
Click to expand...
Click to collapse
Test a dirty flash. If it works then all good and if doesn't, clean flash it again.
sent from my beast, Samsung Galaxy Tab 3 8" T311 (old but gold?) running V5 S5 ROM using Tapatalk.
Ibbi786 said:
Test a dirty flash. If it works then all good and if doesn't, clean flash it again.
sent from my beast, Samsung Galaxy Tab 3 8" T311 (old but gold) running V5 S5 ROM using Tapatalk.
Click to expand...
Click to collapse
Nice anwser
As info..... This ROM supports RRO.....so the older Layers Manager will work to theme this beast!!!
T311 cant detect SIM. Logcat coming soon (Clean flash)
It also lag a little bit when open settings, play store etc (I mean animation, you can turn off it). And Battery is drain bcs miscellaneous bug. Here is t311's logcat
gr8nole said:
First build for T311 is up.
Give it a test and post logcat with any error reports.
Click to expand...
Click to collapse
Can you update Linux kernel to new version?
Бахрам Байрамза said:
Can you update Linux kernel to new version?
Click to expand...
Click to collapse
If it still can run great, so dont need to update it. Dont waste time
Ah new bug: Cant access external storage with every file explorer even file manager
Noob mistake or perm issues ?
Hello,
First of all, thanks for all the awesome work you have been doing with this build @gr8nole !
I needed a different/newer ROM for my tablet and have been waiting for a while to finally test one. :good::good::good:
Not sure if I need to modify or configure it properly but it seems that I'm having some permission issues ? I can't download and then save files from within a browser or manage to bypass a few tweaks I made ( ex: tried to VPN, it connects via OpenVPN and displays correct IP Server stats, but it still uses my local IP. Also had to copy the opvn file via USB cable ).
Not complaining and I am really glad that I am able to use such a recent build on my tablet ( and it looks and runs awesome ! ). Just wondering if there's anything one could do, in order to have it running exactly like I want it to !
s3vla said:
Hello,
First of all, thanks for all the awesome work you have been doing with this build @gr8nole !
I needed a different/newer ROM for my tablet and have been waiting for a while to finally test one. :good::good::good:
Not sure if I need to modify or configure it properly but it seems that I'm having some permission issues ? I can't download and then save files from within a browser or manage to bypass a few tweaks I made ( ex: tried to VPN, it connects via OpenVPN and displays correct IP Server stats, but it still uses my local IP. Also had to copy the opvn file via USB cable ).
Not complaining and I am really glad that I am able to use such a recent build on my tablet ( and it looks and runs awesome ! ). Just wondering if there's anything one could do, in order to have it running exactly like I want it to !
Click to expand...
Click to collapse
For browser downloading, you need to give the browser app "storage" permission, then may need a reboot for correct permission to apply.
Not sure about the vpn stuff.

[OFFICIAL] CyanogenMod 14.1 - mi4 [cancro]

{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review.
Wiki
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/cancro_Info
Installation
First time CyanogenMod 14.1 installation on your Xiaomi Mi4:
Read the official Wiki page
Unlock your bootloader if you haven't done so already
Flash a custom recovery via Fastboot
Push GApps (arm) and the CM 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of CyanogenMod (even from 13.0 and 12.1) :
Push the new CM 14.1 zip to your SD card
Boot into Recovery
Flash the CM 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Supported devices
Mi3w
Mi4 (WCDMA)
These devices are supported, but the maintainer WILL NOT fix bugs that are reproduceable just in those devices
Mi4 LTE
Downloads
Lastest Nightly : http://get.cm/get/cancro-latest.zip
Lastest Recovery (Nightly) : http://get.cm/get/cancro-latest-recovery.img
Lastest Snapshot : http://get.cm/get/cancro-snapshot.zip
Lastest Recovery (Snapshot) : http://get.cm/get/cancro-snapshot-recovery.img
-----------------------------------------------------------------------------
Google Apps (arm): wiki.cyanogenmod.org/w/gapps
All the builds: http://download.cyanogenmod.org/?device=cancro
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Model (Mi3 / Mi4 / Mi4 LTE)
* CM version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
I get error 7 while flashing this rom, what does it mean?
Read what the recovery says: "You're running on an unsupported (Kitkat) baseband". In order to flash the lastest CM builds you must have Miui MM baseband and partition layout installed. Visit http://bit.ly/cancroCMBaseband to learn how to update these
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Why no <insert miui feature here>?
Because this is CyanogenMod
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[OFFICIAL] CyanogenMod 14.1 - mi4 [cancro], ROM for the Xiaomi Mi 4
Contributors
linuxxxx
Source Code: https://github.com/cyanogenmod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: MiUi MM baseband and partition layout
Version Information
Status: Nightly
Created 2016-11-08
Last Updated 2016-11-14
Basic functionality is working fine. Non of the sensors are working.
sensor fix for cm13 not working here...
All sensors working here. And fix is merged for you guys.
Charging is crippled, though. Recommend all of you daily drivers wait.
We have to wait for at least one week to get everything done. They released it early this time so they'll fix the bugs daily
Visit this page for log files
https://www.cmxlog.com/14.1/cancro/
Everything that will be updated will be listed here
The new build is great. It has been one day. No issues. Battery life is great. All sensors are working. Camera quality is not bad. And the rom is for daily drivers. Only problem is slow charging issue. I hope it will be fixed soon. Get into the nest guys
Someone please, can upload a photo taken with this ROM ? I need see the quality , thanks
Enviado desde mi MI 4LTE mediante Tapatalk
Hi, is there any way to see if phone is unlocked? I got phone with custom MIUI 8 from czech developers with pre-installed TWRP, does that mean that phone is unlocked? Thanks I guess it is, because I can manually flash new updates of MIUI 8 through TWRP. Btw. really like this rom!
TrueMS said:
Hi, is there any way to see if phone is unlocked? I got phone with custom MIUI 8 from czech developers with pre-installed TWRP, does that mean that phone is unlocked? Thanks I guess it is, because I can manually flash new updates of MIUI 8 through TWRP. Btw. really like this rom!
Click to expand...
Click to collapse
AFAIK Mi4 models are not bootloader locked from factory. BUT if you already have TWRP installed then it is definitely unlocked.
Okay, thank you so much i thought the same but I wanted to be sure and how is it with going back to MIUI? Can I just flash MIUI in TWRP to go back?
TrueMS said:
Okay, thank you so much i thought the same but I wanted to be sure and how is it with going back to MIUI? Can I just flash MIUI in TWRP to go back?
Click to expand...
Click to collapse
Yes. But once you flash you'll never like miui. CM is better in every way. I'm using CM from 2 years. You'll like it
rahulkamma14 said:
Yes. But once you flash you'll never like miui. CM is better in every way. I'm using CM from 2 years. You'll like it
Click to expand...
Click to collapse
I know, I was using CM on my Zenfone 5 and S3 mini, it's awesome, but I kinda like MIUI, our czech version of MIUI is debloated and without annoying apps and a lot faster, and also im asking because there can be some breaking bug so I will have to go back to the MIUI.
TrueMS said:
I know, I was using CM on my Zenfone 5 and S3 mini, it's awesome, but I kinda like MIUI, our czech version of MIUI is debloated and without annoying apps and a lot faster, and also im asking because there can be some breaking bug so I will have to go back to the MIUI.
Click to expand...
Click to collapse
i also dont like miui since i flash cm based rom
btw if u want debloated miui there are 2 site for that xiaomi.eu and mi-globe.com . go ahead
edit : u need twrp to flash miui from both site
TrueMS said:
Okay, thank you so much i thought the same but I wanted to be sure and how is it with going back to MIUI? Can I just flash MIUI in TWRP to go back?
Click to expand...
Click to collapse
you can flash official firmware without TWRP or you can head to the Xiaomi.eu and flash the zip from twrp.
And, I'd prefer CM with 7.1 on my Mi4 but since Qualcomm not releasing the vulcan files for our SoC, not sure how it will affect it :/ damn you Qualcomm.
Things are working great! Except for the slow charging. *Edit* After flashing ZheurionX Kernel and Feralab script mod. Charging problem is gone and no problem with battery backup either. Now this rom is my daily driver.
epulrevo said:
Things are working great! Except for the slow charging. *Edit* After flashing ZheurionX Kernel and Feralab script mod. Charging problem is gone and no problem with battery backup either. Now this rom is my daily driver.
Click to expand...
Click to collapse
Sorry for double post, but I can't upload pic in "edit"
CM 14.1 with pixel launcher
Battery life is excellent
Mr_Bushido said:
Someone please, can upload a photo taken with this ROM ? I need see the quality , thanks
Enviado desde mi MI 4LTE mediante Tapatalk
Click to expand...
Click to collapse
Camera quality is good
Nobody is facing issues with Auto-Rotate feature?
Cheers,
Sarat

Categories

Resources