Lets talk a bit about Carrier support and roms. As far as I know, this is one of the first times multicarrier has been done on such a scale. This is probably due to Samsung really stepping up and having the same hardware on different networks :good: But it has created a few problems/hackjob solutions that I cringe every time I come upon them. Most devs are in the know now, not to single anyone out at all but many VZW roms have been fixed or are being fixed, The Peoples Rom has full Sprint -> VZW support, Hero seems to have fixed some port issues last release, scrosler has been pointing users in the right direction, and of course Synergy is patched also. There are probably more patched as well and I do not want to leave anyone out, I just am not in the know about the whole suite of Roms. This rant is more so when we see silly things posted we can squash them before they keep spreading.
I am posted this in the dev only section because I do not want to get 1000 questions "what about this on this rom" and am just looking for this to be an open discussion & knowledgebase about not pissing off the powers that be. This also applies to both note2 and gs3 as both are going multicarrier so it seemed perfect. I will also be posting no links here to where any incorrect information started from. This is not a finger pointing contest its just meant to not hoard information and hopefully help the community grow as a whole.
If you are not a dev, just sit back and take it in. If you are a user looking for a way to test out roms, please check out the tool I posted in development - http://forum.xda-developers.com/showthread.php?t=2234003
If you are a dev, feel free to chime in and throw other ideas in as well. There are some ports we are still struggling on, and some carriers that are still neglected from this list. More info that is out there the better :good:
Here are some details on the back end of how things work, and what we need to be careful of when moving a rom between networks
1- CSCs - Consumer Software Customization - Sets Sales Code & Other Values
This article has some more information about cscs - http://droidviews.com/2012/how-to-change-csc-in-samsung-galaxy-phones/
In a nutshell, when a device comes from the factory it is totally blank with just a stock image flashed. At the point device is first turned on SetupWizard kicks to life and the software goes through activation and CSC Verify steps. What CSC Verify does is checks System files to make sure they are not modified and applies Carrier specific settings. This is where your bookmarks, preset dialer numbers, phone default MCCs, programming info like phone information, APNs, and PRLs get set in the rom. Unless you heavily modify the ROM you will be failing a CSC verify check. This appears to be reported in the form of a RIL request if the carrier wants it with a list of files in system different than what the stock image should have.
To check CSCs (only run after a factory reset)
Code:
am start com.sec.android.app.servicemodeapp/.Sec_Ril_Dump
and check CSC compare.
Regardless of a pass or fail there, CSCs have other functions to apply different properties to the rom. Sales Code and Country Code are two big parts of CSCs. These are how networks features are applied (Sprint gets its Connection Optimizer, PRL menus, etc), how APNs get matched to MCCs to validate use(ATT matches its APNs this way), among other things such as Data Roaming. Sales code is actually written down to the EFS under certain conditions and I believe where the IMEI loss is coming from. It seems to be a case where if the Sales Code changes and verify detects some change to run a nvrecovery. I still have not been able to reproduce it 100%, but the condition should able to be found with alittle bit of work close to those lines.
With this being said, the important things to make sure of for CSCs and network compatibility are below. Seriously dont just go deleting these XMLs to get something like lockscreen bubbles. Do the mod the right way or dont do it at all. Do you really want LOL's or some bogus values written to EFS or reported in a RIL query? (sorry for overly dramatic rant, this one just pisses me off. Look down to point2 for even more on why)
-/system/csc/customer.xml
-/system/csc/sales_code.dat
-/Build.prop values. If these do not exist they will fall back to sales_code.dat/customer.xml. Below is a sprint example
Code:
ro.csc.sales_code=SPR
ril.sales_code=SPR
ro.csc.countryiso_code=US
1a - Other Important build.prop values
This is half CSC related, half Network Specific app related, so well make it 1a. Things like model number, ro.build.PDA, chipset and build.product determine what features are enabled on the device and other aspects of registration. Below are important prop values us at Synergy have determined to have set right, the below is a sprint example but regardless of what network you go to, you should have always have these same props just change with values from the build.prop of your device/network combo.
Code:
ro.build.version.incremental=L710VPBLJ7
ro.product.model=SPH-L710
ro.product.brand=samsung
ro.product.name=d2spr
ro.product.device=d2spr
ro.product.board=MSM8960
ro.chipname=MSM8960
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d2spr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=d2spr-user 4.1.1 JRO03L L710VPBLJ7 release-keys
ro.build.fingerprint=samsung/d2spr/d2spr:4.1.1/JRO03L/L710VPBLJ7:user/release-keys
ro.build.characteristics=sprint
ro.com.google.clientidbase.yt=android-sprint-us
ro.com.google.clientidbase.ms=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
# Samsung Specific Properties
ro.build.PDA=L710VPBLJ7
ro.build.hidden_ver=L710VPBLJ7
ro.build.changelist=329968
# end build properties
# 8960 RIL Basic
ro.vendor.extension_library=/system/lib/libqc-opt.so
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22
# Default ECCList (Except USCC)
ro.ril.ecclist=112,911,#911,*911
# Default Operator (SPR)
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
# Do not show no sim notification
ro.config.donot_nosim=true
1b- What Apps Use these Values - AKA Why you should care
This section gives a brief idea of what the impact is of say deleting customer.xml or changing sales code props to the wrong network. Some may be a simple display of the value, others may totally changing the way network functions work, but theres ~50 apks in the list, alot to be messing with and not a good idea.
*NOTE* APKS like CSC/keystring/preloadinstaller/secsettings.apk control other system and network functionality outside of the APK.
*NOTE2* There are probably other places these are checked as well, this is just a quick and dirty list to get the point across these are important
Customer.xml: (means it uses file directly. Salescode list might overlap with this, but they are slightly different checks)
/system/app/CSC.apk
/system/app/ClockPackage.apk
/system/app/SamsungCamera.apk
/system/app/SamsungIME.apk
/system/app/SecBrowser_VZW.apk
/system/app/SecContacts.apk
/system/app/SecEmail.apk
/system/app/SecMms.apk
/system/app/SecPhone.apk
/system/app/SecWallpaperChooser.apk
/system/app/VoiceRecorder.apk
/system/framework/services.jar
Sales Code - (from customer.xml, props, or sales_code.dat, depends on what takes priority)
Framework:
/system/framework/android.policy.jar
/system/framework/framework2.jar
/system/framework/services.jar
ATT:
/system/app/OmaCP.apk
Sprint:
/system/app/Chameleon.apk
/system/app/PCWClientS.apk
Common:
/system/app/AccuweatherDaemon.apk
/system/app/AccuweatherWidget_Main.apk
/system/app/AllSharePlay.apk
/system/app/CSC.apk
/system/app/ClockPackage.apk
/system/app/CloudAgent.apk
/system/app/FactoryTest.apk
/system/app/HiddenMenu.apk
/system/app/Keystring_factory.apk
/system/app/Keystring_misc.apk
/system/app/KiesAir.apk
/system/app/MediaHub_D2.apk
/system/app/MusicPlayer.apk
/system/app/MyFiles.apk
/system/app/PCWClientS.apk
/system/app/PhoneErrService.apk
/system/app/PolarisOffice4.apk
/system/app/Preconfig.apk
/system/app/PreloadInstaller.apk
/system/app/SMemo.apk
/system/app/SMemoProvider.apk
/system/app/SSuggest.apk
/system/app/SamsungCamera.apk
/system/app/Samsungservice.apk
/system/app/SecCalendar_NAmerica.apk
/system/app/SecContacts.apk
/system/app/SecContactsProvider.apk
/system/app/SecEmail.apk
/system/app/SecExchange.apk
/system/app/SecGallery2.apk
/system/app/SecMms.apk
/system/app/SecPhone.apk
/system/app/SecSettings.apk
/system/app/SecSettingsProvider.apk
/system/app/SecSetupWizard.apk
/system/app/systemUI.apk
/system/app/Tag.apk
/system/app/VideoPlayer.apk
/system/app/YahoonewsDaemon.apk
/system/app/YahoonewsWidget.apk
/system/app/serviceModeApp.apk
/system/app/voicetalk.apk
Props
build.PDA:
VZW:
/system/app/SyncMLSvc.apk
SPR:
/system/app/SprintSyncMLSvc.apk
ATT:
/system/app/wssyncmlds.apk
/system/app/wssyncmldm.apk
COMMON:
/system/app/serviceModeApp.apk
/system/app/SecMms.apk
/system/app/BCService.apk
/system/app/SecBrowser_VZW.apk
/system/app/Samsungservice.apk
/system/app/CSC.apk
/system/app/Keystring_factory.apk
ro.product.device -
/system/app/FactoryTest.apk
/system/app/Keystring_factory.apk
/system/app/Keystring_misc.apk
/system/app/Lcdtest.apk
/system/app/SecEmail.apk
/system/app/SecExchange.apk
/system/framework/com.google.android.maps.jar
/system/framework/framework.jar
/system/framework/services.jar
2- Network Specific Apps
This builds a bit more to point 1/1a, making sure CSCs & props are set correctly. Some, not all apps switch functionality based off salescode as seen above. Then there is another category of apps that should switch but are somewhat broken. These are any that contain checks containing compile time inserts of network name into the code itself instead of reading from a prop value. Many of these are for base functionality, and stuff you really shouldn't be living without.
How can devs tell what switches and what doesn't? Below is a badly hardcoded "cross network" check. This example will always be false even where it is suppose to run because obviously the string SPR will never equal VZW. This is likely sprint specific code, as on Sprint the hardcoded value would come out if SPR==SPR resulting in a hardcoded true making this code always run on networks its not suppose to.
Code:
if(mUiccController.getUiccCardApplication(1) != null)
{
if("SPR".equals("VZW"))
This is an example of a proper salescode check looks like that will work on any network, notice it checks from string s for salescode prop instead of a hardcoded value:
Code:
s = SystemProperties.get("ro.csc.sales_code");
if(!"SPR".equals(s) && !"BST".equals(s))
Below is the list of apps us at Synergy have compiled of important apks. Most apps like SecSettings will switch around properly so do not need to be "carrier specific" so are not contained in this list. The ones actually contained in the list all have some use for proper network functionality/back end functions to work right. This list also contains some apks that should be considered "dangerous" and need to be removed from ports to other network such as using Sprints OMADM activation client elsewhere.
ATT:
Code:
[b]Apps:[/b]
LTESetting.apk
LTETest.apk
MoreServices.apk
OmaCP.apk
SecContacts.apk
SecPhone.apk
WISPr_Android22_postpaid_ATT.apk
wssyncmldm.apk
wssyncmlds.apk
[b]libs:[/b]
libAMSWiFiLibsR2.so
libChatOnAMSImageFilterLibs.so
libdprw.so
libjni_emailencryption.so
libomacp.so
libreference-ril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libril.so
libsecril-client.so
libSpeexEncoderJNI_1.0.0.8.so
Sprint:
Code:
[b]Apps:[/b]
Activation.apk
ConnectionManager.apk
LTETest.apk
MIPErrService.apk
OmaCP.apk
PCWClientS.apk
PhoneInfo.apk
SecContacts.apk
SecPhone.apk
SlateTest.apk
SprintAndroidExtension.apk
SprintDM.apk
SprintSyncMLSvc.apk
SprintZone.apk
Sprint_Installer.apk
vtt-sprint.apk
[b]Libs:[/b]
libAMSWiFiLibsR2.so
libChatOnAMSImageFilterLibs.so
libomacp.so
libreference-ril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libril.so
libsecril-client.so
libsyncml_core_sprint.so
libsyncml_sprint.so
Verizon
Code:
[b]Apps:[/b]
appdirectedsmspermission.apk
ba-syncservice-app-signed.apk
LTESetting.apk
LTETest.apk
NewBayService.apk
qospermission.apk
securesettingspermission.apk
SPG.apk
SyncMLSvc.apk
vmmhux.apk
VZWAPNLib.apk
vzwapnpermission.apk
VZWAPNService.apk
VzwSilentSSOEngine.apk
[b]Libs[/b]
libreference-ril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libril.so
libsecril-client.so
3- Network Specific Framework
While there are minor exceptions, ATT/TMO/VZW generally register handsets on the network the same way. Sprint is way off in left field on how telephony registration works. They have their own APIs in framework2.jar, and framework.jar handles most of the telephony part for registration. If you want to port to or from Sprint, you need to make sure the device can register properly. Hardcoding your phone number inside of a APN is not proper registration and is giving the illusion of things working when other major things are failing on the backend. Hence this "fix" should not be used unless you really know what you are doing.
Signs of Improper network registration:
-Unknown Phone number in About Phone
-MMS fails
-Issues with Data Roaming
Proper Way to port:
Merge in framework.jar/com/android/internal/telephony and framework2.jar/com/android/internal/telephony.
Going TO sprint, framework/framework2.jar needs the added Sprint apis
I explained more on what each of the files do over in heros thread here: http://forum.xda-developers.com/showpost.php?p=39896841&postcount=6877
So that ends my 2cent rant. Networks always have a way to know your rooted between CSCs+Sysscope and whatever else they have hidden in the radios. Its a fact of life now, get use to it. Right now no carriers really seems to be caring though so lets keep it that way. If we start to abuse that privilege and cause networks issues there might come the day where enough is enough and thousands of root users cry out in terror and are suddenly silenced. On the flip-side though, If we show carriers were trying to respect their networks and just want to do cool stuff with our devices hopefully they will let us just continue on with what were doing. Who knows, maybe they will read this and make all the apks switch proper based on salescode so we dont have the issues at all in future, but for now lets be careful.
So let 'er rip devs. Fire away questions, lets all get stuff working right and try to put to rest all these silly hacks that are causing more problems than they are worth.
Trev has all the technical details above, but if you want a TL;DNR version, here it is:
This thread is not directed at any one person, dev, or ROM. But since multicarrier functionality is essentially the new wild west for us on Android, we need to take a step back, have a talk, and make sure we are doing this properly before things get out of hand and carriers start dropping C&D notices on all of us.
Basically it comes down to this: Once we start manipulating carrier files (CSCs, RIL, MCC, even smali in certain system apks) we can really cause a lot of network problems on the back end which may aggravate the carriers (who have turned a blind eye to this so far). For example, on the S3 the widely known and generally accepted way to fix lockscreen notification bubbles all over XDA and other forums and news websites/blogs was to simply nuke the customer.xml file. While it may look like that fixed the problem on the surface, it was actually causing a huge network issues on the back end that users weren’t seeing – but the carriers certainly were, and my guess is spamming random networks to get a MCC match all because a user deletes some random XML file to get his bubbles back was probably frustrating the carriers. Which is something we really want to avoid.
Making a multicarrier ROM can be a frustrating task as random bugs show up; if we start guessing at fixes or begin making changes without considering the ramifications on the network end, we will just make the problem worse for ourselves and maybe even forfeit our ability to do this in the future.
Understood
Does this also happen when you flash your phone to a other carrier ?
Edit: didn't think I'd be able to post here lol
innocentmod said:
Does this also happen when you flash your phone to a other carrier ?
Edit: didn't think I'd be able to post here lol
Click to expand...
Click to collapse
Not entirely sure what scenario you mean, but
If you go flashing a sprint stock rom when you are running on Verizon's network that is a bad idea. If a dev goes and makes that stock rom carrier friendly to Verizon you can then run that and not worry about the basics failing.
if you mean changing hardware keys and flashing a Verizon branded phone to use on Sprint's network and what rom to run I cant help much there but I'd say always match up compatible software to the network you are planning on talking to. Moving branded devices between networks is another whole set of hurdles both technically and legally, so your kinda on your own there.
TrevE said:
Not entirely sure what scenario you mean, but
If you go flashing a sprint stock rom when you are running on Verizon's network that is a bad idea. If a dev goes and makes that stock rom carrier friendly to Verizon you can then run that and not worry about the basics failing.
if you mean changing hardware keys and flashing a Verizon branded phone to use on Sprint's network and what rom to run I cant help much there but I'd say always match up compatible software to the network you are planning on talking to. Moving branded devices between networks is another whole set of hurdles both technically and legally, so your kinda on your own there.
Click to expand...
Click to collapse
Well for example, I might use my sprint sgs3 to either boost-mobile or cricket. Let's say I use your rom, would it wotk evem though I'm not on sprints network?
Never knew it went so deep. I have a whole new found respect for the developers like treve and echelon. Thanks for trying to keep things ligit
Sent from my SCH-I535 using Tapatalk 2
treve, makes alot of sense i havent even posted my rom in the sprint forums because i had an idea from reading your posts in the synergy thread etc. that this was an issue. most tmo/att people seem to say everything works good though
innocentmod said:
Well for example, I might use my sprint sgs3 to either boost-mobile or cricket. Let's say I use your rom, would it wotk evem though I'm not on sprints network?
Click to expand...
Click to collapse
Dont know really about cricket and boost, havent checked out the roms too much yet. They might have their own set of apps as well wed havta take into account. We put experimental support in but honestly have not looked much at the little guys.
beanstown106 said:
treve, makes alot of sense i havent even posted my rom in the sprint forums because i had an idea from reading your posts in the synergy thread etc. that this was an issue. most tmo/att people seem to say everything works good though
Click to expand...
Click to collapse
Man, freekin sprint. Youd think going CDMA->CDMA would be a snap when its actually the other way around. For the most part though it looks like
VZW -> TMO/ATT - Simple (no framework change)
Sprint -> VZW - Moderate (telephony framework change)
Sprint -> TMO/ATT - Sucks (deeper telephony change)
VZW -> Sprint - Sucks (Sprints extra apis, ugh)
for att/tmo just gotta make sure VZW apps/props dont go through to them, set salescodes, replace a few apps their all gravy. I think we got semi-lucky with the VZW base because the GSM stuff works great for TMO/ATT. Too bad sprints off in left field
---------------
Also on a side note, just updated the OP a bit with cleanup and a why you should care section, showing some apps that are affected by making some of the changes and a bit more detail on the why its important part of things.
Thank you TrevE and eschelon for all of your hard work and helping us get this done the right way.
Extremely valuable info Treve. Thanks for sharing. Recommended for newsworthy front page.
TrevE this is great info. I just ported a Verizon to tmo for personal use using this info. I know you don't have tmo here but I striped the Verizon apps and kind of compiled the other lists to get tmo.
Seems to work all my tmo apps work and everything in settings show correctly. I hope people continue the movement of doing these right. Verizon already locks down bootloaders. If people keeping actually messing with network function it could bad.
Sent from my SGH-T889 using xda app-developers app
Great read ! Very informative and helpfull thank you ! My question is how does this info effect market apps between roms as well as carriers, example say hulu+ works on a vzw rom but doesn't on a ported rom. Any info is very appreciated.
Sent from my SCH-I605 using xda app-developers app
There is a very simple solution to all of this really. When you are building the rom, leave all the network stuff out. We all know that all S3 are the exact same phone with different software for where they were released. The only ones having issues are the American phones as they have 50 different carriers fighting for everyones service. To simplify the issues, leave any network files alone. This way, when its written to a phone, it only writes and updates the files that are needed for the rom to work. In all honesty, you are never writing to the base operating system any ways. Its not like in the old days when all phones had basic software for one carrier and would change if you activated it on a different network. For example, blackberry curves in Canada all had At&t software on them until the phone was activated on a network. So if you activated it on Telus, it would change some features and splash screen to telus and have the telus apps on it. Or if it it was unlocked, you went to bell, it would update it to bell features. All the base software is still the same, just cosmetic and apps would change to that provider. The same thing goes with Any new phone now. You just have to learn to code the ROMs to rewrite what you want it too, not every files. Sorry if its a bit confusing, its 5 am here.
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