Hi I am running Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid_V2_1_64.08.21_CubeV2 ROM.
And everytime I get an incomming text message or e-mail the backlight comes on.
This happens even after you put it into standby and none of the other buttons will wake it only the power button.
i think that is by default and if u want the phone to wake by pressing any key than u have to make that change under settings.
It should not do that, the last ROM I used did not have that issue. It may not be the ROM I would like to know if anyone else has this problem.
Hi everyone..is there really no way to disable the screen turning on when a text or e-mail comes in. When using a WM6.1 ROM, I have tried different ROMs and they all the doing the same. It seems this should be something that can be configured.
Any input from the experts...if not I will go back to WM 6.0
I didn't have it happen with L26 v4 ROM - it does with Dutty's and it does with Death v3. I have heard from others in those threads who say that it does not happen to them. Some have said that the BBCONNECT program 4.0.0.92 is the solution - I have not bothered to search for or try yet. For me , right now, the common thread seems to be AT&T based ROMs
Arghhhhh....I hate to step back into the dark ages but that issue really bugs me. Knowing that my phone is in my case and everytime and e-mail comes in the screen turns on for 10sec....that accounts for the my short battery life.....And I only want to run the ROM's from Dutty he does really great work....wish I knew half of what he does. I might be able to fix it myself...That then brings the question why certain ROM's an not others...
I will leave that question to the experts.
I think it does this because it is putting an alert notification on the screen... I disabled those on mine and they still seem to come on the screen!!
It's so annoying to have to deal with your emails and at the same time have to dismiss countless notifications!!!
Same annoying problem here.
WM 6.1, and every setting in 'sounds & notifications' fails to show results.
Whether I disable or enable the tone, the showing of a message, or the vibration.. no dice: it keeps waking up from standby mode.
i remember some else asking this question as welll... and i think someone was talking about changing something in the the registry, but i am also interested in this. it would come in handy when i have to put my phone in standby for a long time.
bump
I too have this same issue. I've had my new ROM for several months and love it, but I would like to know how to stop the backlight from turning on everytime an email is received.
It never used to do this, however I am pretty sure the backlight always came on for new text messages.
I can deal with the text messages. However, I run blackberry connect for my work email. Having the backlight come on for each email obviously kills the battery life.
I know if can be disabled as it was before. The question is how? Is there a registry setting?
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
Click to expand...
Click to collapse
Mine locks up when Gyrator2 tries to rotate the screen on incoming calls. Really annoying. I want to be able to rotate my screen in most programs, but it always seems to screw up my incoming calls and creates more lag...I'm gonna try to go back to sensorlock instead of pocketshield...
I will try to post it to the official forum as well.
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
Click to expand...
Click to collapse
I had to same problem. I had Gyrator2 running which rotated the screen and screwed up Pocketshield screen.
I put an Event in Gyrator2 to disable rotation when in PShield screen.
The Event should be the same as Manila's except application/window title is "PShield"
That fix the problem.
i get odd issues as well
I agree, I get odd issues as well. I get the occassional hang, crash, missing bar etc. I uninstall pocketshield and I don't get issues. I'm using NATF 2.3 rom. I paid for it and it worked ok for a while until I noticed these intermittent problems...
wmserver said:
I had to same problem. I had Gyrator2 running which rotated the screen and screwed up Pocketshield screen.
I put an Event in Gyrator2 to disable rotation when in PShield screen.
The Event should be the same as Manila's except application/window title is "PShield"
That fix the problem.
Click to expand...
Click to collapse
I created a rule in Gyrator almost immediately after installing PS - I didn't want it to rotate the PS screen.
I left it up to Gyrator to get the window name and now my rule is set for the window #NETCF_AGL_BASE_.
But my problem is not in rotating, my problem is in unlocking (at least I think so). Anyway, will try to change the window name to PShield and see if it makes any difference.
EDIT
Nope it didn't. The top bar disappeared again during the first seconds of my testing :-(
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
Click to expand...
Click to collapse
An updated version has now been released (9th Dec) to fix this problem...
rmjjjt said:
An updated version has now been released (9th Dec) to fix this problem...
Click to expand...
Click to collapse
Thank you my friend for letting me know. If this is indeed fixed I don't mind paying the $13. Will check it right now.
New version available today - but it's not working correctly. after I use the slide bars one time to ignore a call, every call after that is missing the slide bar (answer and ignore soft buttons are there though) and when caller hangs up before I take any action PS just sits there, like it's stuck. Sounds like the same problems you describe earlier.
Im using PocketShield, but I was wondering - the phone always locks after I insert the stylus (I have Touch HD), after a while PocketShield kicks in and after that if I want to unlock the device, I first have to unlock the "normal" lock and then the PocketShield. Really annying.
Is there a way to disable the lock after stylus insertion?
chetlet said:
New version available today - but it's not working correctly. after I use the slide bars one time to ignore a call, every call after that is missing the slide bar (answer and ignore soft buttons are there though) and when caller hangs up before I take any action PS just sits there, like it's stuck. Sounds like the same problems you describe earlier.
Click to expand...
Click to collapse
actually i just experience this an hour ago.. also every time I slide the keyboard to unlock my Fuze the screen freezes on the landscape mode. all keys on the keyboard besides the windows key. I hope they fix these bugs right away..
I have the same problem with the top bar disappearing. I'm not running Gyrator or anything like that. I'll try a new version when the bugs mentioned have been ironed out. It is a great product though. I do like it.
Are any of these being posted in the PocketSheild forum? They need to know the bugs.
cheez said:
Are any of these being posted in the PocketSheild forum? They need to know the bugs.
Click to expand...
Click to collapse
yes many people posted on the pocketshield forums with same issues...
i dont know if anyone else is having this issue... but
i seems that when slide to answer is activated PSPP some calls get answered automatically... and it takes me to the "talking" screen immediately.
any help on this issue would be super!
I'm having other issues with PocketShield. I didn't have this same problem with version 2.0.6.3, but with version 2.1 I started to have problems with my alarm notification. When the alarm goes off, it just quickly vibrates once and just stops if it's in a locked state. Also, I noticed a heavy battery drain issue--the battery charge would drop about 10% each hour. Once I uninstalled it, the problems with the alarm and battery drain stopped.
Even with the new version (2.1.0.1) I still have problems answering phone calls. I'll slide to answer and the phone just keeps ringing. I hit the "Send" key and nothing happens. I hit the "Answer" soft key and still nothing....
Anyone else still see these problems?
I have a different issue, when phone is not locked and I have an incoming phone call, pocket shield kicks in and shows me "lock screen" where I have to slide to unlock the device and only then I get the standard "Incoming call" screen...
v2.1.0.1
Major Problems
Well I was gonna pay for it but their payment server seems to be phishing site. Also it crashed SQB and when I uninstalled it, the program removed my outlook email account. Sorry but looks like malicious program so going back to an old sensor lock. I did like the software interface but Paypal confirmed me, so I shouldn't need to give you my personal information to pay for the software. No shipping means I am not giving you my phone number and address, etc. Sorry too many questionable things going on for a screen lock... rule is KISS and since this programmer isn't doing that then dump it off my device is my rule.
Neo_ said:
I have a different issue, when phone is not locked and I have an incoming phone call, pocket shield kicks in and shows me "lock screen" where I have to slide to unlock the device and only then I get the standard "Incoming call" screen...
v2.1.0.1
Click to expand...
Click to collapse
version 2.1.0.4 is out and is supposed to fix that problem..
I ran the site and its fine why do you say its a phishing site?
Hey guys
I just flashed to Cognition 3.04 and im loving it
after customizing my homescreen and stuff i got through the day happily (was worried i screwed up somewhere)
everything was good but today my dialer stopped working
i dont exactly remember when it started, but what happens is the call goes through, then my phone vibrates a few times and the dialer closes
afterwards, i get the popup saying Auto-update of Time and Date
I have no problems receiving calls, and my calls do go through (dialed to other people but it seems like the dialer closes after a few seconds)
I`ve noticed that 3g turns off as well :S
Is there an app I can use to figure out whats causing the crashes + any suggestions or solutions?
thanks in advance for any help
nevermind, sorry D: fixed it by turning off call status tones
Hi Guys!
I got a Galaxy S I9000B to replace my Galaxy Ace. As soon as I got it I flashed it with the latest CM7 nightly. I know there is CM9 and 10 for this phone but I had CM7 also on my ACE and I definitely love this rom and GB.
So far everything is great, this an old but really good piece of phone.
Anyways, I noticed something that on my ACE with CM7 didn't happen.
Everytime I have my phone locked (not using it) and receive a SMS text, besides notificating me with the ringtone and vibrate, the softkeys turns on and keep that way until I press the home button. I didn't wait much than 4 or 5 minutes, it might be some kind of notification that this CM7 has for the I9000B, and it might turn off if I wait more but I didn't try that yet. Also it might be a bug, I don't know.
The question is, do you guys know if this is normal ? It it does, do you know if there is an option to turn this option off or at least configure the time the softkeys are turned on ?
Thanks!
It is perfectly normal for your phone to do this:
The Galaxy S lacks a notification LED so the softkey LEDs are used to show unread messages or other notification.
Since I've never used CM7 I can't tell you if there is any option to change the duration, maybe someone else knows more about that.
Hackubi said:
It is perfectly normal for your phone to do this:
The Galaxy S lacks a notification LED so the softkey LEDs are used to show unread messages or other notification.
Since I've never used CM7 I can't tell you if there is any option to change the duration, maybe someone else knows more about that.
Click to expand...
Click to collapse
Thanks dude! I was hoping to be normal since I didn't want bugs hehe.
I was kind of surprising since I have never experienced this behavior with my previous Galaxy ACE (which don't have any notification led either).
If anyone owns CM7 with this phone I would really appreciate if I can get some advise on this. Is there anyway to configure the time out for it or to disable it ? I have just received a text message and let the phone alone without touching the home button for 17 minutes and the lights were still there
Thanks!
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)