Looks like he posted a usable beta on twitter. Might want to check that out. Mind posting the latest package for us to test?JBirdVegas said:I'll look into merging props for d2 not dx
as far as not being able to repo I'm even having problems repoing CyanogenMod's source... this may not be my fault but I'll check again.
I see cvpcs has posted a new audio file and some more work on the hijack ... I'm downloading his latest edits and I'll build a copy we can all test... just hang on ...
Don't forget the media stuff. Camera's broken without it.JBirdVegas said:keyboard mapping may be another prop file ...
also I need to find droid2 values for most of it is still droidx: https://github.com/JBirdVegas/android_device_motorola_droid2/blob/gingerbread/droid2.mk
and more importantly this line (android_vendor_cyanogen/products/cyanogen_droid2.mk) needs to be updated
PRODUCT_BUILD_PROP_OVERRIDES := BUILD_ID=VZW BUILD_DISPLAY_ID=GRH78C PRODUCT_NAME=shadow_vzw TARGET_DEVICE=cdma_shadow BUILD_FINGERPRINT=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys PRODUCT_BRAND=verizon PRIVATE_BUILD_DESC="cdma_shadow-user 2.2.1 VZW 2.3.340 ota-rel-keys,release-keys" BUILD_NUMBER=2.3.340 BUILD_UTC_DATE=1289194863 TARGET_BUILD_TYPE=user BUILD_VERSION_TAGS=release-keys USER=w30471<br />
"Keyboard from Android 2.3" in the market works as well. Any other keyboard for that matter. Need to tweak the source to properly define the keyboard height.terryrook said:* Hey, by the way, The gingerbread keyboard for rubix focused 2.0.1 works on mine anyways, so much better than the 1mm keys.*
It's ueventd.mapphone_cdma.rc in /etc/droid2boot.zip/newbootRevNumbers said:good thinking, however, my understanding of /dev/ comes from linux, and i know in linux udevd creates all the device nodes under /dev at boot... so I'm not sure if there's anything we can push during the install, or even compilation of the rom... however there may be a config file we can modify that will create the node under the other name... or maybe even under both... i'll look into both and see what i can come up with
apparently there is no udev on android.... and /dev/ is just mounted tmpfs so I'm kind of at a loss for how to implement this... i'm not sure how to do what jbird was thinking, but that seems like the best way to do it, lol
No problem. I tore this thing apart for a few hours today. The .rc's look to be all sorts of different from stock moto ones.RevNumbers said:you sir, are a gentleman and a scholar... in other words... thanks!
how about ADB? That still shot?RevNumbers said:true, but for the binaries it needs the x bit... so run a chmod 755 on any of the binaries... none of the files seem to fix anything, but they haven't broken anything either, lol... well except for the libaudio stuff
<!-- This string array should be overridden by the device to present a list of network<br /> attributes. This is used by the connectivity manager to decide which networks can coexist<br /> based on the hardware --><br /> <!-- An Array of "[Connection name],[ConnectivityManager connection type],<br /> [associated radio-type],[priority] --><br /> <string-array translatable="false" name="networkAttributes"><br /> <item>"wifi,1,1,1"</item><br /> <item>"mobile,0,0,0"</item><br /> <item>"mobile_mms,2,0,2"</item><br /> <item>"mobile_dun,4,0,4"</item><br /> <item>"mobile_hipri,5,0,3"</item><br /> <item>"mobile_agps,7,0,2"</item><br /> <item>"mobile_fota,8,0,2"</item><br /> <item>"mobile_oem1,9,0,2"</item><br /> <item>"mobile_oem2,10,0,2"</item><br /> <item>"mobile_oem3,11,0,2"</item><br /> </string-array>
<!-- Determine whether calls to mute the microphone in PhoneUtils<br /> are routed through the android.media.AudioManager class (true) or through<br /> the com.android.internal.telephony.Phone interface (false). --><br /> <bool name="send_mic_mute_to_AudioManager">false</bool>
Sent from my DROID2 using TapatalkRevNumbers said:I need to get up with jbird and make sure we're on the same page with some of the stuff from sholes... but right now on my device the only issues I have are:
aGPS not working (regular gps is fine though)
camcorder audio issues (now that the mic is working right, the camcorder isn't again, lol)
light sensor doesn't work
Torch doesn't work quite right (i've got a workaround but i don't like it)
and the showstopper:
I think that's it actually... lol... wow we've come a long way!