Database Info

Terrible Search Button Bug

Hello,
I have been experiencing a bug where the phone acts as if there has been a long press of the search button (and the appropriate dialog comes up) when I have not touched the search button at all! (I am not pressing it by accident, it will do this while sitting on a table untouched). When it happens, the search button is not lit up (as if it were pressed), and none of the other buttons can be pressed, nor can anything on the screen, other than responding to the dialog. This can last two to four seconds (it's REALLY annoying). What's worse is that this can happen up to once a minute sometimes!
I've discovered that this happens only when I have 3g data turned on. When data is off, or when on wifi only, it does not occur.
Is anyone else having this problem, and (hopefully) has found a fix? I did do a search (both on Google and in here). I discovered a Google forum where people talk about experiencing the problem (a Google employee chimes in with questions) but no solution as of yet. I was hoping to find something about this in Xda, but as stated, couldn't find anything Though this person may be talking about the same problem:
http://forum.xda-developers.com/showthread.php?t=1069765
Here is the link for the Google forum:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Since it only happens when 3g data is turned on, could it be my radio image? Or something else? Any help or thoughts would be greatly appreciated! My current running specs below:
Nexus S
Android Version 2.3.3
Baseband version NO DGSXKD1
Kernel Version 2.6.35.7-g1 d030a7 [email protected] #1
Mod Version Cyanogenmod-7.0.3-NS
Build Number GRI40
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Rooted, bootloader unlocked

I was about to post this exact thread! I am having the same issue with my NS i9020a running stock unrooted 2.3.4. I to have noticed a link between data connection type and the issue occuring. One theory i read said that static charge may be to blame?... but that didn't seem right to me....
Anyway... I would also love some more info on this subject of anyone has any input. I bought my phone off ebay less than a week ago, and if the issue is hardware i am going to have to file a claim with paypal...
Sent from my Nexus S using Tapatalk

This is exactly what I posted in a separate thread. However, I'm not sure about the 2G / 3G changing.
I'll experiment.
Which radio are you using - seems like this was at least temporarily related to my switch to KD1 ?
Sent from my Nexus S using XDA Premium App

I reflashed radio KB3 and problem , at least for now is not happening. It was almost making the phone unusable this am earlier before changing radio
??!
Sent from my Nexus S using XDA Premium App

How can I find what radio I am using? Also, How long have the two of you had your devices? Is this issue something that manifested after you changed something on your phone (thus indicating it is not hardware related) or has it always been there? Thx, and i hope we can get this sorted out.
Cheers

Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App

jcrompton said:
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Baseband Version
NO DGSXXKD1
Kernel version
2.6.35.7-ge382d80
[email protected] #1
Build number
GRJ22
Please update as to whether the radio change is a permanent fix. Thx.
Cheers
Edit: I am assuming that this (NO DGSXXKD1) is the KD1 radio that you switched to and are theorizing may be the culprit...it is also something that all three of our devices have in common. I am eager to see if changing the radio permanently fixes your issue.

I'm on a Telus 9020a radio KB3 and i have the same problem.

Not sure at this point what the deal is! But changing from the upgraded radio KD1 back to KB3 has up to this point solved the issue. Maybe six or seven hours without the phantom search firing.
????
Sent from my Nexus S using XDA Premium App

Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S

Matridom said:
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Click to expand...
Click to collapse
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk

Hey guys, got the Sprint Nexus S 4g just this last Friday. Phantom search button presses and long presses started up soon after. Still going on now. Have not been able to narrow down culprit as far as 3G/4G/Wifi go. Running completely stock everything:
Android 2.3.4
Baseband D720SPRKD8
Kernel 2.6.35.7ge382d80 [email protected] #1
Build Number GRJ22
Just thought I'd add my stat to the growing list.

Sophos1 said:
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm on my phone so it's as little hard to link. In the general section there is a thread to a stock nandroid backup with the kb3 modem.
Sent from my Nexus S

I've now been about 9 or 10 hours after switching back to KB3 - no more issues yet! Pretty strange huh?
Sent from my Nexus S using XDA Premium App

Finally got my device rooted and switch to the KB3 radio.... it's has been a few hours and I have yet to experience the search button bug. I'm crossing my fingers that you found the solution! Thx.
Sent from my Nexus S using Tapatalk

Ok. So it's now been almost 24 hours. No repetitive firing of the search button on my Nexus S since flashing back to the KB3 radio.
Beware anyone experiencing this should not flash to the KD1 radio. I have a 9020a device. I assume it is Canadian since it had ATT 3G bands prior to any mention of ATT devices.
I think they are all a bit different when it comes to hardware which baffles more when I read on a Google forum post about a T-Mobile device that was stock Ann's doing this.
Sent from my Nexus S using XDA Premium App

Where to dowload KB3 radio image? (And advice)
Hey jrcompton,
Wow, that's great news! I tried a bunch of things, including going back to stock 2.3.3 via ROM manager (am now on 2.3.4, as I was prompted almost immediately for an OTA upgrade), and the bug still persists. It seemed after returning to stock that the issue didn't present itself until after installing certain apps (Dialer 1, Handcent, Extended Controls) but after removing them, am still seeing the bug. Was thinking that maybe it was these apps and uninstalling still let some trace and another factory reset might be necessary, but your results give me hope! As it is, on mobile data the bug can present itself several times in a minute! (Making the phone almost unusable).
All that being said, any chance you could share where I could download the KB3 radio? I did search and was only able to find a thread with mostly Tmobile users, and was thinking that the radio in that thread might not be the right one. I'm on Bell, so sounds like the radio that you're using would be right for me (since your phone uses AT&T bands).
Also, never flashed just a radio before, and am a little nervous. I know that there are a ton of threads with instructions, but I hope it's ok if I ask a couple questions. I'm assuming that I download the image, and put it in my ANDROID-SDK-TOOLS directory, then just (in command prompt from that same directory) type "fastboot flash radio *********.img (with the phone in bootloader, and connected via usb). And that I should NOT disconnect, power down, touch, or even look at phone during process, and make sure that PC doesn't power down, reboot, etc. If all of that is correct, do I need to wipe/factory reset or anything else beforehand or afterwards?
Thanks so much in advance, and so glad that you've at least had 24 hours bug free!
If this works for me as well, will post in the Google help forum thread as well.

I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk

If this worked for you guys then that's great, but do you have any suggestions for a NS4G user? I realize we don't have our own subforum but up until that happens, we have to have our questions fielded here. I'm still getting the search button going nuts on me issue. have tried data off/only wifi and still doing it. Wondering if I just got a defective unit...

Sophos1 said:
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey Sophos1 (or anyone else who might know),
My Nexus is now running the following:
Android Version: 2.3.4
Baseband Version: NO DGSXXKD1
Kernel Version: 2.6.35.7-ge382d80 [email protected] #1
Build number: GRJ22
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Would the KB3 radio that you downloaded for your phone work for mine? Also, just for confirmation, will I be ok following the steps that I listed above? Lastly, what's the worst that can happen if I flash the incorrect radio? Would I still have the opportunity to flash the correct radio (or reflash stock including the correct radio) via fastboot?
Thanks so much guys!

So when do u think Google Will Fix the Nexus S i9020A

Some ppl here don't Even know how To root. I myself know but those who updated OTA and aren't Techies are stuck... think Google should Seriously give us an ETA ... =\
Sent from my Nexus One using xda premium

The major problem of the i9020A is the capacitative search button firing on its own. They tried to fix it, but:
with GRK39C
wireless tether broke
search button bug still present
with GRK39F
wireless tether broke still (for me and others on AT&T). There are people on Bell/Rogers reporting it works again.
search button bug still present
The search button bug is present in low 3G areas and I can repeat the bug at will at a couple locations.
I'm fully aware of how to root/unlock flash ROMs, etc but I made a decision that this particular device would stay completely stock so I could have a frame of reference for my other phones.
Google didn't sell many Nexus phones and they are currently doing what they have done on several other projects in leave stuff broke while they attend to the next greatest thing (ICS & Honeycomb/tablets). As for a guess about when they fix this, perhaps Q1 2012 when the NS gets OTA Ice Cream Sandwich.

Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium

slimdizzy said:
Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
same here.

On Rogers had mine since it became available in April. Also never had the search problem and 39f working fine.

[Q] Radio issues with Nexus S, Hardware problem?

Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks

Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium

[email protected] said:
Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Anyway, the standard radio the i9020a comes with is the UCKF1 or KB3 as I have heard. http://forum.xda-developers.com/showthread.php?t=1116884 is where you will find the radios. Just flash the correct one. How you will know whats the correct one is it will be stated after the phone model. for example I9020AUCKF1 the A after I9020 is for the carrier ATT and after the thats the radio it came with. just reflash the correct radio through CWM and you should be ok. If not PM and I will help you further

heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
Flashing I9023 radio on I9020 will brick the phone as it may not even boot into recovery, fastboot may not work too. Just a word of caution.
Sent from my Nexus S using xda premium

Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App

immolo said:
Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What the next step would be is to try a new sim card. Go to your carrier and ask for a new one. If same results then its the phone and I'll assist you more.
Don't forget the thanks button.
Sent from my Nexus S using xda premium

Managed to borrow someones sim card at work today and it was the same result so it does seem to be a hardware problem now.
Sent from my GT-I9100 using XDA App

Yes. That would seem to me like the problem. I'm sure you restored your phone and completely wiped the SD? Also did you try pulling out the battery while the phone was on wait 30 seconds try turning the phone with out the battery then put the battery back in and turn it on? I'm sure you have done that you seem like a decently tech savvy fellow.
I've called Samsung before and I hate to say it but their repair policy is horrendous. You'll need another phone cause you'll be without yours for 2-4 weeks. They want to send "you your original phone back." Even their battery exchange is the same. You send your bad battery to them. They receive it process it then send you a new one. Motorola and apple have their repair department to be easy and quick which is what the consumer wants. More so apple cause you can go right to the local store and get a new one in 10 minutes. Motorola takes 2 days. Better than Samsung still.
Thats it for my rant! Just wanted to give you a heads up of what you will hear. Hope it all works out.
Sent from my Nexus S using xda premium

heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.

thedudejdog said:
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.
Click to expand...
Click to collapse
Well I dont think some one is that dumb to flash a CDMA for a GSM......if you are, you should stick to the iphone

Well it looks like I'm taking a trip to a service centre today let's hope it doesn't cost me too much to repair.
Sent from my GT-I9100 using XDA App

I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older

d128b said:
I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older
Click to expand...
Click to collapse
I tried that last flashing the xxka3 rom with no luck but let me know if you get any better luck then me.
Sent from my GT-I9100 using XDA App

Did you have any luck with Odin? I'm currently waiting for Samsung to diagnosis my problem so it would be nice to know at least one of us fixed this with software.
Sent from my GT-I9100 using XDA App

immolo said:
Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks
Click to expand...
Click to collapse
I've had a similar issue in the past. Restoring my EFS made it work again.
But before that issue, I also had another problem where no amount of radio flashing and EFS fiddling would fix it. Sent it to Samsung and it came back with a form with a hand written note saying "BGA failure".
So I imagine this problem is more common than it might seem. *shrugs*

Restoring the EFS would have been one of my first moves but I was given the phone in this state with no backups made.
Just crossing my fingers that Samsung doesn't charge me a king's ransom to repair it.
Sent from my GT-I9100 using XDA App

[Q] does anyone have rebooting issues?

Hey guys, I've had my HTC One S for T-Mobile and ive had it for about 1 week and it has rebooted on me twice so far. not sure why. the first time it was in my pocket and i heard the T-Mobile boot up animation sound go off in my pocket and pulled it out my phone to see it was just booting up for some reason. then today i was going to look at my friendstream widget (on my home screen) and my phone locked up for a second and then rebooted itself. i'm not happy about it since i once owned a g2x which rebooted like crazy. i'm hoping it stops randomly doing this crap but i reported it to HTC since it gave me the option once it rebooted. my HTC one s is rooted with the stock rom with bloatware removed and carry IQ removed. i just wanted to see if i'm the only one having this issue.

It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?

coronangel said:
It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?
Click to expand...
Click to collapse
not sure why it does this. i just wanted to make sure i wasnt the only one having this issue. but i do hope its a software issue. i keep reporting it to htc when it ask me to send them the error or whatever it says. maybe htc will fix it

I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA

Habarug said:
I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
i dont think there is an update for the tmobile htc one s.

Two days since I bought it and already rebooted two times when exiting the mail client while network was switching from H to 3G. I upgraded it to the latest firmware OTA just after putting the SIM card into.

My son had a problem with random reboots. After enabling Best Wifi Performance in Wifi, advanced settings, they went away. This is on a TMOUS version. Could be totally unrelated to your issue, but worth a try. I've noticed that the wifi has some weirdness to it, like hanging on to a connection long after it's out of range. I hope there is a software update soon.
Sent from my HTC VLE_U

well i hope htc can fix this issue. it hasnt happened again yet. i also have the tmobile htc one s.

s10shane said:
i dont think there is an update for the tmobile htc one s.
Click to expand...
Click to collapse
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA

Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Mine is also on 1.78 but had 2 reboots.

Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
yeah i guess here in the US we havent got an ota update that i know of. i kept checking for updates but it said my one s is up to date.

Another reboot this morning. This time I received a txt thru Facebook Messenger. I saw it on my desktop and ear, exactly at the same time, the HTC One S rebooting. This might be app related this time.
My One S specs:
- EU edition
- Stock ROM, 1.78 OTA
- Wifi disabled

Yes my H1S reboots about 3 times a week, or the "Loading ..." window is seens 3 or 4 times a week as well.

one more time... I'm gonna consider switching to another ROM in a very near future.

rebooting on 1.78 stock and other custom roms too
Hi guys, I had this issue with stock rom on 1.78 and previous too, so it is probably a radio issue. If I am connected to my wifi network at home, then I go out, the phone switches to hsdpa (as it should) and then I come back home,the reconnection to the wifi network causes the phone to reboot.
I had this issue on all roms I used, both stock and trickdroid 3.1 / 4.3.
My wifi direct is already disabled, my location is Italy. I have seen also that people on the US T-mobile support webpage are complaining about something very similar, wifi related.
Thanks

I'm on tmous and have had two of these reboots since I got the phone on US release day.
As others have said, mine have only happened when I'm on the very edge of my WiFi coverage. It's like the phone can't decide which network to grab on to and freaks out. I don't have the issue when it's just normally switching from WiFi to data like when I go out and then come home. It only seems to happen when I'm right on the edge of WiFi for a few minutes.
Not a huge deal, since its only happened a couple of times. If I remember when I'm off this week, i'll try to get a logcat because I should be able to reproduce it at the edge of my back yard

that would be great, as it sounds like it is the same issue. I always found tricky to save logcats due to amount of information in them and spotting the exact reason for crashing.

(Ville C2) Possible data connection issues

Hi All...
Previously, I'm using SGS3 before i gave it to my brother and using HTC One S C2 instead.
Since the very beginning, I'm having an issue with my data connection and it is very very very annoying till i felt paranoid whenever I'm browsing the net using my phone, scared that it will disconnected anytime randomly which is ALWAYS happened.
Sysmptoms:
When i received SMS, it will disconnected.
When it is idle for quite some time, it will stuck at 3G icon and disconnected eventually before reconnecting.
Sometimes, after disconnected, my internet won't work even though i have 3G icon showing and even H icon sometimes.
None of it happened when i'm using SGS3 so i know for sure it is not my SIM nor my provider issue. IT IS the phone but i don't think it is the hardware issue based on the symptoms.
I have done many things, i have revert back to stock, run back ICS RUU for my CID, supercid my phone, update the firmware, s-off it, s-on it back, just name it, i have done everything for few weeks and the issues still haunting me.
I have tried searching on the net but couldn't find anything related to ville c2 though i found a lot of people with quite similar problems (though not 100% same as mine) but not from someone using C2 and most of their fixes is changing some parameters in build.prop which doesn't fix anything for me.
So, i checked my radio catlog and found some interesting logs in there. It seems that my phone keeps doing teardown request which renew my connections. And i know it is related to the stale time of my connections.
EDIT: It seems like the stale time cannot be set using sysctl.conf, now i'm trying another method and ready to waste another more time to figure out why the heck these happened to me. Maybe a combo of this device + my carrier or what. **SIGH**
Anyone who have same issue or have an idea what else can be done to ELIMINATE these issue, please don't hesitate to share it.

Just an update to my issue.
So i have flashed the latest indian cid 38 OTA firmware into my phone under desperation and disappointments. But to my surprise, it is way better than when im on firmware for cid 44 which is supposed to be my phone's cid. Its now has been more than 5 days and i had the previously mentioned issues only ONCE.
Yes sometimes data suddenly slows down or sometimes "frozen" and stuck at 3G and sometimes suddenly goes to E before up to H again (in the middle of browsing or downloading) but the original super annoying issues of disconnections especially when sms coming is GONE.
Wth htc??? Grrrr.....
Sent from my HTC Z560e using xda app-developers app

feed3 said:
Just an update to my issue.
So i have flashed the latest indian cid 38 OTA firmware into my phone under desperation and disappointments. But to my surprise, it is way better than when im on firmware for cid 44 which is supposed to be my phone's cid. Its now has been more than 5 days and i had the previously mentioned issues only ONCE.
Yes sometimes data suddenly slows down or sometimes "frozen" and stuck at 3G and sometimes suddenly goes to E before up to H again (in the middle of browsing or downloading) but the original super annoying issues of disconnections especially when sms coming is GONE.
Wth htc??? Grrrr.....
Sent from my HTC Z560e using xda app-developers app
Click to expand...
Click to collapse
Try applying the build.prop fix for "Fast data" listed in the general forum. A number of folks with the exact problem you are describing are reporting resolution.
It appears it might be an issue with fast dormancy.

I believe I have the same phone carrier combo as you. I do not however have your problems. Where do you stay? East Malaysia?

wognwarren said:
I believe I have the same phone carrier combo as you. I do not however have your problems. Where do you stay? East Malaysia?
Click to expand...
Click to collapse
Sarawak and currently im using celcom, which i never had those issue when im using my SGS3.
Sent from my HTC One S using xda app-developers app

feed3 said:
Sarawak and currently im using celcom, which i never had those issue when im using my SGS3.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
That I'm not sure. I thought you're using DiGi since your picture has DiGi's logo in it.