[DISCONTINUED][ROM][5.1.1][OFFICIAL] Cyanogenmod 12.1 for SM-T700 - Galaxy Tab S Original Android Development

{
"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 5.1 (Lollipop), 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. Your changelog is whatever was merged into gerrit.
Official CyanogenMod Wik
Important information:
This thread is for CyanogenMod 12.1 builds for klimtwifi (SM-T700). The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
Useful links
Unofficial klimtwifi changelog
CyanogenMod Wiki jfltexx
Jira issue tracker - don't report bugs for nightly builds!
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog
Downloads
CyanogenMod:
Nightlies: http://download.cyanogenmod.org/?device=klimtwifi
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[DISCONTINUED][ROM][5.1.1][OFFICIAL] Cyanogenmod 12.1 for SM-T700, ROM for the Samsung Galaxy Tab S
Contributors
deadman96385
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2015-11-19
Last Updated 2016-06-14

Reserved
Welcome everyone! I am now the new Official Cyanogenmod klimtwifi maintainer
Known Issues
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu) - works on some apps (i.e. bootloguptime) on others not.
Some minor crackling when using bt-audio the same time as 2.4GHz wlan (5Ghz wlan is issue free).
YOU tell us...

General changelog of merged changes since i have taken over maintaining:
Made the QS menu slightly bigger (Looks nicer)
Using the half-resolution boot animation (The full res one stutters and slows down boot)
Added and enabled BFQ
A bunch of sepolicy updates from chagallwifi
bluetooth,voip permissions added (Not uber important)
Add Samsung SSWAP support (Swap support)
Changed graphics driver from t6xx to midgard.
Added some missing exynos video support
Change from Samsung proprietary lpm charging to android universal charging.
Updated mali blobs from kitkat to Lollipop based (specifically the canadian T700XXU1BOI1 5.0.2 package)
Changelog of my current test build:
Enabled ANT+ Wireless support (I have no way to test this)
Updated wifi,bt,video encoders/decoders,misc other vendor blobs from kitkat to Lollipop based (specifically the canadian T700XXU1BOI1 5.0.2 package)
Test build (Use any gapps you like):
Here
Test build known bugs:
I forgot to enable charge percentage for offline charging, should be fixed in the next build
At least for my bluetooth headphones audio playback in youtube is delayed by about 1 sec
Youtube will only go up to 360p (Probably related to the bluetooth audio issue)

Good news for all of us thanks @deadman96385

First AICP NOW CM12.1 THEN CM13 NICE WORK MY FRIEND thanksss

deadman96385 said:
Welcome everyone! I am now the new Official Cyanogenmod klimtwifi maintainer
Known Issues
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu) - works on some apps (i.e. bootloguptime) on others not.
Some minor crackling when using bt-audio the same time as 2.4GHz wlan (5Ghz wlan is issue free).
YOU tell us...
Click to expand...
Click to collapse
Thanks a lot @deadman96385! Hoping to have stable cm 12.1 snapshot version soon!

I am curious, I have read up that 5.1.1 has native USB Audio built in, but most everyone has been using 5.0.x and having to use an app to play music through a USB DAC, but when it comes to any other sound generating app such as YouTube, a video player, etc audio is routed directly through the tablet. I have a high end DAC but I don't trust using it for what I'm planning since it's a 5.1 Asus Xonar. I wouldn't trust it not working to judge another. I know my S6 that only works with the specific music apps, unable to test the T700 right now, sorry for the story, just wanted to know if there are USB Audio Drivers built into cm12.1
Sent from my SM-G925T using Tapatalk

Tab Pro 8.4 got CM13 nightlies, hope the tab s can follow soon. BTW, this rom is amazing!

How can i root this? Kingroot doesn't work and cf autoroot says it doesn't work on samsung 5.1+

andreas0013 said:
How can i root this? Kingroot doesn't work and cf autoroot says it doesn't work on samsung 5.1+
Click to expand...
Click to collapse
My god did you ever google or read posts
Cm12.1 is already rooted just enable it in developer option search root access put apps or apps and adb

rookie12 said:
My god did you ever google or read posts
Cm12.1 is already rooted just enable it in developer option search root access put apps or apps and adb
Click to expand...
Click to collapse
Thanks for the info, maybe next time skip the first part

heavy batterie drain with about 30% per hours with 20% brightness

kleinmischa said:
heavy batterie drain with about 30% per hours with 20% brightness
Click to expand...
Click to collapse
I get that on gaming on all AOSP CM12.1 BASED ROMS dont know why?

rookie12 said:
I get that on gaming on all AOSP CM12.1 BASED ROMS dont know why?
Click to expand...
Click to collapse
i was just browsing. the cpu was mostly below 1000 mhz. This is a bit disapointing since it was around 10-15% per hour with the original rom.

kleinmischa said:
i was just browsing. the cpu was mostly below 1000 mhz. This is a bit disapointing since it was around 10-15% per hour with the original rom.
Click to expand...
Click to collapse
Same here.
Sent from my SM-T700 using XDA Free mobile app

I am working on moving to a new gpu driver that seems to be giving a much better battery life under heavier load.

deadman96385 said:
I am working on moving to a new gpu driver that seems to be giving a much better battery life under heavier load.
Click to expand...
Click to collapse
At gaming too just asking
Looking forward thanks for your hard work mate

rookie12 said:
At gaming too just asking
Looking forward thanks for your hard work mate
Click to expand...
Click to collapse
I do not game much on my tablet
General changelog of merged changes since i have taken over maintaining:
Made the QS menu slightly bigger (Looks nicer)
Using the half-resolution boot animation (The full res one stutters and slows down boot)
Added and enabled BFQ
A bunch of sepolicy updates from chagallwifi
bluetooth,voip permissions added (Not uber important)
Changelog of my current test build:
Change from Samsung proprietary lpm charging to android universal charging.
Enabled ANT+ Wireless support (I have no way to test this)
Add Samsung SSWAP support (Swap support)
Changed graphics driver from t6xx to midgard.
Added some missing exynos video support
Updated wifi,bt,video encoders/decoders,misc other vendor blobs from kitkat to Lollipop based (specifically the canadian T700XXU1BOI1 5.0.2 package)
Please test what you can eg wifi, bluetooth, video and audio playback
Test build (Use any gapps you like):
Here
Test build known bugs:
I forgot to enable charge percentage for offline charging, should be fixed in the next build
At least for my bluetooth headphones audio playback in youtube is delayed by about 1 sec

baterie drain is around 15% per hour while surfing with 20% brightness. What I'm wondering is that if the tablet is in deep sleep it show no batterie drain ( 0% in 20h with wifi off). But after I start the tablet again the batterie goes kinda fast down to a certain point and stops again. This phenomen was present during all previous nightys. Lets see how it is with the new build.

Crackling through BT while on 2.4 Wifi is known but I am also having loss of sound synchronization on YouTube. No issues if wired headset is used.

Related

[ROM] CyanogenMod 11.0 | Android 4.4.4 KitKat | [Developer-Nightlys]

{
"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"
}
DO NOT REPORT BUGS UNLESS YOU HAVE DONE A FULL WIPE, INSTALLED THE GAPPS PROVIDED IN THE 2ND POST, AND ARE RUNNING STOCK KERNEL WITHOUT STUPID MODS OR YOUR BUG REPORT WILL BE IGNORED PERIOD.
These are UNOFFICIAL/DEVELOPER builds of CM11 with test fixes for bugs in this thread that will eventually be merged into CM nightlys for klte (GSM), klteusc, kltedv, and kltevzw devices and by NO means this is my ROM. I am just compiling from
CM Source and 100% credits goes to TeamDouche, and all other coders who contributed to CyanogenMod.
For which devices, should work with all klte versions that are qualcomm
Included in the Unified GSM build
kltexx,kltelra,kltetmo,kltecan,klteatt,klteub,klteacg,kltedcm,klte
Individual CDMA builds kltevzw,klteusc,kltespr
Individual GSM builds kltedv
If your device isn't listed in the "individual" lists then flash the generic "klte" build
Click to expand...
Click to collapse
Code:
[B]IMPORTANT[/B]
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT ask for support for flashing in this thread.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
I personally am not fond of these kinds of threads, If it turns into my last one I WILL LEAVE and close the thread. We have started some momentum here. Let's keep it rolling .
Built from CM source
Service
Text
Data
Call
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Internal/External SDcard mounting
Camera
Video recording
IR Blaster
NFC
Touchscreen in some games....
General CM bug: newest instagram update results in black pics...Rollback the update to fix...Then email FB and tell them to fix their apps
Do NOT use superwipes
Wipe data, cache, and dalvik cache
** (if you are simply applying an update to this rom base this might not always be required)
*** ((but do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS (in 2nd post) (No other gapps packages are officially supported!)
Reboot
???
Profit
To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
Read the FAQ thread here before posting any questions in this thread: FAQ
And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
Garwynn XDA
Tom Marshal (tdm)
Ethen Chen (intervigilium)
ktoonsez
Esa Laukkanen aka elelinux
Cyanogen Inc & Team-Kang
MrTrip
albinoman887
so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Thanks and happy flashing!
DOWNLOAD LINK + CHANGELOG in 3nd post
XDA:DevDB Information
[ROM] CyanogenMod 11.0 | Android 4.4.4 KitKat, ROM for the Samsung Galaxy S 5
Contributors
albinoman887, ktoonsez
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-09-01
Last Updated 2014-10-16
Reserved
do not report bugs unless you have done a full wipe, installed the gapps provided in the 2nd post, and are running stock kernel without stupid mods or your bug report will be ignored period.
BUG REPORT TEMPLATE, IF YOU WANT A RESPONSE FOLLOW THIS!!!
Device:: T-Mobile G900T kltetmo
Baseband: ENTER_VERSION_HERE
Bootloader: ENTER_VERSION_HERE
EFS: ENTER_VERSION_HERE
ROM Ver: ENTER_VERSION_HERE
Description: Wiped, flashed 9/8 build, correct Gapps loaded. Everything loaded fine.
BEFORE YOU POST....WORDS FROM A SMART MAN....
MrTrip said:
Hey all, I'd just like to throw this out there for those of you having random bugs.
This is a development tree. Its not stable or even RC. Its testing. While all the testing and bug reports are appreciated, some of these bugs can be solved with the following troubleshooting steps..
1. Make sure you have a clean install. This is most important. Dirty flashing can cause issues even from one build to the next days build. Some apks are changed and if you don't do a full clean flash these settings are not refreshed. Please do a clean flash and test this way.
2. Some issues may arise from using titanium backup to restore apps + data. Unless you absolutely positively need to restore data with these apps I'd advise against it. Albinoman887 had me to a restore of apps without data and things got much smoother.
3. I can't stress this enough from my own experience, xposed modules can and will break CM11. You might think you are making a minor change but it might be the wrong way to make this change.
4. Some apps do interfere with each other. Camera crashes can occur when a GPS fix app is running because the camera cannot geo tag a photo and it just crashes the camera. This is one that albinoman887 noticed the other day. THIS MAY NOT ALWAYS BE THE CASE. But its good to check that for yourself.
5. I know we all want to use our phone for 10 hours constantly no charge and be left with 99% but this simply cannot happen. It would be great if people could just test the rom vanilla and report issues that arise from that. I promise you i have no third party app "saving my battery" and my battery life is great.
6. When submitting a bug report please always mention your carrier and phone model. It helps to narrow down the issue. This is a unified build so an issue on a Verizon wireless s5 and a us cellular s5 might be different or not exist at all on the other units. This I cannot stress enough. Even if you noted your model before, we don't keep a database of users and their models so we do forget when looking for solutions what model this is broken on.
Being a part of this is like an open beta. Opt in or out it is your choice but help us, especially Albinoman887, help you by having the information he needs to find and squish these bugs.
I'm currently helping build a solid bug list with models and information but its hard to maintain when some bugs are because of a dirty flash or a third party app.
Let's make CM11 on the Galaxy S5 be the best it can be!
Thank you for your time, support, and any donations given to the developers during this process. Nobody would be here if it wasn't for a good solid team effort.
Sent from my SM-G900R4 using XDA Free mobile app
Click to expand...
Click to collapse
Fixes NOT YET MERGED into OFFICIAL CM branch.
* UNOFFICIAL kltedv specific builds with fixed NFC
Old Changelogs
Sep-27
* Synced with upstream
** The following changes have not been merged into main CM source yet! **
* Fixed NFC for G900I device
* Added proximity wake up support
* Merged a fix from hlte to help with VOIP choppiness
Sep-24
* This will be the last build compiled by me since nightlys are turned on.
* we now are using the stock GSM ril libs....
* Upstream updates
Sep-19
* First release with split up builds....
* Initial klteusc build
* initial klte gsm only build
* GSM: switched to KK HLTE RIL libs so we can use the new custom RIL class
* CDMA uses all official STOCK KK RIL libs
* Any and all upstream updates at time of compile
** VZW coming soon **
Sep-14
* Fixed touchscreen staying on while screen is off
* Updated vibration strength code (upstream) if dirty flashing and you have changed intensity settings PLEASE RESET TO DEFAULT as the scale has changed
* HighTouchSensitivity (glove mode) now actually works (tested by checking sysfs entry and using my shirt over my finger)
* Updated GPS HAL source to caf branch kk_3.5
* All upstream changes at time of compile
Sep-10
* Removed key disabler support because there are kernel side changes I haven't implemented yet.
* Fixed capacitive keys staying on during a phone call
Sep-8
* Did a bit more tweaking to high-gain-stereo recording mic
* Enabled vibration strength settings (Settings>Sound>Vibration Intensity)
* Enabled high touch sensitivity (Settings>Language & Input)
* Enabled key disabler for when switching to nav bar mode but I can't find it in settings. I might be missing a change...
* Upstream updates
Sep-6
* This is mainly a maintenance update. I went back through the source and double and checked and tested reported bugs.
* Tested phone calls: Dialer works, dialing pad works, no lag when pressing call, called people in and not in my phone book by tapping and by dialing, and people can hear each other. Tested 3 times. from a cold boot. Issues with phone include: capactive keys are still responding when in a call and the screen is off so it is possible to back out of the phone app while on the call and start pressing things with your face
* Tested touchscreen in Snes9x EX+: Still the same issues. No response from touchscreen
* Attempted fix for G900I users and NFC but obviously I can't test since I don't have the device.
* Cherry-picked about 4 coomits from gerrit dealing with audio routing improvements.
* Synced with upstream
Sep-5
* PLEASE ONLY USE THE GAPPS PROVIDED IN THE 2ND POST. NO OTHER GAPPS PACK IS SUPPORTED AND IS KNOWN TO CAUSE ODD ISSUES
* Reverted back to old ril stack since we weren't using 100% stock libs anyways and it was breaking cdma. Will revisit at a later date
* Fixed CDMA (obviously)
* Tried reverting "enable denoise by default" for camera to see if it fixes instagram. Please let me know as I don't use the app
* Any and all upstream updates at time of compile
* Working Sprint NC
* Kernel: merged back ONE change we had in the old bringup branch to see if it fixes audio issue reported by "some" users
Sep-4
* Fixed screw up on my part for NFC. Should be working now
* Added subjective NFC driver loading support so one build can work for sprint and all others (untested on sprint)
* Corrected partition sizes (ktoonsez)
* Enable denoise in camera by default
* Any and all upstream changes at time of compile
* GSM is now using 98% stock RIL libs.
^^ in a nutshell, we were before using all HLTE jellybean RIL libs. If we used ours we would get no data and could not make phone calls. Now with a recent patch to cm we are able to make calls with our ril. what was done was (not by me) digging into the TW framework and finding calls that we don't have. That's what ixed the calling issue. HLTE is now using KK ril blobs due to this fix. They don't have any data issues. we still do unless I swap out libsec-ril.so and then because they tie together also libqmiservices.so to the HLTE KK one (before we were also swapping libril.so to HLTE JB before the patch). Now the reason I think this swap is needed is because of the download booster option in TW. Since AOSP doesn't offer this we most likely need to set something on code that always returns "0" or off for that feature. It will take some digging though. This still gets us a lot closer to stock. there are about 15 files related to the "ril stack" only 2 aren't from our device now. Also I've read through many logs and don't see any regressions from using these two libs
Sep-2
* Fixed NFC (won't work on sprint models until I make a special build just for sprint later today)
* Fixed IR blaster (at least on TMO)
* Switched to newest libqmiservices.so that can be used with the old GSM ril libs (CDMA is using stock KLTE)
* Any upstream changes by CM at time of build
Sep-1
* Attempted to fix issue some were having with wifi password resetting
* Now using about 99% stock NG3 libs. Only swapped libs are the rils from hlte as well as an older version of libqmiservices (NE5) to work with the older RIL libs. Rest 100% stock
* Slowly re-adding some kernel fixes to test battery drain
* Searching for contacts in dialer works
* Low recording mic gain fixed (I fixed this i think yesterday or the day before but forgot to mention it)
** This wasn't really mentioned and I don't know if Esa has added it but right when CM added sources Ethan re-wrote the audio routing code. So now all audio issues should be fixed and small ones that aren't like above should be easy fixes from here on out
*** The next changes may or may not have already been in place in the last builds but I want them to be documented ***
* 100% stock keylayouts
* 100% stock mixer paths
* Enabled dock settings
* GPS should be pretty stable now. We are now using all the correct configurations and libs
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
kltedv :KLTEDV Nightlys
kltespr : KLTESPR Nightlys
klteusc : KLTEUSC Nightlys
kltevzw : KLTEVZW Nightlys
If your specific model isn't listed above and is a CDMA device it is not supported. Otherwise flash the unified GSM build below....
Unified-GSM : KLTE Nightlys
----------------------------------------------------------------------------------------------------------------
GAPPS: : HERE
----------------------------------------------------------------------------------------------------------------
BUILDBOT MIRROR : DOWNLOAD MIRROR
Thanks. Have you guys fixed the touchscreen issue? Don't see it mentioned. Downloading now and will post my results.
Sent from my SM-G900T using NSA's decryption technology.
velayo said:
Thanks. Have you guys fixed the touchscreen issue? Don't see it mentioned. Downloading now and will post my results.
Sent from my SM-G900T using NSA's decryption technology.
Click to expand...
Click to collapse
i dont know i asked when i posted the last bug but no one replied
Thanks for the fast reply. I will know in a few minutes.
Sent from my SM-G900T using NSA's decryption technology.
I'm probably doing something wrong here, but every time I try to flash this I get a failed message on twrp. Md5 matches, and I'm on a 900t.
Sent from my SM-G900T using Tapatalk
velayo said:
Thanks. Have you guys fixed the touchscreen issue? Don't see it mentioned. Downloading now and will post my results.
Sent from my SM-G900T using NSA's decryption technology.
Click to expand...
Click to collapse
Installed this ROM and can not find a touchscreen problem..(what was the problem in other release ?)
Installed also GAPPS and no single error!!
Other ROMs always get a "service stop" error.
Now I'm restoring with titanium and looks great..
Nice! Finally a separate thread.
Thanks for the thread! @albinoman887
Okay, what specific device did you working on and what the difference from elelinux build. Since a little bit confused lately for us and for custom aosp ROM modders
Tried this on my G900i and it works great. Haven't had an issue at all. Thanks!
Am I the only one using cm on a us cellular variant?
Running the latest build on my G900F. Smooth as f***. Thanks devs :good:
thenashy said:
Tried this on my G900i and it works great. Haven't had an issue at all. Thanks!
Click to expand...
Click to collapse
Good to know. Been waiting for a cm build to run on my 900I
So, WiFi is fixed on my G900R4. The only thing I can see is that touch screen still doesn't work on certain apps such as xbmc or almost any emulator. Also, it doesn't know my network, just says roaming indicator off.
My Antutu benchmark : 42166
Can't paste (link) a printscreen.png
warezjunk said:
My Antutu benchmark :
Click to expand...
Click to collapse
How's battery life?
albinoman887 said:
i dont know i asked when i posted the last bug but no one replied
Click to expand...
Click to collapse
Overall the touchscreen works much better now. However when I use Papyrus (note taking app) I don't get any response from the screen.
Sent from my S5 using NSA's proprietary decryption technology.
butterfff said:
How's battery life?
Click to expand...
Click to collapse
Better then stock..

[ROM][5.1.1_r37] UNOFFICIAL CyanogenMod 12.1.1 [STABLE][14/10/2016]

{
"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"
}
Hi everyone, i am currently building a weekly version (or monthly, depending on CyanogenMod fixes and patches) of CyanogenMod 12.1 for a while now, i thought i could share it with you, because peregrine cm-12.1 branch is no longer supported by CyanogenMod.
I made some little modifications to the framework, the device tree and the kernel, which you cand find in the source section.
For those who don't read at those stuffs, the changes are:
- Restored Ambient Display (and tuned a bit) and MotoDoze (wake gestures etc.), since the black screens have been fixed a while ago, this feature is now working correctly here on CM12.1
- Status bar date customizations
- Ability to hide SU icon on status bar (developer settings)
- KCAL support (adjust color contrast and saturation with this app: http://downloads.codefi.re/savoca/kcal)
- Proximity check on wake (disabled by default, you can enable it in Settings/Display), prevents accidental wake ups
- Dexpreopted
- Cyanogenmod's Screencast app from cm-13.0 branch
- Kernel security fixes from cm-13.0 branch
- PowerHAL updates from cm-13.0 branch
- General device tree updates from cm-13.0 branch
- LuK1337 gently found a fix for the GPS bug that forced you to erase modemst1 and modemst2 to make GPS work, so you won't need to do that anymore
- Updated all the libraries and apk/jar's from latest 5.1 build
- Updated Adreno libraries to 5.1 (Motorola is still using 5.0 ones on their 5.1 build)
- CyanogenMod fixed the soft reboots due to strictmode violations (https://github.com/CyanogenMod/andr...mmit/1e60f9b9ae10d46d028c19c90cf0f52d40ca620a), so this fix is of course included here, but is not included in the latest public snapshot for falcon on the CyanogenMod site, so this can be a reason of switching from that snapshot to this build.
- CM12.1 branch is pretty stable right now, so you shouldn't have any major problem
DOWNLOAD
CHANGELOG [09/03/2016]
CHANGELOG [16/03/2016]
CHANGELOG [25/03/2016]
CHANGELOG [05/04/2016]
CHANGELOG [12/05/2016]
CHANGELOG [15/06/2016]
CHANGELOG [09/07/2016]
CHANGELOG [10/08/2016]
CHANGELOG [14/10/2016]
If you want to thank me, click on this link once a day:
CLICK (wait 5 seconds and click on skip ad, then you can close the window)
Also, consider donating to LuK1337, luca020400 or Gabriele M for keeping active motorola msm8226 development
READ POST #2 IF YOU HAVE ANY TROUBLE WITH THE ROM, IF IT'S A COMMON PROBLEM, IT WILL BE THERE
CUSTOM KERNELS AND/OR XPOSED OR ANY OTHER MOD ARE HIGHLY UNSUPPORTED
You may want to take a look at this "project" too: http://forum.xda-developers.com/moto-g/themes-apps/apps-cyanogen-camera-gallery-t3187041
Credits:
- LuK1337
- luca020400
- Gabriele M
- hurtsky
- savoca
- matmutant (for the logo xD)
- Motorola and all the CyanogenMod contributors
XDA:DevDB Information
CyanogenMod, ROM for the Moto G
Contributors
fonz93
Source Code: https://github.com/MotoG-2013
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 41.18+ Bootloader version
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2016-10-14
Created 2016-02-24
Last Updated 2018-02-08
NOTE:
- Reported bugs without any useful logcat will just be trashed
- If you flash any CM12.1 custom kernel, you must flash this package: https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
in order to downgrade your camera blobs from 5.1 to 5.0, if you don't this, the camera won't work ***
-- If, for any reason, you decide to go back to the kernel included in this ROM, you have to install again 5.1 camera blobs, the easiest way to do that is flashing the ROM .zip.
*** I updated camera blobs from the latest Motorola factory image, a kernel update was needed in order to make camera work after updating the blobs (that's not an hack, is a regular update from Motorola), but CyanogenMod dropped CM12.1 nightlies before doing this, so any CM12.1 based kernel doesn't contain that kernel update, that's why you need to downgrade camera blobs to 5.0.
I have to remind you that installing a custom kernel will break any future support by me
Hi fonz93. I am considering installing this version of CM12.1. I am curious about the Kernel. Have you implemented any changes other than the camera blobs stuff? I like to have Adreno Idler as it extends battery life a good deal for me.
razlack said:
Hi fonz93. I am considering installing this version of CM12.1. I am curious about the Kernel. Have you implemented any changes other than the camera blobs stuff? I like to have Adreno Idler as it extends battery life a good deal for me.
Click to expand...
Click to collapse
No, i've just added few kernel security fixes and other minor fixes from cm-13.0 branch, the only external thing i've added is the KCAL support, i don't think i will add something more unless strictly required, sorry
fonz93 said:
No, i've just added few kernel security fixes and other minor fixes from cm-13.0 branch, the only external thing i've added is the KCAL support, i don't think i will add something more unless strictly required, sorry
Click to expand...
Click to collapse
That's cool. I'm on stock at the moment and it runs really stable. Not sure about honing to cm12.1 or cm13.
Thank you @fonz93!! I already loved CM10.2 you did for Huawei Y300, I really like your effort to make stable build for earlier versions when other devs change their focus to the last Android version
I'm currently on CM12.1 from beeto, can I have a brief excursus about difference with your build?
This build is made for stability, so it won't include the thousand of features that the other ROMs have, expecially in the kernel, i don't know which features the build are you referring to has, but you can find all the differences from the official cyanogenmod build in first post
fonz93 said:
This build is made for stability, so it won't include the thousand of features that the other ROMs have, expecially in the kernel, i don't know which features the build are you referring to has, but you can find all the differences from the official cyanogenmod build in first post
Click to expand...
Click to collapse
Here's the rom I'm using http://forum.xda-developers.com/moto-g/4g-development/rom-unofficial-cyanogenmod-11-t3017616
Well, the build is 3 months old, it doesn't include many important fixes (one of them is the strict mode violation fix that causes soft reboots) and many kernel security fixes.
It has a custom kernel while i use a cyanogenmod based kernel plus some fixes backported from the cm-13.0 branch. For the ROM side differences read the first post
This ROM looks very well, but I miss some features.
1.- DT2S on LockScreen
2.- DT2S on NavBar
3.- Network Activity on StatusBar
4.- TaskManager on StatusBar
Everything else is OK. Thanks for your work, Go on!
I am now including in my folder (the one where you can download my CM12.1) a build of TWRP 3.0 wich slightly differs from the one in this forum, thanks to Gabriele M (which will probably be the official TWRP mantainer), the long time wait for wiping /cache and /system and the not responsive touch is fixed, i am not opening a new thread because once Dees_troy (TWRP developer) merges Gabriele M changes into the official peregrine device tree for TWRP, i will stop mantaining my version as it would have no difference from the official build.
Note: The kernel source used to build the TWRP recovery is this: https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-13.0, so it will work on every ROM, both Lollipop and Marshmallow.
sorry double post
I tried the rom, it's very fast and smooth.
I miss two things in particular:
1) switch network (2g/3g/4g) in quick settings (I really can't understand why CyanogenMod 12.1 doesn't have it, I've had this feature since CM7.2).
2) remove shutter sound when taking a picture.
I would love to have those features, but I would like to avoid installing Xposed modules.
Does anyone know why CM devs removed them in CM12/12.1?
DeX1009 said:
I tried the rom, it's very fast and smooth.
I miss two things in particular:
1) switch network (2g/3g/4g) in quick settings (I really can't understand why CyanogenMod 12.1 doesn't have it, I've had this feature since CM7.2).
2) remove shutter sound when taking a picture.
I would love to have those features, but I would like to avoid installing Xposed modules.
Does anyone know why CM devs removed them in CM12/12.1?
Click to expand...
Click to collapse
It's not like they removed them, but the android source has changed so much that they couldn't just port the feature over the new version, no one came up with a working and bugfree patch on gerrit.
About the camera shutter, i don't know, it's not something i care that much, you can just get rid of it by installing a camera from play store
Hello, this ROM is compatible with Moto G 4G (2013) XT1042?
Thank y
pickmod said:
Hello, this ROM is compatible with Moto G 4G (2013) XT1042?
Thank y
Click to expand...
Click to collapse
If the official CyanogenMod works, this one works too, which difference your phone has from european version?
Any chance to tweak the developer option "hold down back key to kill app" delay time to 500ms?
Axaion said:
Any chance to tweak the developer option "hold down back key to kill app" delay time to 500ms?
Click to expand...
Click to collapse
+1, I would love to have this feature.
Issue ive had is that people are complaining they cant hear me in phone calls, i tried the sound recorder and its extremely low, as in if i tap the phone you can hear it, but id have to scream for it to pick up voices.
Axaion said:
Issue ive had is that people are complaining they cant hear me in phone calls, i tried the sound recorder and its extremely low, as in if i tap the phone you can hear it, but id have to scream for it to pick up voices.
Click to expand...
Click to collapse
No problem here

[ROM] [7.1.2_r36] [i9082] [UNOFFICIAL] LineageOS 14.1 [2018/03/27]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device..
Code:
#include
/*
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 based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github RepoAnd if you would like to contribute to LineageOS, please visit out Gerrit Code Review
Device-specific source code:
Device tree
Kernel source
 Compatibilitiy Patches:
WebView
Downloads
ROM
RECOVERY
GAPPS
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera
Video (playback & recording)
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
Screenshots and Recents App thumbnails are blank
Runtime storage permission does not fully work (setns kernel patches are not applied, see com.android.cts.appsecurity.PermissionsHostTest#te stInteractiveGrant CTS test. After granting permission, the app will need to be restarted before it sees the new permission.)
Additionally, Dual SIM has the following limitations (once they work):
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to stock 4.2 first.
Install ClockworkMod recovery with SELinux support. Older CWM will result in a "status 7" error.
Reboot into recovery
If you are using a recovery which mounts /system on boot, unmount it before installing
Wipe data if coming from stock or other ROMs (You may get a "status 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon (In Marshmallow, you MUST flash gapps before booting into the system for the first time or else the proper permissions will not be granted resulting in Setup Wizard crash. If you experience the crash, you will need to do a factory reset.)
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again. (However, if you are experiencing strange issues, you may want to try a wipe.)
Credits
LineageOS team
@pawitp for patches
@GhsR for updated device and kernel tree
@omi for feedbacks and testing
XDA:DevDB Information
LineageOS 14.1, ROM for the Samsung Galaxy Grand duos, ROM for the Samsung Galaxy Grand Duos i9082
Contributors
osas514
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 4.2.2
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2018-03-27
Created 2017-01-23
Last Updated 2018-03-27
CHANGELOG
Changelog
20170122:
- Initial alpha release
20170130
-Upstream merge
20170226
Based on android 7.1.1_r21
February security patches merged in
Updated CM source
For more changes, track github or gerrit
2017-03-20
Based on android-7.1.1_r25
March security patches merged in
Updated Los source
2017-05-08
Based on android-7.1.2_r8
May Security patches merged in
2017-05-21
Fixed portable hotspot (should be working now)
Black status bar fixed by default
2017-06-06
Added zram support
Upstream merge
2017-06-07
Based on android-7.1.2_r17
June Security patches merged in
2017-07-18
Based on android-7.1.2_r24
July security patches merged in
2017-08-15
Based on android-7.1.2_r29
August security patches merged in
2017-09-14
Fixed blank screenshot and recents app thumbnails. Credits to @saayuj98 for the info and @minkon for testing and confirmation
Revert low ram config flag
2017-10-25
October security patches merged in
Revert low ram config flag
2018-01-25
January security patches merged in
Revert zram(graphics glitches)
Fixed random reboots caused by screenshot and thumbnail fix(hopefully)
2018-03-27
March security patches merged in
Revert screenshot flag(no idea why it's still rebooting)
FAQ
FAQ
Q:Is this rom better than rom A or B?
A: Either use it or gtfo
Q:How to enable root access*
A:Goto settings-about device and tap on build number 7 times to enable developer option.. Goto developer option Root access and select apps and adb
Q: When will the bugs be fixed
A: No ETA
Q: Recommended gapps?
A: Open gapps(pico)
Q:Since screenshot are blank with the default key combo how can i take screenshot?*
A: use this app
Q: Screenshot of rom?
A: Check the screenshot tab on this thread
Awesome! Thanks for all your work, to everyone who involved in this.
INGLÊS
I was expecting a lot of this update, I had seen a short time in the android file host, until I found it strange that you have put the dowload there and have not made a post for it. pardon my English.
Thank you so much dev. I'm still using LOS 13 but soon i will use this
VitorFelipe_Br said:
INGLÊS
I was expecting a lot of this update, I had seen a short time in the android file host, until I found it strange that you have put the dowload there and have not made a post for it. pardon my English.
Click to expand...
Click to collapse
Previous 2 builds have camera and video recording issue and i wanted to fix it before making it available on xda. The last build is fine without the video recording issue and your English is fine.
Thank you •OP• for being our Grand Duos Developer.....All Grand Devs doing their best and bring a new ROMs for us. We appreciate that. :fingers-crossed:
GREAT
Good Job Broo...
ty
In the previous builds I have noticed that play store is showing our device as uncertified device check in the play store settings is it showing the same for this build
USB Tethering and Hotspot Portable
still error, please fix if you have free time, thanks for make this great rom
Awesome work bro??
mantap25 said:
still error, please fix if you have free time, thanks for make this great rom
Click to expand...
Click to collapse
Error?
Great work brother
long live grand
omi9082 said:
Error?
Click to expand...
Click to collapse
yup, i don't have wifi on my home, so i use my phone as wifi hotspot
Thank you so so so much for your hard work @osas514 I was so excited to use this ROM
Sent from my GT-I9082 using XDA-Developers Legacy app
Excellent
Although late to the party... But have been testing all your previous versions and 22nd onward on this build only... as a daily driver...
Haven't faced any issues till now in my kind of daily usage... battery back up is pretty decent... For bugs... Not came across any till now... Thanks dear..:good:
can't download using chrome, it say error due to missing sd card. any fix?
Kursem said:
can't download using chrome, it say error due to missing sd card. any fix?
Click to expand...
Click to collapse
It is listed in known issues.
Fix:
* Allow storage permission in Chrome
* Exit Chrome and clear it from recent app list
* Then open Chrome again and download files
555-0134 said:
It is listed in known issues.
Fix:
* Allow storage permission in Chrome
* Exit Chrome and clear it from recent app list
* Then open Chrome again and download files
Click to expand...
Click to collapse
Whoops, didn't realize that's how you fix it. Thanks, though!

[ROM][7.1.2][OFFICIAL] LineageOS 14.1 - SM-T217S

LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.​
{
"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.
*
* 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 14.1 builds for lt02ltespr (SM-T217S). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Official Sprint Build
Older builds
4/13/17 Sprint Build
4/10/17 Sprint Build
4/8/17 Sprint Build
Addon su
su binary is not included in the ROM, you have to flash it manually after
addon su (choose arm)
Google Apps:
Mind The gapps 7.1.2
or
Open Gapps
Kernel
android_kernel_samsung_msm8930-common
My local manifest:
local_manifest
@aytex (He made all of the banners on this post)
@arco68 (For his work on the Galaxy S4 Mini)
@DarkFrenzy (I used his work as a reference to get some of the device specific fixes)​
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T217S, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
deadman96385, flashalot
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2017-04-09
Last Updated 2017-04-08
You tell me
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
Changelog:
4/13/17
Fixed the camera Thanks @DarkFrenzy
Removed unused drm blobs
Updated the time_daemon from shamu
4/10/17
Fixed glitchy power off animation Thanks @DarkFrenzy
Removed button backlight settings (They are unsupported)
Lowered the first boot time by enabling dexpreopt (The zip is a bit bigger but the old boot time was just unacceptable in my eyes)
Enabled some core system files to stay in ram so things should be a bit smoother.
Fixed adb not working unless you had selected mtp as the usb type
4/8/17
Initial release
I have redone the device trees from scratch based off of the galaxy s4 mini trees. @DarkFrenzy did the same thing awhile ago but he did not keep the history so it was useless to me. I also wanted to redo it because it lets me understand it better. My end goal is for it to become official but for that i have to fix the camera. But i have already upstreamed the kernel commits into the LineageOS msm8930-common kernel.
Thanks for still supporting our T217S. I'll give it shot and report.
deadman96385 said:
I have redone the device trees from scratch based off of the galaxy s4 mini trees. @DarkFrenzy did the same thing awhile ago but he did not keep the history so it was useless to me. I also wanted to redo it because it lets me understand it better. My end goal is for it to become official but for that i have to fix the camera. But i have already upstreamed the kernel commits into the LineageOS msm8930-common kernel.
Click to expand...
Click to collapse
Thanks for the Support for this device.
The camera is working fine in my RR build which I built with latest changes from Serrano tree which has some libc fix for camera.
For screen bug you have to set animate to true in device Samsung qcom repo like this https://github.com/FaArIsH/android_...mmit/51f24a5eed4203356c6669614f4dcbe979d74cc4
Yes its better to start from scratch then using my trees I m very lazy to use github that's y I don't use it the best way.
And also its best to give credits to @arco68 instead of me.
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
Thanks for the Support for this device.
The camera is working fine in my RR build which I built with latest changes from Serrano tree which has some libc fix for camera.
For screen bug you have to set animate to true in device Samsung qcom repo like this https://github.com/FaArIsH/android_...mmit/51f24a5eed4203356c6669614f4dcbe979d74cc4
Yes its better to start from scratch then using my trees I m very lazy to use github that's y I don't use it the best way.
And also its best to give credits to @arco68 instead of me.
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
My trees are based on the latest serrano tree's i am not sure why the camera does not work. Thanks for the suggestion on the screen bug the next build will have it i merged in the samsung qcom repo.
New build in OP
Changelog:
Fixed glitchy power off animation Thanks @DarkFrenzy
Removed button backlight settings (They are unsupported)
Lowered the first boot time by enabling dexpreopt (The zip is a bit bigger but the old boot time was just unacceptable in my eyes)
Enabled some core system files to stay in ram so things should be a bit smoother.
Fixed adb not working unless you had selected mtp as the usb type
Thank you!! I'll be watching to see how this pans out.
New build in OP
4/13/17 build
Fixed the camera Thanks @DarkFrenzy
Removed unused drm blobs
Updated the time_daemon from shamu
I spoke too soon, when I wake it up from sleep the backlight is off.
New update in OP
This unoffical thread will now be for test builds that i deem stable so the community can test them before i merge the changes into the "stable" lineage builds.
Changelog:
Removed more unused drm blobs
Fixed backlight issues (Reverted back to the original liblights)
Update prima wlan firmware (This should fix 5ghz wifi let me know though i do not have one)
I am having a problem that everytime I try to install is comes up with error 7 and doesnt do anything in twrp.
Update:
Looks like I needed older version of twrp. It flashed waiting on bootup
Another problem, when doing the setup at first boot up I select new device and it crashes the wizard. I cant get past the wizard at all.
Azrael.arach said:
Another problem, when doing the setup at first boot up I select new device and it crashes the wizard. I cant get past the wizard at all.
Click to expand...
Click to collapse
Use the gapps from this post rather than OpenGapps.
Hello! Is there a way to port this over to SM-T210(R) and if so, could anyone give me resources and tips to help this project?
Thanks!
TrendingTech said:
Hello! Is there a way to port this over to SM-T210(R) and if so, could anyone give me resources and tips to help this project?
Thanks!
Click to expand...
Click to collapse
No sadly the other variants of this tablet use a different cpu/gpu so a direct port is not possible
Is it safe to flash the wifionly.zip file onto this image so I can remove the annoying Sprint messages (I have no intention of ever using the mobile functionality)?
zerbey said:
Is it safe to flash the wifionly.zip file onto this image so I can remove the annoying Sprint messages (I have no intention of ever using the mobile functionality)?
Click to expand...
Click to collapse
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
DarkFrenzy said:
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
Thanks, for now I'll just keep it in Airplane mode with only WiFi enabled.
Sent from my ONEPLUS A3000 using Tapatalk
DarkFrenzy said:
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
I would like to know this buildprop setting. Thanks!

[ROM][A5|7 2017][13] LineageOS 20 Unofficial

LineageOS 20 Unofficial for Galaxy A5|7 2017
{
"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 13 (t), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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.​
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Hardware composer
OpenMAX (hardware encoding/decoding)
Camera (photos + recording)
NFC
Sensors
Vibration
Double tap to wake
Always on display
What's broken?
FDE (full disk encryption) has been fully deprecated in android 13
Network traffic monitoring
Sepolicy is permissive
Supported variants
All variants of Galaxy A5 (2017) and Galaxy A7 (2017). Dual SIM is also supported.
How to install
Make sure you had Samsung's Oreo firmware bootloader and modem before installing this.
Make sure you are using the latest official TWRP version.
Download the lineage build and optionally google apps.
In TWRP format data (if you still have stock rom encryption).
In TWRP wipe data and cache.
Flash LineageOS.
Optional: Flash Google apps (rightafter).
Reboot.
It's okay to dirty flash new updates.
Downloads
MEGA | google drive | androidfilehost | google apps | changelog
Old builds:
Lineage 19.1 Unofficial: MEGA | androidfilehost | google drive | changelog | sources
Donations
If you find the work I do helpful, you can support me by donating via this link.
Telegram
There's a telegram group made by A5|7 users where we hang out. Feel free to check it out.
Credits
Huge thanks to (a lot of people):
RaymanFX for the original work on lineage 14.1 and thus making this possible.
Forkbomb for contribution to original 14.1 sources.
Simon1511 for contributing to these devices via patches uploaded to lineageos gerrit.
Stricted, Danwood76, Fcuzzocrea, Ivan Meler and others for contribution to exynos platform.
SGTPresticle, Jmackley, Simon1511, Arno and others for doing the testing.
LineageOS Team
Me, for the infinite hours spent on this project.
Kernel source: https://github.com/filiprrs/android_kernel_samsung_universal7880
ROM OS Version: Android 13
ROM Kernel: Linux 3.18.140
ROM Firmware Required: Samsung oreo firmware
Created 2022-11-12
FAQ
Help my sim doesn't work
Please read the installation instructions more carefully. Oreo firmware bootloader and modem is a must.
You can find the collection along with the guide in this xda thread.
I'm sometimes having crackling sound when listening to music
Turn off 'ok google now' functionality in google app settings. If you have troubles finding it you can as well go to settings>apps, find app called 'google' and disable microphone permission.
Does this rom support VoLTE?
No. And it likely won't in the near future. Samsung's exynos VoLTE implementation is proprietary and non-standard. It is not possible on AOSP based roms for the time being.
I have weird issues with camera (wrong resolution, issues with flash etc.)
Тhis could very well be an issue with the included camera app. Try a third party camera app.
Will you fix the bugs? Will this version ever go official?
I've already fixed everything I was able to. The main drawback is that our linux kernel 3.18 has become too old. Our devices starting showing their age. Because of this version will not go official.
My hardware keys light up whenever I touch the screen
Navigate to Settings->System->Buttons->Backlight and tick 'Illuminate buttons only when pressed'. You might want to reduce time on the scaler to 1 second, too.
How to switch to full screen gestures
1. Navigate to Settings->System->Buttons->Backlight and tick 'Enable on-screen nav bar'.
2. Navigate to Settings->System->Gestures->System navigation and tick 'Gesture navigation'.
I need help with google camera
Please see this xda post.
Help! I have problems with my bank app/my device is failing SafetyNet.
Try following this guide by Simon1511.
Nice to see this out, great work
Great job as always.
im glad there's still hope for a little bit of support for our rusty device
i know this is pretty ridiculous at this point but i really hope this become another galaxy s2 situation where despite how old the device is.. it still get more and more versions despite its age
Yea, but the S2 is more of a tinkerers device at this point, A5 is still usuable (at least on A11, broke my screen before I could test 12 :C)
Possible update with simple TWRP install (wo delete data) from 19.1 Unofficial? (I think yes.)
Very nice rom ....smoot and stable
Which one is better LineageOS 19 or LineageOS 20? Which one is more stable for daily use? Or is just LineageOS 18 stable enough for daily use for now?
How is the battery consumption?How is the camera?
schneitomee said:
Possible update with simple TWRP install (wo delete data) from 19.1 Unofficial? (I think yes.)
Click to expand...
Click to collapse
I also think yes, but no one has tested this already. Note that you would surely need to reflash the same gapps package you were using before right after the new version flash.
Bried said:
Which one is better LineageOS 19 or LineageOS 20? Which one is more stable for daily use? Or is just LineageOS 18 stable enough for daily use for now?
Click to expand...
Click to collapse
I can't tell this for certain. It totally depends on your usecase and preferences. There aren't any unresolved bugs coming from previous versions (other than mentioned). Some people say however that the rom runs slower than the previous versions, especially with gapps. For me personally it was still ok.
lord_wolf7 said:
How is the battery consumption?How is the camera?
Click to expand...
Click to collapse
Not worse than before with lineage at least. For what it's worth, there is actually a new lineage camera app now. And we were getting some good battery life results during the testing.
thanks for the update.
which gapps is recommended for los20
Option58 said:
I also think yes, but no one has tested this already. Note that you would surely need to reflash the same gapps package you were using before right after the new version flash.
I can't tell this for certain. It totally depends on your usecase and preferences. There aren't any unresolved bugs coming from previous versions (other than mentioned). Some people say however that the rom runs slower than the previous versions, especially with gapps. For me personally it was still ok.
Not worse than before with lineage at least. For what it's worth, there is actually a new lineage camera app now. And we were getting some good battery life results during the testing.
Click to expand...
Click to collapse
the gapps is not available for Android 13. Does it have Google apps?
Option58 said:
I also think yes, but no one has tested this already. Note that you would surely need to reflash the same gapps package you were using before right after the new version flash.
I can't tell this for certain. It totally depends on your usecase and preferences. There aren't any unresolved bugs coming from previous versions (other than mentioned). Some people say however that the rom runs slower than the previous versions, especially with gapps. For me personally it was still ok.
Not worse than before with lineage at least. For what it's worth, there is actually a new lineage camera app now. And we were getting some good battery life results during the testing.
Click to expand...
Click to collapse
What does Network traffic monitoring do? I switch off Mobile data and WIFI for many apps in the app settings. Without Network traffic monitoring, does it mean that separate app Mobile data and WIFI switching off will not work reliably? Or is it completely unrelated?
lord_wolf7 said:
the gapps is not available for Android 13. Does it have Google apps?
Click to expand...
Click to collapse
hodanli said:
thanks for the update.
which gapps is recommended for los20
Click to expand...
Click to collapse
I focused mainly on fixing rom bugs, so I haven't had much time to investigate the google apps situation.
But yeah they exist. They can be found using the link in the thread.
Flamegapps, Nikgapps and perhaps a several others are there for android 13 already.
Bried said:
What does Network traffic monitoring do? I switch off Mobile data and WIFI for many apps in the app settings. Without Network traffic monitoring, does it mean that separate app Mobile data and WIFI switching off will not work reliably? Or is it completely unrelated?
Click to expand...
Click to collapse
I believe that is unrelated. It is literally broken monitoring.
network monitor does not work
backup doesn't work properly
why is the battery mah 3600?
nikgapps go doesn't work properly
issues :
using qr scan notification panel causes settings to crash, HDCP checking causes minor lag, SRGB doesn't work , network monitor does not work, nikgapps go doesn't work properly, backup doesn't work properly

Categories

Resources