yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] PeterGuru:
Some corrections to FAQs

Concerning the 3rd entry about recoveries. I'm using TWRP v2.6.3.7, and I simply flashed the unified CM11-20140218 through it. It worked very well.

Concerning the 6th entry about downgrading from 4.4 to 4.3 bootloader. Yes, you can, if you have a Canadian variant (SM-N900W8). We can upgrade and downgrade at will.

Just thought you'd like to know.

Peter
[Galaxy Note 3 Android Development] fuhayer:
can i install this on N900 Exynose device ?
[Galaxy Note 3 Android Development] luqman98:
No. Exynos version is different at all.

Sent from my highly pimped Galaxy Pocket.

1. Love doesn't need any reason.

2. Wanna speed up 3G (not 4G LTE)?

Here it is:

http://xdaforums.com/showthread.php?t=2586876

3. My blog

4. Press the thanks button if I really helped/assisted you.
[Galaxy Note 3 Android Development] GigabitEthernet:
FAQ updated :).
[Galaxy Note 3 Android Development] fuhayer:
so is there a way to install CM on my N900 Exynos device ?
[Galaxy Note 3 Android Development] GigabitEthernet:
No. This thread is for the Qualcomm version of the Note 3 only.
[Galaxy Note 3 Android Development] jetbruceli:
Not yet unless you know what your doing and can make it yourself

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] wilfredlams:
I am getting an error in cwm v6.0.4.7 E: failed to open /data/media/0/0/cmupdater/cm-11-20140219-NIGHTLY-HLTE.ZIP (No such files or directory) when trying to update from cmupdater. anyone had the same problem?
[Galaxy Note 3 Android Development] GigabitEthernet:
Do a clean flash.

All, is the time issue still an issue on the latest nightly (19/02/14)?
[Galaxy Note 3 Android Development] GigabitEthernet:
Am reporting, just waiting for devs to come online so I can inform them.

Also, I believe the audio channels are reversed on the headphones. Can anyone confirm this?
[Galaxy Note 3 Android Development] wilfredlams:
Na just tried with twrp and works well, I think it's a cwm issue. Yes time is still an issue, just confirmed.
[Galaxy Note 3 Android Development] shingers5:
just change to manual clock in date and time settings and that goes away for now................i know its not a fix but its a way round it for now
[Galaxy Note 3 Android Development] Robster83:
Change log for todays Nightly (19th Feb): http://jenkins.cyanogenmod.com/view/All/job/android/59648/artifact/archive/CHANGES.txt

The change log txt file in the first few posts only seems to apply to the original build, not subsequent updates, so is pretty useless.
[Galaxy Note 3 Android Development] GigabitEthernet:
Thank you. Post updated :).
[Galaxy Note 3 Android Development] amoblox:
Since the merge on 2/18, Textra has been freaking out a bit. When I open the emoji panel, the conversation starts stretching and bouncing like crazy.

Not sure if it has to do with DPI or font, but I've played with the font in both the app and Display settings on the ROM and it doesn't seem to help.

On an SM-N900T (T-Mobile).
[Galaxy Note 3 Android Development] zmore:
The "multi-color-garbage-screen-of-death" thing happened to me as well last night (on 2/18 hlte) after a marathon Chrome session. Buttons and vibration feedback were still responsive, but the screen went whacky, so had to force-reboot. A very similar bug was present in 1/30 hltetmo too - only difference being the screen went black vs multicolor. Happens about once every day or two for me on the CM kernel, but those who switched to temasek's kernel say it never happens, so, there's that.
[Galaxy Note 3 Android Development] springer.music:
The LED is being fixed :good:

http://review.cyanogenmod.org/#/c/59879/
[Galaxy Note 3 Android Development] Khizar:
You could have read the last page or so... And you would have seen that, that is a known bug and the link to the commit that will hopefully fix it was also posted by a user... :rolleyes:

Sent From My SM-N9005 To All You Wonder Nobodies!!
[Galaxy Note 3 Android Development] xueyao:
Hey guys, how's the 6 march build? Planning to jump from tema to official. Can I dirty flash since both uses CM source? My main concern is battery life and basic telephony functionality. Thanks!
[Galaxy Note 3 Android Development] testmonkey1:
The 06 nightly seems good and smooth. Yes you can dirty flash (I would never recommend it though). As for battery life, haven't really had the time to test it out since I'm constantly changing builds/ROMs. You can always flash temasek's kernel though which would yield the same battery life. I am actually testing out different kernels/setups/builds. Unfortunately AOSP seems to give less points in AnTuTu X than stock 4.4 FW (completely weird for me considering the ROM feels much smoother overall).
[Galaxy Note 3 Android Development] PeterGuru:
20140306 also has NO SERVICE problem ...

Well, I have a few hours before my flight, so I thought I would try the 20140306 build to see if my previous NO SERVICE problem was resolved. It's not. I did a clean flash this morning, and the NO SERVICE problem still exists. I'll try again when I'm in China, perhaps in two days. Until then, I'll temporarily revert back to TW.

I'll try restoring my 20140303 build when I'm in China to see if all the necessary functions are working. If yes, then I'll stick with the 20140303 build until they resolve the NO SERVICE issue ... perhaps tomorrow or the next day.

I do prefer CM, so I hope it's fixed soon. My phone is critical for work, especially when in China (I go a few times a year). At least I have working nandroids of both TW and CM variations, so if something critical isn't working, I can easily go back and forth.

Peter
[Galaxy Note 3 Android Development] cam30era:
I'm not sure that this will help you, but FWIW; I just flashed 0306 build and everything related to telephony is good. Verizon version.

But no GPS love for our device, yet...

---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------

I just did a clean install of 0306 nightly. For Verizon users, GPS is still a no go.
[Galaxy Note 3 Android Development] PeterGuru:
NO SERVICE may be device specific ...

I think both problems are device-specific. While I'm having the telephony NO SERVICE issue since 20140304, my GPS has always been fine.

Peter

Addendum: Does anyone know how to make a screenshot of the notification pull-down screen? I tried the standard method in CM by holding the power button and selecting screenshot; however, the moment the power settings window appears, the notification pull-down screen scrolls back up ... so I can't provide a visual method to help others with the NO SERVICE problem I'm having.

Addendum 2: I found a way. I'll provide more details shortly about my problem.
[Galaxy Note 3 Android Development] xueyao:
Just flashed, Tema kernel dosent work (would be great if you could recommend a great kernel), but it flashed without hiccups and everything works. Using cyandelta to update cm now :) and no issues other than lte quick settings force close in telephony.
[Galaxy Note 3 Android Development] testmonkey1:
On the latest nightlies, only temasek's beta 3+ kernel works, but he currently dropped development due to being tired/CM making too much changes and having to rebuild constantly. At the moment there are no other custom kernels, I would suggest sticking with the stock CM one. Test out battery life, and if you don't like it you should return to temasek's v50 build + 2.6 b1 kernel (reported best for battery life and it also seems the smoothest/best scores in AnTuTu).
[Galaxy Note 3 Android Development] xueyao:
I tried his beta 3.0, dosent work. My telephony module crashed...
[Galaxy Note 3 Android Development] PeterGuru:
Detailed NO SERVICE problem ...

Okay, here's a detailed description of my problem, which began with the 20140304 build, and continues with both the 20140305 and 20140306 builds.

There are six images below, with explanations about each underneath. The first three images are using the 20140303 build, and everything is working well. The final three images are using the 20140306 build, although, the problem also exists with both the 20140304 build and the 20140305 build.

IMAGE 1 - Build 20140303: Main Home Screen: Signal meter displays correctly

IMAGE 2 - Build 20140303: Notification Pull-Down: The "Rogers" entry is correct

IMAGE 3 - Build 20140303: Settings>About phone>Status screen: The "Network" entry is correct. The "Mobile network type" is correct. The "My phone number" is correct. The "IMEI" entry is correct.

IMAGE 4 - Build 20140306: Main Home Screen: Signal meter is missing, displays SIM issue

IMAGE 5 - Build 20140306: Notification Pull-Down: The "Rogers" entry is missing. It now says "NO SERVICE"

IMAGE 6 - Build 20140306: Settings>About phone>Status screen: The "Network" entry is correct. The "Mobile network type" is correct. The "My phone number" is missing. It simply says "unknown." The "IMEI" entry is correct.

I can make and receive phone calls during the NO SERVICE problem, but no data connection. Otherwise, all other connections, such as Wifi, appear to be working well. Yes, all APN settings are there, including the one specific for LTE, which is selected. However, I can't get any kind of data connection, LTE or otherwise.

Peter
[Galaxy Note 3 Android Development] testmonkey1:
Unfortunately, I don't think anyone here can help you. Best you can do is enable Bug Reporting from developer options, when the bug occurs, send a report to CM. I have never actually done it so I can't walk you through the process. If there is space for explaining your issue, just post the info you just gave us, and wait for them to fix it.

In the meantime just stick with another ROM/latest CM version that was working for you.
[Galaxy Note 3 Android Development] gakio12:
My sister ran into the sim issue once. A restart fixed it though. SM-900T. It was with the 0305 build.
[Galaxy Note 3 Android Development] PeterGuru:
Will try an ultra-clean wipe and install ...

Thank you for the suggestion. I will try. In the meantime, with a few hours to wait at the airport, and nothing else better to do, I'm going to try something ...

I'll do a complete wipe of my device, flash 20140306, and then set-up my phone as if it's completely new. I won't install any apps, but simply check to see if such a clean install has the same problem. If yes, I'll simply restore my previous nandroid. If the problem is solved, I'll continue with the set-up and app install. I'll report back later.

Peter

Up-Date: Preliminary results are good. I completed the initial device set-up, selected Rogers' LTE APN, rebooted, and now I have data connection. I'll let the phone sit for several minutes and monitor the situation.

Up-Date 2: Still working. Data good. Can make and receive phone calls.

Up-Date 3: Everything still good. Can select and maintain "Preferred network type," however, when I select "Network operators" and the device finishes the search, there is no list of operators, and the error message saying that networks can't be found still exists. When I then select "Choose automatically," it does register the device very quickly ... much like the the behaviour on all previous builds. More to come ...
[Galaxy Note 3 Android Development] Xelphos:
Huh... I am with Fido and it shows as Rogers, I just flashed build 0306 and everything was fine for me.
[Galaxy Note 3 Android Development] beachbumsurfs:
Echo

Does anyone have an issue with Echo's on the person whom your callings line? Build 3.01 had no issues but since then everyone I call says they can hear themselves talk. I flash back to 3.01 build and no issue. I am on the Sprint note3

Update:

If I call through Bluetooth I don't get the echo problem.

Update:

Also if I put my phone on mute others wont here there echo
[Galaxy Note 3 Android Development] PeterGuru:
Another up-date ...

Further up-date: Everything still good. Wifi works great. Set-up Google account and sync working well. Also, Data still works. Will begin installing personal apps shortly.

Up-Date: I think I found the culprit ... the app that's causing all the problems ... Root Call Blocker. I was installing small groups of apps and then re-checking the entire NO SERVICE issue. Everything was working very well until the last group of 5 apps, one being Root Call Blocker. I suddenly had the NO SERVICE issue; however, the moment I un-installed Root Call Blocker, everything went back to normal, and data was working again. I'm now going to perform a nandroid so I don't have to go through everything again following my next test. I will then restore my 20140303 backup, which was working well, uninstall Root Call Blocker, and then re-flash 20140306. I have a feeling it will work. More to come ...
[Galaxy Note 3 Android Development] jamesmuking5:
Well wiping data and resetting seems to fix the issues. It did the same for me too. I guess something related to telephony changed during the 5th march nightly that isn't compatible with the 4th and before nightly. Too bad :(
[Galaxy Note 3 Android Development] Eddiemc:
I'd clear data on settings before dirty flash.. Temasek settings are way different. I remember it fixing some issues when going the other way
[Galaxy Note 3 Android Development] PeterGuru:
Problem appears to be solved ...

Well, it appears that my problem is solved, and it WAS the app Root Call Blocker. Now that it's not installed, everything is working well on 20140306. I'll give it some time to settle, but I think that everything is now okay.

Peter

Addendum: GPS is also working properly.
[Galaxy Note 3 Android Development] skadude66:
Imoseyen's lean kernel (under T-Mobile Original Android Development) for AOSP works perfect with CM nightlies. Been running for a couple days, battery life is great!
[Galaxy Note 3 Android Development] Xelphos:
I am currently using LeanKernel on the latest nightly build, it seems to run pretty good.

http://xdaforums.com/showthread.php?p=50870054
[Galaxy Note 3 Android Development] siraltus:
Do I still need to use a third-party app to set min and max CPU frequencies with lmoseyon's AOSP kernel?
[Galaxy Note 3 Android Development] skadude66:
Well, only if you want to. You could keep them at the defaults. I use Trickster Mod to modify the speeds and governors.
[Galaxy Note 3 Android Development] Xelphos:
Well I just uninstalled SetCPU to see if it would default to 300MHz without it, and it does. Min: 300mhz Max: 2265MHz.

I know that in processor settings it says min is set to 1190MHz, but I am still sitting at 300MHz when not doing anything.
[Galaxy Note 3 Android Development] amoblox:
I don't see a 3/6 build. Am I missing something?
[Galaxy Note 3 Android Development] Xelphos:
http://download.cyanogenmod.org/?device=hlte

It is there. Do you have your Update Type set to "New versions (incl. Nightlies)"?
[Galaxy Note 3 Android Development] amoblox:
Is it only available within the ROM update utility?

Edit: Never mind. I'm mentally challenged today.
[Galaxy Note 3 Android Development] testmonkey1:
Are you sure that it was the culprit? Unfortunately I faced the issue too, and what I narrowed it down to was restarting the phone without WiFi connection. It resets the time to default and cannot set the correct time, thus the network connectivity problems that follow. It happens on a completely clean install without 1 app/setting touched. That is on the 06/06 nightly. Haven't tested the 03/03 one (because that was the nightly this issue originally happened to me).

I have been able to recreate it in PacROM also, the only build that didn't have issues for me was temasek's v50 build since it's based on the nightly from 26th
[Galaxy Note 3 Android Development] amoblox:
Just a heads up:

I did a clean flash from stock T-Mobile a few hours ago. I noticed that Metro PCS was the default access point. I was able to change my access point to T-Mobile without issue (and it stuck after reboot). Not a huge deal, I just wanted to let someone know before people started to complain about signal loss etc.

Edit: Signal reporting seems a little off from prior builds. I'll lose all bars but still maintain LTE and a speed test reports all is well. So I'm not actually losing signal; just reporting really low.
[Galaxy Note 3 Android Development] Whosdaman:
Noticed the same exact thing, but thought it was user error on the metro PCs thing. But yes, all tmo users should check apn settings
[Galaxy Note 3 Android Development] xueyao:
Anyone not able to change lte and network mode in quick settings? Long hold cause it to crash. On 3/6 nightly.
[Galaxy Note 3 Android Development] xionix:
Is sombody too getting Fc at calendar app?
[Galaxy Note 3 Android Development] lambik333:
no problems at all..........
[Galaxy Note 3 Android Development] amoblox:
I'm over it. Going back to stock until my upgrade at the end of the month. Good luck guys.
[Galaxy Note 3 Android Development] jetbruceli:
Unless your truly in need of CM I Don't think there is a device capable of taking the crown away from the note 3. Even with the new devices coming in the next few months there isn't one that will out the note 3.

With that said, stock KK is freaking awesome. Use nova launcher and remove much of the bloat and you have a very stable and well performing piece of equipment!

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] Xelphos:
Same problem here.
[Galaxy Note 3 Android Development] PeterGuru:
Can you explain more?

Well, in China now ... heading to my in-laws by train (5-hour trip), so I have some time. My China Mobile SIM card works well, as hoped, and as expected.

For testmonkey1, can you explain a bit more because I think you may be right. Even though I said in one of my earlier posts that the problem was solved, I did experience a brief encounter with the "NO SERVICE" issue, but a reboot fixed it.

I'm curious about your comment, "... restarting the phone without WiFi connection." Can you provide a bit more detail about this statement? I want to narrow-down this issue, and any information is good. I have a few other ideas, but I can't test them yet.

Thanks,

Peter
[Galaxy Note 3 Android Development] testmonkey1:
I've narrowed it down to this:

Restarting the phone resets the time to 01/01/2013 and some random hour.

You have a working data connection, but the time won't change to the proper one. Connecting to web sites and apps sends them requests as if it were 2013 and their security protocols get confused, and they reject your connection. Changing the time and date manually fixes the protocols issues, but the time still won't set automatically.

After connecting to a WiFi network though, automatic network times start working as expected. Until the next reboot.
[Galaxy Note 3 Android Development] PeterGuru:
Thank you for the quick reply. Let's see if I understand correctly. If I reboot the phone with ONLY a data connection, there could be network issues; however, if the phone boots-up and immediately connects to a WiFi network, then everything should be fine?

Peter

P.S. What I found particularly interesting about my previous NO SERVICE problem was, the moment the phone rebooted, and was ONLY connected to data (WiFi had yet to connect), my network showed "Rogers," but about a minute later, AFTER the WiFi connected, the network appeared as NO SERVICE, and there was nothing I could do to resolve it. For me, the only solution so far has been to NOT install the app called Root Call Blocker. In fact, since I re-flashed 20140306 yesterday, after removing Root Call Blocker, I haven't had a problem since ... but I will try your test above to see if I can duplicate your issue. Time for sleep. It's almost 2am here.
[Galaxy Note 3 Android Development] siraltus:
Yeah, agreed. I just updated to stock KitKat and after debloating and some customization (Wanam Xposed is a godsend) it flies.

Foreverloco over in the Themes & Apps forums is already working on updating his AOSP theme for KitKat, at which point my Note 3 will look 99% stock Android.

I'll wait until Cyanogen gets all the hardware working properly, especially NFC.
[Galaxy Note 3 Android Development] sauron82:
For me CM will always beat stock because of themes. I don't understand why TW won't let you use themes.

Click thanks if I helped you.
[Galaxy Note 3 Android Development] siraltus:
Me too, but I'm not going to run an OS where major things are broken. I want stability.
[Galaxy Note 3 Android Development] sauron82:
I understand and don't blame you. ATM CM is stable enough for me; I don't use NFC that much and once in a while reboots are things I can put up with (on my old Vibrant a reboot could take 60-90 seconds, bit on a Note 3 it's under 20). Although when I went on a trip last month I flashed it back to stock, though that was mainly for the camera.

Click thanks if I helped you.
[Galaxy Note 3 Android Development] siraltus:
Yeah, I use NFC all the time for beaming stuff to/from my friends, and also use Tap-and-Pay (ISIS but it's better than nothing). I have a Nexus 5 with CM on it so I'm not gonna bother with it on the Note 3 until it's on daily-driver level.
[Galaxy Note 3 Android Development] sauron82:
I don't think we have NFC tap-and-pay here in Canada.

Click thanks if I helped you.
[Galaxy Note 3 Android Development] Eddiemc:
No offence guys, but please take this discussion somewhere else.

Unless I'm mistaking this is the official cm11 development thread for our device.

The focus should be on squashing bugs, providing logcats, workaround issues etc. If you think tw is better, good for you. If you prefer cm, good for you. Regardless it's not really contributing much to this thread besides clutter.

If something isn't working, provide a logcat. If you have a fix, please advice.

Hope I haven't offended anyone.

PS,

Nfc works fine on n9005 on the latest few nightlies, connecting fine to both job car stereo and Nokia 360. Also some random reboots that plagued some of the earlier builds seems gone.
[Galaxy Note 3 Android Development] siraltus:
*poof*
[Galaxy Note 3 Android Development] testmonkey1:
Correct after a reboot connected only to data the time resets.

There is network/signal etc. but the time is reset and creating connectivity issues.
[Galaxy Note 3 Android Development] PeterGuru:
Tried test ... my device seems to work properly ...

I tried your test, and my device seems to be immune. I disconnected power to WiFi so that my phone couldn't connect to it. I then rebooted. It quickly found the network signal and showed LTE in the status bar. The clock was also correct. I let it sit for about 10 minutes, but no problems.

Perhaps your situation is device-specific.

Peter

P.S. I haven't yet tried to re-install Root Call Blocker to see if the NO SERVICE issue suddenly manifests itself. I may try later today, or sometime this weekend.
[Galaxy Note 3 Android Development] jetbruceli:
A question was asked and an answer was submitted. Yes this is for CM but some might not understand that Stock is better for them than CM.

CM is great for those who know what they are doing but there are alot who dont know or who want a stable system
[Galaxy Note 3 Android Development] testmonkey1:
Yeah I actually realized last night that our problems are somewhat different since I don't actually get No Service. What device are you using by the way, I'm on the N9005.

Turns out my problem isn't encountered by all users and I'm advised to use a third-party app to sync the date and time. As for yours however, I would advise keeping the Root Call Blocker out of the way for now and see how it goes. I've never used that app, don't even know what it does so I can't comment on it.

Judging by the name though, does it block incoming calls? If yes, why not just use the built in feature of the Phone?
[Galaxy Note 3 Android Development] Jonphinguyen7:
Just clean flashed 08 build and getting phone force close error. Anyone else?
[Galaxy Note 3 Android Development] xueyao:
Try clearing data of the 3 phone related system apps.