yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Yank555:
A last_kmsg will only be present after a

re

boot, becaus it is the end of dmesg kernel log of the previous run.

If you power down the phone, remove the battery, RAM is cleared, and you will just boot, there is no previous run, hence there is no last_kmsg.

JP.

---------- Post added at 09:39 PM ---------- Previous post was at 09:16 PM ----------

The hardware is awesome, the software Samsung imposes on us is a worser nightmare on every iteration of it, and unfortunately, part of that software we need even if we run CM on it, as bootloader and ROM-side is not GPL and as such closed source, we have NO ACCESS to it whatsoever. So the best hardware will still be as bad as the software we "have to" run on it, which in this case is pretty crap with bloat from my point of view (talking touchwiz), or became unstable for some since the KK bootloader (talking CM).

So what I hate is not the device, but what Samsung imposes on us.

We buy the devices, we pay for them (a lot of money, so they make a pretty good living on us), so we own the devices, they are ours, and yet Samsung still wants to decide what software we run on them, that's just not right !

I wave my right to warranty when rooting using custom recovery, kernel and ROM. That I can understand, if I run the device with software Samsung hasn't designed for it, they don't need to cover if the device stops working, but for heaven's sake, they shouldn't go on making this a nightmare :(

Let me make a different example, years back I bought a car, which cost about the price of 60 todays flagship smartphones and I tuned it when it had a few days only by replacing some parts and reprogramming the ECU and I decided to drive it on race tracks. The car's manufacturer didn't disallow me to do so, but if I blow the engine or so, that will be on me, period. That I can accept and is right.

And that is all I would want to see in smartphones, freedom of customization.

But now I'm definately going off topic here ;)

Since the matter at hand (and these are unfortunate conclusions of them) inpact every source based ROM since CM unification / Samsung KK bootloader update, as such it's not really off topic, but it could be a thread of its own where the matter is discussed cross ROM, but I'm not into being OP on xda anymore, if someone cares to, just drop a link in every major source-based ROM thread, we'll meet there ;)

+1, a big huge +1 :(

JP.

---------- Post added at 09:43 PM ---------- Previous post was at 09:39 PM ----------

BTW, if anyone on still on the old bootloader who want to run a non unified CM, I have a fully updated "old non unified" kernel, but I never cared to publish it, because I think I must be more or less the only chap on the planet running a January nightly on my Note 3 :D

If anyone's interested, just PM me.

JP.
[Galaxy Note 3 Android Development] dtr145r:
understandable.

my reboots always accompany a battery pull. holding the power button for any amount of time does nothing...
[Galaxy Note 3 Android Development] Yank555:
Argh, that's bad for logs, of course :(

Lucky for me, if I can put it that way, I could at least so far get away with a long-press...

JP.
[Galaxy Note 3 Android Development] dtr145r:
would you like to do a remote desktop via chrome?

You can run the commands and get the logs that will be valuable.

I can pretty much get it to tweak out and reboot...
[Galaxy Note 3 Android Development] avocco:
I had the Nexus 5 and loved it. The only thing that really bothered me was the battery life. But I hear that the Android L has potentially increased the battery life by 36%. I can't seem to settle on one Phone though. This is my 2nd Note 3 and I had 3 Nexus 5s.

I think the best phone I had software wise was the HTC One M8. That's the only phone where I was ever satisfied with the stock experience.

I truly hope that these new commits help toward the reboot problem. Otherwise its the HTC One again or another Nexus 5. My wife is going to kill me :(
[Galaxy Note 3 Android Development] temasek:
Pls try V109. Comes with Temasek Kernel v3.79 EXP1.
[Galaxy Note 3 Android Development] chazey2:
Thought I'd post my feedback.

Had n9005 for couple of days now, come from i9300 with Temasek cm11 rom ,Boeffla beta.

Within an hour of receiving new n9005 it was rooted ,CWM recovery installed and V108 with kernel 3.78. I updated this morning via dirty flash to V109 with the stock 3.79 EXP1 kernel.

From the outset I have been hammering the n9005 setting up Zooper widgets and adjusting a lot of Tasker profiles to suit the new set up. I have not had any FC's freezes or any other funny behaviour.

Don't know about what bootloader I have but can say phone arrived on 4.4.2, Base band XXUENB1.

Very happy so far slick and butter smooth and quick as I came to expect from every new update whilst using i9300.

Many thanks Temasek!
[Galaxy Note 3 Android Development] AO7:
After flashing V108 over V103 I am experiencing odd behaviour with the app EzPDF. Reading a PDF document in portrait mode works fine. But turning the phone to landscape mode will crash Android. On small documents it does turn the PDF into landscape mode but the screens flickers constantly black while scrolling.

Anyone who can reproduce? Could this be the video driver acting up?

I understand Android does not have a native PDF engine so apps are left to implement their own solution. If anyone else can reproduce I will file a bug with the app developers.
[Galaxy Note 3 Android Development] temasek:
Report only current build version & kernel.

I'm not interested in older releases.
[Galaxy Note 3 Android Development] Yank555:
On a battery pull, there's no log whatsoever, unfortunately.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.0 (3.4.94) kernel.
[Galaxy Note 3 Android Development] Snottierwhale:
I'm on the same boat as you all is extremely smooth with reboots being nonexistent. Great battery life and all-around enjoyable experience that will last me until my two year contract is up. Then I'm ditching the **** service they call sprint. Moving to a real phone company.
[Galaxy Note 3 Android Development] linx1287:
well....i cant live without xposed so i am prepared to except this quite minor inconvenience....btw v109 is running buttery smooth...absolutely clean installation....and not a single hiccup...hope everyone else is having the same experience...will report on battery life later as i just flashed it awesome work temasek :D
[Galaxy Note 3 Android Development] txpxsx:
Why would you buy nexus 5 jp? While nexus 6 will be released real soon?

[MENTION=2332422]temasek[/MENTION] are you on ART or Dalvik?
[Galaxy Note 3 Android Development] dtr145r:
I would like to say that i did have a live wall paper running.

i think that is why i was having a lot more problems than everyone else.

earlier today i disabled it and went with a normal one.

since then i only had 1 reboot,

its not the live wall paper causing the problem but it was one thing triggering it as i still get reboots when the phone has a load on it..

i think the reboots are caused by the CPU or GPU working harder than normal....
[MENTION=2332422]temasek[/MENTION] ive been busy today so i didnt get a chance to try your latest build just yet.

Ill be working the next 3 days so i wont be as active.

im gonna be keeping an eye on the CM change log to see if anything interesting pops up.

Ill most definately be able to flash something by monday night, hopefully sooner if i get the chanc.

thanks all.
[Galaxy Note 3 Android Development] viniciusrsouza:
What you mean by "load" for example? Can you give some examples of load scenarios that stress the phone to trigger your reboots issues?

Just to stay alert here and compare when it happens and, of course, report you.
[Galaxy Note 3 Android Development] dtr145r:
Example use phone prior to about 5 minutes after boot.
[Galaxy Note 3 Android Development] txpxsx:
I just had a reboot on 109 with temasek kernel settings. I never experience any reboots on 108. So this is serious for me.

It seems that mp decision sticks and would not want to turn off

---------- Post added at 10:24 AM ---------- Previous post was at 10:20 AM ----------

I also noticed auto rotation isn't sticking on 109
[Galaxy Note 3 Android Development] temasek:
So u had MP Decision & intelliplug both on?
[Galaxy Note 3 Android Development] orbital_71:
Mr Kang can u bring wave to turn on screen for ur rom i really miss that feature.
[Galaxy Note 3 Android Development] temasek:
No

Battery consumption

Get a flip cover and don't have to touch anything to turn off/on screen except with flip cover.

BTW u are not on my rom so why bother ask? :p
[Galaxy Note 3 Android Development] txpxsx:
Auto brightness has been acting weird. Phone heats up too
[Galaxy Note 3 Android Development] temasek:
I don't have all your symptoms.
[Galaxy Note 3 Android Development] orbital_71:
Kns it bcos u lor take it off mai ahni lah :(
[Galaxy Note 3 Android Development] txpxsx:
Yes, I restored trickster, got my old settings. Turned off mp decision. Got rebooted. Found out mo decision still on

It's switched on now. I could not switch it off, with intelli plug in always reboot lah.
[Galaxy Note 3 Android Development] temasek:
Somehow your trickster is not working properly. Wipe trickster data and reboot and try again.
[Galaxy Note 3 Android Development] txpxsx:
Will try that. Thanks
[Galaxy Note 3 Android Development] koyoupi:
On latest ver, whenever i play a video for mx player, the videos just flashes non stop, audio is fine. However, using another video player like Diceplayer, the video plays fine.
[Galaxy Note 3 Android Development] LunaMaria:
I can confirm that happens to me too for mx player SW decoding. Changing it to HW decoding fixes this though. Also in the latest v109 the CM theme not sticking after rebooting issue hasn't been fixed just letting you guys know.
[Galaxy Note 3 Android Development] koyoupi:
i tried changing to HW decoding alr, that didnt fix it for me.
[Galaxy Note 3 Android Development] temasek:
Xposed prevents cm theme sticking on reboot.
[Galaxy Note 3 Android Development] LunaMaria:
Oh.. Thanks for the clarification.. But at least I'm not having random reboots so it's not too much of a problem at the moment anyway[emoji4]
[Galaxy Note 3 Android Development] Yank555:
Because this weeks lost time was just too much, I'll get the Nexus 6 (or whatever it will be called) as soon as it gets out, I'll be a Nexus afficionado now ;)

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.0 (3.4.94) kernel.
[Galaxy Note 3 Android Development] temasek:
Nexus got its fair share of issues.

... And

No external SD card

---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------

I'm using mxplayer. Hw decoding OK. Only SW decoding got issues. Cm just merged reverts some commits from display caf new repo. Possibly one is to fix the video issue. The fix will be in next release.
[Galaxy Note 3 Android Development] Yank555:
Certainly does, but Samsung is just dead for me, the Note 3 has been but a nightmare on my end ... and my Nexus 7 been a dream.

Nothing is perfect, but I can have source based ROMs

without

having to accept CM's unification mess, by just going AOSP, which is not possible on a non Nexus, as CM is more or less the closest you can get to AOSP, and unification made hell break lose on mine ... and I'm not getting a few more Note 3 until one works fine ;)

Samsung's neverending "even worse after next update crap" gave me the rest, I'm done.

No external card is a drawback, agreed, but one I can live with, Nandroids, ROMs and kernels I can flash from a USB stick (via OTG), so that's acceptable.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.0 (3.4.94) kernel.
[Galaxy Note 3 Android Development] temasek:
Somehow I kept wondering why my Note 3 is flat stable. :(
[Galaxy Note 3 Android Development] koyoupi:
oh ok ty
[Galaxy Note 3 Android Development] txpxsx:
Lol

As if you don't have an excuse anymore to change phones

Let's us know, just in case ?
[Galaxy Note 3 Android Development] temasek:
Fixed

Available in V109.1
[Galaxy Note 3 Android Development] koyoupi:
Thanks!
[Galaxy Note 3 Android Development] Yank555:
Good question, but don't be sad about it, you're lucky somehow ;)

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.0 (3.4.94) kernel.
[Galaxy Note 3 Android Development] jayk32:
MX Player is working fine for me???? :confused:

Oh Well :cool:
[Galaxy Note 3 Android Development] mo123456789:
V109. Expanded desktop is greyed out in power button settings. And when enabling it in display settings it doesn't work.
[Galaxy Note 3 Android Development] temasek:
Toggle

Buttons, power menu, expanded desktop

---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------

HW, HW+ were OK in V109 but not SW mode in eg MX player

Fixed in V109.1 for SW decoding.
[Galaxy Note 3 Android Development] jayk32:
o.k cool. :cool:
[Galaxy Note 3 Android Development] AO7:
Issue resolved after dirty flashing V109.1
[Galaxy Note 3 Android Development] txpxsx:
Too many hangs resulting to boot system ui on 109. Also I got random reboots.
[Galaxy Note 3 Android Development] mo123456789:
I can't turn the toggle for expanded desktop on. Its just greyed out.
[Galaxy Note 3 Android Development] stonedead:
You need to enable it first in "display and light" setting..
[Galaxy Note 3 Android Development] Yank555:
Just gave latest nightly (with the revert mentioned here yesterday) a test, got a freeze / reboot after a few minutes, last_kmsg shows the usual mdss crash :(

Restoring my 20140127 Nandroid ... again ...

JP.

Send from my Nexus 7 ... who just had a break, had a Kitkat ...

Edit : The post I meant : http://xdaforums.com/showthread.php?p=53901735
[Galaxy Note 3 Android Development] temasek:
Time for you to move on to another rom or back to stock rom.

On all my releases it's been rock stable. Total reboot = 0. Total freeze = 0
[Galaxy Note 3 Android Development] Yank555:
It's not your ROM, it's the CM base, it just does not work on all Note 3, this unification brought us this mess :(

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.0 (3.4.96) kernel.
[Galaxy Note 3 Android Development] linx1287:
well i hope i am not the only one saying i am having a completely bug free experience with temasek's rom...so i will post something i have been curious about for a while..... [MENTION=2332422]temasek[/MENTION] is there any way to change the lockscreen style in cm? for example the lockscreen in oneplus one?
[Galaxy Note 3 Android Development] temasek:
What I need is source code.

Well u are the minority. I'm still enjoying freeze/reboot free experience.
[Galaxy Note 3 Android Development] BillGoss:
I would have thought that that's a reason for [emoji7] instead of [emoji20].

How often do you reboot your phone? Every day, multiple times a day,...? I find that the reboots take a day or so to kick in.
[Galaxy Note 3 Android Development] Snottierwhale:
I only reboot my phone to flash the updates when it comes out so sometimes it could be up to 3 days without power off and I'm still rock solid.
[Galaxy Note 3 Android Development] temasek:
I reboot by my own intention more frequently than most users. This is because of testing rom & especially kernel.

What the past posts by users are referring are auto random reboots triggered by rom or kernel. For this random reboots, I'm not having it.
[Galaxy Note 3 Android Development] dtr145r:
would you haven to have a nightly before unification???

id like to test drive an older version and see if the reboots still exist.
[Galaxy Note 3 Android Development] cdmackay:
[MENTION=2332422]temasek[/MENTION] - would you please consider this request? :

http://xdaforums.com/showthread.php?p=53526130

thanks :)

---

V109.1 seems goodo to me...

---

I go several days without a reboot, and no problems here (as no doubt you're all tired of hearing me say...
[Galaxy Note 3 Android Development] avocco:
Its definitely the CM base that's causing the problem. Not anything on your part Temasek.

Before I flashed the latest release. I even used Odin to go back to stock. And not being just content with that, I repartitioned using a .pit file and even performed a nand erase. Too make sure everything was 100% original.

I then did the OTA to make sure I was on the latest bootloader/modem etc.

Then I performed a complete wipe / followed by formatting system etc. I wanted to be sure that I was being thorough. I've also tried using both CWM and TWRP in case there was something in there ( highly unlikely ) but just to be on the safe side.

Still random reboots. I'm going back to stock and just gonna attempt to live with it for now.

Edit: I think its something in the hardware. Can't be anything software wise, I just wonder what it could be ?
[Galaxy Note 3 Android Development] viniciusrsouza:
I just imagine and understand the size of your frustration after doing all of this, since I'm part of the crew who like to navigate all the ocean again from the start just to be sure everything is nice and clear and avoid issues.

I was about to ask the same thing here. What's the chance of hardware differences interfere on these unstable experiences for some and great functionality for others? Is that possible? Maybe a manufacturing issue depending from where the devices "born"?

I think this absolutely doesn't have any kind of precedent, right?

We together need to report this to CM11 team. They must undo this unification!

==========

By the way, just a confirmation question. When latest build flashed, I won't need anymore to flash Temasek's kernel after that, right? Since it seems that it's now integrated, right?
[Galaxy Note 3 Android Development] temasek:
Latest rom build will always comes with latest temasek kernel even up to beta releases.
[Galaxy Note 3 Android Development] chazey2:
Your not no issues here either!
[Galaxy Note 3 Android Development] shaggyskunk:
Reading some posts -stock TW seems like a better choice.... For some people.....

Slim FAQ: http://www.slimroms.net/index.php/faq
[Galaxy Note 3 Android Development] laehtis:
I had some random freeze and then reboot just after bootup, but those was caused by trickster-settings, immediately after changing those, no reboots.

Idk if you are talking about the same thing, but just saying my experiences about rebooting, for me they're all kernel-settings related (my changed settings: min. clock speed and mp-decision off, intelliplug on)

And for bugs, I haven't had any major. Only is the camera sometimes derping with focus, but restarting camera fixes that, no need to force close. And second, if you answer call with speaker when the secure(pattern) lockscreen is on, touchscreen isn't working (not confirmed!!) And for those bugs, I think they're CM-base bugs.

UI is smooth, and I call my setup stable. Thank Temasek, for your awesome work.
[Galaxy Note 3 Android Development] mareis1973:
Have no issues with 109.1. Is working flawlessly. Lucky me

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] Yank555:
Those are still downloadable from CM site :

http://download.cyanogenmod.org/?device=hltexx

If you're still on the old bootloader, you can use these, else they won't boot.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.1 kernel.
[Galaxy Note 3 Android Development] d407974:
109.1 works great.
[Galaxy Note 3 Android Development] aybek555:
v.108 and v109.1 work great, blazingly fast and butterly smooth. Zero reboots, zero freeze. Thank you Temasek for your awesome work
[Galaxy Note 3 Android Development] dtr145r:
I have hltetmo I don't think I can flash that??

---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------

Plus I'm on the new boot loader.
[Galaxy Note 3 Android Development] AO7:
On N9005 with V108 I experienced my first and only random reboot. I traced it down in lastkmsg as a kernel panick. I know this is now an older version but can I help the people with frequent reboots by posting kmsg here?
[Galaxy Note 3 Android Development] piats:
Well can you look up what caused kernel panic. That's the real reason for reboots
[Galaxy Note 3 Android Development] AO7:
This is the immediate before and after. Problem is I don't know too much about kernels so I may be overlooking valuable info.

[ 6128.522205] w1_slave_found : no slave before, id=0x1
[ 6130.521948] w1_slave_detach: detaching 97-742000166f09 [dd043a00].
[ 6130.522011]
[ 6130.522013] w1_ds28el15_remove_slave
[ 6130.522190] w1_slave_release: Releasing 97-742000166f09.
[ 6506.963838] Fatal error on the ADSP!
[ 6506.963888] ADSP subsystem failure reason: memheap.c:1091:In task 0x0, Assertion block_ptr->forw_offset != 0 failed
[ 6506.964005]I[0: swapper/0: 0] Kernel panic - not syncing: adsp crashed: subsys-restart: Resetting the SoC
[ 6506.964102]I[0: swapper/0: 0] ------------[ cut here ]------------
[ 6506.964179]I[0: swapper/0: 0] WARNING: at /android/cm11/kernel/samsung/hlte/kernel/softirq.c:163 local_bh_enable_ip+0xb0/0xf0()
[ 6506.964263]I[0: swapper/0: 0] [<c010d04c>] (unwind_backtrace+0x0/0xfc) from [<c01a5a98>]
[Galaxy Note 3 Android Development] mareis1973:
After 1 whole day on 109.1 usage not even one Problem here. I guess it depends really on some crazy hardware things that some have probs and some not

Gesendet von meinem SM-N9005 mit Tapatalk

---------- Post added at 07:53 PM ---------- Previous post was at 07:43 PM ----------

I noticed just one little thing viper4 android isn't processing with new kernel. Before it did always. But no problem

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] Yank555:
hltetmo, maybe, new bootloader, then certainly not :(

JP.

Send from my 'proudly eFused' Note 3 (n9005) running CM11 hltexx 20140127 on Yank555.lu CM11 htlexx v1.1 kernel.
[Galaxy Note 3 Android Development] LancerV:
I havent had any issues with NF1 and hltetmo on 107 kinda afraid to flash newer version...........
[Galaxy Note 3 Android Development] ajm786:
I've been on 108 since it came out early last week. After the few issues I had during installation with the random hangs and reboots, it's settled down. I have had ZERO reboots since July 2nd; that's 4 full days of uptime.

As soon as the next version of temasek comes out that is not experimental, I will be installing it. Plus, I believe whatever reverts he did to the toolchain will most likely help with stability, so I'm all for it.
[Galaxy Note 3 Android Development] tusvik:
The latest build have been pretty stable for me, had 20+ reboot in a few hours on previous builds. Only had 3 today and mostly when I an in my car connected to Bluetooth