Hi there,
I noticed since few weeks somehow, that after some update I don't have the bottom speaker working anymore. After reading on the net a bit I discovered that it could be SW related.
Now, even after factory reset, nothing changed.
I was just wondering, has anyone else encountered the same issue?
SM-G9110
Thanks!
Related
Got the tab a week ago. The front facing camera was working fine, tried it again today and the color was all screwed up. Is this a hardware or software problem? The back camera still works fine. The picture attached was taken from the front camera.
I would think it is a software issue. Did you install any rom or photo software?
Nope. Havent installed any camera apps or messed with any settings.
If you have root, and you can try flashing a fresh rom.
I have exactly the same issue on my Nexus S. Back camera also works fine. I have stock 4.1.2. Never flashed anything else. Phone version is I9023XXKI1. I know it worked flawlessly for months in skype. Then it changed to this weird color mode for some calls and back without any apparent reason. Now it doesn't change anymore. It just stays this way. I tried to change many settings, nothing helps. I'm also attaching image.
This is the only post I found that seems to be the same as my problem. The hardware is different (well, they are both from Samsung) but result is the same.
Hi all,
Firstly can I say thankyou to all of you at these forums, I've been a lurker for a while, waiting for my Prime to arrive, and I'm very grateful for all your insights!
I have now recieved it and seem to avoided most of the well-documented problems on here, but seem to have managed a new one (at least i couldn't find a similar one through searching).
So I updated the Prime with the new firmware and it all seemed to go well. After a while the notification popped up to do the camera firmware (as I had been expecting from these threads). I set it going, and after a short while it said it was complete. The next time I powered on however, the notification to update the camera firmware was back, so I did it again (thinking it must be additional one). But it keeps doing the same thing - saying it's successful, only to re-appear after a re-start.
My current versions are
Build - 8.8.3.33 (which i know is what it should be)
Camera - 0xFFFFFFFF (which I know is wrong!)
Anyone else had a similar problem? Or any ideas?
I have no idea if it's possible, but I am also wondering whether this is what's causing my auto-rotate not to work. Just to confirm, I have the auto-rotate set on, and the gyroscope doesn't seem to be working for anything else (tried it on riptide demo)
Any ideas would be greatly appreciated!
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
tdrussell said:
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1429067
Mine is completely borked. After installing ICS I got a notification for a camera firmware update. The update failed several times, and now when I launch the camera app it says it won't work without updated firmware...
EDIT: I rebooted and as soon as it started up it bugged me to install the camera update again. I made sure the screen stayed on while it updated this time and things seem to have worked out. Camera is working just fine!
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
My calls are always on speakerphone, doesn't matter if the speakerphone button is on or not, I don't believe this is a hardware problem even though my screen was replaced a few days ago, I mean how could it possibly be. I can't be the only one with this problem, I have searched everywhere, seems like I am. I'm running stock (rooted) so I don't believe it is a software problem either, I have tried rebooting and clearing cache so far.
Details: Stock E2303 MM Rooted. Only thing that could be screwing with audio is Viper4Android, and I uninstalled its drivers already. Also the headphone jack is dead if it matters.
Sorry for creating thread ahead of time, but the problem has been fixed by flashing stock using Flashtool, incase someone has the same problem.
Is anyone else still having s-pen disconnection problems after the latest air command update?
Mine is still playing up. I've reseted the pen multiple times and reinstalled the updates. Short of enabling the keep s-pen always connected option not sure what else to try.
Hi bro
Yes, my pen still disconnects after the update from Galaxy Store. I even wrote a comment about it on SamMobile.
Regards DeHAWK
Mine also disconnects a lot. Is there a fix for this issue?