Related
what about this on hero?
hyyp://forum.xda-developers.com/showthread.php?t=637419
cheers,
spania
pushed it, booted, logcat stops after a few seconds, then nothing for ten minutes...
For this to stand any chance of working you must be using a 2.1 ROM.
I pushed this to my hero running VANILLAIN 1.1 the phone does manage to boot up but I got a whole lot of force closes including (most unfortunately) the main phone software which continually FC'd and reloaded making the system very slow. Despite this, I managed to run linpack and got a return of over 3 mflops so the JIT is clearly running but untill the phone FC is solved clearly it is useless! This will have to be something one of the DEVs looks at. It would be worth others running 2.1 ROMS trying this out also.
I will continue to experiment!
Aleks
Still can't get this to work correctly. Vanillain loads correctly but com.android.phone stops working unexpectedly every time repeatedly. However I have managed to get 3.633 Mflops/s in Linpack which is a vast improvement on the standard benchmark! If the devs can implement this to work without the FC of the phone then we will have android 2.1 running very smoothly indeed!
Pushed it to VANILLAIN 1.1. Managed to get 3.5Mflops/s (Linpack) and 283 Total CPU Score (Benchmark).
I'm going to use this daily and see if I'm getting any problems. Working fine so far with no FC.
nhisyam said:
Pushed it to VANILLAIN 1.1. Managed to get 3.5Mflops/s (Linpack) and 283 Total CPU Score (Benchmark).
I'm going to use this daily and see if I'm getting any problems. Working fine so far with no FC.
Click to expand...
Click to collapse
sounds fantastic
what about the feeled speed(navigating and so on)?
I tried with kagudroid (1.2.2) but have many FC on principal apps and phone was useless... now i try with vanillain 1.1
nhisyam said:
Pushed it to VANILLAIN 1.1. Managed to get 3.5Mflops/s (Linpack) and 283 Total CPU Score (Benchmark).
I'm going to use this daily and see if I'm getting any problems. Working fine so far with no FC.
Click to expand...
Click to collapse
Hi.
How did you do it ? The long instruction from the thread, or did you just push it ??
Rgds Gtot
Yeah, with vanillain 1.1 works very well
With linpack :
before : 2.102 Mflops/s
after : 3.3 or 3.4 Mflops/s
Really a nice performance boost and no fc or crash.
Follow the instruction of topic linked by spania.
Hi @all,
I just flashed the Vanillain 1.1 and tried to enable jit.
The problem I have is, that it does not found su like its said in the jit installation tutorial. But the file exists in the /system/bin.
Do I have to use absolute paths or is there something wrong in my system?
Thanks
Just tried it on CKDroid 1.6b.
With Root Explorer I simply replaced the libdvm.so and gave the file the same permissions as the original file.
Reboot, then the figures :
Before : 2.195 Mflop, 2.47s
After : 3.265 Mflop, 1.68s
Did not extensive tests, but i could not see overall speed improvement. Maybe should I test further.
DarkAdrien said:
Just tried it on CKDroid 1.6b.
With Root Explorer I simply replaced the libdvm.so and gave the file the same permissions as the original file.
Reboot, then the figures :
Before : 2.195 Mflop, 2.47s
After : 3.265 Mflop, 1.68s
Did not extensive tests, but i could not see overall speed improvement. Maybe should I test further.
Click to expand...
Click to collapse
I have done exactly the same on my Hero running Villain 3.0. When the phone has rebooted, everything starts up right, and i can see it receives new messages, but i can't unlock the lockscreen. It looks like the screen just freezes.
Any ideas ?
Gtot
Gtot said:
I have done exactly the same on my Hero running Villain 3.0. When the phone has rebooted, everything starts up right, and i can see it receives new messages, but i can't unlock the lockscreen. It looks like the screen just freezes.
Any ideas ?
Gtot
Click to expand...
Click to collapse
Update: After some reboots, i finally got in. It looks like everything works, except for sliding between homescreens (Sense FC). Benchmarking went from 145 to 278 and linpack went from 2.28 to 3.38 BUT i can't feel any difference.
Gtot
Well mine is very stable and has gone from 2.2 to 3.2. However it isn't noticeable faster to use, will see after more testing!
Lox posted this in his twitter account:
KaguDroid with JIT alpha:
4shared.com/file/229311127/83766b55/KaguDroid-123-jit-alpha.html
You have to put your widgets again
tomfreay said:
Well mine is very stable and has gone from 2.2 to 3.2. However it isn't noticeable faster to use, will see after more testing!
Click to expand...
Click to collapse
Check internet browsing. blazing fast for me. Overall still a bit of imrpovement in application starting and running, but of course not in 3D graphics. But this is ovious.
JIT accelerates execution of code. internet browsing benefits a lot from my experience.
i have over 3mflops but in 25+ seconds no jit,2.1 build any idea?
P!L!F said:
i have over 3mflops but in 25+ seconds no jit,2.1 build any idea?
Click to expand...
Click to collapse
The new version of linpack has changed the measurement from a total of 200x200 to 500x500(don't know exactly what these numbers represent,sorry,but they are some kind of calculations I think).They did that to increase the precision in CPU processing power measurement because newer devices with powerful CPUs got inaccurate results in like 0,15 seconds.
Hope I helped!
oXbench is alot better tbh
jit
tks allot guys ,i was just wondering...my phone is very responsive and it was jut a question of timing...25-30+ seconds seeing 1.4,1.3 ......
About a month ago some of you may remember my posts that I was working on a kernel. Here is my first public release. The whole thing works at about 95% or so.
==============
The advantages I notice while using it besides the normal issues associated with Eclair are as follows:
1. Memory management has changed (has good and bad effects) Good: when you fly through 45 websites the browser does not crash as it eats memory. Bad: when you blow through 45 websites the browser will hang (easy fix hit home, and use app killer to free memory from apps you are not using) (Personally I like not losing my place as I get lost in the web, it also will prevent apps from dieing in the background when you are using multiple apps at the same time, if memory gets low enough the OS WILL KILL the offending apps). I personally found Eclair for Fascinate to handle memory available worse than this kernel, and I find this kernel handles memory more like Eclair on the Moto Droid did, and the Moto Droid had far less memory to work with.
2. UI has a faster response vs stock kernels, the kernel is also running AS scheduling vs BFQ but I updated BFQ to run as well if you want to revert.
3. Internet Connectivity appears to be faster with those apps that properly use the API. Web browsing, CheezeBurger, youtube etc all load content faster (efficiently? / Maybe related to memory management?)
Want something added to this list? Post your requests, just please be reasonable If I like the idea I will try to implement it. Remember this is for kernel features not system ROM modifications.
==============
Issues to fix (ToDo List, I am working to fix these issues / Updated 01/30/11):
1. Investigate and address bluetooth connection issues [ Confirmed that this issue does not affect everyone / or all bluetooth devices ]
2. Investigate and address remaining data connection issues (Orbot activates and test show as using tor on normal websites, tor addresses fail to connect to servers, also Orbot is unable to de-activate [Confirmed]
3. Investigate and address remaining camera crash issues [ Please zip and send in logs from /proc/kmsg, specify if you used the volume control zoom or pinch to zoom ]
4. Improve on touchscreen timing for quick flicks on the first attempt without burning up processor time.
5. Investigate and fix stutter/crash on camera zoom followed by attempt to take photo.
Notice something that should be in this list? Please make a post describing your issue, remember to include the kernel version/rom and the steps you performed to reproduce the issue.
==============
For those doubting, this IS 2.6.29.6, I personally merged the code myself, IT IS NOT 100% COMPLETE. Some drivers still need merging, and the V4L2 code is not completely converted because Fascinate uses different (updated?) V4L code (compare Fascinate's Eclair to Eclair on AOSP)
If anyone wants to help bug hunt I will forever be grateful. I would like to finish squashing bugs in this in the next 2 weeks as I really want to attempt to work on a Froyo for Fascinate. Even if it uses Eclair code to run the only RIL code we have.
I also semi-blindly fixed about 50-100 coding problems in the Eclair Kernel, varied from not returning data from a function that should have, simple void definitions that were returning when they had no data to return and no function collected it. Correcting order of operations in if statements. Declaring data types that were vague (unsigned vs signed). You will notice it compiles a lot cleaner...attempting to fix the camera code nearly kills the camera completely, I am thinking the broken code dumps variables by accident that the corrected code does not.
Edit: I wanted to share a few things every dev (some of it specific to kernels) should remember when nights are long and sleep is a half world away.
1) Keep a backup of your most recent WORKING work safe, because it is too easy to....uh oh *[email protected]$
2) If you edit the config file, remember to make clean and make mrproper before you make, otherwise your still on your original config file (a copy of the one you actually edit .config)
3) Do not put comments to the right of options in the kernel config file...apparently they will be discarded (the entire option line, not the comment, you'll see it in your compile error message logs).
4) Automate the mundane, I have a nice build environment setup, I type one line and it will make a brand new kernel from scratch (I'll be sharing that later, keep an eye on this post)
5) Work with what you have, don't wait for someone else too. Somewhere, someone is working on something better, and tomorrow it will be out.
6) Laugh...at something...anything because lets face it, you make better decisions in a good mood, in a bad mood...entire trees (code) die, either from rm -Rf /work/crap//* or a sledgehammer to the motherboard. Which brings us back to the first thing to remember, where did you put that backup...different drive I hope?
Attached is a working kernel, it will have issues using DI01 (such as no vibrations), it works great with DJ05 ROMS and maybe DL09 system roms. At this time I can not recommend a DL09 system rom with this kernel, during my initial tests it appears to drop GPS and cell data connectivity frequently resulting in having to relock on GPS satillites, and losing data connections in networked applications.
I highly recommend the setup I am running, DL09 Radio, Son Of Skywalker Blackhole v2.4 and this kernel (if you can handle the few bugs that is, it is beta).
Please feel free to post bug reports please include detailed information about the issues, I AM NOT FIXING APP PROBLEMS. Please remember to only report kernel issues and information specific to the kernel crash. If an app crashes on other kernels and not just this one please do not submit a report. This kernel is NOT setup for debug info, I will post one setup with debug turned on later. Right now, play around with it and report your results! Enjoy and have a great time :-D
GITHUB: https://github.com/sirgatez/
Edit 1: I thought I would mention that I originally started with the JT1134 kernel source from late Nov. - mid Dec. and the Samsung Fascinate stock source (from Samsung's Opensource website) then I merged in source from 2.6.29.6 from www.kernel.org and from Cyanogen's 2.6.29.6 Eclair kernel. I stopped on 2.6.29.6 instead of moving higher because of 1 reason, once you step in to 2.6.30 there are major driver changes requiring a lot of double verification and back trekking....In a few words, it is lots and lots of work, and I think that jumping from 2.6.29 to 2.6.29.6 will help transition to the 2.6.30 (Froyo?) series of kernels because then the majority of the work is in restructuring the driver code (which would likely best be done backwards, from the system .h files, to the .c handlers, down to the device drivers) from Samsung to match that in the stock 2.6.30 set. Complexity will be reduced by a measurable amount
Notes 1: Samsung's Android code has some significant differences under the hood from AOSP Android code, I have not sorted it all out yet, but it is possible that without an AOSP stock system that a full kernel update to the current AOSP code may not be possible. There is a built in virtual CD driver for what appears to be hosting the ISO built into the base Samsung system image, I have not opened the image yet but it appears to perhaps be drivers? Also it does not sleep the SD card like standard AOSP does, attempts to do so will disable the SD card from use with no ability to remount without a battery pull. (This is in 3 of 4 lines of code that AOSP had that must be commented out from the Samsung kernel for this SD issue to be prevented). For those wanting it, CIFS and NFS are compiled modules in this kernel. The current kernel is not over-clocked, and does not have voodoo. It does support both with a kernel configuration edit required for voodoo with the proper init scripts, and over-clocking requires changing just a few files and recompiling, I did neither as I wanted a true comparison to compare changes against the original stock kernel. The kernel does have the BLN notification code built in. BLN, Voodoo, and Over-clocking code are not my own creation they are pulled from their respective creators.
REMOVED ALL OLDER KERNEL INFORMATION
Update RC3 v2.2.4-VooDoo/NoVooDoo: This is a minor/major (depending who you ask) bug fix to adjust the processor throttles. Think I've got it too set to a good sweet spot now, the peaks are steep and a little harder to climb but the falls are also quicker. After turning it my phone on with it last night and about 2 hours of use I went to sleep, wake up a couple times to silence various alarms (I wake to wake up, but I want to sleep a little more, can't I do both?), and these are the numbers that setcpu reports for time in state:
1.2Ghz = 0 (Had the phone thottled to 1.0Ghz for this test, but with 1.2 on it only uses it when it needs it, might could leave it on?
1.0Ghz = 164978 (Not such a big a number as before)
0.8Ghz = 292008 (much more reasonable than before, could be a little lower)
0.6Ghz = 117672
0.4Ghz = 114250
0.2Ghz = 104715
0.1Ghz = 2965562 (This is what I was aiming for proportionally for 0.1Ghz)
Remember these times are mostly from idling, the idea was to reduce clockspeed when not in use to save some juice. The phone might take a moment to wake up from idle, but once it is going you shouldn't feel hardly any difference between this and RC2. Bootup clockspeeds from your first 3-4 minutes will almost always remain in the top tier due to applications still loading, media scanner running, etc.
Update v2.2.4-VooDoo/NoVooDoo: This is a major fix kicking us out of RC status and into actual release. Now for the menu, prepare your appetite, for the appetizer we'll be serving a much demanded voodoo color fix, and voodoo sound fixes. Followed by a main coarse of throttle tweaks, throttle shift updates (these are new they decide what the next cpu speed will be when a throttle is exceeded up or down, every kernel to my knowledge including my last used the default for a 5 slot kernel, here is a true 8 slot), and for desert a reduction in logged touch screen data from the touch screen, and an additional surprise to everyone, a reduced cpu load when using the touch screen!
Apparently the touch screen had authority to force the cpu into any slot it wants, it defaulted to slot 1 (which was 1.0Ghz for Blazed, now it's 1.2Ghz). The result of which meant that if you pressed the touch screen your cpu load catapulted up to 1Ghz for as long as you touched it even if you only held your finger in one place with no apps open. I have changed that to only go to 400Mhz, we'll see how this goes, if anything we might bump it to 600Mhz, so far besides a slightly slower response when first touch my touchscreen after leaving it alone for a long period it doesn't effect normal use from one app to another. If your processor is already at 400Mhz or higher it will not up it further. You will find this kernel will likely end up being the most battery conscious you have ever seen, once you get things moving the speed follows. If you find this kernel has a slower response than you feel it needs let me know, because when I fixed the touch screen from blasting the cpu load through the roof, it through off my throttle settings some, now they may be too conservative, report back and we'll fix them if it is a problem. Ah yes, please don't forget to tip your waiter if you enjoyed the service... [ REMOVED - Aggressive throttles not configured for use without aggressive touchscreen driver ]
Update v2.2.4R2-VooDoo/NoVooDoo: This is a minor fix to correct the choppy feeling that v2.2.4 had, the choppiness was due to aggressive throttles to fight off the excessive high speeds the touch screen forced on. This should correct those issues. Unless I have another bugfix for 2.2.4, I will be adding 1.1Ghz in the next release making it a total of 9 slots. The higher speeds still need some tweaking, if your looking to hit benchmarks please set min and max to the speed you are testing, otherwise the throttle is trying to save you power that doesn't need to be used. But for everyday use, these settings should be good
Update v2.2.5-VooDoo/NoVooDoo: Voodoo sound is still broken, anyone have the patched files I could compare to? The screen should be about 15% dimmer than it usually is on the lowest setting (and scaled up from there to 100% at max), I found the dimmest setting just too bright in the dark for my self, and hopefully it will help me save a little extra juice because I usually use my phone on the lowest brightness setting anyway. Major fix to throttles, now they are better tailored to this many slots. Slots updated to 9, 100Mhz, 200Mhz, 400Mhz, 600Mhz, 800Mhz, 1.0Ghz, 1.1Ghz, 1.2Ghz, and 1.3Ghz. Increased processor voltages (my ultra low voltage was about 25uv lower in most slots than everyone else who has a uv kernel...I was a little too aggressive on that one). Update bluetooth driver, it should remain connected now, could someone please verify this? Stability has improved alot with the higher voltages and better handling of throttling for different situations. Several other pieces of hardware discover that have authority to play with processor. I capped highest touch screen processor forced at 600Mhz (the higher I set it the faster your battery goes, default stock is 1Ghz), and all other hardware at 1Ghz (not very many requests, but this is where rouge 1.2 use came from). If you had issues before except for camera zoom or data connectivity in apps give Blazed another try. The slightly higher voltages should improve a lot of the random issues people were having. You may see an improvement in cellular signal now, 1.3Ghz is also stable, but I wouldn't run it all day either due to heat generated etc...Well I hope everyone enjoys, this should be the best release of Blazed Yet!
Update v2.2.6-VooDoo/NoVooDoo: This is a major fix for cellular signal issues many people have been having, the issue again was related to timing and the kernel modules not waiting long enough for the modem to respond before proceeding with action resulting in errors that caused a disconnect or forced a modem reset (requiring a phone reset to regain signal). I found waiting too long only slowed the entire phone down, so I opted to go with nanosecond wait times, waits that short however are active and will warm the phone up some, please report back if it becomes an issue as I am looking for a better wait device than udelay, preferable more like sleep that doesn't keep the processor busy. There is some performance stutter in the phone on the high end of internet connectivity speeds, but your not going to be losing your connection either, I'll continue to attempt to improve on this issue later on. [ REMOVED - Timing further improved in v2.2.7 ]
Update v2.2.7-VooDoo/NoVooDoo: This is a minor for that makes a major difference. Improved timing for communication with GPIO/modem this should be the end of the majority of network connection issues. It was entirely a mailman problem, put package in box, check for package, package still there? no=do other stuff/yes=...wait,repeat at package still there?, etc. The fix is put package in mailbox, wait long, check is package still there? no=do other stuff,yes=short wait and check again...Hope this helps alot of you out, I am aware the touch screen is a little slow to respond and I will be looking into that issue. This little fix should also improve usable speed over v2.2.6 because the waits are better timed.
Update v2.2.8-VooDoo/NoVooDoo: Timing is everything with electronics and this post...as promised today before 11:59pm is v2.2.8. Working Voodoo Sound v4, updates to the dpram/dpio communications again improving connection stability, if you lose your connections please report back (permanent loss requiring a restart only, fluctuations are different issue). Throttles set a little more aggressive about 5% so (helps ease on light loads), stepped up the first throttle jump from 100mhz to 400mhz (touch screen snaps back now). Dropped the 1Ghz permission for misc hardware to 400mhz if you have issues let me know, touch screen retains it's 600mhz permissions. Also screen brightness is reducible to gamma 1 brightness 10, typically reserved for battery about to fail status (I found the lowest setting just too dang bright). Enjoy everyone! I've been hammering away on this since 7am this morning and only had voodoo sound working about 9am. Thanks to JT1134 for his prebuilt kernel containing voodoo sound v2 working, adding v3 & v4 was a snap after that. Please report if you have any issues with it and remember you MUST be using the new voodoo sound app from the market.
Update v2.2.8R2-VooDoo/NoVooDoo: Another dpram timing adjustment (will lower your upload speed a little but will be more stable in operation, down speeds should be around 200KB down 44KB up on a good connection). Adjusted 1.1Ghz dividers per nemesis (not sure that it looks right, appears to get better benchmarks than 1.2 now will follow up on it). Made throttles a little more aggressive, 2.2.8 looked all over the place and having difficulty controlling processor use.
Update v2.3.0-VooDoo/NoVooDoo: Alot of work went into fixing dpram.c and multipdp.c it seems they were incompatible from the very beginning resulting in alot of ril issues and stability problems not just on my kernel but others as well, especially with nonstandard clocks and multiple slot kernel. I also added a fix to the framebuffer courtesy of JT1134 that has long since been overdue but a rare bug most probably have never seen. I fixed all the timing in dpram.c I also fixed the non-matching buffer sizes for multipdp and dpram (they talked to each other using different sized buffers...come on?!) There are still some bluetooth compatibility problems and the camera may still crash on zoomed photo, but I'd say it's 100% out of Beta! Enjoy! :-D I will be working on a Froyo kernel so stay tuned folks!
Update v2.3.0R2-VooDoo/NoVooDoo: Minor fix to help prevent dpram crash by handling and disposing of invalid commands sent to dpram, should fix seeming random lockup. [ Edit: corrected incorrect version numbers in original v2.3.0 series xda posts, thanks to s44 who caught the error, this does not affect kernel downloads, this were named correctly ]
Update v2.3.1-VooDoo/NoVooDoo: I reduced the delays in the ce147 camera driver, repairing the dpram driver resolve many of the seemingly random issues that had once plagued Blazed. Also a special treat for all you Blazed users, a new voodoo sound option that I have named "HEADPHONE_STICK" essentially the option when enabled (per boot) will force all audio directed to the external speaker to be instead directed to the headphone jack if the headphone jack has a plug in it. I find it excellent for not disturbing others around me with notifications when I would rather the phone be silent but I have headphones plugged in. Also excellent for using that awesome amp you have in combination withr you fascinate to wake you up in the morning. I will be contacting the maker of the Voodoo sound app in the market to get this option added to his application for quick and easy access. Also a major rework in the way kernel modules are loaded, all modules non-essential to booting are now stored in /system/kmodules. So if you reflash your system folder reflash your kernel or it may not boot, a quick browse will reveal what modules are kept there, I have more readily compiled and will release a separate "modules only" update.zip for those interested. By moving the modules it will allow for more options that are only available for including in the kernel boot image.
Update v2.3.1R2-VooDoo/NoVooDoo: Reverted some of the CE147 delay changes, reducing all of them caused some minor camera instabilities. EXT3/EXT4 moved back into the kernel, for some reason even with it's depends loaded ext4 doesn't load correctly as a module (resulted in broken boot on voodoo, now fixed). Also You MUST USE RED CLOCKWORKMOD TO FLASH IF USING VOODOO, you may use green clockwork only if Voodoo is NOT enabled due to the fact that some modules required for bootup are now stored on the system partition and if your using Voodoo only red clockworkmod has access to it. Also if you flash a different system or restore a backup you must reflash the kernel to ensure your modules are up to date. Also is a new file KMODULES-FULL contains all of the modules I have been compiling for Blazed thus far, several nifty ones but I have not setup any of the configs to use them, anyone versed in Linux command line can utilize them or setup scripts to use them, have a look inside the zip too see what there is to play with, request and I will add more if the module could prove useful to others. Several of the modules in FULL are also in the Kernel due to being required for startup redundancy (such as the 3D video/LCD drivers etc, which without a Android system folder, Android won't boot, nor will it boot without these modules so system seemed like a reasonable place to store them. The kernel/initramfs file is less than 6MB with Voodoo due to moving these modules to the system folder. I plan to add ClockworkMOD as soon as I have time to test it, then Blazed will also work for Recovery.
The Great Voodoo Debate: I have also been benchmarking Blazed against stock, to determine the difference Voodoo has on the kernel, so far it would appear Blazed has modifications either in the file system handling or the manipulation layers that are nearly equal to negating the speed lost to RFS's use before Voodoo or EXT4 is even brought into the equation. Just compare Stock vs Blazed (novoodoo) using 'RL Benchmarks SQLite Performance" from the market. A difference of 33.246 seconds in favor of Blazed, my preliminary results are (124.944 Seconds Blazed-NoVoodoo) (158.19 Seconds Stock) using the same exact system install less than 20 minutes apart between boots, with over 300 applications installed and several running like any other day. Based on this alone I find Quadrant is at least partially flawed at measuring proper I/O transfer timing, and I would NOT rely on it for an accurate benchmark in regards to I/O at this time until the issue is resolved by the Quadrant team. Voodoo does not produce the outlandish high scores that Quadrant makes out that it does, and Blazed is plenty fast in I/O even with RFS in use as shown by these preliminary results that any one of you can verify on your own using the "RL Benchmarks SQLite Performance" application, Voodoo does improve transfer compared to RFS in my tests but I am still putting together the results on Blazed NoVoodoo vs Blazed Voodoo. But as far as a 1800+ or 2000 score, so far my results say it just doesn't look realistic...sorry guys. On the flip side, if there is an error in my kernel causing a misread on the score you guys are welcome to help me find it and I will push the correction, but right now it looks like the issue is in how Quadrant measures I/O time, and I think non-atomic disk writes are the reason for the high scores, theoretically they would return claiming data is written to disk almost immediately when in reality it is still in memory and the kernel will write it to the disk at later time without the write time being considered as part of the benchmark (Google: write-caching, also known for providing significant performance improvements over atomic-writes).
If you appreciate Blazed and enjoy using it, please consider making a donation. Thank you for trying it out and have fun!
My initial impression after playing around with it for 15 minutes:
Seems to have given my phone new life/snappiness back that it had when I first installed super dark rom and stupidfast 1.54. My phone seemed to be bogging down lately. The internet definitely feels quicker too.
So far so good!
will try, thank you for the release.
Great work!
Sent from my Galaxy-S Fascinate
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Great work, the kernel seems to have given new life to my test fascinate! ADB does however appear to be dead (I got error device not found every time I tried to connect) Other than that I have no complaints, keep up the good work
That is very odd, as I have not had any issues using adb. Please reload your drivers to be safe and double check debug mode has not accidently become disabled. I wired up my fascinate just now and confirmed that ADB is working. (It was invaluable in working with the camera crashes). Also it maybe related to a conflict in the system rom vs the kernel. I personally have not have any issues with DI01 Fascinate stock, and everything worked great using DL09 radio, DJ05 system from SonOfSkywalker (BlackHole 2.4). Right now I am running DL09 Radio, DL09 System Rom from SonOfSkywalker v3, and my kernel from this post, thus far no issues. I am using Ubuntu v9.04 to test right now, and not windows to confirm that ADB is working. I will check on windows later today when I have a chance.
anyone else having an issue with bluetooth? It says "Turning On" but does not turn it on just reverts back to "off" status.
I still have DJ05 modem and on blackhole 2.3 something but updated market and swype maunally.
Camera force closes when you go to zoom in.
Sent from my SCH-I500 using XDA App
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
wizang said:
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
Click to expand...
Click to collapse
Yes, you MUST disable voodoo before using this kernel. I will put together a voodoo and OC flavor of this for those interested later. As of now I have only been working with non-OC and non-Voodoo in this kernel to gauge how the work changed the experience.
Edit: Oh yes, it uses the default partition scheme. It is a goal of mine to eventually change the formats of partitions (similar to voodoo) but keep the layout, it is my thought that doing so provides the largest window of compatibility between stock Samsung/VZW Roms and custom Roms. With a proper recovery, the change could be performed and backups and restores would work no matter the format of the internal media as the layout remains the same.
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yea my phone is not recognized by the computer either, even after a restart.
Naturally I double checked usb debugging and the drivers (adb connected to my white fascinate just fine and I made a jump back to Geeknik's test kernel to double check that something hadn't died in ole blacky and it registered there as well) I wonder if its just this fascinate (as it has had a laundry list of its own issues). This phone is running Superclean DJ05 completely stock and was fresh off a complete wipe and restore
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can confirm that I am unable to access the phone via Samsung's drivers using Windows XP. [Added this too my list]
Wireless tether does work in case you need it, that is why I hadn't noticed this issue. Good catch!
I really like the transparency of your work. It's refreshing to actually read about the process you're working on and the way you explain it definitely makes seems like you have a good grasp of what's going on. I can never quite tell with the other devs. Anyway good luck!
FDro said:
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Click to expand...
Click to collapse
Agreed! If they can get GB running nobody is going to be interested in Eclair or Froyo.
I like the sound of this kernel. Imma flash it when i get home. Looking forward to seeing the OC version
SCH I500 Super Clean v.9 DJ05 Revolution 3.6 OTB oc'd lv1200 Voodoo5
2 SirGatez.
It sounds like you are pushing towards performance optimizations. Have you checked supidfast sources? I tried it before geeknik left and it was significantly faster then stock. May be you can get something from him.
I really appreciate what devs do here, cool stuff! However I do not understand why that much talent spend in vain... Every developer has his own build, mods and bug fixes. Is this real open source spirit to have so many versions? Looks like brownian motion to me.
Now, you can say that I'm free to do it on my own etc, as other devs pointed here. But, full fledged development it not for everybody by various reasons. I hope it is obvious. Would be nice to see some consolidated development! Then it will be much more easy for mere mortal to contribute to that product. We all have same phone!
Once again I do not want to upset anybody.
bendbowden said:
Great work!
Sent from my Galaxy-S Fascinate
Click to expand...
Click to collapse
Also, great write up! I will report back if I notice any bugs not mentioned above.
[?] [Script] V6 SuperCharger !! HTK & BulletProof Launchers! FIX MEMORY FOR ALL ANDRO
so far nobody has mentioned this, not even sure how many people look in this section of the forums, but here goes.
anyone out there willing to test and port this over for fascinate?
http://forum.xda-developers.com/showthread.php?t=991276
general info:
Main points:
- CUST-OOMIZER! Use your settings without Autokiller Memory Optimizer or Auto Memory Manager!
- For newer phones with lots of ram, use the 3rd slot to set how much free ram you want.
- If you have /system/etc/rootfs/init.mapphone_umts.rc, it makes a backup and edits that single file. This is nice and tidy.
... Thank to kabaldan for pointing out the importance of certain things.
- Most Custom ROMs - If you have a /system/etc/init.d folder, it creates 99SuperCharger in there and edits /data/local.prop (20 entries added for adjusting priorities and groupings). You shouldn't need to configure anything else.
- Stock ROMs - If you have neither, it creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop (20 entries added)
Note: For some reason, the minfree levels do not stick on some Custom ROMs. I don't know why this is. Maybe a bug in GingerBread?
........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"
In case of any error, you will find a related help file in the root of your SD card.
So... I think this covers ANY Android ROM
It also determines if you're using Script Manager and gives appropriate information/tips/help files depending on what other factors are present.
The above is really ALL YOU NEED TO KNOW.
The V6 SuperCharger script does everything!
Anything below is extra info!
It's just a single file... 806 lines (807 if you count the blank line at the end LOL)
So... What's it do?
It makes your phone FAST... super snappy with better multitasking!
If you read between the red lines below (parts 1-3), you'll see that at first it was only about minfrees and launcher redraw.
But after installing GingerBread, I saw that it needed more work than Froyo LOL.
Groupings were ALL MESSED UP and made NO SENSE to me whatsoever...
So I figured out how to group them more like CM6 (Froyo) but that still wasn't good enough...
I further rearranged the OOM Groupings and Priorites and lowmemorykiller values for a...
COMPLETE MEMORY MANAGEMENT FIX!
That's basically what this is
Faster than ever, no launcher redraws, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
Upon installation, V6 SuperCharger will first clean up any previous supercharging so none of your files get cluttered.
But if you toggle between Hard To Kill and BulletProof launchers, the memory adjustments aren't affected.
So you can leave your minfrees at stock/default settings and apply the Hard To Kill Launcher and still get the OOM Grouping/Priority fixes.
So if you love your ROMs memory settings, just try the HTK Launcher/OOM Fix... you won't regret it
Ah, I used this script on my wife's Eris, and it did fix the speed a tad, no clue how it would react on an already fast phone, but hell, any little bit helps.
Izeltokatl said:
so far nobody has mentioned this, not even sure how many people look in this section of the forums, but here goes.
anyone out there willing to test and port this over for fascinate?
http://forum.xda-developers.com/showthread.php?t=991276
general info:
Main points:
- CUST-OOMIZER! Use your settings without Autokiller Memory Optimizer or Auto Memory Manager!
- For newer phones with lots of ram, use the 3rd slot to set how much free ram you want.
- If you have /system/etc/rootfs/init.mapphone_umts.rc, it makes a backup and edits that single file. This is nice and tidy.
... Thank to kabaldan for pointing out the importance of certain things.
- Most Custom ROMs - If you have a /system/etc/init.d folder, it creates 99SuperCharger in there and edits /data/local.prop (20 entries added for adjusting priorities and groupings). You shouldn't need to configure anything else.
- Stock ROMs - If you have neither, it creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop (20 entries added)
Note: For some reason, the minfree levels do not stick on some Custom ROMs. I don't know why this is. Maybe a bug in GingerBread?
........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"
In case of any error, you will find a related help file in the root of your SD card.
So... I think this covers ANY Android ROM
It also determines if you're using Script Manager and gives appropriate information/tips/help files depending on what other factors are present.
The above is really ALL YOU NEED TO KNOW.
The V6 SuperCharger script does everything!
Anything below is extra info!
It's just a single file... 806 lines (807 if you count the blank line at the end LOL)
So... What's it do?
It makes your phone FAST... super snappy with better multitasking!
If you read between the red lines below (parts 1-3), you'll see that at first it was only about minfrees and launcher redraw.
But after installing GingerBread, I saw that it needed more work than Froyo LOL.
Groupings were ALL MESSED UP and made NO SENSE to me whatsoever...
So I figured out how to group them more like CM6 (Froyo) but that still wasn't good enough...
I further rearranged the OOM Groupings and Priorites and lowmemorykiller values for a...
COMPLETE MEMORY MANAGEMENT FIX!
That's basically what this is
Faster than ever, no launcher redraws, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
Upon installation, V6 SuperCharger will first clean up any previous supercharging so none of your files get cluttered.
But if you toggle between Hard To Kill and BulletProof launchers, the memory adjustments aren't affected.
So you can leave your minfrees at stock/default settings and apply the Hard To Kill Launcher and still get the OOM Grouping/Priority fixes.
So if you love your ROMs memory settings, just try the HTK Launcher/OOM Fix... you won't regret it
Click to expand...
Click to collapse
I don't think this will work with the fascinate "If you have /system/etc/rootfs/init.mapphone_umts.rc"... the fascinate is CDMA. This will only work with AT&T or T-mobile as they are UMTS
vudiff said:
I don't think this will work with the fascinate "If you have /system/etc/rootfs/init.mapphone_umts.rc"... the fascinate is CDMA. This will only work with AT&T or T-mobile as they are UMTS
Click to expand...
Click to collapse
but it does work on the HTC Eris, which is on the Verizon network??
http://forum.xda-developers.com/showpost.php?p=11178955&postcount=2
vudiff said:
I don't think this will work with the fascinate "If you have /system/etc/rootfs/init.mapphone_umts.rc"... the fascinate is CDMA. This will only work with AT&T or T-mobile as they are UMTS
Click to expand...
Click to collapse
and if you have an init.d folder and if not it uses data folder.
It won't work on ipods tho
Izeltokatl said:
but it does work on the HTC Eris, which is on the Verizon network??
http://forum.xda-developers.com/showpost.php?p=11178955&postcount=2
Click to expand...
Click to collapse
Yes it is on verizon's network. I'm guessing that file isn't doing anything on CDMA phones.
I'm not a dev but I do know my networks. I work for Alcatel-Lucent in which we translate & make the cell cabinet,towers, & customer networks communicate. We are the people that brought you verizons 3g & LTE technology. Currently working on AT&T's UMTS & LTE networks. Yes i am the inside inside man. We provide the Base Station and most routers and make them communicate for the providers... Sprint, verizon/alltel, nTelos, cricket, metroPCS, etc...
http://www.youtube.com/watch?v=7V74huEaaf4
Ya but can you read instructions?
And what's that got to do with oom groupings, priorities, minfrees home launcher and androids lowmemorykiller?
Sent from my Milestone Powered by my V6 SuperCharger
zeppelinrox said:
Ya but can you read instructions?
And what's that got to do with oom groupings, priorities, minfrees home launcher and androids lowmemorykiller?
Sent from my Milestone Powered by my V6 SuperCharger
Click to expand...
Click to collapse
Wow... chill out dude. I saw umts at the end of the file and simply was just saying that these phones are cdma. I already said I'm not a dev. Comments like yours make people not even want to comment. I'm not new to roms, rooting, etc... I started out with the original droid, then D2 and I've had the fascinate ever since it came out. Rooted & started out with superclean when it became available. Geeze
Yes well in post 5 I pointed out that it also looks for the init.d folder and if not an alternative method by using the data folder.
Has nothing to do with networks.
It has to do with which file or method is used to implement the tweaks depending on what options are available.
zeppelinrox said:
Yes well in post 5 I pointed out that it also looks for the init.d folder and if not an alternative method by using the data folder.
Has nothing to do with networks.
It has to do with which file or method is used to implement the tweaks depending on what options are available.
Click to expand...
Click to collapse
OK got ya. I didn't mean to start an argument! Sorry that I misunderstood. I learned something new today... and thank you for breaking it down for me
Ah that's ok...
Btw... cool job lol
Sent from my Milestone Powered by my V6 SuperCharger
Yeah I tried this on a friends Fascinate and it dropped dead, wouldnt boot up.
Had to Odin up and restore back to stock.
I noticed my friends swype keyboard would lag even after restore back to stock.
thus the reason to try this script in the first place.The fasciante is decent lil bugger.
Its too bad I sing its praises on Evo thought, it really kicks butt.
im using this right now on my fascinate running miui 1.9.9 and its working flawlessly... three 3g tweak also works great. thanks zeppelinrox
It works with the fascinate, I use it constantly, and it doesn't need to be ported, the author stated it should work on nearly any device/ROM setup. Just get Script Manager app from the market, open app, go to settings, browse as root, then run the V6 script. It will give instructions as it runs.
Sent via Morse code.
Just ran the script last night, while it took me a while to fidget with it and figure out what option was best for me I can't believe that cm7 could be any smoother but there is a definite difference after running the script, with no lag, or home screen redraw, my phone is as smooth if not smoother at 1GHz.then it was at 1.5GHz before the script...just want to say it was painless easy and really made a huge difference...thanks a lot!
On a side note the battery calibration that was linked in the op does seem to work but I had to figure out when to pull the battery since the original instructions where on the milestone, either way great job and thanks again, I'll run this script after any rom I go to from here on out!
Sent from my SCH-I500 using XDA App
efan450 said:
Just ran the script last night, while it took me a while to fidget with it and figure out what option was best for me I can't believe that cm7 could be any smoother but there is a definite difference after running the script, with no lag, or home screen redraw, my phone is as smooth if not smoother at 1GHz.then it was at 1.5GHz before the script...just want to say it was painless easy and really made a huge difference...thanks a lot!
On a side note the battery calibration that was linked in the op does seem to work but I had to figure out when to pull the battery since the original instructions where on the milestone, either way great job and thanks again, I'll run this script after any rom I go to from here on out!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I ran it last night as well. I cannot really tell a difference. What setting are you running?
Option 8 and then option 12, set to browse root, and run as root in the first config screen...afterwords reboot and run option 1...it will tell you if your home screen was easy to kill or not and gives you a list of minfrees...I had to downgrade my busy box to 1.18.2.to get everything working
Edit: I used script manager to run the script and then put the widget on my home screen to easily access it...if you run option 1 and it says your home screen is bullet proof then it did work...I seem to get much better 3g connectivity and better download speeds.
Sent from my SCH-I500 using XDA App
So, i'm running Eclipse 2.0 on my DX2 right now, and i flashed it after trying CM7. CM7 was great, but felt sluggish at times (admittedly I don't believe that I had the "allow purging of assets" enabled at the time either). So after flashing the brand new Eclipse 2.0, I felt like Eclipse was so much more complete, even though it is blur-based. Now, however, after about 3 weeks it's getting sluggish at random times for no reason. There's no apparently eating up the CPU. I always have 80+ MBs of RAM (I'm running Supercharger V6 with the middle (unleaded?) option for 512mb devices selected). I can't seem to pinpoint the problem. So here's where I pose 2 questions:
Eclipse or CM7DX2 (and your reasoning, if you can)
And any ideas on the sluggish performance? I've had this happen on previous ROMs too (older Eclipse models and stock gingerbread w/ bloat removed). I always SBF and wipe data/cache before each fresh ROM install.
Thanks!
Eclipsed from my DX2
Boardwalk30 said:
So, i'm running Eclipse 2.0 on my DX2 right now, and i flashed it after trying CM7. CM7 was great, but felt sluggish at times (admittedly I don't believe that I had the "allow purging of assets" enabled at the time either). So after flashing the brand new Eclipse 2.0, I felt like Eclipse was so much more complete, even though it is blur-based. Now, however, after about 3 weeks it's getting sluggish at random times for no reason. There's no apparently eating up the CPU. I always have 80+ MBs of RAM (I'm running Supercharger V6 with the middle (unleaded?) option for 512mb devices selected). I can't seem to pinpoint the problem. So here's where I pose 2 questions:
Eclipse or CM7DX2 (and your reasoning, if you can)
And any ideas on the sluggish performance? I've had this happen on previous ROMs too (older Eclipse models and stock gingerbread w/ bloat removed). I always SBF and wipe data/cache before each fresh ROM install.
Thanks!
Eclipsed from my DX2
Click to expand...
Click to collapse
Wow, I'm really surprised to hear Eclipse is running sluggishly. I've been running it for a while now and it's completely reliable, the epitome of a "daily driver". Are you running any funky apps or getting apps from fringe markets?
I've found either one can get sluggish, especially if you have a ton of apps loaded.
What I've been doing now is rebooting daily. I'm also running Fast Reboot Pro, which is really more of a "soft" reboot - it doesn't really reboot the phone, per se, but instead it "simulates" a reboot by stopping many services and programs that wouldn't be running at start up.
I myself have a lot of apps installed. I should probably go and remove them, but for some reason, I like to have them loaded (mainly games) just in case I want to play them. OCD anyone?
In any case, I was running CM7 and I'm now running Eclipse 2.1. I've found that I've had the problems in either one which required a reboot. I just switched to Eclipse 2.1 because I found it a wee-bit more stable (no Superuser issues like in CM7) and Eclipse 2.1 has a even more Motoblur crap removed. It's just as responsive as CM7 IMHO.
But, in any case, a daily reboot will fix things and I'm hearing from many that this is almost global across the board with any ROM for the DX2. I think what really hurts the DX2 is the 512mb of main memory. Just pitiful compared to other phones out there.
I've also found running V6 Turbocharger scripts (the latest) helps as well. I've enabled options 6 and 20. Now, this is fine for Eclipse, but you don't want to run it with CM7. At least, that's what I've been told.
Anyways, when I find things get sluggish, I run the Fast Reboot Pro AND, since I'm running Go Launcher EX, I'll got into the "Running Programs" tab in the app drawer and close all the apps in there as well.
If that doesn't help, I then run V6 TC and run option 18 (which recoups RAM and kills lag). If that doesn't help, then I will reboot.
I also forgot to mention, I also use an application called Autostarts. It allows you to choose which apps start up based on a system event (during startup, after startup, USB connection/disconnect, WiFi status change, etc). I've found that a LOT of apps that I've installed start up on some various events. Many games apparently like to connect when they sense there is a data connection present, so I've turned those off. I only want the apps running when I actually launch them. With Autostarts, I have been able to finely control what apps start and when, which has helped as well.
go into BSR and wipe cache and dalvik cache
lemme know if that clears up Ya,lag
it worked for someone else and I've used that method before to clear up lagging issues...
Sent from my DROID X2 using Tapatalk
also, you know eclipse has a 2.1 version out now correct?
Sent from my DROID X2 using Tapatalk
iBolski said:
I've found either one can get sluggish, especially if you have a ton of apps loaded.
What I've been doing now is rebooting daily. I'm also running Fast Reboot Pro, which is really more of a "soft" reboot - it doesn't really reboot the phone, per se, but instead it "simulates" a reboot by stopping many services and programs that wouldn't be running at start up.
I myself have a lot of apps installed. I should probably go and remove them, but for some reason, I like to have them loaded (mainly games) just in case I want to play them. OCD anyone?
In any case, I was running CM7 and I'm now running Eclipse 2.1. I've found that I've had the problems in either one which required a reboot. I just switched to Eclipse 2.1 because I found it a wee-bit more stable (no Superuser issues like in CM7) and Eclipse 2.1 has a even more Motoblur crap removed. It's just as responsive as CM7 IMHO.
But, in any case, a daily reboot will fix things and I'm hearing from many that this is almost global across the board with any ROM for the DX2. I think what really hurts the DX2 is the 512mb of main memory. Just pitiful compared to other phones out there.
I've also found running V6 Turbocharger scripts (the latest) helps as well. I've enabled options 6 and 20. Now, this is fine for Eclipse, but you don't want to run it with CM7. At least, that's what I've been told.
Anyways, when I find things get sluggish, I run the Fast Reboot Pro AND, since I'm running Go Launcher EX, I'll got into the "Running Programs" tab in the app drawer and close all the apps in there as well.
If that doesn't help, I then run V6 TC and run option 18 (which recoups RAM and kills lag). If that doesn't help, then I will reboot.
I also forgot to mention, I also use an application called Autostarts. It allows you to choose which apps start up based on a system event (during startup, after startup, USB connection/disconnect, WiFi status change, etc). I've found that a LOT of apps that I've installed start up on some various events. Many games apparently like to connect when they sense there is a data connection present, so I've turned those off. I only want the apps running when I actually launch them. With Autostarts, I have been able to finely control what apps start and when, which has helped as well.
Click to expand...
Click to collapse
I agree wholeheartedly with the above statement, they are nearly equals in every respect except for SU and most of the time it depends on the user. You will have your own opinions of what you like and dislike in a ROM.
I have always liked Cyanogenmod and I have nothing against Eclipse, it was something that really saved the X2 for me, I was super POed when I found that there was so little to be done with my phone last August when I upgraded to it.
IMHO I would stick with Eclipse just because it is more stable, Cyanogen was a great release from the norm of Moto based ROMS but it is missing a few things since we cannot build it specifically for our phone as easily as everyone else.
Personally though, I hate you guys for being able to flash things right now and I really, really cannot wait for this F-ing soak to come through so I can either join you on 2.1 or have a really fancy paper weight.....
I've been running Eclipse for months, 2.1 for a few weeks now, best version yet. I run it with the build prop mash up, its always fast and responsive. However there are a couple things I do to help ensure that.
1. I schedule "Clear cache for user & system apps" in TB to run daily at 4:30 AM while I'm sleeping which is 30 minutes after my daily backup runs. After the cache clean it reboots. When I get up at 5:30 its usually quick and responsive all day.
2. Use the Moto performance manager built into Eclipse parts, schedule things that you don't want or need running in the background to auto-end (kills the app 2 minutes after the screen shuts off) This really helps with battery life as well, I can usually get 20+ hours of light/moderate use and it helps manage those apps that like to turn themselves on in the background.
3. I use Avast for security, but I also use the firewall feature to restrict network access of games & apps that don't need it.
4. I keep any apps/games I don't use regularly uninstalled, which I can quickly restore from TB if I need them. That seems to really help to as my wife had every free app of the day from amazon installed on hers and it was constantly locking/freezing. she cleaned most of them up and did the auto-end trick and hers has come back to life.
These are just suggestions but I've been using them for months now and they really work well to maximize the X2 as much as we can given the restrictions we have on it. Goodluck.
iBolski said:
I've found either one can get sluggish, especially if you have a ton of apps loaded.
What I've been doing now is rebooting daily. I'm also running Fast Reboot Pro, which is really more of a "soft" reboot - it doesn't really reboot the phone, per se, but instead it "simulates" a reboot by stopping many services and programs that wouldn't be running at start up.
I myself have a lot of apps installed. I should probably go and remove them, but for some reason, I like to have them loaded (mainly games) just in case I want to play them. OCD anyone?
In any case, I was running CM7 and I'm now running Eclipse 2.1. I've found that I've had the problems in either one which required a reboot. I just switched to Eclipse 2.1 because I found it a wee-bit more stable (no Superuser issues like in CM7) and Eclipse 2.1 has a even more Motoblur crap removed. It's just as responsive as CM7 IMHO.
But, in any case, a daily reboot will fix things and I'm hearing from many that this is almost global across the board with any ROM for the DX2. I think what really hurts the DX2 is the 512mb of main memory. Just pitiful compared to other phones out there.
I've also found running V6 Turbocharger scripts (the latest) helps as well. I've enabled options 6 and 20. Now, this is fine for Eclipse, but you don't want to run it with CM7. At least, that's what I've been told.
Anyways, when I find things get sluggish, I run the Fast Reboot Pro AND, since I'm running Go Launcher EX, I'll got into the "Running Programs" tab in the app drawer and close all the apps in there as well.
If that doesn't help, I then run V6 TC and run option 18 (which recoups RAM and kills lag). If that doesn't help, then I will reboot.
I also forgot to mention, I also use an application called Autostarts. It allows you to choose which apps start up based on a system event (during startup, after startup, USB connection/disconnect, WiFi status change, etc). I've found that a LOT of apps that I've installed start up on some various events. Many games apparently like to connect when they sense there is a data connection present, so I've turned those off. I only want the apps running when I actually launch them. With Autostarts, I have been able to finely control what apps start and when, which has helped as well.
Click to expand...
Click to collapse
iBolski, the similarities between yours and my "phone management" techniques scare me lol.
pretty much everything you have said I do as well, including leaving games installed just in case I wanna play one day lmao
I just wanted to add to the point you made about rebooting once every day, this is something that it's not only recommended for the Dx2 but for ALL, Android powered phones in general, I do believe it is also written in the "manual", that comes with the devices, kinda like how a PC needs a reboot once in a while, Android benefits from a reboot once a day as well, allows it to drop system caches that have built up and are hanging around and such,
that fast reboot app I have also used in the past, but nothing compares to an, accrual power cycle of the device, I will even go ahead and wipe cache from Android recovery as well once every couple days,
our set UPS are most likely extremely similar and I've found I get pretty damn near the most I can get out of this x2, I feel like the only thing else I could benefit from is a new kernel, as I've pretty much tweaked this thing to the max I can get while locked down
ashclepdia said:
iBolski, the similarities between yours and my "phone management" techniques scare me lol.
pretty much everything you have said I do as well, including leaving games installed just in case I wanna play one day lmao
I just wanted to add to the point you made about rebooting once every day, this is something that it's not only recommended for the Dx2 but for ALL, Android powered phones in general, I do believe it is also written in the "manual", that comes with the devices, kinda like how a PC needs a reboot once in a while, Android benefits from a reboot once a day as well, allows it to drop system caches that have built up and are hanging around and such,
that fast reboot app I have also used in the past, but nothing compares to an, accrual power cycle of the device, I will even go ahead and wipe cache from Android recovery as well once every couple days,
our set UPS are most likely extremely similar and I've found I get pretty damn near the most I can get out of this x2, I feel like the only thing else I could benefit from is a new kernel, as I've pretty much tweaked this thing to the max I can get while locked down
Click to expand...
Click to collapse
I think we're so similar due to the fact that I've seen you tell people to do this, so I'm just following your instructions. Scary, huh?
Also, Orange Terror gave a great tip that I didn't even know existed in Titanium Backup Pr. Goes to show you can always learn something new since I've used TBU for about two years now. I've gone in and set up a schedule to clear user and app cache and reboot the system every day around 4 am. At 3 am, I have it backup and upload to my Box account. Now I don't have to worry about doing that myself or missing a backup.
But I think the big thing that has helped me out now is also the Autostarts app. Going through and having it ensure certain apps don't launch under various scenarios has definitely caused my phone to be MUCH more responsive now.
Like you, it's allowed this crap X2 to actually be functional, along with Eclipse 2.1 and/or CM7. With DZK and Nitro, I'm not sure where this phone would be. Probably thrown against the wall and shattered into a million pieces!
iBolski said:
I think we're so similar due to the fact that I've seen you tell people to do this, so I'm just following your instructions. Scary, huh?
Also, Orange Terror gave a great tip that I didn't even know existed in Titanium Backup Pr. Goes to show you can always learn something new since I've used TBU for about two years now. I've gone in and set up a schedule to clear user and app cache and reboot the system every day around 4 am. At 3 am, I have it backup and upload to my Box account. Now I don't have to worry about doing that myself or missing a backup.
But I think the big thing that has helped me out now is also the Autostarts app. Going through and having it ensure certain apps don't launch under various scenarios has definitely caused my phone to be MUCH more responsive now.
Like you, it's allowed this crap X2 to actually be functional, along with Eclipse 2.1 and/or CM7. With DZK and Nitro, I'm not sure where this phone would be. Probably thrown against the wall and shattered into a million pieces!
Click to expand...
Click to collapse
Amen to that. Thanks to Nitro, DZK and anyone that has contributed something.
I've been trying to start synching to box through TBU recently, but I can't schedule it to run automatically and when I try to run it manually after an hour its at like 20%, and I'm doing it on wifi. And it won't upload to my dropbox account at all, just sits there. Any suggestions?
iBolski said:
I think we're so similar due to the fact that I've seen you tell people to do this, so I'm just following your instructions. Scary, huh?
Also, Orange Terror gave a great tip that I didn't even know existed in Titanium Backup Pr. Goes to show you can always learn something new since I've used TBU for about two years now. I've gone in and set up a schedule to clear user and app cache and reboot the system every day around 4 am. At 3 am, I have it backup and upload to my Box account. Now I don't have to worry about doing that myself or missing a backup.
But I think the big thing that has helped me out now is also the Autostarts app. Going through and having it ensure certain apps don't launch under various scenarios has definitely caused my phone to be MUCH more responsive now.
Like you, it's allowed this crap X2 to actually be functional, along with Eclipse 2.1 and/or CM7. With DZK and Nitro, I'm not sure where this phone would be. Probably thrown against the wall and shattered into a million pieces!
Click to expand...
Click to collapse
lol
well I know quote a few people seem to trust my set up lol
that auto starts app sound like it worth checking into also, thanks for the tip!
Thanks for all the responses guys! It's great to see some insight as to what everybody does on their daily schedule.
1. Yes, i do know there is 2.1, I just haven't had the time/availability to upgrade (until tonight, so i'll probably be doing that).
2. I'm admittedly bad at keeping a LOT of apps installed feeling like i'll need to use them, probably would be better off if i just kept them either frozen or only kept a backup.
3. As with you, iBolski, i've been running option 6 in V6 and that definitely helps a lot.
4. I'll have to try the nightly cache clearing, i usually just manually do it when i feel the phone is laggy.
Also, what launchers do you guys use? Just outta curiosity. I personally use LauncherProPlus. Yeah, the development is dead, but I've been using it since my OG Droid days, and it's served me excellently ever since. I don't need beauty in a launcher, just raw speed and a small footprint.
Thanks again!
Boardwalk30 said:
Thanks for all the responses guys! It's great to see some insight as to what everybody does on their daily schedule.
1. Yes, i do know there is 2.1, I just haven't had the time/availability to upgrade (until tonight, so i'll probably be doing that).
2. I'm admittedly bad at keeping a LOT of apps installed feeling like i'll need to use them, probably would be better off if i just kept them either frozen or only kept a backup.
3. As with you, iBolski, i've been running option 6 in V6 and that definitely helps a lot.
4. I'll have to try the nightly cache clearing, i usually just manually do it when i feel the phone is laggy.
Also, what launchers do you guys use? Just outta curiosity. I personally use LauncherProPlus. Yeah, the development is dead, but I've been using it since my OG Droid days, and it's served me excellently ever since. I don't need beauty in a launcher, just raw speed and a small footprint.
Thanks again!
Click to expand...
Click to collapse
just a tip for when you update to 2.1
you really shouldn't need to wipe data, I haven't wiped data once when updating from 2.0> 2.xand I have had zero issues,
also, nitro has added a couple features/options to the stock eclipse launcher which are nice, u can choose amount of home screens, infinite loop, uninstall app when u long press then hold it over the trash can for a second (pretty useful, no more needing To go into manage apps to uninstall apps)
if ya wanna venture from that I recommend adw ex or go launcher ex(nitro has an eclipse theme in the market for go launcher in case ya wanna support him (it's like a buck) and wanna keep an eclipse theme with a different launcher that has more options)
either that or just do a quick market search or Google search for "light weight launcher" to get some nice options, there's an almost endless list of launchers to try, I've spent hours trying different launchers and still haven't touched half of them lol, there is so many choices it's crazy, there is something for every type of user, from minimalistic launcher to fancy ones like spb shell and such
Boardwalk30 said:
Thanks for all the responses guys! It's great to see some insight as to what everybody does on their daily schedule.
1. Yes, i do know there is 2.1, I just haven't had the time/availability to upgrade (until tonight, so i'll probably be doing that).
2. I'm admittedly bad at keeping a LOT of apps installed feeling like i'll need to use them, probably would be better off if i just kept them either frozen or only kept a backup.
3. As with you, iBolski, i've been running option 6 in V6 and that definitely helps a lot.
4. I'll have to try the nightly cache clearing, i usually just manually do it when i feel the phone is laggy.
Thanks again!
Also, what launchers do you guys use? Just outta curiosity. I personally use LauncherProPlus. Yeah, the development is dead, but I've been using it since my OG Droid days, and it's served me excellently ever since. I don't need beauty in a launcher, just raw speed and a small footprint.
Click to expand...
Click to collapse
I'm using Go Launcher EX myself. Have been since I ran an LG Vortex (now THAT was a SLOW phone but man, as far as music goes, it never skipped unlike the X2. Sad since it's an ARM6 600mhz single-core phone AND it had an unlocked bootloader so I could overclock the thing!).
For launchers I started with pro launcher. Then ended up with go launcher for a while. Now I am using adw ex. However I really like the new work nitro did with pro launcher. I would of stayed on it except for the 3D app drawer. Don't get me wrong it looks awesome and I used to use similar app drawer with the shell launcher but it triggers my vertigo.
Boardwalk30 said:
Thanks for all the responses guys! It's great to see some insight as to what everybody does on their daily schedule.
1. Yes, i do know there is 2.1, I just haven't had the time/availability to upgrade (until tonight, so i'll probably be doing that).
2. I'm admittedly bad at keeping a LOT of apps installed feeling like i'll need to use them, probably would be better off if i just kept them either frozen or only kept a backup.
3. As with you, iBolski, i've been running option 6 in V6 and that definitely helps a lot.
4. I'll have to try the nightly cache clearing, i usually just manually do it when i feel the phone is laggy.
Also, what launchers do you guys use? Just outta curiosity. I personally use LauncherProPlus. Yeah, the development is dead, but I've been using it since my OG Droid days, and it's served me excellently ever since. I don't need beauty in a launcher, just raw speed and a small footprint.
Thanks again!
Click to expand...
Click to collapse
I also use ADW EX, it has been the most consistently bug free for me depending on the settings you use it can be lightning fast or just as bad as a stock launcher, but generally it is much faster than the stock ones and it is more user friendly.
Love all the insight here. I was running cm7 for a while but now on eclipse 2.1 and I haven't wanted to go back to cm7 yet. I also usually use adw ex but have been sticking with stock launcher. This go around. I reboot my phone at least once a day. I haven't tried any scripts yet but I haven't felt the need to iether. I try too keep as few apps running as possible. I also found that after I get done charging my phone I will reboot. Seems to give me more free ram. 185mb right now.
Sent from my DROID X2 using xda premium
CM7 rocks. Once CM9 becomes stable and a beta it will most likely be the best ROM on the X2.
Sent from My Rooted MB870/DROID X2 Running CM7
I must say, after upgrading to 2.1, uninstalling 34 apps (mostly large games) that i seemingly never used, and installing the build.prop mash up, i haven't had any issues yet so far! 2.1 seems to be quite the upgrade from 2.0. Thanks to everybody who posted their experience/ideas!
I started experiencing even more lag lately and it would immediately show up even after reboot. This started happening after I set up TBU to do a nightly cache clean and reboot.
What I finally figured out was, V6 Turbocharger scripts mem settings were not sticking! They were reverting back to the default for whatever reason. It was funny because the Lag Nullifier was still active.
So, I unturbocharged and everything via the scripts and set it back up to use local.prop and that seemed to fix everything.
Another thing I did was install Autostarts to tell it what apps should NOT start when certain system events occur (during startup, after startup, media change, etc).
I also used the Motorola Performance Manager to set up most apps to be killed two minutes after the phone goes to sleep.
I reinstalled Widgetlocker and things have been running smooth all day where as before, after playing many games (like Templerun, Fruit Ninja, Sims Free to Play, etc), I would notice lag would seep in and would require a reboot to fix it.
Now, with my set up (TBU clears cache and reboots nightly, Autostarts, Motorola Performance Manager, V6 TC), things are running smooth, smoother than they have before.
Hey guys. I believe that the os21 update has a bad memory leak/background processing management(besides a kernal issue). When playing heavy 3d games like Nova 3 or Sonic, the framerates are really slow or stutter a lot until the games force-close. Well, for the past 2 days, I have not had this issue, both Nova 3 and Sonic play with no stuttering at all, and I have not experienced any more game crashes. My browser also seems much smoother. Please try the two fix options listed below, while noting that the 2nd option seems to work best with mass Efeect, and less "strict" on runnig processes than the first option:
Fix #1- What I did was push the soft reset button on the Prime (using a small paperclip), then waited for the Prime to reboot. Once it rebooted, DO NOT let the Prime load up anything, just immediately go into settings, developer options, select the kill all activities option, then for background processes, select "at most 1 process only" Delete all of your running task managers/task widgets an that's it. Now all of my games run, no crashes, and the framerates for Nova 3 and Sonic is MUCH better.
Fix# 2 - For those still having issues with Mass Effect, this alternate setting will definitely fix the problem. After soft rebooting, go into development settings, and then for background processes, select "at most 1 process only" and DO NOT select kill all processes after leaving them. This setting has been confirmed to fix the Mass Effect issue, as well as all other games while still keeping the Prime running a lot smoother.
Please try using the exact instructions that I have posted, and let me know if this works for you guys. If so, then it proves that the os21 has a memory management issue which is causing all the current issues we are having.
Also, I would like to share this post from Jaycustom, whom has also been using this method for a few days now and enjoying it more than myself lol. He ran a CPU test to test the differences before and after my fix. See his results below:
Default settings said I had about 19 user/ 29 system processes running.
Dev settings gave me 14 user/ 11 system processes running.
Default settings for system memory 600+mb used/300+ free
Dev settings for system memory 300+ used/600+ free
The memory usage was pretty much exactly reversed! So I assume this is where most, but not all, of the performance boost comes from. CPU usage was also lower, not by much though.
See the video that I made (link below)showing me using the default browser, which is now really fast and stable using this method. I also ran Mass Effect 3 and Nova 3 to show that I have no issues playing these games anymore. I used a Samsung Galaxy tab to record, so please re-frame from laughing at the quality of the vid lol! If you guys would like me to try more games/apps, please let me know.
http://www.youtube.com/watch?v=iperCmEH4t4&feature=youtu.be
Thanks guys
Nova 3 is still freezing and crashing, frame rate is still same.... I think tehere is no solution untill FailLoft will update the app for tegra 3.
mibo666 said:
Nova 3 is still freezing and crashing, frame rate is still same.... I think tehere is no solution untill FailLoft will update the app for tegra 3.
Click to expand...
Click to collapse
Sorry to hear that it didnt work for you, but it seems to have resolved the issue for me entirely. I am not exeriencing any more gam crashes or white flashing screens. Are you sure that you followed the stes listed? Waiting for others to rely, but either my Prime just decided to play all my games correctly, or this is "fix" is working for me.
This is not an acceptable fix, it is only a workaround.
leppie said:
This is not an acceptable fix, it is only a workaround.
Click to expand...
Click to collapse
Yes I agree 100%, but it works. At least we can play some of our games/browse without issue until the fix comes out. Did you try it, and did it work for you?
MRCANNADY said:
Yes I agree 100%, but it works. At least we can play some of our games/browse without issue until the fix comes out. Did you try it, and did it work for you?
Click to expand...
Click to collapse
I'll have to try this out tonight. To clarify, when you say "do not let it load up anything", do you just mean go into the settings as soon as possible and kill things? It must start running services as soon as it boots, no? I guess this just minimizes the "damage"?
Hi, I've just tried this and it doesn't seem to have had much of an effect I'm afraid.
In the last 10 mins I've still had two spontaneous browser shutdowns, plus crappy streaming video playback from sites such as bbc iplayer.
The pages seem to load a little faster and scrolling may be a touch smoother but thats about it the best I can say.
This solution works well for me. I have been doing this for some time, except I have limited the processes to three. Limiting it to one seems to improve it even better. Widgets seem also to be a drain on the resources and limiting those works well for me. Much thanks for the post.
You might also try this solution from here post #118 :
http://forum.xda-developers.com/showthread.php?t=1681469&page=12
It seems to have worked for me, I've only had one reboot since. It's at least worth a try. Good luck.
seeknom said:
I'll have to try this out tonight. To clarify, when you say "do not let it load up anything", do you just mean go into the settings as soon as possible and kill things? It must start running services as soon as it boots, no? I guess this just minimizes the "damage"?
Click to expand...
Click to collapse
yes exactly.. this is the way it worked for me. Just immediately go into setting, and select the options that i listed. This will only allow the essential programs to run. Please let me know if this works for you. Also, switch the prime to performance for graphic heavy games. Still testing this, but so far I have not have any crashes since applying.
ksharp4444 said:
This solution works well for me. I have been doing this for some time, except I have limited the processes to three. Limiting it to one seems to improve it even better. Widgets seem also to be a drain on the resources and limiting those works well for me. Much thanks for the post.
Click to expand...
Click to collapse
Thanks for confirm this. Yes, my Prime is no longer lagging when browsing or crashing during gameplay..the difference is honestly night and day. Just confirms for me that .21 is not handling the background processes, or closing them correctly.
jemberton said:
Hi, I've just tried this and it doesn't seem to have had much of an effect I'm afraid.
In the last 10 mins I've still had two spontaneous browser shutdowns, plus crappy streaming video playback from sites such as bbc iplayer.
The pages seem to load a little faster and scrolling may be a touch smoother but thats about it the best I can say.
Click to expand...
Click to collapse
Hey, do you happen to have the sticky player app installed by any chance?
No I've never used sticky player app.
I've been toying with the idea of factory resetting and trying this. I'll see how it goes tonight
jemberton said:
No I've never used sticky player app.
I've been toying with the idea of factory resetting and trying this. I'll see how it goes tonight
Click to expand...
Click to collapse
you shouldn't have to factory reset, that would suck
Can you try the soft reset option again? Once it's done, update the setting as listed and try the Prime on performance mode. If that doesn't help, then you may have a bad app which is hogging on your resources and causing the slowdown/crashes.
This procedure also seems to improve on the strength of the Wi-Fi signal. At least on mine it does.
ksharp4444 said:
This procedure also seems to improve on the strength of the Wi-Fi signal. At least on mine it does.
Click to expand...
Click to collapse
Maybe it's just because the Prime is loading pages a lot faster because there aren't so many things running in the background now. it would be cool though if this also fixed wifi, maybe someone should do a speed test for before and after the fix?
I just tried the default browser again. It does not lag/stutter when scrolling through the pages anywhere near like it used to. it's not as smooth as opera mini, but it's a LOT better than before. Still no game crashes at all since doing this. I can post vids for anyone who would like to see proof after work.
MRCANNADY said:
you shouldn't have to factory reset, that would suck
Can you try the soft reset option again? Once it's done, update the setting as listed and try the Prime on performance mode. If that doesn't help, then you may have a bad app which is hogging on your resources and causing the slowdown/crashes.
Click to expand...
Click to collapse
I was gonna do one anyway, just to start from scratch with a blank slate and get it set up how I want it!
After resetting, and before any apps are downloaded the browser is working much much better once the settings you recommend are applied. Loading and scrolling is faster and there have been no force closes or video hangups.
Cheers, I look forward to this .28 update but thats helped me out a lot in the meantime!
jemberton said:
I was gonna do one anyway, just to start from scratch with a blank slate and get it set up how I want it!
After resetting, and before any apps are downloaded the browser is working much much better once the settings you recommend are applied. Loading and scrolling is faster and there have been no force closes or video hangups.
Cheers, I look forward to this .28 update but thats helped me out a lot in the meantime!
Click to expand...
Click to collapse
Great to hear! yes, my Prime seems much quicker with touch inputs, scrolling, gaming and web browsing. Must of been a bad memory issue along with the kernel for .21.
just did this ans seems to work very well. i was getting around 12-15mbs and now im getting 32mbs in the garage with only 1 bar. im very happy with that. thanks for sharing.