Database Info

Lock / Home screen "fizzes" out. Phone issue or rom issue?

Hey guys, searched for a quite a while and havnt been able to find a similiar problem. Heres what i did
Got the phone 3 days ago and proceeded to root it. It had the perfect SPL so i took the long route and made a goldcard and went to the 2005 SPL.
After phone was flashed i did the "daredevil" way of reverting back to 32b and flashed an appropriate rom to it (cynogens 4.1.8 is on there now)
It seems about %70 of the time when you hit the menu button to get the screen to turn on you can see it flash some lines on the screen like its "charging" the lcd than it just fizzes out, no picture what so ever is visible just weird fuzzy tv looking things than they go away. Trying again usually does the same thing. I have to try probably 5-6 times just to get the screen to turn on and work like normal.
So my question is, is this a PHONE issue, or is this something that could be rom / radio / spl related.
If this is a phone issue i need to take this to unroot and take to the tmobile store asap and get it replaced with another under warranty.

I got the same thing in my G1... send to HTC warranty, they changed the main board. Got it back and it happened again. Then I rooted and installed cyanogen mod, now I never see it again. So I thought it was a hardware issue, but after ROM upgrade I never see it again, so now I really don't know...

The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612

notxel21 said:
The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612
Click to expand...
Click to collapse
ok so this could possibly be both rooted / non rooted boards? Thanks for that link i appreciate it, i'll put my few good words in there. I dont think i can use this phone for business with it doing this.

This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.

Apollo_316 said:
This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.
Click to expand...
Click to collapse
That's what were refering to the screen wake issue. Same problem just called different things. I will try to set my phone at or below 245MHZ for my low and post results!!
Because I've came across both issues depending on the rom. Some give me blur, and some give me the screen wake issue, and some give me both, but I will try you're suggestion.
Thank you for this.

Yeah the JacX hero rom is the only hero rom I have found for the *well at least my* MyTouch3g that *does not* give me the blurry screen issue so that's what I'm running. Then last night I played with my clock settings and went to bed, only to find that my screen was now having this distorted/not waking up issue not like the blur issue of other roms and when I retraced my steps and clocked the processor back down the screen not waking up issue went the way of the dinosaur! I really wish the blurry screen issue could get solved already because I want to try some other hero roms and especially cyanogens experimental rom really bad but I need my phone to work too lol...well I have spare phones so that's not entirely true but I just love my android so much lol!
And you're welcome! I figure that I've learned so much from this forum over the years and had so many helpful and friendly people that it's the least I can do to provide help back!
I'd still love to know if this works for you *I'm confident it will* if you wouldn't mind posting your results as well!

I just updated to 4.1.8 and it hasnt did it in quite some time now. Didnt get the overclock widget yet but im going to wait till it does this again to see if thats the issue. Which more then likely it is.

Not as much of an issue with wake screen on 4.1.9.2 but its still there.
Guess i'll try the overclock widget also.

Yeah the devs (most anyway) are now incorporating built-in cpu clocking settings in the user.conf file for their roms and this allows the rom to do dynamic cpu clocking from the stock rom, which also allows them to push the speeds of the phones the roms are installed on without additional software. The downside to this is when the clock starts above what it's default is, or at least above 245mhz the screen has a tendacy to not wake up properly. If the clock is started at 245mhz and then gradually moved up to 528mhz based on demand on the cpu then the problem goes away. The cpu widget is free and works great to allow you to control the cpu clocks, not the rom. There's another one I'd recommend called SetCPU on the market but it costs like $2 or $3 which also works nicely but doesn't really add anything over the free widget available other than some profile options for low battery and such.
*I'm still learning alot every day about all this android modding stuff so if I've stated anything incorrectly please PM me or let me know here and I'll edit my posts acordingly*
~*Apollo*~

still no dice
im running 4.1.10.1 and it is still not waking up properly. Even with the overclock widget installed and working. Im not sure what else to do. Im updating to 4.1.11.1 right now but i have a feeling this isnt going to fix anything.

I haven't seen this.
This issue has been addressed more thoroughly in the Dream section. Follow up with stories and details there. Otherwise, I haven't seen this problem in any of the most recent ROM ports.
Everyone's device is different regardless of matching statistics. Lol.
Best of luck to you fellas.

Smartass CPU Governor on Droid 2

So I was investigating loadable kernel modules on the Droid 2 this weekend. One of the modules I tried loading was the smartass governor module and to my surprise it worked. From what I can tell it appears to be working with no problems.
The module itself is from a Milestone Cyanogen ROM. Given how close the Milestone is to the Droid 1 and how close the Droid 1 is to the Droid 2 it seemed like a safe try to see if it would load.
Requirements:
You must be rooted. This really should go without saying but I'm trying to cover all the bases here.
You must have busybox installed.
You must be able to boot into clockwork recovery.
I've tried this on Fission ROM but since we can't change the kernel on the Droid 2 this will probably work on any other Droid 2 ROM. D2G users, YMMV.
NOTICE: By installing this you assume any and all risk for what might happen to your phone. I am not responsible if this mod causes your phone to stop working, catch fire, steal your significant other, and/or hijack a plane. Basically I haven't had any issues but that is not a guarantee that you won't have any issues.
Attached is the update.zip. Boot into clockwork recovery and choose this zip to install. Once you reboot you'll be using the smartass governor.

So what has this done for your battery life?

Anecdotally I believe my battery life has improved. With the ondemand governor and data and wifi off I've seen my battery drop 10% in a night. With the smartass governor under the same conditions my battery appears to be the same. Now given that Motorola phones report the battery in just 10% increments my totally non-scientific analysis might end up being nothing.
Really you'd have to try it yourself and determine if things are better. From what I've read online the smartass governor is better at conserving battery than ondemand but it really depends on how you use your phone.

Download circle battery widget from the market. Its free and somehow it reports 1% increments. I have been using it for a while now and it seems to be spot on.
Sent from my DROID2 using Tapatalk

It just guesses

Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.

Looks interesting. I'll wait until a little more feedback is given before I try it. How is the performance after the install?

I'm guessing you have to sbf to go back?

tbaker077 said:
How is the performance after the install?
Click to expand...
Click to collapse
No different than using the ondemand governor. Smartass takes a clever approach to CPU scaling: instead of polling CPU usage like ondemand it detects when the phone comes out of sleep and sets a timer to go off in two ticks. Once that timer goes off it looks at CPU usage and scales if needed. What does all this mean? Well, if you turn on your phone to quickly check the time and then turn it back off the smartass governor will never ramp up the clockspeed. So far after a few days of light usage I've been quite pleased.
rtfield said:
I'm guessing you have to sbf to go back?
Click to expand...
Click to collapse
Nope. If you want to revert just chmod 644 /etc/startup/smartass.sh and reboot.

Sweet
Thanks

I wonder if they could modify this to work with the new gingerbread kernel.
I know when I had an HTC Eris, Conap used a smartass gov on his kernel and it was awesome.

So I took a shot and flashed the smartass governor a second ago on my GB d2, and seems to be working just fine. I'll report later with battery stats and anything else i notice.

Spitemare said:
Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.
Click to expand...
Click to collapse
I took a look at this and found some stuff that might be encouraging.
Here is the source for the battery driver. Line 397 reads as such:
Code:
val->intval = sply->batt_state.capacity;
If line 397 is changed to this
Code:
val->intval = sply->batt_state.batt_capacity_one;
then battery level should be reported in 1% increments. I've posted the updated driver code here.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...

Do we really need busybox to uses this?

tbaker077 said:
Do we really need busybox to uses this?
Click to expand...
Click to collapse
Busybox's insmod is a little more robust then the insmod that's on the Droid 2. You can try editing the file /etc/startup/smartass.sh to remove the references to busybox and see if it works; I just stuck with busybox since that was what worked for me when building this thing. I'd try it myself but I can't at the moment.
I'm running an experiment now to see how long this governor will take me. I charged my phone to 100% last night (really 100% and not just to when the charging light went off) and turned it off. I turned it on this morning and will let the phone run until 5% battery is left. At that time I'll take a screenshot showing how long the system has been up. A few guidelines:
ROM is Fission 2.6.1 which of course means Froyo. I've been thinking about switching to the leaked Gingerbread ROM but I've decided to wait a little longer
Data must remain on. I usually turn data off when I'm not using it but to get results closer to worst case I'll keep data on. The only time it will go off is when I turn on Wi-Fi at home.
No turning off the phone at any time nor plugging it in. I guess I'm going to be using Dropbox a lot during this to transfer files but I don't want to reset the time since plugged in at all.
No overclocking, underclocking, or undervolting. Clockspeed and voltage are stock.
Usage will be light to moderate. I tend to use my phones for calls, chats, and web browsing. I'll throw in some YouTube videos and maybe download Angry Birds.
No apps that try to maximize battery life. That means no SetCPU, Tasker, Superpower, etc. This is supposed to be about how well the smartass governor does for battery life.
Again, once I reach 5% I'll try to take a screenshot of how long the phone went without being recharged.

Spitemare said:
I took a look at this and found some stuff that might be encouraging.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...
Click to expand...
Click to collapse
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.

So unfortunately my phone rebooted halfway into the experiment so there is no screenshot for you all. I will say my phone made it just under 36 hours (6:30 Friday to 18:15 Saturday) on this governor. With some moderate internet browsing and way too many YouTube videos I'm quite happy with the outcome using this governor.
ZaneKaminski said:
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.
Click to expand...
Click to collapse
I've already compiled the modified module and tried to load it. The phone just prevents it from loading since the hardware interrupts are already bound to the compiled in driver.
eFuse doesn't prevent new kernel modules from being loaded. Since a kernel module can alter almost anything not being able to change the kernel isn't too much of a problem. What a kernel module can't really do, however, is change device drivers. There's not a really clean way to unload a device driver module since it binds to hardware interrupts and you can't really unbind that once the phone is up and running. If you want to replace a device driver with an alternate module you have to load the module before the original module is loaded sometime during the boot process. With compiled in device drivers though that's not really possible.
Basically we're in a situation where we need to load an alternate version of the device driver in module form before the compiled in device driver binds to the hardware interrupts. That would take some sort of ramdisk containing the altered driver module and we can't do that with eFuse.
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.

I installed this and didn't see any improvement in battery life until I ran
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
It said it was still ondemand. I checked scaling_available_governors and smartass was not in there, so I went ahead and installed the zip again... still doesn't work.
I went ahead and took a look at /etc/startup/smartass.sh. The permissions were right, so I ran /etc/startup/smartass.sh. I then checked /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and it was set to smartass.
Can anyone shed some light on why this script is not running on boot? I'm running the leaked Motorola Gingerbread ROM if that makes a difference.
Spitemare said:
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.
Click to expand...
Click to collapse
I see. I'm guessing the way to hijack said calls would be through directly modifying memory, right? That definitely is not something that sounds easy to do.

I tried running smartass.sh through an init.d script... still nothing. I actually had to make the /etc/init.d/ directory, so I figured that init.d scripts aren't supported on the Motorola Gingerbread rom... strange. I'll look for somewhere else where I can run stuff on startup.

Look for /etc/install_recovery.sh. That file is run by /init.rc if it exists. It's how the overclock stuff gets loaded on Fission. What the update.zip does is back up that file if it exists and then append /etc/startup/smartass.sh to the end. Just add the following to the end of /etc/install_recovery.sh if the update.zip doesn't add it:
Code:
/etc/startup/smartass.sh

Screen wake issue - battery pull

Hi guys
I know this issue has been mention a bit, and I've searched through countless threads but I find the search system on the site a little counter intuitive, like forum searches will only bring up the thread, not the actual key word references and I have to search again within the threads to yield results, but I'd like to clarify a few things.
I'm running Cm11 nightlies on the phantom kernel and I have the screen wake issue. It takes multiple attempts to wake up the screen. OK.
I understand this is a problem with Kitkat roms for our device. However, my case is that there is a 50-50 chance that the screen doesn't wake up at all and I have to pull the battery. This makes any rom almost unusable for me as 1 out of 2 times I have to pull the battery to access the phone, Music continues to play, and I can skip tracks or play or pause, and even take photos, which means that the phone unlocks only the screen doesn't light up. If I hold down the power button, I can feel the phone vibrate to indicate the shutdown menu and sometimes I can blindly reboot or turn off the phone by tapping the screen roughly where the menus would be, so the touch is working.
Roms have been reinstalled and dalvik wiped etc but no improvement
I'd like to know if there's something I've done wrong to have so much poor luck. I don;t mind waiting for the screen to light up, or even a few tries, I'm aware of the unstable nature of nightly roms, and I am happy to use it and contribute usage stats to help further development, but not being able to get the phone on is a massive problem, especially when receiving a call
If anyone has any tips, I;d love them to let me know so I can add here as a one stop thread to general KK problems and work-arounds.
Pr m,aybe it's just my phone
Current mods
Xposed framework modules
greenify
kk bugs fixer (currently disable as seems to make no change)
minminguard
no lock home
Xposed gel settings.
No crazy overclocks or aggressive governers (tested with ondemand, intelliactive no difference, but great battery)
General rom experience apart from this - Excellent battery and very snappy, only a little skipping with audio (even with cache increased to 4010)
Cheers people!

try another kk rom
i did not use cm11 b,coz i had problems with the low reciever volume
tryout carbon rom or vanir aosp
they are too good

SOLVED
OK, thanks for the suggestions, actually I had the same issue on all roms that I tried.
The fix was the following, I disabled the NO LOCK HOME Xposed module and now all is back to normal.
i think there was an issue with it auto unlocking the screen on wifi or cel tower that caused the lockscreen to crash from time to time or get stuck. All is working like a dream now.
It~s a shame really, here in Brazilo with the rise of the Iphone and the high robbery rate, it´s quite common now for thieves to stick their gun in your face and demand your password or for you to unlock;disable the password during the robbery so that they can reset the apple acount or phone for resale. With nolock home I could save the cel towers near my home and work (for my walks to and from the subway) so that in case of a robbery, the phone just opens up and shows its unlocked, and then I can remotely wipe it later without giving up account details. Anyway, anybody else with this problem, thats the source of the Issue

[TIP]Getting the best out of your phone.

HEATING:
Heating while charging isn't an issue pls. You can let your phone cool down before charging it in a cool place. You can either power it off or put it on Airplane mode while charging. (This will reduce the charging time and also some activities by apps which slow the charging) Heating is normal while charging owing to the Quick Charge x.0 capability of Qualcomm Snapdragon 617 (MSM8952). It will heat up. Heating is reduced in the latest builds, especially while recording video via the camera. This semi-budget oriented processor isn't designed for heavy gaming pls, despite 3GB of DDR3 RAM available to it. If you're a hard core gamer or someone who likes to overclock stuff, this isn't the right phone.
If you feel your phone is heating with normal usage too, consider removing apps which are useless and clear the cache followed by a reboot. See to it that the apps are updated. You can switch to WiFi instead of Mobile Data (keeps my athene cool idk why). If nothing works, consider a factory reset; else shift to a custom ROM if you can and test.
PERFORMANCE:
General phone performance of Nougat has been better than Marshmallow for sure, but for many, 7.0 has had the notification drawer stuttering issue in some cases and Bluetooth being turned on automatically after turning Airplane mode ON. Overall experience is smooth. But many people do not like stock ROM very much, because of the lack of features. AOSP and LineageOS based ROMs are much better that stock in terms of speed. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
BATTERY & CHARGING:
Stock N wasn't very good in terms of battery after all in comparison to MM despite the improved doze mode introduced in Nougat. Well this is the case in almost every android OEM that the battery performance went down in transition from one Android version to another. However, the March 1 update is said to fix a bit of battery and security issues. Android has the habit of collecting garbage (but that makes it smart too) and this can be one of the reasons why battery and performance issues occur after an OTA. The best thing after a "dirty/problem causing" update is to do a factory reset. Anyways, it is advised to clear the cache before and after doing an update. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
Battery Saving and charging Tips:
Please understand the difference between Screen On time of a complete cycle and the usage time. People start judging the battery from the estimated time left after the first charge itself. A tip is to fully charge the battery after a clean flash and then let it drain till 15%. Do not let the battery drain completely, Li-ion batteries lose their capacity over time and are designed to run between 20-100 percent. Battery life of your phone is completely dependant on your usage. Turning off Auto-Rotation, WiFi, Bluetooth, Sync, Mobile Data, Location Services and scanning (almost everything ) when not needed can give you the best battery life possible. You can consider using Greenify although you should avoid any such thing. Android learns how you use it, no need to comment about the 2 H SOT you're getting after a clean flash. You might also want to uninstall the useless apps and block the wakelocks (which you understand) if possible. Turn off the SIM card if it's in very low network. If nothing is helping you, you might consider doing a factory reset too.
Checkout this amazing thread by @rirozizo and the video by XDA TV.
https://www.youtube.com/watch?v=3Zt2j8lFbJQ
Ghost Touch: Your touchscreen is at fault. Visit the service center please.
Screen Retention: Your display is defective. Turning the phone off for a while and then setting blue light filter at 5% for Black colour or changing the RGB values is a temporary fix. Visit the service center please.
Random Reboots: Try factory resetting your device, see if you installed something wrong and flash latest stock firmware, just in case, you know. Else the service center only can fix the issue if still present.
For not being called a noob:
1. Read XDA and other forums and think before you do anything to your phone.
2. Ask in the community if you have doubts. (Read Rules and XDA University's New User's guide first)
3. Always make backups before flashing new things. (Use TitaniumBackup and TWRP backups)
Check the videos by XDA-TV and Rootjunky ( @Tomsgt )
https://www.youtube.com/watch?v=_rEsgCrvEqY
https://www.youtube.com/watch?v=nyr3FstDKH0&index=1&list=PLgLZvFga2ml4Atl32E4c_ZslfrTJJDUfr
https://www.youtube.com/watch?v=j-i59R51Cys
4. See this video by XDA-TV:
https://www.youtube.com/watch?v=JmvCpR45LKA
5. Stop using useless apps and be patient pls.
Valar Morghulis!

Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.

Hard reset: A term with the common misconception here in the group. Hard reset means nothing in android smartphones. It is only a term for older computers where you manually had to reset the old electrical parts from the charge they held.
Factory reset via the settings is equivalent to the Wipe Data/Factory reset available in the stock recovery.
Also, always sign out from your Google account before doing the wipe, else chances are your device may enable Factory Reset Protection and lock the device.

Normally my phone was using two BIG cores (and the four LITTLE ones). Each core was utilized around 40-60%.
Withing kernel manager I have set the minimum value for the BIG cores to 1 and I have lowered the minimum frequency value for that core. Now the utilization on that core is close to 100%.
Now the phone is cold all the time (except when charging with the Fast Charger) and I have no lag issues whatsoever.

Oh, btw, on some kernels (EX 1.07, Vegito), workqueue power saving is built in which iirc tries to schedule tasks on the fewest cores as possible, so on these kernels which tend to turn off cores and lower frequencies while asleep the wakeup action, especially while dozing, the wakeup action will be met with significant lag/delay.
If you have a delay when turning on your phone with these kernels (or even stock kernels for some ROMs), disable the setting called wq_power_saving.

I have the solution for random reboots. But only for those devices that reboots 4 or 5 times every day. Just open your device and disconnect the battery for 30 minits. Or also you can change the battery (confirmated it works)

negusp said:
Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.
Click to expand...
Click to collapse
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?

bluegrass55 said:
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?
Click to expand...
Click to collapse
It's in settings>Google, first 3 menus iirc.

i just had to unroot, re-lock my boot, and flash the latest firmware because someone has been hacking my phone. I purchased a Samsung phone and been switching the SIM between phones. I wish custom ROMs were more secure, flashing every ROM available, some took longer then others. After seeing that the Samsung KNOX wasnt able to be hacked, i decided to flash your stock N package. They are yet to get in my XT-1644 since earlier after the flash.
Am i stuck on the Stock ROM or is there a way to keep from getting a rooted with unlocked bootloader, hacked?

The possible best and functional alternative to Kernel Adiutor

the title says it all, but not to leave them with later doubts, I tell you: I have installed Cyanogenmod with Android 5.1, which of course I'm going for luxury. The detail is that I currently use Kernel Adiutor for CPU / GPU settings and the extras it has. the detail is that I do adjustment after adjustment and then ... it comes to work, unfortunately I have problems with other applications and I must be making adjustments every so often. I have some settings (at the moment) so I can use it for PUBG (which gives in some cases flaws in sound and after some time the application fails completely forcing the phone lock (S3 Neo)). I must resort to the application to give a half solution that finally does that, solve the problem halfway .. Because of the "half solution" I've been doubting if the application itself runs the changes above (a placebo effect), this is because the device once in even with the minimum CPU / GPU settings the phone starts to behave slowly (as is normal) but also consumes a large amount of battery, in the afternoon watching streaming (through medium settings in the application) the battery It drops quickly, from 52% to 9% in an average time of 10 minutes, I was finding out if I changed the application for an at least more durable alternative to Kernel Adiutor (like SetCPU or similar) but I doubt that they are compatible with the version of Android that I own or, if it will also apply placebo effect, as I am beginning to notice.
And if in case of mentioning the battery, it is better not to say anything about it since it is not battery failure. It's the same one that I've always owned, plus, unlike this one, it worked better via Stock for obvious reasons.