Jump to content

craskman

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

0 Neutral

About craskman

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    Nexus One
  1. CIFS is now working perfectly. Thanks Paul. Paul, On more thing, I read somewhere that GN CPU is a dual core 1.5GHz and Google/Samsung have decided to underclock to 1.2GHz for smooth and battery reasons. If this is true, do you think we could have the 1.5 stock speed? (I don't mean overclock but get the full CPU potencial). CrK
  2. The same here. cifsmanager reboots and no joy:) Paul, is the ICS kernel complied using the process used for nexus one? Could we just get the cifs.ko module for instance? Thanks, crk
  3. Hi Guys, has been a while. Have anyone been successful on running any version of Android with this kernel? If not, which issues are you facing? CrK
  4. Hi Eduardo, It looks good, though I dont have time, I will definitely give it a spin this weekend. Hopefully the android experts out there will try to put android running on this kernel. Keep us updated and stick around ;) btw, can you 'finally' tell us where are you from? :P EDIT: btw, if on all this code, the wifi driver is the only thing missing, then we are safe :D EDIT2: You have included the zImage in the boot.rar file, I think that newbe5 can easily test this kernel on his honeycomb port directly. Let us know newbe5 :D EDIT3: I will update my git with your changes next weekend, unless someone step forward before me, please be my guest and let us know. CrK
  5. Nice progress. Can you describe how you manage to access the serial console? Give the steps or some sort of howto :D Thanks CrK
  6. Good, like your confidence :P Dumping the boot info to the screen/LCD is easy but we can't scroll up/down. Thats why I was looking for full serial support (like many other ARM devices) also for input. I have done a serial interface to my LG Blueray (arm5) and worked like charm. On vega (like on any arm boards) I also believe we should have a way of grabbing a Rx and Tx pins form somewhere. Maybe from the bottom connector, but I can't find the specification of this connector. Let me know if you find another alternative (can't find too much info in the internet about this) Regs, CrK
  7. Good work Eduardo. How are you going to test and debug? I tried a USB converter to serial, so I could get all boot info on a terminal app (like putty,.. to perform scroll up/down), but I think is not so that simple. Do you know any better way? Or anyone knows how to get the serial interface working on vega? CrK
  8. Corv, newby, Great work work, getting better every day. Just one little one for now, I have noticed that vega starts to lag badly, after multiple apps open and messing around. Actually, it reach a point where completely gets frozen. I was looking into the init.rc and I think there are few things wrong there, around task management. Some figures are too high and they do not correspond as expected. I extracted the boot/ramdisk and I changed the init.rc with similar values I am using with my N1. I didn't noticed more speed but I noticed that lags less and it is not getting frozen anymore. Here the lines I have changed: # Define the oom_adj values for the classes of processes that can be # killed by the kernel. These are used in ActivityManagerService. setprop ro.FOREGROUND_APP_ADJ 0 setprop ro.VISIBLE_APP_ADJ 1 setprop ro.PERCEPTIBLE_APP_ADJ 2 setprop ro.HEAVY_WEIGHT_APP_ADJ 3 setprop ro.SECONDARY_SERVER_ADJ 4 setprop ro.BACKUP_APP_ADJ 5 setprop ro.HOME_APP_ADJ 6 setprop ro.HIDDEN_APP_MIN_ADJ 7 setprop ro.EMPTY_APP_ADJ 15 # Define the memory thresholds at which the above process classes will # be killed. These numbers are in pages (4k). # These are currently tuned for tablets with approx 1GB RAM. setprop ro.FOREGROUND_APP_MEM 2048 setprop ro.VISIBLE_APP_MEM 3072 setprop ro.PERCEPTIBLE_APP_MEM 4096 setprop ro.HEAVY_WEIGHT_APP_MEM 4096 setprop ro.SECONDARY_SERVER_MEM 6144 setprop ro.BACKUP_APP_MEM 6144 setprop ro.HOME_APP_MEM 6144 setprop ro.HIDDEN_APP_MEM 7168 setprop ro.EMPTY_APP_MEM 8192 # Write value must be consistent with the above properties. # Note that the driver only supports 6 slots, so we have HOME_APP at the # same memory level as services. write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15 write /proc/sys/vm/overcommit_memory 1 write /proc/sys/vm/min_free_order_shift 4 write /sys/module/lowmemorykiller/parameters/minfree 2048,3072,4096,6144,7168,8192 All these 4 groups of attributes are related. Let me know if this helps. CrK
  9. Hi newby5, Just today I had a chance to try this rom. Looks really nice and promising. Maybe we don't need .36 kernel anymore. So, the main issues are the wifi, sdcard and sound. Have you tried to compile the ar6000 module with this kernel? or it is a dead end? Crk
  10. Yes me too. Eduardo can you share what you have done so far? Maybe github. I am still interested to know where are you from,.. your name only can be from PT or ES.. :unsure: Crk
  11. Eduardo, this sounds good and makes sense. My knowledge on linux kernels is,.. sort of,.. mess around and try. But the vega community with skills at this level are not huge. So I was trying to push a bit, specially after finding folio100 nearly working. EDIT: I also have the IT7260 datasheet text version, actually I counldn't find it anywhere, only on google cached data. Keep updating us, I will be doing the same. At least we might be able to exchange some experiences and hopefully with good results. I think there are good people on this community on android side, but not on kernels. Be in touch, this weekend im gonna try again. CrK btw, are you spanish or portuguese?
  12. Great news around here. At least we are moving forward. Thanks for helping Eduardo (portuguese or spanish? Im portuguese btw, so we shouldn't be that far, corvus as well). Eduardo, I got from 'somewhere' the datasheet for IT7260, including driver sample code, if you know more about i2c layer, you might me able to go further with this doc. At linux drivers level I don't know too much, basically I tried to port from .32 kernel and I made some changes because some linux APIs have changed from .32 to .36. I will have a look on your code and I will merge. Though my time is lacking atm. CrK
  13. Corvus, In order to see the boot process you need to flash a modified bootloader (unless you have serial ports/cable, then just plug it). I have attached the bootloader on the previous page of this thread. Also, check my git, I think being close but still some probs on porting some stuff to .36 kernel,.. and my time lacks to do this sort of things. Btw, i am using your rom with OC .32 kernel, nice speed. Would be great put that speed on vega with HC. CrK
  14. Ok, here is the [boot-bega.img] with .36 kernel and your ramdisk. boot_vega.img.zip
  15. Hi add, About your ramdisk, I didnt touch it, I just add the binaries [sh] and [busybox] in the folder /system/bin (on your image) attached are: zImage - kernel .36 boot-vega.img - kernel .36 with your ramdisk (EDIT: in the next post,.. no quote to attach here) Let me know if you are doing some progress. CrK zImage.zip
×
×
  • Create New...

Important Information

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