yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] MitchellHearthog:
Just flashed it and done a quick test. And it's a LOT better! Here are 2 pics in a really dark room. One without the fix and one with:

Since I can't post links yet, please copy the link:

Without: i57.tinypic.com/2iqbos6.jpg

With: i59.tinypic.com/29wjvcg.jpg

Take a look at the sheets and the top right corner (the white wall). You can see a lot of pink-ish noise in the first pic, where the other pic has a lot reduced noise. Furthermore, the overal quality is just improved greatly. This is awesome!

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

Aii, just after posting this message I wanted so make a short video but the camera app crashed and now it can't connect anymore :crying:
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Great difference indeed :)

Yeah I just tested it, I could record video a few times but after flipping back/forth cam/video it crashed. Will look into that. That's why I wanted people to try it first before I push it onto CM ;) But this should be fixible, I dont expect difficulties here. In fact I didnt even think of this, but I shouldnt do certain stuff when video is selected instead of photo. Will fix it.

Thanks for trying it and reporting !
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hehe by now I should know better: difficulties should ALWAYS be expected when working with Samsung stuff :) So I just found the root of the problem and it's not going to be a 1 minute quick fix .... Thing is that I'm forcing the libraries to use camera 1 API. That's why the kernel is included in the fix, it contains a property that forces camera 1 API. I hear you say 'but we are on camera 1 api'. Yes, correct, but somehow we were using part of camera 2 already. That sounds much more interesting than it actually is, cause we can't get any of the benefits without Samsung releasing Camera 2 API HAL.

Anyway, I just found out that if you flash a clean nightly, you can flip a hundred times between photo/video, no crash. However, if you ONLY flash the kernel I posted, then the problem already arises: flip a few time video/photo and it crashes .. The only thing different in that kernel is that it forces camera 1 API. So it must be some bug in the CM code in that camera 1 API. So.... The solution would be to stop forcing Camera 1 API. However of course I was doing that for a reason. I needed to send vendor commands from within the app and that's currently only supported for the camera 1 API. But there might be a way to not do that.

Anyway, I will look into all this. Bottom line is, the low light mode works. That's all reversed engineered and I got it going in cyanogenmod. But now I need to adapt things and see if I can get it going from within the camera 2 API ... Or find the problem in the camera 1 API ...

So, unfortunately, this topic isnt closed yet .... Still work to do :(
[Galaxy Note 4 Original Android Development] than33:
That looks like you like blues all over other colours. I assume you are wearing blue glasses? Because that is what you are doing with your screen.

It is strange, but originally screen is almost perfectly calibrated to sRGB standard. There is no reason to change it. The only option is to choose natural mode (with perfect sRGB colours) or amoled photo with more saturation (which in fact is adobe rgb mode.)
[Galaxy Note 4 Original Android Development] alfredlee:
Phone getting warmer ever since boot.img was merged. Can anyone upload the last working version of boot.img?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Ok, progress :) I've got it now working without forcing camera api 1 ! Flipping photo/video doesnt crash anymore, so that indeed solved it. However since I'm now doing everything in the lib (since I cant send from within the app anymore) it should work with other apps too. And that's the problem, just tried snap camera, that one isn't too happy and freezes ... So still some work to do, will look into it tomorrow again ...
[Galaxy Note 4 Original Android Development] sahalan:
I get 'cannot connect to camera'. Cleared cache but only a reboot helps and then only for the first time I use it. Second time, same thing again.:silly:
[Galaxy Note 4 Original Android Development] gekkehenkie11:
New version here:

https://mega.nz/#!vJAnzYRL!YqmWCnvDz_IF4AmkImzdjXDdfQxjjKCyJpDdzpZKCXg

No need to flash a kernel. In fact make sure you are NOT using the kernel I posted yesterday. So flash a nightly or restore an old backup in TWRP, either should work. Then flash the above zip.

Remember this WILL give problems with 3rd party apps at the moment. But it seems to work fine now in CM stock cam. I tried flipping camera/photo a million times, no problems anymore.

Will keep working on this and try to find a solution so it at least doesnt mess up 3rd party apps of course.
[Galaxy Note 4 Original Android Development] bo-l:
Is there a eta on Android m / 6 to Cyanogenmod? :)

Sendt fra min Note 4 @ Android 5.1.1
[Galaxy Note 4 Original Android Development] Ce:
1. don't ask for eta's ;)

2. Android M is still in beta, not even officially released yet.
[Galaxy Note 4 Original Android Development] Captain Droid:
Guys , Any hope for SM-N910C Exynos variant ? :confused::crying:
[Galaxy Note 4 Original Android Development] mikimadm3:
Just tried low light photo mode, unbelievable achievement, you are the man... Thank you
[Galaxy Note 4 Original Android Development] Venacephalica:
Hey! Thanks a lot for spending your time for it :D

It doesn't work for me but I have to say that I'm on Resurrection Rom...I flashed via recovery but I didn't notice any change:confused:

---------- Post added at 08:19 PM ---------- Previous post was at 08:16 PM ----------

Could you make a screenshot of the cam monitor, please:D
[Galaxy Note 4 Original Android Development] mikimadm3:
Here is my before and after, you can clearly see less noise in the after one
[Galaxy Note 4 Original Android Development] Venacephalica:
Ok, thanks a lot...it's a huge difference :good: But the camera interface is the same, isn't it?
[Galaxy Note 4 Original Android Development] mikimadm3:
Same camera interface...
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Under normal light it will behave exactly the same. When there is low light (at night for example) it will take a bit longer to make the photo. You need to hold the phone still during that moment. And then it just ends up as normal. Just a quality difference, that's all. The whole process is automized and the user wont notice.

In touchwiz it displays a message 'Hold the phone still' during nightshot mode. At one point I might do something too but right now it doesnt have a high priority.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Yes, that's it indeed, looks much better. Now people can stop complaining that you cant shoot good photo's with AOSP roms ;)
[Galaxy Note 4 Original Android Development] smallthings:
I just wanted to thank you for all the work you've put into the many things you do. My Note 4 is now usable in CM again thanks to people like you.

I'd also like to ask if you think that you'll still be able to get auto-brightness into the ROM eventually.

Thanks much
[Galaxy Note 4 Original Android Development] Maerad:
I just installed the lastest nightly and gapps full. Now I dled 2-3 themes / designs from the play store for cm 12 and everytime it installs a theme I get an error "App couldnt be installed".

Any idea what this could be?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
And a new version of the nightshot mode: https://mega.nz/#!jFBR0LBR!vp7iMAEGYtPP2iEMldyT11ABFAioxVhVkF31n06ma30

It seems that 3rd party apps like Snap camera dont crash anymore. So it SEEMS everything is stable now, but let me know please ! I need some feedback before I merge this, I want to make sure it's not causing anyone any problems.

For now, if you want nightshot mode, I suggest to use the CM stock cam. It seems the Snap Camera doesnt always work fine (after switching video/photo it doesnt do night shots anymore it seems). But apart from that Snap camera seems to work normal.

So, hopefully nearing completion/perfection on this one, would love to move onto other issue's (but I need this to be perfect first).

*EDIT* actually scratch that, issue's with snap camera still exist ... researching into it ...
[Galaxy Note 4 Original Android Development] cloak:
I've used this latest version with the Cm camera and the Google camera. Both running well. The quality of the pictures are excellent [emoji106]
[Galaxy Note 4 Original Android Development] cloak:
After installing your magnificent low light camera fix the HDR function in the Google camera isn't working anymore.

For me no problem. But I don't know if it is a problem for other people.
[Galaxy Note 4 Original Android Development] nadejo:
I experience big lags while playing asphalt 8. could it be that this happens because i didnt make a clean install since months?
[Galaxy Note 4 Original Android Development] isaacinsoll:
Night mode is awesome!

If we are voting for the next feature to implement my vote is for a easy way to activate high Brightness Mode on the screen (or automatically like touchwiz)

Much love!
[Galaxy Note 4 Original Android Development] MichaelGroth:
Really enjoying the night camera fix [MENTION=3296134]gekkehenkie11[/MENTION] awesome work. Facebook messenger camera stopped working again tho.. But no big deal, just figured I would mention it :) Thanks for making CM perfect for us. :D
[Galaxy Note 4 Original Android Development] RohanAJoshi:
[MENTION=3296134]gekkehenkie11[/MENTION] : As former LG g3 owner, there were issues in cm/aosp camera such as not working OIS and Laser Auto focus.

I am planning to buy note 4, so want to know that PDAF focus / or something what on back, the flash is working well and overall camera performance ?

what about other issues ?

is IR blaster also working and other sensors such as step detector (if available) ?

sorry, I am asking too much, but my decision depend upon aosp stability.

.

Thanks for your amazing support and nearly perfect cm
[Galaxy Note 4 Original Android Development] pctv007:
Hi there !

I just found that mic sound of BT headset is very low... Tried with 3 different headsets...

Someone knows how to fix that, please ?

Thanx

Maybe editing mixer_path.xml ? But how ?
[Galaxy Note 4 Original Android Development] ROBSONMEG:
will the night mode get merged in to the rom? many thanks rob
[Galaxy Note 4 Original Android Development] isaacinsoll:
IR blaster definitely works :)
[Galaxy Note 4 Original Android Development] shahed26:
Camera almost perfect, only remaining issue for me is the touchpad light that lits up everytime i touch the screen.

If fixed could save a bit of battery as well. Thanks for your effort and time
[Galaxy Note 4 Original Android Development] pctv007:
Step detector is working perfectly ;)

Using it everyday...
[Galaxy Note 4 Original Android Development] cloak:
I had a lot of FCs with Sygic, running long routes (Holland Spain) with Lollipop builds

First I thought it was a Sygic problem. But it seems to be a sygic / lollipop problem..

In the August 19 nightly a lot of overflow bugs seems to be solved.

Sygic is running well now. Even during the calculation of long routes to Gibraltar [emoji106]
[Galaxy Note 4 Original Android Development] Saarliner:
Download Link doesnt work for me
[Galaxy Note 4 Original Android Development] argtoub:
You can fully disable it by this way

Parameters => Buttons => Backlighting
[Galaxy Note 4 Original Android Development] Xokoz:
Is there any other way to make AudioFx work than eng.stk's fix? That fix doesnt work me (well, dpsmanager works, but it makes sound quality bad).
[Galaxy Note 4 Original Android Development] shahed26:
Thanks. Didnt know such option exists. But still a proper fix would be great.
[Galaxy Note 4 Original Android Development] finallau:
Use this fix: http://xdaforums.com/showpost.php?p=60692359

This is the fixed one
[Galaxy Note 4 Original Android Development] thompson9100:
Struggling - HELP Please!!!

Hi

I've gone through everything I can find yet I can't install CM12.1 on my Note 4 910F. I've tried changing TWRP down to version 2.8.xx as suggested on the start of this post, I've cleared everything, and all the time I'm being told I can't use TRLTEXX as I have TRLTE.

I know this must be an annoying thing for those in the know, but I've done everything I can, even allowing stock rom to reinstall, but to no avail (and yes, Delvik, Cache, Data and System were all wiped as well as a full wipe).

Please, if someone can help me out because I'm out of options now!

Many thanks in anticipation.

Dan T
[Galaxy Note 4 Original Android Development] mpcjanssen:
What was the error? Without that information we can't help.

Edit: need to learn to read. Wrong twrp version is the probable cause.
[Galaxy Note 4 Original Android Development] pctv007:
I remember I had this error, a long time ago. It was TWRP related. I had to install TWRP for N910 F (LINK)

Then I was able to install correctly.

Give it a try...

;)
[Galaxy Note 4 Original Android Development] sahalan:
Download link for latest camera update still not working.

Edit: errrr, nevermind. Bedankt?
[Galaxy Note 4 Original Android Development] MMarkkk:
https://mega.nz/#!jFBR0LBR!vp7iMAEGYtPP2iEMldyT11ABFAioxVhVkF31n06ma30
[Galaxy Note 4 Original Android Development] mxdev:
this package is for device : trltexx , trltedt ; this device is trltecan

Excuse me , I have a small question SM - N910F , I downloaded the trltexx for this device but as I do with the flash TWRP 2.8.7.0 tells me : "this package is for device : trltexx , trltedt ; this device is trltecan " . I can find no other version to flash apart from these , however . I also tried different recovery always the same problem .

Thank you
[Galaxy Note 4 Original Android Development] Battlehero:
Could you please use the search function because I have posted instructions for this problem on many different threads.

Can you confirm what your phone model is?

If it's N910F then you need to install the Trltexx ROM.
[Galaxy Note 4 Original Android Development] pctv007:
I remember I had this error, a long time ago. It was TWRP related. I had to install TWRP for N910 F (LINK)

Then I was able to install correctly.

Give it a try...
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Here's a new version of the Nightshot mode:

https://mega.nz/#!nRJQXBhb!PPJwYOpeFIvGolMLT5uWL75QLOC3J0ShU6oiV2Bt6lw

I did some more reverse engineering and found that I was still missing some vendor commands. So I hacked the original api to output *every* vendor api call to the log and I've now implemented them all, in this version.

However problems with for example Snap Camera still exist. And I think that's to be expected. I'm putting the camera in a mode that apps are not aware of and thus behaviour might be unpredicted. I think there's only one solution and only enable this if an app explicitely asks for it. At the moment I'm not sure yet how to do that, but will research into this.

Everything seems to work fine with the CM stock camera though.
[Galaxy Note 4 Original Android Development] Xokoz:
That is DSP Manager, not AudioFX right? And whats different between this version and eng.stk's?
[Galaxy Note 4 Original Android Development] cloak:
I'm going back to V3. I'm using the standard cm camera. Using V4 the picture is a part of the total frame.

Generating the final picture takes a lot of time.

Changing to portrait or landscape gives an FC
[Galaxy Note 4 Original Android Development] jrubenc:
[MENTION=6440829]tsdue[/MENTION] Be careful with installing a wrong twrp recovery or you'll end up in a ""Could not do normal boot ODIN MODE (HIGH SPEED)" boot loop. Reflash CF-Root with Odin for example, to fix it.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
What do you mean with that ? You mean that a part of the photo is missing !?! I just tried it, everything seems fine here. You are using the CM stock cam ? If so, what resolution ?

Should take about 2 seconds for nightshot photo's. It takes more in your case ?

What do you mean exactly ? Preview mode ? Just turning the phone causes a FC ? If so: preview mode for camera or photo ? Or do you mean it happens when you shoot a photo ? And again what resolution ?

I can't reproduce any of what you just mentioned here !??!

Thanks,
[Galaxy Note 4 Original Android Development] pctv007:
Never had such an issue... I flashed every TWRP recovery found on TWRP's site for Qualcomm Note 4;

The only side effect was that with other TWRP recoveries, I had the afore mentioned error "Can't Flash this rom because it's for Trltexx and not for Trlte..."

Furthermore, he says he's got a TrlteXX N910F so I gave him the right link on TWRP's site, to DL TWRP for Trltexx.

Never had to reflash via Odin, as TWRP includes a flash .img files menu.

Thanx

:)
[Galaxy Note 4 Original Android Development] mike13ftw:
Today my phone rebooted 3 times alone without touching it. Has anyone else experience the same issue?
[Galaxy Note 4 Original Android Development] f0xy:
What about the struggles we faced on galaxy s3 ???
[Galaxy Note 4 Original Android Development] Blartiartfast:
All good here, apart from using the note4 on my Bluetooth carkit. Everything is fine, audio clear, etc but if an email or any other message is received then then carkit will drop the phone until the message tone has finished playing and then reconnect. Is there anyway to solve this without turning on media in the Bluetooth options for the car kit in the phone? Cheers for any help.
[Galaxy Note 4 Original Android Development] finallau:
Eng.stk's one the DSP Manager equalizer does not work

Mine I added an additional patch while uses his DSP Manager thus will be fully functioning. You will notice the difference after my patch

Read the description
[Galaxy Note 4 Original Android Development] cloak:
Hi Gekkehenkie.

Yes I'm using the Cm stock cam, in the highest resolution.

I missed a part of the photo and it takes about 5 seconds to generate the photo.

When I made a few landscape shots and a changed to portrait the FC happened during the first portrait and visa versa.

Now I've re-installed V4 again and did a cache and Dalvik / Art cache wipe after flashing the zip file. Now everything seems ok.

The first time I did not do that.

Perhaps this was the problem?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Yeah might be. Let me know (others too) how V4 works for you on the stock CM cam (please dont use other cams during testing cause they might mess it up, I'm only interested to hear how it works on stock since I want to make it exclusive for stock). If everybody is happy with it (no problems) I'll have it merged. Although I still need to figure out how to make it exclusive for stock cam but that should be doable.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
So I was just looking into that. I compared it to Touchwiz and saw that the decision to turn on the touchpad lights after a keypress is being made in the JAVA framework. So that would mean it would happen on ALL CM devices. Can someone confirm this please ?
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
Compass not working in Google Maps navigation mode

I just realised that the compass is not working at all in Google Maps, when you're in the navigation mode (navigating from one place to another). Searching through this thread, I can see many other users have also mentioned this issue over the past months.

[MENTION=3296134]gekkehenkie11[/MENTION] in an older post you did mention that the compass is working for you. But I wonder if you specifically tried it in Google Maps, in the navigation mode? According to what I have read, the compass does work in other apps. It only does not work in Google Maps. Could you try that yourself and confirm it? Is this a known issue for the Note 4?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
I'm actually confused what this whole compass fuzz is about. What IS the compass anyway in google maps ? Can you make a picture about what you're talking here ?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Ok supposedly this is default AOSP behaviour since forever :) So most definitely not related to our Note 4. I think I will skip this issue then and just leave it default AOSP behaviour. If you want you can just turn the touchpad light ALWAYS off as explained in the previous post.

My goal is to first fix all device specific things and then onto stuff like this.
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
I think I'd need to record a video to show it in action. Let me try to describe it better. If you have another phone (not Note 4) available you can test it there and see how it should work....

1) Open Google Maps, type in some nearby destination into the search field and select it, and then tap the blue circle icon in the bottom-right (it should show a car or person in the icon).

2) Tap the blue circle again to begin the navigation. Now you will get a 3D view of your current location, with a blue triangle to represent you. And you can see the route you should take along the streets.

3) If the compass *is* working, you should find that rotating the phone around you will also rotate the map. That means, the blue triangle on the map will be facing the same direction that your phone is facing!

However, on the Note 4, currently nothing happens when you rotate the phone. The blue triangle is locked in the same direction and it doesn't rotate itself as you rotate your phone. That means the compass isn't working.

It's an incredibly helpful and important feature, because it means the phone will always show you what is in front of you, so you can see where you are going on the map! Without the compass, it would look like you are walking/driving backwards or sideways, rather than forwards.

Does that help?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Ok so this should work on touchwiz then right ? Going to try it :)
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
I assume it should work on TW, although I haven't tried it myself. Thanks for testing!
[Galaxy Note 4 Original Android Development] gekkehenkie11:
It's that blue pointer right ? But that doesnt seem to be a compass. When I turn my phone it does nothing. However when I start walking, it starts to point into the direction I walk. So that seems to based on GPS data and not compass data (otherwise it would turn when you're standing still but turning the phone)
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
Yes, that's exactly right. But it's

supposed

to be a compass - it's supposed to rotate around as you rotate the phone around. That means you can stand in one spot, and turn around, and the blue pointer will turn with you.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
BUt that doesnt even seem to work on touchwiz, or I must be doing something wrong ?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Is this still an issue BTW ? If so I'll look into this next.
[Galaxy Note 4 Original Android Development] laehtis:
I don't have that issue.

But my network still keeps dropping the connection, with both 3G and 4G.

Any ideas, should I try Network keeper apps, if there are any?
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
On your TW device, make sure you select walking mode in Google Maps - not car/driving mode. In car mode, the blue arrow will always face the direction of the road. But in walking mode, the blue arrow will use the compass to rotate according to the direction the phone itself is facing.

I've just tested this on a Galaxy S5 that is running TouchWiz, and the compass works there in walking mode.

I've also tested it on a Galaxy S3 that is running CM12.1, and the compass works there too, in walking mode.