Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
I wanted to post this on the 500+ page GSB ROM thread, but alas I need 10 posts under my belt first (9 now!).
Like others who upgraded to GSB v3.2, my soft-key lights quit working. Apparently v3.3 fixed this, but I'm still having the same issue. I wiped dalvik, but did not do a full wipe. Is a full wipe necessary to fix this issue?
Also, I'm having a lot of problems getting zeppelinrox's SuperCharger scripts to work. When I run them in Gscript, I get tons of stderr's. So I rebooted into Clockwork's recovery, mounted /system, mounted /data, and mounted /sdcard. Then I ran the script again from adb. It looks like the script is trying to make changes to /system/etc/rootfs/init.mapphone_umts.rc. This file doesn't exist on my phone, I don't even have the rootfs folder. It appears as though other GSB3.3 users aren't having this problem. Why is mine different?
[poo]
Scratch that first part. The lights are working. I just never paid much attention to them before they stopped working, didn't realize that they were triggered by a sensor. Duh!
I still have the SuperCharger issue, though. I'd really like to get that working!
[poo]
Use script manager to run the script.
I'm making progress, but I'm not quite there yet. I got the same results with Script Manager. Then I noticed that the scripts included with GSB v3.3 were v5 of SuperCharger. So I tried v6 SuperCharger in Script Manager and things seemed to go much much better. The bulletproof launcher setting is sticking after a reboot, but the minfrees get reset back to 6, 8, 16, 36, 40, 40 every time. I've tried all three balanced settings.
[poo]
poo706 said:
Scratch that first part. The lights are working. I just never paid much attention to them before they stopped working, didn't realize that they were triggered by a sensor. Duh!
I still have the SuperCharger issue, though. I'd really like to get that working!
[poo]
Click to expand...
Click to collapse
Sensor so that they only come on when it's dark? Was wondering the same...
I'll follow this thread since I don't have the 10 either and want to get the SuperCharger scripts working as well, because I'm getting the same errors others are getting.
v3.3 also fixed a bug I was having where if I had the Google web widget search on my homescreen and hit the search magnifying glass softkey, the Google widget would move to the top of the homescreen and almost be stuck there, but looks to be good now.
Have you tried SuperCharger v6 with Script Manager, or just v5 with Gscripts?
[poo]
v5 was only for milestone.
You have to use V6.
There might be something overwriting minfrees on boot.
No wonder everyone's having so many issues. I think we all assumed that shed would have bundled the correct version with GSB.
Any idea, off the top of your head, what programs might be also trying to set minfrees at boot?
[poo]
poo706 said:
Have you tried SuperCharger v6 with Script Manager, or just v5 with Gscripts?
[poo]
Click to expand...
Click to collapse
Hmm, no idea? I installed and went into Script Manager and ran cRom-BulletProofLauncherOnly.sh and ran Balanced3, but got the errors all others were getting.
Edit: I used Script Manager and ran those scripts in /gscript. The v6 versions are in a different thread? I just found them, I'll have to install them at home since I don't have my charger here.
Edit x2: Looks like it's one .sh file. Run it in gscript and then select the type of memory management you want, that's it right? wshed says he's running bullet and balanced3. How do you get bullet running?
Download this .txt file and remove the .txt extension:
http://forum.xda-developers.com/attachment.php?attachmentid=586107&d=1304484146
Run that .sh script with Script Manager. It's all in one, no need for all of the individual scripts that were included with GSB. This is the main thread for SuperCharger:
http://forum.xda-developers.com/showthread.php?t=991276
As I said, the script works great. Bulletproof launcher setting sticks, but not memory settings.
[poo]
Use Script Manager and load the single V6 Script.
If you have Auto Memory Manager, disable superuser permissions so it doesn't load settings on boot.
If you have Autokiller Memory Optimizer, you can disable the apply settings on boot option.
If you need to, you can always use Script Manager to load /system/etc/init.d/99SuperCharger on boot.
zeppelinrox said:
Use Script Manager and load the single V6 Script.
If you have Auto Memory Manager, disable superuser permissions so it doesn't load settings on boot.
If you have Autokiller Memory Optimizer, you can disable the apply settings on boot option.
If you need to, you can always use Script Manager to load /system/etc/init.d/99SuperCharger on boot.
Click to expand...
Click to collapse
Yea, the big confusion was everyone was using the v5 scripts and nothing was working... I'll def hit up the v6 tonight, thanks.
I've never installed Auto Memory Manager or Autokiller Memory Optimizer, so those aren't the culprits. Using Script Manager to load /system/etc/init.d/99SuperCharger on boot did work. But I'm a little confused. Aren't all the scripts under init.d run at startup anyway? If true, then using Script Manager to load S99SuperCharger just runs it again, right?
[poo]
Thats right.
Using SM to load it on boot is just a workaround until you figure out what else is loading minfree values.
Since you don't have a minfree app installed, it there may be something else in the init.d folder or perhaps another boot script folder such as a userinit file or folder
I think I found it, /init.rc seems to be the culprit. I take it that init.rc gets executed after all of the scripts in init.d? I'd really rather not have to load SM at boot every time just to override the settings in init.rc. I assume that editing init.rc in some form or fashion would be the best way to go? I could either change the values in init.rc and remove S99SuperCharger, or leave S99SuperCharger in place and comment out the conflicting lines in init.rc.
Thanks for all the help, by the way!
[poo]
Editing init.rc isn't the right approach. It looks as though it gets rewritten at startup. I pulled init.rc via adb, added some text to a commented out line, pushed it back, and rebooted. The text I added was gone after the reboot. So now the question is: how and when is init.rc getting created? If init.rc is already in place by the time 99SuperCharger gets run, maybe 99SuperCharger could just modify init.rc prior to its execution.
[poo]
Actually, init.rc wouldn't interfere with 99SuperCharger.
On the milestone there is:
/init.rc
/init.mapphone_umts.rc
/system/etc/rootfs/init.rc
/system/etc/rootfs/init.mapphone_umts.rc
The first 2 items I can't edit they get created on boot.
The 2 items in the rootfs folder I can and it sticks.
If I have a init.d/99SuperCharger file, it would supercede the *umts.rc file and that file supercedes the init.rc
So the bootscript>*umts.rc>init.rc
I think that only way 99SuperCharger doesn't stick is if your ROM doesn't even load it (there actually was a bug in CM7 for milestone where it didn't load) or you have a userinit.d folder or file
edit: okay look for folders...
/data/local/userinit.d
/sd-ext/userinit.d
or files
/data/local/userinit.sh
/sd-ext/userinit.sh
Also, I wonder if you do have an *rc file (like init.mapphone_umts.rc) that can be hacked... heh
Already looked in both of those places, no files or folders of interest. What creates init.rc, do you know?
[poo]
Its in the boot.img file I believe.
Maybe reflashing the rom will fix it?
Sent from my Milestone Powered by my V6 SuperCharger
I'm trying to run the v6 version but I can't find the Interactive option anywhere in Script Manager. I go to config and it's not there. Help?
Edit: found the new version of script manager you touched the screen for input haha, and got it running.
Well, i just wanted to make this thread so others with the same issues i had would have a place for it all. Unfortunately most of the modded roms didnt have swype, no biggie i thought i backed up the apk from the original rom... well come to find out you need to do a coupla things.
i found these threads below which pretty much explain the process.
first is getting the right swype files in place... follow this thread
http://forum.xda-developers.com/showthread.php?t=841603
i ended up loading up the stock rom from a backup, and used adb and subsequent adb pull to grab the libSwypeCore.so and Swype.apk from the running system.... AND ALSO grab the build.prop as stated here from your ORIGINAL ROM.
http://forum.xda-developers.com/showthread.php?t=1121231&highlight=swype
then reloaded your custom ROM,
at this point, i used adb again to grab the CUSTOM rom's build.prop, and compared it to the ORIGINAL build.prop...
your looking at the lines
ro.product.model=
ro.product.brand=
copy the two lines from the ORIGINAL to the custom one in a text editor... also while your at it, you can fix the issue i had... most of these custom roms are sourced from stock roms that are outside of the US.... which makes things interesting when loading up google maps etc... so while ur editing the build.prop, change the line
ro.product.locale.region=
to where ever your original build.prop is from.
at this point, copy the original Swype.apk, libSwypeCore.so, and modified build.prop to the root of your sd card.
then use adb to mount the file system and copy the files
Code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# rm /system/build.prop
# cp /sdcard/build.prop /system/
# cp /sdcard/libSwypeCore.so /system/lib/
at this point just use an apk installer to install swype n ur all good to go... now you have a licensed original version of swype on your phone with its custom rom.
ALSO NOTE, that changing your region to US in the build.prop will fix the bug with the latest BETA swype where upon boot it says cant load UK language etc.
Hope this helps someone in the future.... i gotta thank everyone around for all their hard work and time into everything, all the custom roms i have played with have been awesome, each has their own flavor and flare and its simply amazing what you can do with these android phones... from a relative newbie.. only had the optimus t for about a week now, the phone is awesome, a great combo of speed size and bat life.
Both this and the original howto are nice pieces of WTH.
- Uninstall Swype if (mis)installed. No need to uninstall the installer.
- Re-run the Swype instaler.
- Follow the instructions, it will download, install and license Swype and tell you how to enable it. You need to register yourself at http://beta.swype.com/android/create/ so that you have the credentials available that you will be asked to provide during the process.
- Done, installed, profit!
yes you can go with the beta, but like stated unless the build.prop says US for the region, the beta swype will error out opon boot of the phone.
also the latest beta has no option to cancel the word suggestion incase you completely fuggered up a swype, unlike in the old word suggestion popup, where u could just hit the x and try again... you now have to hold delete which takes much more time, then swype again.
also neither of the howto's above combine the knowledge of both.
Hi I do mines in a different way. What I do is take all the necessary files and place them in the rom file itself before flashing. You can do this by extracting via 7zip and repacking after.
In regards to the build prop, just open it up in notepad or what not and change the 2 lines you mentioned. For me, I would change to LG-P509 and LGE.
This is how I got my swype and other tmo apps working. No need for adding swype installer and joining beta.
Sent from my LG-P509 using XDA App
For All Defy and Defy + JB Roms
*****Disclaimer***
- Before flashing the BM.Memfree.Defy.zip please patch your service.jar first and place it in the zip /system/framework/
You can get your services.jar from the rom you're currently using with a root explorer. It is located in system/framework/
To Patch it read from *Optional Memfree tweak* in the quote....
Thanks to Husi10 for the heads up
Please thank brainmaster for the zips - Here
Also lambgx02 for his work on the seeder - Here
Below is the original quote from brainmaster read it to know more about the tweaks
brainmaster said:
Here is the description of the Tweaks:
Scripts in the /system/etc/init.d folder:
08dalvik - Moves the Dalvik cache from the ext4 /data/dalvik to the faster yaffs /cache/dalvik partition
95zipalign - This is more enhanced zipaligning method. Its zipaligning the apps in the /system/app and /data/app. It also creates the database that contains infos on apps that are already zipaligned, and checks that databe on reboot. If all apps are zipaligned, it skips the zipalign process. Zipaligning is useful because its reducing the amount of used RAM
99bmtweak - Contains the tweaks that I've collected and enhanced over the time. Included are IO tweaks, TCP tweaks, SDCard ReadAhead tweak, SQLite Vacuum Database tweak
hosts file in the /system/etc folder:
Hosts file makes your Phone ADFree.
resolv.conf file in the /system/etc folder:
Google DNS Servers
placeholders in the /system/app and /data/app folders:
If you want to add a system app or install data/app with the CWM Zip file, just drop the apk in the /system/app or /data/app folder in the CWM Zip file and they will be installed when you flash the CWM Zip.
/kernel folder:
Enables the init.d script support.
updater-script in the /META-INF/com/google/android folder:
Deletes the Cache and Dalvik Cache, mounts the /data and /system partitions, copying the needed files. It sets the permissions. If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app.
build.prop tweaks Injector in the /tmp folder:
Injects the values in the /system/build.prop file. The /tmp/mytweaks.sh file shouldn't be edited! The file /tmp/misc contains the buildprop tweaks. You can add your own build.prop tweaks in that file.If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app, also IF you use comments (#Disable.ADB.Notification.Icon), DON'T use spaces, use ONLY the underline or dot character! These tweaks are included:
Code:
#Disable.ADB.Notification.Icon
persist.adb.notify=0
#Disable.Google.OTA.Checkin
ro.config.nocheckin=1
#Disable.Google.Reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
#Enable_Google_DNS_Servers
net.dns1=8.8.4.4
net.dns2=8.8.8.8
#HSPA.Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
#Dalvik.Optimization
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
Installation
Step 0: You must be rooted!
Step 1: Download the Busybox installer app and install the Busybox to /system/xbin. Again - install the Busybox to /system/xbin not to /system/bin!
Step 2: Reboot to recovery and install the BM.Tweaks.NEXUS.S.zip file.
Optional Memfree tweak - set to 100 MB:
In order to use the Memfree tweak on every ROM, extract the /system/framework/services.jar from the ROM and upload it to android.mimic.ca, let the site edit the file, download the edited services.jar and put it in the BM Memfree zip file. Then flash the BM Memfree zip in the Recovery.
The attached Memfree zip is for the stock JZO54K ROM.
Optional BM Seeder:
You can read everything about the tweak here.
This is my version adjusted for the Nexus S.
How can I be sure that the tweaks are working?
Open the RootExplorer and click on the /cache folder. IF the dalvik-cache folder is present, THEN the tweaks are working properly. Check also your /system/build.prop file for the #Brainmaster Tweaks area.
The tweaks are universal - not ROM version related, and can be flashed over any ROM but ONLY for NS or NS4G.
Disclaimer:
ALWAYS make a NANDroid Backup of your current ROM so that you can go back if you don't like the tweaks.
I will NOT reply any users PM's regarding this thread or my ROMs, only the DEVs should contact me over PM.
If you are user and have questions, write HERE in the thread.
BEFORE asking any questions, make sure that you read this post.
Click to expand...
Click to collapse
Ok So what I have done here is to modify the updater-script to work for the defy.... That's it
I haven't really touched anything else as am not a dev so can't tweak it specially for our defy but since our hardware is similar to the nexus s then I think it should be fine
Notes -
- People with a lot of apps installed on the phone either delete the 08dalvik file from the zip before flashing or after because you may not be able to install apps after this is due to the tweak using the /data partition for dalvik-cache.
- If you have already flashed the zip then Delete 08dalvik from system/etc/init.d.
-You want want to also check this out Don't use this and seeder zip at the same time.
Instructions - Flash zips in recovery and reboot
Don't forgot to patch your services.jar if your using the BM.Memfree.Defy.zip
Changelog
Seeder -
Updated rngd binary for seeder ---- It deepsleeps now noticeable reduced battery drain
BM tweaks & Memfree -
updated to the latest version from brainmaster
Downloads
http://www.mediafire.com/?k0gxranyqnt9w
Mirrors are always welcome
Credits for the original work :
Brainmaster
Lambgx02
Patch the services.jar? How would I do that? I understand the rest
Thank U For the Brainmaster's Tweaks for our Defy
ldnjoe said:
Patch the services.jar? How would I do that? I understand the rest
Click to expand...
Click to collapse
Updated OP with more tips
Kayant said:
Updated OP with more tips
Click to expand...
Click to collapse
In order to use this tweaks should I remove the tweaks that I have from pimp my rom first?
There is any difference with the included in pimp my rom?
This ones are better?
Edit: I don't think that the memfree or seeder binary is included in pimp my rom. I'll give it a try in PAC.
I'm currently using some tweaks I have been collecting and they give me some good results.
Hope this will increase the performance even more.
So, any feedback on results yet? I know it's a fresh mod, but still
Nailtrail said:
So, any feedback on results yet? I know it's a fresh mod, but still
Click to expand...
Click to collapse
Haven't really tested it fully yet but when I tested CM10 with chrome & a some apps in the background it was smooth I mean there was not lag in scrolling for me on chrome when browser theverge.com but as always there was whitespace because of our slow phone
The BM seeder thing really does work I think because one place I see the phone being me optimized is when you wipe dalvik cache for instance It takes ages for it to optimize the apps again if you have many but with the BM seeder tweak installed the process for me was at least two times faster
Btw I had all tweaks installed.......
Thank you Kayant for the release, that was really fast!
I flashed everything, seem to be great as excepted! I don't know if it's placebo effect but when I saw "optimizing app" during 3 time less than usual I think that's powerful.
We need more time to debate about stability or battery but my first impressions are great.
Thank you again for your awesome work.
Sent from my MB526 using xda app-developers app
Husi10 said:
Thank you Kayant for the release, that was really fast!
I flashed everything, seem to be great as excepted! I don't know if it's placebo effect but when I saw "optimizing app" during 3 time less than usual I think that's powerful.
We need more time to debate about stability or battery but my first impressions are great.
Thank you again for your awesome work.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
+ 1 its the same here.. just testing now..
Nailtrail said:
So, any feedback on results yet? I know it's a fresh mod, but still
Click to expand...
Click to collapse
At the moment am just testing...
I only install the seeder binary but I can say that i had seen an improvement in the default browser and in the play store.
I don't see much lag on it. I don't have much bandwidth so could be it that prevent me from seeing the hole potential of the seeder.
Sometimes stuck from loading the play store content for example but it doesn't bother at all.
I'm very happy with the results.
will be testing this and report back later.
here the link for services.jar mod for cna 4.0 by kayant.
credits to blk_jack
Seems to be working
Thanks Kayant! :good:
Seems to be working... the browser works faster and the lock screen waking is much faster....
There seems to be an improvement in gaming performance....
still testing...
do I need to wipe cache or dalvik before or after installation?
Edit: never mind, I'm testing it now, first impression the load of apps is super fast, I have 170 apps loaded in less than 2 minutes, awesome!
thanks for sharing.
modified a version from brainmaster's zips cause I don't like all build.prop changes and I'm to lazy to patch service.jar
the seeder mod with init.d script from brainmaster works better than the original one load only, it makes the phone faster in response and loading apps.
the zipaglin works and the other tweaks else, but need more testing.
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
zopeon said:
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
Click to expand...
Click to collapse
Thanks.... Will update the OP later ....
Edit - OP updated now checking to see if the tweaks need updating (v6)
Let's Go ^_^
zopeon said:
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
Click to expand...
Click to collapse
Agree, since i modified the services file and put the mem tweak started to get much more lag than without it.
It won't work in PAC.
I just put the 08dalvik in init.d, along with 95zipalign and the zipalign file into xbin. That should do right? I mean I want just the dalvik to /cache and the zipalign tweaks.
So I have been using V6 supercharger for ages. Now I turned off the supercharger zipalign option and then realized there is no zipalign in /xbin for CM10, it has never been running till now!
So, guys... One should probably disable V6 Supercharger completely, for these tweaks to work as they should? Or not?
I've finally supercharged my phone after a couple of months and now, a week after flashing, it's still running at the same smooth speed, where it would slow down after half of that time without the supercharger...
Want to try this, anyway, so, are the two compatible in any way..?
Cheers, Kayant, for the Defy version!
niksy+ said:
So, guys... One should probably disable V6 Supercharger completely, for these tweaks to work as they should? Or not?
I've finally supercharged my phone after a couple of months and now, a week after flashing, it's still running at the same smooth speed, where it would slow down after half of that time without the supercharger...
Want to try this, anyway, so, are the two compatible in any way..?
Cheers, Kayant, for the Defy version!
Click to expand...
Click to collapse
I suppose you should turn off V6 if you choose the Memfree tweak, and also zipalign.
But see my post above, zipalign probably isn't running if you are using CM10, check system/xbin to make sure!
But personally I let V6 handle the memfree and stuff, I know it works so I'd rather not try something else
Hello,
I wrote simple aroma installer for 4 apps and one mod.
Everything runs well, but after I reboot my device, there are no changes done!
This is my aroma config: http://pastebin.com/7LQgaXrp
This is my updater scripts: http://pastebin.com/Nt0bLRJC
As you can see, it's very simple
but I still can't find what is wrong that it doesn't apply selected mods :/
Do you know how to make it work?
Can you upload your aroma log as well, when I get to a PC ill take a look at your scripts but having the log can often help for quicker results
Sent from my Nexus 7 using Tapatalk 2
ok got to pc,
so first of all you're not setting permissions to the apps/mods being installed so yeah, that alone will keep them from working
also i see everything is going to /system, and in truth a lot of these are better suited for /data/app , but i guess thats your choice.
also, just a suggestion, but maybe just mount once data and system in the beginning rather than in each if/endif
and being this is so small feel free to just uncomment your set_perms at the end just do it all there (fix your permissions)
and not sure how you have the rest of the .zip set up, but you have your apps coming from lets say c/YouTube for example, and then going to /system
are these again in a folder like c/YouTube/app/youtube.apk ?
just wondering as you want to make sure its installed to /system/app or data/app
also not a huge deal but you may want to get rid of or at least change placement of those set_progress, i mean no biggy but when everything is completed you know
other than this all looks good! if after the changes things still dont work, post your new scripts as well as aroma log
best of luck!