Search results

Okay, my bad, I thought the bootanimation you uploaded was not rotated yet, so I rotated it and that made it into portrait again. I've uploaded a new file into my previous post.

Hi, I think there are two possible things that could have gone wrong: 1) You forgot to swap the dimensions in desc.txt - I think if you forgot that, the animation would just have weird proportions, but would still work somehow, so this is less likely 2) The bootanimation.zip file must not use...

I've been using OpenGapps for quite a few months now, without any issues. I'm using stock gapps with the ForceNewCamera keyword, so it installs the right camera libraries. Can't tell if visual voicemail works, because people never use voicemail in my part of the world, but it does install the...

Hi, I think I had the same problem, often I didn't get a notification until a second email arrived, and then I got two notifications at once, but I think I found where the problem was. Can you look into Gmail - Settings - your account - Inbox notifications and see if you have everything enabled...

I'm using Measure and ARuler (which use ARCore) just fine on Resurrection Remix and crDroid on my smaller Pixel. I'm using opengapps (the stock package with ForceNewCamera option), though, maybe that makes the difference, because it includes some needed native libraries? No idea.

You have to disable pocket detection, it's broken. If it's already off, try turning it on and back off again, there's some mismatch between the toggle and the actual preference value.

You could try downloading OpenGApps Stock from the OpenGApps website, and then putting forcenewcamera in .gapps-config. I'm not sure Stock gapps will fit in the system partition on the Pixel, though, so you might have to unselect some non-critical apps through .gapps-config as well, you can...

Nice! Could you build for sailfish as well, please?

That's probably it, you have to have a completely stock boot.img before flashing Magisk, so that when Magisk restores it the OTA is able to patch it.

Yeah, I have not actually tried this, since I'm not running the stock ROM, so as Sheeezy says, definitely do a backup before listening to any internet stranger's advice. Sheeezy - I wonder, did you have TWRP installed, or do you just fastboot boot it? I think that if you would install TWRP...

If you have only Magisk installed, it's quite easy, Magisk supports uninstalling itself before OTA and then reinstalling itself after OTA but before reboot. Look here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

How exactly did you flash this, and which version? I had the same problem yesterday, I was running RR and EX 3.03 for a few weeks before, and everything was fine, and yesterday I flashed the 3.04 version and it started bootlooping. I solved it by fastboot flashing the boot.img from April...

Try reading here, step 2 might be what you need: https://www.xda-developers.com/google-pixel-2-rounded-screen-corners/

I had a similar issue, it looked like the screen would half turn on and touch would work, but the image stayed completely black. What helped me was to disable Pocket Detection in Settings - Configurations - Buttons. (I actually had it off in the first place, but toggling it on and off again helped.)

Apparently on Huawei devices the bootanimation is either in /system/etc/media (on Marshmallow) or in /product/etc/media on Nougat. Try to take a look if it is there and maybe replace it, it should work. I don't have any Huawei devices, so I can't test it, sorry.

Strange, for me cleaning the button with alcohol didn't help, but knocking works. I have to knock with my knuckles on the display just next to the power button, and it manages to get it unstuck somehow. Also, a quick tip for people without a working power button - you can add a new button to...

I had the same issue last week and doing the restorecon thing worked for me. Did you reboot afterwards? I'm not sure if that was necessary or not, I think I rebooted and then it worked.

I think there is some issue with the SELinux contexts, I think, to fix either open a Terminal emulator app or connect with adb shell and run: su restorecon -FR /data/media/0 That should fix the problem.

When does it show you this error? When you try to add a new card, or simulate an existing one? Also, are you rooted via SuperSU, or Magisk? And did you maybe try the option Advanced / Unlock system partition in the menu of the app?

Where do you see that the MAC address is changing? In WiFi settings? Since Android 5.0, Android is randomizing the MAC address when scanning for WiFi, to prevent hotspots from tracking you. But the MAC address used for actual connecting should always be the same.

Did you mount /system before? Normally when you start TWRP, /system is not mounted and only the bin folder shows up inside. The purpose of the permissions system is to disallow unauthorized users to change the files on the device. Permissions 644 / rw-r--r-- mean that the owner of the file is...

That's super weird, even if the bootanimation was malformed, the phone should start normally, just not showing the bootanimation. How exactly did you install it? Can you check in TWRP if the file /system/media/bootanimation.zip has the proper permissions (644 / rw-r--r--)? Did other...

I sure could! But what orientation do you want it? Should it be 768px wide, or 1024px wide? By the way, if you're playing with bootanimations a lot, I made a tool for resizing them, maybe you'll find it useful.

You need to change the permissions to rw- r-- r--, then it should work.

And which zip did you put there? The one you downloaded, or the one you extracted from the downloaded zip? And did you change the permissions?

How exactly did you install the animation? Via recovery or manually?

Then download some app like Terminal Emulator and run the command (without the 'adb shell' at the beginning) from there.

You can try running this adb command on your computer: adb shell am start -n com.android.settings/.DevelopmentSettings

SysLog works for me well on Nougat.

I extracted LiveWallpaperPicker from the CM 14.1 CAF build by experience7 and installed it as a system APK, and everything works nicely now. I'm attaching it here so you don't have to do the backup, install that ROM, extract, restore this ROM chain yourself, it's tedious. Just extract the zip...

I've just installed this ROM and so far it's a nice experience, thanks! Everything is working well, even Google Camera (both 3.2 and 4.2, although on 4.2 I'm not sure if HDR works). Could you maybe share how did you get it to work in this thread, so people can see what needs to be done and give...

Would it be possible to include this patch so that the core Google apps are granted the needed permissions by default and Google Play Services don't crash on first setup with gapps? Thanks :)

If you installed gapps at the same time as the ROM and you want to set up your Google account in the initial setup wizard, you can open settings even during that setup wizard over adb: Connect your tablet over USB to your computer In command line run adb shell am start -S...

Ziyan, can you put this in the first post, maybe next to the CyanogenMod downloads, please? In a big ass font? For people who shoot first and ask questions later? I installed CM yesterday, I set up my usual settings (including Live Display), and everything appeared to be working fine, but it...

I updated now to 1.22 and it works even without any songs, so maybe I had only 1.20 before, I'm not sure... thank you anyway :)

Hi! I have a bug to report: the application crashes immediately when I don't have any songs on my device. As soon as I copy one there, it starts working again. Also I wanted to ask - what ROM are you using? Or what is the statusbar theme you're using in the screenshots? It looks quite pretty...

No need to do anything, basically, there's just an extra file /system/media/bootanimation.zip on your device, you can delete it, but there's no harm keeping it there either.

This bootanimation will NOT work on newer Samsung devices with stock ROMs or TouchWiz-based custom ROMs. Samsung uses a proprietary QMG format for its bootanimations, and doesn't support the bootanimation.zip which is used here. There's not much that can be done about this, I can only recommend...

Yeah, I believe TWRP 3.0.1 and 3.0.2 fixed some issues with rebooting, so maybe it was a issue with TWRP all along. Happy that it works!

I don't have any shutdown animation, I don't think Nexus devices have it.

No problem with me, the animation was made by Google anyway, I'm just repacking it. And I think CM Theme Engine resizes bootanimations to your device's resolution. xdagee already made a theme with the animation, you can find it in his thread.

That shouldn't happen, strange. The bootanimation is not really important, and even if it's missing, Android should boot perfectly without it. The rebooting might be caused by some bug in TWRP 3.x, but I really have no idea now. Could you try to read what's written on the TWRP screen just before...

What happened when it failed? What error message did it write?

The problem might be that the Galaxy Nexus has a GPU too slow to play this animation in 60fps. The Galaxy Nexus has the same PowerVR SGX540 GPU as the Nexus S, albeit clocked a bit higher, but it has a much bigger display resolution, so when it has to play this animation, it has to push 2.4x...

If you have any CyanogenMod theme for bootanimation installed, then the animation will not change. You would first have revert back to the built-in system bootanimation theme, and then install this bootanimation.

That is simply not true. The animation should theoretically work on any Android device, and it should properly show the final part on any device with Android 4.1 or higher. Sure, some manufacturers like Samsung or Micromax change the bootanimation process in their ROMs, but in general it should...

You should use the 800p version. And wiping cache or dalvik cache isn't useful at all when changing bootanimation, so you don't need to do that.

You have to have a permissive zImage, and make some changes to the props and init scripts in ramdisk, see this post describing the changes. I took a look at the stock ramdisk from marshmallow hammerhead and I could find the place where to do the 1st and 3rd change, but I didn't see the place...

This happened to me as well, I found out that the power button simply broke off from the circuit board, I guess due to wear. I was able to find a workaround, I took off the top cover and pushed in a piece of a thick, sturdy paper (drawing paper / contact card or something similar, about half of...

It is one of the ways it should function, you can watch this video describing how it works. Basically if you pick up your phone, the motion detection turns on the ambient display. This doesn't happen when you have your phone in the pocket because of the proximity sensor, which detects your...