cerialphreak
Members-
Content Count
25 -
Joined
-
Last visited
Community Reputation
17 GoodRecent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Certain keys not working initially? [fixed bug in old ROM]
cerialphreak replied to cerialphreak's topic in Support
You the real MVP! -
Certain keys not working initially? [fixed bug in old ROM]
cerialphreak replied to cerialphreak's topic in Support
This issue appears to be resolved with the newest OTA. -
Certain keys not working initially? [fixed bug in old ROM]
cerialphreak replied to cerialphreak's topic in Support
Great news! Thanks for your effort! -
Certain keys not working initially? [fixed bug in old ROM]
cerialphreak replied to cerialphreak's topic in Support
On mine it is not limited to immediately after a reboot. Seems to happen randomly throughout the day. My pin doesnt have those characters, so this would seems to be a different issue (or at least different behavior). -
I'm curious to see if anyone else is having this issue: when first opening the phone some keys wont type anything until another key is pressed. This seems to happen mostly to Y and H (qwerty varient) which is getting to be seriously irritating considering a lot of text messages start with "yes" or "hi." I've seen the repeating key issue as well, but only once.
-
Apart from having phone specific cards, sprint also has some "universal" cards. I would suggest going to the store and ask the reps to set you up. When I had to get my old Essential PH1 activated they tried every card in the store before just pulling one out of a display phone.
-
End of production for TCL-made BlackBerry phones
cerialphreak replied to Rob. S.'s topic in General Discussion
Bummer. If they were rootable and got updated past oreo I would probably still be using my Key2. Pour one out... -
Good to know it's not just this device (or t-mobile). Based on what I found on the droid wiki, this can be expected behavior on some aosp roms.
-
This is incorrect. I am also on T-mob and posted my findings in the network compatibility thread.
-
I ended up buying sequestris' pro 1 who reported the trouble on T-Mobile. I was able to get it running by manually adding the APN posted on T-mobile's site. So far I have only seen it attach to bands 2 and 4, and the signal meter on the status bar says "4G" instead of "LTE." From what i can find online it could be using the old 4G service since bands 2 and 4 are also used for that, or it could be the rom simply calling LTE 4G which is still technically correct (apparently some asop based roms do this). I can't say for certain based on speed since the two areas I've had the phone in didn't get
-
Just a fun FYI about sprint: they have different sim cards for different phones. Even if the sim size is the same you may not be able to simply swap the card into a new device, so using a mule device might not be an option. Source: former sprint customer.
-
Yesterday I had sent a support inquiry to Fxtec asking about transfer of warranty. Here is their response: Thanks for your message. Yes, the warranty would still be valid if you buy the device from someone else. Feel free to let us know if there's anything else we can help you with. Kind regards, F(x)tec Support
-
Does anyone know if the warranty transfers if you purchase the phone second hand (assuming there is warranty left)? EDIT: Here is Fxtec support's response: Thanks for your message. Yes, the warranty would still be valid if you buy the device from someone else. Feel free to let us know if there's anything else we can help you with. Kind regards, F(x)tec Support
-
Thanks for the write up!
-
Discussion and testing on features and known&potential issues
cerialphreak replied to rejujacob's topic in Bug Reports
If you have a chance could you switch the Bluetooth profile to AAC in developer options and try connecting to the Sonys again? The specs on Sonys website say they support that codec and I'm curious to see if the issue is limited to aptx.