Database Develop

Strange problems (wifi, top toolbar, some unusual force closes) after froyo update

Hi there guys, I have a few problems,
1.)
I have unusual problem (like no one had before )... Sometimes I get an error when I try to enable wifi over top toolbar (on my Samsung Galaxy S). Wifi is like frozen, no signs of activity or whatsoever. When I go to setting tab and see wifi state it is shaded button and after some time it states "Error" just below same shaded button. When I click on it after it states error sometimes it fixes it self (i.e. turns wifi on), and sometimes I have to reboot it to work.
2.)
This one is a more strange than unusual problem )... Sometimes as it is some kind of collision, when I scroll down my top toolbar it just remains opened as big as a little line no more than half an centimeter of a width. And I can't get it down to fully see information (since after installation of some widget or application or when I receive mail there is everything summarized up there). I don't know if I had installed some game or app or widget which interferes with standard top toolbar?
3.)
Some force closes when browsing Internet (via stock browser) or checking mail (via gmail app) are really annoying, but I was looking for related problems here on forum and it looks like "nothing unusual" for Froyo users....
Are there any solutions to these problems or any related thread that I have missed in my search so you can reference me to or if you can give me some solutions or at least explanations of these strange/unusual problems?
Thank you in forward . I really love this community and one day I will do Android programming too. I really need a kick start (this is not topic related question) ... can you tell me how can I get some applications fast up and running and which books/video tutorials to use to quickly become android developer / how much time is needed (I have devotion and zeal in my toolbox and I have some programming background in Java )?
Respect!

Factory reset?

Well I really want to avoid that solution any other suggestion?
Sent from my GT-I9000 using XDA App

I have all problems you describe as well, I did a factory reset (3 times in total since froyo - for these reasons. the last time I formatted the internal SD card as well, just to be sure) and they remain.
The notification bar might be caused by an app, I am still not sure, but I disabled my quick settings shortcut in the bar and the 3G watchdog notification which indicated I am using 3G and it has not happened since. Rebooting the phone also works.
I have the WIFI thing as well, it happens and works exactly like you say, I press it again and it fixes itself - or not. Weird.
Browser force close and gmail force close happens here as well.
I am contemplating bringing it to a service center but I am unsure if that will solve anything or if it's just buggy Samsung software? Any ideas?

Froyo - Galaxy S - Status Bar Problems
Any one guys? Are we only two people on the internet having this issue?
Can someone at least elaborate a bit?

[Q] calling freeze

Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.

Pics

SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)

Display problems after flashing stock FW Xperia V

I've recently flashed the stock rom for my Xperia V as described below for locked bootloader.
http://forum.xda-developers.com/showthread.php?t=2796554
Since then I face problems with the display/phone acting weirdly . About twice a day I can't turn the display back on (display unlock). In this state the phone actually freezes somehow. One strange exampled I've seen today: I received a mail message, with the set signal sound and notification LED. I wanted to check the message but couldn't turn on the display. So I checked if I can call myself with another phone but the mailbox turned on immediately. The notification LED was still active so I'm not sure if the phone actually freezed or not. The only thing I can do at this state is to remove the battery and restart the phone.
Another problem I've since flashing the rom is that when I start a call is that the display turns off immediately no matter if I place my finger/face over the proximity sensor or not. Funny thing is that the call can be held as usual, but after that I'm not able to hold the call as the display won't turn on until the call partner ends it. When he has ended the call the display turns back on. Right now I really don't know what to do.
Here is the history how the problem started:
- dropped phone on floor and display broke
- exchanged display
- I've had installed Xposed installer on external SD card and modified some things on the launcher. While I was waiting for the new display I've used the SD card in a different phone. This has somehow messed with the Xposed settings I assume.
- After I booted my phone with the new display in place and external SD inserted the UI crashed all the time and the launcher won't come back. So I've restored the system with the androids included function.
- This is where I first saw the above described problem.
- I've tried a different, modded rom. With this the display problem didn't occur but the battery performance was really bad.
- Installed stock rom from link above. Now problem with display present again. So maybe there is an issue with the original 4.3 rom?
Has anybody experienced the same issues as I do right now? I really don't know what to do but the problems really annoy me.
Thanks!

Try to repair it using PC companion

Didn't work. Same problem remains.

Ok, I was able to fix the issue with the display turning itself off during voice call.
The headphone connector does somehow connect the light and proximity sensor to the phones mainboard. This connector didn't sit properly inside the middle phone case which cause a bad connection to the sensors. I've reassembled the whole phone and now this problem has disappeared.
The other problem still remains, I hoped it is linked to the display proximity sensor problem, but now it is clear that this has some other source.
Is there some kind of app monitor available? I assume that there is some app which causes the various hang up, but I have plenty of them installed and deinstalling always just one of them and monitor for various days will last for months.
Is there any possiblity to find out if the lock ups are caused by some app?

Really nobody in here who has any ideas? I've now exchanged the display to a new one as I thought it's caused by a faulty display connector, but the problem remained. I'm running out of ideas now.

How to diagnose freezes & crashes?

I seem to have been bitten by whatever it is that's causing Note 8s to freeze. In my case, it seems to freeze when idle - case closed, always-on display showing a clock. Sometimes the digital clock - just stopped; the last time, the analog clock with the second hand ticking, but an otherwise unresponsive phone.
It seems like this is happening to other people, in a variety of other applications - and the only advice anybody is giving is to see what happens in safe mode, then uninstall applications one-by-one. All of which seems rather time-consuming, and counter-intuitive -- if a single App is freezing the system, that suggests on o/s or hardware issue -- the o/s should be isolating the rest of the system from app misbehavior.
Which leads me to wonder how one might track down what's actually going on. If this were one of our servers, I'd crank up logging and look at crash logs. But... those options don't seem to be available without rooting the phone. (Why does Google insist on making syslogs unreadable by normal users - that puts a big crimp in the ability to do any kind of real trouble diagnosis.)
Any suggestions on how to do crash analysis? Any tools that someone can recommend?

Any insight on the matter?

I have not had this problem, so I would not know how to tackle all down to pinpoint the exact culprit, but I would start by controling what apps I dont want to run in background, in maintenance>battery>always sleeping, I put all the apps I dont need to be in always running state, I would also try to unistall or freeze apps I installed just before the problem began, if you have bk disabler this is a rather easy process, as you can batch-disable/enable apps, in the end it is a trial-error exercise

You can use logcat extreme, Catlog or somthing similiar from playstore. But you need some knowless to see wat happend and root. Perhaps you can pull the log file without root to your computer with ADB.

Sounds like impending motherboard failure. My wife's S7 Edge started doing the same thing then one day it just wouldn't start up at all.
Common thing for Samsung phones unfortunately .... and if you're out of warranty they won't repair without a charge.

Question "Tap to check phone", "Lift to check phone", and (most importantly) "Wake screen for notification" all don't work on new phone

Hello my nerdy pals!
I bought a new Pixel 5a yesterday and set it up normally... no bootloader unlocking or rooting or whatnot.
Everything works as expected except for these features:
1) Wake screen for notification (the one I actually care about)
2) Tap to check phone
3) Lift to check phone
I googled this issue and read a post that suggested I boot the phone in Safe Mode to see if the features still don't work. I did that, and in safe mode they work. The post further said that if it works in safe mode and not normally then I have an app installed that is causing the problem. I should then uninstall apps that are possibly interfering, reboot, and then try the feature again.
I have around 100 apps (nothing crazy, this includes all the system/stock apps). Rather than try to uninstall/reboot/test/reinstall each one, I'm wondering if anyone here has any suggestions for solving this issue.

UPDATE: I ended up the process of uninstalling all my apps to find the culprit, and I did find it.
The app causing the problem was, strangely, a radio app for Canadian stations.