yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] :
I'm on v134, and I noticed there is a Hover and Heads Up in Settings > Notification Services. I did some searching, and from what I found, Heads Up can only be enabled on a per-app basis. You cannot enable HU universally. Whereas Hover is a universal setting toggled from the middle of the top right icons of Notification Panel.

Can anyone confirm? Because I found this screenshot that seemed to imply that HU can be enabled universally.
[Galaxy Note 3 Android Development] temasek:
Your screenshot is heads up of cm.

My build is heads up of slimrom.

There is a difference.

---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------

Tested no issues here.

I selected music and choose a Korean song from my music folder.

No issues.
[Galaxy Note 3 Android Development] Goddly:
No IR blaster functionality? Working app? Also swype not working.
[Galaxy Note 3 Android Development] caesar_:
This app works perfectly.. WatchON not so much.

https://play.google.com/store/apps/details?id=com.remotefairy

---------- Post added at 03:23 AM ---------- Previous post was at 03:20 AM ----------

I just tested in 135 hltespr.. Works fine no FC. Try clearing data for clock app.

---------- Post added at 03:28 AM ---------- Previous post was at 03:23 AM ----------

Haven't seen much feedback on hltespr build.. Just wanted to let you know for me at least, everything is rock solid.

Since switching to intelliactive.. My phone has been sleeping like a brick. A little over 30hrs battery and 6hrs of screen time.

All I'm looking for now is a little bit more battery longevity.. Other than that I'm pretty satisfied.
[Galaxy Note 3 Android Development] :
I see, ah... Thanks! (You're from Singapore too?)

Anyway, if I want to switch over to CM for a few days, do I need to wipe? Or can I flash over this?
[Galaxy Note 3 Android Development] temasek:
Pure Singaporean.

U from which rom currently?
[Galaxy Note 3 Android Development] :
Temasek v134. Thanks for this ROM! Love the boot animation :)
[Galaxy Note 3 Android Development] chazey2:
Faux Clock

Hi in reference to the guy with random reboots . I'm having issues tried three /for times to switch from trickster to faux clock. Every time I clear data from trickster and delete before installing faux clock and every time I only ever set faux clock the same as trickster ie interactive and fiops and the read ahead 640 etc. If I reboot the phone boots and immediately reboots in an endless rebooting cycle. Switch back to trickster and all is fine. Any one throw any light on what I'm /it's going wrong.
[Galaxy Note 3 Android Development] bibiner:
Oh you Singaporean. Cool. I might go to Singapore for college soon XD also seek for IT related stuff
[Galaxy Note 3 Android Development] orbital_71:
Wow korean ssong sia wkwkkw :D:D:p:p
[Galaxy Note 3 Android Development] shjane:
Do you suffer form reboots when BOTH trickster and FauxClock is UNINSTALLED? also...

Post your screenshots here for us to see - perhaps there is something you are missing.
[Galaxy Note 3 Android Development] temasek:
Switching over to official cm should be fine.

Never tested personally. :p
[Galaxy Note 3 Android Development] chazey2:
No on trickster my phone nick name steady eddy, flawless rock solid not one error or glitch at all. Problems only with faux clock. Yet I keep settings on both the same??
[Galaxy Note 3 Android Development] shjane:
That is very strange! Your setup I am assuming:

MP Dec - Off

intelliplug On

Governor: Interactive

I/O Scheduler = fiops

How much is your read ahead value here? Mine is at 128

Silly question perhaps - but make sure your "set on boot" is ON

?
[Galaxy Note 3 Android Development] chazey2:
yep only difference read ahead 640 set on boot applied. Once on install I could understand, a glitch on install but 4 times on bounce no. Trickster data cleared out then uninstall then reboot then install faux. When using Trickster phones a speed freak and solid as rock never one problem ever.

Only reason trying faux because sound settings never stick on boot using Trickster.
[Galaxy Note 3 Android Development] 22stars:
V135 hltespr running flawlessly for the past two days, no random reboots, no hiccups, nothing. Thank you Temasek, this ROM is rock solid and loaded with all the right features.
[Galaxy Note 3 Android Development] chazey2:
deleted .
[Galaxy Note 3 Android Development] shjane:
What I would suggest: set your Read Ahead to 480 instead of 640. If you still get reboots, I would strongly suggest you switch of all FauxClock settings and enable the ON BOOT one for one after testing to find the culprit. I would also suggest post the last_ksmg log. I use an app for that called SysLog to easily pull whichever log required. Pull the log after the reboot and post it here.
[Galaxy Note 3 Android Development] viniciusrsouza:
Which are the benefits of fiops compared to the default row one? Never touched this...

Oh, and by the way, Faux users, does the app has something to force a media scanning like that feature available on Trickster?

I need this feature so much, since my Gallery app (from Paranoid stock package) does not update thumbnails from internal storage automatically when I move or delete images and videos.
[Galaxy Note 3 Android Development] shjane:
Regarding the FIOPS vs ROW - I am just too lazy to summarize but there is a nice explanation here: http://xdaforums.com/showthread.php?t=1558153 comparing the different schedulers.
[Galaxy Note 3 Android Development] viniciusrsouza:
Yeah, I already tried to figure out this, but simply can't understand nothing about all of that. It's so much technical for me... ?

Since I'm so stable I will stay using the default row one. I was just curious because I'm noticing a lot of people are using fiops.
[Galaxy Note 3 Android Development] zacharias.maladroit:
it's FIOPS,

not

FIOS:

http://lwn.net/Articles/474164/

info on ROW:

http://lwn.net/Articles/509829/

in a nutshell:

FIOPS appears to immediately process small IOPS (smaller reads/files) over larger reads, its total goal seems to be to optimize for throughput, performance - and it's not organizing the requests that are made to the flash drives in a certain time (slice) but in relation to IOPS (http://en.wikipedia.org/wiki/IOPS) == higher benchmark i/o results, this could lead to slightly higher/more lags and disruptions compared to ROW

ROW makes sure that read requests are more important than write requests - and this in 2 class: normal priority, high priority - since ROW is the default scheduler for Android, apps have to support this distinction == when apps are well-written - there should be less lag (lower latency), sound distortion (during e.g. music playback) or other disruptions in operation when other programs and tasks are executed in the background or playing music and working with other apps at the same time

background:

in flash drives writing small data blocks takes a significantly longer time than larger files - this must be both taken care of in i/o schedulers and is in FIOPS & ROW

BFQ, CFQ, (deadline, v/r, ...) also consider this but probably not as efficient as it could be compared to FIOPS, ROW, and the other specifically for flash-drives designed schedulers

with noop the sorting and management is taken care of directly by the flash drive, the operating system (Android !) or apps have very little to no control how data is processed - so in usually the lags and disruptions could be worse compared to using ROW; FIOPS, FIOS, etc.

this is of course the theory - how this behaves in practice can only be found out after testing & comparing those i/o schedulers

hope this helps ...
[Galaxy Note 3 Android Development] viniciusrsouza:
Sorry for the completely off topic, but it's something great for us, Hangouts lovers (users)!

New Hangouts 2.3 version with material design and voice integration is out! :D

Hangouts 2.3 Update Brings Remaining Google Voice Integration And A Big Visual Overhaul [APK Download]:

http://www.androidpolice.com/2014/0...integration-big-visual-overhaul-apk-download/

And it's available on Play Store the Hangouts Dialer to create the third tab about voice integration on the new Hangouts app!

https://play.google.com/store/apps/details?id=com.google.android.apps.hangoutsdialer

Everything working great here! _o/

Edit: Oh no, not everything. Still can't see other contact when video calling... :(
[Galaxy Note 3 Android Development] chazey2:
Thanks for suggestions mate, but to be honest apart from the sound settings not sticking I'm not that bothered about Faux over Trickster unless of course I'm missing out on something! On my trickster settings my phone has never froze ,glitched or rebooted once in 30 plus builds of Temasek Rom. ' If it aint broke don't fix it' for no good reason lol :laugh:
[Galaxy Note 3 Android Development] dhufford81:
Hltevzw working good! I still have to toggle data after receiving an MMS but it's been that way since the unification. Was hoping deunification fixed but oh well. Thanks again temasek!
[Galaxy Note 3 Android Development] ioneng:
Hi guys, I'm having trouble with setting default browser app. Everytime I open a link from google search results or any other app, I have to choose for a list. Any suggestions?
[Galaxy Note 3 Android Development] shaggyskunk:
You should be seeing - "once" or "always" select - "Always".

http://slimroms.net/index.php/faqandmanual/slimbean/120-kitkat
[Galaxy Note 3 Android Development] ioneng:
Thanks for you information but I already know that. My problem is that even though I choose "Always", the choice doesn't stick.
[Galaxy Note 3 Android Development] antt00:
I am having the same issue to set default browser as well. It just won't stick. Its been going on for quite sometime but its minor so i just ignore it.
[Galaxy Note 3 Android Development] ioneng:
Just want to say that I don't have Kohl's app installed if anyone had similar experience and fixed it by removing kohl's app. See here: http://forums.androidcentral.com/samsung-galaxy-s4/286993-why-wont-chrome-save-default-browser-2.html#post2862570
[Galaxy Note 3 Android Development] shjane:
Hi [MENTION=2332422]temasek[/MENTION]

So I have changed back to interactive from intelliactive - this morning I woke up phone has once again rebooted during the night.

I tried reading the last_kmsg myself (pretending to understand) it seems to me the app Mobiwol I am using was causing kernel to panic? Am I right? If this is the case I know where the/what the problem is. Could you kindly confirm this for me or tell me your understanding?

Am I looking at the "fatal" parts?

1) [19182.189363] MSM-CPP msm_cpp_do_timeout_work:1219 fatal: cpp_timer expired for identity=0x20002, frame_id=353

2) [27305.587607] [0:Mobiwol Firewal: 3012] Kernel panic - not syncing: Fatal exception

Last_kmsg attached.
[Galaxy Note 3 Android Development] caesar_:
On hltespr.. 135. Is anyone else experiencing broken phone speaker? Speakerphone works fine but when I switch to ear speaker, nothing..
[Galaxy Note 3 Android Development] HKShooter:
I flashed V135 for 2 days and had occasional SOD. I had no problem in V133 or earlier versions. I hope it won't happen in the next version:(
[Galaxy Note 3 Android Development] Whosat:
Is f2fs supported?
[Galaxy Note 3 Android Development] temasek:
Kernel yes ramdisk not yet.

So no, not yet.
[Galaxy Note 3 Android Development] Whosat:
Got it! Reverting back to vfat for now :) Just got a 64GB microSD card and was wondering which was the best format and remembered a couple pages back that you were using default/fat32.. I'm assuming vfat is as stable as fat32?
[Galaxy Note 3 Android Development] bigup7:
on v135 and when i connect my phone on my cars built in Ford bluetoothv kit, it seems fine then after 5mins, the phone hard crashes and black screen, i need to take out battery for it to start working again

only happened twice so far and not all the time!
[Galaxy Note 3 Android Development] Snottierwhale:
I use exfat with no issues.
[Galaxy Note 3 Android Development] chazey2:
Is through a 'head unit' ie Sony. If so try deleting all phone profiles set in the head unit and deleting the car head unit from the phones Bluetooth profile.

Rebond the phone again by turning on car head unit then a few seconds later the phones Bluetooth, accept the pairing request and wait a few seconds more and accept the phone book request. I have found in my Focus (Sony) this is the best way to avoid glitches.

Never once had issue with this on this Rom, had issues in the past on S2/3 with other Roms and this method sorted it.
[Galaxy Note 3 Android Development] AhmadAlmousa:
Proximity sensor during call

I am too having a problem with the proximity sensor. I've tried "Phone Tester" app

https://play.google.com/store/apps/details?id=com.mtorres.phonetester

It shows that the sensor is alright and reading light very well. However, when a call is initiated, and the phone is brought to the ear, as mentioned, it won't come back. I'll have to keep clicking home or power button several times before I can go back to home screen NOT to the dialer.

Whenever I try to go back to the call in progress through the notification, screen will be out again (without bringing the phone to the ear) !!

It really drives me crazy !!
[Galaxy Note 3 Android Development] zadigre:
like I wrote before, this is a hardware problem for most if not all Note 3 that have a problem with the proximity sensor...

The problem is very simple... there is some dust getting its way in front of the sensor... and because of that, it doesn't work like it should.

The real solution to this problem is to disassemble your device, clean the sensor and the glass where the sensor is and try to block all holes where the dust can get in.

I had a Note 3 with this problem... and after cleaning it, it was fine.

You can also try to adjust the detection "edge"... but the real fix is to clean the sensor and glass.

if you want to "try" something, Blowing compressed air into the speaker grill could help... it may temporarily fix the problem... if it does, your problem is dust in front of the sensor.

more information here :

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

http://xdaforums.com/showthread.php?t=2477371&page=3
[Galaxy Note 3 Android Development] mdda7:
+1
[Galaxy Note 3 Android Development] jdgamble:
I've had this before. The cause of my problem was the skin on my phone, SlickWraps CF skin. It did have holes in them but the sensor was still detecting them. I downloaded the same app. Don't look at the light sensor, check the proximity. In my case it always said NEAR then i pulled back the slickwraps thus making it FAR, figured it was the culprit. There's just something blocking that sensor.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] AhmadAlmousa:
Thanks guys for the input and I totally get your point. However, i tried several sensor apps and apparently, the proximity sensor is working fine. Moreover, I don't have this problem in TW roms !

Anyhow, I'm planning to get the Note 3 to a service center. For some reason, there's a problem in the speaker. I'll ask 'em to get that sensor inspected as well.

Peace

Update: I think you are right. I guess it was a coincidence that the sensor got dusted in the same period that I installed CM.

I focused a light beam onto the sensor and I can confirm that it has dust.

Thank you again for your input, man.
[Galaxy Note 3 Android Development] jdgamble:
Just don't tell them knox is tripped or you're on custom rom. They will blame everything on that even though it's a hardware problem.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] dirtyjersey856:
I had a problem with my proximity sensor that started awhile ago and persisted through tw & aosp installs...I searched a fix and even tho it said it wouldn't last through a reboot it is still fixed dozens of reboots later...just recalibrated with a terminal emulator and all is still well
[Galaxy Note 3 Android Development] AhmadAlmousa:
I have a role of thumb: act a fool. Get the N3 restored, wiped, and all shiny. Get to the service center and drop it explaining the issue.

It did work last time. I don't know I was lucky that the technician missed it or, simply, missed it. Either way, I'll do it again ;)
[Galaxy Note 3 Android Development] caesar_:
Can anyone confirm or deny if ear speaker is working on hltespr?
[Galaxy Note 3 Android Development] Snottierwhale:
I received a call 3 mins ago and heard them through earpiece on hltespr.
[Galaxy Note 3 Android Development] caesar_:
When you say ear piece do you mean the ear speaker or ear buds.. I can hear through ear buds just fine, ear speaker on phone not so much.

I rarely take calls so I don't know when this started occurring.
[Galaxy Note 3 Android Development] Snottierwhale:
I mean when earpiece on phone so like what u hear when putting phone next to ear to answer call not earphone.
[Galaxy Note 3 Android Development] caesar_:
Clean install and ear speaker is working fine.. Restore back to nand and it's broken again.

Is there anything I can wipe to get the ear speaker back to stock?
[Galaxy Note 3 Android Development] temasek:
Build V136

Hlte & Hltespr

Comes with Temasek Kernel v3.96 EXP2

Sorry no changelog. My time very tight.
[Galaxy Note 3 Android Development] shjane:
Legend!! Thanks temasek.

For what its worth.. I found the culprit to my random reboot during the night.... Firewall app was at fault - back to 100% stability - going to try intelliactive again.
[Galaxy Note 3 Android Development] viniciusrsouza:
Tema, I know you are busy, but just got a reboot while screen off and charging. This is happening rarely, but I'm attaching Logcat and last_kmsg. Sorry, but these are from 135, since I just woke up now (7AM here) and will try to flash 136 now before work. Was already at bed when you uploaded it.

https://docs.google.com/file/d/0B9sEkRaVuPLTYVU0VThkSms0MUk/edit?usp=docslist_api

https://docs.google.com/file/d/0B9sEkRaVuPLTdThjdnRUWGRYdmM/edit?usp=docslist_api
[Galaxy Note 3 Android Development] shjane:
That is a very strange last_kmsg ? I have not yet seen one looking like that. Did you grab the log after reboot caused by "whatever" ?
[Galaxy Note 3 Android Development] viniciusrsouza:
Yes. Was about five to ten minutes after this random reboot happened. Didn't turn off. Didn't reboot manually.

Maybe it's strange because I wasn't doing absolutely nothing? The device was resting plugged to charger beside my bed.
[Galaxy Note 3 Android Development] shjane:
Lets see if someone with more knowledge can respond to this, all my last_kmsg I have pulled after reboots still showed where/why the kernel panic'ed. If you haven't rebooted manually since the last forced reboot (kindly unplug your charger) and pull another last_kmsg and up it again? I just use SysLog app, it pulls the log and I email it to myself.
[Galaxy Note 3 Android Development] viniciusrsouza:
Already rebooted my device... =/

Mainly because I'm desperately trying to calibrate my battery, even though I know it's probably a myth, but I'm experiencing a fast drain and an eternal 1% at the end of the day, even letting my battery go through a complete cycle about three times already.

What I'm trying now is unplug charger at 100, turn off the device, plug charger again for some minutes to be sure battery is full, unplug charger again, turn on device and check if battery is 100.

The first two times I did this the battery wasn't at 100, but about 98, 99. On the third time my device loaded on 100.

Don't know if this will happen, but giving a try. Anyway, battery performance is OK for me. Five to six hours of screen on time on WiFi. Four to five on 3G. But it's so annoying seeing battery reaching 1% and staying there for more than one hour sometimes.

There is something wrong with my battery level counter, if this is even possible...
[Galaxy Note 3 Android Development] svbarbosa:
Have you tried to delete batterystats.bin? Must be done when battery is at 100%.
[Galaxy Note 3 Android Development] viniciusrsouza:
I read that a Google important guy said deleting battery stats is just a myth and doesn't really give us battery calibration, but will try that.
[Galaxy Note 3 Android Development] temasek:
It's a myth. No doubt.
[Galaxy Note 3 Android Development] svbarbosa:
Well, it seemed to work for me in the past. Would someone enlighten me explaining what is the purpose of batterystats,bin and which is the proper way of performing a battery calibration.
[Galaxy Note 3 Android Development] crespi_:
That's truly bizarre.

I would do a nand backup, and then completely wipe your data and then flash v90 real quick, without gapps at first just to see if it works after that. If it works after a clean flash then you can go back to your nand and backup your data and start with a fresh install.
[Galaxy Note 3 Android Development] ajm786:
What version of the HLTE do you have? I'm running the SM-900T, which is T-mobile's Qualcomm version.
[Galaxy Note 3 Android Development] petzku:
Have you checked the quick toggle settings that they arent just set to transparent??
[Galaxy Note 3 Android Development] lawonga:
Nope not transparent
[Galaxy Note 3 Android Development] stonedead:
International version, SM-9005.
[Galaxy Note 3 Android Development] txpxsx:
I wonder, why are we having distorted speaker sound on every cm aosp ROM (i also had it on SGS3). I heard it's a cm bug. And someone made a script to fix this issue on lg g2 thread. However why its never fixed yet

Any solution guys? I hate to return to touchwiz, but i admit the sound quality is much better

---------- Post added at 08:33 AM ---------- Previous post was at 07:48 AM ----------

LOL

Yea mate, i ended up using lean kernel for the time being instead
[Galaxy Note 3 Android Development] crespi_:
Duuuude. Cmon. The volume of questions about this issue is nearly equal to the volume of answers and conversations about it.

F a u x

---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
[Galaxy Note 3 Android Development] ajm786:
See, you guys are running the International version, I assume.

I am running a Qualcomm version, and I just updated to the NE6 bootloader/modem. Maybe it has to do with the fact that Samsung hasn't released the kernel source for this yet?
[Galaxy Note 3 Android Development] shjane:
How to Logcat

For those of you who tends to struggle with Force Closing issues or or or reverting back to previous builds etc, instead of posting your problem and asking why why why, please go here ---> http://xdaforums.com/showthread.php?t=1726238 and learn how to do a logcat (supplying logs for the developer to clearly see what exactly caused this issue for you.
[Galaxy Note 3 Android Development] temasek:
Temasek Kernel v3.67 is up.
[Galaxy Note 3 Android Development] txpxsx:
Tema, any directions for tweaking this new kernel?

Is your kernel settings on first page still relevant to this new version?
[Galaxy Note 3 Android Development] johnpro112:
Hey temasek/anyone how can I go back to norm hardware buttons. Right now hold home button gets google now and hold menu get window switcher like s5.
[Galaxy Note 3 Android Development] crespi_:
Settings > buttons > change to your liking there
[Galaxy Note 3 Android Development] temasek:
I'm using

Mp-decision off

msm_hotplug on

InteractiveX

Noop
[Galaxy Note 3 Android Development] d407974:
How can i enable

msm_hotplug
[Galaxy Note 3 Android Development] temasek:
Use a file manager with root permissions, eg Root Explorer

/sys/module/msm_hotplug

Edit the file named "Enabled"

Change 0 to 1

Save the file and exit.

---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------

Temasek Kernel v3.68
[Galaxy Note 3 Android Development] Khizar:
New build has been up....Just in case yall didn't know, link in OP..

Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
[Galaxy Note 3 Android Development] DaniuPL:
Too many random restarts :(

Newest version.

Same problem anyone ?
[Galaxy Note 3 Android Development] temasek:
Too stable here.
[Galaxy Note 3 Android Development] zadigre:
the proper way to calibrate is very simple...

charge up to 100%. Leave the charger plugged for 2 hours.

unplug the charger and let your device shutdown by itself.

that's it...