yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] menioseten:
V156 is amazing and smooth !!!!

A question,Recommended Trickster ntelliplug on Mpdecision off ??

Thanks.
[Galaxy Note 3 Android Development] NoXXX:
Well I don't see any significant changes to wakeup lag. It is about a second, as it was before. IMHO.
[Galaxy Note 3 Android Development] Gggggas:
Using the stock Temasek kernel, Intelli is recommended to be on and mpdecision off :)
[Galaxy Note 3 Android Development] cpxyz1:
if i have f2fs enabled with v155 do i have to rewipe everything and do the whole process of enable f2fs if i wanted to flash 156?
[Galaxy Note 3 Android Development] temasek:
No

Just flash it.
[Galaxy Note 3 Android Development] cpxyz1:
getting a massive battery drain. i searched the thread and tried disabling google services but it doesn't allow me. i have location and sync off with greenify and amplify. not sure what to do
[Galaxy Note 3 Android Development] jdgamble:
I already miss this ROM damn this Tizen xit making me use TW based ROM. i passed on buying an Android wear device since it's more work to actually get into noti blahblah. Need the call feature also, so i'm stuck. sad days ahead of me... :(
[Galaxy Note 3 Android Development] temasek:
To ALL

I won't be reading or replying anymore gapps related battery drains. It's not even related to this rom or kernel.

Pls note.
[Galaxy Note 3 Android Development] ollden:
You are right. I just did a clean install.

Thank you.
[Galaxy Note 3 Android Development] dramitt_live:
Put this in the OP :))
[Galaxy Note 3 Android Development] songoku2k:
Thank you for this rom

Cast screen does not work any more?

I think in v154 or v153 this function has been working.
[Galaxy Note 3 Android Development] Slypnslyde:
When using twrp the sdcard says internalsd 0 it's blank but not when using philz
[Galaxy Note 3 Android Development] Sik-1:
Works fine over here, jus finished watching a movie
[Galaxy Note 3 Android Development] boriska975:
Looks like Philz CWM touch has been updated

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commits/cm-11.0
[Galaxy Note 3 Android Development] shjane:
Good day

[MENTION=2332422]temasek[/MENTION] - do I have to "Restore your /data & /data/media & /cache from your backup" ? I would like to start fresh so can I just leave this step when changing to f2fs?
[Galaxy Note 3 Android Development] temasek:
No need. Nothing to restore except u sure u don't want to backup your internal sdcard? If u really sure then skip.

---------- Post added at 01:57 PM ---------- Previous post was at 01:57 PM ----------

It's already in V156.
[Galaxy Note 3 Android Development] shjane:
Damn that was a FAST response! were you waiting for me? Hehe

Jip Jip its wiped, did it last night (usually just use my sdcard for music storage).

Thanks! VERY eager to try the new philz + f2fs - on my way to do so everything is downloaded - now to start.

---------- Post added at 06:21 AM ---------- Previous post was at 06:21 AM ----------

[MENTION=2332422]temasek[/MENTION] .Silly question.. but I have followed your guide to convert to f2fs + flashed v156.. how/where do I check that my cache/sd card is now f2fs? :confused:
[Galaxy Note 3 Android Development] Mufasax:
Go back a few. Instructions are there.

---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------

Here you go. Use "System Info for Android" from Google Play Store.
[Galaxy Note 3 Android Development] shjane:
Thanks m8!
[Galaxy Note 3 Android Development] knite75:
Clean installed v156.

The back of the phone, near the camera, it's really really hot. What gives?
[Galaxy Note 3 Android Development] menioseten:
@ temasek,V156 I have no choice store download in the external storage card.I tried with two different browser.

Your rom is fantastic.Thanks.
[Galaxy Note 3 Android Development] temasek:
I have no control over what browsers have in their settings. I'm using Dolphin and it has the option to choose.
[Galaxy Note 3 Android Development] shjane:
Have you let it sit for a while after install?
[Galaxy Note 3 Android Development] temasek:
Those using Dynamic System Bar.

I've updated the frameworks from patch set 1 to patch set 6. It's in V156

Fixing the crazy color changing doing video playback in landscape mode on nav bar.

Just in case u guys didn't realise. Not perfect yet but very usable.

On another note...

Hlte only

Temasek Kernel v3.98.3 EXP4 is up
[Galaxy Note 3 Android Development] InteliDroid:
Hey, so when I flash temasek rom, it flashes the kernel too? And also I get a lot of battery drain compared to other roms, i have n9005
[Galaxy Note 3 Android Development] ravian29:
Same here i think its gpu problem when i set it to 450 or 389 it makes mobile really very hot, i always use it on 320 which makes it feel better

Sent from my SM-N9005
[Galaxy Note 3 Android Development] stavca:
I'd recommend to UV as much as you can (as your chip is able), it's a thing you can do in not so long time and it's really worthy ;)

if you want to have great performance and cool device, here are my tips :)

- HW mod - graphite pads to get heat from chips away

- UV as much as your chip is able to - install for example Antutu and set your min and max CPU freq to highest freq you want to use and run Antutu test, if it pass, try to lower voltage for this freq ;) but at first find out what is your CPU binning and according to this you can start with much lower voltages :) and don't be afraid if your binning is low, mine is 1 I think but I'm still able to run 2265MHz at 965mV perfectly stable ;) this UV lowers heat very much and it should decrease battery consumtion also

- set your max GPU freq to 389MHz, I tried BMs and run FPS meter in games I mainly play (Dead Trigger 2, Real Racing 3) and it didn't make any difference for me except the CPU temp which is even lower because of this ;)

after those mods, I can play 3D games, run BMs and do every "heavy stuff" without thermal throttling which is good because I always have full power :)
[Galaxy Note 3 Android Development] Yank555:
Well I was on vacation enjoying Barcelona :D

I'd say, yes and no.

Hardware-wise, it has an uprated SOC (805 vs. 800), giving it more CPU and GPU power potential. But well, the Note 3 is pretty powerfull, so not really worth upgrading for this reason (at least not for me).

Software-wise, well, it's a Nexus, and hell, I've never seen anything as stable as my Nexus 5 and 7, can't comment on other Nexus devices, but none of those 2 have

EVER

random rebooted ! While my Nexus 7 is stock rooted, it's probably more "logical" and to be expected, my Nexus 5 runs SlimKat plus my kernel with mostly the same stuff that's in my hlte kernels, and it's so rock stable, it's incredible. And I even get decent SOT given the tiny battery it has (3-5h over 18h on battery with everything on at 2.5GHz).

So for me, yes, it will be a huge step up well worth the upgrade.

I'll grab one the second I get a chance, but giving I live in a country which is hardly to be found on a map, that might be in a few months only, though :(

JP.
[Galaxy Note 3 Android Development] LancerV:
Yeah
[Galaxy Note 3 Android Development] ajm786:
This is absolutely maddening.

I just finished yet another brand new, clean install, v93.12, no tweaks whatsoever to the kernel using either Trickster or touching the CM settings, everything default.

I reboot...and all my accounts are gone. Email, Google, and CM. I had set them up perfectly and just with a simple reboot, I have to do it all over again.

How do you catch something like this with a logcat when it's completely unexpected? tema? yank? Any input?
[Galaxy Note 3 Android Development] temasek:
I'm not interested in old builds.

Try V95 as it is first.
[Galaxy Note 3 Android Development] ajm786:
V95 has the same problem. It's why I started backtracking doing installs from tonight. Here is what went down with v95 earlier this evening.

V95, after install, I reboot once or twice, and let it settle in while I'm setting up interface and customization. No problem, sometimes it's not finished building cache or something, so it freezes and needs to reboot.

After I'm finished setting up everything nicely, I reboot. Upon startup, the nav bar is gone, there is no background wallpaper. I reboot twice. Finally, everything is back. However, all my launcher settings are completely forgotten, and even worse, all root apps have been completely forgotten and reset. In other words, I'm back at square one, and have to do everything over again.

I've been having these issues every build after v85, which was the most stable of the bunch. It's like something in the ROM (or maybe even kernel) is forgetting settings and/or getting corrupted on shutdown/bootup.

There's someone else who reported the exact same problems earlier in this thread, and he has the same phone I do: the SM-N900T (T-mobile Note 3), so this is not an isolated issue.
[Galaxy Note 3 Android Development] txpxsx:
Google camera's video is stuttering fyi
[Galaxy Note 3 Android Development] K Dotty:
Iv also been having this, only way around this I've found so far is to full wipe after each build before you upgrade. I had this problem when upgrading to v90 (still using it) and because of this I only upgrade my ROM a couple of weeks

Handwritten from my Note 3

EDIT: Its always a good idea to wipe when moving to a new version of android AFAIK
[Galaxy Note 3 Android Development] LancerV:
Did you go back to a TW rom and than back to an AOSP rom?
[Galaxy Note 3 Android Development] ajm786:
Exactly why I embarked on the crack-flashing trip I did last night. I am indeed fully aware that different Android versions are best off being installed via clean wipe, not dirty wipe/install.

Yes. I tried going back to NE6 official, then clean wiping and installing Temasek.

Here's some more observations.

For the first time last night in about a month, I decided to give plain old vanilla CM11 a shot. I can tell you that generally, it is much more stable than Temasek, although it has some ridiculous bugs that need fixing that Temasek's ROM just puts it to shame with. Having said that, after I got the ROM all configured the way I wanted, I installed Tema's latest kernel.

The instability (or at least some of it) followed. I was watching a 4.6GB video that was on my external SD card. After about 30 minutes, it started to stutter; nothing I could do to shake it. So I rebooted the device. Upon restart, the entire video file was gone, like it had been deleted. I got rid of Tema's kernel and installed Yank kernel, and was able to not only find where the video was (it was "hidden in the same directory), but finished watching it, stutter free.

Regardless, I switched back to Tema's ROM because the stupid CM bugs (audio routing issues, notifications corruption, etc.). Currently, I'm on Yank's latest kernel, and Tema 93.12. 95 was too unpredictable for me.

Like I keep saying, I know tema and the devs want logs, and trust me, I know the moniker: Logs or it didn't happen!. But I really don't know how to handle this. If everything works great, you've got everything configured the way you like, and all of a sudden after a reboot or a random FC, you lose random settings in the OS. I guess the only way we'd be able to track this down is to have logcat running all the time, and then spam tema with it, but I'm sure he's got better things to do than fish through an endless sea of logcats.
[Galaxy Note 3 Android Development] LancerV:
Did you odin back to NE6 or just flash the rom? You have to odin if you go from AOSP to TW. Other wise you will have all kinds of issues
[Galaxy Note 3 Android Development] ajm786:
I'm actually a quite seasoned crack-flasher. :) So the answer is yes: Odin or nothing at all.
[Galaxy Note 3 Android Development] LancerV:
Do you wipe internal storage?
[Galaxy Note 3 Android Development] ajm786:
Complete wipe of all partitions, including data/media.

---------- Post added at 09:41 AM ---------- Previous post was at 09:11 AM ----------

I think I'm onto something. Well, not anything new I'm figuring out, but this may surely help.

Dynamic Fsync is enabled by default in tema's and yank's kernels. I had my suspicions that this may be the culprit, so starting from late last night/early this morning, after all that flashing, I started disabling Dynamic Fsync. I found someone else who has a completely different device experiencing the exact same thing we are on our phones, almost verbatim. Here's the link.

http://rootzwiki.com/topic/36706-ro...tock-android-443-ktu84m/page-951#entry1522394

tema/yank, any thoughts on disabling dynamic fsync by default to help with these issues?
[Galaxy Note 3 Android Development] temasek:
OK next build
[Galaxy Note 3 Android Development] ajm786:
Awesomeness!

Oh yeah, just to make sure DO NOT DISABLE FSYNC. Disable DYNAMIC FSYNC please. :D My bad, just caught that.
[Galaxy Note 3 Android Development] temasek:
I know the difference. :p
[Galaxy Note 3 Android Development] ajm786:
lol!

Yeah, no worries; I mainly made that correction because I don't want people who might be having the same issues to read that and then blame me later and say YOU TOLD HIM TO TURN OFF THE WRONG THING!!!!1!1!!111zzz!!!!!!11

:D
[Galaxy Note 3 Android Development] LancerV:
Does the performance toggle really do anything?
[Galaxy Note 3 Android Development] temasek:
Don't use the rom performance settings.
[Galaxy Note 3 Android Development] Yank555:
it's disabled by default in my kernel, but in Aroma it defaults to on, so if you switch it off in Aroma, it will never be active.

Also, if activated it will be about 1 minute after boot complete only.

But I've used it active since I got my n9005, be it on TW back then or whatever I've used in the meantime. Working fine.

Btw, dynamic fsync registers to the kernel panic handler, so if the kernel panics, it will flush the caches before rebooting. Only danger being a battery pull with screen on (you shouldn't anyway) or a plain reboot without kernel panic (rather seldom).

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta8 (3.4.92) kernel.
[Galaxy Note 3 Android Development] Eldartho:
Tema will your kernel with any cm based aosp ROM? Thought I'd ask before I might mess something up
[Galaxy Note 3 Android Development] temasek:
Welcome back :)

On behalf of the users, would you be kind enough to support f2fs (data & cache) for your kernel?
[Galaxy Note 3 Android Development] Yank555:
Thx ;)

Of course, no problem ;)

But you'll need to fill me in on the details, as there is likely more that just f2fs support source-wise in the kernel itself, ramfs needs changes, too, I suppose ?

JP.
[Galaxy Note 3 Android Development] temasek:
U can extract from mine.
[Galaxy Note 3 Android Development] Yank555:
And that will work for both stock CM and temasek / ext4 and f2fs ?

That'll be a very easy move, then ;)

Will have a look later tonight after work.

JP.
[Galaxy Note 3 Android Development] ollden:
Where do you look to see if it's f2fs or ext4 in this application? Because I downloaded it and I didn't find the info.
[Galaxy Note 3 Android Development] temasek:
Uhhhhhh I think yes.

When I initially tested my f2fs kernel, my rom did not add the following commit to rom but I managed to boot up fine without conversion to f2fs yet. This was to test if kernel boots up fine on my EXT4 partitions.

https://github.com/temasek/android_system_core/commit/427000ecc13b54f59537a799902f397d36a45588
[Galaxy Note 3 Android Development] ElRongMcBong:
Dont forget LED-fading :D
[Galaxy Note 3 Android Development] btvolta:
So, has anyone noticed any huge differences in performance with f2fs? I haven't made the transition yet as everything has already been running great on tema's roms.
[Galaxy Note 3 Android Development] scoobyjenkins:
I couldn't notice any difference, both ways this rom runs excellent for me.

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] temasek:
It's already there for sometime :p

Courtesy of [MENTION=2033478]Yank555[/MENTION]

LED eXtended ConTRoLs v1.2 (Yank555.lu)

- add possibility to set led off delay to 0 (on notification, LED always on)

SysFs Interface :

* /sys/class/sec/led/led_intensity : 0 - 255 (100 = stock)

*

* Set the relative intensity of the LED respecting the userspace's request

*

* /sys/class/sec/led/led_speed_on : 1 - 5 (0 = no on time / 1 = stock)

*

* Devider for delayon (1 - 5 times shorter than requested by userspace)

*

* /sys/class/sec/led/led_speed_off : 0 - 5 (0 = no off time / 1 = stock)

*

* Devider for delayoff (no off time or 1 - 5 times shorter than requested by userspace)

*

* /sys/class/sec/led/led_xctrl_version :

*

* Display the current version of the eXtended ConTRoLs

*

* /sys/class/sec/led/led_xctrl_info :

*

* Display the current settings in human readable format

---------- Post added at 08:10 PM ---------- Previous post was at 08:06 PM ----------

I feel the difference.
[Galaxy Note 3 Android Development] ElRongMcBong:
I love you :o :D

Edit: How i enable fading?

I dont mean blinking
[Galaxy Note 3 Android Development] Mufasax:
System:Mount Points:-data/-cache [scroll towards bottom]
[Galaxy Note 3 Android Development] stavca:
well, after reboot/power on, all my widgets and icons are displayed immediately, on ext4 it took a few seconds to load them all, also scrolling seems to be ever smoother, I also tried some BMs, but to be honest, the values differs very much even between each of the runs
[Galaxy Note 3 Android Development] ollden:
Ok I see. Thank you
[Galaxy Note 3 Android Development] Gggggas:
Guys I followed the f2fs conversion guide but when I format cache I don't have the option to choose f2fs.

Also, should I format my external sdcard to f2fs? (storage/sdcard1)

Thanks
[Galaxy Note 3 Android Development] ravian29:
Awesome tips mate thanks for sharing such useful info, going to follow these and will report back

Sent from my SM-N9005
[Galaxy Note 3 Android Development] ollden:
You have to enable the migration and then you format data, data/media and cache without a choice. It should mention formatted done, it means that 3 are in f2fs. To check you can use system info for android or do a custom backup with philz.

The sdcard is native f2fs so no need to.
[Galaxy Note 3 Android Development] PTJunkie1975:
Sorry for the noob question, but after looking and reading scattered posts around, Will I be able to flash this new updated version on the T-Mo variant? :confused:
[Galaxy Note 3 Android Development] temasek:
Tmo = hlte
[Galaxy Note 3 Android Development] Sik-1:
The tmo version is also called hlte, and yes they are all compatible, jus flash away
[Galaxy Note 3 Android Development] rayman95:
tema, just want to let you know that it was impossible to install a new TW rom with your last recovery.....

It's stuck just before the start of aroma..

I had to revert back to last official Philz for flashing without any issues the rom...

EDIT: Idid some backup and restore with your recovery without any issues and it was TW rom.....
[Galaxy Note 3 Android Development] PTJunkie1975:
Thank you so much for the quick response!

---------- Post added at 07:14 AM ---------- Previous post was at 07:13 AM ----------

Thank you so much!
[Galaxy Note 3 Android Development] Gggggas:
Quick notice to all of you who may have got stuck when formatting cache. The first time I tried to format it to f2fs I couldn't see the option but after rebooting/enabling f2fs again, I could now choose f2fs.
[Galaxy Note 3 Android Development] gretschpr:
Excuse me if this has been discussed before, I made search on the thread but nothing came out, my issue is that videos on the Facebook app don't work, this has happened with earlier builds too...im on the latest and it still happens...as soon as I press one video, it starts loading and sometimes it even starts but a second later the video stops and gives me an playback error. Does anyone knows about this? Thanks for your work [MENTION=2332422]temasek[/MENTION] :)

Edit: YouTube also hangs on loading forever (I think I saw a couple of reports on that, so it's not new)
[Galaxy Note 3 Android Development] Mufasax:
Does anyone know of any fixes to the non-functioning NFC on HLTE N900T (T-Mobile) version?
[Galaxy Note 3 Android Development] songoku2k:
I got it. I have to modify build prop device in i.e. Nexus 5 then I can mirror screen. :good:
[Galaxy Note 3 Android Development] ElRongMcBong:
You change by v156 something on /system/bin/sdcard?

Cant linking with App "FolderMount"
[Galaxy Note 3 Android Development] temasek:
Use other custom kernel.

I'm using sdcardfs which breaks folder mount.
[Galaxy Note 3 Android Development] ElRongMcBong:
Thanks :)...and wat about LED-Fading? I dont mean blinking ;)
[Galaxy Note 3 Android Development] temasek:
I misread your request.

[MENTION=2033478]Yank555[/MENTION]

Do u have led fading feature?
[Galaxy Note 3 Android Development] ElRongMcBong:
No, but i want LED-Fading *.* :D
[Galaxy Note 3 Android Development] temasek:
From https://github.com/CyanogenMod/android_frameworks_base

640fe8c..86aa924 cm-11.0 -> cm/cm-11.0

b52f594..36bec5b stable/cm-11.0 -> cm/stable/cm-11.0

* [new branch] staging/cm-12.0 -> cm/staging/cm-12.0

* [new branch] staging/cm-12.0-caf -> cm/staging/cm-12.0-caf

CM is on the move......
[Galaxy Note 3 Android Development] Stanley Richards:
Why is it whenever I choose a wallpaper, it always looks blurry and pixelated? Does it not use 1080x1920 (portrait) sized wallpapers? I even disabled scrolling. I also only use one page for my home screen. How do I fix this?
[Galaxy Note 3 Android Development] zadigre:
We have to wait for CM to fix this problem...

The Aosp driver for the NFC chip used in the N900T, N900W8 and probably some other variants is not available... This is why it's not fixed yet.

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[Galaxy Note 3 Android Development] bibiner:
You have to set wallpaper through theme. Set from gallary to make it expand and blur

---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------

Interesting
[Galaxy Note 3 Android Development] Yank555:
No LED fading in my mod, hardware is VERY different compared to Note 2 or S3.

It's absolutely doable, not complicated, but loads of coding (code typing), rather boring to do ... so far always had more 'important' stuff to do when I had time to code.

Don't think I'll find time to look into this any time soon either, sorry :(

For example, rather get f2fs support going ...

JP.

Sent from my Nexus 5 running official SlimKAT 7.0 on Yank555.lu v1.1-beta3 kernel.

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

Wow ! This I didn't expect ... suprised ... but in a good way !

JP.

Sent from my Nexus 5 running official SlimKAT 7.0 on Yank555.lu v1.1-beta3 kernel.
[Galaxy Note 3 Android Development] HKShooter:
I also have this problem even I set the wallpaper in "theme". After clean flashing V156, the wallpaper looks blur:(
[Galaxy Note 3 Android Development] txpxsx:
before i move on to f2fs, i'm just wondering, what do we need to do should we want to return back to stock TW (flashing with Odin)

i haven't tried any partition formatting previously, so it scares me
[Galaxy Note 3 Android Development] scoobyjenkins:
If you flash stock via Odin, it should be formatted back to Ext4. If it doesn't boot properly at first, booting into stock recovery and doing a factory reset should sort it.

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] txpxsx:
thanks mate :highfive:
[Galaxy Note 3 Android Development] rayman95:
very interesting question and important thing to know if we want to come back on custom TW rom or even do a backup?????
[Galaxy Note 3 Android Development] encho:
Just flashing with Odin would not format data partition, you need to specifically select that option. On other note, I don't really see big difference, if at all. It could be feeling of freshly formatted card.
[Galaxy Note 3 Android Development] imzaki1994:
My phone cores are always at high frequency any help with that?
[Galaxy Note 3 Android Development] antt00:
Check cpu usage to see which app/service is causing it.
[Galaxy Note 3 Android Development] imzaki1994:
Hwa can i check which app i causing that? Btw thanks for answering