Related
The lovely thing about having a Linux Kernel is that we can do a lot to optimize it.
I figured it would be a great idea to set up a thread where we can bring all these optimizations into one place.
Mind you, I'm no expert by any means...
For my (possibly useless) contribution:
When we compile the kernel to the G1, do we compile it with the general Arm eabi? If so, is that made for ALL ARM cpu's? We have an ARM6 in our G1's. If we set it up to optimize to ARM6, can we set it up to use the CPSID/CPSIE instruction instead of the SWP instruction? Are the drivers open source? Can we recompile them to do the same also? To learn more about why, read this:
http://forum.xda-developers.com/showthread.php?t=516223
That's where I got the idea from.
SWP is a deprecated opcode in armv6 that decreases performance due to the way it locks the bus.
Click to expand...
Click to collapse
Anyhow, whatever you guys post here, I will add to this post. Also, to the people to compile the kernels, can you answer my questions?
answers to some of your questions.
hi i usually don't post here since i am not a developer but in this case i think i can answer some of your questions (since i sometime make custom kernels for my laptop). kernel optimazation is used to removed excessive drivers and services from the kernel that you don't need that slows down your computer or in this case phone. i believe htc already does this when they configured android for the g1. most cell phone manufactures already do this to ensure that there products processor use energry efficiently and and run as smoothly as possible.
When we compile the kernel to the G1, do we compile it with the general Arm eabi? If so, is that made for ALL ARM cpu's? We have an ARM6 in our G1's
Click to expand...
Click to collapse
yes, arm eabi is made for all general arm cpu's i believe you can complie it for arm 6 specifically though. how do you know that htc hasn't already optimize the kernel for that specific processor? also if they didn't you wouldn't really see any noticible speed improvements by compliling the kernel for this specific processor.
Are the drivers open source?
Click to expand...
Click to collapse
no, futhermore they don't offer the drivers for the g1 except execpt for the usb driver so your computer can recognise the g1 as mass storage device.
If we set it up to optimize to ARM6, can we set it up to use the CPSID/CPSIE instruction instead of the SWP instruction?
Click to expand...
Click to collapse
i don't know sorry. thats all i know i'm really not a kernel, coding expert i hope this helps in your task.
bananajama said:
no, futhermore they don't offer the drivers for the g1 except execpt for the usb driver so your computer can recognise the g1 as mass storage device.
Click to expand...
Click to collapse
I think you meant to say "ADB interface" instead of "mass storage device."
t1n0m3n said:
I think you meant to say "ADB interface" instead of "mass storage device."
Click to expand...
Click to collapse
The system type is set to "Quaalcom MSM", so I would imagine that it's optimizing for arm6l.
cyanogen said:
The system type is set to "Quaalcom MSM", so I would imagine that it's optimizing for arm6l.
Click to expand...
Click to collapse
Sounds like it. Well, other than that, are there any other obtimizations anyone else can think of?
there are few things in linux that you can play with to see if you get any performance increase. It's mainly in memory management. run ls on /proc/sys/vm. you can play with the page cache but I doubt that you'll get much perf increase from it since, since most of the things we can play with are for write back cache. If we have access to the dalvikvm we may be able to do more optimization. The one thing that I've always wanted to be able to do is to pin Home in memory, and not allow garbage collector to kill it, so when we exit out of memory intensive apps, like browser, gallery, etc, we do not have to wait for Home to reload. If we have more control over garbage collection we may be able to do more, but I don't know much about the dalvikvm at all.
taking a quick look at the vm. The only nob that may have any effect on android may be vfs_cache_pressure. theoretically setting to 200 would push fs cache out quicker and give more memory to the vm. default is set to 100. I set it to 200 and 300 but didn't notice any difference.
knaries2000 said:
there are few things in linux that you can play with to see if you get any performance increase. It's mainly in memory management. run ls on /proc/sys/vm. you can play with the page cache but I doubt that you'll get much perf increase from it since, since most of the things we can play with are for write back cache. If we have access to the dalvikvm we may be able to do more optimization. The one thing that I've always wanted to be able to do is to pin Home in memory, and not allow garbage collector to kill it, so when we exit out of memory intensive apps, like browser, gallery, etc, we do not have to wait for Home to reload. If we have more control over garbage collection we may be able to do more, but I don't know much about the dalvikvm at all.
Click to expand...
Click to collapse
dxtop, which is a home replacement, does exactly that. It keeps itself in memory so going back to it is much faster than the default home application. And in low memory situations, it tries to free up as much resources as possible while still staying in memory.
ok its simple we all know the benefits of more ram. we all know that android slices up the ram into static addresses within the kernel. i would like to change that as we are in 2009 almost 2010 and we still rely on static ram allocation for the camera, gpu, sensors, radio. the g1 has 192mb of ram. yet we only get 97 for programs to use. i would like to place the camera, gpu, etc into dynamic addresses that we can change within the os without flashing a new kernel. a service, kernel code, module, or any other method could do this. we just have to make it happen. we could do it three ways i see.
1. a system managed ram allocation using a service to detect the percentage used and increase ram on the go.
2. a kernel script or service that only activates and allocates ram when needed. such as once a 3d program is loaded the 8mb magically comes back.
3. a virtual device ram allocation service that makes the device think it has the ram all along, but only actually gets it when it needs it. kinda like the way apps2sd works.
4.(by IConrad01) run perl scripts through ase and use ksplice to patch the gpu1 memory in kernel. one script on and one for off.
any other methods to implement this proper are very welcome and encouraged.
the idea behind this is a proper way to get back more ram for our programs. the idea is simple when 3d is not in use we can used the 8mb it would have used for something else. this applys to everything that has its own ram. camera, etc. say we did this and only got 120 free. thats almost 25% more ram. plus we could go the extra step and let the user choose how much each thing gets(gpu settings 4mb,8mb,12mb. camera on, off. etc) so when it needs it thats what it gets. great if you like/dislike 3d games.
on another note this is the kind of work that gets you noticed. the kind that gets you hired or gets you respect. google would be proud and might implement it and you and i know it. i hope we are successful and google uses it mainstream.
so lets debate a way/ways to do this
provide alpha tests of different ways to do this
and finally lets post a beta so everyone can enjoy.
atm ksplice with perl scripts is where we are going will update as this progresses.
Doesnt Jacs update to his hero rom have this, im probably mistaken
jad011 said:
Doesnt Jacs update to his hero rom have this, im probably mistaken
Click to expand...
Click to collapse
No. The current implementation of this basically cuts the graphics memory in half.
This would dynamically allocate the memory as needed. Much more efficient way of doing it.
he has a static change that takes the ram away from the gpu by a kernel edit. this is to have both more ram but still give the gpu what it needs to perform properly but only when it needs it or you chose to give it.
Are you referring to RAM or storage space? You say RAM in the title but then it sounds like you're talking about storage space before making me think it's RAM again later on. I'm confused :/ I'd really like additional free RAM, anything that helps reduce swapping to SD card is good but storage space I have plenty of.
all of this would apply to ram only. swap and compcache could use the same idea to dynamically allocate swap but that is still a cache for programs. sorry if its confusing. simple way to explain. i want all the ram i can get but still use everything the phone has properly, like games and the camera.
Gotcha and understood. I see so many people say RAM and memory when they're referring to storage space sometimes that I want to scream but extra RAM on the G1 would be more than welcome. Hopefully others with the brains to make it happen can do it
actually anyone with a basic knowledge can help. mostly there are a couple things to developing a good idea.
first the concept.
then ideas on how to do it.
next a map or guide to what does what.
coding different parts
putting them together
debug and test
even if all you do is photoshop the ui or provide ideas it helps. once some different people get aboard this should be working sooner than you think.
Of the three options listed, the kernel script (via ksplice) seems like it would be the shortest route to functionality, but frankly it also seems a bit... well, hackish -- when compared to the virtual device allocation scheme. It would take a hefty re-write of the kernel, I suspect, to accomplish; but being able to resize various devices on the fly would be a good thing. Shrinking CompCache based on real RAM usage for example would probably speed up the phone under light loads.
Just thinking in text here.
personal i think its going to start simple(script or root app) and go straight to gpu shared on or off. choose and reboot. however i do not want to stop there like winmo did. someone could create a short kernel patch that checks for a service or script and gets value or defaults to standard method. then we would have to come up with how to manage the switch(realtime vs. reboot) ideally we would remap the memory from scratch and rebuild the memory management services to dynamically allocate the ram for all devices(128+ ram) as needed. we have a start, we know where and how to turn the gpu1 shared on or off. now lets make it more than a hack and work on how to make our phones better. btw this is not a waste of time. this extends to other phones and the future way to set up our phones from default.
jokersax11 said:
personal i think its going to start simple(script or root app) and go straight to gpu shared on or off. choose and reboot. however i do not want to stop there like winmo did. someone could create a short kernel patch that checks for a service or script and gets value or defaults to standard method. then we would have to come up with how to manage the switch(realtime vs. reboot) ideally we would remap the memory from scratch and rebuild the memory management services to dynamically allocate the ram for all devices(128+ ram) as needed. we have a start, we know where and how to turn the gpu1 shared on or off. now lets make it more than a hack and work on how to make our phones better. btw this is not a waste of time. this extends to other phones and the future way to set up our phones from default.
Click to expand...
Click to collapse
The only problem with this is when the ram is divided, everything in it is cleared, thats why it is set at boot in the kernel. Think of it like repartitioning your SD. Now it would probably be possible have everything mapped to ONE big RAM table & then build something similar to a scheduler like BFS for RAM that would allocate it as necessary. This is messy though.
Just my $.02
well yes but it is possible to create shared memory through c++ http://www.go4expert.com/forums/showthread.php?t=8461
however i think the vm heaps has either a 6 or 16mb limit. anyways the service would basically do a memory patch over the kernel in realtime(like overclock) telling the gpu the memory is there all the time. meanwhile it allocates dynamic shared memory from the application memory for the gpu to read and write. meanwhile an app tied to a script would set the parameters and settings.
Okay -- I know ksplice works with perl; and I know that we can run perl scripts using the ASE .apk.
So... it seems to me that it /should/ be possible to use a patch that reverts the patched kernel back to the previous state, and a patch that switches the original state to the GPU1=0 MB state. From there, we could set up two scripts; one for GPU1-off and one for GPU0-on. Each would simply be an invocation of ksplice to input the specific patch (which would have to be stored on the sd card. [it would be safer if in the ext partition]).
We'd have to set up a secondary RAM device, rather than just adding it to the standard RAM pool... something like establishing it as a /dev/block/shm.
The point of all the above is that when you click on the GPU1-off script, it "reclaims" that RAM and gives you a device that's standard RAM. When you click on the GPU1-on script, it disables that device (forcing the reload of all programs using that RAM) and re-enables the GPU1 device.
Even better yet, the Android Scripting Environment program, much like GScript, supports desktop icons.
So -- very initially speaking, assuming we can get ksplice working on Android (which just requires a static binary, IIRC), we can get a simple pair of icons; one of which frees up the GPU1's RAM; and the other of which re-enables the GPU1.
Since the only times it's going to be "called up" are when a game is actively being played, or something similar, this should be a mostly-satisfactory route to begin with, before we can get into the whole scheduled/scaled script running as a daemon in the background.
Once we get /there/, then we can start looking at true virtual device allocations and shared memory and the like.
Although, I do have to say that I'm not entirely sure how comfortable I am constantly repatching the kernel. Definitely, we're going to want to recommend that people back up their original, unpatched, boot.img files!
IConrad01 i added your method to first post as it was a great start to this project. if you want me to rephrase just post what you want and ill change it. the only issue i might see is what geniusdog254 said it might unallocate the wrong thing and create a reboot. but some clever coding should prevent this.
Nah, that's all good.
There's an easy way to prevent it from becoming a reboot-able issue. Enable the GPU-space device as "swap". This could be done one of two ways; tell the phone that the new 8 MB RAM "device" is to be considered the /first/ swap device to be used, and just leave it "as is". The r/w times would be for true RAM. The other option assumes we have the latest CompCache (0.6+) -- as it allows for multiple instances of CompCache. The theme here should be obvious.
Either way, the result is that only swappable pagefiles would be lost when the device is turned back into GPU memory. No system-vital memory would get tossed. Seems simple enough to accomplish, perhaps. But then again, I Am Not A Programmer.
ok so what are the alternatives to ksplice for the swap device change. since we could make it swap/compcache anyways is it possible to change on the fly like the way overclocking widget does?
Ksplice allows you to make kernel updates and have them implement themselves without having to reboot the device. The swap device stuff would have to be implemented on a script-level. Two different things: I.e.; the script invokes ksplice to install a specific patch, which causes the kernel to recognize the newly freed-up RAM as a specific device (I.e.; such as /dev/ram1 as opposed to /dev/ram0). I am not sure I'm saying/thinking of this properly here: I'm operating on the edge of what I know about Linux.
Anyhow -- the trick is, when we get the kernel to disable the GPU's memory, we enable a new RAM-disc swap partition with its swappiness set to the maximum rating so it picks up everything first. Since it is /actually RAM/, it'll perform like real RAM. We're only 'declaring' it as swap in order to prevent forced reboots when turning it off.
The above wouldn't just be a ksplice thing; ksplice is just to implement daproy's kernel patch and thus free up the devoted memory to the GPU1. This memory would then be allocated to a new device (thus preventing the RAM-dump forced reboot) and /that/ would be set to swap status to ensure no "mission-critical" files go on it.
Then, once we get that built up, we just build it in "reverse" -- turn off swap (dumping its info back to the system, where CompCache / linux-swap would pick up the load) and re-enabling the GPU1.
Once we get /those/ built, we can then create a daemon script, include an invocation of it into the latest userinit.sh, and have that script basically monitor GPU0's load levels. If they go above a certain threshold (scaling, just like with the CPU), it would invoke the second script above, patching the kernel and re-enabling GPU1. This would then monitor the GPU, and once //its// memory load falls back down to where GPU0 can handle it all, turns GPU1 off and frees that RAM back up for individual use.
I can already foresee a complication where turning GPU1 off "on the fly" would cause a reload of all graphics, but... considering how rare it is to even pull a load above what GPU0 can handle in ordinary use, this isn't much of an issue. It'd take some tweaking and beta-testing (which I'm pretty much set to be a tester of at this point, apparently ) but that would be about it.
Now, //ideally// we could create an alternative solution which wouldn't rely on constantly patching the kernel. As I said; that can get... well, "messy".
I just don't know enough to know what that alternative path would be. Virtual shared memory space seems like it would be a good idea. An alternative solution could be something along the lines of enabling GPU1 at all times and simply having it call to a swapfile which is located in /tmp (I.e.; a non-compressing swap-file which is actually located in RAM). Said swapfile could be resized freely according to need and would thus be no issue at all.
Frankly, I can already see one reason why that would be a superior solution to all the ksplice shenanigans above: said swapfile could be made to be /larger/ than 8 MB, and thus actually provide for an increased performance due to higher available memory for the graphics side of things. We'd want some way to make sure that the swapfile itself wouldn't get pages dumped onto an actual swap partition. This seems like a much more elegant solution than the ksplice routine. I simply have no idea if it's even feasible. The swapfile would have to be mounted into /tmp (or it's Android equivalent) //at the time the GPU1 was enabled//. Is that even /possible/ at boot? Could we simply enable the device very late in the boot stage?
Quickly! Someone with /actual programming expertise/, rescue me from my aimless mental tinkering!
Since it seems there's little activity in this thread, I thought I'd share:
There is a debian armel package for ksplice.
( http://packages.debian.org/squeeze/ksplice )
This is ARM-compiled. We would simply need to cobble together a script which invokes ksplice properly. I myself know nothing of how this would be done.
Usage example of ksplice here:
http://www.ksplice.com/example-update
Looks pretty simple. You just need a working kernel build environment. Anyone got one of those laying around? I have wanted to do that for awhile but am too lazy to set up a linux VM, lol.
Hell yeah!!
Im not much good for this project other then willingness to try betas and give feedback, but I'm excited to see where this goes.. It would be great to reclaim the ram being used from the system when you aren't using anything that needs it and use it for what you are using. Has anyone contacted one of the devs that have been modifying the kernels and ask them if they could try building it with the ksplice functionality?? I would think one of them would be happy to build it so you can start playing with it. Wish I could help more on it, but this is a little above my head, but I will be following this thread and learning what I can as i go.. Good Luck!!
I don't see chefs using dynamic pagepools (set to 0) anymore.
When I get a ROM, one of the first things I do is set the pagepool to 0.
Is there a reason that people are shying away from this?
Does having a fixed vs dynamic pagepool really offer better performance?
I've been experimenting with dynamic pagepool (on a 6.1 rom), and I find it works just fine, if not better than when I manually set a 16, 18, or 20 meg pagepool. I have a feeling that results will vary quite a bit though, depending on the OS build and what's installed.
Moved as not ROM Development.
I set to 0 dynamic and find better than a static pagepool generally see the improvement when flicking through pics in TF3D and access of start menu icons.
I've used everything from 12-28 on 6.5 roms (they all seemed pretty much the same), and have used 0 before and have gone back to it. It is faster for me; particularly, I get faster boot speeds in sk tools benchmarking (by maybe 0.5 seconds). I don't do hardcore multitasking, but it seems to me that it runs smoother with several heavy apps running. But it uses memory like crazy sometimes. I'll see 100 MB disappear when I use wmplayer to play an .mp3 (but not other formats, like .wma). It seems pretty stable; I remember having the device periodically freeze for 30-60 seconds when I tried it earlier, but it hasn't been a problem in this go-round. I kind of like it. It is definitely one way to get the most out of your ram.
I too receive better performance with a dynamic pagepool. What I'm wondering is whats everyone setting for they're file system filter cache?
nagle3092 said:
I too receive better performance with a dynamic pagepool. What I'm wondering is whats everyone setting for they're file system filter cache?
Click to expand...
Click to collapse
I have mine set at 800 (hex), but keep in mind that you can only change it before cooking the rom. I know that it appears in a lot of tweak programs, but changing it on the device post-flash doesn't work. The value is set in early boot, and it appears in the boot.hv which is in rom and can't be changed. It appears when you look at the registry with a registry editor, and you can change it, but by the time the sytem.hv is loaded it's too late for it to have any affect. Most roms have it disabled (set to 0). You can pull your boot.hv off your device and check the value on a pc with ceregeditor, but you can't change it. The same goes for the other file system caches. Hell, cachesize is an obsolete value, so trying to tweak it is doubly useless.
Hi everyone
I am in need of urgent Help
I upgraded my Motorola Milestone XT720 from 2.1 to 2.2 using Cincinatti Bell Manual.
I referred this
http://www.cincinnatibell.com/milestoneupgrade/#howtoupgrade
Now, After successful upgrade, I have some serious issues
1) My Camera's Flash isnt working. I cant enable it.
2) Performance is low
3) Lost MotoNav. How can I get it back?
4) Even if I keep Pattern lock, the slide lock do appears
5) Also, How I can merge duplicate contacts? like one contact has 3 numbers saved that are same..
Thankyou
1. im not sure. should work.
2. performance is low. you can overclock using milestone overclock if you are still rooted. however, if you are not the kind who maintains you phone everyday, i suggest you go back to 2.1 as its the most stable.
3. just google motonav apk
4. thats a flaw in the rom, cant be fixed. if you'd like to try out custom roms and maintain you phone like most of us do here, then go ahead. its very exciting lol
5. you can merge duplicate contacts by signing in to gmail on a computer, click contacts and just look around the buttons. its called "find and merge duplicate contacts" if im not wrong.
hope this helped
1) Tried all level best best to start flash... It didnt. Installed Sleekcamera apk.
2) Google find and merge always crashes and unable to do the action
3) Whats overclocking? Is it a self explanatory software??
4) Dont feel like going back to 2.1...Love App2SD
5) I also have some issues - cant play HD video and my internal video player isnt working to its full potential as I am unable o avi file. I feel, that there is codec problem, as Ringdriod isnt working too...
Chety said:
1) Tried all level best best to start flash... It didnt. Installed Sleekcamera apk.
2) Google find and merge always crashes and unable to do the action
3) Whats overclocking? Is it a self explanatory software??
4) Dont feel like going back to 2.1...Love App2SD
5) I also have some issues - cant play HD video and my internal video player isnt working to its full potential as I am unable o avi file. I feel, that there is codec problem, as Ringdriod isnt working too...
Click to expand...
Click to collapse
if you like to have apps on your sd, there's a more advanced way to have it. i think its better than android's own move apps to sd. many roms we have around here have app2ext automatically set if they detect any ext partitions on your sd card. it moves all user apps onto an ext partition on your sd card (you have to use a partition tool to make this ext partition).
overclocking is actually just controlling your cpu clock speeds. most of us overclock our phone because it sometimes get laggy if we use the stock speeds. theres an app that helps us overclock on the market called milestone overclock. please remember that you need to be rooted do these stuff.
for the camera, you might have hardware problems. i dont know. contacts you should try doing the find and merge duplicates again. i'll upload a pic to show you what it looks like.
i recommend mioze's cm6 rom if you ever want to play around with flashing stuff. the stablest i've tried so far. Cyanogenmod is very versatile lol. there are a lot of themes for this rom too, made by Sileshn our master themer. for the videos i dont think i can help. you could try mobo player from the market (i think?)
Thankyou - Sorry to buggin u again n again. One last help
if you like to have apps on your sd, there's a more advanced way to have it. i think its better than android's own move apps to sd. many roms we have around here have app2ext automatically set if they detect any ext partitions on your sd card. it moves all user apps onto an ext partition on your sd card (you have to use a partition tool to make this ext partition).
How do I do that..in a esy way? I saw I video and it was very complicated for guy like me. Any easy way like app or something??
overclocking is actually just controlling your cpu clock speeds. most of us overclock our phone because it sometimes get laggy if we use the stock speeds. theres an app that helps us overclock on the market called milestone overclock. please remember that you need to be rooted do these stuff.
Cool...Thanks.
for the camera, you might have hardware problems.
No bro. It used work fine before upgrade.
i dont know. contacts you should try doing the find and merge duplicates again. i'll upload a pic to show you what it looks like.
Thanks..but Gmail says Oops… the system encountered a problem (#101)...Maybe due to slow Internet(300kbps). Any app??
i recommend mioze's cm6 rom if you ever want to play around with flashing stuff. the stablest i've tried so far. Cyanogenmod is very versatile lol. there are a lot of themes for this rom too, made by Sileshn our master themer.
This is baffling for me. I feel like M not too smart for smartphone
for the videos i dont think i can help. you could try mobo player from the market (i think?)
Yup, I have that. Unable to to pay HD vid. It shows a lag of sound and vid. Tried soft decoding. Didnt work.
Couple of things about this. Are you still Rooted? CBW gave root permissions and then I think later in the tutorial they tell you how to give it back. Don't give it back. For what you want to do, you need to keep Root permission of your device.
Next are you comfortable with flashing custom ROMs and doing realtive non-beginner stuff on your phone. We can help you and walk you through stuff but unfortunately, there isn't an "app for that". If so, then here we go.
If you successfully were able to upgrade your phone, then you can do this. There are many custom ROMS in our forums that you can use. CM6, Hellmonger's, Kahl's V4, Bravo (wip) and CM7 (wip). I suggest CM6 or Kahl's V4 as they are stable enough for beginners to learn on. The have 99% working everything and what doesn't work, is either being fixed or there are already work-arounds. (search the development forums for these)
CBW's ROM doesn't have app2ext. It only has the native Froyo app2sd where you can go to settings>apps>pick your app>move to sd. This is not the same as App2ext or Link2sd. In these you have to partition your SDcard with an ext partition. Do you know how to partition your SD card? All the above ROMs do have the native Froyo app2sd, so if you don't know how to partition your SD card, that is fine too.
Answer those and then you can decide to move forward or not. It isn't hard and you don't have to be super smart to do it, although the more you read around, there are some seriously intelligent people in here. It is just from reading your posts above, how comfortable are you? You will not brick your phone and make it a paperweight, we can bring it back from the brink, if need be. We've done it before.
**Milestone Overclock is an app in the market (requires Root) that is free to download. Just download it and set it at preset 1000/66 and you'll definately seem a boost in performance.
**Google contacts. If merge doesn't work for you, go into google on PC and look at your contact and you may have some duplicates in there. When i first got it, i had 3 of everyone too. Also, go into your phone and go to settings>account/sync and see what is sycnhing. Side note: if you have a Google+ account, unsych that as everyone in your circles will be put on your phone and vice-versa.
**Moboplayer. I use this all the time and have no problem seeing HD vids. Might want to take another look at the preferences. It even says it on the thunmbnails that it is HD.
**Camera. If you don't like the the camera function, there are a few on the market (mostly paid though) that work well. I use Vignette, but there is Camera360 and I think one for LG too. If your flash isn't working though, that might be a hardware issue.
Figure out what you want to do with your phone (flash custom ROM or not) and we can help. If you already flashed the CBW upgrade, then you are really half-way there.
Also sorry for the manifesto sized response.
Hi
Actually thankyou for detailed resonse. I find it very helpful. But, M disappointed to tell, that in afternoon,I installed Moto-optimizer after I couldnt work on Motorola Overclock and Started the process at 800...and then, its only M logo which is showing up.
Will give it to service centre tomorrow and get back to 2.1. I hope, they are not ale to detect this s/w fault..
Will love to learn our SD card partition,
Chety said:
Hi
Actually thankyou for detailed resonse. I find it very helpful. But, M disappointed to tell, that in afternoon,I installed Moto-optimizer after I couldnt work on Motorola Overclock and Started the process at 800...and then, its only M logo which is showing up.
Will give it to service centre tomorrow and get back to 2.1. I hope, they are not ale to detect this s/w fault..
Will love to learn our SD card partition,
Click to expand...
Click to collapse
See this before you do the below. Easy read but might work for you instead of flashing back to 2.1.
Here is a recent troubleshoot that we fixed.
http://forum.xda-developers.com/showthread.php?t=1089148
No need to take back to service. We can get you back to stock pretty easily.
All you need is to download RSDlite on your computer, install it and run it.
Here are the .sbf's http://forum.xda-developers.com/showthread.php?t=953863
Here are the directions http://forum.xda-developers.com/showthread.php?t=753170 See first post. It's easy to do.
Has anyone tried this on the Infuse ?
[SCRIPT][19.9.2011] The Best RAM Optimization - Updated!
I also did the following.
Used Root Explorer, and Open & edit /system/build.prop, change dalvik.vm.heapsize= to 80m
Any one confirms this is great ?
Have not tried, might muck around with it later today after i finish my essay. Do you think his script will run on top of DynamicRAM's 99 tweaks? I know the supercharger script didn't play nice with it if you have both installed at the same time.
Didn't notice anything
hey ya'll watch this!!
If this is what I think it is then it is what dynamic rams script is based off of. If it is an init.d script then most likely the parameters that each changes that ate the same will new set to the last commands that runs setting it. Though both may run together it is gonna be mostly redundant. One script will mostly not be applied. Changing the name of the script will determine what runs first. I know the letter s and I think e are used for this but I don't know which is set to run first. Then the number sets the order after that.