LeoLawliet presents..
- Codename LightningBolt -
Balanced tweaks for everyday use
\/ Please read if you're new to this \/
Before you continue, please don't assume the tweaks don't work for you.
Chances are your device might or might not support it, not all phones are the same..
I myself test the tweaks before releasing updates, lately I've only been able to test on ICS & JB.
With that said keep in mind if you use GB and plan on flashing these tweaks,
GB support hasn't been confirmed yet. YOU'VE BEEN WARNED!!
If you don't understand what these tweaks do, please DO NOT flash any of them..
the last thing I wanna hear is "your tweaks don't work" okay..? They work..
I have done what I could so cut me some slack guys.. I have a life too
and can't be here holding your hands throughout every step of the way..
that's not fair to me. I've tested and put together the tweaks,
I've written up a thread for the tweaks with two other reserved posts,
I published the tweaks, I wrote instructions, and I kept things updated on a regular basis.
All of this and I haven't even asked for a single donation, I'm doing this for free.
So I am asking you all nicely, please don't give me a hard time with the tweaks.
I've already explained how it all works, just read the OP it's all there..
- Brief Introduction -
What Codename LightningBolt is
These are CWM flashable zips containing the latest tweaks I've been using on my ROMs,
mainly meant for a balance of performance and good battery without pushing your device too far past its limits.
I've only had a chance to test these tweaks on LG myTouch 4G & LG Optimus L9 and LG G2x (only one it didn't work on)
but should work just fine with any device running ICS or JB that need an all around boost in performance and battery life and performance.
At first I wanted to increase performance for gaming purposes on one of my low-end devices, that's what got this started.
This set of tweaks made my myTouch a better gaming device than the rest I own and it's only running on a single core,
emulators such as n64oid would lag for me back then but for the most part I can now play games like Super Smash Bros smoothly without lag,
as well as Lumines and Ridge Racer on PPSSPP.
Click to expand...
Click to collapse
- Installer differences explained -
Which is which, and what does what
Buildprop - Only installs the build.prop tweaks I handpicked
Engine - Installs the basics. init.d scripts, xbin scripts, custom add-ons, Smart Launcher, no build.prop tweaks included
Engine min - Minimal version of Engine, does not include Smart Launcher & custom add-ons
AIO - All-In-One installer is just like the Engine, except it includes the prop tweaks as well.
AIO min - Minimal version of All-In-One, does not include Smart Launcher & custom add-ons
[8]AROMA - The latest installer, which includes a GUI that allows you to select what you would like to install
Click to expand...
Click to collapse
- Requirements -
What you will need:
Root (obviously)
Android device running 4.X.X firmware, stock or aftermarket both work
Firmware 2.3.X has not been tested thouroughly,so.... GB NOT SUPPORTED!!
At least 14mb of free space in /system/ partition & 2mb in /data/
Your device must have init.d support, if your kernel doesn't support it install this
Your device must also have sysctl support, that's built into the kernel
At least CWM5 recovery, haven't had a chance to test it on TWRP Recovery
Latest busybox installed, get it here
Android Terminal Emulator, you can get it here
Make a nandroid backup, just in case anything goes wrong
Click to expand...
Click to collapse
- List of Tweaks -
The included tweaks are listed below:
Smart Launcher included (in v1.7 you can uninstall it)
boost in performance (many optimizations and performance tweaks)
swap2cache terminal script creates a 64mb swapfile in /cache with swappiness set to 40
swap2data terminal script creates a 128mb swapfile in /data with swappiness set to 40
swap2emmc terminal script creates a 90mb swapfile in /emmc with swappiness set to 90 (probably fastest)
increased responsiveness by increasing touch sensitivity and forcing GPU to render touches
better battery life (disabled sleepers)
faster boot (rapid boot build.prop tweaks)
I/O scheduler tweaks (deadline only for now)
sleeper tweaks (this saves battery)
hardware rendering tweaks (take full advantage of your device's GPU)
improved sdcard read/write speed (should be set at 2048kb readahead)
disables logger (slight performance boost, but disabled logcat)
zipalign on boot (optimizes apps to consume less RAM and run faster)
defrag on boot (sqlite database is wiped on each reboot)
renice tweaks to open some system apps faster, may consume more ram
disables journalism (slight increase in performance, might cause some instability in rare cases)
nice set of terminal scripts (see 3rd post for the list)
disables vsync (boost in performance, might cause glitching in rare cases)
tweaked ADJ & VM values
entropy tweaks included (significant lag reduction)
graphics rendering tweaks (better 2D/3D graphic performance)
video/music streaming tweaks
custom UI sounds (MGS4 based sound effects I found and converted to .ogg)
increased jpeg + video recording quality
call tweaks
cpuramcheck script to monitor CPU/RAM usage in realtime using the terminal emulator
Stabilized FPS through a build.prop tweak (might not be so stable, be warned. Thanks Pizza_Dox & LENAROX!!)
Click to expand...
Click to collapse
- When including Codename LightningBolt in your ROMs -
This is all I ask
If you would like to include these tweaks in one of your ROMs, just give proper credits such as
"Codename LightningBolt Tweaks by leolawliet"
and link back to this post somehow, they deserve a lot of thanks and credit for helping make this all possible.
Click to expand...
Click to collapse
- build.prop tweaks -
Use on whatever ROM you like, just copy & paste to your build.prop
(The build.prop tweak installer has the best handpicked already)
New build.prop tweaks
Code:
### LeoLawliet's new tweaks 9/15/2013 ###
# Misc Tweaks
debug.gr.swapinterval=0
debug.performance.tuning=1
dev.pm.dyn_samplingrate=1
persist.adb.notify=0
persist.service.adb.enable=1
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
qemu.hw.mainkeys=0
ro.min_pointer_dur=1
ro.sec.proximity.delay=0
sys.mem.max_hidden_apps=15
# Battery Tweaks
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
# Unlocks Screen using Menu Button
ro.config.hw_menu_unlockscreen=true
# Kernel Tweaks
ro.kernel.checkjni=0
# Ram Tweaks
persist.sys.purgeable_assets=1
# Kills Loging
ro.config.htc.nocheckin=1
ro.config.nocheckin=1
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
# Media Streaming Optimizations
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-record=true
# Camera & Media Tweaks
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.dec.jpeg.memcap=20000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=75
ro.media.enc.jpeg.quality=100
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.cam.preview.fps=25
ro.media.codec_priority_for_thumb=so
# CM9 Tweaks
hwui.disable_vsync=true
hwui.render_dirty_regions=false
# Voice Optimization
ro.ril.enable.amr.wideband
# Better Telephony Settings
ro.config.vc_call_vol_steps=15
ro.config.vc_call_steps=20
ro.telephony.call_ring.delay=0
ring.delay=0
ro.lge.proximity.delay=25
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
# Google DNS
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
# TCP Tweaks (might break WiFi)
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.hspda=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,163 84,256960
# Wireless Conection Tweaks (might break WiFi)
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.route.flush=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_fack=1
net.ipv4.tcp_mem=187000 187000 187000
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_rfc1337=1
net.ipv4.tcp_rmem=4096 39000 187000
net.ipv4.tcp_sack=1
net.ipv4.tcp_timestamps=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_wmem=4096 39000 187000
# 3d performance
persist.android.strictmode=0
ro.min_pointer_dur=1
ro.secure=0
# 16BIT Support
debug.fb.rgb565=1
# 16BIT Transparency
persist.sys.use_16bpp_alpha=1
# Graphic Tweaks
ro.product.gpu.driver=1
debug.gr.swapinterval=0
# Better scrolling responsiveness
windowsmgr.max_events_per_sec=90
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
# Better Touch Responsiveness
touch.presure.scale=0.001
# Dalvik Tweaks
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=122m
dalvik.vm.heapsize=122m
dalvik.vm.dexopt-flags=m=y,v=n,o=n
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.lockprof.threshold=500
dalvik.vm.execution-mode=int:jit
dalvik.vm.jmiopts=forcecopy
dalvik.vm.dexopt-data-only=1
# Enable Qualcomm tile rendering (Hardware Rendering)
debug.enabletr=1
persist.sys.composition.type=gpu
# enable harware egl profile
debug.egl.profiler=1
# FPs Booster
persist.sys.NV_FPSLIMIT=60
persist.sys.NV_POWERMODE=1
persist.sys.NV_PROFVER=15
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_STEREOSEP=20
# Graphic Optimization
debug.gr.numframebuffers=3
ro.min_pointer_dur=1
# Hardware 2D & 3D Rendering
hw3d.force=1
hw2d.force=1
# Pro-Tuned ADJ 1.2 by LENAROX.
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=4
ro.PERCEPTIBLE_APP_ADJ=3
ro.HEAVY_WEIGHT_APP_ADJ=2
ro.SECONDARY_SERVER_ADJ=1
ro.BACKUP_APP_ADJ=5
ro.HOME_APP_ADJ=6
ro.HIDDEN_APP_MIN_ADJ=7
ro.EMPTY_APP_ADJ=15
#Ultimate Assassin Mode!
#ro.SECONDARY_SERVER_ADJ=15
#ro.HIDDEN_APP_MIN_ADJ=3
# Qualcomm Display Settings (Qualcomm devices ONLY!!)
com.qc.hardware=1
debug.qc.hardware=true
debug.qctwa.preservebuf=1
debug.qctwa.statusbar=1
# Rapid Boot Technology 1.1 (Reduces bootup time)
persist.sys.shutdown.mode=hibernate
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
# Rendering Tweaks
debug.composition.type=gpu
debug.egl.hw=1
debug.enabletr=true
debug.overlayui.enable=1
debug.qctwa.preservebuf=1
debug.performance.tuning=1
debug.sf.hw=1
dev.pm.dyn_samplingrate=1
hw3d.force=1
ro.config.disable.hw_accel=false
ro.fb.mode=1
ro.sf.compbypass.enable=0
ro.vold.umsdirtyratio=20
persist.sys.composition.type=gpu
persist.sys.ui.hw=1
video.accelerate.hw=1
# Sensor Sleep Control
ro.ril.sensor.sleep.control=1
# Smoothens UI
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
### End of LeoLawliet's new tweaks 9/15/2013 ###
- Disclaimer & Warning -
If you mess up your device using these tweaks, it's not my fault
As usual, I will leave a disclaimer.
I will NOT be held responsible if this causes any damage to your device.
You are responsible for making a nandroid backup
in the case that a bootloop occurs.
Click to expand...
Click to collapse
\/ Credits on second post \/
Credits
Credit goes out to these guys
Pizza_Dox - for hc & gm scripts, 02SDCardAccel, 08IO, 20vmlt, 82Sleepers, some build.prop tweaks
Chainfire - for some scripts. 01-GPU_touchrender, libncurses.so
ImbaWind - for Adrenaline Boost script
Spex - for some of the Fluid Engine tweaks and some build.prop edits, I started out with his collection and kept tweaking it and changing it up every now and then it. Thanks!
zeppelinrox - for sclean script
LENAROX - for 20vmlt, FPs Stabilizer, ADJ values, avcore, and you made cpuramcheck script possible. Thanks
defiant07 - for helping create the build.prop tweak installer script
BSDgeek_Jake - For the motherload of AD-blocking host files, best and largest database I've seen so far
And once again because I can't tell you how annoying it is for someone to screw up their own device for not following instructions carefully and then blame someone else.. I will NOT be held responsible if this causes any damage to your device, you are responsible for making a nandroid backup in the case that a bootloop occurs.
Enjoy
Sent from my LG-P769 running PenberRom5 using Tapatalk 2
Terminal scripts & changelog
- Terminal Scripts -
Type "su" then..
Code:
avc
^ avcore script by LENAROX, it has built in instructions.
Click to expand...
Click to collapse
Code:
boost
^ instant ram boost
Click to expand...
Click to collapse
Code:
cpuramcheck
^ check CPU usage and RAM usage in realtime
Click to expand...
Click to collapse
Code:
gm
^
modded version of boost script, also kills media server
Click to expand...
Click to collapse
Code:
hc
^ hyper cola v2.6 tweaks by Pizza_Dox, reboot to deactivate and save battery. This is meant to give a boost for gaming
Click to expand...
Click to collapse
Code:
sclean
^ wipes cache & dalvik-cache then reboots your device, I recommend running this at least once a week to speed things up if your device is slowing down over time
Click to expand...
Click to collapse
Code:
swap2cache
^ creates 64mb swapfile in /cache/swap/ with swapiness set to 40 (virtual RAM, risky)
Click to expand...
Click to collapse
Code:
swap2data
^ creates 128mb swapfile in /data/swap/ with swapiness set to 40 (virtual RAM, risky)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
____________________________________________________________________________________________
- prop tweak installer explained -
- The change that was implemented to the build.prop tweak installer script mainly effects
the creation of the backup of build.prop, then applies the tweaks to build.prop while leaving
build.prop.PrePenberEngine backup file untouched. All it does is if it detects build.prop.PrePenberEngine
it won't make a new backup, thereby preserving the original backup while tweaking the build.prop that will
end up being used. It does NOT "cancel out the installer script" from doing stuff to the build.prop and this time
it should prevent duplicate entries. (edited, sorry for the misunderstanding and thank you for clarifying this defiant07).
- Also stated by defiant07: "Furthermore, there was some lack of attention to detail
on my part in the suggestion because I was focused solely on not having the backup
overwritten when your users update (which was the concern expressed in the user's
post that gave me the idea for the suggestion). I was wrong in that the change I suggested
does not totally eliminate the need to restore the build.prop backup because it will
still add stuff the build.prop. Although this is not really a problem it would cause duplicate entries."
- The best way I can explain it is basically his new code will make it so if it detects
build.prop.PrePenberEngine it will restore build.prop.PrePenberEngine and then
add all the entries OR if it does NOT detect build.prop.PrePenberEngine it will make
a backup and then add all the entries. This should ultimately make it so the user
does not have to touch the build.prop or build.prop.PrePenberEngine when updating
and it will avoid duplicate entries...the zip should now do everything for you guys,
thanks goes to @defiant07 for this.
Click to expand...
Click to collapse
____________________________________________________________________________________________
Progress in general ~12/21/2013~
I will no longer update the changelog through the OP, it will be accessible from the AROMA Installer.
This makes things easier, and reduces the clutter on the thread, also encourages other to try the tweaks.
~What's new? ~
Update on progress - 12/21/2013:
NEW!! AROMA Installer added, includes a GUI which allows you to select the tweaks you want installed
NEW!! Added swap2emmc script
NEW!! The build.prop tweak installer script still needs to be worked on, any help with that would be great
NEW!! I will no longer be updating the changelog on the thread, but instead in the AROMA Installer (much easier)
Major Update - Project renamed - 11/15/2013:
NEW!! Every installer now first removes old files before flashing new ones
NEW!! Every installer also individually sets permissions for each file
NEW!! Updated sysctl tweaks! (probably my favorite part of this update)
Made uninstallers for both PenberEngine and Codename LightningBolt (still BETA, youve been warned!!)
Removed fluid engine script, merged some of the code with main Codename LightningBolt script
Update on progress - 10/29/2013:
NEW!! MGS4 UI sounds and notifications, I could have done a better job converting the files.. that's on my to-do list
NEW!! Added sysctl tweaks
NEW!! Added custom host file for AdBlocking
NEW!! Added sclean as xbin script, I recommend running this once a week for a quick tuneup
EXPERIMENTAL!! Added latest fluid engine script (98fluid_engine init.d script only!) Let's see how this plays out
Tweaked/Updated a couple of init.d scripts (97PenberEngine_Main/98PenberEngine_LagReduction/99PenberEngine_Renice) still testing but working well
Prop tweak installer should be working fine now
Updated the updater-script for every installer, neater looking installation and fixes applied
Made sure installer individually sets permissions for each init.d script
Update on progress so far - 10/13/2013:
I updated the build.prop tweak installer. The script within it as well.
I got a nice boost all around with the prop tweaks alone.
I also updated the init.d scripts, please remove the old ones
before installing this update and please restore your old build.prop
as well. If you don't it might cause problems with performance.
I also made sure the all-in-one installers applied the
prop tweaks properly, they're all working fine for me
Announcement.. - 10/12/2013:
This tweak package is said to work well alongside CrossBreeder
But I myself haven't confirmed it, feel free to try it out,
it hasn't caused the other users any problems as far as I know.
Announcement.. - 10/07/2013:
It has come to my attention that these tweaks aren't exactly noob friendly,
don't take chances if you don't understand any of this,
not everyone will get the same result
or even know how to fully make use of it.
If you no comprende don't flash,
I'm not responsible if this messes up your device,
always make a backup beforehand.
Current progress on - 10/06/2013:
You can find the installers >>here<<
So far things seem smoother, RAM handles better, I've included avcore
to test out for a bit (thanks LENAROX, I hope you're okay with me using this,
otherwise just ask me to remove it and I will)
and I attempted to include the older build.prop script in the newer engine
and AIO, also updated the updater-binary files with the one defiant07 made.
Click to expand...
Click to collapse
____________________________________________________________________________________________
Looking for the 9/3 build is it uploaded yet ?
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
Testing now..
just wondering about using CrossBreeder with this package? Also are you using V6SuperCharger because I see an installation marker which you get from installing V6 in your build prop extras?
Sent from my GT-I9000 using xda premium
Is this mod make difference on my Gnexus ? Or it is just for some old devices?
Xx_silenzer_xX said:
Looking for the 9/3 build is it uploaded yet ?
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
There isn't, I just decided to make the thread on 9/3
9/1/2013 is the latest.
RuffBuster said:
Testing now..
just wondering about using CrossBreeder with this package? Also are you using V6SuperCharger because I see an installation marker which you get from installing V6 in your build prop extras?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I use it sometimes, I would usually leave that line at the bottom of my build.prop. V6SuperCharger isn't included. I high'y recommend you don't use crossbreeder with this, it will conflict with the tweaks I've already added. This is like crossbreeder, it's a package of tweaks. You only need one or the other, otherwise too many conflicting tweaks could cause more problems than benefits.
okanb3 said:
Is this mod make difference on my Gnexus ? Or it is just for some old devices?
Click to expand...
Click to collapse
It made a difference on two of my devices, both different and not exactly high end. It helped with my LG Optimus L9 which is fairly new, not even a year old. Try it out and if you don't like it restore your backup.
Skimmed the zip's contents out of general curiosity and it seems like a pretty suspect, half assed haphazard hodgepodge to me . The problems are numerous ...
There are no usage instructions in your OP (for xbin scripts and it seems one of your init.d scripts requires user editing).
There is nothing in your zip that installs the build.prop tweaks you list in the OP.
Your turbo xbin script is totally empty, lol.
34dalvikcalc does absolutely nothing.
cpuramcheck will do nothing. EDIT - I am an idiot...this script does work as intended.
Those are the issues I noticed in five minute skim, but I imagine there are others.
BTW, why include three zipalign scripts???
defiant07 said:
Skimmed the zip's contents out of general curiosity and it seems like a pretty suspect, half assed haphazard hodgepodge to me . The problems are numerous ...
There are no usage instructions in your OP (for xbin scripts and it seems one of your init.d scripts requires user editing).
There is nothing in your zip that installs the build.prop tweaks you list in the OP.
Your turbo xbin script is totally empty, lol.
34dalvikcalc does absolutely nothing.
cpuramcheck will do nothing.
Those are the issues I noticed in five minute skim, but I imagine there are others.
BTW, why include three zipalign scripts???
Click to expand...
Click to collapse
Build.prop tweaks weren't applying with the installer, for that I apologize, so I decided to post them in the OP so users have the option to copy & paste whatever they like to their own build.prop. I still need to fix up the OP, it's still not 100% done. I've been testing these tweaks myself along with the help of other users, nothing bad has happened to either of our devices, in fact they like the boost they got from it. I can't say for sure that everyone will get the same results, but please keep in mind I've only had a chance to test it on 2 devices, both of which seemed to run better with the tweaks so I can't really say I'm noticing any problems other than some stuff I wanna remove. I like the engine the way it is, doesn't need stuff added onto it but I don't like the filesize and hope to shrink it down some more. If you got any suggestions to slim it down, shoot away I'm listening.
I was supposed to remove turbo but forgot, I noticed it wasn't working at all. It's getting replaced with Hyper Cola v2.6
The xbin scripts instructions, I'll get to it when I can write it up, just a busy night at the moment. Labor day weekend just passed and I'm getting back to work (actually at work as we speak) I'll write instructions along the way, my bad for not including them.
34dalvikcalc & cpuramcheck are working fine for me, do you have the latest busybox installed?
As for the question about the zipalign scripts, zipalign is needed while zalignx and zepalign do the zipaligning in their own ways, just not sure what other users preferred zipaligning with. There's a difference tho, I think zalignx is more detailed, at least I get to see what gets zipaligned or already was prior to running the script.
Any more feedback you or anyone can provide will help, I'll fix the errors just gotta point them out
İ cant fiash it.My phone is huawei sonic with CM9 4.0.4
Just some info, good job first off!
2nd - dalvik calc WONT work, its placebo (bad Unix), I made it for a Rom of mine or sth and it had some Unix issues, I even named it 34dalvikcalc, it's not 100% mine, I nodded it, and its originall creator was someone from another forum (can't remember) and it didn't properly calculate, so I fixed and popped in meh Rom, and LENAROXS fps stabilizer actually uncaps the fps limit, its a bad tweak, as higher fps than refresh rate causes some weird screen stutters and probs, besides we can't see past 60fps
I hope this project turns up good and I will look forward to trying, once again, Awesome job!,
Sent from my R800i using xda app-developers app
leolawliet said:
Build.prop tweaks weren't applying with the installer, for that I apologize, so I decided to post them in the OP so users have the option to copy & paste whatever they like to their own build.prop. I still need to fix up the OP, it's still not 100% done. I've been testing these tweaks myself along with the help of other users, nothing bad has happened to either of our devices, in fact they like the boost they got from it. I can't say for sure that everyone will get the same results, but please keep in mind I've only had a chance to test it on 2 devices, both of which seemed to run better with the tweaks so I can't really say I'm noticing any problems other than some stuff I wanna remove. I like the engine the way it is, doesn't need stuff added onto it but I don't like the filesize and hope to shrink it down some more. If you got any suggestions to slim it down, shoot away I'm listening.
I was supposed to remove turbo but forgot, I noticed it wasn't working at all. It's getting replaced with Hyper Cola v2.6
The xbin scripts instructions, I'll get to it when I can write it up, just a busy night at the moment. Labor day weekend just passed and I'm getting back to work (actually at work as we speak) I'll write instructions along the way, my bad for not including them.
34dalvikcalc & cpuramcheck are working fine for me, do you have the latest busybox installed?
As for the question about the zipalign scripts, zipalign is needed while zalignx and zepalign do the zipaligning in their own ways, just not sure what other users preferred zipaligning with. There's a difference tho, I think zalignx is more detailed, at least I get to see what gets zipaligned or already was prior to running the script.
Any more feedback you or anyone can provide will help, I'll fix the errors just gotta point them out
Click to expand...
Click to collapse
At least you are responsive and responsible in that you acknowledge and try to fix your problems . However, IMO you should not release stuff unless you fully test everything (try using debug ).
Regarding the build.prop stuff your OP states it's included (and I quote: "The tweaks included are listed below:")??? If you don't have the time to make a half decent, informative, and accurate OP, IMO you should wait and release the product when you do have the time...there's no rush, XDA will still be here tomorrow.
As @Pizza_Dox said 34dalvikcalc is totally flawed...it does nothing in Pizza Box too (which I looked at last night as well since you credited him). Do you know anything about bash/shell scripting??? Busybox version is irrelevant, I did not run any of your scripts (nor will I ever)...as I stated all I did was a 5 min skim, but just by looking at the code I can tell it is bad. If you cannot tell this code:
Code:
#!/system/xbin/sh
# The Dalvik Optimizer 1.0 by Pizza_Dox
mem=785624;
heapsize=0;
dalvik_heapsize=0;
dalvik_vm_heapsize="m";
setprop dalvik.vm.heapsize ;
# XDA: http://goo.gl/xEdOa
# Blog: http://androidpizza.blogspot.com/
# Email: [email protected]
is bad, you have no business releasing mod packages. What in this script leads you to believe it does anything productive??? Again try using debug.
As for cpuramcheck, you can really run that script??? I smell BS (unless maybe you have a magic rom of some sort???)...as previously stated, try actually testing before releasing. The major issue with this script is it is missing that good ole fashion required opening line - #!/system/bin/sh. So there is no way it will do anything for anybody (you included), lol. FAIL. EDIT - I was wrong...this script DOES function as intended...EPIC FAIL on my part.
Try actually learning some code instead of "borrowing" it all and you may avoid such issues :silly:.
defiant07 said:
At least you are responsive and responsible in that you acknowledge and try to fix your problems . However, IMO you should not release stuff unless you fully test everything (try using debug ).
Regarding the build.prop stuff your OP states it's included (and I quote: "The tweaks included are listed below:")??? If you don't have the time to make a half decent, informative, and accurate OP, IMO you should wait and release the product when you do have the time...there's no rush, XDA will still be here tomorrow.
As @Pizza_Dox said 34dalvikcalc is totally flawed...it does nothing in Pizza Box too (which I looked at last night as well since you credited him). Do you know anything about bash/shell scripting??? Busybox version is irrelevant, I did not run any of your scripts (nor will I ever)...as I stated all I did was a 5 min skim, but just by looking at the code I can tell it is bad. If you cannot tell this code:
Code:
#!/system/xbin/sh
# The Dalvik Optimizer 1.0 by Pizza_Dox
mem=785624;
heapsize=0;
dalvik_heapsize=0;
dalvik_vm_heapsize="m";
setprop dalvik.vm.heapsize ;
# XDA: http://goo.gl/xEdOa
# Blog: http://androidpizza.blogspot.com/
# Email: [email protected]
is bad, you have no business releasing mod packages. What in this script leads you to believe it does anything productive??? Again try using debug.
As for cpuramcheck, you can really run that script??? I smell BS (unless maybe you have a magic rom of some sort???)...as previously stated, try actually testing before releasing. The major issue with this script is it is missing that good ole fashion required opening line - #!/system/bin/sh. So there is no way it will do anything for anybody (you included), lol. FAIL.
Try actually learning some code instead of "borrowing" it all and you may avoid such issues :silly:.
Click to expand...
Click to collapse
cpuramcheck works..
The rest of whatever you said I'm ignoring, take your negativity elsewhere. Nobody likes a troll. Maybe if you actually tried something instead of immediately bashing on something, you'd see that it works..
I don't need your opinion, it looks like you're trying to discourage me, that's not cool. If you don't like this thread you don't have to stick around and be a troll.
Sent from my LG Optimus L9 running PenberRom5 using Tapatalk 2
leolawliet said:
cpuramcheck works..
The rest of whatever you said I'm ignoring, take your negativity elsewhere. Nobody likes a troll. Maybe if you actually tried something instead of immediately bashing on something, you'd see that it works..
I don't need your opinion, it looks like you're trying to discourage me, that's not cool. If you don't like this thread you don't have to stick around and be a troll.
Sent from my LG Optimus L9 running PenberRom5 using Tapatalk 2
Click to expand...
Click to collapse
My bad, I stand semi-corrected, cpuramcheck kinda sorta works. If you try and run it by doing su -c cpuramcheck (which is the way most bin scripts work...including the others in your mod package), it will NOT work...you will get a 'cannot execute' error. To make it work the user would have to manually invoke the shell, which is very odd to begin with, plus it is inconsistent with the other bin scripts you included. I doubt most users would figure this out. BTW, adding the standard opening line would eliminate the need for the user to call the shell manually. I'll call this one a wash as we are both right and wrong. EDIT: Okay, you are 100% correct in these regards...I am a donkey idiot...I tested it as an xbin script out of curiosity (with the text I stuck out I ran it in script manager, which required me to tell it is was a script, hence some of my comments) and it does work as intended...guess I need to learn more about bin and shell scripts...I will cop to my mistake and edit my previous post so people know I was wrong in this matter.
What you do NOT want to acknowledge your incompetence in regards to 34dalvikcalc so you choose to ignore my questions? LOL
I am not trying to troll you; just calling things as I see them [edit: (which is obviously wrong sometimes)].
If it discourages you from doing things you obviously have no business doing, then GOOD...it helps the quality control of XDA. XDA does NOT need another completely unoriginal mod package where the dev does not really/fully know what they are doing.
Ignorance is bliss; enjoy it, as it seems you are drowning in it...don't be mad I called you on your BS and lack of knowledge. Again maybe try actually learning some bash/shell scripting before you try to compile a mod package.
I held off on give this a one star rating, but your comments have confirmed my initial suspicions...sad and pathetic.
Have fun dragging down the overall quality of XDA and collecting undeserved thanks from the legions of silly crack flashers.
EDIT: Overly harsh...poor form on my part...many apologies. I will refrain from further commentary...I should have learned by now that if one has nothing good to say it is best to remain silent.
Is it compatible to use this mod on LG OPTIMUS G PRO?
Sent from my LG-E988 using Tapatalk 4
defiant07 said:
My bad, I stand semi-corrected, cpuramcheck kinda sorta works. If you try and run it by doing su -c cpuramcheck (which is the way most bin scripts work...including the others in your mod package), it will NOT work...you will get a 'cannot execute' error. To make it work the user would have to manually invoke the shell, which is very odd to begin with, plus it is inconsistent with the other bin scripts you included. I doubt most users would figure this out. BTW, adding the standard opening line would eliminate the need for the user to call the shell manually. I'll call this one a wash as we are both right and wrong. EDIT: Okay, you are 100% correct in these regards...I am a donkey idiot...I tested it as an xbin script out of curiosity (with the text I stuck out I ran it in script manager, which required me to tell it is was a script, hence some of my comments) and it does work as intended...guess I need to learn more about bin and shell scripts...I will cop to my mistake and edit my previous post so people know I was wrong in this matter.
What you do NOT want to acknowledge your incompetence in regards to 34dalvikcalc so you choose to ignore my questions? LOL
I am not trying to troll you; just calling things as I see them [edit: (which is obviously wrong sometimes)].
If it discourages you from doing things you obviously have no business doing, then GOOD...it helps the quality control of XDA. XDA does NOT need another completely unoriginal mod package where the dev does not really/fully know what they are doing.
Ignorance is bliss; enjoy it, as it seems you are drowning in it...don't be mad I called you on your BS and lack of knowledge. Again maybe try actually learning some bash/shell scripting before you try to compile a mod package.
I held off on give this a one star rating, but your comments have confirmed my initial suspicions...sad and pathetic.
Have fun dragging down the overall quality of XDA and collecting undeserved thanks from the legions of silly crack flashers.
EDIT: Overly harsh...poor form on my part...many apologies. I will refrain from further commentary...I should have learned by now that if one has nothing good to say it is best to remain silent.
Click to expand...
Click to collapse
Dude.. instead of bashing, you could encourage me to improve the package and fix things and give me pointers, you know.. give some insight but not if you're gonna be so harsh that it looks like you're attacking me.. did you even try the tweaks..? Clearly not if you keep assuming stuff, and even YOU provided false info. Why are you even giving feedback if you haven't even tried it and never plan on using it? You just THINK you know what you're talking about.. but look what happened, you automatically assumed one of my scripts was total BS and it worked.. maybe not the way you wanted it to work but it does in fact work as stated. You insult me saying I need to learn how to code, and then I correct you, and then you correct yourself.. what was that you said about me needing to learn how to code? The same goes for you, learn your stuff too so it doesn't look like you're pretending to know what you're talking about, cuz seriously it looks that way now. I'm learning at my own pace trying to teach myself so I don't bug and annoy anyone for advice but I'm not gonna pretend I know everything. You made your own self look like a complete moron, that was your own doing, not mine.
It's a tweak package seriously who starts crap over that? It's ridiculous. I can understand if you DID try the tweak package without making a backup and then you screwed up your device, at that point I'd feel bad I'd apologize and try to help make things right, but that's not even the case here. You didn't even flash anything so why are you even talking like you tried it and it killed your phone? -____-
I thought this was supposed to be a friendly community, I wouldn't even think of calling out anyone to speak to them the way you've spoken to me, just honestly speaking you came off as really rude to me and I felt some kind of way about it.. it's difficult to look at it any other way.
Also.. how many other developers and users post up stuff on a daily basis that isn't even a final product? Tons of users have done it, and for their own reasons. So why the hell single me out like you did? Do you talk to everyone on XDA this way? Have some respect and consideration for others. Maybe you had a bad day and wanted to take it out on someone, but I don't know that so I can't assume and won't assume, but your behavior was definitely out of line and not normal. I'm not bashing you, nobody is. You made your own self look like a troll. You had no legit reason for behaving the way you did towards me in the first place, you do not know me from a hole in a wall. At least I'm not posting anything that breaks radio/battery indicator/GPS/WiFi/data/Bluetooth/etc. At least I posted something, I'm not someone who announces something BIG that gets everyone all hyped up only to never release it. If anyone feels adventurous, and knows what to do with these tweaks, they will check it out. If someone doesn't understand any of this, they're in the wrong place and I can't be blamed if they screw up their device because they SHOULD be aware of what they're doing. If users see some obvious mistakes in any of the things, I encourage them post their findings in the thread. You did that, BUT you were in fact very rude about it. Regardless if it points a person in the right direction you just can't speak to anyone like that, some people will take it some kind of way, like I did. Do you see where I'm coming from with this? We have this community so we could all support each other, help each other out somehow, not discourage others. I've seen noobs turn out to become great developers, I have mad respect for them for the effort they put into everything they did and for how far they've come along. You gotta start somewhere but if you sit around doing nothing, not interacting with others, how do you hope to learn anything? I may make mistakes along the way, as well as other users, but ultimately we learn from it. When you learn from a mistake you learn not to repeat it and how to avoid it.
All I wanted to do was create a package with my preferred tweaks, to flash over any ROM update I install, without having to do it all one-by-one all over again, that was the whole point of this package. And the point of this thread was to share it and spot out anything wrong with it and to improve it. I welcome feedback and insight to improve the package, I encourage it because I want something that would benefit everyone. I just would appreciate it if the person came to me in a nice way. Honestly speaking, I can't remember the last time anyone spoke to me this way on XDA. I'm shocked, everyone else here is so nice and always willing to point me in the right direction, but half the time I don't wanna ask because I don't wanna be bothersome so I look for a way to figure things out on my own so I could avoid stuff like this.
Also.. "Credit goes out to these guys" http://forum.xda-developers.com/showpost.php?p=45273653&postcount=2
^ If you read the 2nd post you'll see I'm not taking any credit. You'll see I have told users to thank the credited developers on the 2nd post and it's been that way since I started this thread.. I never intended to take credit for the work of someone else, and really I haven't.. it's all there.
I should also mention I started that OP post on one of the threads for one of my ROMs and it had been copied over from there and changed a bit, I didn't thoroughly look through everything written the first time around, I didn't intentionally try to mislead anyone, and if anyone felt that way then I apologize and I corrected the post.
Another thing I wanted to say, I have been testing these tweaks for some time, along with the help of others so I didn't do this alone, I've had help along the way. I've even asked them to test them on the ROM updates I posted and on their other devices. No complaints. If I didn't feel confident that these tweaks would help others, if these tweaks haven't helped me in the past, I wouldn't have felt the need to share anything with anyone. The last thing I want right now is to cause someone's device to stop functioning, I would never want that to happen to anyone. The disclaimer states that I warned users to make a backup first before they try anything, that's common sense for anyone who has a custom recovery installed. If anything goes wrong, they have the option to restore their backup. I've been wanting to package these tweaks together for a while now, and just recently started learning how to put together flashable zips, which I had always wanted to learn how to do but never really got a chance to look into it till recently since I have access to PCs at work at any time now. The tweaks are working just as described for the devices I have tested them on (except LG G2x), and nothing conflicts, for me at least. I don't have a super phone, just a dual core device running PACrom JB 4.3, and that's not even so stable on it's own to be honest.
As for the build.prop tweaks I wanted to include, I'm gonna explain. At first I did include them, I had a built-in script that WAS supposed to install them, I double checked everything from the script to the updater script, but for some odd reason I couldn't get it to work right and didn't wanna frustrate myself over it so I corrected it by instead posting the tweaks to copy and paste from the OP and in my opinion that is the better way to go with the build.prop tweaks because they don't always work on every device and you wouldn't have to install them all at once. This gives users a better chance to single out the tweaks that don't work for them, for the sake of avoiding bootloops & such. I tested them on my LG G2x a while back and didn't get the results I wanted (but that phone always had issues with whatever I tried doing with it). This won't work the same for every phone.
I just didn't like how you came off towards me, it could've been handled better. It's not even that I wanna ignore what you said about the 34dalvikcalc script, you angered me and it didn't seem like you were trying to be helpful, instead it just seemed like you were trying to pick on me. I took a look at 34dalvikcalc and I'm gonna exclude it from now on. Not looking for anything to replace it with, at this point I'm gonna slim down the installer and exclude some of the stuff. I was gonna remove the script but you really didn't have to push things that far.. the least you could've done was send me a message in the first place, that's all it takes. That's what everyone else does when they have an issue with anything I pointed them out to.
I accept your apology, we were both wrong in some ways. I'm not even trying to make you feel negatively about me either so don't get the wrong idea about my response. I'm a pretty nice person, I'm not used to arguing with anyone. I rarely do but when I do I tend to have a short fuse. I'm too nice to put up with it. I'm not about to have an argument with someone I'll probably never meet over a thread post. It's pointless and it looks dumb. I'd rather be making friends over here at XDA. Let us drop this discussion, and allow the thread get back on topic.
drumbeater79 said:
Is it compatible to use this mod on LG OPTIMUS G PRO?
Sent from my LG-E988 using Tapatalk 4
Click to expand...
Click to collapse
There's only one way to know. Make a nandroid backup first, then flash the tweaks. If you find anything wrong let me know. This isn't for every phone.
Tgyztrk said:
İ cant fiash it.My phone is huawei sonic with CM9 4.0.4
Click to expand...
Click to collapse
If you like I can help you with this later if you're still interested in trying the tweaks, I'm on my way home from work.
leolawliet said:
Dude.. instead of bashing, you could encourage me to improve the package and fix things and give me pointers, you know.. give some insight but not if you're gonna be so harsh that it looks like you're attacking me.. did you even try the tweaks..? Clearly not if you keep assuming stuff, and even YOU provided false info. Why are you even giving feedback if you haven't even tried it and never plan on using it? You just THINK you know what you're talking about.. but look what happened, you automatically assumed one of my scripts was total BS and it worked.. maybe not the way you wanted it to work but it does in fact work as stated. You insult me saying I need to learn how to code, and then I correct you, and then you correct yourself.. what was that you said about me needing to learn how to code? The same goes for you, learn your stuff too so it doesn't look like you're pretending to know what you're talking about, cuz seriously it looks that way now. I'm learning at my own pace trying to teach myself so I don't bug and annoy anyone for advice but I'm not gonna pretend I know everything. You made your own self look like a complete moron, that was your own doing, not mine.
Click to expand...
Click to collapse
Umm, okay I admitted to as much in the edits I made to my previous post...I shot my self in the foot regarding the cpuramcheck script...never seen a bin script not start with the standard opening line...never said it was your doing, I took and will continue to take full responsibility, which is why I did not delete my old silly comments, instead I stuck out the old text and added edits so my mistakes would be public record.
But in all fairness, all the other points I made were valid and are a reasonable basis for concluding this package is of suspect quality.
leolawliet said:
It's a tweak package seriously who starts crap over that? It's ridiculous. I can understand if you DID try the tweak package without making a backup and then you screwed up your device, at that point I'd feel bad I'd apologize and try to help make things right, but that's not even the case here. You didn't even flash anything so why are you even talking like you tried it and it killed your phone? -____-
Click to expand...
Click to collapse
I never talked like I tried it...reread my posts I explicitly stated at least twice that all I did was skim the zips contents. BTW - quite a bit a of crap is started over suspect tweak packages...read the PurePerformance and NetForks threads for examples...this kinda reminds me of PurePerformance, although I doubt it will cause the problems that pureperformance did/does.
leolawliet said:
I thought this was supposed to be a friendly community, I wouldn't even think of calling out anyone to speak to them the way you've spoken to me, just honestly speaking you came off as really rude to me and I felt some kind of way about it.. it's difficult to look at it any other way.
Click to expand...
Click to collapse
Agreed...I should have remained silent or have been more constructive and tactful in my criticisms.
leolawliet said:
Also.. how many other developers and users post up stuff on a daily basis that isn't even a final product? Tons of users have done it, and for their own reasons. So why the hell single me out like you did? Do you talk to everyone on XDA this way? Have some respect and consideration for others. Maybe you had a bad day and wanted to take it out on someone, but I don't know that so I can't assume and won't assume, but your behavior was definitely out of line and not normal. I'm not bashing you, nobody is. You made your own self look like a troll. You had no legit reason for behaving the way you did towards me in the first place, you do not know me from a hole in a wall. At least I'm not posting anything that breaks radio/battery indicator/GPS/WiFi/data/Bluetooth/etc. At least I posted something, I'm not someone who announces something BIG that gets everyone all hyped up only to never release it. If anyone feels adventurous, and knows what to do with these tweaks, they will check it out. If someone doesn't understand any of this, they're in the wrong place and I can't be blamed if they screw up their device because they SHOULD be aware of what they're doing. If users see some obvious mistakes in any of the things, I encourage them post their findings in the thread. You did that, BUT you were in fact very rude about it. Regardless if it points a person in the right direction you just can't speak to anyone like that, some people will take it some kind of way, like I did. Do you see where I'm coming from with this? We have this community so we could all support each other, help each other out somehow, not discourage others. I've seen noobs turn out to become great developers, I have mad respect for them for the effort they put into everything they did and for how far they've come along. You gotta start somewhere but if you sit around doing nothing, not interacting with others, how do you hope to learn anything? I may make mistakes along the way, as well as other users, but ultimately we learn from it. When you learn from a mistake you learn not to repeat it and how to avoid it.
Click to expand...
Click to collapse
In all honesty I have only seen a handful products as unpolished as this and most of those at least had half decent OPs. Furthermore, many of these products label themselves as WIP or alpha/beta, which makes such deficiencies somewhat understandable. The way in which you presented your product leads users to believe it is in a more or less finished state, meaning it should be free of silly errors.
I did not single you out...as previously stated, I call things as I see them (albeit my vision is far from perfect)...I have gone after the devs of PurePerformance and NetForks (although I was 100% correct in these cases)...admittedly I get more annoyed than I should and perhaps react poorly...why should I care if other users crack flash crap?
leolawliet said:
All I wanted to do was create a package with my preferred tweaks, to flash over any ROM update I install, without having to do it all one-by-one all over again, that was the whole point of this package. And the point of this thread was to share it and spot out anything wrong with it and to improve it. I welcome feedback and insight to improve the package, I encourage it because I want something that would benefit everyone. I just would appreciate it if the person came to me in a nice way. Honestly speaking, I can't remember the last time anyone spoke to me this way on XDA. I'm shocked, everyone else here is so nice and always willing to point me in the right direction, but half the time I don't wanna ask because I don't wanna be bothersome so I look for a way to figure things out on my own so I could avoid stuff like this.
Click to expand...
Click to collapse
Okay, how nice of you...what an altruist. But you have to admit the inclusion of a total empty file (that turbo script), a script that does nothing (dalvikcalc, which you clearly thought did something productive), and an inaccurate and uninformative OP (that states the build.prop tweak were included, when they are not and has no usage instructions) would lead any reasonable observer to conclude this is a half assed effort where the dev does not really know what they are doing.
leolawliet said:
Also.. "Credit goes out to these guys" http://forum.xda-developers.com/showpost.php?p=45273653&postcount=2
^ If you read the 2nd post you'll see I'm not taking any credit. You'll see I have told users to thank the credited developers on the 2nd post and it's been that way since I started this thread.. I never intended to take credit for the work of someone else, and really I haven't.. it's all there.
Click to expand...
Click to collapse
Umm, whatever...I never said anything about a lack of proper credits (in fact, if you were to ask my option of the matter, I would say you did an excellent job giving credits)...if you reread my second post you will find that I stated I looked at Pizza Box because you credited it. In addition, this is the exact reason why I called this 'unoriginal' in one of the struck out sections of my previous post; so I have no idea where this rant came from.
leolawliet said:
I should also mention I started that OP post on one of the threads for one of my ROMs and it had been copied over from there and changed a bit, I didn't thoroughly look through everything written the first time around, I didn't intentionally try to mislead anyone, and if anyone felt that way then I apologize and I corrected the post.
Click to expand...
Click to collapse
Although I know your sick of my opinions, this is why I previously stated you should have waited until you had the time to make a proper, decent OP.
Also previously stated, at least you are responsive and responsible, not to mention you are clearly trying to make a honest effort to learn (I've seen many of those posts you've made in the threads you used stuff from)...I noticed you corrected that error, but it should have never existed in the first place (<<my opinion - if you're gunna release it to the public there ought to be a minimum quality standard that includes an accurate and informative OP)
leolawliet said:
Another thing I wanted to say, I have been testing these tweaks for some time, along with the help of others so I didn't do this alone, I've had help along the way. I've even asked them to test them on the ROM updates I posted and on their other devices. No complaints. If I didn't feel confident that these tweaks would help others, if these tweaks haven't helped me in the past, I wouldn't have felt the need to share anything with anyone. The last thing I want right now is to cause someone's device to stop functioning, I would never want that to happen to anyone. The disclaimer states that I warned users to make a backup first before they try anything, that's common sense for anyone who has a custom recovery installed. If anything goes wrong, they have the option to restore their backup. I've been wanting to package these tweaks together for a while now, and just recently started learning how to put together flashable zips, which I had always wanted to learn how to do but never really got a chance to look into it till recently since I have access to PCs at work at any time now. The tweaks are working just as described for the devices I have tested them on (except LG G2x), and nothing conflicts, for me at least. I don't have a super phone, just a dual core device running PACrom JB 4.3, and that's not even so stable on it's own to be honest.
Click to expand...
Click to collapse
Just because none of them complained does not mean there are no issues. Clearly your testers missed the two valid script related problems I pointed out. Even a total noob should have noticed the blank turbo script.
leolawliet said:
As for the build.prop tweaks I wanted to include, I'm gonna explain. At first I did include them, I had a built-in script that WAS supposed to install them, I double checked everything from the script to the updater script, but for some odd reason I couldn't get it to work right and didn't wanna frustrate myself over it so I corrected it by instead posting the tweaks to copy and paste from the OP and in my opinion that is the better way to go with the build.prop tweaks because they don't always work on every device and you wouldn't have to install them all at once. This gives users a better chance to single out the tweaks that don't work for them, for the sake of avoiding bootloops & such. I tested them on my LG G2x a while back and didn't get the results I wanted (but that phone always had issues with whatever I tried doing with it). This won't work the same for every phone.
Click to expand...
Click to collapse
Makes sense and further explains the initially inaccurate OP...like I said - your honest and responsible, which imo puts you a cut above the creators of PureNonsense and NetForks.
GL with this and HF learning.
leolawliet said:
I just didn't like how you came off towards me, it could've been handled better. It's not even that I wanna ignore what you said about the 34dalvikcalc script, you angered me and it didn't seem like you were trying to be helpful, instead it just seemed like you were trying to pick on me. I took a look at 34dalvikcalc and I'm gonna exclude it from now on. Not looking for anything to replace it with, at this point I'm gonna slim down the installer and exclude some of the stuff. I was gonna remove the script but you really didn't have to push things that far.. the least you could've done was send me a message in the first place, that's all it takes. That's what everyone else does when they have an issue with anything I pointed them out to.
Click to expand...
Click to collapse
Although you're kinda beating a dead horse at this point, I will agree with you again - this is all true and correct.
leolawliet said:
I accept your apology, we were both wrong in some ways. I'm not even trying to make you feel negatively about me either so don't get the wrong idea about my response. I'm a pretty nice person, I'm not used to arguing with anyone. I rarely do but when I do I tend to have a short fuse. I'm too nice to put up with it. I'm not about to have an argument with someone I'll probably never meet over a thread post. It's pointless and it looks dumb. I'd rather be making friends over here at XDA. Let us drop this discussion, and allow the thread get back on topic.
Click to expand...
Click to collapse
Thank you, you are most gracious. Your responses have been most civil and I don't take your criticisms negatively as they are quite justified.
Sorry again.
=========
To get things back on topic (although it was never really totally off topic) and to be constructive for a change , if you want to include build.prop tweaks in your zip and if you have not already resolved this issue: (1) create a script named "buildprop_additions" in .sh format that follows this general guideline
Code:
#!/system/bin/sh
busybox echo "" >> /system/build.prop
busybox echo "### PenberEngine Tweaks Begin" >> /system/build.prop
busybox echo "YOURFIRSTTWEAK" >> /system/build.prop
busybox echo "YOURSECONDTWEAK" >> /system/build.prop
etc
etc
busybox echo "### PenberEngine Tweaks End" >> /system/build.prop
; (2) place this script in the base of your zip; (3) in the updater script somewhere after you mount /system add this
Code:
package_extract_file("buildprop_additions.sh", "/tmp/buildprop_additions.sh");
set_perm(0, 0, 0777, "/tmp/buildprop_additions.sh");
run_program("/tmp/buildprop_additions.sh");
I could very well be wrong as I have never actually done this first hand, but based on my limited knowledge it should work. Hope this helps.
I get where you're coming from now, I should've prepared the thread better before posting it. I got a bit eager and felt like sharing it and hopefully improving it along the way. Well, I corrected the title of the post and marked it as a project. I might actually rename PenberEngine to something else along the way, I don't think I'll stick with the name. It's just there because I use the tweaks on my roms.
I hadn't realized the turbo script was empty at first, it didn't copy over correctly. The one I had on my device wasn't empty. I guess I made a mistake with that in zipping it, my bad. Although it's better that I exclude the turbo script, I like Hyper Cola better. I'm including a couple of things I wanted to add before, and I removed enough stuff to slim it down to 2mb instead of 8mb.
This is what I saw on the build.prop script that stood out, the starting line was this:
Code:
#!/sbin/sh
while the line you gave me looked like this:
Code:
#!/system/bin/sh
I'll post back and let you know. Thanks for the pointer.
Edit: weird stuff happened, a 2nd build.prop was created
Related
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
hugerobot said:
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
Click to expand...
Click to collapse
Pre-complaining about others' complaints = lame.
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
rynosaur said:
Pre-complaining about others' complaints = lame.
Click to expand...
Click to collapse
Calling me lame when it appears that you didn't even read my post=the reason why I hardly ever post here. Ugh.
rynosaur said:
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
Click to expand...
Click to collapse
I think maybe you only read the part where I precomplained... since that seems to be the only item you commented on appropriately. But to answer your questions...
1. I clearly stated that I keep home app in memory because I like the performance gain. I have no idea what your asking me.
2. I don't use task killers/memory managers. Cyanogen and most other experts have argued against them enough to convince me that it's not the right solution.
3. huh?
4. I'm not complaining. This is not geared toward any particular dev. Slow phone is a known inconvenience with all eclair builds on G1. Didn't think I needed to go asking if anyone else was experiencing it. I have flashed so many eclair roms to my phone, and with all of them the phone app has behaved more or less the same way.
BTW- I also clearly stated that I have a G1 running the latest superbad.
Here's my question again... Would keeping the phone app in memory improve it's performance in the same way that keeping the home app in memory does? If so is there value in including this option in spare parts?
blackvyper said:
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
Click to expand...
Click to collapse
Thank you for your suggestion... but I'm leery about using task managers/killers based on some of the discussions I've read from some of the expert devs (cyanogen, etc). I suppose if it works, the result is the same. I am surprised no one has asked this question before. I searched quite a bit and couldn't find a mention- on here, and a straight up Google search.
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
hugerobot said:
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
Yes, I'm sorry for my part -- I started sarcastic and then thing flew out of hand. My point about priority and memory allocation is this: dialer is, by its nature, held in memory-it doesn't have to be loaded after boot, it just has to be recalled. I'm sure you've noticed that no matter what you're doing on the phone, it all takes a backseat to an incoming call, and usually very quickly, <5 seconds. The phone is still built to take calls above any thing else.
So my answer to your question is this: bump up the priority of phone.apk. It will respond to the green button more quickly. In my ROM, Phone has an OOM of -12, while HTC Sense is 0 -- that's Spare Parts working to make dialer higher on the food chain. Think about it. Don't wait for someone to rewrite a ROM, just use AutoKiller to bump it up the foodchain and push other background processes further to the back. If you use compcache, remember dialer.apk may end up there, where it takes more till (being compressed) than normal to recall. Also Phone Prioritizer (which I can't find on the market anymore due to my build) is nice fore renicing more frequently than the OS does by default. All these things could help. Reducing other concurrent background tasks will help as well.
hugerobot said:
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
I know what you mean. Im not sure what happend to XDA lately. Back when it was ALL windows mobile forums (phones no android), everyone was very helpfull ect... When android phones started coming out that brought the whole world to XDA and now we have people on here who have nothing else to do but bash people instead of helping them... Anyways... LOL
As for the dialer / home in memory situation. I found that enabling swap / compcache makes a huge difference.
I been on every 2.1 rom on G1 and ALL of them had problems with loading apps very slow and opening the home screen real real slow even with "Home in Memory" checked in spared parts.
And then I flashed Super E yesterday wich is a 2.1 rom that has swap / compcache settings inside spare parts. I partitoned my sdcard with 254mb swap and enabled Swap and Compcache of 32mb. I also went to the market and downloaded "Swapper 2" which will also enable swap and tell you your swap statistics. After doing that everything and I mean everything opens rather instantly.
My sdcard is class 2 so I never been a fan of using swap but using swap with compcache makes a huge performance difference for me on my G1 on the Super E rom. I think theres an update to Super E that I havnt flashed yet but with the perfomance so far I dont see a need to update but I might update just for the hell of it.
Long story short. Enable swap partition on your SD card / Install Super E / Install Google Apps / Enable Aps 2 SD / Spare Part Enable compcache / swap 32mb / Enable Launcher in memory / Download Swapper 2 from market and set to on.
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
hugerobot said:
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
Click to expand...
Click to collapse
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. The rest of the dialing, such as when you use the green button, is done via contacts.apk. The slow load times are really a part of the way android kills processes. If you are running a replacement launcher like LauncherPro or GDE, etc, what you are seeing is that acore needs to reload and takes a long time. The stock launcher is much more forgiving. I have found that by installing the "DialerOne" dialer from the market, that these alternate launchers do not cause the acore reload, and the dialer is very fast to load.
bkmo said:
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. .
Click to expand...
Click to collapse
I never said phone.apk but I did transpose dialer and phone as interchangeable names for the same process. My fault, but what runs in the background to let let you make phone calls is name com.android.phone.
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
The other gentleman's response that more cache is the answer may be a great answer for cm5.0.7 ROMs--if you can get a good cache going, I never could--but it's almost a non-question in Sense ROMs since everyone will run one anyway, whether it be backingswap or linux-swap.
Now that's we've cleared this question up completely
I couldn't bother reading all of the back and forth stuff, I am using Xtreme-1.2.2-black it is 2.1 CM5 base.
I have been using shadowch31 Renice Script that gives the "phone" app a higher priority and it starts up a lot faster.
Also using and ogg file instead of an mp3 has been know to help.
I haven't seen the script in any of the forms so I am not sure if shadowch31 wants it released so pm me or him if you want to give it a try
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
htcclay said:
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
Click to expand...
Click to collapse
From the man himself! So did my suggestion help? Did I actually contribute by posing the question?
For the record, I did say that this was the case with all 2.1 roms I've tried, not a problem with superbad.
rynosaur said:
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
Click to expand...
Click to collapse
You are right, there is no "contacts" process. And I have seen this contact.apk loading issue since "donut", so it is not an "eclair" only issue. What I do see is that when you are running an alternate home app, that when you press the green button, or the phone icon, what you get is an "acore has died" in adb logcat. At this point acore reloads all the programs under it including launcher, before it runs the contacts app to get you the dialer. I have seen up to 20 seconds before the dialer comes up. Renicing phone.apk does not help this issue in my testing. I have just tried dialerone from the market, and it does not suffer the slow load times. I do not know what brings up the dialer when you press the button, all I know is that the dialer is included in contacts.apk, and what I see in a logcat whn I press the button or icon. Dialerone is working for me, and I can use the latest ADW launcher without a delay to the dialer. Thanks for setting me straight....seriously.
mejorguille said:
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
Click to expand...
Click to collapse
AFIK phone.apk is not the dialer, and is already locked and does not get killed. Just think about it, if it was able to be killed, what would be running to handle an incoming call?
bkmo said:
Thanks for setting me straight....seriously.
Click to expand...
Click to collapse
Hey, everybody's got to be wrong at least once a day, me . . . . more 10 or 20 times a day. I don't know what it is with gapps and acore crashing regularly in cm eclair builds, but my impressions from t1-stable were: Hero-like instability, without the Hero bells and whistles. So I switched to Sense 2.1 Result, apps do die when I look at the phone funny (or press Dial -- fring dies when I press dial, or the mysterious com.smithmicro.DM -- probably a keylogger), but the bells and whistles are nice, so there's tangible payoff for dealing with a stretch of a mod.
Hope HTCClay works a miracle and fixes your phone. Maybe he can share the secret with other devs Peace
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
there must be some mod out there to shut up this silly stupids like this guy...why this people ever answer in a post?!!!!
Announcement: I highly suggest you flash void. - http://forum.xda-developers.com/showthread.php?t=887281
Well, here's one more ROM for you guys: Megatron.
Why the name? Seemed only logical considering the name of our device, Optimus One.
It's basically a ROM tweaked for performance while retaining a decent battery usage. Also, with this ROM, you won't need to flash any other tweaks.
I daresay it's so far the speediest ROM for LG P500.
Features:
v2:
to be updated
v1:
root + superuser + busybox
APKs deodexed + zipaligned + png-optimized
apps2sd + dalvik2sd [1]
performance tweaks: (JIT, hardware acceleration, etc) [2]
includes drellisdee's custom kernel [3]
kernel repacked to set onboot the scheduler to interactive (tweak)
applications removed: App Advisor, Layar, Twitter, Facebook, LG Home, Think Office, Update notifications and Twitter [4]
applications changed: Genie widget (now transparent), Music (imported from CM)
applications added: Titanium backup, File Manager (imported from CM) and the awesome LauncherPro [5]
ringtones, notification and alarm sounds added (including iPhone ones)
changed boot animation to a more cute one
auto-overclock to 728Mhz and possibility to easily revert (minitron tweak) [6]
[1] Rather than move_cache_sd program used in another ROMs, I use another method for moving dalvik-cache to SDcard since sometimes using the aforementioned program won't work successfully. It's a known issue of Dsixda's kitchen.
[2] Heapsize: 32MB; without a doubt the best value.
[3] Check the original thread here and if you can, buy him some beer.
[4] I left CarHome due to popular demand.
[5] Titanium backup will allow you to uninstall any system application and to backup the ones you install. LauncherPro is in my opinion, way better (performance-wise) than ADW.
[6] As far as I've read, 728Mhz is stable for everyone til now.
Click to expand...
Click to collapse
Requirements:
In order to flash this ROM, you'll need on your device:
Having read the feature list and notes above
Root (check thread)
Drellisdee's custom recovery (check thread)
Class 4 SDcard or higher (bench it with h2testw)
Megatron (download it here)
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Important notes:
* There were some reports on other ROMs that battery usage was very high, especially on standby. While this ROM should perform better, it won't still have as good battery usage as stock ROM mainly due to the scaling governor being set to interactive. Also because of this reason, benchmarks could be slightly lower. I however promise that the overall experience and snappiness will be quite satisfying.
* I've made an easy and friendly way to decrease the clock back to stock 600Mhz. Instead of needing to use SetCPU, you just need to create a folder in your SDcard called "minitron" (without the ""), then reboot your phone. Your clock will be now back to 600Mhz. If you wish to revert it to the default 728Mhz, just delete the folder and reboot your phone again. Since the voltage is the same for both clocks, battery consumption should be around the same too. If for some odd reason, you get a boot loop, it means your phone doesn't support (*gasp*) a 728Mhz clock. To avoid a boot loop, go back to the custom recovery, toggle sdcard-pc connection and create the "minitron" (without the "") folder. Reboot, should be fine.
* Remember, you won't need to flash anything else. Everything's here.
As you already know, I cannot be held responsible for any damage you may cause to your phone by following these instructions. Every step taken is of your entire responsability.
Testimonials:
* "I noticed that the phone was another! much better performance! I did all the tests and there are no problems!"
* "This Rom is just... Amazing!!!"
* "Feedback: working nicely untill now. So far so good - the best ROM yet"
* "Great work , phone is workin faster and booting 2times better now great work."
* "So far I can say it is arguably fast. Phone is super snappy and responsive."
Time to see for yourself.
Just remember, it's still an experimental ROM.
-reserved-
Thanks for the work, though I think I'll be passing for right now.
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
http://forum.xda-developers.com/showthread.php?t=866774
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Other than the kernel issues, seems like it will work well for those who want those features.
Just my 2 cents, seems like a decent enough ROM, like to see how it works for people.
eigokyoukan said:
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
Click to expand...
Click to collapse
Been using it for days and no complaint.
Like I said, it's a performance-oriented ROM. Default OC makes sense to me.
If people are scared of long-term effects, they should Minitron-it then.
Anyway, I'll update the thread's title.
And interactive is way better than anything to be honest. It will even be the next default scheduler in CyanogenMOD.
eigokyoukan said:
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Click to expand...
Click to collapse
Didn't read that and it's the first request of the kind I've seen.
For user's comfort, custom kernels often tag along with custom ROMs. Protocol has always been to credit the author, point to original thread and urge for a donation. At least to what I'm used to. However, if he insists on this and contacts me directly stating he really doesn't want his kernel included on a ROM, I will abide and remove the whole ROM since it loses its raison d'être.
Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work.
It is not uncommon to not want your work bundled, but at least you gave credit. I see too often credit not even given for others discoveries and hard work.
I still say default OC is a bad idea until we understand the full long term effects of having this hardware 700+MHz, but then again, this will start getting it tested.
Have installed the ROM. Works Great, No problems so far. Like the LP. But I would like to have an option to install themes and so one. That would be fantastic.
Thanks!
EDIT: Solved
There is a reason I set max freq on boot to 600mhz in kernel as its to prevent users from getting stuck in a boot loop at a speed thats too great for their device. If you kernel panic it will reboot back to stock max as as had it set up. I did also have in my post not to repack kernel in rom and posted source so rom makers could build their own variant to use. I'm not going to ask for you to pull rom however as I see no reason for that. I just made it so it would reach as broad an audience as possible even those that don't want to overclock as its optional as I had it setup. Also, by using koush's any kernel its compatible with virtually any rom.
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.
hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!
eigokyoukan said:
Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work..
Click to expand...
Click to collapse
Yea, no worries. Sorry if I seemed harsh in my reply, not my intention.
I do have a different opinion though, slightly more optimist.
Since the voltage is the same for both clocks and the cpu only peaks if called, I don't think there will be much overheating. Also, I've never heard of any MSM7227 that toasted itself or his hardware neighbours.
That being said, you may think it's a leap of faith but I find it perfectly safe to use a 728Mhz clock as default. I may be wrong but let's hope not.
drellisdee said:
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.
Click to expand...
Click to collapse
I understand that.
So far, the least stable clock that someone had on your awesome kernel was 748. Even so, as a safety measure, I've set it @ ~728. If for some reason there's someone out there that gets a boot loop, he just have to go to the custom recovery, toggle the sdcard-pc and create "minitron" folder. Done, 600Mhz!
Also, thanks for officially letting me use your kernel on this ROM.
fr4nkr0c said:
hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!
Click to expand...
Click to collapse
I'm glad you found it speedy!
Regarding your reboot problem that happened before, even on other ROMs, sounds to me it is a phone matter. Shouldn't you allege malfunctioning to your carrier and get the phone switched?
* Quadrant (w/ default options) attached to main post
* Forgot to add to features a different boot animation
i say thumbs up just for the name , not to mention the rom
I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.
Optimus T = O1 for T-mobile
gemarc said:
Optimus T = O1 for T-mobile
Click to expand...
Click to collapse
Yes, I know, but that wasn't my question. I understand that the processor in the O1 is MSM7627 and the Optimus T has a MSM7227. Since the kernel was made for the O1 would I need to find a different compatible kernel for this rom on the Optimus T or would this OC'd kernel work? I'm willing to test it, but I just wanted an opinion before I started.
Can you add an option on this ROM ? I would really like the softkeys to be always on.
Congratulations for your work !
Sent from my LG-P500 using XDA App
This Rom is just... Amazing!!!
Congrats
l30r0 said:
I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.
Click to expand...
Click to collapse
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right
Nice job
xilw3r said:
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right
Click to expand...
Click to collapse
thanks for the tip.
do games run better with this rom?
Build.props, setctl, ro.ril, vacuum, zip align, loopy smooth, group your oom, don't use his script use mine.
Just wondering if some effort could be put into a central repository at this point. Or get them into cyanogenmod if they are really proven to benefit all or a majority of phones.
For instance- It's it just me or does zip aligning and sqlite optimizing on every boot seem onerous?
I'd think these types of scripts need to be weighed for efficiency.
I'd rather do something once or once a month rather than be unnecessarily slow for 2 minutes on every startup.
Isn't zip aligning done by most -if not all- ROM developers? I could see if it would need triggered as new apps are installed maybe bit I don't know if newly installed apps already get zip aligned when the phone is live. ...Or if zip aligning doesn't stick after every reboot.
Have tweak verification to skip over ones already in the ROM. A big thing with any OS is boot times and not doing something twice if it isn't necessary.
If not a cyanogenmod commit have a market app rather than messing with terminal. It's playing with our OCD
Just throwing it out there.
I step away from the mic to breathe through my nose
Nice point brother. %95 of apps are already zipaligned out of box.
Sent from my GT-I9000 using Tapatalk 2 Beta-6
+1
Sent from my Inspire 4G using xda premium
i think, it is because each phone has different memory and kernel version, so each people just tweak to get better to his phone. zipalign is not worth i think, because rom vendor already optimize it, i think png size reduction is worth..
just my 2 cents
If there is only 1 kind of tweak, it would be no fun. all of this different tweaks has different in the configuration. It may be small, it may be big differences, but it gives us way to try it and see which would be better for our device.
I am with the OP. Most of the "tweaks" means nothing. I am zialigning my rom, while building it. And do not even mention it in the posts, because it's obvious. And every apk on Market and stock rom is zipaligned, until it's recompiled.
Many devs include some "ui rendered with gpu" tweaks in gingerbread, when it's not possible. First android that renders ui with gpu is ICS. Except roms with 3D rendering, like Motorola Blur 2.
Never found any benefit in performance when optimizing databases. Only thing, that increases performance for me, is the library without "sync".
Etc., etc.
But some tweaks are useful. Mostly those, that are already used in CM roms. ;-)
Hey everyone,
Version 2.0.0 released!
This version introduces performance tuning, power management control, and an optional MMC I/O queue extension/timing change.
For those of you who have seen reboots / black screens that seem to be caused by Seeder, I suspect it may be due to the power management implemented in previous versions. Disabling power management (by unchecking "Suspend RNG service while screen off") may help. In my testing, battery impact was negligible (less than 2% per 24h).
The performance profiles are Light, Moderate, and Aggressive, and they control how frequently rngd wakes. The default configuration (Light) is unchanged from previous versions. Moderate and Aggressive may impact battery life (slightly), but may also help on devices where the entropy pool is drained quickly and often.
Last but not least, the "Extend I/O queue" option increases the nr_requests on MMC devices to 1024, and increases the dirty page expiry time, allowing more outstanding writes to accumulate. This may allow the I/O scheduler to make better decisions and combine more writes; some users have reported an improvement under heavy I/O.
Feedback appreciated!
---
On some (older) versions of Android, the JVM (and other components) often read random data from the blocking /dev/random device. On newer builds, this problem has been solved, yet depletion of the input entropy pool still seems to slow devices.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? Significant lag reduction (for some people)! :good:
Note - if you want to try it, you must be running a rooted device, and you only need to install one of the APKs (latest version is best). Then, just open it, and turn it on. The other files (patches / .zips) are intended for recompiling, packaging, and init.d integration. If you uninstall the app, either turn off rngd first (open, and click the on/off button), or reboot afterwards; the UI does not presently kill the daemon on uninstallation.
For more information on using the .zip flashing method, see Ryuinferno's post here:
http://forum.xda-developers.com/showpost.php?p=36479461&postcount=1924
FAQ
Q: Do I need the .apk or the .zip?
A: The easiest method is simply installing the latest .apk, attached below. You do not need to use the patch or the .zip file.
Q: What is the patch for?
A: The patch file contains the source differences needed to recompile the Seeder version of the rngd binary. You only need it if you want to recompile rngd yourself.
Q: What is the .zip file for?
A: The .zip file contains the latest rngd binary. It is intended for ROM builders or those who want to build their own CWMR packages.
Q: Seeder keeps shutting down! Does this mean I have to restart it?
A: The Seeder UI is only used to configure and start/stop the RNG service, which runs in the background. The RNG service is not visible from Android, since it is a native Linux process. You can terminate the UI at any time, and the service will continue running.
Q: Does seeder cause excessive battery drain?
A: Seeder 1.2.7 introduced an RNG service power-saving mode. The process automatically suspends whenever the screen is off. The code is actually in the rngd native binary, so suspend/resume events happen independently of the UI; you can see it in action by attaching to the running process with strace. This means that battery drain while the screen is off is highly unlikely.
While the screen is on, the RNG service simply polls a file descriptor every second, and, when needed, injects a small amount of random data into /dev/random (and calls an ioctl). It's unlikely that this would present enough load to trigger a CPU governor state change at 10mhz (let alone 200mhz), so it shouldn't impact battery life. Having said that, I have received sporadic reports that it does reduce battery life on some devices. They may be coincidental (other software installed at the same time), or due to extra device use while testing. Or, they may be real. If you think your battery drain has increased, shoot me a PM!
Q: How can I see the RNG service Linux process?
A: In a terminal, type: ps | grep rngd
Q: How do I uninstall the .apk?
A: Launch Seeder, and stop the RNG service. Then, uninstall the app as you normally would. Alternatively, uninstall the app, and reboot.
Q: Is seeding /dev/random with /dev/urandom safe?
A: Seeding /dev/random with PRNG-derived data does reduce the quality of its random data. However, it's worth noting that nearly all major OSes except Linux do this. Linux is one of the very few to offer a blocking RNG device. And, at least as of ICS, Dalvik doesn't even read /dev/random, so there is little difference anyway.
Updates
There has been a lot of controversy about Seeder/rngd. In newer versions of Dalvik, nothing touches /dev/random, and yet many users (including myself) still notice a lag reduction. There are theories ranging from kernel lock contention to UI polling load when crediting the entropy pool to simply kicking the governor. And many who believe it's all placebo. I'm trying my best to figure out what exactly is happening, and others are as well.
Someone asked how I arrived at the conclusion I did when I started the thread back in November, and I posted this; I think it might be better served here:
A while back one of the webapps I was hosting on Tomcat (server-side) was experiencing some inexplicable latency and while stracing java I saw it frequently hanging on read()'s from /dev/random. I checked the available entropy, and it was constantly under 250 or so. It was a VM, no HWRNG, so I decided to use rngd to push urandom->random.
Dropped session creation times under load from 5-10 seconds to less than a second.
It's worth noting that Linux is one of very few OSes that have a blocking RNG device. Free/OpenBSD, Windows, etc.. essentially only provide urandom. It's generally considered secure, even for long-term crypto keys, so long as the initial seed is big (and random) enough.
Checked on my device, and saw a few processes grabbing /dev/random. /proc/sys/kernel/random/entropy_avail reporting depleted input pool. Figured it was worth a shot, so I rebuilt rngd for arm (with a few patches, linked on first page), and tried it out. It made a significant difference. Posted it up on this thread, and had a lot of positive feedback. Wanted to get into Android development, so figured.. why not wrap a little UI around it. More positive feedback, so I threw it on the market as well.
I had no idea it would take off like this and was shocked when I saw it Thursday morning. I'm in the awkward position now of explaining why it seems to work for some people, and not for others, especially given the fact Dalvik doesn't have references to /dev/random as of ICS. Theories abound, but it looks like it might be an issue of polling the UI for input events when the entropy pool drops (which never happens so long as rngd is running).
I'm doing this as a hobby. I'm a *nix admin by trade, and can only spend time working on this stuff on evenings and weekends, and the last few weeks have been kinda nuts.
I want to stress to everyone that:
a) It doesn't work the way I thought it did on later Android builds, but it does reduce latency for me and many others even on these builds,
b) I'm offering (and always will offer) Seeder for free to everyone on XDA,
c) Like I say in the market description, if anyone has purchased it and it isn't working, PLEASE email me for a refund (and let me know what device you're on if you're willing).
I was one of the first to root the Captivate glide (my first Android phone), and submitted the A2DP bitpool patch; I was active in the n900 community. I hope everyone understands that I'm doing my best here!
I hope the technique proves useful to people, and if there is in fact contention at the kernel level, I hope it's solved so we all benefit.
Version 2.0.0 attached. No changes.
Version 2.0.0b1 attached. New performance profile selector, I/O queue extender, and power saving control. Improved root checking.
Version 1.4.0 attached. Major refactoring. Service control now fully asynchronous.
Version 1.3.1 attached. No changes from 1.3.1-beta.
Version 1.3.1-beta released. New root check method during ANR-sensitive code.
Version 1.3.0 attached. Proper IntentServices for process control, and notification on upgrade / loss of root / autostart failure.
Version 1.2.9 attached. Yet another update to the upgrade/autostart code.
Version 1.2.8 attached. Asynchronous startup of rngd during boot; this should solve the remaining autostart problems some users have reported.
Version 1.2.7 released. This version introduces a much more efficient suspend-on-sleep mode for rngd.
Version 1.2.6 released. This version reverts the suspend-on-sleep rngd change which may have been contributing to new latency. I'm sorting out a better way of implementing it.
Version 1.2.5 released. This version should fix the autostart failure some users have seen.
Version 1.2.4 released. This version implements a progress bar displaying your currently available entropy, as well as automatic rngd restart on upgrade.
Version 1.2 released. This version implements rngd suspend-on-sleep, and contains minor user interface updates, more robust process and superuser checks, and a new icon (thanks Nathanel!)
Version 1.1 released. This version uses the release signature, so you will need to uninstall the old XDA version first!
This version fixes the issue some users were seeing on later Jellybean ROMs, where the UI would misreport the RNG service status.
Caveats
There is a (theoretical) security risk, in that seeding /dev/random with /dev/urandom decreases the quality of the random data. In practice, the odds of this being cryptographically exploited are far lower than the odds of someone attacking the OS itself (a much simpler challenge). It's worth noting that as of ICS, Dalvik uses /dev/urandom exclusively, anyway, and that Linux is one of very few modern operating systems that even offer a blocking RNG device to begin with.
Support for rngd suspend-on-sleep was added to Seeder 1.2. It should no longer impact battery life while the device is asleep.
There has been a large amount of speculation on why/if this actually improves performance on ICS+ devices. I'm continuing to investigate and will post updates to this thread.
If you try it, let me know how it goes.
ROM builders - feel free to integrate this into your ROMs (either the .apk / application, or just the rngd binary called from init.d)!
If anyone's interested, I've launched a paid app on the Play store for non-xda users. As I add features I'll post the new versions here as a thanks to you guys (and xda community at large for being such a great resource). But if anyone's interested in the market's auto-update feature, just thought I'd mention it.
Cheers! :highfive:
This seems absolutely amazing!I think I'll try it out on the weekend, cheers!
Will this work for cwmr 6
Sent from my SGH-I927 using xda app-developers app
Hi,
I would try this, cause I experienced these lags, and they're really annoying, but I'd really need a simple instruction for what to do. You wrote how you managed to discover what to do and stuff, but I'm lost between the lines. Since I'm kind of a newbie, I'm kindly asking you to write some kind of instruction manual step by step, and forgive my ignorance
Laugher19 said:
Will this work for cwmr 6
Click to expand...
Click to collapse
Not yet. If a few people try it and report positive results, I'll make a flashable image. Stay tuned.
soadzoor said:
Hi,
I would try this, cause I experienced these lags, and they're really annoying, but I'd really need a simple instruction for what to do. You wrote how you managed to discover what to do and stuff, but I'm lost between the lines. Since I'm kind of a newbie, I'm kindly asking you to write some kind of instruction manual step by step, and forgive my ignorance
Click to expand...
Click to collapse
I updated the first post with instructions. Please be careful, though! Let me know if you need more detail.
lambgx02 said:
I updated the first post with instructions. Please be careful, though! Let me know if you need more detail.
Click to expand...
Click to collapse
I got troubles. Using Terminal Emulator I got an error message when I type the 3rd line ("cp /mnt/sdcard/rngd /system/xbin"), it says: "sh: cp: not found"
soadzoor said:
I got troubles. Using Terminal Emulator I got an error message when I type the 3rd line ("cp /mnt/sdcard/rngd /system/xbin"), it says: "sh: cp: not found"
Click to expand...
Click to collapse
Where did you transfer rngd to on your phone? Have to make sure the source path matches.
lambgx02 said:
Where did you transfer rngd to on your phone? Have to make sure the source path matches.
Click to expand...
Click to collapse
It does match, that's why I'm confused.. :\ which terminal do you use?
Will test this later, for sure! If all goes well, may I request permissions to include this with the MIUI build I will be learning to make and attempting to produce?
edit: My phone wasnt particularly laggy before except when playing games, but there is a noticeable difference after executing this binary. Noticed a few small hangs but unsure if it is related to this binary.
I've tested it ... integrated it into my rom and installed ... there was no lag even right after it first boot ... its incredibly smooth ... though I too noticed small hangs ... though I attributed this to the device getting ahead of itself ....
Sent from my SGH-I927 using xda premium
Yeah it kind of seems like its fine after settling a bit. Can't wait to see it in 0.7 thegreatergood.
Sent from my SGH-I927 using xda premium
Ok, everyone. I built a very simple Android app that bundles the rngd binary and starts/stops it. Details in first post.
lambgx02 said:
Ok, everyone. I built a very simple Android app that bundles the rngd binary and starts/stops it. Details in first post.
Click to expand...
Click to collapse
wow ... that was quick ... maybe i should look into a custom tweaking app for my rom ...
Zero Computing said:
Will test this later, for sure! If all goes well, may I request permissions to include this with the MIUI build I will be learning to make and attempting to produce?
Click to expand...
Click to collapse
Of course you can!
edit: My phone wasnt particularly laggy before except when playing games, but there is a noticeable difference after executing this binary. Noticed a few small hangs but unsure if it is related to this binary.
Click to expand...
Click to collapse
Yeah, sometimes we really do hit filesystem I/O limits, but at least this should help once everything has been cached.
Ok, autostart on boot is working.
Seems to be a little faster...game still lagging though guess I will give it time
Sent from my SGH-I927 using xda app-developers app
Trying it out. Definitely noticing faster returns to the home screen. I'm using the ICS "only one" build for galaxy note sgh-i717
.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
OMG! I downloaded via qr code. and OMG! My phone runs sooo much smoother than before!!
This is one of the best mod for glide ever. Things are much smoother and faster to access. ES file explorer, dialer and contact list comes up so fast.
Thanks for this, really appreciate the mod. I'm keeeping it .
Sent from my SGH-I927
Would this work on other devices?
I'm interested in some kind of Magisk modules especially tweaks such as Raiden Tweaks. I could install it when I use the device for the first time. Then I could not install it although I install the EU Rom many many times as the clean flash. Each time the module application does not seen when I try to install it.
... and people wonder why their phone bricks, or why they have issues. For god sakes, man!
So. how exactly is this Raiden Tweaks suppose to improve user experience? Can you give me some examples?
https://github.com/raidenkkj/Raiden-Tweaks
...just some bull tweaking script, not worth anyone's time.
Tomo123 said:
https://github.com/raidenkkj/Raiden-Tweaks
...just some bull tweaking script, not worth anyone's time.
Click to expand...
Click to collapse
Yea, I found github page as well, but there is no info whatsoever about what this module does, but you are probably right, I doubt this will improve anything.
After downloading it, I checked the .sh files... just some script kiddy tweaks found all over the net. Tweaks for online games like PubG, Genshin and like, some system mods, prop edits...
Personally, I would avoid it.