ZTE Open C only scans 11 Wi-Fi channels (not 13 or 14)

My Wi-Fi access point (a home router) operates on channel 13.
ZTE Open C does not detect this network unless I set the channel to 11 or less.
For my home network there's an easy workaround (though I may lose some speed) but I'm worried if I'll be able to scan other public networks.
Is it possible to alter the phone config so it will scan for all available networks?

Hi choco-banana,
The supported network types are:
WEP
WPA-PSK
WPA-EAP
The only - non-overlapping 2.5GHz wireless network channels in the U.S. are 1, 6 and 11.
"In the USA, 802.11 operation in the channels 12 and 13 are actually allowed under low powered conditions. The 2.4 GHz Part 15 band in the US allows spread-spectrum operation as long as the 50-dB bandwidth of the signal is within the range of 2,400–2,483.5 MHz[11] which wholly encompasses both channels 12 and 13."[http://en.wikipedia.org/wiki/List_of_WLAN_channels]
If there are networks that are remembered, you can manage them the Settings options. However, if there is a limit to the number in this list what is the maximum you are seeing? There is a scan again option for detecting new networks. If you toggle this, they should be detected.
I wonder if its below 2.5 it is not being detected? What kind of network is the home network? Password protected? [WEP, WPA-PSK,WPA-EAP?]

Similar Messages

  • Quicken 07 always crashes on open. Only in one logon user not others?

    Have a macbook pro. I have been using Quicken '05. Decided to try Q Essentials. Hated it. Erased those files and decided to back to Q'05. Wierd thing is that quicken '05 now fails on openning every time. Used another logon on my laptop and quicken '05 works. Go back to my logon and Q'05 doesn't work. Repaired all permissions. Removed my preferences folder and rebooted. Q'05 still won't work. Decided to download and try Q'07 - that crashes too. However, the new Q'07 does work on another logon user (just like Q'05). Anybody have any thoughts about what's going on? BTW, all other programs work fine. I feel like Intuit is torturing my for asking for my money back on Q.Essentials...

    BTW, I also booted in safe mode. Q'07 and Q'05 still crash under my logon. Stymied...

  • When is Firefox OS v1.2 and v1.3 released to ZTE open?

    Currently the ZTE open is delivered with Firefox OS v1.0.
    Firefox OS v1.1 is released and avaiable for the ZTE open. It can be installed.
    Firefox OS v1.2 is only available as Beta-Release for the ZTE open.
    When is Firefox OS v1.2 finally released for the ZTE open?
    Some monile phone producers do not facilitate each new release to their customers.
    Firefox OS v1.3 is ready and released by Mozilla.
    When will Firefox OS v1.3 be available for the ZTe open?

    Hi schaefi,
    I understand that you would like to know when the update for the commercial version of ZTE Open will be released to the public.
    The OEMs (Original Equipment Manufacturers) are the ones responsible for testing and releasing updates to the users, for each specific device. Unfortunately, we at Mozilla do not have any information of when they will release those updates.
    We apologize for the misinformation given earlier, regarding an 1.2 update being available on April 28th. For specific details regarding the updates, you may contact the manufacturer directly.
    Thank you for your understanding.
    - Ralph

  • ZTE Open C Accelerometer only works when phone is upside down?

    I just received my new ZTE Open C and when I tried a few games, like Sketchbook Squad, for example, I found that the accelerometer control ONLY works if I hold my phone upside down.
    Does anyone know if this may be an OS related issue relating to calibration, or maybe it's a defective device?

    Hi bugninja,
    I also tried SketchBook Squad and it's working correctly on my device.
    Can you please list *all* the apps that you are having problems with? Please specify which of those apps the accelerometer do not seem to work at all, and which of those apps the accelerometer only works when the phone is upside down. This information will help greatly in investigating this issue.
    Please also let us know the Build ID of your ZTE Open C device. To find the Build ID, go into '''Settings''' > '''Device Information''' > '''More Information'''.
    Thanks,
    - Ralph

  • Use volume button on ZTE Open only for music and not for ringtone/sms/alarm

    I wounder if its possible to override the volume button on the device so it dosent change the ringtone and sms volume? I had this feature on iOS where I can set the ringtone and notification volume then a switch that sad "Change with buttons" = true || false.
    My Android device (Padfone2) did not have this feature and I end up missing calls and sms because you turn the volume up and down when you browse the web, listening to music ect.
    Does someone know if this is possible on my ZTE Open with FFOS 1.1?

    To further explain where the volume controls are going,
    'There's multiple different settings for audio volume:
    * audio.volume.content: Affects the "content" and "normal" audio channels. It's an integer between 0 and 15 where 0 means muted (but not paused).
    * audio.volume.notification: Affects the "notification" and "ringer" channels. It's an integer between 0 and 15.
    * audio.volume.alarm: Affects the "alarm" channel. It's an integer between 0 and 15.
    * audio.volume.telephony: Affects the "telephony" channel. It's an integer between 0 and 5.
    * audio.volume.bt_sco: Volume when bluetooth headset is plugged in. It's an integer between 0 and 15.'
    Take from https://wiki.mozilla.org/WebAPI/AudioChannels
    So as per stated before, the Ringer & Notification has a different setting than the Alarm, as well as the Telephony voice and the content as well as blue tooth volume.
    I agree that it can get rather confusing with which volume is getting affected when. In general if the sound is currently going off, then most likely that is what the volume is controlling. We should probably file a bug on somehow getting the volume controlling less confusing.

  • I can only sync once a day with Hotmail on ZTE Open phone

    1. Each morning when I fire up my ZTE Open phone I can sync with my Hotmail account. Anytime after that it simply will NOT sync again for the rest of the day
    2. I have yet to actually read an email on my Firefox ZTE Open phone, once I choose any email it appears to start to open it up but I then just get the spinning icon, I've let it spin for 1 hour and still nothing appears.

    Thanks for response, but this is an issue with the app that is on the ZTE Open phone when I got it. So when I mention sync, I'm talking about the app syncing with Hotmail or Gmail for that matter. Has anyone managed to get this Email app working with their email account?

  • Update problems, no space left on device (ZTE Open)

    I just received a ZTE Open device in the mail today, and after playing around with it a bit, I noticed that every time I tried to check for system updates, it would show me one 13.xx MB update, which I downloaded, apparently applied, and the phone seemed to restart itself, but then I would be shown the same (??) update available. The phone is without a SIM card, just playing with it connected via Wifi, with the 4GB microSD card installed. Then, this evening, I got an error message, which apparently was recorded on the SD card, a file called recovery.log (contents follow):
    <pre><nowiki>Starting recovery on Fri Aug 23 07:29:21 2013
    framebuffer: fd 4 (320 x 480)
    recovery filesystem table
    =========================
    0 /tmp ramdisk (null) (null) 0
    1 /boot mtd boot (null) 0
    2 /amss mtd amss (null) 0
    3 /appsbl mtd appsbl (null) 0
    4 /mibib mtd mibib (null) 0
    5 /qcsbl mtd qcsbl (null) 0
    6 /oemsbl1 mtd oemsbl1 (null) 0
    7 /oemsbl2 mtd oemsbl2 (null) 0
    8 /splash mtd splash (null) 0
    9 /cache yaffs2 cache (null) 0
    10 /data yaffs2 userdata (null) 0
    11 /misc mtd misc (null) 0
    12 /recovery mtd recovery (null) 0
    13 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
    14 /system yaffs2 system (null) 0
    I:Got arguments from /cache/recovery/command
    mtd: successfully wrote block at 0
    I:Set boot command "boot-recovery"
    Command: "/sbin/recovery"
    ro.secure=1
    ro.allow.mock.location=0
    ro.debuggable=0
    ro.build.id=IMM76D
    ro.build.display.id=OPEN_US_DEV_FFOS_V1.0.0B01
    ro.build.version.incremental=eng..20130724.030603
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.4
    ro.build.sw_internal_version=US_DEV_FFOS_V1.0.0B01
    ro.build.baseband_version=P752D04B02
    ro.build.firmware_revision=V1.01.00.01.019.144
    ro.build.date=2013年 07月 24日 星期三 03:06:47 CST
    ro.build.date.utc=1374606407
    ro.build.type=user
    ro.build.user=
    ro.build.host=ThinkCentre2-XXXX
    ro.build.tags=test-keys
    ro.product.model=roamer2
    ro.product.external_model=ZTE OPEN
    ro.product.brand=ZTE
    ro.product.name=roamer2
    ro.product.device=roamer2
    ro.product.board=roamer2
    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=msm7627a
    ro.build.product=roamer2
    ro.build.description=roamer2-user 4.0.4 IMM76D eng..20130724.030603 test-keys
    ro.build.fingerprint=ZTE/roamer2/roamer2:4.0.4/IMM76D/eng..20130724.030603:user/test-keys
    ro.build.characteristics=default
    rild.libpath=/system/lib/libril-qc-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
    debug.sf.hw=1
    debug.composition.7x27A.type=mdp
    debug.composition.7x25A.type=mdp
    dalvik.vm.heapsize=128m
    persist.cne.UseCne=none
    persist.cne.bat.range.low.med=30
    persist.cne.bat.range.med.high=60
    persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
    persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
    persist.cne.bwbased.rat.sel=false
    persist.cne.snsr.based.rat.mgt=false
    persist.cne.bat.based.rat.mgt=false
    persist.cne.rat.acq.time.out=30000
    persist.cne.rat.acq.retry.tout=0
    persist.cne.fmc.mode=false
    persist.cne.fmc.init.time.out=30
    persist.cne.fmc.comm.time.out=130
    persist.cne.fmc.retry=false
    media.stagefright.enable-player=true
    media.stagefright.enable-meta=false
    media.stagefright.enable-scan=true
    media.stagefright.enable-http=true
    media.stagefright.enable-fma2dp=true
    media.stagefright.enable-aac=true
    media.stagefright.enable-qcp=true
    ro.opengles.version=131072
    ro.use_data_netmgrd=true
    persist.data.ds_fmc_app.mode=0
    persist.ims.regmanager.mode=0
    ro.bluetooth.request.master=true
    ro.qualcomm.bluetooth.sap=false
    ro.bluetooth.remote.autoconnect=true
    persist.sys.strictmode.visual=false
    persist.omh.enabled=1
    ro.config.ehrpd=true
    ro.qualcomm.cabl=1
    ro.fm.analogpath.supported=true
    ro.fm.transmitter=false
    ro.fm.mulinst.recording.support=false
    ro.hw_plat=7x27a
    ro.emmc.sdcard.partition=18
    ro.screen.layout=normal
    debug.enabletr=false
    debug.camcorder.disablemeta=0
    persist.fuse_sdcard=false
    debug.camera.landscape=true
    ro.max.fling_velocity=4000
    hwui.render_dirty_regions=false
    httplive.enable.discontinuity=true
    power.webview.DM=false
    dalvik.vm.heapstartsize=5m
    dalvik.vm.heapgrowthlimit=36m
    org.bluez.device.conn.type=boolean
    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.config.alarm_alert=Alarm_Classic.ogg
    ro.vendor.extension_library=/system/lib/libqc-opt.so
    ro.display.colorfill=1
    ro.moz.ril.emergency_by_default=true
    ro.moz.omx.hw.max_width=640
    ro.moz.omx.hw.max_height=480
    ro.moz.cam.0.sensor_offset=270
    ro.moz.ril.simstate_extra_field=true
    persist.sys.ztelog.enable=1
    persist.radio.add_power_save=1
    ro.sensor.arch.type=new
    net.bt.name=Android
    net.change=net.bt.name
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.factorytest=0
    ro.serialno=ROAMER2
    ro.bootmode=unknown
    ro.baseband=msm
    ro.carrier=unknown
    ro.bootloader=unknown
    ro.hardware=roamer2
    ro.revision=0
    ro.emmc=0
    init.svc.recovery=running
    E:Error in /cache/recovery/log
    (No space left on device)
    E:Error in /cache/recovery/last_log
    (No space left on device)
    mtd: successfully wrote block at 0
    I:Set boot command ""
    E:Error in /cache/recovery/log
    (No space left on device)
    E:Error in /cache/recovery/last_log
    (No space left on device)</nowiki></pre>
    The SD card also contains a zip file in updates/fota/update.zip, which in turn contains patch/system/P752D04_DEV_US_20130726.zip, which contains: amss.mbn (about 20 meg) and boot.img (about 4 meg).

    Just jumping in here, I received mine on the 23rd and I am also seeing the same problem, but the logs are a bit different. Although, I am running OPEN_US_DEV_FFOS_V1.0.0'''B02'''. While the recovery log states B01.
    I'll toss my log up as well so trends can be examined.
    Starting recovery on Sun Aug 25 07:04:10 2013
    framebuffer: fd 4 (320 x 480)
    recovery filesystem table
    =========================
    0 /tmp ramdisk (null) (null) 0
    1 /boot mtd boot (null) 0
    2 /amss mtd amss (null) 0
    3 /appsbl mtd appsbl (null) 0
    4 /mibib mtd mibib (null) 0
    5 /qcsbl mtd qcsbl (null) 0
    6 /oemsbl1 mtd oemsbl1 (null) 0
    7 /oemsbl2 mtd oemsbl2 (null) 0
    8 /splash mtd splash (null) 0
    9 /cache yaffs2 cache (null) 0
    10 /data yaffs2 userdata (null) 0
    11 /misc mtd misc (null) 0
    12 /recovery mtd recovery (null) 0
    13 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
    14 /system yaffs2 system (null) 0
    I:Got arguments from /cache/recovery/command
    mtd: successfully wrote block at 0
    I:Set boot command "boot-recovery"
    Command: "/sbin/recovery" "--update_package=/sdcard/updates/fota/update.zip"
    ro.secure=1
    ro.allow.mock.location=0
    ro.debuggable=0
    ro.build.id=IMM76D
    ro.build.display.id=OPEN_US_DEV_FFOS_V1.0.0B01
    ro.build.version.incremental=eng..20130724.030603
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.4
    ro.build.sw_internal_version=US_DEV_FFOS_V1.0.0B01
    ro.build.baseband_version=P752D04B02
    ro.build.firmware_revision=V1.01.00.01.019.144
    ro.build.date=2013年 07月 24日 星期三 03:06:47 CST
    ro.build.date.utc=1374606407
    ro.build.type=user
    ro.build.user=
    ro.build.host=ThinkCentre2-XXXX
    ro.build.tags=test-keys
    ro.product.model=roamer2
    ro.product.external_model=ZTE OPEN
    ro.product.brand=ZTE
    ro.product.name=roamer2
    ro.product.device=roamer2
    ro.product.board=roamer2
    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=msm7627a
    ro.build.product=roamer2
    ro.build.description=roamer2-user 4.0.4 IMM76D eng..20130724.030603 test-keys
    ro.build.fingerprint=ZTE/roamer2/roamer2:4.0.4/IMM76D/eng..20130724.030603:user/test-keys
    ro.build.characteristics=default
    rild.libpath=/system/lib/libril-qc-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
    debug.sf.hw=1
    debug.composition.7x27A.type=mdp
    debug.composition.7x25A.type=mdp
    dalvik.vm.heapsize=128m
    persist.cne.UseCne=none
    persist.cne.bat.range.low.med=30
    persist.cne.bat.range.med.high=60
    persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
    persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
    persist.cne.bwbased.rat.sel=false
    persist.cne.snsr.based.rat.mgt=false
    persist.cne.bat.based.rat.mgt=false
    persist.cne.rat.acq.time.out=30000
    persist.cne.rat.acq.retry.tout=0
    persist.cne.fmc.mode=false
    persist.cne.fmc.init.time.out=30
    persist.cne.fmc.comm.time.out=130
    persist.cne.fmc.retry=false
    media.stagefright.enable-player=true
    media.stagefright.enable-meta=false
    media.stagefright.enable-scan=true
    media.stagefright.enable-http=true
    media.stagefright.enable-fma2dp=true
    media.stagefright.enable-aac=true
    media.stagefright.enable-qcp=true
    ro.opengles.version=131072
    ro.use_data_netmgrd=true
    persist.data.ds_fmc_app.mode=0
    persist.ims.regmanager.mode=0
    ro.bluetooth.request.master=true
    ro.qualcomm.bluetooth.sap=false
    ro.bluetooth.remote.autoconnect=true
    persist.sys.strictmode.visual=false
    persist.omh.enabled=1
    ro.config.ehrpd=true
    ro.qualcomm.cabl=1
    ro.fm.analogpath.supported=true
    ro.fm.transmitter=false
    ro.fm.mulinst.recording.support=false
    ro.hw_plat=7x27a
    ro.emmc.sdcard.partition=18
    ro.screen.layout=normal
    debug.enabletr=false
    debug.camcorder.disablemeta=0
    persist.fuse_sdcard=false
    debug.camera.landscape=true
    ro.max.fling_velocity=4000
    hwui.render_dirty_regions=false
    httplive.enable.discontinuity=true
    power.webview.DM=false
    dalvik.vm.heapstartsize=5m
    dalvik.vm.heapgrowthlimit=36m
    org.bluez.device.conn.type=boolean
    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.config.alarm_alert=Alarm_Classic.ogg
    ro.vendor.extension_library=/system/lib/libqc-opt.so
    ro.display.colorfill=1
    ro.moz.ril.emergency_by_default=true
    ro.moz.omx.hw.max_width=640
    ro.moz.omx.hw.max_height=480
    ro.moz.cam.0.sensor_offset=270
    ro.moz.ril.simstate_extra_field=true
    persist.sys.ztelog.enable=1
    persist.radio.add_power_save=1
    ro.sensor.arch.type=new
    net.bt.name=Android
    net.change=net.bt.name
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.factorytest=0
    ro.serialno=ROAMER2
    ro.bootmode=unknown
    ro.baseband=msm
    ro.carrier=unknown
    ro.bootloader=unknown
    ro.hardware=roamer2
    ro.revision=0
    ro.emmc=0
    init.svc.recovery=running
    Finding update package...
    I:Update location: /sdcard/updates/fota/update.zip
    Opening update package...
    I:1 key(s) loaded from /res/keys
    Verifying update package...
    I:comment is 1746 bytes; signature 1728 bytes from end
    I:whole-file signature verified against key 0
    I:verify_file returned 0
    Installing update...
    try_update_binary(path(/sdcard/updates/fota/update.zip))
    radio.diff not found
    Verifying current system...Failed to mount /dev/block/mtdblock4 on /cache: Device or resource busy
    mtd mount of cache failed: Device or resource busy
    51191808 bytes free on /cache (5714 needed)
    applying patch to /system/build.prop
    "/system/build.prop" is already target; no patch needed
    Removing unneeded files...
    Patching system files...
    Symlinks and permissions...
    script result was [/system]

  • My sim card is no longer recognized by the ZTE Open sold on EBay

    After 6 month of happy usage of my ZTE Open, manually upgraded to Firefos OS 1.3.
    My phone suddenly does not recognize my sim card any more.
    I performed some tests with other phones, other operators, and other sim cards that lead me to tell that the problem comes from the phone.
    There was no special event that can explain this problem (no fall, no update, no water...).
    I tried to retart the phone, to reset it. No way the sim card is recognized.
    I seem to be able to call and receive phone calls, but no sms and no data.
    Can you please help ?

    Same thing with me, but SMS and data seem to work fine. Only seems to affect Usage app on my phone (ZTE Open C).

  • How to update apps in a ZTE Open (with FFOS 2.0 custom build)?

    I have a ZTE Open I regularly update trough custom builds. In particular, I updated it to the 2.0 version by:
    BRANCH=v2.0 VARIANT=user ./config.sh inari
    BRANCH=v2.0 VARIANT=user ./build.sh
    The operation has apparently been successful, and by the test apps being missing I guess that I really built and flashed the user variant.
    Now, I do not expect system updates to work, as I heard that the inari update channel has been shut down.
    Though, I would expect it to at least automatically update the third-part apps from the Market store. This does not seem to happen: I have outdated apps (Loqui IM v3.1, in particular) but the "Check now" button from the Settings has no effect (it says "Checking for updates", but nothing else happens).
    Moreover, I do not remember of having ever received an update with previous build, so I guess it may be not a problem with this particular build.
    Is there something I can do about it?

    Are other ZTE Open users with a custom build experiencing the same problem? Do you receive any app update at all?
    I can't tell whether there is a problem in my build, in some setting or in the device.

  • PP CS5, importing mp4's I only get 1 audio channel instead of all 4...?

    PC,
    PP CS5, importing mp4's I only get 1 audio channel instead of all 4...? I put the clips in Vegas & all 4 channels appear. What can I do? Going insane!!!
    Steve

    It's pretty simple... when you know how
    Get ffmbc - FFMedia Broadcast .   This is a customized build of FFmpeg that is more geared toward   broadcast formats and applications. The latest "official" release (0.5)   will work.
    Open the archive and find the "ffmbc.exe" file in  the "bin" folder. Drop it into the folder with the MP4s--or if you know  how to set up a custom path, you could do that too.
    Create a new  text file called something like "mp42mxf-4mono.bat" making sure that you can  see file extensions; you need to have the .BAT extension. Make this file  in the same folder as the MP4s and FFmbc.
    Paste the following into the batch file:@ECHO OFF
    for %%a in (*.mp4) do ffmbc -i "%%a" -vcodec copy -acodec pcm_s16le -f mxf -y "%%~na".mxf -acodec pcm_s16le -newaudio -acodec pcm_s16le -newaudio -acodec pcm_s16le -newaudio
    Save it--again making sure it has a .BAT  extension--and then double-click it to run it. It will rewrap all of the  MP4s as MXF files that will import into Premiere. It will also retain the original four mono tracks as four mono tracks in the destination MXF.
    That's all there is to it. Save that script, and you can recycle it whenever you get a batch of these types of problematic files in. Note that it's a completely lossless rewrapping, and should only take a few moments (or minutes, if you have a lot of footage, I suppose). Let me know how that goes.

  • How to install Skype/viber for video calling on ZTE open C firefoxOS mobile

    I have problem in installing Skype/viber video calling app on my ZTE open C
    Firefox OS mobile every time I try it directs me to google play store which identify only
    Android OS

    Unfortunately, Skype or Viber is not available for Firefox OS at this moment. There are alternative chat apps that are available in the Marketplace however, I don't think it supports Skype or Viber at this moment.

  • ZTE Open C reboots during calls

    The phone reboots during calls. OS version 1.3, latest according to ZTE.
    Thing is, only when it is set to use 3G. But if I set to 2G the audio is absolutely terrible.
    Both when using 2G and 3G sometimes the calls get cut-off on the receiver phone. I can hear the other person talking but the other person doesn't hear anything. This is another issue.
    What can I do? The phone was bought from Ebay on September 2014.
    Problem didn't start now, ZTE Ebay support said the issue was a SIM one. I recently changed to 3G because the noises in 2G are almost unbearable.

    ''Ralph Daub [[#answer-713346|said]]''
    <blockquote>
    Hi Falconet,
    I understand you are experiencing rebooting and call quality issues on your ZTE Open C device.
    Since ZTE is responsible for the Firefox OS build specific to your device, I would suggest following their advice.
    You may be able to request a new SIM card for your device by contacting your carrier support.
    I hope this resolves your issue. Please let us know if you have any other questions about your Firefox OS device.
    Thanks,
    - Ralph
    </blockquote>
    Hi,
    What ZTE meant was changing carriers not just sim card. I can't do that for another 1.5 years. The reason they said is because the phone seemed fine for a while when using another carrier. Sadly, the SIM is fine since another SIM card from the same carrier does the same. Both are working fine on Android Phones.

  • Why does my ZTE open c Firefox OS smart phone forget the wlan settings and does not ring the alarm?

    Sometimes it is even enough to go outside to the waste bin to let my smartphone forget the settings for the wireless lan. When I return I have to enter the - not so short - code from my wlan router again. After that the internet connection is running as it should.
    Additionally the alarm clock does not work, I can set alarms as I like, setting the volume to the max and activate also the vibration alarm but nothing happens when the preset time is arrived, even when the alarm clock is shown on the screen the whole time. Is my phone broken? Or is it a bug in my Firefox OS installation?
    Where does Firefox OS store these values for wlan connection and alarm times? Is there an internal database that is maybe corrupted?

    Hi Markus,
    I understand that you're having issues with the Wi-Fi connection and the alarm clock in your ZTE Open C device.
    The alarm clock issue appears to be similar to what has been reported by other users and is being tracked on [https://bugzilla.mozilla.org/show_bug.cgi?id=1052245 bug 1052245].
    Do you have more information regarding the alarm clock issues that you encounter? This may be very helpful to our engineering teams investigating. Please be aware that ZTE is the manufacturer of your device, and only they are able to release an update.
    The wifi issue may be related to [https://bugzilla.mozilla.org/show_bug.cgi?id=923324 bug 923324].
    Please reply to this message with the following information:
    * What is the OS version and Build ID found in the Device Information page? Please visit [https://support.mozilla.org/en-US/kb/how-do-i-find-what-version-firefox-os-i-have this link] if you need help finding the Build ID of your phone.
    * Please provide the exact steps to reproduce the issue you are encountering.
    * How often do you encounter this issue?
    Please be sure to include as much detail as possible, including any websites that may exhibit this issue, and any error messages that you may be receiving, exactly as they appear. This will ensure that we have all the necessary information to investigate this behavior.
    - Ralph

  • How to install Firefox OS on ZTE Open C?

    I've purchased ZTE Open C on Ebay, and it has arrived today, but it's got Android OS instead of Firefox one - how can I install FF OS on it?
    Another thing is that in settings it says the model of my phone is Kis 3 and not Open C - is this correct?
    Thanks for any help.

    Hi bazujewicz,
    It seems that the Ebay seller may have sent you the wrong item. You should contact the seller to inquire about an exchange to the correct cell phone device.
    This link shows how to manually update and flash a ZTE Open C:
    * [https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#.22Manual.22_updates Manually Update a ZTE Open C]
    However - since your phone may be a different model, it could end up bricking and voiding warranty on your device.
    Please contact the seller and the appropriate Ebay channels for further support.
    - Ralph

  • MS Access database opens read only

    An Access application with linked databases opens read only, but sometimes is editable. The system was developed in Access 10 on a Win 7 machine and migrated to a standalone laptop running Win 8 and Office 365.
    The Access 10 has no problem in operating the application. The Win 8 laptop randomly opens the application read only. I have reviewed Trust settings and there is no difference between the different laptops and systems. 
    Is this a common problem? Is it associated with Win 8? Is it associated with Access form Office 365? The application is crucial to the business and we are getting way behind because we don't have a reliable or useful system. Last year the same application
    ran satisfactorily on Win 7 and Access 10.
    I would welcome some thoughts leading too a solution.

    Hi,
    Did you get the error message like "You are trying to open a read-only database". If yes, this issue may be due to the permission of the Access database. If we migrate the Access database from Access 2010 to Access 2013, the user/account's permission
    may be changed with different Windows operation system. We need the full control permission of the Access database. To workaround this issue, follow these steps:     
    On the desktop, double-click My Computer.
    Locate the Microsoft Access database that you moved.
    Right-click the database name, and then click Properties.
    In the Properties dialog box, clear the Read-only check box under
    Attributes.
    Click OK to apply the change.
    Open your database in Access.
    Please note: Make sure the user has full control of the root folder.
    If no, please tell us the whole error message, we'd like to do further troubleshooting.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

Maybe you are looking for