yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] linx1287:
from what i understand after reading through some other rom threads and this....mixing bootloaders modems and such and not flashing the whole rom package may be a source of issue for users....its always better to flash the whole package and not just bootloader or modem..... its a pain for me to download 1.9GB all the time i have to flash a new TW rom as my internet speed is abysmal to say the least....but its worth it when you have a completely smooth rom with mad battery life :D
[Galaxy Note 3 Android Development] HSD-Pilot:
The last two are toooo hard to show :D

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] Yank555:
Well I never flashed any update, so I still have the bootloader, modem etc. that came with the Note 3 when I bought it...

JP.
[Galaxy Note 3 Android Development] Snottierwhale:
Dont stop the ROM updates. I've been extremely stable for 3 months. If u need to take a brake from looking at the forums.
[Galaxy Note 3 Android Development] scoobyjenkins:
I started out with 4.3 bootloader that came with the phone and chose not to update as I had read you can't go back. After a while I decided to flash a 4.4 stock rom, root and flash custom rom again. All went fine but started getting reboots around the same time as others on Temasek and Carbon did. When someone posted a theory about mismatched bootloader and baseband I recalled that after flashing stock rom, system was still described as custom in download mode and perhaps following the advice to get everything official before starting again rooting and flashing might help. I did that and my reboots stopped for quite a while, then came creeping back again! So I'm guessing it is something to do with video drivers but don't know how flashing stock temporarily resolved it! Do you know what the CM maintainer for our device thinks about the reboots?

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] Yank555:
No idea, don't know if anyone actually is looking into anythign thelike.

The commits come from Cyanogen himself (he comitted them to the hlte kernel repo, he didn't write them).

JP.
[Galaxy Note 3 Android Development] ajm786:
What happens if he simply reverts them? Is he going to lose the unified ability for the entire HLTE line?
[Galaxy Note 3 Android Development] Yank555:
I reverted the bunch that made it go from "bad" to "hell", but there are so many ... and partially they might come with ROM counterparts.

It would be easiest if the one who added them (kernel & ROM) would revert them to a level where all was working fine.

JP.
[Galaxy Note 3 Android Development] Amd4life:
I'm going back to my last stable 4.4.2 build backup (kernel 3.69) to try and go forward till the reboots started on my device. What was the last temasek kernel that would work for 4.4.2 , right before the 4.4.3 Roms started?

Thanks
[Galaxy Note 3 Android Development] ajm786:
You guys think this is the issue? It's a report on CyanogenMod Jira about the MDSS patches, although the device is a Hammerhead.

https://jira.cyanogenmod.org/browse/MC-21
[Galaxy Note 3 Android Development] viniciusrsouza:
Well guys, V112.1 gave me stability again.

Full wiped and all my basic apps installed again, without using themes, Xposed, Titanium, etc. All done by manual work, as always.

I confess I didn't have enough courage to have fun with Gallery app to check if it will bring me freezes and reboots.

Didn't check if Lock Screen Notifications is still forcing screen turn on when removing device from pocket.

Wallpaper flashing is still occurring when unlocking device. I'm. using See Through Blur feature, so this is more noticeable, but it's a minor issue, of course.
[Galaxy Note 3 Android Development] txpxsx:
Maybe it's better for you to upgrade bootloader etc please try.

I've upgraded this morning, woke up very early, and I'm happy that my phone now have better 3G signal than before

Also I haven't got any reboots which I usually have after playing with themes and xposed
[Galaxy Note 3 Android Development] viniciusrsouza:
I'm creating more courage about this...

Actually I really would get an updated firmware and a updated Brazilian modem, that's true, but at present I think this reboot issue is in fact related to video driver or even my external SD Card, because 99% of my freezes followed by reboots is occurring when I'm simply sliding Gallery app left or right. Maybe something related to my external SD Card is causing that, since all my pictures and videos are there.

And some builds ago this happened also when browsing these files using Documents app. So this rises even more my questions about any kind of external SD Card possible reasons for this.

At this moment my notebook's HD is full and it's battery is already pretty old. I will need some days to free up some space on it and to replace battery (to use Odin safely...).

I'm thinking about formatting SD Card on NTFS in instead of the actual FAT32. Or maybe just formatting it and moving all files again to check if this Gallery browsing coincidence stops.

But well, if I stop to think a little bit, I will remember that I already got reboots just outside Gallery and even not messing up with pictures or videos.

And then... I get crazy!
[Galaxy Note 3 Android Development] ajm786:
I doubt it's anything related to the external SD card. I've installed CyanogenMod vanilla, no tweaks, and different versions of Temasek's ROM, no tweaks. No external SD installed. As soon as the ROM would load, it would hard lock, and/or I would get random reboots. So it's not the external SD.

I actually ran the phone for a week without the external SD card because I thought that was the problem. No dice. Still got the same old hard locks and random reboots.
[Galaxy Note 3 Android Development] viniciusrsouza:
I was almost sure it was too early to celebrate. Got a freeze and reboot when opening a picture on G+ app. If froze exactly on the picture opening animation.

This is crazy, not ROM related, not kernel related, simply random and there is no solution.

It's a deal with it or go back to stock ROM frustrating thing.

I'm starting to hate Samsung!
[Galaxy Note 3 Android Development] ajm786:
Actually, this is completely the ROM's fault. And not Temasek. It's a CyanogenMod issue.
[Galaxy Note 3 Android Development] viniciusrsouza:
I will take a rest a few days about all this full wiping everyday and will Odin the latest KitKat firmware from Brazil and start all over again.

Encouraged by [MENTION=1267978]txpxsx[/MENTION], need to say, although, for example, already knowing that [MENTION=4728887]scoobyjenkins[/MENTION] just did this and didn't get rid of these issues.

And one true fact about this is that we have people to say that their reboot issues started after upgrading bootloader, others will say that only had reboots before upgrading. Clearly there is no rule for this. It's a matter of luck.

For now on I will simply live with it and will start to flash new builds dirty flashing, something that I never did since I started navigating on custom ROM world on my Note 1 (trust me). I'm perfectionist, always prefer a clean installation when I decide to update something.
[Galaxy Note 3 Android Development] shaggyskunk:
There is more than likely - Some user apps or settings that are the issue - I'm running a different Rom - with Tema's kernel - and have no issues with freezing or reboots - Temasek is running his Rom and kernel with no issues... As are many others - Neither Tema or any other Dev - can control what users introduce into the mix - Run Tema's Rom and kernel with his settings (exactly his settings!) And you will almost certainly avoid the issues... It's Not temasek - it's not CM - It's not any other Dev's "fault"....

Slim FAQ: http://www.slimroms.net/index.php/faq
[Galaxy Note 3 Android Development] ajm786:
I beg to differ. It is statistically true that there are a number of users who actually have apps that are to blame. But the reality is that there is something wrong with the MDSS commits in CyanogenMod. These random reboots are happening across the board with a lot of devices, not only the HLTE.

I can install CyanogenMod, vanilla, no tweaks, no apps, nothing, and it will still freeze on boot up. Randomly. And when I say freeze, there is no way to run any type of custom settings, because you don't even get that far. The phone freezes on the CyanogenMod splash screen. The only thing that can unfreeze it is pulling the battery; not even the power button works.

If CyanogenMod vanilla freezes like that, I don't know how much more clear it can be that it is CyanogenMod to blame. And like I said, ever since Tema got dmesg enabled in his kernel (like Yank has had in his), the culprit of these hard locks and reboots 90% of the time has been MDSS related. It is actually only a testament and due to the hard work of devs like Tema and Yank that we're actually able to use our HLTE devices. The few times that CM did boot up and I was able to use it, it was atrocious compared to Temasek ROM. And this is coming from someone who is a supporter of CM.
[Galaxy Note 3 Android Development] abbyhacko:
Hey i am using samsung gts-6312 model . Can anyone tell me where i can cynogenmode 11 ,gapps and kernel . Thanks in advance !:thumbup:
[Galaxy Note 3 Android Development] viniciusrsouza:
But all these days I'm already running everything stock. Now, for example, running V112.1 with it's own kernel. Didn't mess with theme, didn't installed Xposed, didn't even enabled Development Settings! Just to be sure I'm almost default as possible.

Only installed some Google apps from Play Store and about 5 more "inoffensive" apps like SpeedTest, Root Explorer, Cerberus...

But well, you gave me a reason to try something I didn't do yet. I will try to use that Trickster app for the first time and set the same settings Tema is using. But you need to agree with me that just at this point I won't be at a "default" status anymore.
[Galaxy Note 3 Android Development] ajm786:
Hey all, maybe this will help us. Post what bin # your phone is. You can find it here:

sys/devices/system/soc/soc0/soc_pvs

I'm curious to know what Temasek's phone is. Technically, the best is supposed to be a 6. Mine is a 1. :(

https://gist.github.com/imoseyon/7226820

According to Imoseyon, a bin 1 is supposed to get higher voltages. Look at the difference between bin 1 and bin 4 voltage values. I can tell you that by default, the voltages I'm getting are for bin 4 when they should be for bin 1. I can definitely see how the phone would lock up now since it's probably getting "starved" for voltage.

Again, this is only a hunch. I wonder what CM's default kernel does with the voltages according to the bin values? Or does it just ignore it?
[Galaxy Note 3 Android Development] viniciusrsouza:
That's it! That's the point!

I got these almost immediate freezes on welcome screen using another ROM for example. The difference is that I never needed to remove battery. My device always reboots.

Thankfully Temasek's and Yank's hard work give us the opportunity of having usability!

---------- Post added at 12:13 AM ---------- Previous post was at 12:07 AM ----------

Number 3 here!
[Galaxy Note 3 Android Development] ajm786:
Hmm. The lower CPU frequency voltages are almost the same, but in the upper registers, your bin calls for more voltage.

What are your default voltage values that Trickster reads when you open it up? In mine, it's wildly off, because bin 1 should get a lot more voltage than a bin 3 or 4.

I'm going to test my theory. I'm going to do another brand new clean install of Temasek v112.1, except this time I'm going to try LeanKernel.
[Galaxy Note 3 Android Development] viniciusrsouza:
Never used Trickster before, just installed it now. I'm lost.

Where I get this info? I'm using the free version.
[Galaxy Note 3 Android Development] ajm786:
In the tab that says Specific (the last tab). All the values are toward the bottom.

They range from 300 to 2265 (and maybe higher, due to whatever kernel you are using).

I just flashed Imoseyon's kernel. I hope I might be onto something. The default voltages are EXACTLY according to the table I linked. I'm getting voltage values for bin 1, which are higher than bin 4.

I tried to make the ROM freeze, which I normally can by pulling down the status bar, and swiping back and forth really fast between the notification area and the QS tiles...but it doesn't freeze!

Testing further. More to come...
[Galaxy Note 3 Android Development] viniciusrsouza:
Here it starts on 300MHz at 750 and finishes on 2496MHz at 1045.

Is this what you need?

What interferes on that bin number thing? Manufacturing related thing?

By the way, using V112.1 with it's own kernel.
[Galaxy Note 3 Android Development] ajm786:
Your bin is 3. You are getting values for almost a bin 6, which means that your CPU is potentially getting starved for voltage.

Download and flash Imoseyon's kernel and test it out. Try and see if you still get instability.

Make sure you download the right one. It is AOSP kernel, v3.3.

https://onedrive.live.com/?cid=f1ed4badfee3fc02&id=F1ED4BADFEE3FC02!218
[Galaxy Note 3 Android Development] viniciusrsouza:
Ok, will try that!

I confess I'm trying hard to understand all that info from that link, but I simply can't. But I think I'm understanding what you are saying.

Will be necessary to configure anything here after flashing kernel or it will do all the work by itself?

Edit: Tried to reproduce that swipe left and right inside Notification Drawer as fast as possible, but my device doesn't freeze on this situation.
[Galaxy Note 3 Android Development] ajm786:
Just download the file, flash it, and test for instability. Don't do anything else. By not tweaking, you're not introducing any other variable into the equation.
[Galaxy Note 3 Android Development] viniciusrsouza:
Ok! Will need some hours or even days to state any practical results here, since differently from you I don't have any freeze recipe here!

I even tried to reproduce reboot swiping left and right inside Notification Drawer as fast as possible, but my device doesn't freeze on this situation.
[Galaxy Note 3 Android Development] ajm786:
That's fine. Just use the phone as you normally do, and try to go into the Gallery or whatever it was that caused your phone to freeze the last time, and see if it does it with Imoseyon's kernel. Then report back.
[Galaxy Note 3 Android Development] jayhi74:
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

[MENTION=3770600]Schneckmeier[/MENTION]

Thank you for this I was getting the reboots on 112.1 but this fixed it!
[Galaxy Note 3 Android Development] ajm786:
What's your bin #?

http://xdaforums.com/showpost.php?p=54064179&postcount=1216
[Galaxy Note 3 Android Development] chazey2:
No issues here what so ever.

V112.1 stock kernel bin no 2.
[Galaxy Note 3 Android Development] jayhi74:
1
[Galaxy Note 3 Android Development] ajm786:
Ok, now what are your voltage ranges from 300 to max?

---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------

You also, what are your voltage ranges from 300 to max?
[Galaxy Note 3 Android Development] jayhi74:
300-22656
[Galaxy Note 3 Android Development] ajm786:
Not CPU frequency. Voltages please. You can find them in the Specific tab if you have Trickster installed.
[Galaxy Note 3 Android Development] jayhi74:
Ohh dohh sorry!
[Galaxy Note 3 Android Development] Whosat:
Bin 2

Voltages 750 - 1070mV

I'm getting quite a stable build on temasek's cm using his kernel. Gallery, ES File Explorer, swiping notification down when scrolling through xda's all forum list view, all doesn't crash the phone.

Ran a 3D game nonstop for 8 hours and no reboots, freezes or FCs.
[Galaxy Note 3 Android Development] ajm786:
Yours is a little closer, but still looks like its undervolted. Your values are like a mix between bin 3 and higher bins. Hard to tell since I don't know what the values are in between.
[Galaxy Note 3 Android Development] viniciusrsouza:
Kernel flashed! Let the tests begin! Now I'm from 775 to 1170 here.

By the way, what differentiate that bin number on our devices? It's a manufacturing related thing? What's it's meaning? What it causes?

I searched at leanKernel thread for a discussion about these findings, but didn't find anything. I want to take part of the discussions and efforts! Where you got this? Could you please point the thread's link?
[Galaxy Note 3 Android Development] ajm786:
From Imoseyon's kernel thread. Simply do a search within the thread for the term "bin".

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

His kernel voltage tables, based on bin #.

https://gist.github.com/imoseyon/7226820

His specific post on bin #.

http://xdaforums.com/showpost.php?p=46931621&postcount=336

---------- Post added at 12:07 AM ---------- Previous post was at 12:05 AM ----------

Yours is being rated close to a bin 4 when it should be bin 1.

Now, I'm not saying this is really anything. Tema or Yank need to chime in on this since they are the kernel gurus. Or even Imoseyon. But it's still worth mentioning. Our phones might be picky about voltages. If they don't get the voltage they need, they'll randomly crash, freeze, or reboot.
[Galaxy Note 3 Android Development] viniciusrsouza:
My limit of thanks for today was reached. Be sure I will give you all possible thanks later!
[Galaxy Note 3 Android Development] jayhi74:
Thank you [MENTION=3106156]ajm786[/MENTION] for your info and help much appreciated!

And I can't thank you enough Temasek for all your hard work! 112.1 is sweeeeeeetness!!!
[Galaxy Note 3 Android Development] temasek:
I'm 2 too
[Galaxy Note 3 Android Development] ajm786:
Well, the man says it himself. :( Don't know about my theory anymore, but I'll stick it out a few more days with Imoseyon kernel and see how it goes.

And yes, I too am on v112.1, and it rocks.
[Galaxy Note 3 Android Development] caesar_:
Can't those mpu values be changed within trickster
[Galaxy Note 3 Android Development] ajm786:
They can but the problem is that they are not defaulted in the kernel. Which means during startup and for a time after startup, you are running undervolted, which opens you up to random rebooting and data corruption.
[Galaxy Note 3 Android Development] caesar_:
I'm a little under volted myself.. Just slightly.

I'm bin 0..

I'll try lean and see if it gets me closer.
[Galaxy Note 3 Android Development] mareis1973:
I'm 3

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] ajm786:
Dammit I already miss Tema kernel and faux sound.

[MENTION=2332422]temasek[/MENTION], would you be willing to release a kernel which uses Imoseyon's bin kernel voltage tables? This way were can take this question out of the equation. I'd really rather be using your kernel quite honestly since I've already found some things I don't like about Lean kernel.
[Galaxy Note 3 Android Development] temasek:
I'll have a look at his sources later.

Imoseyon is a well respected kernel dev so don't u dare say u don't like his kernel! :)
[Galaxy Note 3 Android Development] ajm786:
Lol! Understood! And thanks for looking into it!

Mostly the lack of faux. I really need that HQ sound. And his kernel causes audio to stutter when waking the screen up from being off. Your kernel doesn't do that.
[Galaxy Note 3 Android Development] Schneckmeier:
oh guys so much to read in the morning, why don't you sleep at all in the night? ;)

mine is bin 1, Voltages from 775-1095 with temaseks kernel 3.79 from date 0707.
[Galaxy Note 3 Android Development] sauron82:
Same here. Running v110 rock solid since release.

Click thanks if I helped you
[Galaxy Note 3 Android Development] caesar_:
Wow with lean 3.3 it wouldn't even let me unlock the phone.. Reboot every time I swipe.

Had to upload Temasek kernel 7/7 via USB on the lock screen and flash just to unlock my phone dam
[Galaxy Note 3 Android Development] ajm786:
I had the opposite experience. Nevertheless, I reloaded Temasek 3.78 except this time I'm using the Lean kernel bin 2 voltage table. I needed my Faux sound back. :D
[Galaxy Note 3 Android Development] caesar_:
Next time I make a nand backup I'm gonna change those values.. Too tired to start messing with it tonight.
[Galaxy Note 3 Android Development] viniciusrsouza:
I told this is a random crazy madness! Bizarre things happening randomly on our devices!

For me it's pretty stable until now.

No problem, I'm still testing it here and will continue to report my battle!

Does your device still reboots when you do that Notification Drawer trick after this?

By the way, I always disable the native equalizer and install ViPER4Android, that is still working using Imoseyon's kernel.

Or at least is not causing the sound issue you reported. Played music here and turned off and on the screen without any sound issue!

Edit: Bang! Device froze and rebooted just when I opened Gallery app. This time I couldn't even browse. It froze immediately.

So frustrated... =/

Edit 2: Two more reboots. One more inside Gallery app and another one just 1 minute ago when I was typing here this post edit.

Nowadays when the first one appears to me, then comes a sequence!

I need to flash Temasek's kernel as fast as possible.
[Galaxy Note 3 Android Development] txpxsx:
mine is 3, that explains why I got the reboots.

so what's the best recommended voltage for 3? this reminded me of the S3 days playing with voltages and daily temasek rom builds
[Galaxy Note 3 Android Development] caesar_:
I wanted to try viper 4 audio but never knew which one to install.. One says for 4.2.2 and the other says for 4.3 which one is working good for our device?
[Galaxy Note 3 Android Development] txpxsx:
are you sure 3.3 it's for aosp ? not for tw ?

i think his latest kernel for aosp was 3.1
[Galaxy Note 3 Android Development] ajm786:
So far I had gotten no reboots on Imoseyon kernel. On Temasek 3.78, even with the same voltage settings applied, I got 3 reboots.
[Galaxy Note 3 Android Development] caesar_:
The kernel I flashed had cm in the name.. There's really only one thing that cm means, aosp. I could be wrong though.

But then again I think if I flashed a tw kernel I wouldn't have got past the splash screen. On the kernel I flashed I was getting to the lock screen.
[Galaxy Note 3 Android Development] shaggyskunk:
That's really strange - I flashed CM Nightly 07/04 on my N3..... Not a single issue!

You say that there's a problem "across the board"... I have a Note 2, Nexus 7, Skyrocket & the N3.... And no issues on any of the 4 Devices!!

Reading through some of the posts - Why are some people messing around with under volting etc - Is it because you think that you know more about Android and Kernel development than the Devs??

Slim FAQ: http://www.slimroms.net/index.php/faq
[Galaxy Note 3 Android Development] ajm786:
I have a SGS 3, my Note 3 , and a Nexus , and they all have some kind of issue with CM vanilla. One of the reasons I switched to Temasek. And we are not talking about undervolting at all. The opposite actually.
[Galaxy Note 3 Android Development] chazey2:
750-1070
[Galaxy Note 3 Android Development] Yank555:
Just a stone in the water :

My kernel does not have a voltage interface (by design, messing with voltages mostly brings instability for no real gain), but to those who use my kernel, I have updated the voltages tables from day 1, the voltages in my unified kernel (Samsung KK kernel base) has the voltages bumped up to Samsung JB kernel levels, which is +25mV accross the board for all bins.

I have a 3, reboots are a daily issue, so I don't think CPU voltages are the cause, that was the first thing I looked into when I switched to unified builds. That's also the reason I upped the voltages to bring them back to JB levels where all was fine and stable.

JP.
[Galaxy Note 3 Android Development] tsukot:
2 here as well. ROCK STABLE.

? ive been like a troll telling mine is rock stable. Haha.