• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Call Rejection Hang ups!

screaminbug said:
Surely, framework must be written in Java too. Only native libraries, dalvik and, of course, drivers, firmware and kernel are written in C/C++. So, if it is a software problem of a sort steelskin speaks about (which I too doubt) it must be in native code (probably in radio library).

It would be interesting to see a logcat's output when this problem happens. Has anyone done this? Could you post it here please?
Click to expand...

Hi screaminbug, if you could let me know where I can find the logcat's ? output I'll post it. I use linux (no MS windows) so I'm familiar with linux CLI and can use connectbot etc as a console. Just need to know which logs and where I'll find them.

Thanks.
 
steelskin said:
Hi screaminbug, if you could let me know where I can find the logcat's ? output I'll post it. I use linux (no MS windows) so I'm familiar with linux CLI and can use connectbot etc as a console. Just need to know which logs and where I'll find them.

Thanks.
Click to expand...

Ok, I googled it, from Android Debug Bridge | Android Developers

I'll post it ASAP.

Enabling logcat Logging

The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered by the logcat command.
Using logcat Commands

You can use the logcat command to view and follow the contents of the system's log buffers. The general usage is:

[adb] logcat [<option>] ... [<filter-spec>] ...

The sections below explain filter specifications and the command options. See Listing of logcat Command Options for a summary of options.

You can use the logcat command from your development computer or from a remote adb shell in an emulator/device instance. To view log output in your development computer, you use

$ adb logcat

and from a remote adb shell you use

# logcat

Filtering Log Output

Every Android log message has a tag and a priority associated with it.

* The tag of a log message is a short string indicating the system component from which the message originates (for example, "View" for the view system).
* The priority is one of the following character values, ordered from lowest to highest priority:
o V
 
steelskin said:
Hi screaminbug, if you could let me know where I can find the logcat's ? output I'll post it. I use linux (no MS windows) so I'm familiar with linux CLI and can use connectbot etc as a console. Just need to know which logs and where I'll find them.

Thanks.
Click to expand...

Sorry. English is not my native language so I may have made a grammatic mistake. By "logcat's output" I meant a log which you can get using logcat command.

Sure, you can use ConnectBot, but it's more convenient if you use adb tool. Unfortunately, adb binary for Linux from Android SDK is not working with Galaxy.
But you can use this one, which works fine:
http://floe.butterbrot.org/external/adb.gz

See this thread for more information.

Cheers!
 
Posted on the O2 forums site 3/Jan/2010

I forgot to mention battery life...

As long as you makesure wifi and GPS are switched off then battery life should be ok... however I read an earlier post that said that putting the phone in it's nice little wallet that comes with the phone is a bad idea and will cause the battery to drain prematurely.

I too have found the same. Putting the phone into the tight fitting wallet must cause one or more of the buttons to activate and cause the battery to discharge much quicker.

If you are having battery issues, don't put the phone in it's wallet unless it is switched off.

Good Luck, Let's hope the next version of firmware sorts these problems out !
The most appalling problems with the galaxy I7500 I4 (O2)

by steelskin on Sun Jan 03, 2010 4:58 am


mobychick wrote:
Im seriously considering this phone but I have read so many bad things. Is the battery really that bad? Galaxy owners come forward pls!


If all you want to do is browse the web on it, it's fine.... HOWEVER, if you want to use it as a proper phone it has some seriously annoying bugs (I consider them show stoppers). They should never have released this phone like this.

I have now had two Galaxy I7500. Both running the I4 firmware, currently still the official latest in the UK as far as I'm aware. I use my phone mainly for normal incoming and outgoing calls, maybe 10-20 calls per day and for business use so it absolutely MUST be reliable. Browsing restricted to 10-20 mins per day.

Here's my list of problems with this phone, starting with the most annoying, inconvenient and liable to cause the phone to be thrown out the window.

1. This is a BIGGI. Call hangups. It doesn't matter whether it's an incoming or outgoing call the phone will intermittently hang up the call as soon as it's answered or a second after you dialled it. Signal strength is excellent, so has nothing to do with poor reception. This alone will drive you nuts will cause you to hate and despise both Samsung and O2 for allowing this to go on and on without a fix... (workaround, sometimes rebooting the phone will fix it till the next time) .. and sometimes not.

2. Screen lock - This phone seems to have a mind of it's own. It will lock the screen seconds after using it when it's not supposed to, again completely intermittent.

3. It will intermittently flash the screen on and off in the middle of the night. First time I saw it I thought the damm thing was possessed, with some ghostly hand keep pressing the lock screen button.

4. Wifi range is not as good as my laptop. (The least of my problems)

- I've not seen the screen flicker issue myself.
- I've not tried the PC Studio software yet so can't confirm any issues with that.

If not for these problems it would be an excellent phone.

Samsung please get this sorted ! O2 PLEASE APPLY PRESSURE ON SAMSUNG TO GET THIS SORTED !

Anybody from O2, acknowledgement of these issues would be most appreciated. Please don't keep fobbing us off with we are not aware of these issues.

If you expect to use one of these phones for heavy duty business use I would not recommend it until Samsung have sorted the top 3 bugs out above.
 
I've run logcat using connectbot (connected as local) and although it's difficult to decide which events relate to the dialler. It looks like either an 'sensor' event occurs which causes the dialler app to end ? or a window ID is missing causing the dialler to end. ?? However somebody that knows the code I'm sure would know what was going on.

If you are still interested in seeing the default log let me know and I'll post it.
 
I believe i have figured out the reason for these call rejections.
It is related to the magnetic sensor. If the phone is in a dense magnetic field (say the sensor gives 1000) the call is rejected.

I don't know yet how much magnetic field is enough to cause this.
 
Interesting, what application are you using to measure the sensor. I could then confirm that my phone behaves in the same way.
 
You can use Sensor Test or Metaldetector.
However i'm not sure it's entirely related to magnetic field because i could not replicate it with a rare-earth magnet.

However, if the phone is at one place ontop of my iBook G4 laptop that has high magnetic field the calls are rejected everytime. That place sometimes also makes the lockbutton go on and of many times within a second without the lock button pressed :o Checked this from logcat.

Weird stuff :)

Edit: The place is right on top of the hard disk so the rejections could still be related to magnetic fields.
 
Thanks, I've had exactly the same problems, including the lock button on and off, (screen flashing on /off). As regards location my call rejections have happened in the car and amongst other computers, in the lounge. I think I have also had the problem out walking ie aware from all man made objects however can't be sure of that. I've given up using mine for day to day use. I'm waiting for Samsung to fix this by releasing an update. I still can't believe they don't publically acknowledge there is a problem. Gone back to using for Nokia Classic for phone use, then swap over the SIM to the Galaxy when I want to use the internet. What a pain !. I'm going to give them till March to release a fix and if they don't I'm going to return it to O2 as faulty. I think I'll try and get the Google phone if Samsung don't sort things out at least you can be sure Google will update the firmware.
 
i had those problems sporadicaly on 1.5 firmwares, but during last ten days that I'm running mustymod, it haven't happened once.

also, very annoying problem with screen going blank during call while waiting for other side to answer is gone with 2.0.
 
Thanks I will give it a try. There seems to be a number of non official firmware updates available, is there a opinion on which one of these firmware updates provides functionality as close as possible to the original 1.5 firware (without the bugs) ? I noticed that with mustymod, the camera, GPS and light sensor are not working, although the developer may be working on it.
 
Hi steelskin, I have the same call rejection timely. But when I cleared the call log frequently, this issue could be eliminated temporarily. After one week&#8217;s running without power off, the issue had not occurred again seemingly. I do wish this could be helpful for finding the real problem of this phone.

Damn Samsung!
 
steelskin said:
Yes, Damn Samsung indeed. It would be nice if they would at least acknowledge our pain even if they plan to do nothing. People don't like being ignored, they think twice about buying Samsung again.

Thanks for your suggestion regarding clearing the call logs, I'll try it and see if it gets rid of the call rejection/call hangup problem.
Click to expand...

Unfortunately I tried it and it didn't work for me. What does seem to have more of an effect is if I leave the phone on the desk and answer the call without actually picking the phone up and holding it to my ear. If I use speaker phone and avoid moving thie phone then the call seems to work. Of course that's really not practicle for a mobile phone. But it may indicate a bad connection somewhere or maybe some of these sensors trigger the problem.
 
Still, it ALWAYS fails for me when I'm on 2g networks, and ALWAYS works for me when I'm on 3g networks..

BTW, seems that the newer firmwares (II8+) does so that the key presses this bug activates are filtered out of the log ...
 
Hi I had exactly the same symtoms as you using IK5 and reported it in the http://androidforums.com/samsung-i7500/32870-ik5-latest-official-firmware-out-npc-italy.html thread. I fixed it buy going back to the official II5 download, by my telephone provider. I think it might have somthing to do with the CSC file messing with the APN setting as I had not taken out the Italien CSC file before installing.But it was really anoying as it always ocurred away from home and always in a 3G area, haven't had time to look further into it as like you need the phone for work.
 
The bug is still with me on II5, on an outing yesterday same thing phone unstable going into lock unlocking locking, camera switching on etc...managed in a moment of calm to switch the 3G off and everything came back to normal . think I will take the phone back and see if it can be fixed :confused:
 
So has anyone reached a conclusion yet? I got my I7500 in october 2009 and it started to reject and hang up calls in march. So I had it for a long time without this problem.

So I went back to use my N73 for a while. But now I wanted to give the Galaxy one more try, after keeping it in my desk for a month. Guess what, the problem is still there.. Rejecting almost every call.

So I flashed Galaxo 1.6.2 with same baseband XXII8. Looks and feels great! But did it help? Well, it's better.. With two days of testing it only rejected one call, not bad. But not good enough. And since I have flashed it now, I guess thats it for my warenty?

I would think Samsung should have come up with something by now..
 
LN-EMD said:
So has anyone reached a conclusion yet? I got my I7500 in october 2009 and it started to reject and hang up calls in march. So I had it for a long time without this problem.

So I went back to use my N73 for a while. But now I wanted to give the Galaxy one more try, after keeping it in my desk for a month. Guess what, the problem is still there.. Rejecting almost every call.

So I flashed Galaxo 1.6.2 with same baseband XXII8. Looks and feels great! But did it help? Well, it's better.. With two days of testing it only rejected one call, not bad. But not good enough. And since I have flashed it now, I guess thats it for my warenty?

I would think Samsung should have come up with something by now..
Click to expand...

I have never experienced this problem, but I can tell you that if you reflash the original firmware (which can be found around here), your warranty is still fine.
 
I sent my phone back for repair as it was constantly dropping calls but only when I was away from home , I thought I was due to the 3G signal,but the repair slip just said updated firmware and replaced screws on the backplate,so I have a feeling more was done than just updating the phone as I had already tried that before sending it for repair. As long as you put an official firmware back on the phone before sending it for repair there seems to be no problem with warranty. The phone is working better now only one dropped call this month and that might have been someone hanging up
 
LN-EMD said:
So has anyone reached a conclusion yet? I got my I7500 in october 2009 and it started to reject and hang up calls in march. So I had it for a long time without this problem.

So I went back to use my N73 for a while. But now I wanted to give the Galaxy one more try, after keeping it in my desk for a month. Guess what, the problem is still there.. Rejecting almost every call.

So I flashed Galaxo 1.6.2 with same baseband XXII8. Looks and feels great! But did it help? Well, it's better.. With two days of testing it only rejected one call, not bad. But not good enough. And since I have flashed it now, I guess thats it for my warenty?

I would think Samsung should have come up with something by now..
Click to expand...

Still not been able to nail down the problem. Tried lots of different firmwares under cupcake 1.5 to no avail. Someone would phone me, the phone would hang up and then I'd phone them back. However my phone is significantly better under Donut 1.6. Still had a couple of hang ups, but very few. Conclusion from my phone, Donut is significantly better.
 
steelskin said:
Unfortunately I tried it and it didn't work for me. What does seem to have more of an effect is if I leave the phone on the desk and answer the call without actually picking the phone up and holding it to my ear. If I use speaker phone and avoid moving thie phone then the call seems to work. Of course that's really not practicle for a mobile phone. But it may indicate a bad connection somewhere or maybe some of these sensors trigger the problem.
Click to expand...

I did used to see this, but now its OK on IK4

Could it be related to the proximity sensor ( http://androidforums.com/samsung-i7500/30397-proximity-sensor-while-making-calls.html#post295902) where dust collects on the IR transmitter/receiver, and stops the dialpad working.

If instead of picking up the phone, just answer, then cover the very top bit (by the speaker) with your hand, to simulate placing it against your face. You dont even need to touch it....

Does this then drop the call?

Saying that my dialpad issue is back now so I need to re-clean the sensor, but maybe this is why it not dropping calls.....
 
The first two days with 1.6 it seemed like it was much better. But today it did not work at all.. Rejecting all incoming calls and I can't even make outgoing calls. Back to my N73 again :(

Restarting the phone did not help at all. And it didn't seem to be affected by the proximity sensor in any way.

Thinking about dropping the hole phone and go get me a HTC Legend instead..
 
Well, my last post was in November 2009 after having not solved the problem with the call hangups I put my galaxy back in it's box, hoping that Samsung would eventually produce an update.... no chance.

Anyway I got it out of it's box last week and decided to update it to Android 2.0 compliments of MustyMod (V1.03b) available here mustymod Samsung Galaxy Rom .... Boy was I glad I did upgrade to Mustymod V1.03b , after having made over 50 calls with no explained hangups and received about 50 calls and only had about 4 unexplained hangups (which I can certainly live with) my Samsung Galaxy I7500 is now working like it should have from the start. (No Thanks to Samsung, MANY MANY thanks to MustyMod). I can't put into words how pleased I now am with this phone. The GPS and associated Apps are just great. Surfing the web via 3G or WiFI works just fine. I Love this phone now and all the apps in market are just amazing.

However, with the mustymod 1.03b version there are two things that don't work. The camera and bluetooth. I can live without these two functions, the rest of the phone makes up for the loss of these two devices. So as long as you can also live without the camera & bluetooth and you have the call hangup issue that is driving you nuts, then I would update to Mustymod's V1.03b.

Just a couple of notes when updating the phone...
You need the Odin Loader (Odin: http://www.sendspace.com/file/i1mjwk ) which only runs on windows (I used XP) however you MUST also install the PC Studio software provided with the phone which installs a driver that the Odin software uses.

Unzip the tar files and in the odin software select the four tar files. Plug in the phone and put it in firmware download mode by selecting and holding down the following three buttons simultaneously for 2-3 seconds.. The buttons are PowerOn, OK and VolumeDown. The screen displays what looks like a clipart image of an SDCARD with the words downloading. Odin should detect the phone and show the port ie USB0/Com3 etc and then you just click on the start button and wait for the download to complete. After Odin said the download was complete and verified, Power down the phone and power backup.

There also appears to be Android 2.1 available for Galaxy i7500 available from here .. Latest ROM

I have a second Galaxy I7500 (Lucky Me) which I will install 2.1 on and let you know how it goes.

Regards
 
You must log in or register to reply here.
Back
Top Bottom