yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] PeterGuru:
My device is an N900W8.

Yes, Root Call Blocker does exactly what the name suggests ... blocks calls. A few years ago I wanted an app to block calls; however, the app had to perform in a very specific way. Let me explain. Back then, when I was looking into such apps, many would block calls, but my phone would still ring briefly before the call was actually blocked ... or the phone would not ring, but the caller would be sent immediately to voicemail, which is NOT what I wanted. With Root Call Blocker, I would never hear anything, and the caller would simply get dead air ... no ringing, nothing! This was perfect for me. I didn't want to hear anything, and I didn't want the caller to be sent automatically to voicemail. Root Call Blocker solved the problem perfectly.

However, I have noticed the call block feature within the phone. Perhaps I should try it to see HOW it blocks calls. Most of the call blocking apps ultimately send the caller to voicemail, which is no good for me. I'll try the built-in feature and let you know.

Peter

Addendum: Unless I'm doing something completely wrong, and I'm quite sure I'm not, the internal call blocking feature isn't even working. I just added my in-laws' home number, and then made a call from their phone to my device, but the call gets through. I even tried a number of different variations of my in-laws' number, and it doesn't matter. The calls still get through. Any ideas?

Addendum 2: I'm going to try a clean re-install of Root Call Blocker to see if there was some kind of glitch with the previous installation. I'll report back later.
[Galaxy Note 3 Android Development] Xelphos:
I installed Root Call Blocker, never had it before and I got the same issues you were having. So there is definitely an issue with Root Call Blocker and CM.

Update: I tried a few other root level call blockers and I got the same "No Service" problem.

Update: Got it working. When I rebooted my phone and Root Call Blocker requested root the android internal server crashed and just went back to the boot animation, at this point I had no service, I put the phone in airplane mode for a few seconds and I had service again. (This may or may not work for you, but it does work for me.)
[Galaxy Note 3 Android Development] gakio12:
There is a call blocker built in to android (or cm, I only use cm lol) now as well, it's in the dialer settings.
[Galaxy Note 3 Android Development] Xelphos:
The CM Blacklist doesn't stop it at system level, if someone who is on the blacklist calls you your phone will ring for a split second and then the phone will auto-hang up on them.
[Galaxy Note 3 Android Development] DavidFlory:
Still no GPS for my hltevzw

I am now on the cm-11-20140308-NIGHTLY and I still am not seeing any satellites much less getting a GPS fix. This is reported from the GPS Status app. Has anyone gotten GPS working for a SM-N900V DevEd? The problem has shown up in all the universal builds. I am getting frustrated. GPS Status reports the sensors and the orientation stuff fine. It does not see any satellites and never gets a fix.

No GPS added to no NFC may force me to jump ship, at least for a while.
[Galaxy Note 3 Android Development] cam30era:
I'm seeing exactly the same. But I like CM11 enough, that I've reverted to the last hltevzw build (0130). OK for now.

I sure hope hashcode is aware of this. I tried to file a bug report from my N3, but it didn't work. Not sure if there's another way?
[Galaxy Note 3 Android Development] PeterGuru:
Yes, I know, but it doesn't work on my device. If you read back a few posts, I discuss this issue. My phone simply keeps ringing, even when the number is on the built-in Blacklist.

See comments below:

Yes, the "split-second" ring is exactly what I don't want, which you seem to understand perfectly. :) For gakio12: Root Call Blocker blocks calls on the system (root) level ... hence the word "root" in the app name; your device won't ring at all.

Peter

---------- Post added at 06:15 PM ---------- Previous post was at 05:54 PM ----------

I'm also on 20140308, and my GPS is working fine. Then again, I have a different device: SM-N900W8. The app I use is GPS Test.

Peter
[Galaxy Note 3 Android Development] wilfredlams:
This merge should fix preferred network options, wait for today's nightly.:fingers-crossed:

http://review.cyanogenmod.org/#/c/60661/
[Galaxy Note 3 Android Development] LillieBennett:
I tried the pacrom but it was working with fixes starting in about 10 sec. Use something like fasterGPS to set the locale and use a satellite checker. I think the status icon is not working.

SM-N900V DE
[Galaxy Note 3 Android Development] DavidFlory:
The problem is CM-11 and the hlte/universal builds. It started with the first universal build. I got a good GPS fix quickly with the last few hltevzw builds. I also got a good fix with Beans TW 4.3 custom ROM (to which I may return).

I have tried faster GPS and tested with GPS Status and GPS test. NO satellites! If you don't detect any satellites you do not get a GPS fix.

Is there anyone with a SM-N900V DevEd who is running a CM-11 hlte/universal build who DOES see satellites?
[Galaxy Note 3 Android Development] dhufford81:
I'm in the same boat, dev edition vzw.
[Galaxy Note 3 Android Development] DACHIGGA:
Dock audio is not working.

Phone appears to detect dock but no audio output goes to the dock (and speaker is silent as well).

So when dock is connected there's no audio through any output. Headphone, Speaker and dock are all silent.
[Galaxy Note 3 Android Development] gakio12:
Nope, that commit just added even more options and now ALL locales result in a force close if you try to change the network type, even US English.

So it made our situation worse.:p
[Galaxy Note 3 Android Development] jetbruceli:
I just want you all to know that I actually download every nightly and back up my stuff. Right before I go and start flashing I read this thread.

It's really pain staking with all the issues that are faced with this device and cm.

So I don't flash and keep my stock rooted debloated tw kk.

I really respect cm and the team who has so much on their hands with this.

I guess I will wait till a rc or stable is released.

Last thing, I really respect you all who flash this and test it. You all are the ones really sacrificing your time to help those like me get a better cm.

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] LillieBennett:
The pacman rom is based on cm11, I have the DE for VZW and I get GPS fix easily. Sorry you felt my post was irrelevant but I will try same with the real McCoy cm11 tonight.

SM-N900V DE
[Galaxy Note 3 Android Development] farfromovin:
The last couple nightlies for me break the cam/camcorder if I dirty flash like you should. Example- I was on 3/7 and flashed 3/8 broke my camera. Clean installed 3/8 and camera is fine. Updated to 3/9 broke my camcorder...

Anybody else? CM nightlies are usually very good to me on almost all my devices.
[Galaxy Note 3 Android Development] PeterGuru:
Standard "dirty" flashing is okay here ...

I haven't had a problem after dirty-flashing the last several builds. Camera/Camcorder is working fine.

Peter
[Galaxy Note 3 Android Development] DavidFlory:
And I will try the pacman rom to see how it works for me. Thanks.
[Galaxy Note 3 Android Development] gakio12:
My camera also force closes since the 03/08 build.
[Galaxy Note 3 Android Development] Whosdaman:
All is fine here
[Galaxy Note 3 Android Development] zmore:
Yeah, looks like the Camera is crashing right after you switch from Pic to Vid mode. There were a few camera changes in the last couple nightlies.

W/dalvikvm(14226): threadid=16: thread exiting with uncaught exception (group=0x41717ce0)
I/OMXNodeInstance( 9921): OMX_FreeBuffer for buffer header 0xb7095b48 successful
...
E/AndroidRuntime(14226): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime(14226): Process: com.android.camera2, PID: 14226
E/AndroidRuntime(14226): java.lang.RuntimeException: startPreview failed
E/AndroidRuntime(14226):	at android.hardware.Camera.startPreview(Native Method)
E/AndroidRuntime(14226):	at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:256)
E/AndroidRuntime(14226):	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(14226):	at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(14226):	at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 892): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher

FWIW, if you Clear Data for the Camera, you can still take pics, just don't switch to video mode. Also, other camera apps will still work fine for video - I use Camera Awesome (because I love its 5-second video pre-buffer feature so much).
[Galaxy Note 3 Android Development] PeterGuru:
I was wrong ... Camcorder not working ...

My comment above is incorrect. Although my camera is working, the camcorder is not.

I'm experiencing the same thing.

Peter
[Galaxy Note 3 Android Development] skadude66:
Is anybody here running SuperSU successfully with the nightlies? I restored all of my apps using the built-in Superuser from CM11, and then I go into SuperSU to update the binary (I want to use SuperSU as my main Root app) and update the binary successfully. All is well, but then it seems that Superuser will then take over as my main root app and then I need to continuously update the SuperSU binary.

Does anybody have any idea why SuperSU is not sticking as my root app, or how to "disable" Superuser?
[Galaxy Note 3 Android Development] gakio12:
Found this under a rock lol. I'm not sure if it works, but it is supposedly a fix for GPS on the unified builds.

http://xdaforums.com/showpost.php?p=50436908&postcount=4711

EDIT: just realized that was for the nighties to temesek's build, but it was mentioned in hashcode's Verizon thread.
[Galaxy Note 3 Android Development] cam30era:
I tried this after the first unified nightlies, and it didn't work for me. But it would be interesting if another Verizon user tried it.

And thanks for the suggestion. It's heartening that someone is listening.
[Galaxy Note 3 Android Development] gakio12:
Just a few more things to report:

The Samsung sensors don't appear to be working (step counter). I use a step counter, which worked great before the unified builds, but now it only records maybe 1-5 steps (opposed to 5000) through a day. Even if the sensors that stop working after deep sleep are working, step counter isn't.

The battery life is great when the screen is off. With the screen on, the battery drains 1% every 3-5 minutes. I can sit there watching the battery drain :p
[Galaxy Note 3 Android Development] TSman74:
Gave it a shot on both newest nightlies of CM and Pac but no dice. Used Faster GPS and GPS Status to test. But thanks for looking out though!
[Galaxy Note 3 Android Development] lawonga:
Anyone's phone freezing after a while or after heavy usage, and anyone's phone's spen not working after usually a nights sleep?
[Galaxy Note 3 Android Development] xueyao:
Working well here with lean kernel
[Galaxy Note 3 Android Development] PeterGuru:
Camcorder still not working with 20140310

My camcorder is still not working with 20140310.

As before, the camera works when you open it, but if you then switch to video, the app force closes. Afterwards, every time you open the app it will force close. The only solution, as previously suggested by zmore, is to Clear Data for the Camera app, and then do NOT switch to video mode.

Peter
[Galaxy Note 3 Android Development] sauron82:
I flash SuperSU after I flash a rom. Titanium doesn't like the built-in Superuser binary (not sure why it hasn't been updated lately), so I use SuperSU. Rom -> Gapps -> Kernel (if using a different kernel than rom default) -> SuperSU. I'm using the XDA app so I can't upload the actual flashable zip, but if you do a search for "latest flashable SuperSU" I'm sure you'll find it. I think latest version is 1.93.

Also, if you dirty flash an update, you'll need to reflash SuperSU.
[Galaxy Note 3 Android Development] LillieBennett:
GPS gets a couple of sats but not enough for fix on cm11 but pac works. Noticed some differences between gps.conf so I'll try some swaps.

SM-N900V DE
[Galaxy Note 3 Android Development] skadude66:
You're not running into any issues with Superuser and SuperSU conflicting??
[Galaxy Note 3 Android Development] sauron82:
No, SuperSU just takes over.

Click thanks if I helped you.
[Galaxy Note 3 Android Development] skadude66:
Thanks, I'll try that out.
[Galaxy Note 3 Android Development] TSman74:
Wish I could duplicate your results. Running touchwiz gives me a fix on 18/22 sats. I get 0/0 on CM and Pac. Can't even see sats. Why does this seem only to be an issue on vzw though?
[Galaxy Note 3 Android Development] cam30era:
Could you share what you are doing on CM11 and Pac to get a couple of satellites? My phone, on any of the unified nightlies, can see no satellites at all.
[Galaxy Note 3 Android Development] LillieBennett:
Don't know but we do have extra hardware being fully compatible with CDMA and GSM nets. I tried swapping gps.conf files cm11 claims networks disabled so no joy.

It's troubling that you don't with pacrom, kinda indicates variations in hardware. My DE is from the first batch. With pac I just used Faster GPS but suspect it would have worked had I not. With cm11 its not working. I have the mje radio software. Has anyone tried different kernals?

SM-N900V DE
[Galaxy Note 3 Android Development] cam30era:
My DE is from the first day of availability, 11/4 if I remember right. I'm also on MJE modem. And I tried CM11 with imoseyn's kernel, without luck. I'm traveling for the next week and need GPS. Maybe I'll try PacRom when I get back, if CM11 GPS isn't working. Thanks for the feedback.

Edit: I'm currently using the last pre-unified hltevzw CM11 build (0130). It works quite well. Only anomoly is a FC or two when trying to open settings. I'd recommend it to any Verizon CM11 user who needs GPS.
[Galaxy Note 3 Android Development] TSman74:
Same here on all counts.
[Galaxy Note 3 Android Development] cam30era:
I'm currently using the last pre-unified hltevzw CM11 build (0130). It works quite well. Only anomoly is a FC or two when trying to open settings. I'd recommend it to any Verizon CM11 user who needs GPS.
[Galaxy Note 3 Android Development] TSman74:
Btw, what recovery are you using?
[Galaxy Note 3 Android Development] LillieBennett:
I like TWRP the best, currently 2.7 for 4.3.

SM-N900V DE
[Galaxy Note 3 Android Development] TSman74:
I'm using CMW. How about you [MENTION=3209971]cam30era[/MENTION]? Do you think that may be the difference?
[Galaxy Note 3 Android Development] LillieBennett:
Would that be the PhilZ touch or other CWM. The TWRP is still the tmo version, I keep the PhilZ in case I get trouble with the asserts.

SM-N900V DE
[Galaxy Note 3 Android Development] TSman74:
CWM touch from the play store. Had PhilZ before that and twrp before that. Might go back to twrp.
[Galaxy Note 3 Android Development] cam30era:
TWRP 2.6.3.10. And no, recovery has no effect on ROM/OS once it's booted up.
[Galaxy Note 3 Android Development] freeman_g:
Just bought n9005 after my S4 (i9505). Unfortunately CM for n9005 is much less optimized and has more bugs but I still do not want to use TW.

Have the same issues with camera as described above but would like to understand if it is possible to activate HDR in stock CM camera? I just do not have such an option (used to have it in i9505). Or the only way is to use third-party app?
[Galaxy Note 3 Android Development] Kevin36:
I have issues during a call i get no screen i have to press home buttons to get screen to turn on. It only turns on when the person hangs up. What can I do?
[Galaxy Note 3 Android Development] Darietto:
do you mean that when the phone rings the screen doesn't turn on untill you hit a button? if yes i have the same problem
[Galaxy Note 3 Android Development] Kevin36:
During a call i cannot acces my screen it stays black. The other person hangs up and i get my screen back
[Galaxy Note 3 Android Development] gakio12:
It's a problem with your proximity sensor. Take a can of compressed air and blow it into the cracks around it. That is a common issue with the note 3; it's a design flaw. Dust can sometimes block the sensor
[Galaxy Note 3 Android Development] testmonkey1:
Any suggestions about the "fixed" preferred network?
[Galaxy Note 3 Android Development] mrjaydee82:
Quick question I haven't heard anyone mention it...is it just me on T-Mobile 4.4.2 bootloader have issues with lots of sound distortion since updating the T-Mobile bootloader on all aosp ROMs?
[Galaxy Note 3 Android Development] PeterGuru:
My device is working properly; it's not exhibiting the behaviour noted above.

Peter

---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------

I know this has been mentioned a lot, and it seems to have solved a similar problem for many others; however, seeing your Post Count and Thanks Meter, I'm sure you already know about it.

Try disabling Touch sounds in Settings>Sound.

Peter
[Galaxy Note 3 Android Development] mrjaydee82:
Yeah that does help but not a cure...I'm going through some junk to try an squash it and fix..but no go...even messed around with the kernel and still no go...well I'll continue to mess around.. Went to go work on my ROM yesterday lol and noticed it. Thanks
[Galaxy Note 3 Android Development] Kevin36:
Thanks alot opened my note cleaned the area on speaker and sensor good as new thanks alot
[Galaxy Note 3 Android Development] PeterGuru:
Video still not working with 20140311

The camcorder (video) is still not working with the 20140311 build. Like before, if you open the camera app and then select video, the app force closes. It will then continue to force close every time you open the app unless you first to into Settings>Apps>Camera, and then "Clear data."

One other thing ...

The following issue has been ongoing as long as I can remember, and it's still there. If you go into Settings>More...>Mobile networks>Nework operators, the search for networks will begin, but it continues to return the error message, "Error while searching for networks." The subsequent list is blank; however, if you then select Choose automatically, it will correctly return the phrase "Registered on network."

Peter
[Galaxy Note 3 Android Development] wilfredlams:
If we merge this to hlte, it might fix the problem we currently have.

http://review.cyanogenmod.org/#/c/60871/
[Galaxy Note 3 Android Development] wilfredlams:
Just did a compile and can confirm that does fix the fc completely.

Edit:

Just submitted it to gerrit and hope they will merge it. :)

http://review.cyanogenmod.org/#/c/60999/
[Galaxy Note 3 Android Development] SleemLDJ:
Hi guys. I'm about to make a move from my Sony Xperia Z1 to Galaxy Note 3 for the purposes of installing cm11 on it

How does it hold up as a daily driver on this device as of today please?
[Galaxy Note 3 Android Development] testmonkey1:
Quite usable as a daily driver, but it does get sketchy at times.
[Galaxy Note 3 Android Development] SleemLDJ:
Thanks for replying me. As long as the everyday stuff works. Camera, call, SMS, good sound output, optimised battery, good performance. I think I'm good.

I wanna work on a stock android for a bigger screen than my Sony Xperia Z1
[Galaxy Note 3 Android Development] xueyao:
Get a pro 2 or z2. Samsung has the worst developer support. I bet that the z2 and g2 pro will have a better aosp build in a month than note 3. Plus z1 has aosp builds by Sony, while Samsung basically hates the dev community. Don't change, performance of z1 will be much better in due time than note 3 aosp. Unless u don't mind using touchwiz.
[Galaxy Note 3 Android Development] testmonkey1:
I don't agree with the poster above me. Sure, Samsung does hate the dev community but we have great developers on the Note 3 at the moment.

Yeah the so-called everyday stuff works and everything else works also :D But you do get the occasional bug, FC and what not here and there. New builds sometimes break stuff, etc. the reason I'm currently experimenting with different builds/kernel combos. Definitely usable as a daily driver, however if you want 100% stability I would stay with Stock TouchWiz for now (which by the way for the 4.4 KitKat update is pretty damn smooth and great, would use it myself it it wasn't for all the restrictions/fugly UI)
[Galaxy Note 3 Android Development] SleemLDJ:
This makes sense. No to touchwiz. Lol. I was just think about the same after reading up some more stuff on Google. It seems to be more of a daily driver on the z1 than the note 3

---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------
[Galaxy Note 3 Android Development] jetbruceli:
Maybe not the place but if you didn't know that samsung has issues with most of their products and source than you must live in a box.

I didn't buy a note 3 to put aosp on it. It's fun to play with it but not practical.

If you wanted the power of the note with a huge screen and aosp support than you should have gotten a zultra

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] Khizar:
I understood 2 things from your post.

1. You prefer tw over AOSP cuz you need the features of tw.

2. Due to your need you feel everyone that is using AOSP on their Note3 isn't using their device to its true potential.

I will just say this, it's your opinion that note 3 is better on tw, fine. Nobody will argue with you on that but don't claim your opinions to be facts.

It isn't "practical" to run AOSP on the note? Maybe for you but for others that don't care about sapple bloat it is practical. You need to understand everyone wants different things from their phone, you need the tw gimmicks and i couldn't care less about them, well ok actually that isn't completely true, I love the MW feature. That's the only reason why I keep switching between AOSP and tw. So in the end it depends on each use whether they want to use tw or AOSP.

As for the comment that users should have gone with the Z ultra if they wanted "power of the note with a huge screen and AOSP support"...I don't even know how to respond to that. You are comparing maybe the worst Sony device to the best android phone that's out as of right now, that comment didn't even make sense...

PS- Now as this is the dev thread we should stop with the OT and stay on the topic at hand...

Sent From My SM-N9005 To All You Wonder Nobodies!!
[Galaxy Note 3 Android Development] PeterGuru:
Camcorder (Video) still not working on 20140312

Just to report ... the camcorder (video) is still not working on the latest build, 20140312.

Like before, the app will force close if you select video, and if you then try to re-open the app, since it is now in "video" mode, you will forever get a force close. To fix it, go into Settings>Apps>All, find the camera app and then select "Clear data."

Peter
[Galaxy Note 3 Android Development] PeterGuru:
Network search error ...

I wrote the above post a day or so ago. Is anyone else having the same issue?

Peter

P.S. Overall, I'm not having any connectivity issues, and my device quickly connects to my provider, Rogers. I'm simply posting this to find out of others are having a similar "network search" issue.
[Galaxy Note 3 Android Development] siraltus:
If you're on a T-Mobile Note 3, here's relief from TW fugliness: http://xdaforums.com/showthread.php?t=2676315
[Galaxy Note 3 Android Development] wilfredlams:
Yes, this issue has been happening since day 1, I had never been able to search for network on this phone with any cm base rom.
[Galaxy Note 3 Android Development] wilfredlams:
Preferred network settings fix has been unified for the d2, jflte and hlte and had been merged, it should be in the next nightly.:D

http://review.cyanogenmod.org/#/c/61025/

http://review.cyanogenmod.org/#/c/61027/

http://review.cyanogenmod.org/#/c/61026/

http://review.cyanogenmod.org/#/c/61030/