yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] viniciusrsouza:
[MENTION=3173896]dtr145r[/MENTION]

You quoted my post about expanded notifications, but didn't type anything about it. Did you forget to say something? :p

By the way, the setting I'm looking for is this one called "Force expanded view". It's present on CarbonRom. Credits to [MENTION=235478]padlad[/MENTION] for the screen shot.

Any change of adding this feature, [MENTION=2332422]temasek[/MENTION]?

About reboots and freeze issues, it's almost 12hs since I flashed build 105 and Temasek's kernel here and it's so far so good. No reboots or freezes.

Edit: Just found here inside "Notifications on lockscreen" that there is a "Force expanded view" setting for notifications displayed on lock screen. It's the last one on that page.

Still looking for the same settings, but for the normal notifications panel.

---------- Post added at 11:13 AM ---------- Previous post was at 10:47 AM ----------

Hi there [MENTION=1953422]cdmackay[/MENTION].

The only "breathing" settings I found was about SMS, Missed Call and Voicemail notifications icons in the status bar. Didn't find the "breathing" setting for the notification LED light. There is nothing about it inside LED light notifications settings here... :(

Which build are you using?
[Galaxy Note 3 Android Development] datajosh:
There's still no way to adjust the vibration intensity, is there? I think that's the only issue I still have personally.
[Galaxy Note 3 Android Development] cdmackay:
My apologies - I saw those settings, and just assumed they referred to a breathing light pattern, not a breathing notification.
[Galaxy Note 3 Android Development] viniciusrsouza:
Ok! No problem! ;)

Guys, I just installed Hangouts through Play Store and noticed that video calls are not working fine. I can't see the other contact video, only the contact picture at full screen. At least the image from my camera is shown correctly.

I tested on my PC and everything runs fine! Only when using my Note 3 this issue occurs. I flashed Banks Gapps Standart (latest one - 06/29), so Hangouts was not pre installed.

Does anyone noticed this? Or using another Gapps package that already comes with Hangouts is running video calls fine on your devices?
[Galaxy Note 3 Android Development] AO7:
V105 upgraded from V104. Still experiencing massive Google play services battery drain up to 25% of total usage.

Anyone else with the issue persisting? I'm not in a position to full wipe.

I'm using PA gapps. Temasek kernel on intellidemand with trickster.
[Galaxy Note 3 Android Development] datajosh:
I am too, I used the Disable Service app to enable SystemUpdateService under Google Play Services and Google Services Framework and that seems to have fixed it for now.
[Galaxy Note 3 Android Development] viniciusrsouza:
Bad news! Just got my first reboot... :(

It happened when I touched a video folder to open it using Documents app. My device froze and then rebooted.

As I said before, I'm using V105 and Temasek's kernel. Bootloader from 4.3 Samsung Stock ROM.

Didn't mess up with anything, unless changing animations speed to 0.5, just this.

Edit: I think there is some issues about Documents app. I'm getting a lot of "Documents has stopped" while trying to browse files with it mainly when opening video folders.

I have a lot of pictures and videos, maybe the app itself isn't dealing well the amount of files on my external SD card.

Don't know if this justifies the freeze and reboot I got, but I'm sure the native Documents app is not working so well here.
[Galaxy Note 3 Android Development] temasek:
V107 is up with Temasek Kernel v3.77
[Galaxy Note 3 Android Development] dtr145r:
The only kernel version I saw to download was 3.76

Where is it posted?

Thank you.
[Galaxy Note 3 Android Development] d407974:
look here

http://www.androidfilehost.com/?w=files&flid=11929
[Galaxy Note 3 Android Development] ajm786:
I was able to catch something in Logcat while it was happening. Basically, my freezes are exactly as described here:

http://xdaforums.com/showpost.php?p=53816094&postcount=848

I wish I saved the Logcat, because it said something like "Input ignored due to xxxxxxxxxxxxxxx" (I forgot what the xxxx'es was). So anytime you'd touch the screen or press any button, it would give that error message because the SOC was busy or something, rendering the entire device useless, and the only way you could reboot was to pull the battery.
[Galaxy Note 3 Android Development] dtr145r:
I actually have 2 log cats.

I don't think either say anything about that.
[Galaxy Note 3 Android Development] viniciusrsouza:
More bad news...

Just got my second random reboot. This time browsing Gallery.

It seems there is some kind of difficulties for the ROM when browsing media files, causing reboots.

Like the first time, the screen froze for a few seconds and then the device reboot all over again.

Edit: Third reboot right now. Again when browsing Gallery.

This is absolutely disappointing, since the ROM itself runs so smooth! And another very annoying thing is that I lose a lot (about 5%) of battery when this happens!
[Galaxy Note 3 Android Development] temasek:
I got zero reboots fwiw
[Galaxy Note 3 Android Development] viniciusrsouza:
I will flash latest build and kernel from today and check what happens.

Maybe would be useful return to Samsung 4.3 Stock and do absolutely all wipes again?

I think I will do some tests using the original kernel from the build itself. But I guess some people also experienced reboots with it also...

I'm confused... :(

Edit: Fourth reboot now. The third one when browsing Gallery app.

I'm questioning myself if maybe it's something related to the file system of my external SD card. I'm almost sure I configured it to FAT32 a long time ago. I will insert it on my notebook to check.

Any chance this is related to the issue? Maybe FAT32 is incompatible to KitKat ROMs?
[Galaxy Note 3 Android Development] stonedead:
Me too, zero reboot.. Now on v107, gallery and document both ran perfectly well.

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

Try running it without external sdcard, see if you still got a random reboot.
[Galaxy Note 3 Android Development] ajm786:
I got zero reboots when doing a clean installation of v106. However, today, I installed v107. Immediate reboot (actually screen froze and had to pull the battery). This happened 3 times in succession, the last being when the phone compiled Dalvik by itself instead of ART like I had chosen. This was all without my external SD card.
[Galaxy Note 3 Android Development] stonedead:
I dirty flashed v107 over 105, still with dalvik cause I need to use some xposed modules. So far so good…
[Galaxy Note 3 Android Development] viniciusrsouza:
Which kernel are you using? Default one or other?

I actually removed it for a while and browse a little bit the Gallery and Documents apps, but since I did a complete wipe from Samsung Stock 4.3 ROM there are only a few pictures on internal storage. Just one camera picture and 4 screen shots. But I didn't get reboots.

Just to inform, I didn't change anything about this Dalvik and ART thing. And I'm "glad" to hear that probably SD Card is not a reason for reboots, since you got them even without using it.

By the way, same question for you, which kernel are you using?

What's for sure is that reboots happens on both bootloaders, with or without external SD Card and with different Kernels. Pretty freaking thing.
[Galaxy Note 3 Android Development] stonedead:
Default kernel..
[Galaxy Note 3 Android Development] ajm786:
Same here. Default (as in Temasek) kernel.
[Galaxy Note 3 Android Development] txpxsx:
so you guys mean..all these reboots are due to CM commits...not the kernel itself ?
[Galaxy Note 3 Android Development] piats:
Yes & yes: CM commits in CM kernel source
[Galaxy Note 3 Android Development] AO7:
I think you need to go back to basic troubleshooting. Flash back to 4.3 Samsung stock, dump logcat while using the phone for a day or so. If that fixes your reboots start building from there. Custom recovery. Custom ROM. Custom kernel
[Galaxy Note 3 Android Development] viniciusrsouza:
But that's what I did. I was using Omega V4 (Android 4.3), so I did a factory reset and after that I got back to Samsung Stock 4.3 and did again a factory reset and then an absolutely clean up on my device manually (deleting all internal storage folders) and after this I used TWRP to wipe everything except External SD Card, of course.

I flashed Temasek's build and kernel from an absolutely clean device just because I already was reading a lot about reboots... :(

And I never had reboots issues on Samsung Stock or Omega V4.

Anyway, today I will test some combinations of kernel and ROMs here to give my experience to everybody, since it's pretty clear this is not an specific ROM or Kernel issue.
[Galaxy Note 3 Android Development] AO7:
What happens when you run the phone without an external sd card installed.
[Galaxy Note 3 Android Development] shaggyskunk:
Uhm - You don't have access to the content of the external sd card ?

Not everyone has an external sd card...
[Galaxy Note 3 Android Development] AO7:
I don't understand what you mean by that. He said he has one installed. For the purpose of testing he should remove it to eliminate another failure point.
[Galaxy Note 3 Android Development] shaggyskunk:
The external sd card would be very, very unlikely to have anything to do with reboots!!

Read post #878 He's right!
[Galaxy Note 3 Android Development] viniciusrsouza:
I tried for a while yesterday using without it and I didn't face reboots, but it was just for a few minutes, since I needed to go out. And, by the way, I had just 4 pictures inside internal storage to really browse. And other people that even doesn't use external SD Card are facing reboots too.

As [MENTION=4351374]shaggyskunk[/MENTION], probably it's not related to reboots. I'm even using FAT32 on it, that's theoretically a safe/stable file system for every ROM/Android version.
[Galaxy Note 3 Android Development] temasek:
I'm having zero reboots and I'm trying my best to reproduce it on my Note 3. So far not successful.

Anyway next kernel update should be able to grab any kernel logs available so at least this should help. Atm my kernel unable to grab last_kmsg logs.

BTW V108 expected tomorrow together with kernel v3.78

For those curious of my current setup

MP Decision off

Intelliplug on

Fiops scheduler

Interactive governor
[Galaxy Note 3 Android Development] dtr145r:
Let me know how to help you out when you release your next kernel version.

I use official cm but I'll install the kernel and get you the logs you need

I had about 30 reboots so far today.

They finally cleared up about an hour ago but I'm sure they'll start back up again.

Usually when a reboot happens I can't use anything on the phone until about 5 minutes after it turns back on. I guess to many apps trying to start back up at once.

If I use the phone before that it usually freezes and reboots again...

I really hope you can figure out what's going on with it.
[Galaxy Note 3 Android Development] chazey2:
Thanks Temasek

Big thanks Temasek got my n9005 rooted and an hour ago flashed V107 with 3.77 tema kernel. So far all running super sweet and slick. Just made my new n9005 experiance soooooo much better ,loving it!
[Galaxy Note 3 Android Development] avocco:
I've been having random reboots and tried near enough everything to get stable. Ive also tried temasek kernel and lean kernel and with exactly the same results.

I also downloaded 4 different stock firmwares and flashed each one using a pit file and wiping everything on internal storage. This includes a complete wipe ( data / cache / system and even formatting the / firmware ) all of them resulting in the same reboots.

I also switched to Slim ROM because of the stability that was suppose to exist and still same problem. I even tried temaseks version of CM and still reboots.

I thought maybe it was the gapps package I was using and tried 5 different versions including minimal and still same problem.

I think Yank555 was absolutely right regarding video drivers. Just before my device reboots it tends to get all slow and everything starts to stutter. Other times it will exhibit clear graphical glitches just before the reboot happens.

I'm just glad that we finally have a clue as to what is causing the reboots for some of us.
[Galaxy Note 3 Android Development] viniciusrsouza:
What's your experience when using Yank Kernel? Did you try that? (Sorry if you already posted about this. I'm so confused with all of this and following so many threads at the same time, reading posts and answers from so many people!)

I just got a reboot on CarbonROM (with it's default kernel) also when browsing Gallery. I'm just informing this to let everyone be sure that this is not an specific ROM or Kernel issue.
[Galaxy Note 3 Android Development] txpxsx:
Users who got reboots, are you on n9005 international?
[Galaxy Note 3 Android Development] viniciusrsouza:
I am!
[Galaxy Note 3 Android Development] dtr145r:
no i havent tried yanks kernel.

im waiting until tomorrow to try out Temasek's kernel and get the logs.

im not finding it just related to gallery. its any usage that causes them...

tmobile version
[Galaxy Note 3 Android Development] viniciusrsouza:
Oh, ok. I will give a try to Yank one right now and will report my experience.

And I agree that it's related to any usage. Maybe I'm only experiencing reboots on Gallery and Documents app because they are two of a few apps I'm still using, since I'm wiping my device every day.

Probably (sadly) reboots will spread to other system areas when I have more and more apps installed...
[Galaxy Note 3 Android Development] encho:
I am as well but have zero issues! My note never had such smoothness and stability. I hope it won't start behaving badly such as in your case now [emoji1]
[Galaxy Note 3 Android Development] viniciusrsouza:
Don't want to to give you bad expectations, but my Note also never had such smoothness! It's so great and faster than crappie Samsung TouchWiz garbage.

The unique problem is the reboot one.

Edit: By the way, already on Yank's kernel here. Let's wait and see...
[Galaxy Note 3 Android Development] temasek:
V108 is up. Comes with Temasek Kernel v3.78.

There are some updates & reverts to display caf new repo so its recommended to update to V108. Also includes many bug fixes.

Kernel changelog

- Lots of updates to intelliplug by faux

- Linux 3.4.96

- fixed kernel log

- some other misc stuffs.

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

ATM I'm having DNS issues with temasek.hopto.org site so its not available.
[Galaxy Note 3 Android Development] stonedead:
Thanks..Will try this as i got problem with theme in v107,theme applied correctly but some parts return to default after restarting phone.

Clean install also didn't help..
[Galaxy Note 3 Android Development] temasek:
CM Theme is still WIP and the devs are pushing updates VERY frequently.
[Galaxy Note 3 Android Development] stonedead:
Ok mate..don't worry about it.
[Galaxy Note 3 Android Development] dtr145r:
how do i get the kernel log when i have reboot?
[Galaxy Note 3 Android Development] dtr145r:
Just wanted to let you know that when I clicked to download the kernel from devhost this apk tried to come with it....
[Galaxy Note 3 Android Development] temasek:
/proc/last_kmsg
[Galaxy Note 3 Android Development] stonedead:
Theme problem fixed in v108..

---------- Post added at 10:27 AM ---------- Previous post was at 10:18 AM ----------

Those with reboot problems, did you guys enable back up and restore data option after login to Google account? I've seen this create some problems before..
[Galaxy Note 3 Android Development] ajm786:
Installed 108. After everything loaded, I pulled down the status bar, cleared a notification, and when the notification bar went back up, the phone tried to freeze and crash, but then recovered. Instead, it restarted the UI and kicked me back to the lock screen.

This has happened many times before. Hopefully now that we have kmsg, we can narrow it down, once and for all.
[Galaxy Note 3 Android Development] dtr145r:
Yes I normally bypass that screen and the option is already checked.

I just flashed the newest kernel AMD I'm awaiting my next reboot so I can get the log.

When I install tomorrows nightly I will unchecked that option and see what happens.

I actually had a similar problem a long while back with the gapps package I was using.

Is anyone else using banks gapps?

Specifically minimumal if it matters...
[Galaxy Note 3 Android Development] ajm786:
No. I never use that option, because all the apps I install that need root won't work correctly unless you grant them rights again (after a clean install, that is).
[Galaxy Note 3 Android Development] dtr145r:
good news.

i had my first reboot on the newest kernel.

im hoping to have the log soon

:D

EDIT:

I dont have a 'lastkmsg'

the only thing there is kmsg.

maybe ill get a lastkmsd when i have another reboot...

i guess we will see..
[Galaxy Note 3 Android Development] stonedead:
I just found out that it was xposed framework which is responsible for themes problem.

Uninstalled xposed framework and it's all good now..
[Galaxy Note 3 Android Development] dtr145r:
just to be clear,

the option was checked but i never let the play store restore any apps. i would always stop them first.

[MENTION=2332422]temasek[/MENTION]

I had 2 reboots so far and im still not getting a 'last lmsg' in the proc folder...

do i have to enable anything to get it to do the logs or am i missing something...??

EDIT:

3 reboots.

i also verified that i am on 3.78

thanks
[Galaxy Note 3 Android Development] temasek:
U on V108 or official cm? If official cm pls update next nightly build first. I suspect is the display caf stuffs.

I'm still having solid stability here with zero reboots. Also last_kmsg is available here.

1. What app u using for kernel?

2. What's your kernel configuration?

3. What Rom release u using?
[Galaxy Note 3 Android Development] dtr145r:
I'm on official cm 20140702 nightly.

Here is a screen shot of the proc folder.

Its not showing up for me..
[Galaxy Note 3 Android Development] temasek:
Backup your rom, flash my V108 and check again. See if it's more stable.

This is my /proc folder

https://www.dropbox.com/s/rnbk5p0owmpkeqy/Screenshot_2014-07-03-11-42-06.png
[Galaxy Note 3 Android Development] txpxsx:
i got a reboot while waiting for Google signing in. this is my last_ksmg

thanks temasek
[Galaxy Note 3 Android Development] ajm786:
I'll tell you one thing v108 fixed. From version 100 to 107, music playback was pretty bad with popping and clicking all over the place. V108, while not perfect, has brought it back down to a completely acceptable level, which means almost non-existant.

Tema, was there any commits that would have affected audio playback? I read over the commits in your github, but nothing stood out.

---------- Post added at 11:58 PM ---------- Previous post was at 11:57 PM ----------

Looks like Yank was right. The kernel panic was caused by MDSS.
[Galaxy Note 3 Android Development] temasek:
I didn't have audio issues at all so I didn't even know it exist.

I must have a solid note 3 here with me. Haha :)

---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------

Hammerhead recently merged tons of mdss stuffs and I suspect many of it may be added to our cm kernel sources soon. As there were too many mdss commits from hammerhead so I didn't port over.

Hopefully soon it will fix this issue for most of u. I am perhaps few or even only one not affected by any freezes or reboots. Kind funny.
[Galaxy Note 3 Android Development] stonedead:
You and me actually..:D
[Galaxy Note 3 Android Development] dtr145r:
I had 1 reboot while restoring my spa so far.

I got the last kmsg this time.

I'll try to get it attached

Thanks
[Galaxy Note 3 Android Development] temasek:
This is my setup for my kernel. You may try to see if it's stable for u guys.

Only use trickster

MP Decision off

Intelliplug on

Interactive governor

Fiops scheduler
[Galaxy Note 3 Android Development] scoobyjenkins:
That's naughty devhost on Chrome! If you hit back and try again, should be OK. Or use Dolphin.

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] txpxsx:
this settings are unfriendly with v107, since i got a lot of reboots, will try on 108 and report you back
[Galaxy Note 3 Android Development] Whosat:
Anyone has a quick guide on getting last_kmsg and stuff?

BTW, latest cm-temasek on BTSync key: B4KT6BM5224H5UCMSGTYMNX5YMTFY2NHK
[Galaxy Note 3 Android Development] Yank555:
Welcome to the mdss_fb0 crashers club, your video driver just went down the drain...

What is you exact device model and which bootloader do you have etc. give most possible details if you can ;)

Thanx, JP.

---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------

Use any root explorer, copy the file "last_kmsg" located in "/proc" to your sd-card and then zip it and upload it here.

JP.

---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------

What helped a lot for me, though it's still not 100% stable, was to revert the mdss commits added on May 24, 2014 and May 26, 2014 by Cyanogen.

The day I added those, hell broke lose on my old n9005 (hardware revision MP 0.602, manufactured date 2013.09.18). And it drastically improved again when I removed them again. I'm on 4.3 bootloader still, also.

JP.

PS: This app gives you a lot of details on your device.
[Galaxy Note 3 Android Development] scoobyjenkins:
So builds of roms using these sources prior to that date could be more stable? I'm happy with my current setup but grabbed a May 23rd build just in case!

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] Yank555:
It's not a ROM build thing, I'm talking kernel commits only here. I don't know if those commits were paired with any changes in the ROM, like was the case with the 201406030 <-> 20140701 commits which broke video if using the wrong kernel <-> ROM combo.

I do only look at the kernel side of things, which indeed may at times only be half the picture :(

JP.
[Galaxy Note 3 Android Development] scoobyjenkins:
Ah, fair enough. Though it did seem to be around May time when my issues started if I remember rightly!

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] Yank555:
Likely when these commits went in :(

Same was for me.

JP.
[Galaxy Note 3 Android Development] dtr145r:
here is my last kmsg from last night.

not sure what im looking for in there.

can you check to see if its the same as the other one?

thanks.
[Galaxy Note 3 Android Development] Yank555:
Definately a different story ...

[ 469.347202] sec_debug_check_crash_key code 116 value 1 state 0 enable 0
[ 469.347355] (sec_debug_set_upload_cause) 85
[ 470.138369] sec_debug_check_crash_key code 116 value 0 state 0 enable 0
[ 470.138447] (sec_debug_set_upload_cause) cafebabe
[ 473.010027] init: untracked pid 2660 exited
[ 476.044414] SysRq : Emergency Remount R/O
[ 476.145148] set_dload_mode <0> ( c019b86c )
[ 476.145195] (sec_debug_set_upload_magic) 0
[ 477.522810] Restarting system with command ''.
[ 477.523560] Calling SCM to disable SPMI PMIC arbiter

Problem happened about a little less than 7 minutes after boot...

But not mdss / video related as it looks.

JP.
[Galaxy Note 3 Android Development] ajm786:
Here's someone with the exact same issue on an older device. It also happens to be a Samsung, too.

https://jira.cyanogenmod.org/browse/CYAN-2222
[Galaxy Note 3 Android Development] Yank555:
Where do you see the "same issue" ? I've looked at the last_kmsg, it's a very different thing...

If you mean this :

[257414.713069] SysRq : Emergency Remount R/O
[257415.098755] Restarting system.

That's generic, just saying it manages to properly put the filesystem to read-only and initiate the reboot.

The last line is not what matters, it's where it starts going down the drain ;)

JP.