Welcome to Unofficial International LeEco Phone Support

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

zhoushiyi213

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

19 Good

About zhoushiyi213

  • Rank
    Member
  1. As far as I know unofficial xposed for sdk25 by PurifyOS works on the stock JUI 0704, and now the newly released official xposed v88 also woks on the stock JUI0704 I'm using Can't live without it!
  2. Hi; for those who have been using this ROM, is magisk functioning well with modules loaded? If so I'd be happy to flash this ROM!
  3. Great job, kime01! Thanks! I'm curious how you added support for magisk -- the kernel from stock ROM seems to have no support for loop device and installation always fails… Did you insert a loop.ko compiled from third party kernel source?
  4. I guess that's the case with DSDS (dual sim dual standby). To overcome that it has to be DSDA (dual sim dual active) which is even more elusive. Just found out that although the mcfg_hw.mbn in the firmware partition (non-hlos.img) supposedly support W+W, the actual mcfg_hw that is loaded by the phone is embedded in modem.b14 file, which comes without support of W+W. Interestingly, it seems that most mcfg (except Common/ROW, China Unicom, China Telecom and CMCC's mcfgs) in the firmware partition is not loadable, either with modemtestmode.apk or via PDC tools. In contrast, loading the mcfg_sw from EUI 5.9 ROM is successful (I tried t-mobile and att). Hope there is a simple tweak (maybe an nv item?) that can fix this -- with that loading the W+W mcfg_hw will enable 4G+3G standby!
  5. The command needs to be run after wifi is turned-on; the wifi country code is checked and set by the system whenever the wifi is turned-on or connected to AP :-)
  6. Hi guys, I just found out that in the non-HLOS.bin of JUI ROM, the mcfg_hw.mbn of MSM8952/LA,7+5 seems to include W+W support! Can anyone with two sim cards try if the phone can be dual sim, dual standby with 4G+3G or 3G+3G?
  7. By the way, you can check with root with command "dmesg | grep cfg80211" and look at the last set of results to see the country code and channels your phone is set to work with.
  8. Look at here for a list of wifi channel refulation by region code:https://en.m.wikipedia.org/wiki/List_of_WLAN_channels Say, you are in Europe or Japan where your router works on some channel forbidden in China, then your phone will not be able to detect your wifi signal because it's not looking for that with country code default to CN. I'm having my router working at channel 116 with 80Hz bandwidth in US and have to make the fix to let my phone detect its 5GHz channel.
  9. The wifi countrycode regulation management in JUI is messed up. It's automatically set to CN all the time, even if you set it once manually by compiled iw command. After hours of serching, the problem lays in the wifi-service.jar. Specifically, after decompiling with apktool, in the WifiStateMachine.java. Originally it's like public String getDefCountryCodeFromProperty() { String countrycode = SystemProperties.get("persist.sys.zeusis.country", "CN"); loge("CountryCode is " + countrycode); return "CN"; } Interestingly, the persist.sys.zeusis.country is always set to GL, and it's automatically set back to GL during reboot even after changing it. Nonetheless the function always returns CN as the country code. Stupid programmer! To make the story short, if you are using 0704 build of JUI on coolpad, you can replace /system/framework/wifi-service.jar with the attached file (I used "cat <path-to-new-wifi-service.jar> > /system/framework/wifi-service.jar to avoid permissions troubles). After reboot, you can manually set your country code by setting persist.wifi.countrycode (for example, by running "setprop persist.wifi.countrycode EU"; case sensitive). Cheers! wifi-service.jar
  10. You should know that this method only locks band instead of unlocks the band, and a similar tutorial has been posted a long, long time ago here:http://www.leeco.re/topic/1989-change-bands-lte-and-gsm-cool-1/ Our Cool1 (based on nv items) only supports the bands listed on their website. For extra bands values needs to be changed/modified in the nv items. On the hardware side, it may support more bands than those listed, but have you dismantled your phone to see the chips? If you haven't then don't say for sure. Also besides hardware it's really hard to figure out a proper non-HLOS.bin as well as nv items to make extra bands work. See my first post.
  11. If anyone happen to use the Coolpad Cool1 with EUI 5.9.026S (ZAXCNFN5902606201S), you can download the attached modified SystemUI.apk and use EUI moder with it. Note that it is mostly likely not working for any other EUI version or any other phone hardware. Also the atrached file has a quick toggle panel mod in expanded status bar with EUI mode (i.e. even without EUI moder :-). If you succeed with any ROM/phone other than Cool1 with 5.9.026S, please share your success~ Also anyone can make an updated version of EUI moder (original source is available on github), please please do share your work! Thanks in advance! SystemUI.apk
  12. After hourse of research and trying I finally work out a workaround for eui moder to work on EUI 5.8+ (tested working flawlessly on my Coolpad Cool1 running stock EUI 5.9.026S)! Since I'm not a developer nor do I know any thing about Android programming (including xposed), it has to be done in the hard way for now (if you don't understand each step do not proceed). Hope someone can update the EUI Moder module for easier modificaion! Here comes the steps: 1. Install the latest apktool. 2. Check if your ROM is odexed. If so, first deodex your ROM (no need to flash; just need the apk files); if not, grab the apk files (/system/framework/framework-res.apk and /system/priv-app/SystemUI/SystemUI.apk) and install the framework: apktool if framework-res.apk apktool if SystemUI.apk 3. Decompile SystemUI.apk: apktool d SystemUI.apk 4. Here comes the important part. Open SystemUI/smali/com/android/systemui/statusbar/policy/MobileSignalController.smali with a text editor. Locate the following paragraph (There can be multiple .line comments. Neglect those.): ....iput v1, p0, Lcom/android/systemui/statusbar/policy/MobileSignalController;->mImsRegState:I sget-boolean v1, Lcom/android/systemui/statusbar/phone/PhoneStatusBar;->LEUI_ENABLE:Z if-eqz v1, :cond_0 sput-object p1, Lcom/android/systemui/statusbar/policy/MobileSignalController;->mContext:Landroid/content/Context; invoke-direct {p0, p1}, Lcom/android/systemui/statusbar/policy/MobileSignalController;->initSystemFeature(Landroid/content/Context;)V sget-object v1, Lcom/android/systemui/statusbar/policy/MobileSignalController;->mContext:Landroid/content/Context; invoke-static {v1}, Lcom/android/keyguard/KeyguardUpdateMonitor;->getInstance(Landroid/content/Context;)Lcom/android/keyguard/KeyguardUpdateMonitor; move-result-object v1 iput-object v1, p0, Lcom/android/systemui/statusbar/policy/MobileSignalController;->mKeyguardUpdateMonitor:Lcom/android/keyguard/KeyguardUpdateMonitor; :cond_0 new-instance v1, Landroid/util/SparseArray; invoke-direct {v1}, Landroid/util/SparseArray;-><init>()V iput-object v1, p0, Lcom/android/systemui/statusbar/policy/MobileSignalController;->mNetworkToIconLookup:Landroid/util/SparseArray; .... Delete the bolded/stroke lines. In java it meas to skip EUI_enable check to run a few functions that is also required when AOSP feature is enabled (mainly wifi calling associated functions); here's the corresponding decompiled piece: ....if (PhoneStatusBar.LEUI_ENABLE) { mContext = context; initSystemFeature(context); this.mKeyguardUpdateMonitor = KeyguardUpdateMonitor.getInstance(mContext); } this.mNetworkToIconLookup = new SparseArray(); .... Don't know if disabling EUI features will introduce some other bugs that needs to be fixed. Hopefully not. 5. Now re-compile SystemUI.apk: apktool b SystemUI 6. Open the original, unmodified SystemUI.apk with 7-zip and copy META-INF and AndroidManifest.xml into the newly compiled SystemUI/dist/SystemUI.apk. Now the newly compiled SystemUI/dist/SystemUI.apk is ready for use. 7. Replace the SystemUI.apk in your phone with the new SystemUI.apk (make backup!), set correct permission (I always use Magisk for ROM modification -- recommended), but don't reboot immediately! 8. Connect the phone to your computer. Run adb on your computer, make sure your adb is trusted in the pop-up window (i.e. no confirmation dialogue is required for the adb connection). 9. Reboot your phone and wait for it to boot up. If SystemUI crashes, don't panic. Use adb to grant the new SystemUI proper permission: pm grant "com.android.systemui" "android.permission.READ_CONTACTS" 10. Now you can turn on the first option in EUI Moder settings and enjoy AOSP feature! Seems to me the mod is not a very big change and should be easy to be compiled into an updated version of EUI moder. Somebody who know android programming and XPOSED language, please do help us :-)
  13. Hi there. I've figure out a way to enable wifi calling on our EUI-based ROMs (I'm using metropcs and it works fine)! Here are the steps: First, edit/add following lines in /system/build.prop: persist.data.iwlan.enable=true persist.dbg.wfc_avail_ovr=1 Second (Optional!! -- It seems that the wifi calling feature works fine without this apk, and after days of trying I found out that that's the program that messes up with the incoming calls via cellular network. Not sure why it appears in Le X522 ROM but not in Le X527 ROM), place the attached apk under /system/priv-app/WfcService and reboot phone. It's a deodex-ed apk from LeS3/Le2 X522 offical rom. It says "t-mobile", but it also works with metropcs (t-mobile's branch), and I'm not sure about other carriers that offer wifi calling service. Last, try to launch the activity "wifi calling" from settings.apk (use applications info, or add shortcut from nova launcher, or use adb shell command, etc. It's near the end of the long list of activities). There you can turn on the wifi calling service and also set perferences (prioritize wifi or mobile network). If you have the correct APN settings and the carriers allows it, you can go somewhere without signal to test it out! (Simpler way: set the perferences to prioritize wifi calling, wait for around half a minute and see if the banner on status bar / lock screen says "t-mobile wifi calling" instead of simple t-mobile) For now airplane mode with wifi turned-on does not allow wifi calling, though. Please reply if it works with your carrier other than t-mobile(US)/metropcs. WfcService.apk
  14. Hi! Does anyone know what the function of "fsg" partition? If I wipe that partition as well as modemst1 and modemst2, followed by restoring my qcn file, the radio works still fine -- only takes much longer time to get signal. It has to have something to do with the radio. The header of the partition says "IMGEFS-SIGNED_IMAGE". 7-zip can open it but was unable to decompress it. Also if one unpack the pcb file, there is a corresponding image called "nv.tar.mbn". Does that updates the calibration data during our system update, and is there any way to view it? Help please!
  15. If anyone haven't heard about it from the Chunese official forum , Coolpad is going to publish new ROM for Cool1 and Cool1C! It's named as JUI -- no longer stupid EUI and without many useless preset apps, and it' based on android 7.1.1! Seems to be less modified from AOSP to me. Look here for screenshots:http://bbs.coolpad.com/thread-5833897-1-1.html It's being tested in a small circle these days. The expected release date is said to be in June.