yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] zroice:
[MENTION=4709667]Wootever[/MENTION]: Thanks! Just two final questions (or 2 and a half..):

1.) Do I need any additional sources or is the github clone enough? When running make command I got some file not found errors like "sys/types.h" and I dont have that folder. Do I need a "base kernel source" which gets "enhanced" by your github sources?

2.) Quick command to get the linaro installed? On linaro.org the downloads seem to be source files themselves, not prebuilts. (and how/where should I install it to?)

or quick way to compile it myself? (I'm "good" with the terminal and coding logics etc. I would say but I just haven't used linux much lately, so sorry for these "noob" questions..)

2.5) Where do i get the ramdisk? In your github there is no such thing it seems. (and you modified the ramdisk too, right?) Do you have sources or just edited the existing prebuilt ramdisk of n9005? (if thats the way to go, then I'll just extract the ramdisk image from the latest kernel - but honestly I would like to see the source for these too, to maybe even disable some more knox crap like the watchdog or the enterprise stuff that seems to run inside the init binary as far as it looks... at least the watchdog)
[Galaxy Note 3 Android Development] amirnote:
this kernel has damaged my efs ...

i had restarted my phone and it couldnt boot . after i had able to make it boot (installed rom with bl ap csc cp pit) i had black screen and my phone was also restarting...

i think i lost my imei after i fixed the imei , my phone can not register on the network !!!!

any idea ? what should i do ?
[Galaxy Note 3 Android Development] raychak:
Very common on Note3, try this http://xdaforums.com/showthread.php?t=2507403
[Galaxy Note 3 Android Development] zroice:
Regarding that bootloop / no network issue (for me this lately happens after deinsallation of system apps... have to clear or restore efs to make it go away..):

I saw that in the custom version of TWRP created by Wootever the modemst1 partition gets cleared every reboot. And I also read somewhere else that clearing that partition and also the modemst2 does also fix this. But the "bootloop fix" script just formats efs - so which is the right one?

The bootloop fix at least gives a temporarily fix to me, but I wonder if it makes sense to just manually clear the modemst1 and modemst2 partitions one time to see if that helps to prevent this bug from reappearing. Can I just safely format modemst1 and modemst2? I created backups, just incase .. but still better ask hehe to make sure I dont **** up my phone by this ...

ADD: By the way - since that bootloop fix script basically clears the /efs partition, any clue where the "real" efs stuff is saved now? Is it hardwired or is it just on some other partition? Even after clearing the efs with the bootloop script etc still doesnt clear imei or anything, so it must be located somewhere else right?

ADD2: So I saw Wootever's post inside the bootloop fix thread that one can safely clear the modemst1 and modemst2 partitions. He had the same problem as me, that every time smth on the /system partition gets changed the weird bootloops begin. Efs restore temp fixes that, but the next time I change something again, the problem is back. Let's see if wootever's fix changes this permanently..
[Galaxy Note 3 Android Development] amirnote:
my rom is ML2 singapure

i flashed this a moment ago but it does n t work ...

should i flash mj7 rom ?
[Galaxy Note 3 Android Development] zroice:
Thanks alot man! Hopefully I can contribute something useful hehe.. but I will first have to get familiar with the code anyway hehe. But thanks so much for the explanation. Saves me some big time to figure it all out myself lol!

---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------

Do you have a backup of efs made by TWRP? You can try to restore this one. That also helped me at times when bootloops occured. (if not then try to also clear modemst1 and modemst2 like discribed by wootever in that other thread).

And where does it hang? Inside android or bootloop before even showing the homescreen?
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3160325]zroice[/MENTION]

As far as i can tell the error is starting from modemst1, also the efs script fixer does not format the efs but the modemst1 partition, it is the same thing but wrongly labeled.

My recovery build got locked up because of formatting that partition on every recovery boot, probably not not the best solution, but i only move into recovery to fix this corruption issue. ;)
[Galaxy Note 3 Android Development] zroice:
sigh, no clearing modemst1 and modemst2 actually didnt help.. I just deinstalled a system app and phone behaves weird again...

gonna try to grab a logcat

....

ADD: WEIRD stuff happening... so I first cleared both modemst1 and modemst2 (inside android, while running). Then I rebooted and deinstalled the "trim" system app with titanium. Rebooted and had no battery icon and phone not responding correctly (this is how this bug shows itself to me..). So I forced reboot to recovery and ran the bootloop fixer again (like 100 times in the past lol..). And the bug disappeared.

So I reinstalled the trim app (just copied the apk over and fixed permissions). Rebooted, and everything was still fine.

Then I deinstalled it once more.. and still everything is fine now. Bug didnt reappear so far.. but could only be temporarily. Loool just as I wanted to get a logcat the bug doesnt occur...

ADD2: Just deinstalled another system app (sim toolkit) and still bug-free... maybe clearing that modemst2 as well did the fix..? But it still reappeared once more after I cleared both the partitions... so no clue yet.
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3160325]zroice[/MENTION]

This is just temporary as soon as something got accessed/deleted/changed in a specific way (that is currently unknown) on a protected partition the modemst corruption starts again.

Edit:

Maybe a knox related issue?
[Galaxy Note 3 Android Development] zroice:
It might be related to the watchdog daemon? This thing writes out something like a counter:

I/SystemServer( 1699): Init Watchdog
E/Watchdog( 1699): !@Sync 0
E/Watchdog( 1699): !@Sync 1
E/Watchdog( 1699): !@Sync 2
E/Watchdog( 1699): !@Sync 3
E/Watchdog( 1699): !@Sync 4
E/Watchdog( 1699): !@Sync 5
E/Watchdog( 1699): !@Sync 6
E/Watchdog( 1699): !@Sync 7
E/Watchdog( 1699): !@Sync 8
E/Watchdog( 1699): !@Sync 9
E/Watchdog( 1699): !@Sync 10
E/Watchdog( 1699): !@Sync 11

... the sync error probably results from the missing knox apps I'm guessing. (would be good to know if this error appears on untempered devices).

So maybe after the counter reached a certain point something triggers that will cause the problem if anything is changed on the system partition afterwards.. But this is just a really wide guess... could be totally unrelated. But still - we should try to get rid of this watchdog maybe - its not present on non knox phones afaik.

ADD/EDIT: Well I just remembered that these logcat errors already appeared on my phone when I still had knox 0x0 (but rooted). And at that time it was rock solid. No bootloop issues or smth like this. So I guess its unrelated to our problem here.

But yea it could be still related to something else with knox. Since it only seems to appear once the knox counter is triggered. (aka when running a custom kernel).

We should try to flash the stock kernel back on our knox 0x1 devices and see if the bug appears there at all. If not then it must be a problem in the kernel source maybe. Otherwise it's knox trigger related most likely.
[Galaxy Note 3 Android Development] amirnote:
where should i clean the modemst1 and modemst2 ?

does it help me to register on the network?
[Galaxy Note 3 Android Development] Wootever:
[MENTION=4841176]amirnote[/MENTION]

Download this file and install it with your custom recovery.

Edit:

modemst gets handled by /system/bin/rmt_storage, if it's renamed or missing the same error occurs as with the modemstorage corruption.

logcat | grep rmt_storage

Now we need a reliable method to reproduce the corruption issue.
[Galaxy Note 3 Android Development] zroice:
# make mrproper
/home/user/Desktop/Kernels/kernel-samsung-n9005/scripts/gcc-version.sh: line 25: /home/opensource.m/toolchains/arm-eabi-4.7/bin/arm-eabi-gcc: No such file or directory
/home/user/Desktop/Kernels/kernel-samsung-n9005/scripts/gcc-version.sh: line 26: /home/opensource.m/toolchains/arm-eabi-4.7/bin/arm-eabi-gcc: No such file or directory

My linaro toolchain is inside /opt/linaro-4.8 and the path is definedto /opt/linaro-4.8/bin in .bashrc (working)..

But somewhere there is an old entry inside the scripts it seems. I checked gcc-version.sh but this is just where the error occurs and not where the variable is defined. Any idea?

Well I guess I gotta redownload the latest source. Think i just have outdated source now. (you just updated to linaro 4.8 right?)

ADD: Nah grabbing the latest commit didnt help the wrong defined path. Also I saw that most stuff is set inside the "make" file itself already (the ARCH and PATH etc). This does get read from the make file if I run "make <command>" inside the kernel folder right?

I'm not really familiar with make itself. There is a binary/script in the system which is called make right? And this one reads the "make" file inside the folder you are trying to build? Because otherwise I'd have to execute "./make <command>" instead or?
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3160325]zroice[/MENTION]

./make is my own build script and not related with make [...], you can try do delete all files inside the kernel folder (but don't delete hidden files) and execute git reset --hard
[Galaxy Note 3 Android Development] zroice:
ahh I see. (i just read about make myself.. it grabs the Makefile and executes that one, right?)

The "wrong" path definitions are inside the Makefile then.. (is it ok to edit this one or should I rather set the variables in terminal before building? (it gives problems with pulling if I edit files right?)

ADD: The mrproper worked fine now... lets see. But I'm sure I have everything set up right now.. just need to edit the paths or set variables right as you explained and everything should work fine.

Final question for today: Whats the best way to make changes to the kernel but still beeing able to pull last commits from you? I'd just copy stuff to a 2nd folder and edit there to have my own "custom" one. (when I actually find anything useful to contribute I'll let you know off course lol..) But to test things out etc without breaking git pull?

Or should I just make a git account and fork?

ADD2: ok I have one more question .. but thats really the final one lol... do we have the "source" for the ramdisk as well? Like for the init binary and the other binaries in /sbin etc? (I'm pretty sure theres more knox stuff left inside). Plus inside the "system_server" process/binary. (but this one is not kernel but system/bin)

P.S: Actually my biggest failure was to not find the toolchain binaries on the website of linaro.org lol... I had downloaded the source over and over and was wondering where the "bin" folder is lol...

---

Unrelated to the kernel building: Does this modemst1 corruption show itself the same way to you wootever? Because people talk about bootloops, when its not really a bootloop to me (I get inside android, but then the phone reboots itself after a while and doesnt show battery icon or start any apps) or do you get "real" bootloops?
[Galaxy Note 3 Android Development] Wootever:
You can also edit the makefile with a proper path for the toolchain.

If you want to update your modified source you can use 'git remote update' and cherry-pick all new changes.

git cherry-pick commit..commit

older -> newer commits

A git account is always appreciated if you like to share your changes/additions.

Edit:

Everything on the ramdisk that is not editable is closedsource unfortunately.

as of recently it already crashes on the bootlogo, probably because of changes on the kernel source and ramdisk.
[Galaxy Note 3 Android Development] zroice:
I R Baboon ... I got some errors again when trying to build or make config, but I think I know my mistake now... I need to have the full kernel sources from samsung first and then patch them with your changes? Sorry if this should have been obvious... I'm just downloading the kernel files.. I just copy them over your files without overwriting anything then (so that I keep the changed files), right?

The error im getting is missing the "sys" folder inside the kernel directory. (and probably more but its already stopping at the sys/types.h not found error)
[Galaxy Note 3 Android Development] zroice:
Gaawd. opensource.samsung.com download takin ages. Are there any mirrors?

---

I have to admit I "cheated" on your kernel and had faux 004 installed for a while....

But now I reinstalled this baby here and this thing really is the best out there lol! I didnt tweak anything (cleared synapse and fauxclock settings and rebooted to have default config... well ok i set governor to intellidemand and turned on intelliplug and turned off intellithermal for the benchmark)... and I got 38500!

Best score so far. And I got a few resource hogs installed that could slow things down a bit: system-dpi@320, Xposed and Xprivacy plus customized the systemui with wanam, xblast and xuimod (custom animations n stuff)... yet gettin 38500! (and this was the first time the test ran after clearing dalvik and application cache as well)

you should call it "roadrunner" kernel or smth :P ... "meep meep"

Best score before that was 37500. (both with faux123 and older version of your kernel)

--

Really great job! (btw. is the gpu overclocked to 450mhz or is that default? I think in the older versions it was only 400mhz or am I wrong?)

...

Rebuilding the dalvik cache also seems faster with your kernel.

UPDATE to the kernel building: Well I was wrong .. not missing the kernel sources, but missed some packages.... but I'm gettin there.. slowly but steady hehe.

one also needs "build-essential", "qt4-dev-tools", "qt4-qmake", libqt4-dev", "lib32ncurses5dev"

Can run menuconfig and xconfig now finally.. I'm gettin there!
[Galaxy Note 3 Android Development] PiPoLiNiO:
Download link is bad...

Wysłane z mojego SM-N9005 przy użyciu Tapatalka
[Galaxy Note 3 Android Development] mateenf:
Cant download. It just fails... can anyone please upload the latest one here...
[Galaxy Note 3 Android Development] zroice:
Gonna load the new kernel in a few (didnt get to compile yet, but maybe later today if I finally find enough time)..

One thing I wonder:

In the 04 version if I remember correctly, you could also change the MDNIE-lite settings inside faux clock, but this is only possible with synapse now? Or was it tricksermod that also supported this?

And b: In the 04 version there were some MDNIE-lite tweaks preapplied to the white color (and some more options in synapse, like dynamic gamma curve). Any reason that got removed?

And what were the tweaks again? I remember with your tweaks the white color actually looked better, but I forgot which settings were set.

--

But anyway: Is there one kernel tweaking tool that includes all the settings? I would rather just use one to make sure things dont get messy.

(or how do I set MDNIE settings in terminal / with a script? I'd actually like to get rid of synapse and just use fauxclock if thats alright..)
[Galaxy Note 3 Android Development] m.4_ts@yahoo.com:
can you include boeffla sound enhancement? it would be the greatest.. thanks dev
[Galaxy Note 3 Android Development] zroice:
[MENTION=4709667]Wootever[/MENTION]: I deleted all old files and reloaded the sources from your git but now the kernel config file is gone. Can you please re-add it or pm it to me or smth? I'm still noob and some starting point for the config is needed hehe. (I guess you already configured everything to the best settings anyway, but I would like to compare the default and your config to see what stuff actually makes actually sense to configure in the config)

And btw: I'm still on 7b - but I did not have a single boot loop or reboot yet, maybe it's fixed for good...

---------- Post added at 03:51 AM ---------- Previous post was at 03:02 AM ----------

Dont forget to mention this baby also has init.d support now!
[Galaxy Note 3 Android Development] jrrevoltar:
I am using Sweet Rom v5, would this kernel be compatible with it? Probably yes, but just making sure..
[Galaxy Note 3 Android Development] samaxen:
yes
[Galaxy Note 3 Android Development] Wootever:
[MENTION=4493663]PiPoLiNiO[/MENTION] and [MENTION=2124694]mateenf[/MENTION]

Download should work again.

I reworked the control interface for more clarity, it is not compatible with fauxclock for now.

I thought it would be a good idea to leave everything "stock" and let the user decide, but it is probably more pleasant to get recommended settings "out of the box".

echo 255 240 255 > /sys/class/mdnie/mdnie/control_white

(it reduces the green color for a warmer white point)

Take a look here: mdnie lite control: add control interface it explains the sysfs interface.

Is there something missing you would like to see on synapse?
[Galaxy Note 3 Android Development] zroice:
Thanks again!

Well fauxclock has a few more options (while missing some others) - but I guess those are not really important to set or are more counterproductive than that they help?

(like the "Power Suspend" option and the C-States etc. in fauxclock - but ok if I find out how to set the stuff in terminal or on boot, then I dont really need faux anymore.

I just wanted to have one tool-app which controls all the settings instead of two.. but if you say its better to keep synapse, then I can just keep that off course.

---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------

Thanks again!

Well fauxclock has a few more options (while missing some others) - but I guess those are not really important to set or are more counterproductive than that they help?

(like the "Power Suspend" option and the C-States etc. in fauxclock - but ok if I find out how to set the stuff in terminal or on boot, then I dont really need faux anymore.

I just wanted to have one tool-app which controls all the settings instead of two.. but if you say its better to keep synapse, then I can just keep that off course.

---

The Synapse options are configured with those json files in /res?
[Galaxy Note 3 Android Development] Wootever:
Powersuspend and idle-states will be enabled with a ramdisk script on boot-up.

I'm planning to get synapse as full-value alternative to other configuration programs, but of course you are free to use any other program you like.

(also synapse is not installed as system application, so you can uninstall it easily)

Yes.
[Galaxy Note 3 Android Development] Pianoman144:
[MENTION=4709667]Wootever[/MENTION] is your kernel compatible with a 4.4.2 Rom (Official or custom) and do you know if fauxkernel is compatible too? Thanks

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] samaxen:
No, Samsung has not released sources of 4.4.2 yet. Unless they release none of the developers can make kitkat compatible kernel
[Galaxy Note 3 Android Development] demmo81:
I just installed it with same settings no changes this is my result which is less than the stock one any advice guys :) thanks for the kernel it's smooth
[Galaxy Note 3 Android Development] turilo:
Has camera FC issue been fixed for the n900t and n900w8 devices with this kernel?
[Galaxy Note 3 Android Development] zroice:
you doin it 'rong!

I get 38000 to 38500 with following settings:

Intellidemand governor, 2.5ghz. For benchmarking, deactivate intellithermal or up the temperatures, otherwise you might get throtteling, which could be the reason for your low score.
[Galaxy Note 3 Android Development] Wootever:
Changelog:

- release 08
[Kernel]
* added small tweaks to ramdisk
* added various fixes
* updated linux to version 3.4.76 (thanks to imoseyon)
* updated mdnie lite control to version 1.1

[Synapse]
* added function to export mdnie settings to init.d script (use your favorite settings without synapse)
* added option to copy color profile from existing mdnie profile (Standard, Natural, Movie)
* added settings for powersuspend and dynamic fsync
* added various livelabel elements (thanks to AndreiLux)
* readded gamma curve settings

Download:

(hlte-custom-08) [N9005]​
[Galaxy Note 3 Android Development] samaxen:
Working fine:good:

Thanks
[Galaxy Note 3 Android Development] sphameed:
working great under volting -50mv

omega 6.0 rom

thanks man
[Galaxy Note 3 Android Development] sphameed:
View attachment 2521941

With omega v6.0 kernel ver 8 nice result
[Galaxy Note 3 Android Development] zroice:
grmpf, just updated to ver 8 and those damn bootloops are back.... have to run the fix to get booting again, but only lasts for one time.

Reproduceable it seems. If I find a fix ill let ya know..

UPDATE: So it seems that clearing modemst1 and modemst2 do only a temporary fix.

What I did to get this fixed was to restore full efs backup (including modemst1 and modemst2) made by twrp.

So far it seems stable again. Clearing modemst1 and modemst2 alone would only let me boot once and then fail again.

UPDATE2: False alert .. after booting 2 times im back to bootloop...

UPDATE3: so after a couple of efs restores later it seems stable now... really weird behaviour with this bootloop thingy. I am guessing you need to have the "right" efs backup to get rid of it. Modemst1 and Modemst2 clear alone dont fix it for good.

UPDATE4: sigh still not fully fixed - with 7c everything was so stable, then I flashed 8 and hell broke loose again...so annoying,

But its not the kernels fault, tried flashing back 7c, and that didnt help... trying to investigate finally whats the cause.

wtf is this... really weird
[Galaxy Note 3 Android Development] samaxen:
For me it works perfect no reboots and great battery life

[MENTION=4709667]Wootever[/MENTION] 4.4.2 Kit Kat sources are out hopefully you can bring some of your magic to that :good::laugh:

http://opensource.samsung.com/
[Galaxy Note 3 Android Development] zroice:
Yea its not the kernel itself who's causing this bullcrap behavior.

I still use TWRP but I'm gonna switch over to cwm to see if it helps.

I managed to get everything working again by restoring an old backup.

It seems the problem lies either on data or system partition, because simple efs restore, kernel switching and so on did not help at all. Only clearing modemst1 works as a temporary fix if this behaviour occurs, but no matter what I couldnt get things to fully work again once the error occured (well restoring a working backup helps it seems, but thats not a real fix).

Now I got everything working again with the latest version as well.. but this was the final nail in the coffin for TWRP for me... (until things are definitely fixed..)
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3160325]zroice[/MENTION]

If you interested, i have uploaded the new kitkat source: samsung source N9005 NA6

I haven't much added yet (only support for gcc 4.8+ toolchain) but it will build without errors or warnings.

Step-by-step guide for kernel building
[Galaxy Note 3 Android Development] zroice:
thx but Ill stay on 4.3 for now, dont wanna upgrade bootloader (yet) etc.

But this damned bootloop issue is back again...... =(

ARGH... but Ill keep trying till I find out the source of the problem..

(but this time these are real bootloops, not missing statusbar icons only etc...)

---

OK so I restored my oldest backup which always worked...then I restored data and system from latest backup and everything is working fine, but with old kernel (faux 004).

Ill install CWM now after confirming everything is working adn then flash with that.. hopefully this avoids the issues =/..