Database Users

[Q] network apn save

question: how to save network apn on meizu mx
details: meizu mx 032, using flyme 1.1.7(a9904)
with giffgaff sim
giffgaff sim recognised automatically, i.e. shows when i pull down main screen
however giffgaff doesn't show in network > apns
which show under 'apn access point' heading = o2 mobile web, o2 prepay, tesco.. and under 'mms' = o2 mms
the problem is that saving apn (existing of new) corrupts network/apns
tried:
1. with old flyme version (probably 1.1.4 or 1.1.5) with same problem
2. with flyme 1.1.7, if i just open existing apn, say tesco.. and only change the name to tesco2.. and click save.. and restart the android..... then it's all gone.. and problem crept
3. even after factory reset new apn addition, like for giffgaff.. fails. and then it's all gone
4. reset to default doesn't bring anything
5. and neither does restart/reboot
workaround: only factory reset works
debug:
1 wanted to find and edit config file where apn entry resides, but until now couldn't find the config file, as it must be somewhere in system partition as i can't access to it, even after enabling usb debugging, as these partitions aren't visible when i connect to computer... i can see data partition though
2. also disabled flyme sync, and google sync, to ensure that it's not syncing with my old copies of network.. as factory reset followed by sync(may be) caused same problem
3. later on will probably try with o2 sim
4. tried with android apps like 'giffgaff apn', 'apn manager, 'apn backup and restore', etc.. none work.. and these apps do say that this version of android doesn't allow apn 'saving'..or something like that

[Q] NJ4 WiFi Issues

I manually upgraded my i337 from NB1 (4.4.2) to NJ4 (4.4.4), and then I re-rooted it. While I noted minor differences between the versions (I now had the "Custom Unlocked" logo on the splash screen, for example, and the notification "shade" did not scroll off and on as quickly), the most problematic issue was WiFi connectivity, which caused me to reinstall NB1 (pending a solution).
With NB1, my WiFi worked as I thought it should. It would automatically re-connect to hot spots and, if there is a password, it would automatically handle it for those sites I had logged into previously. Thus, for example, my phone would automatically log into my home WiFi router as soon as I walked through the door.
It appears that NJ4 is broken. I have found that under NJ4, the WiFi will only *automatically* re-connect to the most recently-used hotspot (whether or not passworded). This is not affected by restarting either the phone or the router. Thus, if I connect to my home router, the phone will re-connect effortlessly PROVIDED I don't connect to any other hotspot. If I have connected to another hotspot, once I return home, I find that there is no longer an automatic connection (I receive a "WiFi Hotspots are Available" notification), and once I initiate the connection manually, I am asked for my password EVERY TIME. At least I know my home password; I don't know the passwords of the many other hotspots I have connected to.
The collected WiFi credentials are maintained in the file data/misc/wifi/wpa_supplicant.conf. I looked at that file to see whether the passwords had been deleted. No, they were all still there (albeit encrypted). Here is an entry like the one for my home router:
network={
ssid="SqueekyNet"
psk=[the encrypted p/w is located here]
key_mgmt=WPA-PSK
priority=657
frequency=2462
disabled=1
autojoin=1
usable_internet=0
skip_internet_check=0
}
Note the line that says "disabled". The system inserts this line once you log into a *different* hotspot. It does this for *every* entry, so the only entry without this line will be the one for the current hotspot (or for the most recent one, if you aren't logged in to any WiFi hotspot).
I have found that if I edit the wpa_supplicant.conf file on-the-fly ... changing "disabled=1" to "disabled=0", then my home WiFi is instantly recognized, and I am immediately logged in (the "forgotten" password isn't really forgotten). Further, if I then re-examine the wpa_supplicant.conf file, I will see that the "disabled" line has been deleted from the current hotspot, and will only be re-inserted once I log into a *different* hotspot. BTW, while I am using the home hotspot as a test, the same behavior applies to ANY hotspot. Thus, under 4.4.4, NO hotspot is logged into automatically (unless it is the most recent hotspot), and unless you are attempting to log into the most recent hotspot, you ALWAYS receive a request to enter the password for a protected hotspot (even though the password is actually still in the file). I use WiFi heavily, and this isn't viable for me.
The problem apparently isn't limited to the i337 (AT&T) build of NJ4. I noticed this discussion in the T-Mobile forum: https://support.t-mobile.com/thread/84926 (I tried to comment on it, but I can't register for the forum since I'm not a T-Mobile customer).
I am now comfortably back on NB1.
Does anyone have a solution for this?

UPDATE: I found that after I reinstalled 4.4.2 (NB1), using ODIN and then Titanium Backup, as soon as I activated WiFi, my device would strip all of the entries from wpa_supplicant.conf that contained a password (psk). I tried a number of different techniques to reload my original wpa_supplicant.conf file, and was never successful. All of the entries without a psk remained, however (there are hundreds).
I also found that after reinstalling NB1 (including the restore via Titanium Backup) once I re-entered the password for a particular WiFi hotspot, then the re-entered password would stay in the wpa_supplicant.conf file (and the phone would again login to WiFi automatically, without ever/always asking for a password re-prompt as was happening with 4.4.4 NJ4).
While I don't really know for sure, it is my guess that the psk entries were stripped from the wpa_supplicant.conf file by the Google server. Not sure why, but since I am able to totally restore the device with all of the pre-backup data files (including the original wpa_supplicant.conf file), this is my only explanation.
For me, NB1 works to remember passwords and log-in automatically to WiFi hotspots; 4.4.4 NJ4 does not.

[Q] Encryption on P7000 not working?

Hi,
I wanted to turn on the standard encryption on my P7000 (to gain access to corporate exchange server and sync) but I have discovered a bug:
- encryption starts, black screen with android logo (no animation) and nothing happens even after hours (replace the battery to reboot the phone necessary).
- after reboot the phone is not encrypted (but also not broken, so seems to start and runs in an error before messing up partitions)
- power is connected,battery at 100%
- latest OTA image from 20150617 from elephone was applied automatically (Android 5.0)
- after a missed try I rooted the phone and gave it another try (with same result)
So I installed touchdown for the moment (can also access via activesync) to have a workaround but I would like to see this issue fixed.
Any hints or tipps what I cound try to fix it myself, or do I need to wait until Elephone might fix it with one f the next OTAs?
Best,
Peter

not sure if it helps i have p7000
hello. i have two exchange services email accounts on mine. it is non rooted just stock updated to 52915
i download the latest exchange mail services for gmail. i can provide link to see if it helps but i have active syncing on both exchange e mail addresses.
sorry if im off topic

Hi,
I have the same exact problem on the P8000.
For P7000, there is a post on the elephone forum, but no solution...
http://bbs.elephone.hk/thread-5858-1-1.html#.VckPfZM-IrQ

Same issue for me. Need to encrypt my phone. Even with the latest stock rom the encryption process is not working.
Tried with adb-logcat and found that there was an issue with the /data : "unmounting /data failed: Device or resource busy"

Looks like there is a fix for encryption on P7000:
http://bbs.elephone.hk/thread-7731-1-1.html#.VfbcMLM-I8N

Cannot Access WLAN via a DHCP connection , only by using a Static IP

Hey everyone, long time reader- first time poster- hopefully someone can help me!
really frustrating issue, after over 2 years of near flawless use with my n9005 yesterday i noticed i was no longer connected to my saved home wlan, every time i tried i would receive the message: AP currently not in use......, i proceeded to restart phone/router, forget network- and re enter details without any success. after googling the issue i tried all the basic suggested fixes, toggling various wifi settings, toggling date and time, toggling wifi power saving mode via *#0011# all without avail. I researched further and attempted to access the dhcp_list to delete it via root explorer (also viewed the permissions using x-plore and its all ticked for read and write accordingly) etc, however i was never able to do this- always being told i didn't have the file permissions, same story when trying to use terminal with the input: rm /data/misc/dhcp/*. I have checked and do have root access and always granted access before attempting these through the configs of the file explorer and super user or by typing su first in the terminal. Whenever i enter a static IP it connects and works immediately, however when i was out the house yesterday i noticed it was doing the same issue with 2 other saved WLAN networks which being public i cannot use a static ip/ and ultimately cannot join/use. So last night i factory reset my phone/cleared cache this did not work as im still receiving the same Obtaining IP Address loop and AP not in use error message and once again the Static IP work round is my only way to gain access. Im now at a loss what to do next, considering to flash a different ROM/Modem/Boot Loader but dont know if this would be any help?. My system details are listed below any help would be much appreciated
BOOTLOADER: N9005XXUGBOA5
RADIO: N9005XXUGBOA1
home wifi router is the, EE brightbox

Solved installed new ROM all good!

Success: Bypassing *samsung account* lock after factory reset

Hi all, before I forget about this and move on, I just thought I'd share my experience, as most "fixes" for the Factory Reset Protection that I could find online related to google account-based lockout, rather than samsung account-based lockout. The lockout in question says something like "This device is locked because of an abnormal factory reset. Sign in to the Samsung account that you have already signed in to on this device to confirm it belongs to you."
Apologies for the vagueness of the final step (5) below - I wasn't setting out to document what I did, so wasn't taking notes. I am in a rush now but when I have time I'll try to be more specific. Perhaps someone else may jump in with their detailed experience in the meanwhile!
Background: My workplace passed on to me a used Galaxy E7 (specifically SM-700H). Not knowing about the infuriating "Factory Reset Protection" protection, I simply wiped it via the stock bootloader the moment I got it. Then I discovered it was now locked - and that the previous user/employee had walked without sharing the samsung account and password used. All purchase info etc lost in the mists of office disorganization so no chance of an unlock via Samsung, I assumed .
Anyway, so I found the installed 5.1.1 rom (specifically, LMY47X.E700HXXU1BPA1) was resistant to tricks I read elsewhere designed to give access to the phones settings, so I downgraded to an older kitkat rom, then found I could access settings from that, as this hole presumably hadn't been patched. The following worked for me:
1. Download ODIN (I used ver 3.11)
2. Download a stock kitkat rom to use to downgrade to. I used E700HXXU1AOE4 which is from Nepal I think, but the region doesn't seem to matter. (Most free firmware download pages are deliberately crippled, I found they are super slow and always timed out before completing; but this free page has fast downloads: http://www.theandroidsoul.com/galaxy-e7-stock-firmware/#jump-model-no-sm-e700h )
3. Flash that newly downloaded firmware using ODIN (you can use the instructions here: "How to Install/Update Official Firmware on Galaxy E7 SM-E700H Manually through Odin:" http://www.androidofficer.com/2016/01/e700hxxu1bpa1-android-511-xxu1bpa1.html )
4. Boot up, connect to the internet via wifi. I signed into my google account at some point, but not sure if that was necessary. That step comes before the Samsung Account lockout screen presents itself.
5. (SORRY this is a little vague, will come back to it later, but trust me, this worked for me!) Click about through the several available pages and settings which appear before the Samsung Account lock page until you find any piece of disclaimer/info text, I was looking for some which included a URL, but it turned out I think that wasn't even required. Highlight some text, touch it again, and look for a search/globe/internet icon. Amazingly, that will launch the phone's search function via google now/its internal browser.
6. At that point, you're essentially outside of the "lockdown" intro screens. What i did was put the word "settings" into the google now search box, then at the bottom of the results page, slid the category slider from the default "web" results source, past "apps" and "images" etc across to "phone", which delivered a link to the phone's actual settings.
7. At that point, you can drill down to "Security" then deactivate the "Reactivation lock" setting, enable developer mode, unsigned apps, etc - whatever you feel needs doing - then restart the phone in the normal manner. The setup screen is back after restart, but without the lockout. Voila, a working phone.
Notes: So no need to download sideload any external apks. Also a gotcha - I subsequently created a new random Samsung Account to sign into, because i was afraid the unknown samsung account lockout curse would return - then i noticed that by signing in to that, it had once again ticked the "Reactivation lock" setting - watch out for that!