Hey guys, haven't seen much discussion, or even any questions regarding signal strength in the new B35 update. So that's what this thread is for. Has anybody noticed any changes in either loss or gain of signal strength after the update? Can anybody confirm if the baseband changed or stayed the same? I know Oreo will bring us a new baseband maybe resulting in better signal but not guaranteed. I'm bypassing this update as of now because Oreo is just around the corner so I'd rather wait for that before I go and have to revert to stock and all of that. Just wondering if B35 brings any improvements to the signal strength.
brian117 said:
Hey guys, haven't seen much discussion, or even any questions regarding signal strength in the new B35 update. So that's what this thread is for. Has anybody noticed any changes in either loss or gain of signal strength after the update? Can anybody confirm if the baseband changed or stayed the same? I know Oreo will bring us a new baseband maybe resulting in better signal but not guaranteed. I'm bypassing this update as of now because Oreo is just around the corner so I'd rather wait for that before I go and have to revert to stock and all of that. Just wondering if B35 brings any improvements to the signal strength.
Click to expand...
Click to collapse
I can honestly say the refurb I just received from ZTE that is on B35 has horrible signal vs both of the other ones I have had. I'm fairly sure it's B35 and not the hardware, but I can't complete a download of B32 to downgrade. I tried the MM SD update to downgrade, but it fails. So I've spent a day and a half trying to download a file unsuccessfully in an area that has great coverage. Also, although my area is mostly band 12, I have noticed it is used far less. Mostly band 2 and 4 are used preferientially.
Edit: also, if anyone has issues unlocking BL from B35, you have to use the SD card updates' update.zip to roll back two (b32 and b19 from the axon 7 support page) and then you can use axon 7 tool. #profit
Related
Hi,
I currently use the latest OxygenOS and ak's 004 kernel. My sim card is EE which has the best range of channels. Although i've had my opt for over a month iv'e yet to switch from my old phone due to very poor reception - its half bars where my older phone has full bars, and no bars where my old phone has 2 bars.
Has anyone any confirmed tweaks or instructions to improve this that i can personally do?
I am guessing the best advice is to change ROM and kernel - Anyone in uk switched ROMS and found an improvement? However im a bit fed up wiping phone and reinstalling everything from backups (any ROM installations or updates cause many issues to me unless I flash full from scratch). I just follow and wait for a cm ROM (Developers doing a great job!). I believe exodus has nightlies which would make it easier to update but id read somewhere there was a virus in one of the builds and that theres some custom security regulated by the developer which is effectively classed as dangerous malware due to giving developer complete control, and prohibitive of being able to use certain software (apologies if its not exodus ROM).
I saw the issue exists in opo but you could use oppo 7 modem firmware to fix this. havent seen anything like this for op2. Im a regular visitor to the OPT forums, apologies if i have missed a thread or post if a solution is present.
Thanks
I have an Indian model and I'm in Arab, same problem -_-
Sent from my ONE A2003 using XDA Free mobile app
after alot of googling i found you can press *#*#4636#*#* and choose bands, apparently nobody here knows this. google said ee uses 38 and 42. switching to 42 was big improvement, before it was 900. theres a thread i think for opowhere you can install something to unlock all bands but havent looked into it in great detail, been sorting out my 4.4.2 tab which has a standyby of 11 days compared to op2's 2days
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
we're stuck on verizon's firmware. i use viper and the software is updated to the latest release, just not using the eu/intl firmware.
btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk
dottat said:
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.
camparks said:
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.
Click to expand...
Click to collapse
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.
dottat said:
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.
Click to expand...
Click to collapse
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!
camparks said:
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!
Click to expand...
Click to collapse
Hardware wise most are the same. And you are right about me recommending firmware that matches your carrier. That aside, my experience has been like this....
I have been asked a couple times to try to fully convert a phone from one carrier to another. On the 10, we know that unlocked<->verizon works and we thought it would since HTC gave them the same MID (different CIDs though). On the m9, I have attempted to fully convert a verizon m9 to an ATT model. The RUU flashes everything BUT tp and one or two other ones. It boots up fine (att death star and all)... but it will never boot to recovery and never load TWRP when flashed. There's something about the overall partition structure that makes it different.
On the rom/firmware front.... Verizon and HTC do very specific testing for firmware/OS releases. They do this not only to ensure optimal performance for the user, but also to make sure that the phone itself doesn't cause issues on the network itself. As the manager of an engineering team for a huge US based ISP, I can tell you that firmware of devices CAN and DOES impact the network stability from time to time. I'm not talking about capacity issues, I'm talking about your phone making a phone call and causing a network card back at the CO/Tower/ETC reset. It does happen.
Lastly, I measure things by what you gain. What would gain by flashing unlocked or EU firmware images onto a phone on the verizon network? An increase in number version? As much as I see people who change their aboot do so to avoid red text, it always surprised me to see a VZW phone with a third X.X.401.X number on their bootloader indicating non-vzw firmware. There's a new piece of fun around since the m9 and present on the 10. If you manage to get an aboot on your phone doesnt match your firmware and you reboot the phone you will be stuck in bootloader with no access to download/recovery and often OS. The only fix is to manually flash each firmware image / partition file by name manually and it must match the aboot for it to work. So that's another reason to not go and mix and match because to be honest... most people don't make it beyond the panic moment of that. That phone gets returned and added to the reasons verizon makes it more difficult going forward.
\
There's my 2 cents
This is a tough call but all things considered, I should really flash back to complete stock. It's definitely the 1st time I've gone without root.
I need a reliable phone right now. There's some great people trying to make the most out of this with the Eng kernel, but ultimately I running into problems (sometimes it'll run great for over a week but then the issues become apparent. )
That said, I'm told Ufirmware has a problem with getting Doze to work properly. The result is poor battery life.
So my question is what would be the best fw to use?
My model is SM-G935U
CARRIER: AT&T in the USA
***first samsung phone for me and the most confusing part is all the different variants. Should I download xxa?
If you want the best experience on the network, I'd suggest SM-G935A. Sure, it has the carrier bloat, but I don't have an issue disabling the ones I don't use.
Sent from my SM-G955U using Tapatalk
1) The U firmware does not have a doze problem. It gets far better battery life than the A version.
2) This device does not work well with root. You *can* root, but most people seem to go back to stock at some point due to all the glitches and patches required.
3) The U firmware will work just fine on AT&T, but you will lose carrier specific features. Specifically, WiFi calling, VoLTE, etc. (You can get most of the others back by installing APKs)
4) The A firmware obviously will work fine on AT&T, but AT&T really gimped the bajeezus out of the S7 Edge Nougat ROM. I was getting unacceptable lag on bone stock A firmware.
5) You *can* disable packages on either using various Knox-based tools, but in some cases this can actually make things worse depending on how the package is used.
You just need to decide which is more important. Fast and battery efficient, but "bare bones"; or full featured, but a hot, laggy mess?
I was rooted using the samsung u firmware on the att model. I lost my phone a week ago and the insurance sent me a brand new one thankfully. I really didn't have any complaints when I was using the rooted s7 edge. But when I got this new one full att stock. It is quite clear to me now it is night and day difference. The rooted version right now is ok and usable but i will not be rooting my new s7 edge. This phone just flies with stock compared to eng root which just putts along.
jshamlet said:
1) The U firmware does not have a doze problem. It gets far better battery life than the A version.
2) This device does not work well with root. You *can* root, but most people seem to go back to stock at some point due to all the glitches and patches required.
3) The U firmware will work just fine on AT&T, but you will lose carrier specific features. Specifically, WiFi calling, VoLTE, etc. (You can get most of the others back by installing APKs)
4) The A firmware obviously will work fine on AT&T, but AT&T really gimped the bajeezus out of the S7 Edge Nougat ROM. I was getting unacceptable lag on bone stock A firmware.
5) You *can* disable packages on either using various Knox-based tools, but in some cases this can actually make things worse depending on how the package is used.
You just need to decide which is more important. Fast and battery efficient, but "bare bones"; or full featured, but a hot, laggy mess?
Click to expand...
Click to collapse
Thanks for the info!
Wish I'd waited just a bit longer. I wound up flashing xaa. Performance wise, it's good. Battery is also fine but I think right now WiFi Calling would be very useful. A family member just moved to an Island and the cell service is fair if it even works.
That's disappointing about 935A fw. Is it really laggy?
Also after flashing I couldnt write to my external sdcard. The system could but I lost those permissions and after much trial &error, I had to factory reset. Still not entirely sure why but it's been awhile since my phones had an sd slot. Think I recall removing it every time I flashed a new rom or even an update. Is that what you do?
Edit-it just occurred to me I downloaded the fw for my model G935U so I believe I am using the U firmware. I don't remember what xxa means. I think it applies to the region?
Hi everyone,
I was wondering if any of you know ZTE was going to provide any software update on their stock rom. From what I read, it does seems to be very unclear considering what's happening with the US government. So far, I haven't rooted my phone yet since my old LG G3 started to have wireless connectivity issues after I flashed a few roms on it and I continued to have those issues after I put the stock LG rom, so I'm a little bit scared to try again. Still, I'm wondering if any of you guys knows if there's a good rom out there that can work fine and that has the lasted security patch. If not, I'll probably think about switching phone, since I don't really like the idea to use a phone that's unsupported.
Thanks
There won't be any more Nougat updates as it's up to the ROM (Nougat B10 for my global model) where it bridges to Oreo and now Oreo even if it's released or leaked won't get updates.
Just my opinion but can't see how it could go any other way.
I guess for longevity, all you can look at is if any custom ROMs are long term and bug free. I think all custom ROMs for Axon 7 have at least one proper bug which affects calls or camera. One reason I stay stock.
RobboW said:
There won't be any more Nougat updates as it's up to the ROM (Nougat B10 for my global model) where it bridges to Oreo and now Oreo even if it's released or leaked won't get updates.
Just my opinion but can't see how it could go any other way.
I guess for longevity, all you can look at is if any custom ROMs are long term and bug free. I think all custom ROMs for Axon 7 have at least one proper bug which affects calls or camera. One reason I stay stock.
Click to expand...
Click to collapse
Thanks for the answer.
At least I'm not the only one to feel that this is what's going to happen. I love the Axon 7, but if it doesn't get updated, I should probably go for the Samsung Galaxy A8 since my carrier has a pretty good deal on it (15$ CAD over 24 months). The Nokia 7 doesn't seems like a really good phone as well with updates directly from Google. I think I'll have to shop a little bit.
The #8 post(replay from zteusa [email protected]) says all
https://forum.xda-developers.com/axon-7/help/news-2017g-android-oreo-t3755822
vas said:
The #8 post(replay from zteusa [email protected]) says all
https://forum.xda-developers.com/axon-7/help/news-2017g-android-oreo-t3755822
Click to expand...
Click to collapse
That's even worst than I thought
vas said:
The #8 post(replay from zteusa [email protected]) says all
https://forum.xda-developers.com/axon-7/help/news-2017g-android-oreo-t3755822
Click to expand...
Click to collapse
what does it "say"?
Oreo is around, ZTE says the word "no update" and it gets out
Hi my camera either works or it doesn't depending on when I last dropped my phone so I was wondering if there is a buildprop edit that will disable the ois on the camera.
I saw on here the instructions for a OnePlus 2 in one of the sun forums so that is where the idea came from.
My only other option to consider is maybe seeking out a phone with a Samsung isocell camera and fitting it to see if the drivers work for it since it would be in the same family.
Someone on ZTE community recommended a camera from another axon 7 but that defeats the point. I might aswell just use that and keep my one as spares but I'd rather seek a fix rather than a new purchase.
My axon 7 is a 2017u model I bought in Canada but I am currently living back home in England. I am moving back next year so the 2017u is better for me on the network I use there.
I am also eagerly awaiting official 8.0 and lineage 15 as I will be looking to try both. Though finding it hard to get my head around the files needed to flash (bootstacks etc) as I came from a nexus 6p and nexus 5 previous so flashing to me was a doddle.
Cheers
John
Jcth1 said:
Hi my camera either works or it doesn't depending on when I last dropped my phone so I was wondering if there is a buildprop edit that will disable the ois on the camera.
I saw on here the instructions for a OnePlus 2 in one of the sun forums so that is where the idea came from.
My only other option to consider is maybe seeking out a phone with a Samsung isocell camera and fitting it to see if the drivers work for it since it would be in the same family.
Someone on ZTE community recommended a camera from another axon 7 but that defeats the point. I might aswell just use that and keep my one as spares but I'd rather seek a fix rather than a new purchase.
My axon 7 is a 2017u model I bought in Canada but I am currently living back home in England. I am moving back next year so the 2017u is better for me on the network I use there.
I am also eagerly awaiting official 8.0 and lineage 15 as I will be looking to try both. Though finding it hard to get my head around the files needed to flash (bootstacks etc) as I came from a nexus 6p and nexus 5 previous so flashing to me was a doddle.
Cheers
John
Click to expand...
Click to collapse
A camera from another phone model is not gonna work, like, ever, unless it is the exact same sensor... dob't even think about it. But from another axon7, yeah.
Oreo B01 and B12 have been released by NFound as flashables, they are both official 8.0 and you don't need anything else (besides magisk of course) to flash them since they are aroma zips with the modems bundled. just select which modem you want and you're fine
Cheers...I will wait to see if anyone can guide me to a buildprop edit to maybe disable the OIS then...
Also quick question. What is with the b numbers for ROMs. I would have thought the Oreo ROM would be one number but you quote 2 different variants.
Is there a guide somewhere about that so I can catch up to the whole scene from the beginning of the axon 7
Cheers
Jcth1 said:
Cheers...I will wait to see if anyone can guide me to a buildprop edit to maybe disable the OIS then...
Also quick question. What is with the b numbers for ROMs. I would have thought the Oreo ROM would be one number but you quote 2 different variants.
Is there a guide somewhere about that so I can catch up to the whole scene from the beginning of the axon 7
Cheers
Click to expand...
Click to collapse
No, we planned to do one but just didn't eventually.
There are 3 models: A2017 which is from China, A2017G which is Int'l, and A2017U for the US. These 3 models have different developer teams for some reason.
So the Chinese and U devs number all of their betas, and for example, in this case the first official update to Oreo would have been around B15 (They don't start from B01, they just count until they get a stable one and release it). So, that's why they skip numbers; for example on the U you have B32 and then came B35, because there were two unreleased betas in the middle. This causes the build numbers to go up a crapton.
The updates are usually labeled A2017xVx.x.xBxx. V1.0.0 is Marshmallow, and then Nougat may be V1.2.0 for example. But they all use different naming schemes and it's a mess.
The G team never skips numbers. For example the Oreo update is called B01. Nougat and Marshmallow also had B01 as the first versions. This way it's much easier because they don't skip any numbers, but you don't know how many betas it went through
In this case Oreo is A2017GV1.3.0B01
I don't believe disabling OIS from build.prop is possible
Cheers anyways. I installed the new unnofficial 15.1 lineage and the camera has been fine since so all is good at the moment.
Very happy chappy here. Glad I kept the phone and waited to take it to android 8