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.
*
*/
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.
These are last known stable builds from work done by qsnc. Latest commits do not work, so I have reverted them to last working point.
Download link : Blog
XDA:DevDB Information
[STABLE]CyanogenMod, ROM for the Sony Xperia ZR
Contributors
Daedroza, qsnc
Source Code: https://github.com/daedroza
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-06-29
Last Updated 2016-06-28
Reserved
Screen Shot?
Sent from my C6603 using Tapatalk
Yaaaa!!! I love you so much :3
Is it stable .any bug ???
Anyone help me
GApps?
Can anyone tell me , which GApps version would go with the ROM?
Up to now, I dont see any big issue in this rom and i think that may be more stable than RR 5.7
Eragon_Z said:
Can anyone tell me , which GApps version would go with the ROM?
Click to expand...
Click to collapse
Gapps 6.0 of course.
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
This rom is stable.I don't see any bugs or issues.But the main disadvantage is I can't use any sony apps.
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
So there won't be any official nightly release?
Thank you 2 friends
---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------
So sad if can not use camera sony @@
max26292 said:
Up to now, I dont see any big issue in this rom and i think that may be more stable than RR 5.7
Click to expand...
Click to collapse
Hi you.which recovery i can use to flash this rom ???
New Developmental kernel :
*Fixes cpu/vfp_bounce
*Added a lot of new features using qsnc commits
*Under progress.
Flash over using TWRP. This requires heavy testing. Let me know of any issues!
---EDIT---
New kernel available : merging_july_04_dogo
Please don't use kernel_july_04_2016 it is outdated
*Added new cherry-picked commits
*Fixed alarm bug!
Did not try the updated kernel yet, but the kernel from the Jun 29 build (Linux version 3.4.112-cm-g6392ba2 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Jun 29 23:05:25 IST 2016) has some significant memory leak — the KernelStack value in /proc/meminfo increases until the system becomes completely unresponsive due to kernel running out of low memory.
Some logs taken just before the hang: View attachment 20160705-KernelStack-leak-hang.7z
shell.log is the output of some commands executed in adb shell — see "KernelStack: 393008 kB" there.
After pulling the battery I noticed that KernelStack slowly increases even when not doing anything with the phone, and pressing the power button to turn the screen on and back off eats 150-250 kB of KernelStack. Logs taken when doing this: View attachment 20160705-KernelStack-leak-2.7z
Going to flash the development kernel now.
Update: Flashed merging_july_4_dogo.zip, and apparently there is no KernelStack memory leak issue there — after some minutes KernelStack stabilized around 7336 kB, and its value does not keep increasing when turning the screen on and back off.
sigprof said:
Did not try the updated kernel yet, but the kernel from the Jun 29 build (Linux version 3.4.112-cm-g6392ba2 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Jun 29 23:05:25 IST 2016) has some significant memory leak — the KernelStack value in /proc/meminfo increases until the system becomes completely unresponsive due to kernel running out of low memory.
Some logs taken just before the hang: View attachment 3803646
shell.log is the output of some commands executed in adb shell — see "KernelStack: 393008 kB" there.
After pulling the battery I noticed that KernelStack slowly increases even when not doing anything with the phone, and pressing the power button to turn the screen on and back off eats 150-250 kB of KernelStack. Logs taken when doing this: View attachment 3803647
Going to flash the development kernel now.
Update: Flashed merging_july_4_dogo.zip, and apparently there is no KernelStack memory leak issue there — after some minutes KernelStack stabilized around 7336 kB, and its value does not keep increasing when turning the screen on and back off.
Click to expand...
Click to collapse
That's the problem with my stable branch. But it is the only point where my kernel and ROM boots up. I had merged all my new commits into a very fresh build along with qsnc's latest updates. The problem with this newly baked build is that never goes beyond "Starting Apps" logo.
I wasn't able to get logs or any such stuff and not to mention adb wasn't started even after kernel booted when I attempted this. Perhaps, I can again make a fresh build and with your expertise you could possibly get me logs in any way I could follow up the matter, try a little fix by myself or run it against other developers.
Let me know if you're up for testing @sigprof, Personally message/report if interested we could do a hangout on G+
My current kernel branch already includes qsnc's work + some additional commits and is way ahead of CM's original apq8064! All thanks to qnsc!
Daedroza said:
I wasn't able to get logs or any such stuff and not to mention adb wasn't started even after kernel booted when I attempted this.
Click to expand...
Click to collapse
Enabling adb during boot requires setting these properties in default.prop inside the ramdisk:
Code:
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
You can patch boot.img as follows:
Code:
abootimg -x boot.img
mkdir -p initrd && zcat initrd.img | ( cd initrd && cpio -idm --no-absolute-filenames; )
mkdir -p ramdisk && cat initrd/sbin/ramdisk.cpio | ( cd ramdisk && cpio -idm --no-absolute-filenames; )
sed -e 's/^\(ro\.adb\.secure\)=.*$/\1=0/' -e 's/^\(persist\.sys\.usb\.config\)=.*$/\1=mtp,adb/' -i ramdisk/default.prop
( cd ramdisk && find -mindepth 1 -print0 | cpio -o0 -H newc -R 0:0 ) > initrd/sbin/ramdisk.cpio
( cd initrd && find -mindepth 1 -print0 | cpio -o0 -H newc -R 0:0 ) | gzip -9 > initrd-new.img
abootimg --create boot-new.img -f bootimg.cfg -k zImage -r initrd-new.img
Then use fastboot flash boot boot-new.img to flash the patched image. Most adb commands (including "adb logcat") should be available immediately after the SONY logo disappears (if you are rebooting from recovery, do not start "adb logcat" too early, because the recovery also includes adbd).
New update (July 09, 2016) :
*Switch to audio: switch to new msm8960 HAL
*Lots of init updates, mpdecision updates from qsnc
*Additional Commits for kernel including Alarm fix
*Remove some bloated software
*July 05 Security Patch
Download link in OP
I've been using this ROM with included kernel for a day already. So far without any problems.
However, I have noticed a small bug - there are no any indicators for WiFi or mobile data activity in the status bar. I'm not sure if this is a normal behavior or a bug?
Thanks @Daedroza and @sigprof!
LaudaDev said:
I've been using this ROM with included kernel for a day already. So far without any problems.
However, I have noticed a small bug - there are no any indicators for WiFi or mobile data activity in the status bar. I'm not sure if this is a normal behavior or a bug?
Click to expand...
Click to collapse
It happend to me too.
Solution: Flash gapps (latest pico opengapps) without factory reset.
Sent from my Xperia ZR using XDA-Developers mobile app
vanbroekhoven.wim said:
It happend to me too.
Solution: Flash gapps (latest pico opengapps) without factory reset.
Sent from my Xperia ZR using XDA-Developers mobile app
Click to expand...
Click to collapse
I have already flashed gapps pico after flashing CM13 ROM.
Should I do it again?
Related
(Series 5 Release 3)
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
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.
*
*/
http://www.cmxlog.com/12
Before you install make sure to do a factory reset. First boot after install can leave your device at a black screen for up to 5 minutes. Be patient.
Downloads
Mod edit, download links removed, project has been abandoned.
Source code
* CyanogenMod
https://github.com/CyanogenMod
* Device specific repos
https://github.com/eousphoros/android_device_samsung_klimtwifi.git
Credits:
@crpalmer for his work porting cm12 to the picassowifi. It was of great help getting cm12 on the sm t700
@Barracuda77777 for his kernel loving (Series 1)
@nvertigo67 && @UpInTheAir for their kernel magic and misc fixes (Series 2)
Unofficial Build instructions
Code:
# [ -e /usr/lib/apt/methods/https ] || {
apt-get update
apt-get install apt-transport-https
}
# apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
# sh -c "echo deb https://get.docker.com/ubuntu docker main\
> /etc/apt/sources.list.d/docker.list"
# apt-get update
# apt-get install lxc-docker
# git clone https://github.com/stucki/docker-cyanogenmod.git
# cd docker-cyanogenmod
# ./run.sh
# repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
# repo sync
# source build/envsetup.sh
# breakfast klimtwifi
// you will need to extract the binary blobs from your device
# brunch klimtwifi 2> errors
eousphoros said:
(Release 1)
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
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.
*
*/
What works:
Very early build, expect there to be issues
Before you install make sure to do a factory reset
Downloads
SM-T700:
Cyanogenmod 12: https://blck.io/cm-12-20141206-UNOFFICIAL-klimtwifi.zip
CWM Recovery: https://blck.io/cwm-20140806-UNOFFICIAL-klimtwifi.img
Source code
* CyanogenMod
https://github.com/CyanogenMod
* Device specific repos
https://github.com/eousphoros/android_device_samsung_klimtwifi.git
Click to expand...
Click to collapse
What are the differences between CM11 and CM12?
Very cool. Looking forward to giving this a run. Thanks heaps.
jewnersey said:
Very cool. Looking forward to giving this a run. Thanks heaps.
Click to expand...
Click to collapse
Downloading now! Fantastic work mate!
Downloaded and flashed this. Booted up fine and am going through the set up process. So far so good
Edit: First thing I have noticed is the camera view is turned sideways. Wifi works with no issues
It won't let me get to the setup process, keeps saying "Unfortunately set up wizard has stopped".
interfreak said:
It won't let me get to the setup process, keeps saying "Unfortunately set up wizard has stopped".
Click to expand...
Click to collapse
I flashed with TWRP and made sure I wiped the data also
So did I, but I'll try again.
How do you manually boot into TWRP?
*edit* worked it out lol
This is really good news. I'm tempted to download and test it out on my SM-T705, even if the 4G modem doesn't work because well, why not? I'd love to try Lollipop goodness on my tab!
I'm sure once we crack the modem business we can make a unified ROM that works on both devices. So if you have a T700, you flash this ROM, it'll use only WiFi, if you have a T705, you flash this, and it'll be able to use both LTE and WiFi.
From my limited knowledge, the only differences is the T705 has a Intel (?) modem chip that requires a driver in the kernel, plus the Radio I/O Layer.
Nope, won't load at all for me
maybe try cwm, it is what I used.
Great...I've tried to download the official firmware and flash with ODIN...Now it's stuck at the Samsung logo lol.
*edit*
Got it to boot!, Will try to flash with CWM...
---------- Post added at 02:27 PM ---------- Previous post was at 01:30 PM ----------
GREAT.
Installed a factory ROM, and now I can't root...
http://forum.xda-developers.com/galaxy-tab-s/help/root-sm-t700-t2963954
Amazing job! Thanks for doing this.
Awesome job! Thanks for all your hard work.:good:
OK, got it to install finally lol!
First off, fantastic job eousphoros!!! You're the first to put Lollipop on the Galaxy Tab S.
Now, this is obviously a *very* early build, so for those that want to try it I say go ahead - but there are a lot of bugs to be ironed out yet.
Can't wait to see this developed!!
As for cm11, can I also flah this one on T705?
Can't seem to download cwm from the link provided in the op. It opens a page full of words and has no option to download
hassan_1000 said:
Can't seem to download cwm from the link provided in the op. It opens a page full of words and has no option to download
Click to expand...
Click to collapse
right click and save as (or save link as).
Gapps are included? Or should i download one? Which one?
edit: Ok, I got it.
Great job, euosphoros! I'm waiting for updates and the stable version in future. ROM has a few bugs for example funny camera , not working recent apps button (I have to use screen buttons) but I know... it is first version of the ROM.
Can someone upload cwm to drive or mega or something as i don't have access to a laptop atm, unless someone can confirm it works with twrp
Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy Grand Prime SM-S920L | SM-G530MU | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
ROM Status: Stable
ROM OS: LineageOS 13.0
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: https://bugs.msm8916.com/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
Click to expand...
Click to collapse
Download
All builds: https://download.msm8916.com/
Jenkins Builds: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_GRAND_Prime/
TWRP Builds: https://jenkins.msm8916.com/job/TWRP_Builds/
GApps: http://opengapps.org/?arch=arm&variant=micro&api=6.0
RSS: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_GRAND_Prime/rssLatest
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Features
Code:
* The usual LineageOS features.
* All builds support over-the-air updates.
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding
XDA:DevDB Information
[UNOFFICIAL][ROM] LineageOS 13.0 for Galaxy Grand Prime [SM-S920L|G530FZ/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime
Contributors
vince2678, minz1
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 4.4 (KitKat)
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-03-27
Created 2016-11-01
Last Updated 2017-08-29
Reserved
Changelog
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] In-call audio should now work fully without having to
toggle the loudspeaker. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should be fully functional [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Vibration should be working for SM-G530MU. The kernel
config now specifies the correct vibration driver. [/B]
Code:
[B][U]14/04/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built into the kernel. Should
(slightly) improve speed of enabling/disabling wifi. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.14[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Updated RIL in-call audio fix, microphone should now
work proper after the regression from last build.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] There have been several other changes as well,
mostly to the underlying structure of the kernel and device trees.[/B]
Code:
[B][U]07/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The 2-ring bug should be fixed for the SM-S920L [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Accelerometer and magnetic sensor (compass) should
be working proper on SM-S920L [/B]
Code:
[B][U]04/04/2017[/U][/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] NFC should be work for SM-G530MU as well
as SM-S920L (after today's builds). [/B]
Code:
[B][U]26/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530FZ builds are working. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU builds are working. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Brightness control now works for SM-G530FZ. [/B]
Code:
[B][U]12/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530FZ builds are working [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU builds are still WIP [/B]
Code:
[B][U]12/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Unified SM-G530P.[/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Built TWRP 3.1.x for all devices.[/B]
Code:
[B][U]09/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] SM-S920L builds should be working now.[/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU and G530FZ builds are still WIP [/B]
Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added device S920L [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Unified the T/T1/W into one image. They are essentially the same device.
This should simplify development on my part and make it easier for everyone to
get the updates. And I can also be absolutely sure about bugs
since we'll be using the same image. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high, and could quickly
kill power on mobile devices. Lowering to 200Mhz should significantly extend batery life
on the stock scheduler. [/B]
Code:
[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]
There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.
Code:
[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]
Code:
[B][U]25/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added G530MU [/B]
Code:
[B][U]25/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed sources to LineageOS [/B]
Code:
[B][U]17/01/2017[/U][/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed. [/B]
Code:
[B][U]16/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Removed ViperFX [/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Screen timeout bug should be fixed [/B]
Code:
[B][U]07/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added Snap Camera [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Disabled engineering mode. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Minor kernel tweaks. [/B]
Code:
[B][U]05/01/2017[/U][/B]
*[B][[COLOR="Blue"]FIXED[/COLOR]][/B][B] Audio should be fixed across all devices on the latest builds. [/B]
*[B][[COLOR="Blue"]FIXED[/COLOR]][/B][B] Device and app hanging/crashing should be fixed as well. [/B]
*[B][[COLOR="Blue"]FIXED[/COLOR]][/B][B] SD storage should be detected and mounted properly. [/B]
Code:
[B][U]04/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] First alpha builds made. All alpha builds are set to engineering mode by default.[/B]
Code:
[B][U]02/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added SM-G530P device [/B]
[B][U]01/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Brought up kernel code [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Built TWRP 3.0.x images for all devices [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] built cm-13.0 image for SM-G530W [/B]
Code:
[B][U]01/11/2016[/U][/B]
* [B] [ [COLOR="Red"]ALL[/COLOR] ][/B] [B] Created DevDB project [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None. [/B]
Reserved
i am very very glad to see this!! i will be willing to test out builds for sure
Ohhh @vince2678 you are the best !!! I test for the FZ
Sent from my SM-G530FZ using XDA-Developers mobile app
Is it OK to downgrade from CM 14? I will replace recovery and wipe everything.
when it will be available .... I only found cm12.1
thanks to the work done
SnuffyRus said:
Is it OK to downgrade from CM 14? I will replace recovery and wipe everything.
Click to expand...
Click to collapse
you shouldn't right now since the CM-13 Images aren't uploaded yet or in other words, don't downgrade until they are uploaded, then you can downgrade
melc70 said:
when it will be available .... I only found cm12.1
thanks to the work done
Click to expand...
Click to collapse
If you go to his FAQ, he answers your question [emoji3]
Sent from my SM-G530W using XDA-Developers mobile app
joe_5579 said:
If you go to his FAQ, he answers your question [emoji3]
Sent from my SM-G530W using XDA-Developers mobile app
Click to expand...
Click to collapse
How do I get to his FAQ?
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
joe_5579 said:
you shouldn't right now since the CM-13 Images aren't uploaded yet or in other words, don't downgrade until they are uploaded, then you can downgrade
Click to expand...
Click to collapse
Ore you one of the ones helping to get booting cm13 images?I am hoping to have at least a testing build for my sm-g530t1 by January/February
jdoggawesomex900 said:
How do I get to his FAQ?
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
Ore you one of the ones helping to get booting cm13 images?I am hoping to have at least a testing build for my sm-g530t1 by January/February
Click to expand...
Click to collapse
No, I am not a helper of this ROM xD but hopefully we see something before then, but we also need to give him time too, and here, this is exactly what he said: "Whenever I have the time to actually fix any issues and get an image booting. The time will vary depending on various factors ( my mood, how much homework I have, how well fed I am, etc.. )"
Nice Vince ! I will Help you as CM12.1 ! thanks for your work !
As I can see main concern goes for building sm-g530w builds right now which apparently is the only one with a booting cm13 image right now
jdoggawesomex900 said:
As I can see main concern goes for building sm-g530w builds right now which apparently is the only one with a booting cm13 image right now
Click to expand...
Click to collapse
It bootloops.
Sent from My SM-G530W using XDA Developers app
Okay guys.They are making new cm 12.1 builds for all devices as we speak do still cm 12.1 .Soon after cm13 images will start.
jdoggawesomex900 said:
Okay guys.They are making new cm 12.1 builds for all devices as we speak do still cm 12.1 .Soon after cm13 images will start.
Click to expand...
Click to collapse
Yep, we are fixing small bugs on cm12.1, doing final builds and preparing the environment for the cm13, also we are improving the telegram channel and other things. Give us time
kentone said:
Yep, we are fixing small bugs on cm12.1, doing final builds and preparing the environment for the cm13, also we are improving the telegram channel and other things. Give us time
Click to expand...
Click to collapse
Very hyped and looking forward to this, Thank you all maintainers[emoji85] [emoji91]
Sent from My SM-G530W using XDA Developers app
kentone said:
Yep, we are fixing small bugs on cm12.1, doing final builds and preparing the environment for the cm13, also we are improving the telegram channel and other things. Give us time :good:
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
I am happy!This will be the first marshmallow rom for my device!
Click to expand...
Click to collapse
litte question: what are the advantages from cm13?
I know it's better and I want it to but I don't know the advantages
Sent from my SM-G530FZ using XDA-Developers mobile app
leoon0 said:
litte question: what are the advantages from cm13
I know it's better and I want it to but I don't know the advantages
Sent from my SM-G530FZ using XDA-Developers mobile app
Click to expand...
Click to collapse
All this: https://www.androidpit.com/android-m-release-date-news-features-name
plus this cyanogen spice: http://www.cyanogenmod.org/blog/cm-13-0-release-1
and maybe some more small features not listed here
Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy Grand Prime SM-S920L | SM-G530MU | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
ROM Status: Stable
ROM OS: LineageOS 14.1
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/Samsung_MSM89XX
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: https://bugs.msm8916.com/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
Click to expand...
Click to collapse
Download
All builds: https://download.msm8916.com/
Jenkins Builds: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_GRAND_Prime/
TWRP Builds: https://jenkins.msm8916.com/job/TWRP_Builds/
GApps: http://opengapps.org/?arch=arm&variant=micro&api=7.1
RSS: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_GRAND_Prime/rssLatest
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Changelog
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]22/08/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] SM-G530MU and SM-S920L builds now boot [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability to build
it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] In-call audio should now work fully without having to
toggle the loudspeaker. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Vibration should be working for SM-G530MU. The kernel
config now specifies the correct vibration driver. [/B]
Code:
[B][U]14/04/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built into the kernel. Should
(slightly) improve speed of enabling/disabling wifi. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.14[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Updated RIL in-call audio fix, microphone should now
work proper after the regression from last build.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] There have been several other changes as well,
mostly to the underlying structure of the kernel and device trees.[/B]
Code:
[B][U]01/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] LineageOS updater can reboot to recovery properly.[/B]
Code:
[B][U]30/03/2017[/U][/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B]Data and SMS should be functional on all devices.
You may need to set APN settings again and reboot for data to work.[/B]
Code:
[B][U]28/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B]Added SM-G530MU.[/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B]Data and in-call audio should be functional
on all devices.[/B]
Code:
[B][U]26/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B]SM-G530FZ builds *should* be functional.[/B]
Code:
[B][U]09/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added SM-G530FZ.[/B]
* [B][[COLOR="Red"]FIXED[/COLOR]][/B] [B] Rear camera view in Snap camera was distorted. Now fixed. [/B]
Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Unified the T/T1/W into one image. They are essentially the same device.
This should simplify development on my part and make it easier for everyone to
get the updates. And I can also be absolutely sure about bugs
since we'll be using the same image. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high,
and could quickly cook your phone and kill power on mobile devices.
Lowering to 200Mhz should significantly extend batery life
on the stock scheduler. [/B]
There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.
Code:
[B][U]12/01/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Bluetooth is now working across all builds. [/B]
Code:
[B][U]12/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] First images built. [/B]
Code:
[B][U]11/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Finished merging Qualcomm (CAF) LA.BR.1.2.9_rb1.11 kernel into device kernel. [/B]
Code:
[B][U]10/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored the project repositories. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Migrated repositories to new GitHub page. [/B]
Code:
[B][U]20/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Made some substantial changes to our build infrastructure,
which should make my life substantially easier and
using Jenkins and all a more pleasant experience. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None[/B]
Features
Code:
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding
XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS 14.1 for Grand Prime [SM-S920L|G530MU/FZ/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime
Contributors
kentone, vince2678
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 4.4 (KitKat)
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-06-08
Created 2017-01-11
Last Updated 2018-08-10
Reserved
Great Share ✌ But not for people who have smg531f device I cant buy you one xD instead i would buy a new.
Link to download cm 14?
biga1 said:
Link to download cm 14?
Click to expand...
Click to collapse
They are currently created and building the ROM. It should be out around next months or so. Hope you understand.
Slenderman8090 said:
They are currently created and building the ROM. It should be out around next months or so. Hope you understand.
Click to expand...
Click to collapse
No I don't understand. Please explain.
biga1 said:
No I don't understand. Please explain.
Click to expand...
Click to collapse
Biga1, as the Kernel code for Samsung is outdated somewhat. Nouget is created by hand for this device.
Slenderman8090 said:
Biga1, as the Kernel code for Samsung is outdated somewhat. Nouget is created by hand for this device.
Click to expand...
Click to collapse
OK. I saw the thread with download instructions and like an idiot searched for a link. My bad for reading the OP.
Why does it say 6.0 in the rom os version? Isnt this nougat lol
bassem763 said:
Why does it say 6.0 in the rom os version? Isnt this nougat lol
Click to expand...
Click to collapse
Generally, people do make mistakes. But yes, I agree that is misleading. Dev, if you are able to.. Please change OS Version to 7.0 Nougat.
Slenderman8090 said:
Generally, people do make mistakes. But yes, I agree that is misleading. Dev, if you are able to.. Please change OS Version to 7.0 Nougat.
Click to expand...
Click to collapse
Fixed.
Sorry for bugging but just a question are you guys going to change the sources from cm to lineage os or nah
bassem763 said:
Sorry for bugging but just a question are you guys going to change the sources from cm to lineage os or nah
Click to expand...
Click to collapse
The only difference for now between the two is in name, so no.
vince2678 said:
The only difference for now between the two is in name, so no.
Click to expand...
Click to collapse
True lol
CyanogenMod 14.1 is being uploaded for SM-G530W Currently. Estimated wait, around an hour or so.
UPDATE: SM-G530W has been uploaded and finished.
Fm Radio does not work on mine , getting error msg " FM operation failed. If the problem persists, pls turn off FM and turn it back on" . My Android version shows up as 6.0.1 . "CM version is 13.0-20170118-NIGHTLY-gprimeltetmo" > Could not install pico Gapps version 6.0 or 7.1 getting error that wrong version. So not sure if you have actually fixed the name change to reflect Nougat. Have an sm-g530t
shakazoid said:
Fm Radio does not work on mine , getting error msg " FM operation failed. If the problem persists, pls turn off FM and turn it back on" . My Android version shows up as 6.0.1 . "CM version is 13.0-20170118-NIGHTLY-gprimeltetmo" > Could not install pico Gapps version 6.0 or 7.1 getting error that wrong version. So not sure if you have actually fixed the name change to reflect Nougat. Have an sm-g530t
Click to expand...
Click to collapse
That's CyanogenMod 13.0 you're running there mate, not CYanogenMod 14.1. The only device for which a CM14.1 exists is the G530W at the moment. You'll be alerted when building starts for everything else.
Stuck on Samsung boot screen. Tried three downloads.
vince2678 said:
That's CyanogenMod 13.0 you're running there mate, not CYanogenMod 14.1. The only device for which a CM14.1 exists is the G530W at the moment. You'll be alerted when building starts for everything else.
Click to expand...
Click to collapse
Thanks for the response.
shakazoid said:
Thanks for the response.
Click to expand...
Click to collapse
Shakasoid, I will be announcing updates for various models once they are readily available.
Update: LineageOS 14.1 should be out within 3 weeks.
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 repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
KNOWN ISSUES
- Report with logs
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running Marshmallow bootloader
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://download.lineageos.org/onyx
Old Downloads :
https://github.com/ashwinr64/LineageOSUpdater-API/releases/
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/LineageOS/android_device_oneplus_onyx
Kernel: https://github.com/LineageOS/android_kernel_oneplus_onyx
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
HOW TO BUILD
- repo init -u ssh://[email protected]/LineageOS/android.git -b cm-14.1
- add local manifest to .repo/local_manifests/
- repo sync -j4
- . build/envsetup.sh
- brunch onyx
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_device_oneplus_onyx" path="device/oneplus/onyx" remote="github" />
<project name="LineageOS/android_kernel_oneplus_onyx" path="kernel/oneplus/onyx" remote="github" />
</manifest>
SUPPORT ME
Do you like my work? Consider donating me some beer!
XDA:DevDB Information
LineageOS, ROM for the OnePlus X
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2017-01-13
Last Updated 2017-01-27
Reserved
Changelog:
17/1:
-Synced with Lineage.
-Sneak peak of our new bootanimation ;P
-Fixed the string derp in Settings dashboard.
-Added support for automatic updates.
NOTE: I'll look into the incall audio very soon. Users need to flash superSU separately in order to have SU , we are planning on an addon SU release
.
10/1:
-Rolled back to old RIL stack , no more network instabilities
-Enabled SDcardfs
-WiFi hotspot fixed.
-No need to flash 3rd party kernels ( sorry for the delay guys,no network here,STILL :/ )
First!!
Going to flash it later today!
Edit- running smoothly with stock kernel and dynamic gapps!!
Hotspot working! And every thing else I tried.
One bug I guess(see ss ).
for me
Download queued ... Thank you
Edit: Finally get some LinOS logos, nice!
Super Machi
Sactgr said:
Going to flash it later today!
Edit- running smoothly with stock kernel and dynamic gapps!!
Hotspot working! And every thing else I tried.
One bug I guess(see ss ).
Click to expand...
Click to collapse
It isn't a bug but yeah will fix it in next build
@ashwin007 Thanks a lot Happy new year, btw!
Did you manually fix the kernel because other builds (Lineage and AICP) still require you to flash the kernel? Just asking out of curiosity.
I'm eager to see it here! Nicely done @ashwin007
BrokenBee said:
@ashwin007 Thanks a lot Happy new year, btw!
Did you manually fix the kernel because other builds (Lineage and AICP) still require you to flash the kernel? Just asking out of curiosity.
Click to expand...
Click to collapse
Must've fixed something as it's listed as fixed in the changelog.
The Bug that the preferred Sim changes after every reboot from Sim2 to Sim1 still persists.
Not official, but very close to what the first official weekly will be
The bugs i found out-
1.In call volume control for earpiece(speaker works fine)
2.Split screen size changing.
3.The file explorer
4.In the camera app the shutter sound option doesn't work.
Btw huge thanks to @ashwin007 to let us have a hands-on on possibly the best 7.1 rom till date.
Exciting!
Works fine so far!
Shall i flash arsenic kernal or not?
aryaraj said:
The bugs i found out-
1.In call volume control for earpiece(speaker works fine)
2.Split screen size changing.
3.The file explorer
4.In the camera app the shutter sound option doesn't work.
Btw huge thanks to @ashwin007 to let us have a hands-on on possibly the best 7.1 rom till date.
Click to expand...
Click to collapse
Have you tried the other LineageOS builds?
shyamalgarg said:
Shall i flash arsenic kernal or not?
Click to expand...
Click to collapse
Shall you or should you? You don't need to (see changelog).
can i dirty flash this over CM14.1-20161207-UNOFFICIAL Build?
Monitormann said:
can i dirty flash this over CM14.1-20161207-UNOFFICIAL Build?
Click to expand...
Click to collapse
I make it, and work fine, but in 20161222
Enviado desde mi ONE E1001
The ROM is perfect at least the way I use it. What I don't understand is why the signal strength fluctuates so much and drops off completely. It's not something I experienced in this ROM but in all nougat Roms. I'm getting a range of -90 to -109 dBm and I see the indicator drop off completely. I wonder if I may miss a call or text, if I initiate a call the indicator will jump up and once off call it drops off again. It something that is not present in OOS. (OOS avg. -70 to -90 dBm)
Hi everyone. I'm sharing my personal AOSP 8.0 & 8.1 builds here
The builds are compiled from official sonyxperia Repos with some Commits from Linage, Omnirom , AOSP master & open Pull Requests from sonyxperia Repos.
Kernel is built using latest sonyxperia sources.
* !!! ROM WILL BE CONTINUED BY FASTBOOTKING !!! '
Working:
* HSPDA
* LTE
* Camera
* Flash
* WiFi
* GPS
* Video playback
* Reboot to Recovery
* Gapps backup
Works most of the time:
* Fingerprint
Issues:
* Tell me
Unknown:
* VoLTE
* WiFi Calling
* WiFi Tethering (should work as i made no changes to it)
* BT Audio (No device to test it)
Downloads:
8.0:
Google Drive :
Build 1: https://goo.gl/ADa8nP
Build 2 : https://goo.gl/uwMiTD
Build 3: https://goo.gl/Kn7FXk
Build 4: https://goo.gl/Kn3Nuf
Build 5: https://goo.gl/ZhJDyJ
Androidfilehost:
Build 6: https://goo.gl/6S3qQK
Build 7: ----
Build 8: https://goo.gl/eeBmNB (with prebuilt oct kernel from sony)
Build 9: https://goo.gl/w7e8as
8.1
Build 1: https://goo.gl/FgG4xr
Build 2:Download from Sourceforge
Build 3:Download from Sourceforge
Build 4:Download from Sourceforge
Build 4.1:Download from Sourceforge
Build 5:Download from Sourceforge
Build 5.1:Download from Sourceforge
Build 6:Download from Sourceforge
Users of the 1. Build posted here on XDA need to do a clean flash!!!
Vendor files :
8.0
https://goo.gl/mtj9yQ
8.1
8.1 odm image
Latest Version: 11-03-2018
Starting with Build 4: Latest official Vendor image musst be flashed before rom flashing!!!!
Clean flash rom Zip with latest twrp.
after that every dirty flash saves the gapps state.
I'll push new builds after succesfull basic testing by myself
Rom-Source: https://github.com/SlimBit-AOSP
Kernel Source: https://github.com/sonyxperiadev/kernel & PR's from same repo & sometimes manual changes.
XDA:DevDB Information
[F8331][Oreo][11-03-2018] SlimBit-AOSP 8.1 Builds, ROM for the Sony Xperia XZ
Contributors
Bitti09, https://github.com/sonyxperiadev
Source Code: https://github.com/sonyxperiadev/kernel
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2017-10-07
Last Updated 2018-03-23
Reserved
Changelog:
8.0
Build 1:
Code:
* First public release
Build 2
Code:
* Default CPU Govenor set to OnDemand
* Testing qcom caf display commit for video fix
Build 3::
Code:
* Widevine DRM fix
* Display whitepoint calibration by kholk
* PR: Updated media codecs by alviteri @github
* Enabled AOSP Night light setting (experimental)
Build 4:
Code:
* New Wifi kernel parts
* Updated kernel with video fix
* App Replacements:
+ Camera -> SnapdragonCamera
+ Music -> SnapdragonMusic (with Snapdragon Audio+ Equalizer)
+ Gallery -> Snapdragon Gallery
Build 5
Code:
* Build from clean AOSP&sonyxperiadev repos without any PR
* some little things changed
Build 6
Code:
* Build from clean AOSP&sonyxperiadev repos without any PR
* some little things changed
Build 7
Code:
* Build from clean AOSP _r30&sonyxperiadev repos without any PR
* November AOSP Patch state.
Build 8
Code:
* merged PR's from older Builds.
Build 8
Code:
* night mode enabled.
* new FP behaviour:
fp scanner is inactive on screen off
gets activated after power button was pressed and display is on.
8.1
Build 1:
Code:
* First public release
Build 2:
Code:
* Fixed video lag
* Fixed gapps backup
* recent SODP changes merged
Build 3:
Code:
* Added native substratum support (no root needed)
Build 4:
Code:
* Kernel : Some tweaks
* Kernel: merged Usb Mtp fixes from sodp
* Device: Merged recent sodp changes
* Rom: Fixed Deskclock Alarm again
Build 4.1:
Ready for Vendor V10
Code:
* Kernel: Merged commits by @_LLJYY
* Camera: Merged partial commits from LA.UM.6.4.r1-06100-8x98.0 CAF-Tag
* Device: Merged recent sodp changes
* SODP: Merged recent changes
Build 5
Code:
* Rebased on Android 8.1 R14 -> Rom Patchset is now 05-02-2018 :D
* Cleaned up some useless/non working commits.
* Substratum commits updated.
* Merged SODP Changes.
* Some smaller things. :p
Build 5.1
Code:
* Bootloop fixed
Build 6.0
Code:
* Rebased onto March AOSP Update.
* Cleaned up Device& Kernel trees.
* Temp. removed Wireguard support
* Updated rootless Substratum commits
Discord Support Group: https://discord.gg/sRDkrfc
Works with dual sim f8332???
karrouma said:
Works with dual sim f8332???
Click to expand...
Click to collapse
i don't think so.
Bitti09 said:
i don't think so.
Click to expand...
Click to collapse
no patch or anything that change build and modem.
the patch from 7.1.1 works in 8?
karrouma said:
no patch or anything that change build and modem.
the patch from 7.1.1 works in 8?
Click to expand...
Click to collapse
I DON'T SUPPORT F8332 cause i DON'T own this device type. I only give support for the single sim Version aka F8331
Uploading 2. Build with video stuttering fix ( tested with several 1080p 60fps videos & 360° cardbord demos.)
Coming from my first build you don't need to flash gapps. Just dirty flash the rom and wipe cache & reboot
When you said flash vendor files before flash the rom you mean this?
* Extract SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.ext 4.zip
* Boot into TWRP
Code:
adb push SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.ext4.img /dev/block/mmcblk0p53
Cheers
juanpirulo said:
When you said flash vendor files before flash the rom you mean this?
* Extract SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.ext 4.zip
* Boot into TWRP
Code:
adb push SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.ext4.img /dev/block/mmcblk0p53
Cheers
Click to expand...
Click to collapse
yep
@Bitti09
just flashed your rom over CLShortFuse rom and it seems that google play and play service are missing.
ojessie said:
@Bitti09
just flashed your rom over CLShortFuse rom and it seems that google play and play service are missing.
Click to expand...
Click to collapse
you need to clean flash my rom to have the backup part installed.
Where i can download SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.ext 4.zip ?
EDIT: Finally i found it.
Play & Play service missing
@Bitti09
just installed your recenlty posted vendor img, did a clean install but play and play service is still missing.
ojessie said:
@Bitti09
just installed your recenlty posted vendor img, did a clean install but play and play service is still missing.
Click to expand...
Click to collapse
what gapps are you using? i've teted myself with official opengapps
Bitti09 said:
what gapps are you using? i've teted myself with official opengapps
Click to expand...
Click to collapse
Sorry, just recognized it by myself that I have to install gapps additionally (thought they are included) getting tired ... my bad. Sorry
Fingerprint not working for me, did not wipe /system though. should I have?
Looking forward to build with widevine fix
ratoune said:
Fingerprint not working for me, did not wipe /system though. should I have?
Looking forward to build with widevine fix
Click to expand...
Click to collapse
1. I've started with a clean flash aof build 1 and i've tested several builds today without any fp issues. even after reboot it still works.
2. i plan to push the new build in next couple of hours.
ratoune said:
Fingerprint not working for me, did not wipe /system though. should I have?
Looking forward to build with widevine fix
Click to expand...
Click to collapse
Just to confirm I had also the fingerprint problem. Started with a clean flash but with V2
ojessie said:
Just to confirm I had also the fingerprint problem. Started with a clean flash but with V2
Click to expand...
Click to collapse
fp problem still present? if yes provide logcats.
new build slightly delayed. forgot to revert a broken commit.
ojessie said:
Just to confirm I had also the fingerprint problem. Started with a clean flash but with V2
Click to expand...
Click to collapse
I had started by V2 with a "clean" flash but not wiping system.
I reflashed wiping /System /Cache /Data in TWRP and now FP is working like a charm.
ratoune said:
I had started by V2 with a "clean" flash but not wiping system.
I reflashed wiping /System /Cache /Data in TWRP and now FP is working like a charm.
Click to expand...
Click to collapse
:good:
EDIT: New build will be online whithin 24 hours.
Main changes are : widevine, fp update