Related
Hello,
I'm a GSII (Korea version) user,and now using CM9.
The reason why I bought Korea Version (though Im not in Korea) is that it has NFC module.As we all know ,NFC is really convenient ,especially for exchanging business card.But I can not find NFC in system setting,could you help me ?
Maybe CM9 doesnt support NFC ,I think,can anyone provide a NFC patch or a package for CM9?
Thanks.
1odd said:
Hello,
I'm a GSII (Korea version) user,and now using CM9.
The reason why I bought Korea Version (though Im not in Korea) is that it has NFC module.As we all know ,NFC is really convenient ,especially for exchanging business card.But I can not find NFC in system setting,could you help me ?
Maybe CM9 doesnt support NFC ,I think,can anyone provide a NFC patch or a package for CM9?
Thanks.
Click to expand...
Click to collapse
CM in general has issues with NFC on the GS2.
As far as I know, CM developers have the following hardware:
I9100 (no NFC)
I777 (NFC hardware, but was disabled in carrier firmware)
Last time they tried to get NFC working in CM7, bad things happened. With CM9 - don't even think about trying to start on something like this until kernel source is released. Even then, with no ICS-specific NFC libraries (until an I9100P, I777, or M250 leak shows up), it isn't likely to happen.
Speaking of that - have there been any ICS leaks for the Korean M250 series devices? Leaks/updates of Korean firmware tend to not show up here - but you're the most likely to receive an ICS update that includes NFC.
(Odd question - did you have Google Wallet on any of your Gingerbread firmwares?)
The basic problem is that there is one CM developer with NFC-capable hardware (atinm), and on that hardware, the carrier (AT&T) disabled NFC functionality. In addition, it seems like Samsung's NFC libraries don't play nice with AOSP-derived firmwares.
Entropy512 said:
CM in general has issues with NFC on the GS2.
As far as I know, CM developers have the following hardware:
I9100 (no NFC)
I777 (NFC hardware, but was disabled in carrier firmware)
Last time they tried to get NFC working in CM7, bad things happened. With CM9 - don't even think about trying to start on something like this until kernel source is released. Even then, with no ICS-specific NFC libraries (until an I9100P, I777, or M250 leak shows up), it isn't likely to happen.
Speaking of that - have there been any ICS leaks for the Korean M250 series devices? Leaks/updates of Korean firmware tend to not show up here - but you're the most likely to receive an ICS update that includes NFC.
(Odd question - did you have Google Wallet on any of your Gingerbread firmwares?)
The basic problem is that there is one CM developer with NFC-capable hardware (atinm), and on that hardware, the carrier (AT&T) disabled NFC functionality. In addition, it seems like Samsung's NFC libraries don't play nice with AOSP-derived firmwares.
Click to expand...
Click to collapse
Hi,Entropy512
I have just tried the NFC package of M250k(2.3.5),but FC.
There is no leak for M250s/k so far,and I am still waiting for samsung 's offical updates. I wonder whether can I copy the NFC firmware of M250 (when it's released one day)to CM9 so that the module could work,or there is something wrong with signatures?
As for me ,I don't have a Gwallet on GB,NFC is not available here for shopping ,but for checking the cards' information.I use it as a cards exchanger in business.
Could you tell me why AT&T disabled NFC functionality ,but as far as I know,NFC works well in Korea now?
And the Korea Version still has other BUGs,such as the sensors don't work and no DMB,but I don't know how to let the developers know them.Though I have started some topics in CM forum,it seems not to make a difference.
1odd said:
Hi,Entropy512
I have just tried the NFC package of M250k(2.3.5),but FC.
There is no leak for M250s/k so far,and I am still waiting for samsung 's offical updates. I wonder whether can I copy the NFC firmware of M250 (when it's released one day)to CM9 so that the module could work,or there is something wrong with signatures?
As for me ,I don't have a Gwallet on GB,NFC is not available here for shopping ,but for checking the cards' information.I use it as a cards exchanger in business.
Could you tell me why AT&T disabled NFC functionality ,but as far as I know,NFC works well in Korea now?
And the Korea Version still has other BUGs,such as the sensors don't work and no DMB,but I don't know how to let the developers know them.Though I have started some topics in CM forum,it seems not to make a difference.
Click to expand...
Click to collapse
I have the M250S (korean version from SK Telecom that has NFC and SIM), and I have NO issues whatsoever with the CM9 that's been released here on XDA. The ROM works insanely well, and I'm lovin' every minute of it.
I would really like to see some movement on the NFC front, I know that NFC works on AOSP roms for the Nexus S, just wish there was a way to make that work on the GS2.
Also, the AOSP versions for SGS2 Gingerbread releases were modifiable to include NFC by just installing the missing files that someone released here on the forums a few months back. I understand that the files are completely different from GB to ICS, but is there no way to compare the differences between the Nexus S NFC files and the SGS2 NFC files, and then update the Nexus S's NFC files to work for our GS2's? I REALLY want to make this work, but I don't have much knowledge on the subject.
If anyone is willing to work with me on this and teach me a little on the way, I would be more than happy to start working on this. As it is right now, I'm in Korea, and the trains and buses use NFC cards where you add cash to them and swipe them by the entrances/exits to ride the subways, so if I could get this working I would definitely be the cool kid in town (I'm on an Air Force base here until December)..
+1 to NFC
I've a I9100P (orange UK) that should have NFC but it is currently disabled as I'm using a ICS mod. I've tried using NFC enabler but it caused my system to hang on the install screen. NFC isn't vital to me but I would like to use it as the phone has it.
I guess I'm waiting for a ICS distribution to leak with NFC enabled.
Cheers
Nask
So in the span of an hour I had rooted and unrooted my phone. Did this for a couple reasons really. First being this is my first android phone and I wanted to experience the process. Second being I wanted to try the sixaxis controller apk.
I live in Canada and imported a phone via amazon.com purchase. I believe I got the Taiwan model as right out of the box it was defaulted to a chinese character setting. During my unroot process, I flash the UK base into it. This happened because of two things. One being I wasn't 100% sure I had the Taiwan model or not when I was selecting the rom to flash back to. And two, I was following the video in the rooting section which included resetting my flash count to zero and changing my phone from KOR to BTU.
Since then I've run some tests. Cell service is looking good, data is working. Only thing I noticed that I lost in the process was the language keyboard(canada) was available in the chinese stock rom, but I have to use the US one for this stock.
Is there anything I should be aware of? Should I not get too attached to this stock rom and try my best to flash back into the original?
Is there anything I should be aware of?
Click to expand...
Click to collapse
Nope. Rom's are completely interchangeable within the boundaries if the i9300/i9300T hardware.
You can even go as far as cherry-picking the System from one ROM, the CSC from another, the modem from yet another...
(Only within compatibility, Axxx and Bxxx ROM's are not compatible, Bxxx being newer)
Great, good to know. Thanks.
actually just found something, I can no longer access the menu button from within the wifi settings screen. As a result I can't select frequency band, etc.
It's possible that some ROM's dont include that feature. If it's on auto you should be fine anyway since it _should_ prefer the 5Ghz band over 2.4.
AOSP Roms don't have it either, no issue here =)
Hello people,
For the past few months I'm having this issue which I find extremely [email protected]!!
Every few minutes, my phones just loses internet connectivity - the 3g signal appears to be normal during all the time, thing is, whenever I try to use any internet application - it just hangs. and then, after a minute or so, connectivity is back(again, for a few minutes).
I have tried flashing so many versions of modems - some improved it a little but most of them didn't help at all, or even made it worse.
Hopefully someone could help me with that as I'm that close to give up on this and buy a new phone.
Thanks in advanced.
Nir.
Which firmware are you running on your phone? What modem do you have right now and where do you live? Do you have problems with all apps that use internet-connection? Do the problems dissapear when you use wifi?
Just some information would be usefull
Donnie Sins said:
Which firmware are you running on your phone? What modem do you have right now and where do you live? Do you have problems with all apps that use internet-connection? Do the problems dissapear when you use wifi?
Just some information would be usefull
Click to expand...
Click to collapse
Yop.. forgot to mention a 'few' things...
Model: GT-I9100
Rom: RootBox V3.8
Kernel: 3.0.31-CM-g7ce58e6
Baseband: I9100DXLPB
Android version: 4.2.2
I live in Israel, bought the phone in Thailand.
I tried flashing all available Israeli modems(from various cell phone providers) - none helped.
Problem disappear when I move to WiFi - as 3g connectivity moves to background...
Thanks.
I assume you've read the Rootbox threads to see if other people experience signalproblems?
Did you compare the connectivity with other roms? Stock-based roms for example...
Donnie Sins said:
I assume you've read the Rootbox threads to see if other people experience signalproblems?
Did you compare the connectivity with other roms? Stock-based roms for example...
Click to expand...
Click to collapse
I've been hovering the internet for weeks in search for a solution..
That's not a RootBox issue in particular as I tried using various roms...
niiiro said:
I've been hovering the internet for weeks in search for a solution..
That's not a RootBox issue in particular as I tried using various roms...
Click to expand...
Click to collapse
That seems quite weird.. The only thing I can come up with is 1) a hardware problem, or 2) you live in an area where the signal is crap
Hopefully someone else knows anything.. Good luck.
Donnie Sins said:
That seems quite weird.. The only thing I can come up with is 1) a hardware problem, or 2) you live in an area where the signal is crap
Hopefully someone else knows anything.. Good luck.
Click to expand...
Click to collapse
Neither of them thanks anyways.
Anyone else...?
If you've only tried flashing the modems bundled with stock roms from Israeli carriers, you haven't done nearly enough. There are literally dozens of modems available, you need to start flashing as many as you need to. This isn't going to fix itself magically.
MistahBungle said:
If you've only tried flashing the modems bundled with stock roms from Israeli carriers, you haven't done nearly enough. There are literally dozens of modems available, you need to start flashing as many as you need to. This isn't going to fix itself magically.
Click to expand...
Click to collapse
I haven't flashed only Israeli modems but others as well. I've tried around 20 so far...
Question is, which direction should I choose? should I look for Thai modems or IL?
That depends. I know Israeli carriers sold (still sell ?) the I9100T, are you sure you don't have one of these ? If that's the case, I'd be trying modems bundled with roms released by the Australian & NZ carriers which sold the I9100T (I have one), and yes, the Thai ones as well.
If you do have an I9100, then keep trying any/every modem you can get your hands on. If it's not a carrier-side issue, this is really all you can try, unless you want to start messing around with RIL's as well. I've not found any difference in connectivity doing this personally (tho many people have) but if you get to the point of trying every single modem & you're sure it isn't a carrier issue, you might as well try. But I would leave this till last given many people find their connectivity messed up even worse by flashing an incompatible RIL.
Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
mario24601 said:
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
Click to expand...
Click to collapse
My understanding was that the hardware is still present in the US version, but it was disabled for legal reasons. Could be wrong though.
msamuels0 said:
Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Click to expand...
Click to collapse
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Pakman123 said:
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Click to expand...
Click to collapse
Exactly what I was looking for, thanks!
We'll see how it goes!
msamuels0 said:
Exactly what I was looking for, thanks!
We'll see how it goes!
Click to expand...
Click to collapse
no problem good luck
Let us know if it works, I am curious.
DAVe3283 said:
Let us know if it works, I am curious.
Click to expand...
Click to collapse
Quick update...
I finally got a chance to mess with this over the weekend. There is not yet a Custom UK E5823 release for MM, so I tried copying the files from another MM non-us release, and it didn't appear to work. However, I did go and revert back to Lollipop with the latest available UK release, and can at least confirm that the fingerprint hardware is indeed present, as the fingerprint manager then showed up, and the sensor worked. I went back to the latest E5803 Custom US Marshmallow, and will wait until MM is available for UK, and try to copy those files and rebuild again then.
Interesting... that is good to know. It seems that we could buy the US version to get the warranty, then just flash an international firmware to unlock all the functionality. And hopefully down the road, do the mash-up firmware for the best of both worlds!
I'm just surprised they disabled the sensor in the US, especially with the sensor still present in the phone!
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Fantastic work!
Sent from my SM-G850M using Tapatalk
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
AnandRajaguru said:
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
Click to expand...
Click to collapse
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Woo! This makes my day!
runningwarrior08 said:
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Click to expand...
Click to collapse
Yeah, I noticed the signal meter reading lower than it should on the Nordic firmware on US T-Mobile. Getting 20Mbps on 4G with no bars is fine with me.
Amazing news for US version owners
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
You don't have volte though right?
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Sony phones have always reported lower signal than actually present. No idea why
Possible to revert back?
This is great news. Is it possible to revert back to make it report as the right model for warranty purposes?
Of corse, just flash back US firmaware and it'll be ok.
just flashed "customized uk" version and got my US z5c fingerprint reader up and running. wonder what, if any, issues might arise from running a firmware for a different model, e5823 vs. e5803.
this thing is nice, but man , it does get pretty hot in the back top center. yowza.
I use an ATT unlocked variant of s21 5G
1: It overheats excessively, you cant even game on it
2: When gaming, the touch sensitivity is very low despite turning on increased sensitivity in settings
Anyone know why or give a possible solution, my guess is because its still stuck on One Ui 3 and Android 11
habiodunz said:
I use an ATT unlocked variant of s21 5G
1: It overheats excessively, you cant even game on it
2: When gaming, the touch sensitivity is very low despite turning on increased sensitivity in settings
Anyone know why or give a possible solution, my guess is because its still stuck on One Ui 3 and Android 11
Click to expand...
Click to collapse
I can't say why with any certainty, but can say I would never want a carrier rom on my phone, I always switch to an 'open' version as it rids you of the carrier bloat and and restrictions etc they put in their roms.
Granted, that doesn't work for everyone as they are 'tied' to a specific carrier. So, if that's the case, I'd look for info about whatever that specific rom / carrier problems exist.
But, if you can go with any carrier you want, go with one like Mint Mobile, which allows volte, vowifi, and 'open' rom phones, like the S21. It's easy enough to find how to use Odin to flash an 'open' rom also.
One additional thing you would accomplish by doing the above; you'll discover if the issues you're experiencing are the fault of the current rom, or they are hardware related. Not sure how else you would test that hypothesis other than doing the exact above?
good luck
AsItLies said:
I can't say why with any certainty, but can say I would never want a carrier rom on my phone, I always switch to an 'open' version as it rids you of the carrier bloat and and restrictions etc they put in their roms.
Granted, that doesn't work for everyone as they are 'tied' to a specific carrier. So, if that's the case, I'd look for info about whatever that specific rom / carrier problems exist.
But, if you can go with any carrier you want, go with one like Mint Mobile, which allows volte, vowifi, and 'open' rom phones, like the S21. It's easy enough to find how to use Odin to flash an 'open' rom also.
One additional thing you would accomplish by doing the above; you'll discover if the issues you're experiencing are the fault of the current rom, or they are hardware related. Not sure how else you would test that hypothesis other than doing the exact above?
good luck
Click to expand...
Click to collapse
Thanks mate, started getting the files for a new ROM