Click root, mount system as r/w,
And make changes.
Yeah, Paget96 put read-only mounting on reboot, with his mod
Attachments
Last edited:
[ROM][OFFICIAL] CyanogenMod Nightly Builds for d2spr
- Thread starter noobnl
- Start date
Click root, mount system as r/w,
And make changes.
Yeah, Paget96 put read-only mounting on reboot, with his mod
I dont know, where I must to write about my problem
But
And here
On my L710 any nightlies of CM12.1 not booting.
Used TWRP 2.8.7.0, CWM last, CM recovery, nightlies from december, november.
Boot stuck.
Trying to return to ND8, NJ2. Nope.
What I can do wrong... CM11 started, MIUI started, TW-roms started.
But
And here
On my L710 any nightlies of CM12.1 not booting.
Used TWRP 2.8.7.0, CWM last, CM recovery, nightlies from december, november.
Boot stuck.
Trying to return to ND8, NJ2. Nope.
What I can do wrong... CM11 started, MIUI started, TW-roms started.
Have you been doing a clean wipe? Try flashing just the ROM with no kernel or even GApps. See if at least the ROM boots up on its own like that.
Wiped cache, dalvik, internal storage, data!
Clean CM12.0, 12.1!
Clean ROMs without any kernels etc
LTE to Lrs121
I appreciate your prompt, and curtious feedback.
You suggestions are great! I will try them out.
Just wanted to clarify a couple things, Right now I have DNJ2 rom flashed on my virgin moble with 4g working.
I have removed knox, loving how everything just works, but interested in furthering the development of cm13 on (sph-l710)
In your sentence: "So, I'd recommend, when first setting up, you'll wanna flash the ROM, gapps and the fix, reboot, the flash the ROM and fix."
when you say ROM, in both those instances, I am assuming you mean cm13? Is this correct?
What do you recommend formatting after each flash?
I found a problem, that with flashing anything other than d2LTE (tested newest updated release), unless I format the /Data partition in twrp 3.0.0-0, after having install a stock rom, via odin, I get an error message upon flashing cm11,12, (haven't tried 13) but I assume it is the same deal.
The error message states that data is incompatible and will not flash. I have erased the /Data partition, and found that it proceeds to install the new cm11/12 when attempting to do so.
So, do you recommend erasing the /Data partition only? Or do you recommend erasing Dalvik, and cache as well?
It seems I get errors like, system not responding, along with other errors, but I may have never tried flashing gapps immediately after installing cm11/12. It seems like I have flashed a million different ways.
Does dirty flashing only relate to /system partition?
Which /partition is crucial for 4g to correctly work?
Please describe the steps in greater detail.
I appreciate your hard work and contribution to the android community!
Currently running: Virgin Mobile (sph-l710)
(open gapps 4.4)
(offical stock DNJ2 ROM, spr)
(Knox removed)
(4G working)
(rooted)
(TWRP-3.0.0-0)
I appreciate your prompt, and curtious feedback.
You suggestions are great! I will try them out.
Just wanted to clarify a couple things, Right now I have DNJ2 rom flashed on my virgin moble with 4g working.
I have removed knox, loving how everything just works, but interested in furthering the development of cm13 on (sph-l710)
In your sentence: "So, I'd recommend, when first setting up, you'll wanna flash the ROM, gapps and the fix, reboot, the flash the ROM and fix."
when you say ROM, in both those instances, I am assuming you mean cm13? Is this correct?
What do you recommend formatting after each flash?
I found a problem, that with flashing anything other than d2LTE (tested newest updated release), unless I format the /Data partition in twrp 3.0.0-0, after having install a stock rom, via odin, I get an error message upon flashing cm11,12, (haven't tried 13) but I assume it is the same deal.
The error message states that data is incompatible and will not flash. I have erased the /Data partition, and found that it proceeds to install the new cm11/12 when attempting to do so.
So, do you recommend erasing the /Data partition only? Or do you recommend erasing Dalvik, and cache as well?
It seems I get errors like, system not responding, along with other errors, but I may have never tried flashing gapps immediately after installing cm11/12. It seems like I have flashed a million different ways.
Does dirty flashing only relate to /system partition?
Which /partition is crucial for 4g to correctly work?
Please describe the steps in greater detail.
I appreciate your hard work and contribution to the android community!
Currently running: Virgin Mobile (sph-l710)
(open gapps 4.4)
(offical stock DNJ2 ROM, spr)
(Knox removed)
(4G working)
(rooted)
(TWRP-3.0.0-0)
E
ElectricCrayon
Guest
I've been having issues with Bluetooth media playback since the switch to cm13, by issues I mean since upgrading to cm13 I have no media playback over bluetooth. Media playback never worked perfectly for me on 12.1 though (a lot of random few seconds of screeching distortion) but it was listenable. I'm eager to get it back as well. I think the only thing there is to do is wait. CM13 is still relatively new and is still being worked on. Or you can always rollback to the last cm12 version that worked for you.
Yes I know it will be worked out eventually! Ironically for me it was the exact opposite and media normally work perfectly but I could not make phone calls on Bluetooth at all. Now I can make phone calls properly but I can't play any media back. A bit of good news though is that now with Bluetooth phone calls working I can use this as a daily driver and experience to better battery life I've been eagerly awaiting
Sent from my SPH-L710 using Tapatalk
Sent from my SPH-L710 using Tapatalk
E
ElectricCrayon
Guest
I noticed today there's a thread about the issues with bluetooth on the CyanogenMod forums with a request for log files. Hopefully that means it's at least being looked into, or more optimistically that a fix might be on the way soonish.
Swing by here if you're curious or maybe want to send in some logs.
http://forum.cyanogenmod.org/topic/119262-bluetooth-issue/
...no BT for me, either!
...yeah, I'm one of those unlucky folk where BT media playback failed as soon as the new d2spr nightlies kicked in.
Back when this was still an unoffical, BT media worked grand.
Now, meh, not so good.
Y'know, I haven't given my Chromecast Audio a shot since the ROM went official.
I'll give that a go once I get home.
Don't think the BT issue would be of any difference to a Chromecast, though!
...yeah, I'm one of those unlucky folk where BT media playback failed as soon as the new d2spr nightlies kicked in.
Back when this was still an unoffical, BT media worked grand.
Now, meh, not so good.
Y'know, I haven't given my Chromecast Audio a shot since the ROM went official.
I'll give that a go once I get home.
Don't think the BT issue would be of any difference to a Chromecast, though!
E
ElectricCrayon
Guest
I had some luck sending in some logs just by trying BT after each nightly. One of the last times resulted in a BT crash and a prompt to automatically send in error logs to CM. At this point at least we know they know about the issue. I'm just happy they're working on this phone at all!
Side note: Wait, Chromecast Audio works over BT? I thought it was only for casting over WiFi. Google's Chromecast Audio product site completely trashes using bluetooth (casting via wifi = better quality, no interruptions, longer range, doesn't drain battery, share music, multiple speakers). I've only got the original Chromecast and casting over wifi works perfectly there.
Side note: Wait, Chromecast Audio works over BT? I thought it was only for casting over WiFi. Google's Chromecast Audio product site completely trashes using bluetooth (casting via wifi = better quality, no interruptions, longer range, doesn't drain battery, share music, multiple speakers). I've only got the original Chromecast and casting over wifi works perfectly there.
Well that was actually an issue on my part settings wise on my Chromecast. It works now and it does use Wi-Fi and not Bluetooth
Sent from my SPH-L710 using Tapatalk
Sent from my SPH-L710 using Tapatalk
cm-13.0-20160322-NIGHTLY-d2spr.zip
...not to derail this thread into a tangent on Chromecasting, but how'd you do it? Are you on Chromecast Audio? Because for some reason, my d2spr ain't recognizing my CA on the network, but my old-ass Nexus 7 (rehashed, thanks to http://xdaforums.com/nexus-7/development/rom-cyanogenmod-11-nexus-security-fixes-t3241243) totally works fine.
It could be also because I'm two nightlies ago (20160322), but still no BT media working; although, my Pebble Steel connects great and gets notifications.
Like everyone else, I anxiously await the next nightlies to tackle these issues.
EDIT: My bad, Chromecast audio works. I dunno what happened there, really. Bah, user error.
...not to derail this thread into a tangent on Chromecasting, but how'd you do it? Are you on Chromecast Audio? Because for some reason, my d2spr ain't recognizing my CA on the network, but my old-ass Nexus 7 (rehashed, thanks to http://xdaforums.com/nexus-7/development/rom-cyanogenmod-11-nexus-security-fixes-t3241243) totally works fine.
It could be also because I'm two nightlies ago (20160322), but still no BT media working; although, my Pebble Steel connects great and gets notifications.
Like everyone else, I anxiously await the next nightlies to tackle these issues.
EDIT: My bad, Chromecast audio works. I dunno what happened there, really. Bah, user error.
Last edited:
My Chromecast require software update, it's also the newest model they just came out with.
Sent from my SPH-L710 using Tapatalk
Sent from my SPH-L710 using Tapatalk
E
ElectricCrayon
Guest
Good news! The latest nightly (cm-13.0-20160411-NIGHTLY-d2spr) has restored bluetooth for me! :good::good::good:
According to cmxlog the change was for a2dp (bluetooth audio for media) and it might cause issues with bluetooth phone calls. I only use bluetooth with a few bluetooth speakers so I can't personally say whether bluetooth calls are affected. The audio is working for me about as good as it did on CM12.
According to cmxlog the change was for a2dp (bluetooth audio for media) and it might cause issues with bluetooth phone calls. I only use bluetooth with a few bluetooth speakers so I can't personally say whether bluetooth calls are affected. The audio is working for me about as good as it did on CM12.
...great news, thanks! I've been biting my toenails in anticipation!
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
191CyanogenMod 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. */
This is a nightly build of CM for the Galaxy S3 on Sprint.. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Please submit a patch to our Gerrit instance if you want to help out.
Install instructions:
1. Install ClockworkMod Recovery for "d2spr". Sorry, CM cannot provide support for other recoveries, although they may work fine.
2. Get the nightly build http://get.cm/?device=d2spr.
3. Reboot into recovery and install.
Do not report bug to the bug tracker if you are using this build.33Regarding the 3.4 kernel
I have seen some questions about just what the 3.4 kernel is and why the shift was made in the first place. I apologize in advance for the long-winded post. If you are looking for the punch line, skip to "Why should you care?" at the bottom of the post.
Let me answer a few of these questions.
First of all, the obvious, the 3.4 kernel is based on a Linux kernel that is about a year newer than the 3.0 edition. It's not an exaggeration that there's probably +1000 individual patches that separate the two linux kernels. Though, if you want specifics about these changes, you will have a hard time finding answers, partly because bug fixes get applied to the stable branches of both long-term-support linux mainline kernels (currently 3.0 and 3.4). So it's mostly new features that were adopted for 3.4 that were left out of 3.0, and even then, the vast majority is code that is not even compiled for our device. There are some things that are relevant: I know for a fact, for an example, that ext4 has evolved quite a bit between 3.0 and 3.4.
Far more importantly for us: the lineage of this kernel is straight from Qualcomm not Samsung. Let me explain a bit what this means: The 3.0 kernel that we were using until recently came originally from the Samsung source drop (looks like some time later, Steve merged/rebased it on top of some qualcomm sources). The 3.4 kernel was developed a bit differently.
A little aside, you may have heard of Codeaurora Forum (CAF) - it is an extension of Qualcomm, looks to be some fictitious quasi-partnership with some other non-contributors. I've heard stories that it's an elaborate way to get around the lawyers at QCOM that have a firm choke-hold on open sourcing most of the qcom code. This way, via CAF and under the sham of "venue to share code with their partners", qcom engineering code gets released to the public.
If you poke around codeaurora you will find the MSM git repo. This is a kernel repo aimed at specifically developing android kernels for the MSM family of devices. It's a very active repository, with dozens of patches/bugfixes going in weekly. The quality of the patches is extremely high (from my limited understanding), obviously because qcom engineers have a very intimate (and often proprietary) understanding of their SOC.
Right around the holidays in December, I started porting the tip of this tree, their "jb_2.5" branch (labels being mostly meaningless) for our device. The idea was, rather than doing mass merges with the existing samsung kernel (which wouldn't work anyways since the two kernels were worlds apart), be more surgical and only import samsung code if it was absolutely necessary. I think we managed to do this, by the way, and kept the vast vast majority of the msm code unpolluted, and samsung free (modulo perhaps camera, where we had very little choice except to mangle the msm v4l2 layer).
At some point in January I had a booting kernel, and posted a screen-shot here on XDA. Before that thread got invaded and shut down, invisiblek (d2vzw) had joined the effort and we got the peripherals working (sound, wifi, bluetooth, hd playback, rear camera, front camera video, sensors, gps, fixed various panel glitches, usb etc). A couple of weeks ago we pitched the kernel to cyanogen who jumped on the idea, fixed the front camera snapshot and a few other bugs and the rest is where you guys come in. I should say that in porting this kernel, I (we) are standing on the shoulders on everyone else who committed patches to the old kernel. Obviously cyanogen, but also other CM contributors. In particular mkasick's kexec patches were an invaluable asset.
Why should you care? The reason why QCOM devices are blessed with early ports of most CM builds, is because of CAF (and many motivated CM contributors, obviously). Not only does qcom share MSM kernel code via CAF, they also share sources for the android (userland ) components that speak with the kernel most directly - the HAL (hardware abstraction layer). If you poke around CAF you'll find "hardware/qcom/display" "hardware/qcom/audio" "hardware/qcom/media" (etc) repositories, all of which we are currently compiling (or are compiling repositories heavily based on these) for d2.
As newer and newer devices hit the market, these repositories evolve and shift their focus on newer socs. I already see this, 8960 is no longer the focal point, there are a lot of 8974 patches going in, as well as lot of snapdragon 400/600 code that gets committed. This spells trouble for older devices, as QCOM stops supporting older devices on CAF, CM ports begin to die. This is why it is imperative to upgrade our kernel and keep up with the changes. If you want to see android 5.0, 6.0 or whatever on d2 we need to have a kernel that can speak with the most up-to-date HAL repositories on CAF. Devices with 3.0 kernels already are struggling and hacking up both their kernels and userland in order to be compatible with the HAL code on CAF. We, on the other hand, are sitting pretty, since at this time, we are one of few devices (if not the only one) that is running an almost pure CAF "jb_2.5" kernel, compatible with the very latest qcom HAL repos.
So sit tight, and enjoy the process, if nothing else. If you want to be helpful, look up how to provide relevant debugging output (there's more to it than logcat), and post a detailed description of your problem along with the relevant log. You never know, maybe someone with time/interest/and skills is reading and can take a look. Also, don't assume that everyone can recreate these problems. I am using a kernel that's a bit different than the one in the current nightlies, but I can tell you I have not had a single freeze/random reboot in about a month on this kernel.
Otherwise, jump back to M2 and enjoy it for what it is.32I am so sick of people being DICKS on this thread. If you don't have a helpful benevolent answer, don't say anything at all. These answers have been answered in the past, yes, but that doesn't mean that EVERY SINGLE answer has to be said with an aura of smug bordering on prime-time fashionista. If you are one of these people (and I think you know who you are), then just shut the **** up. If someone has a question, why not try and improve the outcomes for ALL of us by offering REAL answers rather than clogging up the thread with bull**** disguised as smugness. What pisses me off more than anything is that I am having to sift through so many pages of argumentative, unhelpful smugness, that by the time I get to the end of it, I'm not only irate, but haven't accomplished anything. These are moments of my life that I will never get back.
In summary, quit being douche bags, start being helpful. In fact, start living your lives this way fundamentally; we don't need more douche bags, the landfill is full.27
You showed a pretty high degree of ignorance yourself. Let me spin you a little story. Back in 2008, I bought a G1. Pre-release. I was one of the first people to try the original root method when haykuro and crew cracked it. HARD bricked three phones in the process of testing the first custom roms (there was no odin or anything of the sort back then, and it was entirely possible to brick your phone in the most literal sense that our game has, it wouldnt turn on, it wouldnt bootloop. it was just dead.). I worked on the artwork for the very first themes. I made the first tutorial video for creating startup animations and bootscreens. I was here when the first beta versions of CM rolled off the compiler. I was here when cyanogen got the C&D letter (to which I wrote a scathing response before google clarified their position) which caused gapps to be separately packaged. I've been using it as my rom ever since, so I've got a pretty good handle on whats "well known" and what isnt.
The fact that you say that it's "well known" that switching between versions will cause problems or bootloops is 100% false. As someone who has been through EVERY SINGLE VERSION OF ANDROID, I cant begin to count how many versions I've jumped between without issue. I havent had a solid bootloop on a device in ages. If I did, its a simple enough fix. But it's certainly not well known, nor is it guaranteed that either one of those things that you attribute to having a new version will happen. Every device will act differently in some aspects, simply due to installed applications, wipes, hardware anomalies, etc. Many will share common issues and flaws as commits get piled on in nightlies (the SVDO fix in tonight's nightly is a good example), but its not always guaranteed. I, for one, had no issues connecting to SVDO on the previous nightly, so the fix wouldnt really apply to me.
Also, he might not be as experienced as some of the rest of us are, but he had the presence of mind to know a bootloop when he saw it, attempted to fix it the easy way by reflashing (and flashing other roms), and wound up having to go the long way home by using odin to stock the phone and start over. He then closed his statement by saying he'd come back in a month when its stable. This isnt any worse than Cartman from south park saying "screw you guys, i'm going home".
Now if he had come in and blurted out "EHRMEGERD I FLASHED CYANOGENMODZ AND NOW MY PHONE IS STUCK FOREVER ON THE LOGO, I HATE YOU ALL, BUY ME A NEW PHONE", we might be having a different discussion. As it stands, someone with at least a baseline knowledge came in and told us about his personal experience with the latest unstable build. Fine. Thats not ignorance. Berating someone for being ignorant, while simultaneously ignoring that they're not ignorant and espousing so-called common knowledge and being completely wrong about it, is relatively obtuse.
So next time you fly off the handle, remember that you're in a community that was founded by people who asked questions and shared our experiences. If you cant say something constructive or help someone along the way, perhaps its best to just not say anything. I'd have a post count in the millions if I spouted off at every single "stupid" post I've seen, every single issue that could have been solved in the search bar, or simply wasted my time in calling someone an idiot. But I kept my mouth shut and only really posted when I could offer a solution to someone or had meaningful (or funny) input on a situation. Maybe you are just having a bad day and felt the need to pipe up, I've read a lot of your posts and just exploding on someone seems a bit out of character. But seriously, before you call someone an idiot next time, consider finding a better way of doing things. You never know who the next great mind of the android community might be, but if we go around calling everyone names for things that we dont agree with, we may never be able to nurture that ability.27New and enhanced:
RIL framework is enhanced to support samsung and sprint changes
external sdcard is back
GPS fixes
Bugs:
Camera is black and broken.
audio is not enhanced for dual mics ( you may get feedback and echoing due to the fact we haven't merge d2 changes over to nexus4's qcom audio HAL)
download:
http://d-h.st/Gt0
