3g turbocharger on the OV - Optimus V Android Development

This should work for other phones besides ours where WiFi breaks if you're using the zeppelinrox scripts.
Scenario:
Using zep's v6 supercharger and kick ass kernelizer and they play fine. Add the 3g turbocharger and you can't connect to any WiFi networks.
The quick way to fix:
Copy these scripts to your sd card and set them to run at boot from script manager and use the 3g turbocharger script like you have been.
The options I used when running the v6 Supercharger in the supercharger file I attached was option 5 since it's for 512MB memory phones (like ours) and the Nitro Lag Nullifier.
Here's the steps if you don't want to use my choices:
Run the V6 Supercharger and Kick Ass Kernelizer and make your tweak changes as you normally would.
Use a file manager and copy your generated 98KickAssKernel.sh and 99SuperCharger.sh from /system/etc/init.d/ to your SD card.
Now rerun both scripts and undernelize/uninstall your tweaks.
Confirm the 2 scripts above aren't in the init.d folder after you ran the script uninstallers. If they stayed after the uninstall delete them with a file manager.
Delete the supercharger lines from /data/local/userinit.sh with a text editor.
Run these two at boot and with root credentials from Script Manager or another scripting app (I use another script app but that's just me).
Now run the 3G Turbocharger and it'll do it's own thing and not screw up Wifi this time.
With the 3G tweaks I ran the speedtest.net app and benchmarked my 3G speeds a few times and did notice maybe 50% gains on my 3G speeds- so in that regard I think the 3G and kernelizer scripts are more apparent then the v6 supercharger script for me.

My problem with the 3G turbocharger isn't actually the wifi breaking, it's my notification power widgets breaking. I found if I supercharge options 7 and 13 then use KAK, it works fine. But when I use the turbocharger, my notification power widgets get all tweaky. Wifi seems fine for me though. ...any chance this fix happens to fix that issue as well?
Edit: oh yeah I should clarify on how the notification power widgets break. The orientation button doesn't work, the status bar brightness control doesn't stick if you turn the screen off, brightness button doesn't work, etc.
OH and I've tried the experimental #1 and also the known max values option. Both break it =[

Yeah. I don't know about that. I use other power notification buttons than those. One of them being for brightness because I never liked the status bar one.

Do these scripts even help? I tried the supercharger script, but it didn't do anything besides kill all apps that I lowered. It pretty much killed multitasking. It didn't speed up any apps or let them load faster.
How does this 3G script work? What values does it change? I'm very skeptical of these things. My 3g speeds vary second by second. You really need repeated extended test to get an accurate average.

I'll see if I can scrounge up some links on the values that get changed with the 3G script. They're kinda spread all over the interwebs in various forums. Zeppelinrox did do a good job of pulling them together in his script.
As for the v6 script I'm one of those guys he doesn't like. I've tried testing his script following his steps to monitor the effects of OOM grouping modifications and don't see any difference before and after using his script. That being said I still use the v6 script because it became part of my routine on ROM upgrades.

Can someone send me their build.prop file from a phone that hasn't done the 3g tweaks? I want to see if any of these values even exist on our phones out of the box. A lot of the ro.ril values it adds/adjusts are mainly documented for GSM network phones which Virgin Mobile is not- we're on a CDMA network.

Related

[Q] Adreneline v. Supercharger V6

It appears that Adreneline and Supercharger V6 perform similar functions.
Any thoughts on which is better (if either is better) and why?
hgoldner said:
It appears that Adreneline and Supercharger V6 perform similar functions.
Any thoughts on which is better (if either is better) and why?
Click to expand...
Click to collapse
I Like adrenaline better because you can flash it and be done with it. instead of having a script manager using a service which uses battery. IMO
synisterwolf said:
I Like adrenaline better because you can flash it and be done with it. instead of having a script manager using a service which uses battery. IMO
Click to expand...
Click to collapse
Not quite on the supercharger part. You run the script once, and it saves to the init.d and you're good. Script Manager doesn't need to be running all the time.
PonsAsinorem said:
Not quite on the supercharger part. You run the script once, and it saves to the init.d and you're good. Script Manager doesn't need to be running all the time.
Click to expand...
Click to collapse
Oh i didnt know how it worked. i thought script manager had to turn it on with every boot. thank you.
Right now I have the following init.d scripts:
00cpufreq_modules (comes from tiny's kernel, I believe)
77sdcardspeedfix (adreneline takes it up to 3048, I keep it at 512)
94fastcharge (also associated with kernel, I think)
94incredicontrol (likewise, looks like I need to change the number!)
S97ramscript (Juwe's RAM script)
Adrenaline appears to include some of these; Supercharger appears to modify init.rc and build.prop.
And that's all I can figure out on my own so far.
V6 for me. Has a lot of options to tweak, plus it's easy to undo and redo (when flashing a new kernel, etc.).
hgoldner said:
Right now I have the following init.d scripts:
00cpufreq_modules (comes from tiny's kernel, I believe)
77sdcardspeedfix (adreneline takes it up to 3048, I keep it at 512)
94fastcharge (also associated with kernel, I think)
94incredicontrol (likewise, looks like I need to change the number!)
S97ramscript (Juwe's RAM script)
Adrenaline appears to include some of these; Supercharger appears to modify init.rc and build.prop.
And that's all I can figure out on my own so far.
Click to expand...
Click to collapse
Best way to learn is to open them up in a text viewer and read what they do. The 94 one is redundant. Fast charge turns on fast charge, where Incredicontrol turns on fast charge and audio boost. They can have the same number, but in this case they're overlapping and it's pointless to have both.
So only use one of them?
Sent from my ADR6300 using XDA App
Erisnoob said:
So only use one of them?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Only use one of what? The two 94 scripts? You can have both, it doesn't hurt, but you don't get any added benefit. So, the question is, do you want only fast charge (use fast charge and delete Incredicontrol) or do you want both fast charge and audio boost (use Incredicontrol and delete fast charge).
Thanks, I was talking about adrenaline or v6 tweaks. From the mods thread it was a little muddy on whether or not to use both. Thanks again.
Sent from my ADR6300 using XDA App
Erisnoob said:
Thanks, I was talking about adrenaline or v6 tweaks. From the mods thread it was a little muddy on whether or not to use both. Thanks again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
If I remember right, those are sort of overlapping again, but not quite to the point of redundancy as the 94 scripts mentioned above. Both have RAM tweaks, of which you only need one of. I think V6 would take precedence if both were used. But adrenaline has some stuff that V6 doesn't have, and vice versa. Both should be able to be safely used together, but there is a lot of wasted motion.
And that uses up my allotted number of helpful/informative posts here, so now I'm going back to my #Occupy forum.
synisterwolf said:
I Like adrenaline better because you can flash it and be done with it. instead of having a script manager using a service which uses battery. IMO
Click to expand...
Click to collapse
after taking the time to rip apart V6 and Adrenaline i found out that script manager is only used to view the script and not to run it for V6. you can use terminal emulator after you you told V6 to install to your system.
if you did what i said above all you need to do is type
Code:
$ su
# bash V6
its will put a script into init.d and do some build.prop tweaks. i have been running both mods for 3 days now with no problems. ( every phone is different)
for me i chose the option 6 the "leaded under 512hp" along with adrenalin its been super smooth. i would also suggest to do the mods after you have done a clean wipe if you are on CM7 nightly.
there are some redundancies to having both mods but to avoid this if you flash the older universal adrenaline without the rams script, version 9, you will avoid using 2 rams scripts. i hope this helps anyone out there reading this.
PonsAsinorem said:
Only use one of what? The two 94 scripts? You can have both, it doesn't hurt, but you don't get any added benefit. So, the question is, do you want only fast charge (use fast charge and delete Incredicontrol) or do you want both fast charge and audio boost (use Incredicontrol and delete fast charge).
Click to expand...
Click to collapse
Interestingly, I removed the 94fastcharge and the 94incredicontrol failed to "stick". I removed the 94incredicontrol (I don't care about audio boost) and the fastcharge script always sticks. Go figure.
hgoldner said:
Interestingly, I removed the 94fastcharge and the 94incredicontrol failed to "stick". I removed the 94incredicontrol (I don't care about audio boost) and the fastcharge script always sticks. Go figure.
Click to expand...
Click to collapse
It should. Odd. Maybe because it's the second line, but that shouldn't matter. I'll have to experiment and switch aboost with fast_charge_USB and see if that sticks.

Editing Calkulin's Processor Speed Script?

Does anyone know how to edit Calkulin's processor speed scripts to run at 800MHz all the time instead of using the following preset profiles of 1.2GHz - 100-85%, 1.0GHz - 84-36%, 800MHz - 35-0%?
Simply put, I don't need the faster processor speeds and would rather have the benefits of the longer battery life that running at 800MHz provides. Problem is there are several scripts and I don't know what values to change to accomplish a constant state of 800MHz. If anyone can help me out, I would appreciate it.
FYI I sent Calkulin a message several weeks ago asking this question and presume he is very busy as I have not received a response. I thought I'd try asking the community.
Have you tried to view your screenstate scaling... the profiles are right there you can change where it say 120000 to 80000 similar to battery profile 2 as well as where it says MaxCPu speed.... you can change that to your desired speed.... just use root explorer or notepad+
Its really pretty simple... if you have rom toolbox you can change it there as well which as a whole program is pretty damn useful
Sent from my Xoom using Tapatalk
You can use a third party app, like Setcpu, to established the desired clock. If you want to do it manually without an app, you can open the script file with a text editor and change the values. Look in /system/etc/init.d for the script.
Easiest way is to use Setcpu so you can edited on the fly.
Easy way would be edit the line "MAX_CPU_SPEED_PROFILE_1="1200000"" to show "MAX_CPU_SPEED_PROFILE_1="800000""

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

Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!

[ROM] Dec.1st -{}- UVDLJA {} LIGHTNING_rev3 -{}- 4.1.1 Jelly Bean OTA

Welcome to Lightning ROM
MAJOR UPDATE, REV3, CHANG LOG IN SECOND POST**********
The goal when creating this today has been simple. Squeezing the most performance out of the T-Mobile Galaxy S III as I possibly could, without destroying your battery. This ROM was build with two things in mind - optimization and speed. Nuff said. It is based off the official Jelly Bean leak as of late last night and wild child's deodexed version he was kind enough to throw down. It will probably impregnate you, with twins, then not pay you child support. If you are ready to propel your device to levels above 9 thousand, you should probably keep reading. You have been warned. IT IS FAST! ..... yet... friendly...
Like myself, in the spirit of android, I am sure you all love customization. I am doing something a little different with this. Rather than add all the toggles, mods, themes, etc, I focused today on the performance aspect and will leave the theming up to you, and after you get it set up the way you want (as there will soon be and already is tons of pretty extras for this build) revert to post 2 of this thread for a nice little guide to odex this bad boy straight from Android UI via terminal emulator. I'll take care of the tweaking, you theme it the way you want, then wrap it up with some memory optimization of your own, or don't. Sound good? Thought so
Getting right down to it - a quick list of things modified here, and I know I am missing some things:
-Init.d support
-Busybox
-Deodexed (until you odex - see post 2)
-Rooted - duh
-CIQ removed***
-Debloated: removed a lot of stuff, but it is all avail' in the market, youtube, etc, you would have had to update it anyways -__-
-File system and SD read optimized for speed
-added freeza's custom CPU script to init.d ***see changelog in post 2
-Build.prop has been modified.
*added the 0 ring delay script
*wifi scan adjusted to 600
*media streaming optimized
*media recording optimized (video and image)
*data speeds optimized
-Database df on each boot / sql support - totally kanged this from somewhere else it was kanged... all credits due
-Memory optimizations
-Default IO scheduler optimized for flash-type disks (android devices)
-Carefully modified CPU parameters with performance in mind. Tweaked values to optimize IO throughput during heavy workload and multi-tasking, yet on the other end, CPU cycles are greatly reduced when system is not under heavy load. You will see this in performance :highfive:
INSTALLATION - follow this to the T, or I will ignore you. And keep in mind you might still have issues. Not every device is the same.
1. download ROM, put it on your external SD card, and verify it is good with an MD5 check
2. once all is well, boot to recovery
3. do a factory reset/data wipe (I have always been in the habit of being thorough and formatting anything 3 times)
4. format/wipe system (3 times recommended)
5. flash ROM
6. reboot (it will take a couple minutes)
7. once the device boots, let it stand alone for about a minute or so (i typically wait until it shuts off the display on its own) and ENJOY
NOTE: DO NOT TRY TO SIGN IN TO DROP BOX. I REMOVED IT. DL FROM MARKET!!
Also, some other things removed: browser, YouTube, calculator, some other stuff. I didn't remove anything that was not available in the play store. Wanted to keep it light weight. Do not try to sign in to anything other than your google account when you boot. Again, enjoy.
thanks to wild child, freeza, virus, steelH, dj, luke, ktoonz, and many others. mad respect to you all. i have implemented things that are either your direct work or things i have learned from you. so here is my humble shout out. if there is something i left out, somebody i didn't mention, please forgive me and post in this thread and call me out, i will happily update the OP with thanks. respect to you all
REV_3 - ready, set.. ok click now!
With morfic's kernel..... clocked at 1.83
ok... so if you are like me, and you REALLY wanna get intense with this, and just make it as bad A as you possibly can, keep reading....
This will essentially odex all files in your /system/framework and it will do it straight from the Android UI via my personal favorite app ... this is good because it frees up mem, and reduces DVM size. OPTIMALLL
1. download the odex.zip here --> PURPLE
2. extract all files with a file explorer, i prefer root explorer or fx file explorer
3. place the extracted folder and all of it's contents in /data/local/tmp ... so you should have /data/local/tmp/odex/+(misc files in new odex directory)
4. give the new directory and ALL contents FULL permissions. full read, write, and execute perms. your file explorer, if it has taken you this far, should be able to accomplish this
5. download this app TERMINAL EMULATOR dont worry it is free. open the app
Type the following commands - each new line should be executed with the enter key:
su (hit enter, it will ask for root)
/data/local/tmp/odex/odex (hit enter, you will see
you will see a bunch of outputs. there will be a message when it is done (honestly, like 10 seconds if that) saying something like "enjoy your hybrid ROM"
type "reboot recovery" (without the quotes)
device will boot into recovery immediately after you hit enter...
wipe cache and dalvik cache once more each, and reboot your device.
viola <--- this was spelled wrong. but i am going to leave it. because i can. rofl
THANKS*** freeza for sending me the the odex script, and you're welcome, for the bootclasspath for the script.. lulz. and thanks freeza for convincing me to download titanium backup again... and you're welcome for giving you the peace of mind that you can odex framework from android. el o el
****change log*****
rev3-December 1st, 2012 -uploading
-added morfic's alpha 23 kernel. OC'able to 1.83, no UV, L2 cache tables optimized, CPU hot plugged (for now, panel of=cpu1 off), pretty much an overhaul here. performance is ridiculous.
-removed CPU tweak by freeza (i still love you tho)
-optimized IO, AGAIN. adjusted ondemand parameters for a little bit better performance
-removed unneeded scripts from init.qcom.post_boot.sh file - positive effect on IO
-cleaned up build prop, added scripts for TCP windows, added network hack by... somebody... can't remember. File is in /etc/init.d/ "internet"
-optimized BT audio streaming
-added properties for optimal accessibility of T-Mos spectrum/towers
-disabled unneeded logging - save CPU cycles and power
-debloated some more. lightweight. DO NOT... try to sign in to dropbox upon first boot (if it even gives you the option) download the latest version of the app on the play store.
rev2-NOVEMBER 19, 2012
-removed some UI audio sounds (charger connection [for those that listen to music], lowbattery sound, volume toggle sounds, other annoying useless sounds such as boot up and power off)
implemented freeza's CPU control script for some amazing performance and battery life. thanks bud, as always, great work. i have been running this since he was finished with it, and it is absolutely amazing. your device with tons of unique and user friendly, editable scripts.
-freeza's CPU script adjusts CPU parameters for both cores based upon whether your device is charging, and how much battery you have left. it is a performance and battery friendly script that is power efficient and editable depending on what YOU want your device to do.
beta1-
initial release
all the things...
In rev 2, with freeza's CPU mod, you can navigate to init.d and you will see a "70cputweak" file. if you open that up, you can adjust CPU values and parameters of governors to your liking. for now, i left them as is - the way they were when freeza gave them to me. edit them with a file explorer and reboot and you are now adjusting your OWN values based on the performance and battery YOU desire. follow instruction in OP to flash
Thanks will try this later today
Sent from my SGH-T999 using xda app-developers app
Does teathering work on this?
ScottBroker said:
Does teathering work on this?
Click to expand...
Click to collapse
wireless/native? no. but my easy tether app works perfectly. i'll implement it, if i have time, in beta2... i haven't slept in two days lol
OP updated
Will the odex.me app work with this rom? I'm not lazy, just curious if there's an easier way to odex..tia
Sent from my SGH-T999 using Xparent Blue Tapatalk 2
Yeah does the odex me app work the same way than doing all that other stuff?
Sent from my SGH-T999
which tether app you using ?
Thanks
Odex me app will not work
great Rom thanks
Is this still running Touchwiz? How much RAM available? Other then your optimizations for speed what has been added or removed? Are animations gone due to the optimizations?
EGBTMagus said:
Is this still running Touchwiz? How much RAM available? Other then your optimizations for speed what has been added or removed? Are animations gone due to the optimizations?
Click to expand...
Click to collapse
All I have done is tweak properties listed. Didn't mess with animations, or anything. You guys can do all that with a theme, kitchen, etc... I would recommend wild child's work. It's great stuff. Like I said the reason for this is because after you get it the way you want, you can go in and odex it and finalize your OWN build the way you want it to look. I'm not too big on aesthetics. But I can make your device run better
And to answer your question, yes, it is still running touchwiz launcher by default. Again I would recommend apex or nova. touchwiz is awful IMO. nothing unique about it.
Rom looks great will be testing it tonight!
Can anyone confirm wildchilds kitchen is working?
Sent from my SGH-T999 using xda app-developers app
Liking the rom so far, only issue I have come across is that I can't get App2ExtSD2 working.
Can we use your Odex wizardry in any deodexed TW Rom?
SiNJiN76 said:
Can we use your Odex wizardry in any deodexed TW Rom?
Click to expand...
Click to collapse
yeah
http://forum.xda-developers.com/showthread.php?t=1994048
Thanks...didn't know he created a separate thread.
Anyway, the first thing I noticed was that when I try to sign into Drop Box from the initial boot sequence, it FCs... I also got nowhere near the Quad score the OP got. Mine was in the 3Ks. Just my experience.
CIQ?
SiNJiN76 said:
Thanks...didn't know he created a separate thread.
Anyway, the first thing I noticed was that when I try to sign into Drop Box from the initial boot sequence, it FCs... I also got nowhere near the Quad score the OP got. Mine was in the 3Ks. Just my experience.
Click to expand...
Click to collapse
I got over 5K in Quadrant, but I also came from a 100% stock phone (reset it to make sure there were no issues). DropBox fails intially because he removed dropbox from the rom.
EDIT:
I can't seem to find the stock web browser... has it been removed?

Noob here on init.d

What exactly are some scripts I can use with this? I've recently flashed Freezas optimized kernel. And my friend said I can use battery performance tweaks and everything. I've never used anything like this before so please be bold and informational on the explanation.
thanks!
Sent from my SPH-L710 using Tapatalk 2
Well really you can have almost anything in there...those scripts are executed as soon as the OS starts up (on "init" lol)
Its not limited to ONLY battery performance tweaks
For example, on my shift theres a soft-key backlight brightness issue on JB since its not officially supported, so I made a script that just does "echo "0" > /sys/class/leds/....." since the "/" file system is recreated on boot
So my backlights are kept off
Some mods, for example lentropy feeders, will add their own startup scripts here to initiate their tweaking services at boot (if they dont have an app counterpart to receive the BOOT_COMPLETE receiver)

Categories

Resources