So. I've usually seen not equal as =/=, so you're saying in theory DevEd mods (Which don't have a Architecture / Chipset requirement) could potentially work on our now Dev mode N900V's? Not that I looked much into it, or what that may even entail as a year ago a lot of the hacking seemed to gear towards the DevEd. Just curious.
in the C language - the thing the Android kernel and most of the native libraries are written in:
Code:
a = b; /* assignment. set the value of a to be the contents of b */
if (a == b) dothis(); /* test for equality */
if (a != b) dothat(); /* test for inequality */
But what I was saying is that bootloader unlocked phones are
functionally identical to Developer Edition phones.
And as I clearly missed the previous discussion on re-flashing I had some troubles with my device being able to transfer files to the SD using TWRP, so I personally had to re-flash stock, boot it, then transfer files (As I didn't have a reader handy), as I had wiped the ROM in hopes to fully clean flash CM13. But I had forgot to add GApps to my SD.
. You could put the SDcard in a PC that has a media reader slot. -OR-
. An IOGear USB 3.0 SDcard adapter key/stick is pretty cheap. (USB 2.0 even cheaper.) -OR-
. TWRP (not the SafeStrap version) fully supports OTG devices and can flash/backup from/to an OTG USB storage device. A OTG cable is even cheaper than the USB SDcard adapter stick. The most expensive item is going to be a big uSD card, say 32 GB. You are going to want that; TWRP backups and Note 3 ROMs are big - 3-8 GB.
reflashing back to stock seems like the long road to doing things.
That being said, ODIN'ing back to stock I did lose both root and DevEd, unlike
@RaaidR
What happened to RaaidR (as reported) seems to be logically impossible. The DevEd signature modification occurs
in the middle of the aboot partition (not at the end!). The only explanation for his result is either a miracle from the Pope, or more likely the flash never happened.
The DevEd owners had no "unlocking" mechanism available to them. If they overflashed their bootloaders, they instantly and semi-permanently converted their devices to retail. So if you don't want to lose your unlocked bootloader
don't flash bootloader firmware!
though perhaps Jasmine loads a customized "stock"?
That's exactly what it does. For Retail/Locked phones it never touches the stock boot partition. (kernel+devicetree+ramdisk). DevEd devices can use a modified boot partition though, and I suppose that's what is done in the multiboot versions of Jasmine, maybe even in the DevEd version.
Dunno. Honestly didn't even try Jasmine before going balls deep into CM13, as I loved the look of it on a friends device. So far still no woes to report. Except my poor device's internal GPS I think is dead all together. Won't register on stock or any custom. I don't think service is needed for GPS to be enabled? My phone's currently Wifi only.
I would read up a little on GPS. By itself, it typically works very poorly indoors, if at all. If aGPS (Assisted GPS) services are not available, a
perfectly functioning GPS receiver can
take up to 15 minutes to get it's first fix. That's because it takes that long to download the almanac and ephemeris data from the satellites, and it cant do that until it has "found" the satellites by searching through frequency offset space and coding space. Indoors, that problem is even worse because the signals are quite weak, so the problem of "finding" the satellites gets even worse. (But note: that is exactly how stand-alone GPS was designed to work).
I just put my (rooted-stock) Note 3 in Airplane Mode, and then turned WiFi back on (simulate your situation). It seems to be able to download aGPS data over WiFi only. Hopefully your will as well.
Using the "GPS Status & Toolbox" app (MobiWIA - EclipSim) while connected to your WiFi, do this:
Enable
(touch screen) -> Menu -> Settings -> Display & Tools -> Show time to GPS fix
Enable
(touch screen) -> Menu -> Settings -> Background behavior -> Use GPS when screen is off
Then
(touch screen) -> Menu -> Manage A-GPS state -> RESET
you should see two Toast messages appear on your screen, one after the other:
Internal GPS state cleared
GPS Assistance data downloaded
Next ...
Take your phone outside where you are standing under an unobstructed sky
and wait. Keep touching the screen to keep it awake. And wait.
Do you see any satellites appear, even if there is no fix yet? If you loiter out there for 10-15 minutes do you get a GPS fix?
Since you are using the device without cell service, if you took the device someplace that is also without WiFi (for instance a car), it could literally take 10-15 minutes to get a first GPS fix. (Usually it will be faster if you download aGPS data - almanac & ephemeris before you leave your WiFi connected goodness. The ephemeris data will stay valid for an hour or so.).
After that first fix a GPS track-recording app meant for off-network usage (hiking or geocacheing apps) will have no problems maintaining a GPS fix,
so long as they continue to request GPS updates. You could give the "GPS Essentials" app a try for this - in track recording mode it is constantly asking for GPS position. It can give you a "live map" view using offline maps but I don't believe turn-by-turn navigation.
===>>
Don't use Google Maps for GPS testing either on-network or off. (even if you have downloaded an offline map cache). It is known to act in a bizarre fashion on some CM13 builds. This is probably because it switches back and forth between different LocationServices() data sources, and in the time intervals that GPS requests are not being made, the GPS subsystem loses lock.
Hope that helps.
