I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
siamboyecc said:
I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
Click to expand...
Click to collapse
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
afrizal_chen said:
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
Click to expand...
Click to collapse
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Now I changed sleep mode =2 and it's working.
siamboyecc said:
Now I changed sleep mode =2 and it's working.
Click to expand...
Click to collapse
That should have no effect whatsoever on wifi.
Also, if you're running a newer kernel with the PLL2 commit, you should be setting this to =1... You'll get much better battery life, and you'll be able to OC without SoD (at least not as many as previously )
siamboyecc said:
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Click to expand...
Click to collapse
Force_cdma= should be set to 0 or deleted as your t7373 is a Rhod100 if i'm correct.
So your problem seems to be that you don't receive phone calls when your phone is in sleep mode? Make sure you run the newest kernels. I can't remember issues like this on my rhod100..
Maybe just try a clean build, delete data.img (rename if you don't wanna lose everything, backup!). Or try a different build to pinpoint your problem.
And the last thing, as you are running a froyo x build, this question would've fitted perfectly in that thread
Good luck!
Thanks everybody.
Related
Anyone know why my hardware button lights don't turn off? I'm not overclocking or anything
Android doesn't support controlling the keyboard/button backlights, so if they're on in WM before loading Android, they'll stay on as long as the device is in Android, and if they aren't lit up when in Android, they will not light up. The only solution is to make sure the hardware buttons are not lit up before booting into Android.
viper786 said:
Anyone know why my hardware button lights don't turn off? I'm not overclocking or anything
Click to expand...
Click to collapse
One of the solutions is to turn off auto-backlight control in WinMo. This way you don't have to worry about WinMo tripping the backlight right as you're trying to run haret.
The easiest way to do it is when you open the xdandroid app in winmo, before you hit "run android" press the top button to turn off the screen, then turn it back on, then hit "run android." Works for me all the time
-------------------------------------
Sent via the XDA Tapatalk App
my phone started doing that today, but for some reason mine stay on even on windows.
redsrt4 said:
my phone started doing that today, but for some reason mine stay on even on windows.
Click to expand...
Click to collapse
Reboot WinMo. Sometimes strange things happen! But a reboot or two usually sorts them out
snalbansed said:
Reboot WinMo. Sometimes strange things happen! But a reboot or two usually sorts them out
Click to expand...
Click to collapse
must have booted like 10 times but they still stay on dim but they are still on. im gonna try reflashing my rom see if that takes care of it.
well lights are still on after i did this:
task29
flashed rom
reflashed hard spl
any other suggestions on what i can do to fix it?
thanx in advance
If they stay on even in WinMo, there *may* be a hardware issue. Have you tried flashing back to stock?
im goin to try that today
I'm having exactly the same problem. Can you tell me if you found any solution to solve this issue?
Anyone get a solution to this? I've tried flashing back to stock and the keys still stay lit.
kaskd said:
Anyone get a solution to this? I've tried flashing back to stock and the keys still stay lit.
Click to expand...
Click to collapse
If your lights never turn off in WinMo, something is wrong with the phone's hardware I would think.
As was stated previously, if you boot Android with these lights on in WinMo they will stay on in Android. There's a patch in the works to fix this issue...
Try a new battery. I had similar issues with battery not fully charging changing the battery cleared it up. Sprint gives batteries for free.
Hello everybody.
I have a rooted 4.0.4 XXLFB Galaxy S3 and have noticed a problem.
Whenever I'm on a call using my blueooth headset, the screen turns on once every 30 seconds, give or take.
It's a problem because if I have the phone in my pocket, sometimes I mute the call, other times I turn off the headset...
Does anybody know how to solve this?
Thanks in advance.
Posting to add a "me too" to the list. Trying a ton of different things, almost to the point of clean device.
Hit the button and the screen turns off, about 2-5 seconds later, screen turns back on. Does not matter what I do. Seems to do it with speakerphone option too. If neither Bluetooth nor speakerphone are used, and you put the phone to your ear, backlight stays off. Otherwise, it automatically turns back on by itself. Tried with wifi on/off, speaker with bt on/off, different headsets, etc. My Wife's does not have this issue, so I gotta look into what is different. There has gotta be a setting or app installed that is doing this. I've even tried apps such as screebl and others. Some even had a thing to say lock it off till press button, and it still comes back on after 2-5 seconds. I've muted and hung up on many people when the phone was in my pocket because of this issue.
I've not used a BT headset but i'm thinking that maybe because the phone isn't against your head the screen comes on. possibly to give you information about the caller.
I'm not saying you should put the phone to your head even though your using bluetooth either.
thanks, but, don't help, tried that too. Had entire top half of phone covered during most tests. Screen does not turn off unless I press button, then comes back on automatically after 2-5 seconds. I did find one app today that seemed to work, but not sure if it works too well "Smart Screen Off".
Sounds silly but have you tried locking the handset?
That's what I meant by pressing the button. Button on right side that if I am not on a call, turns off screen and locks it.
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
agree with the above. if you leave call status up while connected via BT headset, screen remains active (comes in and out). if you exit active call status (ie press home) then the screen timeout works. if you are talking on the phone without headset, no problem.
so yes, that's the prob. any solid fix yet?
please and thanks....
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
Thanks a lot, visegrip. It was really frustating having to redial every other call because i hang up without noticing.
Any solution to this problem? Hitting a home button and locking the phone is not an option when I keep my phone in a leather holster on my belt. That's a main reason for having bluetooth as hands free.
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
Almazick,
It would be great if you can send me the fix!
ital1981 said:
Almazick,
It would be great if you can send me the fix!
Click to expand...
Click to collapse
Here is the fix for a screen that I created. Let me know if it works or not for you.
http://www.mediafire.com/download.php?1ikj7d4wnjs9hx5
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Inane65 said:
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Well, It's pretty easy.
Profile -> Phone Offhook
Task:
Wait 20 seconds
App-> Go Home
Display -> System Lock
In case if you'll have any problems just use my apk file which is exactly the same.
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Hmmmmm... OK. Thank you. I'll have to try that and see how it works. I was looking, hoping and working on trying to get something that would keep the screen off. Dialing, talking and ending the call. I've got something that seems to work for the most part, (I still get quick flashes, which is fine) but still have some more work to do on it.
Sent from my ADR6425LVW using xda premium
visegrip72 said:
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Click to expand...
Click to collapse
It's not fixed. I'm getting crazy about this master bug.
I have two problems in my Samsung Galaxy S3
1- When I open the lock there is a transition of black lines on the screen. The moment I open the lock few black lines appear on the screen for a second. It blinks and then it is back to normal. But when I switch off the power saving mode it doesn't. This problem just starred to appear as there was no such problem before.
2- My battery drains on idle. I charge my phone and within 3 hours it seems to go down to 87 % without any use. The cell standby is what is eating the battery. It takes about 70% of power in cell stand by. I have read on many forums about the it but i don't want to flash my phone to solve that problem.
Please help me to solve my problems.
One backup data and factory reset .
Two check for updates via KIES .
Three Wifi settings turn off always on .
Fails then as you don't want to flash the next step is a service centre .
jje
skhan33 said:
I have two problems in my Samsung Galaxy S3
1- When I open the lock there is a transition of black lines on the screen. The moment I open the lock few black lines appear on the screen for a second. It blinks and then it is back to normal. But when I switch off the power saving mode it doesn't. This problem just starred to appear as there was no such problem before.
2- My battery drains on idle. I charge my phone and within 3 hours it seems to go down to 87 % without any use. The cell standby is what is eating the battery. It takes about 70% of power in cell stand by. I have read on many forums about the it but i don't want to flash my phone to solve that problem.
Please help me to solve my problems.
Click to expand...
Click to collapse
Are you sure this is not the ripple bug? Is it a dark wallpaper? If so turn off the ripple.
JJEgan said:
One backup data and factory reset .
Two check for updates via KIES .
Three Wifi settings turn off always on .
Fails then as you don't want to flash the next step is a service centre .
jje
Click to expand...
Click to collapse
I tried them all doesnt work
Kangburra said:
Are you sure this is not the ripple bug? Is it a dark wallpaper? If so turn off the ripple.
Click to expand...
Click to collapse
I don't think it is a ripple bug and I have tried all wallpapers it appears in all of them whether it is a dark one or plain white
skhan33 said:
I don't think it is a ripple bug and I have tried all wallpapers it appears in all of them whether it is a dark one or plain white
Click to expand...
Click to collapse
but have you turned the ripple effect off to be sure?
skhan33 said:
I tried them all doesnt work
Click to expand...
Click to collapse
Fails then as you don't want to flash the next step is a service centre
jje
Kangburra said:
but have you turned the ripple effect off to be sure?
Click to expand...
Click to collapse
Yess I did it still appears
skhan33 said:
I have two problems in my Samsung Galaxy S3
1- When I open the lock there is a transition of black lines on the screen. The moment I open the lock few black lines appear on the screen for a second. It blinks and then it is back to normal. But when I switch off the power saving mode it doesn't. This problem just starred to appear as there was no such problem before.
2- My battery drains on idle. I charge my phone and within 3 hours it seems to go down to 87 % without any use. The cell standby is what is eating the battery. It takes about 70% of power in cell stand by. I have read on many forums about the it but i don't want to flash my phone to solve that problem.
Please help me to solve my problems.
Click to expand...
Click to collapse
Just about to write a new thread about this problem. I have the exactly same screen problem you are having. I notice the problem since 2nd week I bought the phone. Try factory reset, flash new firmware (from original firmware which I forgot the version > latest stock LH1 > leaked LI8 > LIB), re-flash LI8 once and of course with a full wipe every time I flash. But the same thing happens again. This is so annoying since I found the problem. Try a lot (ripple off, force GPU on, change wallpaper, screen mode, screen tone and everything about screen) still no solution yet.Have to visit Samsung Centre I guess
I think maybe others have this problem too just they didn't notice it. Try turn on power save mode (it doesn't matter you tick the options inside or not, I have try them all), locked or turn off your screen then turn it on. Stare still on the screen to see if you have the black line.
ctingwei said:
Just about to write a new thread about this problem. I have the exactly same screen problem you are having. I notice the problem since 2nd week I bought the phone. Try factory reset, flash new firmware (from original firmware which I forgot the version > latest stock LH1 > leaked LI8 > LIB), re-flash LI8 once and of course with a full wipe every time I flash. But the same thing happens again. This is so annoying since I found the problem. Try a lot (ripple off, force GPU on, change wallpaper, screen mode, screen tone and everything about screen) still no solution yet.Have to visit Samsung Centre I guess
I think maybe others have this problem too just they didn't notice it. Try turn on power save mode (it doesn't matter you tick the options inside or not, I have try them all), locked or turn off your screen then turn it on. Stare still on the screen to see if you have the black line.
Click to expand...
Click to collapse
I feel the same that I have to walk in to a samsung service centre. I don't understand how such big phones have these errors and I always have bad luck in terms of mobile phone. I always get a faulty piece or something with some problem or other.
I tried power saving mode and there is no blinking as I have mentioned above but why does it blink on power saving mode ??? My friend too have same phone but he doesn't have an such problem.
skhan33 said:
I feel the same that I have to walk in to a samsung service centre. I don't understand how such big phones have these errors and I always have bad luck in terms of mobile phone. I always get a faulty piece or something with some problem or other.
I tried power saving mode and there is no blinking as I have mentioned above but why does it blink on power saving mode ??? My friend too have same phone but he doesn't have an such problem.
Click to expand...
Click to collapse
Guess like we have no other choice but head to Samsung service centre
ctingwei said:
Guess like we have no other choice but head to Samsung service centre
Click to expand...
Click to collapse
Well finally I've found a thread that describes the same bug I'm having.
I confirm this bug. When power saver mode is ON, there's a flickering when you unlock the screen, black lines appear for a second and then disapper, like a screen refresh or something... but this problem is not there when power saver mode is OFF. Weird.. but I just turned it off. Have you guys found another solution?
GasparIPerez said:
Well finally I've found a thread that describes the same bug I'm having.
I confirm this bug. When power saver mode is ON, there's a flickering when you unlock the screen, black lines appear for a second and then disapper, like a screen refresh or something... but this problem is not there when power saver mode is OFF. Weird.. but I just turned it off. Have you guys found another solution?
Click to expand...
Click to collapse
Turning off the power saving mode is the only solution by now. And I also found the same problem happened when I use camera. It's quite hard to notice because it happens just right after you click the camera icon before the screen changes.
Sent from my GT-I9300 using Tapatalk 2
This could be a fix
Hi guys
Do you have whatsapp installed?
I had the phone for 5 days now and it ran perfectly for about 3 days.
I used the screen sticker that came with the phone for a while because i didn't have
a screen protector(still not). Then i started installing stuff and whatsapp was installed
then i noticed crappy black horizontal line flicker the screen. Today I had a friend over
and the phone when mad, it booted but then stopped responding, now here's the part where
the black flicker gets fixed. I restored the phone to its default settings and the black was gone
installed whatsapp and droidwall and the flicker came again, it's uninstalled now and the phone
works fine.
Turning off power saving mode didn't work for me, this did
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem
Hi everyone, I'd like to ask you a question. I have a Mi Pad 4 and every time, after booting, the touch screen does not appear to respond immediately to the commands on the lock screen. I have to press the screen randomly to make it work. Once the touch starts, the tablet works perfectly.
Can you tell me if I'm the only one with this problem?
Thanks!
I do too. The screen would hang up when boot. I have to turn off the screen and on again for it to work.
And anyone have auto shutdown bug? Mine will auto shutdown when enter deep sleep and battery is below 15%, even when plugged in. Nothing happen above 15%.
Never_Sm1le said:
I do too. The screen would hang up when boot. I have to turn off the screen and on again for it to work.
And anyone have auto shutdown bug? Mine will auto shutdown when enter deep sleep and battery is below 15%, even when plugged in. Nothing happen above 15%.
Click to expand...
Click to collapse
Fortunately I'm not the only one with this problem/bug.
Regarding the DeepSleep and the shutdown I have never try to verify it. Usually when the tablet is 30% I recharge it.
I'll try to test that.
Currently I have the HavocOS 2.8 ROM and I don't know if the deepsleep is set in the same way. But ill will try and I let u Know.
If someone else has our problems please reply this thread.
Yes after boot I have to pick up the tablet and move to unlock the screen faster.
Maybe its a feature?
It appears in TWRP too
paul-planlos said:
Yes after boot I have to pick up the tablet and move to unlock the screen faster.
Maybe its a feature?
It appears in TWRP too
Click to expand...
Click to collapse
I don't know, I thought it was just my problem, but apparently I'm not the only one. Even with TWRP and custom rom happens