|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
Quote:
In the next rootfs, I am making this change for the 3d testing: if [ -f /sdcard/gralloc.msm7k.so ];then mount --bind /sdcard/gralloc.msm7k.so /lib/froyo/hw/gralloc.msm7k.so mount --bind /sdcard/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so elif [ "$WVGA" = "1" ] && [ "$RCSCRIPT" = "froyo" ];then mount --bind /lib/froyo/hw/gralloc.msm7k_wvga.so /lib/froyo/hw/gralloc.msm7k.so mount --bind /lib/froyo/hw/gralloc.msm7k_wvga.so /system/lib/hw/gralloc.msm7k.so fi if [ -f /sdcard/libGLES_qcom.so ];then mount --bind /sdcard/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so fi if [ -f /sdcard/build.prop];then mount --bind /sdcard/build.prop /system/build.prop fi And, I have added support for all of the rhod100 vairants in the new rootfs. I'm waiting on feedback from those users so I can automate that one as well Last edited by natemcnutty; 12-15-2010 at 06:19 PM. |
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
alright i have a few questions did you ever make the roots that enabled the screen to stay on while android is starting up and do use the libgles_qcom.so, build.pro and gralloc is it the same as haret?
|
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
Quote:
Then I did the code I posted previously for optionally loading the libgles, build.prop, and gralloc from the sdcard. If you do not have the files on the sdcard, it will default to the original ones. I think some of the issues people are having with graphical issues might be because I replaced the original files with the 3d testing ones in the last builds. The method I am doing now will be much better. Just waiting on the files to download right now |
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
alright hey can you help me. So i have been on android through haret but decided to run nand. So i already flashed the ruu and put the rootfs, modules, and ext 2 into a andboot folder and it want start up is there anything special i need to do? also if i put gralloc, libgles, and build.prop on the root of the sd card is that all i need to do for that or do i need to make a special folder?
|
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
sweetness. you don't think it's faster/better to be running android from a "natively" partitioned ext2 partion on sdcard as upposed to just the fat32 andboot partitioned sdcard? and i'm dumb with the finding of how the hell i get a .kb file, all i see is .kl in the keymapping folder.... trying to get end=home/recent apps|power=power/turn off with the accesibility option to end call with power button....
edit: also, i can test some shtuff on the rhod400 if needed Last edited by MassStash; 12-15-2010 at 03:59 AM. |
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
Quote:
For the .kb file, you shouldn't need it unless you want to override the automatic keyboard detection. To create one, just open notepad, click File-Save As, change the File Type to All, and save as rhod400.kb. Also, the new RootFS is uploading to here: http://dl.dropbox.com/u/11790134/roo...14-42b44e2.img |
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
hey nate can you help me out with my last post? please
|
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
heck yea i'm running ubuntu 10.10. super nasty at that. but yea, trying to get the end buttong to home instead, didnt know i could just make up the file lol werd to the new rootfs dropping dlin now... get back to you on it asap
edit: gettin 404 at the file site brudda.... edit to edit: ahhhhh ha ha ha, "IS uploading"...... damn i'm a jumpy ass nerd haha Last edited by MassStash; 12-15-2010 at 04:22 AM. |
|
||||
Re: NAND Boot Testing - 12-11: Panel power off and on now working!
yea that should do it. but you need the new rootfs he's dropping to utilize the point of the grallloc, lib etc in the root dir. eventho he already had them in the last build n he thinks they may have caused issued, thus the point of the new build with the old shtuff, and the option to do neww stuff in root after trying out old stuff first... hint hint
|
|
|
|