yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Rintenfinten:
Settings / Status Bar doesn't seem to work. Anyone having the same Problem?
[Galaxy Note 3 Android Development] Bobanovicz:
Same here
[Galaxy Note 3 Android Development] temasek:
Those on V16.4 and having Settings FC in status bar probably needs to clean flash.

Backup and do it.

I'm not having FC issue.
[Galaxy Note 3 Android Development] Barmenchik:
+1 NO FC. For me OK.:p:good:
[Galaxy Note 3 Android Development] Rintenfinten:
I did a clean flash...
[Galaxy Note 3 Android Development] tommyhui:
Hello, is there any news about fixing the sensors of cardboard vr?
[Galaxy Note 3 Android Development] el mario:
Seem tot have missed the f2fs workaround. Can anyone tell what its for and how to?

Verstuurd vanaf mijn SM-N9005 met Tapatalk
[Galaxy Note 3 Android Development] ekre:
clean flash, fc in settings

status bar clock is italic by default, looks strange
[Galaxy Note 3 Android Development] enigma2u2:
Didn't Google change their logo this week
[Galaxy Note 3 Android Development] brakatz:
---------- Post added at 10:04 PM ---------- Previous post was at 10:01 PM ----------

[/COLOR]

Thanks. Logically speaking if you device works and mine doesnt it can only mean that my hardware is defective. Although some reported also having the issue. We will have to wait for people to manifest.

Have you tried a bluetooth device that consumes data in a constant stream?

For instance watching videos and having the audio stream to a bt speaker will crash wifi. Listening to spotify streaming audio to bt stereo system will crash wifi.

In some cases when the wifi doesn't crash. In these cases youtube videos will lag. They load, slow.

Thanks for the brain work
[Galaxy Note 3 Android Development] Caillin:
I did quite a bit of testing between all the governors after reading up on them, and arteractive seamed to be the most responsive, though it can be very hard to pick differences. Only other thing I can think of, is I recently moved back to using F2FS after a hiatus of a few months, and I feel it has definitely helped with the smoothness. For me, my test scenarios that cause occasional stutter are Press newsreader when swiping forward through articles with an image, and scrolling in the XPA/Tapatalk apps. For some reason, those two specific scenarios are almost impossible to get scrolling smoothly. Everywhere else is perfect for me on Nova launcher.

To be honest, the speed and smoothness of Tema's last CM11 build haven't been surpassed so far. If you feel like mucking around and flashing, try flashing back to it compared to the lollipop builds and see what I mean. I was tempted to move back, but anything CM11 based just ends up with endless Play Services FCs.

I think I'm just now resigned to the fact that there will be a little jank, here and there, and only occasionally, and that's just the price of entry. I have noticed that it doesn't exist on the Nexus devices from what I've handled, so I'll be very tempted to see how the new Huawei Nexus 6 turns out as a potential upgrade from the Note 3.
[Galaxy Note 3 Android Development] temasek:
Those with settings fc on statusbar settings, read the following

Check out davjjak's Tweet: https://twitter.com/davjjak/status/639570465191661569?s=09

Basically he was saying deleting /data/data/com.android.settings did the trick.
[Galaxy Note 3 Android Development] svbarbosa:
You have to run it at least two times in sequence to trigger the 2.8GHz.
[Galaxy Note 3 Android Development] Spellable:
Hey guys, can anyone one here help me with the problems I've had moving from ext4 to f2fs?

Specs if that helps:

Sprint Note 3 (hltespr)

TWRP 2.8.7.0

Temasek's Rom 16.2

OC5 Baseband/Modem

On TWRP whenever I try changing the cache to f2fs it shows successful, but, immediately afterwards it shows "E : Unable to mount '/cache' " and will only be able to mount again if switched backed to ext4. Also when changing data to f2fs it doesn't even succeed and instead says failed at the top with the message:

"E:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk1k0p26 process ended with ERROR=1

E: Unable to wipe '/data'.

E:Unknown MTP Message type: 1

E:Error changing file system"

When I fix the data error by using terminal and typing "mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata" then rebooting into recovery, the data is set to f2fs but I still get the error "E: Unable to mount '/data' "

I've tried many things to fix this but so far none have worked out.

Somethings I've tried were:

Disabling MTP

Removing SD Card, Restoring Original Stock Rom, Re-Rooting and Flashing TWRP 2.7.8.0

Flashing FormatPartition.zip

Enabling the setting "rm -rf instead of formatting"

Even downgrading TWRP and trying with all the versions down to before the f2fs feature was even implemented.

Would really appreciate some help, other than that though, Rom has been working great. :)
[Galaxy Note 3 Android Development] temasek:
Downgrade your recovery.

I'm still on twrp 2.8.30
[Galaxy Note 3 Android Development] BazBaz:
It should be a better file system for flashmemory such as ssd and sd cards. Try search for how.
[Galaxy Note 3 Android Development] viniciusrsouza:
Oh! How time goes by so fast! Last year I was so admired by Nexus 6, but Google/Motorola never brought it to Brazil and, to be honest, Temasek's work simply made me stick with my Note 3 and for the first time ever not upgrading and even not bothering about the new Note 4! Now 2015 is coming to an end and even Note 5 didn't call my attention! (Maybe for obvious reasons...)

Anyway, I truly understand you. I'm using Samsung Android phones since Galaxy S II and I'm convinced that I would only get completely rid of random stuttering if I use a Nexus device, and even with that I know there are some rare stuttering/lags. By the way, even iPhones suffer from this occasionally! Maybe only some Windows Phone devices can state real smoothness nowadays, if I'm not wrong.

Back to the topic, I'm facing freezes/reboots randomly when using ondemand even when not typing here on Chrome, so something is wrong in my setup and obviously it's full wipe time for me, although I really can't do it for the next few weeks, at least. So now I'm back to interactive governor with default CPU limits and GPU running at 320, but with Force GPU Rendering on again. Don't know if there is any difference, it's something placebo effect, but I think maybe it's so smooth as it would be with CPU at 2.8 maximum speed.

About F2FS, on next full wipe I will surely try it!

And, finally, we are very lucky to be running Temasek builds! I simply can't even remember all the lags and slowdowns when running TouchWiz!
[Galaxy Note 3 Android Development] BazBaz:
Well that worked for me. Thanks!! :D:D:D
[Galaxy Note 3 Android Development] Spellable:
I've tried, though for some reason twrp for htlespr didn't get f2fs till the 2.8.6.0 update. So the only versions with the option to go from ext4 to f2fs are 2.8.6.0, 2.8.6.1, and 2.8.7.0, which all don't allow me to mount on f2fs.

Unless there is a way to add f2fs to an earlier version or to flash and boot the general hlte twrp on my sprint phone then I don't think this will work
[Galaxy Note 3 Android Development] davjak:
thank you

Encode Sans is the font used, sadly it messed with the lockscreen clock

Installed Explosed and lockscreen clock mod and all is fixed
[Galaxy Note 3 Android Development] Caillin:
I went from Note 1 to Lumia 920, to Note 3. I really really liked the 920 running Windows purely because it was 100% fluid in all situations, without fail. There was just no way to make it stutter, and its obvious that the OS was built around perfect screen drawing/rendering first and foremost. The only thing that drew me back to Android is just the app situation. Having said that, the Note 3 running this ROM by Tema, is pretty bloody brilliant. Without him still supporting the platform, I probably would have already jumped to the Nexus 6. The Note 5 is very tempting, from my play at a store, it seems to perform very fast, and Samsung have now added the ability to theme out the fisher price style settings menu and dropdown in Touchwiz which I abhor. Still waiting to see the new Nexus though, and also see what MS has up it's sleeve in the 950XL and how many app developers could be bothered porting their apps to the new Windows Phone ecosystem with the new code conversion tools.

Also, back to topic, I've also just been playing around with ondemand governor, and I too get a freeze and reboot, regardless of frequency setting, in most of my apps. I think there may be something bugged in this version of Tema's kernel regarding it. But yeah, give F2FS a go, as I'm positive it wasn't a placebo and it made the phone more fluid. I think a slow file system really hurts Android in terms of smoothness, and may explain why the newer Samsungs seem to perform a lot better than the previous ones, due to their efforts and change to UFS. If you look at the difference between the S5 and S6 here: http://www.anandtech.com/show/9146/the-samsung-galaxy-s6-and-s6-edge-review/7 it's pretty telling how much of an improvement they've made to the underlying storage performance.
[Galaxy Note 3 Android Development] brakatz:
Cardboard is broken here too
[Galaxy Note 3 Android Development] Buslova:
Well, I've ran it back to back several times and it still never forced my clock to go above the 2.2 I have it set at. What app are you using to set your cpu clock? I'm using kernel auditor.
[Galaxy Note 3 Android Development] Journyman16:
Mine works fine and was dirty flash over 16.3, just ran the zip as DL'd in OTA. But I don't have any of the animation stuff running so maybe try turning them off and see if it still happens?

I have to head out for a bit so can try streaming some music in the car. Mostly my BT is passive stuff, not streamed.

It's not necessarily a hardware issue - like almost all programming, Android software seems quite capable of providing random 'fun' in how it performs from device to device. To give an example I had to rebuild some PC's in a remote office. They gave me a USB that was supposed to connect to Melb and DL the images. 75% of the time it would fail because some 'genius' had made the install process load the AV software in the middle of the process - even the slightest hesitation in connection and the load would abort.

I've been thinking about this for some time because if you go back through the posts, it is exceedingly difficult to find common factors in Tema's work - problems seem to happen almost randomly - for every person with an issue there's another 3 that did exactly the same thing and had it work.

Except for the OTA I did yesterday, I now clean flash pretty much all the time - if I do dirty it is only because people have reported a problem so I flash and see if I have it. THEN I wipe and clean flash after, even if I didn't see the issue. Seems to work - I hardly ever have issues that matter. e.g. I have one with Settings/Sounds - when I change to my custom sounds Settings FC's but it DOES make the change. But every so often I flash a new version and Settings DOESN'T FC when I change the sounds.

I had keybd FC's but they are mostly gone now I freeze the AOSP one and use Lollipop 123 keybd. Been maybe a week since the last one. And even there the randomness strikes. Sometimes I have to tap in the text windows to get the keybd back and other times it FC's then pops straight back up.

I think what is happening is Physics. Years back, before spintronics came along, there was a paper in SciAm about randomness in IC's - after all the testing they said we can expect at least 1 bit in a gigabyte to be wrong, simply because things are so small. Spintronics then dropped the sizes even further so I would think that might increase the number of random errors in chips and disks.

So when I see a few people with issues that others AREN'T having, that old paper comes to mind. :D The faults might even be why they have different ratings for each phone - they test them and downgrade the rating for phones with noticeable errors in hardware.

Anyway... just rambling while I wait for the missus... :D
[Galaxy Note 3 Android Development] svbarbosa:
Trickster just to check figures. No kernel mods applied.

The problem was there on kernel 1.25 and earlier versions. Maybe Tema has fixed it.

Anyway I am know running another rom. Will test again when back to Tema's.
[Galaxy Note 3 Android Development] jufegoco:
Sorry, I can't answer your questions because I have this phone only about a week and as you said maybe it's early to judge this. You're looking for a very specific situation that it's possible not represent our interests or I don't have the expertise to answer this questions...

Sorry for my bad english
[Galaxy Note 3 Android Development] modifiedbears:
I'm getting "No SIM card" after installing cm-12.1-20150903-UNOFFICIAL-temasek-hltespr-V16.4.zip

I flashed back to a stock ROM and everything worked fine so it's not a hardware issue.

Any ideas?
[Galaxy Note 3 Android Development] jufegoco:
Can you [MENTION=4459766]SuperSmashedBro[/MENTION] tell us what xposed and frame did you use exactly? You can make easier our efforts.. :D:D thank you very much...
[Galaxy Note 3 Android Development] chazey2:
Alpha 4 apk and V73 working great here.
[Galaxy Note 3 Android Development] BillGoss:
Did you do a clean (wipe data, system) install?

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Caillin:
Just had another thought. Would be good to compare certain areas in the stock OS where you are getting stuttering. I'm 100% smooth in places like the settings windows, chrome (with the 512mb tweak), Relay for reddit, Play Store. Pretty much everywhere.

I turned on the GPU profiler to try and get an objective measure of any frames that are taking longer than 16ms to output (which would likely result in a dropped frame), and all the above apps give me smooth graphs under the 60hz/16ms frame render time. I've also tried Interactive governor, and moved the max frequency back down to 2.2Ghz based on comments above, and didn't notice any change in frame rendering time, so I'm going to leave it at 2.2 for the time being.

I'd be interested if you could post some screenshots in some of those apps and areas and see whether the frame drops your seeing are consistent with others (and myself). If it is noticeably different, then we can start looking at what other background services or apps you have running differently to others.
[Galaxy Note 3 Android Development] Caillin:
Here are some screenshots from some areas that people complain about scrolling stuttering.
[Galaxy Note 3 Android Development] peped94:
i can see the graph always higher than the green line when you scrolling fast in playstore main page and in the apps details. the instagram also suffer from that stutter
[Galaxy Note 3 Android Development] strifej:
Anyone seen the wifi problem where it won't connect to a saved network until you "forget" it and re-enter the password?

I was on 16.1 when everything was normal, then it started happening. I just clean flashed 16.4 and I'm getting the same issue. I connect to a wifi point, then after a reboot it won't reconnect anymore. In wifi it'll say saved. Only after I forget and connect again with password does it work.

I'm on baseband OF3 if that makes a diff (newest I believe).

I'm going to try to restore an old backup (pre-V16) to see if it works there.
[Galaxy Note 3 Android Development] hurdubaiev:
Hi, did anyone encounter any problems after formating to f2fs? I've read some comments here http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/ that say they had some corruption problems. Can you connect the phone to a windows machine and see the internal sd? Were there any problems in formatting back to ext4?

Thanks
[Galaxy Note 3 Android Development] Journyman16:
I haven't tried formatting back to ext4 but it's all working fine on F2fs. I did the terminal command to format Data so have Data, System and Cache all on f2fs

---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------

My first thought was, "nope, don't have that" but then I remembered the last couple of versions I do have a small issue - not quite as bad as yours but if I go to a previously connected wifi, it isn't automatically connecting like it did. But I can just tap the connection and click 'Connect' and it does - don't have to 'forget' it first.

Doesn't seem to be any relevant settings to auto-connect or similar. I will look some more.
[Galaxy Note 3 Android Development] crazyboyxx:
same situation here, when using the phone a period of time, need to toggle the wifi / 4G to re-enable data.
[Galaxy Note 3 Android Development] JWnSC:
I believe it's a problem with the sprint note 3 recovery. I tried a while back but had to use the hlte note 3 recovery. It's complicated though. I had to replace metadata folder from the hlte rom to the hltespr rom so it would flash when using the hlte recovery.
[Galaxy Note 3 Android Development] rockerdudelive:
does anyone have the problem with settings force closing when uninstalling an app? I had it on 16.2 so i fresh installed 16.4 and only flashed gapps (tk universal pico) and tried to install an app from the play store (in this case sms backup and restore) and when trying to uninstall it always says unfortunately settings has stopped.

before I did a clean wipe I saw that it would still be in my titanium backup. even more than once. It's like the apps don't get deleted but the play store sees it as deleted :(
[Galaxy Note 3 Android Development] temasek:
Cm bug

I'll pin point the culprit and kill it by next build hopefully.
[Galaxy Note 3 Android Development] wil32:
nfc not working on n900w8, filled a bug report.

need it for upcoming Android Pay.

have a great weekend
[Galaxy Note 3 Android Development] BazBaz:
Think you didn't read alot about CM. NFC doesn't work on CM for Note 3.
[Galaxy Note 3 Android Development] Link.exe:
What's the difference between this, and regular CM12.1?
[Galaxy Note 3 Android Development] Gggggas:
Guys sorry if this has been asked before I searched the thread with no luck. Titanium can't access my sd card and I have unchecked the supersu mountspace.

Thanks
[Galaxy Note 3 Android Development] Spellable:
Thanks man your fix works great, really appreciate the help :)
[Galaxy Note 3 Android Development] temasek:
V16.5 later today.....
[Galaxy Note 3 Android Development] EarlZ:
Until now messaging/keyboard FC is still rampant, Will this ever get fixed or is this a CM issue ?
[Galaxy Note 3 Android Development] temasek:
Spellchecker issue.

Workarounds

1. Enable "Disable FC notifications"

Or

2. Freeze "AOSP Keyboard" and download Google Keyboard or use your favourite keyboard.
[Galaxy Note 3 Android Development] saszseb:
It does work on CM (sm-n9005).
[Galaxy Note 3 Android Development] Journyman16:
Hopefully fixing it for uninstalls will also fix it for the Sounds? Other than tha minor issue I have no FC's (touch wood) even for Keybd (using Lollipop 123 keybd with AOSP frozen)
[Galaxy Note 3 Android Development] temasek:
Build V16.5

hlte md5sum - 1514977dd7f3d302cce365f48200b199

hltespr md5sum - 6cb12ac86de5c86230acbd65c7c11f46

CHANGELOG

FIXED - Settings FC immediately after uninstalling an app in "Applications"

FIXED - TRDS statusbar header

FIXED - 4th navigation bar button not appearing in landscape mode

FIXED - Possible overlapping of Power Button in navigation bar when IME switcher is shown concurrently.

Added - Up to 14 font variants to Status Bar Clock. Original feature by yours truly.

Added - Up to 14 font variants to Status Bar Weather

Added - Font size for Carrier Label in Status Bar

Added - Lockscreen Rotation

Added - System App Removal in "Privacy" settings

Added - Option to show Volume Panel in expanded mode by default in Sounds Settings

Added - MOTO X Ringtones and Notification Tones (This caused increased in overall fize size. I may remove it on next build)

Updated - Change in pictures for Custom Headers (Not confirm will stay. I'll see if I like it or not)

HEADS UP moved to "Notifications"

Misc frameworks bug fixes

Updated cm sources

I don't always write so much. Just for today

Enjoy :)
[Galaxy Note 3 Android Development] sebastjanp:
10x Tema. Don't remove them :)

Poslano z mojega SM-N9005 z uporabo Tapatalk
[Galaxy Note 3 Android Development] jvandenbroek:
Is there a way to increase the font size for network traffic stats in the status bar? My DPI is set to 380, which makes it (with both incoming and outgoing enabled) really tiny :o
[Galaxy Note 3 Android Development] temasek:
Let me think about it.
[Galaxy Note 3 Android Development] shiverz07:
Yay for landscape mode on lockscreen! But is there any way to get the visualisation to be set across the whole screen in landscape mode?
[Galaxy Note 3 Android Development] brakatz:
It is fixed. I remember the first things I did when I first flashed this phone was flashing a modem. After 5 months it has this this one modem driver.

And you can guess now. Wrong modem.

Flashed modem N9005XXUBMI6 on April

Original modem N9005XXUGBOA1

Wifi and bluetooth worked. Like a cat on catnip but it worked

Fix found on this post

http://xdaforums.com/galaxy-note-3/general/ref-galaxy-note-3-sm-n9005-gsm-modems-t2842806

I apologize for causing any confusion
[Galaxy Note 3 Android Development] pearljohn:
Anyone else have Status Bar setting crash when clicking on it in System settings? Dirty flashed 16.5 over 16.2 Cheers.
[Galaxy Note 3 Android Development] daddycruel:
Has anyone found a fix for this?

Flashed 16.5 today, problem still remains :(
[Galaxy Note 3 Android Development] pearljohn:
Thanks for the reply. Time I did a clean install then)
[Galaxy Note 3 Android Development] BazBaz:
Try this, worked for me.

---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------

Tell us how you got it to work then on your CM 12.1 for Note 3? We all would like to know.
[Galaxy Note 3 Android Development] pearljohn:
Cheers mate. That worked. Saved me a lot of time. Don't know how I missed that, thought I'd been reading all posts, doh.
[Galaxy Note 3 Android Development] Journyman16:
DAMN you good man... :D
[Galaxy Note 3 Android Development] verrix:
Thanks, please always write detailed changelog like this one! :D

---------- Post added at 07:01 PM ---------- Previous post was at 06:55 PM ----------

Same here. Don't close the app, I've found that if you open the lateral menu and click on 'inbox' again (or wherever you're in) just makes the emails appear again.
[Galaxy Note 3 Android Development] saszseb:
- get two device and turn on NFC on both phone (I have sm-n9005 and Sony)

- touch the devices together or bringing them into proximity to a distance of typically 10cm or less.

- after establishing the communication, touch the screen to get data transfer.

(CM 12.1_v16.5).
[Galaxy Note 3 Android Development] Spyritus:
+1, NFC does work on SM-N9005 (hlte)

I tested with some amiibo of mine.

https://wiki.cyanogenmod.org/w/Known_Issues_page_for_hlte
[Galaxy Note 3 Android Development] shero73:
Sorry if this had been asked before, can't find anything in search but I was wondering if there's any way to tidy the settings menu so you can just see what you need. I'm certain this was possible in kit Kat. Cheers
[Galaxy Note 3 Android Development] BazBaz:
Woow, that was a thing i totaly missed it worked again. :good: Still thought there was a driver missing or something like that.

Didn't know it was fixed. Not that i need it though ;)

Thanks for your reply.

But for the guy i replied to my answer was good, for his Note 3 it isn't working. :D:p
[Galaxy Note 3 Android Development] HAIMH2012:
Is the email bug is a bug with the gmail app itself or is it a bug with the rom?

Because i have that too.

V16.5
[Galaxy Note 3 Android Development] daddycruel:
Don't know, same bug happens in exchange mail app (Nine)