I don't know if this exists, but I thought it would be a good idea to place all the bugs that people find in one place, in hopes of them getting fixed either by Samsung or by a custom rom. If this is a bad thread idea, or has already been done, mods please feel free to do with this what you will.
Just off the bat, I've noticed only a couple of bugs.
1) After using Google Navigation, my system volume resets to the highest level. I usually have it completely turned off, because the sounds on every click are quite annoying. I just noticed that I always have to turn it back down after using Navigation.
2) I had the timer set, then the alarm went off, but I accidentally hit the home button or the back button before I could stop the timer. The alarm continued going off, no matter how many times I would set and stop a new timer. Could not figure out how to turn the alarm off, and eventually had to reboot to kill it.
That's all I really have for now, but if you have noticed anything else please feel free to add it to this thread.
edit: this is for bugs in the stock rom, obviously modifying your phone opens up a whole 'nother can of worms
People using different ROM will have different bugs. Unless you talk about stock ROM bugs.
Taking a picture in portrait mode and then sharing it (Facebook, messaging, etc) results in a landscape photo orientation that is 90° incorrectly rotated.
My haptic feedback vibration is just gone after flashing JI5 . Wont vibrate with the soft bottons or using key pad. I really dont like not having any vibration.
Sent from my SGH-T959 using XDA App
Anyone out there having as issue where the sound from the keyboard clicks, unlock and lock sounds, and the dial pad phone calls went almost un-hearable??
I have no current mods to my phone just picked it up started typing and noticed i could no longer hear my keyboard clicks and went on to discover that many of system sounds were quieter.
The rings and other notifications work just fine though very odd this is not the first time this has happened to me with other android devices but typically either a battery pull or a quick reset resolves the issue but not this case.
Anyone with similar issues with a quick fix aside from restore??
I have noticed that when the battery get low sounds and vibration setting get shut off.
Please post questions in Q&A section.
Whorok305 said:
I have noticed that when the battery get low sounds and vibration setting get shut off.
Click to expand...
Click to collapse
Yep.. You can edit all that in the Power Saver Options. It also will shut down WiFi. Very Annoying.
well i thought that also but my battery was fully charged.
I noticed when I clicked things the clicking sound was randomly extremely low. I went to the sound settings and just played with em for a min and it went back to normal :/
sadly i tried all that stuff and i am getting extremely frustrated
Funny thing.......my htc keyboard wont let me turn off the vibe feedback.
Sent from my HTC Glacier using XDA App
pdxrealtor said:
Funny thing.......my htc keyboard wont let me turn off the vibe feedback.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Mine turns off just fine but I've seen that issue on other phones, don't know how to fix it though.
Theres a power saving mode your phone gets into when it reaches 15% or lower. This setting quiets your phone, takes off vibrations, and more thing just to save batt. life, u can change this is settings
Sent from my HTC Glacier using XDA App
i have the same problem..it is extremely frustrating..ive rebooted my phone,factory reset it too..but nothing works D=
Its the system volume settings.... download AUDIO MANAGER AND ADJUST SLIDER ON SYSTEM VOLUME ALL THE WAY to right...
Sent from Hawaii using XDA App
Wondering if anyone else is having this issue. My screen will dim randomly while in the middle of use and I have no idea why. I'm not talking about the auto-dim that occurs before the screen turns off. I also have auto brightness turned off. I seem to notice it happen right after pressing a hard key, like back or home. When it happens, it seems to un-dim itself after I long press on the screen or switch applications. It doesn't happen every time I use a hard key and it does happen when not using a hard key at all. It's not application-specific but it seems to occur often while using the Market and NewsRob.
For example, I'll be looking at an app in the market and right after I hit the back button to return to, say, search results, the screen will be noticeably dimmer. Normally long pressing or switching out of the app to something else corrects the issue, but I can't pinpoint exactly what causes it or what fixes it.
I downloaded the AdjBrightness app because it has the option to lock other applications from changing my set brightness level, but the issue persists.
Anyone else experience this? I'm on 2.2.1 (2.3.340) but I noticed it with 2.3.320 as well.
never had that issue, I'm on .340. sounds like a hardware issue. Just speculation though
Sent from my DROIDX using XDA App
i successfully updated to froyo from kies. before this i had the stock rom and did not install any custom one
after updating my proximity sensor works when the phone is held vertical in an upright position
but after making a call, if i keep it on the table and close the sensor, the screen doesn't turn off. it should turn off and was working fine in 2.1 for me
can you guys confirm if the sensor turns off even when laid flat on the table?
also, the volume up/down button does not silence the ringtone when i get a call
please reply so that i can confirm whether the problem is with my phone or with the new release.
Not sure about the sensor problem but as far as your second problem is concerned hold the vol down button for a few seconds to mute the ringtone
Sent from my GT-I5800 using XDA App
Proximity Sensor is problematic
Yes The Sensor does'nt seem to be responding towards the end of the call. Just use the home key to light up the screen.
The display screen timeout settings does not automatically turn off even after specified time.this happens very often and need to enable screen timeout settings again and again.
Sent from my GT-I5801 using XDA App
Yes , I am experiencing problem with Swype , it is not responding to aby gesture. I am able to type using swype as regular keypad but not as "swype". I resetted my phone 3-4 times but i wasn't lucky.
So i am using keypad only. Its official DDJP2 FROYO version thpugh its flashed using odin as i was experiencing problem with KIES.
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
satyamsit said:
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
Click to expand...
Click to collapse
May be you have checked "screen lock sounds" option in /settings/sound unchek and see if the problem persists...
deadwood01 said:
May be you have checked "screen lock sounds" option in /settings/sound unchek and see if the problem persists...
Click to expand...
Click to collapse
Thanks a lot for ur reply but the option is unchkd from beginning ... ..
satyamsit said:
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
Click to expand...
Click to collapse
Yes....This is happening
This is the worst release by Samsung , as per me....Even on call if you are using headphone, you will hear clicking sound (argh)
Yes the proximity sensor isn't working fine. Screen does not turn on after a call. So I need to press home screen every time.
And long pressing menu button in call log does not enable search bar which happened perfectly in 2.1
maverickgenius said:
also, the volume up/down button does not silence the ringtone when i get a call
please reply so that i can confirm whether the problem is with my phone or with the new release.
Click to expand...
Click to collapse
For those who r facing the problem silencing the ringtines from vol up down, press power on off button, it shud work.
satyamsit said:
For those who r facing the problem silencing the ringtines from vol up down, press power on off button, it shud work.
Click to expand...
Click to collapse
we do know about pressing the power on/off key but that also switches off the sceen. but volume up/down only silences the ringtone but doesn't switch off screen.
araandroid said:
Yes , I am experiencing problem with Swype , it is not responding to aby gesture. I am able to type using swype as regular keypad but not as "swype". I resetted my phone 3-4 times but i wasn't lucky.
So i am using keypad only. Its official DDJP2 FROYO version thpugh its flashed using odin as i was experiencing problem with KIES.
Click to expand...
Click to collapse
swype doesn't work because languages are not installed. root, delete swype, install swype from official site.
jaskiratsingh said:
Yes....This is happening
This is the worst release by Samsung , as per me....Even on call if you are using headphone, you will hear clicking sound (argh)
Click to expand...
Click to collapse
and during a call, if you press volume up/down button to increase/decrease the volume, the voice breaks for a second and you hear a clicking noise.
these problems are seriously irritating me. thinking of going back to 2.1 or some custom ROM is samsung does not release an update fixing these problems.
Few more problems that I had observed....
1. If you open contacts and press back button you won't be going any where
2. Previously I used to connect my phone using bluetooth to my PC (Ubuntu) but now even after turning on my Bluetooth along with visiblity phone is not visible. Once I was lucky and recognized my phone as "V5" though the device name is different.
3. If you try to add pics to the contacts from your gallery the time taken is very long which was not the case with Eclair 2.1
4. Previously with Launcher Pro plus on Eclair I never had to "Force close" any application, but after upgrading to Froyo the first call itself raised a warning for force close. Even after sometime in my other call I couldn't End my call as the screen was not responsive.
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
techie.raj said:
Few more problems that I had observed....
1. If you open contacts and press back button you won't be going any where
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
Click to expand...
Click to collapse
I was experiencing the same problem on the first day, but after that i rooted my phone and installed busybox. from last 2 days did not find that contacts back key problem anymore.. i dont know its a temporary fix and what has fixed it anyway...
but really .. somehow this release is not at all convincing. so sad.
techie.raj said:
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
Click to expand...
Click to collapse
i too feel the same way mate..
can anybody tell me if I5801ZHJPF better that DDJP2?
I have another different problem my battery life is not going above 10 hrs while on 2.1 i used to get 18hrs. Am i missing some setting or what.I am gonna install something else if this **** firmware does not improve in the next update
i think this update was hastily released.
many bugs in it.
if you see the in-built task manager, the "uninstall" button is not even properly designed.
even accelerometer has some problems
the worst bug ever is the camera bug
theres this geo-tagging option..
until you get a fix on ur location camera will force close..
and it cant be disabled at all..
the only way to get around it is to use 3g or disable network mode in 2g..
19.nvv.11 said:
the worst bug ever is the camera bug
theres this geo-tagging option..
until you get a fix on ur location camera will force close..
and it cant be disabled at all..
the only way to get around it is to use 3g or disable network mode in 2g..
Click to expand...
Click to collapse
i saw somewhere that this can be solved by disabling "use wireless network" option in settings->location and security.
not sure though. try it.
maverickgenius said:
i think this update was hastily released.
many bugs in it.
if you see the in-built task manager, the "uninstall" button is not even properly designed.
even accelerometer has some problems
Click to expand...
Click to collapse
+ add one more bug to the list,
the microphone is also not working properly with different applications like Talking Tom or Talking Parrot, previously they used work on 2.1 without any problem or distrubance.
Did anybody also had the same problem?
One good thing with the Froyo update is previously my phone is used to restart unconditionally with the stock firmware (randomly sometimes during call or when Ideal). But till now no such weird behaviour in the current release.
My nexus stopped vibrating
Hello!
I just realised that my phone does not vibrate anymore at all - not when I recieve a call nor when I recieve a notification of any sort. It doesn't even vibrate when I'm setting the volume to vibrate mode with the rockers. I checked the profile and it is set on Default just like always (I haven't touched any profile settings ever). I downloaded a massage app and even with it running the vibration motor doesn't work at all. I haven't ever dropped or hit my phone in any way, it just randomly stopped vibrating. Do you have any suggestions on how to fix this issue? I'm running the latest CM 12 nightly build with a stock CM kernel (I have some doubts that it might be causing the problems) and have been running the nightlies even before the issue.
Thanks in advance!
Have your tried reflashing your rom, first without wipe and then with? If that doesn't work, please return to stock 5.1.1 through fastboot. If that doesn't work, then it seems the vibrate motor is dead.
Sent from my Nexus 4 using XDA Free mobile app