yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] jetbruceli:
Hey guys I tried it and it's ok. It's basically the same as the stock aosp but with a different ui and has a complicated blur effect.

It does not take better photos than tw but when it seems to make sure the shot is in total focus before proceeding. Which means it's slower to snap.

I think though for cm use its great to have a camera app that can be used on all Roms with kitkat.

But for aosp I would like the sg4 google edition for the note 3. It has all features but no 4k.

I have to keep stock tw because the camera app has one thing none else has and that's the 60fps video. Once you shoot a few in that mode you will not want to leave home without

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] Whosdaman:
Update to 16. Its all fixed now. I had the same issue.
[Galaxy Note 3 Android Development] speedyjay:
Hey guys, I was wondering if I could have some advice?

Every time I flash CM11, then eventually restore my backup sammy ROM, open spotify, I always get a storage error, and I can't install anything or use the Internal SD card whatsoever. Any advice would be great :)
[Galaxy Note 3 Android Development] NOZX:
Any luck witb OTG USB? Not talked about much...but its something I rely on. I happy enough with all other bugs but i need this :(
[Galaxy Note 3 Android Development] navdra:
Works fine for me with 'USB OTG Helper' app. Even ntfs.

Insert host cable and flash drive, open USB OTG Helper, tap Mount and enjoy.

Remember to unmount when finished.

I tried a mouse and it works without problems.

It didn't work in TWRP until I realized that TWRP doesn't support ntfs. At least that's what I figured out - FAT formated USB flash works fine.

N9005, CM11 nigthlies, TWRP 2.7.0.3
[Galaxy Note 3 Android Development] maxturk:
N9005: It's working great but we need s pen support, mhl support, otg support, 4k video support and usb 3 support... But it's a great rom
[Galaxy Note 3 Android Development] navdra:
Check here: http://xdaforums.com/showthread.php?t=2611415

Enough for me. I only miss Pen Window.

Haven't tried this.

Works fine here with. Flash drives mount with 'USB OTG Helper' and read fine trough 'Total Commander'.

Not really important for me.

Just made an experiment with 64GB Supersonic Rage XT USB 3.0 Flash Drive (PEF64GSRUSB) and USB 3.0 OTG host cable:

Read 5.5 GB file from USB 3.0 flash drive in under minute (reading cam to 100% in Total Commander). That translates to rougly 100 MB/sec. It took some more time (around 3 minutes) to write it down to internal phone memory and finish copying in Total Commander.

Feels like USB 3.0 to me, but I'm not sure. See for yourself. Anyway, I'm not really sure if I'll be copying such big files to my phone...
[Galaxy Note 3 Android Development] maxturk:
I know for s pen app but why it's not integreted to the rom?? moreover, when i kill all recently app it's shutdown s pen app and i need to reboot the phone :/ You have a solution please?? but i prefer officiel support ..

Usb otg: The same... Why there is not official support ?? if it's work with an app i think it's easy to add :s

I know it's free and great work i respect and thanks for all i just said what need the rom for be more great ...

Sorry for my very bad english :)
[Galaxy Note 3 Android Development] speedyjay:
I'm running the latest nightly now and the distortion is still present. What nightly are you running buddy?
[Galaxy Note 3 Android Development] xueyao:
Distortion present if u have touch sound on. It's fixed if u off it.
[Galaxy Note 3 Android Development] ThaMystery12:
I was running the 04/16 nightly. And i switched the touch sound off. Currently im running the temaseks build with the temaseks kernel and its pretty smooth now.
[Galaxy Note 3 Android Development] speedyjay:
Thanks guys, all fixed now :) one more quick question though. I use setcpu to maximise battery life, is a min of 300mhz and a max of 1.7ghz a good combination?
[Galaxy Note 3 Android Development] ThaMystery12:
Dont know, if it runs well and smoothly why not?

--------------------------------

ThaMystery
[Galaxy Note 3 Android Development] celderic:
Still present with all touch sounds off.. so i put them back on as the sound is rubbish either way for me.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] sauron82:
Is it possible to turn if the hiding status bar and have it always be shown like before? I've checked every single setting in the menu and I can't find anything about it.

Click thanks if I helped you
[Galaxy Note 3 Android Development] ki1120:
I found a bug, when profile is enabled, and various app is added into application group, with "vibration" option being overwritten, the phone will keep vibrate itself at random intervals.
[Galaxy Note 3 Android Development] jetbruceli:
Hey guys and gals. Anyone know how to after changing the dpi to make the device rotate like let's say a nexus 7?

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] dagger19:
does anyone have a problem of calling out or receiving calls after flashing 20140418 nightly?

is there other way to recover this besides a factory reset?

i tried to flash backwards to 20140416 but the problem still persist
[Galaxy Note 3 Android Development] dtr145r:
o have no problems with the 18th build...
[Galaxy Note 3 Android Development] piit79:
Genuine question: what do you need 60fps for?
[Galaxy Note 3 Android Development] Yank555:
On fast moving images you do clearly see frames missing at 25/30 which you don't at 50/60.

Not that I do film at 60fps on my phone, but driving on a racetrack filming with my GoPro I rather film @50fps 720p than @25fps 1080p (which looks just way too unnatural with half the frames missing).

Course if you film a mostly steady / slow moving landscape, there's no need for double the framerate, but there definately is a difference between 25/30 and 50/60 ;)

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta9 (3.4.87) kernel.
[Galaxy Note 3 Android Development] springer.music:
CM 10.2 had settings to allow both lockscreen and Trebuchet rotation.

CM11 doesn't have such settings available (yet).

You can achieve full rotation by following these steps:

1. In Settings > Display & lights > Rotation - enable all of the modes

2. Install Xposed framework + GravityBox + Xposed GEL

3. GravityBox > Lockscreen tweaks > Enable lockscreen rotation

4. Xposed GEL > General > Rotation (this enables both Trebuchet and GEL rotation)

If you use a different launcher (e.g. Nova) you can avoid the bits about Xposed GEL
[Galaxy Note 3 Android Development] jetbruceli:
The video looks alot better, period. If you havent tried it then I suggest you do.
[Galaxy Note 3 Android Development] pbrown148:
In-call issues

Ever since the early March nightlies, I've had issues with operating the dial pad (and phone in general) during calls. Examples of general behavior:

- With the screen on, dial pad buttons (numbers, speaker, mute, end call, etc) are completely unresponsive. I can draw down the status bar, but nothing on the dial pad works at all.

- If the screen goes off at any time during the call, it is absolutely impossible to turn it back on, which makes things like ending calls, answering other calls, or navigating call menus impossible

- Pressing the power button or the home button does nothing to turn the screen on. If I want to end a phone call, I literally have to pull the battery or wait for the other person to hang up first. If the latter occurs, my phone immediately returns to normal operations.

- I've done multiple full wipe/clean installs

- I've tried cleaning the proximity sensor a few times with no change in performance

- I downloaded & installed the AOSP phone APK with no change in performance

Does anyone else have this issue? Any recommendations on how to improve? Much appreciated.
[Galaxy Note 3 Android Development] thools60:
Yep! Me to. Thought that it happened when I dropped my phone on the floor since no one else has mentioned it. Thank God someone else noticed this.
[Galaxy Note 3 Android Development] pbrown148:
I would have thought it was a hardware issue too, except I flashed back to stock TW and the phone worked flawlessly - it's an issue with CM.

I should also note that I've ruled out any interfering apps - after a full wipe/clean install with only gapps installed (i.e., no market apps installed), the issue still persisted.
[Galaxy Note 3 Android Development] thools60:
Guess it's back to 20140317 again......
[Galaxy Note 3 Android Development] amoblox:
Do you have a copy of 3/17? Or a link to DL?
[Galaxy Note 3 Android Development] thools60:
Here it comes:

https://www.dropbox.com/s/5jxr2ohew0eir8j/cm-11-20140327-NIGHTLY-hlte.zip

---------- Post added at 10:31 PM ---------- Previous post was at 10:29 PM ----------

Sorry, I meant 0327. The last one that worked for me.
[Galaxy Note 3 Android Development] amoblox:
You are a true gentleman!
[Galaxy Note 3 Android Development] thools60:
Where is everybody btw? It's been dead as Detroit here for days now. Has everybody moved to a new thread and I missed the bus???
[Galaxy Note 3 Android Development] jetbruceli:
This is what happens when new flagships show up. People are more focused else where.

I have noticed that the last few nightlies have been the exact same size.

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] pbedard:
I've changed devices lol
[Galaxy Note 3 Android Development] Robster83:
The Nightlies are more stable these days, other than the known ongoing bugs, so less to talk about I guess.
[Galaxy Note 3 Android Development] eye_omega:
is n9009 supported?

i tried on the n9009 china telecom model but failed to boot up.
[Galaxy Note 3 Android Development] jetbruceli:
Well there are still ongoing issues like the dialer someone posted earlier and audio sounds. My issues are more related to the camera not as good as stock tw and also the non native support for OTG USB.
[Galaxy Note 3 Android Development] speedyjay:
How do I enable the on screen buttons?
[Galaxy Note 3 Android Development] BillGoss:
Add:

# enable soft navigation keys

qemu.hw.mainkeys=0

to either /system/build.prop or to /data/local.prop

If you want a zip file: https://www.dropbox.com/s/b9hr7w0tbjbrns6/Navigation_keys.zip

Sent from my SM-N9005
[Galaxy Note 3 Android Development] farfromovin:
Can anyone point me in the direction of how to report bugs officially on the latest milestone? I really want NFC to work on the hltetmo.
[Galaxy Note 3 Android Development] Eldartho:
We need an Omni rom port
[Galaxy Note 3 Android Development] testmonkey1:
Also I think a lot of people reverted back to stock TouchWiz which is almost as fast as CyanogenMod on KitKat (lag free experience for both, but a bit longer loading for TouchWiz) I've noticed.

The reasons? As I sad above, performance in the latest firmwàre is very vood, combine that with the S-Pen functions/Multitasking (which I tried to replicate on AOSP but its just not quite the same) and top it with slow development (more noticably the slow fixing of critical system bugs).

Basically I weighted the pros/cons and the only thing that CyanogenMod offers right now is slighltly faster loading times, why would I keep it? Plus I got tired of reflashing my phone every day only to find the same bugs there for months on end.

I would love to return to CM one day, as it is the ROM that suits my need, but in it's current state TW is just better off now.
[Galaxy Note 3 Android Development] Robster83:
I couldn't imagine going back to TW, it's by far and away the worst thing to have ever happened to Android. The only reason I bought a Note 3 was the ability to put CM11 onto its excellent hardware.
[Galaxy Note 3 Android Development] Yank555:
The sad thing is what because of TW KK, and the crappy bootloader update and kernel rebase that came along with it, CM has gotten a lot worse as compared to what it was.

I'm still on the old bootloader running 20140127 nightly.

I've tested 20140416 (so been about 3 months on the late january nightly) and seriously, 20140416 is awfull bad ! Unsmooth, few strange bugs, like lockscreen PIN not working on boot right after entering the SIM PIN, need to turn the device off then on again etc.

Ondemand has become unusable (reboots, freezes), that's thanks to the new kernel base. Touchwake will not work reliably when placing call, as reading the proxy sensor is very delayed on the new kernel etc. etc. but mostly really unsmooth (full stock)... compared to the old one I mean.

Conclusion, I've nandroided back on the old CM, it's a bliss compared to what Samsung have doomed upon CM (and us) with the kernel rebase...

I don't blame CM, they had to rebase their kernel as well in order to accomodate for the new (not downgradable) bootloader, but this has really given me motivation to start seriously looking for a different device, I've had enough crap from Samsung :silly:

Not quite unlikely I'll end up with a Nexus 5, if I can get hold of one...

JP.
[Galaxy Note 3 Android Development] frostmore:
The slowness in CM development in N3,i believe, is due to samdung's locked bootloader.

In the past,cm development was a lot faster in N2 than it was in N3. but thanks to samdung's locked bootloader,ppl are forced to use TW based roms rather than CM based roms.

This i believe is samdung's way of making sure ppl use their TW to propagate their so called popularity and they can claim credit for android's lion share of the market.

Who could forget the EMMC bug found by xda developers in N2 when samdung did not even knew it existed?and how long did it take for them to patch the thing in the TW rom?

the excuse given by the for the locked bootloader due to know is horsecrap at best. and an outright lie.

I believe samdung is supremely jealous that there are ppl out there using their hardware and putting in CM softwarein their phone.and jealous that CM made better roms than they could.

the so alled new features in N3or S5 is just gagetry at best.nothing new came out of samdung other than the crap called knox and knox 2.0.

putting an enterprise phone in normal consumer's hands and getting them to pay for it?

the only reason i bought N3 was to put Cm in it,NOT TW. thanks to knox and their warranty void bullcrap,this willbe the last phone from samdung i will ever own.
[Galaxy Note 3 Android Development] asphaeris:
I laughed, why the **** did you buy n3 ?
[Galaxy Note 3 Android Development] springer.music:
For those of us who'd like some extra S-pen features in CM11, xda member LegendK95 has developed an app called SPenBoardSwitcher (which you probably are already aware of).

I personally use it with MyScript Stylus Beta for handwriting + NextApp Keyboard (AOSP derivative with number row and extra features)

More info about SPenBoardSwitcher:

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

More info about MyScript Stylus Beta:

https://play.google.com/store/apps/details?id=com.visionobjects.stylusmobile.v3_2_store

More info about NextApp Keyboard:

https://play.google.com/store/apps/details?id=nextapp.inputmethod.latin

This is all good but unfortunately, the SPenBoardSwitcher installer doesn't work with AOSP based ROMs at the moment.

You can still get it to work it by extracting the main app from the installer, copy it to /system/priv-app/ , change permissions and reboot.

When you are on a nightly channel, this can be a bit of a PITA...

To make our life easier, you can download a flashable zip file from the following post:

http://xdaforums.com/showpost.php?p=52182589&postcount=115

Hope this helps :)
[Galaxy Note 3 Android Development] thools60:
Well, I'll stick with CM. I really miss the Spen features on TW but the sheer ugliness of it makes me go with CM. I think, eventually, CM's gonna be a great ROM. I really don't have any big issues as it is today and I don't hesitate to use it as my daily driver. It's a pity though that, from what I understand, it seems difficult to get bug reports through to the devs. Why is that? Anybody could explain that to a slow noobie?
[Galaxy Note 3 Android Development] ajm786:
I'm highly interested in getting the Note 3 and putting CM on it. I do have a question though.

Is there a reason why NFC is still not working in CM? Is it a driver thing where the CM team is just having a difficult time getting driver info from Samsung? Or is it something else (like just not high priority)?

Thanks!
[Galaxy Note 3 Android Development] Ogy77:
Guys can we flash newest stcok rom,bootloader and then CM11 or better stay on old bootloader NA6?
[Galaxy Note 3 Android Development] Yank555:
Depends ...

Once the new bootloader is flashed, you'll :

1) won't be able to boot a TW 4.3 ROM

ever

2) won't be able to boot the old CM (like from late january) which is way better than the current one, but not maintained anymore

If you can live with both, you can go ahead and flash.

If not, better keep from flashing it.

JP.
[Galaxy Note 3 Android Development] Robster83:
It works just fine on the international model, SM-N9005. It's the other models that have the problem.
[Galaxy Note 3 Android Development] springer.music:
NFC is working fine on the N9005 and N900P but not on some of the other models (e.g. N900T, N900W8...).

As to the reason why NFC is not working on some models (plus some other bugs which affect all variants) I don't have an answer. What I can say is that I haven't seen much going on for hlte recently, which makes me think that the Note 3 has become low priority. Are the CM devs all too busy with CM11S for the OnePlus One? Maybe, maybe not...

Another thing I've noticed is that there is no Note 3/hlte section in the official CM forum. Who should we talk to to request an official hlte section there?
[Galaxy Note 3 Android Development] ajm786:
Well this is certainly not good news. :( I really wanted the Note 3 because its size and it's AMOLED screen, but did not want to sacrifice on functionality/stability.
[Galaxy Note 3 Android Development] Ogy77:
I know I just wan know can I again CM11 or aosp rom on new rom,bootloader?
[Galaxy Note 3 Android Development] datajosh:
As far as I know, the only person that's been involved with hlte development that would be involved with 11S would be Cyanogen himself so the devs are probably just busy with real life.
[Galaxy Note 3 Android Development] springer.music:
You're most likely right. Let's hope to see some progress soon.
[Galaxy Note 3 Android Development] testmonkey1:
If you are planning to get the N9005 variant, NFC is working just fine.
[Galaxy Note 3 Android Development] ajm786:
I would, but the problem is that the N9005 doesn't support LTE on either Verizon or T-mobile. I'd have to either get the N900V or the N900T.
[Galaxy Note 3 Android Development] bleuwave:
In between the two, definitely get the tmobile because I don't think you can flash custom kernels on the Verizon or the at & t.
[Galaxy Note 3 Android Development] Yank555:
The answer was already in my previous post, the magic word being "old" ;)

So the newer CM will boot, so yes you can go to CM / AOSP on the new bootloader, it's only the old (but for now better) CM you will lose access to.

JP.
[Galaxy Note 3 Android Development] Yank555:
Just in case anyone is willing to help test my alpha kernel, it can be downloaded here.

It will work on both old and new bootloader, kernel it at current CM level, Linux 3.4.87 and ramfs is the one in 20140416 nightly.

JP.
[Galaxy Note 3 Android Development] dtr145r:
Any sound fix?
[Galaxy Note 3 Android Development] Eldartho:
I'd love to see what Omni rom would be like on our devices but that's not gonna happen
[Galaxy Note 3 Android Development] crespi_:
I doubt it's appropriate to be namely, so I'll just say this guy's; I'm a long time official cm user, and i got the note 3 about 2 months ago. This is the first time I've been happier with a non official cm rom. I'm simply unhappy with the development of the official cm11 for this device.
[Galaxy Note 3 Android Development] CZ Eddie:
The Note 3 is probably the closest competitor to the new CyanogenMOD 5.5" phone. So..... hmmm.

Btw, to another poster... do NOT get the Verizon or AT&T Note 3 if you want to run CM11. Neither works.

I'm on TMO Note 3 and so far, so good.

Though it seems like low data reception areas give worse download speeds than I'm used to (on AT&T plan). While good reception areas are giving typical speeds that I'm used to on AT&T phones. But I've only had this phone ~3 days.
[Galaxy Note 3 Android Development] thools60:
Just a noob question. Just how much does the kernel affect the overall performance of the ROM? Is it mostly battery related or is there more to it?
[Galaxy Note 3 Android Development] sauron82:
The kernel basically rums the rom.

Click thanks if I helped you
[Galaxy Note 3 Android Development] Yank555:
Depends on what you're looking for, faux sound is on the todo list, but if you're looking for a fix for the derpy sound when using touchsounds, that's a ROM thing, CM needs to get that fixed, nothing we can do in a kernel...

As [MENTION=4686957]sauron82[/MENTION] put it, the ROM is just a program running on the kernel, so the kernel is the foundation. It takes care of all the low-level stuff, handling hardware etc.

There can be more to a custom kernel than just performance and / or battery life, there can also be added functionality and also the potential for better stability (if the base is derpy, and here it most definately is), like is the case with TouchWake, eXended LED Control, or FastCharge, to name the three I've implmented so far in this alpha release.

You can try kernels, if you don't like what they do, dirty reflashing the nightly you're currently on will remove them, and you're back to stock kernel.

That's also the drawback when on nightly and running a custom kernel, you'll have to reflash it after each nightly.

JP.
[Galaxy Note 3 Android Development] thools60:
OK. Thanks for clarifying a LOT for me. I've never tried to flash a kernel. Is it the same thing as flashing a ROM? Do I need to do a clean flash? Is there anything in particular I need to do, if you don't mind my asking?
[Galaxy Note 3 Android Development] Khizar:
Just flash it in recovery, no need to clean flash, even wiping cache/dalvik is useless but you can if you want..

Sent From My SM-N9005 To All You Wonder Nobodies!!
[Galaxy Note 3 Android Development] Yank555:
Just flash. You'll see an Aroma Installer, giving you choices, if you don't know, just hit next, you'll be going with my settings.

JP.
[Galaxy Note 3 Android Development] cam30era:
Well, not exactly true. You are correct that the Verizon RETAIL Note 3 (with it's locked bootloader) can not run CM11. However, the Note 3 Developer Edition (for Verizon network) has an unlocked bootloader, and runs fine on CM11, or any other ROM or kernel. Available directly from Samsung (and unsubsidized).
[Galaxy Note 3 Android Development] springer.music:
I think he refers to the crackly sound you get for the first few few secs in certain situations (regardless of the touch sounds being on or off).

In my case it happens when the phone is in deep sleep and a sound event is started by an app (e.g. an alarm goes off, someone calls me through Hangouts, etc): for the first few seconds the audio is horribly crackly, then it settles.

Sounds like the phone struggles to set the correct sample rate or an audio buffer is to small.

This doesn't seem to happen with regular phone call ringtones and SMS notifications.

It appears to be a CM11 issue which only affects the Note 3 as it doesn't happen on a GS3 on CM11.

I can only reproduce this bug when the phone is in deep sleep.

I've tried your kernel but the issue is still there.
[Galaxy Note 3 Android Development] Yank555:
The opposite would have been a surprise, as I've done nothing so far that might help ;)

Could also be the CPU(s) freq. to be too low and taking a little to scale up...

JP.
[Galaxy Note 3 Android Development] CZ Eddie:
I didn't bother mentioning the VZW Dev edition because you have to pay full retail for it. You can't get it via the two-year agreement or any other specials through VZW.
[Galaxy Note 3 Android Development] cam30era:
Correct