Hey. Was just using Emoji Switcher when suddenly, all my emojies disappeared. Now on the smilies tab I only have a couple emojies, including a smileyface and a skull head. What do I do to fix this?
Can't seem to find out anything about this issue anywhere else either - not even anything related to it.
and now after doing cache/delvik wipe I'm stuck in a bootloop. This has been the weirdest day.
More information please, if you really wanted help you would have, right? I need info such as device (how did you not state this), rooted? Xposed? Romed? ANY modifications to software? Android version? What have you tried to fix this issue (all things).
Related
Hi everyone.
I have recently upgraded my SGA from original 2.2.1 to 2.3.3 XXKPE and i have detected an issue when i try to use the WPA + AES combination. The phone detects the wifi but it tries to validate the password a few times and then it is disconnected...
When i tried to connect with the older firmware (Froyo 2.2.1) i could connect the first time but when i lost the connectivity my wifi changed it's state to error and the only way to reconnect was restarting the phone.
No issue detected with WEP or WPA + TKIP.
Anyone else has the same problem? If not, can you tell me your firmware version?
Many thanks in advance
Same situation: S5830 + ASUS WL500W works only with WPA TKIP. But with TKIP speed is limited to 54mbps. Android OS 2.3.4
Just picked up a Samsung Galaxy Ace running stock Android 2.3.4 (baseband S5830LUBKP7, kernel 2.6.35.7-perf-CL366939 [email protected] #1), and seem to be having this same problem.
My home wifi is set to WPA2 Personal+AES, and when the correct passphrase is entered, the Ace just continuously cycles through "Connecting... Disconnected", over and over.
If I drop back to WPA Personal+AES, I get the exact same thing. *However*, if I drop to WPA Personal+TKIP, the phone connects immediately.
I really don't want to use TKIP, as it has known exploits. Is there a known FOTA update for a US-market, unbranded Galaxy Ace that fixes this, or is there any known workaround except "don't use AES"?
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
evilxdeadly said:
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
Click to expand...
Click to collapse
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
knoxploration said:
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
Click to expand...
Click to collapse
Just update it over the air from setting -> about/phone -> update.
Make sure you have backed up the data like contacts and sms.
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
alexnm said:
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
Click to expand...
Click to collapse
Check the OP date?
Oops, didn't see that, sorry :$
alexnm said:
Oops, didn't see that, sorry :$
Click to expand...
Click to collapse
No need to be sorry. You're replying to a thread that's current, in that I replied to it with my own problem. (And I did so because it was the only thread that came up in the Ace forum on a search for AES, which seems to be specific to the problem. Didn't seem to make sense to start a new thread when this one covers the same topic.)
Hello people, I have a rather peculiar issue with my SII
I have had this issue for some time now and really doesnt bother me that much, its just annoying. And its just now that I have bothered writing a post about it.
If Ive run out of battery, I plug my phone into the charger, turn it on while its charging, I get no service, not prompted to input PIN and get the Uknown IMEI\baseband version. But if I let it charge a couple of minutes, unplug the charger and turn it on, everything works fine. Whats going on here?
I think this problem occured after installing one of bmarko's MIUI roms. I have since full wiped and restored stock rom. Upgraded two new official samsung roms as they have been released, currently running XWKI8 unrooted completely stock and the issue still persist.
I have searched around and there are similar cases out there but not really any clear solutions. Theres even a post over at cyanogenmods forum site, but no replies.
As said earlier its not really a big issue for me, not expecting a immediate solution but I would really like to understand the problem if someone has the information since I dont have the technical competence to understand it myself. I obviously havent corrupted or lost anything in my efs folder since its working without the charger, or? Could there be remains of a bug from another rom still in the system causing this?
Any replies would be appreciated, thanks.
Same Problem
Hey FlipTrick,
I got exactly the same problem. Dont remember how it happened exactly, but do remember I didn't do anything exotic. Can't display my IMEI, unknown baseband version and no prompt for my PIN.
I Tried several things:
- Reflashed the advised codeworx kernel using odin.
- ReInstalled CM 7.1 and tried nightly version.
- Reflashed different RADIO ROMS from XDA (goo.gl/TjoaM)
Nothing worked. Does anyone know what the problem might be? Or know what I could try next?
Greetings,
Xianduras
I had this problem once when I used a jig to reset the flash counter. Given the modem (and the IMEI) wasn't showing up in the phone details, I reflashed the modem which fixed it.
Occasionally after a reboot my modem/IMEI details take around 20-30 seconds to appear, but they've never not turned up/left me without service apart from that one occasion.
problem gone?!
Problem seems to be gone, noticed it after flashing Hydrog3n rom. Cant say if thats the solution though, havent tested it for awhile and i've flashed alot of roms
After I updated the phone to 4.3, all my apps/widgets keep on disappearing. I have to turn the phone off and on to fix the issue. The phone is not rooted or been modified in anyway. I don't want to try a factory reset yet unless its the last thing I have to do since it is not my phone, its a friends phone. Has anyone had experience with this issue or know how to fix it.
Thanks in advance for any help that is provided.
Hi guys, this morning my father's Le Max 2 (snap820, 4/64) stopped receiving calls, and both the home and recent apps virtual buttons decided not to function, too. Strange enough, I'm able to long press them and get the action I'm supposed. Any ideas/fix? I've already checked the phone for malicious apps and misconfigurations
Hi, I have exactly the same issue, plus I cant download any more applications from play store. Can anyone help?
If you have a backup taken when the phone was working well, I'd suggest you to restore it. If not, try another ROM, or at least a different ROM flavor (if it had an EUI based ROM, use LineageOS and viceversa). If that doesn't work, you may need to get into Qualcomm recovery mode and flash the developers ROM to get the phone to a real factory state.
But first, try to revert to factory settings from the current ROM, and see if that solves the issue.
There are several threads here with info on how to apply the above solutions.
If none of these solutions works, and you still have warranty time left, you may want to contact the seller for a repair or replacement.
Good luck.
Do the notifications work?
I was on holiday, so no PC I could use for flashing or else. A reset from the settings worked, still don't know what caused the issue sadly
I couldn't find the fix for this in any other threads, can someone help a not-terribly-tech-savvy person with a fix for this
Today I also had a same problem. So just I backed up all important data's and done factory reset. Now everything works fine.
Everyone have same problem at the same time means the ROM has virus or Trojan.
What is the ROM everyone is using?
ANDROID WEAR 2.0 - ISSUE?
When accsessing recovery mode, I cannot actually use any of its options as the touchscreen doesnt respond. I am able to get into it but I cant go down (I would like to clear cache partition.) This is only an issue as of build NWD1.170706.001 (Wear 2.0.0.161057753). I dont need to use it as its not a huge problem, but I just wanna know if anyone else has experienced this on their Asus ZenWatch WI501Q. (Large model)
nathandavies386 said:
ANDROID WEAR 2.0 - ISSUE?
When accsessing recovery mode, I cannot actually use any of its options as the touchscreen doesnt respond. I am able to get into it but I cant go down (I would like to clear cache partition.) This is only an issue as of build NWD1.170706.001 (Wear 2.0.0.161057753). I dont need to use it as its not a huge problem, but I just wanna know if anyone else has experienced this on their Asus ZenWatch WI501Q. (Large model)
Click to expand...
Click to collapse
Yes i have the same problem
Me too but why. No function by swipe up or down.
Since update to 2.0 my watch is useless. No connection to my mobile. No copy from my Google Account. Asus support is not responsible. disastrously
Seems broken a bit yes. Well, but why don't you use fastboot to clear whatever you want?