• Content count

  • Joined

  • Last visited

Community Reputation

17 Good

About ipaq3870

  • Rank
  1. So much work, so little time! I'll be offline until Jul real soon. The code is already in place, I'm just not sure if I have time to release a 5.0 build. Tentative changelog: Screen calibration: can calibrate and adjust to one's own device - see special instructions. Switch off touch panel on screen blanks - phone no longer wakes up twice when pressing hold button. Also "screen turned off delay" of the lockscreen can now be set to anything - it was having accidental wakeup problems. 24bpp framebuffer now reports itself as 32bpp as expected by Android, though the hardware is still 24bpp. Screenshot apps such as AndroSS, and console apps such as Live Logcat now work properly in 24bpp. Vibrator now vibrates at 175Hz (strong) and is independent of CPU or AHB frequencies User selectable vibrator strength via sysfs file: /sys/class/timed_output/vibrator/freq
  2. Finally someone succeeded. Nice.
  3. It still baffles me as to why an Andriod reinstallation would work. It's not uncommon for me to switch kernels and modules 20-30 times a day if I am doing development, and still yet to encounter any gsm/wifi problems like you guys described. Anyway, good to know it works for you.
  4. Good to know! What exactly you have done to make Wifi work? Did you reinstall the whole OS via the beta2 installer, or just the kernel part? What other things you have done? Perhaps these are useful info for others.
  5. I applaud your persistence. But you still must have typed something wrong. Typing serious commands in terminal is really a challenge and a PITA, I know. I attach the script so that you don't have to type. 1. Download the ke.txt 2. Rename it to ke (without the extension) 3. Put it in say /ke of your phone 4. Do a "chmod +x /ke" 5. Run "su" 6. Disconnect USB 7. Run "/ke" See if this works. ke.txt
  6. Touch? IIRC, I didn't touch the touch part of the kernel, i.e. the touch screen driver. Did you try any prior version(s) of my kernel and encounter this issue? As far as I know, there are calibration data hardcoded in s3c-ts.c. You may want to take a look at it. As for GPS, I think I didn't touch that as well, and the problem seems stemmed back at least from at least cm b2. I guess you can find your answer in the stopped b2 thread. I have the feeling that it's an Android build problem though I didn't really look at it.
  7. These are shell programming commands - be very careful about the quotes: Double quote --> " (?123 key then c) Back quote --> ` (?123 key then ALT key then 2) You pasted the command correctly in this post but apparently not in the command terminal. There are non-breaking double quote-back quote or back quote-double quote sequences. And there's no dot between getprop and haret.kernel as well. Also remember to unplug USB before trying.
  8. Did you setprop haret.kernel properly, and chown/chmod properly? You can verify it by running the manual script. If it does not work and just spits out error messages, then recheck steps 1 - 6. If it does work via manual script but not in Android UI, check steps 9 - 11. If the Android UI hangs at rebooting phone, check steps 7 - 8.
  9. It's a known issue already stated in the Caveat section. Seems the vibrator somehow depends on the max speed of your CPU. EDIT: Okay, it's not difficult to fix - just borrowed some code from the spica forum. :D Download and replaced the original vibrator.ko in /modules/ and you are set. Also a bonus feature: vibration strength can be user tuned via this sysfs parameter /sys/devices/virtual/timed_output/vibrator/freq. This hotfix is from commit 5e743b13 hacked to be used in official 4.0 builds, and will be integrated when a new major release is out. vibrator-5e743b13.zip
  10. Depending on how you executed the zr script, it may or may not have successfully unmounted your old swap partition on the SD card. But it really doesn't matter - as Z-Ram has priority over it and it's almost never used even when you have 2 swap spaces active. If you want to make sure you are not using the old swap, do a "swapoff -a" in terminal manually, and check with the free command again.
  11. I have already edited the script few days ago to silence the error. Go get the latest one.
  12. Arghhh! Finally finished writing the documentation of 4.0 sans the development bits... wasted so much time wrangling with modaco's Wysiwyg editor :angry: Will take a much needed rest....
  13. Kexec a.k.a. Never See WinMo Again (Almost) These are the files needed for using kexec - for kernel 4.0 or above. See first post for details. framework.part1.rar framework.part2.rar libc.zip
  14. 4.0 Even more memory CPU: 667Mhz / AHB: 166Mhz / 160MB free memory / 24bpp display Build No: a3b8d7f-951 Note: always watch first post for latest builds in case this build has been superseded. 4.0-ae49c12-951-667mhz-166mhz-160mb-24bpp.part1.rar 4.0-ae49c12-951-667mhz-166mhz-160mb-24bpp.part2.rar

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.