Hey -
I've been having a problem and wondering where I should go from here...
It seems that I can use gfree to SuperCID and even SIM Unlock my device. The problem I have is when I try to set s-off. There is no problem with s-on.
If the secu_flag is set to 0, the problem that I'm seeing (regardless of ROM used):
The first call that I let timeout and go to voicemail after booting up
causes the rild to crash and relaunch. After rild relaunches, there are no additional problems...
Steps that cause error:
1) Reboot phone
2) Place phone on lock screen
3) From another phone, dial your cell phone
4) Let the call go to voicemail
5) RILD Crashes:
* When the 'missed call' notification appears in the bar, and
device returns to the lock screen, the upper right text showing the
network changes from 'T-Mobile' to '(No Service)' then back to
'T-Mobile' all within about 5-10 seconds...
* The antenna indicator in the notification bar will have an 'x'
in it, then return to it's previous bar state. In addition, any cell
data icon (E,3G,H) will disappear and re-appear. (in that 5-10 second
window mentioned above).
I've been asking on IRC. Guhl and I have been looking into this, but aren't sure what the problem is.
Am I the only one experiencing the problem? Anyone have any ideas on how to fix or where to look?
Related
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
seraphic8x said:
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
Click to expand...
Click to collapse
Did you try a hard reset?
Hello everyone,
I just bought my ATT tilt 2 and I have a few issues that I would like to address. If you guys can help me address them it would be greatly appreciated.
(1) When I get a call and message at the same time, my phone doesn't stop vibrating even when I am in a call and the other end can hear a buzzing noise.
(2) In my message tab, I have a '1' icon showing that i have a new message but I have no new message. I even deleted all the messages and still it does not go away. Therefore TouchFLO is also showing me '1' new message all the time.
(3) In my previous phone (omnia), I could hit any of the front hardward key to light up the phone then I could unlock it. but that feature does not seem to work in this phone, I have to everytime hit the power key to go in and out, therefore I find no use for the lock feature. I changed the setting for it to never go on standby but then the screen always on (low visibility) and that would probably use up alot of battery.
Any fixes for these problem?
I do not mind changing ROMs but I have no idea which ones are stable and how to go about changing them. I can look up on how to change them but I need to know what people are happy with. I do not want to keep changing ROMs.
Thanks Alot for your help
Have to push power button to wake up device
I have a TILT2 and it sucks to have to push the power button to wake it up. Does anyone know how to modify this?
I would like to push one of the front buttons to wake it up as they are more accessible.
Thanks.
Number 1 is weird. Maybe try a hard reset.
Number 2: Go to Start>Settings>Today do to "Items" tab. Uncheck TouchFlo3D, and check Messaging. Hit OK, and go back to the Today screen. There should be some stupid welcome message from Microsoft in the text messages (for some reason doesn't show in TF3D). Delete it, and you can go back into the Settings and turn TF3D back on. The "1" message icon should be gone
I had the same problem, and this worked for me.
number three:
Try this link from XDA:
http://forum.xda-developers.com/showthread.php?t=578061&highlight=wake+device+button
If you want to wake up TP2 by any hardware keys, please try: HKEY_LOCAL_MACHINE\HARDWARE\OEM\KEYBD "KeyLock" = 0 (default is 1) then Reset..
Hi,
I've got the latest FW and am running on DooMLoRD's kernel #8 (now on #9), min/max 256/1209MHz and everything was fine until a couple of days ago when some random Force closes started appearing, and today I experienced SIM lock skips. By that I mean that when my phone boots, it shows SIM lock screen, but after a few seconds it continues to main screen without me entering the code. This second thing started happening after I've installed WidgetLock Lockscreen.
The phone also didn't allow me to connect to my operator. It showed me a toast message Your SIM card can't connect to this operator, or something along that line.
Also, some system apps started FCing, and when I was receiving a call, I saw only the notification bar and black screen, thus could not answer. My phone usually vibrates for a few seconds, then starts ringing, and a bit after that shows the screen with who's calling and the answer/reject slide bar (this whole action is way too slow :/ ).
I went into recovery mode and restored one of the backups, then turned on my phone and everything was alright. After that I restored the newest backup from today and now everything seems to be in its place.
Any ideas what might have been the problem? The call screen delay is still there (it show up after 10 seconds of ringing + a second or two to be able to answer). Is that normal? I also noticed that with WL Locksreen enabled I have to wait SEVENTEEN seconds to be able to see the call screen and answer the call.
Hi,
yesterday I've flashed my desire (bravo) with IC 1.1.4.
Everything went fine, system is running, but I've encountered few strange issues and couldn't find anything like that on google
1. When turning off Flight mode phone won't ask for the PIN code and will not connect to the network - had to do a restart of the phone
2. When setting lockscreen to pattern I will loose the lockscreen - will prompt for the pattern and then immediately show home screen
3. When having code as protection I will have the lockscreen with the buttons, but phone is waking up every 1-2 minutes for no obvious reason after several hours of stand by (only way how to prevent this was reboot)
Any ideas why/how to solve those issues?
(Unfortunately I'm not able post directly to http://forum.xda-developers.com/showthread.php?t=1016940 )
I have a SGN2, unrooted. It runs Android version is 4.1.2. I use a utility to toggle on/off the lock screen, "SwitchPro Widget". My lock mode is "Pattern Lock".
SwitchPro works perfectly in toggling many of the state variables. I notice a "bug", but I don't think it is attributed to SwitchPro - I think it might be of Android.
Situation where things work properly:
Assume that I have the lock screen toggled off (no security set). Occasionally I get a notification, for which I can slide open the Notification window for a listing of all current notification. If I close the listing, without opening any individual notification message, then the lock screen remains toggled off. Good, no change as expected.
Situation where things mysteriously change:
Assume that I have the lock screen toggled off (no security set). Occasionally I get a notification, for which I can slide open the Notification window for a listing of all current notification. If I select an individual notification message from the list, then the lock screen mysteriously toggles on, and demands me to enter my unlock pattern code, before viewing the individual notification. The is bad - what is causing the lock screen state to be toggle?
Has anyone else encountered this?
Any ideas on how this can be remedied?
You could try simply turning off the security in the android settings, instead of trying to use a widget to do it.
Most apps that claim they can turn off your lock settings, usually can't. Android won't let them do it permanently. If you reboot, you will need to re-run the app, but before you can do that, you'll need to enter the code.
You can however, simply go into the android settings and turn it off manually. Then it will be permanent until you go back and turn it on again.
Skeleton said:
I have a SGN2, unrooted. It runs Android version is 4.1.2. I use a utility to toggle on/off the lock screen, "SwitchPro Widget". My lock mode is "Pattern Lock".
SwitchPro works perfectly in toggling many of the state variables. I notice a "bug", but I don't think it is attributed to SwitchPro - I think it might be of Android.
Situation where things work properly:
Assume that I have the lock screen toggled off (no security set). Occasionally I get a notification, for which I can slide open the Notification window for a listing of all current notification. If I close the listing, without opening any individual notification message, then the lock screen remains toggled off. Good, no change as expected.
Situation where things mysteriously change:
Assume that I have the lock screen toggled off (no security set). Occasionally I get a notification, for which I can slide open the Notification window for a listing of all current notification. If I select an individual notification message from the list, then the lock screen mysteriously toggles on, and demands me to enter my unlock pattern code, before viewing the individual notification. The is bad - what is causing the lock screen state to be toggle?
Has anyone else encountered this?
Any ideas on how this can be remedied?
Click to expand...
Click to collapse
I have encountered this numerous times and it can be frustrating. If you are rooted, you can install Xposed Framework and install the Notification Direct Launcher module. This will prevent this from happening, works like a charm.
http://forum.xda-developers.com/showthread.php?t=2434164