You are probably correct. However, given the number of downloads of Temasek's hltevzw build on Basketbuild (5 just now compared to 467 for the hlte version) I don't think our version is high on his priority list. We should be thankful he builds for us at all.
It could well be that the problem arose from a change in the CM-12 base that would have to be teased out and reverted. That takes time. One approach would be to clean install v3.5 and test. Then repeat, carefully, for each successive version until the problem arises. You then would have two adjacent versions, one good and the next bad. You then go into GitHub and see exactly what changed between the two version and look to see where the problem lives. My guess is that would require a serious developer with time on his hands.
I am not he. Are you?
We have a good solid work-around for the problem now. That removes the urgency. Feel free to tackle the problem yourself but please stop asking others to do it for you.
This is 100% true. Also consider that this is a variant specific issue. If there's a commit in a shared repo (i.e. the Telephony repo) that if reverted fixes the issue for us then they would also need to make sure it didn't cause issues for the other variants.
Some additional information:
You think I'd be fine on a clean flash? Dirty flashing would just over write the buggy files anyways so clean flash should be just fine right?
Sounds like to clean flash a 3.x then without booting dirty flash 6.9+. To me, this equates to a clean flash since data hasn't been modified between the 2 flashes.
I assumed you needed to boot into 3.x first for the fix to work. Data about your system apps is stored in your /data partition and created on the first boot. When you dirty flash this data persists. My thought is that some data from com.android.phone or com.android.telephony persisting is how the fix works.
Why does no one clean flash and grab a log for temasek? Dirty flashing is just a bandaid.
DavidFlory has reported the bug to Temasek with relevant logs. LillieBennett doesn't have her SIM card in her Note 3. I don't have this issue on my phone. Like I said before this issue is really something that CM should be working on, not Temasek. There is no CM12 support for us though.
But I don't get why if it has worked then why all of a sudden we need blobs from Samsung/Verizon LP? Something seems like it just got screwed up between versions.
3.5 and under were bugged to crap (GPS issues, video stream issues, com.android.phone FCs). This is why Temasek stopped building. This is why CM has no official support. We are using Sprint blobs currently (this was the major change between 3.5 and 5.9) but I suspect there's some kind of incompatibility that won't be resolved until we get Verizon blobs.
Yes but sitting around saying it's not a priority with or thumbs up our butt does nothing. I want to find someone that will help once I gather all the documentation. Just like I did with bigbiff everyone on here was saying we had no recoveries to use so I got mine and contacted the right people and found bigbiff. Gave him my recovery from stock and bam had something us 4.4 bootloader people could use. Meanwhile it sounded like others were just giving up. Sorry if I sound frustrated but that's because I love my Dev edition and would like all of use to keep them as long as possible. PLEASE don't take any of this out of context you and all the others are a big help I just get frustrated when it seems like no ones being proactive. Right now it feels like everyone wants to play the waiting game. I want to get the logs and everything to the people that need them so they can look into it when there's time. Sorry for freaking out. Rant over!!
I would maybe try getting in touch with the CM maintainers (the Temasek thread mentions most of them; Tony Laher (slayher) is the main one). At the very least, they could probably provide some good insight into why they don't offer CM12 for us and if/when they will. I would grab logs of a clean flash of current Temasek, clean flash of 3.5 Temasek and dirty flash of current Temasek on top of 3.5. You could also grab a log of cmRemiX. Let them know that current Temasek builds use the Sprint NH4 blobs and Temasek 3.5 and cmRemiX uses the Verizon NC4 blobs. Use adb to grab logs if you are getting reboots. Use logcat -v long (this makes them look a bit nicer). You could also try deleting that newril line from build.prop like I mentioned a couple pages ago and report back.
As far as giving up goes, I think it's kind of unfair to say that; sometimes you might not realize what's going on. Red_Out and DavidFlory nailed down a workaround for the SIM issue. radionerd gave me a workaround for 5GHz WiFi. I put in quite a bit of work (all easy stuff for a real dev but it was hard for me) that resulted in Temasek building again and I spend more time than I should staring at the relevant repos and looking through logcats. And that's only off the top of my head of things I am aware of. Case in point, I didn't realize all you did getting TWRP up for 4.4 (thanks by the way). It's not a large community but I like the people here. It's frustrating for everyone but especially since there are so few of us it's important to get along.
P.S. I was looking at CM's vendor repo. They are still using NC4 blobs. I think jumping to using Sprint blobs before trying NK1 may have been jumping the gun somewhat. If I have time this weekend I'll do a test build with NK1 blobs. No guarantees though, real life and whatnot.
@other people
I have not done a clean flash since I flashed v3.5 which seems to have been the thing that fixed my SIM issues. I did flash the NK1 modem but since the incremental dirty flashes are working so well I have not clean flashed since. Temasek just said to look for 7.0. Perhaps then I will test.
Personally, I think if you have your device working you shouldn't risk a clean flash.
I just wanted to update those who had helped me a few pages back. I installed Alliance and LK 3.16, and honestly, I didn't know I could be so happy with a TW rom. =) This phone will carry me for at least another year or so (unless it breaks, or the new hotness is released). I sincerely appreciate the help.
Cheers!
Awesome! Alliance is a sweet ROM. Those guys did great work. When I first ran it I thought "Wow. This is the first TW rom I've tried that seems like more than just stock with a system app or two removed." leankernel is a sweet kernel. I've liked imoseyon since 2011 when I used to read his blog. I'm currently running this setup as well.
