[11-03-2016] [UNOFFICIAL] [UBER] AOSPB For Verizon G3 - Verizon LG G3

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.
*/
What is AOSP?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps.
Anyway to get a working system I added some changes from CodeAurora Forum and CyanogenMod. I added also 3 non-AOSP features for a better user experience (Advanced Reboot, "Clear All" button in Recents and an option to delete screenshots from the notification area) and I'm NOT going to add something other.
Features
Pure AOSP
It's pure AOSP (based on Slim and CAF)
Downloads
Latest Build
GAPPS (Please use the Micro GAPPS Package that's the one working properly)
Link To Download Folder
How To Install
1. Place ROM & Gapps in your SD Card
2. Reboot in Recovery Mode
3. Wipe Data/Factory Reset
4. Wipe Dalvik cache
5. Install the ROM zip
6. Install the GAPPS zip
7. Reboot
8. Profit
P.S: Huge shout out to Team M8 for making this possible, without them i am nothing.
XDA:DevDB Information
AOSPB For Verizon G3, ROM for the Verizon LG G3
Contributors
amirfida, PunkUnity
Source Code: https://github.com/AOSPB
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP + CAF + Some stuff from Slim
Version Information
Status: Testing
Created 2016-03-09
Last Updated 2016-03-11

News: AOSPB haven't updated their code from past couple of days so i won't compile until they update their source. Cheers

This is mine thanks download now

Because this is AOSP will android pay work?

Okay, here's whats not quite working right now
CaptainElwood said:
Because this is AOSP will android pay work?
Click to expand...
Click to collapse
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!

KShion619 said:
Okay, here's whats not quite working right now
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!
Click to expand...
Click to collapse
if you do find that commit please let me know, ill soon upload a new build

amirfida said:
if you do find that commit please let me know, ill soon upload a new build
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work

KShion619 said:
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work
Click to expand...
Click to collapse
hey thanks for that i really appreciate it, will mention you in credits for sure
waiting for the workaround, i never really use NFC so never knew that its not working, really appreciate your hard work
Edit: My build uses CM device trees so the file is already the same one, i am testing new build will release it soon
Edit 2: New build has been uploaded compiled with Uber Toolchain

Just curious will Layers themes work on this?

AngryManMLS said:
Just curious will Layers themes work on this?
Click to expand...
Click to collapse
nope it won't... Sorry

amirfida said:
nope it won't... Sorry
Click to expand...
Click to collapse
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.

AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
You are welcome

Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:

KShion619 said:
Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:
Click to expand...
Click to collapse
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again

amirfida said:
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again
Click to expand...
Click to collapse
yeah, im mainly referring to the CM vendor trees, im not quite sure if that matters

AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
In 6.0 rro was merged. Any aosp or slim rom on 6.0 will work with layers as long as it doesnt have cmte.

Related

[ROM][D852] CyanogenMod 12 UNOFFICIAL EXPERIMENTAL TEST BUILDS

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
THIS IS UNOFFICIAL EXPERIMENTAL BUILDS WHICH CONTAINS CODE TO BE TESTED BEFORE IT IS MERGED INTO CM.
IF YOU WANT OFFICIAL BUILDS THEN CHECK BACK IN A FEW DAYS.
Official will come when the last annoying incall audio bug is squashed​
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.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Important information:
This thread is for CyanogenMod 12 opensource builds for the LG G3 (D852). The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Instructions:
Your device will need to be rooted and have custom recovery before proceeding. Please check your device forum for instructions.
First time flashing CyanogenMod 12 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 & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps add-on package.
Already on CM12, try a dirty flash.
Reboot into recovery
Make back up <optional>
Wipe cache, system, dalvik-cache
Optional: Install the Google Apps add-on package.
Reboot
Download: CM12 EXPERIMENTAL BUILDS - Check EXPERIMENTAL folder for your device
AndroidFileHost - HERE
BasketBuild - HERE
Goo.im - HERE
Google Apps: Optional add on package that allows Google Play services such as Google Play Store and other Google Apps outside of AOSP based ROMs.
Check THIS post
Changelog:
CyanogenMod Change Log HERE
G3 Specific Change Log HERE
D850 Specific Change Log HERE
AndroidUser00110001 Change Log HERE
invsisblek Change Log HERE
GitHub - Source Code:
GitHub - CyanogenMod
GitHub - AndroidUser00110001
GitHub - invsisblek
Credits:
Thanks to all sent Paypal!!!
CyanogenMod
Thanks to @invisiblek for the work he has done on device trees.
Change Log & Other info
Changelog:
2015-01-12 - In addition to the changes below. This build is currently being built and uploaded.
g3: Get rid of ctrl_interface=/data/misc/wifi/sockets http://review.cyanogenmod.org/#/c/84746/
camera: add 3840x2160 video size http://review.cyanogenmod.org/#/c/84832/
camera: set lge-camera parameter - http://review.cyanogenmod.org/#/c/84833/
2015-01-11 - This build is currently being uploaded.
In addition to the changes from 2015-01-08
Set System prop to allow proper Imsi handling - http://review.cyanogenmod.org/#/c/84293/
selinux: Fix access to the vibrator amplification sysfs - http://review.cyanogenmod.org/#/c/84770/
Camera2: Samsung 4k Camera workaround - http://review.cyanogenmod.org/#/c/83332/
Some changes may have been merged but not in latest nightly.
2015-01-08 - This build is currently being built and will be on servers in about an hour from now.
In addition to the changelog in post #1 the following code has been merged into today's EXPERIMENTAL TEST BUILD
Adjust volume for voice-speaker
Default AT&T G3 APN
d850 cleanup
sepolicy: give radio access to tap2wake node
ProximitySensorManager: disable TapToWake while we have a prox wakelock
Bugs:
Only report bugs for UNOFFICIAL EXPERIMENTAL BUILDS pertaining to new code that is listed above in the changelog. Please report if anything is broken or if fixes actually fix something. THANKS!
For proper technique on reporting bugs:
Read THIS and THIS.
When reporting a bug be as specific as possible.
Make sure you can replicate the bug when coming from a clean install with no other apps installed besides what comes with ROM and GApps.
If you narrowed down a specific app that crashes only on CM ROM then please include app version and all info about app too.
Do not have any modifications done to the Android system besides.
It is very important to read on the proper technique to report a bug. Helps keep thread clean and makes tracking issues easier.
OFFICIAL FOR D855 please
Awesome, glad to see another D852 build! Thanks. Testing it out now!
D855 plz...
gdonanthony said:
OFFICIAL FOR D855 please
Click to expand...
Click to collapse
Kookitza said:
D855 plz...
Click to expand...
Click to collapse
Isn't there CM12 for D855?
sean222 said:
Awesome, glad to see another D852 build! Thanks. Testing it out now!
Click to expand...
Click to collapse
Let me know if it boots or not and what issues it may have please.
What's the difference between this and the other Cyanogenmod 12 for the G3 ?
AndroidUser00110001 said:
Isn't there CM12 for D855?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
Professor Jones said:
What's the difference between this and the other Cyanogenmod 12 for the G3 ?
Click to expand...
Click to collapse
Is there CM12 for the D852?
Kookitza said:
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
Click to expand...
Click to collapse
Me too If there is none than maybe I will build.
AndroidUser00110001 said:
Is there CM12 for the D852?
Click to expand...
Click to collapse
Sorry, I thought this one was for the 855. Nightly means that it gets an update every night ?
AndroidUser00110001 said:
Me too If there is none than maybe I will build.
Click to expand...
Click to collapse
There is one: http://forum.xda-developers.com/lg-g3/development/rom-cyanogenmod-12-t2945191
But it's not nightly...
Plz build for us also.. :fingers-crossed:
AndroidUser00110001 said:
Isn't there CM12 for D855?
Click to expand...
Click to collapse
we need OFFICIAL but its okay i can wait
So is this working? Anyone flash it yet?
AndroidUser00110001 said:
So is this working? Anyone flash it yet?
Click to expand...
Click to collapse
I just finished flashing it on my d852g , so far it's looking good. Wifi ok, LTE ok, bluetooth ok. I flashed gapps micro beta from the 1st post here, I'll report back later!! I gotta tell you, flashing ROM's on this device is soooo much faster that my Asus TF300T tablet
zurny said:
I just finished flashing it on my d852g , so far it's looking good. Wifi ok, LTE ok, bluetooth ok. I flash gapps micro beta from the 1st post here, I'll report back later!! I gotta tell you, flashing ROM's on this device is soooo much faster that my Asus TF300T tablet
Click to expand...
Click to collapse
Thanks! @Cuzz1369 also tested for me and all seems OK for now.
gdonanthony said:
we need OFFICIAL but its okay i can wait
Click to expand...
Click to collapse
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
AndroidUser00110001 said:
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
Click to expand...
Click to collapse
Flashing NOW!! :victory:
AndroidUser00110001 said:
https://goo.im/devs/androiduser00110001/ROM/D855/CM12/
Let me know in private if it boots and if anything different is broke when compared to other ROMs you have flashed.
Click to expand...
Click to collapse
perfect. found no bug till now
For D855 users that have asked
http://forum.xda-developers.com/lg-g3/development/rom-cyanogenmod-12-unofficial-nightly-t2973522
Now lets get back on topic in this thread

[ROM][N910F] Unofficial CM-12.0 for 910F Note 4. (trltexx)

[ROM][N910F] Unofficial CM-12.0 for 910F Note 4. (trltexx)
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
For weeks there has been a team effort initiated by Gekkehenkie11 to bring CyanogenMod to the N910F. Many test builds have been released in this thread: http://forum.xda-developers.com/note-4/general/rd-porting-cm12-t2951934 .
More and more users have asked for a ROM thread, to make releases more clear. Plus it's time to focus more on R&D in the R&D thread, and less on flash / usage issues. So here it is. The thread you've asked for.
Consider this the worst ROM thread in history.
This ROM would not have been possible without Slayher and Fattire! They have identified and solved a lot of the common trlte issues, and merged them back into the CM source. See their thread for more information about their work: http://forum.xda-developers.com/note-4-tmobile/development/unoffcial-cm-12-0-t-mobile-note-4-t2964887 . We've picked up from there to modify everything for the N910F, rebase the work on the N910F kernel source, fix RIL issues, fix up missing blobs, tweaks, etc.
To quote Slayher:
CM-12.0 is not ready. There are still massive changes of the code base as it progresses to add the already established features and enhancements.
There will be things broken.
Click to expand...
Click to collapse
More info will follow later.
Expect bugs, flash at your own peril. Make sure you wipe the device, even if you come from a previous build.
Enjoy!
P.s.
This is all done on our free time. Take it or leave it. Don't expect support..... but we'll try our best to help you.
MOD EDIT -
The OP is no longer active but here are the latest builds, flash at your own risk.
Build 5th Feb...no need to flash blobs anymore.
gekkehenkie11 said:
new build up ! https://mega.co.nz/#!vQJlQL7Y!yIvuVFx85vQV1gdayQ9GmRt54Kq4tdx5C52BzDdO8b0
NFC should work now without draining your battery ! And vibrator works again.
Click to expand...
Click to collapse
6th Feb
gekkehenkie11 said:
New build:
https://mega.co.nz/#!CQ5EkbzR!qYs2bM0dDbWs6c1enWjFUy-J3qokvs2t64zjWj0wopI
* GPS is fixed.
* NFC works but either leave it always on or uninstall NFC: cause if you boot while NFC was off, it will drain battery during that session !
* It may say 'no service' during some sessions, this is a known upstream bug at the moment, but doesn't seem to affect functionality at all
More changes here: http://www.cmxlog.com/12/trltetmo/
Enjoy !
Click to expand...
Click to collapse
Latest build 11th Feb
gekkehenkie11 said:
New build:
https://mega.co.nz/#!iEBUHLCY!KNv3R4kFZFwJZ4jYszka2UOf4T39CA6XFTmGK_14TZs
Changelog: http://www.cmxlog.com/12/trltetmo/
Click to expand...
Click to collapse
19th Feb -- Daily builds can be found HERE
Gapps - HERE
XDA:DevDB Information
CM-12.0 for 910F Note 4, ROM for the Samsung Galaxy Note 4
Contributors
Preaper, gekkehenkie11, slayher, fattire
Source Code: http://github.com/jaapp
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-12-29
Last Updated 2015-02-21
Great job guys!!!
Maybe add last build date in topic? And gapps in OP?
910G here, was running previous builds, just tried to flash this, couldn't get past boot animation, just flashed gekke's blobs on top to see if it boots.
This latest build contains changes to make the Samsung smart cover function. Which makes the device turn on in my pocket. This is an issue that needs to be addressed soon.
Welcome to the world of alpha builds
I am stuck in bootloop in this build
mike13ftw said:
I am stuck in bootloop in this build
Click to expand...
Click to collapse
Same
I also have a bootloop with 28 dec build
mmui90 said:
Same
Click to expand...
Click to collapse
Flash 25dec build back and everything works.
Bootloops only happen if you don't wipe your device before flashing.
Preaper said:
Bootloops only happen if you don't wipe your device before flashing.
Click to expand...
Click to collapse
Full wipe?
Preaper said:
Bootloops only happen if you don't wipe your device before flashing.
Click to expand...
Click to collapse
Just full wiped, still not booting.
For the people having issues flashing the latest build, this is the previous one from the 25th: https://mega.co.nz/#!D0FEFQ6Y!fihYU8Lu-jQl7Fr7SqnBOv5SIUrX0dSUY1sbqZXbdto
Give that one a shot and let me know if this makes any difference.
Beukhof1 said:
Full wipe?
Click to expand...
Click to collapse
Yes.
Preaper said:
For the people having issues flashing the latest build, this is the previous one from the 25th: https://mega.co.nz/#!D0FEFQ6Y!fihYU8Lu-jQl7Fr7SqnBOv5SIUrX0dSUY1sbqZXbdto
Give that one a shot and let me know if this makes any difference.
[...]
Click to expand...
Click to collapse
25th build works. 28th (after full wipe) however doesn't for me.
Preaper said:
For the people having issues flashing the latest build, this is the previous one from the 25th: https://mega.co.nz/#!D0FEFQ6Y!fihYU8Lu-jQl7Fr7SqnBOv5SIUrX0dSUY1sbqZXbdto
Give that one a shot and let me know if this makes any difference.
Yes.
Click to expand...
Click to collapse
Ok will try a full wipe and report back.
28th build doesnt boot as well. Tried with a full wipe. 25th build works fine for me.
Beukhof1 said:
Great job guys!!!
Maybe add last build date in topic? And gapps in OP?
Click to expand...
Click to collapse
Thanks for the suggestion. I'll add this later.
Some screenshots please?
kosako17 said:
Some screenshots please?
Click to expand...
Click to collapse
It's stock cm12. Looks the same on every phone.
I believe I know what is causing the issues with the latest build. The boardconfig changed, and I was behind pulling from some repo's. To fix it I have to nuke my build environment and rebuild everything again. This usually takes 6 hours which means it will finish when I'm in bed. Expect a new build in 24 hours or so.
Hi all.
Can someone please explain in few words why CM ROMs are better than TW ROMs? What are the advantages of flashing CM builds over TW etc? Thx
cornelito said:
Hi all.
Can someone please explain in few words why CM ROMs are better than TW ROMs? What are the advantages of flashing CM builds over TW etc? Thx
Click to expand...
Click to collapse
The question for me is why does Samsung put TW on Android? Pure Android is so sexy. With CM it's even more.

[ROM][I777][5.1.1][OFFICIAL] CyanogenMod 12.1 Nightly Builds

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 Lollipop, 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
IMPORTANT INFORMATIONS
- Root is now disabled by default on CM12.1. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
- Even if I (Lysergic Acid) don't own an i777, I'm maintaining it officially as everything I do for my i9100 gets to the i777 too, so it's fair enough to open a thread for you guys
We'll not support users and answer questions from users which:
- Are running a custom kernel
- Have flashed mods
- Modified system files
- Didn't follow our instructions
- Are unfriendly
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/I777_Info
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i777
Changelog: http://www.cmxlog.com/12.1/i777
First time installation instructions:
Download CM-12.1-XXXXXXXX-NIGHTLY-i777.zip to your sdcard
Make sure you're using a Kitkat Compatible Recovery
Boot into Recovery
Wipe all your data
Flash CM-12.1-XXXXXXXX-NIGHTLY-i777.zip from sdcard
(Optional)Flash Google Apps.zip from sdcard
Reboot
CM12.1 official nightly builds:
http://download.cyanogenmod.org/?device=i777
Recommended Google Apps:
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Choose Pico version to fit in the /system partition.
If you like my work, consider making a small donation ​
​
XDA:DevDB Information
CyanogenMod 12.1, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
Lysergic Acid, rogersb11
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Kitkat Compatible Recovery
Based On: AOSP
Version Information
Status: Nightly
Created 2015-07-04
Last Updated 2015-07-03
Reserved
Hi,
I'm currently running Cyanogenmod version 11-20140402-Unofficial-i777 on my SGH-i777. I'd like to update to this Nightly build. Can I use the instructions in OP to update to this Nightly? (Just want to clarify because your OP clearly says "First Time Installation Instructions" but the process looks the same as any other update.)
CM and kernel details:
CyanogenMod version 11-20140402-Unofficial-i777
Kernel version 3.0.64-RB11-Shift-1.1
Thanks for your work on bringing CM 12.1 to the Galaxy S II!
Flashed 07032015 but stuck at cm logo.
Sent from my i777 using XDA Free mobile app
Great work but IMO this should have never gone official for the i777. The outgoing call bug is a huge bug.
It would never have passed under Entropy/Cody.
Is there a thread on JIRA for the outgoing call bug? I couldn't find one but would like to contribute by scouring the code (and would like to see what others have done so far).
Build cm-12.1-20150704-NIGHTLY-i777 Install fine on my sgh-i777. Phone bug still there. I used Tasker to toggle the speaker on and off for incoming calls and it seemed to work ok. Build ran cool and stable for the short time I had it install. Surprised with the Cyanogen Recovery limitations, seems like it won't install zip files. Had to use Mobile Odin to flash a kernel to get CWM recovery back to restore backup file.
jankypatella said:
Hi,
I'm currently running Cyanogenmod version 11-20140402-Unofficial-i777 on my SGH-i777. I'd like to update to this Nightly build. Can I use the instructions in OP to update to this Nightly? (Just want to clarify because your OP clearly says "First Time Installation Instructions" but the process looks the same as any other update.)
CM and kernel details:
CyanogenMod version 11-20140402-Unofficial-i777
Kernel version 3.0.64-RB11-Shift-1.1
Thanks for your work on bringing CM 12.1 to the Galaxy S II!
Click to expand...
Click to collapse
Yes, just follow that instructions and you'll be fine.
yosmokinman said:
Great work but IMO this should have never gone official for the i777. The outgoing call bug is a huge bug.
It would never have passed under Entropy/Cody.
Click to expand...
Click to collapse
I thought this bug had been fixed, anyway, I don't have this problem on my i9100, that's probably related to the different mic location of the i777. Sadly without the phone I'm not the best to fix this.
Quicksilver13 said:
Build cm-12.1-20150704-NIGHTLY-i777 Install fine on my sgh-i777. Phone bug still there. I used Tasker to toggle the speaker on and off for incoming calls and it seemed to work ok. Build ran cool and stable for the short time I had it install. Surprised with the Cyanogen Recovery limitations, seems like it won't install zip files. Had to use Mobile Odin to flash a kernel to get CWM recovery back to restore backup file.
Click to expand...
Click to collapse
CM recovery installs signed zips only.
^Yeah it's not fixed and really going to be a ***** I think.
i9100 is fine. i777 with the yamahell chip I still think is the problem. Remember Paul from the replicant project? Helped greatly but maybe not so with 5+
The i777 seems to be how many hacks can you stack on top a hack.. ie. hwc
Edit: That Dead show was gooooooooooooood. LA? My emmc was definitely repartitioned.
yosmokinman said:
^Yeah it's not fixed and really going to be a ***** I think.
i9100 is fine. i777 with the yamahell chip I still think is the problem. Remember Paul from the replicant project? Helped greatly but maybe not so with 5+
The i777 seems to be how many hacks can you stack on top a hack.. ie. hwc
Edit: That Dead show was gooooooooooooood. LA? My emmc was definitely repartitioned.
Click to expand...
Click to collapse
I'll look in the differeces of the i777 and try something, but I don't promise anything.
The OTAs are block-based in Lollipop btw, that's why it looked like a repartition, but it was not
Latest nightlies will resize the system according to your pit.
Lysergic Acid said:
CM recovery installs signed zips only.
Click to expand...
Click to collapse
Thanks for the information. I couldn't find much info on CM Recovery. Is it possible to make backups and restore on CM Recovery?
Quicksilver13 said:
Thanks for the information. I couldn't find much info on CM Recovery. Is it possible to make backups and restore on CM Recovery?
Click to expand...
Click to collapse
Sadly not yet, only through adb. CM recovery is very simple indeed, I think it's made for people that don't even use the recovery
Looking forward to trying this and thanks for the ROM. I wonder if the AJNewkirk mic-swap kernels would have any .ko files that would help the call bug?
Lysergic Acid said:
Latest nightlies will resize the system according to your pit.
Click to expand...
Click to collapse
Glad to see that finally make it in. I wouldn't want to have to redo that partitioning again.
Are the scripts setup not to have to reflash gapps after every upgrade yet? (it was an issue on the i9100 thread last week -- not sure if it got resolved or if with the block update there is no way to solve it).
TeutonJon78 said:
Glad to see that finally make it in. I wouldn't want to have to redo that partitioning again.
Are the scripts setup not to have to reflash gapps after every upgrade yet? (it was an issue on the i9100 thread last week -- not sure if it got resolved or if with the block update there is no way to solve it).
Click to expand...
Click to collapse
The block-based OTAs came in to fix the gapps backup, so yes, it works
The phone runs really well on the latest nightly! Multi tasking is smoother than ever before. Unfortunately I lack the skills, but it would be great if someone (CM? @cyril279, @rogersb11, @Lysergic Acid) could re-pack the stock kernel with a custom recovery.
Edit: unbelievably solid as a rock. Thank you to all the devs over the years that have helped keep this device relevant. This latest nightly from CM is like butter on the SII...I even put the OneplusOne and the Nexus4 on the shelf and threw my sim card back into this phone for the last couple days. Loving it.
The slim kernel is essentially the cm kernel, with TWRP 2.8.7.0
So the quickest solution would be to flash:
CM
SLIM kernel
Google apps
Regarding the call-bug @Lysergic Acid, I'd ship you an i777 if you were in the states, but I fear that international shipping makes it cheaper to buy you one than ship one... Are there any particular logs that could help to identify the issue?
-Cyril
erad1 said:
[...] but it would be great if someone (CM? @cyril279, @rogersb11, @Lysergic Acid) could re-pack the stock kernel with a custom recovery.[...]
Click to expand...
Click to collapse
---------- Post added at 09:28 PM ---------- Previous post was at 09:21 PM ----------
dimoochka said:
Is there a thread on JIRA for the outgoing call bug? I couldn't find one but would like to contribute by scouring the code (and would like to see what others have done so far).
Click to expand...
Click to collapse
I don't think that a JIRA issue has been filed on this, but it deserves one, along with logs. Jira is designed to centralize and track the progress and effort of specific issues.
-Cyril
^I really doubt they'll ever touch it.
I still think it's the yamahell **** all over again.
OT thanks for Omni that's my dd and runs as nice as you could expect on this phone. Plus twrp. cm recovery is trash and a dealbreaker till they fix it up a bit.
cyril279 said:
The slim kernel is essentially the cm kernel, with TWRP 2.8.7.0
So the quickest solution would be to flash:
CM
SLIM kernel
Google apps
-Cyril
Click to expand...
Click to collapse
Thanks for the tip Cyril .. Do you have a link for the Slim Kernel?
kingfiras said:
Thanks for the tip Cyril .. Do you have a link for the Slim Kernel?
Click to expand...
Click to collapse
BEWARE:
- Cyril's cm-kernel does NOT currently include the FPbug-fix recently added to CM kernel source.
The kernel that I'm linking to only includes CM commits up through may 2015. I just noticed that CM more recently included the FPbug fix into their source (thanks LA), and my CM kernel does NOT include that (I wasn't paying attention when I switched to the CM kernel source from OMNI). : embarrased :
I'll update and build another within the week.
:: kernel-i777_5.1_TWRP-signed.zip ::
- Kernel source -

[ROM]Unofficial OmniRom 5.1[No RIL]

Code:
Code:
/*
* Your probably long expired 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.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png

[6.0.1 marshmallow][UNOFFICAL] CyanogenMod 13.0 for SM-G860P

As always, you are responsible for your device. Use common sense and make backups
I am just a compiler not a developer but i try to find fixes when I can. That doesnt mean everything will get fixed.
In case anybody wants a pure cm13.0 for the kltesprsports, here it is. Was built from cm13.0 sources, 6.0.1
***Thanks***
CyanogenMod Team
@miked63017 be sure to hit this guys thanks button
Any and all testers of my work!
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
Installation
flash(odin) unoffical twrp from here = https://androidfilehost.com/user/?w=settings-dev-files&flid=52449
wipe everything except sd card
install cm13.0 from here = https://www.androidfilehost.com/?w=files&flid=52450 new builds will be here when updated!!!!!!!
install gapps from here = http://opengapps.org/?api=6.0&variant=nano reccomend the aroma
XDA:DevDB Information
[6.0.1 marshmallow][UNOFFICAL] CyanogenMod 13.0 for SM-G860P, ROM for the Sprint Samsung Galaxy S 5 sport
Contributors
1991mustang50, miked63017
Source Code: https://github.com/1991mustang50/android_device_samsung_kltesprsports
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: working with issues
Know issues:
Nfc not working
Camera must turn on HDR in camera settings
And you tell me up in bug reports
Created 2016-03-21
Last Updated 2016-03-20
Reserved
Reserved
Works! Thanks for the hard work!
Sent from my SM-G860P using Tapatalk
1991mustang50 said:
As always, you are responsible for your device. Use common sense and make backups
In case anybody wants a pure cm13.0 for the kltesprsports, here it is. Was built from cm13.0 sources, 6.0.1
***Thanks***
CyanogenMod Team @miked63017 be sure to hit this guys thanks button
Any and all testers of my work!
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
Installation
flash(odin) unoffical twrp from here = https://androidfilehost.com/user/?w=settings-dev-files&flid=52449
wipe everything except sd card
install cm13.0 from here = https://www.androidfilehost.com/?w=files&flid=52450
install gapps from here = http://opengapps.org/?api=6.0&variant=nano reccomend the aroma
XDA:DevDB Information
[6.0.1 marshmallow][UNOFFICAL] CyanogenMod 13.0 for SM-G860P, ROM for the Sprint Samsung Galaxy S 5
Contributors
1991mustang50, miked63017
Source Code: https://github.com/1991mustang50/android_device_samsung_kltesprsports
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-03-21
Last Updated 2016-03-20
Click to expand...
Click to collapse
Thank you so much for the hard work and answering my previous questions. I'll definitely be flashing this and reporting back tomorrow. Question: if I'm on the latest cm12 build currently, can i just flash the new TWRP through Odin over the CWM recovery for the Sport? Or is it required to flash back to the stock firmware?
g4_e said:
Thank you so much for the hard work and answering my previous questions. I'll definitely be flashing this and reporting back tomorrow. Question: if I'm on the latest cm12 build currently, can i just flash the new TWRP through Odin over the CWM recovery for the Sport? Or is it required to flash back to the stock firmware?
Click to expand...
Click to collapse
Just flash twrp through odin
1991mustang50 said:
Just flash twrp through odin
Click to expand...
Click to collapse
OK. Thank you very much for the quick replies. I'll flash tomorrow when I get back from school. :thumbup:
Been working great all day. Haven't hit any bugs and doze is really helping battery life! Thanks again @1991mustang50 for this and TWRP. Will say that TWRP is slow to take a stock backup (not as slow as the CWM we had prior), but it may be because TouchWiz is so heavy. Either way, thanks again. I know the guys that still use this phone daily really appreciate it and so do us that just use it as a toy now!
Good job @1991mustang50, it's a shame I had already given up on the phone and sold it
victor1g said:
Good job @1991mustang50, it's a shame I had already given up on the phone and sold it
Click to expand...
Click to collapse
How much did you get for it, if you don't mind me asking?
New build up same link in op just pulled cm changes!
1991mustang50 said:
New build up same link in op just pulled cm changes!
Click to expand...
Click to collapse
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
atcq28 said:
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
Click to expand...
Click to collapse
I started a build before i left for work if no problems i have new build up for kltespr!
Chief_Nodnarb said:
How much did you get for it, if you don't mind me asking?
Click to expand...
Click to collapse
I sold it for $100 to a cousin. It was in a rough condition around the edges and had call quality issues
Having issues getting data or cell service - I can see sprint under network operators, but haven't been able to get the phone connected. Is anyone else having the same issue and/or found a workaround?
I've flashed TWRP and the ROM and I have to say that so far there have been very few issues. TWRP makes backups very quickly compared to the previous CWM. The ROM has calls, data, SMS, and MMS working perfectly. One minor issue is that if you go into settings and click on carrier settings it will not recognize the SIM card and it will continuously crash the phone application until you reboot. It's a minor issue with an easy fix so dont worry too much about it. I tested Bluetooth which isn't in very good shape. Listening to music from my phone on a wireless headset was constantly cutting out. However I understand it's a beta build and Bluetooth shouldn't be a very big problem for me as I can just use the headphone jack. This next problem I don't think is specifically tied to the ROM however I would like if anyone can give me any ideas for. Basically write access on the external SD is not working as usual but all of the previous fixes you could use aren't working anymore. Any ideas or fix for marshmallow? Overall, the ROM is in great condition for such a new release. Doze works beautifully and battery life is even better than the previous CM12.1 build. I'll be using the ROM more to see if I can tell you about any other issues I may encounter. Thanks so much for the great ROM and TWRP. I'll be looking forward to future builds.
bigfatdude said:
Having issues getting data or cell service - I can see sprint under network operators, but haven't been able to get the phone connected. Is anyone else having the same issue and/or found a workaround?
Click to expand...
Click to collapse
I am not sure why you have this problem others seem ok. If you go back to cm12.1 do u get it back?
atcq28 said:
Any chance on making a build for the regular boost mobile one? The one on Mike's is giving me too many issues when it comes to bootloops
Click to expand...
Click to collapse
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
1991mustang50 said:
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
Click to expand...
Click to collapse
Sweet! Can't wait to try it out
1991mustang50 said:
Havent forgot i did set up repo for kltespr to build twrp like i am doing forkltesprsports
Click to expand...
Click to collapse
That was post to say i didnt setup the repo for kltespr to build twrp which my build enviroment is set up to. So running new build for kltespr now. Should be posted in the morning

Categories

Resources