All alphabets disappear leaving behind a blank white space.
Having the issue since the last two versions.
Any workaround?
EmuI 3.1
Sent from my PLK-UL00 using XDA-Developers mobile app
@jayesh113.60 hello, are you on a custom ROM, or rooted your phone? As this problem is not happening with anyone I guess. Try uninstalling the update, and redo it again. If that doesn't works, try wiping dalvik-cache and see.
Related
Just wondering if anyone can help me out. A few days ago I installed the new market apk that was floating around. It installs fine, and once it loads the main title screen it FC's.
I've tried all install methods, uninstalling the old, overwriting the the vending.apk.. as well as combinations of wipe cache/data for market, and market updater. I've also tried wiping cache/dav cache as well.
Now tonight I just tried the updated gapps package.. flashed from CWM, and same problem.
I'm telus fascinate, cm7 galaxysmtd70, glitch v11.
Any help?
Thanks.
FYI, I have CM7 Build 3 from nightlies thread.
I installed the new market ('vending.apk'), it is not fc'ing for me. But it does seem to take longer to load than the old version of the Android Market. My LauncherPro, however, does force close from time to time.
Try running 'permission fix' from ROM manager that came with CM7.
I ran this fix and the first time my phone booted, it was on 'safe mode.' Pulled battery and everything was fine. I have yet to find any fc'ing issues after doing so.
Try your luck!
Go into settings then force stop and delete data for Market. Reboot, then try opening the Market.
Thanks for the suggestions, but neither worked. I got to figure this out. If I do, I will keep this post updated.
I cannot figure this out for the life of me. I've tried everything. Including full wipe and reinstall. Still getting the FC's.
MrManiacNF said:
Now tonight I just tried the updated gapps package.. flashed from CWM, and same problem.
I'm telus fascinate, cm7 galaxysmtd70, glitch v11.
Any help?
Thanks.
Click to expand...
Click to collapse
which recovery did you try to flash the gapps. zip with? Did you use the power button menu reboot recovery...or did you three finger boot to recovery?...im just saying I've done it by accident/force of habit!...just covering the bases since this is the first I've heard of gaps not installing correctly or fc'ing left and right on anyone.
Sent from my SCH-I500 using XDA App
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
Hi.
I'm on my 2nd S3 now. First one suffered from the "sudden death syndrome".
My 2nd S3 has been perfectly fine bar the odd lock up. It's rooted and flashed with Supernexus by Faryab on v4.2.2
It has been freezing a lot lately, maybe 3 or 4 times a day but over the past few hours, it's now locked up approximately 20-30 times and I have to keep the power button pressed to reboot it. I've uninstalled any apps I have installed over the past few days. Booted into recovery and cleared cache and davlik cache (it's now saying Android is Upgrading upon every reboot). I can't even get time to backup my apps using Titanium Backup without it crashing.
What is going on anybody? Any help is much appreciated.
Try having a read of the freezing thread over in general.
boomboomer said:
Try having a read of the freezing thread over in general.
Click to expand...
Click to collapse
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
5aq1b said:
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
Click to expand...
Click to collapse
I guess i spoke too soon. More crashes again today
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
cooza said:
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
Click to expand...
Click to collapse
Hey, yeah I did a full wipe including system format before I installed the new ROM. I've had this ROM for probably 3 months now and haven't had any problems with it up until the last few weeks. Infact 4.1.2 was killing my battery in a matter of hours. 4.2.2 ROM made me love my phone again as it fixed my battery woes!
This is so frustrating...
4.2.2 being a beta version can do this but re-installing can sometimes cure it though. Changing the kernel in 4.1.2 can give you better battery if you play around with a few and if course is more stable being an official release too. You can also try a different 4.2.2 ROM. They aren't all the same.
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Same Problem
5aq1b said:
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Click to expand...
Click to collapse
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Niko_v said:
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Click to expand...
Click to collapse
I think you may have found it
Wifi for example is controled by the kernel but there is no source codes released by Samsung so thats why there are no custom 4.2.2 kernels available for the S3 or you could flash one and most likely sort the problem out.
Its a shame cos there are for other phones on this version.
Hi dude
I went to the freezing thread here and found that the DFG method solved it all. So for anyone willing to try this please head over to that thread or just download the dummy file generator apps (2 in app store) although one is only necessary.
Gl and ty for the reaponse
Xda 4life
Sent from my GT-I9300 using xda app-developers app
I got huawei G510-0200 from friend to try to fix it. The phone is allready rooted and has installed a custom ROM(SlimKat 4.4) and TWRP recovery. But when the software is booted up, all the time i get the pop up message of applications crashing(play store, messenger, nova launcher etc) and i didn't run any application. So here's the real problem... When i access recovery and try the full wipe, factory reset or installing new rom, twrp reports that actions are successful but nothing happened. Nothing has changed. The phone was not reseted, data and applications are still there and same rom is still running. Someone told me that issue could be partitions.
Anyone had this problem, any ideas how to solve it?
Thanks in advance...
Sent from my P5_Quad using XDA Free mobile app
Hello guys,
as some of you may know, there was a bug in which when camera app was started, it appeared only a black screen and the camera buttons. So i've had this problem in months, but in the last 2 weeks, the camera stopped working at all.
I didn't reinstaled the android via SEUS, cause i've waited for lollipop to come, hopping that it will solve the problem.
Today, the update came, i have now android 5.0 but guess what? The camera STILL doesn't works.
So please if any of you had this problem and know how it can be fixed ....
Thank you.
any help anyone? i've tried everything - wiping cache, clearing data, force stop, disableing camera, nothing seems to work. Should i try a repair via seus? Does that helps better than updating to lollipop through the same method? no one seems to know anything else besides clearing app cache. If it helps, any other camera applications, doesn't work
pilifida said:
any help anyone? i've tried everything - wiping cache, clearing data, force stop, disableing camera, nothing seems to work. Should i try a repair via seus? Does that helps better than updating to lollipop through the same method? no one seems to know anything else besides clearing app cache. If it helps, any other camera applications, doesn't work
Click to expand...
Click to collapse
more info about the problem please. Stock ROM? Rooted? Installation method...etc
- i had android 4.4.4 romanian version, i updated via sony pc companion to lollipop . Not rooted on 4.4.4 and not on 5.0
I had this bug once, then I reboot the phone and the camera is working fine...
Android version is 4.4.4 .167 firmware
Sent from my D6543 using XDA Free mobile app
You might wanna try to flash the stock ftf again