![]()
Comprehensive Camera Help Guide for Samsung Galaxy Note 3 SM-N900 (ha3g)
We understand the frustration that comes with installing a custom ROM on a legacy device like the Samsung Galaxy Note 3 SM-N900 (ha3g). The Resurrection Remix ROM offers incredible customization and breathes new life into older hardware, but the loss of stock camera functionality is a common hurdle. The proprietary Samsung camera drivers and image processing algorithms are often difficult to replicate in open-source Android builds, leading to the degraded image quality and bugs you are experiencing.
This guide is dedicated to restoring your device’s camera capabilities to their full potential. We will explore a variety of methods, ranging from advanced software configuration and Magisk Module implementations to kernel-level adjustments and alternative application suites. Since you mentioned removing root access to install Resurrection Remix, we will first address how to regain root capabilities, which are essential for the most effective solutions.
Understanding the Camera Limitations on Custom ROMs
The Samsung Galaxy Note 3, codenamed ha3g (international Exynos variant), utilizes a specific set of hardware components that require proprietary vendor libraries to function correctly. The stock Samsung TouchWiz firmware includes these libraries, but most AOSP-based custom ROMs like Resurrection Remix rely on open-source drivers.
The Role of Vendor Blobs
Vendor blobs are binary blobs provided by the manufacturer (Samsung) that allow the Android Open Source Project (AOSP) to communicate with hardware. For the camera, these blobs handle image signal processing (ISP), autofocus, noise reduction, and color correction. When these are missing or improperly configured, you experience:
- Low Resolution: The camera app may default to a lower resolution sensor setting.
- Slow Performance: Shutter lag and slow focus.
- Crashes: The camera app force-closes when attempting to switch modes (e.g., HDR, video).
- Poor Quality: Overexposed, underexposed, or grainy images due to lack of post-processing.
Resurrection Remix Configuration
Resurrection Remix often includes device-specific settings that can toggle between open-source implementations and proprietary Samsung frameworks. We need to investigate these settings first.
Checking ROM Settings
Navigate to Settings > Resurrection Remix Settings > Misc Interface. Look for a sub-menu labeled Camera or Hardware Keys. Depending on the specific build version of Resurrection Remix you are running (e.g., RR-N-v5.8.5), there may be a toggle for “Stock Camera HAL” or “Samsung Framework Support.”
- Enable Samsung Framework Support: If available, this attempts to load the necessary Samsung libraries. A reboot is usually required.
- Camera2 API Overrides: Ensure that the Camera2 API is enabled in the developer options. This allows third-party apps to access manual controls and higher-resolution modes.
Regaining Root Access via Magisk
You mentioned that you removed root access to install Resurrection Remix. To utilize the most powerful fixes—specifically Magisk Modules designed for the Note 3—you must re-root your device. We recommend using Magisk rather than SuperSU, as Magisk offers systemless modifications which are safer for custom ROMs.
Prerequisites for Rooting
- A custom recovery (TWRP 3.0.0-1 or higher recommended for Note 3 ha3g).
- The latest Magisk.zip file (v27.0+).
- A full backup of your current data (ROM and internal storage).
Installation Steps
- Download: Download the Magisk.zip file and place it on your device’s internal storage or SD card.
- Reboot to Recovery: Power off your device completely, then hold Volume Up + Home + Power to boot into TWRP Recovery.
- Flash Magisk: In TWRP, tap Install, locate Magisk.zip, and swipe the slider to flash.
- Reboot System: After flashing, reboot your system.
- Verify Root: Install the Magisk Manager app (if not installed automatically). Open it and check that “Installed” in the Magisk column shows the latest version.
Once root is confirmed, we can proceed with installing modules that specifically target the ha3g camera issues.
Magisk Modules for Camera Restoration
The Magisk Module Repository is an excellent resource for finding community-developed fixes. While generic modules exist, we need to look for those compatible with the Samsung Galaxy Note 3 Exynos variant.
Recommended Modules for ha3g
Samsung Camera 3.3.1 Magisk Module
For the Note 3, the stock camera application (TouchWiz Camera) version 3.3.1 is often considered the most stable on custom ROMs. This module ports the stock Samsung camera app and its dependencies to AOSP-based ROMs.
- Functionality: It installs the Samsung Camera APK and the necessary vendor libraries (libexynoscamera.so, libsec-ril.so) into the system partition in a systemless manner.
- Installation: Download the module zip file from the Magisk Module Repository. Open the Magisk Manager app, go to the Modules section, tap Install from Storage, and select the downloaded zip. Reboot immediately after installation.
- Verification: Check if the “Samsung Camera” app appears in your app drawer. Test basic functionality: taking a photo, switching to video mode, and using the flash.
Camera2 API Enabler / HAL3 Enforcer
If the stock Samsung camera module causes conflicts, you may prefer using the Google Camera (GCam) port. However, GCam requires a Camera2 API implementation that supports the HAL3 level.
- The Fix: Some custom ROMs disable Camera2 API by default to save resources. A Magisk module called “Camera2 API Enabler” can force the feature on.
- Implementation: This module modifies the
build.propfile (systemless) to setpersist.camera.HAL3.enabled=1andpersist.camera.max.jpeg.size=1. This is crucial for running GCam ports on the Note 3.
EIS and OIS Stabilization Fixes
The Note 3 hardware lacks Optical Image Stabilization (OIS) but supports Electronic Image Stabilization (EIS) for video recording. Stock Resurrection Remix often disables EIS to prevent processing overhead, resulting in jittery video.
- The Fix: Look for modules tagged “EIS Enabler” or “Video Stabilization Fix” in the repository. These modules tweak the media encoder profiles to utilize the Exynos 5420’s video processing capabilities.
How to Use the Magisk Module Repository
Since your repository is located at Magisk Module Repository, we recommend filtering your search for keywords like “Samsung Camera,” “Note 3,” “Exynos,” or “ha3g.”
- Navigate to the repository on your device.
- Download the module zip file directly to your storage.
- Ensure you have active root (Magisk) before attempting installation.
- If a module causes a bootloop (rare but possible), you can always reboot to TWRP, go to Advanced > File Manager, and delete the module script located in
/data/adb/modulesto remove it.
Manual Configuration via Build.prop and Libs
If Magisk modules are not available for your specific Resurrection Remix build, or if you prefer a manual approach, you can manually inject the necessary camera libraries and properties. This requires a root-enabled file manager (e.g., Mixplorer) or a terminal emulator.
Modifying build.prop
The build.prop file in the /system directory controls many system parameters. We need to add specific lines to optimize the camera for the Exynos 5420 SoC.
Open your file manager with root access and navigate to /system.
Edit build.prop and add the following lines:
# Camera Fix for Exynos 5420 (ha3g)
persist.camera.HAL3.enabled=1
persist.camera.mode.camera2=1
media.stagefright.1080p=1
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
persist.sys.camera.camera2=true
Explanation:
persist.camera.HAL3.enabled=1: Forces the Hardware Abstraction Layer (HAL) to version 3, enabling advanced features like RAW capture and manual shutter speed control.ro.media.dec.jpeg.memcap=8000000: Increases the memory cap for JPEG decoding, preventing crashes when processing high-resolution images.
Pushing Proprietary Vendor Libraries
The most critical step is ensuring the correct shared object files (.so) are in the correct paths. For the ha3g model, the libraries should ideally be located in /system/lib64/hw (for 64-bit processing) or /system/lib/hw.
Files to look for (from a stock TouchWiz ROM dump):
camera.exynos5.solibexynoscamera.solibcamera_client.solibmmcamera_plugin.so
Procedure:
- Extract these files from a stock firmware ZIP for the SM-N900.
- Using TWRP or a root file manager, push these files to
/system/lib64/hw/. - Set permissions: Long press the file, select Properties, and set permissions to 644 (RW-R–R–).
- If you are using an AOSP ROM, you may need to rename
camera.exynos5.sotocamera.vendor.exynos5.soand symlink it.
Warning: Manually pushing libraries without a Magisk module (systemless method) modifies your system partition. If you ever need to pass SafetyNet or update the ROM, you will need to reflash your ROM. Using Magisk modules is always safer.
Alternative Camera Applications
If the kernel-level fixes are too unstable or you cannot regain root, switching to a different camera application that uses the limited open-source drivers effectively is a viable alternative. You mentioned trying paid apps, but there are specific open-source projects optimized for legacy Samsung devices.
Open Camera
Open Camera is an open-source camera app that does not rely on proprietary Samsung frameworks.
- Pros: Highly configurable, supports Camera2 API, allows manual ISO and exposure control.
- Cons: Image processing is entirely software-based, so low-light performance on the Note 3 will be worse than stock.
- Configuration for ha3g:
- Go to Settings > Photo Settings.
- Set Image Quality to 100% (do not use 95%).
- Enable DRO (Dynamic Range Optimization) to compensate for the sensor’s age.
- In Video Settings, set Video Stabilization to Auto (this relies on software EIS, which the Exynos 5420 handles reasonably well).
Footej Camera 2
Footej is a paid app, but it is often less buggy than GCam on older devices because it has a more forgiving buffer implementation.
- Focus: It is excellent for JPEG burst mode, which the Note 3 hardware supports well.
- Settings: Use the “High JPEG Quality” mode. Disable “Zero Shutter Lag” if it causes the app to freeze, as the Note 3’s eMMC storage speed is a bottleneck.
GCam Port (Google Camera)
Getting Google Camera to work on the Note 3 is difficult but possible with the right APK and XML configuration files.
- APK Version: You need an older version of GCam, such as GCam 4.4 or GCam 5.1, as the Note 3 lacks the Neural Network APIs required for GCam 7+.
- XML Configs: Search for “GCam Configs for Exynos 5420.” You will need to load an XML file that configures the gcam settings specifically for the Note 3’s sensor size and processing capabilities.
- Libraries: Some GCam ports allow you to load “Libs.” For the Note 3, loading a “Google Lib” or “Sultan Lib” can improve sharpness and dynamic range.
Troubleshooting Common Camera Issues on Resurrection Remix
Even with the fixes above, you may encounter specific bugs. Here is how to address them.
Camera App Crashes on Launch
If the camera app force-closes immediately after the Resurrection Remix logo:
- Clear Data: Go to Settings > Apps > Camera (or Android System WebView) and clear data/cache.
- Wipe Cache/Dalvik: Boot into TWRP and wipe Dalvik/ART Cache and Cache (do not wipe Data or Internal Storage).
- Conflict Check: If you have both the Stock Camera app and Open Camera installed, try uninstalling one. Sometimes having multiple camera apps causes permission conflicts in AOSP.
Purple/Pink Tint or Green Lines
This is a hardware acceleration issue related to the Exynos GPU drivers in custom kernels.
- Solution: Switch to a kernel that supports older GPU drivers or disable “Hardware Overlays.” To do this, go to Developer Options and look for “Disable HW Overlays” (or “Force GPU Rendering”). This will tax the CPU more but may eliminate color artifacts.
Autofocus Hunting
The Note 3 autofocus motor is mechanical and can be noisy or slow on custom ROMs.
- Solution: In the camera settings, try setting the focus mode to “Infinity” or “Macro” manually rather than relying on “Auto.” If using Open Camera, enable “Touch Focus Lock.”
Video Recording Audio Sync
On custom ROMs, video audio and video streams sometimes desync over time.
- Solution: This is often a kernel issue. If you are using a custom kernel (e.g., from XDA forums for Note 3), ensure you are using a stable “Daily Driver” version, not an experimental one. If you are on the stock Resurrection Remix kernel, try recording at 1080p/30fps instead of 60fps, as the audio encoder on the Exynos 5420 struggles with higher frame rates on Nougat (Android 7).
Advanced: Flashing a Stock-Based Camera Port
If Magisk modules are insufficient, the ultimate solution for the SM-N900 (ha3g) is to flash a “Stock Camera Port” zip file via TWRP. These are often found on XDA Developers or specific Telegram groups for Note 3 development.
The “OneUI Port” Attempt
While newer OneUI ports are heavy and generally unstable on the Note 3, some developers have successfully ported the Samsung Galaxy S5 (SM-G900F) camera libraries to the Note 3. The S5 shares similar hardware architecture with the Note 3 (Snapdragon 801/Exynos 5420).
- Why this works: The S5’s TouchWiz camera app is highly optimized for the same generation of sensors. By flashing a zip that replaces the Note 3’s camera libraries with S5 equivalents, you gain features like “Shot and More” and “Virtual Tour.”
- Risks: This modifies system files. You must have a NANDroid backup before attempting this.
Kernel Modification
For advanced users, editing the kernel parameters via Franco Kernel Manager or Kernel Adiutor (requires root) can yield results.
- Scheduler: Change the I/O scheduler to “Sio” or “Row” for the eMMC storage. This speeds up write speeds for JPEGs and video files, reducing lag.
- CPU Governor: Set the governor to “Interactive” or “OnDemand” when the camera is open. The Exynos 5420 is a big.LITTLE architecture; ensuring the A15 cores (performance cores) are active when the camera app launches is crucial for stability.
Summary of Steps for SM-N900 ha3g
To resolve the camera quality issues on Resurrection Remix for your device, we recommend the following prioritized workflow:
- Root with Magisk: Reinstall Magisk immediately to allow systemless modifications.
- Install Magisk Modules: Browse the Magisk Module Repository for a Samsung Camera module specifically for Android 7 (Nougat) and the Exynos 5420 chip.
- Configure build.prop: If modules are unavailable, manually edit the
build.propto enable Camera2 API and increase memory caps. - Use Open Camera: If the stock app remains unstable, use Open Camera with DRO enabled for the best compromise between performance and stability.
- Update/Change Kernels: If you experience persistent lag or color issues, look for a custom kernel on XDA that is specifically optimized for the ha3g variant of Resurrection Remix.
By leveraging the systemless root capabilities of Magisk and the specific hardware optimizations for the Exynos 5420, we can significantly improve the camera performance of your Galaxy Note 3. It requires patience and careful module selection, but the results will bring your device back to usable photographic standards.