[Q] Screen off animation - Wildfire Q&A, Help & Troubleshooting

Hello.I would like to ask if screen off animation works on cyanogenmod 7.1 rc1.Thanks for reply.

It's random it seems. I haven't got it to work, but, it works for others, and, you can find many solutions like rebooting, clearing dalvik cache in Recovery then rebooting. etc. (Didn't try any though - I can live without the screen off animation)
But again, as I said, its random,

On Ruymanca v7.2 it works without a flaw.

Related

[Q] Home screen keeps crashing / looping every time i change roms

I have been having a problem every time I change roms where after it boots up, i get maybe 5 minutes to play around and then the home screen crashes. It reloads, finds a signal, media scanner running etc, just like i just turned the phone on. Before I can do anything, it crashes again and repeats forever. Its not boot looping though. But it makes the phone useless.
This happened last time i tried the 12 lockscreens mod (im on calkulins 2.8.1), so i had to wipe and reflash calks rom since my backup was bad. Then i made another backup to be safe, which is working. Today i tried flashing blu kuban by rujelus22. Same thing happened. Which makes me thing there is a deep seated issue somewhere in the phone.
Every time i flash a new rom, i wipe cache and dalvik, and format system. I also tried a factory reset. Nothing solves my problem and I cant find anything similar anywhere.
I really hope one of you has a brilliant idea for me because I really love this phone, but If im stuck with one rom forever I would be a very sad panda
BTW i have to thank all the devs for all the sweet roms and hacks, you guys rock
Download calkulins wipe all.zip
Run that then try to flash your rom
Also in CWM run the fix permissions option....that usually fixes alot of issues
Sent from the near past

[Q] CM10 suddenly unstable after reboot.

recently flashed cyanogenmod 10 (stable) to my sgs2. It worked wonderfully until my first reboot, then any app, including settings would freeze and need to be killed. I tried fixing permissions, but would get stuck at the boot animation. tried wiping cache, again stuck at boot animation. restoring from a backup made before the first reboot works fine, but sure enough the same stability issues come back if I reboot the phone.
Anyone have any idea whats going on or how i can fix this? I searched for a while for similar threads but couldn't find anything.
so ronrey.

[Q] [CM10.1] Using lockscreen shortcuts causes restart

I'm currently running Cyanogenmod 10.1-20130403-Nightly with the 20121011 released of gapps for Jelly Bean (both flashed with TWRP with a davlik cache wipe) and I have a very odd issue. I've searched high and low and can't seem to find someone with the same issue. Basically, unlocking the screen with a custom shortcut (not the default unlock one) causes my phone to soft restart. I don't see the Samsung logo so I think it's not a full restart. Does anyone have any clue as to what could be causing this? I've made sure that this isn't a one time thing as it happens with every custom shortcut I add. I haven't done a factory reset since I haven't done a backup yet and I'd like to see if this could be fixed without having to do one.

Reboot on start with CM roms

Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.
dissonance01 said:
Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.
Click to expand...
Click to collapse
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?
audit13 said:
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?
Click to expand...
Click to collapse
Thanks for the reply, sadly yes I've wiped pretty much everything but the sdcard in between installs. ROM's like OH!NO!'s v20 work fine.
Thing is I used to have CM10 installed before (and even had 10.1 but it was a bit unstable), until one day the phone had a random reboot and then would not stop boot looping. I stayed with v20 for a while before trying at CM10/10.1 again, and now here I am
EDIT: I just tried OH!NO!'s CM10 hypersonic which works great... until I reboot, and from that point on it just boot loops. I wiped data, cache and dalvik after that and now it's just like the others, reboots on pressing start >_<
Maybe there is something wrong with the hardware?

Getting bootloops after rebooting for being laggy

Hi all, I would like to have some feedback if some of you is experiencing the same issue as I am. My N5X is running Stock Marshmallow (latest release) and it's rooted (SuperSU v2.71) with Xposed (latest version for arm64).
Every now and then (usually with an uptime more than 80 hours) the device becomes very laggy and my usual solution for eliminating the lag is rebooting. It would be the ideal solution if only the device wasn't remaining stuck in bootloop after rebooting.
For now the only "solution" I have found is doing a factory reset from TWRP, after performing a backup of /data. Uninstalling from recovery Xposed or simply wiping cache/dalvik or even flashing separately the stock images (boot, cache, system, vendor) did nothing without a factory reset.
The first times I got bootloops on the device I knew why it was happening (one time I modified build.prop forgetting to change the permissions, another time a similar thing but with the transfer of an app in /system), but these kinds of bootloop remain a mistery for me.
It also occurred without Xposed installed and with both stock and ElementalX kernel.
A peculiar thing I noticed while in TWRP is that the Cache was displayed occupying 0 MB. Might it be related to this issue?
Now, I know now that I should probably reboot more often, but I still would like to know why this happens because it's being very annoying doing the restore procedure every damn week.
And so, while doing my research, I wanted to have some feedback from those of you who had similar issues with a similar setup.
Thanks and cheers!
A new kind of problem occurred. This time Telegram wasn't connecting to the net and so I rebooted. And BOOM, stuck at the boot animation (the four colored points) for no apparent reason.
If I only wiped Dalvik and Cache in recovery, the phone would go past the boot animation, but after the Android logo, it would display only a black screen.
This time, before doing a factory reset, I flashed via fastboot boot, cache, system and vendor, hoping that could solve something for the future.
I have no idea why this is happening. After the new reset, I will try to limit the modifications to /system by not installing Stericson's Busybox and GSam Root Companion app, but I'm still wandering in the dark. It looks like my 5X is possessed.
Please, if you have any sort of feedback or insight, I will gladly listen.
Update: today I had no issues but I rebooted anyway. Result: stuck at bootanimation.
As you English speakers say:"F*ck this sh*t, I'm out".
Yeah, I decided that I'm done with the stock ROM and decided to flash PureNexus ROM in the hope that the **** up I was doing with the stock ROM will never happen again.
Maybe now the mods can close this thread.

Categories

Resources