Related
I have a problem in my U.
Everytime someone calls me, first the led lights up, then it vibrates about 2-3 times in the middle starts ringing and only after all that the screen turns on so i can answer or reject the call.
After i answer a call sometimes it takes 3-5 sec to hear sound from the other phone, but the caller says he can hear me the whole time.
When receiving SMS, first the led lights up, then after a while it vibrates and after that it rings, but sometimes it doesn't ring.
Another thing, it lags to much to open the contacts, phone and messages app.
My wifes Tipo dual, opens almost instantly the phone app after i touch it.
I'm using The ROM, etc that are stated in my signature.
Please help!! Already tried different kernels, etc. :crying:
It can be something in the mods or it can be the rom itself.
Didi you get these bugs before the mods?
The stock rom sucks, mine did this as well, made the phone unusable.
mirost1 said:
It can be something in the mods or it can be the rom itself.
Didi you get these bugs before the mods?
Click to expand...
Click to collapse
Already had the excessive lag opening the apps with a fresh stock ROM. Honestly i put and did so many things that i don't know now.
But i installed the Sliding XU 3.3 kernel and it's working almost fine now, only has the original lags opening the apps of the stock ROM.
theronkinator said:
The stock rom sucks, mine did this as well, made the phone unusable.
Click to expand...
Click to collapse
So wich ROM do you use
Im on stock Droid DNA ROM. Have the latest update. Every time I try to open the camera it says "Unable to start the camera." I have already hard reset the phone 2 times and restarted. I also cleared the camera data and cache. I don't know what to do now..
Try downloading a camera app from the market and see how it works. If that app also can't get it to start then it may be a hardware issue. If it can then you know there is something wrong with the stock camera app.
Sent from my HTC6435LVW using xda app-developers app
Jaggar345 said:
Try downloading a camera app from the market and see how it works. If that app also can't get it to start then it may be a hardware issue. If it can then you know there is something wrong with the stock camera app.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
tried. It wont use the camera
Sounds like a hardware issue then.
Sent from my HTC6435LVW using xda app-developers app
This is the same error I get on the CM10.1 ROM since the camera isn't working yet... as everyone else has mentioned it's most likely a hardware issue especially if you've tried wiping the entire phone and still have the problem.
Had this happen today. Did you ever get it straightened out?
If I try a photo the flash comes on and will not go off unless I reboot. If I try a video the screen goes black and freezes. I've rebooted, "hard" rebooted by holding power button down, turned off fastboot, cleared data and cache.
I tried CameraMX from the market and it doesn't work.
I did not buy my phone from Verizon. What are my options?
It doesn't matter where you bought it, HTC will warranty it as long as you talk to them like a human and explain the situation while being respectful.
Sent from my HTC6435LVW using Tapatalk 2
Thanks bud. I'll give it a shot. I really like HTC phones I hope this (along with whatever may happen with the warranty) doesn't leave a bad taste in my mouth.
So, I've been resetting, force closing and clearing data the past 2 days throughout the day for the camera. Usually, after I've did a reset the camera will open, but when I try to take a picture the flash comes on and stays on the the app freezes. The led flash will not go off until I do a reset. A force close won't even shut it off.
Today after a reset, I opened the camera and instead of trying to take a pic I cycled through the flash settings. As soon as I did the interface switched to portrait, (like the phone was held) and it took pics and video like normal!!!!!!!!
It works now. What a crazy problem.
Completely stock DNA with latest ota update. Phone has not been dropped or anything.
Wow, that doesn't make any logical sense. How strange... Glad you got it fixed though!
Sent from my ViperDNA using Tapatalk 2
I see similar camera weirdness a lot when I'm at Best Buy in the best buy mobile section and I've intervened on 10 or 15 exchanges by tinkering with camera and gallery like clearing app data.
You've taught me a new trick in case I ever get to show off for the hot best buy mobile girls.
Sent from my HTC6435LVW using Tapatalk 2
If you have a flash light app and do not turn the flash off this will cause the camer to not start
Recently had the problem (camera won't start, or can't connect to camera). Got the solution here:
http://forums.androidcentral.com/verizon-droid-dna/244680-camera-unable-start.html
Just hold the power button for ~20 seconds til it reboots, and camera works just fine. No loss of data or anything. It's supposed to be the equivalent of battery pull.
Mine too!
bluesamg said:
Im on stock Droid DNA ROM. Have the latest update. Every time I try to open the camera it says "Unable to start the camera." I have already hard reset the phone 2 times and restarted. I also cleared the camera data and cache. I don't know what to do now..
Click to expand...
Click to collapse
Hi there ,
I have my DNA in the same situation ("Unable to start the camera").it crashes.... I have tried everything ! NOTHING works..tried to root ,change rom...maybe firmware! nope ,No solution for that i guess.
Please tell me what did you do to get it working ? did you send it back to verizon ?what did they do ? can they fix it ?or they have changed the whole phone ? please be in touch .
One more question is : Does your phone sometimes crashes ? in my case i have the same problem with the camera ..... and i have my phones system gives me :"proccess system not responding " . could that be bacuse of the camera problem ? Do you have the same ?(your phone get stuck sometime ..and goes OFF\RESTART ?)
I have the same case !! but in my country i have NO verizon here ..so actually i can't fix my phone !
What should i do ?
Thanks guys for help .
shadyabs said:
Hi there ,
I have my DNA in the same situation ("Unable to start the camera").it crashes.... I have tried everything ! NOTHING works..tried to root ,change rom...maybe firmware! nope ,No solution for that i guess.
Please tell me what did you do to get it working ? did you send it back to verizon ?what did they do ? can they fix it ?or they have changed the whole phone ? please be in touch .
One more question is : Does your phone sometimes crashes ? in my case i have the same problem with the camera ..... and i have my phones system gives me :"proccess system not responding " . could that be bacuse of the camera problem ? Do you have the same ?(your phone get stuck sometime ..and goes OFF\RESTART ?)
I have the same case !! but in my country i have NO verizon here ..so actually i can't fix my phone !
What should i do ?
Thanks guys for help .
Click to expand...
Click to collapse
Read the thread please. The answer is in it.
Sorry for the necromancy, I'm having the same issue, and no amount of resets, soft or hard, has resolved anything.
I received this phone about a month ago as a total care replacement for a very sad old Droid X that was needing to be put out to pasture. When I first got it, everything worked fine. The camera worked a couple weeks ago, even, but I went to use it today, tapped the camera icon, it briefly opened then instantly closed with a message "Unable to start the camera".
I tried a few more times, force quit, cleared cache, tried again, still nothing. Force quit, cleared data, tried again. Soft reset, tried again, nothing. Held power button for a reset, still nothing. Powered off and back on again, still nothing. Another soft reset, still nothing. Tried 3 other camera apps, Google Camera closed immediately with a similar error message, Vignette just sat there at Initializing Camera forever, and some garbage front camera only selfie app opened but only showed a black screen for the viewfinder.
I did another soft reset, still nothing.
I did a factory reset, and tried again without downloading any of the apps previously installed. Still nothing.
I've tried several more soft resets and cache clears since then.
It's looking more and more like a hardware problem but previous posters in this thread reported fixing similar issues without doing anything to the hardware. It has never been dropped, it has never been wet. It hasn't even been outside in a light drizzle. It's never been sat on, it's never gotten warmer than 109 reported internal temp.
Other than take it to Verizon and whine at them about how the free phone I just got a month ago is a broken piece of crud for no apparent reason or malfeasance on my part (which is probably why they had it on hand to give away, reconditioned my big toe), is there any potential resolution I'm missing that doesn't involve warranty-voiding stuff.
THIS IS PROBABLY THE ANSWER YOU ARE LOOKING FOR!
"Today after a reset, I opened the camera and instead of trying to take a pic I cycled through the flash settings. As soon as I did the interface switched to portrait, (like the phone was held) and it took pics and video like normal!!!!!!!!"
I didn't see you mention that you tried this. It fixed my dna and I never had another issue.
natypes said:
THIS IS PROBABLY THE ANSWER YOU ARE LOOKING FOR!
"Today after a reset, I opened the camera and instead of trying to take a pic I cycled through the flash settings. As soon as I did the interface switched to portrait, (like the phone was held) and it took pics and video like normal!!!!!!!!"
I didn't see you mention that you tried this. It fixed my dna and I never had another issue.
Click to expand...
Click to collapse
I can't even get that far, as soon as I tap the camera icon, the camera app flashes open for a moment then instantly closes with an 'unable to start' message. The odd thing is that every so often, with no rhyme or reason, it will randomly start working just fine, then not work at all for weeks on end.
Of course now it's so broken, even LED Flashlight apps don't detect it as even having a camera.
Unsure if this a problem caused by CM 10.1 or android 4.2.2 but using both jellybam and paranoidkangdroid I am unable to put the screen to sleep, the hardware button still works for shutting down just not turning off screen. I also have a hard time getting music to play, requires reboots and shutting down of apollo app, unsure of which of these actually does the trick or if its just luck.
Part of the symtoms include a flashing black screen, what it looks like is a black overlay with part of the status bar still visible. As well as rare random reboots.
Does anyone know if this a problem with the i717 and the most up to date roms or something else.
Help much appreciated thanks.
The only issue I can comment on is Apollo. Mine you have to select the music you want or hit play, wait, hit back when the app freezes and then wait for the pop up saying "Apollo has stopped working". Press Ok and go back into the app and hit play or the song you chose again to get it working. After that the app works amazing! I think it actually is a common problem on 4.2.2 but can't say for sure. The rest, I don't really know what to suggest. Sorry
Best of luck to you
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
bak3donh1gh said:
Unsure if this a problem caused by CM 10.1 or android 4.2.2 but using both jellybam and paranoidkangdroid I am unable to put the screen to sleep, the hardware button still works for shutting down just not turning off screen. I also have a hard time getting music to play, requires reboots and shutting down of apollo app, unsure of which of these actually does the trick or if its just luck.
Part of the symtoms include a flashing black screen, what it looks like is a black overlay with part of the status bar still visible. As well as rare random reboots.
Does anyone know if this a problem with the i717 and the most up to date roms or something else.
Help much appreciated thanks.
Click to expand...
Click to collapse
I'm getting this same issue in JellyBAM, PAkangdroid, and CM10.1 M-release (2013-04-11 latest). Re-flashing the ROM in recovery seems to fix it for a while, but I still haven't been able to narrow down a root cause yet.
Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Go into settings > apps > all apps, clear all data for anything relating to contacts then all will be fine, make sure contacts are backed up tho of course
Sent from my D6503 using Tapatalk
I have tried and have not seen the message. Will keep you updated if it has conpletely gone
Sent from my D6503 using XDA Free mobile app
It should do it did for me glad I could help
Sent from my D6503 using Tapatalk
Update: It happened again when I reboot my phone today. Is it possible a firmware bug?
I should wait for the next release, hope Sony will fix this issue.
Regards,
I'm on romaur which is 402 and haven't seen this error since I wiped contacts data so not sure, you still on stock or?
Sent from my D6503 using Tapatalk
Same issue!
tuanph.aus said:
Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Click to expand...
Click to collapse
I also have the same issue as the OP. It particularly happened after I upgraded to .402 using PC companion.The message will appear always after restarting. My devices has not been rooted. Tried to clear data and cache for contact apps, but after restarting, the message appeared again. I am still lazy to do a re-install because aside from the message appearing only after a restart, there are no other major effect to my Z2's performance. but clearing it will be nice though.
I have the same thing when i touch the phone immediatly when it just restarted, but when i restart and leave it untill screen goes off i don't get the message.
Sent from my Xperia Z2 with the use of Tapatalk
phscyiipfer said:
I also have the same issue as the OP. It particularly happened after I upgraded to .402 using PC companion.The message will appear always after restarting. My devices has not been rooted. Tried to clear data and cache for contact apps, but after restarting, the message appeared again. I am still lazy to do a re-install because aside from the message appearing only after a restart, there are no other major effect to my Z2's performance. but clearing it will be nice though.
Click to expand...
Click to collapse
Mafiatounes said:
I have the same thing when i touch the phone immediatly when it just restarted, but when i restart and leave it untill screen goes off i don't get the message.
Sent from my Xperia Z2 with the use of Tapatalk
Click to expand...
Click to collapse
Hi guys,
Thank you for your info.
I tried to disable contact sync of Viber and I think the message has temporarily gone. Sometimes it still pop up but not as often as before I disabled the contact sync of Viber.
Apparently, this problem is caused by contact synchronisation between Viber, Facebook, Messenger, Whatsapp, etc. Other users, such as Samsung phone users, reported that they have the same issue but when they turned off contact sync of the above-mentioned apps, the error message somehow has gone.
To be honest, I have just recently switched to android from iPhone, and I have been usings iOS for years and never seen any kind of issue/error like this on iOS. However, Sony Z2 is one of the greatest phone I ever owned and I am so happy with it, specially its crazy battery life.
Hope you guys will share your solution here if someone can fix it permanently.
Cheers,
tuanph.aus said:
Hi guys,
This is my first post.
I just got a Sony Z2, and yesterday I updated it to latest firmware 17.1.1.A.0.402 using flashtool. After that, everytime when I switch off my phone and turn it on, the message of "...android.process.acore has stopped" appeared.
I tried to flashed the phone again using PC Companion to re-update the same firmware. I though the error message has gone but than it is still there.
I have tried several ways as mentioned in this forum but the problem seem to be there. I don't see any problem/error caused by this error message yet.
Any idea/solution to completely remove the message?
Click to expand...
Click to collapse
Running any Xposed Mods ?
defsix said:
Running any Xposed Mods ?
Click to expand...
Click to collapse
Nope, running original stock firmware. No jailbreak/root.
Cheers,
Update 13.06.2014: Guys, I have tried and flashed my Z2 with UK .402 and so far so good, I dont see that error message pop-up again after reboot.
Regards,
possible fix
i had this problem, amongst others stopping my phone. i pulled the sim card out, then rebooted the phone. the phone then showed it was updating all apps i let it boot up and it seemed to work. pulled battery and put sim card back in. and all ok so far. i have sent my phone 3 times away to vodafone for this repair, with android.clock stopping, android.phone stopped working and the phone actually crashing on the samsung screen and not even booting up. each time all they do is a factory reset. like duhhhh, i have never thought of that (sarcasm). i am hoping that doing this, will give my phone some sort of permanency in it's repair. i have not rooted the phone, it is stock.
Vodofone refused to replace the handset even though it had been in so many times for repair. word of advice. steer clear of vodafone. i am cancelling all my contracts with them.
sorry that went off topic, but i want a phone that works and vodafone will not help you in that matter.
tbish said:
i had this problem, amongst others stopping my phone. i pulled the sim card out, then rebooted the phone. the phone then showed it was updating all apps i let it boot up and it seemed to work. pulled battery and put sim card back in. and all ok so far. i have sent my phone 3 times away to vodafone for this repair, with android.clock stopping, android.phone stopped working and the phone actually crashing on the samsung screen and not even booting up. each time all they do is a factory reset. like duhhhh, i have never thought of that (sarcasm). i am hoping that doing this, will give my phone some sort of permanency in it's repair. i have not rooted the phone, it is stock.
Vodofone refused to replace the handset even though it had been in so many times for repair. word of advice. steer clear of vodafone. i am cancelling all my contracts with them.
sorry that went off topic, but i want a phone that works and vodafone will not help you in that matter.
Click to expand...
Click to collapse
Xperia's have unremovable batteries, maybe you should steer clear of Samsungs
Is that a good thing or a bad thing though? Cos sometimes taking a battery out is what could be needed to fix a problem.
But point taken. Perhaps a change of manufacturer would help
Sent from my GT-I9300 using XDA Free mobile app
tbish said:
Is that a good thing or a bad thing though? Cos sometimes taking a battery out is what could be needed to fix a problem.
But point taken. Perhaps a change of manufacturer would help
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
I know people who advocated pulling the battery from devices as the only answer but I've yet to come across a situation on any device which couldn't be handled with >adb reboot or a three finger reset.
There's actually a method on Xperia devices, to disconnect the battery and plug it back. It's called "Hard Reset". Yeah you don't take the battery out in reality, but this method does it in Matrix dimension. So, the consequences are the same.
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.