Guest Simon O Posted September 13, 2010 Report Posted September 13, 2010 I think we dont need flame over CC versus swap (az all), I recommend to stop it. Agree. Both Swap and Compcache can be added to the kernel. Then you can choose what to use.
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 Fibble, another question: which firmware and which Froyo version did you use?
Guest Azurren Posted September 13, 2010 Report Posted September 13, 2010 Agree. Both Swap and Compcache can be added to the kernel. Then you can choose what to use. Soooo.. How much swap ram can we give ourselves without being greedy? Are we talking about enough to obliterate the launcher closing and the sms bug or enough to turn our poor old pulses into rockets?!! :lol: (If every app you usually use is open in Ram then it would open almost instantly)
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 Remember - with Cupcake we had more of free RAM than we have with Eclair (and Froyo with Eclair partitioning) :lol: CC/Swap has nothing to do with partitioning of internal storage memory.
Guest Tom G Posted September 13, 2010 Report Posted September 13, 2010 It looks like this kernel has usb gadget support which means we could eventually port PSFreedom to our Pulse :) The 2.6.27 kernel had gadget support but I couldn't get it to work. The MSM72K driver was new in 2.6.27, so hopefully it is improved in 2.6.29. If that's as easy as enabling swap then I will :lol: One thing I noticed: WLAN crashes =/ WLAN works fine for me. MCR 1.7 uses 32 MB of compcache and it works well, so it is not a bad idea, i guess. I'm fairly sure none of the MCR roms have used compcache. Sadly I don't know how to compile kernels. Compcache definitely slows the phone down (think about it.. the already slow CPU has to compress ram every time it's written). Swap is much better for us. Infact most G1 users disable compcache. make ARCH=arm menuconfig change stuff make ARCH=arm CROSS_COMPILE=arm-eabi- If you do menuconfig without ARCH=arm it will do the config for x86, and then won't compile.
Guest McSpoon Posted September 13, 2010 Report Posted September 13, 2010 Does recompiling the kernel fix the ADB serial number bug? If you do 'adb devices' does it list the device as '??????' or does it now correctly show the serial number? When T-Mobile released the previous kernel source for cupcake that bug was fixed simply by recompiling the kernel. I'm hoping the same applies for this too.
Guest Simon O Posted September 13, 2010 Report Posted September 13, 2010 Soooo.. How much swap ram can we give ourselves without being greedy? Are we talking about enough to obliterate the launcher closing and the sms bug or enough to turn our poor old pulses into rockets?!! :lol: (If every app you usually use is open in Ram then it would open almost instantly) Swap should be as small as possible. 32mb is ideal.
Guest Simon O Posted September 13, 2010 Report Posted September 13, 2010 Fibble, another question: which firmware and which Froyo version did you use? Froyo 0.51
Guest Simon O Posted September 13, 2010 Report Posted September 13, 2010 Does recompiling the kernel fix the ADB serial number bug? No
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 Froyo 0.51 Same here, WiFi works with new kernel
Guest McSpoon Posted September 13, 2010 Report Posted September 13, 2010 No Damn. Hopefully we might find a fix for the ADB serial number bug by comparing the old and new kernels.
Guest Tom G Posted September 13, 2010 Report Posted September 13, 2010 Damn. Hopefully we might find a fix for the ADB serial number bug by comparing the old and new kernels. Hows that going to help? Didn't the old one do it as well.
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 (edited) I'm fairly sure none of the MCR roms have used compcache. I definitely know that at least MCR 1.7 does have compcache, I even played with trying different CC sizes, BTW the fact that it contains CC is listed in the MCR topic's first post. If you used MCR, and didn't even realize that it is compcached means that it is fast. Edit: http://android.modaco.com/content/t-mobile...online-kitchen/ Edited September 13, 2010 by gusthy
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 (edited) Cache in work: (The picture is a bit funnyi, because during shake for screenshot, it rotated) Edited September 13, 2010 by gusthy
Guest Fusion0306 Posted September 13, 2010 Report Posted September 13, 2010 Cache in work: (The picture is a bit funnyi, because during shake for screenshot, it rotated) Looks nice :lol:
Guest McSpoon Posted September 13, 2010 Report Posted September 13, 2010 Hows that going to help? Didn't the old one do it as well. Yes, the original stock kernel had that bug too. But Paul's MCR roms fixed it. Simply because he had recompiled the kernel source. Martinbrook was the first to get that initial code release to compile and he soon discovered ADB was getting the serial id, as he reported in this ancient thread. I'm pretty sure the other QMR release of that code also had the issue fixed too. So we might be able to identify what is causing it just by comparing against the cupcake driver.
Guest starkos Posted September 13, 2010 Report Posted September 13, 2010 I've also managed to get swap (32mb) and ext3 support working, & I've gotta say so far it's looking pretty good for multitasking lol :lol: !
Guest igor_anta Posted September 13, 2010 Report Posted September 13, 2010 I've also managed to get swap (32mb) and ext3 support working, & I've gotta say so far it's looking pretty good for multitasking lol :lol: ! Can you upload it in a flashable zip so others can use it?
Guest starkos Posted September 13, 2010 Report Posted September 13, 2010 Can you upload it in a flashable zip so others can use it? I would but most people here use flib's rom which is slightly different to the one I use with regards to things like A2SD/init.rc entries. So it may be best to wait until flib releases an update.zip containing just the new boot.img and swap script...
Guest gusthy Posted September 13, 2010 Report Posted September 13, 2010 I've also managed to get swap (32mb) and ext3 support working, & I've gotta say so far it's looking pretty good for multitasking lol :) ! two questions: - what do we expect of ext3? - did you use swapfile or swap partition? Be brave, I added 96megs of swap and runs looooots of apps :lol:
Guest igor_anta Posted September 13, 2010 Report Posted September 13, 2010 I would but most people here use flib's rom which is slightly different to the one I use with regards to things like A2SD/init.rc entries. So it may be best to wait until flib releases an update.zip containing just the new boot.img and swap script... Oh, in that case you right, it would cause chaos:) Cheers!
Guest Stevos Posted September 13, 2010 Report Posted September 13, 2010 (edited) Be brave, I added 96megs of swap and runs looooots of apps :lol: This might be the best answer to the SMS bug. I'm starting to get in trouble with my GF for "ignoring" her messages... Edited September 13, 2010 by Stevos
Guest starkos Posted September 13, 2010 Report Posted September 13, 2010 two questions: - what do we expect of ext3? - did you use swapfile or swap partition? Be brave, I added 96megs of swap and runs looooots of apps :lol: I believe ext3/4 have journalling where as ext2 does not? I used a swap partition, & I reckon 96mb would be overkill and may actually do more harm than good as the system will probably slow down with too much in swap
Guest Simon O Posted September 14, 2010 Report Posted September 14, 2010 I would but most people here use flib's rom which is slightly different to the one I use with regards to things like A2SD/init.rc entries. So it may be best to wait until flib releases an update.zip containing just the new boot.img and swap script... Not really. Just unpack the boot.img and replace the kernel with the new one you compiled.
Guest Simon O Posted September 14, 2010 Report Posted September 14, 2010 (edited) Swap works. a2sd check [ ] Apps2SD is launching... [ ] GetProp Command = /system/bin/toolbox getprop [ ] SetProp Command = /system/bin/toolbox setprop [ ] Mount Point = /sd-ext [ ] Starting Apps2SD Check Program. [ ] Searching for Mount Point... [*] Mount point /sd-ext located. [ ] Checking for ext partition Darktremor Apps2SD Status Report =============================================================== Legend: [*]=Setting is correct [!]=Setting is correct, but not optimal. [X]=Setting is incorrect and needs to be fixed. =============================================================== Partition - [*] Mounted as EXT2 Apps - [ ] Linked to SD Card. [ ] No Apps2SD Flag File not found. [*] Programs run from SD card To run from internal storage, type a2sd remove Private Apps - [ ] Linked to SD Card. [ ] No Apps2SD Flag File not found. [*] Private Programs run from SD card To run from internal storage, type a2sd remove Dalvik Cache - [ ] Regular directory. [ ] Dalvik to /cache flag file not found. [ ] Dalvik to SD flag file not found. [*] Dalvik runs from Int. Storage. To run from SD card, type a2sd cachesd. To run from /cache partition, type a2sd cachepart. Swap - [ ] Partition present. [ ] No Swap flag file not found. [*] Swap starts. To deactivate swap, type a2sd noswap ZipAlign - [*] Not running at boot. To activate it, type a2sd zipalign Dalvik Heap(MB)- [*] Set to Default. Low Memory Killer Settings- [*] 1536,2048,4096,5120,5632,6144 Note: Values are in pages. 1 page = 4KB memory. Values represent the following: 1st number = Foreground App 2nd number = Visible App 3rd number = Secondary Server 4th number = Hidden App 5th number = Content Provider 6th number = Empty App Property Patch - [*] File System Ready property found. [*] Boot image init.rc patched. # cat /proc/swaps cat /proc/swaps Filename Type Size Used Priority /dev/block/mmcblk0p3 partition 31544 24608 -1 Now to try and get compcache working. Edited September 14, 2010 by flibblesan
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now