yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
About 64bit

@ripee

So, the note 4 is currently running a 32bit kernel, and maybe even bootloader. I had been researching recently just after I found that exynos 5433 has support on linux mainline, and these are the informations.

1. The Samsung "TM2" phone is the Tizen Mobile 2, and it's basically the note 4 n910 variant. But, it runs 64bit linux.

2. The mainline kernel supports almost everything except the modem for the tm2. This means that if we get 64bit kernel to run we can also get linux mainline, and the latest android too.

So, for 64bit..

1. I found an unmerged patch for samsung tm2 and exynos5433, for getting u-boot. You can check it out here : https://patches.linaro.org/cover/150400/

2. Although I don't really know if it also works on the N4, I applied the patch and fixed issues for building, and you can get it from here : https://github.com/ahisky/u-boot

3. To debug if it actually works, we need a uart cable.

And, for cable uart..

1. We need to short ID pin and GND (earth) pin, and put a 619 kOhm resistor between them.

2. I found some useful guides for it, check it out

- https://redmine.replicant.us/projects/replicant/wiki/SamsungSerial (How it works for other older samsung; similar to this target except resistor value)

- https://wiki.postmarketos.org/wiki/Micro-USB_Interface_Controller (619kOhm)

- https://wiki.postmarketos.org/wiki/Serial_debugging:Cable_schematics#USB_debug_cable (How to and which pins for which)

If the AOSP kernel gets rebased onto newer mainline, and we get linux mainline working before they rebase later then the newer aosp common kernel would even get to contain the n4 support, and this way we can reduce kernel works too. The target device's specs aren't bad, it's fully capable of newer softwares, it's just the software issue, so I think this would be a good chance to completely mainline and/or get 64bit.

Soo, I'm gonna try buying the cables (I can't easily; I'm a student. Gotta request to my parents!), and if you're interested, since this is about also getting android 64bit in it.. I just leave comment here. Thx!

(And thank you ananjaser1211 and ripee for making rom for this old (but still very cool) device!)

Or, the other way. (Added later):

Maybe, something different could had been done on the tm2, on the bootloader side. #linux-exynos folks also didn't really know much about that. So maybe, our device's bootloader may be uncompatible with 64bit anything, at all.

So, although it ain't android, maybe, we can edit the exynos 5433 patches, and tm2 patches and make it armv7 instead of aarch64. And then it would boot on our stock 32bit-only s-boot.

If we get mainline to run with 32bit, although we can't get newer android, we can still get security patches and new OS for the phone, since we have mobile linux distributions like Mobian or postmarketOS. We can get them to run on our phones too, if we work on the kernel to 32bit.
[Galaxy Note 4 Android Development (Exynos)] Menelkir:
I would gladly test it, even if it's postmarketOS (being there, done that, I didn't had too much luck trying to make postmarketOS happens, I'm lacking the proper knowledge).
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
So, I have the tre3calte board (N916S), which variant do you have?

It would be nice if you can try compiling and booting u-boot. And if you can, please try buying the uart cable and testing if it actually works or not. Thanks.

For u-boot you can just fork my github and merge latest mainline u-boot patches and build and install to the boot partition.

You need to make it a boot.img format, by following the guide on postmarketOS wiki for porting u-boot

And for linux mainline, after we are sure that u-boot works then we can just rename the two tm2 dts and make it n4 dtses
[Galaxy Note 4 Android Development (Exynos)] Menelkir:
I have the n910c. The problem is, postmarketOS have already a lot of issues for this one and I'm not sure how to go forward to make something usable.

I don't think I'll be able to get this cable working, my guess I can't direct flash the u-boot without messing up hard, right?
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Issue on postmarketOS is because it's a downstream kernel port.

So, right here flashing the mainline kernel or u-boot is very easy. You just have to compile and flash with twrp.

The hard part is, to know if it actually works or not.

For example, that u-boot, it may not work at all. But maybe it also had worked. u-boot doesn't show anything on screen or usb, so we cannot know without that debugging cable.

If we don't have the cable, we won't be able to make much progress, that's why. I'd try buying it though, although may take time.
[Galaxy Note 4 Android Development (Exynos)] atomxdaii:
Hi,

Newbie here.

First thank you for a wonderful rom for the Note 4.

Any help is much appreciated for i need a health apk with SP02 measurement that can work with this rom

Had tried a few but cannot wor.
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
get a medical certified device, don't rely on a PHONE to do it
[Galaxy Note 4 Android Development (Exynos)] soad26:
Can someone help me. After installing the rom and micro gapps, i always get the "couldn't sign in, there was a problem communicating with google servers" whenever i try to sign in to play store or add my google account.

I'm connected to wifi, i can browse the internet, ly time is correct. Did i miss something? My device is 916s

Edit#2: after 24 hours, i still find no success with my issue. This also happens on the RRQ rom. I've formatted, clear cache, and reset everything. I find no errors in flashing the gapps in twrp. This is really frustrating! Google just don't want to connect to servers whenever i try to add a google account. Please, someone, help me
[Galaxy Note 4 Android Development (Exynos)] dck.rgga:
plz.. make lineage 16/ 15/14 for my samsung galaxy note 4 (n910U)
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
he doesn't have a phone to work on it, it's difficult to do it blindly
[Galaxy Note 4 Android Development (Exynos)] CesarB794:
I have a SM-N910C and sim card won't work :(

Maybe detect the sim carrier, but says me "Emergency call only".
[Galaxy Note 4 Android Development (Exynos)] dck.rgga:
hmm. i so sad :(
[Galaxy Note 4 Android Development (Exynos)] Standardstaples25:
I'm new here. Just want to know if the S pen works in this rom?
[Galaxy Note 4 Android Development (Exynos)] soad26:
Work just like a stylus. No Spen features, stylus button is useless
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
you can read more here about how to use SPen in AOSP, of course with some limitations - don't expect dedicated samsung functionalities

https://xdaforums.com/t/tips-to-enable-s-pen-features-on-cm-aosp-roms.3504865/
[Galaxy Note 4 Android Development (Exynos)] Standardstaples25:
Thank you. 👍
[Galaxy Note 4 Android Development (Exynos)] Pitec:
any news on when the final/latest version of LineageOS 17.1 is coming out? my note 4 is missing it badly:)
[Galaxy Note 4 Android Development (Exynos)] Menelkir:
How about the pins near the battery? None of them can work as a JTAG or something?
[Galaxy Note 4 Android Development (Exynos)] mixxlegend:
Huge respect for people having time developing this, anybody knows when "unofficial" will become "official"? I want stable version of lineage os so bad that i miss my samsung galaxy s4 with lineage os 16 with 0 bugs, yet with note 4 people are working on 17.1 and don't even have stable LS 16... and now starting developing LS 18 lol... divided focus is never good... if you guys just finish to the end one of this versions it would be so awesome... till then im on stock 6.0.1 :)
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
never

lineage os will never pick up the development of this old device or any other the like

before judging why the development is going as it is, maybe try to read a bit and understand what custom ROM development is with closed sources

until then, please do enjoy your stock marshmallow

some of us are just crazy and brave enough to fight a war of technology so that many like you shouldn't have to

have a nice day
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
We already know the UART part.

I don't really know about the pins near battery, no info.

We need the cable to see bootloader logs, but unfortunately I still couldn't buy it.

(It'd be nice if someone here manages to make a working cable!)

Thanks.
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Hey, the LOS17 is stable enough. Unofficial doesn't mean it's more unstable than Official. (Although sometimes, that's true)

Just use the stock TW if you want, or the RefindNougat TW 7.1.2 rom that has not much bugs, only the finger print sensor doesn't work.
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Some will need to buy parts like this for uart.

https://www.adafruit.com/product/3972 (USB port breakout)

https://www.aliexpress.com/item/4000216010101.html (UART adapter that works for multiple voltage)

https://www.aliexpress.com/item/32834077930.html (Resistor needed to make the phone's usb port to be uart mode)

(And if you don't have, need jumper wires like this https://www.aliexpress.com/item/4000203371860.html )

After it, you need to assemble them. Pin maps available on postmarketOS wiki.

The resistor needs to be bought as 620K ohm. (the uart thingy needs 619k ohm but we can't buy that, and 620k also works)

After we assemble, IDK if it's 3.3v or 1.8v, so someone should maybe buy two uart adapter and break one to find out, or buy a multimeter to find out the voltage value.

WIth these all, connect the adapter to PC and you get the logs. (Probably baud rate is 115200)
[Galaxy Note 4 Android Development (Exynos)] bigroots:
interesting. I was having random reboots, more than once every 24h, 95% of the times right after unlocking the phone when in sleep. It was enough to discourage me using the phone as a daily tool. After reading this post, it clicked in my mind that I was using a clock with weather forecast on the actual location, so presumably the clock widget was trying to update the forecast (therefore the location) at the moment the phone was unlocked.

Not having the computer with me I could not collect the data/tombstones, so I went for trial-and-error. Just to change something in the GNSS system, I first tried to set "Force full GNSS measurements" in the developer options, and the phone survived without spontaneuous reboots during 36h. Then I allowed again the GNSS system to duty cycle, removed the widget with weather forecast and ... still not random reboots. Now ... I do not take it as a guarantee that this is the actual problem, but at least as a serious suspicion.
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Pressure function works but not the button.

with ibis paint or something it works quite well
[Galaxy Note 4 Android Development (Exynos)] LegendOcta:
Intersting. I'm using it without much apps, especially not the widgets, and I'm also using without the GAPPS and the phone stayed for almsot 1 month uptime properly working. (Rebooted after to test something)

Maybe try removing gapp and those apps and use again?
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
ive been a bit too occupied with other projects, i will push new builds as soon as possible with fixes to some random reboots related to GNSS that @bigroots mentioned, we found the culprit and it should be fixed in upcoming releases.

i was attempting to fix audio mic quality but results are not full yet, so that might not make it sadly.

regarding the official/unofficial comment, in order for our device to become official we first have to enforce the kernel and add sepolicy rules, which is not trivial but time consuming, the other more important aspect is that we must have a "zero" bug system. that involves fixing the video camera in stock app. so far that is not possible and not being pessimistic but unlikely to happen. as its not only me working on that issue, but the exynos5420 official lineage team with much smarter people are trying to solve it too, however sadly neither of us had any luck.

the last part is i will have to recreate our lineage trees (and kernel) to be more "tidy" as right now our work is built upon years of trials and errors that clutter the git history, also not trivial but very time consuming,

if we manage to do these things, we can do the official label and get builds signed by lineage build system and OTA updates. aside from that there isnt much difference so i am not really pursing that at the moment, i will consider it when/if we fix the video camera problem.

and for lineage 18.1, i am currently not working on it, the exynos5433 org has 18.1 trees for the Tab S2, but i dont feel comfortable yet in pursing that as 17.1 still has plenty of bugs to iron out, a bigger version isnt important at the moment. and i dont really have the time anyways for it, it will be coming in the future as i am not ditching this device, but not any time soon.
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
many thanks again for you passion and efforts Anan

years behind this device gave us a glimpse of the patience rewards

enjoy life bradar :)
[Galaxy Note 4 Android Development (Exynos)] retiredtab:
There's the possibility of manually editing the manifest.xml file to switch to gnss hwbinder for more advanced users to try. It may or may not work as I don't have a Note 4. See post #18

https://xdaforums.com/t/troubleshoo...-version-of-android-10.4308203/#post-85434311

If it doesn't work, simply reflash the last rom over it.

There's a whole laundry list of things that a rom must meet. Details at

https://github.com/LineageOS/charter/blob/master/device-support-requirements.md
[Galaxy Note 4 Android Development (Exynos)] qq1226737590:
Can you make a trhpltexx (N910U) version,please.
[Galaxy Note 4 Android Development (Exynos)] papajek23:
i tested on my n910s.. not working . stack only on logo.. please make it work in our note4
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
We are overdue for an update aren't we..
[Galaxy Note 4 Android Development (Exynos)] papajek23:
can you help me? im using n910s .. its stock in samsung logo
[Galaxy Note 4 Android Development (Exynos)] muzliamir:
Wipe dalvik cache in recovery .. if same cases , flash stock firmware again
[Galaxy Note 4 Android Development (Exynos)] papajek23:
Thank u so much.. !! I downloaded the zip uploaded by kokosei in telegram and boot IMG.. Its now working ... Thank you so much..
[Galaxy Note 4 Android Development (Exynos)] clewis.it:
Oh yes, the 910c needs a little love.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Good news, "one of the biggest issues that prevented me from doing lineage 16 has been resolved. sdcardfs and WiFi."

If i manage to keep up this pace, the next update will be sweet. im also working on patches for the RIL and video camera. among other stuff
[Galaxy Note 4 Android Development (Exynos)] kidkree1:
Great work, still waiting on the bugs to get worked out then I will upgrade from your port Refined Nougat N7FE Port 6.0. Hope they get worked out soon looking forward to the new build.
[Galaxy Note 4 Android Development (Exynos)] Gentlemenc:
I wish too lucks to you for great works...
[Galaxy Note 4 Android Development (Exynos)] J73:
I just want to say thanks for this ROM.

I've been looking for any vanilla ROMs for my Exynos Note 4 and thank god I came across this thread.

I installed the experimental version because I have slow speeds on androidfilehost. Looking forward to this! Thanks again.
[Galaxy Note 4 Android Development (Exynos)] vadimevsykov:
s pen ??

Not bad !!! Everything works perfectly. Can I add a program for working with s pen ???
[Galaxy Note 4 Android Development (Exynos)] krakowiak84:
Great job. Works fast, doesn't reset.

wifi works, there is only a network problem (RIL). He often loses it and cannot log in. I'm testing the rest ...
[Galaxy Note 4 Android Development (Exynos)] Menelkir:
SPenCommand is probably what you want.
[Galaxy Note 4 Android Development (Exynos)] pol-der:
[MENTION=4637718]ananjaser1211[/MENTION],

Thanks for this Oreo ROM!

N910C:

*SIM Card is not recognized (tried the solution in Q/A but not worked. Rebooted and tried again but no luck. Wiped Dalvik/Cache but not worked. Tried 3G and LTE but not worked.)

*Fingerprint is working mysteriously!

Could you please tell me what i supposed to do about SIM Card issue? For now everything is working fine. I will test Encryption feature when battery is fully charged.

P.S: Is there any ETA about update from BETA to STABLE?

EDIT: Backed up LOS 14.1 EFS partition and restored on 15.1 (current) but not worked again.

EDIT2: Backed up N910C stock ROM EFS partition and restored on 15.1 (current) and worked! Here are the steps:

1) Flash stock ROM with Odin

2) Turn on the phone and check network. If it is not working reboot recovery and make Factory Reset and Wipe Cache. Reboot and check network again. This time it will work.

3) Flash latest TWRP and back up only EFS partition.

4) Fresh install 15.1 and check network. Most probably it will not work.

5) Reboot recovery and restore stock ROM's EFS partition.

Voila!

EDIT3: Encryption is not working. When enabled encryption phone rebooted in 2 seconds and network is gone again. Do not try this.

EDIT4: Rebooted phone and network is gone again. Repeated same steps but no luck. Waiting update..
[Galaxy Note 4 Android Development (Exynos)] Rasoir:
We're waiting for update.
[Galaxy Note 4 Android Development (Exynos)] pol-der:
Do you know is there any ETA about LOS 16.0?
[Galaxy Note 4 Android Development (Exynos)] Rasoir:
I think there isn't any ETA about it but You can check official Telegram channel.
[Galaxy Note 4 Android Development (Exynos)] pol-der:
Thanks for the info. Btw i updated my latest comment and it is working fine.
[Galaxy Note 4 Android Development (Exynos)] hussein995:
Good luck
[Galaxy Note 4 Android Development (Exynos)] retiredtab:
@bigroots , the tombstones are key as they tell you what process is crashing. On S2 exynos5433, the crash messages looked like what is documented in this commit.

https://github.com/universal5433/an...6a5336751fce3691dec5f07093b0f5214a65e07a49a1e
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Thanks for the list!

We currently fail on

Devices SHOULD support any additional audio configuration inherent to their device (eg. echo cancellation, extra mics, etc).

All Camera HAL versions accessible with the device's Camera HAL MUST comply with the Camera and Video Recording requirements.

Device trees MUST support a lineage.dependencies file for breakfast command & roomservice to be functional.

All devices MUST NOT implement any form of clock manipulation (underclocking, overclocking, etc.) for any processor (CPU, GPU).

All devices MUST NOT implement any form of hardware voltage manipulation (undervolting, custom voltage tables, etc.).

All devices MUST NOT implement any form of custom KSM driver (UKSM, etc.).

All devices MUST be configured for SELinux Enforcing.

Devices MUST NOT use non-PIE binaries

Devices SHOULD use the global extraction script (located in vendor/lineage).

I can see a way around all of those except the non-PIE binaries, if thats the case, devices from Galaxy S7* series and older cant see official lineage. so i am not sure about this clause, i will have to look more into it and ask few people.

if that was really the case, sadly under no circumstances will we ever get official builds
[Galaxy Note 4 Android Development (Exynos)] agtherluyd:
The last build is very good, few bugs, most of them do not bother me in normal use. About the Camera, I've gotten used to footej to the point of installing on the devices from here home, the only bug that can sometimes bother is the audio leak, with the headset connected, the sound sometimes does not come out through the headset, comes out through the speaker, just restart to solve the problem, this did not happen to me with Bluetooth headphones.

It happened to me very few reboots, however, very random, could not say what was the circumstance of the reboot, the battery is in normal use, the inaccurate indicator of the network signal still persists (marking empty, half or full), the previous build was more accurate.

Overall, I'm finding the build very good, in these 3 months that was released, for me it is very close to stability, I do not think we need an official label of LineageOS, and the unofficiais builds of XDA are already good, it is very little to be perfect.
[Galaxy Note 4 Android Development (Exynos)] agtherluyd:
I do not believe that the official seal of LineageOS will change much in relation to us, that we already have access to XDA, besides being impossible to achieve 100% stability with a new system and an old device, it is already 8 years from the release of the Note 4, today has hardware of an incoming mobile phone 2021, but fully functional

LineageOS helped many who like to explore the Android system to the limit, CyanogenMod who started all this, but LineageOS managed to expand facilitating the system ports, we have LineageOS up for Nintendo Switch, each time the LineageOS project tends to improve, especially for unofficial builds, that we can do whatever we want with the system, thanks to free Android and the easy tools of LineageOS
[Galaxy Note 4 Android Development (Exynos)] numba1icon:
Can someone tell me what country f8 is from? 2nd and 3rd numbers of serial number. Just seeing if I got an official update not registering. Also, does this rom add volte support? I'm running a sm-n910c.
[Galaxy Note 4 Android Development (Exynos)] ananjaser1211:
Oh wow i have not pushed the audio leak fix yet ? my bad guys...i assumed the public build is the one with encryption / audio leak fixes etc, i sure dropped the ball on that.

as a temporary solution, you could replace the library manually in your ROM.

proprietary_vendor_samsung/trelte-common/proprietary/system/lib/libaudioroute.so at lineage-18.1 · universal5433/proprietary_vendor_samsung

Exynos5433 vendor tree. Contribute to universal5433/proprietary_vendor_samsung development by creating an account on GitHub.

github.com

Download this library, and copy it to "system/lib"` replacing the existing libaudioroute, you can use FX Explorer, or any root file explorer that can mount system as R/W (so most of them)

this will fix the issue that causes audio to leak out to speaker, and will increase audio route stability from/to calls and other scenarios.

the reboot sadly is a bit more cumbersome to fix manually, the previous post by @retiredtab does explain the process. the manifest file can be found at "system/vendor/etc/vintf/manifest.xml"

Good news is, apparently the PIE clause was for something totally different, and we wont have issues with it, lineage member stricted explained to me what it meant.

but true, getting official status wont matter much. but i ofcourse it would be very rewarding and "cool" to manage to re-enlist what was previously a device dead on nougat.

i am still surprised that this thread is even still active, and that people still use the note 4. this is the main thing that keeps me motivated and working on this old device. the community is still here after all those years!

LineageOS Statistics

stats.lineageos.org
[Galaxy Note 4 Android Development (Exynos)] w41ru5:
If you can use google, you will find this :

Latest Samsung GALAXY Note 4 firmware

Download the latest Samsung firmware for GALAXY Note 4 with model code SM-N910F. Check out our free download or super fast premium options.

www.sammobile.com

as for VoLTE - we have a miracle box in this forum, it's called "search"

hint: it's very clearly stated if you can use it. or not.