yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] zroice:
sigh - even with CWM I get bootloop now.. WTF is this sh!t .. got everything working and rebooted 10 times to make sure everything was working.. then flashed cwm and made a backup, then flashed the kernel v8... and 2 reboots later it loops again......... ARGHHHH (just mad at this happening lol.. not again awwwww)

---

Final update: Had to flash the bootloop fix script again from cwm this time, and now its finally stable again......no more twrp for me *sniff*, actually liked it..
[Galaxy Note 3 Android Development] empat:
I suppose you have seen that, and sorry if it's stupid, but did you tried disabling the "always allow searching" , under WiFi /advanced settings? For me it was the only solution for the bootloops, and solved it completely.
[Galaxy Note 3 Android Development] zroice:
Disabled that really early on, but thanks for reminding.

---

I really can't fully tell whats causing it... the error lies inside modemst1 (at least partially) because clearing that with the bootloop fix script makes my device boot up fine every time (at least once). But then after a few reboots (usually one or two) the phone either loops at the boot animation or it boots up inside android and phone is unresponsive and reboots after a while.

But the trigger for this happening does seem to be on other partitions...?! Or its TWRP restore - messing up backups randomly or smth.. really hard to tell. I couldnt reproduce the problem reliably, and also not sure what finally got rid of it. (if I finally got rid of it..)

It started when I flashed the v8 of the Custom N3 kernel with TWRP. Didnt wipe anything, no cache or anything. Then after two reboots I had that boot animation loop... but it does not happen every time. Flashed the other kernel versions without problems the same way.

---

and back to looping.....(after I booted into cwm and just rebooted system without doing anything inside cwm).....RAAAAAGE
[Galaxy Note 3 Android Development] Wootever:
Currently i'm only affected when i reboot into recovery and flash the kernel zip package.

However i never noticed this issue when i flash the kernel on android and reboot.

dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

(that's how i mostly test my kernel builds)
[Galaxy Note 3 Android Development] zroice:
gonna see of that helps.

Do you / did you get the loops right away or after a couple of restarts like me? Thats whats so weird about it. When I clear the modemst1 or flash a kernel it boots 100% of the time, but on 2nd or 3rd reboot usually it starts with the loops...

EDIT: I should not write this, because so far whenever I said that its working, the next reboot it would loop again lol ... but switching to CWM does seem to have helped a bit... I had to run the bootloop fix here too, but now I finally managed to get everything working without reboots or weird lags.

---

What I'm starting to wonder after all this trouble. What are those extra partitions that are not part of odin packages used for?

There are many (backed them all up at one point with dd to file):

dbi, ddr, fsc, fsg, modemst1, modemst2, pad, backup (all partition names)...

And whether they are created from the other partitions data (like from modem and efs) or if they should be backed up as well and handled like the efs partition maybe? (maybe corruption in these is causing all the bootloop trouble...? but even if not.. wtf are all those pesky partitions for..?)

It seems some of them are related to the rmt_storage binary like Wootever already pointed out - the name could mean "remote_storage" for example - or other ideas what it could be?

rmt_storage definitely also works with the fsg and fsc partitions apart from modemst1 and 2.

Check this:

/rmt_storage( 442): No EBR found
/rmt_storage( 442): Error (-1) parsing MBR partitions
/rmt_storage( 442): Registering modemst1: 0x4a /boot/modem_fs1
/rmt_storage( 442): Registering modemst2: 0x4b /boot/modem_fs2
/rmt_storage( 442): Registering fsg: 0x58 /boot/modem_fsg
/rmt_storage( 442): Registering ssd: 0x5d ssd
/rmt_storage( 442): Registering fsc: 0xff /boot/modem_fsc
/rmt_storage( 442): 5 GPT partitions found

and maybe "/rmt_storage( 442): Error (-1) parsing MBR partitions" is the problem...?!
[Galaxy Note 3 Android Development] Wootever:
I made a (unofficial) twrp build compatible with kitkat:

* updated kernel source to version 4.4.2

* removed corruption fix

Download:

(hlte-twrp-kitkat)​
[Galaxy Note 3 Android Development] zroice:
So I compared the checksums of all my efs backups, and they all differ..... both for efs itself but also for the additional partitions modemst1 and modemst2 (as well as fsg and backup).

From searching around I read that modemst1 and modemst2 are actually important to back up because they contain additional info (IMEI alone is not enough). And FSG plus BACKUP partitions are actually copies of these two partitions.

Weird thing though is that none of these partitions have the same checksum and diff reports also that they are different - i tried all combinations.

----

So what is it? Unfortunately I only have a "real" efs backup made when I got my device new, I do have modemst1 and modemst2 etc backups but they were all taken after I already had custom kernel installed (made with TWRP backup..).

But for now my problems seem to be fixed again... no more bootloops.
[Galaxy Note 3 Android Development] Pianoman144:
Is that a twrp recovery or a kernel flashable only with twrp? Sry xD

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] turilo:
Yes a 4.4.2 kit kat compatible twrp as he mentioned. Flash via Odin
[Galaxy Note 3 Android Development] mateenf:
Can this be flashed via cwm?
[Galaxy Note 3 Android Development] zroice:
this one needs 4.4 or does it work on 4.3 still?

And does that mean you updated bootloader and are on 4.4 now? (aka no more updates for the 4.3 version?)
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3160325]zroice[/MENTION]

Yes, i'm also working on a test version for version 4.4 (doesn't include much stuff yet - mdnie control - init.d - selinux permissive and basic synapse settings)

Edit:

The recovery does not work on 4.3 bootloader.

Changelog:

- release 01
* [based on samsung source NA6 kitkat]
* added mdnie control interface
* added init.d support
* added initial synapse screen settings
* build with linaro toolchain (gcc 4.8.3)
* disabled securestorage
* disabled samsung kernel debug
* removed knox container setup
* set selinux to permissive

Download:

(hlte-custom-01-kitkat) [N9005]​
[Galaxy Note 3 Android Development] A.N.Droid:
no, it does not.

stuck at the "recovery booting" screen.

had to pull the battery to get into download mode.

i flashed the original twrp with odin and everything is ok again.

was a bit scared first, but no big deal in the end.
[Galaxy Note 3 Android Development] Wootever:
Only with odin, i will later add a flashable zip package.

[MENTION=3160325]zroice[/MENTION]

I'm very satisfied with the kitkat update and so far i didn't encounter the corruption issue.
[Galaxy Note 3 Android Development] mateenf:
Oc/UC available in new kitkat??
[Galaxy Note 3 Android Development] Okarina26:
install it then you will see it...:o
[Galaxy Note 3 Android Development] zetlorf:
Has anybody tried the new kernel for kitkat? Everything is working?
[Galaxy Note 3 Android Development] micky387:
Thanks man. Working on mobile odin? Or pc only?

Envoyé de mon SM-N9005 en utilisant Tapatalk
[Galaxy Note 3 Android Development] effry:
the kitkat kernel works good but doesn't have voltage control (tried with trickster mod) enabled. why?
[Galaxy Note 3 Android Development] Pianoman144:
No.. I have flashed the kernel

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] meawww:
Device freeze time to time and wifi weak signal.
[Galaxy Note 3 Android Development] zroice:
hehe thanks... the reason why I want to stay on 4.3 for now is that I already spent soooo much time on setting everything up, and I'm sure not all my modifications (many xposed modules, etc) might not fully work yet on kitkat I'm thinking.

So I'll give it more time.

Are there any real benefits from Kitkat? I'm using custom launchers anyway with custom theme etc. so the new interface and the "less ugly" Touchwiz do not really interest me.

What I'm considering though: Flashing ProBAM 4.4.2 - now that CM even got multiwindow support - only thing I'd be missing out on would be the spen enhancements of samsung. (but not using the pen much anyway.. )

Any more arguments for TW over AOSP base expecpt spen funtionalities. (like penwindow, and scrapbook etc - which I never used so far lol..)?
[Galaxy Note 3 Android Development] Okarina26:
this is happening with all customroms on my Note 3...:crying:
[Galaxy Note 3 Android Development] AuxXxilium:
no issue with stock na6 and this kernel
[Galaxy Note 3 Android Development] Okarina26:
i think i will go back to stock for a while...:good:
[Galaxy Note 3 Android Development] Drizzy xS:
Does anyone have any nice colour settings for synapse my note 3 came with weird out washed out yellowy whites and I want them to be more bluey..
[Galaxy Note 3 Android Development] zetlorf:
Also i flashed this kernel. Very good! No problems so far... Thanks!
[Galaxy Note 3 Android Development] sebastan:
Is it possible to add 2-way call recording to KK kernel? Is it a big problem?
[Galaxy Note 3 Android Development] Wootever:
Changelog:

- release 02a
* added fauxsound
* added small ramdisk tweaks
* fixed fauxsound compatibility with kitkat

- release 02
* added bfq/fiops/sio scheduler
* added dynamic and asynchronous fsync (by faux123)
* added intelli-demand cpu governor 5.0 (by faux123)
* added intelli-thermal driver (by faux123)
* added intelli-plug driver (by faux123)
* added powersuspend driver (by faux123)
* added optimized arm algorithm and routines
* added advanced tcp congestion control (westwood)
* added ramconsole (last_kmsg)
* added various slab/slob/slub updates and fixes
* added various kernel scheduler updates and fixes
* added various filesystem/lib updates and fixes
* added various small ramdisk tweaks
* fixed intelli-thermal compatibility with kitkat
* readded synapse controls for cpu/storage/thermal and misc

Download:

(hlte-custom-02a-kitkat) [N9005]​
[Galaxy Note 3 Android Development] civato:
A qeustion. Where can I find your kitkat source. I can't find it anymore on github. I want to build from your source but change some things.
[Galaxy Note 3 Android Development] Jeshter2000:
Are these setting available through Faux Apps?
[Galaxy Note 3 Android Development] raychak:
Any chance that there will be cm11 version Custom N3 kernel available soon? :)
[Galaxy Note 3 Android Development] antt00:
Faux sound control cannot be saved when using trickster. Is this an issue with the kernel or the app. Thanks.
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3986004]civato[/MENTION]

Kitkat source is still a heavy work in progress, as soon as i have polished it enough i will upload it to my git repository.

[MENTION=2879028]Jeshter2000[/MENTION]

FauxSound is fully compatible (also no issue with write protection), FauxClock will only list settings that are currently implemented.

[MENTION=238877]raychak[/MENTION]

As soon as they update compatibility with kitkat bootloader i will take a first look and will decide then if i stay with cyanogenmod. (Only support for the system that i actually use.)

[MENTION=556260]antt00[/MENTION]

It's an issue with Trickster. Fauxsound uses a write protection that has to disabled first.

echo 0 > /sys/kernel/sound_control_3/gpl_sound_control_locked

Change your settings and re-enable the write protection or it will get altered by the system.
[Galaxy Note 3 Android Development] genius.lizard2:
[MENTION=4709667]Wootever[/MENTION]

Bump :)
[Galaxy Note 3 Android Development] civato:
Ok thank you, I fully understand.

I noticed myself there are a lot of changes in kitkat source.

Thanks in advance.

Side note:

I took a look at your ramdisk of the kitkat kernel and the cpu idle stuff in the settings.sh isn't correct anymore for the kitkat rom .

Here is the kitkat "init.qcom.post_boot.sh" code.

delete the .txt
[Galaxy Note 3 Android Development] PiPoLiNiO:
Please, correct link 8 version!

Maybe someone put the file on a server?

Wysłane z mojego SM-N9005 przy użyciu Tapatalka
[Galaxy Note 3 Android Development] mateenf:
[MENTION=4709667]Wootever[/MENTION] any chance to add OC/UV support to kitkat?
[Galaxy Note 3 Android Development] Silverbolt:
Version 2a changes me serial number under Settings, Status. I had this issue with lean kernel on 4.3 but this is the first time with this kernel. Is there a reason why?

It concerns me that it happens because none of your previous kernels have done this.

I have gone back to Civs Engine 1.1 and my serial has returned.
[Galaxy Note 3 Android Development] vertigone:
NO Call Recording

Hi flashaolic. I am sorry for the bad news but SAMSUNG not implemented call recording in 4.4.2 KK.

Most of developers of rec call he said that: NO recording call software after the upgrade to KK.

SHAME samsung.:(:confused:

I need call recording for work, dammn...;)

I wait the call recording in the next update.:fingers-crossed:
[Galaxy Note 3 Android Development] :
I think CM is working on the compatibility. Saw something about a NA6 commit being submitted.

If SPen features will be crucial in your decision of choosing between CM11 and stock , there are apps to add the missing functionality.

Notes, ScreenWrite, Sketchbook, handwriting recognition keyboard, detection of spen attach, detach, Tasker warning if spen out for more than predefined period etc.

Tell me if you want the list.
[Galaxy Note 3 Android Development] Yank555:
It's off-topic, but you caught my attention ;)

The only thing I miss is the screenshot with ability to make annotations, do you know of any such app, pay app ?

Thanx, JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.8-beta3 kernel.
[Galaxy Note 3 Android Development] Wootever:
Small update:

Changelog:

- release 02b
* added cpu overclock (up to 2.5ghz)
* added extended led controls (by yank555.lu)
* added synapse gpu control
* fixed cpu idle settings (thx to civato)
* readded synapse led controls

Download:

(hlte-custom-02b-kitkat) [N9005]​
[Galaxy Note 3 Android Development] :
Try anote

https://play.google.com/store/apps/details?id=com.plumillonforge.android.ano

You can even highlight selected parts :o

Free one does everything, :D I bought it just to support the developer.
[Galaxy Note 3 Android Development] samaxen:
Working fine:good:
[Galaxy Note 3 Android Development] samaxen:
Min frequency keeps on jumping to 1.1 ghz even when I set it to 300 mhz in trickster mod
[Galaxy Note 3 Android Development] Wootever:
[MENTION=4107754]samaxen[/MENTION]

This is caused by Samsung's new touchboost implementation, instead of increasing the current frequency it will set a higher minimum frequency.

Mpdecision has a similar behavior, i will probably add a min freq lock as workaround.
[Galaxy Note 3 Android Development] civato:
test report 02b version.

Changing to simple_ondemand gpu governor results in reboot (I have the same problem on stock kernel so there only 2 governors available, performance and msm-adreno-tz)

Governors need linking.

Changing the cpu governor on cpu0 what synapse & other control apps do, does result only changing the governor on cpu0.

I fixed it with the governor linking fix of imoseyon from JB. look at my github or download cpufreq.c (remove .txt) and use that when compiling kernel)
[Galaxy Note 3 Android Development] civato:
That question has been answered a few posts earlier.
[Galaxy Note 3 Android Development] Silverbolt:
Version 2b also changes the serial number. However I have noticed it is the same or similar number.

I don't believe this should happen at all. Does anyone have an explanation?

It doesn't happen with Civ 1.1.
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3986004]civato[/MENTION]

Thanks, didn't check this because i'm using interactive as default.

I also pushed my current kitkat source to git repository, keep in mind that it is not final and might get rebased at any time.

Source
[Galaxy Note 3 Android Development] civato:
Thanks. This way I can learn more about the kernel changes. Thanks again.
[Galaxy Note 3 Android Development] Wootever:
I'm guessing soundcontrol will be next addition for synapse. ;)
[Galaxy Note 3 Android Development] Wootever:
Another update:

Changelog:

- release 03
* added cortex a15 and neon optimization flags
* added cpu overclock up to 2.7ghz
* added various fixes for arm/neon, ext4, futex and selinux
* fixed governor settings only applied to cpu0
* removed unused ramdisk services and outdated sysfs links
* updated synapse to version 0.18

Download:

(hlte-custom-03-kitkat) [N9005]​
[Galaxy Note 3 Android Development] sille:
Does synapse work as good as fauxclock?

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] LaZer713:
Hi thanks for the kernel, how can i increase the CPU clock? it keeps getting the default.thanks.
[Galaxy Note 3 Android Development] Silverbolt:
Release 03 also changed my serial number under Settings - General - About Device - Status - Serial Number.

Civ Engine 1.3 did not.

Am I the only one this is happening to or am I just the only one who cares?
[Galaxy Note 3 Android Development] Jeshter2000:
Does someone have to optimal settings for Display?
[Galaxy Note 3 Android Development] souljasteve84:
Is there anyway to implement smartassv2 Governor?
[Galaxy Note 3 Android Development] Rajada:
hi

In Faux Sound the "Analog Output Gain Controls" seem doesn't work. It's a related bug, or a new one?
[Galaxy Note 3 Android Development] hong25:
Latest custom kernel 03 keep on restart phone, set cpu to max don't know why it happen to my phone on android 4.4.2
[Galaxy Note 3 Android Development] Drizzy xS:
I'd love to know this too
[Galaxy Note 3 Android Development] Wootever:
As far as i can tell this is only a cosmetic issue the actual serial is stored at /efs/FactoryAPP/serial_no, but i will check why it is different now.

I guess you mean setting max frequency to 2,7ghz is unstable for your device, then you need to lower it to max 2,5ghz or 2,3ghz.

Unfortunately this is intended, the power amp registers need to be accessible by the system, a locked control override (as used in fauxsound and trickster) would cause sound distortion.

It would be magnificent if someone could actually do a proper display calibration and share their results. :)

(that was my primary reason for the mdnie control)
[Galaxy Note 3 Android Development] Jamal Ahmed:
Man!!!

Thanks a million for this kernel! I can't express how grateful I am xD ever since I got my Note 3 I had a huge disappointment over how low the volume in 24-0 it vinyl tracks was. Even the volume cranked to full was less than half of a 320 kbps song. But the faux sound in this kernel really blew the hell out of me :D

There was nooo other alternative and then you appeared beautifully with a kernel with faux sound xD thanks man!
[Galaxy Note 3 Android Development] Wootever:
Synapse soundcontrol is almost finished:
[Galaxy Note 3 Android Development] Pianoman144:
Are you able to implement the CPU Undervolting? Or maybe the GPU stuff?

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] sille:
[MENTION=4709667]Wootever[/MENTION]

hey flashed your kernel and used fauxclock instead of synapse... when i now take a look on the CPU settings and dont change the Minimum Freq i can see that the frequency jumps wildly from 300 to 1GHz or even higher or back to 300... is this an error with fauxclock or is this a problem with your kernel?
[Galaxy Note 3 Android Development] flow78:
This is new samsung's touchboost implementation. No problem with fauxclock or this kernel
[Galaxy Note 3 Android Development] Yank555:
That is mpdecision doing its work, mpdecision = Qualcomm's CPU driver daemon which they made as a binary and didn't include in the kernel so they can keep it closed source.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu CM11 v0.8-beta3 kernel.
[Galaxy Note 3 Android Development] allenjthomsen:
Got 4.4.2 for n9005 to boot with this rom on my tmobile note 3 but it locks uo on me any ideas how to stop it from locking up on me and fcing under security settings
[Galaxy Note 3 Android Development] testmonkey1:
Hello guys. Can someone report performance/battery usage with 4.4 KitKat?
[Galaxy Note 3 Android Development] mirek190:
From yesterday I got 3 radom reboots on this kernel.

On stock never happened.
[Galaxy Note 3 Android Development] samaxen:
[MENTION=4709667]Wootever[/MENTION]

Is their init.d support on your Kitkat support like your JB?

Guys please check noop scheduler set at 256 KB read ahead, my clock speeds remain 300-2.2 GHZ (It doesn't change/jumps)
[Galaxy Note 3 Android Development] Jamal Ahmed:
Same here
[Galaxy Note 3 Android Development] Pianoman144:
I got only one reboot a day xD it have to be the kernel. Checked with the stock NA6 and there is no reboot

Gesendet von meinem SM-N9005
[Galaxy Note 3 Android Development] antt00:
You guys know all these talks about reboots help nothing. Provide logs or at very least tell what setting or rom you using.
[Galaxy Note 3 Android Development] mirek190:
How to provide logs ?

I just changed schedule to on demand and row.

And was unable.

Now after 3 reobots settings back to default and now is working fine so far 12 h without restart.
[Galaxy Note 3 Android Development] LaZer713:
i don't have any reboots, working good since release.
[Galaxy Note 3 Android Development] Jamal Ahmed:
I only had one reboot since yesterday. I can't provide log as I've rebooted my phone multiple times after it. Also, I'm on stock rooted kitkat if that helps :)
[Galaxy Note 3 Android Development] Wootever:
[MENTION=4703406]Jamal Ahmed[/MENTION]

I think this reboot issue is caused by unstable overclocking frequency on most devices (=2.7ghz) in combination with the non-functioning samsung cpufreq limiter, even if limited to 2ghz it will jump randomly to the max freq of 2.7ghz.
[Galaxy Note 3 Android Development] allenjthomsen:
Is there anyway u coild fix the issue so it doesnt jump around
[Galaxy Note 3 Android Development] Wootever:
[MENTION=3198335]allenjthomsen[/MENTION]

Yes, i modified the samsung cpufreq limiter and added new sysfs controls. It will definitely keep the frequency that was set (for both min and max frequency), but this will only work on synapse. Every other kernel tweaker (or system application) can't change frequencies anymore.
[Galaxy Note 3 Android Development] allenjthomsen:
Sweet cause as soon as i can grt my hands on the newest buold ill have 4.4.2 running perfectly without a bootloader on the tmobile note 3
[Galaxy Note 3 Android Development] testmonkey1:
Wait I'm a little confused. Are the reboots already fixed or they will be in the next release?
[Galaxy Note 3 Android Development] allenjthomsen:
Sorry i have a tmobile note 3 and i believe that he is saying he is making another update to the kernel
[Galaxy Note 3 Android Development] allenjthomsen:
Thanks to him i wouldve never got rhis far on my tmobile note 3
[Galaxy Note 3 Android Development] Wootever:
If you got troubled with reboot issues please take a moment to provide some system logs so i can investigate further:

Bug report

Download SysLog and grant it Superuser access.

Reproduce the error (run benchmark, recording a video, etc) once you are finished go back to SysLog and click on Take Log.

Logs will get saved at /sdcard/SysLog - copy the *.zip package and attach it to your post.

This will also include the previous kernel log, after a crash you can click on Take Log too.
[Galaxy Note 3 Android Development] AxAtAx:
What your saying is there is going to be a tmo 4.4.2 kitkat kernel?
[Galaxy Note 3 Android Development] allenjthomsen:
Possibly dont know yet
[Galaxy Note 3 Android Development] AxAtAx:
So, with the kernel provided here, it booted your 4.4 on the tmo? If so, I am going to try this later, I can fix the rest....I just want it to boot, and when it does, its on, I can handle it from there....

Thanks for the info.