Guest ayziaa Posted October 20, 2011 Report Posted October 20, 2011 (edited) CM team take position regarding the SDK developpement http://www.androidpo...cs-source-does/ Have you seen this? Edited October 20, 2011 by ayziaa
Guest timfimjim Posted October 20, 2011 Report Posted October 20, 2011 Cm9, just to check is cm8 honeycomb then?
Guest hugobosslives Posted October 20, 2011 Report Posted October 20, 2011 Cm9, just to check is cm8 honeycomb then? well its been reversed for honeycomb (but that may never happen officially)
Guest hecatae Posted October 21, 2011 Report Posted October 21, 2011 Actually, I'd love to try, if just someone would take the time to put the files together in the right way. Feel that I don't have the skills and confidence in this subject to do it myself. Quite sure I wouldn't be the only one trying it out if it was possible neither... read this: Ippe H was responsible for all the honeycomb ports for blade, and is now looking at the ics sdk system image, watch that thread
Guest cicciopuzzo Posted October 21, 2011 Report Posted October 21, 2011 I've found the applications from ics... but if i want to install i read a error message... is possible to convert these app (like gmail calendar camera ecc) for gingerbread??
Guest sej7278 Posted October 21, 2011 Report Posted October 21, 2011 Will we have to hope for a new kernel source release or can ICS be run on the 2.6.35.7 kernel we have? strictly speaking ICS should use kernel 3.0 but lets face it we've been running gingerbread on 2.6.32 for months when it should have been 2.6.35 i can't see we'd get a 3.0 kernel for the blade as i doubt zte would be making any ICS upgrades for blade/skate/v9 i'm not convinced the blade/skate are up to running ics, it seems to rely heavily on accelerated graphics, and its probably pushing arm6 too far.
Guest Chris_M Posted October 21, 2011 Report Posted October 21, 2011 Still no news of when the source code will be released.... http://www.theregister.co.uk/2011/10/20/google_ice_cream_sandwich_freedom/
Guest ayziaa Posted October 21, 2011 Report Posted October 21, 2011 Apparently ice cream sandwich sdk has been ported on the Nexus S. http://www.androidcentral.com/ice-cream-sandwich-sdk-ports-begin-nexus-s-4g?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A%20androidcentral%20%28Android%20Central%29
Guest .mil Posted October 21, 2011 Report Posted October 21, 2011 Apparently ice cream sandwich sdk has been ported on the Nexus S. http://www.androidce...id%20Central%29 Time to sell Zte Libra and to buy Nexus S
Guest ayziaa Posted October 21, 2011 Report Posted October 21, 2011 (edited) I think we should give it some time and we will see... If we don't have sdk port for blade, there allways will be CM9 in a fews weeks or months. If ICS can run on the blade's cpu, there is no reason to think we won't have ICS at some point. Correct me if I'm wrong? Some people says that ICS needs 1go of rom or something, that it is very heavy... I don't know if you agree? But if it is true, it would be a huge step back. Edited October 21, 2011 by ayziaa
Guest Carlos Manuel Leemet Posted October 21, 2011 Report Posted October 21, 2011 (edited) Android ICS init.rc by: one of JetDroid developer... init.rc on early-init start ueventd # create mountpoints mkdir /mnt 0775 root system on init sysclktz 0 loglevel 3 # setup the global environment export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin export LD_LIBRARY_PATH /vendor/lib:/system/lib export ANDROID_BOOTLOGO 1 export ANDROID_ROOT /system export ANDROID_ASSETS /system/app export ANDROID_DATA /data export ASEC_MOUNTPOINT /mnt/asec export LOOP_MOUNTPOINT /mnt/obb export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar # Backward compatibility symlink /system/etc /etc symlink /sys/kernel/debug /d # Right now vendor lives on the same filesystem as system, # but someday that may change. symlink /system/vendor /vendor # Create cgroup mount point for cpu accounting mkdir /acct mount cgroup none /acct cpuacct mkdir /acct/uid mkdir /system mkdir /data 0771 system system mkdir /cache 0770 system cache mkdir /config 0500 root root # Directory for putting things only root should see. mkdir /mnt/secure 0700 root root # Directory for staging bindmounts mkdir /mnt/secure/staging 0700 root root # Directory-target for where the secure container # imagefile directory will be bind-mounted mkdir /mnt/secure/asec 0700 root root # Secure container public mount points. mkdir /mnt/asec 0700 root system mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000 # Filesystem image public mount points. mkdir /mnt/obb 0700 root system mount tmpfs tmpfs /mnt/obb mode=0755,gid=1000 write /proc/sys/kernel/panic_on_oops 1 write /proc/sys/kernel/hung_task_timeout_secs 0 write /proc/cpu/alignment 4 write /proc/sys/kernel/sched_latency_ns 10000000 write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000 write /proc/sys/kernel/sched_compat_yield 1 write /proc/sys/kernel/sched_child_runs_first 0 # Create cgroup mount points for process groups mkdir /dev/cpuctl mount cgroup none /dev/cpuctl cpu chown system system /dev/cpuctl chown system system /dev/cpuctl/tasks chmod 0777 /dev/cpuctl/tasks write /dev/cpuctl/cpu.shares 1024 mkdir /dev/cpuctl/fg_boost chown system system /dev/cpuctl/fg_boost/tasks chmod 0777 /dev/cpuctl/fg_boost/tasks write /dev/cpuctl/fg_boost/cpu.shares 1024 mkdir /dev/cpuctl/bg_non_interactive chown system system /dev/cpuctl/bg_non_interactive/tasks chmod 0777 /dev/cpuctl/bg_non_interactive/tasks # 5.0 % write /dev/cpuctl/bg_non_interactive/cpu.shares 52 # Allow everybody to read the xt_qtaguid resource tracking misc dev. # This is needed by any process that uses socket tagging. chmod 0644 /dev/xt_qtaguid on fs # mount mtd partitions # Mount /system rw first to give the filesystem a chance to save a checkpoint mount yaffs2 mtd@system /system mount yaffs2 mtd@system /system ro remount mount yaffs2 mtd@userdata /data nosuid nodev mount yaffs2 mtd@cache /cache nosuid nodev on post-fs # once everything is setup, no need to modify / mount rootfs rootfs / ro remount # We chown/chmod /cache again so because mount is run as root + defaults chown system cache /cache chmod 0770 /cache # This may have been created by the recovery system with odd permissions chown system cache /cache/recovery chmod 0770 /cache/recovery #change permissions on vmallocinfo so we can grab it from bugreports chown root log /proc/vmallocinfo chmod 0440 /proc/vmallocinfo #change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks chown root system /proc/kmsg chmod 0440 /proc/kmsg chown root system /proc/sysrq-trigger chmod 0220 /proc/sysrq-trigger # create the lost+found directories, so as to enforce our permissions mkdir /cache/lost+found 0770 root root on post-fs-data # We chown/chmod /data again so because mount is run as root + defaults chown system system /data chmod 0771 /data # Create dump dir and collect dumps. # Do this before we mount cache so eventually we can use cache for # storing dumps on platforms which do not have a dedicated dump partition. mkdir /data/dontpanic 0750 root log # Collect apanic data, free resources and re-arm trigger copy /proc/apanic_console /data/dontpanic/apanic_console chown root log /data/dontpanic/apanic_console chmod 0640 /data/dontpanic/apanic_console copy /proc/apanic_threads /data/dontpanic/apanic_threads chown root log /data/dontpanic/apanic_threads chmod 0640 /data/dontpanic/apanic_threads write /proc/apanic_console 1 # create basic filesystem structure mkdir /data/misc 01771 system misc mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth mkdir /data/misc/bluetooth 0770 system system mkdir /data/misc/keystore 0700 keystore keystore mkdir /data/misc/keychain 0771 system system mkdir /data/misc/vpn 0770 system vpn mkdir /data/misc/systemkeys 0700 system system # give system access to wpa_supplicant.conf for backup and restore mkdir /data/misc/wifi 0770 wifi wifi chmod 0660 /data/misc/wifi/wpa_supplicant.conf mkdir /data/local 0771 shell shell mkdir /data/local/tmp 0771 shell shell mkdir /data/data 0771 system system mkdir /data/app-private 0771 system system mkdir /data/app 0771 system system mkdir /data/property 0700 root root # create dalvik-cache, so as to enforce our permissions mkdir /data/dalvik-cache 0771 system system # create resource-cache and double-check the perms mkdir /data/resource-cache 0771 system system chown system system /data/resource-cache chmod 0771 /data/resource-cache # create the lost+found directories, so as to enforce our permissions mkdir /data/lost+found 0770 root root # create directory for DRM plug-ins mkdir /data/drm 0774 drm drm # If there is no fs-post-data action in the init.<device>.rc file, you # must uncomment this line, otherwise encrypted filesystems # won't work. # Set indication (checked by vold) that we have finished this action #setprop vold.post_fs_data_done 1 chown system system /sys/class/android_usb/android0/f_mass_storage/lun/file chmod 0660 /sys/class/android_usb/android0/f_mass_storage/lun/file chown system system /sys/class/android_usb/android0/f_rndis/ethaddr chmod 0660 /sys/class/android_usb/android0/f_rndis/ethaddr on boot # basic network init ifup lo hostname localhost domainname localdomain # set RLIMIT_NICE to allow priorities from 19 to -20 setrlimit 13 40 40 # Memory management. Basic kernel parameters, and allow the high # level system server to be able to adjust the kernel OOM driver # paramters to match how it is managing things. write /proc/sys/vm/overcommit_memory 1 write /proc/sys/vm/min_free_order_shift 4 chown root system /sys/module/lowmemorykiller/parameters/adj chmod 0664 /sys/module/lowmemorykiller/parameters/adj chown root system /sys/module/lowmemorykiller/parameters/minfree chmod 0664 /sys/module/lowmemorykiller/parameters/minfree # Set init and its forked children's oom_adj. write /proc/1/oom_adj -16 # Tweak background writeout write /proc/sys/vm/dirty_expire_centisecs 200 write /proc/sys/vm/dirty_background_ratio 5 # Permissions for System Server and daemons. chown radio system /sys/android_power/state chown radio system /sys/android_power/request_state chown radio system /sys/android_power/acquire_full_wake_lock chown radio system /sys/android_power/acquire_partial_wake_lock chown radio system /sys/android_power/release_wake_lock chown radio system /sys/power/state chown radio system /sys/power/wake_lock chown radio system /sys/power/wake_unlock chmod 0660 /sys/power/state chmod 0660 /sys/power/wake_lock chmod 0660 /sys/power/wake_unlock chown system system /sys/class/timed_output/vibrator/enable chown system system /sys/class/leds/keyboard-backlight/brightness chown system system /sys/class/leds/lcd-backlight/brightness chown system system /sys/class/leds/button-backlight/brightness chown system system /sys/class/leds/jogball-backlight/brightness chown system system /sys/class/leds/red/brightness chown system system /sys/class/leds/green/brightness chown system system /sys/class/leds/blue/brightness chown system system /sys/class/leds/red/device/grpfreq chown system system /sys/class/leds/red/device/grppwm chown system system /sys/class/leds/red/device/blink chown system system /sys/class/leds/red/brightness chown system system /sys/class/leds/green/brightness chown system system /sys/class/leds/blue/brightness chown system system /sys/class/leds/red/device/grpfreq chown system system /sys/class/leds/red/device/grppwm chown system system /sys/class/leds/red/device/blink chown system system /sys/class/timed_output/vibrator/enable chown system system /sys/module/sco/parameters/disable_esco chown system system /sys/kernel/ipv4/tcp_wmem_min chown system system /sys/kernel/ipv4/tcp_wmem_def chown system system /sys/kernel/ipv4/tcp_wmem_max chown system system /sys/kernel/ipv4/tcp_rmem_min chown system system /sys/kernel/ipv4/tcp_rmem_def chown system system /sys/kernel/ipv4/tcp_rmem_max chown root radio /proc/cmdline # Define TCP buffer sizes for various networks # ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax, setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208 setprop net.tcp.buffersize.wifi 524288,1048576,2097152,262144,524288,1048576 setprop net.tcp.buffersize.lte 524288,1048576,2097152,262144,524288,1048576 setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208 setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040 setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680 # Set this property so surfaceflinger is not started by system_init setprop system_init.startsurfaceflinger 0 class_start core class_start main on nonencrypted class_start late_start on charger class_start charger on property:vold.decrypt=trigger_reset_main class_reset main on property:vold.decrypt=trigger_load_persist_props load_persist_props on property:vold.decrypt=trigger_post_fs_data trigger post-fs-data on property:vold.decrypt=trigger_restart_min_framework class_start main on property:vold.decrypt=trigger_restart_framework class_start main class_start late_start on property:vold.decrypt=trigger_shutdown_framework class_reset late_start class_reset main # Used to disable USB when switching states on property:sys.usb.config=none stop adbd write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/bDeviceClass 0 setprop sys.usb.state $sys.usb.config # adb only USB configuration # This should only be used during device bringup # and as a fallback if the USB manager fails to set a standard configuration on property:sys.usb.config=adb write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 18d1 write /sys/class/android_usb/android0/idProduct D002 write /sys/class/android_usb/android0/functions $sys.usb.config write /sys/class/android_usb/android0/enable 1 start adbd setprop sys.usb.state $sys.usb.config # USB accessory configuration on property:sys.usb.config=accessory write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 18d1 write /sys/class/android_usb/android0/idProduct 2d00 write /sys/class/android_usb/android0/functions $sys.usb.config write /sys/class/android_usb/android0/enable 1 setprop sys.usb.state $sys.usb.config # USB accessory configuration, with adb on property:sys.usb.config=accessory,adb write /sys/class/android_usb/android0/enable 0 write /sys/class/android_usb/android0/idVendor 18d1 write /sys/class/android_usb/android0/idProduct 2d01 write /sys/class/android_usb/android0/functions $sys.usb.config write /sys/class/android_usb/android0/enable 1 start adbd setprop sys.usb.state $sys.usb.config # Used to set USB configuration at boot and to switch the configuration # when changing the default configuration on property:persist.sys.usb.config=* setprop sys.usb.config $persist.sys.usb.config ## Daemon processes to be run by init. ## service ueventd /sbin/ueventd class core critical service console /system/bin/sh class core console disabled user shell group log on property:ro.debuggable=1 start console # adbd is controlled via property triggers in init.<platform>.usb.rc service adbd /sbin/adbd class core disabled # adbd on at boot in emulator on property:ro.kernel.qemu=1 start adbd # This property trigger has added to imitiate the previous behavior of "adb root". # The adb gadget driver used to reset the USB bus when the adbd daemon exited, # and the host side adb relied on this behavior to force it to reconnect with the # new adbd instance after init relaunches it. So now we force the USB bus to reset # here when adbd sets the service.adb.root property to 1. We also restart adbd here # rather than waiting for init to notice its death and restarting it so the timing # of USB resetting and adb restarting more closely matches the previous behavior. on property:service.adb.root=1 write /sys/class/android_usb/android0/enable 0 restart adbd write /sys/class/android_usb/android0/enable 1 service servicemanager /system/bin/servicemanager class core user system group system critical onrestart restart zygote onrestart restart media service vold /system/bin/vold class core socket vold stream 0660 root mount ioprio be 2 service netd /system/bin/netd class main socket netd stream 0660 root system socket dnsproxyd stream 0660 root inet service debuggerd /system/bin/debuggerd class main service ril-daemon /system/bin/rild class main socket rild stream 660 root radio socket rild-debug stream 660 radio system user root group radio cache inet misc audio sdcard_rw log service surfaceflinger /system/bin/surfaceflinger class main user system group graphics onrestart restart zygote service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server class main socket zygote stream 666 onrestart write /sys/android_power/request_state wake onrestart write /sys/power/state on onrestart restart media onrestart restart netd service drm /system/bin/drmserver class main user drm group system inet drmrpc service media /system/bin/mediaserver class main user media group audio camera inet net_bt net_bt_admin net_bw_acct drmrpc ioprio rt 4 service bootanim /system/bin/bootanimation class main user graphics group graphics disabled oneshot service dbus /system/bin/dbus-daemon --system --nofork class main socket dbus stream 660 bluetooth bluetooth user bluetooth group bluetooth net_bt_admin service bluetoothd /system/bin/bluetoothd -n class main socket bluetooth stream 660 bluetooth bluetooth socket dbus_bluetooth stream 660 bluetooth bluetooth # init.rc does not yet support applying capabilities, so run as root and # let bluetoothd drop uid to bluetooth with the right linux capabilities group bluetooth net_bt_admin misc disabled service installd /system/bin/installd class main socket installd stream 600 system system service flash_recovery /system/etc/install-recovery.sh class main oneshot service racoon /system/bin/racoon class main socket racoon stream 600 system system # IKE uses UDP port 500. Racoon will setuid to vpn after binding the port. group vpn net_admin inet disabled oneshot service mtpd /system/bin/mtpd class main socket mtpd stream 600 system system user vpn group vpn net_admin inet net_raw disabled oneshot service keystore /system/bin/keystore /data/misc/keystore class main user keystore group keystore socket keystore stream 666 service dumpstate /system/bin/dumpstate -s class main socket dumpstate stream 0660 shell log disabled oneshot This init.rc can be useful... with the Android SDK ICS 4.0 DUMP ROM! only boot.img or other boot image needs to make for ZTE to get it to work also it needs other init files too... Edited October 21, 2011 by Carlos Manuel Leemet
Guest slitz Posted October 21, 2011 Report Posted October 21, 2011 Some people says that ICS needs 1go of rom or something, that it is very heavy... I don't know if you agree? But if it is true, it would be a huge step back. The Nexus One has 512 MB of ROM.
Guest tilal6991 Posted October 21, 2011 Report Posted October 21, 2011 Guys - all the devices that have had a port are ARM7 devices - the same as the SDK image. The Blade is an ARM6 device. So it would essentially be impossible to port it.
Guest t0mm13b Posted October 21, 2011 Report Posted October 21, 2011 (edited) Guys - all the devices that have had a port are ARM7 devices - the same as the SDK image. The Blade is an ARM6 device. So it would essentially be impossible to port it. Hate to disappoint... thanks to a tweet by bl2nk (Thanks bl2nk for that! :) ) and a small conversation via twitter between me, bl2nk and HCDRJacob, but the bar has been raised, see here: In a nutshell: 6GB Download for entire ICS AOSP source25GB Scratch space to build16GB RAM 64bit obviously5+ hours to build like wtf... kinda makes you wonder if its actually worth the effort to build... BTW this was from twitter so the figures kind of don't add up, either a rumour or genuine but this was from Jean-Baptiste Queru, aka the AOSP guru..found here on googlecode newsgroup (Thanks hecatae) and NO! am not talking about customized ROM's with a minor bit here and there tweaked or even partial framework.jar submitted to UOT for fancy crapola - we're talking about a full blown stock AOSP ... For an example: On 32bit build -3.5GB download2GB RAM1.5GB scratch space32bit (don't laugh) it works - don't care what others think2.5 hours to build So something is amiss: Put this into perspective - all that source to spit out a compiled binary system.img weighing about 110Mb for Gingerbread...fine and dandy for those who have TPT'd 160Mb system partition for gen2... Now, with ICS, am guessing this will suck up more... so... its questionable on the final size of the compiled binary system.img which may take up a lot more than that partition that was allocated via TPT.... Can neither confirm nor deny if its true.... but .... as the saying goes "forewarned is fore-armed" Just my 2cents... Cheers, B) Edited October 21, 2011 by t0mm13b
Guest hedgepigdaniel Posted October 22, 2011 Report Posted October 22, 2011 You guys have 16gig ram? who doesn't? I have 128GB on my desktop - it makes facebook REALLY FAST.
Guest ColdEmbrace Posted October 22, 2011 Report Posted October 22, 2011 who doesn't? I have 128GB on my desktop - it makes facebook REALLY FAST. No amount of RAM will help facebook :P nice for the $12,500 investment in RAM though. Must have been a great working bonus :D
Guest hedgepigdaniel Posted October 22, 2011 Report Posted October 22, 2011 No amount of RAM will help facebook :P nice for the $12,500 investment in RAM though. Must have been a great working bonus :D haha, I was joking, I'm aware it won't make facebook any faster. Where are you buying your RAM from? If i need 128GB of DDR3 RAM I can get it for AUD$640.
Guest ColdEmbrace Posted October 22, 2011 Report Posted October 22, 2011 haha, I was joking, I'm aware it won't make facebook any faster. Where are you buying your RAM from? If i need 128GB of DDR3 RAM I can get it for AUD$640. haha i know i was joking with you too and i'd get it from a reputable manufacturer Like here
Guest hedgepigdaniel Posted October 22, 2011 Report Posted October 22, 2011 Actually to be fair, I'd need to find a motherboard with 32 DDR3 Slots for my deal :(
Guest iKrautDroid Posted October 22, 2011 Report Posted October 22, 2011 I have some connections and own a K computer supercomputer that does 8.1 petaflops... Jealous? ;)
Guest t0mm13b Posted October 22, 2011 Report Posted October 22, 2011 I have some connections and own a K computer supercomputer that does 8.1 petaflops... Jealous? ;) Ooohhh.... "The Gibson".... :lol: :P
Guest ThrashMan Posted October 22, 2011 Report Posted October 22, 2011 Stop talking blx.....I want ice cream....in a sandwich!! :)
Guest t0mm13b Posted October 22, 2011 Report Posted October 22, 2011 Stop talking blx.....I want ice cream....in a sandwich!! :) For what a euro, go into a shop and ask for a "Ice cream sandwich" ;) :P Seriously, if you want it, you will have to sacrifice your wallet for a go-faster PC that can handle what you WANT! :lol:
Guest ThrashMan Posted October 22, 2011 Report Posted October 22, 2011 lol is the problem that none of our devs has a PC up to spec to build ICS?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now