Krsmqn
Member
Service worked fine if I remember correctly. I haven't had the n9511 for several months now so I won't be much help. Mine was one of the originals though. If yours is new, there may be some subtle differences. Idk.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
CM11 Developer and Tester thread for ZTE MSM 8x30 devices
- Thread starter hroark13
- Start date
- Status
Service worked fine if I remember correctly. I haven't had the n9511 for several months now so I won't be much help. Mine was one of the originals though. If yours is new, there may be some subtle differences. Idk.
i tried (Zte radiant Z740 & tester3a). it doesn't work. Still can not connect to the camera.
jseiscio
Well-Known Member
Yeah I understand it's not ready. I'm pretty familiar with the whole process and I'm willing to test anything you guys put out. Also I'm going to link this thread in the official boost Max forum, as I'm sure there are some guys who would also test there as well.
HMT Chryssi
Member
How do you want me to install this?
warrior1988
Lurker
Zte radiant did you add the camera drivers setting to script.bin from boot.IMG so the script.bin loads the libs/modules/driver
no, never heard of that before, and that is not how the drivers are loaded on Android
warrior1988
Lurker
If script.bin isn't config right for the devices drivers then the drivers won't work. I believe you must convert script.bin to script.fex to edit then back to script.bin
jimsmith80
Android Expert
On my build, soon after the device boot it states that the sim card is not installed. Have you ever had this happen on a cdma build. I swapped out the radio files for the stock warplte files, and changed
frameworks/native/data/etc/android.hardware.telephony.gsm.xml:system/etc/permissions/android.hardware.telephony.gsm.xml
to
frameworks/native/data/etc/android.hardware.telephony.cdma.xml:system/etc/permissions/android.hardware.telephony.cdma.xml
I ran grep for sim on the device tree, and didn't see anything that caught my eye
frameworks/native/data/etc/android.hardware.telephony.gsm.xml:system/etc/permissions/android.hardware.telephony.gsm.xml
to
frameworks/native/data/etc/android.hardware.telephony.cdma.xml:system/etc/permissions/android.hardware.telephony.cdma.xml
I ran grep for sim on the device tree, and didn't see anything that caught my eye
KingReaper
Newbie
So does your sim work now? If so I will swap out the radio files with stock files for the zte source and then it would be usable
jimsmith80
Android Expert
The warplte does not have a sim, so short answer is no.
try adding this to the build.prop, and then do a factory wipe
ro.telephony.ril.v3=qcomdsds
telephony.lteOnCdmaDevice=1
persist.radio.tdscdma_present=2
ro.telephony.default_network=7
ro.cdma.home.operator.numeric=311870
ro.cdma.home.operator.alpha=Boost Mobile
KingReaper
Newbie
OK sorry didn't know that
That's weird cause my warplte has a sim.
junkie2100
Android Expert
they all do, the lte on the warp 4g actually does use a sim card, well, a uim card but same basic thing just different size, thats like arguing the difference between an sd and a micro sd
also on a side note, you have to use the sprint numeric network info for it to function properly in my experience, 310120, boosts is just a mask that cm doesnt seem to agree with in most cases, that will not however cause failure of the lte card reader, not sure why it would do that. what ril are you using??? i see it says qcomdsds or something like that, for the force i think we used standard qcomsharedril or something like that and the sony shared one worked very well on the sequent but that was 3g only so i cant say for sure, it also worked with the qcom shared as well though
jimsmith80
Android Expert
You can pull the umi, and 3g/cdma will still work. Ill try the build.prop additions and see where we get
jimsmith80
Android Expert
I pulled the ril related files from the warplte using the original metis tree as a reference.
junkie2100
Android Expert
that works, may not be able to use the stock libs though you know how zte is. and yes 3g/phone should work even without the lte card if its set to the right network mode and its already pre programmed in stock
it WILL always give the no sim error regardless though, so you have to ignore that and just try it
it WILL always give the no sim error regardless though, so you have to ignore that and just try it
if those libs dont work maybe he can try the ones this guy used on ZTE Nubia Z5s Mini
https://github.com/MoKee/android_vendor_nubia_nx403a
https://github.com/MoKee/android_device_nubia_nx403a
https://github.com/MoKee/android_kernel_nubia_nx403a
jimsmith80
Android Expert
I made the build.prop modifications, and still nothing. I'm going to play around with the libs some more and see where i get.
after you made changes to the prop and did a factory wipe, was it still asking for a SIM card ?
jimsmith80
Android Expert
No. Sorry for not mentioning that. That did get me over that hurdle. Do you think I should be including qcnvitems.jar qcrilhook.jar, and sptint.jar into the build? I've seen that done on several cm10 builds.
no i would try the libs from the ZTE Nubia (not all) just the RIL libs and binaries
I posted a link a few posts back
As you know, I did not use ZTE Libs for the Radiant, I used Samsung, but if Mokie was able to get the Nubia libs to work, you should too
warrior1988
Lurker
Zte radiant camera and when I speak in mic people cant hear me. This is kernel related as far as I can tell. What I would recommend doing is take the configuration file to build the cyanogenmod kernel for your device and in the kernel product copy files copying over the modules from the stock kernel source/ROM. Keep in mind this still may not fix these problems. Camera hardware is often broken on custom ROM's, and can be extremely difficult or near impossible to fix.
junkie2100
Android Expert
wait a minute... what is default network type 7?!? i could swear 8 was the proper setting for cdma lte. check what network mode youre in and not via the system menu that doesnt always work right, theres a hidden menu, you can get to it with a dial code but i dont remember it, i use lte onoff
https://play.google.com/store/apps/details?id=net.andirc.lteonfoff
says for thunderbolt but it works great on cm for the force, make sure its set to lte/cdma (auto)
in my experience even lte only wont work, and i think, cant be sure, but i think you have it set to lte/gsm which will give you no network
AH its global... k. that may or may not work though im not really sure, the phone isnt actually global the sim slot cant be used for gsm purposes, so its worth a shot trying to adjust it
https://play.google.com/store/apps/details?id=net.andirc.lteonfoff
says for thunderbolt but it works great on cm for the force, make sure its set to lte/cdma (auto)
in my experience even lte only wont work, and i think, cant be sure, but i think you have it set to lte/gsm which will give you no network
AH its global... k. that may or may not work though im not really sure, the phone isnt actually global the sim slot cant be used for gsm purposes, so its worth a shot trying to adjust it
jimsmith80
Android Expert
Ill check that out. I have a new build in progress right now. I could have just swapped the libs but i was feeling lucky
Network was set to 4 in the stock build.prop
Network was set to 4 in the stock build.prop
- Status