yashsingh1/xdaforums huggingface dataset:
[Moto X4 Questions & Answers] quakeaz:
Snapdragon 821 is the chipset in the Google Pixel. Probably about 3x more powerful than the 630.

I assume the 630 is going to perform similarly to your Moto X Style's Snapdragon 808, due to the fact it is running at full HD instead of the Style's QHD resolution.
[Moto X4 Questions & Answers] birckston:
Are there any resources comparing IPC in these chipsets and in chipset lines (8xx/6xx)? I had assumed they'd be on similar architecture, and the clock difference between 630 and 808 would make the 630 faster per core.

Edit: so I spent some time searching for this, and my assumption was wrong. The A57 cores are significantly more powerful than the A53 at almost everything, to the order of 3-5x in some cases. https://www.anandtech.com/show/8718/the-samsung-galaxy-note-4-exynos-review/3

In effect, the 5X's Snapdragon 808 being 2xA57+4xA53 is in fact likely more powerful than the 4xA53+4xA53 configuration of the Snapdragon 630. It's too bad they didn't go with Snapdragon 660 for the X4.
[Moto X4 Questions & Answers] Voicebox:
I didn't read through most of that article, but it is 2 years old and also I couldn't find any straight comparison between the cores in there while skimming. But I think only comparing the actual multi-core chips running makes sense, particularly since they have different quantities of cores and a mixed bag in one case. Plus apparently at different clock speeds.

I did find this, which gives a 20% edge to the 630 in "Total Clock Speed". No indication how that is measured. Also it can handle higher speed RAM, but of course would have to actually be paired with higher speed RAM. The 630 is also 14nm vs 20 nm for the 808, so the 630 should use less power. Except it runs more cores at a higher clock speed, so who knows what the net is.

https://versus.com/en/qualcomm-snapdragon-630-vs-qualcomm-snapdragon-808-msm8992

The 630 can run "Up to 2.2 GHz"

https://www.qualcomm.com/products/qualcomm-snapdragon-630-mobile-platform

The 808 can run "Up to 2.0 GHz"

https://www.qualcomm.com/products/snapdragon/processors/808

GSMArena has the Moto X4 running the 630 "Octa-core 2.2 GHz Cortex-A53" and the Nexus 5X running the 808 "Hexa-core (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)." Seems like all 8 running at 2.2 GHz should be faster versus 4 at 1.4GHz plus 2 at 1.8 GHz, even if the big cores are better performers. Edit: Other sites, including the LG site have the 5X at 1.8 GHz. But that could also be a marketing thing of using the max clock speed in the specs. Either way, it is quite a different speed than 2.2 GHz.

http://www.gsmarena.com/motorola_moto_x4-8634.php

http://www.gsmarena.com/lg_nexus_5x-7556.php
[Moto X4 Questions & Answers] mightysween:
Age old debate... all other things equal, an 808 will still kill a 630 on a per-core operation level.

For example, if you are a gamer, an 808 platform will perform better. If you are not, the 625 will probably be better at day-to-day tasks, and have better battery life.

It all comes down to individual usage. I do some multitrack audio recording on a Nexus 6p, and it performs well. I am not expecting my X4 to do the same :)
[Moto X4 Questions & Answers] saketkutta:
Is it confirmed that the Fi version of X4 has Bluetooth 5.0, Google's page mentions 4.2, but Moto's page mentions it having Bluetooth 5.0.
[Moto X4 Questions & Answers] HypnoticSilence:
If I had to take a guess, the Moto page is probably the correct one. My understanding is that both phones will have the exact same specs, just different software.

If I also had to take a guess, the X4 will probably be locked down on the standard Motorola version. I am hoping it will have an unlockable option for the Project Fi version.
[Moto X4 Questions & Answers] Unknown_Burrito:
But the Adreno 508 is about as powerful a GPU as the Adreno 418, plus with the Full HD display and 14nm node process, the X4 would beat the X Pure quite easily in gaming. On a per-core basis, the A57's of the X Pure are handily superior to the A53's of the X4, but collectively, the X4's SD630>X Pure's 808. Two 4-core clusters of A53s, 2.2GHz and 1.8GHz respectively on a 14nm process, do perform better than a Dual and Quad-core combination of 1.8GHz A57s and 1.44GHz A53s.

Just to clarify, the Fi X4 is Bluetooth 5.0 compatible but Bluetooth 5.0 will be enabled on it with the Oreo update.
[Moto X4 Questions & Answers] crazyates:
SD630 Benchmark.

Total: 70,013

3D: 18,136

UX: 25,614

CPU: 21,248

SD808 Benchmark.

Total: 67,286

3D: 21,245

UX: 24,774

CPU: 16,460

These numbers say what we pretty much already knew: The SD630 with its more cores is better in multithreaded benchmarks, and will probably be a very smooth phone to use. However, without the A57 cores and with the slower GPU, it won't be quite as fast for gaming. It should get better battery life, however, since it's based on 14nm, and those A57 cores are a HOG on power.

Note: I choose to use the 7.1.2 numbers for the Nexus 5x (SD808) because that's what the X4 is running. It will get Oreo "before the end of the year" however.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Sai praveen:
Link: https://drive.google.com/file/d/0B8MhH1I4i6xrY3ZwbjF3N2pIblU/view?usp=drivesdk

As requested by [MENTION=5608673]kartik verma[/MENTION] :)
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ROGGGER3G:
xt1773?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Sai praveen:
xt1770 dude;)
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ROGGGER3G:
Do you have an easy way to backup stock recovery?

I, m on windows 10, and it sucks to make this.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Sai praveen:
https://forum.hovatek.com/thread-13347.html

checkout this!

its for mtk devices

i dont know for snapdragon devices!
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] AustinSaintAubin:
Anyone find the stock recovery for XT1775 (OVENS) purchased from Amazon?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] rana.likhi1:
how to install this stock recovery.bin file
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] AustinSaintAubin:
fastboot flash recovery recovery.bin
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Karangharat875:
Stok recovery download link not working
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] DaVE9073:
can anyone give download link for stock recovery xt1770
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] nappingbeam7:
File doesn't exist ☹️
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] DaVE9073:
Can anyone capture the stock recovery and post it here....help needed
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] gergev:
I just got an XT1775 from Amazon, unlocked, no ads version.

Is it possible to create a stock ROM ?

I would like to try to root, but would like to make a backup first before messing around with this.

Is backing up using TWRP before rooting the same as creating a stock rom?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] vicky85427:
Link not working

Link not working ... May be it expired.. can you share link again ...
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
It is possible if you know what you are doing. You will want to back up first and do it the smart way with backing up your stock system image. Don't just back up like normal (Sytem, data, cache, boot.img partitions)in TWRP, but make sure to grab the system image too. I would back up all partitions that TWRP allowed you to in the stock OS.

If you do not, you will be in a situation like my self. I built RR for the XT1775 and flashed it but have no data now and no way to install apn. So, your normal course would be to restore back and start over. Well, all I backed up was system and not the system image. Big mistake. Learn from my mistakes...lol...

Anyways [MENTION=718594]super[/MENTION]R makes a kitchen that is outstanding and might be able to help you with your stock rom build. I use it and recommend it highly.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] OSTUNG:
Shaer

if you found a stock recovery for xt1773 share with us . Thanks:good:
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] sachingodishela:
Stock recovery.img for xt1770, xt1771, xt1772 can be found in stock firmware file.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] danyfenton:
Reup please
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
What is the system image partition and why do you need it?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
Well to make this as simple as possible the system image backs up everything, like modem and other very important stuff that your phone needs to connect. This was all mentioned in the OP as well as any videos that I have on my YouTube channel. Especially on this device but for any device that you are flashing to for the first time you always make a system image backup (if available and on this device it was, but only on the initial backup). The only way to fix this now is to go back to stock with the links in the "general" and "question and answer" forums for this device.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
So they included a backup image (thus a partition/space we may be able to use)?

I'm just trying to understand how that partition differs from the remaining partitions taken together.

I haven't worked much with Motorola and this is the first I've seem this system image option in TWRP.

Much like the issue with persist on the G5 is a new source of problems to me.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
On most devices, when you unlock the bootloader and install TWRP, the very first backup you make ( of the stock rom) there is an option in TWRP to backup "System.img". So when you hit the "backup" button and it shows the list of options/partitions to back up (like; System, Data (excl. storage), Cache, Boot, Recovery, EFS), on a stock rom (and on this device) there is also this option in with the others I just mentioned "System.img". The "System.img" should show even more in size than just the system partition. This is because you aren't just backing up the System partition with the "System.img" option. It includes Sytem, boot.img, modems and much more all in one.

This is only offered on the stock rom though. Once you flash a custom to your device, this option in TWRP backup "System.img" will be longer show as an option. So, "System.img" is not a single partition, but rather the entire stock partitions needed to run the device in the stock configuration.

I don't know any other way to explain it. Any of the other roms in this forum will tell you that backing that up is a must before flashing any of these custom roms in this forum. LOS was the first custom rom out for our e4 plus and he had this info in his OP as well. So the bottom line is that you need to go back to stock in order to get your radios to work once again. After you have returned to stock, you can start over again but be sure (this time) to back up the "System.img" before flashing anything to your device. I hope this helps.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
So it's something TWRP does, not a separate partition?

How is it different from backing up all the other partitions?

It was not an option on my prior devices (Samsung, LG, and Nook).
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
I can't answer you question any better than I already have. To back up the "system image" as apposed to just "system" you are including everything in that backup and it's more like an OTA. It's got radios and everything in it. I can't make it any simpler than that. I may not be the right person to explain this to you. But in order to flash a custom rom on any device you should have a back up of the "system image" of that device died somewhere just in case something goes wrong.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
Never saw that on any other device nor was it mentioned in tbe threads for them (like GS3, LG G2, Nook HD)

Just backed up all the partitions; system, modem, efs, aboot, etc.

So I'm asking how is "system image' different than just backing up all the partitions and why not include whatever is missing as a separate option?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
Again, I can't explain this any further or be any clearer than backing up "system image" on a stock rom (like on the moto e4 plus) is like having a stock firmware backup (which has more involved/included files in it than your normal backup). I'm sorry I couldn't help you with this, I'm finished. This is one of the reasons I don't post my builds here on XDA any more. Read the entire OP on the LOS Unofficial for this device. I also mentioned it in the OP of my Rom thread. Hopefully someone else can explain this to you better than me.

Thank you.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
I guess. Just odd no one seems to know what it contains. Then act like I'm the odd one for trying to understand what it is.

I hoped a developer would know.

XDA doesn't have much development discission anymore.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] glockman4519:
Again, I an not trying to be a jerk and don't take it that way. But if you read the OP in the beginning of my rom threads, I clearly state that I an not a developer. Not even close. All I did was compile a ROM using the ROM's source and use another developer's device trees (giving full credits to that developer/developers for their source code). Like I said in my last post, I am sorry that I can't explain it in a way that you can understand.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] ST Dog:
Found it.

TWRP function. None of my prior devices were 6.0+ stock nor did they use dm-verity.

From the above it's nothing more a dd image of /system
[YU Yuphoria] akashraju.2010:
during flash write system.img failed... :confused:
[Magisk] CrashOverride1995:
Hey guys, this is my first Magisk module which I created seeing the recent development on the Modded Google Camera which is going on.

This modules is specifically designed for the OnePlus 3T and 5. It replaces the media_profiles.xml located at /system/etc/ to enable the HEVC (High Efficiency Video Codec). This results in increased quality due to the newer codec at the same bitrate which was being used with H264.

This module also enables 60fps video recording in Google Camera on OnePlus 3T/5 and also fixes slow motion crash on Google Camera which enables you edit SloMo videos (with sound) made with Google Camera in Google Photos and change the part where you need SloMo and where you need real-time just like iPhones.

Available in Magisk Repo

NON FUNCTIONAL AS OF NOW ON OREO ***ONLY HEVC WORKS ON OREO*** WILL BE UPDATED ONCE A FIX IS RELEASED

Changelog

v3.2 - Minor fixes to improve functionality on OxygenOS.

v3.1 - Updated to latest Magisk template.

v3.0 - Added support for Oreo.

v2.5 - Removed 60fps mod since Modded Gcam supports 60fps by default

v2.4 - Updated to latest Magisk Template 1400

v2.3 - Added support for OnePlus 3

v2.2 - Fixed Slo-Mo not working in OOS Camera.

v2.1 - Enabled Slow Motion for Google Camera

v2.0 - Added 60fps recording capability for Google Camera

v1.1 - Added support for OnePlus 5

v1.0 - Initial Release

Credits

[MENTION=8172874]tusar8[/MENTION] for HEVC mod

[MENTION=5467580]iaTa[/MENTION] for 60fps mod

[MENTION=4447339]AcmE85[/MENTION] for Slow Motion fix on GCam

[MENTION=3927764]theduke7[/MENTION] and [MENTION=6493997]Sytis[/MENTION] for testing it on their OP3s

[MENTION=3927764]theduke7[/MENTION] for Oreo support workaround
[Magisk] Sytis:
What is the reason for the OP3 not being supported as it features almost the same hardware and definitely the same unified software? I hope you can help me out with the reasoning :confused:
[Magisk] CrashOverride1995:
I didn't test it on that device, I have both the 3T and 5 with me personally and can test stuff on them so that's why I didn't mention the 3. I am absolutely sure about this working on 3T and 5.

PS - If you are willing feel free to test it out and PM me.
[Magisk] geotsai:
Hi, thanks a lot for this. Would you be able to provide the media_profiles.xml file as well so we can easily see what has been applied?
[Magisk] v0 HaVoK 0v:
Any chance you could do a version with increased bitrate? I don't think the video recording looks very good quality on the OP5, would be good if it can be improved
[Magisk] CrashOverride1995:
Extract it from the module zip.
[Magisk] CrashOverride1995:
OP5 records at 20Mbps for 1080p and 42Mbps for 4K, which I think is okay for the respective resolutions as YouTube uses way less bitrate while streaming i.e 8000kbps for 1080p and 35-45Mbps for 4K (this is similar to OP5).

PS - YouTube reference if you are comparing the recorded video to a YouTube video of similar resolution.
[Magisk] ShironLive:
Chrome app can't connect to the internet after v2.5, firefox app works fine though. Using OP3T.
[Magisk] CrashOverride1995:
This module has nothing to do with Chrome. It's a derp on your side.
[Magisk] IvanIvanov2:
Does it works on oreo?
[Magisk] CrashOverride1995:
The latest v2.5 should work on Oreo but I have not yet tested it on Oreo. Please try and report back.

P.S. Don't forget to take a backup first.
[Magisk] IvanIvanov2:
Then its doesnt work or need use a proper camera?
[Magisk] CrashOverride1995:
Which ROM are you using?
[Magisk] IvanIvanov2:
Beta 18
[Magisk] CrashOverride1995:
PM me your ROM's stock media_profiles.xml located at /system/etc/
[Magisk] CrashOverride1995:
Oreo Update!!

v3.0 IS LIVE!!

Added support for Oreo based ROMs running on OP3(T) and OP5.

Thanks to [MENTION=3927764]theduke7[/MENTION].
[Magisk] papzi57:
Finally! The first Magisk module, complete with OREO support! Thank You!

Update: After rebooting doesn't work again:crying:
[Magisk] ShironLive:
That's weird because everything works fine after i disable the module, tried multiple times, with reboots between.
[Magisk] Schrotty35:
Can you make for 5t please?
[Magisk] IvanIvanov2:
Instagramm crash when try to upload filmed video
[Magisk] mcdachpappe:
Thanks for the update.

i dont want to blame your Module but i want to let you (and the other users) know that this module isnt working on the latest nitrogenos 8.1 (build 12th dec.) with gcam mod
[Magisk] Schrotty35:
Please add 5t too.
[Magisk] harrisonweld:
It doesn't work for me.

Im on Oxygen os 5.0

It crashes when trying to record smth on slo-mo
[Magisk] theduke7:
Slow-mo doesn't work on most Oreo Roms.
[Magisk] jkyoho:
Slo-mo tested working on 5t TheOneOS v2.1(5.0.3) stock camera with this module v3.0
[Magisk] CrashOverride1995:
5.0.3 is not out yet for 3/3T or 5, they are still on 5.0.2. It's not yet tested on OP5T because I don't have that device.
[Magisk] theduke7:
sadly i tested it on the latest beta for OP3... still no go here, hopeful next beta and stable will be like 5t

that said, the slowmo screen you added is from the Stock camera, this module is to enable the Gcam slowmotion
[Magisk] MrPhilo:
Hi, I will test this when I update my 5T to Oreo, just being lazy atm :)

Does this work with the Camera M? (Modded Stock Camera)
[Magisk] jkyoho:
Yes, I have Both camera M mod and this mod running fine on stock camera apk(modded by camera M). And some ppl mentioned Gcam v1.4 Should be a Go for OP5t
[Magisk] walkwitmeinhel:
I just try in op5t ob3 but didnt work
[Magisk] Valeriuz:
Hello, the module works but the videos have the same size of the original h264. What could be wrong?
[Magisk] Pastitsio:
OnePlus 5T. Works for every video mode(720, 1080, 1080@60, 4k).
[Magisk] jerrygo2:
The V3.0 is not installed on my OP5 with OB7.

Is the only I that have this problem?

Magisk version I installed is 16.3(beta) now.

Installation logs said,

/data/magisk isn't setup properly!

Please install Magisk v14.0+!
[Magisk] Didgeridoohan:
From Magisk v16.3, modules based on the 1400 template (like this module) won't install. It needs to be updated...
[Magisk] jerrygo2:
So, I gotta wait for updating... :eek:
[Magisk] badlipe:
Same error here, waiting for update on the module :good:
[Magisk] 3lMghraby:
I am on OOS 5.1.2 everything is working except slow motion (fatal error)
[Magisk] Lycox:
+1
[Magisk] liloow:
Updated to Magisk template 1500 if anyone is still interested !

I bumped the version to 3.1 for repo compatibility, nothing in the code itself has been touched !
[Magisk] fscussel:
Does this works with ZUK Z2 and dark moon kernel?
[Magisk] liloow:
I can't see why not, it's basically just overriding some vendor built config! Keep in mind that the super slo-mo on G-cam is currently broken in the mod and therefore in my template port too !
[Magisk] CrashOverride1995:
Module updated in accordance with the latest Magisk template.

NON FUNCTIONAL AS OF NOW ON OREO ***ONLY HEVC WORKS ON OREO***
[Magisk] yohouse2:
I tested v3.1 on Android 8.1 OOS 5.1.2 (OP5), it is saving in HEVC, but 1080p 60fps records at 30fps at 40mbit/s

Could you add a version with reduced bitrates (or tell me where to find the values i need to modify) ?
[Magisk] CrashOverride1995:
As stated in the post quoted by you, it is non functional on Oreo.
[Magisk] CrashOverride1995:
Module updated with minor fixes to improve functionality on OxygenOS.

NON FUNCTIONAL AS OF NOW ON OREO ***ONLY HEVC WORKS ON OREO***
[Magisk] grotesque02:
Op3T with omnidragon rom block gcam.
[Magisk] furatxp:
Thank you
[Magisk] nikhilZ2:
2.4 please

Please provide older module 2.4 or 2.3.

Because in latest module hevc works but 60fps not working.

So i need to try 60fps enabled module.

My Device Zuk z2-Miui Nougat-Gcam BSG 4.4.

Thanks in advance..
[Magisk] everlasting207:
Hi! Could you please remove the nougat restriction on the 3.4 on the repo? marcant01 seems to have found fix for the slowmotion cam issue for oreo based roms..
[Magisk] CrashOverride1995:
It's better to have a restriction, that way there will be less people complaining about the module not working on their phones.
[Magisk] everlasting207:
I see.. I wanted to download the 3.3 version for now, but I couldn't find how I would be able to do that. Thanks for your work either way.
[Magisk] jkyoho:
:svetius:;)
[Magisk] magzflip:
Hello! I can't get 3.3 to update to 3.4 with magisk. The log says my op5 needs to be an op5 :confused: I'm on stock A-8.1.0/OOS-5.1.7

"- Copying zip to temp directory

- Installing HEVC+SM_GC_OP3&3T_and_OP5-v3.4(13).zip

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

inflating: post-fs-data.sh

inflating: service.sh

inflating: system.prop

inflating: install.sh

inflating: module.prop

*******************************

HEVC+SM GCam for OP3/3T/5

*******************************

******************************

Powered by Magisk (@topjohnwu)

******************************

- Extracting module files

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

creating: system/

creating: system/etc/

inflating: system/etc/media_profiles.xml

inflating: system/etc/placeholder

creating: system/vendor/

creating: system/vendor/etc/

inflating: system/vendor/etc/media_profiles.xml

inflating: system/vendor/etc/media_profiles_V1_0.xml

inflating: system/vendor/etc/media_profiles_v1.xml

inflating: system/vendor/etc/media_profiles_vendor.xml

inflating: system/vendor/etc/placeholder

Your device is not a OnePlus 3/3T/5

! Installation failed"
[LineageOS Questions & Answers] jakey1995abc:
I am trying to download the latest LineageOS build for the OnePlus 2, but every time I try downloading it fails almost instantly. I've tried downloading it though the update menu on my phone and also tried downloading directly from their site, but both fail to download. Is anyone else having this issue?
[LineageOS Questions & Answers] IDisposable:
Last build was so broken it was deleted. Wait a couple days, at least.