Jump to content

wooshy1

Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

5 Neutral

About wooshy1

  • Rank
    Newbie

Profile Information

  • Location
    UK
  • Your Current Device(s)
    Nexus One, Advent Vega
  1. my changes to the gpu ram left the github unbootable with the old kernel command line please check out my github for newest commit. I will add the new touchscreen driver shortly. edit: updated TS driver now Eduardo I did notice that in the orginal .32 TS driver if the egalax driver was not loaded it disabled something on the tegra-i2c and if the IT7260 driver was loaded it enabled a NOSTOP mode on the tegra-i2c driver is this function required? or is this surplus to requirement with the new driver?
  2. This is a good idea thanks for the tip on the gpu memory usage cat /sys/kernel/debug/nvmap/generic-0/clients It seems the stock browser uses loads of gpu ram in most cases I have seen it using in excess of 140MB on its own.
  3. I have been experimenting with the 32bit depth for a while now on the .36 kernel and this is the only way to stabilise the stock browser on honeycomb obviously as you have already mentioned this significantly increase the video/image quality however you must also increase the amount of gpu ram. I have currently got it set at 184mb with 5mb fb1 and 8mb hdmi 720p fb which is stable I think we may be able to reduce it a little more yet. regarding gpu ram I looked at the xoom, tf and streak 7 kernels to see how they have done it. the xoom kernel goes about gpu ram by using the low memory for main system ram and the himem for gpu ram giving it 512mb for main ram and 512mb for gpu ram it also has 8mb for fb1 and 16mb for 1080p hdmi fb. the tf kernel has 768mb for main ram and 256mb for gpu ram and the same as the xoom for both the framebuffers. both the tf kernel and xoom kernel have 32bit depth on internal and hdmi fb's. This is ok if you have 1gb of ram which we do NOT so I looked to the dell streak 7 kernel which is a ventanna tablet with 512mb ram and an official honeycomb update. the way dell have achieved this is by cheating in my opinion ;) they have reduced the screen resolution to 800x480 used 16bit depth for internal fb and 24bit depth for hdmi. All this allows the streak to have 128mb gpu ram leaving 384mb for system ram 2mb for fb1 and strangely only 2mb for hdmi even though at 24bit depth and 720p it should need a bigger fb than this. With this tied together with the android low memory killer settings allows honeycomb to run very well if a little sluggish at times on the streak. now comes the problem I cannot get the initlogo.rle to display correctly with the 32bit depth enabled the image is displayed with garbled colours and it is display twice in the top half of the screen and the bottom half is just black and white lines. I have tried using a black image and an image produced at 32bit depth to no avail. Any pointers here would be helpful. I assume the frameworks in android are optimized for either 16bit depth or 32bit depth that is why when 32bit depth is enabled alot of problems go away and considering we are essentially emulating a xoom as both the ICS build and honeycomb are based on xoom/tf targets. Also I did notice that before nvidia introduced the seperate dc/fb driver they allowed the lcd resolution to be different from the framebuffer resolution and the driver would stretch it to fill the screen, I did try to get this working in the new driver but I do not think they have fully implemented the functionality. again any pointers on the is would be great. great work cass and eduardo I really cant wait to have ago with your latest efforts for both the .39 kernel and ICS. please correct me if I am wrong on any of the above. ok this has been a long post but just one more thing. Cass will you be publishing the device profile for ICS so anyone can build from aosp when you have got it working I would like to give it ago but my build keeps failing in libmedia cant remember the error for now but was just wondering? thanks again guys/gals your work is much appreciated.
  4. It is in my github it is just a kernel config option to be set at kernel build time. https://github.com/wooshy1/kernel_2.6.36_nvidia_base
  5. This is not defined as you can see /**/ so that is why I havent re-enabled it in the .36 kernel. The main difference regarding the two kernels is the fact the .39 has a kernel config option that .36 did not have I have set this in my last update to github. I have pm'd you about this Aero. CONFIG_INPUT_BMA150_I2C=y[/CODE] tells BMA150 driver to output i2c instead of raw iirc regards wooshy1
  6. Just out of interest what does the following command produce cat /proc/cmdline
  7. Ok so I have noticed a few people posting about using a USB GPS dongle with the Vega so I thought I'd give it a go. First off DO NOT attempt this if 1: you are faint hearted 2: you do not know how to use a soldering iron. 3: you do not know how to build and deploy your own kernel. I am not responsible for you destroying your Vega in the process of installing this mod. No Advent Vega's were harmed in this modification. Check that the USB GPS dongle you buy has a linux driver. The one I have used is a globalsat nd-100s which simply renders itself as a pl2303 based usb to serial adaptor which is well supported in linux. I have installed my GPS dongle inside the Vega and will show you below how I did it. If you just wish to use a USB GPS Dongle externally with the USB port in HOST mode you can skip the hardware section. Hardware Preparation: First off follow either of the following excellent posts to get yourself a spare internal USB port. http://android.modac...al-camera-port/ http://android.modac...hub-and-3g-mod/ For the GPS to work correctly ie be able to get a satellite fix it must be mounted down the one side of the display and then shielded. As you can see in the images below you will need to remove a section of plastic (using a hot knife) big enough for the ceramic patch antenna, I also scratched away some of the black paint on the back of the glass so you can see the GPS LED from the front of the tablet to check if it has locked out. You can also see the plain kitchen foil I used to shield the GPS module from the lcd screen (this is important as without this shield there is too much interference to get a satellite fix). Finally the modification to the rear panel note I removed the middle retaining leg. My rear panel doesnt quite fit as flush as it did originally it only protrudes about 0.5-1.0mm in the centre. This could be because in my haste to remove the usb plug from the GPS module I pulled off the data- pad so had to solder to the secondary connector on the back of the GPS pcb . You have been warned so be careful. Software preparation: As already stated the GPS dongle I am using uses the pl2303 usb to serial adaptor driver if your chosen dongle differs you will need to add the relevent driver (if not already in the kernel) and the config option. The next step is to build support for the pl2303 usb-to-serial adaptor into the kernel simply download the kernel relevant to your rom in my case I am using the excellent HoneyIce 3.2.7 by Aero for which the kernel is in my github https://github.com/w....36_nvidia_base then add CONFIG_USB_SERIAL_PL2303=y to the .config file either by hand editing or menuconfig then build the kernel. if your GPS device is fitted internally like mine add this service usbgps /system/xbin/busybox stty -F /dev/ttyUSB0 ispeed 4800 class core oneshot setprop ro.kernel.android.gps ttyUSB0 to the init.rc in your ramdisk (again this speed is dependent on the GPS device you use) Then deploy your new kernel, ramdisk and wifi drivers to the tablet. If you are using your GPS externally via the USB port in Host mode, simply get a terminal app up and as su enter the following: stty -F /dev/ttyUSB0 ispeed 4800 followed by setprop ro.kernel.android.gps ttyUSB0 This should be all that is required however I could not get the libgps provided by ejtagle in the kernel thread to work so I did the following download and install UsbGPS4Droid_alpha3.apk from http://forum.xda-dev...=1143329&page=2 it means you must run this mock location app whenever you want to use the GPS. Maybe when I get some more time I will get the libgps working so that this app is not needed but for the moment it works and I have a GPS lock and have used it with google maps to navigate round my local area. Hope this helps others who are thinking about this modification. Credits for this must go to ejtagle, rebel1 and anybody else who helped in the development of the 2.6.36 kernel rose840, windin101 and richardmlea for the internel usb hub mod herbert1 for the Usb4GPSDroid app. Aero for HoneyIce 3.2.7 Anybody else I have forgot to mention.
  8. first off thanks to rose and windin for posting this o/ I have just done this mod all went as expected and I must say those wires are very small on the camera cable :o. I have added a 4GB usb stick and a bluetooth dongle (as the built in one is terrible) plus wiring in the builtin camera, so I now have only one usb port free I may add gps later if I can fit it in but I have no real need as my nexus one streams gps over bluetooth (which now works correctly with the new bluetooth dongle I fitted :) ). The only thing I would add is that for the camera to work you need to leave the yellow wire connected to the camera as this is what is used by the tegra soc to power the camera board up and down. p.s If someone wanted to add gps aswell providing the gps hardware was supported by the kernel you may need a wrapper to pass the gps data to android
  9. I dont have it compiled lol run out of disk space :-O about half way through the build
  10. Builds ok but I am unable to test the zimage as I dont have my vega at the moment :( away for repair. https://github.com/wooshy1/android-tegra-nv-2.6.39
  11. As far as I can see no as deep idle is a feature of the nexus s cpu this line in vega_postboot.sh keeps the camera on or shuts it off in suspend #DISABLE CAMERA in Suspend echo 0 > /sys/devices/platform/shuttle-pm-camera/keep_on_in_suspend this is working for me I dont have any blue led in suspend however I do have to open the camera app and then close it again before going to suspend I assume this starts the camera then shuts it back down as the kernel leaves the camera power on at boot. I am also getting the reboot when trying to record a video with bluetooth enabled nothing shows up in logcat and cant get to dmesg because this is a kernel panic but I have not got any further than this at the moment. regarding overclocking agree with Eduardo on this there is too much heat generated at 1.4ghz as the core has to be at least 50mv higher than the cpu 1.2ghz maybe the only safe maximum.
  12. rebel1 already included this fix https://github.com/wooshy1/kernel_2.6.36_nvidia_base/commit/6263da5256536d1a74e511c7001a4fd2e27e4716 https://github.com/wooshy1/kernel_2.6.36_nvidia_base/commit/7442268b40cd6966d2d7cc7fc6ac3f43e5a23498 it should help with the battery as I had to ramp up the core and cpu mv by quite abit to get 1.4ghz to run stable. I also experimented increasing the gpu memory to 192mb and never had the browser fc but there wasnt enough memory to do anything useful so i enabled 128mb swap but android never used more than 16mb of the swap however I had no fc's related to lack of memory.
  13. Here is my repo forked from rebel1 and added all of Eduardo's kernel updates plus overclocking to 1.4ghz https://github.com/wooshy1/kernel_2.6.36_nvidia_base you will need to add abtfilt and the other bits to your ramdisk to take advantage of the wlan/bt daemon and usb tethering. Eduardo I had to change the framebuffer memory reservation back to setting it manually in board-shuttle.h otherwise the kernel does not boot. I have also changed the config to 720 on the hdmi as for 32 bit depth at 1080 we would need a framebuffer memory size of 16.5MB and as we are short of memory set it to 720.
  14. you need java jdk installed and in your path then android sdk then install tegra android development kit note where you install this git clone git://github.com/rebel1/kernel_2.6.36_nvidia_base cd kernel_2.6.36_nvidia_base/ git checkout -b nv-11.2.13 remotes/origin/nv-11.2.13 then pull config and put in kernel_2.6.36_nvidia_base/ you will need to alter the path below to match your install path of tegra android development kit export CCOMPILER=/home/richard/NVPACK/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- make ARCH=arm CROSS_COMPILE=$CCOMPILER wait for compilation mkbootimg zimage and ramdisk with something similar to this command line ./mkbootimg-H --cmdline '[email protected] vmalloc=192M usbcore.old_scheme_first=1 mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](staging),[email protected](userdata)' --kernel zImage --ramdisk newramdisk.cpio.gz -o boot.img then alter paths in /home/richard/kernel_2.6.36_nvidia_base/atheros/AR6kSDK.2.2.1.151/build.sh ATH_LINUXPATH=/home/richard/kernel_2.6.36_nvidia_base ATH_CROSS_COMPILE_TYPE=/home/richard/NVPACK/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi- then double click and run to build the wifi driver. then boot vega to CWM recovery and format boot and mount system and wipe dalvik cache etc adjust path below to match your user adb push /home/richard/kernel_2.6.36_nvidia_base/atheros/AR6kSDK.2.2.1.151/bin /system/lib/hw/wlan adb shell chmod 644 /system/lib/hw/wlan/* then reboot out of recovery you should get fastboot usb download or similar ./fastboot -i 0x955 -b 0x10000000 boot boot.img above command to test your kernel then after next reboot ./fastboot -i 0x955 -b 0x10000000 flash boot boot.img to flash your kernel that lot give me a booting kernel with DIET 3.2.5 and working wifi sorry this is abit messy but should give you some pointers.
  15. Finally got a chance to test this and you have fixed the a2dp issue you can now stream music/videos and listen with a2dp headphones with no skipping. Excellent work Eduardo!
×
×
  • Create New...

Important Information

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