I have the most recent version of PH's blazer rom, v2.3 and have run into a bug/issue that I hope someone else has a solution to! After doing a full wipe and install of the rom everything works great, until I try to switch from the crappy samsung keyboard to the Android keyboard. The phone will completely freeze up and require a long hold down on the power button or a battery pull, but unfortunately after that the phone does not boot all the way, gets stuck at the glowing samsung screen. The only solution i've found is to:
A.) Wipe and reinstall rom after selecting the messed up keyboard input and
B.) Avoid switching to the android keyboard!
I was able to switch to swype just fine and I hadn't re-downloaded swiftkey to make sure it will switch too but I don't have any doubt that it will switch fine. A few more bits of info, I have tried downloading the rom three times thinking maybe a bad download, the md5 checks fine and all 3 downloads gave me the same result.
Am I missing something idiotic or can anyone else replicate this problem?
Related
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
DanielWGK said:
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
Click to expand...
Click to collapse
Did you try a restart, I have heard of camera problems like this before (i think first FroYo update) and all it needed was a simple reboot.
Reboot didn't work. I reflashed the rom and BAM, it worked again. Crisis averted.
I have the same problem.
I'm running the following:
Azreal 3.0
circular battery widget update
removed HTC lock screen
superior battery charging kernel
wifi hotspot patch
I'm currently trying things to figure out what will fix it.
Here are the current things I have tried that did NOT fix the problem:
Reboot
Wipe cache/davlik cache
fix UID mismatches
I then reflashed azreal 3.0
At this point the camera worked again but everything was wiped. I then reapplied the following patches:
Circular battery
remove HTC lock screen
wifi/hotspot patch
after this everything continued to work
I then applied:
superior battery charging kernel and it broke again
I think the problem is the superior battery charging kernel
i am having the same problem and have not been successful yet fixing it. switched from cm7 back to stock to update my prl and tryed to use the camera while stock when the black blank screen happened. flashed to evdo(sense) and same result. flashed back to cm7 and the 1st time i opened camera it opened the ffc. when i tried to switch and everytime i have tried to open it since i get "camera error cannot connect to camera" help plz!
If you have HW 0004 phone or HW003 with the new camera, you have to make sure your rom has a kernel with the NEW drivers. The kernel in my signature has the new drivers for ASOP roms (like cm 7).
just flashed Savaged-Zen-V002-CFS-HAVS-SBC-WiMAX - GB.zip
with the same result running cm7. seems like ive tried 20 different things with no success. everything i have flashed has been off my sd meaning i have had all of it running before at one time or another with no problem. i really cant think of what ive done new to have caused this
Same here
Happened to me right after I flashed calkulins_format_all.zip and then the MikFroyo4.4.zip yesterday. I thought it was a problem with mikfroyo so I flashed Azraelz 3.1 and still the same issue (i was using azrael 3.0 with no prob prior to mikfroyo).
I'll post if I find anything that works, please also give any suggestions i'm willing to try anything b4 i take her to sprint.
I also flashed calkulins evio rom. When I flash back to stock it will start running again sometimes. Not even right away though. It will be black for a while then if I just let the phone sleep for a bit and come back to it bam. Camera again. For a little while. Then back to the same thing an hour later without doing anything! This is very frustrating! Someone plz help!
Sent from my PC36100 using XDA App
UPDATE
I turned my phone off and switched SD cards to one that has an old backup (3.29, kernel#11), when I booted into recovery, I could hear clicking noices coming from the lens, at a super fast rate (say 2-3 clicks a second).
Not wanting to do any more damage I turned off the phone.
I did just take my phone to sprint to fix my kick stand, maybe they did something to mess with me (thats just my paranoid side speaking)...
But what gives? What would make the camera shutter do that while im in recovery (btw using latest amon ra recovery)?
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
I'm running CM 6.1.1 Stable on my G2 (just a couple weeks old) and I've noticed that my home button doesn't work sometimes. It works about 95% of the time, but then it will do the occasional hiccup where nothing happens. If I touch it a few more times it will eventually start working again. Not sure what it is, but I read in another thread here that it could have something to do with how the CM ROM is configured for capacitive touchscreen sensitivity. And I believe I read that this has only been reported in CM and not other ROMs.
dutman said:
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Does it completely not working??, delayed maybe??
Sent from my HTC Vision using XDA App
Had this issue yesterday. I did a factory wipe from Clockwork and reflashed CM. Fixed it.
even iam facing the problem, but i guess mine is worst as the all(4) softkeys doesn't respond, but when i press it, i receive the feedback i.e it vibrates.
2nd issue: my physical keyboard layout is pretty much messed up, the symbol key which i press on my keyboard doesn't display the exact symbol
it would be kind if someone offer some solution for this
Rom: CM 6.1.1 (even tried nightly build #85)
Build: HK
P.S: i never had those problems in the stock rom
I'm having the same problem with CM6.1.1. I noticed it after installing Twidroyd app. I couldn't exit it via the home button...had to back all the way out. Uninstalled and still having the problem. Doesn't seem to be working at all now.
I had this sort of problem with my G1, I flashed the BiffMod ROM and some day, the phone just randomly did a factory reset, the background is set to how it was when I first flashed it and the home screen was back to normal like how it was when I first flashed it. My home button would not work, when I pushed the end call button to put the phone in sleep mode, it would turn off but if I were to press it again,the screen would turn on but it didn't go to the lock screen it just turned on. To fix it I went into recovery and wiped all five(I'm using Amon_Ra's recovery on it) then I booted back up and my home button worked again and when I put the phone to sleep, it turned back on like normal with the lock screen. That has happened a few times, some times when I did the wipe, every thing would start working again and my home screen still had everything placed where it is suppose to be. You could try to wipe everything, but I can't guaranty it because I don't even have my G2 yet so this has never happened to me on a G2.
i wiped everything data / cache ,flashed GingerVillain 1.4 , the softkeys won't work even in this rom, the only place where softkeys work is HTC's Stock rom. iam just wondering is it due to my build, as its Hong Kong build, so there is a possibility that the keymap for softkeys are different?
Update: Fixed! http://forum.xda-developers.com/showpost.php?p=9353194&postcount=1
Good Afternoon,
I flashed my phone with a bunch of stuff a few weeks ago, and it's been running spectacularly, but the past few days, I've been having some issues getting my phone to boot completely. ADW would keep force closing, and my phone would randomly reboot, and I'd sometimes need to battery-pull to restart it from being frozen completely. Also, my volume buttons no longer work, and the screen occasionally goes 4-split screen from the keyboard opening ( I'm assuming flex ribbon ). Now today, after the the splash screen, the phone screen just goes black and stays like that. From reading around, I think I know what the problem is, but I was wondering if anyone more knowledgable could give some insight as well, specifically, if there's any chance it could be a software issue and **crosses fingers** not a hardware issue. I attached what I could get of the adb logcat.
Also, if it helps, here's some info about my phone:
Rooted & S-Off, with newest radio
Rom: nickmcminn60's XM-8 Vr 1.1
Kernel: Miguel's
Mods: darktremor A2SD & ?Firerat's? Custom MTD Partition
Any help or advice would be much appreciated.
1) don't use Miguel's kernel with these latest builds.
2) did you fix permission with rom manager to help with fc's.
3) I don't think this will fix the screen issues, that's is mostly hardware related.
Sent from my fingertips using Android.
Thanks for the help! I hadn't done fix permissions yet, as last time it somehow broke my rom. Unfortunately, I tried doing a nandroid backup first, yesterday morning before trying fixing permissions, and after my phone finished and rebooted, the phone just froze, and I couldn't reboot into recovery ( my volume buttons don't work ), and after a few reboot attempts, my screen died. I'm going to try ADBing into it tonight if I can.
In case I can get it fixed though, what kernels should I be using instead? I tried drowningchild's, but I seemed to have fewer issues with Miguel's.
Use stock cm kernel when using cm roms if using sense I believe nbetcher has a good kernel
Sent from my fingertips using Android.
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
jr8801 said:
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
Click to expand...
Click to collapse
Looks like it might be a kernal problem. Have you flashed back to the stock kernal? If not, I'd look there first
yeah i flashed stock kernal as well...problem still persist
uninstall Google+
no google + never have had it.
Have you tried flashing CM7 Alpha #2? I had that same problem with Alpha #1 release then flashed #2 fixed permissions. Then at first start up i rebooted with GPS on and voila! No more phone FC.
I started with Alpha #1 where the problem started flashed over #2 fixed permissions and same problem. thats when i started flashing the other roms to try to solve the problems but this hasnt helped. So i odin back to stock. flashed stock kernal and stock recovery. and i still have the problem.
What sucks is im just graduating college and im starting to receive calls from future employers and i cannot talk for more then 2 minutes before my phone decides to shut off.
So any other advice???
bump it up. Any help please...::
what it is doing now update: I click on a contact or type a number and press call and the screen turns black except the status bar. soft keys dont work, hard keys dont work. phone is a fail. people can still hear me and i can still hear them but the phone is unusable and i have to pull battery to get out of the black screen.
This was doing it on every rom and i have now put beastmod v2 4.0 still no luck :[
I just received my White GS2, finished the OTA update.
And yes, the dialer FC on me every single time once I push the hangup button.
I was trying to activate the AOSP lockscreen on the HTC ONE M8 on Verizon. I succeeded in that, but when I read through the walkthrough further it said there was a way to keep the Touch Twice to Wake and fast charge features. So I continued on to flash the Bulletproof Kernel. I, sadly, didn't pay attention when it said it worked on everything except the Verizon version. Now, I lost my soft buttons and have to reboot anytime I want to switch applications. I've found similar problems, but they were unique to settings found in Cyanogen and other roms. I'm mostly completely stock. It's been suggested that I try flashing Cyanogen or something, but I'd really like to keep the camera and IR functionality.
Solutions I've tried.
Rebooting 20+ times. Didn't work.
Draining the battery, and recharging, and rebooting. Didn't work.
I found a stock kernel and flashed that. Didn't work.
Loaded the backup I had from when I installed CWR. Didn't Work.
Wiped all cache and factory reset. Didn't work.
I'm now out of idea's and need some help. Anything guidance in the right direction would be greatly appreciated.
This was the how-to I was following: htc-one.wonderhowto.com/how-to/activate-hidden-aosp-lock-screen-your-htc-one-m8-0154651/
EDIT: I just put a ROM on it. Fixed my problems for now. I still have no idea what happened though.