AOSP Android 2.2 FroYo! 1/22/11 New Build Posted

Toggle sidebar Toggle sidebar
cordell said:
Awesome! I tried to use that kitchen to combine nROM and AOSP1 together but got looped. I have cooked about 4 diff roms and all get looped, lol. You got a good thing going here, thanks for the hard work!
Click to expand...

Your welcome! I enjoy doing this (surprisingly) because to me it's like a puzzle, and just getting one piece of it work right is so satisfying.
 
mrinehart93 said:
Aha! That's the guidance I've been looking for! Thanks gbhil! I'll take a look at it tomorrow (today was the last day of my four-day break :() So even though I'm using a ramdisk with the correct points in the stock Sprint rom, they aren't correct for AOSP?
Click to expand...

There's something early in the init, or a bad kernel making the AOSP boot.img not boot. Without a log, it's a guessing game.

If I'm reading correctly, your AOSP kernel boots when using the Sprint ramdisk, so that tells me it's the init.

The Sprint ramdisk boots up, but it tells the system to look for files that don't exist, have wrong permissions, are in the wrong place, or aren't the right version.

This is all my best guess, it could be something different. My first 1.6 build for the Hero wouldn't boot because the logo.rle image was corrupt, and took me several weeks to find it. Once you get it to boot far enough that you see the android logo and feel one short vibration, you're gold -- you can log via adb after that point
 
gbhil said:
There's something early in the init, or a bad kernel making the AOSP boot.img not boot. Without a log, it's a guessing game.

If I'm reading correctly, your AOSP kernel boots when using the Sprint ramdisk, so that tells me it's the init.

The Sprint ramdisk boots up, but it tells the system to look for files that don't exist, have wrong permissions, are in the wrong place, or aren't the right version.

This is all my best guess, it could be something different. My first 1.6 build for the Hero wouldn't boot because the logo.rle image was corrupt, and took me several weeks to find it. Once you get it to boot far enough that you see the android logo and feel one short vibration, you're gold -- you can log via adb after that point
Click to expand...

Well it currently boots into Android, but I don't even get the "good news" vibration lol. It must be the ramdisk then! If you want any kind of log that you could look at, I'd be glad to provide it.
 
I know nothing about getting this happy on a phone... but it sounds very intriguing... it obviously should be VERY doable...

Did you grab the source from LG as well so you should have the drivers for the kernel?
 
mrinehart93 said:
Thanks guys! Right now, I'm trying to figure out the driver situation... it doesn't really make sense. The kernel I've been using HAS the drivers included (I think), but AOSP doesn't seem to want to use them. I've even tried using a boot.img from some others ROM's, and I got the same result. Just curious... do you think it matters that I'm using a ramdisk other than the one that was compiled when I compiled the ROM itself? I've tried the AOSP-compiled ramdisk, but I couldn't even get the phone to boot with that.
Click to expand...

IF this is linux based, it might be worth diffing the configuration directory... (assuming it's that close to "standard" linux.)
 
scifan said:
IF this is linux based, it might be worth diffing the configuration directory... (assuming it's that close to "standard" linux.)
Click to expand...

Diffing it would help, but the thing is that the drivers don't work even with a kernel like Xionia, which should (in theory) work. So like gbhil said, it's probably a problem with the ramdisk, so I'll take a look at that when I get home.
 
What pain is involved to setup a cross-compiling environment in ubuntu?

Sent from my LS670 using Tapatalk
 
OMG! I think I got it figured out! Going off of what gbhil was saying, I found this in a file labeled init.thunderc.rc:

Code: 
## hopemini@lge.com, 20100416

on boot
	chown bluetooth bluetooth /sys/module/bluetooth_power/parameters/power
	chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
	chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
	chown bluetooth bluetooth /proc/bluetooth/sleep/proto
	chown system system /sys/module/sco/parameters/disable_esco
	chmod 0660 /sys/module/bluetooth_power/parameters/power
	chmod 0660 /sys/class/rfkill/rfkill0/state
	chmod 0660 /proc/bluetooth/sleep/proto
	chown bluetooth bluetooth /dev/ttyHS0
	chmod 0660 /dev/ttyHS0
	chmod 0666 /dev/msm_snd
## VIBRATOR
# LGE_CHANGE_E [kiwone.seo@lge.com] 2010-02-03, LG_FW_AUDIO_PWM_VIBRATOR 
	chmod 0666 /sys/class/timed_output/vibrator/amp
	chmod 0666 /sys/devices/platform/lg_diag_cmd/sms_status
	chmod 0666 /sys/devices/platform/lg_diag_cmd/get_sms
	chmod 0666 /sys/devices/platform/lg_diag_cmd/set_sms
	chmod 0666 /sys/devices/platform/lg_diag_cmd/rsp_sms_status
	chmod 0666 /sys/devices/platform/lg_diag_cmd/rsp_get_sms
	chmod 0666 /sys/devices/platform/lg_diag_cmd/rsp_set_sms
## SENSOR
	chown system system /dev/ami304
	chmod 0666 dev/ami304
	chown system system /dev/ami304daemon
	chmod 0666 dev/ami304daemon
	chown system system /dev/ami304hal
	chmod 0666 dev/ami304hal
	mkdir /data/amit 0770 ami304d ami304d
	chown system system /dev/KR3DH
	chmod 0666 /dev/KR3DH
	chown system system /dev/KR3DM
	chmod 0666 /dev/KR3DM	
## PROXIMITY SENSOR
	chmod 0666 /sys/bus/i2c/drivers/proximity_gp2ap/4-0044/enable
## USB
	chmod 0666 /sys/devices/platform/msm_hsusb_periphera/composition

	chown system graphics /dev/hw3d
	chmod 0660 /dev/hw3d
	chown root root /dev/kgsl
	chmod 0666 /dev/kgsl
	chmod 0666 /dev/pmem
	chown system graphics /dev/pmem_gpu
	chmod 0666 /dev/pmem_gpu
	chown system graphics /dev/pmem_gpu1
	chmod 0666 /dev/pmem_gpu1
	chown system audio /dev/msm_aac
	chmod 0660 /dev/msm_aac
	chown system audio /dev/msm_amrnb_in
	chmod 0660 /dev/msm_amrnb_in
	chown system audio /dev/msm_amrnb
	chmod 0660 /dev/msm_amrnb
	chown system audio /dev/msm_qcelp
	chmod 0660 /dev/msm_qcelp
	chown system audio /dev/msm_evrc
	chmod 0660 /dev/msm_evrc
	chown system audio /dev/msm_voicememo
	chmod 0660 /dev/msm_voicememo
	chown system graphics /dev/msm_rotator
	chmod 0660 /dev/msm_rotator
	chown system audio /dev/msm_preproc_ctl
	chmod 0660 /dev/msm_preproc_ctl
## AUDIO - SBA52101007
	chown system audio /dev/pmem_smipool
	chmod 0660 /dev/pmem_smipool
	chown system audio /dev/pmem_audio
	chmod 0660 /dev/pmem_audio
## QCT5320
	chown system audio /dev/msm_amr_in
	chmod 0660 /dev/msm_amr_in
	chown system audio /dev/msm_amrwb
	chmod 0660 /dev/msm_amrwb
	chown system audio /dev/msm_vidc_reg
	chmod 0660 /dev/msm_vidc_reg
	chown system audio /dev/msm_vidc_dec
	chmod 0660 /dev/msm_vidc_dec
	chown system audio /dev/msm_vidc_enc
	chmod 0660 /dev/msm_vidc_enc

	chmod 0666 /dev/graphics/fb0
	chmod 0666 /sys/class/leds/lcd-backlight/alc

	chown system system /dev/system_bus_freq
	chmod 0660 /dev/system_bus_freq
	chown system system /dev/cpu_dma_latency
	chmod 0660 /dev/cpu_dma_latency

	mkdir /data/radio 0770 radio radio
	chown system radio /dev/rtc1
	chmod 0660 radio /dev/rtc1

# LGE_CHANGE_S, [jisung.yang@lge.com] 2010-04-24, <make wifi directory>  
# WIFI
	mkdir /data/misc/wifi/sockets 0770 wifi wifi
    setprop wifi.supplicant_scan_interval 20
    setprop wifi.interface wlan0
	mkdir /data/disk 0777 system system

#DHCP
    mkdir /data/misc/dhcp 0777 system system
# LGE_CHANGE_E, [jisung.yang@lge.com] 2010-04-24, <make wifi directory> 

## ERS
	mkdir /data/data/com.lge.ers
	mkdir /data/data/com.lge.ers/android
	mkdir /data/data/com.lge.ers/kernel
	mkdir /data/data/com.lge.ers/arm9
	chmod 0777 /data/data/com.lge.ers/android
	chmod 0777 /data/data/com.lge.ers/kernel
	chmod 0777 /data/data/com.lge.ers/arm9

# Collect ramconsole data
	copy /proc/last_kmsg /data/dontpanic/last_kmsg
	chown root log /data/dontpanic/last_kmsg
	chmod 0640 /data/dontpanic/last_kmsg

on property:init.svc.hcid=running
	write /sys/devices/virtual/bluetooth/hci0/idle_timeout 7000
# LGE_CHANGE_S [sm.shim@lge.com] 2010-08-02, FPRI/DB check
# DBCHECK
        mkdir /data/dbcheck 0777 system system
# LGE_CHANGE_E [sm.shim@lge.com] 2010-08-02, FPRI/DB check 

# LG_FW_AUDIO_BROADCOM_BT , not used below lines
#service hci_qcomm_init /system/bin/log -t qcom-bluetooth -p i "hci_qcomm_init service requested"
#    user bluetooth
#    group bluetooth net_bt_admin
#    disabled
#    oneshot

# +++ BRCM +++
# Make sure we startup btld before bluetoothd
# Set target address to emulator host loopback IF
# Limit baudrate to 460800 to ensure reliable uart operation
service btld /system/bin/logwrapper /system/bin/btld -pf /system/bin/BCM4325D1_004.002.004.0218.0248.hcd -hb 4000000 -lpm 1
    user root			
    group bluetooth net_bt_admin			
    disabled			
    oneshot			
				
service bluetoothd /system/bin/bluetoothd -n			
    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 hciattach /system/bin/sh /system/etc/init.qcom.bt.sh
#    user bluetooth
#    group qcom_oncrpc bluetooth net_bt_admin
#    disabled
#    oneshot

#service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
#    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 hcid drop uid to bluetooth with the right linux capabilities
#    group bluetooth net_bt_admin misc
#    disabled

#service hfag /system/bin/sdptool add --channel=10 HFAG
#    user bluetooth
#    group bluetooth net_bt_admin
#    disabled
#    oneshot

#service hsag /system/bin/sdptool add --channel=11 HSAG
#    user bluetooth
#    group bluetooth net_bt_admin
#    disabled
#    oneshot
# --- BRCM ---

service cnd /system/bin/cnd
    socket cnd stream 660 root radio
    socket cne stream 660 root radio

service qmuxd /system/bin/qmuxd 

service ami304d /system/bin/ami304d

## USB
# LGE_CHANGE [dojip.kim@lge.com] 2010-09-05,
# postpone port-bridge daemon launch due to lock-up during boot-up time (from VS660)
#service port-bridge /system/bin/port-bridge /dev/smd0 /dev/ttyGS0 
service port-bridge /system/bin/port-bridge /dev/smd0 /dev/ttyHSUSB0
    disabled

on property:init.svc.bootanim=stopped
    start port-bridge

# LGE_CHANGE_S, [jisung.yang@lge.com], 2010-04-24,<register WLAN services>
service wpa_supplicant /system/bin/wpa_supplicant -Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf #-dd
	socket wpa_wlan0 dgram 660 wifi wifi
	group system wifi inet
	disabled
	oneshot
#	console

#service dhcpcd /system/bin/dhcpcd -B wlan0
service dhcpcd /system/bin/dhcpcd -BKLA wlan0 # disable ARP operation
	disabled
	oneshot

on property:init.svc.wpa_supplicant=stopped
stop dhcpcd
# LGE_CHANGE_E, [jisung.yang@lge.com], 2010-04-24,<register WLAN services>

#service dhcp-service /system/bin/netcfg eth0 dhcp
#    oneshot

service qcom-post-boot /system/bin/sh /init.qcom.post_boot.sh
	user root
	disabled
	oneshot

on property:dev.bootcomplete=1
    start qcom-post-boot

#on property:dev.bootcomplete=1
#    stop dhcp-service
#    start dhcp-service


service rmt_storage /system/bin/rmt_storage /dev/block/mmcblk0p10 /dev/block/mmcblk0p11
    user root
    disabled

service netmgrd /system/bin/netmgrd -E
    disabled

on property:ro.use_data_netmgrd=true
    start netmgrd

service wiperiface /system/bin/wiperiface
    user location
    group qcom_oncrpc
    oneshot

# LGE_CHANGE [dojip.kim@lge.com] 2010-08-06, 
# CKPD-daemon is required to support remote AT command feature. (eg. CKPD, CTSA)
# FIXME: really need???
#service ckpd /system/bin/CKPD-daemon
#    onrestart /system/bin/log -t RIL-CKPD -p w "CKPD daemon restarted"

# LGE_CHANGE [dojip.kim@lge.com] 2010-09-02, blocked in production build
# bugreport is triggered by the KEY_VOLUME_DOWN and KEY_MENU keycodes
#service bugreport /system/bin/logwrapper /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
#	disabled
#	oneshot
#	keycodes 114 139

# LGE_CHANGE_S [jeongku.choi@lge.com] 2010-07-09, [CIQ] adapting patch files
service iqmsd /system/bin/iqmsd
    disabled

on property:service.iq.active=1
    start iqmsd

on property:service.iq.active=0
    stop iqmsd

# LGE_CHANGE_E [jeongku.choi@lge.com] 2010-07-09, [CIQ]

# LGE_CHANGE [dojip.kim@lge.com] 2010-06-14, from VS660
# LGE_CHANGE [dojip.kim@lge.com] 2010-09-29, no auto udpate in mass
# mcs6000 TOUCH F/W AUTO upgrade run
# LGE_CHANGE [younchan.kim,2010-06-13] 
#service tsdown /system/bin/tsdown
#	oneshot

# LGE_CHANGE [james.jang@lge.com, 2010-08-06] 
service soft_resetd /sbin/soft_resetd
	user root

Does that not look like driver code to you? If my guess is correct, then I can insert that into our init.rc (for the AOSP ramdisk), and it should load those drivers! Am I right??
 
The first part (~1/3) is changing permissions and ownership.. Saw some parts that looked to be creating directories. Saw some stuff that appeared to be setting defaults... And some stuff launching services. I would expect drivers to be in a modules file...

Is there a lsmod command? I wonder if they use modules like under "standard" linux...

I know in standard you need to specify modules that are pre-loaded...

Sent from my LS670 using Tapatalk
 
When I do lsmod, I don't get any output :(

Here's something interesting:

When I paste that code above into the AOSP ramdisk.img init.rc (below the "on boot"), my computer can recognize my phone as "GOOGLE Mass storage". With the Sprint ramdisk.img, my computer won't recognize my phone at all.
 
mrinehart93 said:
When I do lsmod, I don't get any output :(

Here's something interesting:

When I paste that code above into the AOSP ramdisk.img init.rc (below the "on boot"), my computer can recognize my phone as "GOOGLE Mass storage". With the Sprint ramdisk.img, my computer won't recognize my phone at all.
Click to expand...

Its a big step :)
 
smccloud said:
Its a big step :)
Click to expand...

It's also a step back, since the phone will not successfully boot haha. I was just talking with Decad3nce, and he said it is probably incorrect permissions being set on the drivers, so they're not being loaded.
 
this is awesome. Your "that" close to getting this all rocking. Deca is a badass. If you have his help, it will be sooner then later.
 
rodcpierce said:
this is awesome. Your "that" close to getting this all rocking. Deca is a badass. If you have his help, it will be sooner then later.
Click to expand...

Yeah, Decad3nce is pretty awesome. He thinks that the problem is permission errors... so, does anyone want to look through some files and help me see what could be wrong?

Btw gbhil, Decad3nce says I'm in good hands with you helping me lol.

Oh, btw I got busybox installed in the ROM while I was trying to figure some stuff out.
 
mrinehart93 said:
Yeah, Decad3nce is pretty awesome. He thinks that the problem is permission errors... so, does anyone want to look through some files and help me see what could be wrong?

Btw gbhil, Decad3nce says I'm in good hands with you helping me lol.

Oh, btw I got busybox installed in the ROM while I was trying to figure some stuff out.
Click to expand...

woohoo, keep it up.
 
Coming from and HTC Hero CDMA and from over at that other sight (cough lol) I can honestly say that Deacadence is very helpful. His Brainfuct Kernel was simply amazing on my Hero..... the stable ones not the uncapped. My poor little here couldn't go past 768Mghz :*(
 
Good news! I think I ALMOST have AOSP working! I got a TON of drivers to load now (according to dmesg), but the phone keeps bootlooping. I think once I can get it past the bootloop, we should have a fully working AOSP 2.2 :)
 
  • Like
Reactions: debh945
You must log in or register to reply here.

Similar threads

T
Android 4.4.4 AOSP Based d2lte Nightlies
Replies
83
Views
56K
Samsung Galaxy S3 Rooting, ROMs, & Hacks
The Keeper
T
S
[ROM][TH3ORYROM]A05PTH3ORY V1.4X [AOSP/CM7]DKSM Kernel 8/14/11
Replies
68
Views
11K
Thunderbolt Rooting, ROMs, and Hacks
tfrank10
T
C
[KERNEL] [SENSE & AOSP] 11-08-2011 - AnthraX series of kernels -
Replies
5
Views
8K
HTC EVO 3D Rooting, ROMs, and Hacks
_KDunK_
K
Jerry Hildenbrand
AOSP FROYO ROM -- all the goodies out of the box
Replies
0
Views
3K
Google Nexus One Rooting, ROMs, and Hacks
Jerry Hildenbrand
Jerry Hildenbrand
J
[REF] Infuse 4G Super Everything Thread {2nd Edition} 1 Aug
Replies
2
Views
20K
Infuse Rooting, ROM's, and Hack's
joe1987
J

Latest posts

Trending Posts

Members online

Total: 1,497 (members: 6, guests: 1,491)

Forum statistics

Threads
956,900
Messages
6,970,520
Members
3,163,644
Latest member
roneginsberg

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom