Related
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
That is happening on every 4.4 I think. It was on CM10.1, CM10.2 too.
Lag on calling screen
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
krazzykuldeep said:
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
Click to expand...
Click to collapse
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Klaas68 said:
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Click to expand...
Click to collapse
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
krazzykuldeep said:
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
Click to expand...
Click to collapse
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Klaas68 said:
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Click to expand...
Click to collapse
I installed the AOSP rom and it seems stable and maybe the call delay issue is better, still have to test it more.
I do however miss some nice functions which were present of the Carbon ROM:
- separate lockscreen background
- disabling the annoying Google Now bar on the homepages
- some fine tuning in icon colors
- kliing an app by long-press the back button
- defining hotkeys e.g. for the camera
and some more..
Is there maybe some package to install to add functions like this to the AOSP ?
Klaas68 said:
...
Click to expand...
Click to collapse
Use Xposed module for all what you need. Gravity Box or others module..
R_a_z_v_a_n said:
Use Xposed module for all what you need. Gravity Box or others module..
Click to expand...
Click to collapse
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Klaas68 said:
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Click to expand...
Click to collapse
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
shut_down said:
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
Click to expand...
Click to collapse
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Klaas68 said:
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Click to expand...
Click to collapse
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
shut_down said:
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
Click to expand...
Click to collapse
OK I did those 3 steps before flashing the new ROM. Sometimes I even had to do it twoce because the ROM did not install and raised a error 7 or so...
I think it was more a problem with the APN configuration and never before needed to do this manually...
Updating from 4.4.2 to 4.4.4
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
harsh3793 said:
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
Click to expand...
Click to collapse
If you dirty flash (just wipe cache/dalvik and install) the new version, you want loose your apps etc.
But I would recommend to do a clean flash (factory reset and format system), but before backup your apps with Titanium. After installing the new version you can restore your apps and data.
But anyway, before wiping/installing anything do a nandroid backup. So if anything went wrong, you can go back in just a minute.
solution ?
Klaas68 said:
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
Has anyone solved this problem ? I have this problem with every rom that i've tried. I'm losing patience with android phone.
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Wysłane z Light-fonika 1-2 ....
...
MikiGry said:
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Click to expand...
Click to collapse
I am stressed when receiving an incoming call and caller don't hear me. I wait from mobile phone calling without problems.
I just wanted to know if there is a ROM without this problem or if anyone have solution.:cyclops:
@ian2189
This is our phones problem. 99% of the users (me too) were expiring this since gingerbread 2.3.6 . So i think there isnt a solution. I now why it is happening but it is unfixnable.
Wysłane z mojego nexusowego tablecika.....
Yeah... I even bought another phone because of this...
I have been having a persisting force close issue that I initially thought was linked to Greenify. "Unfortunately, Context Service has stopped" after every call I made or received, and upon booting the phone. Trial and error have caused me to find the only thing that allows me to run Xposed without any issue is having 7 or less modules enabled. I can switch between modules. For instance, I had Xposed Torch enabled and things were fine with 7 modules. I installed Xtoast, rebooted, and instant error/FC. Repeats no matter how many times I reboot. I uninstall Xposed Torch, which was just working perfectly fine, and leave XToast installed. Reboot and no error. Rebooted over and over to ensure, no error. Switched a few modules around to ensure, and it seems to not matter what modules I have installed. I have no issues whatsoever running Xposed as long as I only have seven modules installed, but if I go to install an 8th, no matter what it is, I immediately get Context Service force closes. I have not found anything on here about a definitive amount of modules you can install, so I can only hope someone has a clue what could be going on. Normally I'd look to the Logcat, but it doesn't seem to be a specific module causing this. I'd really appreciate any help any of you might have. Xposed has a lot more to offer for me than you can cram in seven modules.
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
GermainZ said:
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
Click to expand...
Click to collapse
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
wrongway213 said:
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
Click to expand...
Click to collapse
Enable 7+ modules so that the issue will be reproduced on next boot.
Reboot and start the logcat while the device is booting.
Wait till you see the FC and stop the logcat.
Upload the logcat.
Thanks for your reply. I just figured out the problem, thankfully.. I was preparing to do what you said, and I for some reason thought to reinstall Busybox before installing an eighth module and rebooting. My Busybox install must have been faulty. After reinstalling it said I had just reinstalled the same version as previously installed, but now I am back to nine modules and no problems.
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
wrongway213 said:
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
Click to expand...
Click to collapse
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
GermainZ said:
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
Click to expand...
Click to collapse
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
F/C All devices
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
wrongway213 said:
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
Click to expand...
Click to collapse
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
jon3640 said:
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
Click to expand...
Click to collapse
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
GermainZ said:
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
Click to expand...
Click to collapse
problem came back again for no reason, only 6 mods enabled and all have been stable for days... restart phone because i was getting a crazy mms wakelock in bbs. here's the logcat with the "unfortunately, context service has stopped" both from just automatically happening and i triggered it by having my girlfriend call me. i then disabled xposed, restarted and no problems, so i took a logcat of that to show how my phone runs normally in case you need it. let me know if you do and i will upload that as well.. if you can find anything in here i will greatly appreciate it. i can't even use xposed at this point, i'm worried i'm either damaging my phone or possibly missing calls/texts/notifications. thanks for your time in advance.
It's an ANR (Application Not Responding) error, so I'm guessing your phone kinda hangs for a bit before showing you the dialog?
It doesn't seem to be related to Xposed at all, though. It's Samsung's "Context service" (com.samsung.android.providers.context), so I'd personally try checking for a system update before anything else. You're likely to get more help in the S5 section (since the problem isn't related to Xposed), through it looks like no one else has this problem.
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled? That's why I assumed it was xpoaed related to begin with. Do I need to Odin back to stock? I don't want to damage my phone but I don't know anything about that error or if it could he damaging.. Sorry for the text wall. Thanks for being so helpful.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled?
Click to expand...
Click to collapse
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
wrongway213 said:
Do I need to Odin back to stock?
Click to expand...
Click to collapse
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
wrongway213 said:
I don't want to damage my phone but I don't know anything about that error or if it could he damaging..
Click to expand...
Click to collapse
It's mostly just annoying, there should be no permanent damage of any kind.
GermainZ said:
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
It's mostly just annoying, there should be no permanent damage of any kind.
Click to expand...
Click to collapse
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
wrongway213 said:
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
Click to expand...
Click to collapse
I didn't see anything related to S Health, but it might've related to the secure storage (though I'm not sure if that's a stock Samsung thing or if it's activated by the user).
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
Hello, I hope I can post this here.. i tried, i searched... can't find any solution to my issue.
Model : SM-T810 , with Samsung 128GB UHS microSD. OS : stock Nougat from Samsung.
Here is the problem :
On the play store, if there are pending updates, they only install one at a time, and then it won't do more. Like if there is 5 pending updates, it will maybe do one, and then the other 4 stay pending. It might only do the download portion of the first one and not go to the install phase. If there's no pending updates, and i try to install an app, only the downloading portion of the process shows up, it stops after that, it doesn't go to installing. I have to close the store and go back in for it to install, but if there's a queue of downloads (updates or asked to install multiple apps), I have to close the store for the same amount of apps in the queue for them to install one by one. Now I noticed that every once and a while, 2 or 3 will have updated overnight but that's it!
I closed the process, I cleared the cache, I cleared the data, I cleared the download manager's data and cache, i rebooted, i forced a wrong date and time then set it to auto-date and time to retry, etc.... I uninstalled the Play Store updates, nothing worked!!!
The next step was to do a factory reset. I did not want to lose some progress on some games, AND I have an app to read PDF files and did not want to lose read/unread status of my files...
So I used Odin to flash TWRP, did a backup, rooted, used Titanium Backup to backup my apps.
Then I did factory reset. Store behaved normally again! Installed a few apps, waited a few hours, still good. Did a restore of my apps from titanium backup, everything seemed fine, then a few hours later, store still was not updating or installing the apps right...
Did another factory reset, store worked fine, only restored a couple of backed up apps (the critical ones that i wanted to keep the saves from), everything worked fine. Over the course of 24 hrs, i re-installed a bunch of my regular apps via the play store. Play store worked fine. I did to another Nandroid backup with TWRP just in case.
Then all of a sudden, it started to lag a bit between clicking install, to downloading, to installing. And then a few hours later, issue completely came back, store won't install without me closing it between the download finish and install.
Now one of the last steps I did before it started acting up again was moving ONE app to the SD card (not using any root features). I'm not sure if that caused the issue to come back.
I did notice that Android left a bunch of files on my SD card, some Android folder, with a bunch of subfolders.
I'm wondering if the SD card could be the culprit... I will do one last restore from my last working Nandroid backup and not move anything to the SD card.
If it comes up again, i think i will move the data that i have on my SD card that I dont want to loose (my PDF, pictures, etc.) on to my NAS, and do a factory reset without the SD card installed. Maybe even re-flash with Samsung Kies... and forget about my Titanium Backup saves...
It's my last resort so I was hoping anyone would have any idea on what else to try before doing that?
One last point : yes the stores kinda slows down at some point where the download process takes a few seconds to kick in, and then a few seconds to installing, up to the point where it never does. BUT the rest of my tablet still is really fast, no slow downs anywhere else... All apps launch fast
Thanks!
Auto updates are bad. They just kill the performance of your s2.. better do such things manually.
Niii4 said:
Auto updates are bad. They just kill the performance of your s2.. better do such things manually.
Click to expand...
Click to collapse
Auto updates of the apps? Or the OS?
Apps i can see... but still... If I turn that off, that solves the issue of the auto-updates. But then if I want to update a bunch, they will only do one by one, i have to close the store and open again after each updated app.
But even with app auto-updates, if i want to install one new app on my S2, it will only download, but not install, i have to close the store and open it again for it to install. Then the next time that I want to install an app, I have to do the same thing again, close and open. It's like the download manager doesn't tell the Play Store app to do the install (or tell whatever app or service to install the APK...)
Niii4 said:
Auto updates are bad. They just kill the performance of your s2.. better do such things manually.
Click to expand...
Click to collapse
What a bunch of nonsense. Please stop spreading misinformation.
@stefer09 A logcat reader may help you determine the cause of the issue.
Niii4 said:
Auto updates are bad. They just kill the performance of your s2.. better do such things manually.
Click to expand...
Click to collapse
fonetyk said:
What a bunch of nonsense. Please stop spreading misinformation.
@stefer09 A logcat reader may help you determine the cause of the issue.
Click to expand...
Click to collapse
Thanks, that's new for me, I'll read into it!
stefer09 said:
Thanks, that's new for me, I'll read into it!
Click to expand...
Click to collapse
I am having the same issue on my sm-t810 as well hope you find a solution and post it.
Tabpro8.4 said:
I am having the same issue on my sm-t810 as well hope you find a solution and post it.
Click to expand...
Click to collapse
After more research i've seen other people on other devices with same issue... no answer or solution in sight
if i find something ill come back here for sure
I had an OTA update last night to NRD90M.T810XXU2DQCL and the play store is working better now but it is still slow to update.
Tabpro8.4 said:
I had an OTA update last night to NRD90M.T810XXU2DQCL and the play store is working better now but it is still slow to update.
Click to expand...
Click to collapse
Thanks for the info.
I would check for OTA update but since i rooted mine, it won't do them...
I'd have to flash the stock rom from samsung again and loose my saved data... which right now i might be OK living without...
Anyone knows if I loose TWRP if i flash a stock rom with odin ? If so... am i better using Kies?
Fair, let's recap: you do not use stock rom. You have root, twrp, flashed this and that and a morbid desire to have always the very lastest version of whatever the app. And now the Play store doesn't work properly anymore.. d
Do you see the pattern?
But, hey, maybe you need even more *lates updates* to fix your issue.
Updates = bad performance and new issues in general. Period.
Niii4 said:
Fair, let's recap: you do not use stock rom. You have root, twrp, flashed this and that and a morbid desire to have always the very lastest version of whatever the app. And now the Play store doesn't work properly anymore.. d
Do you see the pattern?
But, hey, maybe you need even more *lates updates* to fix your issue.
Updates = bad performance and new issues in general. Period.
Click to expand...
Click to collapse
Wooooh, DON'T jump to conclusions here.
I was running the STOCK out of the box Android for the S2, no root, no TWRP. The issue started after one year of usage, and not only included updating apps but installing FRESH NEW ONES TOO.
The "flash this and that" came AFTER i ran into issues.
I also have a Note 5 supplied from work and for that reason I'm still runing stock, not rooted, and never will root it. I have over 100 apps on there, 5 email accounts (2 professionnal, 3 personnal), multiple google calendars, multiple outlook calendars, auto-update is on, it's been over a year and a half, if not more, and never ran into this kind of issue, ever! It's synced with my CPAP, my smart watch, and my headphones. And it's still goes the same speed and gives me the same performance as when i took it out of the box.
My tab S2 is my second Android tablet, before I had a Tab 3 that never gave me issues like that either, and always had auto-updates on.
Sometimes you need updates. Some online services might not work right or at all if you don't have the app that matches the features, like evernote, facebook, onedrive, dropbox, etc...
Or you get new hardware that requires an update.
Yes sometimes they include bugs ... which are fixed in a later version.
Niii4 said:
Fair, let's recap: you do not use stock rom. You have root, twrp, flashed this and that and a morbid desire to have always the very lastest version of whatever the app. And now the Play store doesn't work properly anymore.. d
Do you see the pattern?
But, hey, maybe you need even more *lates updates* to fix your issue.
Updates = bad performance and new issues in general. Period.
Click to expand...
Click to collapse
In my case I do have stock rom and have had issues with play store since update to Nought. It does seem better since last night's OTA update.
Tabpro8.4 said:
In my case I do have stock rom and have had issues with play store since update to Nought. It does seem better since last night's OTA update.
Click to expand...
Click to collapse
I saw multiple posts of people having different phones running stock having this exact issue for a while with no solution in view. I think it has to do with Nougat too... But my Note 5 is on Nougat and no issue... it might be brought on with specific services or apps running while on Nougat.
Tabpro8.4 said:
In my case I do have stock rom and have had issues with play store since update to Nought. It does seem better since last night's OTA update.
Click to expand...
Click to collapse
Thanks for letting me know about the OTA update. Since i was rooted, i can't get OTA updates, would have needed to wait for the 7.1 Rom to flash...
I ended up taking screenshots of the stuff i didnt want to loose (read/unread status of my pdf files, nevermind the save games) and then i used Samsung Smart Switch to reflash the whole thing back to strictly stock, lastest firmware. So far so good, crossing fingers
I*was*running the STOCK out of the box Android for the S2, no root, no TWRP. The issue started after one year of usage,
Click to expand...
Click to collapse
Fair. So in this *year of usage* you never ever updated the OS?
And auto-update was of course *off*, right?
If that's the case, then clearly there must be some other issue with your s2.
Otherwise, you have merely confirmed what I have told in the very beginning: updates = bad performance and new issues in general. Period.
By the by, apps like evernote and facebook track and spy on you.
About your Note 5, maybe there weren't so many updates..
Niii4 said:
Fair. So in this *year of usage* you never ever updated the OS?
And auto-update was of course *off*, right?
If that's the case, then clearly there must be some other issue with your s2.
Otherwise, you have merely confirmed what I have told in the very beginning: updates = bad performance and new issues in general. Period.
By the by, apps like evernote and facebook track and spy on you.
About your Note 5, maybe there weren't so many updates..
Click to expand...
Click to collapse
...
Yes in that year of usage I upgraded the OS from 5 to 6 to 7. Yes auto-update was on, for Android and for my apps. By stock rom i meant nothing flashed "this and that" like you said.
If you would read my other comments, you'd also realize that another member helped me more by letting me know there was an OTA update that helped him. I reflashed my S2 with Samsung Smart Switch and haven't had any issue with the Play Store since... that proves that updates do fix issues.
There's no OS versions, app versions, firmware versions on any devices that don't have any issues whatsoever. Updates might bring bugs but they also fix the ones from previous versions. If you think that anything stock out of the box never have any issues whatsoever, you're wrong.
Apps like evernote and facebook spy and track you? Really? And you're on a forum for Android based product and don't think that Google tracks what you do? If you dont sign in with your google account and only browse the web with your tablet, that's your business, but you can't go on forums and admonish people for doing otherwise.
Besides, this is a forum where a good part of the posts are about custom roms, flashing different boot/recovery loaders, different kernels, unlocking phones... and you're judging me because i do app updates, and flash "this and that" ?
Come on...
No judging here. Just pointed out the probem at hand.
You did update the OS at least twice.. see?
OEM updates = bad in general.
Sure, new updates fix what *previous updates* screwed up to begin with; sometimes.
I totally agree that there is no OS version that is 100% issue free, but -- why trying to fix something that seems to work?
You see, that is my whole point.
I told you about evernote and facebook because you mentioned to have them on your Note 5 which happens to be your professional work phone?!
Just be aware that Evernote steals content just like the FB messenger. And I mean literally. Your creative ideas become their property. You did agree to their terms! FB also records the mic(s) 24/7.
Certainly Google tracks and spies as well. Then again, you can deactivate or block (firewall) those services/apps.
Just remember, things that are *free* come with a price.
Niii4, I tried to subtely pass the message that I did not want any of your help when I said that SOMEONE ELSE helped me with their input and update.
I didn't say that I was using evernote and facebook on my Note 5 from work. Jumping to conclusions again.
You want to know what are the biggest secrets in my Evernote notes ??? RECIPES!!!!!
Oh no... they can read the oh so secret lemon crinkle cookies recipe that is available with a quick online search! Here's the link btw : http://www.laurenslatest.com/lemon-crinkle-cookies/
I came here after trying a lot of troubleshooting steps, when everything that I've tried failed. And someone else helped me.
All you brought to the table was misinformation about updates in general and spread paranoia on who is spying on who.
fonetyk asked you to stop that, and I asked you to stop that. So far my issue has been resolved and i'm thankful to the user Tabpro8.4 for his comment.
Please, please leave my thread.
First and foremost, this is a forum and thus other users that may encounter similar or the exact same problem(s) will seek to comprehend the whole issue at hand and not just one side of a problem.
Oh yeah, an OTA update seemed to have fixed it. Seemed.. for now.
Second, this is not exclusively about *helping you*. Apparently you are quite knowledge resistant, especially when facts are being stated that don't conform your general view.
True, you only have hundreds of apps on your work phone. But definitely not FB messenger or whatnot. Whatever. What's right is right, and what's fair is fair.
I suppose, you are probably right, the work you do must be of no interest for anybody in this world; at all. Same for your private life. Now, be a neat little sheep and go on chewing the green.. (while we are watching you).
Oh, and you stalking all my comments, telling people to ignore me is hilarious. Keep up the great whine. ?
Niii4 said:
First and foremost, this is a forum and thus other users that may encounter similiar or the exact same problem(s) will seek to comprehend the whole issue at hand and not just one side of a problem.
Oh yeah, an OTA update seemed to have fixed it. Seemed.. for now.
Second, this is not exclusively about *helping you*. Apparently you are quite knowledge resistant, especially when facts are being stated that don't conform your general view.
True, you only have hundreds of apps on your work phone. But definitely not FB messenger or whatnot. Whatever. What's right is right, and what's fair is fair.
I suppose, you are probably right, the work you do must be of no interest for anybody in this world; at all. Same for your private life. Now, be a neat little sheep and go on chewing the green.. (while we are watching you).
Oh, and you stalking all my comments, telling people to ignore me is hilarious. Keep up the great whine.
Click to expand...
Click to collapse
Lol... knowledge resistant. Thats cute.
:angel:
Stalking your comments... ah! Maybe you got that dead pixel from trying to plug your bluray player on your tablet. Seriously clueless or just trolling...
My issue is resolved so im unsubbing from this thread.
Bye bye :good:
Hello,
I'd like to have some help with diagnosing what hiccup my device recently has.
For a few days I'm on EUA4 Android 11, BL unlocked, Magisk patched, fresh install. Before that I was running some months old Android 10 also magisk rooted, some modules etc. and had uptimes of several weeks without reboot.
Now I get random reboots a few times per day. System shows samsung logo for a while, brings up warning messges "your devide... not official... security" etc., shows SIM pin, Device pin and crashes right again before launcher is fully up. Sometimes multiple times until system stays on. (Can interrupt this ofc with Power+bix+VolDown and boot Power+bix+VolUp into magisk)
Can someone help me figure out why? Some app, magisk module, frozen app idk...
I tried reading through last_kmsg and bugreport files but I'm not that savvy to actually understand why watchdog is killing system and what extra information I should fetch from the device.
I don't know where to look for the reason why this happens so I can fix it or avoid it after the next flash.
Thanks for your help.
you are not alone. its happening to me on S10+ aswell.
Thanks, always nice to know
I went back to Android 10 (DTK9). Device running for 68h without even an app force closing. Same setup otherwise, same apps/ magisk modules/ magisk canary/ disabeled samsung apps etc...
Really don't know why I couldn't get 11 to run acceptable. I'm clearly missing some diagnostic capability like "your device rebooted cause app x did something funny that produced a 0 somwhere else and that caused something in the kernel to **** it's pants..."
Propably android somehow could point me there, but obviously I'm too much of a noob to understand it.
Thats why I asked for help if someone can teach me to understand what my poor system tries to tell me.
If you can - or at least show me where I can learn about that - I'm still interested, but for the next few months I'll skip firmware updates
emanrov said:
Thanks, always nice to know
I went back to Android 10 (DTK9). Device running for 68h without even an app force closing. Same setup otherwise, same apps/ magisk modules/ magisk canary/ disabeled samsung apps etc...
Really don't know why I couldn't get 11 to run acceptable. I'm clearly missing some diagnostic capability like "your device rebooted cause app x did something funny that produced a 0 somwhere else and that caused something in the kernel to **** it's pants..."
Propably android somehow could point me there, but obviously I'm too much of a noob to understand it.
Thats why I asked for help if someone can teach me to understand what my poor system tries to tell me.
If you can - or at least show me where I can learn about that - I'm still interested, but for the next few months I'll skip firmware updates
Click to expand...
Click to collapse
im am sorry, but i cant help you with your issue. I just wanted to let you know that we all struggle and i am planning on switching back to A10 aswell, since Samsung pay still doesnt work in my country... hope someone can help you tho!