yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] nighthawkca:
I'm on 4.4.2, the 0524 nightly from this thread. It's the stability that I'm looking into, this is a great rom but has some random reboots and I don't know if updating the bootloader will help or not.

The firmware browser in Phone Info shows two others that are available, with the most recent being N900TUVUDNE6. It's 4.4.2 from May 2014. It's been a while since I've flashed a bootloader on a samsung device, would I download that image and then flash it with ODIN?

Thanks.

---------- Post added at 03:23 PM ---------- Previous post was at 03:15 PM ----------

The OP doesn't say much about updating the bootloader, except that it probably won't help much. But Phone Info shows that there are two newer 4.4.2 ones available. Yeah, I agree about reading a lot before flashing. This is probably the 12th device I've flashed (hate stock software, love CM!) and I've never had any bricks or serious problems because you first read, read, read. So that's where I'm at now, trying to determine if this Note3 on CM11 will run better or not with an upgrade of the bootloader. And I'm thinking of upgrading TWRP while I'm at it.

Is there anyplace that lists bootloader numbers and versions for the Note 3? I haven't found it yet, though I assume sammobile is the place to find the latest.
[Galaxy Note 3 Android Development] cam30era:
Bootloaders will make no difference in how your device runs.
[Galaxy Note 3 Android Development] xueyao:
Is there any chance for 4k and high framerate to be implemented on aosp? I know it's a minor issue, but is there even any chance of future implementation, or is totally dependent on touchwiz? Thanks guys.
[Galaxy Note 3 Android Development] johnpro112:
Does anyone else's phone run a little warm? If so, what have you done to remedy it? Thanks.
[Galaxy Note 3 Android Development] HSD-Pilot:
Check your min frequency, because on mine it stucks @ 1728mhz. Change it once back to 300mhz and it should be fine. Also disable the per-app profiles...

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] johnpro112:
Thanks, I changed my CPU settings using the CM performance Menu,but how do I disable per-app profiles? Thanks
[Galaxy Note 3 Android Development] Ooo_Pepi:
Hello, I tested latest 5 versions from 21-st may to 25 but all have this bug:

When I started titanium backup menu button is not active.

With older version I have no problem.

I try others rom based on CM but all have this bug.

Is this fixed in new release from today ?
[Galaxy Note 3 Android Development] gorinnosho:
Hi all, for fun and the knowledge, i'm trying to build a cm11 hlte by following cyanogenmod instructions. I have succeeded to produce a cm...zip but after flashing it...i'm stuck on boot animation.

Have trying to wipe davlvik cahe and cache and reboot, but i stuch on android updating : starting apps.

Someone can help me please? How can i find and correct error?
[Galaxy Note 3 Android Development] springer.music:
I'm on the 0526 and the Titanium menu button works.
[Galaxy Note 3 Android Development] Jonphinguyen7:
I remember reading previously that the option was there on the camera but it didn't work. Hopefully this means it'll be available in the future.
[Galaxy Note 3 Android Development] dneill2006:
CPU speed seems to be stuck at either 1190 MHz or 1728 MHz most of the time, it's not down-clocking to 300 MHz.

Tried using 3rd party apps and the built in performance settings. It does down-clock once the setting is change, but then goes right back to 1190 MHz or 1728 MHz.
[Galaxy Note 3 Android Development] Eldartho:
I've been having that problem and it's the main reason I don't use an aosp rom..... Everyone will always tell you to use this app or flash this kernel but they don't do a dizzam thing....
[Galaxy Note 3 Android Development] BillGoss:
See this post by [MENTION=2332422]temasek[/MENTION] for info: http://xdaforums.com/showthread.php?p=52949030

Sent from my SM-N9005
[Galaxy Note 3 Android Development] NoXXX:
Didn't find if this question was asked before, but did you notice that sound volume during video recording is much much lower than on stock? Is there a workaround for that? Is this known issue?
[Galaxy Note 3 Android Development] ajm786:
Has anyone noticed a bug with the quick launch shortcuts in landscape orientation?

It's following the screen orientation, which is acceptable, but what should happen is that the icons should simply rotate when rotated from portrait to landscape; instead, the entire circle rotates, which ends up with it getting cut off.

Here is a screenshot.

http://imgur.com/wmgRym2
[Galaxy Note 3 Android Development] Whosat:
I'm getting the exact same issue. Read somewhere about something about touch boost... Could it be that? I don't ever see the clock speed going down though
[Galaxy Note 3 Android Development] Xelphos:
Yeah, I just updated to the most recent version and I see what you guys are talking about. Don't upgrade unless you like BBQ.
[Galaxy Note 3 Android Development] Whosat:
Might be worthy to note that this happens even on custom kernels. Using leankernel 2.5 now and 28/05 nightly, same issue persists
[Galaxy Note 3 Android Development] Robster83:
If you use something like TricksterMOD you can see what frequencies have actually been used and for what percentage of time. On mine it shows 300Mhz is being used quite a lot, despite what the 'minimum' value appears to be set to.

That's on the 28th Nightly and both Temasek and Leankernel.
[Galaxy Note 3 Android Development] DonPhelippe:
A weird question (but bear with me because it must have something to do with CM).

Greetings peeps, here is your mind-tease for today.

I have a microSD card which has served numerous phones up to now, from a HTC Sensation, to a S3 and now to N9005. I have been able to use the card on the phone, read from it, write to it, etc etc. When I plug the card to a card reader and then to my PC I got that this disk was not formatted but that was okay because when I put it back on the phone and connected the phone to my computer, I could see the files/folders etc when I browsed the phone (as an MPC device) on my PC.

Well, after some time (and I suspect it has something to do with M6, because I did some work in the microSD when on M5) when I connect the phone (with 3 different cables no less) to 2 different windows 7 PCs, one of them the one that I used to root/CWM/CM11 the phone, I get only *SOME* of the files in the microSD card and not all of them, likewise with the folders. E.g. on ES Explorer I get e.g. 20 subfolders in a folder and on Windows Explorer I get 2, same with files.

Is there something I could try to alleviate the situation? Anyone came up with something like that, ever?
[Galaxy Note 3 Android Development] Whosat:
Encountered exactly that issue on a different device (Galaxy S4 Mini) when I was on CM 11 nightlies. Didn't manage to find a fix though..

I had to resort to using an assortment of file transfer tools like Bittorrent Sync and the built-in FTP functions of ES File Explorer to allow me to manage files from a desktop.
[Galaxy Note 3 Android Development] crespi_:
In all honesty I think you should try temaseks unofficial cm11. He fixes any known issues from cm11 and it's a much better rom than official cm11 in my opinion.

But more notably, he recently added built in support external SD cards formatted as exfat. There are other ways around your problem but using his build you won't have to do anything most likely.
[Galaxy Note 3 Android Development] sanjsrik:
Is anyone else having issues sending text messages? I saw some posts back in March 30 that some were having issues, but it's only now happening for me. I can't send anything. Or anything that does send, sends 3-4 times. It's very frustrating.

I'm the latest nightly on T-Mobile.

Any help would be most appreciated.
[Galaxy Note 3 Android Development] :
Does the NB4 boot loader work? It's not listed on the front page :/
[Galaxy Note 3 Android Development] temasek:
Don't mention me here in official cm11 thread.

This thread is all about official stuffs.

Thanks
[Galaxy Note 3 Android Development] caesar_:
I already told you this rom is compatible with both 4.3 and 4.4 bootloaders.
[Galaxy Note 3 Android Development] :
Haha thanks for replying so promptly, but my previous question was posted in another thread (Heisenberg ROM), not this. I'm exploring the various custom ROMs. But thanks, it's good to know! :)
[Galaxy Note 3 Android Development] caesar_:
All aosp roms are universal and they all work on both bootloaders.
[Galaxy Note 3 Android Development] :
Is there MHL/HDMI support?
[Galaxy Note 3 Android Development] :
Data

Not sure if it's just me but i can't get data on the last 2 nightlies. Anyone else?
[Galaxy Note 3 Android Development] springer.music:
Data works fine here.
[Galaxy Note 3 Android Development] :
Thanks, for some reason my data will not work. I am going to odin back to stock and then reflash to see if that fixes it.
[Galaxy Note 3 Android Development] :
Just finished doing the process above and got no data at first. i then toggled LTE and it came on.
[Galaxy Note 3 Android Development] bourne220:
YouTube issues

Still having issues with YouTube on the AOSP based ROMS. Hangs then throws up Touch To Retry. Don't know if anyone else is still having this or it's just me.
[Galaxy Note 3 Android Development] Whosat:
[MENTION=5439536]bourne220[/MENTION], are you using YouTube flashed from a gapps package or downloaded from the Play Store?
[Galaxy Note 3 Android Development] bourne220:
It's an original GAPPS package YouTube that's been updated a few times. Would a download of the current APK and installation using Root explorer in system/app solve the issue or do I need to just remove the system app and install from the Play Store?
[Galaxy Note 3 Android Development] DaniuPL:
I can't set min CPU speed to 300 MHz..

ROM force 1728 MHz.

Newest version.

Help.
[Galaxy Note 3 Android Development] navdra:
Anyone else having problems with AlarmManager partial wakelock? It's keeping my phone awake all the time and chewing trough my battery life. It started yesterday. I'm on the newest nightly. BBS dump for reference:

https://www.dropbox.com/s/sqlf7f9347hk0no/BetterBatteryStats-2014-05-31_211655060.txt
[Galaxy Note 3 Android Development] borimol:
Same here. CM bug.
[Galaxy Note 3 Android Development] springer.music:
Could this be related to some other video issues that I'm experiencing?

E.g. Videos are choppy when played back with the stock CM player (and with other players that use the standard hw acceleration - for example Quickpic).

VLC works fine using software rendering but crashes when hw acceleration is enabled.

MX Player works fine with the options “Software decoder“ and "H/W+ decoder" but the playback stutters with the standard H/W acceleration.

Some games (e.g. The Respawnables) now crash all the time (they worked well some time ago).

See this:

http://review.cyanogenmod.org/#/c/64610/
[Galaxy Note 3 Android Development] DaniuPL:
Solved the problem. Installed Temasek version with Trickster Mod :) The app should work on Official CM and force CPU speed to 300 MHz C:
[Galaxy Note 3 Android Development] herczyn:
hey guys, just FYI.

i've been having problems with the proximity sensor during calls. this solved it:

http://xdaforums.com/showpost.php?p=51018367&postcount=6292
[Galaxy Note 3 Android Development] siraltus:
It's because dust accumulated inside the proximity sensor window and is blocking the sensor. You should get it cleaned.
[Galaxy Note 3 Android Development] herczyn:
what? did you read the post?

i said that those instructions worked, no cleaning needed.
[Galaxy Note 3 Android Development] siraltus:
DId you even think about what I wrote before replying?

The reason your sensor went out of calibration in the first place is because dust accumulated over it and now it thinks it's always covered, not allowing your screen to turn on during calls when it should. Recalibrating it simply changes the "uncovered" and "covered" lux (light intensity) threshholds, but does not fix the actual problem. It will happen again after more dust gets in.
[Galaxy Note 3 Android Development] robbiekhan:
I've had a look around buy can only find old threads. Is there a possibility of adding apt-X support into CM builds either manually or flashable zip? It's a shame that sound quality is less than Samsung's as I have apt-X enabled amps and car stereos that I enjoyed music on.
[Galaxy Note 3 Android Development] RaluSiCris:
Same here, last nightly
[Galaxy Note 3 Android Development] 954wrecker:
It's been like that for months on every aosp ROM. It records in 1 channel not the normal 2 channels. It's only been spoken about rarely I'm assuming nobody on aosp cares about the camera let alone the camcorders sound quality.

sent from my note 3
[Galaxy Note 3 Android Development] Robster83:
If it's a problem you can log it in Jira and provide logs to help them fix it.
[Galaxy Note 3 Android Development] ki1120:
Can i use MSC mode for accessing the external SD card via computer in CM11?
[Galaxy Note 3 Android Development] herczyn:
sorry, you may be right.

still, it's much easier to use those instructions than to clean the inside's of the phone, isn't it?
[Galaxy Note 3 Android Development] Lodix:
CM can be installed like other custom roms into recovery ?

First time trying non stock rom.
[Galaxy Note 3 Android Development] wmfreak:
Yep. Don't forget gapps though!
[Galaxy Note 3 Android Development] siraltus:
Yes it is easier, but it's not a permanent solution. Eventually, so much dust will get in that the sensor will stop working altogether. It's a design flaw in the Note 3, I had it happen on two different units.
[Galaxy Note 3 Android Development] fanshaw:
mp4 playback is still buggy in the latest nightlies. For example, videos are extremely choppy when using MX Player's HW decoder, but work perfectly with the SW decoder enabled. Is this a known problem? People have been mentioning it on this board for quite some time.
[Galaxy Note 3 Android Development] springer.music:
I don't know what's being done to address this issue at the moment but I think that the following (from May 24) may be related to the video playback issue you encountered:

http://review.cyanogenmod.org/#/c/64610/
[Galaxy Note 3 Android Development] wilfredlams:
Anyone willing to test if this charger mode fix does anything on the hlte? Cheers.

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

Edit:

Just tested it fixed the charger mode problem!
[Galaxy Note 3 Android Development] Yank555:
Extract ramfs from boot.img, unpack it, change the given file, repack the ramfs and rebuild the boot.img and flash it.

JP.
[Galaxy Note 3 Android Development] wmfreak:
thanks
[Galaxy Note 3 Android Development] Juanito216:
Does anyone run the rom without turning the min cpu speed down? I think I've done it and the phone seemed OK. Wondering if is safe to do so.
[Galaxy Note 3 Android Development] cam30era:
Yes. And battery life is quite good.
[Galaxy Note 3 Android Development] RaluSiCris:
it means that the offline charging will be fixed?

thanks
[Galaxy Note 3 Android Development] jcespi2005:
Someone can makes videos with 120 fps? Camera FC when select this...

Enviado desde mi SM-N9005 mediante Tapatalk
[Galaxy Note 3 Android Development] springer.music:
Can anyone confirm that the following has now fixed the S-pen issue?

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

The S-pen has not stopped working randomly for me since the above fix was merged.
[Galaxy Note 3 Android Development] palletguru:
I'm using 5/31 nightly and MHL works great with my AppRadio.
[Galaxy Note 3 Android Development] RaluSiCris:
For me s pen works OK since latest nightlies :)
[Galaxy Note 3 Android Development] SleemLDJ:
I haven't used cm before but can someone please tell me what functionalities the Spen has on it.

And how stable is it for a daily driver
[Galaxy Note 3 Android Development] springer.music:
The S-pen has some basic features on CM11, including some assignable gestures (Settings > Language & input > Stylus gestures).

You can get some extra features by installing CM Spend Add on + Note Buddy.

As to the stability, it's pretty stable but there still are some device specific bugs which need to be ironed out.

Here's a list:

http://wiki.cyanogenmod.org/w/Known_Issues_page_for_hlte
[Galaxy Note 3 Android Development] dperique:
I was using CM11 5/15 nightly (most stable for me so far as I get only 1-2 reboots every 2-3 days). Every nightly build since then, I've been getting about 1 reboot a day sometimes more; I went back to rooted/tweaked Touchwiz stock firmware after the 05/28 nightly.

I know folks will use a different kernel than what comes with CM11 and that may make things more stable but I've not delved into that yet. I still need to understand how to upgrade/downgrade kernels and if I can undo them, etc. They're easy to install, I just need to do a little homework to ensure I feel comfortable about going back to an original kernel.

I'll give it a little more time, maybe wait for the M7 build, monitor this thread, and perhaps switch back at some point. 'S-pen working better' is a good sign.

I've made nandroid backups to allow me to restore/continue with CM11 (or Touchwiz) as needed.

For sure, battery life is down by maybe 25% on touchwiz vs. CM11 but it's nice to have no reboots in the last 6 days.

Dennis
[Galaxy Note 3 Android Development] caesar_:
You're doing it all right buddy. Backup backup backup. And don't flash at will without full understanding. Most people forget or never learn those 2 simple things.

To give you a few pointers. You flash kernels the same exact way you flash roms. If you want to test out a non stock kernel, make a nand backup of your setup.. In the same recovery session, wipe cache and dalvik and flash kernel by overwriting. Optionally wipe cache and dalvik again and reboot. You will now be running that new kernel.

To go back to stock kernel you just simply boot back into recovery and do a factory reset (I do 2 back to back just to be sure) and restore your nand backup.

The two popular custom kernels for CM nowadays are Lean and Temasek's. There are XDA threads for both for you to read up on before flashing.
[Galaxy Note 3 Android Development] willl03:
You may want to give a shot to Temasek kernel

Flashing kernels and reverting is easy

Just flash the kernel zip, no need to wipe caches or things like that

There's no reason to roll back to stock kernel, but if you ever want to do just reflash rom and gapps, again no need to wipe caches. It will overwrite current kernel with stock one

Sent from my ATARI-JAGUAR using 64-bit mathematics
[Galaxy Note 3 Android Development] caesar_:
And of course there will always be the users giving you misinformation or saying and promising something is OK when it just isn't. Lol.

The post above is probably a perfect example of a user that forgot or never learned how to nand backup. He never mentions it once. He probably deems that not necessary as well.

He also doesn't mention that most kernel devs make an aosp and tw version of their kernels and if you flash one while being on the other.. You are in for some fatal issues if you don't have a nand backup you can revert to.

I remember when wiping cache and dalvik were standard before and after flashing ANYTHING. But I guess I'm just old school. I've been in this game since CM6 so what do I know? It's not like I'm a dev or anything.

The problem is you got so many uneducated users teaching new users how to not do things correctly that now there is a whole new breed of them. They are taking over XDA. Most of them in the teenager age group and don't care if they jack their phone up.

Why not wipe cache and dalvik???

Because it will save you a whole 3 seconds???

Why would you want any old cache remaining on your phone from before flashing a fresh kernel. That's like taking a shower with your dirty sh!t stained underwear on. Smh.

Sometimes I just like rebooting into recovery randomly and clearing cache and dalvik just so my phone is as fresh as me. So why not do it during A Major install such as a kernel. It only makes the whole rom run.

Because one user deems it not necessary? OK. 5 years ago 9 out of 10 would tell you to wipe both definitely before. Half that number would tell you before and after. Nowadays 5 of 10 would deem it not necessary because one fly by night user taught another the wrong way and he taught a gullible nother.

Now you have a whole fleet of dimwitted users teaching new users to become more dimwitted users who keep the cycle going. Which equals more bricked phones which is why we have Knox and impossible to unlock bootloaders.

But what do I know?

I'm not a dev..

Good luck.
[Galaxy Note 3 Android Development] dhufford81:
Let them eat cake.
[Galaxy Note 3 Android Development] RaluSiCris:
In the last nightly have again the stylus bug:(
[Galaxy Note 3 Android Development] springer.music:
Oh crap, you're right :(

It has just happened to me as well...

So the S-pen bug has definitely not been sorted out yet.
[Galaxy Note 3 Android Development] dperique:
Thanks for the advice about flashing a kernel and how to go back. I didn't realize it was this easy and thinking about it, it makes sense. I may give CM11 another go this weekend or so.

But now I just read about S-pen broken again? bummer. I might determine which nightly it was before it broke and use that.

It is unfortunate that folks refer to nightlies as "the latest nightly" ; identifying the particular nightly by date is more useful. I guess if you find the original thread identifying the "latest nightly" broke such and such, you can look at the timestamp on the post, determine the timezone, look at the date/time of the nightly when that nightly was built, determine if it was the nightly of the date of the post of the one before or after depending on timezone -- then you can know which nightly they were referring to. And if you got it wrong, you can always restore from nandroid, try again, post here, and try to find the real answer, etc.

Maybe it's best that folks identify the nightly build of interest by mentioning the date so there is no ambiguity -- just a humble suggestion.

BTW, I'm pretty religious about making nandroid backups and copying them to my extSDcard or PC. I spent a bit of time understanding the backup process and have a procedure I use (which includes making notes about what I did and any anomalies encountered). This way I feel safe about the ability to "go back" if anything goes bad. I'm even careful about backing up before installing Xposed modules (at least most of the time) and googling about experiences before installing. After having bricked a phone (iPhone 3G back in the day) and destroyed/corrupted EFS on a Galaxy S3, I now know the drill -- my mantra is "follow procedure and no one gets hurt".

I hope to get back to CM11 soon and try the Temasek kernel.

Dennis
[Galaxy Note 3 Android Development] tehwench:
Hey, can anyone confirm/deny if the HDMI out feature works on CM11 for hlte before I go ahead and buy a smart dock?

Sorry if wrong place to post, couldn't think of a better place than ITT. Thanks
[Galaxy Note 3 Android Development] palletguru:
I'm on the 5/31 Nightly, and MHL works - used the official Samsung adapter as well as the monoprice one. Both work great.
[Galaxy Note 3 Android Development] tehwench:
Exactly what I wanted to hear, thanks!
[Galaxy Note 3 Android Development] G U C C I:
Just updated to the newest nightly! 4.4.3!
[Galaxy Note 3 Android Development] thools60:
In developer options there's an option to update recovery when flashing. Is this something that's recommended? What do you guys do? Feels scary, to say the least, to mess with a working recovery.
[Galaxy Note 3 Android Development] caesar_:
From what I've heard it always checks and updates you to the latest version of clockwork mod recovery. So if you're using twrp you should not use this feature.
[Galaxy Note 3 Android Development] thools60:
Yeah, but it only updates if you tick the box. Should I tick it.......?
[Galaxy Note 3 Android Development] caesar_:
You ever seen the matrix? Red or blue pill.. The choice is yours Neo.