Hi all,
Quick PIN is the feature where you can enter your 4 digit PIN without having to press OK (this gets annoying when you are forced to PIN down and unlock every time you want to use the phone)
I know CM7 has Quick PIN, but unfortunately bluetooth doesn't work in the car.
Any other ROMs which have Quick PIN?
Thanks
any way to add Quick PIN to other ROMs? any apps, etc?
I've been searching for this as well. So far, CM7 is only ROM that actually works, other than leaked AT&T UCKJ2 and UCKJ4.
I decided to use UCKJ4 for now, until CM7 supports BT headsets. I will try out new Rogers stock (made by jordan) later, but previous rooted Rogers GB ROM wasn't working properly. I think it was working when I originally used Rogers stock (before the rooting & trying out the custom ROMs).
Related
Hey. I'm having some trouble using the firmware for this phone that is posted in the development section. I've tried a couple of different ones but each seems to have the same problem. Getting a GPS signal seems to be impossible, it just won't fix on anything. I checked some help threads and found you should use fasterfix, gpsopt and dial *#*#1472365#*#*. But gpsopt fails to load, fasterfix doesn't make a different and dialing the number brings up nothing.
But when i'm using stock firmware, after using gpsopt and dialing that number, i get a GPS fix within 5 seconds each time and it works great. But i'd much rarther use custom firmware if possible since it seems to be much more responsive than my older stock firmware.
Any ideas how i can get it working well? The one i'm using at the moment says it supports it
GPS is nor fully working on cm7. If you want GPS to work, use any froyo firmware.
Click the thanks button on my posts if I helped!
Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!
HugoS said:
Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!
Click to expand...
Click to collapse
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).
polobunny said:
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).
Click to expand...
Click to collapse
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?
HugoS said:
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?
Click to expand...
Click to collapse
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.
polobunny said:
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.
Click to expand...
Click to collapse
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.
HugoS said:
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.
Click to expand...
Click to collapse
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.
polobunny said:
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.
Click to expand...
Click to collapse
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.
HugoS said:
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.
Click to expand...
Click to collapse
You don't have a SIM? You should be able to set a PIN password on any working SIM as far as I know.
Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?
bigb78 said:
Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?
Click to expand...
Click to collapse
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.
jlokos said:
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.
Click to expand...
Click to collapse
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks
bigb78 said:
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks
Click to expand...
Click to collapse
I was using the Q2 with pattern lock. I now use the jawbone with PIN lock. Sorry for the confusion.
Thanks.
But... DAMN! LOL I can't figure out why this is happening. I will try Cyberon, but S Voice and Assistant failed for me.
http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)
bigb78 said:
http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)
Click to expand...
Click to collapse
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.
jlokos said:
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.
Click to expand...
Click to collapse
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)
bigb78 said:
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)
Click to expand...
Click to collapse
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.
jlokos said:
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.
Click to expand...
Click to collapse
Yep, I am watching the forum. Don't want to be the first one to try it, I don't yet have the skills to fix undocumented problems.
I think my problem though, is the Bluetooth security bypass. Not the Voice app..... but time will tell.
Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!
bigb78 said:
Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!
Click to expand...
Click to collapse
Try this link: http://forum.xda-developers.com/showthread.php?t=1896171
I recently bought a Galaxy S5 G900P tied to Sprint but for FreedomPop. It's not locked to any plan. Once I got it I rooted it and set up the Exodus ROM. I like it without all the bloatware. It works fine for most everything. But I can't get it to access Secret Codes.
I've research the Internet, even watched YouTube videos as someone goes through each number press and shows actually getting the results. I use the native dialer, do the exact same thing and all I get is if I want to add it to my contacts. Either there's some secret hidden button no one's talking about or my phone has a problem.
Please understand one other thing. I've worked with, programmed, tested, and built computers since the old 8086s, but I'm a total newbie when it comes to these tiny contraptions. I don't even know how to SMS or whatever that is so, please, be patient and kind.
Flash a stock based ROM, like MOAR. The creator of your ROM doesn't have the necessary apk to make the secret codes work. I believe the apk is something like HiddenMenu.apk.
The secret codes only work on stock based ROMs I believe.
Sent from my SM-G900P using Tapatalk
what he said. tw or custom roms based on stock will have hidden menu apk as a system app
ie: to increase your wifi power to 10 for better wifi reception you would pres *#0011# then hit the menu key (left of home button) and you'll see power save is on by default (power save is set to 7) you can click it and turn it off and exit and your wifi will pick up exceptionally better and it really dont hurt the battery. so TW based stock roms are the best IMO. Moars 7. is the best out there by a mile everything is unlocked and working every function the phone can do and moar. lol
Moar 7.0 doesnt have the usb menu enabled,but the rom is awesome.
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
zmauls said:
First, I don't know much about custom ROMs or root processes in general. I rooted the phone myself, and installed the recovery/flashed the ROMs, but my knowledge is one step above basic, if that.
A couple of weeks ago I stopped being able to send MMS. I simply dealt with it. I don't send a whole lot of pictures. I finally called Sprint yesterday to address the issue, and the wizard on the other side of the line did some sort of magical spell which caused (I think, could've been coincidence) my 3G connection to stop functioning as well after a few reboots.
This is a Samsung Galaxy S3 for the Sprint network. I am currently running CyanogenMod 11 (AV 4.4.4) and have ClockWorkMod installed as my recovery. Fixes I have tried so far include:
- Reflashing all my ROMs
- Updating CM11
- Flashing CM12.1 instead of CM11
- Multiple hard/soft reboots
- TouchWiz MMS Fix
- FreedomPop APN adjustment
Nothing has worked so far. I am at the point where I am about to just purchase a new phone. If it matters, the verdict on the phone with Sprint was to take it to a store, which I did, but when they crack open an AOSP it seems they have no idea what they're doing.
Please help.
Click to expand...
Click to collapse
This issue has been resolved. I flashed over a rooted stock MK3 ROM with a custom modem which allowed me to update profile and PRL. Thank you.
Great that you solved the problem.