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
Related
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 =)
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Googler_1976 said:
So what are the pros and cons.... I know about the partition. Are they any other issues with the conversion? If you came back from N4 what made you come back? Cos after the SD card, NFC and LTE fix what else was broken? Thanks in advance.
Click to expand...
Click to collapse
My main reason for doing the conversion was to get hybrid ROMs like Rootbox or PACman (which weren't available natively on LGOG at the time). To me, really the only pro is a larger selection of ROMs. This isn't necesarily a better selection, just bigger - it depends on what you are specifically looking for in a ROM as to whether this makes it worth it or not.
With the available fixes already posted, there really aren't any huge cons either - GPS works, camera works, you get full internal storage and external SD support. However, there were cases I ran across where I couldn't get certain fixes working with certain ROMs - things like touch key lights not working and the like. I'm sure they are fixable in these cases, it just takes someone smarter than me to figure out how.
I think the main reason the conversion is frowned upon is that there isn't a compelling, across-all-ROMs improvement or feature that would be available on a converted device that isn't available on the 'native' track. So why risk a brick monkeying with partition layouts and potentially dangerous N4 install scripts (apparently some of them flash using partition numbers rather than names, and this will kill ya dead - gotta read carefully. I never ran across one).
I had minimal issues when running converted ( I think I was running that way for 3 weeks or so maybe?? Can't remember). Most of the issues were things that were more annoyances, rather than real usage problems. However, as my main reason for converting was to get a hybrid ROM, once houstonn brought Rootbox to the LGOG natively, I decided to come back. I'm usually a little short on time, and it was getting difficult to keep up with all the LGOG threads, plus all the N4 ROM threads, plus figuring out how to fix the ROMs for use on the LGOG. It's easy here, a one stop shop for LGOG learning, if you will...
I suspect with the native 4.2.2 stuff running around here now, there will be a steady decrease in the amount of 'development' on conversion stuff - it seems quite a bit quieter now than it was a month or 2 ago. I'd rather stay where the action is, as that's usually where the little remaining issues get solved first.
FWIW, I had no issues either converting to, or back from, N4. The threads here do a good job of spelling out the process - it's just a matter of reading through them enough times to understand what is going on and what to expect at each step.
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Googler_1976 said:
Thanks for writing up your experience... The main reason I asked this question was... Some of the (if not all of them) AOSP Roms have major issues like if GPS works something else will be broken and if something else worksworks other is broken. But I did not see that in N4 conversion. (At least to my knowledge) I'm just talking about just pure aosp Roms. ..is this a trurt statement I'm making? Thanks in advance.
Click to expand...
Click to collapse
I can't say for certain - most of these 'tradeoff' issues, at least from what I've seen, seem to revolve around which modem you choose to run. I believe, at the moment the only 100% no issue setup is and ICS ROM with ICS modem. I believe these issues persist whether you are on N4 conversion or native LGOG setup - but I could be wrong here.
Here's the basic breakdown - somebody correct me if I'm wrong on these, I haven't run most of these setups personally:
If you run ICS modem on JB ROM, you get broken GPS.
If you run .33 N4 modem you get good GPS and Data speeds, but occasional data drops. Also, apparently you can't make outgoing calls in LTE coverage. You can fix the data connection by toggling airplane mode. This isn't a huge issue for most people, but is for me as I use Google voice and IM apps for messaging (rather than SMS) so if I don't notice the data drop and toggle, I'm missing messages.
If you run ATT JB modem on JB ROMs you get working GPS, decent data speed, and working LTE calling. All Outgoing calls drop to a background process after initiation, so if after hitting dial you need to interact with the call, you have to open the notification drawer and then click on the call to foreground it. Does not impact actual functioning of the call. Network name is reported as 'maritime' rather than AT&T.
I think there's another N4 modem that will work with LTE (.27 maybe - somebody jump in here) so that might be another option...I haven't tried it. there is one N4 modem that breaks LTE support.
I've been almost exclusively on houstonn's RootBox since coming back to native setup - so I may have missed issues with other ROMs - I do try to keep up with all the threads though. Hopefully someone else on one of the others can chime in with other issues, if there are any, that I missed. FWIW, I have never lost GPS on my device...I'm not sure why some have and some haven't...
http://forum.xda-developers.com/showthread.php?t=2270319
One stop shopping for all your radio needs.
Thanks again both of you... t I wanted to know why and I think I got what I was looking for.. Anyway, I guess I will stick with my rooted stock JB for now till some of these issues get resolved. Thanks again for all your time.
Okay, so, I've done a fair amount of reading and searching about modems and RILs, including other forums, but I've still yet to find the specific information I'm looking for. (Most of the stuff that I've found relates to the i9100.) So if I missed the relevant post, I apologize, please direct me there.
That said, here's the deal. I've got an i777, which I have unlocked and am currently using on T-Mobile. I've flashed the stable CM 10.1.3 (Android 4.2.2). Its baseband is UCLE5. It's running well. I have few complaints, except for occasional low signal.
I've already seen this thread, with the different modems available: http://forum.xda-developers.com/showthread.php?t=1336958
I lost the link, but I also found a thread, possibly on another forum, where a T-Mobile user reported better performance with baseband UCMD8. I'd like to try it. I think I can manage flashing it on my own via CWM.
However, I've read in a bunch of places that it's also important to have a RIL matching the baseband version. I found a thread that gives a terminal emulator command to find your current RIL version (getprop "gsm.version.ril-impl"), and mine is "Samsung RIL(IPC) v2.0", which is apparently from Gingerbread.
So, my question is this: Should I also change my RIL? If so, 1) where would I get the appropriate RIL for the i777 with CM10.1.3, and 2) how would I install it, preferably without performing another wipe, reset and ROM installation?
Thanks in advance for your help!
NightSteel said:
So, my question is this: Should I also change my RIL? If so, 1) where would I get the appropriate RIL for the i777 with CM10.1.3, and 2) how would I install it, preferably without performing another wipe, reset and ROM installation?
Click to expand...
Click to collapse
You have nothing to worry about - just flash the i777 modem you want via recovery; you don't have to wipe anything, it will work fine. I wouldn't worry too much about RIL; over the two years of changing modems back and forth I've never encountered any problems regarding RIL (except for some wakelocks, but that's more to do with bad/weak signal than anything else).
To be clear, I'd still be happy for input from anyone regarding the i777's RIL, but I did go ahead and flash UCMD8. I've already noticed something new; my phone now seems to drop from H+ to 3G fairly aggressively when I'm not actually using it, then go back to H+ when I do, where since flashing CM10.1.3, it previously connected only at H+ or E. I imagine this is a battery saving measure. I'll have to see how it behaves for a few days.
Thanks for your response SteveMurphy. By the way, what baseband/RIL version do you use, if I may ask?
NightSteel said:
To be clear, I'd still be happy for input from anyone regarding the i777's RIL, but I did go ahead and flash UCMD8. I've already noticed something new; my phone now seems to drop from H+ to 3G fairly aggressively when I'm not actually using it, then go back to H+ when I do, where since flashing CM10.1.3, it previously connected only at H+ or E. I imagine this is a battery saving measure. I'll have to see how it behaves for a few days.
Thanks for your response SteveMurphy. By the way, what baseband/RIL version do you use, if I may ask?
Click to expand...
Click to collapse
I'm on UCMD8,
The reason you're seeing 3G more often is because with the newer roms you have the ability to better control your network modes. For instance, if you want to use Edge you can manually switch to 2G mode. It's possible the older firmwares (GB, ICS...) had this option but I really can't remember.
Galaxy S Backdoor
So it seems my question about RILs was unintentionally timely, as Samsung's RIL for Galaxy S devices contains a backdoor that's been verified with proof of concept.
https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor
http://redmine.replicant.us/projects/replicant/wiki/SamsungGalaxyBackdoor
I'm not sure which version of Samsung's RIL they tested, or whether they tested the I777, but it seems most Galaxy phones are affected.
Hope someone gets to work on this soon.
NightSteel said:
So it seems my question about RILs was unintentionally timely[...]
Click to expand...
Click to collapse
Suspiciously timely, yes.
here's another take on the back-door claim:
http://arstechnica.com/security/201...-of-remote-backdoor-in-samsung-galaxy-phones/
-Cyril
edit: and this: http://www.xda-developers.com/andro...mctr=(not provided)&__utmv=-&__utmk=122317964
Might sound like a stupid question but ive read on a few different sites that you can install verizon roms to sprint phones (galaxy series in particular) and adjust the apn settings to get the signal working, anyone tried this? Development for the verizon g3 is picking up a little and id like to try and run cm11 but im not ballsy enough to risk it, has anyone tried it?
hoebag said:
Might sound like a stupid question but ive read on a few different sites that you can install verizon roms to sprint phones (galaxy series in particular) and adjust the apn settings to get the signal working, anyone tried this? Development for the verizon g3 is picking up a little and id like to try and run cm11 but im not ballsy enough to risk it, has anyone tried it?
Click to expand...
Click to collapse
I'd love to say yes but when the OP specifies the variant(s) the rom is intended for, I'd be willing to take their advice and refrain from flashing to a different device. A lot of the roms posted explicitly state not to try flash the rom on a different device.
I'd sit tight until sprint specific roms come, or even multi variant roms appear, which shouldnt be long..
I've read a million times that you shouldn't use roms for other variants. I wouldn't risk it.
Sent from my LGLS990 using XDA Free mobile app
Yea im definitly not going to try it, im curious if anyone has? And if its just an apn issue? Its tempting to flash cm11 just to check it out knowing it wont fully function, as long as it wont destroy my phone. Somone on here must have tried it and knows if it boots
From IRC, TMO is actually closer hardware wise the Verizon. Sprint (LS990) and TMO (D851) both use broadcom chips for bluetooth/wifi. The rest do not.
That's not to say flashing a D851 ROM will work, it wont because of vendor blobs and bump, but you might find it easier to use for a base (might).
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.