I currently own a Nexus 6 that I purchased from the Google Play Store about a month a ago. One of the features of Android 5.0+ is that when you insert a carrier SIM card it will install carrier specific apps to your phone. I was pleasantly surprised that it installed the NTT Docomo Area Mail app for emergency alerts. I was quickly disappointed when it said that it didn't support my phone so I uninstalled the app.
With the strong earthquake that we had today I was surprised that I got an Area Mail alert even with the application not installed. I did find that the "Cell Broadcast Alert Service" was running and had started at the exact time the earthquake started.
Showing posts with label Nexus. Show all posts
Showing posts with label Nexus. Show all posts
Monday, May 25, 2015
Saturday, November 9, 2013
Potential fix for 3G data and Nexus 5
UPDATE:Nope, doesn't work: "The patch only makes the phone think it's registered so it doesn't really have any effect on the network level. One thing I noticed is that it tries to register with MNC=215, not idea where that comes from..."
Over on oov's blog, he has a post on the Nexus 5 and Android 4.4 (kit kat) data-only SIM cell standby [J]. He has found another bug in Android 4.4 that is related to (apparently) incorrect mobile signal reporting. With an LTE data-only (not a data+voice) SIM, the signal bars are properly displayed in the notification bar, but cell standby shows a relatively high percentage of total battery consumption and the phone reports the time without a signal as 100%.
However, this just appears to be an issue with display only, because the phone does have a signal, it doesn't get hot, and the battery drain is not unexpectedly high.
He's created a patch for it and is looking for someone with a 3G SIM or 3G-only mobile contract to test to see if the patch also fixes the problem with 3G networks (bug here). This is all manually done right now because there is no Xposed installer for Android 4.4.
THIS IS NOT FOR BEGINNERS AND WILL VOID YOUR WARRANTY!
You will to have adb and fastboot setup on a computer and you will need to unlock the Nexus 5's bootloader, and flash a custom recovery, and then decompile and recompile jar classes.
Over on oov's blog, he has a post on the Nexus 5 and Android 4.4 (kit kat) data-only SIM cell standby [J]. He has found another bug in Android 4.4 that is related to (apparently) incorrect mobile signal reporting. With an LTE data-only (not a data+voice) SIM, the signal bars are properly displayed in the notification bar, but cell standby shows a relatively high percentage of total battery consumption and the phone reports the time without a signal as 100%.
However, this just appears to be an issue with display only, because the phone does have a signal, it doesn't get hot, and the battery drain is not unexpectedly high.
He's created a patch for it and is looking for someone with a 3G SIM or 3G-only mobile contract to test to see if the patch also fixes the problem with 3G networks (bug here). This is all manually done right now because there is no Xposed installer for Android 4.4.
THIS IS NOT FOR BEGINNERS AND WILL VOID YOUR WARRANTY!
You will to have adb and fastboot setup on a computer and you will need to unlock the Nexus 5's bootloader, and flash a custom recovery, and then decompile and recompile jar classes.
- Boot in to fastboot by holding volume down and the power button, connect to your PC with USB, type:
fastboot oem unlock
then confirm on the phone. This will do factory reset on your phone, wiping everything. Google for "adb backup" if you want to backup some of your stuff (assuming it works on the N5). - Reboot the phone, then disable MTP and enable USB debugging.
- Reboot in fastboot and flash the teamwin recovery with:
fastboot flash recovery openrecovery-twrp-n.n.n.n-hammerhead.img - Boot into recovery and mount the system partition.
- Pull a the following files to your pc to create a backup:
adb pull /system/framework/telephony-common.jar
adb pull /system/framework/telephony-common.odex
then delete the odexed fileadb shell rm /system/framework/telephony-common.odex - Download and start up Baksmali / Smali Manager.
- Enter 0 -> f -> telephony-common.jar (which pulls this file from the phone).
- Enter 5 -> 1 to set the current project file to telephony-common.jar.
- Enter 1 -> x -> Y
- Open com/android/internal/telephony/ServiceStateTracker.smali in a text editor and search for:
useDataRegStateForDataOnlyDevices()
and on the following line change:if-neztoif-eqz
then save and close the file - Return to Baksmali / Smali Manager and enter 2 -> N to recompile the jar classes with the patched file
- Finish with 3 -> Y -> f -> R and the phone will reboot.
Wednesday, November 6, 2013
Nexus 5 is not compatible with 3G contracts
UPDATE: a bug report has been filed. This affects all 3G contracts, regardless of whether the SIM is LTE-capable or not. This Google Plus post has good discussion in the comments.
Reports in the comment section here and elsewhere widely indicate that, for reasons not exactly clear, the b-mobile 3G SIMs are not working with the Nexus 5. According to a local android developer, the phone does not even see the "NTT DOCOMO" network under available networks. While JCI has not yet tested the Nexus 5, they also have been getting a number of reports of 3G SIMs not working.
It his highly likely that ALL docomo MVNOs will be similarly affected.
SIM cards that are currently incompatible are the BLUE and white FOMA ones:
Reports in the comment section here and elsewhere widely indicate that, for reasons not exactly clear, the b-mobile 3G SIMs are not working with the Nexus 5. According to a local android developer, the phone does not even see the "NTT DOCOMO" network under available networks. While JCI has not yet tested the Nexus 5, they also have been getting a number of reports of 3G SIMs not working.
It his highly likely that ALL docomo MVNOs will be similarly affected.
![]() |
| This SIM will not work with the Nexus 5 |
- Visitor SIM 1 GB and 14 day
- B-mobile FMC
- Talking SIM U300
- Amazon 3G smartphone
- Yodobashi 3G smartphone
- All the old, discontinued products that some of you still may be using (I still have the original 3G Fair), including:
- original 3G smartphone
- original Aeon 3G smartphone
- original talking 1GB flat rate
- original talking FAIR
- original 1GB flat rate (data-only)
- original FAIR
- original U300
- ¥2,100 for a new account when switching from 3G to LTE
- ¥3,150 for a new SIM card.
Tuesday, November 5, 2013
Using the Nexus 5 with NTT Docomo Xi
UPDATE: See this post for a list of instructions on how to change your Docomo ISP to Mopera U from sp-mode, which is necessary to use the Nexus 5 (or any unlocked, non-docomo phone with a Xi contract). Users are reporting that there is not an option to add the cheaper lite plan online, but because the standard plan has a 6 month free campaign now, add the standard plan now, then within 6 months change to the lite plan by going to a Docomo Shop.
There has been a lot of discussion and questions regarding exactly how to use the Nexus 5 with Docomo. Many of you have existing contracts for docomo LTE (Xi), and you may be wondering if you can just simply swap out the SIM card.
The answer is probably not.
If you just walked into a docomo shop and bought a Xi LTE phone, you are 99.9999999% using their "sp mode" ISP. However, the APN used with this ISP is filtered by the phone's IMEI number, with only numbers specifically whitelisted by docomo able to use this ISP.
There are two basic choices of mopera plans:
To change your ISP, I understand this can be done online through the my docomo page. If you can't figure out how to do that, you can just go to a docomo shop and get it done. You really don't need to tell them why you are doing it, and you don't even need to bring the phone.
NEVER change you ISP from sp-mode to mopera if you have an unrooted, unhacked, docomo Xi phone. Docomo firmware changes the APN when activating tethering, and this APN is incompatible with Mopera U. Data will work fine but you won't be able to tether. The Mopera U ISP and APN is only for unlocked, non-docomo phones.
Once you have changed the ISP to Mopera U, put your SIM card in the shiny new Nexus 5, then set mopera.net as the APN. It will most likely happen automatically. Alternatively, you can use open.mopera.net, which removes some filtering.
[List of docomo APNs.]
Here are some various screenshots from the mobile networks settings
![]() ![]() |
| Nexus 5 home screens showing a connection to docomo LTE |
The answer is probably not.
If you just walked into a docomo shop and bought a Xi LTE phone, you are 99.9999999% using their "sp mode" ISP. However, the APN used with this ISP is filtered by the phone's IMEI number, with only numbers specifically whitelisted by docomo able to use this ISP.
Many of you may not even realize that Docomo has different ISPs, since the mobile carrier typically is the ISP. There was at one point a good reason for it, well sort of. Docomo used a separate ISP for data devices, like the old USB dongles or other devices that would tether a computer to their network. This did two things:
Therefore, you will need to change your ISP from sp-mode to docomo's other ISP, Mopera U. sp-mode comes with extra services, like sp-mode mail that provides an @docomo.ne.jp email address. You will lose this email address with a Nexus 5. If you want to continue having an email address, you can continue having one @mopera, but honestly, with gmail, there is really no need for either an sp-mode or mopera mail account.- made it easy to charge a premium price for that service and
- segregated devices that were potentially able to eat a huge chunk of instantaneous bandwidth from the typical customer.
There are two basic choices of mopera plans:
- Mopera U Standard for ¥500+tax includes email
- Mopera U lite for ¥300+tax without mail
![]() |
| N5 using the mopera.net APN, which is preconfigured. |
To change your ISP, I understand this can be done online through the my docomo page. If you can't figure out how to do that, you can just go to a docomo shop and get it done. You really don't need to tell them why you are doing it, and you don't even need to bring the phone.
NEVER change you ISP from sp-mode to mopera if you have an unrooted, unhacked, docomo Xi phone. Docomo firmware changes the APN when activating tethering, and this APN is incompatible with Mopera U. Data will work fine but you won't be able to tether. The Mopera U ISP and APN is only for unlocked, non-docomo phones.
Once you have changed the ISP to Mopera U, put your SIM card in the shiny new Nexus 5, then set mopera.net as the APN. It will most likely happen automatically. Alternatively, you can use open.mopera.net, which removes some filtering.
[List of docomo APNs.]
Here are some various screenshots from the mobile networks settings
![]() ![]() |
| This is the Non-North American version, and it can see the other carrier's networks In the case of KDDI, it is seeing their Band 1 LTE data network (voice not compatible) |
Thursday, October 31, 2013
Both Nexus 5 models appear compatible in Japan
The Nexus 5 is now official. From the product page, select the "tech specs" in the drop down menu, then "View full tech specs". The "leaked" service manual appears to have been for the "Rest of the World model" (I'll call it international).
It is my understanding that Docomo's planned 150 Mbps LTE downlink will be using Band 3, which the international model supports, but not the North American model.
(Japanese frequency bands)
For people who are based in Japan but make trips to North America, the international model looks like the best route. You will NOT get LTE service in the US, but it is compatible with T-Mobile 3G (WCDMA Band 4) and AT&T 3G (WCDMA Band 2). We've all happily lived with 3G for years now. It is totally sufficient.
For people who are based in North America but make trips to Japan, the North American model is best. It is compatible with both T-Mobile and AT&Ts LTE networks (LTE Band 4), and also with what is currently the primary LTE band in Japan for Softbank and NTT Docomo (LTE Band 1). However, lacking Band 3 might become a hinderance in Japan using Docomo or MVNOs as Band 3 seems to be central to Docomo's expansion plans.
Monday, October 7, 2013
Supposedly leaked Nexus 5 service manual indicates support for Japanese LTE bands.
If this is really the Nexus 5 service manual, then this is good for Android users in Japan: Support for LTE without having to deal with a device that locks you out of mobile network settings.
FDD-LTE: Bands 1, 3, 5, 7, 8, 20.
WCDMA (HSDPA 3G): Bands 1, 2, 4, 5, 8
Band 1 is Docomo and Softbank's 2100 MHz, used for both LTE and 3G. As far as I can tell, the Nexus 5 does not support the low frequencies of either carrier, though.
CDMA is mentioned in the manual, but as you can see below, it is not listed as a "Supporting Standard". Therefore, my guess is that the reference to CDMA is probably just a standard copy-paste, to be read as "IF this did CDMA, here's what it would be."
However, as far as I can tell, CDMA is unsupported. (Also FeliCa, mobile Suica, etc. is not supported.)
Sunday, September 29, 2013
NTT docomo does not prevent unbranded devices from connecting to LTE network
There are now several posts online that describe using the Nexus 7 LTE with various Japanese SIM cards. Unlike the iPhone (and just as I expected) there appear to be no problems getting a connection with an unlocked, unbranded device on docomo's "Xi" LTE network. LTE service, both direct from docomo and through an MNVO, works perfectly.
Until now, we couldn't rule out a "server-side" origin for the problems that unlocked iPhone 5 users encounter when trying to connect to docomo LTE. This was because, except for those provided by docomo, there were no other LTE devices that supported docomo's primary LTE frequency (Band 1, 2100 MHz). We had two variables (iOS software and docomo servers), and one equation (Apple hardware), which is unsolvable.
We can now safely say that 3rd party devices are not subject to an across-the-board lock out from "Xi" LTE.
It still remains unclear (due to lack of testing) what will happen when an unlocked iPhone 5S or 5C is brought to Japan. iOS is well known for disabling the ability to easily alter APN settings depending on the SIM card that is inserted. As mentioned in comments on another post, the iPhone Configuration Utility can be used to create configuration files that add new APNs, and this is used by some MVNOs to work around disabled APN settings. However, as I noted earlier, the docomo carrier bundle appears to prevent attaching to 3G and LTE networks with anything other than the sp-mode APN. If this is the case, it could render the configuration utility useless if these same rules are included on unlocked iPhones as well.
The sp-mode APN is filtered by IMEI number on the "server side." Only whitelisted devices (sold by docomo) can connect.
The Shukan Ascii article compares different LTE SIMs in the Nexus 7. I'll briefly translate and summarize the contents in another post when I have more time.
In short, Docomo Xi SIMs work and are recommended by Shukan Ascii. You will need either:
A contract change was also required to get a KDDI SIM to work, but as I suspected, coverage is not the best (though better than expected in the Tokyo metro area). Emobile SIMs are not yet compatible pending a firmware update.
Shukan Ascii weren't able to get the Softbank LTE SIM to work with anything except regular 3G, but they admit they didn't try very hard. I know of at least one person claiming to have softbank LTE and an iPhone SIM card working with Android.
![]() |
| N7 APN settings (Image source). |
Until now, we couldn't rule out a "server-side" origin for the problems that unlocked iPhone 5 users encounter when trying to connect to docomo LTE. This was because, except for those provided by docomo, there were no other LTE devices that supported docomo's primary LTE frequency (Band 1, 2100 MHz). We had two variables (iOS software and docomo servers), and one equation (Apple hardware), which is unsolvable.
We can now safely say that 3rd party devices are not subject to an across-the-board lock out from "Xi" LTE.
Prospects for unlocked iPhone 5S and 5C in Japan
It still remains unclear (due to lack of testing) what will happen when an unlocked iPhone 5S or 5C is brought to Japan. iOS is well known for disabling the ability to easily alter APN settings depending on the SIM card that is inserted. As mentioned in comments on another post, the iPhone Configuration Utility can be used to create configuration files that add new APNs, and this is used by some MVNOs to work around disabled APN settings. However, as I noted earlier, the docomo carrier bundle appears to prevent attaching to 3G and LTE networks with anything other than the sp-mode APN. If this is the case, it could render the configuration utility useless if these same rules are included on unlocked iPhones as well.
The sp-mode APN is filtered by IMEI number on the "server side." Only whitelisted devices (sold by docomo) can connect.
Nexus 7 LTE SIM options
The Shukan Ascii article compares different LTE SIMs in the Nexus 7. I'll briefly translate and summarize the contents in another post when I have more time.
In short, Docomo Xi SIMs work and are recommended by Shukan Ascii. You will need either:
- a subscription to docomo's Mopera ISP (mopera.net APN) or
- a contract with a docomo MNVO.
A contract change was also required to get a KDDI SIM to work, but as I suspected, coverage is not the best (though better than expected in the Tokyo metro area). Emobile SIMs are not yet compatible pending a firmware update.
Shukan Ascii weren't able to get the Softbank LTE SIM to work with anything except regular 3G, but they admit they didn't try very hard. I know of at least one person claiming to have softbank LTE and an iPhone SIM card working with Android.
Tuesday, September 17, 2013
Nexus 7 LTE "currently" incompatible with emobile LTE
UPDATE: A firmware update will make the Nexus 7 compatible with emobile LTE.
From the Nexus 7 LTE purchase page, we have the following:
I have no idea how to interpret the word "currently" in this sentence. It could mean that this current hardware revision is incompatible, and if you buy it, you'll never have the option of emobile LTE. Or, it could be that there is currently a firmware incompatibility that a future OS update will fix.
From the Nexus 7 LTE purchase page, we have the following:
E-mobile band 3 (1800MHz) not currently supported.
I have no idea how to interpret the word "currently" in this sentence. It could mean that this current hardware revision is incompatible, and if you buy it, you'll never have the option of emobile LTE. Or, it could be that there is currently a firmware incompatibility that a future OS update will fix.
Nexus 7 LTE on sale in Japan
If you access the direct link for the LTE version on the play store, you can add the US version to your cart, and it indicates a 1-2 business days for shipping. However, on the official Japanese Nexus 7 site, it is currently listed as unavailable, though if you choose one of the other versions, you can change that for the LTE version (though the display language switches to English).
North America or European Version
Right now, only the US version is available from the play store in Japan. Both will work in Japan. Neither will grab the NTT Docomo's or KDDI's "800 MHz" bands. This is because there are a ton of bands that are called "800" (even "850" is sometimes called "800").
(Japanese frequency bands)
Docomo's "800" band is Band 19, and KDDI's is Band 18. The EU version supports Band 20, and there is not sufficient overlap on the downlink for this to support Docomo's low frequency (though the uplink does overlap). There is no overlap at all with KDDI at "800 MHz".
So, even though the EU version has "800 MHz" it won't have any benefit in Japan over the US version. This really won't matter at all for Docomo now because they don't seem to have deployed much LTE service on their "800 MHz" band.
North America: LTE Bands 1, 2, 3, 4, 5, 13, 17
Europe: LTE Bands 1, 2, 3, 4, 5, 7, 20
(To display the above information from the official Japanese Nexus 7 site, click 技術仕様, then スペック情報を表示)
Recommended to avoid KDDI
I stand by my earlier claim that the Nexus 7 will suck on KDDI for the immediate future. There are currently problems with Verizon in the US, another CDMA-2000 carrier, who just like KDDI, has rolled out an LTE network. However, the reason for the Verizon suckage is totally different from the reason why KDDI will suck.
[LTE is an evolution of W-CDMA which is in turn an evolution of GSM. CDMA-2000 is based on CDMA. W-CDMA and CDMA-2000 are both "3G" and they are totally different and incompatible technologies.]
Verizon has the proper network to support the Nexus 7, but they refuse to do so, citing the inability to activate a line of service for the device because it lacks a CDMA-2000 radio. If this is true, it's just temporary and mainly an excuse. At activation, the clerk fills out a form on a computer. There is a field for the CDMA radio ID, and if that field is blank, then the the form can't be submitted. Easy to fix — update the activation system.
There are two reasons to avoid KDDI with the Nexus 7 LTE:
- No CDMA-2000 radio in the Nexus 7 LTE, so the device can't fallback to "3G" when LTE is unavailable, which will be...
- All the damn time because KDDI's supported LTE network uses Band 1 (2100 MHz), and they recently got busted misrepresenting the coverage, stating Band 1 covered almost everyone when it in fact covered almost nobody at all.
Nexus 7 as an indicator of unlocked iPhone 5S/C performance with a Docomo Xi SIM
The iPhone 5 technically supported Docomo's Xi network (Band 1, 2100 MHz), but it never really worked. Using an unlocked device with a Docomo contract requires using Mopera as the ISP, as opposed to sp-mode. There has been speculation whether the problems with the Mopera APN were purposely caused by Docomo, Apple, or both.
I think there should be no problems with the iPhone 5S or 5C with a Docomo contract and Mopera as the ISP. I'd speculate that an Apple carrier.plist preference file was denying a connection to Xi with a Docomo (44010) SIM. I could be wrong.
If you can bring an unlocked Nexus 7 LTE to Docomo and use the Mopera ISP with no problems, then it shows that the Docomo is NOT actively preventing non-branded devices from accessing the Xi network.
Friday, August 30, 2013
Nexus 4 now available from Japanese electronics retailers
I figured it would be available through the play store, but that is not the case. It is available through Yodobashi camera, for a mere ¥49,800. Here's a list of reasons why we aren't interested. In case you do want to get one simply in Japan, try this.
Wednesday, August 28, 2013
Nexus 4 finally released in Japan. So what? Who cares?
It goes on sale tomorrow, but no one cares. There is no reason to buy this and many reasons not to:
- Jacked up price
- Old hardware
- No LTE, so it'll be slow
- No keitai osaifu, so no FeliCa mobile payments
- No Foma Plus area (800 MHz), so no reception with MVNOs in the countryside
Think about that, $249 for the 16 GB version would be ¥24,175. Sure round up to 3 man if you will but, 500 bucks? For that old thing? おま国だね。
(「売ってやるがお前の国が気に入らない」もしくは「お前の国には売ってやんねーよ」の略)
Sunday, August 25, 2013
LTE version of Google Nexus 7 will probably suck with KDDI, for now
UPDATE: KDDI has announced the sale of the wifi-only Nexus 7, and Engadget Japan has a more detailed article [J]. ¥39,800 for the 32 GB LTE model. Supported technologies and frequencies are:
4G LTE 700, 750, 850, 1700, 1900, 2100 MHz (Bands 1, 2, 4, 5, 13 17)
HSPA+ 850, 900, 1900, 2100, AWS (1700, 2100) MHz (Bands 1, 2, 4, 5, 8)
GSM 850, 900, 1700, 1900MHz
As suspected, it does not support CDMA-2000 and it does not support LTE Bands 11 and 18 (1500 and 800 MHz), which means that with KDDI, the only option will be Band 1 LTE, which in May had extremely limited coverage.
A new post on Engadget is, without any citing any sources, announcing that the LTE version of the Nexus 7 will be available in Japan within a few weeks. Unlike iPads sold in Japan, it will of course be unlocked ("SIM free") for use with any carrier. According to Mat Smith at Engadget:
Instead, what will most likely happen right now is, anytime you would see an "H" or a "3G" icon with a SoftBank or docomo SIM, you'll see a BIG RED X or 圏外 (out of area) icon with KDDI.
It could be as long as a month before it's available if the Engadget article is correct. We'll be sure to keep you appraised of carrier options. As we've long said, an MVNO is perfect for a second, data-only device.
4G LTE 700, 750, 850, 1700, 1900, 2100 MHz (Bands 1, 2, 4, 5, 13 17)
HSPA+ 850, 900, 1900, 2100, AWS (1700, 2100) MHz (Bands 1, 2, 4, 5, 8)
GSM 850, 900, 1700, 1900MHz
As suspected, it does not support CDMA-2000 and it does not support LTE Bands 11 and 18 (1500 and 800 MHz), which means that with KDDI, the only option will be Band 1 LTE, which in May had extremely limited coverage.
![]() |
| N7 LTE with KDDI? |
Google says it'll work on all three of Japan's major carriers (DoCoMo, Softbank and KDDI's au).Technically that is true, because all operate a Band 1 LTE (2100 MHz) network. However, if you intend to actually have a good mobile experience, we recommend staying away from KDDI, for now.
KDDI lacks the appropriate LTE coverage
You may recall that back in May, KDDI was caught greatly exaggerating their Band 1 LTE coverage. They claimed over 95% coverage, when in fact they had less than 15% and no plans for expansion. While KDDI is certainly working to increase coverage, that's just an amazing misrepresentation. KDDI does have the stated LTE coverage with Bands 11 and 18 (1500 and 800 MHz), but unless the modestly-priced N7 has some uber multiband LTE radio, the only way to support all Japanese carriers is with Band 1, and KDDI doesn't have the coverage.KDDI 3G is likely incompatible
If you use LTE in Japan and pay attention to the network displayed in the status or notification bar, you'll notice that it often falls back to "H" or "3G", indicating no LTE signal. The problem is that, unless the N7 LTE model includes a dual WCDMA/CDMA-2000 radio in addition to the LTE radio, there will be no fall back for KDDI users.Instead, what will most likely happen right now is, anytime you would see an "H" or a "3G" icon with a SoftBank or docomo SIM, you'll see a BIG RED X or 圏外 (out of area) icon with KDDI.
Wait for clarification
Of course anything is possible. Yes, LTE coverage will improve with time, and yes, Apple makes LTE hardware that fully supports SoftBank (WCDMA) and KDDI (CDMA-2000). Therefore it's not impossible for the N7 to do the same. It is just highly unlikely to get that in a budget tablet priced between 30,000 and 40,000 yen. Even a Japan-specific model seems unlikely at that price, given the total increase in manufacturing costs.It could be as long as a month before it's available if the Engadget article is correct. We'll be sure to keep you appraised of carrier options. As we've long said, an MVNO is perfect for a second, data-only device.
Saturday, August 10, 2013
Improved fix for Docomo MVNO data-only SIM "cell standby" battery drain
There are many data-only SIMs from a number of different Japanese MVNOs, including b-mobile. These may offer superior value over full price data plans from the big carriers. They're also great for a second device, like a 3G Nexus 7 tablet, and the prepaid versions are perfect for temporary visitors.
The problem is that these SIMs are provided by Docomo without a specific component that Android expects. This causes the phone to appear to not have a data connection at all (when it actually does), resulting in excessive battery drain as power to the radio is boosted while searching for a signal.
While the problem has finally been addressed in the Android source code, this will most likely only help for tablets that have no built-in phone capability. A normal Android phone with a data-only SIM provided by Docomo will most likely still not show signal bars. The previous fix required a fair bit of work. The new fix uses a simple Xposed module, so it can be performed entirely on the phone and can be easily disabled when you use a voice SIM.
If you read Japanese, visit oov's blog for a more detailed explanation.
I'd been running a very old beta of unofficial Cyanogen 10 on a Nexus S for about a year now. It was really out of date and buggy, but patching a freshly installed ROM was just a pain. You had to pull the framework.jar file to a computer, decompile it, patch it, recompile it, push it back, and hope everything worked. The previous batch file wasn't really usable because of a bug with virtual box and the Nexus S, and I never got around to making a batch shell script, so I had to do it all manually, which meant that I just never did it.
The problem is that these SIMs are provided by Docomo without a specific component that Android expects. This causes the phone to appear to not have a data connection at all (when it actually does), resulting in excessive battery drain as power to the radio is boosted while searching for a signal.
While the problem has finally been addressed in the Android source code, this will most likely only help for tablets that have no built-in phone capability. A normal Android phone with a data-only SIM provided by Docomo will most likely still not show signal bars. The previous fix required a fair bit of work. The new fix uses a simple Xposed module, so it can be performed entirely on the phone and can be easily disabled when you use a voice SIM.
If you read Japanese, visit oov's blog for a more detailed explanation.
![]() |
| Xposed Installer with oov's signal bars module installed and enabled. |
Requirements
- Android 4.03 - 4.3
- Root
- Xposed Installer (apk)
- Docomo Sim Patcher (Xposed module; apk)
Instructions
- Download and install the most recent version of the Xposed installer. The current version at the time of writing is
XposedInstaller_2.1.4.apk. - Launch the Xposed installed and tap "Install/Update".
- Reboot the phone
- Download and install the Docomo Sim Patcher module. The current version is
DocomoSimPatcher20130726.apk. - From the Xposed Installed tap the modules tab and enable the Sim Patcher module by tapping the checkbox.
- Reboot the phone.
I'd been running a very old beta of unofficial Cyanogen 10 on a Nexus S for about a year now. It was really out of date and buggy, but patching a freshly installed ROM was just a pain. You had to pull the framework.jar file to a computer, decompile it, patch it, recompile it, push it back, and hope everything worked. The previous batch file wasn't really usable because of a bug with virtual box and the Nexus S, and I never got around to making a batch shell script, so I had to do it all manually, which meant that I just never did it.
![]() |
| Flashing the latest CM based off 4.2.2 from the teamw.in recovery, which is really full of win |
![]() |
| HSPA and signal bars! |
Friday, March 29, 2013
JCI applies for MVNO access to both KDDI and Softbank
Japan Communications Inc. (JCI) announced (J) that they have applied for MVNO access to both KDDI and Softbank Mobile (SBM) networks.
The Japanese mobile landscape has change dramatically since March 2009 when JCI started offering b-mobile data products as an MVNO using NTT Docomo's (DCM) 3G FOMA network. Each mobile carrier now has a low-frequency spectrum allocation and offers LTE (currently 3.9G). This means that, technically, Softbank should suck a lot less than previously.
Accordingly, JCI is looking to expand into a domestic multicarrier MVNO. A combined SBM/DCM network would bring expanded Band 1 (2100 MHZ) FDD-LTE and 3G access with supplementing 800 and 900 MHz bands for better rural and underground penetration. Because many more overseas phones support 900 MHz than 800 MHz, this would be a good development for people who are not purchasing Japanese carrier-branded handsets, like most Nexus phones. This also moves closer in the direction of the original Nexus plan separating phone and carrier selection.
More on Japanese frequency bands.
Internationally, they could bridge the CDMA-2000 networks of KDDI and US Sprint, to which JCI already has access.
It will be interesting to see how this goes. Such developments are actually not AT ALL in the interest of the traditional carriers - the one's on top at least. JCI has had a bit of a rocky ride with DCM. To gain open access, they had to force MIC arbitration, and then later down the road, a billing disagreement arose. So it's only natural that JCI would look to expand it's options.
The Japanese mobile landscape has change dramatically since March 2009 when JCI started offering b-mobile data products as an MVNO using NTT Docomo's (DCM) 3G FOMA network. Each mobile carrier now has a low-frequency spectrum allocation and offers LTE (currently 3.9G). This means that, technically, Softbank should suck a lot less than previously.
Accordingly, JCI is looking to expand into a domestic multicarrier MVNO. A combined SBM/DCM network would bring expanded Band 1 (2100 MHZ) FDD-LTE and 3G access with supplementing 800 and 900 MHz bands for better rural and underground penetration. Because many more overseas phones support 900 MHz than 800 MHz, this would be a good development for people who are not purchasing Japanese carrier-branded handsets, like most Nexus phones. This also moves closer in the direction of the original Nexus plan separating phone and carrier selection.
More on Japanese frequency bands.
Internationally, they could bridge the CDMA-2000 networks of KDDI and US Sprint, to which JCI already has access.
It will be interesting to see how this goes. Such developments are actually not AT ALL in the interest of the traditional carriers - the one's on top at least. JCI has had a bit of a rocky ride with DCM. To gain open access, they had to force MIC arbitration, and then later down the road, a billing disagreement arose. So it's only natural that JCI would look to expand it's options.
Wednesday, February 6, 2013
Unlocked Nexus 7 3G tablet coming to Japan
This will be just perfect with a prepaid data SIM. The 32 GB Nexus 7 3G version will be on sale in Japan from 2/9 at major electronic stores for ¥29,800. That is by far the best deal in Japan for a 3G tablet. It uses a micro SIM card.
List of b-mobile SIMs here.
This would also be perfect for Ingress.
Friday, November 16, 2012
本当にドコモのベースバンド(radio.img)で上書きする必要はあるのか?
Editors Note: See below for English.
ドコモ版Galaxy Nexus(SC-04D)がJB4.1にアップデートされたタイミングで手元のデバイスをJB 4.2 (JOP40C)にアップデートしました。
Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet)
このROMに含まれていたradio.imgのベースバンドはi9250XXLH1で、いつもはflash_all.shでアップデートすることはなくベースバンドはドコモバージョンを残しておくか上書きするのですが、今回はせっかくなのでグローバル版のベースバンドとドコモ版のベースバンドの通信状況を比較してみました。
試しに焼いてみたのは下記radio.img。
なので結論からいうと、気にせず最新のブートローダやradio.imgを焼いても問題がなさそうです。これで迷うことなくROM焼きができますね。
I have 2 Samsung Galaxy Nexus handsets, and I compared the radio baseband version of those two after updating on the same day. I always leave the docomo radio because I assumed the baseband that the carrier releases includes better support for local radio frequencies or optimized for bandwidth / speed / packet size.
But after comparing, I couldn't find a significant difference between the following basebands:
ドコモ版Galaxy Nexus(SC-04D)がJB4.1にアップデートされたタイミングで手元のデバイスをJB 4.2 (JOP40C)にアップデートしました。
Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet)
このROMに含まれていたradio.imgのベースバンドはi9250XXLH1で、いつもはflash_all.shでアップデートすることはなくベースバンドはドコモバージョンを残しておくか上書きするのですが、今回はせっかくなのでグローバル版のベースバンドとドコモ版のベースバンドの通信状況を比較してみました。
試しに焼いてみたのは下記radio.img。
- 2012.06.10: SC04DOMLE3 radio.
- 2012.11.13: JRO03C.SC04DOMLK2 build. (yakjusc, ドコモ版)
- 2012.11.13: i9250XXLH1 radio. (takju, アメリカ版, 下のスクリーンショット)
なので結論からいうと、気にせず最新のブートローダやradio.imgを焼いても問題がなさそうです。これで迷うことなくROM焼きができますね。
Comparing Galaxy Nexus radio (baseband) between docomo vs global
I have 2 Samsung Galaxy Nexus handsets, and I compared the radio baseband version of those two after updating on the same day. I always leave the docomo radio because I assumed the baseband that the carrier releases includes better support for local radio frequencies or optimized for bandwidth / speed / packet size.
But after comparing, I couldn't find a significant difference between the following basebands:
- 2012.06.10: SC04DOMLE3 radio.
- 2012.11.13: JRO03C.SC04DOMLK2 build. (yakjusc, docomo version)
- 2012.11.13: i9250XXLH1 radio. (takju, US version, screenshot above)
Monday, October 22, 2012
Review of Nexus 7
Note: This post was originally published at Janne in Osaka and has been slightly adapted for reposting here.
I've had the Nexus 7 - Googles new 7" tablet - for a month now, and it's a nearly perfect device. It's not my first tablet; I've used a budget Android 2.3-based tablet for the past year. It was cheap, limited and full of flaws, but I did find it surprisingly useful as a book reader. The N7 removes every one of those flaws and annoyances. I've also used and admired the iPad, but find the Nexus 7 to be the better device for me in many ways.
I bought the Nexus 7 through the Google Play store soon after it went on sale in Japan. The price includes tax and shipping, and it also included a ¥2000 credit in the Play store — most of which I spent on Final Fantasy III. Delivery took just a few days. (Note that the Google Play credit offer ended this past September. Also, see comment below for more information when buying multiple Nexus 7s.)
The size of the N7 is just right. Width, height and weight is similar to a paperback, but it's very thin, and with its curved edges and sloping, grippy back it's easy to hold and use in one hand for long periods. It goes easily into a coat or jacket pocket, and it even fits in my jeans back pocket when I need both hands for the food tray at lunch. A larger device is too big and heavy to use at the table, on the train, reading in bed or looking thing up on the street. Of course, a larger device may be very good for other uses — I don't recommend taking the Nexus 7 into the bath.
The Nexus 7 is wifi only (though a 3g version is rumoured). It keeps the price down and battery life up, of course, and you don't depend on a network carrier with opinions on what you can and can't do with your device, but it can be a little limiting. Fortunatly it is easy to tether the N7 to my phone when I need a network connection on the go. I have a Galaxy Nexus on the NTT DoCoMo Xi network, and tethering is allowed. Once you've set it up ut works fairly well. Turn on "wifi hotspot" on the phone (you need stock Android, not NTTs version) and the tablet automatically finds and connects to it. I have a 7Gb monthly data limit, but I've yet to actually use the entire monthly quota.
I got a slim book-style cover, but while it may make sense for a large tablet it makes the Nexus 7 clumsier than I like. Fortunately the N7 just snaps in and out of place, so I use the cover as a carry sleeve and stand — the front flap folds back to become a support — but remove the tablet for use. The N7 really shines when used without a cover, so I'll probably replace the cover with a slip-in pouch later on.
The N7 is a "nexus" device. That means that it's Google-branded and runs the latest version of Android. It gets new updates as soon as Google releases them — we got 4.1.2 just last week — not when the maker or carrier decide to update it (if they ever do). Nexus devices are meant to showcase the Android system, and Android 4.1 on the Nexus 7 is a pleasure. It's smooth, beautiful and fast. The UI just gets out of the way, and is far more polished than earlier versions.
Up until now, many cheap tablets don't actually have the Google Play store, a crippling omission. The success of the full-featured, fully-supported Nexus 7 will hopefully have an impact far beyond its user base. The Nexus 7 — at the same price level as many budget tablets — will set a new minimum standard and weed out most of the horrible, barely usable products currently out there. Any maker who wants to stay in this market will have to at least match the Nexus 7 for basic features or find themselves without customers.
Battery life is good — really good, in fact, with the latest update. As a test, I took the N7 off the charger (standard micro USB - thank you for that) on Tuesday morning, then used it as I normally do until the battery ran out. A typical day I read my RSS feeds during my morning commute, read a book during lunch and at night, and occasional web surfing, games (I finished "Anomaly: Warzone Earth"1 on my way home Tuesday night), reading and dictionary use throughout the day.
I disconnected the N7 Tuesday morning. It reached 4% charge and a final power warning on Thursday night, after two days and 15 hours; that is 63 hours of use on one charge. This is fairly light use, but typical for me on weekdays (I spend most of my time working after all). I've made no attempt to extend the battery life; If I turn off GPS, lower the screen brightness, turn off wifi when I'm not using it and don't play games I could probably use it another half a day on a charge.
What's the use for something like this? Anything that involves mostly consuming things rather than creating it. It's perfect for reading books; email and web surfing (Firefox runs great); forums and chat; social sites such as Facebook, Google+, twitter and so on. The screen is fine for viewing photos (though that's one area where a larger screen could be handy) and movies. It's an excellent gaming system; I've got Minecraft, Final Fantasy III, Broken Sword and a dozen Humble Bundle games on it and they all run beautifully. It excels at video chats. And for all the talk about the lack of "tablet optimized" applications on Android, I've yet to find an app that doesn't work great on the Nexus 7.
The weak point for tablets is creating content. Writing is clumsy and slow on a touch screen, and not comparable to a real keyboard. Short emails, chats and posts are fine. Longer texts soon become cumbersome; I'm drafting this blog post on the N7 at a cafe in Namba, and this is about as long a text I would ever want to write without a real, physical keyboard. Small portable keyboards are not a real solution; they're almost as hard to write with as an on-screen one. Android has voice input of course, but it's too slow and still too error-prone to replace typing, and you usually can't dictate things aloud in public.
The price is an overlooked feature of the Nexus 7. At just below 20k yen it's half the price of similar size Android tablets and substantially less than an iPad. That's cheap enough that you can buy one on impulse, rather than after careful decision, and cheap enough to easily replace it if it would break. An expensive tablet is something you feel you must be careful with; something you need to protect and coddle, wrap in a protective case and keep safe in a bag. The N7, on the other hand, I can treat like a paperback or noteblock rather than a computer. I simply throw in my bag and use in a crowd without worry that it'll get bumped, scratched, spilled on or dropped. It's light and well-built and if it breaks then getting a new one would be no big deal.
I've got the 16Gb model, though an updated model with 32Gb memory is coming. You might be tempted to wait for the update, and I wouldn't blame you of course. But I've installed all the apps, books and other data I use, and it takes up less than 3Gb on my 16Gb Nexus 7. You can reportedly connect memory sticks and USB hard drives to it using an OTG USB adapter. That would give you essentially unlimited storage, but you apparently need to install extra software for that, and may need to root your Nexus 7 as well.
Google and Asus have really hit the bulls-eye with the Nexus 7. There's a few quirks and niggles — it can't connect to ad-hoc wireless hotspots, and there's no Swedish keyboard dictionary — but it doesn't detract from it being a nearly perfect device.
I've had the Nexus 7 - Googles new 7" tablet - for a month now, and it's a nearly perfect device. It's not my first tablet; I've used a budget Android 2.3-based tablet for the past year. It was cheap, limited and full of flaws, but I did find it surprisingly useful as a book reader. The N7 removes every one of those flaws and annoyances. I've also used and admired the iPad, but find the Nexus 7 to be the better device for me in many ways.
I bought the Nexus 7 through the Google Play store soon after it went on sale in Japan. The price includes tax and shipping, and it also included a ¥2000 credit in the Play store — most of which I spent on Final Fantasy III. Delivery took just a few days. (Note that the Google Play credit offer ended this past September. Also, see comment below for more information when buying multiple Nexus 7s.)
The Nexus 7. Some light reading and web browsing during lunch. it's easy to hold and use in one hand, and if a few drops of soup would hit the screen, it's nothing to worry about. This kind of situation is where a tablet this size excels.
The size of the N7 is just right. Width, height and weight is similar to a paperback, but it's very thin, and with its curved edges and sloping, grippy back it's easy to hold and use in one hand for long periods. It goes easily into a coat or jacket pocket, and it even fits in my jeans back pocket when I need both hands for the food tray at lunch. A larger device is too big and heavy to use at the table, on the train, reading in bed or looking thing up on the street. Of course, a larger device may be very good for other uses — I don't recommend taking the Nexus 7 into the bath.
The Nexus 7 is wifi only (though a 3g version is rumoured). It keeps the price down and battery life up, of course, and you don't depend on a network carrier with opinions on what you can and can't do with your device, but it can be a little limiting. Fortunatly it is easy to tether the N7 to my phone when I need a network connection on the go. I have a Galaxy Nexus on the NTT DoCoMo Xi network, and tethering is allowed. Once you've set it up ut works fairly well. Turn on "wifi hotspot" on the phone (you need stock Android, not NTTs version) and the tablet automatically finds and connects to it. I have a 7Gb monthly data limit, but I've yet to actually use the entire monthly quota.
I got a slim book-style cover, but while it may make sense for a large tablet it makes the Nexus 7 clumsier than I like. Fortunately the N7 just snaps in and out of place, so I use the cover as a carry sleeve and stand — the front flap folds back to become a support — but remove the tablet for use. The N7 really shines when used without a cover, so I'll probably replace the cover with a slip-in pouch later on.
The N7 is a "nexus" device. That means that it's Google-branded and runs the latest version of Android. It gets new updates as soon as Google releases them — we got 4.1.2 just last week — not when the maker or carrier decide to update it (if they ever do). Nexus devices are meant to showcase the Android system, and Android 4.1 on the Nexus 7 is a pleasure. It's smooth, beautiful and fast. The UI just gets out of the way, and is far more polished than earlier versions.
Up until now, many cheap tablets don't actually have the Google Play store, a crippling omission. The success of the full-featured, fully-supported Nexus 7 will hopefully have an impact far beyond its user base. The Nexus 7 — at the same price level as many budget tablets — will set a new minimum standard and weed out most of the horrible, barely usable products currently out there. Any maker who wants to stay in this market will have to at least match the Nexus 7 for basic features or find themselves without customers.
Battery life is good — really good, in fact, with the latest update. As a test, I took the N7 off the charger (standard micro USB - thank you for that) on Tuesday morning, then used it as I normally do until the battery ran out. A typical day I read my RSS feeds during my morning commute, read a book during lunch and at night, and occasional web surfing, games (I finished "Anomaly: Warzone Earth"1 on my way home Tuesday night), reading and dictionary use throughout the day.
Nexus 7 battery graph just as it reached 4%, giving me 2 days and 15 hours of use. Wifi was constanly enabled, as was account synchronization and GPS.
I disconnected the N7 Tuesday morning. It reached 4% charge and a final power warning on Thursday night, after two days and 15 hours; that is 63 hours of use on one charge. This is fairly light use, but typical for me on weekdays (I spend most of my time working after all). I've made no attempt to extend the battery life; If I turn off GPS, lower the screen brightness, turn off wifi when I'm not using it and don't play games I could probably use it another half a day on a charge.
What's the use for something like this? Anything that involves mostly consuming things rather than creating it. It's perfect for reading books; email and web surfing (Firefox runs great); forums and chat; social sites such as Facebook, Google+, twitter and so on. The screen is fine for viewing photos (though that's one area where a larger screen could be handy) and movies. It's an excellent gaming system; I've got Minecraft, Final Fantasy III, Broken Sword and a dozen Humble Bundle games on it and they all run beautifully. It excels at video chats. And for all the talk about the lack of "tablet optimized" applications on Android, I've yet to find an app that doesn't work great on the Nexus 7.
You can connect a keyboard to the Nexus 7 with an OTG USB adapter. Here I've connected a Happy Hacking Professional JP keyboard2 to the Nexus 7 and it works just fine. Even such a small keyboard dwarfs the N7, though, and as the small size of the tablet is a main feature, adding a bulky keyboard sort of defeats the purpose. If you need to write a lot, then do yourself a favour and bring a real laptop.
The weak point for tablets is creating content. Writing is clumsy and slow on a touch screen, and not comparable to a real keyboard. Short emails, chats and posts are fine. Longer texts soon become cumbersome; I'm drafting this blog post on the N7 at a cafe in Namba, and this is about as long a text I would ever want to write without a real, physical keyboard. Small portable keyboards are not a real solution; they're almost as hard to write with as an on-screen one. Android has voice input of course, but it's too slow and still too error-prone to replace typing, and you usually can't dictate things aloud in public.
The price is an overlooked feature of the Nexus 7. At just below 20k yen it's half the price of similar size Android tablets and substantially less than an iPad. That's cheap enough that you can buy one on impulse, rather than after careful decision, and cheap enough to easily replace it if it would break. An expensive tablet is something you feel you must be careful with; something you need to protect and coddle, wrap in a protective case and keep safe in a bag. The N7, on the other hand, I can treat like a paperback or noteblock rather than a computer. I simply throw in my bag and use in a crowd without worry that it'll get bumped, scratched, spilled on or dropped. It's light and well-built and if it breaks then getting a new one would be no big deal.
I've got the 16Gb model, though an updated model with 32Gb memory is coming. You might be tempted to wait for the update, and I wouldn't blame you of course. But I've installed all the apps, books and other data I use, and it takes up less than 3Gb on my 16Gb Nexus 7. You can reportedly connect memory sticks and USB hard drives to it using an OTG USB adapter. That would give you essentially unlimited storage, but you apparently need to install extra software for that, and may need to root your Nexus 7 as well.
Google and Asus have really hit the bulls-eye with the Nexus 7. There's a few quirks and niggles — it can't connect to ad-hoc wireless hotspots, and there's no Swedish keyboard dictionary — but it doesn't detract from it being a nearly perfect device.
#1 A neat idea, well executed. The game's a bit short, but as it starts to feel a little repetitive towards the end, it's really just the right length. Another unexpected Humble Bundle gem.
#2 The HHKB keyboards have full-size keys in a very compact layout. Perfect for a cluttered, busy desk. There's two model lines: the "Lite", which is mechanically a normal keyboard with the compact layout; and the "professional" with much higher quality build and better tactile feel. If you have the money to spare, get a "professional" model.
Wednesday, October 17, 2012
29 ตุลาคมนี้รอลุ้นกันว่า Google จะเปิดตัวอะไร
Google เริ่มส่งทำเนียบเชิญชวนสื่อมวลชนให้มาทำข่าวกับงาน event ที่จะจัดขึ้นที่เมือง New York ในวันที่ 29 ตุลาคมนี้ แต่ยังไม่มีรายละเอียดอะไรมากนักนอกจาก Google กล่าวแต่เพียงว่า "สนามเด็กเล่นกำลังจะเปิด" (The playground is open)
ซึ่งเชื่อได้ว่าน่าจะเป็นงานเปิดตัวมือถือ Nexus ตัวใหม่จาก LG หลังจากที่มีภาพหลุดออกมามากมายก่อนหน้านี้ แต่เชื่อว่าแฟนๆ Android (และตัวผม) หวังว่า Google คงจะไม่เปิดตัว Nexus จาก LG เพียงค่ายเดียว หวังว่าจะมีรายชื่อของค่ายอื่นๆ อย่างเช่น Sony ที่มีข่าวหลุดมาก่อนหน้านี้มาเปิดตัวมือถือ Nexus พร้อมๆ กัน
นอกจากนี้เราอาจจะได้เห็นแท็บแล็ต Nexus รุ่น CPU แบบ Single Core ที่ปรับราคาลงมาเหลือแค่ $99 เปิดตัวในงานนี้ หลังจากที่มีข่าวลือก่อนหน้านี้ว่า ASUS เตรียมปล่อยแท็บแล็ต Nexus ราคาถูก ($99) ภายในไตรมาส 4 ปีนี้
ที่มา Android Central
Tuesday, October 9, 2012
[ข่าวลือ]ภาพหลุดล่าสุดของเครื่องต้นแบบ Optimus Nexus และสรุป specs อย่างคร่าวๆ
หลังจากที่มีภาพหลุดของมือถือปริศนาที่คาดกันว่าน่าจะเป็น Optimus Nexus ของ LG จาก XDA ในวันนี้ก็มีรูปหลุดอีกชุดจากนาย 4shael นอกจากนี้นาย 4shael ได้ออกมาให้รายละเอียดเพิ่มเติมผ่าน XDA และได้ตอบข้อสงสัยของที่มาที่ไปของรูปนี้ และเปิดเผยรายละเอียด specs อย่างคร่าวๆ ของ Optimus Nexus
นาย 4shael ได้กล่าวว่า รูปที่เค้า post ลงไปนั้นเป็นเพียงแค่เครื่องต้นแบบ (Prototype) ของ Optimus Nexus เท่านั้น จากภาพของเครื่องต้นแบบล่าสุดทำให้เราได้เห็นว่าด้านหลังของ Optimus Nexus นั้นคล้ายคลึงกับ LG Optimus G ของเครือข่าย Sprint มากดังภาพข้างบน
ส่วนด้านหน้าจะคล้ายๆ กับ Galaxy Nexus จะต่างกันก็ตรงลำโพงเสียงสนทนาด้านบนเท่านั้น ส่วน specs คร่าวๆ มีดังนี้
- CPU: quad core ARMv7 1.5GHz
- RAM: 2 GB
- Memory: 8GB (no SD slot)
- GPU: Adreno 320
- Android version: JellyBeanMR1
- Kernel 3.4.0
- Screen: 768x1184 (320 dpi)
- Camera: 8 MP
ซึ่ง specs ดังกล่าวค่อนข้างจะตรงกับข่าวลือที่หลุดมาก่อนหน้านี้ ส่วนในเรื่องหน่วยความจำภายในที่เราเห็นว่าทำไมมีแค่ 8 GB เท่านั้น เพราะ Optimus Nexus จะมีอยู่ 2 รุ่นคือ 8 และ 16 GB ตามข่าวลือก่อนหน้านี้
ที่มา XDA ผ่าน Android Central
Monday, October 8, 2012
[ข่าวลือ] หรือว่านี้จะเป็นรูป Nexus ตัวใหม่จาก LG
วันนี้มีรูปหลุดมาจาก XDA เป็นรูปมือถือปริศนาจาก LG ที่มีรูปทรงคล้ายๆ กับ LG Optimus G โดยคาดว่ามันน่าจะเป็น Nexus ตัวใหม่ที่ LG จะเปิดตัวร่วมกับ Google ในปลายเดือนนี้
แต่จากรูปด้านบนของมือถือปริศนา พบว่ามันยังไม่ได้มาพร้อมกับ Android เวอร์ชั่นใหม่อย่าง 4.2 ยังคงเป็น Android 4.1 อยู่ แต่มีจุดที่น่าสังเกตุอยู่ตรงที่ code name ที่มีชื่อว่า Mako โดยชื่อ code name ของมือถือปริศนานี้ค่อนข้างจะมีทิศทางไปในทางเดียวกันกับชื่อ code name ของ Galaxy Nexus เพราะก่อนที่จะเปิดตัว code name ของ Galaxy Nexus ก็ใช้ชื่อปลาเช่นเดียวกัน
แต่ถึงแม้ว่ารูปที่หลุดมามันจะมีส่วนที่คล้ายคลึงกันกับ Optimus G อยู่บ้าง แต่ตำแหน่งการวางกล้องและ LED Flash ค่อนข้างจะไม่เหมือนกันกับ Optimus G ซักเท่าไร ทำให้เชื่อได้ว่าฮาร์ดแวร์ด้านในอาจจะไม่เหมือนกับ Optimus G ซะทีเดียว ทิ้งท้ายด้วยภาพทั้งหมดที่หลุดมาหลัง Break
ที่มา Android Central
ปล. ทำมันมันคล้ายๆ กับมือถือรุ่นใหม่ที่เพิ่มแถวใหม่มาแถวนึง....
Subscribe to:
Posts (Atom)









































