Develop Bugs

mssmison did it!: CyanogenMod 5.07 test 3. for kaiser!

wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680

could someone resize it to 240x320 please? cant wait to try this

Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone

So how is it? I'm too lazy to install it.

Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.

just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick

nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..

The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.

kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop

Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.

i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?

Can't get wifi to work with updates, which one should I need?

kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.

Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.

Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.

Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.

kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)

kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/

I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?

Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)

[BOOST] Give your Desire a REAL boost! [Root required] [Batterylife + performance]

This tutorial has been written for the XPERIA X10. But it should also work on other devices. Official thread can be found here. Please report if this works on your HTC Desire. Many thanks. Before even trying this, make a Back-up of your current ROM!
Click to expand...
Click to collapse
[Compatible with 2.1, 2.2.1 and 2.3.x]
[Warning, these apps are NOT paid! Only setCPU is paid, you can get it from the Android Market!]​
-- You need to root your Desire to use these apps! --
[/
If these simple Android Market apps, cause any problems on your device it means you've got something unstable installed on your device! I never had problems with Autokiller, setCPU and AutoRun Manager on any ROM.​
Hey,
In this thread I will show you how to get a REAL boost on your HTC Desire! This method could also improve performance and battery life on any other handset. This is compatible on Android 2.1, 2.2.1 and 2.3.x. (This way of boosting performance is without Systcl config! I suggest you to uninstall Systcl config, since it doesn't improve anything for me (and maybe for more persons here).
This method made me lose 0-2% in 9 hours on WolfBreak his Cyanogenmod 6.1.3 and ALL 2.1 ROMS! These simple apps, did improve my performance and battery life!
Lets get to the point
Download this and this package, put in on your phone and install them!
Lets config it now
Open Autokiller.
Go to the tab Memory limits.
Now put these configuration into the 3 boxes. (If these values cause problems you can better uninstall AutoKiller. Lower values are almost android default )
Hidden app: 150
Content provider: 160
Empty app: 170
Now press on Apply.
(Don't put these values listed above higer. If you do your device can start to malfunction)
Now press on the Menu button on your Device and tap on Settings. Now make sure Apply settings on boot is turned on! After turning it on, press on Advanced system tweaks. Now make sure that Battery and Memory management are turned on!
Exit Auto Killer by pressing the menu button and reboot your device.
---------------------------------------------------------------------------------------------
Now open Autorun Manager.
Now make sure every service that is listed in the tab Basic you don't need is turned off! Make sure you only turn off things in the tab Basic! After doing that, exit Autorun Manager with the Menu button and reboot your device.
---------------------------------------------------------------------------------------------
You don't have to buy setCPU. In this way it will only save some battery when your screen is turned off. It's to you to buy it if you want to save a little bit of battery. This configuration only effects you device when your screen is turned off. Don't expect with this setCPU very big changes!
The settings here below won't cause any lag when coming from sleep (atleast for me). Even with heavy apps.
[To get the XDA-free version of setCPU take a look at this post. Credits for telling this are going to DooMLoRD]
This step has a payed app. You can buy it from the Android Market. The app is called ''setCPU''.
Buy setCPU from the Android Market. Now open it and do the following:
Tap on Show Other Frequency Sets and tap on the list on Nexus One/Snapdragon [QSD8x50]. Put
Now press left in the corner on the tab Main. Put in the scaling bar the maximal frequency on 998MHz. Now put the minimal frequency on 245MHz.
Now press on Scaling and choose out of the list Ondemand, after pressing on Ondemand turn ''Set on Boot'' on.
Now press on the tab that you can find next to Main. It's called Profiles. Make sure that ''Enable'' turned one and Notifications turned off. Then press on Add Profile. In the Edit Profile window you have to put the following settings:
Profile: Screen Off
Max: 384MHz (Don't put it lower or it can cause malfunctioning!)
Min: 245 MHz
Scaling: powersave
Priority: 100 (High)
Then press Save.
Then reboot your device and enjoy!
---------------------------------------------------------------------------------------------
Your Desire is now fully optimized with a few simple apps! Not only the battery but also the performance! And... Don't forget to press the ''Thanks'' button instead of saying Thanks in this thread
Have fun!
Regards,
PlayGunsta

Does this really work/helps ? anyone tested ?

nickislauw said:
Does this really work/helps ? anyone tested ?
Click to expand...
Click to collapse
Works for the x10 (Official thread: http://forum.xda-developers.com/showthread.php?t=1040497)
There is not much diffrence between these two devices. And all apps are also downloadable in the android market. So it couldn't (shouldn't) cause any problems at all.

i thought those on CM7 cannot use setcpu and set power profiles.

PlayGunsta said:
Works for the x10 (Official thread: http://forum.xda-developers.com/showthread.php?t=1040497)
There is not much diffrence between these two devices. And all apps are also downloadable in the android market. So it couldn't (shouldn't) cause any problems at all.
Click to expand...
Click to collapse
okay, but i got netcounter, pinghchat, whatsapp in the service window in autrun app.. i should not thick them right >

nickislauw said:
okay, but i got netcounter, pinghchat, whatsapp in the service window in autrun app.. i should not thick them right >
Click to expand...
Click to collapse
Don't tick the services you need/use and they will not be affected.

PlayGunsta said:
Don't tick the services you need/use and they will not be affected.
Click to expand...
Click to collapse
okay so what should i thick? it says the following in the basic tab:
- Adfree
- Download Manager
- Java-Box
- Netcounter (app to check my data in MB^^, guess i dont need to disable it)
- Pingchat
- SetCPU
- SMS Backup & Restore (to backup my sms for another rom)
- Tweetcaster Premium
- Whatsapp
So please tell me whats safe ?
Bedankt!
EDIT: and i do not have "powersave" governor in the screen of profile only ondemand, userspace, and performance..

I guess you can disable these ones without problem:
- Adfree
- Download Manager
- Java-Box
- SMS Backup & Restore (to backup my sms for another rom)
- Tweetcaster Premium

PlayGunsta said:
I guess you can disable these ones without problem:
- Adfree
- Download Manager
- Java-Box
- SMS Backup & Restore (to backup my sms for another rom)
- Tweetcaster Premium
Click to expand...
Click to collapse
Ok thanks !

Ddddddddddddddddd

Would anyone know if blocking the Gmail app from starting using autorun cause any issues (if it is blockable)?
I like to use to the HTC mail app for all my email addresses and Gmail cant be uninstalled.

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets​
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2​
Difficulty Easy - Controlling app 'net Access​
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3​
Difficulty Moderate - SD cache/readahead tweaking​
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4​
Difficulty Moderate - Overclocking​
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5​
Difficulty Advanced - How Android Manages Memory/apps​
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6​
Difficulty Advanced - Managing Apps that auto-start on boot​
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any BLAC-specific tweaks that others should be made aware of!

Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).

ThaiDai said:
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
Click to expand...
Click to collapse
I'm sure there are more as well... These are just the ones that I found made the most difference on my device.
I'm also curious about the minfree setting. I've only tried a few settings, they seem good. I haven't done any drastic number changing, it seems like changing these values should be done with a lot of caution and testing. There are definitely some values that should not be touched and others that can take some more fudging with numbers .

Added Topic 3 and Topic 4 to startup.txt and rootfs.img.
Just booting. Let's see if this is stable.
Software options I do not test now because I only test the new versions now. So specific app optimization only necessary when ThaiDai Android Loader and installation procedure reaches v2
Ok, boot ok, started Android (NeoFROYO build(, will tell tomorrow if stable.
If so I will use this options as standard for Blacky and I will add software like Droid firewall.
Thanks and good night

Update - I redid topic 4, feel free to re-read it.

Thanks
Enviado desde mi FROYO BLUE CWM1.9 usando Tapatalk

Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?

john_matrix said:
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
Click to expand...
Click to collapse
No clue. What does that have to do with the Speed Improvements thread?
I'm guessing you tried and it didn't work? What APK!?!
I guess I don't really follow your train of thought. Does sqshfs'ing and odexing an APK make it run faster...? I'm pretty new to Android in general. Never even used a native Android device .

http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630

farukb said:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
Click to expand...
Click to collapse
I still don't get what that has to do with our builds. ODEX and DEODEX have nothing to do with our builds... That stuff only applies to native devices, or builds that are ported from native devices (I would think).
Perhaps I'm missing something here... please tell me if I am .

Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.

ThaiDai said:
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
Click to expand...
Click to collapse
LOL!
Epic.

OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it

x12CHRIS18x said:
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
Click to expand...
Click to collapse
Did you make the choices in the script, or did you just exit the script?
You have to make sure ScriptManager is running as root too. There's a setting for it. "Browse as root" - make sure that is enabled. You won't be able to see /data without browsing as root.
...You have a TouchHD? I always thought you had a RHOD, lol.

[ROM][ICS 4.0.3] [27.05.2012] HeroICS v3

Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3

If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0

Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'

CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.

1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?

lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?

Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...

lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...

Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.

lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers

WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.

lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?

1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.

Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support

Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.

Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?

Thanks lost, will try your radio, im on .14 atom

Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?

lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!

Come on people.. test the build!

[Q&A][UNOFFICIAL] CyanogenMod/LineageOS

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?