Hello,
i made the B520 update for my Huawei P6 (european) a week ago.
(never updated, completly stock, no root, bought on september 2013)
Everything works good except when i got new voicemail (with the notification icon),
the arrival of new voicemail seems to make it crash... i can reproduce it easily.
The phone freeze, something like "com.android.phone isn't replying" (in english i guess)
appears, and i have to wait, or close.. i can eventually restart the phone to make it come back
faster if i choose to wait.
I wiped cache partition but the problem is still here.
What should i do?
Change Update? Downgrade?
Thanks for your help !
Tried so far:
(no apps installed, not even my google account set)
B708 update => same problem
other sim (same operator) => same problem
B709 (oxalis) update via TWRP => same problem
Full swipe dalvik etc => same problem
Safe mode => same problem
downgrade to b111 (Jellybean) => problem disapeared
go back to b708 => problem came back
i like the kitkat... i would like to find why it does that... it's like
my phone does not support kitkat.
i tried to log information with adb logcat, but there is so much
data...
as soon as i got the "voicemail" icon notification, the phone (com.android.phone) freeze,
even if i open or don't open the notification it will freeze the phone app.
i can't eventually post some adb logcat logs where it freeze
sometimes the freeze make the phone loose signal for 5 minutes, like to no network,
then it come back
Thanks for helping
Try the B125 or B132 and then move to b512 or simply stay on B132
Waouais said:
Tried so far:
(no apps installed, not even my google account set)
B708 update => same problem
other sim (same operator) => same problem
B709 (oxalis) update via TWRP => same problem
Full swipe dalvik etc => same problem
Safe mode => same problem
downgrade to b111 (Jellybean) => problem disapeared
go back to b708 => problem came back
i like the kitkat... i would like to find why it does that... it's like
my phone does not support kitkat.
i tried to log information with adb logcat, but there is so much
data...
as soon as i got the "voicemail" icon notification, the phone (com.android.phone) freeze,
even if i open or don't open the notification it will freeze the phone app.
i can't eventually post some adb logcat logs where it freeze
sometimes the freeze make the phone loose signal for 5 minutes, like to no network,
then it come back
Thanks for helping
Click to expand...
Click to collapse
Hello,
problem gone with installing Cyanogenmod 11 rom,
but now i am facing mic mute problem, that happens
only on incoming calls.
When i answer, i can hear the person, but the person
can't hear me all the time, like if the mic get muted
5-10 seconds after i answered the call.
If i call back the person, there is no problem.
Thanks anyway
Related
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
gaga111 said:
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
Click to expand...
Click to collapse
No problems for me. Ive just got 4.1.2
Anbody else :S
Just to be clear.. i dont mean switching it on and off
Sent from my Galaxy Nexus using xda app-developers app
edit:
seems like light flow is causing the force close...
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
gaga111 said:
Anbody else :S
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
Click to expand...
Click to collapse
Same problem here and that fixes it for me too! Happens on my wife's Nexus 7 too, but she has NoLED there so this may be a bug that has to do with anything enabled under accessibility settings (or at least not ONLY Light Flow).
Edit: I wonder if this is related:
http://forum.swype.com/showthread.p...Swype-Issue-Thread&p=35850&posted=1#post35850
"Note: We have found that this issue is related to running apps that have settings in the accessibility menu in Android settings. In the meantime, you should be able to use Swype by disabling any apps that are in Android Settings > Accessibility."
Sounds like 4.1.2 has some kind of Accessibility bug,
I just updated my gnex and since then my phone started freezing.
The touch control doesnt work for a while then it works for few seconds and freezes again.
If i get a call the phone doesnt ring (like silent mode) and i cant answer it because the touch control is down.
Any help
jasaad said:
I just updated my gnex and since then my phone started freezing.
The touch control doesnt work for a while then it works for few seconds and freezes again.
If i get a call the phone doesnt ring (like silent mode) and i cant answer it because the touch control is down.
Any help
Click to expand...
Click to collapse
Any other update you have done after run 4.3? Which method you update : official ota came from your phone or download from shared ota link?
Sent from my Galaxy Nexus
official OTA, it came by itself i didnt force it.
IT started freezing directly after updating. I updated my apps whatsapp and appex launcher and few other that i have also on my nexus 4.
But still having freezing problem. And sometimes i have to remove the battery.
The phone is stock locked
jasaad said:
official OTA, it came by itself i didnt force it.
IT started freezing directly after updating. I updated my apps whatsapp and appex launcher and few other that i have also on my nexus 4.
But still having freezing problem. And sometimes i have to remove the battery.
The phone is stock locked
Click to expand...
Click to collapse
factory reset my friend !, theres probably too much left over data on u phone which is causing the slow down and freezes. i updated my gnex from the factory rom files and cleared all my data (including sdcard ) now my device is flying 4.3 is 4.2.2 on steroids
hahah okay i will try it thx u.
Hello!
I recently updated to 4.3 and rooted the device using Odin, however the default camera app is no longer responding - it gives me the following error message: "Unfortunately, Camera has stopped working".
Things I've done to try and fix it:
1- cleaned cache and data but that didn't solve the problem.
2- also reset the device to factory through settings but it didn't work either
3- re-install camera.apk (wouldn't install using Titanium)
4- install new stock camera from 4.3 rom (installed but got the same message)
5- manually replaced the files for the camera (system/app/SamsungCamera.apk and SamsungCamera.odex) AND Gallery (SecGallery2013.apk and SecGallery2013.apk) with new ones
Issue still persists...
Any ideas? Pls help.
Thanks!
if you're using xpose mod and wanam update to the latest wanam.
ragomes14 said:
Hello!
I recently updated to 4.3 and rooted the device using Odin, however the default camera app is no longer responding - it gives me the following error message: "Unfortunately, Camera has stopped working".
Things I've done to try and fix it:
1- cleaned cache and data but that didn't solve the problem.
2- also reset the device to factory through settings but it didn't work either
3- re-install camera.apk (wouldn't install using Titanium)
4- install new stock camera from 4.3 rom (installed but got the same message)
5- manually replaced the files for the camera (system/app/SamsungCamera.apk and SamsungCamera.odex) AND Gallery (SecGallery2013.apk and SecGallery2013.apk) with new ones
Issue still persists...
Any ideas? Pls help.
Thanks!
Click to expand...
Click to collapse
ascrackoo1 said:
if you're using xpose mod and wanam update to the latest wanam.
Click to expand...
Click to collapse
Thanks but it didn't work.
I got it solved today thou in an unexpected way by actually using the Back up feature within ROM Manager - the phone went into back up mode (like recovery mode where you see the little android robot and command lines), waited until the back up process was finished then rebooted without choosing the option to "fix possible root loss" warning. After that camera was finally back again.
Then I recalled that the last time I've done this back up through Rom Manager there was some sort of problem during the process which interrupted it so I realize now that somehow it affected the camera (have no idea how they relate thou) - but the fact is that as soon as it successfully finished the back up the issue was automatically fixed. Weird, stupid and very rare, I know... At least is fixed!
ragomes14 said:
Thanks but it didn't work.
I got it solved today thou in an unexpected way by actually using the Back up feature within ROM Manager - the phone went into back up mode (like recovery mode where you see the little android robot and command lines), waited until the back up process was finished then rebooted without choosing the option to "fix possible root loss" warning. After that camera was finally back again.
Then I recalled that the last time I've done this back up through Rom Manager there was some sort of problem during the process which interrupted it so I realize now that somehow it affected the camera (have no idea how they relate thou) - but the fact is that as soon as it successfully finished the back up the issue was automatically fixed. Weird, stupid and very rare, I know... At least is fixed!
Click to expand...
Click to collapse
Not to thread jack, but do you have the apk for the stock camera app from 4.3? Thanks in advance
I've had exactly this same problem. Do I have to run a backup to fix it?
I wanted to ask you if some1 got this problem when you are in an app and press the home softkey and get this message : unfortunately home has stopped.
Is there any fix for it or not ? I have G3 D855 int. version. Running the latest V20H software version with the new softkeys.
Not rooted.
malicovjek said:
I wanted to ask you if some1 got this problem when you are in an app and press the home softkey and get this message : unfortunately home has stopped.
Is there any fix for it or not ? I have G3 D855 int. version. Running the latest V20H software version with the new softkeys.
Not rooted.
Click to expand...
Click to collapse
Yeah, happens about once a day for me, usually when I quit whatsapp.
Never happened to me. I dont use whatsapp. Using D855 TWN 20H stock non-rooted
This happens to me as well,(stock lollipop no root) something to do with whatsapp . Go into settings > Manage apps > All Apps > then scroll down to homescreen. Tap on it and then tap on "clear data". This works for a while but using whatsapp brings the problem back.
After pressing several back from whatsapp, home stops...
Stock 20h, no root
Serbia
I have the same, but not especially from whatsapp, more often from gmail. I've been having these on all Lollipop roms.
malicovjek said:
I wanted to ask you if some1 got this problem when you are in an app and press the home softkey and get this message : unfortunately home has stopped.
Is there any fix for it or not ? I have G3 D855 int. version. Running the latest V20H software version with the new softkeys.
Not rooted.
Click to expand...
Click to collapse
Yes, I get the "Unfortunately, Home has stopped" error intermittently since updating to lollipop, v20c is still the latest for my D855.
Pressing home or back does it, but difficult to reproduce consistently.
In searching I have not found a solution, doing a full reset doesn't work either.
The only way I have found to stop the error is to use another Launcher as a workaround.
Hello, I am happy owner of 1+3 (coming from Xperia U) and I am very happy with this phone, no bugs at all except for this. Normally it works perfect but after maybe a day of usage without restarting phone, recent apps (or open apps) tab not showing any open apps but its definitely graphic bug only because all apps that I open again are normally loaded from memory. After restarting phone it works, even all opened apps before restart are showed. Oxygen OS 3.2.2. See screenshot before and after restart.
before reboot h ttp://i.imgur.com/KMOruMN.jpg
after reboot h ttp://i.imgur.com/hLkUn8S.png
Sorry for links, this is my first post...
I'm Also having this problem in 3.2.2. Already had it in 3.2.1.
Sent from my ONEPLUS A3003 using Tapatalk
Here are your options
1. Factory reset
2. Root it and remove unwanted apps
3. Flash another ROM. My suggestion is flash this STOCK BASED ROM..Which is perfect.
Also just had this for the first time yesterday on 3.2.2. Recent apps reappeared after reboot.
Same problem for me
I had the same problem since last upgrade to Oxygen 3.2.2 and fixed with only doing a reboot to recovery (you can do it from power off menu if you mark the option advanced reboot in developer options or if you start the phone holding down power+volume down button at the same time) and then reboot to system normally again and voilá the recent apps button worked again for me.
Hope it helps.
Un saludo.
Get in touch with OP support team
Guys, I have talked with OnePlus 3 support. They wanted to schedule a remote support session with me, but that involves flashing a new firmware, and as I do not feel like tinkering with my new phone I had to decline.
Is anyone experiencing this issue wanting to do some flashing to help the community? Just open a ticket with OP3 explaining the problem. They'll get in touch in no time.
Anyone?
Same problem for me on Oxygen 3.2.4. Only reboot helps!
Clear google app data
This is supposedly a google voice activation bug.
To fix it (atleast temporarily) clear the Google App's data from application settings, then the Recents window starts showing the apps
Awesome! That worked for me. (OnePlus X)