Hi all.
This thread is for random builds and development. There is no agenda other than to keep the Kindle Fire alive for the few of us that remain. This thread is not meant to support any specific ROM. I hope this is okay with the forum administrators.
With that said, please join in. We're all in this together.
Cm-12.1 2015-10-15
I made a public viewable folder on my Google Drive for Android stuff here https://drive.google.com/folderview?id=0B7BjC3Ky49TVcjdZQlpHYV9JWXc&usp=sharing
I uploaded a build of CM-12.1. The file name is weird so I will explain (in case you care):
cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip:
kad = kernel compiled with ArchiDroid toolchain
rsm = ROM compiled with SaberMod toolchain
O3 = almost all compiled with -O3
mo3 = more optimization, specifically as much of JustArchi's compiler flags as would work. The '3' is my third attempt to add more optimizations.
wifi = hack to make wifi work without doing a clean install, that is, there is a script, fix-mac.sh, which I think only gets run with a clean install. My hack was simply to copy the file that the wifi driver wants to the name that it wants. This should allow either dirty or clean flashing.
Suggestions:
* Change the animation duration levels in Developer Options to 0.3x or less.
* Use the Noop I/O scheduler for regular things like reading a book (that's why you bought a kindle, right) or browsing the web.
* Use the Deadline I/O scheduler for interactive things like playing a game.
* If you like Gapps, I suggest OpenGapps or TK Gapps. I have not tried this ROM with Gapps.
* You will need to get a third party program to change kernel settings. I like Kernel Adiutor.
The issues:
* Don't use the brightness slider in quicksettings. If you do use it, the status bar goes away and leaves the top part of the quicksettings panel in its place. I suggest disabling the slider and using the brightness control in the status bar settings. I'm not sure if this is a new bug or the result of too much optimization.
* There are no app snapshots in the recents switcher. This may be internal to Android as a way to save memory for low RAM devices, or it may be a bug in CM.
* The Kindle Fire just doesn't have enough RAM (or rather Android is just too freakishly bloated). Attempting to run memory intensive apps will likely result in them crashing or running slowly because the RAM they are using is being swapped to ZRAM. You may be able to adjust the ZRAM size and get better results.
There you have it. I hope you find it useful.
Ah. I just realize this thread. Going to try the 12.1 now
Sent from my Nexus 5 using Tapatalk
@pfederighi. Running fine and fast on the first boot. I clean flashed it without gapps.
After I flash Pico opengapps, it's rather slow now, but probably adjusting things. I'm going to use this for a while and see.
I M using privacy guard to block wake up and keep wake permission for (almost) all apps, since I don't use app that need to do that. Been set it up like that since ur cm11. Gave me very good battery life.
Will post some screenshot later
Thanks for this
Sent from my Nexus 5 using Tapatalk
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
{
"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"
}
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Battery life looks good.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
View attachment 3514625View attachment 3514626View attachment 3514627
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
kev716 said:
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
Click to expand...
Click to collapse
U don't need supersu. There's su app built in. Try installing Adiutor again, I remember I had that issue too, but I re open it, and it ask superuser request.
Su setting is on developer options. It's enabled by default.
Did u open kernel Adiutor and supersu from notification panel? (the one that tell us that xxx app is installed). I did, and it give that error. starting the app from home screen and app drawer works fine. Dunno if it's related to notification panel one, or u just need to open it twice.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
pfederighi said:
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Click to expand...
Click to collapse
I don't use that many app, so dunno have experience with crashing. I use 1gb zram since ur cm11, although I don't see any benefit. No crashes though.
I'll try 256mb later then.
I thought swap is remmended at 2x ram on Linux?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
I thought swap is remmended at 2x ram on Linux?
Click to expand...
Click to collapse
Indeed, but that is swap to disk. ZRAM is the method of allocating an area of RAM that is treated as a compressed disk and using it as a swap file system. It is a way of using limited RAM more efficiently, at the expense of CPU time, but it is still using RAM. So, on our device, 100 MB is eaten up by graphics buffers and proprietary firmware. Another ~300 MB is eaten up by Lollipop itself. This leaves us with ~100 MB for user programs, which is not a lot. If you allocate ZRAM at 60 MB, that leaves 40 MB of regular RAM + ~120 MB compressed on the ZRAM drive for programs. This gives us more memory to work with, but effectively 75% of it is compressed, which means every time it's read, it needs to be decompressed, and every time it's written, it needs to be compressed. The memory manager of linux does a great job of making it efficient, but it still slows down the system.
If Android were to actually swap to disk, which it can do, it would wear out the solid state media very quickly because there are a limited number of writes before the media no longer works. There have been great advances in the field of solid state technology such as Intel's and Micron's new 3D XPoint (it's awesome, check it out). So, in the near future this may no longer be an issue, but it doesn't help our old devices.
If you really do need the memory, you can make a swap file on an externally powered USB hard disk, mount the drive, and then issue a `swapon path_to_your_swap_file` from the terminal. I've done it before. It's painfully slow, but it works.
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Regarding not using ZRAM:
From what I understand, yes, if you have enough RAM without using ZRAM, then it's generally better to not use it.
Regarding KSM:
KSM compares the specified number (default 100) of RAM pages per check. If it finds that any RAM pages are identical, it merges them to a single copy-on-write page (that is, they will remain merged until a process attempts to write to it, at which point it'll be copied back to separate pages). Since there are often many read-only pages that happen to be identical, it tends to be very effective.
It runs at the specified interval (default 500ms). I've found that increasing the interval to 750ms or even 1000ms significantly reduces system load with no appreciable difference in the amount of RAM freed.
Because for some CPU & RAM intensive programs I've noticed slightly worse performance with KSM running, I have sometimes run KSM for a few seconds to free up the RAM, disabled it, and then run said program. It seems to work rather well. I suppose I could also have left it running and just increased the sleep interval to a higher amount, say 10000ms.
In general, KSM will free up about 10% of the total RAM, which in my experience is true.
CM-11.0
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
pfederighi said:
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Click to expand...
Click to collapse
I would be interested in a 10.2 build.
And of course thx for all your interest in keeping this device alive. Great little tablet.
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I don't remember facing those issues. About have to press button several time to wake up, sometimes it just need 1-3 secs for the screen to wake, probably because of low cpu clock too.
I remember using 10.x that has privacy guard, but it's different from 11.x. As long I can block wake up and keep wake, I'm sold.
As the sound,
Anyway, since you re offering otterx version, I definitely will test it out, since it's easy and won't require a pc.
Thanks
Sent from my Nexus 5 using Tapatalk
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I thought CM11 had more free ram than CM10?
VTCruzer said:
I thought CM11 had more free ram than CM10?
Click to expand...
Click to collapse
10 is faster, much more responsive than 11. For free RAM I'm not sure, but AFAIK, free RAM can be set using minfree. More free RAM doesn't mean it will run faster, it just mean less crash on apps and more capable on running apps that need high ram.
@pfederighi already explain about the zram. Using that, we can get more free RAM, but will use More cpu to decompress the zram when accessed. So, probably not faster than without using zram.
If we really want to compare the ram, I suggest to compare the usage (system), not the free one.
Sent from my Nexus 5 using Tapatalk
I too would be very interested in a 10.2 build for otterx
Related
Surprising to me, I have been PMd by a few people asking about how I resolved issues that I was having with my tablet. I could not give you a specific answer on why and how well my tablet runs so this is just how I do it. Results for you may vary, and what works for me may have been a problem for others. I am in no way a dev, nor do I take credit for their work.
I am posting this as possible tips for CM10 (9/2/12build) w/ godmachine kernel v2.0 & the latest gapps available from goo.im. If you are not to that point or do not understand what I am talking about, STOP, and go read pio_masaki's [Guide] All things Iconia A100 (guide to modding)
MY RECOMMENDED APPS
Apex Launcher (NOVA Launcher is a good alternative) since Trebuchet 2.0 freezes/crashes ALOT
SetCPU w/profiles enabled for my overclock needs
ESFileExplorer for root and normal file manipulation as well as streaming video from my home server.
Titanium BackupPRO i think is the best file backup/restore software. Market Doctor as well as bloat ware/unwanted system app melter ability to integrate apps into ROM, than create a backup in CWM and next time you flash, all your apps will be included.
ESTaskManager for boot up app disabling/enabling, as well as Task killer if I need to terminate a running app. Has many other useful functions such as power optimization.
STARTING FROM SCRATCH/BUILDING MY CM10 SETUP
INSIDE TEAMWIN RECOVERY PROJECT
I use TWRP. In this order I wipe cache, dalvik cache, factory reset, and internal storage. Then I flash CM10, kernel, and gapps. Power off via menu option. Power on and i do not touch for 10min. than reboot wait 5 min, fill in Google profile, reboot than I start installing the rest of my apps. This is more your customization stage. Although I recommend installing your custom launcher, such as Apex Launcher, and updating Superuser before doing anything else.
USING TITANIUM BACKUP FOR FREEZING/REMOVING APPS
At this time I usually will start changing all my settings and freezing/uninstalling apps. Doing this will free up RAM and stop unused apps from even loading into the system. You can "thaw" them out anytime.
I use Titanium Backup and I freeze these system apps (I don't uninstall in case freezing an app causes a conflict):
E-Mail 4.1
Exchange Services 5.0
Face Unlock 4.1-392829
Gallery 1.1.4000 (In this build there are two identical listed, so I freeze one)
Google Play Music 4.3.605.392829
Google+ 2.6.1.30454518
Movie Studio 1.1
News&Weather 1.3.11
ROM Manager 5.0.0.8
Trebuchet 2.0
Lucky Patcher 2.5.0 (if you use it, use it for your purpose than FREEZE it until next time you need it)
Dev Tools 1.0
com.android.smspush 4.1.1-eng.odin.20120903.000735 (Not a 3G tablet, not texting so I freeze it)
[VOICEMAIL] Mobile Data 4.1.1-eng.odin.20120903.000735 (not a 3G tablet, so service not needed)
[SMS/MMS/APN] Mobile Network Configuration 4.1.1-eng.odin.20120903.000735 (not a 3G tablet, service not needed)
Network Location 1.1.10
Setup Wizard 1.3
Spare Parts 4.1.1-eng.odin.20120903.000735
VpnDialogs 4.1.1-eng.odin.20120903.000735
Voice Dialer 4.1.1-eng.odin.20120903.000735
USING ESTASKMANAGER TO EDIT STARTUP APPS
Next, I use ESTaskManager and disable a lot of the boot up apps. A lot of the apps you can disable their startup because you can launch them manually. This reduces boot up time and saves us some precious RAM and CPU cycles. Depending on what apps you uninstall or freeze, these may or may not be available to you.
I Disable:
Any of my user apps that aren't system related. Example, I can disable NOVA 3 from the boot up list because it's just cached in memory, and wasting memory to display notifications. For free games, this can actually stop all those annoying ads you get on startup. But I wouldn't want to disable SetCPU on startup, as it is controlling my governor, I/O scheduler, and CPU frequency. I am not going to list all my user apps, you get the point.
Calendar Storage-disable if you don't use
Contacts
Download Manager
Email
Exchange Services
Gmail
Google Contacts Sync
Google Playstore
Google Search (safe if you do not have any GSearch widgets, and you disable the "persistent" search bar from you home screens in settings)
News&Weather (safe if you don't use the widget)
ROM Manager (it's just best not to use this stupid thing! will get you into more trouble than good!)
Voice Dialer
USING SETCPU W/PROFILES ENABLED FOR OVERCLOCKING
Now for SetCPU, and how I use it.
Several users state that SetCPU causes a lot of problems with our tablet, and this is true, if you don't follow a few guidelines. I do have profiles enabled. I have 4 profiles. One for regular use, on for per app basis overclocking, one for screen off, and one for screen off on a per app basis so I am not under clocking as low as when screen off profile is triggered, for when apps like ESFileExplorer or Titanium Backup are performing long tasks and the screen times out.
I find using True/False and the "Any of these are true..." triggering events works best.
{
"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 problem with our tablet is it does not like using profiles. I have pinpointed the issue of SODs and random reboots being associated with SetCPU. When building profiles, you have to make sure you use the same governor in all of your profiles. You can change the I/O Scheduler for each profile without any negative effects. I use my tablet almost solely for Android Gaming, so leaving all my profiles set with lulzactive or smartassV2 is not an issue for me.
If you ABSOLUTELY want to change your governor, you can change it manually at the SetCPU "Main" screen. Just remember when you’re done to change it back to the one used in your profiles. To stop SODs (Sleep of Death), in your Screen Off profile, raise the MHz slider from 216MHz to 312MHz for your minimal under clock speed.
You can also use other features of SetCPU to undervolt and edit governors like lulzactive.
MY SYSTEM SETTINGS OPTIONS
Under Performance tab make sure for Processor and I/O scheduler that the "Set on Boot" option is OFF/UNCHECKED!
Under Memory I do have allow purging of assets ON/CHECKED
For Surface Improvement I select the "disable dithering" option. Some games/apps I use would FC until I turned this off.
zRam
I also have zRam turned on, but you have to flash a special zRam .zip from godmachine/linuxsociety from TWRP/CWM to actually have it working. Just download the appropriate .zip file for the amount of RAM you want to use for zRam compression. I use just the 100MB .zip. All the zips and a good explanation by linuxsociety are in his kernel thread
Under the Developer Options tab:
Turn on Android Debugging
I disable the "USB debugging notify" option, we already know we turned it on.
I turn on "Force GPU rendering"
For Background Process Limit I have it changed from Standard Limit to At most 4 processes
I have Kill app back button option checked.
Under Profiles tab, I tick the slider and turn profiles off.
For Wi-Fi sleep policy, I have a 5m time out. I found that wireless really sucks the life out of the battery. So if I'm not using it, I manually disable it.
BUILD.PROP MODS
I have used these, and for my uses I find that it is not needed. They do have benefits. For testing purposes I keep a copy of the stock build.prop and a copy of the modded build prop both in the system directory. Put them both in there and rename them build.prop.reg.bak and build.prop.mod.bak. Than with ESFileExplorer, make sure you have root access enabled, see pic) you can just rename the file you want to use to build.prop. Boot into recovery and clear cache and dalvik cache, and make sure you let the tablet sit for 10mins anytime you clear caches. The only time I really use the build.prop is to make an app list for the A500 in the playstore so I can download/purchase it and have it marked as so in the playstore, than extract the APK with titanium backup and than go back to stock build.prop and side load the app. Some apps will install under the A500 mod, but will FC or not run properly until you return to the stock build.prop.
I really can't think of anything else that I may be doing that can help you guys out. A suggestion I stand by, is I don't bother with widgets. They take up memory and CPU cycles for information you can usually get to via a couple taps on the good ol' touchscreen. And I have no idea why, it may just be me thinking it improves battery life, but I turn airplane mode on, and when I need wireless access I leave airplane mode on and turn wireless itself on. For some odd reason I see improved battery life, and my assumption is that when airplane mode is on, there are system apps that are put to rest by seeing the tablet is in this state.
Anyways, I hope this info will be useful for people. Any questions, feel free to post or PM me. I am a full time college student so I may not respond right away!
Very nice! Thorough, clear, and I can find no faults in your advice that isn't personal choice.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Very nice! Thorough, clear, and I can find no faults in your advice that isn't personal choice.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Approval from you means a lot to me, cause you know what your doing more than I do!! lol
Good job, although it could better sectioning, make it easier to find stuff. Besides that, not bad!
Sent from my A100 using Tapatalk 2
das_webos_transformer said:
good job, although it could better sectioning, make it easier to find stuff. Besides that, not bad!
Sent from my a100 using tapatalk 2
i'm open to suggestions!
I wasn't quite sure how to break it down, like how to label a category and what would go into that category.
Sent via acer iconia a100 on cm10_build090212; godmachine v2.0 kernel, smooth, stable, fast
Click to expand...
Click to collapse
edit: Updated op organization
Nice tut. Should help out some to squeek out max performance.
A little more detail of how to freeze (paid version only), and disable startup apps, might help the novice.
Pretty much the way I run, with several different personal preferences.
Looks good. I especially like the list of apps that can be frozen. Just want to add that there are a few free apps (i.e..App Quarantine) that also freezes unwanted app.
Might be just me anal but the pictures attached shows up really big on the computer, taking up most of the screen and really distracting. I almost missed the blurp about setcpu profiles in between the pictures.
illego said:
Looks good. I especially like the list of apps that can be frozen. Just want to add that there are a few free apps (i.e..App Quarantine) that also freezes unwanted app.
Might be just me anal but the pictures attached shows up really big on the computer, taking up most of the screen and really distracting. I almost missed the blurp about setcpu profiles in between the pictures.
Click to expand...
Click to collapse
lol I KNOW!!!
I was wondering why they posted so big from my linked photobucket.
Maybe I should scale them down and re-upload.
[/u]Looking good!
Sent from my A100 using Tapatalk 2
das_webos_transformer said:
[/u]Looking good!
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. Over the next few days I am going to add in a section about app compatibility and what runs on CM10. Games, media, tools, all of it.
If anyone wants to contribute information for this CM10 Tips guide, I will gladly fit it into the OP and credit your name.
Thanks for the support guys!
Bump
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
Tsk tsk
Sent from my A100 using xda premium
das_webos_transformer said:
Tsk tsk
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Gotta give the thread some bump love for the noobs.
I keep having to bump pio's guide as well, if it goes to the bottom of the threads, its basically nonexistent as noobs don't know how to operate a basic search function. lol
justjackyl said:
Gotta give the thread some bump love for the noobs.
I keep having to bump pio's guide as well, if it goes to the bottom of the threads, its basically nonexistent as noobs don't know how to operate a basic search function. lol
Click to expand...
Click to collapse
hey im not a "noob" ,..(ok so maybe ) im thinnking of trying this on my backup (yes i have 2 a100s) ..the second one is the 16 gb version..is there anything i should be made aware of before i do this?..(and i have looked but where is the godmachine kernel)
mordeith said:
hey im not a "noob" ,..(ok so maybe ) im thinnking of trying this on my backup (yes i have 2 a100s) ..the second one is the 16 gb version..is there anything i should be made aware of before i do this?..(and i have looked but where is the godmachine kernel)
Click to expand...
Click to collapse
God machine aka linuxsociety. http://forum.xda-developers.com/showthread.php?t=1818924
Start here http://forum.xda-developers.com/showthread.php?t=1711125. Once you get cm10 loaded up follow this guide.
Romman0 said:
God machine aka linuxsociety. http://forum.xda-developers.com/showthread.php?t=1818924
Start here http://forum.xda-developers.com/showthread.php?t=1711125. Once you get cm10 loaded up follow this guide.
Click to expand...
Click to collapse
ahh you beat me to it
but I am going to add ROM and kernel links into the OP. Should have the first time.
I need to update this but I've been so busy with my stickied G2x Kernel thread! lol
I've all about abandoned SetCPU in favor of Antutu/No Frills (still testing) alongside with Android Tuner Pro <--- Which is flippin sweet on this tablet.
I may just be using it by itself as it can OC/UC/UV as well, than startup editing, build.prop modding, SysCtril modding somuch more. My tablet has been running smooth, and usually I just turn it off when not using as I could not get standby battery drain under control. I've just hit 18hours and still counting after using Android Tuner and I am still able to play all my HD games smoothly, meaning performance is not horribly hindered. I'll run a benchmark on it.
Great guide. used this on my desire s as well.
Hi jackyl, just wanted to say "great guide" I'm from the a500 forum and I feel guilty saying that i never knew you guys existed :shame: If it hadn't been for a 100 user posting his issues over our side I'd still be locked in ignorance!!!
I will link your guide and pio's in my flash guide if thats ok....there's some great info everyone should read imho
Keep up the fantastic work, happy tabbing
rgds dibb
dibb_nz said:
Hi jackyl, just wanted to say "great guide" I'm from the a500 forum and I feel guilty saying that i never knew you guys existed :shame: If it hadn't been for a 100 user posting his issues over our side I'd still be locked in ignorance!!!
I will link your guide and pio's in my flash guide if thats ok....there's some great info everyone should read imho
Keep up the fantastic work, happy tabbing
rgds dibb
Click to expand...
Click to collapse
Hey thanks for the support, feel free to link it.
:thumbup:
Sent from G2x, CM7 Weekly 1-1-13, Faux 054.
Just a note, added a link here in that guide thing I wrote as well.
This is not meant to be a complaining post, mostly I wanted to see if anyone else is having my problems.
I am currently running ParanoidAndroid 2.50 (CM10 based ROM) and I absolutely love how all AOSP ROMs look and feel. TouchWiz had some neat things, but it felt really bloated.
My problem is, multi-tasking on AOSP blows, really, really, really, BAD. I mean it's downright as bad as HTC One X's Sense UI multitasking. For whatever reason, I can never get my free RAM to dip below the 600 MB limit. Usually it hovers around 750 MB, and occasionally I can get it down to 650 MB.
I am not a huge multitasker, but I HATE HATE HATE app re-draws and reloads. This was the one nice thing about TouchWiz, it would keep my opened applications running until I was absolutely at the bottom of my free RAM (~150 MB). My frequently used applications almost never needed to be reloaded/redrawn. This is especially big for applications like Youtube and Browser/Firefox, as you lose everything that you had loaded otherwise.
I've tried spamming opening apps, and the most apps I seem to be able to have open at once is around 8-10 depending on the circumstances. As soon as I cross that threshold of open apps, my other opened apps start being force closed, and require a redraw/reload. This is an absolutely pitiful amount of apps, especially with the whopping 600-800 MB of free RAM that I usually have.
I also have the issue that sometimes even when I don't open a lot of apps, some of my apps like to force close for no reason after a few minutes of being idle. My MailDroid and Firefox apps seem to be extra susceptible to this random time based force close compared to GoSMS, which rarely closes after an inactive period of time.
I have tried multiple kernels, multiple ROMS, multiple governers and I/O schedulers, and I even tried zeppelinrox's V6 supercharger + multitask mods. Nothing I do seems to allow me to crack into that 600 MB of unused RAM. I am so flustered by this that I'm actually considering going back to TouchWiz.
Could anyone else provide me with some feedback with their multitasking app limits/free RAM? Is this a known CM10 issue?
TL : DR
-I can never get below around 600 MB (usually hovers around 700MB) of free RAM
-My running app limit seems to be 8-10 with about 6 widgets
-My apps seem to force close after short durations of inactivity
-I experienced NONE of these problems on TouchWiz
-Could someone post their numbers for some of these things, and is this a known problem for CM10?
Same problem here... I think most people like this problem though. Many like to see more free ram, but I prefer faster multitasking. My main concern is my downloads being closed and interrupted.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yeah definitely a known issue on AOSP. Memory allocation issues I guess. I've never seen a dev comment on it, despite the fact it has been brought up several times. I suspect we won't get a fix until the JB sources are released for the d2.
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
zeppelinrox said:
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
Click to expand...
Click to collapse
Oh wow it's zeppelinrox! Hi
Yes, I used the Windows Jellyscream tool to patch my services.jar. The ICS Service Center in your script insists that it worked, but CM10 does not currently have a "Charge Only" or "No Action" mode when the cable is plugged in, I'm forced to mount the SD card(s). Your tool specifically says do not do that, but I don't really have a choice :/
My current MinFree values are:
8, 14, 40, 50, 60, 75
I have also tried the auto-calculated ones (which in my opinion leaves way too much free RAM theoretically):
8, 16, 325, 358, 390, 423
Both of them didn't seem to make a difference.
I have attached my services.jar to this post as well as requested.
As for aLogcat, I'm not sure what that is or how to do that
Hi
Well I can't open it up... is the file size correct?
Maybe it's an incomplete upload.
I assume that it's for ParanoidAndroid 2.50 so try upping it again since I haven't cracked one of those open yet lol
The service centre only looks at the supercharged launcher aspect and the windows exe isn't up to date for the multitasking mods.
I've actually just updated the ultimate jar script today... and also has an SGS3 specific edit
However it may be only for the stock rom.
The aLogcat test is described in the ultimate jar thread OP.
Weird, I'm also not able to open the one on my phone, that's kinda scary.
Ok, I'll give your new ultimate script a spin, and I'll look into the aLogcat thing as well and try to provide you some information.
Here's the services.jar file that was leftover in the Jellyscream directory (JellyScreamPatcherV6_0.9.0.6/framework/services.jar). I chose not to delete the temp files, so I'm guessing it's the same file.
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
ChrisG683 said:
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
Click to expand...
Click to collapse
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752a
am: Allow more hidden apps on devices with lots of RAM
* If more than 1.5GB is present, allow up to 40 hidden apps. * Number is somewhat arbitrary, but was found to work well on D2. * Also look at the sys.mem.max_hidden_apps value if given.
Click to expand...
Click to collapse
Uh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
zeppelinrox said:
btw how did you decompile?
Click to expand...
Click to collapse
Hmm, I'm not sure what you are asking here, could you clarify?
zeppelinrox said:
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752aUh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
Click to expand...
Click to collapse
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
ChrisG683 said:
Hmm, I'm not sure what you are asking here, could you clarify?
Click to expand...
Click to collapse
OH that's ok.
The second file you posted decompiled fine
themadproducer said:
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
Click to expand...
Click to collapse
Yes you were using dorimanx's trick to break the lowmemorykiller on HD2
He asked me to break it on ICS and above, which I did.
But that only lasted a day because I found another way to do it... boost number of running apps without breaking lowmemorykiller.
Needless to say, dorimanx got real happy lol.
See post 2 of the ultimate jar thread for more about that.
So yeah, you still have the app limit and lots of room for more multitasking since you can't get very low on ram.
I've added more mods to reduce the likelihood of apps closing on you. (Check the change log)
Sense users are ecstatic with the latest
Anyway, I'm sure that if you try it, you'll notice a difference - it's just a matter of you not knowing how much better it can be
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Deoxlar said:
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Deoxlar...are you asking me?
With the HD2, I had the OS rigged to NOT kill any apps EVER and used System Tuner Pro as my APP Killer with exceptions checked off. I used Tasker to determine the ram availability each time a window opened or changed, and Tasker would trigger STP when necessary.
But Zepplinrocks' V6 Supercharger as a very unique system for doing similar...but overall, it handles everything to do with ram management and better. Also, for some people's setup, it is a dramatic improvement...a FIX... a LIFE SAVER. (Basically the rom Devs are going to eventually slowly STEAL Zeps ideas. But we will not forget.
My old HD2 memory mngt system was an ALL or NOTHING workaround so it suffered in that regard.. The way my S3 with stock ICS is handling things right now is surprisingly good. I did a test last night opening as many apps as possible until I basically ran out of FREE ram. At that point, the OS was doing it's thing, killing another app or 2 so it could run the new app launched. Multitasking...or switching to newly launched apps and then returning to previously launched apps where they left off....worked near flawless and FAST on my i747m. When I woke up today, 3/4 of the apps were still in memory ready for resuming.
This is why I went from 2 years of OBSESSIVE flashing and tweaking....to using my new S3 with the Stock rom and about 1/100th of the tweaks. Super STABLE and not a slouch. I hope the upgrade to JB...well....is an UPGRADE. yadda yadda yadda...:good:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
{
"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 16th hidden app gets killed because the limit is usually 15.
zeppelinrox said:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
The 16th hidden app gets killed because the limit is usually 15.
Click to expand...
Click to collapse
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
themadproducer said:
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
Click to expand...
Click to collapse
LOL thanks for the kind words man
zeppelinrox said:
LOL thanks for the kind words man
Click to expand...
Click to collapse
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
So, you're using the "ultimate jars" script in conjunction with which ROM? And did you use in conjunction with the supercharger script?
Just trying to understand exactly what is required to "fix" the multitasking issue.
themadproducer said:
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
Click to expand...
Click to collapse
Wow I've never heard of a stock rom having the app limit set to 50.
However when you type free in terminal, how much is system tuner reporting as free?
There is a difference because the free command in terminal is always very low whereas apps like system tuner/task managers always report free ram as "free ram + cached apps" which is a much bigger number.
Can you post a deodexed services.jar (it's probably odex tho since it's a stock rom) or at least the smali files?
The windows patcher should be able to decompile it.
If it's not sense I'd only have to look at ActivityManagerService.smali and ProcessList.smali.
Hi,
I've got a Tegra One X running SlimBean 4.2.2 WEEKLY 5.7 and n3okernel.
So far so good but there are still some things I'm not really sure about.
First there's something very annoying compared to other phones and even to Sense One X's.
From pressing the lock button to the screen coming on it takes about 1-2 seconds (which is still quite slow but acceptable to me), but sometimes the phone just takes a little bit longer. Sometimes it takes up to 20 seconds (haven't stopped it but it's my impression).
Does anyone have an idea why this could be? Is it possible to disable the fade on animation? I don't need it. I'd rather have the screen just coming on.
And otherwise I've been playing around with Pimp My Rom Beta from the Play Store and fiddled around with some settings and the results seemed quite good to me. Can someone tell me if it's recommended to turn these settings on:
Hardware acceleration (Pimp My Kernel - Android Features)
Lock Launcher In Memory (Pimp My Kernel - Android Features)
Call Ring Delay 0 (Pimp My Kernel - Telephony)
Proximity Sensor Delay 0 (Pimp My Kernel - Telephony)
AMR Wideband (Pimp My Kernel - Telephony)
Optimize sqlite3 Databases (Pimp My Kernel - Miscellaneous)
Ext4 File-Systems Tweaks (Pimp My Kernel - Miscellaneous)
Internal SD-Card I/O Tweaks (Pimp My Kernel - Miscellaneous)
Zipalign all APKs at each boot (Pimp My Kernel - Miscellaneous)
Battery savings (Pimp My Kernel - Miscellaneous)
Quick Power-On (Pimp My Kernel - Miscellaneous)
Adjust GPS config to my country
Wifi Scan Interval 180 (System Tweaks - Internet)
It doesn't have anything to do with speed but I discovered that my battery drains quite fast if I have mobile data enabled. If I disable it there's nearly any drain.
Is this normal and is there a way to make the drain a bit less extreme?
Thanks in advance!
land.apfel
Change kernel would probably fix screen on delay
Sent from my HTC One X using xda app-developers app
This is the reason why I've chosen n3okernel. It seems to be better now but still not completely cured.
Which one would you recommend?
I've got the same problem on my Nexus 7 also.
I've flashed Faux there.
land.apfel
Oh boy, where to even start. First it's a known issue with higher end mobile processor's (like tegra 3) that fstrim is not correctly adjusted. To take care of that go to play store and download lagfix and run it, you'll probably notice an immediate difference. I would also download cache mate, clean master (has a broom icon) and also clean master pro (has a little ying/yang icon). Download all 4 of those apps and run them all and you should notice a huge difference. If your SD card space is getting low, that can also slow down your phone. Again, I would go to the playstor and download SD maid and use that to clan up your SD card. This should all make a huge difference. Like I said though I would start with the lagfix app.
I tried lag fix but it made everything worse I suppose.
So I didn't try the other tools.
My SD still has some gigabytes of space so this shouldn't be a problem.
My main problem really is the slow unlocking at the moment.
And the battery drains pretty fast too, but unlocking is really what's annoying me at the moment.
Thanks anyway!
land.apfel
You gotta remember too, the Rom your running is basically a constant beta if you're using weeklies, these issues may pop up. Might wanna try a different Rom and see if it persists.
from my Viped out one x
A few apps could help alot
Download greenify, and seeder
< Coming to you live from the planet One X >
I was running the official build 5 until yesterday but then I thought I should maybe try a newer build. Maybe it's better.
As Build 6 came out today, I've upgraded to this one.
Does Seeder really help?
I've read that it does not help at all because entropy is not really needed so often.
Is there no simple solution for faster unlocking?
land.apfel
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
herqulees said:
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
I've already deleted every system app I'm comfortable removing using Root Uninstaller. After having everything I have to have installed on the phone, with as many apps set to not run in the background that I can and Greenify helping too, I tend to have 10-70MB of RAM free, it tends to be 15-35MB free though. I don't use task killers since all they do is play cat and mouse and waste battery, and tried a few auto start managers but can't really get into using it with how complicated they are. Right now the main thing I want to figure out is getting a swap partition up and running since that sounds the most promising with how little RAM this phone has.
Did a backup and switched to the nitest-0721 kernel and so far it's doing good. Disappointed the OC only goes up to 1.2GHz but it's better than nothing (don't understand kernels that limit how much you can OC when it's up to you to find how much your phone can OC), hopefully I can find a way to get it to go higher, and the "voodoo color" is weird but I can install a different version of the kernel to remove that if my eyes don't adjust first. Anyways... my free RAM now stays between 100-200MB, usually about 160MB, with 18% zRAM, purging of assets, and samepage merging enabled which is amazing. Apps are opening faster and don't stutter anywhere near as much as before, so I'm happy but will see how things go tonight when I go to work and am playing with it on and off, along with need to find a way to really overclock it.
herqulees said:
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
Try going with one of didhiy's nitest kernels and maybe a different AOSP ROM, like AOKP, PAC, etc. Or try out SuperNexus even. That's an extremely lightweight ROM with no customization options (Its straight up stock Android, just like a brand new Nexus phone), but its fast and quite stable from what I remember.
Sent from my LG-LS970 using xda app-developers app
Or find one of didhiy's nutest kernels, those have live oc, more free ram, and i believe it goes to 1.4 GHz. I'm not sure though. But it is less stable than nitest
Sent from my SPH-D700 using Tapatalk 2
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
herqulees said:
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
Click to expand...
Click to collapse
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
AndyYan said:
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Click to expand...
Click to collapse
I just seriously hate kernels that limit how high you can overclock instead of making OC options to unreachable levels letting you find your phones limits. People make kernels, roms, hacks, etc so we can get around limitations that the hardware vendors put up. So if we've managed to circumvent the manufacturers blocks why are the same people that got around them making their own blocks, they already put up silly warnings about anything you install/do could break your phone but if you're going to give that warning it needs to be true. Anyways ending my rant lol...
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
herqulees said:
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
Click to expand...
Click to collapse
Uh, AFAIK, isn't these frequency decided only when the kernel is COMPILED (from source code)? I don't exactly know...
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Q&A for CyanogenMod/LineageOS for Celox Devices (Hercules & Skyrocket)
As requested I created a Q&A thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by me.
Before posting, please use the forum search and read through the discussion thread above for your device. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Frequently Asked Questions
Q: My device reboots when I receive or make a phone call. Why?
If your using OpenGapps read this: https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Click to expand...
Click to collapse
Q: Formatting my SD Card as Internal Storage doesn't work. How to fix it?
Goto Settings > Storage. Click on your external sdcard
Tap the Menu button in the top right and select Settings.
Then choose Format as internal. (This erases all the data on the sdcard so backup if necessary)
Once you click Erase & Format, the device will format your card.
The process may get stuck at 20% and timeout after about 2mins. If it does reboot into recovery after it times out.
In TWRP, select Wipe then Advanced Wipe. Select "MicroSD Card - Data" and click "Repair or Change File System".
Choose, "Change File System" and select FAT. Then swipe to change.
Reboot, then goto Settings > Storage. Your sdcard should appear as corrupted.
Continue and format as internal storage. It should then get past 20%. If it does, continue with the steps shown to you.
Click to expand...
Click to collapse
[FONT=Arial,Roboto,Helvetica Neue,Helvetica,Verdana,sans-serif]Frequently Asked Questions[/FONT]
Since this is a unified thread, I will use Celox to refer to both the Hercules and the Skyrocket. This was their planned codename for the LTE S2, and both use the celox-common branch in source code.
Q: How do I root my Celox? I flashed SuperSU, and my phone won't boot!
A: You don't need SuperSU. Root access is baked into the ROM.
Wipe everything and install the ROM without SuperSU. Now, in Developer options, set Root access to Apps and ADB. If you really, really, want SuperSU, install it from the Play Store and have it install it directly without recovery. (not confirmed working, but should work.)
Q: Do I install this like any other ROM? Why can't I install Gapps?
A: No. This is a virtually partitioned ROM, common in today's Celox ROMs. The different partition layout is necessary to take full advantage of your phone.
Q: Clean flash or dirty flash?
A: I always dirty flash. I never wipe unless I am switching ROMs. You may want to wipe, your choice.
Q: Virtual repartition? Whaaaaaat? Do I need a PIT file? Will this damage my device?
A: The classic issues with the S2 are:
Not having enough room to install apps
Being forced to use tiny Gapps packages
having waaaaaay too much internal sd card free space, even when you have a real SD card that you haven't filled up either.
Virtual repartitioning changes the way the system sees the partitions ("sections" of the 16GB of storage), making it similar to the 16GB Samsung Galaxy S3. This fixes all of those problems!
Here is what happens:
To make more room for apps and data, we made that SD card partition multitask as apps, data, and the internal SD card storage, emulated at /data/media/0, like modern devices. This will wipe those files on the internal SD card partition, though! You now get 11.2GB freely usable by the system.
Since Lollipop, ROMs have been increasing in size greatly. They even use a different installation method. Our measly 598MB /system partition, which couldn't even hold all of 4.1.2 TouchWiz, has been moved to what /data was before. That means 2GB for the ROM, Gapps (yes, you can even flash STOCK!), BusyBox, root stuff, extensions, you name it!
And that 598MB /system partition becomes /cache, because you can always have more cache!
No PIT is needed, and, if you flashed a PIT (like the one that gives you 6GB for data), flash it back to stock! You will end up with 7GB shared for the internal SD card and app data and 6GB for /system, which is ridiculous.
And the best part is: Nothing is damaged. It is 100% safe! It is just a renaming scheme, and you can always flash to stock in Odin.
Q: Which Gapps should I use?
A: Well, as always, it is your decision, so so as you wish. I personally use Nano, which I also recommend. However, you need to install keyboard_patch.zip (attached to this post) after a Full or smaller Gapps or you will get spammed by "Unfortunately, Android Keyboard (AOSP) has stopped.", making it impossible to set up your device.
Stock fixes this issue, but it also adds crapware that I bet you don't need, like Google Sheets, Google Maps, Google+, and especially Chrome.
Q: HALP!! I'm getting "Unfortunately, Android Keyboard (AOSP) has stopped.", I can't set up my phone, and I am about ready to throw this thing at the wall!!!!!1!
A: Calm down. Breathe. I know it is annoying and gives you headaches.
Just reboot into recovery (using the key combo), and flash keyboard_patch.zip, attached to this post.
Q: Whenever I browse the web in Chrome, my phone goes berserk! It slows down, shows me black screens then the lockscreen, etc.
A: Don't use Chrome. The stock browser is about as good and doesn't wreak havoc to our device. However, this is replaced when you flash a larger Gapps package. I recommend using Nano and installing what you want instead. Just wipe system, flash ROM, Nano, keyboard_patch.zip, and reboot. Alternatively, you can use Opera, which has everything Chrome has except Google account bookmark sync and bloat.
Q: I have one of the following issues:
Calls don't work. They reboot or say "Cellular network not available."
When I turn on my device, I don't have a data connection.
A: You flashed the wrong build. Flash anything after 20160126 and those issues are fixed!
Q: My battery life is bad.
A: Here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Understand that lower signal = shorter battery life.
Settings > WiFi > Menu > Advanced > Keep WiFi on during sleep > Only when plugged in.
Settings > WiFi > Menu > Advanced > Always allow scanning > Off.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Q: After 30 minutes of my phone's screen being off, WiFi turns off. I just can't seem to shake this bug!
{
"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"
}
That is called "Doze", it is a built-in feature added in Android to attempt to save battery. Jerry Hildenbrand did a good job explaining this at Android Central.
You can configure this using [root] Naptime, but it is a rather advanced tool.
Q: My keys stopped working! What did I do wrong?
A: Disable Sweep2wake in the "Advanced Settings" app. That tweak is cool, but not yet stable enough for daily use.
Q: How do I make things smaller?
A: Settings > Display & lights > LCD density.
Thankfully, they fixed the alignment bug, so you no longer need to edit your build.prop.
The larger the number, the larger things will be, and the smaller the device will identify as.
240 is the default. The 4.5 in (11.43 cm) device is recognized as a measly 3.89 in (9.87 cm). Friends don't let friends stay on 240 DPI.
Technically, the Celox has a DPI of 207, but apps work best with multiples of 20.
I personally recommend 200dpi, which makes the device identify as 4.66 in (11.85 cm). It is quite nice.
However, with a non-standard DPI (standards are 120, 160, 240, 320, 480, and 640), it can cause scaling issues like blurriness.
Q: Should I use EXT4 or F2FS?
A: I use F2FS. F2FS is safer for your data, writes faster, and is actually designed for flash memory (it is called Flash-Friendly File System), unlike EXT4, which is made for a hard drive. However, some people encountered issues with F2FS and the Play Store.
EXT4 is tried and true, and is still relevant.
Q: Why does my camera keep crashing?
A: In the Advanced Settings app, check "Force low-power flash".
Q: I get random reboots. I see the Samsung logo, then a black screen! Grr!
A: At the time of this writing, 1/26 (sometimes 1/27) is the most stable. Try flashing that.
Q: How do I remove the pesky # on the status bar?
A: Install this Xposed module, or it is also a part of this all-in-one tweakbox by the same developer.
Q: Are there any cool features in this ROM/Kernel?
A: Yes, there are more features in this than the usual CyanogenMod Celox kernel. Some features are still being worked on and are a bit unstable, but testing and fixing is welcome on our GitHub repo!
We have, so far:
Wake/Sleep:
sweep2wake
doubletap2wake
doubletap2sleep
pocket detection (enable in Kernel Adiutor)
Click to expand...
Click to collapse
Miscellaneous:
Backlight notification (the keys light up like the LED indicator we never had)
F2FS support
Screen undervolting to -500mV
Low-power flash
zRAM (compressed RAM)
Magically added more RAM: Now we have 834MB.
Click to expand...
Click to collapse
CPU general
Overclock to 1.83GHz
Under/Overvolting
A democracy of governors (see below)
GPU can be overclocked to 320MHz
Click to expand...
Click to collapse
CPU Governors:
Bold are considered (mostly) stable.
hyper
badass
conservative
gaming
interactive
interactiveX
lazy
lionheart
minmax
ondemand (the default)
performance
powersave (though this just locks at the minimum frequency)
sakuractive
samsung
scary
smartassV2
uberdemand
userspace
wheatley
Click to expand...
Click to collapse
I/O Schedulers:
bfq
cfq
deadline
noop
row
Click to expand...
Click to collapse
If you want more, request it!
Or... even better, contribute to the kernel on Github.
Q: Why can't I configure my CPU governors?
There was a bug in the 2/16 build that added governors, but they had issues with case-sensitivity. Flash 2/22 or newer and you get governors and configuration.
Q: When will we get an update?
A: Be patient! Or build it yourself. Don't forget that some people have lives, and some people don't have lives but still aren't going to constantly update.
I will update this with more questions and answers.
Please don't quote this whole thing. Just mention @Easy_as_Pi_3.14 and I should respond quickly. Or don't, I am subscribed to this thread and love to answer questions.
Easy_as_Pi_3.14 said:
Q: My battery life is bad.
Sorry, this isn't the best ROM for battery life. That hasn't really been hammered out yet.
However, here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Click to expand...
Click to collapse
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT
cameraddict said:
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT
Click to expand...
Click to collapse
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
David (not even gonna try to spell his username, too late at night) was also comparing his battery life to 4.4 AOKP. I have always heard that AOKP is amazing on battery life.
Update, here is my battery life. The Doze part was me using my S3 when this was on my bed, and then finally watching The Force Awakens. (PS: Great movie!)
And that is in airplane mode the whole time.
The rest was mostly me web browsing or watching a YouTube playlist.
Sent from my SGH-I727 using Tapatalk
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Nope. There may be Yes, there is an Xposed module for that. See two posts down.
Sent from my SGH-I727 using Tapatalk
Easy_as_Pi_3.14 said:
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
Click to expand...
Click to collapse
Yeah, I get pretty good signal here. I live in a major city. :good:
But about 8 hours of that was in an area of low signal. Also, my Doze usage was for nearly two days! And I didn't baby the phone. I just used it for messaging/calls/email and a few searches, and my calendar and updating a few apps in that time. When I plugged it in this morning I had hit 48 hours with 1.25 SOT with 4% left. I could have gone another few hours if need be.
My average SOT time is closer to 2.5 hours with about 24 hours standby (Doze). I've gotten as high as about 4 hours SOT with about 18 hours standby. I've already run a high drain test, SOT almost at 100% of the time, it averaged about 20%/hour. So at that rate the device would last for about 5 hours. But that is not average usage. My high usage of 3-4 hours with 18 hours standby is a better metric. And by all standards, this is excellent battery life for a device with an 1800mah battery without battery saving features engaged!
Oh, and my Doze usage last night was at 0.9%/hour
tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Yep, there is an Xposed mod for that! Disable su indicator (CM12) or in his all-in-one here.
I updated the Q&A. Thanks for asking that question!
@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/
javelinanddart said:
@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/
Click to expand...
Click to collapse
For short, call me @π.
Or, 355/113 will still get my attention.
Governor Explanations
I found this interesting thread about different governors, how they work and how to tweak them. Thought some might find it interesting:
@bryan2894, I noticed that the Show CPU usage in Developer options is blocked by SELinux.
I know it is silly, but here is the message:
Code:
type=1400 audit(1456274524.501:678): avc: denied { search } for pid=743 comm="ndroid.systemui" name="3846" dev=proc ino=31386 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
Deleted
Deleted
@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.
Couldn't find it, but is there power menu options to add screenshot?
tommyguns818 said:
Couldn't find it, but is there power menu options to add screenshot?
Click to expand...
Click to collapse
It is there already for me.
However, I found it easier to either use the key combo (volume first helps) or downloading an advanced file manager (my favorite), open Now On Tap (long-press Home in virtual keys, Menu or Search if I recall correctly on touchkeys), hit the share button, then use Save as.
Sent from my SGH-I727 using Tapatalk
Easy_as_Pi_3.14 said:
@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.
Click to expand...
Click to collapse
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.
javelinanddart said:
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.
Click to expand...
Click to collapse
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk
Easy_as_Pi_3.14 said:
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hmmm... I've had that before as well, but I do not recall having it on hercules (although I'm on CM11)
I had it on T769 (Candy 5.1)
So maybe it's a LP+ Issue?
Does anyone remember having it from before LP?