I run the script as described, and everything goes fine. But, after a phone reboot, they go back to default values. What am I doing wrong? I have followed moons tutorial, but when I remove the oom references in 99tweaks, Script Manager wont let me update it. So the lines just go back into it. this is getting frustrating, I hope the great minds here can help me out.
Also, even with V6 and the build mash, I NEVER have more than 85mb of available memory. I don't have any widgets running at all.
Related
Disclaimer: not my work, and I'm still on Eclair so haven't tried it.
That said, this mod from the i9000 forums -- replacing the above /system/bin/ files with their most recent 2.3.3 equivalents -- should probably work on the Fascinate as well.
Anyone willing to guinea pig?
Could you elaborate
Sent from my SCH-I500 using XDA App
Based on the linked thread, it seems that there are Gingerbread versions of the aforementioned files which increase system responsiveness overall.
Just copied via Root Explorer. Reboot was quick, no problems so far.
eb01, modified stock\deodexed, no themes.
I saw this fugumod earlier and i think ill try it.
I also used root explorer to install. Seemed to work without any issues...not sure if it improved anything though.
whats the difference between flashing via cwm and copying thru root explorer
NERFed (a soft brick!) me on SuperClean 2.8 / EB01. Endless Samsung logo. Had to wipe/restore from backup. No harm done.
I went back to the original files. I didn't like the way this felt to me. Seemd more laggy than smooth.
Pushed the files with adb, and did a chmod 755 (will bootloop if you skip this step), rebooted.
Seems to pause when loading something new. Just a slight bit longer than normal. After it's in the memory, no pause. Did a back and forth test between the two sets of files... and couldn't really tell. I need some testing conditions that are known to bring out the difference, otherwise I'm just guessing.
Haven't gone over the logs with a fine toothed comb, but I didn't spot any new errors off the bat.
Update: no harm so far, but cant really tell the diffetence in my use either.
Sent from my SCH-I500 using XDA App
dont know what different... no harm.
maybe just stick with this modded a few days, then back to original
Here's an experience with rooting, lag fixes and voodoo (final item), in case this is useful for the various developers or others trying to use what the devs are producing....
Thank you to all the devs for so many choices - and some of the software needs error handling improvements
Okay, to start with while rooting device with Super1Click, there was an error (partition full) while "busybox" was being installed. SU worked, so i kept looking for stuff to fix the busybox install which was broken ("Seg faults" when trying any of the commands). "Busybox installer" from Market can install but no option to un-install. Ti Backup will go ahead and use its own included busybox...etc. Un-rooting via Super1Click did not even seem to remove the rooted-ness, let alone cleanup the broken busybox.
So now phone is running with a full /system partition and everyonce in a while it just freezes and only "hard" resetting (pullng out battery) can get it going again.
So I decided to delve further and maybe improve performance as I had read about on XDA (while poking around for the gTablet options). Decided to use TiBackup and save stuff first in case i mess up everything ( like i messed up avatar movie when i copied it off and back to SD card..). Of course, no busybox but thank yu Titanium for having the "problems" button and installing what you need elsewhere and working like software should. Okay now i have backups of everything done.
So now its rooted and backed up, so i try OCLF to get performance and of course ext2 tools & fix is not enabled because /system partition is full.
Back to cleaning up the "bloatware" (why cant the OEM/carrier make the partition bigger if they are going to add bloatware ?).
So after deleting a few things, now OCLF installs but fails towards the end - trying to 'mv ...playlogos1 to ...playlogosnow' (partition is read-only error) and does not 'catch' and undo itself like it generally does on other errors it runs into. Okay so now stuck with a partially completed OCLF and the menu system will not recognize the presence of fix and thus cant use the "undo" menu item.
But, thank you for another menu item which "restores" the old playogos file and suddenly lag fix can be undone...great, more reading on XDA, discover that Voodoo is the way to go, not unsupported OCLF.
btw - found the feature of sending off the logs on error pretty handy, i'm sure its not such a nice feature from your end unless you have an email filter setup for it.
Now to the topic of this post - OCLF undone, deleted OCLF ext2 partition file, fixed busybox by using busybox installer (no uninstall option available), read all the XDA threads...(nary a thread on /system partition full - doesn't anyone else run into this problem with all the stuff they do ?)
Downloaded SGS Kernel flasher, got Voodoo for Froyo KA6. Decided to go ahead and put clockwork mod and do a backup just in case...also saved kernel via SGS
Flashed Voodoo, great robot voice technique till it said "No space on parition" and 'abort' or something similar and finished booting (then i'd rather see a log brought up after the reboot is finished).
Downloaded "Voodoo Controls" from market and nice it can see that 3 partitions are converted, but /system is not BUT it says Voodoo sound is not supported by the kernel (so assume that was the stage to be done after the "abort" happened on system partition.
Deleted more system "wares" reluctantly, uncheck boxes in Voodoo control and reboot to remove ext4 conversion. check boxes and reboot and voila - now all 4 partitions are converted, but still sez no Voodoo sound supported kernel. ?? oops no sound fix stage executed if already installed...
Current Status:
Quadrant scores at 1436, not different than when only 3 partitions had been converted (941 on stock). Btw - Linpack scores haven't changed since it was stock (12.78~13.48).
Now sometimes it shows the cpu is running at 100Mhz or 400Mhz....used to always say 800Mhz when it was stock.
Voodoo Sound still not available in controls. /system is back to 1.6M free from 8.4M at height of removing bloatwares.
Next strategy:
Uncheck and convert back to RFS, then flash back saved original kernel using SGS (thank you for very nice program).
See about /system again - dont have anything left to remove though..wonder what has eaten up the space (clockwork mod ??)
Flash Voodoo kernel again and hopefully wll go through and get Voodoo sounds fixes this time OR just do Overstock+Voodoo ROM...
Anyone have suggestions / comments on the strategy i should pursue next ?
Main goal is to get a phone that wont freeze at random moments and secondary goal is to make it fast as the hardware allows it to go but staying close to stock software so the next update from T-mobile requires least (=no) effort.
Another ques - anyway that i can 'insitu' increase the /system partition size so i can put the bloatware back on and not have a partition that keeps going full when i fool around trying out different things...can it even be done in-situ that is?
I'm using the script in this thread to try and remove the bloatware from my SGS2 (my phone dropped from 55% battery life when I went to sleep last night, to empty when I woke up. I've reset battery stats as I only flashed recently, but thought this would be a good step as well). I've run the backup script and got a few file/directory could not be found errors, but it seemed to work ok. However, when I run the delete script, it starts and appears to delete the first couple of apps, then forces a restart of my phone suddenly. Have tried multiple times, both with a modified version of the script to leave the Digital Clock widget in tact, and also with the unaltered version the creator provided.
I'm running Lite'ning 4.1, I thought that maybe this script was only meant for the stock rom but it didn't say anything in the OP so I thought it should be OK. I tried to post in the thread for the script itself but haven't got enough posts to reply outside of this forum yet. If anyone could help it would be much appreciated.
Hello,
I installed the new 3.3.4 rom and I wanted to install the v6 SuperCharger and after following all the steps and rebooting I go into the script and it says that its weak, and that values dont match supercharge.
The only thing that i did not see on the instructions nor remember how to do is activate a script and set it to run at boot.
Anyone running the script on the new rom, please help me a little bit.
Electroniko said:
Hello,
I installed the new 3.3.4 rom and I wanted to install the v6 SuperCharger and after following all the steps and rebooting I go into the script and it says that its weak, and that values dont match supercharge.
The only thing that i did not see on the instructions nor remember how to do is activate a script and set it to run at boot.
Anyone running the script on the new rom, please help me a little bit.
Click to expand...
Click to collapse
is the script that runs on boot running on boot?
It does not seem like it is.
First make sure you have buisybox 1.18 or lower installed. Second load up script manager and and at the top hit "..." twice. Then hit menu and options and choose browse as root. Then select the data folder then choose 99supercharger. Check run as root and run at boot. For dx2 at least running eclipse 0.2.2 option 9 in supercharger runs it the best. Option 9 should be megaram with 512mb. There are two it should be the second one. Im running update 8 so im not sure which option it is anymore.
Also you mean you are running the ATRIX 2.3.4 right? If so has the audio problem been solved with that? That's the main thing I want to know with that rom since it has android 2.3.4 on it.
Sent from my DROID X2 using XDA App
well im not sure what you are running but make sure that either /system/etc/init.d is being run on boot
I followed the directions, but when I go into data there is no file 99etc... to run at boot.
Did you first run supercharger. Run it but don't reboot the x2. And make sure you are browsing as root. You choose that in the options of script manager. Also are you running buisy box with 1.18?
Sent from my DROID X2 using XDA App
running busybox 1.18.1
Tried it like four times, and no go.
do you have root?
Are you using script manager? Cause that just odd. Just to be sure you're going to "/data" as browsing as root in script manager and scrolling down to the end of that file and not choosing the other data folder to make it "/data/data" cause it should be there as long as you first ran v6 supercharger and chosen which ever option that 99supercharger script should have been made.
I say unsupercharge. Delete scriptmanager and reinstall it and then try again just to see id there was a glitch. If this doesn't help then your pretty much out of luck. But I thought navens. Mods where included in the rom so you shouldn't need it(could be wrong).
Sent from my DROID X2 using XDA App
Its weird because I had been able to run supercharger on eclipse, I will keep diging around to see what I can find.
Just a question... Isn't supercharger unnecessary for 2.3.3 and above?
Sent from my Droid X² Eclipse Rom + BNB Theme
I have the same problem, and no its not the users. I don't think it is working correctly. Or at least not placing the files where they are normally found.
if you run the 99supercharger script that is suppose to run at boot as root then rerun the "installer" script are the mem splits correct?
Versatile1 said:
Just a question... Isn't supercharger unnecessary for 2.3.3 and above?
Sent from my Droid X² Eclipse Rom + BNB Theme
Click to expand...
Click to collapse
its quite usefull just not so much for music on stock gb blur. it gives you a faster boot and screen transission but thats about it on blur.
on elcipse 0.2.2 if you use v6 supercharger (update8 option 9), 98kickasskernal safe and v6noop nearly got rid of all the music skips and pops. about three songs per 85 on my playlist skips or pops if im not doing anything other then listen to music and it will only skip once if its the first time i opened the internet and then runs fine. but the 3 songs are complete random. and sometimes it goes to 5 songs.
without them running this phone skips, pops on nearly every single song on my 85 song playlist (i have 2 gb of music on my phone this is just my most used playlist).
so it makes a difference just not much on blur as it does on eclipse.
I have found a good work around for those of you who may enjoy more usable space on your screen. With the screen the S4 comes with it only makes sense to use it. Only follow these steps after you are running on Hyperdrive ROM successfully (I am guessing this will work with other roms as long as Xposed Framework can be installed).
Background Work (no major changes yet)
1) Open the app Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Framework Installer
3) Click Install/Update
4) Select the tab 'modules' from the top
5) Check all the boxes you see (I had 3)
4) Click Reboot
Let's get started
1) Reopen Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Per App DPI Settings
3) Select Google Keyboard
4) Turn the switch to ON
5) Enter 160 for DPI, 100 for Font and check the box labeled 'xlarge res'
6) Click save and click yes.
7) Repeat steps 4-6 with the apps Swype and Samsung Keyboard
8) Make sure you followed the above steps then continue
9) Now find an app called Android System from the list and select it.
10) Enter 280 and don't change anything else (I don't know what you would be doing so I stayed away)
11) Click save and click NO.
12) Restart and enjoy.
I went back and changed System UI to 340 as I didn't like how small the notification bar became. Also recommending ExDialer as the stock keypad won't 'stretch' and lastly as a must, look into a good launcher. I am using NOVA Prime.
If you want to undo changes you can simply turn everything 'Off' and click Save and No. Then restart.
Hopefully this helps some!
If I am missing anything or if anyone wants to add more detail let me know! Side note: random but AOSP helper was installed on my device also allowing easy toggle from 3G to 4G with JuiceDefender...
Colton
Mods can you list this as a [HOWTO]... sorry left that out.
awesome.. .thank you!
OMG thank you for this, i has given up on how to do anything on it. I did not know how to use Xposed frameworks, this is what i needed, than you very much:good:
Has anyone tried changing the overall system DPI and then changing just the misbehaving Samsung applications back to stock (i.e., Contacts/Dialer, Camera)? I pretty much manually set all of my apps to between 320 and 340, but the Notification dropdown is way too big. (Email and Gmail both at 320 in order to become usable).
This made my launcher grid super tiny and the keyboard is unusable it is so small. I can imagine how some slight DPI adjustment could be good, but this is aweful!
that being said, I will use this method to adjust things how I would like them.
I'm glad it worked well for you guys but both of those changes made things worse for me. I put it back on stock and am very happy with it.
I'm running 320 DPI in my build prop. To fix the dialer I went into the per app DPI and changed the contacts app and phone app to stock 480 DPI and also the calculator app as well. They all run just like stock now no problems at all
Forgot to mention gallery as well
Sent from my SCH-I545 using xda premium
im using 360 in my build.prop. and have had no problems. only thing i had to fix was my market. which i used this market found here
http://forum.xda-developers.com/showthread.php?t=1839871
using the correct version of the one in my current rom(hyperdrive). Dont ask me why this works. But someone else said they tried it and it worked. so i did and it worked. Sometimes ive noticed it will all the sudden on reboot, change to a different version of the market. But that has only happened a couple of times. and usually it didnt matter(most apps still showed up like normal). But i dont know that this will work the same way for everyone since it seems to be a semi flakey method.
It works fine in HyperDrive RLS 4. Don't try to change the build.prop for the first boot, though. Let it boot once, then change it. Let's just say that the results were a hung device first.
I added clock back to 480 because there are issues with it.. The year view in Calendar is a bit off, but that's the only screen that doesn't work right... The Market works fine at this resolution (360). This is much easier than what I was doing before...
Now Touchwiz can be somewhat usable as it isn't huge gigantic text everywhere (even on the Tiny selection in Screen)
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
kcellb said:
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
Click to expand...
Click to collapse
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
jeffreycentex said:
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
Click to expand...
Click to collapse
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
colton22 said:
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
Click to expand...
Click to collapse
I had problems with the first two downloads. Then I was able to get one to work early this morning... Also note that it is supposed to be a wipe'd flash, so make sure you do the format data/cache 3 times, then format system... I generally do a flash of the rom first to make sure that there aren't problems, though, before I format system...
I only use 320, 360, and 480's as DPI's on the S4.
Your approach is the way I used to do, but I wanted everything smaller, so every time I installed a program, I changed it to 320/360.. But then I wanted 320/360 to be the overall and only make exceptions for the things that demand stock DPI.
Understood - I didnt wipe to flash as i never did before without an issue. I am downloading stock ODIN now as something is up with my data partition...? It hangs on every second+ boot from restore/install and will not even boot off an install. I will go to stock odin, root, recovery and then install. Also downloading a fresh copy of Hyperdrive RLS4... Thank you for the tips.
C22
Found a better way!
Okay so I am now on RLS 10.2.0...
Download some type of Root file manager... I paid for/use Root Explorer love it.
Navigate to /system and long press build.prop
Find the line that contains screen density =480 and change it to your desired DPI (I am using 280)
From there all apps/everything is changed to that dpi... some stock apps you will have to use xposed to change them back to 480 just to make it work because they show different resolutions horribly.
I followed these steps...
http://forum.xda-developers.com/showthread.php?t=2269483
works great! Enjoy.. Also on the Multi DPI stock app post, the only one that works with the Verizion phone is the Gallery S4 v2.zip file... The others I am trying to work with the dev on getting up and running for our phones.
Colton22
deleted
Thanks