My LG G5 (H850) and me - My experience and advice - LG G5 Guides, News, & Discussion

Dear friends,
Here is what I found after one full year of using this device. This is not intended to be used as installation guide. Please reffer ro appropriate thread for that.
One confession: I'm a flashoholic.
- It has a great camera setup. The images are rarely rivaled even by Galaxy S8+
- Removable battery!
- It has 3 main issues: LCD ghosting/burn-in, GPS connectivity and erratic fast-charging.
These issues made this great phone dirt cheap. Luckily ghosting and fast-charging are software issues (or software fixable issues) and GPS can be fixed.
ROMs:
Marshmallow stock is blazing fast. I'm actually using it now after having tried all other, including Oreo. Fast-charging has not issues here and the ghosting can be fixed by using sFilter Lite. Just set it to black, 10% (you'll get it)
Nougat stock is the slowest I've used. Battery hungry too. It also features notification delay which was unacceptable for me. Nougat introduced the fast-charging issues on some G5s. If you like Nougat, go for Fulmics 5.5 (thank you @xpirt) or H-Rom H30 Port 3.0 (thank you @Astrako). These are beautiful and great. Also, don't forget to flash mk2000 1.5.5 kernel (thank you @askermk2000). It will fix the fast-charging and enable you to use Kernel Adiutor to set Screen to 238 R/G/B to fix ghosting without overlay (sFilter).
Lineage 14.1 is the most stable of all the LOS/RR family. The only problem for me is the camera. You can install GCam port, but it will not use the Laser Autofocus which was to much of a compromise.
Lineage 15.1 and RR 6.2.1 are feature packed and fast but with small niggles might bother you. Make sure you flash these with Nougat bootloader as it will not boot with stock Oreo bootloader. Note that this may soon change.
Oreo stock fixed fast-charging again and restored some of the speed and battery life Nougat lost, but it is not as fast as Marshmallow and, for me at least, it has notification lag issues. I have 7 e-mail accounts and I can't have this. Make sure you install mk2000 2.0 (check for latest) for ghosting fix. Also, try the amazing new H-Rom.
Check out the thread about GPS Issues to demystify them... or just squezze the top right of the phone when you need GPS.
I'm happy with my LG G5. It is trully an amazing device!
Waiting to see how the Project Treble will work out.
That's it from me for now.

Hold up.. How do you remove ghosting with mk2000 kernal..
Otherwise great little review

Mk2000 kernel supports color calibration. You then just need an app to tune the kernel, such as Kernel Adiutor, to set the RGB values and remove ghosting.

tremalnaik said:
Mk2000 kernel supports color calibration. You then just need an app to tune the kernel, such as Kernel Adiutor, to set the RGB values and remove ghosting.
Click to expand...
Click to collapse
Just set R/G/B to 238 in Screen section of Kernel Adiutor. Ghosting will be gone.

I see it...man I feel a dumbo not knowing this

russy23 said:
I see it...man I feel a dumbo not knowing this
Click to expand...
Click to collapse
It took me a year to find and test everything. That's why I decided to share.

thanks for the tip, i never experienced MM as bought the phone around 6 months back, but for me oreo is very snappy and smooth
the 2 negatives for me are: -
1. GPS, we all know the troubles with it, weirdly oreo helped, but its only decent outside, inside forget it..
2, fingerprint scanning, dont use it now..back on 7.0 it sometimes worked..but more often than not i would get an error saying not working or something,
now on 8.0, i cant register a print, get an error about enrolment...i just stick to pincode so its not a problem

1. I am using my H850 for 2 years and have seen burn-in only for one single day (about half year ago), after that it just vanished an I have never seen ghosting anymore. My brightness is always set to 100% and I have never used any color filters or custom kernels with color calibration features on my Fulmics 4.5 (exactly 4.5 version, because I am too lazy to update it and it works just good, but I don't say that new versions is bad).
2. never had any problems with stock Qualcomm fast charging on Nougat. Speed of charging is the same as speed of Power Delivery for iphone 8. Don't understand what are you talking about, guys...
3. there is very laggy expanding and scrolling in notifications list on Nougat ROMs. Yeah, it is true.
4. russy23, my fingerprint scanner successfully scans in 99 cases of 100. G5 has not the fastest scanner on the market, but it is very accurate. But maybe it is just my skill, because I am using smartphones with back-mounted fingerprint scanners since 2014
5. can't say anything about GPS, I don't need 1 meter accuracy, so GPS on my G5 just works when I call a taxi and that's fine

vkeza057 said:
Just set R/G/B to 238 in Screen section of Kernel Adiutor. Ghosting will be gone.
Click to expand...
Click to collapse
Hey man, i ran kernel auditor on rooted phone, running Nougat stock... Can't find the screen section anywhere... Any help? can you send a screenshot to see where exactly the setting is?

MCL95 said:
Hey man, i ran kernel auditor on rooted phone, running Nougat stock... Can't find the screen section anywhere... Any help? can you send a screenshot to see where exactly the setting is?
Click to expand...
Click to collapse
You need to flash mk2000 kernel. I suggest version 1.5.5
Reboot to TWRP, flash mk2000 and wipe cache/dalvik, reboot and you will have Screen in Kernel Adiutor

vkeza057 said:
You need to flash mk2000 kernel. I suggest version 1.5.5
Reboot to TWRP, flash mk2000 and wipe cache/dalvik, reboot and you will have Screen in Kernel Adiutor
Click to expand...
Click to collapse
Hey bro, just tried it. it says "updater process ended with error:1
Error installing zip file '/external_sd/h850_v1.5.5-mk2000.zip'

MCL95 said:
Hey bro, just tried it. it says "updater process ended with error:1
Error installing zip file '/external_sd/h850_v1.5.5-mk2000.zip'
Click to expand...
Click to collapse
That's strange. Make sure you have the latest TWRP 3.2.3.1 as you are on stock Nougat, not LOS based rom. Also, try redownloading the file. Maybe it is corrupt.

vkeza057 said:
That's strange. Make sure you have the latest TWRP 3.2.3.1 as you are on stock Nougat, not LOS based rom. Also, try redownloading the file. Maybe it is corrupt.
Click to expand...
Click to collapse
Hey. I run on 3.2.3.2. Stock nougat. Only rooted with SuperSu 2.79. Redownloaded the file. Still this is what i get

MCL95 said:
Hey. I run on 3.2.3.2. Stock nougat. Only rooted with SuperSu 2.79. Redownloaded the file. Still this is what i get
Click to expand...
Click to collapse
Strange indeed. I didn't have any issues even with encrypted stock and believe me, I flashed a lot. I'll look into it.
Edit: Some people report issues with Magisk, bu you are on SuperSu.
If you don't like experimenting with instaling Magisk (removing SuperSu), then you can install sFilter Lite and enjoy. See above for details.

vkeza057 said:
Strange indeed. I didn't have any issues even with encrypted stock and believe me, I flashed a lot. I'll look into it.
Edit: Some people report issues with Magisk, bu you are on SuperSu.
If you don't like experimenting with instaling Magisk (removing SuperSu), then you can install sFilter Lite and enjoy. See above for details.
Click to expand...
Click to collapse
Hey. It was something.wrong with the twrp. Went on to 3.2.3.1 and i flashed the kernel alright ? now time to test it!

MCL95 said:
Hey. It was something.wrong with the twrp. Went on to 3.2.3.1 and i flashed the kernel alright ? now time to test it!
Click to expand...
Click to collapse
I saw your post in mk2000 thread. Great!

Related

Random reboot with lollipop 5.1

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)
Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app
killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.
This does not happen at all to me(using stock 5.1 with Franco Kernel).
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).
Your battery is dying, I've been getting the same problem until I replaced the battery today.
richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?
I've been getting the same issues on my N7 since updating.
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.
Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng
gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.
I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk

Should I install custom rom?

Hi there. I am kinda new on these things.
I am at my home right now. I have the time to backup everything.
I am on stock right now , I have started getting a bit of lags here and there.
Should I root and install a custom rom?
And if yes , what is the best combination of kernel and rom for the best performance and battery.
Akshatk said:
Hi there. I am kinda new on these things.
I am at my home right now. I have the time to backup everything.
I am on stock right now , I have started getting a bit of lags here and there.
Should I root and install a custom rom?
And if yes , what is the best combination of kernel and rom for the best performance and battery.
Click to expand...
Click to collapse
DO NOT INSTALL CUSTOM ROM, if you have to ask that question.
On a serious note, a factory reset will take care of all lags.Rooting is for those who have a spare phone,want to play around and can afford brick sooner or later. Moto has determined stock to be best for all others.
pradyot said:
DO NOT INSTALL CUSTOM ROM, if you have to ask that question.
On a serious note, a factory reset will take care of all lags.Rooting is for those who have a spare phone,want to play around and can afford brick sooner or later. Moto has determined stock to be best for all others.
Click to expand...
Click to collapse
I am not so new dude. I have installed custom roms many a times..on my canvas a1.
On that device , it was good bcoz the device itself wasn't so good.
But this moto g5 plus is a nice phone. That's why I'm asking whether i should install custom rom or not
Akshatk said:
I am not so new dude. I have installed custom roms many a times..on my canvas a1.
On that device , it was good bcoz the device itself wasn't so good.
But this moto g5 plus is a nice phone. That's why I'm asking whether i should install custom rom or not
Click to expand...
Click to collapse
Acknowledged !! and my apologies.
Rooting and custom roms work well on MotoG+.On some of the latest Oreo roms I was playing around with in the past couple of months,the camera app broke more often than once.If you can live with that in exchange for performance, LineageOS 15 and Pixel Experience roms worked great.
But as with any phone, you have to play around for the best of latest or for stability.
Just my two cents .
pradyot said:
Acknowledged !! and my apologies.
Rooting and custom roms work well on MotoG+.On some of the latest Oreo roms I was playing around with in the past couple of months,the camera app broke more often than once.If you can live with that in exchange for performance, LineageOS 15 and Pixel Experience roms worked great.
But as with any phone, you have to play around for the best of latest or for stability.
Just my two cents .
Click to expand...
Click to collapse
What about the battery life?
Can i use greenify etc with these roms?
Thanks for the reply
Install only if a stock firmware higher or equivalent to your current version is available. Else you will not be able to go back to stock. If you attempt to downgrade you will run into problems with bootloaders.
Akshatk said:
What about the battery life?
Can i use greenify etc with these roms?
Thanks for the reply
Click to expand...
Click to collapse
Battery life is pretty good on the custom rom side. All updated ROMs are now Android 8.1 and are 64 bit. I usually get 6-7+ hours screen on time and switch between every rom that's released For battery and customizations I recommend AEX or Validius. Also, you can use greenify on any of the custom ROMs and root with magisk and pass safety net as well. I Also recommend you download from telegram group as those links are updated more often than xda.
Telegram links are:
t.me/g5pluslinks ---> All new ROMs released no chat
t.me/motog5plus ---> Release of new ROMs / kernels but lot of chat too.
t.me/MotoG5PlusStuff ---> Collection of all kinds of camera apps.
Too late. I failed to root. And now my camera doesn't work. :Cries:
Gonna try flashing stock (some 92 version ) which has the Nov patch. Older one failed(downgrade).
Help me if you can. PLEASE.
I can explain everything I did.
Too late. I failed to root. And now my camera doesn't work. :Cries:
Gonna try flashing stock (some 92 version ) which has the Nov patch. Older one failed(downgrade).
Help me if you can. PLEASE.
I can explain everything I did.
Ok guys. So..i somehow got the root to work. But the camera is not working. It is saying camera is busy . What should I do?
Akshatk said:
Ok guys. So..i somehow got the root to work. But the camera is not working. It is saying camera is busy . What should I do?
Click to expand...
Click to collapse
I believe that using custom kernel was the fix to that issue, not 100% sure as I never had the issue myself. Also, if you decide to go to a custom rom you won't have that issue (it only affects stock rom). Another option if you want to stick on stock is find the thread on here for TWRP flashable stock ROMs and use latest one for your phone.
I'm not able to select SD card storage in the recovery mode. What's the issue here? How do I fix it?
Akshatk said:
I'm not able to select SD card storage in the recovery mode. What's the issue here? How do I fix it?
Click to expand...
Click to collapse
nevermind. I updated twrp to 3.2.1.0 . Now i can use my sd card there.
jeffsga88 said:
I believe that using custom kernel was the fix to that issue, not 100% sure as I never had the issue myself. Also, if you decide to go to a custom rom you won't have that issue (it only affects stock rom). Another option if you want to stick on stock is find the thread on here for TWRP flashable stock ROMs and use latest one for your phone.
Click to expand...
Click to collapse
I installed lineage 14.1.
I have no issues now.
Thanks bro!
Akshatk said:
I installed lineage 14.1.
I have no issues now.
Thanks bro!
Click to expand...
Click to collapse
No problem. Happy I could help.

[GUIDE][addison] SETUP Moto z play XT1635-02 : from stock 6.0 to custom ROM.

I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194

is anybody getting massive lag when you unlock the phone?

Is anybody getting massive lag when you unlock the phone
Just going from the lock screen to any part of the phone and it's laggy, really laggy maybe a solid 2 second delay between actions. Reboot helps trying to lessen how much ram is being used helps for some reason turning on and off certain settings works, uninstalling an app fixes it but none of these are permanent. I'm not sure if it's the kernel I'm using or not either (Blu spark OOS)
Edit: well i updated Blu spark to the latest version and I haven't been having the issue in the last couple of hours since updating.
Joe199799 said:
Is anybody getting massive lag when you unlock the phone
Just going from the lock screen to any part of the phone and it's laggy, really laggy maybe a solid 2 second delay between actions. Reboot helps trying to lessen how much ram is being used helps for some reason turning on and off certain settings works, uninstalling an app fixes it but none of these are permanent. I'm not sure if it's the kernel I'm using or not either (Blu spark OOS)
Edit: well i updated Blu spark to the latest version and I haven't been having the issue in the last couple of hours since updating.
Click to expand...
Click to collapse
custom kernels causes lags, also the ota fixer does too, made me lag like hell but i fixed it
yenkoPR said:
custom kernels causes lags, also the ota fixer does too, made me lag like hell but i fixed it
Click to expand...
Click to collapse
It seems updating the kernel has fixed the problem I was having, could you share your fix in case I happen to have this problem again?
I am having serious lag but it's when I press the power button to make the screen come on. What I have been doing is swiping up and the nav bar comes up with screen black and I press the recent apps button and it finally comes up. It's not everytime but it's a lot more than I would like. I have stock kernel. This phone shouldn't be having this issue with 12gb of ram. But I deal with it.
Joe199799 said:
It seems updating the kernel has fixed the problem I was having, could you share your fix in case I happen to have this problem again?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=81793961&postcount=60
after this, direct install from magisk
yenkoPR said:
https://forum.xda-developers.com/showpost.php?p=81793961&postcount=60
after this, direct install from magisk
Click to expand...
Click to collapse
So I'm not on .25 I'm still on .19 any chance you could direct me to a way to install .25 but keep root and all that if you don't mind.
Joe199799 said:
So I'm not on .25 I'm still on .19 any chance you could direct me to a way to install .25 but keep root and all that if you don't mind.
Click to expand...
Click to collapse
just go to the first page on the link i gave you, you will need to re-root afterwards
I'm facing some issues with unlocking my device as well, sometimes needs to reboot for it to work properly. Then again, I'm on Bluspark kernel which could have something to do with it?...
champ784 said:
I'm facing some issues with unlocking my device as well, sometimes needs to reboot for it to work properly. Then again, I'm on Bluspark kernel which could have something to do with it?...
Click to expand...
Click to collapse
Also on bluspark kernel possible it's the problem here
Joe199799 said:
Also on bluspark kernel possible it's the problem here
Click to expand...
Click to collapse
That's what I'm thinking.. any kernel recommendations?
champ784 said:
That's what I'm thinking.. any kernel recommendations?
Click to expand...
Click to collapse
I looked around on here and couldn't find anything possibly on telegram it would seem that's where everybody is moving to.
champ784 said:
That's what I'm thinking.. any kernel recommendations?
Click to expand...
Click to collapse
Turns out I took a stock kernel backup through EKM before flashing bluspark I'll let you know if I still experience the lag or not
Performance seems exactly the same to me post unlock. The only modifications I've applied are Magisk and a few modules, other than that I've got 100% stock kernel, /system, etc... So far
DrWowe said:
Performance seems exactly the same to me post unlock. The only modifications I've applied are Magisk and a few modules, other than that I've got 100% stock kernel, /system, etc... So far
Click to expand...
Click to collapse
It was the kernel, bluspark is a good kernel unfortunately it was just giving me issues.
Joe199799 said:
Is anybody getting massive lag when you unlock the phone
Just going from the lock screen to any part of the phone and it's laggy, really laggy maybe a solid 2 second delay between actions. Reboot helps trying to lessen how much ram is being used helps for some reason turning on and off certain settings works, uninstalling an app fixes it but none of these are permanent. I'm not sure if it's the kernel I'm using or not either (Blu spark OOS)
Edit: well i updated Blu spark to the latest version and I haven't been having the issue in the last couple of hours since updating.
Click to expand...
Click to collapse
U must enabled auto switch for fhd and qhd . that's why.u have to select fhd or qhd at once.no auto switch.auto causes the problem

CPU Cores Stuck At Max

Anyone have anything similar happen?
On OOS 10.5.13 rooted with Magisk stable 20.4.
Tested on several kernels, same results.
A reboot fixes this temporarily but eventually will go back to max. Any help would be appreciated!
What kernel are you using?
What ROM?
Are you in performance mode?
dladz said:
What kernel are you using?
What ROM?
Are you in performance mode?
Click to expand...
Click to collapse
Currently on blu_spark, also happens on Kiri, and Franken
Running stock OOS
No performance mode enabled
rickysidhu_ said:
Anyone have anything similar happen?
On OOS 10.5.13 rooted with Magisk stable 20.4.
Tested on several kernels, same results.
A reboot fixes this temporarily but eventually will go back to max. Any help would be appreciated!
Click to expand...
Click to collapse
For how long stuck on this frequency?
Just flash stock boot img
rickysidhu_ said:
Currently on blu_spark, also happens on Kiri, and Franken
Running stock OOS
No performance mode enabled
Click to expand...
Click to collapse
So it's not going to be anything to do with the ROM. I'm on 10.5.12 UK which is the same as 13 in your region.
Honestly, I'm on xXx and rooted.
Just don't flash the kernel tweaks..
Just go with the stock kernel.. performance seems to be the emphasis on all of the custom kernels yet battery doesn't..
This is a side effect of it..
The reason it's been inherited between kernels is because there are values or even a few changes which haven't reverted.
You may even need to reinstall the OS. Unless you can isolate the changes causing it..just saying. Maybe quicker.
cultofluna said:
For how long stuck on this frequency?
Just flash stock boot img
Click to expand...
Click to collapse
It stays stuck permanently. Rebooting helps for a short while but then it goes back.
Yeah I haven't tried stock yet but something tells me it's not kernel related, but possibly some app or module.
dladz said:
So it's not going to be anything to do with the ROM. I'm on 10.5.12 UK which is the same as 13 in your region.
Honestly, I'm on xXx and rooted.
Just don't flash the kernel tweaks..
Just go with the stock kernel.. performance seems to be the emphasis on all of the custom kernels yet battery doesn't..
This is a side effect of it..
The reason it's been inherited between kernels is because there are values or even a few changes which haven't reverted.
You may even need to reinstall the OS. Unless you can isolate the changes causing it..just saying. Maybe quicker.
Click to expand...
Click to collapse
I don't have any kernel tweaks installed, just a couple of Magisk modules like systemless hosts for AdAway, fonts, and BusyBox.
Having trouble isolating the issue so I may need to wipe and start fresh. Just thought maybe a user here had a similar experience and could tell me what caused it for them so I can fix it myself.
Appreciate the responses!
Welcome mate, tbh though I don't shouldn't say you need a kernel for performance.
Maybe battery life but tbh the stock kernel does a decent enough job..if you do wipe, I wouldn't bother with custom kernels.
The performance is defined there already.
dladz said:
Welcome mate, tbh though I don't shouldn't say you need a kernel for performance.
Maybe battery life but tbh the stock kernel does a decent enough job..if you do wipe, I wouldn't bother with custom kernels.
The performance is defined there already.
Click to expand...
Click to collapse
Yeah I just try to find a more lightweight kernel where OnePlus' debugging is removed. Maybe the difference is not noticeable in performance/day to day use so I guess for me it's more of a OCD thing lol
I mainly only like high brightness mode in terms of kernel features. Otherwise I get about the same battery results with every kernel, which is 11%-15% drain per hour.
As for this CPU issue, it's been flawless all day. I'm trying my hardest to stress test the device to see what exactly triggers it. If it remains fine throughout the night and by morning, I guess I saved myself a couple of hours for wiping and getting my setup back!
Will keep this thread posted if I ever manage to find the culprit.
Did you end up finding the culprit? I'm facing the exact same problem. I'm on stock 10.5.13 global, stock kernel. Rooted with magisk 20.4, No mods except for youtube vanced and adaway. Any help is appreciate Ed.
fuukinguy said:
Did you end up finding the culprit? I'm facing the exact same problem. I'm on stock 10.5.13 global, stock kernel. Rooted with magisk 20.4, No mods except for youtube vanced and adaway. Any help is appreciate Ed.
Click to expand...
Click to collapse
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
rickysidhu_ said:
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
Click to expand...
Click to collapse
I flashed omega kernel like you suggested, and the problem just went away. It's been three days now with omega and everything has been great so far. Thanks again!
rickysidhu_ said:
Unfortunately no, however I don't have the issue anymore after switching to Omega Kernel.
I'm not trying to say the kernel I was previously on caused the issue, and that Omega resolved it; just saying that's the only change I made and now my CPU cores are behaving normally and haven't given me problems since.
Maybe try playing around with custom kernels yourself? Also check for what apps you have chosen not to be battery optimized, could be a potential culprit as well.
Click to expand...
Click to collapse
Which app you used to check the cpu cores?
Sent from my IN2023 using Tapatalk
aygul12345 said:
Which app you used to check the cpu cores?
Click to expand...
Click to collapse
EX Kernel Manager.
Issue came back just last night...frustrating. Noticed battery life was going fast, might need to factory reset at this point.
rickysidhu_ said:
EX Kernel Manager.
Issue came back just last night...frustrating. Noticed battery life was going fast, might need to factory reset at this point.
Click to expand...
Click to collapse
Mine hasn't come back yet, everything is still good thankfully. I'm still on omega. I just can't wrap my brain around this one. And no one else seem to be experiencing this problem.. I searched high and low on this forum, believe me. You and I are the only ones reporting this so far i think.
fuukinguy said:
Mine hasn't come back yet, everything is still good thankfully. I'm still on omega. I just can't wrap my brain around this one. And no one else seem to be experiencing this problem.. I searched high and low on this forum, believe me. You and I are the only ones reporting this so far i think.
Click to expand...
Click to collapse
Yup, seems like it.
Might bite the bullet and reset this thing when I get some time this week.
Update on this issue:
Ended up factory resetting shortly after I originally posted this and everything is working as normal!
Switched to the Pixel 5 though, so will not be keeping an eye on this thread any longer. If anyone else experiences this, seems like a factory reset will do the trick if all else fails! Just install everything back one by one to ensure it's not an app or mod causing it.

Categories

Resources