[GUIDE] Everything we know so far for DEVELOPER EDITION NOTE 3

[alexp1289]

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 is 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.




I assumed you needed to boot into 3.x first for the fix to work. Data about your system apps is also 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.



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.



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.



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


Personally, I think if you have your device working you shouldn't risk a clean flash.



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.

I may not know very much about ROMs and android but I would like to speed up support for us as fast as possible. Sorry for being frustrated earlier and I realise not everything everyone does is able to be seen. That was an oversight on my part and I'm sorry. I do however believe that we need our voices and logs seen/heard by as many as possible that could help. The squeaky wheel gets the grease

 

[capnkrunch]

Hey, hey everyone. I have a couple test builds in the works (it takes my computer forever to finish building). In the meantime, I'd like some logcats. Can someone get me a logcat of a clean flash of current Temasek with the unrecognized SIM problem AND a logcat of a working setup using the clean flash 3.x, dirty flash current fix? Please use "logcat -v long" to grab them (it formats the log a little nicer). Use adb if you can't get it from your phone (actually I'd prefer you use adb either way). See [Tutorial] How To Logcat if you need help.

@DavidFlory: I already have a logcat of your SIM not registering (from Temasek's thread). I totally understand if you don't want to risk breaking things with a clean flash and hope that the 3.5 -> current fix works again. Would you mind at least grabbing a logcat of your currently working setup? For that please do NOT use "-v long" since your old one didn't use that either ("-v long" is nice but comparing ones formatted the same way is nicer).

EDIT: More detailed instructions *PLEASE FOLLOW*
Using adb
1. Reboot phone
2. Wait for SIM error or network to connect
3. Connect to computer as soon after as possible
4. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log
5. Toggle airplane mode
6. Stop logcat as soon as you get the SIM error or reconnect to the network

Using phone
1. Reboot phone
2. Wait for SIM error or network to connect
3. Open terminal emulator as soon as possible
4. Grant the shell root with "su"
5. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log
6. Toggle airplane mode
7. Stop logcat as soon as you get the SIM error again or reconnect to the network

Please use the same method for both logs. This means if you can't get terminal emulator installed (or CM's built in terminal enabled) AND granted superuser permissions when you get the SIM error you need to also use adb for the working log. Please pull logs from a system that's as clean as possible (do this before installing any apps). I'd prefer you use adb to get logs. Please make sure you aren't doing anything else before or during the logcat. Please do the steps in order and as quickly as possible. Please make sure the log's name identifies if it is from the working setup or the broken one.

EDIT 2: Please grab a logcat of 3.x as well. Follow the same instructions above only instead of waiting for the SIM error wait for the com.android.phone FCs. Overall I'd like you to clean flash current Temasek, get a log, clean flash 3.5, get a log, dirty flash current, get a log.

 

[alexp1289]

Hey, hey everyone. I have a couple test builds in the works (it takes my computer forever to finish building). In the meantime, I'd like some logcats. Can someone get me a logcat of a clean flash of current Temasek with the unrecognized SIM problem AND a logcat of a working setup using the dirty flash 3.x, clean flash current fix? Please use "logcat -v long" to grab them (it formats the log a little nicer). Use adb if you can't get it from your phone (actually I'd prefer you use adb either way). See [Tutorial] How To Logcat if you need help.

@DavidFlory: I already have a logcat of your SIM not registering (from Temasek's thread). I totally understand if you don't want to risk breaking things with a clean flash and hope that the 3.5 -> current fix works again. Would you mind at least grabbing a logcat of your currently working setup? For that please do NOT use "-v long" since your old one didn't use that either ("-v long" is nice but comparing ones formatted the same way is nicer).

EDIT: More detailed instructions *PLEASE FOLLOW*
Using adb
1. Reboot phone
2. Wait for SIM error or network to connect
3. Connect to computer as soon after as possible
4. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log
5. Toggle airplane mode
6. Stop logcat as soon as you get the SIM error or reconnect to the network

Using phone
1. Reboot phone
2. Wait for SIM error or network to connect
3. Open terminal emulator as soon as possible
4. Grant the shell root with "su"
5. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log
6. Toggle airplane mode
7. Stop logcat as soon as you get the SIM error or reconnect to the network

Please use the same method for both logs. This means if you can't get terminal emulator installed (or CM's built in terminal enabled) AND granted superuser permissions when you get the SIM error you need to also use adb for the working log. Please pull logs from a system that's as clean as possible (do this before installing any apps). I'd prefer you use adb to get logs. Please make sure you aren't doing anything else before or during the logcat. Please do the steps in order and as quickly as possible. Please make sure the log's name identifies if it is from the working setup or the broken one.

Adb over USB connected to a PC is probably the only way to get a log of the issue. When I did a clean flash of temasek 7.0 cm12 I couldn't even get past the second part of the phones setup it would try to detect the network at the second setup screen (after choosing language). Not sure if the kernel puts the log somewhere in the root directory because getting past that second screen without a reboot/screen freezing was impossible for me. If the kernel does automatically save a log in the filesystem could it be accessed via adb in download mode? Or via adb connection in twrp?

 

[capnkrunch]

Adb over USB connected to a PC is probably the only way to get a log of the issue. When I did a clean flash of temasek 7.0 cm12 I couldn't even get past the second part of the phones setup it would try to detect the network at the second setup screen (after choosing language). Not sure if the kernel puts the log somewhere in the root directory because getting past that second screen without a reboot/screen freezing was impossible for me. If the kernel does automatically save a log in the filesystem could it be accessed via adb in download mode? Or via adb connection in twrp?

Via adb it should be saved on your computer regardless of freezing or reboots. (I'm pretty sure) logs are not saved on your phone after a random reboot but in that case you can grab /proc/last_kmsg for me as well (this is a very cool Samsung kernel debug feature that saves dmesg from RAM in the event of a kernel panic triggered reboot; I think that's how it works at least). You can use a root explorer to copy it to your phone's storage or sdcard or use "adb pull". It sounds like "adb pull /proc/last_kmsg /path/on/computer/last_kmsg" will be the way to go.

Actually, between 3.5 and 5.9 the kernel make command line was changed in a commit that said something like "fix modem." I don't think this is the problem commit but depending on how last_kmsg looks I might give you a kernel built with the old command line to test (building a kernel takes infinitely less time than building a whole rom).

If you report random reboots to Temasek (or most devs really) you know they want that last_kmsg. Last I checked CM has it disabled, though I haven't looked through their kernel source in KK. Most kernel devs enable it as do a number of custom roms.

EDIT: If it is rebooting before you can connect your USB per my instructions then just do the initial reboot while already connected or connect before advancing to the second setup screen. If the logcat still doesn't write to your computer then try stopping the logcat before the freeze/reboot but as close to where it normally happens as possible. If you need deviate from the instructions in my last post, please let me know what happened and what you did (even if all you did was what I said in this post). I am far from a real dev so there's a good chance I won't pick up that kind of thing just from reading your logs.

On a different note, these test builds I'm working on are straight CM sources, not Temasek. The idea being the CM maintainers might be more willing to help if we gather data using their code base. Plus if we, by some miracle, get it working and get the fixes upstreamed to CM it will eventually be merged by everyone else as well.

 

[DavidFlory]

@capnkrunch do you think that the following would probably restore my current environment including no SIM problems?
* Take a complete TWRP backup.
* Clean flash v3.5 and initialize it.
* Restore the backup.

If yes, then I should be able to test by doing a clean flash of v7.3 or v7.4 and taking a logcat of SIM problem.
Clean flash v3.5 and initialize then restore as above and take a logcat.

 

[capnkrunch]

@capnkrunch do you think that the following would probably restore my current environment including no SIM problems?
* Take a complete TWRP backup.
* Clean flash v3.5 and initialize it.
* Restore the backup.

If yes, then I should be able to test by doing a clean flash of v7.3 or v7.4 and taking a logcat of SIM problem.
Clean flash v3.5 and initialize then restore as above and take a logcat.

I want to say it should but since I don't really understand how or why the fix works really your guess is as good as mine. For now if you can just pull a logcat of your working setup I can get a better handle on what's going on. I'd rather wait for someone who doesn't currently have a working Lollipop setup to pull back to back broken/working logs than risk your system breaking.

UPDATE: I realized I'd like a 3.x log as well. I updated my post with the instructions to include that. If someone already has already posted one from back in the day could you please point me to it?

UPDATE 2: My first test build is done. This was build using straight CM sources and NC4 blobs. It boots on my phone but says my SIM is unrecognized. Please clean flash for testing. Please DO NOT flash GApps or SuperSU for testing purposes. Please pull a log with adb and "-v long" whether or not you have any issues. If you feel like doing some extra work, I'd like someone to try clean flashing Temasek 3.5 (and pull a log while you're there) then dirty flash this on top and grab a log.

https://www.androidfilehost.com/?fid=95916177934525484

A second build using NK1 blobs that I'm cautiously optimistic about is in the works right now.

As always, my sources are at my github:
https://github.com/capnkrunch/android_device_samsung_hltevzw/tree/cm-12.0-nc4
https://github.com/capnkrunch/proprietary_vendor_samsung/tree/cm-12.0-nc4

I also added a repo with my local manifest in case anyone wants to get in on this
https://github.com/capnkrunch/local_manifests

UPDATE 3: Here's the NK1 test build. Once again, it booted but failed to recognize my SIM. Source is the same, just on the NK1 branch.
https://www.androidfilehost.com/?fid=95916177934525638

UPDATE 4: If you didn't realize, this project is over due to lack of interest, lack of time, and that sweet, sweet Nexus 6 that's in the mail.

 

[alexp1289]

If I could find a buyer for my Dev note 3 I'd sell it and get nexus 6. It's been fun guys but time to get out.

 

[droidstyle]

why the Nexus 6 is buggy...a friend of mine has one and bitches about it.

 

[dhufford81]

why the Nexus 6 is buggy...a friend of mine has one and bitches about it.

I have one and love it. It's not buggy anymore than any other android phone I've owned. Especially the note 3 lol.

 

[untouchablez]

I've been thinking about moving on from my DE N3 as well. Not sure if it's worth it to get a DE N4 since there not much development going on over there since the retail is locked up tight and all the good developers have pretty much moved to N6 or other carriers..

I can live with no SD card slot on the N6 but the lack of a removable battery is the biggest hurdle for me. Popping in a freshly charged battery is so damn convenient lol.

 

[dhufford81]

I've been thinking about moving on from my DE N3 as well. Not sure if it's worth it to get a DE N4 since there not much development going on over there since the retail is locked up tight and all the good developers have pretty much moved to N6 or other carriers..

I can live with no SD card slot on the N6 but the lack of a removable battery is the biggest hurdle for me. Popping in a freshly charged battery is so damn convenient lol.

Turbo charge is nice, makes it easier to deal with.

 

[untouchablez]

To those who have installed CM12, is it still pretty buggy? I've been running Eclipse for a while now & it's been rock solid but I wanted to try out some Lollipop newness.. Any recommendations on which builds are pretty stable at the moment? I'm already running NK1 baseband and 2.8.5 twrp.

 

[DavidFlory]

To those who have installed CM12, is it still pretty buggy? I've been running Eclipse for a while now & it's been rock solid but I wanted to try out some Lollipop newness.. Any recommendations on which builds are pretty stable at the moment? I'm already running NK1 baseband and 2.8.5 twrp.

I am using v8.8 as my daily driver. Two suggestions. Read my older posts about how to avoid problems recognizing your SIM and getting an LTE/4G data connection. Do not do clean flashes after your first one.

 

[untouchablez]

I am using v8.8 as my daily driver. Two suggestions. Read my older posts about how to avoid problems recognizing your SIM and getting an LTE/4G data connection. Do not do clean flashes after your first one.

Yeah I saw some of your other posts already.. Going to try a fresh install of 3.5 & then dirty flash straight to 8.8... What kernel are you using?

Update: so I downloaded 3.5 and 8.9 for hltevzw but I've always had hltetmo twrp recovery and twrp is saying the binary failed to execute b/c the package is for hltevzw but my recovery is hltetmo... I didn't update twrp to hltevzw since I'm still on 4.3 bootloader so I used the tmo twrp... Do I just need to use hltevzw specific twrp even though I'm on 4.3 bootloader?

Sorry for the noobish questions, it's been a while since I've flashed anything

 

[DavidFlory]

Yeah I saw some of your other posts already.. Going to try a fresh install of 3.5 & then dirty flash straight to 8.8... What kernel are you using?

Update: so I downloaded 3.5 and 8.9 for hltevzw but I've always had hltetmo twrp recovery and twrp is saying the binary failed to execute b/c the package is for hltevzw but my recovery is hltetmo... I didn't update twrp to hltevzw since I'm still on 4.3 bootloader so I used the tmo twrp... Do I just need to use hltevzw specific twrp even though I'm on 4.3 bootloader?

Sorry for the noobish questions, it's been a while since I've flashed anything

I am using Temasek's builtin kernel. Works fine for me.
I am using openrecovery-twrp-2.8.5.0-hltevzw-4.3.zip with no problems. You should be able to get it from this site.
http://www.techerrata.com/browse/twrp2/hltevzw

 

[untouchablez]

I am using Temasek's builtin kernel. Works fine for me.
I am using openrecovery-twrp-2.8.5.0-hltevzw-4.3.zip with no problems. You should be able to get it from this site.
http://www.techerrata.com/browse/twrp2/hltevzw

Sweet! I'm going to check it out later. Appreciate it!! Thanks

 

[untouchablez]

So I was able to get temasek cm12 installed and wow that is a pretty smooth & polished rom, I was definitely impressed. However, I had to go back to Eclipse bc I was having issues with data connectivity. Clean installed 3.5 then dirty 8.9 and the LTE would be fine for a while then it would dissappear and wouldn't reconnect no matter how many times I rebooted, toggled airplane mode or changed to LTE from global etc etc.. I tried to rinse & repeat with 3.2 and 3.5 then dirty to some of the newer builds but the end result was the same... Sucks going back to 4.4 but I needed a stable phone bc of work..

 

[DavidFlory]

So I was able to get temasek cm12 installed and wow that is a pretty smooth & polished rom, I was definitely impressed. However, I had to go back to Eclipse bc I was having issues with data connectivity. Clean installed 3.5 then dirty 8.9 and the LTE would be fine for a while then it would dissappear and wouldn't reconnect no matter how many times I rebooted, toggled airplane mode or changed to LTE from global etc etc.. I tried to rinse & repeat with 3.2 and 3.5 then dirty to some of the newer builds but the end result was the same... Sucks going back to 4.4 but I needed a stable phone bc of work..

Which modem are you on?

 

[untouchablez]

Which modem are you on?

NK1

 

[DavidFlory]

NK1

Did you give the phone a chance to settle into v3.5 before you flashed v8.x? I needed to turn on WiFi and toggle airplane mode a few times before I got away from phone problems. It never got happy with v3.5 but then the dirty flash of a v8.x worked for me. I am using it as my daily driver with no problems. I am wondering if you might have gone strait from v3.5 to v8.x without a reboot or two and some time...perhaps 20 or 30 min.