yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Schneckmeier:
same here with v3.98.1EXP4; look at the flight mode time @ night - same draining like over the day. Back to 3.97 EXP 4 yesterday morning and then 1% batterydrain over night again like the last half year.

Same with yank and ZION Kernel; tested the whole last week. In my opinion the reason is in the kernel sources since 23-09-14.
[Galaxy Note 3 Android Development] DeadPicsel:
How have you got Faux sound?
[Galaxy Note 3 Android Development] caesar_:
Pretty much the same way.. Everything zero'd out except poweramp is +1

But I've yet to test with it like I said so I'm sure that might change
[Galaxy Note 3 Android Development] DeadPicsel:
And you use this kernel Yeah?
[Galaxy Note 3 Android Development] caesar_:
Always on tema's latest
[Galaxy Note 3 Android Development] valtronic:
When i am roaming with this rom (in germany with uk vodafone contract) for some reason i can't get any data connection nor does it switch from 2g to 3g to hsdpa. it just stays where it is and has no reception. Any idea why this could be happening... And also my available choices are just 2g/3g/LTE and since i am pretty sure LTE isn't available on roaming i am missing HSDPA completely. I remember i never had that problem on touchwiz, it just cycled between the different modes depending on what was available.

Other than that everything is working fince on 145 for me and is otherwise the best rom i have ever used.

Edit: 2G/3G Data connection is now working but still missing HSDPA

Edit 2: Hold on 3G included HSDPA i guess doesn't it? hmmm

Edit 3: Installed this https://play.google.com/store/apps/details?id=de.android.telnet and found my connection is actually HSDPA+ so all good... I just wish there would be visual feedback in the status bar even when roaming... Don't understand why the little roaming R is more important than the network mode...
[Galaxy Note 3 Android Development] caesar_:
FauxSound doesn't seem to be sticking for me either. Cosmetically it does, but I have to toggle gain away from target then back to, to get my preferred setting.

I also noticed that trickster sound profile sounded way better than faux.

So back to trickster it is.
[Galaxy Note 3 Android Development] slayher:
When you have to pay extra because you were using Roaming data, and you did not know, you will find that R important. :D
[Galaxy Note 3 Android Development] temasek:
Amen
[Galaxy Note 3 Android Development] micmars:
Trickster sound profile sticks on reboot for me just fine. I always had a problem with faux, whether on TouchWiz or CM11 faux compatible kernels.

Just to eliminate the obvious, I wonder if you've taken to naming the sound settings and letting it settle in at least 2 minutes after reboot.
[Galaxy Note 3 Android Development] caesar_:
I don't even have to reboot.. I just come back later and my saved profile is changed to default.

I've saved it and named it both.. Just doesn't stick.
[Galaxy Note 3 Android Development] caesar_:
It's weird..

It actually creates a new saved profile called untitled. And reverts to it after a certain period of time
[Galaxy Note 3 Android Development] DeadPicsel:
I've installed Fauxsound and I'm amazed with the sound quality. Thank you Temasek and Caesar. ☺
[Galaxy Note 3 Android Development] AO7:
I have similar wakelocks and fairly mediocre battery life. V138.1 was stellar, now it's been going downhill. I'm puzzled!
[Galaxy Note 3 Android Development] txpxsx:
Cm certainly has some limitations if we're talking about battery life, compared to TW roms

I thought my battery is dying, but I'm having better battery life now at the moment with TW
[Galaxy Note 3 Android Development] xavihernandez:
Yes, of cource AOSP ROMs has not the battery life of TW ROMs. Everyone would be happy if so :D.

My device still most of time flatline when sleeping though.
[Galaxy Note 3 Android Development] micmars:
OK Caesar, your issue has been bugging me as of late, mostly because I hate to see things not working the way one wants them.

Another basic question to eliminate: have tippy set Trickster to apply settings on boot, as shown below?
[Galaxy Note 3 Android Development] caesar_:
Yessir..

That option is ticked when I initially setup trickster. The issue is that it is not a reboot that triggers the reset. But more of an amount of time.

I've only set one sound profile for trickster.. Named it "KNOCK". There is also one called default (this one cannot be deleted). If you look at the pic below, you will see a 3rd profile named "untitled" that I did not create. It seems to be auto generated when the sound setting goes rogue.

I've uninstalled, cleared data all that.. Problem persists. I have gains locked.
[Galaxy Note 3 Android Development] Goddly:
I've also had this problem with trickster. Reboot or not it won't stick. Faux sticks for me.

Trickster works for me on TW. Not on Aosp. Dunno why.
[Galaxy Note 3 Android Development] caesar_:
http://xdaforums.com/showthread.php?p=55854156
[Galaxy Note 3 Android Development] jdgamble:
Terrible battery dive/drain on v145 3.98.1 exp4. This is all during deep sleep or what seems to be a deep sleep.

Sent from my Beast SM-N9005. Thumbs Up Brotha!!
[Galaxy Note 3 Android Development] chazey2:
The very same here .I have Default ,N9005 (my profile) and an untitled which is set after boot which I then set to 'N9005' but whenever I go back to check 'untitled' will be set by it's self.
[Galaxy Note 3 Android Development] micmars:
The untitled profile is happily gone from my system, and I believe that it is due to me having chosen a previously saved profile after flashing each of the last few updates. In other words, on first boot, setting up trickster can be done by either selecting the option of reverting to the old setup when a new kernel is installed or declining that choice.

Irrespective of what I select above, going in and manually selecting each named parameter seems to solve the issue.
[Galaxy Note 3 Android Development] caesar_:
In my case.. It always reverts back to untitled profile. I'm thinking that it's conflicting with either poweramp eq or v4a.

[MENTION=5244502]micmars[/MENTION] do you use poweramp?
[Galaxy Note 3 Android Development] micmars:
No, I don't use poweramp, just viper4android and trickster.

FYI, The Temasek viper4android profile that you shared is only slightly different from that which I've used, but is different enough that I think it's a vast improvement.

The differences include for extra loud, the moderate/infinity (I had used 6x), and using both the equalizer and the convolver settings (I had convolver on, equalizer off, and an impulse response sampling file selected, the latter of which I still employee).

Anyway, I do hope you get trickster or faux to stick, because without it or faux sound setting a level baseline, both apps by default dial down the volume to like -2 on boot, which sort of defeats the purpose of the app.
[Galaxy Note 3 Android Development] temasek:
V146 is up for all variants.

Available in all my download sites.

Comes with Temasek Kernel v3.98.1.

- Includes Sammy update 9 kernel sources.

- Fixed flip_wake_lock issues and more.

- Removal of flip cover feature in kernel and uses slayher ROM implementation

- Smart Cover feature in Display Settings now works. You now can enable/disable smart covers (if you own one). I'm using a flip cover so I know it works :p

- Full kernel changelog -> https://github.com/temasek/android_kernel_samsung_hlte/commits/staging-v3

Pro Tip: Don't start cursing & swearing at kernels tag with EXP. You can throw your punches at me for stable releases :p:p:p

Enjoy. :)

VOTE this thread if u like my work
[Galaxy Note 3 Android Development] bibiner:
Five star service!!!
[Galaxy Note 3 Android Development] caesar_:
I think I got it to stick.. After multiple reinstalls and different sequencing of initial configuration.

Will do some testing on my way to work to see if it indeed sticks
[Galaxy Note 3 Android Development] micmars:
Outstanding news.

After flashing last night's build, I rejected the prompt from Trickster to apply the old configuration to the new kernel, installed my other system files (inverted Chrome, Sprint vvm, Dropbox), reactivated Xposed (CPU temp and tinted status bar only), then tackled the Trickster settings last. Again, grabbing the previously named profile for each main setting followed by a tap of the checkmark (sound, voltage, CPU top and bottom, etc), exiting the app and rebooting, the settings stick henceforth.
[Galaxy Note 3 Android Development] caesar_:
I downloaded but didn't get a chance to nand and install the latest.. When I get to it tonight, I'll give your method a try. I usually just accepted the auto configuration upon flashing a new build.
[Galaxy Note 3 Android Development] temasek:
Pretty quiet here.

How's the latest build working for u guys?
[Galaxy Note 3 Android Development] jdgamble:
Pretty solid. For a couple of 4hrs+ deep sleeps battery drain is very minimal. No longer doing a dive.

Sent from my Beast SM-N9005. Thumbs Up Brotha!!
[Galaxy Note 3 Android Development] caesar_:
I spoke too soon.. Trickster reverted back to untitled profile
[Galaxy Note 3 Android Development] micmars:
Latest build is terrific, boss. Just some tricky trickster settings not sticking, but this is an entirely separate matter from this awesome rom.

Thanks for checking in.

---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------

That just sucks. I'm out of ideas....except after switching from faux back to trickster may have been part of the mix.

What a PITA.
[Galaxy Note 3 Android Development] caesar_:
After further testing.. I suspect it might be conflicting in some way with v4a. Maybe from when I flashed back to TW. idk. Just messing with settings in v4a I can hear when trickster profile switches back to untitled. Looks like a full internal wipe is going down when I get home from work.
[Galaxy Note 3 Android Development] ajm786:
I have this problem also on the latest versions of the ROM. It's definitely some kind of conflict with Trickster, V4A, and or Fauxsound. I never had time to figure it out, but what I can tell you is that uninstalling Fauxsound and using Trickster to set the sound settings usually worked for me.
[Galaxy Note 3 Android Development] caesar_:
I was having this issue with trickster before even installing fauxsound. Did you mean v4a?
[Galaxy Note 3 Android Development] chazey2:
All good here ,thanks. Think the phone is sharper ,crisper and quicker all round on the new build. Running ART here as normal , and yet to find an issue. Many thanks!
[Galaxy Note 3 Android Development] ajm786:
No, I did indeed mean to say Fauxsound. After I uninstalled Fauxsound and use Trickster solely to control sound, even when it reverts to the "Untitled" profile, it still works as it should. If I use Fauxsound app in conjunction with Trickster, it screws up the sound randomly.

The odd thing about all this is that on v114 (the legendary World Cup edition), I use Fauxsound in conjunction with Trickster and have ZERO issues.
[Galaxy Note 3 Android Development] kenz0bux:
awesome!

i just started using this rom today, and believe me when i tell you its rock awesome! did not find any issues at the moment.

but overall this rom is way beyond my expectation! .. keep it up

by the way, im from Singapore and im using singtel. non of the reported issues i read is happening to me at the moment!

CHEERS!!! :good::good::good:
[Galaxy Note 3 Android Development] shjane:
FauxSound keeps popping up with issues it seems to me - Just to add to it.... a few post back I posted about my phone going all SILENT for no reason - no sound from it whatsoever until I reboot. Funny enough the culprit was FauxSound 100%. It was between V4A and FauxSound and after testing properly (V4A uninstalled) FauxSound was to blame. After removing FauxSound I have not yet had this problem again!
[Galaxy Note 3 Android Development] caesar_:
This was the same issue I was having with fauxsound.. No need to reboot. Just move away from target then move back.
[Galaxy Note 3 Android Development] D4rk_nVidia:
Does this ROM or the base(CM) got still the Problem with the spen?

I use it often but I ´flashed this Rom before 2 months and the spen worked only sometimes.

The Screen dosent respond to the spen first after an reboot.

Is this fixed?
[Galaxy Note 3 Android Development] springer.music:
I've been testing a fix from Tony Layher since yesterday, and so far the spen hasn't stopped working yet, whereas yesterday I managed to reproduce the issue 4 times in a row (before installing the fix)

The commit was merged a few hours ago for both nightlies and M releases and should be available in the next builds. :)
[Galaxy Note 3 Android Development] jdgamble:
Still getting ghost battery drains on latest build v146 3.98.1+. It's on deep sleep but still getting this drain, weird.

Sent from my Beast SM-N9005. Thumbs Up Brotha!!
[Galaxy Note 3 Android Development] D4rk_nVidia:
Yeah I read about that earlier but there wasnt any fix out.

Im happy to read that there is a working fix :)

I wait till tomorrow and when the fix is included, I will flash CM.

Or does this ROM gets an update fast?
[Galaxy Note 3 Android Development] masze:
i have been runnings this beauty 3-4 weeks, spen have never fail me and i use the pen alot.. WITHOUT the fix.

(in other aosp i have the problem, never on tema's)

masze©
[Galaxy Note 3 Android Development] springer.music:
After a number of tests, I've managed to trigger the spen issue in temasek's ROM as well.

You can try to reproduce it this way:

-Pull out the spen from the holder

-Turn off the screen, then wait for a few secs

-With the screen still off, start fiddling with the spen on the screen also pressing/releasing the spen button multiple times (short, long and double presses)

-After some mins (at times just secs) of this treatment, there are good chances that when you then turn on the screen, the spen doesn't work

It's still sort of random but this way I I've managed to reproduce the issue a number of times on both vanilla CM11 and temasek's version.

slayher's commit seems to fix the issue for good :)
[Galaxy Note 3 Android Development] xavihernandez:
Bad network coverage may be the issue. I see that u have a grey block only, no green at all.
[Galaxy Note 3 Android Development] encho:
That's interesting, but true. Although I don't see myself using the pen while screen is off [emoji1]
[Galaxy Note 3 Android Development] jdgamble:
Was looking at that as well. But i have everything turned off on mobile data and using Intelli3g to use GSM and WCDMA(auto) when screen is off. Will test further. Thanks for the reply.

Edit :

I also have this screenshot yesterday. Same latest build. Better battery life. Minimal drain and same signal on mobile yellowish.

Sent from my Beast SM-N9005. Thumbs Up Brotha!!
[Galaxy Note 3 Android Development] xavihernandez:
Even if data is OFF, your network still "scanning" for cell, because it is a phone ;p. Plus 3G/2G auto still drain battery as 3G requires more power than 2G, and 2G is generally best covered (at least in France). Try to put you phone in 2G only and make a test. (And if data is OFF what is the aim to use 3G ? ;))

Sometimes it needs several days to properly settle.

I don't know Intelli3G, I think I had tested it but I hadn't been able to make it works properly, so I came back to the historical Toggle2G which works like a charm :).

EDIT : also take a look at "Wakeup triggers" part in Wakelock Detector.
[Galaxy Note 3 Android Development] springer.music:
There are actually network providers that only use 3G for voice (and 3G/4G for data). When there's no 3G available (or it's turned off in settings) the phone switches to 2G in national roaming on another provider (and in some cases this can mean extra charges, especially for data over 2G).
[Galaxy Note 3 Android Development] jdgamble:
Battery drain, much worse now. With calendar being culprit. I've never opened this calendar but gave this much trigger. Anyone know why calendar WL trigger is so high? Plus this ssp wakelock.

Sent from my Beast SM-N9005. Thumbs Up Brotha!!
[Galaxy Note 3 Android Development] Snottierwhale:
So i have learned that my trashy sprint connection has been preventing my cellphone from deep sleeping since I got the phone. I've solved this by using airplane mode and wifi. I use Google voice with hangouts so I can call and text over my home WiFi and school WiFi. My phone now sleep like a baby. [emoji1]
[Galaxy Note 3 Android Development] masze:
why would i start behaving that weird with my spen?

normal use of pen and it will never fail.
[Galaxy Note 3 Android Development] Schneckmeier:
Good morning!

Last night drain with kernel 3.98.1+ was OK; this night bad - look at the pics:
[Galaxy Note 3 Android Development] Yank555:
Looks like sensorhub wakelock messed with you...

JP.

Sent from my Nexus 5 running official SlimKAT 7.0 on Yank555.lu v1.1-beta3 kernel.
[Galaxy Note 3 Android Development] los82:
latest kernal

sprint variant kernal which are the latest download links?
[Galaxy Note 3 Android Development] springer.music:
Well, it's quite simple. If you need to test a bug that's been reported by many but it's still not easy to reproduce as it looks like it happens randomly, then you have to go ahead and try all the possible actions that may trigger the bug. It may look "weird" to you as much as much as it may sound weird to others that one is not willing to dirty their hands with some testing and still posts in a forum labelled as development.

That's the whole point of testing, mate. You test a potential bug in order to help the devs find a solution so that they can iron out the issue for all of us. Then, mind your words: "normal use" - what's normal to you may not be normal to others (otherwise we wouldn't have seen any reports about this issue at all), and then "it will never fail" - using never and fail together in the same sentence it's a bit like trying to defy Murphy's law, isn't it? ;)
[Galaxy Note 3 Android Development] temasek:
All variants have their own respective folders including kernels.

I support 3 variants in 3 download sites in 3 respective folders including 3 for rom 3 for kernels.

So many 3....

See OP
[Galaxy Note 3 Android Development] los82:
thanks!

was serching for a mentioned 4.0 kernal build but only saw 3.98 in the respected folders. Thought that maybe i was looking in the wrong places
[Galaxy Note 3 Android Development] temasek:
4.00 still infant stage.

Now still on V3 kernel.
[Galaxy Note 3 Android Development] Sendaris:
v146 is working great on my international HTLE. The only problem is Lens blur in the Google Camera app FCs while processing the image and doesn't save, I've had this problem for the last few versions so I'm not sure if it has ever worked on our phones?

I've tried clearing app data but it doesn't help.
[Galaxy Note 3 Android Development] temasek:
I suspect is my toolchain used for compiling the sources. I will attempt to change my toolchain next week when I've more time to play.
[Galaxy Note 3 Android Development] masze:
in other aosp the problem was always there, but in Temas i have no problem with spen. (never)

thats all i wanna point out..

And of course the fix is great.. but that was not why i post about!
[Galaxy Note 3 Android Development] temasek:
Slayher's spen fix is not in my builds yet.

V147 will have it.
[Galaxy Note 3 Android Development] dbanzon:
Guys what app do you use for screenshot?
[Galaxy Note 3 Android Development] xavihernandez:
No app, native function. You can include it in power menu for example.
[Galaxy Note 3 Android Development] masze:
hehe...

its that what i saying, my spen working with no issue WITHOUT the fix in your build.

In other aosp/builds i have the problem..

dunno why???
[Galaxy Note 3 Android Development] temasek:
I suspect the screen wakeup lag is due to the recent new adreno drivers.

I am compiling a test build without the adreno drivers and see if the lag is gone. It requires kernel reverts, hlte common branch reverts as well as vendor blob reverts.

I HOPE I AM WRONG!

More updates later.
[Galaxy Note 3 Android Development] kenz0bux:
wow this is amazing...never had this since my z1 days. thanks [MENTION=2332422]temasek[/MENTION]
[Galaxy Note 3 Android Development] temasek:
Cm derped

Audio muted.

Build postponed.
[Galaxy Note 3 Android Development] encho:
Great! One more annoyance less :p Last thing on my Rom bucket list is hover - can you update to latest one which has option to remove the icon from the notification area? :good:
[Galaxy Note 3 Android Development] temasek:
Last I tried it broke hover.

Any idea which rom has that option and it's working?
[Galaxy Note 3 Android Development] scoobyjenkins:
C-Rom Kang has it:

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] temasek:
I cannot find his github. Any idea?
[Galaxy Note 3 Android Development] scoobyjenkins:
Maybe he builds from official C-Rom github? https://github.com/X-ROM

I don't know if the feature comes from there or if it was added...

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] temasek:
Not there.
[Galaxy Note 3 Android Development] scoobyjenkins:
Maybe you could ask him? http://xdaforums.com/showthread.php?t=2831666

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] encho:
I had to go through my old nandroids to check which roms have it. Seems like most of them are ditching hover in favour of headsup (slim, carbon, du, etc). One that had hover is Liquid.
[Galaxy Note 3 Android Development] DeadPicsel:
Is the latest kernel working Okay with the latest M11 merges?
[Galaxy Note 3 Android Development] zadigre:
The latest kernel in temasek's build is not based on M11... It's based on nightlies + a few others commits.

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[Galaxy Note 3 Android Development] DeadPicsel:
I was using nighties but decided to switch to Snapshot builds for now. So would the kernel cause problems with M11?
[Galaxy Note 3 Android Development] encho:
Only one way to find out [emoji41]
[Galaxy Note 3 Android Development] temasek:
It's not the kernel u have to worry about.

M builds and Nightlies build shouldn't mix.

Eg

If u flash a M build which is older than your current nightly build u may encounter issues because of database version differences.
[Galaxy Note 3 Android Development] kamikaze2112:
Is nfc on its way for n900w8 anytime soon?
[Galaxy Note 3 Android Development] apacseven:
Were you able to figure out a work around? I am too getting massive ssp wakelock if I have lockscreen notifications enabled. TIA.
[Galaxy Note 3 Android Development] temasek:
I'm always on lockscreen notifications as I like it. My ssp wakelock always 0s.

I cannot replicate.
[Galaxy Note 3 Android Development] jdgamble:
Isn't ssp wakelocks from humidity and pressure sensor and not proximity sensor.
[Galaxy Note 3 Android Development] apacseven:
Correct. I didn't insinuate that it was related to proximity. It's likely related to slayhers sensor fix in some obscure fashion.
[Galaxy Note 3 Android Development] masze:
im on v145 @ v4.00-EXP1 and i have 0 wakelocks, working perfect..

what to gain in v146 with newer kernel?
[Galaxy Note 3 Android Development] Schneckmeier:
Yes, but you can temporarily stop these wakelocks if you disable lockscreen notifications - test it please.

In my opinion it's not a correct "fix" when other problems appearing.

By the way, who needs this temperature and humidity sensor?

We have cLock, that provides the temperature. And who needs humidity?

When its sultry i feel it with my body.
[Galaxy Note 3 Android Development] temasek:
What device variant u on?
[Galaxy Note 3 Android Development] Schneckmeier:
Good morning master,

i have the international Qcomm hlte.

Tested this the last week again and again with a new install only with Gapps and no other applications. When i switch to your kernel versions without the sensor fixes the wakelocks are gone.
[Galaxy Note 3 Android Development] temasek:
I'm also thinking of reverting the fixes for temp & humidity. I'll spin a build later this evening for hlte. Flash that and see if it helps.
[Galaxy Note 3 Android Development] Schneckmeier:
Many thanks - i'll give you feedback immediately then.