yashsingh1/xdaforums huggingface dataset:
[Moto Maxx General] ChazzMatt:
I used the Moto G4 camera, which I think I got from here:

https://www.androidfilehost.com/?fid=385035244224382755

or I may have gotten it from here:

https://xdaforums.com/droid-turbo/themes-apps/moto-g4-camera-app-bootlogo-weather-t3414260

Try the first link first?

Here'a also the OnePlus camera you can flash:

OnePlus Camera V1.4.

https://xdaforums.com/droid-turbo/themes-apps/oneplus-camera-v1-4-t3415485

I installed the G4 camera in TWRP and after I rebooted I had two Moto cameras in my app drawer. Once I decided I liked the G4 better, I used Titanium Backup to "freeze" the other camera, so I wouldn't see it. I also put the G4 camera shortcut on my desktop.

However, Motorola has since released an update to that G4 camera in the Play Store which is NOT compatible with our devices. Once I installed the update, realized the newer version would not work on my Quark, I rolled back to the "original" G4 camera and disabled the "auto update" checkbox in the Play Store listing. If you install that G4 camera, I recommend disabling auto update.

There are other cameras people use, like the Open Camera and Bacon camera -- but those are available in the Play Store as regular apps. What I was referring to was a zipped file I flashed in TWRP.
[Moto Maxx General] ChazzMatt:
From our official Quark TWRP maintainer [MENTION=5747496]bhb27[/MENTION]...

TWRP update

twrp-3.1.0-0_MOD_1-quark.img

https://www.androidfilehost.com/?fid=457095661767143958
[Moto Maxx General] Rahuld107:
[MENTION=3250376]ChazzMatt[/MENTION],

Flashed the g4 camera from the first link you posted, it has replaced the stock camera. The ui is better than our stock camera. I have removed its market link from playstore to avoid update, have also disabled the auto update feature in the playstore.

I was not expecting it to actually replace the stock camera app since you mentioned that you got two camera apps when you flashed the g4 camera app., one from our maxx stock camera app and other being the g4 camera app. But in my case, i have only one app, the g4 that is, the maxx stock camera app got replaced. I do have the titanium back up of my maxx stock camera app though, in case i need to switch back to it. Thanks a lot for the tip [MENTION=3250376]ChazzMatt[/MENTION]
[Moto Maxx General] ChazzMatt:
Yes, it does have a better GUI.

Thanks for suggesting to remove the Google Play market link. I hadn't even thought of that, even though I see the feature in Titanium Backup.

Maybe I ended up with two cameras because I have a custom ROM (Resurrection Remix 6.X) which had a camera? Been so long since I've run "stock" firmware... :)
[Moto Maxx General] ChazzMatt:
May be because I'm running a custom ROM or something, but removing the market link doesn't stick for me for this "system" app in Titanium Backup. Every time I reboot, somehow it gets re-attached. I would go in and detach it again. But this last time when it re-attached, my Play Store update disabled selection for the app got changed. The camera app auto-updated! :rolleyes:

I tried restoring my previous Titanium Backup app backup (to previous version), disabling and re-installing the camera app in TWRP, etc. What finally worked was just restoring the full TWRP backup I had made this morning (it's an almost daily ritual with me). So, I have the non-updated G4 camera back and I quickly UNchecked the auto-update feature.

Not sure why removing the market link doesn't work for me. But I've never really messed with the feature before.
[Moto Maxx General] Rahuld107:
I can't get it working too. I got same thing going on with me. Detached a few times myself, it works for a few days / until restart i assume. It gets reattached again. Moving the app to sd card and making it as user app might help may be, I have not tried that. Guess we got to live with it :cool:
[Moto Maxx General] ChazzMatt:
Yes, I can live with ignoring the Play Store auto update nag. I do that with a few other apps for different reasons.
[Moto Maxx General] Rahuld107:
I have extracted the motocamera apk, used zipsigner app (from playstore) to change the signature of the camera apk. Then uninstalled the stock g4 camera app using titanium backup. RESTARTED THE PHONE. Then installed the new camera apk( with changed signature). Had to turn on the "unknown sources" option in the security settings. The camera app does not show up in the playstore anymore. Will wait for a few days and check again. I followed the following guide from xda for this :

* get the Apk you wanna detach (eg using TitaniumBackup)

* install ZipSigner from play store

* re-sign the extracted Apk using ZipSigner and test key

* uninstall the original app and install the re-signed Apk
[Moto Maxx General] zys52712:
What you can do for moto camera is get the modded version from here and copy it over the old one in /system everything should work.
[Moto Maxx General] ChazzMatt:
Thank you for that! It's the camera from the new Moto G5!

I just downloaded the APK, and installed it. I then froze the older Motorola (system) camera. The new one shows up as a user app camera. For a few minutes I had two cameras, until I froze the old one.

Everything works well. Yes, it even has professional mode, but I probably won't use that. Video works well too.

New Moto G5 camera for QUARK

Moto Camera Modded APK

(V6.0.62.1)

https://xdaforums.com/moto-x-style/themes-apps/moto-camera-6-0-43-10-modded-apk-t3459690

DOWNLOAD (v4):

https://drive.google.com/file/d/0BzN_CG03Ba9WeUIzM0UySUFwaGs/view

_____

EDIT:

Download with Chrome. It should download an an APK. PC version of Chrome always downloads as an APK.

If you are using the mobile Chrome and it downloads as a .BIN file, go to Chrome settings and request the desktop site version of the website (in mobile Chrome) and click on the "download" again so it downloads as APK.

But make sure you are in Chrome. When I click on the link on my phone, "Google" opens the link and it's not actually Chrome browser. (They look very similar.) I know because when I go to the browser settings, it asks me if I want to open in Chrome. Open in Chrome.

______

BE SURE TO REBOOT THE PHONE AFTER YOU INSTALL THE NEW CAMERA!

Video recording may not work until you reboot the phone.

_______

You should probably freeze (or uninstall) any other cameras until you are sure there are no conflicts.

________

I tested both 1080p and 2160p (4K), and the rear camera works fine.

Video works fine on my Quark (Moto XT1225), but I have the native 1080p QUARK camera video resolution chosen for video recording. I did test 2160p (4K) and it also works fine.

The Quark camera specs are this:

Any other resolution except for those two might not work for Quark (Droid Turbo, Moto Turbo, Moto Maxx).

Since both my TVs are 1080p, I just kept it on that. While 2160p (4K) works, it doesn't do me any good, even on my 1440p AMOLED Moto Maxx display, you know?

SETTINGS:

https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/110618/related/1

________

UPDATE:

New Moto camera from stock 7.1.1.

Probably best to uninstall previous before installing this one. Works great for me.

New Moto Camera 6.0.78.1
[Moto Maxx General] ChazzMatt:
UPDATES:

* added another boot logo

posts #2 (ABD)

and

post #5 (TWRP flashable)

to include "Dark Google ATAP":

Thanks to [MENTION=3623188]XDleader555[/MENTION] for the splash logo I found in Moto X Pure forum -- but I adapted it for our Quarks so it would not be upside down. ;) The other bundled elements are taken from the Black & Teal boot logo file ("recovery", "bootloader", etc) but the splash screen is this black artistic Motorola logo. For the TWRP flashable file I utilized [MENTION=5747496]bhb27[/MENTION]'s excellent logo flasher app. Post #3 is ADB, post #5 is TWRP flashable.

_____________________

* added another boot animation

post #3

to include Motorola stock "Spinning World".

This is the same stock animation that came with my Quarks. Thanks to [MENTION=4131092]metpolds[/MENTION] for recreating this for us, using jpg files!

_______________________

* updated the Moto G5 camera to v.4

See post above this. Thanks to [MENTION=6284772]data365[/MENTION] for his continued work on this!

UPDATE:

New Moto camera from stock 7.1.1.

Probably best to uninstall previous before installing this one. Be sure to reboot.

Works great for me.

New Moto Camera 6.0.78.1
[Moto Maxx General] kreg1744hp:
My device HTC ONE M8

Moderator Edit: see next post, enough said there.

(In future, please do NOT quote the entire OP of a thread. Apart from serving no actual purpose at all, it can cause issues for folk on limited bandwidth or when Mobile. Thanks.)
[Moto Maxx General] ChazzMatt:
And you quoted the ENTIRE OP to tell us you don't know how to find the XDA forum for your device? Why did you quote the entire first post? WHY? We KNOW what it says. I know what it says. I wrote it.

On PC website, there's an XDA search box on any XDA page, upper right to find your device.

You can also Google from any device. Type your device name into Google -- just like you did here -- add the word XDA, hit enter. ;) Here's a link to help you:

http://bfy.tw/BljL

You can easily find the correct XDA forum for your device and those users can help you.

DID you even bother to read what you quoted? At some point you realized, "Hey not only is this not an M8, it's not even HTC! It's for Motorola phones! Maybe I should go find the forum for HTC One M8..."

But no, you quoted the entire op to tell us nothing, except your device is not for this forum. Please go back and edit your statement/question, whatever it is to REMOVE everything you quoted. Thank you.
[Moto Maxx General] ChazzMatt:
New Moto camera from stock 7.1.1.

Probably best to uninstall previous before installing this one. Be sure to reboot.

Works great for me.

New Moto Camera 6.0.78.1
[Moto Maxx General] marinegundoctor:
Hey [MENTION=3250376]ChazzMatt[/MENTION], I always meant to ask...what do you use to make the boot images? I'm thinking about making a few myself. I found a little program on my hdd called "Motorola boot logo maker" from 2014/2015-ish but it has no options for the quarks (mine's an XT1254). I can enter custom dimensions though.
[Moto Maxx General] ChazzMatt:
I have used that same program, yes, to convert jpg or png to .bin format. I see what dimensions other Quark boot logo graphics were (1440 x 2560 pixels) and matched those dimensions. You would want to start with at least that resolution to get a crisp looking logo. You can even start higher than that and then downgrade to 1440 x 2560, but it you try to upsize an existing 1080p graphic to 1440p you may see artifacts. That Moto logo program will make ADB-flashable .bin files.

Then, to make a TWRP flashable version, I use this little app from [MENTION=5747496]bhb27[/MENTION]:

https://xdaforums.com/showpost.php?p=68280872&postcount=4

In one case, when adapting a boot logo from the Moto X Pure forum, I merely had to rotate the logo 180 degrees and re-save it to make it compatible for Quark. It was already the correct dimensions (as that phone also has 1440p display). I had to use that Moto logo program you mentioned to extract the .bin logo to .png, then rotate it in a graphics program like Paint, then used that Moto logo program to re-save it as boot logo .bin file (which can be flashed via ADB). Then, in the [MENTION=5747496]bhb27[/MENTION] app I also made a TWRP flashable version.
[Moto Maxx General] nnjimmy59:
[MENTION=3250376]ChazzMatt[/MENTION]

I have tried to download the logo Maker to no avail. I have had no luck doing a google search. I want to use a GB Packer logo for my boot logo. Any advice would be greatly appreciated. Thanks.

PS I'm on a rooted XT1254 with TWRP and running NepoRood's Nougat ROM.
[Moto Maxx General] ChazzMatt:
I'll see if I can find a valid download link for you for the program, or zip it and upload it.

I'll also take a look at your graphic, but no promises there.
[Moto Maxx General] nnjimmy59:
[MENTION=3250376]ChazzMatt[/MENTION]

I hate to be a pest, doesn't stop me though, I have the same problem as before. When I click on MotoBootLogoMaker.exe, it says "no application available." When I long press on MotoBootLogoMaker.exe it gives me the option to extract, I extract the files and I click on MotoBootLogoMaker.exe, it says "open as"

Text , audio, video, image, other. I cannot find any way to open the application. I really appreciate all your help, if it's getting to be too much trouble, forget it. Thanks again.

nnjimmy59
[Moto Maxx General] marinegundoctor:
Thanks for all of these!

I'm using the new camera with no issues either on RR-M. (Thought I'd test out a theory on a problem I was having with a Verizon app in Nougat).
[Moto Maxx General] ChazzMatt:
Let's back up a minute. You downloaded the zipped file to your Windows computer, then unzipped it to some folder, right?

Then in that folder you should see two files, with one of them being MotoBootLogoMaker.exe.

Then, when you double click on that .exe file, it should open and you should see the interface from the screenshots.

What version of Microsoft Windows are you running on your PC? This is a Windows program. I have Windows 7, but I assumed it was also compatible with Windows 10.
[Moto Maxx General] nnjimmy59:
@ ChazzMatt

I haven't had the chance to try the file you zipped for me on my laptop. I tried to open it on my phone with the results I mentioned. I'll try it on my laptop this afternoon, Windows 10. Thanks again
[Moto Maxx General] ChazzMatt:
Ah, then that's the problem. That's a Windows software program, not an Android app. Because it makes ADB flashable files, which you would normally flash to your phone from your PC.

You can then make them TWRP flashable, with the [MENTION=5747496]bhb27[/MENTION] software, but that's an additional step and is a separate program.
[Moto Maxx General] ChazzMatt:
If you're back in RR-M, don't forget to flash the stereo fix update [MENTION=5747496]bhb27[/MENTION] gave us. Can't remember if he included that in the last partial update (basically was an OTA). I know the stereo fix was after the last full ROM image.

After the last full ROM image, he did the stereo fix as a patch update, then about a month later released a partial updated ROM to dirty flash over the last full image. Hope that all makes sense.
[Moto Maxx General] marinegundoctor:
I'd forgotten about that, I'll look back and flash it. Thanks!
[Moto Maxx General] nnjimmy59:
[MENTION=3250376]ChazzMatt[/MENTION]

I finally had the time to make a logo for my droid turbo. It came out too small, but it worked. I'll have to play around with it when I have more time. Thanks again for all your help. By the way, my Norton program thinks it's a dangerous program. Any idea why?
[Moto Maxx General] ChazzMatt:
UPDATE FROM 6.0.78.1 TO 6.0.84.1

New Moto camera from Motorola stock ROM 7.1.1 for Moto Z Play. Modded by [MENTION=6284772]data365[/MENTION] to work with ALL Motorola phones including our Quarks. Download links below, but go to this thread to thank him!

Moto Camera Modded APK

https://xdaforums.com/moto-x-style/themes-apps/moto-camera-6-0-43-10-modded-apk-t3459690

Probably best to uninstall previous before installing this one. Reboot after installation. Works great for me.

DOWNLOAD

New Moto Camera 6.0.84.1
[Moto Maxx General] LifeAsADroid:
Ok so I'm not sure what went wrong, hoping some insight can be given.

Downloaded the MotoBootLogoMaker executable, extracted, opened .exe file, and ended up with a misshapen window that wouldn't allow me to view the sizing fields for the X and Y (along with partially covering some other options - see first image for reference). Ok, no big deal, might be a Windows 10 thing, so I followed your suggestion and downloaded one of the pre-made logos, loaded into the Maker, highlighted the boot_logo option in the list, selected "replace", selected the .png file I wanted to replace it with (even remembered to make sure the image was rotated 180 :good: ), and saved the file as a new filename.

Extracted the .bin file from within the .zip, flashed in fastboot, however the logo that appears on the phone is the pre-made logo (that I used to open in Maker to have the X and Y pre-set) not the logo I saved the file as. I then checked the .bin file I created in the Maker program and sure enough it's showing the image I designed and saved it as (please see attached second image to know I'm not crazy, lol).

I'm a bit confused, any thoughts? Any steps I overlooked? My only thought is that Windows 10 is screwing with the program in more ways than just the sizing of the fields in the program. I'll give it a shot on a Windows 7 computer if I can find one around. Thanks again :good:

Disclaimer: I don't dislike your image, just perplexed as to why it's loading the way it is (Maker shows one thing, phone shows another) and am now determined to make it work correctly.
[Moto Maxx General] ChazzMatt:
I may not be able to answer this today. Have some other stuff going on. But yeah, the first screenshot shows the options all messed up, so maybe Windows 10 issue on that. Still, not sure why the original image is showing up and not your replacement image. Because I definitely replaced an image in a previous package with that new "artistic" Black & White image recently, while keeping all the other elements of the Teal & Black package.
[Moto Maxx General] LifeAsADroid:
Ok I got it figured out. Used Windows 7 to create .bin file for ADB flash in MotoBootLogoMaker, no change in the way I was flashing the logo image from Windows 10 (though the layout of the program was improved and looked how it should). (Back on Windows 10 computer --> ) So I went looking through the different logo image categories in the .bin file via MotoBootLogoMaker to see what the other images looked like. Lo-and-behold I found a duplicate image of the image I was trying to replace in the file stored under "logo_unlocked". After replacing the stored image with the image I wanted to use (same image I used for "logo_boot") and flashed that .bin file with ADB fastboot everything worked just fine. Which I guess makes sense since it's the "warning: bootloader unlocked" image that I wanted to replace. Thanks again for the guidance with this and providing the pre-made .bin files and MotoBootLogoMaker executable.

TL;DR: I replaced both the "logo_boot" and "logo_unlocked" images with my own .png image and everything worked how it should.
[Moto Maxx General] ChazzMatt:
Glad you got it figured out. Maybe what you did was a step I actually did, and didn't realize it or forgot about it? Believe me, I am not an expert myself. I muddle through until I can do something -- take screenshots, maybe write something up to help others -- then often completely forget what all I did. :cool:

Back in early 2015 when I was messing with QPST and other similar programs to try to add LTE band 5 for AT&T to the XT1225 (which, turns out, already had LTE band 5 -- Motorola just didn't want to admit it at first) I dove DEEP into that project for weeks. Two years later, now when I look back at those posts, I'm like "Wow, who wrote all that?" There's tons of screenshots, numbers, detailed instructions. It was me, but if it's not something I do every day... I quickly forget it. I couldn't sit down and tell people about QPST like I could two years ago when I was very involved.

For this, I did enough to use the MotoBootLogoMaker to replace one of the already-made logos (Teal & Black, which was my favorite) with the newer "artistic" Black & White (my new favorite). Saw it was upside down, then had to adjust it, and re-import it to be upside down. Previously I had used [MENTION=5747496]bhb27[/MENTION]'s app to then make it be TWRP-flashable -- for those who don't want to use ADB. That's useful for some people because once you have TWRP, you can ditch the ADB commands.* So, I pulled that out again and made the new boot logo TWRP flashable. But, since it had been MONTHS before when I did it the first time, I had to go read the instructions again.

Again, glad you got it figured out, because I had already told you about all I could. ;)

(* However, there's a limit -- you can't TWRP flash a boot logo and a boot animation in the same TWRP session. Don't ask me why. You have to reboot and then use TWRP to flash the other element.)
[Moto Maxx General] LifeAsADroid:
It probably was something that you had done at the time of implementation yourself but had forgotten (I doubt it was my discovery, I'm sure I just Columbus'd the idea when I figured out my issue ;) ). Like you said, if it's not something that we do every day it's easy to forget steps or entire processes completely - I'm the same way as are most people I would think. I remember having my unlocked DROID RAZR HD Maxx and flashing over the unlock warning image as well as a boot animation, but obviously didn't remember the process since it took me a few days of research and asking questions here on XDA to figure out the process again (actually a different process I believe, but you get what I mean :cool: ). If I'm not mistaken it was your suggestion in another thread that brought me here to flash over the bootloader unlock warning, and I think helped me along the way of a custom boot animation. So much happened in 3-4 days of owning the device it's hard to keep it all straight.

Thanks for the info about flashing the items in separation TWRP sessions. I had flashed them separately due to getting one figured out prior to the other, and technically I did an ADB flash of the logo.bin file. But it is good to know this for future reference (as well as have the info here for anyone else lurking out in internet-space reading along this thread's story).

If I could ask one favor of you, hopefully small and not too much taking of your time. Would you mind editing your post #2 (I think it was post #2) to include the changing of the "logo_unlocked" image file along with the "logo_boot" file in the instructions you have written? I fear that sometime in the future I may need to reference that post again if I feel a need to change a boot logo image and also fear that 1) I won't remember and 2) will reference your post instead of these few to figure out what happened. I think it might also help someone in the future with their struggles as well.

BTW - thanks for the updated MotoCamera apk link in another thread as well :good:
[Moto Maxx General] ChazzMatt:
You are welcome!

I'm a little confused what needs changing? Post #2 of this thread is about ADB flashing a new image to replace the unlocked bootloader warning, and those instructions are correct as far as I know. There are several Motorola logos to choose from and you are flashing the BIN image via ADB. Those were made by other people as well that "artistic" Black & White which was adapted by me. (I gave credit for the logo I found in another device forum. I didn't make the logo, I just adapted it to work for our phone.) Those BIN images all work fine, when flashed by ADB.

Then, post #5 is the TWRP-flashable versions of those same logos. I took the ADB BIN versions and used [MENTION=5747496]bhb27[/MENTION]'s app to make them TWRP-flashable.

What I think you are suggesting needs changing is in the discussion we had about making your own BIN image -- which started on page 6 with a couple of different users who were interested. The post that probably needs changing was post #58 ? Your post #70 clarifies both categories that need to be changed, while I only mentioned the first category (as I knew I had done that one). I can go back and change post #58 to include your updated information. I'll do that later today.
[Moto Maxx General] LifeAsADroid:
Ah yes, you're right, I did mean the convo from the page 6 area. I forgot the original point was to offer pre-made flashable files and not to actually create a flashable on our own. Thanks!
[Moto Maxx General] ChazzMatt:
OK, I went back to page six and

added your instructions to the bottom of that post

. I didn't yet change the screenshots to match, but I hope that helps someone!
[Moto Maxx General] atkesavan:
Question?

Is this method is suitable for XT1225 (Moto Turbo) India with stock marshmallow update 6.0.1 without any custom modifications