Skip to content
Gate 180 180° · 4:3 OG
ImpressumPrivacyTerms[DE]

Turning off oversharpening and shooting 16-bit RAW Bayer on Android

Engineering note on how Gate 180 handles Camera2 pipelines, why stock phone video falls apart in grading, and when to pick 10-bit YUV over 16-bit RAW.

Drop video from a modern phone next to an A-cam in DaVinci Resolve and the giveaway is almost always edge sharpening. Almost every phone camera app runs aggressive contour sharpening around hair, foliage, and eyelashes, then smears flat skin with heavy temporal noise reduction to hide the sensor grain it just amplified. Once those white halos and smeared shadows are baked into an H.265 stream, you cannot grade them back out.

Gate 180 gives you two ways around that, depending on what the shot needs.


Option 1: 10-bit Zero-Edge YUV (ISP_BYPASS_YUV)

This is the default mode when you open the app. It still uses the phone's hardware video stream, so you keep high frame rates (up to 4K 60 fps, and 120 fps on phones that actually expose it in Camera2) and lower battery draw.

Instead of accepting the manufacturer's consumer look, Gate 180 turns off the stock post-processing flags on every capture request (EDGE_MODE_OFF, NOISE_REDUCTION_MODE_OFF, HOT_PIXEL_MODE_OFF, and electronic video stabilization off) and applies a gentle 32-point log-shoulder tone curve. On Android 13 and newer, it records into 10-bit HLG10 (BT.2020) when the lens supports DynamicRangeProfiles.HLG10.

One catch we ran into early in testing: some phone makers silently ignore manual Camera2 flags in firmware. A capture request asks for EDGE_MODE_OFF, and the HAL quietly hands back sharpened frames anyway. Because of that, Gate 180 reads back TotalCaptureResult on every frame through HalIntegrityMonitor. If the firmware overrides our request for three consecutive frames, the HUD tells you instead of pretending the bypass worked.


Option 2: Live 16-bit RAW Bayer GPU Debayer (RAW_BAYER)

When you want zero OEM ISP involvement at all, you can switch to RAW BAYER 16B from the format popover on any lens that supports RAW_SENSOR fast enough for 24p/30p.

Here is what happens on every frame:

  1. Camera2 hands over raw 16-bit Bayer CFA data (RGGB, BGGR, GRBG, or GBRG) before the phone's ISP sharpens, denoises, or tone-maps it.
  2. We upload the raw sensor buffer directly to the GPU (GL_R16UI), subtract per-channel black levels (SENSOR_DYNAMIC_BLACK_LEVEL / SENSOR_BLACK_LEVEL_PATTERN), and normalize against the sensor white level.
  3. An OpenGL ES 3.2 fragment shader runs a 5x5 Malvar-He-Cutler gradient-corrected demosaic into linear 16-bit floating point (GL_RGBA16F). On step-edge test targets, overshoot is 0.0.
  4. Color is solved from the physical lens's dual-illuminant factory DNG matrices (interpolated between Standard A 2856K and D65 6504K, white-balanced with the four RGGB channel gains, inverted into CIE XYZ, adapted via Bradford to D65, and mapped into Rec.709 or BT.2020).
  5. The reconstructed image goes straight into a standard hardware-encoded .mp4 (10-bit HEVC HLG10 or Rec.709) or a full-sensor .jpg/.heic still.

One subtle quirk we had to fix on Samsung hardware: the Galaxy S25 (SM-S931B) caps analog sensitivity on RAW_SENSOR frames at ISO 403. Above ISO 403, raw frames stop getting brighter even if you dial ISO 800 or 1600. Gate 180 reads SENSOR_MAX_ANALOG_SENSITIVITY and multiplies the linear post-RAW signal by the exact missing ratio (appliedIso / maxAnalogSensitivity) so RAW BAYER exposure tracks ISP_BYPASS_YUV cleanly in dim rooms.


Why MP4 instead of CinemaDNG folders?

Writing uncompressed CinemaDNG sequences fills a 256 GB phone in minutes, forces you to carry an SSD even for quick b-roll, and adds a transcoding step before you can cut anything. Gate 180 does not write CinemaDNG image sequences. The goal of RAW BAYER 16B is to skip the OEM's sharpening and denoising completely while still landing in a normal .mp4 file that drops straight onto a timeline in Resolve or Premiere at 35, 80, or 150 Mbps.


Honest trade-offs between the two modes

10-bit Zero-Edge YUV16-bit RAW Bayer GPU
Frame rates23.976 to 120 fps (HAL dependent)23.976 to 30 fps
Heat & batteryLower; suited for long continuous takesHigher GPU load; best for controlled shots
OEM ISP involvementBypassed via Camera2 flags (audited)None (raw CFA debayered on GPU)
Still frame resolution1920x1440 PBO grabFull sensor (e.g. 4080x3060 12 MP)

If the sensor stream starts dropping RAW_SENSOR frames (3 or more sustained drops), Gate 180's frame-drop guard steps back cleanly so you do not end up with a corrupted file.


Related notes: Which Android phones work · 400 Hz Gyroflow and Audio LTC timecode · Back to Gate 180

ImpressumPrivacy PolicyTerms & EULAWithdrawalAccessibilityLicenses
© 2026 Evgenii Bykov · No cookies, no trackers, no banner.