Leaderboard

Hi, I have had messaging issues on the Droid 2 Global. The device would prepend 011 to the mdn and then send it to the network. It took me a while to fix it and below is what needs to be changed. Go to /system folder on your android using root explorer or any other explorer. Mount the directory in the R/W mode. Tap the build.prop file and check the properties of the file. Note down the permissions. Open the build.prop file using any free android editor or use your PC to make changes to the file. Set the below parameter in the build.prop file ro.telephony.gsm-routes-us-smsc = 0 radio.cdma.nbpcdallowed=1 ro.cdma.home.operator.isnan=0 ro.cdma.nbpcd=1 Once the changes have been made, please ensure the permission of the file is the same as it was before. Remount the folder in the R/O mode. Below is how my build.prop looks like. # begin build properties # autogenerated by buildinfo.sh ro.build.id=S273 ro.build.display.id=Fission_2.4.3 ro.build.version.incremental=2.4.29 ro.build.version.sdk=8 ro.build.version.codename=REL ro.build.version.release=2.2 ro.build.date=Thu Oct 21 23:44:06 CDT 2010 ro.build.date.utc=1287722646 ro.build.type=user ro.build.user=xrpk47 ro.build.host=il93lnxdroid25 ro.build.tags=ota-rel-keys,release-keys ro.product.model=DROID2 GLOBAL ro.product.model.internal=A956 ro.product.brand=verizon ro.product.name=droid2we_vzw ro.product.device=cdma_droid2we ro.product.board=droid2we ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=motorola ro.product.locale.language=en ro.product.locale.region=IN ro.wifi.channels= ro.board.platform=omap3 # ro.build.product is obsolete; use ro.product.device ro.build.product=droid2we_vzw # Do not try to parse ro.build.description or .fingerprint ro.build.description=cdma_droid2we-user 2.2 S273 2.4.29 ota-rel-keys,release-keys ro.build.fingerprint=verizon/droid2we_vzw/cdma_droid2we/droid2we:2.2/S273/2.4.29:user/ota-rel-keys,release-keys # end build properties # # system.prop for CDMA Droidwe # # rild.libpath=/system/lib/libril-moto-umts-1.so rild.libpath=/system/lib/libmoto_ril.so rild.libargs=-d /dev/ttyS0 ro.sf.lcd_density=240 ro.default_usb_mode=2 persist.service.adb.enable=0 ro.mot.ril.danlist=611,*611,#611 persist.ril.ecclist=911,*911,#911 persist.ril.modem.mode =1 # This defines the max event window manager can # handle in 1 s. We may adjust this # for performance # reason later windowsmgr.max_events_per_sec=70 # USB modes allowed for UI and switching ro.ngp_available=1 ro.modem_available=0 # Default network type. # 4 => CDMA / EVDO. ro.telephony.default_network=4 ro.com.google.clientid=android-motorola ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html ro.cdma.home.operator.numeric=310004 ro.cdma.home.operator.alpha=Verizon ro.config.vc_call_vol_steps=7 # wlan interface wifi.interface = tiwlan0 # Time between scans in seconds. Keep it high to minimize battery drain. # This only affects the case in which there are remembered access points, # but none are in range. wifi.supplicant_scan_interval = 1800 # Indicate carrier OTA SP number schema # refer to frameworks/base/telephony/java/com/android/ # internal/telephony/cdma/CDMAPhone.java for the schema: ro.cdma.otaspnumschema=SELC,1,80,99 # The OpenGL ES API level that is natively supported by this device. # This is a 16.16 fixed point number ro.opengles.version = 131072 # This is a high density device with more memory, so larger vm heaps for it. dalvik.vm.heapsize=32m # The URL for safety information ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal # our HTML browser (not WAP browser ) does not need to specify UAProf URL ro.mot.hw.uaprof= # Enable HAC to also display Call Setting Menu Option. ro.mot.hw.HAC=1 # Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android # Property to set enabling state of the location privacy setting feature. # Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067 #ro.mot.settings.locprivacy=1 # ERI feature # 0 OFF # 1 ON ro.mot.eri=1 # Motorol,twv437,27/08/2010,IKSTABLETWO-4889 # Display media sync status # 0 OFF # 1 ON ro.mediasync.enable_sync_ui=1 # Motorol,a6889c,02/Feb/2010,IKSHADOW-619 # Proximity Sensor feature # 0 disable # 1 enable persist.mot.proximity.touch=1 # End IKSHADOW-619 # BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841 # VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING # 0 disable # 1 enable ro.cdma.nbpcd=1 # END IKSHADOW-702 # BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone # Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone # persist.mot.powerup.tone=/system/media/bootup.ogg # END IKSHADOW-1784 # Motorol,ychen2,14-Mar-2010,IKSHADOW-1951 # 17518 A2DP passthru feature # 0 disable # 1 enable persist.mot.a2dp.direct = 1 persist.mot.usb.mediasync = 0 # persist.usb.android_config = 1 # System property for SMC ro.service.start.smc=1 ro.HorizontalBUA=true #Proximity sensor debounce time mot.proximity.delay=450 # disable touch below 60 pixels mot.proximity.distance=60 # BEGIN Motorola, qpmc46, 05-Jul-2010, IKMAIN-311 persist.ril.mux.noofchannels = 8 # END Motorola, qpmc46, 05-Jul-2010, IKMAIN-311 #BEGIN Motorola, nfjb73, 21-jun-2010, # this is for feature 34386, other features for vzw global phone # could use this property too. IKMAIN-732 #1 this is verizon wireless globle phone #0 this is not verizon wireless globle phone ro.mot.phonemode.vzwglobalphone=1 # END Motorola, nfjb73, 21-jun-2010, IKMAIN-732 # BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624 # this is for feature 33860, when phone is activated, the cdma mdn is written. persist.radio.vzw.cdma.mdn= # END Motorola, nfjb73 # BEGIN Motorola, qmfd78, 14-Jul-2010, IKMAIN-884 # GSM SMS traffic needs to be routed/sent through North America SMSC. # This is part of the VZW World-phone Feature. SMS are always sent to a US SMSC and then injected # into that network. This allows for billing and give the user the impression that the device is # still in the US. ro.telephony.gsm-routes-us-smsc = 0 # END Motorola, qmfd78, 14-Jul-2010, IKMAIN-884 # BEGIN Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423 # For north american cdma operators, this flag should be 1. # It enables number mangling when nbpcd (plus code dialing) is not supported. # This is part of the VZW World-phone Feature. ro.cdma.home.operator.isnan=0 # END Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423 # BEGIN Moto,IKDROIDPRO-430, a17673 # Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA ro.mot.FTR.33857=true # END IKDROIDPRO-430 # BEGIN Moto, IKSTABLETWO-689, nfjb73, for 34387,33857 # when phone in Global mode, FW need to know the last phone mode beore power off # when phone power up, it would use the right mode to avoid switch persist.radio.ap.phonetype=2 # END IKSTABLETWO-689 # BEGIN Moto, IKDROIDPRO-381, xrn374, for 34174 # Feature 34174 support for the Enterprise Device Management (EDM) ro.mot.dpmext = true # END IKDROIDPRO-381 # BEGIN Moto, IKSTABLETWO-1284, nfjb73 # without this property, the lock screen would take global phone as UMTS # block user to operate before setup keyguard.no_require_sim = true # End Moto # BEGIN Motorola, a22600, 13-Aug-2010, IKSTABLETWO-2244, FID 31841/33858 # Property to determine if current network supports NBPCD # Will be dynamically updated by CdmaPCDHandler # 0 NBPCD is not allowed # 1 NBPCD is allowed radio.cdma.nbpcdallowed=1 # END IKSTABLETWO-2244 # BEGIN Motorola, vfhk68, 18-Aug-2010, IKSTABLETWO-3894,33531 flex on for D2WE # true feature enabled # false feature disabled ro.mot.fid.33531.keylock_ecm=true # END IKSTABLETWO-3894 # BEGIN Motorola, in1961c, 8-Sept-2010, IKSTABLETWO-7241, Master clear is taking more then 30 minutes ro.mot.master_clear.shredsd = false # END IKSTABLETWO-7241 # BEGIN Motorola, e50202, 3-Sept-2010, IKSTABLETWO-7041, default Mobile Hotspot is on ro.mot.mynet=true # END IKSTABLETWO-7041 # BEGIN Motorola, hpqg67, 19-Sept-2010, IKSTABLETWO-9197 # write cdma MIN to property for VVM use in GSM/UMTS mode persist.radio.cdma.min = 0 # END IKSTABLETWO-9197 # BEGIN Motorola, qvg387, 25-Sep-2010, IKSTABLETWOV-587 # true Horizontal VVM is preloaded, not allow to install standalone version of VVM from Android Market # false Horizontal VVM is not preloaded ro.HorizontalVVM=false # END IKSTABLETWOV-587 # # ADDITIONAL_BUILD_PROPERTIES # ro.kernel.android.ril=yes persist.ril.mux.noofchannels=8 persist.ril.mux.ttydevice=/dev/ttyS0 persist.ril.modem.ttydevice=/dev/ttyUSB4 persist.ril.features=0x0E persist.ril.mux.retries=500 persist.ril.mux.sleep=2 ro.ftmipcd.ipcdevice=/dev/ttyUSB0 ro.config.ringtone=Droid.ogg ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=Alarm_Classic.ogg media.stagefright.enable-player=false media.stagefright.enable-meta=false media.stagefright.enable-scan=false media.stagefright.enable-http=false ro.default_usb_mode=0 ro.media.enc.aud.fileformat=qcp ro.media.enc.aud.codec=qcelp ro.media.enc.aud.bps=13300 ro.media.enc.aud.ch=1 ro.media.enc.aud.hz=8000 ro.com.google.gmsversion=2.2_r6 ro.telephony.call_ring.multiple=false ro.telephony.call_ring.delay=1000 ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=A855 ro.setupwizard.enable_bypass=1 ro.com.google.clientid=android-motorola ro.com.google.clientidbase=android-verizon ro.com.google.clientidbase.am=android-verizon ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html ro.cdma.home.operator.numeric=310004 ro.cdma.home.operator.alpha=Verizon ro.config.vc_call_vol_steps=7 ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83 ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000 ro.media.capture.maxres=5m ro.media.capture.flash=led ro.media.capture.flashMinV=3630000 ro.media.capture.classification=classF ro.media.capture.fast.fps=4 ro.media.capture.slow.fps=60 ro.media.capture.useDFR=1 ro.mot.setuptype=2 dalvik.vm.dexopt-flags=m=y net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt ro.com.google.clientid=android-motorola ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf ro.build.version.full=Fission_2.4.3

Hi all, bought three superb hardware during last few days:- 1). HP Touchpad 16GB Purchased from USA for Rs. 10000/- (just double the price at which HP sold it) Saved on Duties and Shipping as I got it through my Cousin coming from US. Why - Becoz I can't get any better tab in this price range, at least for my home and personal use (truly speaking for my wife & 4 year old son). Though, out of box, worth of this tab is not more than $99 (at which HP sold it out), its very sluggish and slow. But once you install the required patches and applications, it is just rocking. I am running it overclocked at 1.5GHZ and with some necessary patches. Had all the things, which they normally use. Playing Angry birds HD and Asphalt 6: Adrenaline, listening Music & watching Movies, Facebook & Browsing. The Facebook application is just awesome and browsing too is fast on wifi. Though the stock media player support only MP4 but I Played almost all the formats MP4 / AVI / MKV on the KalemSoft Media Player. Only few more things I will try on this - one is Android Porting (just waiting for CM7 or other stable), using non webos phone with TP. 2). Blackberry 9850 Torch This is again an awesome creation from Blackberry, wonderful touch and good graphics with the all new WebOS 7. Being a true Android fan now a days, I decided not to port to Blackberry again. So didn't used it except for checking GSM working and sold to Genius Dr. Vinay. Waiting for a review from him. 3). Verizon Fivespot (aka Tata Docomo Hotspot) This I neither bought from Verizon US nor from Tata Docomo. I bought it over Alibaba for Rs. 4500/- landing cost to Delhi. The best part is that I can use both CDMA Evdo & GSM HSUPA/HSDPA on this device just out of box without any issues. I had already posted my speed test results using this device.

Anyone using 32GB card with EVO 3D?? I am planing to buy.. Need suggestion. Thanks Sameer

I am interested in Back Cover, if in good condition. Please quote price. Thanks

^^^ http://www.rimweb.in/forums/topic/31965-interest-check-palm-pixi-palm-pixi-plus-digitizer/

Any good deal for 32GB Micro SD Card.. Need for my HTC EVO 3D. Also need Palm Pixi Plus Back Cover.. Any Deal.. Thanks Sameer

As most of you are aware by now MEID Registration and EVDO Activation on Reliance CDMA is a reality now thanks to efforts from members like HetalDP, Sadikk, etc. This will allow foreign CDMA handsets to be activated legally and use on Reliance Mobile CDMA network with EVDO. We never know if Reliance may force A-Key authentication which can affect foreign CDMA Handsets configured by changing ESN in the past; and changing handsets or selling to someone is a hassle too - so MEID registration is the way to go for complete peace of mind and you get the oppurtunity to have EVDO as well. Without doubt this is a major achievement for everyone for which we have been waiting for several years. In order to cover the costs incurred till now for everyone involved in making it a dream come true and for future software development we need to help them financially even though they are not forcing for it. So we have decided to raise funds (instead of seeking random donation) by uniformly charging the following amounts for members who would like to take advantage of MEID registration and/or EVDO activation: MEID Registration + EVDO Activation = 1000 MEID Registration only = 500 EVDO Activation only (if your MEID is already registered) = 750 This will benefit everyone as both the developers and the members will be able to support each other instead of having just a few members to bear the costs involved. I request everyone to help raise the funds for something we have been eagerly waiting for. Here are some FAQs which I presume will be asked by some members: Does it really cost that much for MEID Registration/EVDO Activation process? No, it will not cost that much. The major part of the charge will be spent for covering the costs incurred till now and for future software development. How do I get my MEID registered and activate EVDO for my MDN? Go here and read the instructions in the first post. How do I make the payment for the fundraiser? We will try to give you as many options as possible like Bank A/C Transfer, Credit Card, PayPal, etc. Please mention your preferred mode of payment when you send the email and the details will be given in the reply. I have already sent the email earlier? You will be informed about the payment details in the reply email. How do I configure my new foreign handset after MEID is registered and for EVDO activation? New topics with configuration instructions will be coming up in the Technical/Programming forum in the coming days along with other related FAQs. What are the softwares being developed? Currently the process for configuring the handset after MEID/EVDO registration/activation has to be done manually which can be bit difficult for the technically challenged. A new software that can configure A-Key, MDN, PPP and HDR UID & password with EVDO settings which is dump compatible for CDMA Workshop 2.7 is being planned. The software is also expected to load Reliance NAM settings like Channel/MNC/MCC/SID/NID and have device specific support as well. This software is only planned and not easy to develop since it involves CDMA programming and can take time as well. Since we do not know if it would be possible for sure; for configuring the handsets new topics with instructions to do that will come up in the Technical/Programming forum or by email one-on-one. Will I get refund if the software development is unsuccessful? No, we are not commited to provide the software based on the funds raised as that is not the main purpose of the fundraiser. Recovering the money spent till now is the first priority. If we get enough funds then we will go ahead to develop the software to write HDR and other parameters in the handset. Manual configuration support will be provided anyway as indicated earlier. I have sent the details by email few days ago but I haven't received any response yet? I will keep an eye on the whole process though I am not directly involved in it. Sadikk will be posting the updates in this topic. Where do I find the Bank payment details? See the attachment in this post