First off, using Velocity 1.2b18 on an old LG Ally. As the thread title says, it's based on (ancient by this point I guess) Android 2.2.2/Froyo.
Velocity comes with a modified lock screen font that has a square/robotic/futuristic/etc font chopped in for the numbers. Since it was about as far from matching my launcher clock font as it could possibly be, I figured I would simply switch Velocity's stock font for that of the launcher font. Others have apparently done this in the past, it seemed simple enough, so I figured...why not?
I used 7zip to grab the font from the apk it was in, dropped it into my SD card, and started the process. I did the following in Total Commander, while the phone was running; in hindsight I realize this was a terrible idea. Anyway, I copied the replacement font into the fonts folder, renamed it to Clocktopia.ttf, and renamed the old one Clocktopia.old. Then I exited and tried to lock the phone.
It tried to shut off and lock, came back up, then the screen shut off again. After that, whenever woken up, the key lights and backlight would come on, but it simply freezes on a black screen. Opening the physical keyboard (which would normally auto-unlock) does nothing, and it won't go back to sleep via the power button. Rebooting the phone, since it normally boots to the lock screen, has the same result.
"Ok," I thought, "so I'll simply remove the replacement font and re-rename the original and all will be well". And so, booting into recovery and accessing the phone from adb, I did just that. Rebooted the phone after this: same result as before. A bit of googling suggested clearing the cache when messing with fonts, so I cleared both caches and rebooted: same thing.
I've since made a nandroid of this apparently now borked android installation and restored a backup from the middle of the month (note to self: backup BEFORE screwing with things I don't fully understand next time), but my questions are...where did I go wrong? Was it that I performed the replacement while the phone was running? Why didn't restoring the original font reverse the effects, and is there any way to save the backup from its currently screwed-up state?
Related
I tried to install the latest update for my acer tablet. My tablet is unrooted and it was doing fine with the android icon with spinning gears and a progress bar. Though it froze and stayed froze...i had no choice but to reset. Once I did though the system would come back up to the slide your finger to unlock screen, my same background was working but a vibrate would happen (before touching) and after that touching the screen wouldn't do anything or react so couldn't slide to unlock. After this, I tried the plus volume button + power+ moving the orientation switch on and off. This got my old background to go away so something happened but it never reset on its own as it was saying: clearing user data and clearing cache. After that i shut it off again and rebooted using the minus volume. It said it was going to revert back to some file. The friendly android robot with spinning gears occurred then shortly after the progress bar came up that friendly android was replaced with an android icon with a big yellow warning sign in it (exclamation point) as far as i can tell nothing happens afterwards. After a few more reboots and + trick i can get the system to boot (no drag finger to unlock) but the minute it gets to the home screen the "shutting down" dialog shows up with the "powering off" message. It never goes away, tablet never shuts down. This happened REPEATEDLY. I did contact acer tech support; and since the first time it didnt reboot on its own after clearing user data and user cache he said its a hardware defect and to return it. I do hesitate to believe that cause I have babied this thing. I wonder if its an odd software error?
Now if i just let the tablet boot up it will come to that home screen with that shutting down dialog. And sometimes i swear a message box pops u behind it I cannot click on it (i swear the dialog that pops up behind the powering off dialog is something about the apk installer). I cannot get to the privacy ->restore to factory defaults...cause everytime i make it to the settings screen and click okay or something the home screen comes back and everything else go s away...so can never click on anything in the settings without it fading away. Which means I cannot click privacy -> restore factory defaults. So now my acer just boots up and says shutting down right away and does nothing else. Its clear of the apps i had on it, but st still not coming up. Am I missing some other step to the process or is the acer device really going to be needed to send out? I think i did everything right but wondering if anyone else had the boot up and then see the shutting down/powering off dialog the whole time... it should be noted that it never actually does shut down.
Any ideas or help id love it!
I don't own a tablet, but here is a thread that you can check out. Hopefully it will help you out. Good luck!
OK, so I successfully installed the ROM. It works fine and all until I actually use openscript on the terminal. For example, I wanted to change CPU frequency. I changed it, quit the terminal, and checked the frequency in system information. It was successful. But After about a minute my screen suddenly locked and here is the current situation. The locking screen works fine (I had the pattern lock), I can even open emergency calls. But when I unlock it, the only thing I see is the notification bar (which works btw, clock, wifi , all the icons are there, I can slide it down and up and so on). Everything else is just black. The buttons work - I can quit the notification tab buy clicking back or home or something like that. But I dont see my home screen, menu, buttons - nothing. I can lock it again, and it works fine again in the lock screen but afterwards same black screen again. Reboot does not work.
So I reinstalled the rom. Immediately after installing changed the frequency and waited for a bit. Everything was fine. I installed all the crap I usually have and kept using the phone. But the next day, I got annoyed by the music player and decided to change it again via the openscript. Same thing happened. And this is where I am stuck right now (actually this is already the third time I have this problem in 3 days and it's my third reinstall of the rom, but the first one also happened after using openscript to change frequency.)
So is there a way to fix this without reinstalling the rom again, cause I've customized the **** out of it and I don't wanna do it again. If no, how can I prevent this in the future?
P.S. If this helps, when rebooting, I hear the sound before the android splash screen which is sometimes skipped and sometimes shown for an unusually short time.
P.P.S. Also, I have the apps2sd flashed.
Any help would be appreciated.
Thanks.
Got same problem
Hi,
Even I got same problem when I tried to change boot animation. Just blank screen.
But i realised it is due to, launcher app is not initiated. So tried a trick which worked indeed
Trick is when u are in a blank screen, click "HOME" button which will pop u up the list of launchers u have. Click One of them though they r not visible
Voilaa!!! Your screen is back
Regards,
Murali
Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
Hi. Today I rooted my phone using Odin 3.7 and Siyah-s2-v6.0b5 kernel, everything went fine, installed few applications like Smart Launcher, customized everything and messed around with a phone but after few hours noticed that my menu and back button lights stay always on. I tried everything, turning energy saver on and off, changing button light duration (off to on etc) and nothing helped. Lights kept staying no matter what. They only turn off with the screen (I changed the setting to 15 seconds). Why is that?
Yes, I did factory reset too actually. All my applications are now gone (I hate doing backups, but whatever) and I thought it will sort this issue out but it didn't help. Is there something that could be done without flashing ROM or kernel again? I'm paranoid of bricking my phone.
I googled and seems like I'm the only one with this problem. Android version 4.1.2. First time noticed this problem today after rooting.
P.S. I tried also some moderators solution here: sys/class/misc/notification/led_timeout change value to -1 but no effect, value doesn't change, reverts back.
EDIT: sorry I don't find the option to delete the thread. The problem was solved using STweaks application (got the idea from some member here to edit option in BLN folder) and I set timeout to 1 sec and everything is fine now. Thank you stranger very much.
I'm at the end of my rope with this. Several days ago my s5 started refusing to drop down the notification panel and the quick settings menu. I'm running stock rooted kitkat 4.4.2. I did a factory reset, disabled xposed (in case some notification bar mod was causing this even though I hadn't changed my xposed settings for months), got a replacement SIM card, went back to an earlier version of google, and now sometimes it will work for a whole day and then stop responding again. I took out the external SD card and it still does it. I uninstalled anything new (not much) that had recently been installed. I have been using Nova as my launcher, so I tried going back to just Touchwiz, but no change.
It's not just the drop down screens, when I open Titanium Backup and try to use the "clear" or "menu" buttons at the top of the screen, they don't respond either. It's like something is freezing the top half inch of the screen (I measured it in frustration).
I went into the diagnostic menu and checked the screen and everything is responding as far as I can tell--the line goes up to about an eighth of an inch from the top of the screen but the pictures for this when I googled looked like that so maybe they aren't supposed to reach the actual top of the screen.
Googling shows that several models at least of Samsung, and even some Sony, are showing this problem and nobody seems to know how to fix it.
Has anyone got any clues they can give me about this? I can't seem to find what the problem is.
Update--I tried flashing Hispasian Kernel but it didn't solve the problem. I tried defrosting everything I had frozen with Titanium Backup and that didn't solve the problem.
Flash latest stock lollipop FOL1 and see if it's still there. If that doesn't work then you have a hardware defect and you'll need to get your phone repaired.
That's a good idea. Thanks!