[Q] CM Wifi problem! - Samsung Galaxy Fit GT 5670

Hello. I have some kind of a big problem with all CM ROMs. I start the Wi-fi>Connect, I remain with my wi-fi opened, and if the screen locks, and stays a period like this, then my phone will be blocked, and I will need to remove the battery and plug it in again, to start the phone. Any good advice please? I mention I tried this with and without OC, and is still the same problem and I need my wifi on all the time! Thank you anticipated!

Blocked??
In settins>wireless networks>wifi, press menu, and select advanced, there check if sleep policy is ticked under "never"...
Typed on a small touchscreen

a.cid said:
Blocked??
In settins>wireless networks>wifi, press menu, and select advanced, there check if sleep policy is ticked under "never"...
Typed on a small touchscreen
Click to expand...
Click to collapse
Ty Very much, it was "Never when plugged in" checked, I think I was supposed to check Never, so I did. If It's resolved I'll post here.

Ty
Thank you very much man, I tested it, and it seems I don't have any problems so far. I realy forgot about the advanced tab I wish you well!

You're welcome
Typed on a small touchscreen

Related

problem with soft reset plz help

i downloaded the Device Reset -Ranster which is the red button on the phone which does a soft reset but for some reason my screen somtimes goes black but the keypad buttons are lighting and i have to take out the battery i have been searching for the shortcut buttons that do the soft reset without taking out the battery and cant find it??
Please someone let me know what those two buttons are, thank you
Have a look at the bookmarks in my signature - look at the HD2 cabs thread. There's a cab on that thread called TouchX reset & wifi. It gives you both a reset button and a wifi toggle.
Or use xda shutdown its realy good.
Look here:
http://forum.xda-developers.com/showthread.php?t=544016
thanks for your help but i already have a reset button but thats not the issue my issue for some reason sometimes my screen won't turn on the buttons are lighting and i know the phone is on but the screen itself won't light up and i need i guess a way to restart it with the buttons on the phone i don't know why it happens maybe its because of the cookies home tab cause thats when the issue started when i installed cookies but i love too much to delete it
hus09 said:
thanks for your help but i already have a reset button but thats not the issue my issue for some reason sometimes my screen won't turn on the buttons are lighting and i know the phone is on but the screen itself won't light up and i need i guess a way to restart it with the buttons on the phone i don't know why it happens maybe its because of the cookies home tab cause thats when the issue started when i installed cookies but i love too much to delete it
Click to expand...
Click to collapse
I had this issue before. Check whether the below setting is enabled.
Start > Settings > Menu > All Settings > Today > Items
The setting "Today timeout", at the bottom left hand corner,
should not be selected/enabled.
thanks a lot Zentury that hit the spot it was on time out every 2 hours which was crap lol thanks for your help guys
del post! hum..mmm!
anhphe076 said:
App Soft Reset:
Click to expand...
Click to collapse
Man...people aren't learning to read before replying...

How to Disable ICS bugfix/bugreport?

Hi, everyone. I always accidentally press my NS' power + volume up buttons, which activates the bugfix/bugreport email window.
Is there any way to safely disable this feature?
Thanks in advance.
Sorry to ask, but what? You mean you press them when powering up the phone? If not, could you post a screenshot?
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
flodb113 said:
Sorry to ask, but what? You mean you press them when powering up the phone? If not, could you post a screenshot?
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Click to expand...
Click to collapse
Yes, I accidentally press them when powering on or off my NS. Try holding the power and volume up buttons. Your NS will vibrate and bring up your default email app and compose a bugfix/bugreport email for you.
IIIV said:
Yes, I accidentally press them when powering on or off my NS. Try holding the power and volume up buttons. Your NS will vibrate and bring up your default email app and compose a bugfix/bugreport email for you.
Click to expand...
Click to collapse
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?
ghost_301 said:
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?
Click to expand...
Click to collapse
Turn off USB debugging.
The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.
IIIV said:
The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.
Click to expand...
Click to collapse
You shouldn't need USB debugging for TB on any new rom. From official FAQ:
40. Why does Titanium Backup demand that the Android Debugging Bridge (ADB) be enabled? I don't develop on my phone and don't want this.
The only reason is that on some ROMs, earlier versions of Superuser (the app that grants root privileges) didn't work properly if ADB (USB debugging) was disabled. This is why I added the warning at startup.
Nowadays, on most ROMs you can leave USB debugging disabled in your phone settings and also disable that warning in Titanium Backup. The option is: MENU -> Preferences -> "Warn if no USB debug".
Click to expand...
Click to collapse
Uni7 said:
You shouldn't need USB debugging for TB on any new rom. From official FAQ:
Click to expand...
Click to collapse
Thanks for the info, it works! Never know it's the USB Debugging option, guess I never explore deep enough.
Thanks again!
Uni7 said:
Turn off USB debugging.
Click to expand...
Click to collapse
[CM9 nightly] unluckly this doesn't help
IIIV said:
The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.
Click to expand...
Click to collapse
mcalamelli said:
[CM9 nightly] unluckly this doesn't help
Click to expand...
Click to collapse
Sent from my ice cream powered Nexus S
mcalamelli said:
[CM9 nightly] unluckly this doesn't help
Click to expand...
Click to collapse
have you solved this problem ?
ghost_301 said:
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?
Click to expand...
Click to collapse
Same here on my Galaxy Nexus...anyone eager to help us out?
I have the same problem. HELP
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
I should add that in addition to the way mentioned above that will completely disable it, disabling USB debugging should also disable it in 4.0.4.
Sent from my brain using human to phone transport technology.

Dock Wakeup Issues

Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?
KinetiClutch said:
Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?
Click to expand...
Click to collapse
Are you using custom kernel?
buhohitr said:
Are you using custom kernel?
Click to expand...
Click to collapse
Yeah CROMI. Tried both thats and hunds kernels both with same result.
KinetiClutch said:
Yeah CROMI. Tried both thats and hunds kernels both with same result.
Click to expand...
Click to collapse
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?
buhohitr said:
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?
Click to expand...
Click to collapse
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?
KinetiClutch said:
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?
Click to expand...
Click to collapse
try the key with the lock see if that works.(top right handside of the keyboard).
buhohitr said:
try the key with the lock see if that works.(top right handside of the keyboard).
Click to expand...
Click to collapse
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.
I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?
KinetiClutch said:
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.
Click to expand...
Click to collapse
OK, last try, disabled the screen lock (no lock screen) and see if it wakes.
sbdags said:
I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?
Click to expand...
Click to collapse
Yeah when I open the lid this does wake the screen.
I guess this must be it, weird is it even worth the bother of emailing ASUS?
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough. Noticed that tonite i've had no issues with using the trackpad to wake the screen however, spotify is running so maybe that interferes with the locking process?
Thanks for the help Buh, but don't think it's worth disabling the lock screen completely just to get this working!
KinetiClutch said:
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough.
Click to expand...
Click to collapse
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.
_that said:
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.
Click to expand...
Click to collapse
I hate you
I guess this is my tablet punishing me for using such poor stock ROM's on it for so long
I also have this problem when I use Cromi. I found that I can "fix" it by clicking and unclicking "MobileDock Battery saving mode" whenever I reboot the tablet-doing so allows me to wake the screen using the keyboard. Also, see if you have the same problem with Cromi-X. I recently upgraded to Cromi-X and the keyboarding waking screen problem went away.
I had the same issue, and fixed it with a clean wipe and install...

[Q] Wifi goes off after the mobile screen goes sleep

Hi to all, I have this problem after upgraded to 4.1.1, my wifi goes to sleep when the screen goes to sleep
i have tried this method too setting-->Wi-Fi-->Advanced-->kept wifi on during sleep as never, even though the same problem persist, Kindly do help
Go to Setting > Wi-Fi > hit Menu Button Go to "Advance"
Keep Wi-Fi on during sleep = make it "Always"
ekhasti said:
Go to Setting > Wi-Fi > hit Menu Button Go to "Advance"
Keep Wi-Fi on during sleep = make it "Always"
Click to expand...
Click to collapse
oh goddddd, please see my full message and then reply
santha3e said:
oh goddddd, please see my full message and then reply
Click to expand...
Click to collapse
bro which rom ur using??? do you try to restore ur phone??? may b it will work
santha3e said:
Hi to all, I have this problem after upgraded to 4.1.1, my wifi goes to sleep when the screen goes to sleep
i have tried this method too setting-->Wi-Fi-->Advanced-->kept wifi on during sleep as never, even though the same problem persist, Kindly do help
Click to expand...
Click to collapse
Dude, see the thing in RED, you have made it NEVER, hence it disconnects the wifi when screen is OF. You need to make it ALWAYS to prevent it from disconnecting.

Screen Problems

I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
goldblot said:
I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
Click to expand...
Click to collapse
Do you use glass protector?
You can you test the touchscreen w/o the glass protector.
settings > about phone > diagnostics > test > test the touch screen
With the battery Unfortunately it is true that the battery is not a super long lasting device, but with moderate use of the device(not stressing it) the battery last me through out the day.
Siam4k said:
Do you use glass protector?
You can you test the touchscreen w/o the glass protector.
settings > about phone > diagnostics > test > test the touch screen
With the battery Unfortunately it is true that the battery is not a super long lasting device, but with moderate use of the device(not stressing it) the battery last me through out the day.
Click to expand...
Click to collapse
I don't use any protectors at all.
And, for some reason, there isn't a "diagnostics" under "about phone" in the settings.
The battery drain is weird because it can drain really quickly (with verrrrrry little use, literally just turning it on every hour to check the time).
If you want to test your touchscreen, you can open diagnostics by press *#*#7378423#*#* in phone app.
Hope this help! but I never faced this problem before, better check with Sony service.
civilzaza said:
If you want to test your touchscreen, you can open diagnostics by press *#*#7378423#*#* in phone app.
Hope this help! but I never faced this problem before, better check with Sony service.
Click to expand...
Click to collapse
For some reason, it checks out fine. It just acts weird like in the op only at the lock screen.
goldblot said:
I don't use any protectors at all.
And, for some reason, there isn't a "diagnostics" under "about phone" in the settings.
The battery drain is weird because it can drain really quickly (with verrrrrry little use, literally just turning it on every hour to check the time).
Click to expand...
Click to collapse
Did you get the last firmware update for your phone?
try to install the latest firmware for the phone and get security patch.
Siam4k said:
Did you get the last firmware update for your phone?
try to install the latest firmware for the phone and get security patch.
Click to expand...
Click to collapse
Does root still work with the latest update?
And trying to update via Flashtool doesn't work, don't know why.
goldblot said:
Does root still work with the latest update?
And trying to update via Flashtool doesn't work, don't know why.
Click to expand...
Click to collapse
You can use Flashtool to update your device after root and use the included Xperifirm to download the firmware.
http://www.xperiablog.net/2017/02/2...te-33-2-x-4-70-with-january-security-patches/
download the lastest update for your device(depend on your phone .model )and follow instructions
i have this problem how i can fix it ? Any soliton ?
PislickB3 said:
i have this problem how i can fix it ? Any soliton ?
Click to expand...
Click to collapse
No solution just yet for me even updated to Nougat 7.0 update through flashtool. I think I'll just break down and send it in to Sony soon but I'm exploring other options before I do that.
goldblot said:
I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
Click to expand...
Click to collapse
This is called Ghost Touch. I read you don't use any kind of protectors so it is a hardware problem and you can't fix it with software repair. If you have warranty use it, if not you will need to open it and remove connectors and put them back. Most of time that will solve problem, but my advice is to send it to service (there is electricity problems from you and all other things that you can screw up if you are not careful). You can try to google for more informations, but mostly you will end up with what I wrote you.
Edit: Because you have that problem, phone thinks you are using your screen whole time and it never goes to sleep could be a problem for a battery drain.

Categories

Resources