Jump to content

morfic

Members
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

0 Neutral

About morfic

  • Rank
    Newbie
  • Birthday 10/09/1972

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Location
    SATX
  • Your Current Device(s)
    Vibrant, Liquid, Behold
  1. Someone asked for a version for the modaco custom rom r3 I'll build one if I know what the rom needs in initrd to work. Later when this is on github Paul can just grab it from there.
  2. This Kernel is for the rooted stock rom. (<---Disclaimer because i will build a kernel for Sombionix' optimized Nexus S ROM after hitting SUBMIT, don't want there to be confusion later) http://dl.dropbox.com/u/16615951/zImage http://dl.dropbox.com/u/16615951/bcm4329.ko http://dl.dropbox.com/u/16615951/fastboot you may notice there is no boot.img, good, we don't need one right now, fastboot can do it on the fly just fine. (This means there won't be a update.zip for a while) First backup your modules, do this only once to keep your stock modules around. mkdir ~/nexussmodules cd ~/nexussmodules adb pull /system/modules/ . cd .. The following you can use to flash this and any others i might put here until mkbootimg agrees with fastboot. #!/bin/bash adb push ~/Downloads/bcm4329.ko /system/modules/ adb shell sync adb reboot bootloader sleep 15 ~/bin/fastboot -b 0x30000000 -n 4096 boot ~/Downloads/zImage Pay attention to where the module and kernel are loaded from and where fastboot is called from, this is for linux hosts with adb, fastboot you can grab from the links above. Note: This boots the kernel, it does NOT flash it. When you reboot, you are on stock kernel, push back your backed up bcm4329.ko if you do not like the kernel. If you want to keep it (and why not?) change boot to flash boot in the fastboot line above. Add this to build.prop: windowsmgr.max_events_per_sec=68 benchmark with governor set to "performance" before and after if you want comparable results, i forgot nexus s has default governor "ondemand", which makes results impossible to compare to a Vibrant with "conservative" governor. This kernel on Nexus S @1.2GHz already outperformed my DoW14 for Vibrant on Nero3 rom in nenamark benchmark. neocore maxes out at 65fps, just like on Vibrant (which makes the nenamark results easier to interpret, neocore is a nice and quick way to confirm i am not limited to 56fps however) Enjoy (BTW, this is not a finished product, however, some may think it is worth flashing, not just booting for a giggle)
  3. morfic

    now after seeing this!!! non development

    I had a lagfix and loved it, thought there was an issue with the phone (second wiping before returning it fixed the "not orienting issue" btw.) and on the replacement decided to just root and not rerun the lagfix script, and hope the vm tweaks are good enough, well obviously they can't fix what a crappy kernel and a crappier slow ®FS cause, so the VM tweaks can only minimize the amounts of data written, thus leading to smaller less frequent stalls. Long story short, ignoring how the phone acts while installing apps (or otherwise high amounts of IO) and being at a point where app installs do not happen often, i love the phone ( i totally ignore the GPS until i get a fix from tmo.) On a day to day use of the phone, i love it, the screen, the battery that does not drain at my work place where i have shitty reception (imagine edge/noreception switches and mt3g and liquid especially die a quick death and after coming home i charge it (speak 12-13hours), vibrant i come home and use with screen on for a few more hours), the battery life that is awesome until i drag the phone around the house constantly using www/SNS/mail and finish the battery off in ~16-17 hours. The UI response when switching between apps or screens (currently back on my "i think launcher pro is snappier than adw" trip) I am upset about the low quality rom Samsung has shipped on a finished product, sure, it would make a nice rom for a tester, who would have to be testing blindfolded to not notice the lag and gps issues and wonky reception and battery indicators (i love seeing ~75% on the notification bar, doesn't help if the actual percentage is long below that), and who decided twlauncher itself should not orient? (it's how i missed orientation gets fixed by wiping, i only tested on twlauncher after wiping and had no memory of "it just doesnt orient on homescreen, stupid" ;) ) YEs this is much longer than i thought it would be, the Vibrant is an amazing phone once you start looking past the buzz kill first moment, after charging, "they really shipped this like that?" findings and start using it in your normal day to day life, and as long as i do not become another "behold victim" in the end, i will keep saying it's a worthy phone. now let's go and request tmo/att/* demand samsung increase their QA department staff, and do not copy the Acer field testing recruiting model, and instead ensure they only get high quality field testers. (we can pretend they care and feel good for a moment or two!) I'll enjoy 2.2 for a long time before i worry about looking who made a cm6+tw rom, to test after backup :)
  4. morfic

    Gyroscope

    Great to find this and other threads like it i thought, i run the tool, and i get this: # sensorcalibutil_yamaha ===================================== Sensor Calibration Utilities Copyright © 2009 Yamaha Corporation ===================================== Starting calibration utilities... access: Stale NFS file handle msmachdep_Init failed calibration utilities failed When i try to use a compass app, or the *#0*# sensors app, i always see this in logcat: I/ActivityManager( 2255): Starting activity: Intent { cmp=com.mictale.gpsessentials/.compass.CompassActivity } E/SensorManager( 3332): registerListener 1:MS-3C Magnetic Sensor delay:120 E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. giving up... E/SensorManager( 3332): =======>>>Sensor Thread RUNNING <<<======== E/SensorManager( 3332): registerListener: [email protected] E/SensorManager( 3332): registerListener 0:SMB380 delay:120 E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying... E/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. giving up... E/SensorManager( 3332): registerListener: [email protected] D/dalvikvm( 3332): GC freed 1200 objects / 63336 bytes in 40ms I/ActivityManager( 2255): Displayed activity com.mictale.gpsessentials/.compass.CompassActivity: 2603 ms (total 4577 ms) W/PowerManagerService( 2255): Timer 0x7->0x3|0x3 I/PowerManagerService( 2255): ULight 7->3 f0 D/dalvikvm( 2707): GC freed 1085 objects / 49960 bytes in 119ms the yamaha sensor server is running logcat has this when booting the machine: D/SensorManager( 2256): ====>>>>>Num Sensor: 1 D/SensorManager( 2256): found sensor: SMB380, handle=0 D/SensorManager( 2256): ====>>>>>Num Sensor: 2 D/SensorManager( 2256): found sensor: MS-3C Magnetic Sensor, handle=1 D/SensorManager( 2256): ====>>>>>Num Sensor: 3 D/SensorManager( 2256): found sensor: MS-3C Orientation Sensor, handle=2 D/SensorManager( 2256): ====>>>>>Num Sensor: 4 D/SensorManager( 2256): found sensor: gp2a Proximity Sensor, handle=7 D/SensorManager( 2256): ====>>>>>Num Sensor: 0 D/SensorManager( 2256): found sensor: gp2a Light Sensor, handle=4 E/SensorManager( 2256): ####### akmd2 started!!! using *#0*# the proximity sensor works then later: D/NetworkConnectivityListener( 2340): onReceive(): mNetworkInfo=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true mOtherNetworkInfo = [none] m$ I/LogsProvider( 2466): onAccountsUpdated: Delete SNS log : spType = 0 D/PowerManagerService( 2256): bootCompleted E/SensorManager( 2256): registerListener 0:SMB380 delay:240 E/Ms3CSensor( 2219): msmachdep_LoadGsOffset failed[-1] W/Ms3CSensor( 2219): Ms3CSensor::initialize() failed. retrying... I/LogsProvider( 2466): onAccountsUpdated: Delete SNS log : spType = 1 I can't help but wonder if the sensor calibration tool would fix this if it ran, but i have no idea, what stale "NFS" file it complains about. so it looks like it should work, but then it just doesn't. I wiped earlier today then did a nandroid restore when nothing changed after wiping. If noone has a "dude, you suck googling, follow this [link], it's tell you" i might have to go request Vibrant #3..... Thanks in advance for looking, Daniel
  5. morfic

    Livehome

    A nice way to put an end to the same old launcher apps. Try it, select one of the transitions you like, I am a fan of the book style transition. And then notice all this does not even come at the cost of being slower than adw or lp. Scrollable widget support is almost done. Most other things you would expect are there. Updated often. A great launcher for a great phone.
  6. morfic

    XFJM6 Samsung's fixed lag? GPS?

    Nice, not less than stock, unlike JP* were, thanks for the info.
  7. morfic

    XFJM6 Samsung's fixed lag? GPS?

    Can we afford choosing any file system? Because if the phone's controller does not take care of wear leveling, then I would not choose a filesystem that is not meant for flash memory like typically used for nand/mtd partitions. While I am not shy using ext2 on my removable sdcard, I am not that brave with internal partitions. Noone fixes what ain't broken, but when you had to tinker to be happy, then you will wonder what a new rom will be like with some tinkering. And if samsung does not drop rfs, we can't not do something about it. 1800 in quadrant without the possibility for double caching in loopmount fix.....i expect that from samsung if they can make it smooth too. That's why the interest in this rom . :P vicariously at least
  8. morfic

    XFJM6 Samsung's fixed lag? GPS?

    Switching from adw to launcher pro made a nice difference for me. Livehome just has some eyecandy that's fun to see. LauncherPro though performance wise, haven't used adw in a while now, maybe I should retry. Ever do a ' cat /proc/meminfo' on those roms?
  9. morfic

    XFJM6 Samsung's fixed lag? GPS?

    In simple words, how do stock rom with fixes and this one compare. Considering I am so happy with my phone right now that I do not even bother with any roms or kernels, I wonder how the "much snappier" might quantify. I'm pretty sure it's snappiest with launcher pro, but livehome with it's "turning the page" effect for home screens is just too tempting to ignore. I guess I wonder if there is any benefit in these roms for me other than being 2.2 This way I don't have to admit I flashed the rom just to tinker :P
  10. morfic

    XFJM6 Samsung's fixed lag? GPS?

    /proc/sys/vm/ has the dirty ratio and cache pressure. Just cat them. For the slice idle I'd have to paste from desktop later, it's a longer path I wouldn't want to get wrong. Other was /proc/meminfo Getting rid of rfs sounds good, sounds like they tried for a "good FAT"
  11. morfic

    XFJM6 Samsung's fixed lag? GPS?

    Still happy with gps? No lag yet? What do dirty_ratio and vfs_cache_pressure default to on this rom? What is slice_idle default value for cfq? cat /proc/meminfo shows what mem total? Stock is around 333mb, doing the lazy 1k instead of 1024 math. Thanks, Daniel
  12. I can't say I have seen this in a while. Went back to deadline, fixed a typo that kept cache pressure from being set. Dirty Ratio still at 5% #!/system/bin/sh if [ "$(/system/xbin/busybox id -u)" == "0" ]; then for f in mmcblk0 mmcblk1 stl3 stl9 stl10 stl11; do echo deadline > /sys/block/$f/queue/scheduler; done echo 90 > /proc/sys/vm/vfs_cache_pressure echo 5 > /proc/sys/vm/dirty_ratio echo -e "Switched to deadline\n" else echo -e "Getting root privileges\n" su<$0 fi [/codebox] Is what I run right now. [codebox]mkdir /data/ext2data; mount -w -o noatime,nodiratime,errors=continue -t ext2 /dev/block/mmcblk1p2 /data/ext2data; for f in mmcblk0 mmcblk1 stl3 stl9 stl10 stl11; do echo anticipatory > /sys/block/$f/queue/scheduler; done userinit.sh Yes, still executing deadline script through sl4a
  13. I am still using that loop in userinit.h, setting anticipatory, but then rather soon run my deadline script, but been so busy with work, i didn't get to much else. Rather than the loop mounted ext2 on rfs, i mount mmcblk1p2 with symlinks to the directories on that mount point. What made things blow up on the xt2 move was simply that the mount i have wants options in a particular order, while i wrote them the order i would use on my desktop, turns out that does not fly :huh:, no more wiping Vibrant to get back into OS, when the mount fails and there is no /data/data and rest, it's just stuck. My little spare time was consumed on building a RTAI kernel for my desktop, since i wanted to test my desktop's latencies, to see how something like this would fare as PC for the cnc control we are going to use, funny thing is, the newer the cpu, the worse all the power savings and frequency scaling and deep sleep make the hardware for a realtime system, Would like to have some time to evaluate /proc/sys/vm/vfs_cache_pressure some more. Btw, using the ext2 on my class6 instead of the loop mounted /data/data i get a slightly slower quadrant score, makes me wonder if the loop mounted fix gets some double caching during the benchmark (shouldn't but seems that way) If linux is on your desktop, keep an eye on this: http://lkml.org/lkml/2010/8/26/327 And people need to stop calling the BFS scheduler names, there was one bad revision, that did get picked up and used on a cm4.something release, ever since people are split about it, bfs on a cell phone is amazing.....if someone could build us a recent kernel for the vibrant and includes bfs, i am pretty confident we would like it. for the mt3g, i could always build a bfs kernel for cm, even when he stopped including it, later was easier to just d/l one of the many offerings, long story short, i MISS having bfs on my phone. If you run 2.6.35 vanilla, go patch it and build it with -ck1 (are larger patch set from the guy who made bfs) and then try your system again, of course if you tell me you never noticed any UI lags or general poor interactivity, then you will probably not see it benefit you much. Side note: Benchmarks are actually bad, because interactivity most of the time works against throughput. So perhaps i end up editing the quadrant line up there out after a while ;)
  14. morfic

    Liquid > i9k

    Good deal, My Liquid has around 160MB for linux, my vibrant has about 330mb, which counts most for me, as it keeps more apps running, instead of killing/starting all the time. GPS on my Vibrant is whack, even after all the fixes, and when not plugged into usb, it can show me drive one block to left or right. Most of the time i can get locks down to 10m, still once in a while for no apparent reason it's just way off. Never been of on the liquid. And still, i love the vibrant, not so much the Liquid, Acer had some nice potential, restarting apps on liquid are not my cup of tea. Is cyanogenmod important to you? Doesn't look hot for galaxy s yet, does it? Oh, and battery life is better, much better, even when i never tell it to "use 2g only", of course i use it much mre, so screen is on more and thus at end of day battery is still down to 15%, but it's after much much more use out of it than i could ever get out of the liquid. Just in case "tomorrow" hasn't happened yet, else, enjoy the vibrant.
  15. Con Kolivas suggested noop for having the least through put. As it would require less cpu time during a stall. The stalls have to do with the (linux) VM (don't confuse it with a java VM), you can read about dirty pages and write back caching. And the info will be much more accurate than when I rephrase it. I lowered the dirty ratio to 5% of the ram, then the stall could be only half as bad as with the default 10% set. The reason is the slow writes on the /data partition, which exposes this possible stall condition in the kernel. The loop mount fix speeds up the physical writes. If you run linux on your desktop there are similar things you can tweak, stemming from most defaults being wrong for an interactive desktop. A phone is much like a desktop with slow slow disks. I encourage some reading in dirty pages, write back caching, swappiness, linux vm for a good understanding. Swappiness to default to 60 is fun, should be around 5, luckily there is no swap in our android phones. What we want is vm improvements to make it into 2.6.36 and to get that for our phones. Alternatively, some one who can build a vibrant kernel to patch it with bfs for 2.6.35 and build us that.
×

Important Information

By using this site, you agree to our Terms of Use.