[Q] Basic question seeking clarification. - G 2014 Q&A, Help & Troubleshooting

I'm wondering why it appears so difficult to get hotspot or tethering working on the Moto G? The basic hardware is essentially identical to the Moto X, particularly the wireless chip hardware, yet Moto X has hotspot but G doesn't. More than that, SOME Gs, especially outside US, has the function. Further still, the G HAD the function in the US for a bit before google decided to arbitrarily cripple the hardware via broken software. What I wonder is why aren't devs (apparently) taking software/drivers from Gs that have the hotspot driver function and simply adopting it to any/all Moto Gs? It isn't a matter of the hardware not supporting it, it is purely driver based (and there are already examples of functional drivers out there to use).
So, I'm wondering why it appears to be such an issue? I rooted my G in hopes of sidestepping the artificial crippling of the hardware only to find that rooting did me no good whatsoever. Surely there's a hack out there to allow for altering settings? I've been looking for a ROM to use too only to find nothing. Can y'all please explain the issue? If I could, id install a ROM from Europe, one wherein google didn't pointlessly cripple the hardware. The Moto G is particularly irritating to me because it is, otherwise, a big upgrade from my previous phone - more powerful, more feature-full EXCEPT hotspot. The phone my G replaced was a much lessor android phone yet had full hotspot capability. It was replaced by what I thought would be a better phone because it got wet and no amount of drying by any method rescusitated it.

Moderator move the thread?
After I posted my question I saw the info that this section isn't for questions and thread creators aren't empowered to move their threads so...can a moderator plz move this to the moto g questions area?

Tethering is disabled if you bought the phone from a carrier. If you bought it unlocked then it should be there.
You can always flash a custom ROM to get the tethering back

Related

G Watch R Disassembly

After all this debate on whether this thing has WiFi support or now, I decided to tear mine apart to provide some better shots of the internals than the crap iFixit teardown.
Tonight, I'll be seeing someone to see if we can get that metal shroud off without damaging the board.
Disassembly Album
Edit: Updated the album with closeup shots of the ICs
Current parts list:
SK Hynix H9TU32A4GDMC-LRKGM - PoP 512 MB LPDDR2 + 4 GB eMMC (same as G Watch)
Qualcomm PM8226 - Power Management IC (same as G Watch)
Qualcomm WCD9302 - Audio Codec (not in G Watch?)
AKM AK8963 - Compass IC (same as G Watch)
Synaptics S3526B - Touch controller (different model in G Watch)
InvenSense MPU-6515 (?) - 3 axis gyro and accelerometer (same as G Watch)
Broadcom BCM4343WKUBG - Bluetooth 4.2 and WiFi b/g/n (different from G Watch)
cgutman said:
After all this debate on whether this thing has WiFi support or now, I decided to tear mine apart to provide some better shots of the internals than the crap iFixit teardown.
Tonight, I'll be seeing someone to see if we can get that metal shroud off without damaging the board.
Disassembly Album
Click to expand...
Click to collapse
Thats awesome man! Looking forward to the pics.
I got the shielding off and as LG claimed, the Broadcom chip (BCM4343WKUBG) supports WiFi. Pics are in my album.
It's also very likely that their "no antenna" excuse is total BS. Given that this specific BCM4343 SKU is specifically designed for WiFi+BT in wearables, Broadcom would be stupid to require 2 antennas in such a small device when 1 would suffice.
Adding further evidence for WiFi support is commits from LG employees working specifically on BCM4343 WiFi support in Android 5.1:
https://android.googlesource.com/pl...an/+/1a8bf7a905f23a1f2948dcbc6a101b443233917e
https://android.googlesource.com/pl...an/+/69ffc0b6785198631bf617a6bad44c51c997fd49
Good job!
Yet LG are still denying that the R is capable of utilizing wifi at all. I guess if it is just LG dragging their feet and the hardware is all there, hopefully someone will port the Urbane kernel for us. Fingers crossed.
finalbillybong said:
Yet LG are still denying that the R is capable of utilizing wifi at all. I guess if it is just LG dragging their feet and the hardware is all there, hopefully someone will port the Urbane kernel for us. Fingers crossed.
Click to expand...
Click to collapse
Actually theyve yet to come with an official answer. Which is weird.
I've said it once and I'll said it again, none of the LG customer service reps know the answer to the wifi question. You can call and ask and get a different answer everytime. If the hardware does in fact exist, as the evidence does indicate, then either LG is purposely disabling it to push sales of their watch urbane or we will get the update. We will find out soon enough. If it turns out that WiFi support is purposely omitted then I trust the hive mind that is XDA will figure out how to get it working.
novaIS350 said:
I've said it once and I'll said it again, none of the LG customer service reps know the answer to the wifi question. You can call and ask and get a different answer everytime. If the hardware does in fact exist, as the evidence does indicate, then either LG is purposely disabling it to push sales of their watch urbane or we will get the update. We will find out soon enough. If it turns out that WiFi support is purposely omitted then I trust the hive mind that is XDA will figure out how to get it working.
Click to expand...
Click to collapse
Apparently LG has tweeted about it not having the correct hardware. But i agree with you. These people are probably regular everyday idiots hired just to tweet or answer phones and they have no idea what theyre actually saying. Anyway, i just made this post in another thread about this: forum.xda-developers.com/showpost.php?p=60384338&postcount=65
Google are responsible for all current software on Wear devices, LG shouldn't have anything to do with whether the update has wifi or not, if the hardware is capable.
very good job
ChrisM75 said:
Google are responsible for all current software on Wear devices, LG shouldn't have anything to do with whether the update has wifi or not, if the hardware is capable.
Click to expand...
Click to collapse
Nope, lg can retouch the update a bit before releasing it!
Great thread - the news we've been hoping for!
Very good job !!
thx cgutman :good:
m i n a r said:
Nope, lg can retouch the update a bit before releasing it!
Click to expand...
Click to collapse
A bit, doesn't mean remove features.
In a frustrated attempt at an explanation regarding wifi capability of R, one of LG's European workers, when confronted with the FCC report that says the clock has everything you need for wifi, it said that there are differences between the US and european versions and in particular one of the differences would be even wifi (how convenient)!
So the question is ...
Can anyone confirm if there really is a difference between the versions!
Obiwanhug said:
In a frustrated attempt at an explanation regarding wifi capability of R, one of LG's European workers, when confronted with the FCC report that says the clock has everything you need for wifi, it said that there are differences between the US and european versions and in particular one of the differences would be even wifi (how convenient)!
So the question is ...
Can anyone confirm if there really is a difference between the versions!
Click to expand...
Click to collapse
Bs on bs, that's what i think!
This is definitely the last LG product I will purchase. It's complete and utter BS that they can't get this right.
m i n a r said:
Bs on bs, that's what i think!
Click to expand...
Click to collapse
Totally agree with you! However in the end it will be the LG that will decide whether appeals to customers who purchased the Watch R or will be greedy and will want to foist the same device but masi polished for another 100 euros / dollars!
However should be aware that displease old customers will not certainly draw new or maintain they already have !!!
novaIS350 said:
This is definitely the last LG product I will purchase. It's complete and utter BS that they can't get this right.
Click to expand...
Click to collapse
Did you buy the watch on the promise that it would some day support WiFi? probably not..
Do you expect these customer support people that you've been contacting to really have a clue as to what the future plans of LG are concerning this watch?
Is LG being unusually quiet about this? Yes! But they are probably just taking the "safe" approach.
People complain about features they were never even promised. I can only imagine the feedback they'd get if they made a statement that they couldn't back up.
Just my opinion...
townsenk said:
Did you buy the watch on the promise that it would some day support WiFi? probably not..
Do you expect these customer support people that you've been contacting to really have a clue as to what the future plans of LG are concerning this watch?
Is LG being unusually quiet about this? Yes! But they are probably just taking the "safe" approach.
People complain about features they were never even promised. I can only imagine the feedback they'd get if they made a statement that they couldn't back up.
Just my opinion...
Click to expand...
Click to collapse
The question is...
If the Watch R really haves the capability of Wi-Fi, why LG don't allow? What they earn? People with a 6 months old device leave it and buy almost the same but more expensive? I don't believe!
But in other hand if the watch really don't have the capability... then bad luck!
The problem is that according with a lot of information and even the Watch release presentation that don't seems to be the case! And like others brands (LG is not alone in this behavior) they are being grief!

Status of LineageOS 14.1 for H811 (LG G4 T-Mobile)

LineageOS apparently de-certified the H811 build of LOS 14.1 in late November because of some bug(s) in that series. The last available nightly is dated 2017-11-28.)
But I can't figure out where to go to find out what the problem was or what the status is. Any pointers would be appreciated, thanks.
(My G4 has run flawlessly with absolutely no bootloop or hardware failure of any kind, ever, so I'd really hope it will continue to be supported in LOS)
I think I found the reason for the cessation of builds for h811 at the moment - a bug with storage encryption on at least 2 variants of LG G4:
https://jira.lineageos.org/browse/BUGBASH-498
Perhaps I should start a thread in the LOS section to track the status? Don't really want to have to create an Lineage dev account just to track this bug...
Exabyter said:
LineageOS apparently de-certified the H811 build of LOS 14.1 in late November because of some bug(s) in that series. The last available nightly is dated 2017-11-28.)
But I can't figure out where to go to find out what the problem was or what the status is. Any pointers would be appreciated, thanks.
(My G4 has run flawlessly with absolutely no bootloop or hardware failure of any kind, ever, so I'd really hope it will continue to be supported in LOS)
Click to expand...
Click to collapse
You can use my unofficial LOS on h811 since today
To put it simply, the G4 sucks. No one is interested in developing or fixing bugs for such an unpopular and buggy device that few still use or buy. The main issue here is the bootloop caused by poorly assembled motherboards. The emmc and RAM/Qualcomm Snapdragon CPUs were not well soldered onto the motherboard, and/or overheated and expanded. LG has neglected to fix their defective G4, V10, and Nexus 5x (deplorable that a Google phone has to be significantly defective) beyond their warranty period, given this issue they should extend it. And finally LG's stupid bootloader locks on anything but the H815 and H811 models. Why does AT&T and Verizon get to decide the software that's loaded onto my device? Heck, my ISP in the forseeable future won't require my computer to have a locked bootloader. Why are Mobile Network providers raping consumers and becoming more than a service provider? They're becoming hardware and software manufacturers, it's not a good thing for them to step in like that. IMO a community developed ROM will always be better than anything LG could ever make, their ROMs are and will be forged by us. Last time I remembered, ALL G3 variants were bootloader unlocked with the stock 10a/b/c/d/x firmwares, and can be modded out-of-the-box. I also promise that LG and all carriers will no longer provide security updates to the G3, G4, and V10. Verizon and AT&T's phones will not get nougat as promised. blobs
patato21 said:
To put it simply, the G4 sucks. No one is interested in developing or fixing bugs for such an unpopular and buggy device that few still use or buy. The main issue here is the bootloop caused by poorly assembled motherboards. The emmc and RAM/Qualcomm Snapdragon CPUs were not well soldered onto the motherboard, and/or overheated and expanded. LG has neglected to fix their defective G4, V10, and Nexus 5x (deplorable that a Google phone has to be significantly defective) beyond their warranty period, given this issue they should extend it. And finally LG's stupid bootloader locks on anything but the H815 and H811 models. Why does AT&T and Verizon get to decide the software that's loaded onto my device? Heck, my ISP in the forseeable future won't require my computer to have a locked bootloader. Why are Mobile Network providers raping consumers and becoming more than a service provider? They're becoming hardware and software manufacturers, it's not a good thing for them to step in like that. IMO a community developed ROM will always be better than anything LG could ever make, their ROMs are and will be forged by us. Last time I remembered, ALL G3 variants were bootloader unlocked with the stock 10a/b/c/d/x firmwares, and can be modded out-of-the-box. I also promise that LG and all carriers will no longer provide security updates to the G3, G4, and V10. Verizon and AT&T's phones will not get nougat as promised. blobs
Click to expand...
Click to collapse
No one buys any smartphone more than 12-18 months after its introduction today because that's about the market lifespan of a smartphone now. (With the possible exception of Apple) So people not buying them any more isn't really the reason one older device gets more support than another older device.
Yes, I recognize that LG had production problems with the G4 but the one I'm typing this on atm has been 100% flawless for at least 9 months now and I'm not even the original owner.
Re: locked bootloaders and carrier control over software, little to none of that is LG's fault, talk to your politicians about having created a business-environment in the USA that panders to corporations and sticks it to the customers.
Re: your PC, I suggest you learn about Microsoft's "secure boot" swindle that is part of most PCs sold retail in the US these days if you really think Wintel boxes are a fountain of user freedom, lol.

Nexus 6 to G5S plus, thoughts?

Hi all, ready to move on from my Nexus 6. Would love some pro's/con's from this community on how happy I'd be to make this switch. I've ready G5S plus give great bang for buck and has a good modding community which is a must have for me.
Any thoughts on making the G5S + my primary phone??
All I can say is I love mine and I came from a Nexus 4.
You calling it "moving on" rather than an upgrade is pretty accurate. It's an upgrade overall, but not as much as you might think for a 3-year newer model. You need to realize that the Nexus 6 was a $700 phone (when first released) and the G5S Plus is a $300 phone. The improvements with the G5S Plus is that it's 64-bit hardware, even though the stock ROM is 32-bit and most people highly suspect the Oreo update (if it ever comes) will also be 32-bit. Because it's not a Nexus, the G5S Plus has a microSD slot so you have the potential to have a lot more storage, but the camera hardware is not great (despite the fancy dual lens). The camera works out if flash a 3rd-party 64-bit ROM and use the Google Camera, but I can't do that (see below). On the US model there is no NFC, so no AndroidPay (I didn't care, but some might).
My personal experience with unlocking/rooting/ROMing the two phones has been very different when I thought it would be far more similar (since they're both Motorola). The best way to describe the process with the G5S Plus is kludgy, and it's not all that easy to go back to stock since there are no official, signed stock images for the G5S Plus. Stock updates (even security updates) are few and far between. This just isn't a Nexus. The Nexus 6 had a lot more 3rd-party development options and support, and the G5S Plus has now been out long enough that what you see here now is probably all we're going to get. I haven't had much luck with the existing 3rd-party ROMs working well with my carrier (Sprint). The ROM features seem to mostly work fine, but the carrier settings don't work at all on Sprint, and when I try to change them I completely lose my mobile signal and don't get it back until I reset network settings. This makes it highly questionable how successful I'll be with these 3rd-party ROMs when roaming, even just locally in the USA. I have no faith in these ROMs working when roaming internationally. The reason why I'm encountering the same problem with all of these 3rd-party ROMs is I'm pretty sure all of them are using the same base from the same developer. So if you're like me and have a problem with any of these ROMs, you'll likely have the same problem with all of them.
Overall? I wish I'd gotten the Pixel 2 XL. But although I can afford to pay $1000 for a phone, I'm not going to because that's just ridiculous. I've looked around...thoroughly. There just isn't really anything out there any better featured that doesn't at least cost $700, so I'm still using the G5S Plus. I may be a little more limited than you because I'm Sprint (CDMA) whereas people on GSM networks might have more options. I've had to go back to stock rooted 7.1.1, which isn't horrible but not really ideal (and not what I'm used to with the Nexus 6). But I can't successfully get the G5S Plus back to stock unrooted to even take security updates, so I'm on the October security patch. When the stock Oreo update is released, I don't see me being able to take that either. I'm hoping that development community here will put out a flashable stock Oreo ROM then, but then I'll still be in the same boat with OTA Oreo security patches. This is a very capable phone with some nice features, but if you liked being a flashaholic on the Nexus 6, I wouldn't necessarily expect the same experience on the G5S Plus.
FYI, I'm not a developer, but far from being a noob. I've been rooting/ROMing/modifying Android devices (HTC, Samsung, Motorola) since the Froyo days. I would have to rank this phone as the most difficult Android device I've owned to do all that.
I can tell a slightly more upbeat story.
Migrated from a Nexus 6P which I loved dearly, but after spending a small fortune on battery replacements realised it was time to call it a day.
I am very pleased with the Moto. Honestly? I see very little functional difference between this and the 6P in my use case. The screen is slightly smaller. From a Nexus 6 it would be more noticeable I suspect. I recovered the real estate by turning off the nav bar and using fingerprint swipe gestures (which are nice once you get used to them). It is fast and fluid in use and I genuinely don't see anything different in use from the 6P from the end user's perspective. I use my phone mainly for work and the intertubes so not fussed about the camera. When I point it at things what ends up on the phone looks vaguely like what I pointed the phone at. That fulfils my criteria although I have recently started tinkering with some of the hacked GCam apps from the Pixel just for the "because I can" factor.
Internetpilot is right, the development scene is a fraction of what you'd see on a Nexus or Pixel. However, as a long standing flashaholic from the very early days of Android (HTC Magic anyone?) I found myself more than happy with rooted stock for a long time. Moto's stock rom is bloat free and works extremely well. I did try a couple of custom roms early on and found them not as smooth or stable as the stock one, so reverted and ran stock for about six months until very recently.
Internetpilot is right in that it is very difficult to get the thing back to a stock state once you start tinkering. I was in a similar boat whidh meant I couldn't accept OTAs. This was what finally prompted me to try the custom ROM scene again. It has improved in leaps and bounds since last year. Currently running Pixel Experience Oreo and it is rock solid. It's been a keeper for me. But it is worth bearing in mind that if you root then you will be on your own and probably end up forced down the custom ROM boat as I have. It would be a lot easier if Moto had flashable stock images, but it's not a show stopper if your plan was basically to go custom from the get go.
I can't agree with Internetpilot hat it's any major difficulty to unlock, root and flash. You go to Moto's website, you get an unlock code, you unlock your bootloader, you flash TWRP and away you go. Not significantly different from the process I've done on most phones I've had since the HTC Magic days. I've had Sonys that were more grief than this.
I can't speak for any of this CDMA stuff as I am not transatlantically challenged . I've had no problems with my own network provider (Vodafone UK) or roaming on any rom. But if you're stateside clearly that's something you'd need to consider. It's worth also noting that most of the community are in developing countries eg India where this phone has quite a bit of a foothold.
But generally this is a lot of phone for the money. It's a good time for the low-mid range Android phone market. I chose this phone because I didn't want to pay stupid money for a top end device and I really didn't like the 18:9 form factor. The Moto is generally the same form factor as my beloved 6P and the price is right. Now if you have a bit more to spend, the Oneplus 5T looks interesting and perhaps might have a more Nexus-like community. Other options in the Moto's price range include the Honor 7X which I might well have bought instead if it'd been available when I bought the Moto. I am also intrigued by some of the Xiaomi devices. But the tl;dr version? The Moto is highly commended. Would buy again.
Wow, thank you both for your elaborate remarks, really helpful and exactly what I was looking for. So yes I've been rotting for awhile as well (since HTC Eris) and have had some pleasant and less than pleasant experiences. Some earlier Moto droids were obv torture to get unlocked, while the Nexus 6 was certainly quite the opposite.
I'm disappointed to hear dev is so sparse, as the usual spots (Android Police, Auth, 9to5Google, etc) all said this was the best phone to look at for modding after Pixel 2 & OnePlus given it's ease of unlock and robust community. Honestly I find such great value in the ability to unlock, root etc that I do plan on doing so right away and it heavily influences my purchase decision. I suppose if I wanted just one locked in phone experience I would just go to an IPhone, but I want to be able to customize.
From a hardware perspective, I appreciate both viewpoints. Yes don't like the thought of losing screen real estate but not sure what the alternative is as other options I've looked at are 18:9. Played with the 2 XL today and was shocked at the lack of screen space in landscape. Web browsing already is limited given ads in landscape and it seems even worse in the 18:9 ratio. As to software, Internetpilot certainly makes me wary as I'm on VZW, another CDMA. Personally I've generally had a good experience with my network relative to friends of mine on Sprint, but persisting network issues concern me as I also want a smooth experience when on a different rom.
As to the financial point, agreed on both sides. Certainly bang for the buck kind of phone. There are better out there but I too can't stomach the thought of dropping a grand on these, just seems a bridge too far given where the prices were just a few years ago. But at the same time I really don't want to have a phone that is nothing but hassle and constant re-flashes. I'd like to find a rom that is stable, supported and simply support it and continue on.
Well, I thank you both for the time and opinions, really helpful to be sure. Internetpilot I'll certainly dig for other posts with similar concerns but if you care to share some you've come across I'll def have a look.
Thanks again to the both of you.
To clarify a bit -- the phone is no more difficult to unlock, root, and ROM than the Nexus 6. However, the reason I gave it my "most difficult" award (haha) out of all the phones I've owned, is that gaining root on a device that isn't very well supported in the 3rd-party development arena doesn't really do you much good if you can't unroot just as easily. I can't get SuperSU working on this device, so I had to resort to Magisk (which is new to me -- I've always used SuperSU) and when I perform the unroot option via the Magisk Manager app, I end up with a "bad key" error on the bootloader screen and the ROM won't boot. The same thing happens if you try to restore all the original stock partitions via TWRP. Restoring any one of the boot, recovery, and one other partition that I can't remember results in the same "bad key" error. It's gotten to the point that even though I want to get it back to stock unrooted so I can grab the latest OTA security update (and eventually get the stock Oreo update when it's released), I really hate to mess with it. It's not because I think I'm going to brick it -- it's just I know I'll end up spending hours without a phone while trying to get passed that stupid "bad key" error, and then when I finally do that, my data partition will re-encrypt so I'll lose everything and have to set the phone up all over again. Since I'm trying to get it back to stock unrooted, I can't just easily restore my apps/data with Titanium Backup (because I don't have root), so everything is either gone or all messed up, so it's a huge pain in the posterior. Both versions of TWRP we have available for this phone don't reliably backup/restore the data partition either, so you can't rely on TWRP to backup everything if you want to mess around with flashing other ROMs, etc. That's what I mean by most difficult out of all the devices I've owned. When a new ROM is released, you really have to think twice before just backing everything up and flashing it to try it. You just might end up without a working phone for 3 or 4 hours before you get everything restored back to a working state.
I don't think you'll have a problem with Verizon. I know several people who are running 3rd-party Oreo ROMs on this phone on Verizon and they don't have the same issues I do with the carrier settings blowing everything up. It just seems to be Sprint. And to clarify my problems on Sprint, the stock rooted (and unrooted) ROM works flawlessly on Sprint. I can change the carrier settings, update my PRL, even use the "secret" dial codes to change APN settings, etc. But I can't do any of that on any of these 3rd-party Oreo ROMs. The carrier settings default to Global (which strangely works on Sprint's CDMA network), but I can't change Preferred Network Type to "LTE", can't turn on data roaming, can't change the CDMA roaming mode, and can't update the PRL or device config. Like Loccy said, all of the development on this phone is from India where the phone is very popular, so they probably don't know anything about Sprint. But even with these ROMs working fine on Verizon, how long will they be updated/supported? The Moto G6/G6 Plus is likely going to be released during the Summer, and that will probably fizzle the minimal development that the G5S/G5S Plus currently has. I think Moto is going to likely support this phone longer than the 3rd-party development community will.
Yeah, those are all great points. I agree with the heart of your contention in that I absolutely love tinkering with my phone, trying new ROMs, seeing what sort of added and better features I can apply to my device, making it mine instead of having some company tell me what to do with my device. But conversely I absolutely dread those lost days when something doesn't go right and you spend days and weeks scouring the forums and doing research just to get your phone to what you deem to be an operable state. Certainly that can be part of the fun of owning a device like this but with multiple kids, job, and other life stuff getting in the way and not being an engineer by trade or anything technology related it does become a bit of a hindrance at times. I suppose I just want my cake and to eat it too, but that's not the landscape that Android lives in right now.
I also take your point that this is a mid range device that has Hardware limitations and a development community that will only support it for so long. I'd like to make a choice that has a little more longevity built into it like the 4+ years I got out of my Nexus 6.
I think I may actually go for a verizon pixel to xl give it all these conversations, can get one on payment for less than 500 out the door. While I absolutely recognize that I will probably greatly miss having total control over my device, I really like the Android software landscape and it still offers a much richer customization experience than does an iPhone.
Look, really appreciate all your feedback and thoughts. Will let you know some months down the road if the decision was a good one. Cheers.

Moto G5S plus does not support Miracast, can i root,unlock and unroot it ?

I recently bought a TV which only supports miracast, but i just now found out that most new stock android type devices do not support miracast, so i was thinking, can i root my phone, enable Miracast protocol and Unroot the device back again ?
Sorry, may be a noob question but that's what i am right now about this topic
If not, alternatives are always welcomed.
P.S- if i don't screw around with a rooted phone too much is it safe to keep a phone rooted for always ? i may end up giving this phone to my sister who is very bad at handling devices software wise and am afraid she may brick it.

Why are one power forums so dead??

Its such nice phone. Still the forums are so dead. Any specific reason?
Port Moto camera 2
Can anybody port latest Moto camera 2 to Moto one power with all working features.
thedemon786 said:
Its such nice phone. Still the forums are so dead. Any specific reason?
Click to expand...
Click to collapse
I think the reason behind this is that we are not getting what we want like Google camera with all features working perfectly ( like night sight,slow motion, photo booth as these all features are not working smooth or even not working and pictures also take too much time to load),Moto camera 2, Moto actions,etc.
And another reason I think is due to the reason that we all are very much disappointed with Motorola as we have a stock camera which is different from other Moto's camera and it missing many basic features and Mop does not have Moto actions like other Moto's phone and even Moto does not taking us seriously.
[email protected] said:
I think the reason behind this is that we are not getting what we want like Google camera with all features working perfectly ( like night sight,slow motion, photo booth as these all features are not working smooth or even not working and pictures also take too much time to load),Moto camera 2, Moto actions,etc.
And another reason I think is due to the reason that we all are very much disappointed with Motorola as we have a stock camera which is different from other Moto's camera and it missing many basic features and Mop does not have Moto actions like other Moto's phone and even Moto does not taking us seriously.
Click to expand...
Click to collapse
I agree.
Motorola has kind of abandoned any kind of support or even basic features of Android One on Moto One Power.
They will just provide security updates from Google as per the agreement, but they will rarely fix any serious issue related to the phone.
I had a broken display once, the official service centers told me that data would be reset.
I fixed it from a local store and the data was intact, and the price was almost 70% cheaper than the official solution even though the parts were the same.
Their recent Android 10 update is riddled with problems, the battery works like a 3000mAh now, and my phone is currently going through a "System UI" issue, for which the support which I am getting is zero.
Even the official forums would never help at all.
Don't believe me?, check their website.
I guess they are just fooling customers in the name of 'Android One'
I have learned not to look for support from Motorola anymore, and stay away from Motorola Brand as a whole. :good:
I was considering this phone, have had many moto phones in the past, currently have a z2 play and it is time to upgrade. I am no longer considering this phone, and am disappointed in moto's support of their phones in general as they seem to be digressing in all aspects of non high end phones/customers. They should drop the motorola moniker that they play on and just call it a lenovo. They ain't made in the USA motorola anymore.

Categories

Resources