yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] stonedead:
On v112 now, clean installed. Got a constant reboot when opening ES file explorer. Something must be wrong here cause I never had a reboot problem all this time before...
[Galaxy Note 3 Android Development] Schneckmeier:
Same here, no theme installed and temasek kernel prefs used

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] viniciusrsouza:
Well, just like on V109.1, I didn't have any random reboot until now after almost 12 hours on V111.

Except for the two items I reported earlier (about pocket mode insisting to be activated and wallpaper flashing when unlocking device), everything is running fine here!

Not using Xposed and any kind of theme here...
[Galaxy Note 3 Android Development] txpxsx:
V111 has been rock solid! Reliable performance! Wallpaper flashing occurs when you apply live wallpaper only. It's not a big deal though. 7-1 was a big deal. Sorry
[Galaxy Note 3 Android Development] viniciusrsouza:
Strange. Wallpaper flashing occurred here also before using Muzei Live Wallpaper (that only blur the image I was using before, original Android L wallpaper). Will use it again without Muzei blur effect to check if that flashing will stop. Anyone using V112 can tell us if it's also occurring?

7x1 was a HUGE deal, my friend. Actually, a national (sport) tragedy. I think the unique worst sensation than that was only when Ayrton Senna died.

Tema, I'm not using any custom kernel and I will not mess with it to check how long this rock solid random reboot free experience will persist, but I really would like to use touch wake feature.

Is there any file I can edit to enable it using your kernel?
[Galaxy Note 3 Android Development] ajm786:
V111 seems to be working out for me as well...after the ridiculous time I had installing it yesterday. For the first time ever, I was actually able to undervolt all voltages across the board by -25mV, with no consequences to speak of yet.
[Galaxy Note 3 Android Development] viniciusrsouza:
Setting a normal wallpaper doesn't avoid that wallpaper flashing when unlocking here. Will turn on Muzei Live Wallpaper again.

Just noticed that Google+ does not work with Hover. It shows "Google+ stopped." with the OK button pop up. After touching OK the app itself opens in full screen. I will black list it from Hover now to stop that. (Edit: I will black list it from floating mode! Hover is working great. What is not supported for Google+ is floating mode!)
[Galaxy Note 3 Android Development] linx1287:
[MENTION=2332422]temasek[/MENTION].... i have a very selfish request & i hope you dont mind...but could you release a system ui apk with imaged battery of 4.3 unlike the coded one of 4.4? this way....many of the xposed battery mods could work again.... i have no issues with any of your roms... i can run xposed and themes without running into any issues...so thats why i was hoping you could make a systemui with that old battery system....thank you
[Galaxy Note 3 Android Development] viniciusrsouza:
Bad news...

Suddenly my Gallery app stopped to load folders and pictures thumbnails, facing difficulties to even open pictures itself and was hanging when opening it's settings, where we can disable online pictures sync, eternally loading Google account.

Trying to open images using Documents app also resulted in the app itself hanging. Then I also noticed YouTube app couldn't open any videos. When trying to play something it simply froze.

I deleted cache for all three apps, but didn't solve the issue. After some time, when the screen turned off, I got a sleep of death and, after about two minutes, I got a reboot even before the need of force resetting it or removing battery.

This time the issue was involved again to Gallery and documents app, with the YouTube problem as a bonus. Don't know if all of this can be related.

Edit: Again, a new freeze followed by a reboot inside Gallery app. All my nightmares are back... =/

Will full wipe again later and move to V112, or maybe get back to V109.1.

Edit 2: Less than 5 minutes later, again a new freeze and reboot inside Gallery app. Impossible to use it.

Simply can't understand what's causing all this random instability madness!
[Galaxy Note 3 Android Development] caesar_:
Every time you reboot.. Go into trickster and reconfigure the values.
[Galaxy Note 3 Android Development] viniciusrsouza:
I don't use this app. I'm absolutely at all default settings. Even Titanium Backup to restore things I don't use. You suggest that I try different settings with it?

I'm planning now to full wipe (as always) and start all over again with V112 and Yank's kernel again.
[Galaxy Note 3 Android Development] linx1287:
why do you use the stock gallery and camera app? i use oneplus one's camera and gallery and both are rock stable...no issues and i did a comparitive test with pictures and the oneplus one camera app produces a better picture....v112 is running absolutely stable....not even a single reboot....did another clean installation and using xposed and themes

also...as soon as i flash the rom and gapps i do a couple of freezing on unnecesary stuff and then i go back to recovery and i flash this http://xdaforums.com/showthread.php?t=2360670 .... and tweak my settings in trickster as following

read ahead buffer 1024 deadline

gov intellidemand

mp decision off

intell-plug on

multicore power save 1

temp throttle on
[Galaxy Note 3 Android Development] viniciusrsouza:
I just try to stay as stock and "default" possible simply trying to avoid issues, just that.

But thanks for the tip. Will give a try as soon as possible.

Did you get these from Play Store or from any XDA thread?
[Galaxy Note 3 Android Development] linx1287:
xda thread....trust me...its as close to stock as it can be but with a bit more flair....i am running an error free v112
[Galaxy Note 3 Android Development] caesar_:
Default settings will have your minimum governor stuck at 1190Mhz.. Changing it in the cm performance tab and it will not stick.

I've had better luck with it sticking with trickster. Although you have to reconfigure after every reboot.

With default settings I was rebooting continuously.. Below are the settings I have configured in trickster. Haven't rebooted in days.

Trickster settings.

TCP Congestion Control: Westwood

Scheduler: row

Frequency Lock: off

Min: 422400

Max: 1728000

Governor: ondemand

With these settings.. Minimum has been locking true at 422 and the phone hasn't been rebooting due to minimum over clocking and overheating.

Good luck.
[Galaxy Note 3 Android Development] ajm786:
I've found that it has more to do with MP-Decision. If you use MP-Decision, you're probably not going to be able to reliably have the minimum CPU speed locked. If you use Intelli-Plug, you'll be able to.
[Galaxy Note 3 Android Development] caesar_:
Like I said.. It locks with the settings I provided. And doesn't freeze or reboot. Hope everyone profits from it. I didn't change mp_decision or intelli plug and things are fine.

Either way.. It needs to be reconfigured after each reboot as values will just change back to defaults and you'll be back to freezing and rebooting in no time.

Good luck
[Galaxy Note 3 Android Development] ajm786:
Everyone's phone is different. And if he's using Trickster, there is absolutely no reason to have to reconfigure after every single reboot if you set Trickster to set those for you on startup. I never do on mine, and settings are always set after bootup, and locked. I have plenty of screenshots to prove it. My phone spends the majority of its time in Deep Sleep, and when on, in the 300Mhz range.

If you didn't change MP Decision or Intelliplug, chances are you're running MP Decision. You should try Intelliplug; it's much better.
[Galaxy Note 3 Android Development] caesar_:
I switched to intelliplug just for the sake of testing and rebooted and all my configurations were set back to default.

But you're right, all phones are different.

What works for one may not work for everyone. All I know is I used to get reboots 5 minutes apart. Using the performance tab did nothing. Trickster is the only thing that has given me consistent uptime.
[Galaxy Note 3 Android Development] stonedead:
Did you tick kernel setting to set on boot in trickster? Trickster should load your current setting if you set it that way.
[Galaxy Note 3 Android Development] caesar_:
That worked for me.. I was just using lock frequencies. But locking kernel settings now I don't have to reset it every boot.

Thanks for that.
[Galaxy Note 3 Android Development] txpxsx:
I wonder if ART makes any difference with this rom ? i tried but don't feel any difference. what do you suggest?
[Galaxy Note 3 Android Development] ajm786:
It makes a slight difference; it's smoother. HOWEVER (reason for the caps there), there is a big tradeoff. Your apps better be compatible, or you're going to go through reboot hell.
[Galaxy Note 3 Android Development] temasek:
V112.1 is up. Pls try it.
[Galaxy Note 3 Android Development] ajm786:
Just tried. Brand new clean install. Pulling down the status bar crashes the phone IMMEDIATELY, requiring battery pull to restart. 100% reproduceable, happens every time.

Installing 3.78 kernel over it fixes it.
[Galaxy Note 3 Android Development] viniciusrsouza:
Did you try Yank's kernel on latest builds? If yes, got stability?
[Galaxy Note 3 Android Development] temasek:
No issues here whatsoever.
[Galaxy Note 3 Android Development] orbital_71:
Theme sound and notification does not stay in latest build after reboot
[Galaxy Note 3 Android Development] sauron82:
I think that's from Xposed. It has problems with new Theme Engine I think.

Click thanks if I helped you
[Galaxy Note 3 Android Development] chazey2:
Or here, all good.
[Galaxy Note 3 Android Development] ajm786:
I have used Yank's kernel in the past. It did not help with stability. In addition, I have to keep coming back to Tema's kernel because it has Intellidemand, and I get much better battery life and performance with it.
[Galaxy Note 3 Android Development] Schneckmeier:
Same bug with 112.1 as yesterday with v112, freeze and reboot every time when starting ES-File Explorer.

Flashing kernel 3.79 from 070714 solved the problem => definitly a Kernel Problem
[Galaxy Note 3 Android Development] orbital_71:
Nope 111 was fine not 112.1
[Galaxy Note 3 Android Development] Ogy77:
I used banks gapps standard 4.4.4 but ART not work,anu help?
[Galaxy Note 3 Android Development] temasek:
I'm almost giving up doing rom/kernel for hlte.

Everything is fine at my end be it rom or kernel on all releases. :(

My patience wears on thin ice.
[Galaxy Note 3 Android Development] Schneckmeier:
Hey temasek,

we don't complain about your work - we want only the best ROM for note 3 that will be even better ;)
[Galaxy Note 3 Android Development] temasek:
It's not that.

I cannot replicate any issues. That's frustrating.
[Galaxy Note 3 Android Development] Schneckmeier:
Have you installed ES-File Explorer? Please test it.

For me i have no reboots since v50 or so but only since v112 i have problems.
[Galaxy Note 3 Android Development] shjane:
No issues

Hey temasek, if it help in any way I have never had 1 problem either! On V111 (flashed yesterday before 112) and rock solid!
[Galaxy Note 3 Android Development] chazey2:
None of these issues here either.

Why not try solid Explorer? It's better I think.
[Galaxy Note 3 Android Development] eaver:
same here. been running your builds for nearly a month without a single crash or reboot.
[Galaxy Note 3 Android Development] SkyThes:
A month ago I had also several reboots per day but the latest versions are rock stable!

Please don't leave us Temasek :(
[Galaxy Note 3 Android Development] aybek555:
No issues here

+1 Temasek your roms and kernels are rock stable for me. Btw I'm using art with no single issue, zero freezes, zero reboots. Thank you for your awesome work and your time. Your over 2300 followers for only hlte are always waiting your rom/kernel and I'm sure majority have no single issue please don't leave us.
[Galaxy Note 3 Android Development] Yank555:
[MENTION=2332422]temasek[/MENTION] :

I agree that it's frustrating not being able to reproduce the issues as that gives no chance at all to fix them :(

But even though I'm able to reproduce them (well let's say they impose on me randomly), I still don't how to fix them either, that's likely even more frustrating ;)

I'd suggest to go on making your ROM/kernel for the sake of the lucky ones being able to run CM based ROM flawlessly on their Note 3.

Once, or if CM fixes the base issue, all other will jump in and enjoy your work at that point.

I will continue making kernel updates for the unified CM, even if I don't / can't use them, in the hope that sometime soon I'll benefit from them as well.

And so long, this Nexus 5 will be in my pocket instead of my Note 3...

JP.

Sent from my Nexus 5
[Galaxy Note 3 Android Development] viniciusrsouza:
Does CM (already) knows about all these (random) issues?

I already know you [MENTION=2033478]Yank555[/MENTION] don't want to OP an integrated thread for all AOSP ROMs (since all ROMs users are facing these crazy issues), but I think that you and [MENTION=2332422]temasek[/MENTION] have a pretty strong respect absolutely sufficient to get their (REAL) attention about this. I'm sure they would stop a little bit and reflect about this if coming from guys like you, differently from a few (maybe a lot) users reporting (crazy and random) issues.

Please, help us! :(
[Galaxy Note 3 Android Development] temasek:
Trust me.

We are nothing to cm devs.

The only way is thru cm hlte maintainers, unless they uninterested or cannot reproduce the issues like me.

Random reboot is the effect and not the cause.

Worst is i don't have random reboots. :(
[Galaxy Note 3 Android Development] ajm786:
THANK YOU. This is exactly what I was about to say.

CyanogenMod seems to have forgotten their roots. They look with disdain on people who report issues, like they are the ones who are doing something wrong. These days, instead of fixing issues, they do one of two things:

1. Stall until the next M release, at which point they ask "Do you still have the issue on the latest release? Install it and then update this issue and let us know if you still have the problem."

2. Close your report as not enough information/CM is not the problem/you're not running M version/etc.

As I said previously, we are lucky to have devs like Temasek. I don't know what I'd do without his ROM on my Note 3. If he stops making it, I'll be forced to sell it. Regardless of the reboots. All I can tell you is that Temasek and Yank are probably the only two devs who are actively trying to help the community solve the reboots...and the problem is not even their kernels/ROMs. It's CM, and CM refuses to believe anyone who has issues with the Note 3 and CM.
[Galaxy Note 3 Android Development] tsukot:
Mine rock stable as well. If I'd not be able to have temasek as my Note 3's maintainer ?, or able to have his ROM releases, I'd die! Lol
[Galaxy Note 3 Android Development] Dahdoul:
Hi guys this my first cm 11 on note 3 so if you don't mind I have some questions.

1. Is possible to change the screen DPI on cm?

2. Can I change the grid size of the drawer menu without installing another lunchers.?

3. Sound seems distorted any way to fix that?

Thank you,
[Galaxy Note 3 Android Development] radicalisto:
1 - texdroider_DPI @ playstore (unless the ROM you are using has DPI editor in custom options of course)

2 - Xposed mod will let you change the grids on default AFAIK

3 - Turn off touch sounds as it's an issue on CM ROMs has been for a while/
[Galaxy Note 3 Android Development] temasek:
Pls try to replicate the time issues that N9005 users having in V64.

Let me know if it happens.
[Galaxy Note 3 Android Development] Schneckmeier:
For me the time/date bug is fixed with v64.

After reboot the correct time is immediatly shown at the PIN-inputwindow

Great Job!!
[Galaxy Note 3 Android Development] temasek:
Pls show your thanks to

[MENTION=5147713]wilfredlams[/MENTION]

It is his fix of the old time daemon that he found to be the solution.

Cheers :)
[Galaxy Note 3 Android Development] gianton:
Is the time daemon fix applies to the recovery time/date bug too?
[Galaxy Note 3 Android Development] fahadali2315:
Nah i still got it in twrp. But its good that whenever i reboot,whatsapp doesnt show up that time change everytime. Yayyy happiness.
[Galaxy Note 3 Android Development] Dahdoul:
I have some problems , I will be thankful if someone could help with me it.

1.I keep getting inaccurate date error on whatsapp in every reboot and sometimes happen randomly.

2.some apps uninstalled it self. And others give insufficient storage when i try to update it.

Thank you.,
[Galaxy Note 3 Android Development] fahadali2315:
Try the latest build V64 .

It doesnt have whatsapp bug anymore.

Do full wipe.

Should solve all bugs.
[Galaxy Note 3 Android Development] Dahdoul:
Thank you and developer for the new update, the date error got fixed.

But distort speakers still exist I followed the guy method on post #102 with no joy. Any suggestions?
[Galaxy Note 3 Android Development] turbovan:
Just got going with Temasek build a few days ago, I must say its a great ROM, so thanks to Temasek and all other contributors - great work! :highfive:

I have found one issue now that I cannot seem to solve. From the Quick Settings panel, I tried out the power saving function by changing from Balanced to Power Save. Immediately I noticed that Vibrate on Touch stopped - I guessed it was to save power. Later I set the power setting back to Balanced.

But now I cannot get vibration to work at all, not for touch and also not for incoming calls - no vibration at all.

I tried rebooting, and I feel the vibration as the phone first boots so I am sure the vibrator still works, but then nothing.

Any suggestions? I have a N9005 and on V62.
[Galaxy Note 3 Android Development] piats:
Hlte - Temasek kernel v3.32 will add updated cm kernel sources.

Hlte - Temasek kernel v3.32 is up.

Changelog: https://github.com/temasek/android_kernel_samsung_hlte/commits/staging-v3

Download links:

http://temasek.hopto.org/?m&dir=Samsung Galaxy Note 3 - hlte/CM11/Temasek Kernel V3 (V50.1 onwards)

http://d-h.st/users/temasek/?fld_id=33687#files

Lähetetty minun hlte laitteesta Tapatalkilla
[Galaxy Note 3 Android Development] davjak:
Do you mean Vibrate on Touch located in Settings > Sound ?
[Galaxy Note 3 Android Development] piats:
There are new governors included in latest temasek's kernel. They're called HYPER & nightmare :D

Lähetetty minun hlte laitteesta Tapatalkilla
[Galaxy Note 3 Android Development] temasek:
U missed mentioning Pegasusq governor.
[Galaxy Note 3 Android Development] jaycb420:
Just wanted to say thanks for the kernel. Loved your old tree kernel, and the newest version is excellent. Think it surpasses your previous efforts. Thanks for the hard work, and helping me pimp my phone out.

Sent from my ZeroLemon powered SM-900W8 running W03SlimKAT v12 over clocked to 2.7GHz Temasek v3.30 using Tapatalk 4
[Galaxy Note 3 Android Development] temasek:
Damn myself.

I added schedulers but forgot to enable it. Will be in next release.
[Galaxy Note 3 Android Development] Dahdoul:
How to disable auto turn on screen when take your phone from your pocket?

Thanks

---------- Post added at 03:54 AM ---------- Previous post was at 03:26 AM ----------
[Galaxy Note 3 Android Development] temasek:
Lockscreen, lockscreen notifications, disable pocket mode.
[Galaxy Note 3 Android Development] temasek:
Temasek kernel v3.33 is up. Those using my kernels are encouraged to update it.
[Galaxy Note 3 Android Development] txpxsx:
bro, i told you already. we both follow temasek wherever he goes. lol

anyway, if you're not having any issues now, as you were having problems before baseband upgrade...i think maybe unmatched baseband could be the problem ?

i'm having 0 issues though on v112, but for the sake of trial, i'm about to update to latest baseband on sammobile

[MENTION=2332422]temasek[/MENTION], what's your current baseband model? latest singapore firmware/modem does not give me the best 3G signal, it's frustating :eek:
[Galaxy Note 3 Android Development] tsukot:
I just upgraded to the latest rom for my TGY note3.. I was on old BL, so basically from old - - - > new :)
[Galaxy Note 3 Android Development] Yank555:
So if I get it right, you had reboots while being on the old bootloader, and those stopped upgrading to the new bootloader ?

Generic question to everyone having random reboots :

Which bootloader are you on ?

I tough to have read reports with new bootloaders as well, but it's all a little mixed up in my mind by now :(

JP.
[Galaxy Note 3 Android Development] linx1287:
i think the samsung's stock firmwares should be flashed and that too the latest ones as they might be the source of all the headaches....i am running NF3 & no issues to report.... however when i was on NB & NC's i did face some freezes...so people with issues should try to flash the NF3 and then root it and use recovery to flash temasek's rom...maybe that might wipe out all the issues users are having.....
[Galaxy Note 3 Android Development] tsukot:
Yes. Had multiple reboots back then when on old BL. Downloading 1.3gb stock is a pain in the a## in the Philippines but it was worth the wait!

I just downloaded the latest stock for my region/csc which was TGY. Thats it.

But i also read reports on new BL's still having reboots. Puzzled ?
[Galaxy Note 3 Android Development] rendler:
Can't someone just post the latest bootloader file only for flashing in Odin?
[Galaxy Note 3 Android Development] mareis1973:
Hey temasek. I have no problems on my end with your brilliant Rom. Don't dare to give up[emoji12]

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] tsukot:
Dont dare to stop sharing your builds or else WE WILL HUNT YOU in SINGAPORE. haha
[Galaxy Note 3 Android Development] viniciusrsouza:
I'm using 4.3 bootloader from the latest 4.3 released ROM for Brazil.

I confess I already thought about a step forward and update to the new bootloader, but, for Samsung, almost always a step forward means go back to to pre-historical ages...

For example, there are reports on the Brazilian Note 3 community on G+ that the latest BTU stock ROM is blocking root.

And just to inform and to let everybody even more sure that it's not an specific ROM issue, I just full wiped and flashed the latest another CM11 based build (Carbon) and I got two freezes and reboots in sequence when browsing Gallery app in less than 10 minutes after flashing it.

Tried it using your kernel, [MENTION=2033478]Yank555[/MENTION].

Will test V112.1 now!
[Galaxy Note 3 Android Development] kamikaze2112:
Been running 111 for a couple days now, rock solid, no issues whatsoever.
[Galaxy Note 3 Android Development] Yank555:
Do also test with stock kernels, to see how they "cope".

JP.
[Galaxy Note 3 Android Development] Schneckmeier:
I'm using 4.3 bootloader from the latest 4.3 released ROM for Germany.

No Exposed, stock theme, preferred settings from Temasek in Trickster.
[Galaxy Note 3 Android Development] viniciusrsouza:
Yeah, will do this also! ; )

Oh God! Don't say "Germany" again, please! :crying:

:p

Going to the point... what's your experience through the time? Ever had reboot issues and got rid of them? Or didn't have and got it any time?
[Galaxy Note 3 Android Development] boriska975:
Just a thought.

Maybe it has to be taken in mind that also combination bootloader/baseband better to be from the same ROM.

There was(is) a number of cases when people flashed a fresher stock TW rom through odin and got freezes and other issues. Then they realised (through phone INFO app for example ) old baseband still there (it could happen in various cases). And then finally getting same version of bootloader and baseband(modem) solved they problem.

Maybe it's not the case here but who knows...