Jump to content

backside

Members
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

5 Neutral

About backside

  • Rank
    Newbie
  1. Hi Hogweed, Sure! Read this: http://softwarebakery.com/ and install DriveDroid in your Modible. I do some (internal) patches to Cyanogenmod in our device to support this tool (mainly "/cust" partition support, "autorun.iso" support and full USB autorun mode [init.huawei.usb.rc]), and it works like a charm. Perhaps, if the great Mr. Dazzozo developer rectifies and don't call me a "clown", I'll publish the patches (see: http://www.modaco.co...00#entry2087118). No one likes to contribute if others don't appreciate the effort! :angry: After a Galaxy Spica, Galaxy Ace, Huawei u8650, ZTE Skate and now a G300, I found the scene of this device the less politely.... with difference! :(
  2. Please, don't waste your time! I check the scripts, and first I do a copy of my current bootloader: # dd if=/dev/block/mmcblk0p9 of=./bootloader.img # dd if=/dev/block/mmcblk0p14 of=./oemsbl.img After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL! If the problems with 3G reboots (In my case, I really need to change to 2G to avoid them!) is related with the bootloader, we need to open the ICS (and not de GB) version! Regards.
  3. Ok Dazz, Please, begin to tag your releases. We like to use your great kernel & rom, and make patches.
  4. Thank you, Dazz! You'll consider also to "patch" the values of auto-brightness in the R6? And one more question: What branch I need to use from your git tree of the kernel that you use for compatibility with R5 (and future releases)? https://github.com/Dazzozo/android_kernel_huawei_u8815 I like to compile some other modules and patch some of them. Can you provide some simple instructions? Can you publish for each release the tag used for kernel? Best!
  5. Hi Dazzozo, Good news about patching the bug of zram in R6! Related to CD-Emulation: You don't need to include the file "automount.iso" in the ROM. You only need to add support for it! If you see about the DriveDroid tool, you can mount ANY iso that you like. In any case, the definition of the "autorun,..." don't has any interference with the current rom. It's only for add a new mode (automount), and anyone has to worry about it. Please, update the file "/init.huawei.usb.rc" with the new code for the next release! I ask for this because patching init.rc files is difficult (modify the "boot.img" it's risky and time consuming). Remember: you only ADD a new definition mode without collateral effects.
  6. PATCH #2: CDROM.ISO (AKA automount) enabled Explanation: Stock ICS firmwares for G300 have the hability to provide a virtual CDROM drive with an ISO file that contains the driver for the device. When you use a Windows computer connected to the mobile in the Mass Storage (UMS) mode, a CDROM unit appears on the host. This is done because the stock ROM provides the file "/system/cdrom/autorun.iso", a simple ISO image file that contains the drivers. You can replace this file with ANY other file (in ISO format) and you see your CDROM content from the phone. Nevertheless, the CM9 ROM by Dazzozo don't have support to this file... after now! Solution: If you modify the file "/init.huawei.usb.rc" and include the next lines you can restore this functionality (remember that edit "init.rc" files is a hard work!): # USB google mode configuration on property:sys.usb.config=autorun,mass_storage write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 12d1 write /sys/class/android_usb/android0/idProduct 1037 write /sys/class/android_usb/android0/f_mass_storage/nluns 3 write /sys/class/android_usb/android0/f_mass_storage/cdrom_index 2 write /sys/class/android_usb/android0/f_mass_storage/lun2/file /system/cdrom/autorun.iso write /sys/class/android_usb/android0/functions mass_storage write /sys/class/android_usb/android0/enable 1 setprop sys.usb.state $sys.usb.config on property:sys.usb.config=autorun,mass_storage,adb write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 12d1 write /sys/class/android_usb/android0/idProduct 1038 write /sys/class/android_usb/android0/f_mass_storage/nluns 3 write /sys/class/android_usb/android0/f_mass_storage/cdrom_index 2 write /sys/class/android_usb/android0/f_mass_storage/lun2/file /system/cdrom/autorun.iso write /sys/class/android_usb/android0/functions mass_storage,adb write /sys/class/android_usb/android0/enable 1 start adbd setprop sys.usb.state $sys.usb.config Include this code after the "on boot" section at the begining. This don't complete the trick, you need to execute in ADB the command "setprop sys.usb.state autorun,mass_storage,adb", and after that if you have a file at "/system/cdrom/autorun.iso" you show the content in your workstation! Note: If you like you can use a GUI to do the task to select the ISO file, use the great free APP "DriveDroid" (search for it on the Market). Please, note that this software is developed thinking in use images as USB MASS STORAGE (like a pendrive), not for PURE ISO (CDROM emulation). The proposed hack works with ANY ISO, and you don't need at all any hybrid support. You can boot any bootable OS (not only Linux!) or use any type of CDROM. To mount as CDROM choose as the logical unit "F Mass Storage 3".
  7. PATCH #1: Fix Compcache (AKA zram) disabled Explanation: The current compcache service isn't started in CM9. The source uses the file "/system/etc/init.local.rc" to declare at boot the service, but this file is NEVER called at the boot process. The file "/init.rc" has the import, but the filesystem isn't mounted (/system) when the "/init" parser reads the import. You can check that this an unresolved bug of cyanogenmod. If you like to check: open an ADB session and see "/dev/block/zram0". Solution: Execute the file "/system/bin/handle_compcache". This initializes the compcache using the correct values of the interface. To execute this file, you have two options: Option 1: Modify the file "/init.rc" to include the lines from file "/system/etc/init.local.rc". This is a hard work because you need to edit the "boot.img" file and write it to flash. I suggest to Dazzazo to include this on next release. This creates the service compcache inside the Android. Option 2: Add a "init.d" file that call to "/system/bin/handle_compcache". I add an attachment with one of this files. You only need to set RW of SYSTEM and copy the file to "/system/etc/init.d/". Note: The same patch apply to any other custom ROM based on CM9. This problem is derived from cyanogemod. 89zram.zip
  8. Hi, I like to open this thread for contribute to the good effort from Dazzozo to port and patch CM9 for the G300. This thread is for posting PATCHES or CONTRIBUTIONS. Please, don't post for requests or suggestions, or for report bugs; use the main thread to do it. This is a DEV thread. Next two posts include some contributions by myself. Backside!
  9. Hi, "init.d" support ins't related to kernel. If you like to add support for it in a STOCK rom see:
  10. Hi, I'll appreciate if someone creates a .ZIP file for CWM with the files of this thread. In my case I do all my work from adb/ssh, and as consequence I think only on experienced users. If someone creates the ZIP file, it can be used on any STOCK rom. Several programs uses "init.d" support to execute scripts at boot! Regards.
  11. If you like to use this on a STOCK rom, please read:
  12. Hi to all, I'm sorry, but a huge requirement it's set "mount as ext4" in settings of S2e. After you install the application, run it, select settings and pick the option. After you reboot, the scripts of the application will be executed. Regards!
  13. Hi Sandrogp, All things will be easier if Tillaz adds the file "/system/etc/init.d/20userinit" to the INFUSION firmware. This file ins't created by me, it's copied from the repository of CM7/CM9; and It's pure safe! The only thing that this can do is execute scripts on "/data/local/userinit.d/". Please, ask to him to add it. Regards.
  14. Please, Webmaster, add support for Forum Runner: http://www.forumrunner.net/?p=create Remember: Now Tapatalk support is already working: http://www.modaco.co...ow/page__st__80 Thank you!
  15. Hi Tillaz, I found a BUG in the last release (or from my point of view is a bug): The busybox (/system/xbin/busybox) has "sudo" privileges. This creates problems with system-linux-init.d scripts. I suggest to make "chmod 755" for this file. Moreover, I suggest to create "all" symbolic links to busybox in the directory "/system/xbin/". Other ROMs do this, and is more easy to work with ADB shell. Can you do it, please? Regards!
×