Skip to main content

Google Camera with NightSight on Redmi Note 4x

I have been running Google Camera 5.x on a rooted Redmi Note 4x / MIUI9 for the longest time. The default HDR+ shots are fantastic, and the portrait mode is fun and surprisingly reliable.

I generally dislike flashing new ROMs due to the hassle of configuring the environment and having to setup the odd apps that do not properly restore their settings from the cloud. So I have stuck with MIUI and have generally grown quite used to it.

A number of factors have finally nudged me out of my comfort zone. First, the MIUI10 update was a total disaster. Google Camera stopped working with no known workaround. Once one has tasted the power of Google Camera, it's hard to go back to anything else! Secondly, MIUI10 is an aesthetic mess. It abandoned color notification icons for the black-and-white aesthetic of vanilla Android, but left its own apps (eg. Mi Fit) alone. This led to something so horrible that even a typically function-over-form guy like myself couldn't stand it. Thirdly, this version has ads! You can disable them if you want to, but they are scattered all over the place, and leaves a pretty bad taste in this user's mouth.

Finally, there have been so much news of the magical NightSight feature in Google Camera 6.x that I have been actively looking for ports for Redmi Note 4x. After much research, it appears some people have had success with it:

so I decided to give it a shot (no, I don't understand Hindi, so it is a long shot!).

Basically, I need to get a Android 9 (Pie) ROM onto the phone. Pixel Experience (as recommended in the video) seems to be a pretty solid choice.

Here are the steps I took to load Pixel Experience onto my phone:

1. Make sure bootloader is unlocked.

2. Make sure latest version of TWRP for Redmi Note 4/4x (codename: mido) is installed. My version is 3.2.3-1 (twrp-3.2.3-1-mido.img)

3. Download Pixel Experience ROM for mido ( and put the file in internal storage of phone.

4. Download franco kernel for mido ( and put the file in internal storage of phone.

5. Boot to TWRP recovery.

6. Create a backup of the current system just in case.

7. Select "Wipe". Select "Format Data".

8. Select "Wipe". Selected "Advanced Wipe". Check "Dalvik Cache", "System", "Data", "Internal Data", "Cache", then proceed.

9. Select "Install" and install and

10. Reboot

After a longish wait that happens whenever the ROM is updated, you will hopefully see the Pixel Experience welcome screen and have a fully functional Android Pie phone.

The version of Google Camera included with Pixel Experience is an older one without NightSight. To load the version with NightSight:

1. Disable the built-in version by long pressing on the "Camera" icon and selecting "Info". Then hit the "Disable" button.

2. Download and install (GoogleCamera_6.1.013.216795316-debug.apk).

I have tested NightSight extensively, and it works every bit as advertised. "Magical" is the word that keeps popping to mind. The tech news is choked full of review photos, but believe me, when you try it out yourself in a pitch dark environment with a sub-$200 phone and see the results, you will still get a WTF jaw-dropping kick out of it. It is magical!

I have also tested other features such as HDR+, portrait mode and video capture, and they all work fine. I am sure there are existing issues with this port, but I didn't find any. Doubtless it will only get better with time, but even in its current state, I am a happy camper.


Popular posts from this blog

Adding "Stereo Mixer" to Windows 7 with Conexant sound card

This procedure worked for my laptop (Thinkpad E530) with a Conexant 20671 sound card, but I suspect it will work for other sound cards in the Conexant family. I was playing with CamStudio to do a video capture of a Flash-based cartoon so that I can put it on the WDTV media player and play it on the big screen in the living room for my kids. The video capture worked brilliantly, but to do a sound capture, I needed to do some hacking. Apparently, there was this recording device called "Stereo Mixer" that was pretty standard in the Windows XP days. This allowed you to capture whatever was played to the speaker in all its digital glory. Then under pressure from various organizations on the dark side of the force, Microsoft and soundcard makers starting disabling this wonderful feature from Windows Vista onwards. So after much Googling around, I found out that for most sound cards, the hardware feature is still there, just not enabled on the software side. Unfortunately, to

Attiny85 timer programming using Timer1

This Arduino sketch uses Timer1 to drive the LED blinker: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 /* * Program ATTiny85 to blink LED connected to PB1 at 1s interval. * Assumes ATTiny85 is running at 1MHz internal clock speed. */ #include <avr/io.h> #include <avr/wdt.h> #include <avr/sleep.h> #include <avr/interrupt.h> bool timer1 = false , led = true ; // Interrupt service routine for timer1 ISR(TIMER1_COMPA_vect) { timer1 = true ; } void setup() { // Setup output pins pinMode( 1 , OUTPUT); digitalWrite( 1 , led); set_sleep_mode(SLEEP_MODE_IDLE); // Setup timer1 to interrupt every second TCCR1 = 0 ; // Stop timer TCNT1 = 0 ; // Zero timer GTCCR = _BV(PSR1); // Reset prescaler OCR1A = 243 ; // T = prescaler / 1MHz = 0.004096s; OCR1A = (1s/T) - 1 = 243 OCR1C = 243 ; // Set to same value to reset timer1 to

Hacking an analog clock to sync with NTP - Part 5

This is how it looks after I have put everything together. The Arduino sketch is available here . The 2 jumper wires soldered to the clock mechanism are connected to pins D0 and D1 on the ESP-12 (in any order). When the device first boots up, it presents an access point which can be connected to via the PC or smartphone. Once connected, the captive portal redirects the web browser to the configuration page:     A custom field has been added to the WiFi configuration page to enter the current clock time in HHMMSS format. Try to set the clock time to as close to the current time as possible using the radial dial at the back of the clock so the clock will have less work to do catching up. In the config page, the HTML5 Geolocation API is also used to obtain your current location (so if your web browser asks if you would like to share your location, answer "yes"). This is then passed to the Google Time Zone API to obtain the time and DST offset of your time z