Related
This pertains specifically to the recent LG release of ICS (with the NVIDIA accelerated hardware drivers) for the SU660 (Korean version of the Optimus 2X) and the lack of developer interest in porting it to the P990 and P999 versions of the same phone.
WHERE HAVE ALL THE DEVELOPERS GONE
Original words and music by Pete Seeger
Originally performed by Pete Seeger and Tao Rodriguez-Seeger
Changed lyrics by Core Memory (Member of XDA Developers)
Where have all the developers gone?
Long time passing
Where have all the developers gone?
Long time ago
Where have all the developers gone?
LG has disappointed them every one
When will they ever learn?
When will they ever learn?
Where have all the developers gone?
Long time passing
Where have all the developers gone?
Long time ago
Where have all the developers gone?
NVIDIA has disappointed them every one
When will they ever learn?
When will they ever learn?
They'll be back when the kernel source code is released (don't worry, LG is legally obliged to release it due to the contract terms of using Android).
I doubt the devs can just pick apart the Korean .kdz file to extract binaries - they need the source code. And we know the source code WILL come now, it's just a matter of time.
Hang on man, I'm excited myself. Especially being in North America where we are unlikely to get any OTA update.
hehe, forward your message to LG man ;P
machoman1337 said:
They'll be back when the kernel source code is released (don't worry, LG is legally obliged to release it due to the contract terms of using Android).
I doubt the devs can just pick apart the Korean .kdz file to extract binaries - they need the source code. And we know the source code WILL come now, it's just a matter of time.
Hang on man, I'm excited myself. Especially being in North America where we are unlikely to get any OTA update.
Click to expand...
Click to collapse
Especially especially in Canada.
i just flashed the V30A_00.kdz on my O2x but i doesnt boot, only one thing works the new logo
lol, for those who dont know what song is this like me, here is the original version
http://www.youtube.com/watch?v=0aw-HiMW-3M&feature=related
danydani90 said:
i just flashed the V30A_00.kdz on my O2x but i doesnt boot, only one thing works the new logo
Click to expand...
Click to collapse
LOL, I think Stefan already announced that this would happen. Although the SU660 and the P990 have the same specs there are slight variations in the partitioning and so on that makes it impossible to just mix-and-match ROMs. Same for just about every phone with regional variations, it's to prevent people from easily debranding phones and removing carrier bloatware. It's nothing that our devs can't overcome... but they need source code first.
machoman1337 said:
LOL, I think Stefan already announced that this would happen. Although the SU660 and the P990 have the same specs there are slight variations in the partitioning and so on that makes it impossible to just mix-and-match ROMs. Same for just about every phone with regional variations, it's to prevent people from easily debranding phones and removing carrier bloatware. It's nothing that our devs can't overcome... but they need source code first.
Click to expand...
Click to collapse
i have one of those versions with vibrating issue on normal cwm and non vibrating issue with su660 cwm and i was curious
Our devs are awesome! Without their hard work, we'd still be stuck on stock gingerbread (or even froyo in some cases)
Keep up the awesome work guys! :good:
Our devs have their hands tied right now because they don't have enough material to work with quite yet... It's not that they "aren't interested" as you say...
http://www.youtube.com/watch?v=KMU0tzLwhbE
Core Memory said:
This pertains specifically to the recent LG release of ICS (with the NVIDIA accelerated hardware drivers) for the SU660 (Korean version of the Optimus 2X) and the lack of developer interest in porting it to the P990 and P999 versions of the same phone.
Click to expand...
Click to collapse
I think you should inform yourself a little more.before creating a thread calling for developers.
I don't know of a single dev who has a "lack of interest", most are quite excited. If it would be easily possible to port the SU660 ROM to the P99x one it would already have been done. It is NOT the "same" phone.
And keep in mind that this phone never had a lot of - how to phrase it - "real kick ass developers".
The best thing which could have happened to our phone was arcee, his skills are amazing. Without him the LG 2x custom ROM scene would be nowhere near the current state.
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
helloha1 said:
http://www.youtube.com/watch?v=KMU0tzLwhbE
Click to expand...
Click to collapse
Steve is just crazy (and unfortunately not the best CEO).
helloha1 said:
Our devs are awesome! Without their hard work, we'd still be stuck on stock gingerbread (or even froyo in some cases)
Keep up the awesome work guys! :good:
Our devs have their hands tied right now because they don't have enough material to work with quite yet... It's not that they "aren't interested" as you say...
http://www.youtube.com/watch?v=KMU0tzLwhbE
Click to expand...
Click to collapse
My OP is not a criticism of developers.
Many have "moved on" from the Optimus 2X/G2X.
Because of "agro" from LG and NVIDIA .
Will LG and NVIDIA ever learn.
LG and NVIDIA will never learn.
Steve Balmer's developer rant is a symptom of what's wrong with Microsoft. Good video.
Core Memory said:
My OP is not a criticism of developers.
Many have "moved on" from the Optimus 2X/G2X.
Because of "agro" from LG and NVIDIA .
Will LG and NVIDIA ever learn.
LG and NVIDIA will never learn.
Click to expand...
Click to collapse
Hm.. then please list only 5 names of the "many" devs who moved on...
If you have been following the threads about the leak, you would know that they can't do anything at the moment because basically they still need the kernel sources to work (which we still don't have) and in consecuence you wouldn't have posted this (right?).
I'm a developer and I don't really like this kind of stuff. It feels like pressuring them to get working on something, remember they are doing this for fun / self training and for free - so please people let them be. If something new happens they will be the first ones to inform about it.
tonyp said:
Hm.. then please list only 5 names of the "many" devs who moved on...
Click to expand...
Click to collapse
I'll leave that to you because you know that more than that have sold their Optimus 2X and G2X phones and moved on and others such as RC have "put it on the shelf" and, depending on LG releasing ICS with accessible NVIDIA hardware drivers and whether he thinks it is worthwhile spending his time on it instead of his current and future interests, he may or may not be counted among the developers who "moved on" (hopefully not).
DrummerMuppet said:
If you have been following the threads about the leak, you would know that they can't do anything at the moment because basically they still need the kernel sources to work (which we still don't have) and in consecuence you wouldn't have posted this (right?).
I'm a developer and I don't really like this kind of stuff. It feels like pressuring them to get working on something, remember they are doing this for fun / self training and for free - so please people let them be. If something new happens they will be the first ones to inform about it.
Click to expand...
Click to collapse
Again, I am not blaming developers. I am blaming LG and NVIDIA. So, if you are a developer, any SU660/P990/P999 developer, don't take it personally.
Core Memory said:
Again, I am not blaming developers. I am blaming LG and NVIDIA. So, if you are a developer, any SU660/P990/P999 developer, don't take it personally.
Click to expand...
Click to collapse
But the thing you're missing is that the devs are still here. Just today JB alpha was released. You make yourself look stupid.
Sent from O2X via xda premium, beware of autocorrection
coolacrille said:
But the thing you're missing is that the devs are still here. Just today JB alpha was released. You make yourself look stupid.
Sent from O2X via xda premium, beware of autocorrection
Click to expand...
Click to collapse
Yes, JB alpha for the O2X was just released but ICS and JB are already available for other, older, phones with less worthy hardware. W're fortunate that, in spite of NVIDIA and LG causing development for the O2X to be somewhat masochistic, there are still some developers working on it. If LG releases a public version of ICS with a locked bootloader for the SU660/P990/P999, there will be even fewer developers. It is interesting to note the lack of developers commenting about my post. I think they understand where I am coming from.
Core Memory said:
Yes, JB alpha for the O2X was just released but ICS and JB are already available for other, older, phones with less worthy hardware. W're fortunate that, in spite of NVIDIA and LG causing development for the O2X to be somewhat masochistic, there are still some developers working on it. If LG releases a public version of ICS with a locked bootloader for the SU660/P990/P999, there will be even fewer developers. It is interesting to note the lack of developers commenting about my post. I think they understand where I am coming from.
Click to expand...
Click to collapse
1. The opposite will happen when we get the official ICS release (which will most likely have the locked bootloader, yes). More devs will gain interest as there's finally something to do instead of waiting. The locked bootloader will be annoying but there will be ways around it.
2. The real devs usually don't read xda in general and not the general section in particular. No wondering why...
3. Start learning to develop your own stuff then the 2x will be exactly the way you want it to have. No offense, but this thread leads to nothing.
Sent from my LG-P990 using xda app-developers app
tonyp said:
1. The opposite will happen when we get the official ICS release (which will most likely have the locked bootloader, yes). More devs will gain interest as there's finally something to do instead of waiting. The locked bootloader will be annoying but there will be ways around it.
2. The real devs usually don't read xda in general and not the general section in particular. No wondering why...
3. Start learning to develop your own stuff then the 2x will be exactly the way you want it to have. No offense, but this thread leads to nothing.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Good luck.
I recently purchased a used droid 4 on ebay. Unfortunately it has been upgraded to the OTA release of ICS 4.04. Anyone working on lifting the simlock associated with the version of the bootlocker included with ICS (I'm assuming the bootloader is the origin of this simlock but technically I could be wrong)? Or is it a lost cause because it is signed? I know it's written to protected ram so any workaround would be nontrivial but does anyone have any possible exploit ideas? Motorola is unlocking a couple other models that they have out. Would petitioning them to include the droid 4 in their list of unlockable devices be a surefire path to getting the simlock lifted? Or should I consider this a lost cause and return my droid 4 to the ebay ether?
If anyone is considering working on this issue I would be more than glad to contribute. While I'm no Android expert I have a decent understanding of the OS and work in command line Linux for a living so I'd be glad to help. The selection of qwerty phones today is beyond attrocious.
One last thought. Is the idea of spoofing the carrier a possibility?
Sent from my SGH-T839 using Tapatalk
Hi blackstar,
So, I recently got a Droid 4 off of CraigsList that I wanted to use on StraightTalk, but found out that what I had perceived (that 2G/Edge was working on GSM North America) was incorrect.
They're not completely sure WHERE it's broken at the moment as far as SIM lock. Some have suggested it might be baked in the ROM -- but more than likely it is built into the modem.
Here have been some stabs at it -- and what to do in regards to getting the modem setup/altered.
http://forum.xda-developers.com/showthread.php?t=1916869
A thought, though -- since we have SafeStrap and Root, doesn't that let us essentially bypass the bootloader in some ways? My understanding is that the bootloader was required to boot the device to a "correct" image and lock the load to Motorola's firmware, but SafeStrap/root gave us access to actually overwrite the RAM/memory and replace the existing kernel with a new one for the chance at custom ROMs. So, I'm not entirely sure it has to do with the bootloader.
To me, it seems like something that's potentially baked into their ROM or in the modem firmware. If it's in the modem firmware, it's a matter of figuring out what keys/values need to be adjusted and then run it. There have been talks about AT&T getting the Photon Q (Asanti) -- rumors that were back around April of this year... but we have yet to see it there and no news about it showing up anytime soon. Not sure if they scrapped the keyboard and then shipped it as a different device.
I would imagine that if we can have the lowest level debug logging enabled and plug in an American SIM, you might be able to figure out what is breaking. Not sure how low logcat can go...
That's my understanding of the current situation, from a programmer's point of view (though I don't code for Android). Spoofing might be interesting -- but if it's locked at the radio firmware, I don't think spoofing can adjust the frequencies. But more power to you if you can figure it out (and force me to find ANOTHER Droid 4, haha).
Good luck! Definitely talk with the OP of the Topic I sent you, since s/he has a pretty deep interest in this as well.
OH, and one more thought -- there was a thought to grab an AT&T version of the Bionic and Verizon version, wherein they had the same radios, but different firmware, and do a diff on them to figure out if some settings had changed, and then potentially patch that into the D4. That might be a good strategy, but that would require us to get dumps from a few different people -- something you might be able to facilitate if you guys all work together.
One final thought -- is there any way we could have a sticky'd topic for people to post their findings, so we don't have to keep scanning and finding this?
Much thanks terinfire.
Let me start off by saying I don't have any definitive information with regards to any of the good questions you posed but if I find out anything I'll be sure to update the thread.
I spent a good chunk of the weekend trying to educate myself on the situation. From what I understand (anyone feel free to correct me or point me to the appropriate thread if I'm completely reinventing the wheel), it seems like it comes down to two most likely scenarios. Either Verizon added an MCC/MCN lock in the baseband when pushing out the OTA ICS release or they placed a restriction in the radio interface layer (RIL) of the ICS ROM. My research hasn't quite enabled me to determine which scenario is more likely. My unscientific intuition (and wishful thinking) is that the restriction is in the ROM somewhere in the RIL (if that makes any sense, still learning the Android OS architecture).
I will post what I've mentioned above in the the forum you mentioned; hopefully I can garner an audience. I will also look into getting a sticky topic created.
Not too sure how to implement any of my intuitions noted above with regards to this problem but I will try and learn as it goes.
One more note - so it is claimed that the Samsung Galaxy III for Verizon can be unlocked to use domestic GSM carriers. I've found no confirmation. (https://plus.google.com/103583939320326217147/posts/b7JbBKjJVSQ)
Pertinent links I came across in my research that may be useful:
MCC/MCN Codes: http://en.wikipedia.org/wiki/Mobile_Network_Code
Radio Interface Layer: http://en.wikipedia.org/wiki/Radio_Interface_Layer, http://www.kandroid.org/online-pdk/guide/telephony.html
RIL Header: https://code.google.com/p/linux-on-android/source/browse/radio/headers/ril.h
Qualcomm MDM660Device Specification: http://www.scribd.com/doc/54154049/...odem-Device-Specification-Advance-Information
At present, we have topics every few weeks or so with someone new, coming to ask if GSM works in America. Then, someone wants to help and try to figure out why -- but there is no consistent thread for this. So let's use this.
Does the Droid 4 work in the US on GSM yet? NO
This is to be used as a master thread to post research/thoughts/findings. If anyone has any clever thoughts, please search the thread first to make sure it hasn't been found yet.
What we do know is that with OTA ICS from Verizon, the Droid 4 supports GSM for *OTHER* carriers outside of the US. There could be any number of reasons that it does NOT work. As a quick run-down of the problem, I'll identify where the primary issues could be and allow for anyone else to build upon it, ask questions, and discuss.
The Radio Firmware
-- The firmware for the radio itself could have a lock or a setting that needs to be adjusted and all data requests are blocked through this.
RIL
-- The interface between the radio and Android -- there could be a software lock here that restricts specific carrier ID's.
ROM
-- The ROM itself has a baked-in block for GSM in America.
The best thing we can do is to try and identify or step through the stack (if such is possible -- I'm a developer, but not for Android) and see WHERE the calls break at.
--If it is a software lock in the ROM, then aftermarket ROM's like CyanogenMod should allow data to work in the US. If we're not seeing this, then this is likely not the case.
--If it is a software lock in the RIL library, then we'd have to have a reverse-engineered library (which could be very difficult to do). We should be getting some kind of error somewhere in here. At this point, though, it's hard to tell if the Radio Firmware or RIL is the actual problem.
Anyone with any background on this, please feel free to contribute. correct, and update. I'll try to get back here and update this master page as I see responses further in the thread.
Can we try to load up a deodexed rom and replace the ril file with, let's say one from XT910 in canada?
Sent from my XT894 running ICS
I assume this is just a GSM radio, without HSPA+, but does anyone know the frequencies it uses?
I just finished comparing a Droid RAZR XT912 to a Rogers RAZR XT910, I checked the /system/lib folder and build.prop files.
I found some really interesting differences, and also found that most of the important build.prop differences between the Rogers XT910 and Verizon XT912 were also consistent with the D4.
lines like:
persist.ril.modem.mode = (1 = CDMA, 2= UMTS)
persist.ril.mux.noofchannels = (10 on Rogers, 8 on VZW)
persist.radio.ap.phonetype = (1 = GSM, 2= CDMA)
and my favourite line
persist.ril.features = (0x182 = Rogers, 0x90A = Verizon)
I also found something only in Rogers build.prop:
ro.tether.denied=false
What's also interesting, is that most of the files in the /lib folder is consistent between the D4 and the RAZR, I have also included this report in the attached ZIP file.
Maybe this in combination with some files from the /lib folder might help. Either way, I've included my comparisons in the attached ZIP.
Does anybody want to just try changing the persist.ril.features in the US and see what happens??
Let's get US bands unlocked soon!!!
In my comparissions,
D:\ = XT894
G:\ = XT912
H:\ = XT910
I saw these and a couple other changes comparing the D4 file to the bionic GSM-working ICS leak build.prop. Unfortnately I'm studying for a GRE exam I have tomorrow but will try to give these changes a try when I take a break and if not, definitely by the end of tomorrow. I'm starting to have faith we'll find something. I don't think Verzion did anything that low-level to implement this US carrier block.
Sent from my SGH-T839 using Tapatalk
blackstar1744 said:
I saw these and a couple other changes comparing the D4 file to the bionic GSM-working ICS leak build.prop. Unfortnately I'm studying for a GRE exam I have tomorrow but will try to give these changes a try when I take a break and if not, definitely by the end of tomorrow. I'm starting to have faith we'll find something. I don't think Verzion did anything that low-level to implement this US carrier block.
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
School first, xda second. Good luck on your GRE!
Sent from my myTouch_4G_Slide using Tapatalk 2
Trying to get Radiocomm to recognize my phone but my phone keeps switching to mass storage mode even with Android debugging and mock location enabled. Was in Hashcode's AOKP and went back to the stock ROM and now I can stay in Media Device (MTP) but still don't have the appropriate Windows x64 driver. I'm currently running the attached file which I came across at some point in the Android Development forum in my earlier research into this whole domestic GSM issue. Does anyone else have another x64 driver?
The motivation for my question: Yesterday ariethekid claimed to get T-Mobile working on his Droid Bionic running Verizon's official ICS 246 release so the steps on this page *should* work - http://forum.xda-developers.com/showthread.php?t=1297714&page=13 along with the appropriate build.prop modifications. The bionic build.prop I attached includes the necessary changes. They would have to be included migrated to the D4 build.prop and I would/will eventually do it but I'm just not that far along yet given my Radiocomm issues.
Update: The OTA ICS updates already includes this 8 byte revision. I believe the only thing that needs to be done is the update of the build.prop.
blackstar1744 said:
Trying to get Radiocomm to recognize my phone but my phone keeps switching to mass storage mode even with Android debugging and mock location enabled. Was in Hashcode's AOKP and went back to the stock ROM and now I can stay in Media Device (MTP) but still don't have the appropriate Windows x64 driver. I'm currently running the attached file which I came across at some point in the Android Development forum in my earlier research into this whole domestic GSM issue. Does anyone else have another x64 driver?
The motivation for my question: Yesterday ariethekid claimed to get T-Mobile working on his Droid Bionic running Verizon's official ICS 246 release so the steps on this page *should* work - http://forum.xda-developers.com/showthread.php?t=1297714&page=13 along with the appropriate build.prop modifications. The bionic build.prop I attached includes the necessary changes. They would have to be included migrated to the D4 build.prop and I would/will eventually do it but I'm just not that far along yet given my Radiocomm issues.
Update: The OTA ICS updates already includes this 8 byte revision. I believe the only thing that needs to be done is the update of the build.prop.
Click to expand...
Click to collapse
In order to get the RadioComm interface, make sure you're using the latest Motorola Mobile Phone Drivers (these are different than the android drivers), they are version 5.9 as of right now. Please download them from here :
https://developer.motorola.com/tools/usb_drivers/
Looks like the Motorola site is down though, so you can download them from here :
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-64-bit-38124.shtml
http://forum.xda-developers.com/showthread.php?p=33230579
this was just posted, has all NV lines together, maybe we can figure it out in here!
dewhashish said:
http://forum.xda-developers.com/showthread.php?p=33230579
this was just posted, has all NV lines together, maybe we can figure it out in here!
Click to expand...
Click to collapse
Just a thought. Perhaps these values could be checked against a Bionic?
4869^"GSM Carrier Suppression"^"GSM*"
4870^"GSM 850 Carrier Suppression"^"GSM*"
4871^"GSM DCS Carrier Suppression"^"GSM*"
4872^"GSM 1900 Carrier Suppression"^"GSM*"
blackstar1744 said:
Just a thought. Perhaps these values could be checked against a Bionic?
4869^"GSM Carrier Suppression"^"GSM*"
4870^"GSM 850 Carrier Suppression"^"GSM*"
4871^"GSM DCS Carrier Suppression"^"GSM*"
4872^"GSM 1900 Carrier Suppression"^"GSM*"
Click to expand...
Click to collapse
You would have better luck posting this question in that forum.
By the way, Bionic GSM is a go. They have it fully up and running in that thread. Confirmed working by quite a few users
danifunker tried that already and folks have posted results in this topic (and it didn't work, apparently):
http://forum.xda-developers.com/showthread.php?t=1916869
Apparently, it does not apply to GSM in the US:
http://forum.xda-developers.com/showpost.php?p=32478552&postcount=21
They, however, did not try to toggle 4869. They did 4870 - 4872. Apparently the Bionic ignores those keys and does not worry about it.
Has anyone actually tried, for sure, to toggle these settings and verify whether they work or not?
D4 for US GSM Bump
Hello out there?
Has anyone come up or been experimenting on how to get the domestic U.S. carriers unblocked on the Droid 4? I've been searching high and low and apparently the Bionic fixes do not work on the D4.
daqueenzkid said:
Hello out there?
Has anyone come up or been experimenting on how to get the domestic U.S. carriers unblocked on the Droid 4? I've been searching high and low and apparently the Bionic fixes do not work on the D4.
Click to expand...
Click to collapse
Quite a few poked around, but there hasn't been any progress in the past few months. If this phone had more support, I'm sure it could be figured out, but not like this. It does take brilliant minds at work to figure this stuff out.
Sent from my SGH-I927 using Tapatalk 2
gtmaster303 said:
Quite a few poked around, but there hasn't been any progress in the past few months. If this phone had more support, I'm sure it could be figured out, but not like this. It does take brilliant minds at work to figure this stuff out.
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
There are some people looking into it but it is absurdly complicated. Granted they keep moving closer to a solution, this is the most complicated phone workaround I've ever seen. Motorola/Verizon is straight evil.
http://forum.xda-developers.com/showthread.php?t=2144335
Sent from my XT894 using Tapatalk 2
blackstar1744 said:
There are some people looking into it but it is absurdly complicated. Granted they keep moving closer to a solution, this is the most complicated phone workaround I've ever seen. Motorola/Verizon is straight evil.
http://forum.xda-developers.com/showthread.php?t=2144335
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Yea that's definitely apparent. That's a brand new thread. Haven't seen it before. Those guys are doing alright
Sent from my SGH-I927 using Tapatalk 2
You can try my Rom.
I edited all settings about CDMA to GSM not only build.prop but I'm not in USA so I can not try.
droid bionic gsm unlock
Hey guys. Ive been on XDA for so long and never reslly mentioned that the gsm on my droid bionic on ICS is unlocked. Ive tried alot of methods but one method i used finally worked. i just pop a non verizon sim card in and it works 100%. txt etc.
What is this method?
It's been known and well established that the MDM6600 radio on Bionic, in particular the hardware revision A first production devices, do not have the block on US GSM carriers that the subsequent RAZR/D4 models have and can be made to work with a few simple modifications.
This does not apply to the RAZR/D4 and after a great deal of examination it has been determined that the block is in the signed BP radio image and cannot be disabled via NV editing nor any other means.
I just replied to a question in the development thread where an N4 user, running stock 4.3 suddenly lost connectivity to his 5ghz router band, nothing changed on his phone but suddenly he loses connectivity to 5ghz band?
Of course this is a well known issue, impacting hundreds of users globally since the 4.3 update, and it got me thinking that just maybe the actual code written for the Wi-Fi radio drivers in 4.3 was overly aggressive in terms of the capabilities of the radio hardware in the N4 and actually physically damaged the hardware? Code can break hardware, we all know of devices that have been permanently bricked and became coasters - all because of bad code or a flash that went wrong.
What if the radio code written in 4.3 was to maximize signal strength to remedy the complaints of poor/slow Wi-Fi on many 4.2 devices, but was too aggressive for the radio hardware in our N4's causing it to basically overload and physically die? I've read of people who had no issues with their 5ghz channel (like me) then after updating to 4.3 completely lost 5ghz connectivity, and even after downgrading to factory 4.2 stock firmware STILL had no 5ghz connectivity. In my case after downgrading to 4.2 i still had no connectivity to both of my dual band Netgear routers, nor any other 5ghz band router I tried, complete 5ghz failure - downgrading to the same 4.2 firmware that had worked flawlessly before updating to 4.3! If it was just software then downgrading to the previous 4.2 firmware should have instantly resolved the 5ghz connectivity, right? If it worked without issue before then it should work without issue again. Except for many it simply remained broken, so it stands to reason that something else changed - i.e. the physical hardware was damaged.
Maybe that's why Google quietly shot out 4 different versions of 4.3 in an attempt to hide the fact that the radio code was too aggressive for some phones hardware? They perhaps toned down the radio code's aggressive push of the hardware, which might explain why some people don't have the issue, but it was already too late for phones with lower hardware tolerances and the damage was permanent.
I'm getting a replacement device from Google tomorrow and if the 5ghz band works out of the box on the stock 4.3 firmware, I'm highly likely to immediately downgrade to 4.2 stock as I have a strong feeling that its just a matterof time before i once again lose 5ghz connectivity just like the person i mentioned at the beginning of this post.
I suspect Kit Kat to use the same drivers as 4.3 so I'm staying clear of new builds until V5.0.
Of course if people regain 5ghz connectivity on Kit Kat I will stand corrected, but I'm willing to bet they don't - if functionality that worked fine on 4.2 can't be recovered by downgrading from 4.3, it's almost certainly damaged radio hardware, and no new versions can fix that.
Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app
THEBANDIT420 said:
Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Google releases their ROM's for numerous phone manufacturers, remember that ICS was the first android version that was cross compatible across all phones and tablets, the idea that it was easy to mass implement.
Consider the price of the N4 - $250 for 16gb model, about 40% of the price of a Samsung GS4! And the old saying that you get what you pay for. Junky screen compared to the SGS4 and other top price phones. Crap audio hardware compared to the fantastic sound chips Samsung uses. And most likely many other corners were cut to be able to release a 'flagship' device for less than half the price of the next major Android competitor (SGS4). It's straight forward economics, you get what you pay for. And I don't think Google realized that the tolerance levels of the N4's radio hardware were as low as I think they actually are, which is why they have been unable to resolve the issue in 4 quickly released 4.3 builds! I think they knew that the first release boosted signal strength in most other phones but didn't expect it to actually exceed the tolerances of lower end components that had to be used in the N4 which packs in all the top features of a high end phone at half the price!
I would never buy an LG flat screen TV, I'd always buy the Samsung simply because it's better quality in every way. I'm not sure why my brain didn't tell me this when I bought the N4. It was too good to be true at less than $250 for the latest Android phone? I think it was too good to be true!!
Let's watch Kit Kat roll out and watch these forums fill with p!seed people who still don't have reliable connectivity, and never will because their phone is physically broken.
Again, the acid test is to downgrade to say 4.1.2 and see if your 5ghz band works and your 2.4ghz speed flies, because it did when the phone was released back in December 2012 when it ran 4.1.1 or 4.1.2. I'm betting it won't work like it did and you still can't connect with the speed and reliability you once had. And if you can't get 5ghz connectivity on 4.3 you won't ever get it again because the hardware is cooked.
Globespy said:
Too long to quote.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Globespy said:
to long to quote
Click to expand...
Click to collapse
You don't buy lg TVs yet you bought a phone made by lg......
You bought the n4 but yet to YOU the s4 is WAY superior to it.....
Then I guess you know what you need to do then.....
Smh
Sent from my Nexus 4 using XDA Premium 4 mobile app
Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------
PJcastaldo said:
Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
And I think and still think the N4 is a great device. Its fast looks nice. I personally think the screen looks nice.. and takes great pictures. So... maybe you should go buy a Samsung...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app
Globespy said:
[A lot of text]
Click to expand...
Click to collapse
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be the Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.
Zenety said:
Click to expand...
Click to collapse
So childish. I bought the N4 for thethe same reason most others did - it was sold as a flagship product for what was literally a 'steal'. I haven't had this many issues with a phone since I ditched windows and moved to Android when eclair came out. But I suppose this makes me a Mac fanboy now? Lol.
I actually have never owned a Mac - PC guy.
Johmama said:
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be thethe Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.
Click to expand...
Click to collapse
This thread was started because of an idea, based on a problem that I've struggled with as well as friends who ate all nexus guys.
It was not to bash LG or Google - I've been around on this forum a LONG time and have bought many nexus phones and tablets, and have enjoyed them!
The last Gnex was not priced at the level the N4 released at, yet at that time Android phones had been selling as much as iPhone, I believe around that time worldwide sales surpassed them for the first time. I understand that Google has a different business model focused on selling software (actually their main business is advertising) and want to market their products at a lower price point than hardware manufacturers like HTC, Samsung etc. But when you do this you still cut corners. I'm not alone here in saying that the screen and sound hardware used in the sgs4 is just better. There's no argument. I could have bought one but I'm a nexus guy and have been for a while. I bought a sgs4 for my Gf, she loves that TW nonsense. But maybe just maybe I have a point about hardware failure given that the majority can't resolve it even going back to software that worked before!
Anyway, your recommendation of flashing different kernels may work for a few, but from looking at the hundreds of posts on numerous different sites (most notably Google's N4 support forum), it's clear that the majority are still having issues, me included which is why I just ordered a replacement phone which success today.
You see, I actually like the device - with a few tweaks here and there it can be vastly improved. Screen gamma can be fixed, sound quality too with things like viper.
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.
Globespy said:
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.
Click to expand...
Click to collapse
When you say you go back to a previous version of Android, how do you do it? Do you have a flashable zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?
Johmama said:
When you say you go back to a previous version of Android, how do you do it? Do you have a zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?
Click to expand...
Click to collapse
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one (like the new one I'll get from Google in a few hours, running JWR66Y), except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3.
In case you are serious about your bet earlier, I'd like to have a few more bills for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.
Globespy said:
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one - except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3! The same one in getting in about 5 hours which I know will be JWR66Y.
In case you are serious about your bet earlier, I'd like to have a few more bills to for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.
Click to expand...
Click to collapse
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.
It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.
lazer155 said:
It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.
Click to expand...
Click to collapse
I get that these methods have worked for some but not all.
Let's get real basic.
If my phone had zero 5ghz issues on say 4.2.2 (with .54 radio), and then lost 5ghz connectivity on 4.3, then I flashed a completely clean version of that previous Google factory 4.2.2 firmware (which includes the .54 radio) and my phone now shows that indeed that old radio was installed, yet i still can't get 5ghz connectivity, then its not software only. Something changed that's not software, otherwise it should work. The phone has been returned to exactly the same way it was before the 4.3 update, every shred of the 4.3 build nuked as if it never existed. Yet part of it is not functional that used to be fine? There aren't too many things it could be - software or hardware. The software didn't change, I know that is factual as its the very same Google factory stock firmware. So......?????
Johmama said:
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.
Click to expand...
Click to collapse
PM sent. I'm just playing with you mate. I just got tired of people on the other end of an internet connection making bets they can't or won't follow through on. I am no novice and have been around long enough to know that my issue is not fixable. Trust me I've tried everything and then some. After trying all the potential fixes, I also bought a new router (the r6300), and tried 3-5 other routers and same problem every time. That's when I threw in the towel and sent for a replacement.
But thanks for your suggestions. I still think in my case it's hardware as I've ruled out software.
So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....
Globespy said:
So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....
Click to expand...
Click to collapse
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.
Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?
Johmama said:
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.
Click to expand...
Click to collapse
Thanks. Tried this with every channel on the 5ghz band, 2-digit and 3-digit channel.
_delice_doluca_ said:
Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?
Click to expand...
Click to collapse
Lots of great ideas. I've heard of only a few people who managed to get the 5ghz band back, although most still suffer from much slower speeds. If you run broad searches you will see that most people can't get it to work after they lose it, even downgrading the entire system to a build/radio that previously worked without issue - like me.
Using MrSkips toolkit it absolutely wipes any trace of the 4.3 ROM and any radio association, turning the phone back to how it was shipped (JDQ39). Yet still no luck. Not all hardware is created equally, just like certain CPU can overclock/undervolt the same amounts. Perhaps some radios have lower tolerances and die? It may sound strange, but not impossible.
I'm sticking with 4.2.2 until Kit Kat comes out and will wait a few weeks to see what happens. If people get 5ghz back then it's likely Google rewrote the radio code.
this device has amazing specs but lack of software support. it would be amazing some custom pie or 10 roms
i don't need asus own features
i really like a pixel experience,los or omnirom the most stock android feeling rom( +120hz you will get a more buttery smooth experience)
please somebody create one
sources are available
even zenfone 6 has custom roms
Yes please !
Alessandro999 said:
this device has amazing specs but lack of software support. it would be amazing some custom pie or 10 roms
i don't need asus own features
i really like a pixel experience,los or omnirom the most stock android feeling rom( +120hz you will get a more buttery smooth experience)
please somebody create one
sources are available
even zenfone 6 has custom roms
Click to expand...
Click to collapse
one problem is TWRP hasn't even been created... Yet. And yes there really is no software support... Yet
Swarai said:
one problem is TWRP hasn't even been created... Yet. And yes there really is no software support... Yet
Click to expand...
Click to collapse
yes exactly i really hope somebody create a tpwr and rom because sources are out
It will be nice if this phone receives TWRP and custom roms.
Sent from my iPad using Tapatalk
Didn't it JUST launch globally today?
Let's give it some time.
i really hope somebody create a stable tpwr since sources are available and the most stable rom out there like omnirom or pixel experience
preferred omnirom
IMO I don't believe it will receive support anytime soon. Unless ROG was able to convince your standard Android enthusiast that this isn't just a gaming device. People that purchase this phone are mainly interested in one thing, gaming, not development. So, ROG has to convince those types that this device is just as good as those others.
It will be interesting to have custom roms for rog. waiting also
ZeroKool76 said:
IMO I don't believe it will receive support anytime soon. Unless ROG was able to convince your standard Android enthusiast that this isn't just a gaming device. People that purchase this phone are mainly interested in one thing, gaming, not development. So, ROG has to convince those types that this device is just as good as those others.
Click to expand...
Click to collapse
My thoughts exactly. Custom roms are awesome but they are generally made or ported to be used by a majority of the phones out there. If we got a custom rom ie. AOSP, who would code in the air triggers from scratch?
Having said that, the stock rom is quite good. I don't have the need to root it like I did with my Mate 20X to shrink down the gigantic icons/screen because by default Asus allows a lot of customization.
n1tro said:
My thoughts exactly. Custom roms are awesome but they are generally made or ported to be used by a majority of the phones out there. If we got a custom rom ie. AOSP, who would code in the air triggers from scratch?
Having said that, the stock rom is quite good. I don't have the need to root it like I did with my Mate 20X to shrink down the gigantic icons/screen because by default Asus allows a lot of customization.
Click to expand...
Click to collapse
Apparently the American version doesn't have volte or voWi-Fi as well.. that, along with the fact that it doesn't support band 71, are big reasons why your normal or typical Android enthusiast/ developer is not going to purchase this device
ZeroKool76 said:
Apparently the American version doesn't have volte or voWi-Fi as well.. that, along with the fact that it doesn't support band 71, are big reasons why your normal or typical Android enthusiast/ developer is not going to purchase this device
Click to expand...
Click to collapse
So does this apply to the Tengent games (CN) version too? I am getting the cheaper CN version and then going to flash the WW (Global) Rom, so essentially I guess I am asking is this a hardware omission, or is it ROM (software) based?
And how does this typically affect say a normal phone user?
It might get an update. As for band 71, I personally don't care because I won't use it all.
jkeener88 said:
So does this apply to the Tengent games (CN) version too? I am getting the cheaper CN version and then going to flash the WW (Global) Rom, so essentially I guess I am asking is this a hardware omission, or is it ROM (software) based?
And how does this typically affect say a normal phone user?
Click to expand...
Click to collapse
As I understand it, it doesn't have to do with software or hardware, they just simply don't support volte of vowifi. In China, they do. So, it's not the device, but the companies choice. May be some restrictions that we aren't aware of, otherwise it doesn't seem like a very smart decision. I was all in until I heard this. 3G is going to be removed from our networks in the next few years, so voLTE is kind of mandatory. Even now, if I don't have voLTE, I can't make or receive calls. VoWiFi, that's beneficial if you're cell signal is low for whatever reason. Maybe you work below ground or in Faraday cage style buildings. Plenty of uses for it. As far as band 71, no, I probably don't need it. But that doesn't mean I wouldn't want it just in case. Always better to have and not need, than to need and not have.
ZeroKool76 said:
As I understand it, it doesn't have to do with software or hardware, they just simply don't support volte of vowifi. In China, they do. So, it's not the device, but the companies choice. May be some restrictions that we aren't aware of, otherwise it doesn't seem like a very smart decision. I was all in until I heard this. 3G is going to be removed from our networks in the next few years, so voLTE is kind of mandatory. Even now, if I don't have voLTE, I can't make or receive calls. VoWiFi, that's beneficial if you're cell signal is low for whatever reason. Maybe you work below ground or in Faraday cage style buildings. Plenty of uses for it. As far as band 71, no, I probably don't need it. But that doesn't mean I wouldn't want it just in case. Always better to have and not need, than to need and not have.
Click to expand...
Click to collapse
This is wrong for TMO. It's in the SW. There's an option for volte carrier check on xiaomis phones. A simple dialer code disables this check, and volte works on TMO. I'm hoping there's a way we can do this on the rog 2. That, or a build.prop edit to enable it. There has to be a setting hidden that disables volte in us.
suzook said:
This is wrong for TMO. It's in the SW. There's an option for volte carrier check on xiaomis phones. A simple dialer code disables this check, and volte works on TMO. I'm hoping there's a way we can do this on the rog 2. That, or a build.prop edit to enable it. There has to be a setting hidden that disables volte in us.
Click to expand...
Click to collapse
I've just been reading a little bit more up on it, and apparently, ASUS didn't pay the cell carriers in North America for provisioning costs. That's why it won't work. So, regardless of software, hardware or any other type of hackery, it won't work in North America.
ZeroKool76 said:
I've just been reading a little bit more up on it, and apparently, ASUS didn't pay the cell carriers in North America for provisioning costs. That's why it won't work. So, regardless of software, hardware or any other type of hackery, it won't work in North America.
Click to expand...
Click to collapse
So is this just a bad/dumb move by Asus or what? I mean I honestly don't know if these omissions will affect me, all I know is I still own a Samsung until I get the Asus and was always able to use my Samsung phone how I wanted to use it