yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] jcadduono:
Proximity sensor shouldn't be using any battery unless an app wakes it like calling or diagnostics.

To be clear, the proximity sensor is not broken in 6.6.0, it merely has the calibration offset being read as 0 instead of ~162, causing it to not switch between true and false for android applications.
[Galaxy Note 3 Original Android Development] 6h0st:
Proximity sensor is working again on 6.6.1. Success!

Thank you.!
[Galaxy Note 3 Original Android Development] wild wadi:
Confirmed: Proximity working again in 6.6.1. Thanks
[Galaxy Note 3 Original Android Development] orbital_71:
Are we good to go wif ur twrp? Just saw it in your folder.
[Galaxy Note 3 Original Android Development] kopitalk:
Man.. you're SICK! f2fs is working smoothly now! Slick move! :cool:
[Galaxy Note 3 Original Android Development] AM.8:
Should we flash the team twrp recovery from OP??

Thanks

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] 6h0st:
RAM usage is way better with 6.6.1. Don't know exactly why, but it is.
[Galaxy Note 3 Original Android Development] tamer7:
Any interest to add a Touch Wake implementation, with configurable timeout since screen auto-off, as was with the (now discontinued) AEL kernel 7.12 ?
[Galaxy Note 3 Original Android Development] TeddyKhalifa:
Are there any proven significant improvement by converting to f2fs? If yes, which ones? Lot of people do that so... There have to be something... Google didn't really help me
[Galaxy Note 3 Original Android Development] kopitalk:
Faster IO read/write, which means to the least, smoother UI.
[Galaxy Note 3 Original Android Development] TeddyKhalifa:
Does it have negative points too? I mean everything has pros and cons
[Galaxy Note 3 Original Android Development] acme1974:
f2fs

when i have make the work of developer...this is extractTarFork() process ended with error=255
[Galaxy Note 3 Original Android Development] shiverz07:
Flashed it. Working 100% MTP and USB Mounting!:fingers-crossed::good::highfive::D
[Galaxy Note 3 Original Android Development] kopitalk:
Not that I know of.. troublesome initial set up maybe? I mean by default everything is in ext4 and you have to manually convert each partition to f2fs in recovery. [MENTION=5672995]jcadduono[/MENTION] btw you missed out one important step which is to backup the /sdcard content to external storage as formatting /data will wipe internal memory as well. Otherwise it's gonna be a perfect moment to scream in agony too for some users.

Can you explain more? What were you trying to do?
[Galaxy Note 3 Original Android Development] acme1974:
when finish to restore to f2fs to 92 % this wrote....extractTarFork() process ended with error=255

the procedure of backup and etcc. is exact but to the end...wrong error extractTarFork() process ended with error=255
[Galaxy Note 3 Original Android Development] kopitalk:
Which partition you're trying to restore when that error happened?
[Galaxy Note 3 Original Android Development] acme1974:
F2fs

Inviato dal mio SM-N9005 utilizzando Tapatalk

---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------

Backup system and data than wipe system and data with f2fs than setting -rm etc and restore. ..but problem to 92 %

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Original Android Development] jcadduono:
Did you disable MTP and are you using gold TWRP idlekernel edition from thread first post? You need to make the backup in yellow twrp as well, you can't restore backups made in blue twrp. There is a fs bug in blue twrp that causes invalid symlinks in backups that makes them impossible to restore with rm -rf mode. If you made the backup with yellow twrp and it still won't restore please find copy log to SD option in twrp and send me recovery.log so I can look into it.

You make a good point OK added a nice red warning message to the top of the post. I keep thinking internal storage is included in data backups. ><
[Galaxy Note 3 Original Android Development] acme1974:
But is big full. .

In ext 4 ....how?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Original Android Development] Tombias:
I'll wait for version 6.6.6 ?
[Galaxy Note 3 Original Android Development] acme1974:
Ok
[Galaxy Note 3 Original Android Development] Segamalaga:
What?
[Galaxy Note 3 Original Android Development] jcadduono:
OK that recovery log doesn't include the error...need the log after the error. But as you said your system partition looks to be full and maybe isn't leaving enough space to write all contents back. You need to free up some space and on /system that can be complicated. You can probably use file manager to delete some apks from /system/csc subdirectories of carriers you don't use. Then back it up and try again. Still, confusing because I would imagine ext4 would give less space than f2fs. :S

Surround your log in code tags or delete it please...

I should add that I don't mean any offense but if English isn't your native language, it might be easier to write your questions properly and detailed in your native language and then run them through Google translate. It might be terrible for converting English to other languages but it works amazing for other languages to English.
[Galaxy Note 3 Original Android Development] Lyokacanthrope:
http://review.cyanogenmod.org/#/c/74923/

Any possibility of merging this in?

Kind of silly but I use it in my own CM builds. (I've never learned how to properly send a pull request, sorry)
[Galaxy Note 3 Original Android Development] jcadduono:
Sure! It will be in the next build. I have to wonder who's idea it was to use an atomic_t as a boolean value...wtf? but ok, lol.

Let me know if you have any other ideas for useful small commits that don't negatively affect performance or battery life that I might be missing.

I will commit the patch to all branches, if you want the change now you can compile it yourself or request a specific build and I'll send the command to the build server for you then give you a download link. (It would be nice to know it works without any issues before I make another release, but I think I'll wait for a few more things to pile up)
[Galaxy Note 3 Original Android Development] acme1974:
Now work. ...thank you

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Original Android Development] acme1974:
OK I am Italian. ...and thank you

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Original Android Development] orbital_71:
Jcad, was it possible to add the step of yours to coverting f2fs in the first page?
[Galaxy Note 3 Original Android Development] piats:
[MENTION=5672995]jcadduono[/MENTION] can you add this fix/changes for your cm13 kernel: http://xdaforums.com/showthread.php?p=64004384

This enables memory card recognition/access in root explorers.

Thank you!
[Galaxy Note 3 Original Android Development] Lyokacanthrope:
I've actually tested it myself and it works fine, been using it in my CM13 builds.

I'm not sure if anything else is missing, really.
[Galaxy Note 3 Original Android Development] Lyokacanthrope:
Oh, I see.

voldmanaged=sdcard1:auto,encryptable=userdata

voldmanaged=usbdisk:auto

in fstab.qcom
[Galaxy Note 3 Original Android Development] jcadduono:
ok I can do that. I'm gonna see if I can compile kernels for every variant on cm. What I need from cm is for them to add the variant detection to their init source. Japanese variants need FeliCa NFC support which they will probably never get so they are fine to use tmo version of cm which has NFC disabled.

If you, [MENTION=293887]Morningstar[/MENTION], or [MENTION=2332422]temasek[/MENTION] want to point me to your hlte and hltetmo build sources I can give you a patches to make init compatible with all the variants I'm supporting in my kernel builds.

I wonder why CyanogenMod isn't supporting more variants already?

CyanogenMod should have just unified their init binary for all variants of Snapdragon hlte and put NFC statements in init.carrier.rc or something... that's what I'm doing.

Have either of you figured out the sdcard issue? Mine still shows up as corrupt unless I format it in CyanogenMod. (exfat formatted from windows or twrp is corrupt)

I would have thought it'd be fixed with this commit: https://github.com/CyanogenMod/android_system_vold/commit/fa407a012666a1a6d5b05743ca61114819a685f9

Have you pulled that for your builds yet?

I'm testing on [MENTION=2332422]temasek[/MENTION]'s "preview" build from today. I'm actually really impressed how fast this is compared to TouchWiz. Can't leave my camera app behind though. </3

WHOA open the browser and hit the back key, cool close animation!

Since I am an elite photographer who likes to capture in the moment:
[Galaxy Note 3 Original Android Development] Bushido76:
Just a short information for all touchwiz users. _alexndr rebased his rom to *ok2. ?

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

(If you did change your system partition to f2fs format it will be ext4 after the flash.)
[Galaxy Note 3 Original Android Development] ikong7:
i'm on aryamod 8.. wud you recommend trying f2fs for this rom before using your kernel? and what version should i use? thanks man!
[Galaxy Note 3 Original Android Development] jcadduono:
AryaMod uses permissive TouchWiz. Always use the one for your device model, and preferably the latest version available (6.6.1 for TouchWiz at the time of this reply)

If you want to try out f2fs, go for it. It doesn't require any ROM support at all, it's entirely kernel based since raw mounting is used for system and data partitions. All in the kernel.

Build 6.6.2 in progress for CyanogenMod 13.0.. updates the selinux policies and fixes a few ueventd entries, higher priority f2fs, removes kernel logger driver, and adds keydisabler. I'm also building it for all variants despite lack of support in CyanogenMod. Go ahead and try temasek or Morningstar's builds with it folks who normally don't have CyanogenMod builds for their devices!
[Galaxy Note 3 Original Android Development] Freyelis:
No issues :)

Thank you man, you deserve the best. I've tested everything on N9005, N900K, N900S, N900L.. all smooth.. using Aryamod on all those models
[Galaxy Note 3 Original Android Development] stavca:
does 6.6.2 fix the SD card issue on temasek's ROM??
[Galaxy Note 3 Original Android Development] jcadduono:
Jeeze are you hoarding Note 3s or what :)

It fixes what it can on the boot image side of things, the rest I believe is bug fixes in vold. Sdcards should work but only if formatted from cm13 at the moment. Do you know anyone who's got it working without format in cm13?
[Galaxy Note 3 Original Android Development] stavca:
don't know about such guy :) but I tried tema's preview with your 6.6.1 kernel and SD card wasn't accessible via explorer even if I formatted it with CM13.0 so will try it in a mmnt with 6.6.2 ;)

Edit: and it works!! Gr8
[Galaxy Note 3 Original Android Development] waplegend:
Has anyone noticed battery life way better on 6.6.0 than it is on 6.6.1 n5port?
[Galaxy Note 3 Original Android Development] jcadduono:
Just a coincidence there were no changes except proximity sensor is reporting proper value.
[Galaxy Note 3 Original Android Development] waplegend:
Yeah its better i will stick to 6.6.0 for now
[Galaxy Note 3 Original Android Development] jcadduono:
you win this round, john haygarth
[Galaxy Note 3 Original Android Development] Bushido76:
Very informative this thread. ? I already knew about the placebo effect but never linked it to john haygarth. ? But maybe the new version number leads to a worse fragmentation on boot partition and ram. ? In my case I did not realize any battery problems in 6.6.1.

Another question: We spoke about it some pages ago. Would it be possible to mount SD card as USB mass storage instead of MTP. I tried drivedroid but I'm looking for a way to access internal and external memory as mass storage all the time. Thx in advance.
[Galaxy Note 3 Original Android Development] Nuno Oliveira:
Is it possible to make a clean ROM flash in f2fs file system? May I wipe it all, change fs of system and data, and after that flash normaly?

Or should I flash it, back it up, and follow the full procedure?
[Galaxy Note 3 Original Android Development] peped94:
Already flashed on darklord 2.1 rc and it boot well. Im using n9005. Will monitor performance and battery life
[Galaxy Note 3 Original Android Development] marbutina:
Video on Darklord Rom is flickering. Is possible to add s-view cover compatibility? It works with Shinto Kernel. Thanks for the kernel.
[Galaxy Note 3 Original Android Development] MarkusOSx:
Great kernel, thanks :)
[Galaxy Note 3 Original Android Development] Bushido76:
Thank you for adapting your kernel to the Darklord N5 port. ? In my eyes this rom is the best I've ever had on my phone. I thought about buying a new phone but with the N5 apps + S6 camera there is no need anymore. (I'm still impressed. ?)

As XDA is intended as learning hub and source code exchange platform I do really appreciate that your kernel is open source. ?

I read the following tweet of the shinto kernel dev: "Everyone is thanking darkera for fixing the video flickering problem...I am baffled...I've learned my lesson & won't make same mistake again" This means, that darkera13 can tell how to solve the problem.
[Galaxy Note 3 Original Android Development] marbutina:
The first who solved the video problem was the creator of Shinto Kernel. [MENTION=4696762]darkera13[/MENTION] contacted him for the adaption to his kernel. I think that for lean kernel can do the same.
[Galaxy Note 3 Original Android Development] peped94:
scrolling was stutter and jerky when using this kernel. any advice ? already turning off adreno idler. or can i just leave it for a day or two to let it settle first ?
[Galaxy Note 3 Original Android Development] DaOldMan:
I installed your kernel, first impressions follow:

1) No video flicker at all ;) WOW !

2) No problems with USSD codes, great !

3) Rils (modem reset, crash) present :( but needs more testing

So far looking like a very very promissing kernel for our rom. Cudos mate, you are great !

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------

No you misunderstood. The Shinto dev has taught Darkera how to fix the video flickering problem in his kernel. Now he is angry that instead of thanking him people thank Darkera. So he will not do the same mistake again - HE WILL NOT HELP OTHERS TO FIX PROBLEMS. I see this like a childish behavior. Pity as we all loose. :(
[Galaxy Note 3 Original Android Development] r-l:
Testing it now on Dark-AU N5 port. Seems smoother the darklord kernel.

Will report back later
[Galaxy Note 3 Original Android Development] Bushido76:
Thank you for your explaination. Indeed I misjudged the situation. But the result should be the same. When the shinto dev is hiding information I hope that darkera is willing to provide the fix.

I can't understand the behaviour too. Shinto kernel isn't part of XDA anymore, because the dev was not willing to provide sources. To be honest - taking millions of source code lines from device manufacturers and other devs - injecting some changes and distribute it as closed source is questionable. That's why I thank everybody who shares the spirit of this community. ? Using hours after hours of spare time to help and teach others deserves my deepest RESPECT! ?
[Galaxy Note 3 Original Android Development] peped94:
can u share your setting of the kernel ?
[Galaxy Note 3 Original Android Development] r-l:
Haven't change any settings yet, just starting with testing
[Galaxy Note 3 Original Android Development] jcadduono:
You could always sic the FSF on him lol! What he's doing is technically illegal. :)

Anyways, it doesn't matter. I'll go download the N920C kernel source from Samsung OSRC and try to find any API differences later today. (Merhhh sleep not finished, damn blinking led)

Biggest problem I see is it already works with no bugs on my phone so it'll be a hassle trying to fix something I can't see lol.
[Galaxy Note 3 Original Android Development] darkera13:
Yes, i need confirm again [MENTION=4098343]CekMTL[/MENTION] guide me fix camera flicker.

Lol, this thing is very same with my Darlord Rom, some ppl dont know im the the fisrt and only one can port N4, S6, N5 for them. Some devs learn from my port, use all my experience, after that they think they can port, lol. No they dont. I always is the first, i do for my hobby, i dont care about anything else.

Xposed for Samsung Lollipop too, im the first find the way to make it work after long time we give up the hope. But after that a guy take it, do with other way and say "I can do too", lol. Disappointed!!!

Sorry to OP if my post is not proper.
[Galaxy Note 3 Original Android Development] waplegend:
Thanks very much for the darklord you are truly great and a source of inspiration to many keep being first and keep working we love you
[Galaxy Note 3 Original Android Development] DaOldMan:
Your kernel is excellent. The only problem I have is the RIL (modem) crashes. In Shinto it doesn't happen. It happens with Darekeras and your kernel. It's provider dependent. I and my mates with Golan Telecom have it but others don't. I hope you have that problem :) so you can fix it ;)

Again thanks for your work :) !
[Galaxy Note 3 Original Android Development] waplegend:
Thanks a lot man for supporting darklord n5 this kernel has been my go to kernel since I hard my note 3 thanks a lot hope the development never stops
[Galaxy Note 3 Original Android Development] waplegend:
And dark if I can give a suggestion I think you should make this a full time job get a standard team and make it all co operations
[Galaxy Note 3 Original Android Development] Bushido76:
I fully understand your thoughts. Like mentioned above your N5 port is outstanding - in comparison with original N3 rom too. It's really sad, that one should buy new hardware for hundreds of dollars instead of getting an updated rom with updated apps. All original note 3 roms are "overbloated" and show a bad performance.

It's condamnable to provide results of others as own results. ? In my eyes there is no difference in comparison to making open source to "own" closed source. XDA is not intended to suffer such a behaviour. Most of the devs follow the rules ? but some are no member of XDA anymore. It's always the same cycle since generations of mobiles. Sad but true.
[Galaxy Note 3 Original Android Development] jcadduono:
By the way, do you mind sharing with me how you or CekMTL fixed the video recording issue?

I'm about to go kernel diffing into N920C's sources and it'd definitely be nice if I didn't have to lol.

I'm expecting it to be a mismatch in camera_v2 api, but on the chance I'm wrong it would be much easier just to know how you did it.
[Galaxy Note 3 Original Android Development] darkera13:
I sorry but i dont have permission to share for you. You should ask CekMTL.
[Galaxy Note 3 Original Android Development] piats:
[MENTION=5672995]jcadduono[/MENTION] I'm using cm13 v6.6.2 kernel with temasek cm13 rom preview2.

I installed supersu v2.52 and now Ikconfig doesn't work via terminal emulator.

If I use build in cm root it works?

Kmsg log: http://pastebin.com/JCtYg8CU
[Galaxy Note 3 Original Android Development] amirsat2012:
tested with Phronesis Rom v2.0

there is a problem using camera with this kernel ...Video recording blinking...
[Galaxy Note 3 Original Android Development] antt00:
As mentioned countless time, the problem is with the rom not the kernel.
[Galaxy Note 3 Original Android Development] amirsat2012:
No sir

With the integrated kernel of the rom there is no such problem

Envoyé de mon SM-N920C en utilisant Tapatalk
[Galaxy Note 3 Original Android Development] Bushido76:
Antt00 is right - the integrated kernel uses a workaround to mask the rom problem.
[Galaxy Note 3 Original Android Development] jcadduono:
Have to wonder why phronesis dev hasn't just pulled the camera API libs from darkau by now. XD

The reason we do this is because of flash scripts...every ROM dev likes to force flash or mount all partitions as ext4 and fails to flash. You can probably just extract zip, find updater-script in meta-inf and replace all occurances of ext4 with f2fs. Compress back to zip. Disable md5 verification in recovery. This might allow you to perform quick upgrades / dirty flashes too.
[Galaxy Note 3 Original Android Development] Bushido76:
I do not follow any projects outside XDA. Is the video flickering problem solved in darkau rom without using a "warez-kernel"?
[Galaxy Note 3 Original Android Development] shiverz07:
This is what I can get of I don't play Clash of Clans all day at work. ?

Could probably get more if I don't play at all. But that'll be very hard... ?

Sent from my DarkAu Note 3
[Galaxy Note 3 Original Android Development] jcadduono:
So they tell me :P I wonder if phronesis is just using note 4 camera libs instead of note 3 because they are very close just note 4 supports a few more commands, and that could explain contrast flashing issue if note 4 lib is sending one command being interpreted as contrast adjust in note 3 kernel

Just terminal emulator or adb set up with bad path entries. Use /sbin/ikconfig instead. Or type:

export PATH=$PATH:/sbin

and it will work until you reboot phone

This happened all the time in cm12
[Galaxy Note 3 Original Android Development] piats:
Yeah that works I was just wondering why it works with cm root.

One another thing what I noticed was that phone screen would randomly turn on while charging? Idk what could cause that?
[Galaxy Note 3 Original Android Development] justin1221:
N900T with Temas cm13 preview1 as secondary rom and DarkAu3.5 as primary.

Downloaded 6.6.2 cm13 Eur and tried to patch with latest DualBoot Patcher and I keep getting failed patch. 6.6.1 patches fine, as well as everything else I've patched.

Attached patch log.

http://pastebin.com/raw.php?i=JxWgbiek
[Galaxy Note 3 Original Android Development] jcadduono:
The log says your dualbootpatcher is 200 revisions and months behind latest lol...

I think you just had an old copy sitting around and accidentally clicked that for 6.6.2.
[Galaxy Note 3 Original Android Development] newintage:
Sorry for asking but, that TWRP is modded ? Or is it just a mirror or something ?
[Galaxy Note 3 Original Android Development] justin1221:
After I reinstalled Dual Boot Patcher, I was able to give proper permissions. Still getting used to Marshmallow, permissions are a little dif. Didn't have r/w for internal. That's what I get for tibu my apps. Lol. Thanks for looking.
[Galaxy Note 3 Original Android Development] jcadduono:
My TWRP is modded yes. It uses idleKernel instead of the prebuilts from Omni. It fixes a few bugs and adds some features.

MTP and USB Mass Storage works in recovery mode, allowing you to plug phone in and easily transfer zips and backups/restores to and from your phone and sdcard. It also fixes some file system bugs that caused ext4 broken backups that couldn't restore to f2fs partitions. On top of that it allows me to support TWRP for variants that aren't officially supported, such as the japanese and korean variants.

You can also use ikconfig in TWRP from adb, allowing you to fix settings like unstable cpu overclocks from recovery.
[Galaxy Note 3 Original Android Development] kpirnie:
genius mate :D

Now thats what I call recovery :)

my boy [MENTION=6360887]sawixso81[/MENTION] themed twrp 2.8.4 for Dominion rom i was thinkin of pokin around... i love [MENTION=4098343]CekMTL[/MENTION]'s ShadowLED enough were i culd picture myself finding that handy during flashing... ;)

so... similar to a boot.img in terms of its got a ramdisk, etc... ?