USB Host Kernel based on ezterry's 2708-enabled kernel - G1 Android Development

ezterry's 2708-enabled kernel
http://forum.xda-developers.com/showthread.php?t=831139
Patching kernels to make them support USB Host on the G1
http://forum.xda-developers.com/showthread.php?t=794643
I've been working on this for about a week.
I patched his kernel source with the patch suggested in the guide, and manually patched what wouldn't go in. Then I took the kernel config from the guide and merged anything that said USB on it with the other using Deltawalker,(which is a very handy tool), to make sure I didn't screw up anything to do with the processor.
Attached is the text that resulted after trying to compile the kernel.
Nothing concerns me that much as most of the errors seem to say things like "defined but not used."
The errors that don't are listed below in order of appearance:
Code:
scripts/kconfig/conf.c: In function ‘conf_askvalue’:
scripts/kconfig/conf.c:105: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
scripts/kconfig/conf.c: In function ‘conf_choice’:
scripts/kconfig/conf.c:307: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
Code:
scripts/kallsyms.c: In function ‘read_symbol’:
scripts/kallsyms.c:112: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
Code:
arch/arm/kernel/return_address.c:61:2: warning: #warning "TODO: return_address should use unwind tables"
Code:
arch/arm/mach-msm/acpuclock-arm11.c:69:5: warning: "force_turbo" is not defined
Code:
arch/arm/mach-msm/clock.c: In function 'clk_set_rate_locked':
arch/arm/mach-msm/clock.c:248: warning: 'ret' may be used uninitialized in this function
Code:
arch/arm/mach-msm/pm.c: In function 'msm_pm_init':
arch/arm/mach-msm/pm.c:861: warning: assignment from incompatible pointer type
Code:
arch/arm/mach-msm/board-trout.c: In function 'trout_fixup':
arch/arm/mach-msm/board-trout.c:913: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
Code:
arch/arm/mach-msm/board-sapphire.c: In function 'sapphire_fixup':
arch/arm/mach-msm/board-sapphire.c:1426: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
Code:
mm/ashmem.c:380: warning: initialization from incompatible pointer type
And this one which makes me the most nervous:
Code:
In file included from drivers/media/video/msm/mt9t013.c:28:
arch/arm/mach-msm/include/mach/camera.h:231: warning: 'struct msm_camera_sensor_flash_data' declared inside parameter list
arch/arm/mach-msm/include/mach/camera.h:231: warning: its scope is only this definition or declaration, which is probably not what you want
drivers/media/video/msm/mt9t013.c: In function 'mt9t013_sensor_probe':
drivers/media/video/msm/mt9t013.c:1479: warning: assignment from incompatible pointer type
drivers/media/video/msm/mt9t013.c: In function '__mt9t013_probe':
drivers/media/video/msm/mt9t013.c:1490: warning: passing argument 2 of 'msm_camera_drv_start' from incompatible pointer type
arch/arm/mach-msm/include/mach/camera.h:259: note: expected 'int (*)(struct msm_camera_sensor_info *, struct msm_sensor_ctrl *)' but argument is of type 'int (*)(const struct msm_camera_sensor_info *, struct msm_sensor_ctrl *)'
CC net/802/p8022.o
CC drivers/media/video/msm/mt9t013_reg.o
CC drivers/media/video/msm/ov9665.o
CC [M] fs/nfs/nfs4xdr.o
In file included from drivers/media/video/msm/ov9665.h:23,
from drivers/media/video/msm/ov9665.c:27:
arch/arm/mach-msm/include/mach/camera.h:231: warning: 'struct msm_camera_sensor_flash_data' declared inside parameter list
arch/arm/mach-msm/include/mach/camera.h:231: warning: its scope is only this definition or declaration, which is probably not what you want
CC net/802/psnap.o
CC net/802/stp.o
CC drivers/media/video/msm/ov9665_reg.o
In file included from drivers/media/video/msm/ov9665.h:23,
from drivers/media/video/msm/ov9665_reg.c:19:
arch/arm/mach-msm/include/mach/camera.h:231: warning: 'struct msm_camera_sensor_flash_data' declared inside parameter list
arch/arm/mach-msm/include/mach/camera.h:231: warning: its scope is only this definition or declaration, which is probably not what you want
drivers/media/video/msm/ov9665_reg.c:206: warning: initialization from incompatible pointer type
CC drivers/media/video/msm/msm_camera.o
In file included from drivers/media/video/msm/msm_camera.c:33:
arch/arm/mach-msm/include/mach/camera.h:231: warning: 'struct msm_camera_sensor_flash_data' declared inside parameter list
arch/arm/mach-msm/include/mach/camera.h:231: warning: its scope is only this definition or declaration, which is probably not what you want
LD net/802/built-in.o
CC net/bluetooth/af_bluetooth.o
CC net/bluetooth/hci_core.o
CC drivers/media/video/msm/msm_v4l2.o
CC net/bluetooth/hci_conn.o
In file included from drivers/media/video/msm/msm_v4l2.c:30:
arch/arm/mach-msm/include/mach/camera.h:231: warning: 'struct msm_camera_sensor_flash_data' declared inside parameter list
arch/arm/mach-msm/include/mach/camera.h:231: warning: its scope is only this definition or declaration, which is probably not what you want
drivers/media/video/msm/msm_v4l2.c: In function 'msm_v4l2_qbuf':
drivers/media/video/msm/msm_v4l2.c:337: error: expected expression before '<<' token
drivers/media/video/msm/msm_v4l2.c:343: error: expected expression before '==' token
drivers/media/video/msm/msm_v4l2.c:346: error: expected expression before '>>' token
drivers/media/video/msm/msm_v4l2.c:346:9: error: invalid suffix "ddb..." on integer constant
make[4]: *** [drivers/media/video/msm/msm_v4l2.o] Error 1
make[3]: *** [drivers/media/video/msm] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
Code:
net/core/rtnetlink.c: In function 'do_setlink':
net/core/rtnetlink.c:1044: warning: 'err' may be used uninitialized in this function
With that many errors, I don't consider it safe to load this on to my G1.
Well, even if it were safe, I'm not sure I'd get much function out of it. My guess is that the video camera wouldn't work.
Anyway, what can I do to fix these messages, and, after I have, what is the next step?
I have been told that I have to merge it with a ramdisk. I assumed that I would need to pull it from my current phone (which uses the 2708 kernel) because it is likely that it would work.
Unfortunately, after trying this I discovered I don't have the privileges as the SPL is S-ON.
Will using the ramdisk provided in the Android SDK work, and if not, what will?
EDIT: Forgot to attach the full text.

Looks like you haven't understood yet how patch/diff files work.
This message:
Code:
drivers/media/video/msm/msm_v4l2.c:337: error: expected expression before '<<' token
drivers/media/video/msm/msm_v4l2.c:343: error: expected expression before '==' token
drivers/media/video/msm/msm_v4l2.c:346: error: expected expression before '>>' token
tells me that the file msm_v4l2.c is broken between lines 337 and 346. You couldn't "put" the resulting kernel in your G1 even if you wanted, since the kernel doesn't even get built due to that error!

Okay, I thought about it for a while, and I couldn't believe that it was the patch file causing this to happen, because the patch file is adding support for the USB Host function, why would it mess with video?
Anyway, I compiled the kernel 3 times after that. I compiled it the way it was meant to be compiled; 2708 config with no patching which obviously worked with little error (although it was surprising to see how many there were anyway), I patched it then I compiled it using the 2708 config to see if it was the merged config at fault, and it was.
So what I decided to do after is merge the two config files again but be a little more careful not to merge anything that doesn't have to do with USB Host.
After I did this, I used the newly merged configuration file, compiled itand it worked!
There was probably about the same amount of errors as the original.
Moving on, what do I do next?
I'll attach both the output text when compiling the original kernel and original config file, and the output text when compiling the patched kernel with the merged config file.
Also, what does "module" mean? I was given many options to compile many device drivers (I'm assuming? that's what it looked like) with three options, N/m/y.
I'm also assuming that N is capitalized because it's default, but I decided to choose m for most of them, because I thought I might use them, and module sounded like a compromise between no and yes.
Maybe what I'm really asking is, where do the modules get stored?

Your modules are here:
Code:
...
Building modules, stage 2.
MODPOST 80 modules
Kernel: arch/arm/boot/Image is ready
...
LD [M] drivers/block/ub.ko
LD [M] drivers/bluetooth/ath3k.ko
LD [M] drivers/bluetooth/bcm203x.ko
LD [M] drivers/bluetooth/bfusb.ko
LD [M] drivers/bluetooth/bpa10x.ko
LD [M] drivers/bluetooth/btusb.ko
LD [M] drivers/cpufreq/cpufreq_userspace.ko
LD [M] drivers/hid/hid-gaff.ko
LD [M] drivers/hid/hid-microsoft.ko
LD [M] drivers/hid/hid-monterey.ko
LD [M] drivers/hid/hid-mosart.ko
LD [M] drivers/hid/hid-ntrig.ko
LD [M] drivers/hid/hid-petalynx.ko
LD [M] drivers/hid/hid-ortek.ko
LD [M] drivers/hid/hid-pl.ko
LD [M] drivers/hid/hid-quanta.ko
LD [M] drivers/hid/hid-samsung.ko
LD [M] drivers/hid/hid-sony.ko
LD [M] drivers/hid/hid-stantum.ko
LD [M] drivers/hid/hid-sunplus.ko
LD [M] drivers/hid/usbhid/usbhid.ko
LD [M] drivers/net/usb/asix.ko
LD [M] drivers/net/usb/catc.ko
LD [M] drivers/net/usb/cdc_eem.ko
LD [M] drivers/net/usb/cdc_ether.ko
LD [M] drivers/net/usb/cdc_subset.ko
LD [M] drivers/net/usb/gl620a.ko
LD [M] drivers/net/usb/hso.ko
LD [M] drivers/net/usb/dm9601.ko
LD [M] drivers/net/usb/int51x1.ko
LD [M] drivers/net/usb/ipheth.ko
LD [M] drivers/net/usb/kaweth.ko
LD [M] drivers/net/usb/mcs7830.ko
LD [M] drivers/net/usb/net1080.ko
LD [M] drivers/net/usb/pegasus.ko
LD [M] drivers/net/usb/plusb.ko
LD [M] drivers/net/usb/rndis_host.ko
LD [M] drivers/net/usb/rtl8150.ko
LD [M] drivers/net/usb/smsc75xx.ko
LD [M] drivers/net/usb/smsc95xx.ko
LD [M] drivers/net/usb/usbnet.ko
LD [M] drivers/net/wireless/tiwlan1251/wlan.ko
LD [M] drivers/net/usb/zaurus.ko
LD [M] drivers/net/wireless/zd1201.ko
LD [M] drivers/staging/ramzswap/ramzswap.ko
LD [M] drivers/staging/udlfb/udlfb.ko
LD [M] drivers/usb/core/usbcore.ko
LD [M] drivers/usb/mon/usbmon.ko
LD [M] drivers/usb/host/ehci-hcd.ko
LD [M] drivers/usb/serial/cp210x.ko
LD [M] drivers/usb/serial/ftdi_sio.ko
LD [M] drivers/usb/serial/usbserial.ko
LD [M] drivers/video/fb_sys_fops.ko
LD [M] drivers/video/syscopyarea.ko
LD [M] drivers/video/sysfillrect.ko
LD [M] drivers/video/sysimgblt.ko
LD [M] fs/cifs/cifs.ko
LD [M] fs/fuse/fuse.ko
LD [M] fs/lockd/lockd.ko
LD [M] fs/nfs/nfs.ko
LD [M] fs/nfs_common/nfs_acl.ko
LD [M] net/ipv4/ipcomp.ko
LD [M] net/ipv4/tunnel4.ko
LD [M] net/ipv4/xfrm4_tunnel.ko
LD [M] net/ipv6/ah6.ko
LD [M] net/ipv6/esp6.ko
LD [M] net/ipv6/ip6_tunnel.ko
LD [M] net/ipv6/ipcomp6.ko
LD [M] net/ipv6/mip6.ko
LD [M] net/ipv6/ipv6.ko
LD [M] net/ipv6/sit.ko
LD [M] net/ipv6/tunnel6.ko
LD [M] net/ipv6/xfrm6_mode_beet.ko
LD [M] net/ipv6/xfrm6_mode_transport.ko
LD [M] net/ipv6/xfrm6_mode_tunnel.ko
LD [M] net/ipv6/xfrm6_tunnel.ko
LD [M] net/sunrpc/auth_gss/rpcsec_gss_krb5.ko
LD [M] net/sunrpc/auth_gss/auth_rpcgss.ko
LD [M] net/sunrpc/sunrpc.ko
LD [M] net/xfrm/xfrm_ipcomp.ko
...
If you choose Y you'll build-in this modules in kernel. When you choose M you must load modules with insmod in particular order.

Okay - thanks. That seemed fairly obvious. If only I looked had at it some more.
Can I use the ramdisk provided in the SDK?
Something tells me that these two methods:
Now, get the kernel on the phone:
1. use fastboot to boot from RAM (not persistent)
~/android-sdk-linux_86/tools/fastboot boot arch/arm/boot/zImage
OR
2. use fastboot to flash it to NAND (boot.img from a nandroid backup)
~/android-sdk-linux_86/tools/fastboot -b flash:raw boot ./zImage ./ramdisk.img
Click to expand...
Click to collapse
aren't going to work because of the S-ON SPL that is required.
I'll try ZipBuilder in a bit though as ideally, it would be nice to just be able to flash it in a zip.

Okay, I think I got it working with ZipBuilder!
I flashed it, and it still booted so that's a good sign.
I'll attach the update_signed.zip.
Is there any for sure way I can see if it worked? (other than loading up the modules and plugging something in - I need to get a cord soldered first).
I copied the modules from my kernel build directory and placed them directly in the system/lib/modules directory. Were they supposed to have the hierarchy like they did in the kernel build directory?
Anyway, here's what ZipBuilder said:
Code:
Directory Check: OK - 'kernel'
Directory Check: OK - 'META-INF'
Directory Check: OK - 'META-INF/com'
Directory Check: OK - 'META-INF/com/google'
Directory Check: OK - 'META-INF/com/google/android'
Directory Check: OK - 'system/'
Directory Check: OK - 'system/lib'
Directory Check: OK - 'system/lib/modules'
File Check: OK - 'kernel/dump_image'
File Check: OK - 'kernel/mkbootimg'
File Check: OK - 'kernel/mkbootimg.sh'
File Check: OK - 'kernel/unpackbootimg'
File Check: OK - 'META-INF/com/google/android/update-binary'
File Check: OK - 'META-INF/com/google/android/updater-script'
zImage exists!
Removed!
cp: cannot stat `../drivers/net/wireless/bcm4329/bcm4329.ko': No such file or directory
update.zip exists!
Removed!
adding: system/ (stored 0%)
adding: system/lib/ (stored 0%)
adding: system/lib/modules/ (stored 0%)
adding: system/lib/modules/bfusb.ko (stored 0%)
adding: system/lib/modules/fuse.ko (stored 0%)
adding: system/lib/modules/usbserial.ko (stored 0%)
adding: system/lib/modules/hid-pl.ko (stored 0%)
adding: system/lib/modules/hid-quanta.ko (stored 0%)
adding: system/lib/modules/sunrpc.ko (stored 0%)
adding: system/lib/modules/hid-mosart.ko (stored 0%)
adding: system/lib/modules/ub.ko (stored 0%)
adding: system/lib/modules/hid-gaff.ko (stored 0%)
adding: system/lib/modules/lockd.ko (stored 0%)
adding: system/lib/modules/usbhid.ko (stored 0%)
adding: system/lib/modules/usbmon.ko (stored 0%)
adding: system/lib/modules/btusb.ko (stored 0%)
adding: system/lib/modules/asix.ko (stored 0%)
adding: system/lib/modules/smsc95xx.ko (stored 0%)
adding: system/lib/modules/xfrm6_mode_tunnel.ko (stored 0%)
adding: system/lib/modules/ah6.ko (stored 0%)
adding: system/lib/modules/int51x1.ko (stored 0%)
adding: system/lib/modules/cifs.ko (stored 0%)
adding: system/lib/modules/sit.ko (stored 0%)
adding: system/lib/modules/smsc75xx.ko (stored 0%)
adding: system/lib/modules/catc.ko (stored 0%)
adding: system/lib/modules/cdc_ether.ko (stored 0%)
adding: system/lib/modules/tunnel6.ko (stored 0%)
adding: system/lib/modules/auth_rpcgss.ko (stored 0%)
adding: system/lib/modules/xfrm6_mode_transport.ko (stored 0%)
adding: system/lib/modules/syscopyarea.ko (stored 0%)
adding: system/lib/modules/ehci-hcd.ko (stored 0%)
adding: system/lib/modules/nfs.ko (stored 0%)
adding: system/lib/modules/ipcomp6.ko (stored 0%)
adding: system/lib/modules/hid-ortek.ko (stored 0%)
adding: system/lib/modules/kaweth.ko (stored 0%)
adding: system/lib/modules/gl620a.ko (stored 0%)
adding: system/lib/modules/usbcore.ko (stored 0%)
adding: system/lib/modules/hid-petalynx.ko (stored 0%)
adding: system/lib/modules/mcs7830.ko (stored 0%)
adding: system/lib/modules/ipheth.ko (stored 0%)
adding: system/lib/modules/ath3k.ko (stored 0%)
adding: system/lib/modules/hid-sunplus.ko (stored 0%)
adding: system/lib/modules/ftdi_sio.ko (stored 0%)
adding: system/lib/modules/hso.ko (stored 0%)
adding: system/lib/modules/usbnet.ko (stored 0%)
adding: system/lib/modules/rpcsec_gss_krb5.ko (stored 0%)
adding: system/lib/modules/plusb.ko (stored 0%)
adding: system/lib/modules/xfrm6_tunnel.ko (stored 0%)
adding: system/lib/modules/hid-ntrig.ko (stored 0%)
adding: system/lib/modules/hid-monterey.ko (stored 0%)
adding: system/lib/modules/zd1201.ko (stored 0%)
adding: system/lib/modules/ipcomp.ko (stored 0%)
adding: system/lib/modules/zaurus.ko (stored 0%)
adding: system/lib/modules/cdc_eem.ko (stored 0%)
adding: system/lib/modules/pegasus.ko (stored 0%)
adding: system/lib/modules/xfrm4_tunnel.ko (stored 0%)
adding: system/lib/modules/wlan.ko (stored 0%)
adding: system/lib/modules/cdc_subset.ko (stored 0%)
adding: system/lib/modules/esp6.ko (stored 0%)
adding: system/lib/modules/mip6.ko (stored 0%)
adding: system/lib/modules/dm9601.ko (stored 0%)
adding: system/lib/modules/hid-sony.ko (stored 0%)
adding: system/lib/modules/rtl8150.ko (stored 0%)
adding: system/lib/modules/udlfb.ko (stored 0%)
adding: system/lib/modules/cp210x.ko (stored 0%)
adding: system/lib/modules/nfs_acl.ko (stored 0%)
adding: system/lib/modules/sysfillrect.ko (stored 0%)
adding: system/lib/modules/cpufreq_userspace.ko (stored 0%)
adding: system/lib/modules/bcm203x.ko (stored 0%)
adding: system/lib/modules/tunnel4.ko (stored 0%)
adding: system/lib/modules/ipv6.ko (stored 0%)
adding: system/lib/modules/xfrm6_mode_beet.ko (stored 0%)
adding: system/lib/modules/ramzswap.ko (stored 0%)
adding: system/lib/modules/sysimgblt.ko (stored 0%)
adding: system/lib/modules/hid-microsoft.ko (stored 0%)
adding: system/lib/modules/net1080.ko (stored 0%)
adding: system/lib/modules/bpa10x.ko (stored 0%)
adding: system/lib/modules/fb_sys_fops.ko (stored 0%)
adding: system/lib/modules/rndis_host.ko (stored 0%)
adding: system/lib/modules/ip6_tunnel.ko (stored 0%)
adding: system/lib/modules/hid-samsung.ko (stored 0%)
adding: system/lib/modules/hid-stantum.ko (stored 0%)
adding: system/lib/modules/xfrm_ipcomp.ko (stored 0%)
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/update-binary (stored 0%)
adding: META-INF/com/google/android/updater-script (stored 0%)
adding: kernel/ (stored 0%)
adding: kernel/unpackbootimg (stored 0%)
adding: kernel/dump_image (stored 0%)
adding: kernel/zImage (stored 0%)
adding: kernel/mkbootimg.sh (stored 0%)
adding: kernel/mkbootimg (stored 0%)
Done!
Let me know if I did it wrong.
I'm assuming the wireless driver didn't load because it wasn't supposed to for the G1 (e.g. the G1 doesn't have that wireless chip?).
Also, what does "stored 0%" mean?
EDIT: Oops! I just looked at the guide by kodovoimeji again and realized I wasn't supposed to put the modules in the zip at all, I was supposed to copy them over to the SD Card which makes a lot more sense anyway.

Hi, is this allready done? I didn't understood at all. I know how Android platform works, but I am a big dummy in English yet.
michael-knight's update-signet.zip is final?

Adding USB HOST support to the kernel is one thing, the next step is to actually add drivers for various USB DEVICES, otherwise USB HOST isn't going to do much for you. One of the drivers that I find particularly useful, especially for something like a phone, are the various USB-to-RS232 adapter cable drivers. This would turn the phone into an INCREDIBLE debugging device.

Keyboard need too some drivers?

thank you very muchhh

Related

[SCRIPT v3.1] Back up all proprietary files to sdcard

This script and the attached statically compiled zip program are able
to create a backup file named bakpak.zip on your sdcard containing
all your phone's proprietary files I'm aware of. If you know about
other files that need to be added to the list please let me know.
Roms with odexed apk packages are not supported as deodexing
them is not trivial and legally dubious.
List:
Code:
/system/app/BugReport.apk
/system/app/checkin.apk
/system/app/Gmail.apk
/system/app/GmailProvider.apk
/system/app/GoogleApps.apk
/system/app/GooglePartnerSetup.apk
/system/app/GoogleSettingsProvider.apk
/system/app/gtalkservice.apk
/system/app/MediaUploader.apk
/system/app/NetworkLocation.apk
/system/app/SetupWizard.apk
/system/app/Street.apk
/system/app/Talk.apk
/system/app/Vending.apk
/system/app/VoiceSearch.apk
/system/app/YouTube.apk
/system/framework/com.google.android.gtalkservice.jar
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.gtalkservice.xml
/system/etc/permissions/com.google.android.maps.xml
/system/bin/akmd
/system/etc/firmware/brf6300.bin
/system/etc/gps.conf
/system/etc/wifi/Fw1251r1c.bin
/system/etc/wifi/tiwlan.ini
/system/lib/libaudioeq.so
/system/lib/libgps.so
/system/lib/libhgl.so
/system/lib/libhtc_acoustic.so
/system/lib/libhtc_ril.so
/system/lib/libjni_pinyinime.so
/system/lib/libmm-adspsvc.so
/system/lib/libOmxCore.so
/system/lib/libOmxH264Dec.so
/system/lib/libOmxMpeg4Dec.so
/system/lib/libOmxVidEnc.so
/system/lib/libopencorehw.so
/system/lib/libpvasf.so
/system/lib/libpvasfreg.so
/system/lib/libqcamera.so
/system/lib/libspeech.so
/system/lib/hw/lights.goldfish.so
/system/lib/hw/lights.msm7k.so
/system/lib/hw/sensors.trout.so"
# Removed because under Apache v2 license
#/system/app/GoogleContactsProvider.apk
#/system/app/GoogleSubscribedFeedsProvider.apk
#/system/app/ImProvider.apk
#/system/app/VoiceDialer.apk
# Removed from list, we usually flash modded versions, could be readded if needed
#/system/etc/AudioFilter.csv
#/system/etc/AudioPara4.csv
#/system/etc/AudioPreProcess.csv
The purpose of this script is to enable devs to backup all proprietary files
before flashing a updated rom and restore them after the flashing process.
The restore script must still be developed, one thing to take care of is that
during restore you have to set the correct file permissions and ownership
yourself if choose to create a zip archive. If you create a tar.gz archive
(-t) the file permissions and ownership will be restored correctly.
Setup:
Code:
unzip backup.zip
adb remount
adb push zip /system/bin/
adb push bakpak.sh /system/bin/
adb shell
chown root.shell /system/bin/zip
chown root.shell /system/bin/bakpak.sh
chmod 755 /system/bin/zip
chmod 755 /system/bin/bakpak.sh
Usage:
Code:
adb shell
~ # bakpak.sh -h
Usage /system/bin/bakpak.sh [OPTIONS]
-t create a tar.gz
-v print version
-h this help
~ # bakpak.sh
or in the terminal
Code:
su
bakpak.sh
Example:
Code:
~ # bakpak.sh
zip warning: name not matched: /system/app/VoiceDialer.apk
zip warning: name not matched: /system/app/VoiceSearch.apk
adding: system/app/BugReport.apk (deflated 1%)
adding: system/app/checkin.apk (deflated 1%)
adding: system/app/Gmail.apk (deflated 16%)
adding: system/app/GmailProvider.apk (deflated 0%)
adding: system/app/GoogleApps.apk (deflated 1%)
adding: system/app/GoogleContactsProvider.apk (deflated 1%)
adding: system/app/GooglePartnerSetup.apk (deflated 1%)
adding: system/app/GoogleSettingsProvider.apk (deflated 1%)
adding: system/app/GoogleSubscribedFeedsProvider.apk (deflated 2%)
adding: system/app/gtalkservice.apk (deflated 1%)
adding: system/app/ImProvider.apk (deflated 3%)
adding: system/app/MediaUploader.apk (deflated 1%)
adding: system/app/NetworkLocation.apk (deflated 1%)
adding: system/app/SetupWizard.apk (deflated 9%)
adding: system/app/Street.apk (deflated 2%)
adding: system/app/Talk.apk (deflated 4%)
adding: system/app/Vending.apk (deflated 3%)
adding: system/app/YouTube.apk (deflated 3%)
adding: system/framework/com.google.android.gtalkservice.jar (deflated 1%)
adding: system/framework/com.google.android.maps.jar (deflated 0%)
adding: system/etc/permissions/com.google.android.gtalkservice.xml (deflated 41%)
adding: system/etc/permissions/com.google.android.maps.xml (deflated 41%)
adding: system/bin/akmd (deflated 67%)
adding: system/etc/firmware/brf6300.bin (deflated 37%)
adding: system/etc/gps.conf (deflated 44%)
adding: system/etc/wifi/Fw1251r1c.bin (deflated 40%)
adding: system/etc/wifi/tiwlan.ini (deflated 67%)
adding: system/lib/libaudioeq.so (deflated 59%)
adding: system/lib/libgps.so (deflated 70%)
adding: system/lib/libhgl.so (deflated 58%)
adding: system/lib/libhtc_acoustic.so (deflated 61%)
adding: system/lib/libhtc_ril.so (deflated 53%)
adding: system/lib/libjni_pinyinime.so (deflated 46%)
adding: system/lib/libmm-adspsvc.so (deflated 55%)
adding: system/lib/libOmxCore.so (deflated 62%)
adding: system/lib/libOmxH264Dec.so (deflated 55%)
adding: system/lib/libOmxMpeg4Dec.so (deflated 55%)
adding: system/lib/libOmxVidEnc.so (deflated 44%)
adding: system/lib/libopencorehw.so (deflated 68%)
adding: system/lib/libpvasf.so (deflated 50%)
adding: system/lib/libpvasfreg.so (deflated 53%)
adding: system/lib/libqcamera.so (deflated 45%)
adding: system/lib/libspeech.so (deflated 50%)
adding: system/lib/hw/lights.goldfish.so (deflated 73%)
adding: system/lib/hw/lights.msm7k.so (deflated 51%)
adding: system/lib/hw/sensors.trout.so (deflated 62%)
~ # cd sdcard/
/sdcard # ls -la bakpak.zip
----rw-rw- 1 system system 4620298 Sep 27 08:59 bakpak.zip
Enjoy!
Changelog:
v1 initial release
v2 remove some packages and add a warning about odex files.
v3 added ability to create tar.gz archives, check if dest exists,
check for missing files when using tar.Added command line parsing.
v3.1 Minor bugfixes
I'm a crash test dummy!
Well, you did great with the Fix_permissions....
I'LL be trying it here in a min. I don't have adb so I'll b doing it thru terminal.
or would it be better to do it thru recovery?
Chevy
You don't need to backup all the propriatary HTC libs, as they are needed to boot up android correctly.
Until HTC C&D's us, we don't need to exclude these files ;-)
Cyanogen is working on an app which backups the GApps for us.
If you want to improve your script, you'll have to let it look after the Google Apps.
Don't back them up if they are odexed, because you then would have to unodex them, which is hard to do for most users here as you have to install a daemon which helps your PC to unodex on your Android device.
Hi! The script is great, maybe we should add an UI or something like that to make thing easy for the novel kids, but this is a great start, good job!
Btw, I've found some packages you list as conflictive but in the Android source tree they come with a NOTICE file with the Apache License in it:
You can check it out if you want, just do a "repo sync" first
Code:
/system/app/GoogleContactsProvider.apk -> packages/providers/GoogleContactsProvider
/system/app/GoogleSubscribedFeedsProvider.apk -> packages/providers/GoogleSubscribedFeedsProvider
/system/app/ImProvider.apk -> packages/providers/ImProvider
/system/app/VoiceDialer.apk ->packages/apps/VoiceDialer
Hope it helps to clarify.
maxisma said:
You don't need to backup all the propriatary HTC libs, as they are needed to boot up android correctly.
Until HTC C&D's us, we don't need to exclude these files ;-)
Cyanogen is working on an app which backups the GApps for us.
If you want to improve your script, you'll have to let it look after the Google Apps.
Don't back them up if they are odexed, because you then would have to unodex them, which is hard to do for most users here as you have to install a daemon which helps your PC to unodex on your Android device.
Click to expand...
Click to collapse
I was thinking about unodexing, but have to test. OTOH this is specific to
Cyanogen mods that are not odexed so there is no problem.
0Vw3 said:
Hi! The script is great, maybe we should add an UI or something like that to make thing easy for the novel kids, but this is a great start, good job!
Btw, I've found some packages you list as conflictive but in the Android source tree they come with a NOTICE file with the Apache License in it:
You can check it out if you want, just do a "repo sync" first
Code:
/system/app/GoogleContactsProvider.apk -> packages/providers/GoogleContactsProvider
/system/app/GoogleSubscribedFeedsProvider.apk -> packages/providers/GoogleSubscribedFeedsProvider
/system/app/ImProvider.apk -> packages/providers/ImProvider
/system/app/VoiceDialer.apk ->packages/apps/VoiceDialer
Hope it helps to clarify.
Click to expand...
Click to collapse
Will check and remove them. Thanks for hint.
ran ok
Pushed and ran thru terminal. Everythings a ok!
Great to see this project moving forward so quickly. As a Linux user though, I'm wondering the logic behind using a .zip instead of a .tar.gz or lzma though, is there any advantage to zip? I can't think of any.
Vash63 said:
Great to see this project moving forward so quickly. As a Linux user though, I'm wondering the logic behind using a .zip instead of a .tar.gz or lzma though, is there any advantage to zip? I can't think of any.
Click to expand...
Click to collapse
All the flashing is done with zip archives, nonetheless adding a command line switch to create a tar.gz is trivial. Maybe in next version.
I'm gettin lost when you talk about odex files. As far as I know, odex files are optimized binaries for the dalvik vm, generated the first time you run them in your device from the dex files contained in the apk, and stored in /data/dalvik-cache (This could be some kind of compilation process (¿?))
So, (sorry for the noob question(s)) what's the problem about that? what do you mean when you talk about odexed - unodexed apks? And the most important, why is it a problem when backing up the apps?
Thanks.
0Vw3 said:
I'm gettin lost when you talk about odex files. As far as I know, odex files are optimized binaries for the dalvik vm, generated the first time you run them in your device from the dex files contained in the apk, and stored in /data/dalvik-cache (This could be some kind of compilation process (¿?))
So, (sorry for the noob question(s)) what's the problem about that? what do you mean when you talk about odexed - unodexed apks? And the most important, why is it a problem when backing up the apps?
Thanks.
Click to expand...
Click to collapse
Some apk are preoptimized and don't have the usual dex file inside,
instead there is a .odex file in the /system/app/ directory.
This odex files are not portable as they refer to the specific
framework from which the they was created.
farmatito said:
Some apk are preoptimized and don't have the usual dex file inside,
instead there is a .odex file in the /system/app/ directory.
This odex files are not portable as they refer to the specific
framework from which the they was created.
Click to expand...
Click to collapse
Thanks for the explanation. So I suppose the great JesusFreke can help with this.
I know that's reverse engineering, but even if it's I'm not sure we'd be breaking any copyright law as we paid for these apps and should be able to run them everywhere we'd want / could.

Has anyone used PDroid on the skyrocket yet?

The installation patching instructions look pretty annoying. Has anyone done this and has a CWM flashable patch I could use?
http://forum.xda-developers.com/showthread.php?t=1357056
This is what I get when using the patch generator:
Code:
PDroid Patcher v0.3 - Patch v1.27
Patching C:\Users\Ryan\Desktop\StockMod-2-UCLA3-0.2kernel.zip
Extracting framework files from ROM
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: META-INF/com/google/android/updater-script
inflated: META-INF/com/google/android/update-binary
Decompiling original files
I: Baksmaling...
I: Copying assets and libs...
I: Baksmaling...
I: Copying assets and libs...
I: Baksmaling...
I: Copying assets and libs...
Cleaning up smali
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\app\ContextImpl.smali 1>framework.mod.jar.out\smali\android\app\ContextImpl.smali.new
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\app\ContextImpl.smali.new framework.mod.jar.out\smali\android\app\ContextImpl.smali
1 file(s) moved.
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\content\ContentResolver.smali 1>framework.mod.jar.out\smali\android\content\ContentResolver.smali.new
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\content\ContentResolver.smali.new framework.mod.jar.out\smali\android\content\ContentResolver.smali
1 file(s) moved.
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali 1>services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali.new
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>move /Y services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali.new services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali
1 file(s) moved.
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" services.mod.jar.out\smali\com\android\server\ServerThread.smali 1>services.mod.jar.out\smali\com\android\server\ServerThread.smali.new
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>move /Y services.mod.jar.out\smali\com\android\server\ServerThread.smali.new services.mod.jar.out\smali\com\android\server\ServerThread.smali
1 file(s) moved.
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali 1>core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali.new
C:\Users\Ryan\AppData\Roaming\PDroidPatcher\tmp>move /Y core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali.new core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali
1 file(s) moved.
Applying PDroid patches
patching file smali/android/app/ContextImpl.smali
Hunk #2 succeeded at 155 (offset 8 lines).
Hunk #3 succeeded at 695 (offset 20 lines).
Hunk #4 succeeded at 1270 (offset 112 lines).
Hunk #5 succeeded at 1294 (offset 112 lines).
Hunk #6 succeeded at 1570 (offset 161 lines).
Hunk #7 succeeded at 1823 (offset 161 lines).
patching file smali/android/content/ContentResolver.smali
patching file smali/android/privacy/IPrivacySettingsManager.smali
patching file smali/android/privacy/IPrivacySettingsManager$Stub$Proxy.smali
patching file smali/android/privacy/IPrivacySettingsManager$Stub.smali
patching file smali/android/privacy/PrivacyFileObserver.smali
patching file smali/android/privacy/PrivacyPersistenceAdapter.smali
patching file smali/android/privacy/PrivacySettings$1.smali
patching file smali/android/privacy/PrivacySettingsManagerService.smali
patching file smali/android/privacy/PrivacySettingsManager.smali
patching file smali/android/privacy/PrivacySettings.smali
patching file smali/android/privacy/surrogate/PrivacyAccountManager$PrivacyAccountManagerFuture.smali
patching file smali/android/privacy/surrogate/PrivacyAccountManager.smali
patching file smali/android/privacy/surrogate/PrivacyActivityManagerService.smali
patching file smali/android/privacy/surrogate/PrivacyContentResolver.smali
patching file smali/android/privacy/surrogate/PrivacyCursor.smali
patching file smali/android/privacy/surrogate/PrivacyLocationManager$PrivacyLocationUpdater.smali
patching file smali/android/privacy/surrogate/PrivacyLocationManager.smali
patching file smali/android/privacy/surrogate/PrivacyTelephonyManager$PrivacyPhoneStateListener.smali
patching file smali/android/privacy/surrogate/PrivacyTelephonyManager.smali
patching file smali/com/android/server/am/ActivityManagerService.smali
Hunk #1 succeeded at 12780 (offset 92 lines).
Hunk #2 succeeded at 18937 (offset 104 lines).
patching file smali/com/android/server/ServerThread.smali
Hunk #1 succeeded at 43 with fuzz 1.
Hunk #2 succeeded at 522 (offset 139 lines).
patching file smali/java/lang/PrivacyInputStream.smali
patching file smali/java/lang/PrivacyProcessManager$PrivacyFileReader.smali
patching file smali/java/lang/PrivacyProcessManager.smali
patching file smali/java/lang/ProcessManager$ProcessImpl.smali
Creating updater script
Original mount statement not found, using default updater script
Building modified framework.jar
I: Checking whether sources has changed...
I: Smaling...
W: Unknown file type, ignoring: framework.mod.jar.out\smali\android\app\ContextImpl.smali.orig
W: Could not find resources
I: Building apk file...
created: META-INF/
inflated: META-INF/MANIFEST.MF
inflated: preloaded-classes
adding: preloaded-classes(in = 65693) (out= 11977)(deflated 81%)
updated manifest
Building modified services.jar
I: Checking whether sources has changed...
I: Smaling...
W: Unknown file type, ignoring: services.mod.jar.out\smali\com\android\server\ServerThread.smali.orig
W: Unknown file type, ignoring: services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali.orig
W: Could not find resources
I: Building apk file...
created: META-INF/
inflated: META-INF/MANIFEST.MF
updated manifest
Building modified core.jar
I: Checking whether sources has changed...
I: Smaling...
W: Could not find resources
I: Building apk file...
created: META-INF/
inflated: META-INF/MANIFEST.MF
inflated: org/apache/harmony/dalvik/ddmc/README.txt
inflated: com/ibm/icu4jni/ThirdPartyProject.prop
inflated: org/apache/xalan/Version.src
inflated: org/apache/xalan/processor/XSLProcessorVersion.src
inflated: org/apache/xalan/res/XSLTInfo.properties
inflated: org/apache/xml/serializer/XMLEntities.properties
inflated: org/apache/xml/serializer/HTMLEntities.properties
inflated: org/apache/xml/serializer/Version.src
inflated: org/apache/xml/serializer/output_text.properties
inflated: org/apache/xml/serializer/output_unknown.properties
inflated: org/apache/xml/serializer/output_html.properties
inflated: org/apache/xml/serializer/output_xml.properties
inflated: org/apache/xml/serializer/Encodings.properties
inflated: java/security/security.properties
inflated: java/util/logging/logging.properties
inflated: org/xmlpull/ThirdPartyProject.prop
inflated: org/kxml2/ThirdPartyProject.prop
inflated: org/xml/ThirdPartyProject.prop
inflated: classes.dex
adding: com/(in = 0) (out= 0)(stored 0%)
adding: com/ibm/(in = 0) (out= 0)(stored 0%)
adding: com/ibm/icu4jni/(in = 0) (out= 0)(stored 0%)
adding: com/ibm/icu4jni/ThirdPartyProject.prop(in = 318) (out= 202)(deflated 36%)
adding: java/(in = 0) (out= 0)(stored 0%)
adding: java/security/(in = 0) (out= 0)(stored 0%)
adding: java/security/security.properties(in = 5084) (out= 1837)(deflated 63%)
adding: java/util/(in = 0) (out= 0)(stored 0%)
adding: java/util/logging/(in = 0) (out= 0)(stored 0%)
adding: java/util/logging/logging.properties(in = 3123) (out= 1129)(deflated 63%)
adding: org/(in = 0) (out= 0)(stored 0%)
adding: org/apache/(in = 0) (out= 0)(stored 0%)
adding: org/apache/harmony/(in = 0) (out= 0)(stored 0%)
adding: org/apache/harmony/dalvik/(in = 0) (out= 0)(stored 0%)
adding: org/apache/harmony/dalvik/ddmc/(in = 0) (out= 0)(stored 0%)
adding: org/apache/harmony/dalvik/ddmc/README.txt(in = 78) (out= 69)(deflated 11%)
adding: org/apache/xalan/(in = 0) (out= 0)(stored 0%)
adding: org/apache/xalan/processor/(in = 0) (out= 0)(stored 0%)
adding: org/apache/xalan/processor/XSLProcessorVersion.src(in = 4126) (out= 1696)(deflated 58%)
adding: org/apache/xalan/res/(in = 0) (out= 0)(stored 0%)
adding: org/apache/xalan/res/XSLTInfo.properties(in = 1061) (out= 606)(deflated 42%)
adding: org/apache/xalan/Version.src(in = 4999) (out= 1909)(deflated 61%)
adding: org/apache/xml/(in = 0) (out= 0)(stored 0%)
adding: org/apache/xml/serializer/(in = 0) (out= 0)(stored 0%)
adding: org/apache/xml/serializer/Encodings.properties(in = 11338) (out= 3094)(deflated 72%)
adding: org/apache/xml/serializer/HTMLEntities.properties(in = 4353) (out= 2220)(deflated 49%)
adding: org/apache/xml/serializer/output_html.properties(in = 1841) (out= 922)(deflated 49%)
adding: org/apache/xml/serializer/output_text.properties(in = 1525) (out= 832)(deflated 45%)
adding: org/apache/xml/serializer/output_unknown.properties(in = 1769) (out= 948)(deflated 46%)
adding: org/apache/xml/serializer/output_xml.properties(in = 1818) (out= 943)(deflated 48%)
adding: org/apache/xml/serializer/Version.src(in = 4720) (out= 1869)(deflated 60%)
adding: org/apache/xml/serializer/XMLEntities.properties(in = 1086) (out= 647)(deflated 40%)
adding: org/kxml2/(in = 0) (out= 0)(stored 0%)
adding: org/kxml2/ThirdPartyProject.prop(in = 209) (out= 173)(deflated 17%)
adding: org/xml/(in = 0) (out= 0)(stored 0%)
adding: org/xml/ThirdPartyProject.prop(in = 224) (out= 178)(deflated 20%)
adding: org/xmlpull/(in = 0) (out= 0)(stored 0%)
adding: org/xmlpull/ThirdPartyProject.prop(in = 224) (out= 179)(deflated 20%)
updated manifest
Creating flashable patch zip
added manifest
adding: system/(in = 0) (out= 0)(stored 0%)
adding: system/framework/(in = 0) (out= 0)(stored 0%)
adding: system/framework/core.jar(in = 1908530) (out= 1897353)(deflated 0%)
adding: system/framework/framework.jar(in = 4087409) (out= 4062341)(deflated 0%)
adding: system/framework/services.jar(in = 883227) (out= 882283)(deflated 0%)
ignoring entry META-INF/
adding: META-INF/com/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/update-binary(in = 224244) (out= 144112)(deflated 35%)
adding: META-INF/com/google/android/updater-script(in = 239) (out= 142)(deflated 40%)
Creating flashable restore zip
added manifest
adding: system/(in = 0) (out= 0)(stored 0%)
adding: system/framework/(in = 0) (out= 0)(stored 0%)
adding: system/framework/core.jar(in = 1925304) (out= 1915877)(deflated 0%)
adding: system/framework/framework.jar(in = 4066524) (out= 4044700)(deflated 0%)
adding: system/framework/services.jar(in = 901158) (out= 900324)(deflated 0%)
ignoring entry META-INF/
adding: META-INF/com/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/update-binary(in = 224244) (out= 144112)(deflated 35%)
adding: META-INF/com/google/android/updater-script(in = 240) (out= 142)(deflated 40%)
Successfully created PDroid patch.
PDroid Patch: C:\Users\Ryan\Desktop\PDroidPatcher\PDroid-v1.27-StockMod-2-UCLA3-0.2kernel.zip.
You can flash it through recovery (for example CWM).
To restore your ROM and remove PDroid, flash PDroid-RESTORE-StockMod-2-UCLA3-0.2kernel.zip
TRY MOUNTING /SYSTEM IN RECOVERY (CWM) IF FLASHING THE PATCH DOES NOT WORK
One of the first things I did for the phone was trying to get this to work. It didn't haha, but I was a novice compared to my level of comfort with modifying apks etc. I might give it another go.
Me three
I would be really interested in seeing this work in the Skyrocket as well! From reading through the posts last night it appears one needs to have DEODX'd ROM to make this work.
What is pdroid?
Sent from my SAMSUNG-SGH-I727 using xda premium
remf4i said:
What is pdroid?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
permissions manager that doesnt load as an app (aka block facebook from using gps, reading contacts, reading phone status, IMEI, etc).
I.E. LBE privacy guard loads once the phone boots, Pdroid would effectively block once the phone receives power and doesnt wait for the phone OS to start.
This stemmed from a fear that LBE privacy guard wasnt very honest, but I went back to it and used droidwall from allowing LBE to communicate any data.
orlandoxpolice said:
permissions manager that doesnt load as an app (aka block facebook from using gps, reading contacts, reading phone status, IMEI, etc).
I.E. LBE privacy guard loads once the phone boots, Pdroid would effectively block once the phone receives power and doesnt wait for the phone OS to start.
This stemmed from a fear that LBE privacy guard wasnt very honest, but I went back to it and used droidwall from allowing LBE to communicate any data.
Click to expand...
Click to collapse
Thanks for the heads up on LBE, after some more research. It scares me that it's written by a Chinese source, and isn't open sourced, their website doesn't even work. I'm too leary of the Chinese Gov sponsored hacking against US targets.
creedicd said:
Thanks for the heads up on LBE, after some more research. It scares me that it's written by a Chinese source, and isn't open sourced, their website doesn't even work. I'm too leary of the Chinese Gov sponsored hacking against US targets.
Click to expand...
Click to collapse
Just use droidwall and block its ability to send any info packets from your ohone
Sent from my SAMSUNG-SGH-I727 using xda premium
Anyone have a patch for sky ics 7 speed- faux 10u- ucla3 modem?
I have yet to understand how to make it
Sent from my samsung-sgh-i727 using XDA
orlandoxpolice said:
The installation patching instructions look pretty annoying. Has anyone done this and has a CWM flashable patch I could use?
http://forum.xda-developers.com/showthread.php?t=1357056
Click to expand...
Click to collapse
Why would you use this???
odeccacccp said:
Why would you use this???
Click to expand...
Click to collapse
Do you like to have any control over the information on your phone?
I am using Pdroid on Sky-ICE 7.4 in addition to LBE. So far, I have have no problems running both on this ROM.
Also, whenever I flash a new ROM, I use Pdoid.
However, I have a T989...but I would assume it would work just as well on on an I727.
My method (when installing a new ROM):
1) Open PdroidPatcher.exe on Windows
2) Select a ROM of your choice (Pdroid prompts you for the file)
3) Patch
4) Copy both the original ROM and the Pdroid generated .zip file to your SD
5) Reboot into CWM
6) *** BACKUP ***
7) Wipe (I use darkside's superwipe)
8) Install ROM from SD card
9) I let the ROM boot up and then reboot again into CWM
10) Install Pdroid generated .zip file
11) Reboot and make sure you install the Pdoid app from the market (play store)
12) Enjoy!
It really isn't that complicated - but if it doesn't work for you, don't blame me

[Q][KERNEL] Errors while compiling with GCC 4.7

I use Linaro 2012.05 GCC 4.7 (arm-eabi) and when I compile stock Nexus S kernel I have these errors:
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 4 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
CC arch/arm/boot/compressed/misc.o
In file included from arch/arm/plat-samsung/include/plat/uncompress.h:30:0,
from arch/arm/mach-s5pv210/include/mach/uncompress.h:17,
from arch/arm/boot/compressed/misc.c:33:
arch/arm/plat-samsung/include/plat/regs-serial.h:284:27: warning: 'struct uart_port' declared inside parameter list [enabled by default]
arch/arm/plat-samsung/include/plat/regs-serial.h:284:27: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and output
arm-eabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o and output
make[2]: *** [arch/arm/boot/compressed/vmlinux] Errore 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Errore 2
make: *** [zImage] Errore 2
Click to expand...
Click to collapse
Can someone help me?
PS:
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:~/android-toolchain-eabi/bin
Click to expand...
Click to collapse
div usage mismatch fix
See a potential solution here.

[Guide][Compile][Patching]A Kernel From Source For Newbies[Any Device]

Hey Guys,
With All the awesome development going on in the Android world. There Are Many newbies who want to strat development but they exactly Dont Know How To begin with or from where to strat with. So I will Write a guide on how to compile your own kernel from source
=================
What Is A Kernel???
=================
The operating system of a device is the part of the device responsible for basic use and administration. This includes the kernel and device drivers, boot loader, command shell or other user interface, and basic file and system utilities. Whereas the user interface is the outermost portition of the operating system, kernel is the innermost. It is the core internals, the software that provides basic services for all other parts of the system, manages hardware and distributes system resources.
============================
Prerequisites To Compile A kernel
============================
1.A Unix Based Os(Ubuntu Recommended Both 32-bit and 64-bit are good to compile a kernel)
2.A few packages, to let the system know that we are compiling a kernel
3. The Source Code of kernel for your Device
Ok, So Now Lets Begin
==================
Packages Required:
==================
Ok So Now Open The Terminal And Copy Paste This Code:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386 git
Okay SO Now If You Are using Ubuntu12.04 , you need to create links of certain files
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Okay now we are done with installing packages
SO Now we need java
Open a terminal and Run This Code:
sudo add-apt-repository ppa:ferramroberto/java
Click to expand...
Click to collapse
Then Run This:
sudo apt-get update
Click to expand...
Click to collapse
Then Type This:
sudo apt-get-install sun-java6-jdk
Click to expand...
Click to collapse
So Now You Have all the needed packages to compile a kernel
Next you need the bootimagetools,source code of kernel and Androidtoolchainsto compile a kernel
Bootimagetools:https://github.com/SaumitraYadav/Boot-Image-tools
AndroidToolchains:https://github.com/SaumitraYadav/Android_Toolchains
Okay once you have Downloaded everything ... now Lets Start Compiling A Kernel
Ok So Fireup A Terminal :
Code:
mkdir kernel
This Will Create a Directory named kernel in your Home Folder
Now extract your kernel Source in this directory
Then Run This:
Code:
cd kernel
Now You Have To Edit the Make File:
Code:
gedit Makefile
The Make file will open.........look out for this and change CROSS_COMPILE= "your toolchain path"
EXAMPLE:
Code:
CROSS_COMPILE?= /home/saumitra/Downloads/Toolchains/arm-eabi-4.4.3/bin/arm-eabi-
this will open up Makefile in gedit, now set the path where youn have downloaded and extracted the toolchains
Now, make the kernel config
Code:
make pico_defconfig
Note: I have a Htc Explorer and my device codename is pico. So i run pico_defconfig
Now Other device users have to look for codename or config names in arch/arm/configs
This Will Make a working kernel config according to the source
Now, if You Wanna Make Some Changes In Your Source Do so , and run this command to start compiling:
Code:
make -jX
The X can be replaced by the maximum number of jobs your computer can handle simultaneously.. The higher this number, the faster the compiling will get.. But do not enter a number too high, your computer may explode due to overheating.
Okay if all goes well your kernel will be compiled in 15mins
The resulting kernel will be in Kernel/arch/arm/boot/zImage
Now We also need modules for wifi and BT to work. So,
cd kernel
Click to expand...
Click to collapse
mkdir modules
Click to expand...
Click to collapse
find . -name '*ko' -exec cp '{}' modules \;
Click to expand...
Click to collapse
Okay So Now The Moules will be in kernel/modules
So Now We will pack the kernel to be flashed on the target Device
-Okay So Now Get A Working Boot.img Of THe Rom on which Wanna Test Your Kernel
-Download and extract The Bootimagetools From The Link Given Above
-place the boot.img in source_img folder inside the boot.img-tools
-enter the bootimagetools Directory
-unpack(This Will extract the boot.img)
$ mkdir -p unpack
$ tools/unpackbootimg -i source_img/boot.img -o unpack
Click to expand...
Click to collapse
-Extracting boot.img-ramdisk.gz(This Will Extract The ramdisk From the boot.img)
$ mkdir -p boot
$ cd boot
$ gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
$ cd ../
Click to expand...
Click to collapse
-Packing a new ramdisk(This Will Pack A new ramdisk which will be used in your kernel)
$ tools/mkbootfs boot | gzip > unpack/boot.img-ramdisk-new.gz
Click to expand...
Click to collapse
Now As we want to create a boot.img from the zImage you made so copy the zImage from arch/arm/boot
Then goto the folder unpack in bootimagetools directory and delete boot.img-zImage
now paste the zImage You copied from arch/arm/boot and paste it in unpack folder and rename it to boot.img-zImage
-Create a new boot.img:
$ mkdir -p target_img
$ tools/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk-new.gz -o target_img/boot.img --base `cat unpack/boot.img-base`
Click to expand...
Click to collapse
Done
Now Take The boot.img for target_img folder and flash it via fastboot and dont forget to push modules else wifi will not work
=============================
Patching The kernel[The Easy Way]
=============================
This will Show You How to Patch your kernel to the latest version.
All The Patches are Available on kernel.org.
So If you apply the patches manually, then your source code will be messed up and you will face compiling errors+ it's time consuming to allow every patch as yes
So I am going to use a program called interdiff to
generate a patch representing the differences between two patches and then
apply the result.
Download:
Code:
http://cyberelk.net/tim/data/patchutils/stable/patchutils-0.3.3.tar.xz
SO Now Setting up the program to work :
1. Download the given file and extract it somewhere ,you swill get a folder named patchutils-0.3.3
2. First Install these Two Packages:
Code:
sudo apt-get install gcc
sudo apt-get install g++
3. Now cd to the folder patchutils-0.3.3
4. Now Type this in terminal
Code:
./configure
5.Now type this
Code:
make
6. Then this
Code:
sudo make install
Now You have setup the program 'interdiff' for applying the patches
To Apply The patches:
Code:
interdiff -z patch-xy patch-yx | patch -p1
Code:
patch-xy: The current kernel version ( for example= patch-3.0.97)
patch-yx: The version to be patched ( for example=patch-3.0.98)
Note: Both the patches should be in your kernel source directory
Credits:
@Red Devil (For Teaching me how to compile a kernel)
Awesome
Markyzz said:
Awesome
Click to expand...
Click to collapse
Thanks
Please Unquote The Post
Great Guide For Noobs Like Me
Speaking Frankly There is a guide by @legen_dary which is really good.
I Don't think this is actually needed.
Thank you.
Brother.. At least change it a little eh??
Or if you want, I can have the original guide thread handed over to you..
ғг๏๓ ҭђє ғเรђ!
Very very useful i'll take a closer look at it later tonight! :good:
Corrected the grammatical errors Happy compiling
Sent from my HTC Explorer using Tapatalk 4 Beta
Added Guide on How to Patch the Kernel Happy compiling
Saumitra Yadav said:
Added Guide on How to Patch the Kernel Happy compiling
Click to expand...
Click to collapse
i need a easy way for patching kernel ...thnxx man u helped a lot ..>!!:laugh:
How to solve this?
Code:
LD drivers/hid/built-in.o
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1408: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1408: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1409: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1409: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1410: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1410: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1415: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1415: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1416: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1416: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1417: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1417: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1418: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1418: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1419: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1419: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1423: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1423: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1424: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1424: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1425: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1425: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1426: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1426: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1427: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1427: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1431: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1431: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1432: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1432: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1433: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1433: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1434: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1434: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1435: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-tamsui-jlo.c:1435: error: (near initialization for 'ion_pdata.heaps')
make[3]: *** [arch/arm/mach-msm/board-tamsui-jlo.o] Błąd 1
make[3]: *** Oczekiwanie na niezakończone zadania....
CC net/core/utils.o
CC drivers/hwmon/hwmon.o
CC fs/fat/fatent.o
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:862: error: 'KGSL_3D0_REG_MEMORY' undeclared here (not in a function)
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:868: error: 'KGSL_3D0_IRQ' undeclared here (not in a function)
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:875: error: variable 'kgsl_3d0_pdata' has initializer but incomplete type
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:876: error: unknown field 'pwrlevel' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:876: error: extra brace group at end of initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:876: error: (near initialization for 'kgsl_3d0_pdata')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:877: error: extra brace group at end of initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:877: error: (near initialization for 'kgsl_3d0_pdata')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:881: error: extra brace group at end of initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:881: error: (near initialization for 'kgsl_3d0_pdata')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:885: error: extra brace group at end of initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:885: error: (near initialization for 'kgsl_3d0_pdata')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:890: error: unknown field 'init_level' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:891: error: unknown field 'num_levels' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:892: error: unknown field 'set_grp_async' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:893: error: unknown field 'idle_timeout' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:894: error: unknown field 'strtstp_sleepwake' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:895: error: unknown field 'nap_allowed' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:896: error: unknown field 'clk_map' specified in initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c: In function 'msm7x25a_kgsl_3d0_init':
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:912: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:913: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:913: error: 'struct resource' has no member named 'gpu_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:914: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:914: error: 'struct resource' has no member named 'bus_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:915: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:915: error: 'struct resource' has no member named 'gpu_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:916: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:916: error: 'struct resource' has no member named 'bus_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c: In function 'msm8x25_kgsl_3d0_init':
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:923: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:924: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:928: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:928: error: 'struct resource' has no member named 'gpu_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:930: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:930: error: 'struct resource' has no member named 'gpu_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:932: error: invalid use of undefined type 'struct kgsl_device_platform_data'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:932: error: 'struct resource' has no member named 'bus_freq'
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c: At top level:
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:1581: error: initializer element is not constant
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:1581: error: (near initialization for 'msm8625_kgsl_3d0_resources[0].name')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:1587: error: initializer element is not constant
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/devices-tamsui-jlo.c:1587: error: (near initialization for 'msm8625_kgsl_3d0_resources[1].name')
make[3]: *** [arch/arm/mach-msm/devices-tamsui-jlo.o] Błąd 1
CC fs/fat/file.o
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:664: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:664: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:665: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:665: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:666: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:666: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:671: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:671: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:672: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:672: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:673: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:673: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:674: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:674: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:675: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:675: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:679: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:679: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:680: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:680: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:681: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:681: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:682: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:682: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:683: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:683: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:687: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:687: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:688: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:688: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:689: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:689: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:690: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:690: error: (near initialization for 'ion_pdata.heaps')
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:691: error: field name not in record or union initializer
/home/lozohcum/CM/kernel/sony/msm7x27a-3.4/arch/arm/mach-msm/board-qrd7627a.c:691: error: (near initialization for 'ion_pdata.heaps')
make[3]: *** [arch/arm/mach-msm/board-qrd7627a.o] Błąd 1
make[2]: *** [arch/arm/mach-msm] Błąd 2
make[2]: *** Oczekiwanie na niezakończone zadania....
do I have to add -w to more flags?
This is part of my makefile
Code:
CFLAGS_MODULE = -w
AFLAGS_MODULE = -w
LDFLAGS_MODULE =
CFLAGS_KERNEL = -w
AFLAGS_KERNEL = -w
CFLAGS_GCOV = -fprofile-arcs -ftest-coverage
hey bro @Saumitra Yadav , can you help me to fix this? thx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ocoot said:
hey bro @Saumitra Yadav , can you help me to fix this? thx
Click to expand...
Click to collapse
Some Package Is Missing Please Give me A pastie of full error
Saumitra Yadav said:
Some Package Is Missing Please Give me A pastie of full error
Click to expand...
Click to collapse
now it's fixed. just install lzop from terminal
mmm can you make a tutorial how to add gov,i/o or freq? coz i added some gov on my kernel when i flash it, it not showing on no frillis, but on command "make menuconfig" its showing the gov i am added before -_-
@Saumitra Yadav can you help me with this?
stuck because of this from 2 days.
Xperia mini | Stock GB kernel Source | ndk 9b
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
arch/arm/boot/compressed/head.S: Assembler messages:
arch/arm/boot/compressed/head.S:363: Warning: (null)
arch/arm/boot/compressed/head.S:444: Warning: (null)
arch/arm/boot/compressed/head.S:465: Warning: (null)
arch/arm/boot/compressed/head.S:484: Warning: (null)
arch/arm/boot/compressed/head.S:492: Warning: (null)
arch/arm/boot/compressed/head.S:783: Warning: (null)
arch/arm/boot/compressed/head.S:822: Warning: (null)
arch/arm/boot/compressed/head.S:823: Warning: (null)
arch/arm/boot/compressed/head.S:870: Warning: (null)
arch/arm/boot/compressed/head.S:877: Warning: (null)
arch/arm/boot/compressed/head.S:885: Warning: (null)
arch/arm/boot/compressed/head.S:896: Warning: (null)
arch/arm/boot/compressed/head.S:910: Warning: (null)
arch/arm/boot/compressed/head.S:942: Warning: (null)
arch/arm/boot/compressed/head.S:944: Warning: (null)
arch/arm/boot/compressed/head.S:945: Warning: (null)
arch/arm/boot/compressed/head.S:952: Warning: (null)
arch/arm/boot/compressed/head.S:984: Warning: (null)
GZIP arch/arm/boot/compressed/piggy.gz
AS arch/arm/boot/compressed/piggy.o
CC arch/arm/boot/compressed/misc.o
LD arch/arm/boot/compressed/vmlinux
arm-linux-androideabi-ld: error: arch/arm/boot/compressed/piggy.o: unknown CPU architecture
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
[email protected]:~/android/kernel/4.0.2.A.0.84/kernel$
piousheart said:
@Saumitra Yadav can you help me with this?
stuck because of this from 2 days.
Xperia mini | Stock GB kernel Source | ndk 9b
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
arch/arm/boot/compressed/head.S: Assembler messages:
arch/arm/boot/compressed/head.S:363: Warning: (null)
arch/arm/boot/compressed/head.S:444: Warning: (null)
arch/arm/boot/compressed/head.S:465: Warning: (null)
arch/arm/boot/compressed/head.S:484: Warning: (null)
arch/arm/boot/compressed/head.S:492: Warning: (null)
arch/arm/boot/compressed/head.S:783: Warning: (null)
arch/arm/boot/compressed/head.S:822: Warning: (null)
arch/arm/boot/compressed/head.S:823: Warning: (null)
arch/arm/boot/compressed/head.S:870: Warning: (null)
arch/arm/boot/compressed/head.S:877: Warning: (null)
arch/arm/boot/compressed/head.S:885: Warning: (null)
arch/arm/boot/compressed/head.S:896: Warning: (null)
arch/arm/boot/compressed/head.S:910: Warning: (null)
arch/arm/boot/compressed/head.S:942: Warning: (null)
arch/arm/boot/compressed/head.S:944: Warning: (null)
arch/arm/boot/compressed/head.S:945: Warning: (null)
arch/arm/boot/compressed/head.S:952: Warning: (null)
arch/arm/boot/compressed/head.S:984: Warning: (null)
GZIP arch/arm/boot/compressed/piggy.gz
AS arch/arm/boot/compressed/piggy.o
CC arch/arm/boot/compressed/misc.o
LD arch/arm/boot/compressed/vmlinux
arm-linux-androideabi-ld: error: arch/arm/boot/compressed/piggy.o: unknown CPU architecture
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
[email protected]:~/android/kernel/4.0.2.A.0.84/kernel$
Click to expand...
Click to collapse
Wrong Toolchain Try This Toolchain
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7
Saumitra Yadav said:
Wrong Toolchain Try This Toolchain
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7
Click to expand...
Click to collapse
I don't know how to use git.
where to download that toolchain
Any idea how much time would it take to download all the neccesary things except the packages used for setting up build envi?
Sent from my GT-I9100 using xda premium
Doesn't take me long to download in Ubuntu.
Samsung open source will probably take you longest
engloa said:
Doesn't take me long to download in Ubuntu.
Samsung open source will probably take you longest
Click to expand...
Click to collapse
Hey buddy..
Haha..nice to see u everywhere.
Thank u..
Sent from my GT-I9100 using xda premium

[Q] Kernel compilation weird errors

I've been trying for two days now to compile AGNi Kernel with Kexec-hardboot enabled under menuconfig>boot options and every damn time i get this error. If @psndna88 could help me it'd be nice.
here is the terminal
Code:
[email protected]:~/android/kernel$ make -j2 ARCH=arm
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
HOSTCC scripts/genksyms/genksyms.o
Generating include/generated/mach-types.h
CC kernel/bounds.s
GEN include/generated/bounds.h
CC arch/arm/kernel/asm-offsets.s
GEN include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
SHIPPED scripts/genksyms/lex.c
SHIPPED scripts/genksyms/parse.h
CC scripts/mod/empty.o
SHIPPED scripts/genksyms/keywords.c
SHIPPED scripts/genksyms/parse.c
HOSTCC scripts/genksyms/lex.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/genksyms/parse.o
HOSTCC scripts/mod/modpost.o
HOSTLD scripts/genksyms/genksyms
HOSTCC scripts/selinux/genheaders/genheaders
HOSTCC scripts/selinux/mdp/mdp
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
HOSTCC scripts/mod/sumversion.o
HOSTCC scripts/bin2c
HOSTLD scripts/mod/modpost
CC init/main.o
HOSTCC usr/gen_init_cpio
GEN usr/initramfs_data.cpio
AS usr/initramfs_data.o
LD usr/built-in.o
CC arch/arm/vfp/vfpmodule.o
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/do_mounts.o
AS arch/arm/vfp/entry.o
AS arch/arm/vfp/vfphw.o
CC arch/arm/vfp/vfpsingle.o
CC init/do_mounts_rd.o
CC arch/arm/vfp/vfpdouble.o
CC init/do_mounts_initrd.o
LD arch/arm/vfp/vfp.o
LD arch/arm/vfp/built-in.o
CC init/initramfs.o
LD arch/arm/mvp/commkm/built-in.o
CC [M] arch/arm/mvp/commkm/check_kconfig.o
CC [M] arch/arm/mvp/commkm/comm_ev_kernel.o
CC [M] arch/arm/mvp/commkm/comm.o
CC init/calibrate.o
CC init/version.o
/tmp/ccdjofq2.s: Assembler messages:
/tmp/ccdjofq2.s:194: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:208: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2328: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2342: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2366: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2380: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2443: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2457: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2624: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2638: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2778: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2792: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2808: Error: garbage following instruction -- `dmb ish'
/tmp/ccdjofq2.s:2822: Error: garbage following instruction -- `dmb ish'
scripts/Makefile.build:305: recipe for target 'arch/arm/mvp/commkm/comm.o' failed
make[2]: *** [arch/arm/mvp/commkm/comm.o] Error 1
scripts/Makefile.build:441: recipe for target 'arch/arm/mvp/commkm' failed
make[1]: *** [arch/arm/mvp/commkm] Error 2
Makefile:955: recipe for target 'arch/arm/mvp' failed
make: *** [arch/arm/mvp] Error 2
make: *** Waiting for unfinished jobs....
LD init/mounts.o
LD init/built-in.o
[email protected]:~/android/kernel$
I am trying to compile this kernel because this thread.
Solved that one, but now one annoying one pops up
/home/lanimereala/android/omni/kernel/samsung/i9305/arm-cortex_a9-linux-gnueabihf-linaro_4.9.4/bin/arm-eabi-nm: 'arch/arm/boot/compressed/vmlinux': No such file
OBJCOPY arch/arm/boot/zImage
/home/lanimereala/android/omni/kernel/samsung/i9305/arm-cortex_a9-linux-gnueabihf-linaro_4.9.4/bin/arm-eabi-objcopy: 'arch/arm/boot/compressed/vmlinux': No such file
/home/lanimereala/android/omni/kernel/samsung/i9305/arch/arm/boot/Makefile:58: recipe for target 'arch/arm/boot/zImage' failed
make[1]: *** [arch/arm/boot/zImage] Error 1
/home/lanimereala/android/omni/kernel/samsung/i9305/arch/arm/Makefile:283: recipe for target 'zImage' failed
make: *** [zImage] Error 2
Solved that one, but now one annoying one pops up
/home/lanimereala/android/omni/kernel/samsung/i9305/arm-cortex_a9-linux-gnueabihf-linaro_4.9.4/bin/arm-eabi-nm: 'arch/arm/boot/compressed/vmlinux': No such file
OBJCOPY arch/arm/boot/zImage
/home/lanimereala/android/omni/kernel/samsung/i9305/arm-cortex_a9-linux-gnueabihf-linaro_4.9.4/bin/arm-eabi-objcopy: 'arch/arm/boot/compressed/vmlinux': No such file
/home/lanimereala/android/omni/kernel/samsung/i9305/arch/arm/boot/Makefile:58: recipe for target 'arch/arm/boot/zImage' failed
make[1]: *** [arch/arm/boot/zImage] Error 1
/home/lanimereala/android/omni/kernel/samsung/i9305/arch/arm/Makefile:283: recipe for target 'zImage' failed
make: *** [zImage] Error 2

Categories

Resources