Related
A. Phone, Router & Firmware info:
1. My Phone : MotoG XT1033 Asia [Nov 2013 Model INDIA]
2. My WiFi Router : DSL-2750U_ADSL_Modem (U1, IN_1.08)
3. Root/Mod Status : No Mods, Not Rooted (Normal)
4. Old Firmware : Lollipop 5.0.2 [220.21.28] Stock
5. New Firmware : Lollipop 5.1 [221.21.56]
6. Update method :
a) File "Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip" downloaded in PC. (file md5-checksum = 94856deaaa3f23a1163120b362cbaef10, 208.7 MB )
b) File copied to phone's sdcard/Internal memory.
c) "apply update from sdcard" thru phone's BootLoader/Recovery menu.​effect same as update thru OTA file, but safer.
7. Updated Date : Sep 12, 2015.
8. Status : Update successfully installed.
9. Post update actions : wiped cache partition (thru fastboot & recovery menu)
-------------------------------------------------------------------------------
B. Issues with 5.0.2 solved in 5.1 (Sep-2015), as experienced/Tested by me
1. WiFi re-connection issues after disconnect, with Channel-13 or auto-channel, earlier in 5.0.2.
(eg: when enforced WiFi disable/enable or by moving out/in of Wifi range).
These issues are solved in 5.1, even with Channel-13 selected (either manually or auto).
2. When an incoming call, is not picked-up even after screen timeout time (say 15 secs), then ringing stops, & display switches off. Accepting the call after this is very difficult. This issue is solved in 5.1
3. Gallery Application fails/ Misbehaves.
Albums/Videos, shows blank squares/Tiles. Problem temporarily solves on reboot, but only for one invocation. This issue is solved in 5.1
4. Two Photo icons in App Drawer. This issue is solved in 5.1.
5. The phone lagging response issues seems to be improved, if not altogethor solved.
At least it is more responsive (response time faster), and smoother to operate, than in 5.0.2.
But the final verdict on this can only be provided after some extended time of usage (say few weeks or more).
Earlier with 5.0.2 it was horrible, especially as time went by, and I was planning to revert to stock Kitkat-4.4.4.
So I want to know others experience regarding phone resposniveness w.rt 5.0.2 in 5.1
6. I am not facing any early Battery drainage issues in 5.1 w.r.t 5.0.2, as reported by some others.
In my opinion, if only it is better. But not sure (feedback only with couple of days usage)
Anyway surely not very bad than earlier.
7. CPU SpyPlus now reports 300 Mhz as min scaling freq, as against 787 Mhz in 5.0.2.
I am sot sure how significant this is. But some people reported this as a problem in 5.0.2
The highest reported freq is 1190 Mhz.
Incidentally some people are referring to this update as 5.1.1 instead of 5.1, here in these & related forums.
I am only seeing Android Version as 5.1 in : Settings --> About Phone Menu.
with Baseband version = MSM8626BP_1032.3116.98.00R and
Kernel version = 3.4.42-g89906d6
So I dont know whether Motorola is released or releasing any newer version 5.1.1 other than this one.
I think people are confusing this with 5.1.1.
I would like to hear other experts comments regarding this.
Even i updated my moto g XT1033 (India) model yesterday. Was running on CM12.1 before so had to flash 5.0.2 stock and then got the OTA update directly.
The changes are minor but what matters is performance and RAM Management and Battery Life.
1. The performance as mentioned by the OP has really improved. Device feels snappier and more usable then 5.0.2
2. I see many people even after updating to complaining about memory leaks but personally in my device i have 300-400mb of memory free (I have downloaded and updated all the apps and many apps like facebook whatsapp etc are running in background)
3. Another major change that i was able to notice was the battery life has improved (comparing to both cm12.1 based /AOSP based/ 5.0.2 stock) specially the stand by time went to bed with 90% and woke up with around 84% (where in cm12.1 it was used to be 70%)
am personally happy with this update even though it was too late. I'd appreciate if motorola could push the 5.1.1 update too since that does not contain any major changes (security patches).
PS: YOUR BOOTLOADER WILL GET UPDATED TO 41:1A this doesn't mean you cannot flash or root. You can flash and root by the same procedures but make sure to use the latest TWRP AND SUPERSU ZIPS.
Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!
Do you experience any battery drain bug such as Google Play Store or the infamous mobile standby drain ? Would love to hear your feedback about this. Last time I've tried some 5.1 custom roms they had this bug, which prompted me to switch back to 4.4.4.
Thanks.
Hi guys, thanks for your reports.
Could you please comment about the "mobile data active" issue? Is it solved or, at least, mitigated in 5.1?
Thanks!
enban said:
Hi guys, thanks for your reports.
Could you please comment about the "mobile data active" issue? Is it solved or, at least, mitigated in 5.1?
Thanks!
Click to expand...
Click to collapse
no its solved in android 6.0. Its google bug.
That problem solved too
Mustajab Is'haq said:
Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!
Click to expand...
Click to collapse
Screen goes to black problem is solved too. now we can use adaptive brightness on an lower the brightness to minimum..
gmp009 said:
no its solved in android 6.0. Its google bug.
Click to expand...
Click to collapse
Well... It seems like I'm going to skip 5.1 also...
Thanks!
E.
How to root it ? Any link for updated supersu and TWRP is helpful.
enban said:
Well... It seems like I'm going to skip 5.1 also...
Thanks!
E.
Click to expand...
Click to collapse
Well, there won't be official 6.0 for 1g Moto G, if you want to stay in stock firmware, you should update.
moralesnery said:
Well, there won't be official 6.0 for 1g Moto G, if you want to stay in stock firmware, you should update.
Click to expand...
Click to collapse
Obviously I was talking about custom ROMs. CM13, maybe? ?
performance upgraded too. its about 4 days I'm running it and found no issue. except battery. I just expected more battery backup.
ant24x7 said:
How to root it ? Any link for updated supersu and TWRP is helpful.
Click to expand...
Click to collapse
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM
thuva06 said:
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM
Click to expand...
Click to collapse
You only need to install TWRP on your device and enter recovery mode.
Once there, you go to "Reboot" and then "System", TWRP will ask if you want to root and will run SuperSU script.
When you boot to Android again, TWRP will update itself over Play Store.
thuva06 said:
Even i updated my moto g XT1033 (India) model yesterday. Was running on CM12.1 before so had to flash 5.0.2 stock and then got the OTA update directly.
The changes are minor but what matters is performance and RAM Management and Battery Life.
1. The performance as mentioned by the OP has really improved. Device feels snappier and more usable then 5.0.2
2. I see many people even after updating to complaining about memory leaks but personally in my device i have 300-400mb of memory free (I have downloaded and updated all the apps and many apps like facebook whatsapp etc are running in background)
3. Another major change that i was able to notice was the battery life has improved (comparing to both cm12.1 based /AOSP based/ 5.0.2 stock) specially the stand by time went to bed with 90% and woke up with around 84% (where in cm12.1 it was used to be 70%)
am personally happy with this update even though it was too late. I'd appreciate if motorola could push the 5.1.1 update too since that does not contain any major changes (security patches).
PS: YOUR BOOTLOADER WILL GET UPDATED TO 41:1A this doesn't mean you cannot flash or root. You can flash and root by the same procedures but make sure to use the latest TWRP AND SUPERSU ZIPS.
Click to expand...
Click to collapse
thuva06 said:
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM
Click to expand...
Click to collapse
Wow! I was worried that when the next update will come I need to flash stock recovery.
I don't know why but my Moto G with 30-35 apps installed (Facebook,messenger, swiftkey etc...) sometimes it's just freeze for like 10-15 seconds and that wasn't happend in 5.0.2.
Is Static Wi-Fi working?
Mustajab Is'haq said:
Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!
Click to expand...
Click to collapse
It has been fixed in 5.1 for me. I put slider to the extreme left and there was flickering it screen going black at all.
Moto G XT1033 @ Android 5.1
I have some doubts. If you all can help me would be very helpful.
I'd like to install the last ROM of @darkera13.
And I read in its english thread at samsungvn this info below:
1. Fix game crash, play flac media, video lag
2. Fix hotspot, wifi direct
3. Sound S7
4. SamsungIMEv2_5 (Fix download language)
-
1. Well... All that 4 fixes is all for "APD3.3"? I couldn't get this information there.
2. Then I have to install in this order: 1, 2, 3 and 4?
3. And about the features, I also could read "Camera 5.0". What that means? That means stock camera of the Android 5.0 (Lollipop)?
Thanks! =)
If the fixes are downloadable then they're for current rom. He removed previous version's fixes.
He has just fixed hotspot for example but when he released 3.3 is not yet fixed. So it's for the current version.
It's a note 5 camera?
Sent from my SM-N920C
I recently bought myself a Redmi Note 3 Pro Special Edition (Kate) for its ability to run an official build of CM13 and, importantly, because Kate offers Band 20 support - a major advantage for UK usage.
As you may realise, getting CM13 onto Kate is somewhat more complex than getting it running on Kenzo. This is due to both the bootloader not being able to be unlocked officially and also because the Radios in Kate are different to those in Kenzo.
After figuring everything out over the weekend, I managed to flash the Official Nightly CM13 onto my Kate device & everything ran perfectly!
I wrote up the process in my Blog in quite a bit of detail, so feel free to have a read if you wish to install CM13 on your Kate edition of the Redmi Note 3.
@mwarner mmm online you can find an version of CM13 for kate
http://blog.yam.com/amjads/article/171744431
Inviato dal mio Z2plus utilizzando Tapatalk
Naphtha said:
@mwarner mmm online you can find an version of CM13 for kate
Click to expand...
Click to collapse
My tutorial is very thorough - every step is taken into account, taking a phone as it would be out of the box running MIUI to having a fully working CM13 installed. If it wasn't complicated, I wouldn't have written a tutorial .
Thanks for the info though - the text and the ROM is all in Chinese but may be of use to someone.
Thank you for work. I will trying it till my kate comes. Doesn't band 20 and 8 work?
Gesendet von meinem Redmi Note 3 mit Tapatalk
mwarner said:
My tutorial is very thorough - every step is taken into account, taking a phone as it would be out of the box running MIUI to having a fully working CM13 installed. If it wasn't complicated, I wouldn't have written a tutorial .
Thanks for the info though - the text and the ROM is all in Chinese but may be of use to someone.
Click to expand...
Click to collapse
I don't believe is only in Chinese. Usually CM is multilanguage.
Inviato dal mio Z2plus utilizzando Tapatalk
A very well written and comprehensive guide, thanks! I've been seeing so many support requests all over the place that i'm still a bit hesitant to flash CM13. Have you noticed /ANY/ issues with hardware support? Dual sim, cameras, FP-reader? Is there anything that works worse on CM than MIUI7 stable?
Thanks again for a good guide, subscribed to your blog too
Sujejsjejej said:
Thank you for work. I will trying it till my kate comes. Doesn't band 20 and 8 work?
Click to expand...
Click to collapse
The Special Edition (Kate) phone supports the following bands:
LTE B1/2/3/4/5/7/8/20/28 ( 2100/1900/ 1800/ 1700/ 850/ 2600/ 900/ 800/ 700MHz)
Kenzo does not support Bands 2, 20 and 28.
kissamopo said:
A very well written and comprehensive guide, thanks! I've been seeing so many support requests all over the place that i'm still a bit hesitant to flash CM13. Have you noticed /ANY/ issues with hardware support? Dual sim, cameras, FP-reader? Is there anything that works worse on CM than MIUI7 stable?
Thanks again for a good guide, subscribed to your blog too
Click to expand...
Click to collapse
I must admit that the Note 3 is not my main phone - a Xiaomi Mi Max contains my primary SIM at the moment - so I have not tested it as much as I would like.
At this point (only having had the phone on CM13 for a few days) I have experienced one bug where I used the fingerprint sensor to unlock & the device unlocked, but to a black screen. Turning the screen off with the power button and then unlocking again with the fingerprint resolved this. I have only seen this once, but I did see it.
Generally, everything seems to work well - performance is great (smoother than MIUI) and both cameras and the fingerprint sensor work as expected. I haven't tried Dual SIM, or indeed a MicroSD card in the device, so I can't comment on this.
The bottom line is that it is a little too early for me to say whether I would use CM13 on the Note 3 if it was my primary phone. A safer bet is to use MIUI and set the phone up to turn off some of the oddities of MIUI. I posted about how I set up my phone here:
http://mikestechlife.blogspot.com/2016/10/guide-to-setting-up-xiaomi-miui-phone.html
On my main Mi Max I use Xiaomi.eu weekly on MIUI 8 with it set up as outlined above. CM13 only has partial supported on the Mi Max, so I don't want to go down this route with my Max.
That's quite the tutorial! Lots of good information there.
1. Xiaomi only support bootloader unlocking on Chinese Developer firmwares. There is NO Chinese firmware available for Kate - only Global ROMs. It is therefore impossible to officially unlock a Kate phone.
Click to expand...
Click to collapse
Not true, at least in my experience. I've officially unlocked my Kate using global dev MIUI8 v6.10.13. Followed these steps.. This particular MIUI release comes with a setting in the dev menu to check for unlocked bootloader and other things.
Now, I'm hoping I wasn't an exception, and officially unlocking Kate has now become just as easy for everyone.
Also, there's a ROM that's quite CM13-like and officially supports Kate and its radio. I come from a 2013 Moto G running CM13 nightlies and I don't miss CM13 after using this for a few days in my Kate. The experience is almost the same, and at least on my Kate, everything's running fine.
Too bad that Xiaomi is playing part lottery when making the phone, seems they can't be bothered to update their sources for all the part providers they're using. I guess we can't complain much when a phone of this caliber is so affordable.
I noticed that Xiaomi.eu have produced a build for Kate this week:
https://xiaomi.eu/community/threads/6-10-27.35843/
Cheers bud great tutorial.
I was using the latest Global Dev Rom and after the first boot loading TWRP it gave me a prompt for password. I could not access storage. Just fully wiped the device with TWRP/Advanced/Wipe Data and did the install. CM13 just booted on my device with a locked bootloader.
Biggie ups!
Does this work with cm 14 too?
Gesendet von meinem Redmi Note 3 mit Tapatalk
There is a developer ROM for kate? Would this not work for official unlock?
http://en.miui.com/download-301.html#449
Kate bootloader can be unlocked officially, I did it with mine on official global dev rom.
adamdabadboy said:
Kate bootloader can be unlocked officially, I did it with mine on official global dev rom.
Click to expand...
Click to collapse
how?
iakoboss7 said:
how?
Click to expand...
Click to collapse
go to en.miui.com/unlock/ and apply to unlock
Use updater to flash global dev rom
Settings -> additional settings -> developer options
enable OEM unlocking
mi unlock status -> register phone
enable usb debugging (not sure if necessary)
reboot into fastboot mode
use mi unlock tool to unlock bootloader
last time i tried the "mi unlock status -> register phone" it faild (and i tried many times and did allot of restarts). i tried it on 6.10.13, what version did you use?
Thanks for the Tutorial. When i flashed the rom with Alka Recovery, i had the error message Encryption was interrupted and can't be completed. With the ZCX Recovery it starts normally.
Has anyone tried this with CM14 or a 7.0 rom?
iakoboss7 said:
last time i tried the "mi unlock status -> register phone" it faild (and i tried many times and did allot of restarts). i tried it on 6.10.13, what version did you use?
Click to expand...
Click to collapse
I used 6.10.13, I'm not sure why you had that problem
Hi,
I got a Nokia X6 TA-1099 in September 2018, with Custom Oreo Rom (locked!) and rooted.
I unlocked it, loaded the Global Oreo one for Nokia 6.1 Plus few months ago and prompted to upgrade to Pie 3.45 right after. Once I did it, I noticed screen issues (much large screens, going out of the edges basically). One of the members of this forum told me that this happens when the SKUID is CN instead of WW. I checked and mine was CN. The phone is also recognised as TA-1103 now.
since I need a locked phone for banking, certified etc... I downgraded to Oreo Security Patch August 2018 and locked the phone "forever". I then disabled the automatic updates.
do you know if newer releases of Pie (like V3.54H which I am prompted about) will "fit" my screen properly even though I have SKUID CN? Or shall I just wait for Android Q that perhaps does not have this issue?
I am worried I will need to downgrade and I won't be able to do it anymore.
Thanks!
The SKUID will always trouble you. Because starting with Pie. parts of the OS rely on the SKU to enable/disable certain services. You're better off with either of the two:
1. Be on CN ROM and keep your CN SKUID.
2. Be on WW ROM but change your SKUID to WW.
3. Stay on Oreo (bonus lol)
The broken Status bar will continue to bug you when on Pie with CN SKUID. Also, some system features will remain missing/broken, including double-tap to wake.
Hi
Can I change the SKUID to WW now that I am on Oreo 8.1 August 2018 patch?
I am not finding any info to confirm this, but I appears that Nokia is now allowing unlock.
I would like to:
- change SKUID to WW
- relock
- upgrade to Pie and follow all the future automatic updates
Do you think this is possible?
Thanks for your help as always.
Nokia does not allow unlock. You will need to resort to the paid methods.
Sent from my Nokia 8.1
Please can you send me some links so I can proceed accordingly?
singhnsk said:
Nokia does not allow unlock. You will need to resort to the paid methods.
Sent from my Nokia 8.1
Click to expand...
Click to collapse
hello, can you please suggest me some place to go for this?
Thanks
mpiulg83 said:
hello, can you please suggest me some place to go for this?
Thanks
Click to expand...
Click to collapse
techmesto.com,
I did it with my nokia and it was 100% safe.
JavaDroid_ said:
techmesto.com,
I did it with my nokia and it was 100% safe.
Click to expand...
Click to collapse
+1
Did for my Nokia 6.1 Plus also.
Thanks guys
I am on Oreo 8.1 August 2018 patch. I was told unlock the phone is not possible anymore.
However, I just contacted singhnsk privately and Techmesto via email. we'll see what can be done.
singhnsk said:
The SKUID will always trouble you. Because starting with Pie. parts of the OS rely on the SKU to enable/disable certain services. You're better off with either of the two:
1. Be on CN ROM and keep your CN SKUID.
2. Be on WW ROM but change your SKUID to WW.
3. Stay on Oreo (bonus lol)
The broken Status bar will continue to bug you when on Pie with CN SKUID. Also, some system features will remain missing/broken, including double-tap to wake.
Click to expand...
Click to collapse
Is it possiable that i still need CN SKUID(for my wifi and signal) but with Lineage OS experience?
i really enjoy the Lineage OS or Evolution X or Resurrection-Remix, but i cant find the CN version ROMs like this....
Apologies for cryptic title. My Mi A1 has multiple issues and a patchy update history. I don't know how to narrow this down to a single, simple question. Hope someone can help to make sense of this.
History: Bought new with stock Android One, Oreo. Few months later updated to Android One, Pie (official update). This caused big problems with wifi (connections constantly dropped and VERY slow downloads). Thought about reverting to Oreo, but decided to change to Lineage (which at the time was Oreo). So I downgraded from Android One Pie to Lineage 15 (Oreo). Generally worked OK, but with 3 big problems:
1. No sound during phone calls (I can't hear them, they can't hear me). Found a workaround involving editing the build.prop file (sorry, can't post link), but fix is temporary and needs regular re-boots.
2. Fingerprint sensor not working (no options to set fingerprint).
3. Camera app lost functionality related to dual lens.
I subsequently updated from LOS 15 (Oreo) to LOS 16 (Pie). Issues still there.
I wonder if I have some missing/incompatible vendor firmware components, but I don't really understand how this works. If I download and install, say, a LOS rom, does it contain EVERYTHING my phone needs to work, or do I need to already have some proprietary bits somewhere on the phone?
Is my best bet to start afresh (clean slate) and if so what would you recommend? Any help/insight greatly appreciated!
Hey pal, the Android Pie Firmware has some kind of anti-roll back protection, so when you install a non-pie ROM such as LOS 15 using Pie Firmware you'll have that problems like no-fingerprint, no incall audio, etc. If you install an Oreo Firmware with an Oreo ROM, you'll have fingerprint but no IMEI/Signal (and other problems).
You have 2 options:
1) Update your firmware to the latest Pie version and install a ROM like Pixel Experience or HavocOS (both Pie) and you're set, IMEI, Signal, Audio and Fingerprints will be working OK.
2) Install the latest Pie compilation using MiFlash and leave it stock.
Greetings.
Thanks for prompt reply! Can you spell something out for me please?
Regarding 1) I have already updated to LOS 16, which is Pie. Is that what you meant by "update your firmware to the latest pie"? Or do you mean a stock firmware? If the latter, then I could find a MIUI rom (from en.miui.com) but not Android One.
Regarding 2) Again, by "latest Pie compilation" do you mean the stock rom, like the MIUI mentioned above?
Thanks