Guest debian2 Posted October 30, 2014 Report Share Posted October 30, 2014 How to remove 2 SIM settings from my v811's firmware? Link to comment Share on other sites More sharing options...
Guest KonstaT Posted October 30, 2014 Report Share Posted October 30, 2014 How to remove 2 SIM settings from my v811's firmware? Isn't that a dual-SIM device? Why would you want to remove it? Link to comment Share on other sites More sharing options...
Guest debian2 Posted October 30, 2014 Report Share Posted October 30, 2014 Isn't that a dual-SIM device? Why would you want to remove it? v811 is single-SIM. Why? Because it is excess. Many garbage settings for SIM-2 Link to comment Share on other sites More sharing options...
Guest KonstaT Posted October 30, 2014 Report Share Posted October 30, 2014 v811 is single-SIM. Why? Because it is excess. Many garbage settings for SIM-2 What is the exact make/model of your device and where (country) it was purchased? Have you installed any official ZTE firmware packages to your device? Post a screenshot of 'Kis 3 Hardware Info' app too. Dual-SIM features are enabled on devices with ro.boot.hwversion=wmfA.6 and so far that has only been reported on V811W's. Link to comment Share on other sites More sharing options...
Guest debian2 Posted October 30, 2014 Report Share Posted October 30, 2014 What is the exact make/model of your device and where (country) it was purchased? Have you installed any official ZTE firmware packages to your device? Post a screenshot of 'Kis 3 Hardware Info' app too. Dual-SIM features are enabled on devices with ro.boot.hwversion=wmfA.6 and so far that has only been reported on V811W's. My phone is «Билайн Смарт 2» («Beeline Smart 2»). Purchased in Russia. I firmwared Android_4.4_EU_P821E10V1.0.0B06_DL with Open C update tool. My build.prop: # begin build properties # autogenerated by buildinfo.sh ro.build.id=KTU84Q ro.build.display.id=cm_kis3-userdebug 4.4.4 KTU84Q dc854dd8a2 test-keys ro.build.version.incremental=dc854dd8a2 ro.build.version.sdk=19 ro.build.version.codename=REL ro.build.version.release=4.4.4 ro.build.date=Wed Oct 29 09:53:58 EET 2014 ro.build.date.utc=1414569238 ro.build.type=userdebug ro.build.user=tuomas ro.build.host=hope ro.build.tags=test-keys ro.product.brand=ZTE ro.product.name=cm_kis3 ro.product.board=MSM8610 ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=ZTE ro.product.locale.language=en ro.product.locale.region=US ro.wifi.channels= ro.board.platform=msm8610 # ro.build.product is obsolete; use ro.product.device ro.build.product=kis3 ro.product.model=Kis 3 ro.product.device=kis3 # Do not try to parse ro.build.description or .fingerprint ro.build.description=msm8610-user 4.4.2 KOT49H eng.root.20140509.130110 release-keys ro.build.fingerprint=ZTE/ZTE-P821E10/ZTE-P821E10:4.4.2/KOT49H/eng.root.20140509.130110:user/release-keys ro.build.characteristics=default ro.cm.device=kis3 # end build properties # # from device/zte/kis3/system.prop # # Audio ro.qc.sdk.audio.fluencetype=none persist.audio.fluence.voicecall=true persist.audio.fluence.voicerec=false persist.audio.fluence.speaker=true use.voice.path.for.pcm.voip=true audio.offload.buffer.size.kb=32 audio.offload.gapless.enabled=true audio.offload.multiple.enabled=false audio.offload.pcm.enable=false av.offload.enable=false av.streaming.offload.enable=false tunnel.audio.encode=false # Display ro.sf.lcd_density=240 ro.opengles.version=196608 debug.composition.type=dyn debug.hwc.dynThreshold=1.5 debug.sf.fb_always_on=1 # GPS ro.qc.sdk.izat.premium_enabled=0 ro.qc.sdk.izat.service_mask=0x0 persist.gps.qc_nlp_in_use=0 persist.loc.nlp_name=com.qualcomm.services.location ro.gps.agps_provider=1 # Media media.stagefright.enable-player=true media.stagefright.enable-http=true media.stagefright.enable-aac=true media.stagefright.enable-qcp=true media.stagefright.enable-fma2dp=true media.stagefright.enable-scan=true mmp.enable.3g2=true media.aac_51_output_enabled=true mm.enable.qcom_parser=37491 vidc.debug.level=1 # Memory ro.config.low_ram=true ro.ksm.default=1 # Qualcomm ro.vendor.extension_library=/system/vendor/lib/libqc-opt.so ro.qualcomm.cabl=0 # Recovery ro.cwm.enable_key_repeat=true # Telephony rild.libpath=/vendor/lib/libril-qc-qmi-1.so rild.libargs=-d /dev/smd0 persist.rild.nitz_plmn= persist.rild.nitz_long_ons_0= persist.rild.nitz_long_ons_1= persist.rild.nitz_long_ons_2= persist.rild.nitz_long_ons_3= persist.rild.nitz_short_ons_0= persist.rild.nitz_short_ons_1= persist.rild.nitz_short_ons_2= persist.rild.nitz_short_ons_3= ril.subscription.types=NV,RUIM DEVICE_PROVISIONED=1 persist.radio.msgtunnel.start=false ro.telephony.default_network=0 telephony.lteOnCdmaDevice=1 persist.data_netmgrd_mtu=1358 persist.radio.apm_sim_not_pwdn=0 ro.telephony.call_ring.multiple=false # Time services persist.timed.enable=true # Wifi wifi.interface=wlan0 # # ADDITIONAL_BUILD_PROPERTIES # ro.rommanager.developerid=cyanogenmod ro.com.google.clientidbase=android-zte keyguard.no_require_sim=true 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.com.android.wifi-watchlist=GoogleGuest ro.setupwizard.enterprise_mode=1 ro.com.android.dateformat=MM-dd-yyyy ro.com.android.dataroaming=false ro.build.selinux=1 persist.sys.dalvik.multithread=false persist.sys.dun.override=0 persist.sys.root_access=1 ro.cm.version=11-20141029-UNOFFICIAL-KonstaKANG-kis3 ro.cm.releasetype=UNOFFICIAL ro.modversion=11-20141029-UNOFFICIAL-KonstaKANG-kis3 ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy persist.sys.recovery_update=false ro.cm.display.version=11-20141029-UNOFFICIAL-KonstaKANG-kis3 ro.config.notification_sound=Argon.ogg ro.config.alarm_alert=Hassium.ogg ro.config.ringtone=Orion.ogg ro.carrier=unknown dalvik.vm.heapstartsize=5m dalvik.vm.heapgrowthlimit=48m dalvik.vm.heapsize=128m dalvik.vm.heaptargetutilization=0.75 dalvik.vm.heapminfree=512k dalvik.vm.heapmaxfree=2m persist.sys.dalvik.vm.lib=libdvm.so dalvik.vm.lockprof.threshold=500 net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt Link to comment Share on other sites More sharing options...
Guest KonstaT Posted October 30, 2014 Report Share Posted October 30, 2014 My phone is «Билайн Смарт 2» («Beeline Smart 2»). Purchased in Russia. I firmwared Android_4.4_EU_P821E10V1.0.0B06_DL with Open C update tool. So then your device is Билайн Смарт 2 (Beeline Smart 2), not V811 like you were saying. Have you installed any other ZTE firmware after using the windows flasher? Because for some reason people on Russian forums have been instructed to install V811W (dual-SIM) firmware on their device?!? That would mean you'd also have a bootloader from dual-SIM firmware which passes the hwversion value. That is build.prop from my CyanogenMod build so that's no use here. I already tried asking several times but no one answered. I guess that happens when you're only inside your 4PDA bubble. Could you (or someone else with Beeline Smart2) post a screenshot of hardware info app to the appropriate thread? There's one notable difference in Beeline Smart2's that isn't addressed yet. I'd need some intelligent way to identify Beeline Smart2's first (ro.boot.hwversion possibly?). Anyone? Beeline Smart2 has a smaller capacity battery (1200mAh vs 1400mAh) and it should use a different kernel battery monitoring driver. This would be easily resolved if there was some way to identify Beeline Smart2's (ro.boot.hwversion possibly?). I still need the above information from 'untouched' Beeline Smart 2 (no other ZTE firmware updates than from Beeline). Sorry, yours is no good anymore. I even already wrote the code to use the correct battery data driver on Beeline Smart 2's, I'd only need to know the hwversion... Link to comment Share on other sites More sharing options...
Guest debian2 Posted October 30, 2014 Report Share Posted October 30, 2014 So then your device is Билайн Смарт 2 (Beeline Smart 2), not V811 like you were saying. Have you installed any other ZTE firmware after using the windows flasher? Because for some reason people on Russian forums have been instructed to install V811W (dual-SIM) firmware on their device?!? That would mean you'd also have a bootloader from dual-SIM firmware which passes the hwversion value. That is build.prop from my CyanogenMod build so that's no use here. I already tried asking several times but no one answered. I guess that happens when you're only inside your 4PDA bubble. I still need the above information from 'untouched' Beeline Smart 2 (no other ZTE firmware updates than from Beeline). Sorry, yours is no good anymore. I even already wrote the code to use the correct battery data driver on Beeline Smart 2's, I'd only need to know the hwversion... OK. All of these from Beeline Smart 2 firmware 0.3 build.prop # begin build properties # autogenerated by buildinfo.sh ro.build.id=KOT49H ro.build.display.id=Beeline Smart2 V0.3 ro.build.inner.version=BEE_RU_P821E10V1.0.0B04 ro.sdupdate.check.info=P821E10 ro.build.secureversionid= ro.build.version.incremental=eng.root.20140531.014004 ro.build.version.sdk=19 ro.build.version.codename=REL ro.build.version.release=4.4.2 ro.build.date=Sat May 31 01:41:17 CST 2014 ro.build.date.utc=1401471677 ro.build.type=user ro.build.user=root ro.build.host=SCL_XA242_087 ro.build.tags=release-keys ro.product.model=Beeline Smart2 ro.product.brand=ZTE ro.product.name=ZTE-V811 ro.product.device=ZTE-V811 ro.product.board=MSM8610 ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=ZTE ro.product.locale.language=ru ro.product.locale.region=RU ro.wifi.channels= ro.board.platform=msm8610 # ro.build.product is obsolete; use ro.product.device ro.build.product=ZTE-V811 # Do not try to parse ro.build.description or .fingerprint ro.build.description=msm8610-user 4.4.2 KOT49H eng.root.20140531.014004 release-keys ro.build.fingerprint=ZTE/ZTE-V811/ZTE-V811:4.4.2/KOT49H/eng.root.20140531.014004:user/release-keys ro.build.characteristics=default # end build properties # # from device/qcom/msm8610/system.prop # # # system.prop for msm8610 # # Use reference RIL for initial bringup #rild.libpath=/system/lib/libreference-ril.so rild.libpath=/vendor/lib/libril-qc-qmi-1.so rild.libargs=-d /dev/smd0 persist.rild.nitz_plmn= persist.rild.nitz_long_ons_0= persist.rild.nitz_long_ons_1= persist.rild.nitz_long_ons_2= persist.rild.nitz_long_ons_3= persist.rild.nitz_short_ons_0= persist.rild.nitz_short_ons_1= persist.rild.nitz_short_ons_2= persist.rild.nitz_short_ons_3= ril.subscription.types=NV,RUIM DEVICE_PROVISIONED=1 persist.radio.msgtunnel.start=false persist.radio.atfwd.start=false # Start in cdma mode ro.telephony.default_network=3 #ZTE shihongliang 20140315 reduce UNSOL_RESPONSE_VOICE_NETWORK_STATE_CHANGED message persist.radio.add_power_save=1 #ZTE_MODIFY by shihongliang enable fastdormancy persist.env.fastdorm.enabled=true # # system props for the cne module # persist.cne.feature=1 # Skip /sys/power/wait_for_fb_* nodes and # force FB to be always on debug.sf.fb_always_on=1 debug.composition.type=dyn debug.gralloc.map_fb_memory=0 debug.hwc.dynThreshold=1.5 dalvik.vm.heapsize=36m dev.pm.dyn_samplingrate=1 ro.hdmi.enable=true #system props for the MM modules media.stagefright.enable-player=true media.stagefright.enable-http=true media.stagefright.enable-aac=true media.stagefright.enable-qcp=true media.stagefright.enable-fma2dp=true media.stagefright.enable-scan=true mmp.enable.3g2=true media.aac_51_output_enabled=true #37491 is decimal sum of supported codecs in AAL #codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS mm.enable.qcom_parser=37491 # VIDC: debug_levels # 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs vidc.debug.level=1 # # system props for widevine # persist.gralloc.cp.level3=1 # add by ZTE lizhao for widevine 20120517 drm.service.enabled=true # add by ZTE lizhao for widevine 20120517 # # system props for the data modules # ro.use_data_netmgrd=true #system props for time-services persist.timed.enable=true #ZTEBSP lichuangchuang add for audio start. 20130922 # System props for audio persist.audio.fluence.mode=endfire persist.audio.vr.enable=false persist.audio.lowlatency.rec=false persist.audio.handset.mic=analog # System prop to select audio resampler quality af.resampler.quality=255 # System prop to select MPQAudioPlayer by default on mpq8064 mpq.audio.decode=true #ZTEBSP lichuangchuang add for audio end. 20130922 # # system prop for opengles version # # 196608 is decimal for 0x30000 to report version 3 ro.opengles.version=196608 # # System props for telephony # System prop to turn on CdmaLTEPhone always telephony.lteOnCdmaDevice=1 # simulate sdcard on /data/media # persist.fuse_sdcard=true # #snapdragon value add features # ro.qc.sdk.audio.ssr=false ##fluencetype can be "fluence" or "fluencepro" or "none" ro.qc.sdk.audio.fluencetype=none persist.audio.fluence.voicecall=true persist.audio.fluence.voicerec=false persist.audio.fluence.speaker=true # Reduce Background apps limit ro.sys.fw.bg_apps_limit=20 # System property for cabl #zte modify 20130904 ro.qualcomm.cabl=0 # system prop for NFC DT ro.nfc.port=I2C #liangrh add GMS clientid ro.com.google.clientidbase= android-zte ro.com.google.clientidbase.yt= android-zte ro.com.google.clientidbase.gmm= android-zte ro.com.google.clientidbase.am = android-vimpelcom-ru ro.com.google.clientidbase.ms = android-zte # #DASH video streaming #Specify max allowed resolution/bandwidth for representations #Set allowed avsync window during playback # persist.dash.max.rep.resolution=1280*720 persist.dash.max.rep.bandwidth=4000000 persist.dash.avsync.window.msec=100 tunnel.audio.encode = false #use VERY_HIGH_QUALITY for audio resampler af.resampler.quality=4 ro.config.low_ram=true #Buffer size in kbytes for compress offload playback audio.offload.buffer.size.kb=32 #8x10 does not support tunnel av playback #this prop should be set to false all the time av.offload.enable=false #enable voice path for PCM VoIP by default use.voice.path.for.pcm.voip=true # #System property for FM transmitter # ro.fm.transmitter=false #enable dsp gapless mode by default audio.offload.gapless.enabled=true # ZTE_MODIFY ,zhangshuzu,2014.04.11, System props for streaming ua profile, begin ro.streaming.ua.prof = http://zte.com.cn/mobile/uaprof/Beeline_Smart2.xml # ZTE_MODIFY ,zhangshuzu,2014.04.11, System props for streaming ua profile, end # zte_modify,sonlgifeng,for 8x10 default timezone,2013.12.30 begin persist.sys.timezone=Europe/Moscow # zte_modify,sonlgifeng,for 8x10 default timezone,2013.12.30 end # ZTE_MODIFY,liyanfang,for 8x10 default MTU size,2014.01.15 begin # set default mtu to 1358 persist.data_netmgrd_mtu=1358 # ZTE_MODIFY,liyanfang,for 8x10 default MTU size,2014.01.15 end # zte_modify,chenshaohua,for 8x10 default memory optimize,2014.03.11 begin persist.sys.memoryclean.enable=1 persist.sys.memoryclean.thres=10 # zte_modify,chenshaohua,for 8x10 default memory optimize,2014.03.11 end # ZTE_MODIFY caoyaobin disable JIT dalvik.vm.jit.codecachesize=0 # # ADDITIONAL_BUILD_PROPERTIES # persist.sys.logkit.ctrlcode=0 keyguard.no_require_sim=true ro.com.android.dataroaming=false ro.com.android.dateformat=MM-dd-yyyy ro.config.ringtone=Ring_Synth_04.ogg ro.config.notification_sound=pixiedust.ogg ro.carrier=unknown ro.config.alarm_alert=Alarm_Classic.ogg ro.vendor.extension_library=/vendor/lib/libqc-opt.so persist.radio.apm_sim_not_pwdn=0 ro.config.low_ram=true dalvik.vm.heapstartsize=5m dalvik.vm.heapgrowthlimit=48m dalvik.vm.heapsize=128m dalvik.vm.heaptargetutilization=0.75 dalvik.vm.heapminfree=512k dalvik.vm.heapmaxfree=2m ro.setupwizard.mode=OPTIONAL ro.com.google.gmsversion=4.4_r3 persist.sys.dalvik.vm.lib=libdvm.so net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt ro.qc.sdk.izat.premium_enabled=1 ro.qc.sdk.izat.service_mask=0x5 persist.gps.qc_nlp_in_use=1 persist.loc.nlp_name=com.qualcomm.services.location ro.gps.agps_provider=1 default.prop # # ADDITIONAL_DEFAULT_PROPERTIES # ro.secure=1 ro.adb.secure=1 ro.allow.mock.location=0 ro.debuggable=0 persist.sys.strict_op_enable=false persist.sys.whitelist=/system/etc/whitelist_appops.xml Link to comment Share on other sites More sharing options...
Guest KonstaT Posted October 30, 2014 Report Share Posted October 30, 2014 OK. All of these from Beeline Smart 2 firmware 0.3 Sorry, I guess I didn't make myself quite clear. I need that information from an 'untouched' Beeline Smart2 (no ZTE updates what so ever). Restoring CWM backup of Beeline firmware is not enough. It does not restore your device's bootloaders or modem firmware. These will always remain the same as the last official ZTE firmware update you've installed (or the stock firmware your device shipped with). Take your favorite zip tool and look inside an official ZTE update.zip, then look inside CyanogenMod ROM package. You'll notice some files missing right from the start. These are the bootloader/modem firmware files. As far as I know there's official Beeline update.zip thus no way to restore/flash Beeline bootloader/modem. Also you didn't answer if you've installed V811 (dual-SIM) firmware to your device? That might explain the wmfA.6 and in that case flashing Kis 3 (single-SIM) firmware might make a difference. It's of course also possible that all Beeline Smart2's are identified as wmfA.6 which wouldn't be ideal in terms what I had planned. :( I'd still need the data from few devices to verify. Link to comment Share on other sites More sharing options...
Guest debian2 Posted October 30, 2014 Report Share Posted October 30, 2014 What about kernel features? Look at these kernels: http://forum.xda-developers.com/showthread.php?t=2160537 http://forum.xda-developers.com/showthread.php?t=2077269 http://forum.xda-developers.com/showthread.php?t=2295108 I want undervoltage on our phone or VDD. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted October 30, 2014 Report Share Posted October 30, 2014 What about kernel features? Look at these kernels: http://forum.xda-developers.com/showthread.php?t=2160537 http://forum.xda-developers.com/showthread.php?t=2077269 http://forum.xda-developers.com/showthread.php?t=2295108 I want undervoltage on our phone or VDD. Ancient 2.6 kernels are hardly a good reference for a modern Qualcomm kernel. :P FYI there isn't even working CPU overclocking on any Qualcomm b-family (msm8610, msm8226, msm8974) device let alone voltage control. I plan to keep this CM kernel clean with only hardware support patches from CAF and security patches from mainline Linux kernel and Google's Android reference kernel. I've never been much of a kernel hacker either so I'm not planning any custom kernels. I might look into 3.10 porting if CAF will have msm8610 reference for it (doesn't have yet). New Lollipop devices will come with 3.10 but the old will likely continue using 3.4. My kernel source is linked in the first post and you are free to fork it and start hacking. ;) Link to comment Share on other sites More sharing options...
Guest okmikel Posted October 31, 2014 Report Share Posted October 31, 2014 New build. New kernel with plenty of updates from CAF. cm-11-20141029-UNOFFICIAL-KonstaKANG-kis3.zip http://www.mediafire.com/?nrcmzjslrpucvdy md5:5feadb777464945e1e7af854d408272b -new kernel (clean up a lot of ZTE crap and add a ton of updates from CAF) -fix bootclass path (possibly caused libdvm to crash occasionally) -automatically enable dual-SIM features on V811W (ro.boot.hwversion=wmfA.6) -encrypting device works (quite sure it didn't before) -enable defferable timer for KSM -Kis3Info: add ambient light/proximity sensor info Fantastic build, installed it yesterday and everything I have tested works find. Battery life is also great with this build, unplugged my phone this morning, now still at ~85% with my normal use, on stock firmware and the older CM11 build it was on evening at ~70-75%. Thanks a lot. Link to comment Share on other sites More sharing options...
Guest AwesomeLewis24 Posted November 1, 2014 Report Share Posted November 1, 2014 (edited) It's awesome and works - although my mic doesn't pick up any sound in call nor does it play any sound from the other end of the call; leading to silent calls. Very annoying and it's my only problem.. :/ EDIT: This is annoying - I'm reflashing the stock rom. Edited November 1, 2014 by AwesomeLewis24 Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 2, 2014 Report Share Posted November 2, 2014 It's awesome and works - although my mic doesn't pick up any sound in call nor does it play any sound from the other end of the call; leading to silent calls. Very annoying and it's my only problem.. :/ EDIT: This is annoying - I'm reflashing the stock rom. I'm sure, not nearly as annoying as posts like yours. :P How about you try to provide at least some useful information instead of just whining... In-call audio works perfectly fine on my device and it's expected work (because it says so on the OP). There's never been a report of such issue and there's also a previous build listed in the second post in case this is something that got broken recently. So, what is the exact make/model of your device (Kis 3?)? What is your ro.boot.hwversion in 'Kis 3 Hardware Info' app (also included in the ROM)? Do you have dual-SIM features enabled (two SIM slots exposed)? Wouldn't that raise suspicion if your device only has one... From now on every bug report must include info about the exact make/model of your device and screenshot/info from the 'Kis 3 Hardware Info' app. I really didn't write it for nothing. I need that information if you want your device supported. There's so many variants of this device (Kis 3, Beeline Smart2, Moche/MEO Smart A16, V811, V811W, etc) and I can't test everything on my Open C (there's even two versions of that). Link to comment Share on other sites More sharing options...
Guest AwesomeLewis24 Posted November 3, 2014 Report Share Posted November 3, 2014 I'm sure, not nearly as annoying as posts like yours. :P How about you try to provide at least some useful information instead of just whining... In-call audio works perfectly fine on my device and it's expected work (because it says so on the OP). There's never been a report of such issue and there's also a previous build listed in the second post in case this is something that got broken recently. So, what is the exact make/model of your device (Kis 3?)? What is your ro.boot.hwversion in 'Kis 3 Hardware Info' app (also included in the ROM)? Do you have dual-SIM features enabled (two SIM slots exposed)? Wouldn't that raise suspicion if your device only has one... From now on every bug report must include info about the exact make/model of your device and screenshot/info from the 'Kis 3 Hardware Info' app. I really didn't write it for nothing. I need that information if you want your device supported. There's so many variants of this device (Kis 3, Beeline Smart2, Moche/MEO Smart A16, V811, V811W, etc) and I can't test everything on my Open C (there's even two versions of that). 1. I wasn't necessarily whining, just was kinda angry at that time. Apologies, guess I let my anger get the better of me :( 2. Now I think about it, it was probably because of the dual-SIM thingy, my device only has one sim slot. Texts seemed to send fine though. I've reflashed the stock ROM anyways so yeah, that's all from me. I respect you man, you're a good guy. You supplied me with the root for my phone when I had been searching on the internet for AGES. Thanks man, but until next time, goodbye Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 3, 2014 Report Share Posted November 3, 2014 1. I wasn't necessarily whining, just was kinda angry at that time. Apologies, guess I let my anger get the better of me :( 2. Now I think about it, it was probably because of the dual-SIM thingy, my device only has one sim slot. Texts seemed to send fine though. I've reflashed the stock ROM anyways so yeah, that's all from me. I respect you man, you're a good guy. You supplied me with the root for my phone when I had been searching on the internet for AGES. Thanks man, but until next time, goodbye Well, I'm getting a little frustrated here myself too. ;) Recent builds I've posted have ~1000 downloads each which should be large enough userbase for me to get the info I need. Yet somehow it has turned out to be an overwhelming task for people to post a simple screenshot! Apparently I can't expect any help from the community. I can't even expect to get a simple 'thank you' when everything is working as intended. But I guess it's alright for you to expect everything to work fine on devices that I don't even have! I worked on the assumption that dual-SIM devices are identified with ro.boot.hwversion=wmfA.6 which I received from two V811W users (had never seen that before). I also several times repeated that I'm going to automatically enable dual-SIM features on such devices on the next build. Not once anyone say 'hey, I have ro.boot.hwversion=wmfA.6 on my single-SIM device too'. Actually I'm yet to receive any 'Kis 3 Hardware Info' screenshots from an actual Kis 3! You certainly didn't post yours. The app works fine on stock ROM too... It actually now looks like all Kis 3 variants return wmfA.6 (where only Open C returns wmfA.4) and I've since reverted this change. This also means that there is no intelligent way to indentify different variants. V811W users will need to keep adding that system property enable to enable dual-SIM features (I'll likely make a flashable zip that will survive ROM updates). Beeline Smart2 users would need to flash a separate kernel (don't feel like doing anything for you guys though :(). Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 4, 2014 Report Share Posted November 4, 2014 New build. Might be a while until the next one since the Lollipop fun is about to start. :D Reverted the change that lead to dual-SIM features being enabled on devices they shouldn't be. Issue with importing contact from SIM card someone reported should also be fixed in upstream CyanogenMod. Dual-SIM (V811W) users will have to manually add a line (persist.radio.multisim.config=dsds) to /system/build.prop to enable dual-SIM features from now on. I might make a flashable zip to do that when I get around to it. cm-11-20141104-UNOFFICIAL-KonstaKANG-kis3.zip http://www.mediafire.com/?hzkm91a0a9181h7 md5:a23d830edaae7532d56ea3b5a7b31763 -don't automatically enable dual-SIM according to hwversion -update bluetooth configuration -Kis3Info: add partition layout info (Open C vs. Kis 3) -fix importing SIM contacts (merged) Link to comment Share on other sites More sharing options...
Guest jadam Posted November 4, 2014 Report Share Posted November 4, 2014 Thanks for all the build updates, I might be the only one, but I installed the 20141029 build and still had system app crashes, with both the CM GApps and the pico PA GApps, also a new issue where my bluetooth headset would disconnect after about 10 seconds, I did an ABA check with the 20141012 build and found it resolved the bluetooth issue so I've gone back to that. Please does this latest 20141104 build have any bluetooth related updates as per the CAF build? Otherwise I'll stick with the 20141012 build, I can live with the apps crashing as it doesn't seem to have a practical effect on phone use? I have the same hardware as hecatae, Open C from ZTE ebay UK, and wiped /system, /data, /cache as well as data wipe between installs (and reset bluetooth headset each time). Link to comment Share on other sites More sharing options...
Guest IvanIvanov97 Posted November 4, 2014 Report Share Posted November 4, 2014 Hi. I installed cm-11-20141029 yesterday. Everything is fine now.How to update to a new version cm-11-20141104? Do a full wipe? And will there be a future version Lolipop? Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 4, 2014 Report Share Posted November 4, 2014 Thanks for all the build updates, I might be the only one, but I installed the 20141029 build and still had system app crashes, with both the CM GApps and the pico PA GApps, also a new issue where my bluetooth headset would disconnect after about 10 seconds, I did an ABA check with the 20141012 build and found it resolved the bluetooth issue so I've gone back to that. Please does this latest 20141104 build have any bluetooth related updates as per the CAF build? Otherwise I'll stick with the 20141012 build, I can live with the apps crashing as it doesn't seem to have a practical effect on phone use? I have the same hardware as hecatae, Open C from ZTE ebay UK, and wiped /system, /data, /cache as well as data wipe between installs (and reset bluetooth headset each time). Please test the new build with a clean installation and post logcats of both issue if they're still there. Actually there wasn't any device specific bluetooth changes between 20141012 and 20141029 builds. I'll have to check if there were any in upstream CyanogenMod. There was bunch of audio releated kernel changes though. In today's build I've updated the bluetooth build config to what it should be these days (missed it from the changelog because I had already pushed it earlier). Unfortunately I don't have too many bluetooth devices to test with, I don't even own a headset. Hi. I installed cm-11-20141029 yesterday. Everything is fine now. How to update to a new version cm-11-20141104? Do a full wipe? And will there be a future version Lolipop? Just flash the new ROM package in recovery. No need to wipe anything. Lollipop source code was just released last night. I can't make any promises and I won't give any timeline for it (other than months, not days or weeks). But I'm certainly going to try. ;) Link to comment Share on other sites More sharing options...
Guest IvanIvanov97 Posted November 4, 2014 Report Share Posted November 4, 2014 Use CWM for update? :blush: Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 4, 2014 Report Share Posted November 4, 2014 Use CWM for update? :blush: Yes. Link to comment Share on other sites More sharing options...
Guest IvanIvanov97 Posted November 4, 2014 Report Share Posted November 4, 2014 Yes. Thx. I already updated. Link to comment Share on other sites More sharing options...
Guest saVTRonic Posted November 4, 2014 Report Share Posted November 4, 2014 New build. Might be a while until the next one since the Lollipop fun is about to start. :D Reverted the change that lead to dual-SIM features being enabled on devices they shouldn't be. Issue with importing contact from SIM card someone reported should also be fixed in upstream CyanogenMod. Dual-SIM (V811W) users will have to manually add a line (persist.radio.multisim.config=dsds) to /system/build.prop to enable dual-SIM features from now on. I might make a flashable zip to do that when I get around to it. cm-11-20141104-UNOFFICIAL-KonstaKANG-kis3.zip http://www.mediafire.com/?hzkm91a0a9181h7 md5:a23d830edaae7532d56ea3b5a7b31763 Thanks, previous version works perfectly on a french ZTE Open C. So, to update, i just need to do the step n°5 ? All my data/config will stay ? What about gapps-kk ? Link to comment Share on other sites More sharing options...
Guest KonstaT Posted November 4, 2014 Report Share Posted November 4, 2014 Thanks, previous version works perfectly on a french ZTE Open C. So, to update, i just need to do the step n°5 ? All my data/config will stay ? What about gapps-kk ? Yes, just flash the new ROM zip. No need to wipe anything or install gapps again. There's a backup script that runs during installation and it will backup/restore the gapps you've installed. If you're still using the same gapps package, you can safely reinstall it though. If you switch to a different gapps package, you need to also format /system first because of the backup script. And then a reminder of the 'no wipe - no whine' policy. :P If you encounter any issue, please try to reproduce them on a clean installation first. Link to comment Share on other sites More sharing options...
Guest okmikel Posted November 4, 2014 Report Share Posted November 4, 2014 New build. Might be a while until the next one since the Lollipop fun is about to start. :D Reverted the change that lead to dual-SIM features being enabled on devices they shouldn't be. Issue with importing contact from SIM card someone reported should also be fixed in upstream CyanogenMod. Dual-SIM (V811W) users will have to manually add a line (persist.radio.multisim.config=dsds) to /system/build.prop to enable dual-SIM features from now on. I might make a flashable zip to do that when I get around to it. cm-11-20141104-UNOFFICIAL-KonstaKANG-kis3.zip http://www.mediafire.com/?hzkm91a0a9181h7 md5:a23d830edaae7532d56ea3b5a7b31763 -don't automatically enable dual-SIM according to hwversion -update bluetooth configuration -Kis3Info: add partition layout info (Open C vs. Kis 3) -fix importing SIM contacts (merged) Installed the build right now and at first sight it works superb on my german Open C. Thanks again for your work. I nearly can't belive you are going to try lolipop. I am looking forward to it :) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now