yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Exynos)] Bman:
Thanks! Much better then old org battery.
[Galaxy Note 4 Android Development (Exynos)] dsbowskill:
A quick thank you for keeping my 2014 device functioning so well!

Haven't tried the 2022 update as still running 30june21, but have noticed that SIM authentication of Wifi (used by some UK networks such as EE) is not working in this ROM.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
TWRP 3.7.0_9 Has also been released. Update is not mandatory for this version.

https://xdaforums.com/t/exynos-gala...tom-recovery-07-28-2021.4311777/post-87929053
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Great update! Apps seem to use less ram now.

Dirty flashed to 11 from 10 (Had to manually remove /data/system/locksettings.db because of keystore issues), so if I ever encountered some strange issues, I would reset this phone.
[Galaxy Note 4 Android Development (Exynos)] imglai:
I'm gonna buy a 2nd hand N9100CQ soon and I was wondering if there is anything I should look for specifically when I see the phone? Also, is there any tool or app to check internal pieces?
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Can confirm this was needed after updating lineage 18.1 october build > december build. not sure what happened there but yes keystore breaks on dirty flash, no issues observed yet after removing it and re-setting pin
[Galaxy Note 4 Android Development (Exynos)] hojjat61:
Thank you for your great ROM, there is a problem that was also present in Android 10, but there is no problem in Android 9. The sound stops in the Clubhouse program. Thank you for your help.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Ill take a look once i get the chance thanks.
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Guess I'm a bit late to the party :)

Happy new year @ananjaser1211, thanks for this amazing rom again!

I'll be installing this as soon as I finish the backup on my Note 4 :cheers:
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Thank you mate, Enjoy, Another update will be pushed this month addressing some issues reported.

Next release will fix bad power management (due to recent tuning) , call recording , safetynet (currently fully broken unless you use Magisk fingerprint altering modules) and enable MicroG support.

will try to tackle more bugs as the month progresses
[Galaxy Note 4 Android Development (Exynos)] Tu Dam:
Wow never thought I would see Android 11 come to Note 4. Thanks so much 👍.
[Galaxy Note 4 Android Development (Exynos)] Tu Dam:
Can anyone provide screenshot of this ROM?
[Galaxy Note 4 Android Development (Exynos)] EzZzO:
I'm having trouble restoring from zip files after updating to 18.1

I have tried to restore app data from Neo Backup and MyBackup Pro but I get an error message if I restore from a zip file

I think there is a problem with read permissions in zip files

sorry for my bad english
[Galaxy Note 4 Android Development (Exynos)] shandess:
Happy New Year @ananjaser1211 and thanks for this!

I still use my N916K a lot for media consumption mainly on WiFi, just installed this update and everything works fine for my use case.

Really appreciated also the clear and straightforward instructions on the wiki.
[Galaxy Note 4 Android Development (Exynos)] Ketab1:
Thank you anan ❤️❤️

-Nice ROM ,Very smooth

-Without any major problem so far except battery drain

-very hot but after some day cool

-I enjoy this rom with cool note20 launcher+one ui icon pack+Samsung music,note and gallery mod app. we Wait for update this rom and PixelExperience 11 and android 12.thanx❤️❤️
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Home screen https://media.discordapp.net/attach...Screenshot_20230107-023148_Pixel_Launcher.png

Lock screen https://media.discordapp.net/attach...90159413334107/Screenshot_20230107-023550.png
[Galaxy Note 4 Android Development (Exynos)] unicunic8:
Sorry Ananjaser1211, I want to ask whether the Samsung Note 4 can be updated/patched with kernel ver 3.10.x to kerenel ver 4.9, sorry if this is a stupid question
[Galaxy Note 4 Android Development (Exynos)] Tu Dam:
Thank you. Can you screenshot some more? Like setting menu, app drawer, ...?
[Galaxy Note 4 Android Development (Exynos)] retiredtab:
I answered the above questions wrt to my msm8916 tablet devices and I also build exynos 5433 tablet devices. So my replies 3, 4, 5 and 6 apply to the exynos5433 3.x kernel.

https://xdaforums.com/t/how-to-build-linux-4-4-x-for-galaxy-msm8916-devices.4523411/#post-87781117

I can also say that the existing 3.x 5433 kernel works for 19.1 tablet devices.
[Galaxy Note 4 Android Development (Exynos)] unicunic8:
ooo yes I understand, thanks for the response
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
I randomly ran into a bug where I do have a lot of free memory (around 800MB - 1GB free), but Android kept killing apps. Funnily enough I had this bug 2 days after I factory reset my phone. This also happened in Android 10 builds. It looked like a kernel-mode memory leak, because I remember how Running Services screen looked like when I made a 1GB file in /tmp in an older device.

Additional Information: When this happened to me, I remember losing Wi-Fi connectivity. Also, this bug triggered around when I switched access points.
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Spoiler content hidden.
[Galaxy Note 4 Android Development (Exynos)] jac2317:
I know this has probably been asked a ton already but does the spen work I lost mine so I bought a replacement. its fine if it doesn't but it would be great if it worked
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Thank you for the logs, it "may" be possible that the dead wifi_vendor service is causing the issue, i cant be certain, you could try to "fix" the glitch by doing "stop vendor.wifi_hal_legacy" and "start vendor.wifi_hal_legacy" in termux (requires root) and see if the app killing behaviour is gone.

I have seem to have gotten this wifi issue fixed anyhow, i have not faced the disconnection in a while while using p2p with this commit https://github.com/universal5433/an...mmit/57667220abc903c48715b44eefda9369d3266340

so it will come with the next set of builds, i am a bit occupied debugging audio and video camera, the usual bugs. cant imagine it will be long until i push the refreshed builds however.

hopefully it fixes LMK, if not will have to dig more into it, frankly i dont even remember how LMK is being handled anymore, we updated the kernel driver but i have not looked into lmkd tuning at userspace, in android 11 onwards google switched to something called PSI (pressure stall information) to tune LMK, which is on linux 4.4 onwards, so i need to study a bit more into this subject for further tuning, right now we just brute force the issue with zram / swappiness rates, we no longer use vnswap (disk based swap that stock uses)

Only as a very basic pointer device, so you will need to find apps on the app store that mimic some features from samsung roms like notes / drawing etc, there used to be an app called spencommand that did a bunch of these features, but i have no idea how it is anymore, last i checked it was paid in a weird shady way so i never bothered to dig more into it
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Noted. Will do this the next time this happens to my phone.

Anyways, pictures from the lineage camera seems to somehow became better this build, or maybe it's just placebo.

HDR mode on the Lineage camera more or less matches the 6.0.1 stock camera behaviour, even at low light shots (Super minor detail I noticed, 6.0.1 / Refined N7 can go as 1/7 second exposure, and lineage cam can only do 1/8 second exposure. Not a big difference.)

Video encoding on the Lineage stock camera will definitely be a game changer.

Also I recorded some videos earlier, post processed it on Premiere Pro to remove the “bad mic” quality. 3 kHz low-pass filter, aggressive equaliser to reduce trebles and increase bass and it sounded decent.

Sheesh. To end it, I can't believe I'm using this note4 for 6 years already. 7th year this upcoming July. Served as a secondary phone, and my daily driver for a lot of times whenever my Poco F1’s screen got broken (6 times already!) So yeah I can definitely say this ROM is decently stable, feels smoother than the custom ROM’d Poco M3 I was borrowing.

Great work, will definitely donate someday :-))
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Haha right, stock ROM sucked so bad, system memory usage is always high and funnily enough Android 11 on this device uses lesser memory lmao.

About those Graphics crashes, I'm going to investigate something on my free time which is lightroom crashing on export, happened several months ago on 10.0. (I didn't collect logs that time because we were drinking that time and my brain is partially working that time.)

I hazily remember the crash is also related to graphics. So I'll just send log dumps after doing them and hopefully it gives more useful information.
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Speaking of memory: I have 5 apps open (Reddit, MS Edge, Photos, Messenger, and hkTweaks) and so far none of them have been removed from cached apps yet. Impressive.
[Galaxy Note 4 Android Development (Exynos)] pepperjones:
Many thanks for your work on this to this day.

On previous releases I tried both LineageOS and RR, and my G-Note 4 is still running on RR. I got another phone and wished I could give this one to my kid for him to call me, but the microphone issue is critical at that. When I used G-Note 4 running this ROM, as already known, only telephone calls had sufficient volume, I couldn't use the ROM for calls in any social media apps, because the audio isn't just bad quality, it's nearly impossible to hear, you literary have to raise your voice, almost screaming, for the people to hear you. So.... I really wished this could be solved, because not being able to have calls over the internet, only through a telephone operator, is really a killer.
[Galaxy Note 4 Android Development (Exynos)] azmtechnic:
Hi @ananjaser1211 .

Really appreciate your hardwork on this build. Really smooth working on n910h 3g variant. Almost everything working fine. but Still automatic network changing is the matter. But hopefully, in this build we can fix the signal lost without rebooting the phone.
[Galaxy Note 4 Android Development (Exynos)] retiredtab:
@ananjaser1211 , I haven't seen the above message before.

For 18.1 5433 tablets, we are running the default render engine which is either gles or threaded. I haven't traced down which is the default. For 19.1, Google switched the default from gles/threaded to skia by default. Since 19.1 5433 tablets worked with fine the new skia default, I left it at that and haven't seen any messages like the above.

For both 18.1 and 19.1, we are still using the R15 driver. While I have tested the R22 driver in 19.1, I decided to continue using the R15 for 19.1.

For 19.1 msm8916, I couldn't use the skia render engine and had to fall back to gles threaded as per

https://github.com/retiredtab/andro...mmit/50bb3dca15203e831fabca7cfea098c28aa715a5

Let me know if I can help using our usual communications channel.
[Galaxy Note 4 Android Development (Exynos)] Tu Dam:
Yeah hope this ROM won't have this issue.
[Galaxy Note 4 Android Development (Exynos)] tujrrbirosoiqktfjp:
@ananjaser1211

thank you so much for not giving up on this phone!

i have been using samsung note 4 since 2016. last year i was going to buy a new phone, than i discovered this page and i have managed to install "17.1-20210304-UNOFFICIAL-treltexx" that you provided.

because of you it is still my main phone, i use it daily, and it works.

hopefully one day there will be an official lineageos release for this phone.

my note 4 phone is N910C and the version i am using (17.1-20210304-UNOFFICIAL-treltexx) have some bugs. probably it is already mentioned here and you already know about them, but here it is just in case you missed it;

---if i use a wired headphone, the sound is playing from both the headphone and the speaker.

---if i use the phone more than 10 minutes, it gets too warm. and i am not talking about playing games. i read messages on signal message app, i scroll up and down, and phone gets too warm after a while.

---if for example i open a web page in a browser and while the browser loads the page, i scroll down too quickly (too sudden) with my finger, the phone reboots (restarts) immediately. i think gpu or cpu somehow cant handle that.

i am wondering if it would be a good idea, that you lower the cpu and gpu clock speeds. may be the phone wouldn't get too warm, and also it would stop rebooting.

---also i have 2 sim cards from different operators. one of them works without any problem. but when i put the other sim card, it works for a while, but then it says "connection problem or invalid mmi code". i think it is because of the weak signal (bad reception) from the operator. everytime this happens i have to reboot the phone and it starts to work again for a while. is there any way to fix this without reboot? usually people send a message to me saying they are calling me but cannot reach me. (i am getting their message via wifi). then i reboot and message them to try calling me again. only then they can reach me.

sorry for my not so good english. again, thank you so much for your excellent work!
[Galaxy Note 4 Android Development (Exynos)] pepperjones:
It does because it's still listed in the release, so I have no reason to upgrade at all.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Thanks! totally forgot to check mic volumes, will look into it, it is a bit difficult to test VoIP due to the laws here but ill let you know what i find, i did test normal calls and the earpiece sounded good, person on the other side said microphone was fine and no echo was noticed, so i guess i will try to take the values from normal calls and use them in VoIP, just need to figure out why that is not happening

I found an issue with the build were the device fingerprint / lte or 3g configuration is not being set properly per device, this will be fixed next release, not 100% sure it will properly default n910h to 3G but it might help.

Hey mate, you installed a pretty old build from around 2 years ago, most recent lineage-17.1 build is lineage-17.1-20220430-UNOFFICIAL-treltexx.zip you can find all modern releases here https://sourceforge.net/projects/galaxy-note-4-exynos/files/LineageOS-17.1/

Lineage-18.1 builds are also up with more fixes https://sourceforge.net/projects/galaxy-note-4-exynos/files/LineageOS-18.1/

i dont recall what the mmi code / offline fix was, i think it had to do with APNs if im not mistaken, i would try to manually load in your operator's apn in settings, and set network mode to 4G/3G

CPU / power management has been heavily changed in 18.1 but another release is coming with even more changes to address some drain issues, so i would wait for that, but its better to setup your phone on 18.1 as you cant flash 17.1 > 18.1 without clearing some files in /data
[Galaxy Note 4 Android Development (Exynos)] azmtechnic:
Thank you so much @ananjaser1211 for your support.

Phone is set to 3g. But the problem is network mode changing automatically from auto to manual. In auto mode the signal is on UMTS. and signal is perfect. but when network goes to manual by itself, the signal goes to GSM. And signal lost in this mode. However i tryed to set telephony to 0 or 3 on build prob. But it doesn't take effect. I hope you can fix this issue as you said.

And another issue i found in this build:

Gallery is really slow to show contents. and when try to selecting multi content in gallery too. you should tap several times on a picture or video to select it. i don't know other's have same problem or not.

Anyway. Thank you again.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
@pepperjones Hey mate, any particular social media apps i can test with the low volume issues ? ive tested discord (since thats the one i can make two accoutns for easily) and telegram.

the volume in both earpiece mode, speaker mode and video mode was fine, the other side volume was loud and clear, i can push it up a notch but i dont think thats the issue you are facing.

telegram had similar results, didnt need to shout into the phone.

S9 > N4 : Earpiece was loud, speaker was very loud

N4 > S9 : earpiece was loud and much more clear (due to SFX on samsung ROMs), speaker was loud and clear

Other information you might not care about :

When using earpiece and VoIP the path used was

"D/audio_route: Apply path: earpiece-mic"

which enables "main-mic-normal" aka the scenario used for normal recording (that has **** quality + alot of gain boost)

so this ideally would be changed to main-mic-voice to use the same path used in telephone calls

When using Speaker / Video calls and VoIP the path used was

D/audio_route: Apply path: voice-speaker-mic

This path already uses main-mic-voice so no issues there. the only improvement i would do is switch to voice mode.

however the issue i noticed is (probably why im using main-mic-normal) is that earpiece-mic route is also used by 3rd party recorders like Telegram / whatsapp voice notes, so this might be an issue as using the call route for it will produce inaudible recording. so i need to figure out a way to properly separate these routes. something that the current audioHW does not support.

I was working on a new AudioHW based on samsung's official HAL, sadly i did not notice any improvements in recording quality, but it does have much better scenario separation, but it wont be ready for use any time soon as it requires a boatload of work

haven't observed echo (phone was in another room as my brother was reporting results
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Hi. I tried to report back faster but I had forgot about this so I'm writing now (lol).

I have a N916S (tre3calteskt) and had LOS17.1 working fine, tried dirty flashing but it didn't want to work properly so I cleaned all partitions including data and it works now.

While I didn't find any critical bugs while usage the graphics/animations are very slow. The app launching animations are especially slow, and the notification center pull down also shows laggy animations. Scrolling on settings app is similar to the performance on LOS17.

I wonder if this is a known issue. I do not have any kind of GApps or Magisk installed.

Anyway, thanks for your hard work onto getting our N4 working on A11. Cheers.
[Galaxy Note 4 Android Development (Exynos)] pepperjones:
Hi @ananjaser1211, sorry the late reply. On the last RR build that's still on my G-Note, I've faced the issue within the app I use for communication, which is Signal (signal.org).

It happened in two forms, either the audio in the call (either video or just audio) was extremely low from start, or the audio volume started normal and then suddenly dropped halfway in the call.

If I'm not mistaken this also happened when recording videos. I only ever experienced this issue when using your ROMs, previously I was using /e/ OS, which still provides ROMs for this device but got no updates for quite a while.
[Galaxy Note 4 Android Development (Exynos)] khamakelz:
I like this rom ... am still testing it...

i have a problem every time I restart my device am getting a "null imei" which means i have no signal... it only works if I restore an EFS backup from the stock ROM...

using n910c
[Galaxy Note 4 Android Development (Exynos)] imglai:
Could you fork ih8sn for note 4 for people who doesn't want to root their phone
[Galaxy Note 4 Android Development (Exynos)] wildcatacu:
I am experiencing the same issue but unlike you, I have gapps installed (android 11 pico arm). Lawnchair from github as the default home app, too. Scrolling, pulling the notifications, and switching quick setting pages within Settings isn't too bad for me, smooth almost (near 60fps visually). From Lawnchair and Chrome, UI sometimes stutters and isn't as smooth when scrolling in Settings. When using the recommended GCam, quickly previewing shots glitches and flashes (edit: only when animations are turned off from developer options).

Things I've tried to mitigate to no avail:

* Turn window/transition animation scale and animator duration scale all to off

* Remove animations from Accessibility settings

* Set Performance profile to Performance

*Clear Cache from TWRP

*Setting resolution down to 720x1280 with ADB

Other than that and the mic issue, all good. Using Dolby On from Play Store for voice recordings. The quality is a bit better than the stock provided.

I'm a new user from stock and more than happy to provide more insights. My device is N916K. Big thanks @ananjaser1211 for maintaining this!

Edit: While pressure sensitivity works for SPen, palm rejection doesn't. I tested various apps such as PENUP, Squid, MediBang, Google Keep, and Sketchbook. All seem to have a certain issue wherein the stroke is immediately erased when the palm is on the screen. A quick search brought me to this: https://xdaforums.com/t/fix-enable-palm-rejection-for-spen-on-non-stock-roms.4042799/ Can this fix be applied for this ROM? I don't have the proper resources to compile the ROM myself to test it unfortunately.
[Galaxy Note 4 Android Development (Exynos)] TableCraft0R:
Oval icons are in default Styles and Wallpapers
[Galaxy Note 4 Android Development (Exynos)] c0ffyy:
" Further more, i will be compiling PixelExperience 11 and releasing it soon, since sadly there is no RR-OS with android 11. "

No stress no hurry etc im super thankful for everything you do for our old devices.

But im looking forward to this so so so much.

Super big thanks it's awesome some important banking apps in my country stop working on older android versions. Right now the lowest allowed version for banking apps is android 6 so official stock is working.

But what about next year. So all your work really helps.

Keeping our old devices with removable backside alive.

<3
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Could you please share the method for scaling down res?
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
I am not very familiar with that module, i will look into it, i have fixed SN to an extent, i.e it only requires one module to function as opposed to multiple, however i ran across an issue were it seems that the note 4 original fingerprint no longer passes CTS on its own, so i need to figure out a way to get that working.

Another issue that prevents CTS from just working is we run permissive and google does not really like that, so we still have to bypass selinux (and if i use in ROM bypasses for that it refuses to boot, so thats another bug i need to look into or stop delaying and enforce the ROM already)

Performance should improve on the next set of builds, i am running 1080x1920 here with default animations on balanced profile, it runs much better than 1440x2560.

Thanks for the patch for stylus, i will look into it and see if thats something we can implement on 18.1

in termux / terminal emulator or adb shell, type

wm size 1080x1920

wm density 480

(480 or 420 i dont recall excatly which density is ideal for 1080 but feel free to try)

stock values are

wm size 1440x2560

wm density 560