I wasn't interested, really. Phone runs fine. But, I came across some stuff, was reading, decided to try ktweak. I'm running Lineage 17.1 on my edge. Seems to be no problem and if I noticed anything at all thus far it's maybe a bit more battery life. I wouldn't swear to it, though, hasn't really been long enough. Also, it could be that SD Maid was faster when listing all the phone's apps in the appcontrol section, which is something I would care about. The edge was already pretty fast in that the apps listed in about 2.3 seconds. Seems to be just under 2 now. Could be wishful thinking, I dunno.
THere's lots to do if you get into tweaking your kernel - that's a big rabbit hole, and I'm just not that geek anymore. Ktweak is just a script, it just runs that one time to make its changes. It won't survive a reboot, but, there's an apk for an interface that lets you toggle to run at every boot.
THere's already a ton of info about it so I won't throw my ignorance in. Just wondering if anyone else decided to make a few kernel changes, or, is maybe using this script. You can see the tweaks here.
I noticed an error since utilizing this script. Coincidence or not, I dunno. 3C all-in-one has a cache feature for the 'drives' on your phone. You can increase it following a quick test. I have done it in the past on this phone and ROM, without ill effect. I had a 'download' error yesterday in Firefox and in Aurora. I didn't a few days ago, so I reset the cache option to default in 3C, rebooted, and the download error was gone.
I set the cache option in 3C after I ran this script.
It's all anecdotal to this point, but maybe the 3C cache setting doesn't play well with the default hacks this script performs. I didn't even look, I don't even care - it's just a thing I noticed and currently all is well.
Since utilizing the kernel mods set by this script I haven't really noticed anything different in real-world usage in the phone, other than mentioned. It has always been responsive, fast, it runs really well with Lineage, it ran well with stock, too. I'm not performing experiments or anything remotely similar, I am just using the phone as normal.
What is interesting is that I got almost 4 days out of my last charge. That is definitely an improvement. It's not that big a deal, really. The phone gets 2 days anyway and I have a routine that alleviates battery/charge concerns.
4 days, 6 hours+. That's something.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I don't fully understand what wakelock is, I know it has to do with CPU at minimal usage while screen is off, but that's it.
Alongside that I know some kernels can reach 128MHz, but I've found they only scale to 245Mhz by default.
Could we discuss wakelock issues and scaling, maybe get a better understanding for all?
I'm still looking for feedback, my phone has has 100% awake time lately.
Using spare parts, the numbers just don't compute...partial locks are far less than the system uptime.
You can read a fair amount about wakelocks here: http://geekfor.me/news/facebook-1-3-wakelock/
I'm not saying that facebook is your issue but that's an article I wrote a few months ago when the new facebook update wasn't releasing a wakelock. That has been fixed since then though.
This chart should answer a few of your questions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are also several screen shots at the bottom that show the commands you can run from ddms (dalvik debug monitor... it's part of the android sdk) to see any current wake locks that are in place on the phone.
FYI your phone will not sleep when it's plugged in, so you can't compare awake and sleep time when you have it plugged in. It also will not sleep after very first boot until you wake it up and then put it to sleep again. If you are having wake time issues then you should start uninstalling applications until it starts sleeping. Or the faster way would be to just do a data wipe and start over and slowly re-install your applications, paying attention to when it stops sleeping.
I know this is brief but I just wanted to give you a place to start looking.
As for 128mhz vs 245mhz... 245 is the lowest the phone can go by default. I honestly don't keep up with the kernel stuff a whole lot but if there is a kernel that is capable of going down to 128mhz then you would need to use an app such as setcpu to allow it to scale that low. In my experience in the past I have had issues on my phone when going below 245mhz. The phone would automatically drop to 19mhz and basically come to a hault. However like I said I haven't done anything dealing with custom kernels in months so I'm sure I'm behind on new changes.
Extremely helpful, thank you so much.
As much as I have many more questions, you've set me in the right direction.
So far I've found after wimax is shut off I get a connection error sourcing from wimax repeatedly.
Still looking into this.
Hello, I've got a weird error that I don't even know how to begin tracking down. Not sure if this is an ICS issue, an app issue, or a device (hardware) issue.
Several times now, I get a problem were, after a reboot, all the text on my home screen - names for apps and text within widgets is mangled somehow. Like pixels inverted, or boxed over, etc. (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first couple of times this happened, a single reboot made it go away. However with my latest occurrence, I've rebooted several times without a fix.
EDIT: It seems like my data connection may also require examination? Since on the 3rd or 4th reboot I was in my office with a solid WiFi connection (versus previous reboots I was in my car en-route), the problem has now gone away again.
My initial reboot this morning was as a quick-fix attempt at an absent data connection. Guess I'm off to research these "radios" everyone keeps on about...
EDIT 2: Ok, perhaps ignore the above. After a reboot made this go away, it has now come back spontaneously (i.e. just noticed it sitting in the cradle with the error again - no reboot this time.) CRUUUUD.
Are you using a custom Kernel? Some 'Overclock' the GPU to 512MHz, while Stock is 384MHz. Some devices can't handle the increase and cause screen artifacts. Post your Kernel details and I'm sure someone will point you in the direction of another Kernel if this is the case.
Not that I know of - should be all stock, since I haven't rooted or unlocked anything yet (just got the phone a couple of weeks ago).
Thanks for the help.
Stock launcher? Or using nova/apex etc?
Sent from my Galaxy Nexus using XDA
Hi,
Another thread...:http://forum.xda-developers.com/showthread.php?t=1646985
Nothing related to GPU overclock...just about this possibility...
Looking in different threads in Q&A/General.
If you are using the stock launcher...I think I saw a topic with this weird issue with the stock launcher...but I can not find it anymore
In any case clear data/cache of your current launcher,reboot and see...If you're on another launcher than stock,reinstall...
I speak only for the launcher issue.
Yep, stock launcher. Thanks for the other thread.
Seems to be at bay now. Will keep an eye on it.
Hey just thought I'd post this here and see if anyone else is having similar problems. I updated to the latest firmware a few weeks ago and ever since then my phone is dead after only 6ish hours with pretty average use in between. My battery stats are pointing towards the Google plus app as being the culprit so I force close it but it obviously keeps restarting.
Before the update I was able to go over a day before it would go completely flat.
Here's a screen grab of my battery stats, anyone have any ideas on what I can do to sort this out?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh and I forgot to mention, the phone is completely stock unrooted, locked boot loader etc.
Cheers.
Maybe try and uninstall updates to Google+ and reinstall. I had a problem after updating to 4.2.1 where Google+ kept syncing and it was solved this way.
Edit: Forgot to mention, my phone is stock with unlocked bootloader.
Cheers, I'll give that a go and see how it works out.
I just took my phone off the charger not long ago. Will post another screenshot when it's been on battery for a while, should give you a better idea of reasonable ratios.
Worst comes to worst, wipe everything (including SD) and start over. You could have some spooky ghost files and some cobwebs all up in your GNex!
My 4.2 Experience
i have been trying several 4.2 roms and with all of them i was getting the worst battery and also a very strange bug or at least i think it was a bug :silly: since i was using my phone normally and then all of the sudden the screen goes black but the phone still funtional it wasnt a SOD for example i was playing a game and then boom black and the sound vibration and everything all was keep on working i the end i decided to go back to CNA
Took another screenshot. I haven't used my phone so much today, but what you're seeing, OP, is definitely not normal.
I uninstalled Extended Controls. Battery stats for the app was ridiculous if the system app showed correctly. If I'm lucky I'll notice improved battery life now
I was wondering if someone who updated to nougat can make a mini-review. How is the battery, the performance, are the bugs fixed? I want to update, but if it's not better than mm, i'll just install a custom software.
It's been fine for me. Twitter didn't work at first but seemed to have fixed itself without even rebooting it. I'd heard many other people have trouble with apps not working but most of them said it was fixed after rebooting. It really depends on luck tbh. Some people are having loads of trouble while others like myself thankfully have no problems.
I think this won't be the final version of Nougat by Lenovo given it's only 7.0 and it arrived earlier than the date they announced.
VimanAdrian said:
I was wondering if someone who updated to nougat can make a mini-review. How is the battery, the performance, are the bugs fixed? I want to update, but if it's not better than mm, i'll just install a custom software.
Click to expand...
Click to collapse
if you upgrade to nougat, then make sure you reset phone and do a fresh start
its same as MM :highfive: in every aspect
but benchmarks seems to have improved
Is CPU never go in deep sleep stage? When I check battery stats I see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like factory reset is last chance for me
veimus said:
Is CPU never go in deep sleep stage? When I check battery stats I see this:
View attachment 4094591
Looks like factory reset is last chance for me
Click to expand...
Click to collapse
Yeah everyone's CPU usage seems to have a high percentage for some reason. I haven't noticed any difference in battery life really so it could just be a glitch. Does a factory reset fix it?
Compass sensor not work after update
frankcilo said:
Compass sensor not work after update
Click to expand...
Click to collapse
My compass is working fine. Have you cleared the apps cache and data and allowed location in the apps permissions. Do this via the app manager/the app you want/storage(for cache and data) or permissions (for what the app is allowed to use).
Edit, Sorry just noticed you are a experienced member so ignore my comment on how to fix the problem as you would have already tried this.
quiet, do not worry. I finally just restarted, and the compass libraries have started to work again. thanks anyway
For more info on swap memory, check this article.
I know swap memory shouldn't be necessary on Android, as we already have ZRAM, however, that still takes up RAM space and we only have 4GB at our disposal.
Plus, 512MB of ZRAM is not that much, even if it's compressed.
I use a lot of apps. Most of them don't run in the background, so that's fine. However, the one time they do run is just after a reboot. Then they all fire almost at the same time because they have on-boot listeners and this clogs up my ZRAM and RAM completely causing everything to crash up to System UI.
When System UI resets after a while, all the apps get the on-boot command again and it repeats... The only solution I have right now is using System Monitor 2 to stop the processes continuously for a minute or so, until all the apps have gotten their on-boot command and the phone runs normally.
I've tried the background check and battery savings settings for those apps, but they still run on boot :/ I also looked at some apps that could block apps from starting on boot, but they all seemed a few years old, back from when phones still had 1GB of RAM.
So, as SWAP helped my laptop from crashing every time my RAM filled up, I thought it would help my phone as well!
The stock kernel however doesn't seem to support swap (which I checked with "su cat /proc/cpuinfo" as described in the article).
Next I tried ElementalX which also doesn't seem to support it.
Any other kernels I should try?
I'm not sure about Kernels with swap support but I use an app called SD Maid to turn off apps run at boot command. That app is constantly updated and does the job well.
How do you do that exactly? In appControl I can see which apps run at boot and I can uninstall or freeze the app, but not disable it booting as far as I can see
It's under app controls receiver manager. You can turn off start at boot and any other services it has.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yess got it! Thanks! Let's test if that can solve my problem. I'm still curious towards a swap enabled kernel though, also for other reasons
Hmm for some reason all apps still wake after the boot is finished, even though I blocked them all with SDMaid. Really odd...
That is odd. SD Maid has worked really well for me. I don't know if it makes any difference but I'm using the Pro version. I've had it so long I can't remember what the difference between the free and pro versions are
I'm also using pro, so that's the same. But yeah, when booting I notice apps like AliExpress still starting when I disabled its boot receiver with sdmaid and even blocked it from running in the background in two places of the Android settings (battery saving and background check)