-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [DEV] Continuing Triumph ICS Development
- Thread starter mantera
- Start date
-
- Tags
- motorola triumph
BadAngel
Member
awesome dude!... so easy too...
I'm currently porting over all of the new adreno drivers to our old kernel... been working on it for hours lol...
Haha, having difficulty testing because the keyboard acts really wonky. When I try to switch to #s/symbols it switches as long as I hold down the ?123 key, but switches back when I let go (and I can't do a second touch with it held down). Easy, I thought, just long-press the top row to get numbers... Well, long-pressing may work to keep the symbol page up, but not at all with the other keys
... I can text someone in my history of calls though, so I was able to try that, and receiving SMS works. Just thought the keyboard behavior was interesting. Anyone know why this might be happening?I don't have access to another MMS capable phone right now to test that.
Haha, having difficulty testing because the keyboard acts really wonky. When I try to switch to #s/symbols it switches as long as I hold down the ?123 key, but switches back when I let go (and I can't do a second touch with it held down). Easy, I thought, just long-press the top row to get numbers... Well, long-pressing may work to keep the symbol page up, but not at all with the other keys
I don't have access to another MMS capable phone right now to test that.
we probably want to take a look at the keyboard layout files.
I also tried changing the build.prop file with the line that you posted in a build I had on my phone from yesterday and I can confirm that we do have radio now. I'll make the update tonight and push it up for the rest of us.
On a side note, we gotta get a more recent GAPPS version. The one from the CM site is for cm7 and it just FC's when I tried to go through the setup wizard.
I'd like to look at audio next. Any suggestions or previous insights gleaned welcome! Isaac mentioned something in the previous thread about the audio wrapper changing and breaking legacy libaudio? Anyone know if other FIH-fb0 variants made changes to successfully bring up audio?
marc12868
Android Expert
Haha, having difficulty testing because the keyboard acts really wonky. When I try to switch to #s/symbols it switches as long as I hold down the ?123 key, but switches back when I let go (and I can't do a second touch with it held down). Easy, I thought, just long-press the top row to get numbers... Well, long-pressing may work to keep the symbol page up, but not at all with the other keys
I don't have access to another MMS capable phone right now to test that.
You do know that you can text yourself? If you have service you'll receive it and if not you won't so you can send a pic to your number and see if it will send and receive.
Whyzor
Android Expert
link
Would recommend adding to OP when you post download link for rom
Related to the keyboard, I can upload framework-res from the hauwei ics ROM, if you like
How is that gapps different than these ones:
gapps-ics-20111122-full.zip
gapps-ics-20111125-2.zipJust wondering if it's more recent or not.As for using Huawei's framework-res.apk, even if it works, it would be broken as soon as CM9 makes further updates. We need source code updates to build proper framework-res for the MT.
rukin5197
Android Enthusiast
How is that gapps different than these ones:
gapps-ics-20111122-full.zip
As for using Huawei's framework-res.apk, even if it works, it would be broken as soon as CM9 makes further updates. We need source code updates to build proper framework-res for the MT.
Well he said that the gapps was for cm7, and I new that as made specifically for ics so... oh, and from what I know, its very recent. I can't test it though because I don't own the MT. So if someone could leave feedback?
Thanks, didn't know that - just tried on stock and yes, Iget my own MMS. ICS with the working RIL is a no go, however - tried also over lunch with sending/receiving MMS with my wife's phone. It can't send (service unavailable), and it receives two messages full of garbage data rather than the MMS.
How is that gapps different than these ones:
gapps-ics-20111122-full.zip
As for using Huawei's framework-res.apk, even if it works, it would be broken as soon as CM9 makes further updates. We need source code updates to build proper framework-res for the MT.
The one that gannon linked had dates for the apps from around 1/14/12 and it looks like they were pulled from the XOOM ICS update.
So they look like they're more recent than the dates on the 2 in your links.
It was weird though. When I flashed the Xoom gapps, it tried to run me through activating my phone again.
Build failed from last night
Do you mean that you got an error during the build?
Or do you mean that the build failed to boot?
Whyzor
Android Expert
Here's a "diff -u" of mantera's BoardConfig.mk with edowar's FB0. The + lines are for MT, - are for FB0. The FB0 has more hardware working, so I would aim towards that, unless someone has tried a few of these values, then we should keep track so others don't have to waste time retrying them. For audio, try changing the audio lines to false.
+TARGET_PROVIDES_LIBAUDIO := true
BOARD_USES_GENERIC_AUDIO := false
+BOARD_USES_AUDIO_LEGACY := true
+TARGET_PROVIDES_LIBAUDIO := true
BOARD_USES_GENERIC_AUDIO := false
+BOARD_USES_AUDIO_LEGACY := true
Code:
-# inherit from the proprietary version
--include vendor/fih/fb0/BoardConfigVendor.mk
+# inherit from the proprietary version
+-include vendor/motorola/triumph/BoardConfigVendor.mk
-TARGET_SPECIFIC_HEADER_PATH := device/fih/fb0/include
+TARGET_SPECIFIC_HEADER_PATH := device/motorola/triumph/include
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := msm7x30
@@ -24,46 +38,47 @@
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
-TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
-TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp
-
TARGET_USES_2G_VM_SPLIT := true
+#TARGET_USES_OLD_LIBSENSORS_HAL := true
# Set insecure for root access
ADDITIONAL_DEFAULT_PROPERTIES += ro.secure=0
# Releasetools
TARGET_PROVIDES_RELEASETOOLS := true
-TARGET_RELEASETOOL_IMG_FROM_TARGET_SCRIPT := ./device/fih/fb0/releasetools/triu
mph_img_from_target_files
-TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT := ./device/fih/fb0/releasetools/triu
mph_ota_from_target_files
+TARGET_RELEASETOOL_IMG_FROM_TARGET_SCRIPT := ./device/motorola/triumph/releaset
ools/triumph_img_from_target_files
+TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT := ./device/motorola/triumph/releaset
ools/triumph_ota_from_target_files
BOARD_USES_QCOM_HARDWARE := true
+COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
BOARD_USES_QCOM_LIBS := true
BOARD_USES_QCOM_LIBRPC := true
BOARD_USE_QCOM_PMEM := true
-BOARD_USES_QCOM_GPS := true
# Bluetooth
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
# Audio
+TARGET_PROVIDES_LIBAUDIO := true
BOARD_USES_GENERIC_AUDIO := false
+BOARD_USES_AUDIO_LEGACY := true
# Graphics
-USE_OPENGL_RENDERER := true
-TARGET_USES_C2D_COMPOSITION := false
-TARGET_HAVE_BYPASS := false
+BOARD_USES_ADRENO_200 := true
+BOARD_USES_GENLOCK := true
+BOARD_EGL_CFG := device/motorola/triumph/egl.cfg
+BOARD_OVERLAY_MINIFICATION_LIMIT := 2
+#USE_OPENGL_RENDERER := true
+#TARGET_USES_C2D_COMPOSITION := true
+TARGET_HAVE_BYPASS := true
+BOARD_NO_RGBX_8888 := true
TARGET_USES_OVERLAY := true
-TARGET_QCOM_HDMI_OUT := true
-TARGET_GRALLOC_USES_ASHMEM := false
-TARGET_USES_GENLOCK := true
-TARGET_FORCE_CPU_UPLOAD := true
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60
-
-BOARD_EGL_CFG := device/fih/fb0/egl.cfg
-
-BOARD_OVERLAY_MINIFICATION_LIMIT := 2
+#TARGET_GRALLOC_USES_ASHMEM := true
+TARGET_FORCE_CPU_UPLOAD := true
+TARGET_QCOM_HDMI_OUT := true
+BOARD_USE_FRAMEBUFFER_ALPHA_CHANNEL := true
# Wifi
BOARD_WPA_SUPPLICANT_DRIVER := WEXT
@@ -75,29 +90,27 @@
WIFI_SDIO_IF_DRIVER_MODULE_NAME := "librasdioif"
BOARD_WEXT_NO_COMBO_SCAN := true
-
-# Older Touchscreen Support
-BOARD_USE_LEGACY_TOUCHSCREEN := true
-
# Camera
-#TARGET_LEGACY_CAMERA := true
+BOARD_CAMERA_USE_GETBUFFERINFO := true
+BOARD_USE_CAF_LIBCAMERA := true
# GPS Defines
-BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := fb0
-BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50001
-BOARD_VENDOR_QCOM_GPS_NEEDS_LNA := true
-BOARD_VENDOR_QCOM_GPS_HAS_BROKEN_XTRA := true
+#BOARD_USES_QCOM_GPS := true
+#BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := triumph
+#BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50001
+#BOARD_VENDOR_QCOM_GPS_NEEDS_LNA := true
+#BOARD_VENDOR_QCOM_GPS_HAS_BROKEN_XTRA := true
# USB
-BOARD_USE_USB_MASS_STORAGE_SWITCH := true
-TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/usb_mass_storage/lun0/
file
+TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/platform/usb_mass_storage/lun0
/file"
# Recovery
-TARGET_PREBUILT_RECOVERY_KERNEL := device/fih/fb0/recovery_kernel
+TARGET_PREBUILT_RECOVERY_KERNEL := device/motorola/triumph/recovery_kernel
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_USES_MMCUTILS := true
-#BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/fih/fb0/recovery/recovery_ui.
c
-BOARD_CUSTOM_GRAPHICS := ../../../device/fih/fb0/recovery/minui/graphics.c
+BOARD_UMS_LUNFILE := "/sys/devices/platform/usb_mass_storage/lun0/file"
+BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/motorola/triumph/recovery/reco
very_ui.c
+BOARD_CUSTOM_GRAPHICS := ../../../device/motorola/triumph/recovery/minui/graphi
cs.c
# Filesystem
BOARD_SYSTEM_DEVICE := /dev/block/mmcblk0p7
@@ -112,7 +125,7 @@
BOARD_HAS_NO_MISC_PARTITION := true
TARGET_USERIMAGES_USE_EXT4 := true
-BOARD_KERNEL_CMDLINE := console=ttyMSM1 androidboot.hardware=qcom
+BOARD_KERNEL_CMDLINE := console=ttyMSM1 androidboot.hardware=triumph
BOARD_KERNEL_BASE := 0x00200000
BOARD_KERNEL_PAGESIZE := 4096
@@ -122,7 +135,6 @@
BOARD_FLASH_BLOCK_SIZE := 262144
TARGET_OTA_ASSERT_DEVICE := triumph,WX435,fb0
-TARGET_BOOTLOADER_BOARD_NAME := fb0
-
-TARGET_PREBUILT_KERNEL := device/fih/fb0/kernel
+TARGET_BOOTLOADER_BOARD_NAME := triumph
+TARGET_PREBUILT_KERNEL := device/motorola/triumph/kernelWhyzor
Android Expert
I built after synching last night around midnight central & it succeeded, also resynced this morning & rebuilt and it was fine. Haven't tried flashing it though.
PerkinsII
Android Enthusiast
Error during build, though that was when your github tree was 245(when it says fetching projects) now it is back to 244, will try to rebuild tonight
PerkinsII
Android Enthusiast
I built after syncing at 9pm cst
Raptor5150
Android Enthusiast
So is wifi working on your latest build Whyzor.. (or whoever lol) im considering asking for the zip so i can flash it.. cause since bluetooth is working.. i could just load up the onlive Apk and start using my 4.0 only controller (bastards..)
but im guessing since no one has hardware accel on.. that means onlive wont work correct even tho it streams?? oh wait but no sound.. meh i can atleased give my controller a try hehe
but im guessing since no one has hardware accel on.. that means onlive wont work correct even tho it streams?? oh wait but no sound.. meh i can atleased give my controller a try
heheRaptor5150
Android Enthusiast
I think from the 2 minutes it took you to post that.. you could have said.. "Why yes Raptor Wifi is indeed working but without HW Accel nothing graphical will run.. and sadly i cannot give you a flashable zip just yet.." Or somhing along those lines..
Dunno why all this stuff is like a big secret that no one can just share for one question id understand if everyone was poking in here asking but I only wanted to ask one thing and i didnt want to PM you since others could have responded quickly to the same question..
Whyzor
Android Expert
Because if I answer, someone else will ask something else, and then someone else will ask something else. Last few threads about developing for ICS have been like that. I may have time sometimes, but other devs may not want this thread derailed.
This isn't to keep it a big secret. It's to prevent people who don't know what they're doing from asking too many repeated questions that can be answered with a simple search. We're not trying to keep it a secret, there's just no point to flashing the ROM at this point if you don't know how to get it to run. I'm not targetting you, just as a general post so others see this (they probably won't once this post is past the most recent page).
BTW, nobody said Wifi works.
idbl_fanatic
Android Enthusiast
sharpe351
Well-Known Member
It isn't a big secret at all. Just that the devs DO NOT want to put out a partially working product. This takes considerable time and asking for an unfinished ROM is actually kind of rude. If it was in some kind of proper working order I see no problem in using it, but this is not. I have had many issues trying to build this ROM myself, and I cannot do it with my equipment. Therefore, I will wait patiently until Whyzor, mantera and the others working on this get a stable release build.
KinichAjaw
Member
Why? It's no secret-there are at least 2 threads about ICS on the forum. The reason you were given such a post, is yours effectively sounds like "Lolz guess there's not much except whatever you guys are working on? Where's my ROM at?" Which, as was said, sounds really rude to someone working hard to get something we should rightfully have without having to sort through the code ourselves (not that I mind, of course...)
....OK since there are like 3 other posts and I don't want this to go horribly OT I'll stop there.