yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] droiddude414:
How I got LTE/data working was to go under APN and click the 3 right dots on the upper left and selected "reset to default". This erased the 10 random sprint APN settings and autoadded freedompops. Now I was getting the LTE setting with an X through it. After that I went into the freedompop apn and change APN/protocol and APN roaming protocol from "IPv4" to "IPv4/IPv6" for both and LTE has been working ever since. Hope this helps.
[E 2015 Android Development] LargePrime:
can you clarify what rom and what you flashed and what you did in more detail.

I dont even have the freedompop apn after reset. Just one sprint one.
[E 2015 Android Development] LargePrime:
also, one would flash the ROM after setting this fastboot config, correct?
[E 2015 Android Development] LargePrime:
can a wipe remove this setting? How sticky is this setting, and when would i need to reset it?

I wiped data, system, and flashed 14Feb Laos and still cannot get Freedompop CDMA to work.

When i enter carrier settings com.android.phone stops.

Celluar networks settings are

Preferred = LTE

CDMA Subscription = NV

AP Name has everyone but FP, including the dead RingPlus, but none are selected. Sometimes, if i ENTER one of these as if to edit it, and then back out two FP appear in the list. I am supposed to choose FreedomPop LTE, right? Then, sometimes, I edit the APN as droiddude414 recommends.

If I 'reset to default' as droiddude414 recommeds they all just comeback.

But in any case, the APN does not stick, as immediately reentering does not show the APN.

It all seems pretty buggy. Is it not for all you?
[E 2015 Android Development] kskillz2000:
Works fine for me. Set it once and was good to go. I'm on boost mobile, but what I did do, was go in APN and click reset then I got lte

Btw where did you get a feb 14 build? Last on this build is the Feb 04 build
[E 2015 Android Development] LargePrime:
https://download.lineageos.org/surnia 2017-02-14 14:52:16

do you think flashing this threads rom would give a different result?
[E 2015 Android Development] droiddude414:
I am on the Feb 1st nightly. I'm sorry I don't know how to describe it in more detail than what I previously posted. If it doesn't auto add the APN you can add it manually and it should stick. I also used MVNOslayer R4 which definitely has Freedompop for an option.

Maybe try pulling your sim and placing it back in? Keep tinkering, you will get it.
[E 2015 Android Development] :
Any Indian can chime in and tell is VoLTE working on Jio on official builds nowadays?
[E 2015 Android Development] NoInt:
The development of this ROM will continue ?? or do I need to change to the "official".

I'm asking this because the last build was on Feb 04 2017.

BTW, the Automatic upgrades are working for anyone ? I enter and try to check and got the error, "Error seeking upgrades, check your internet connection", I'm translating this, the error is show in spanish.
[E 2015 Android Development] vermaarun2494:
VOLTE ( jio )

yes VOLTE ( jio ) is work fine with this rom
[E 2015 Android Development] Seraph08:
edit
[E 2015 Android Development] merothh:
Including calling from stock dialer with data off ? (because in the night lies it seems to be hit or miss.)
[E 2015 Android Development] Seraph08:
https://basketbuild.com/filedl/devs...1/lineage-14.1-20170304-UNOFFICIAL-surnia.zip
[E 2015 Android Development] Soneliem:
I didn't know you were still maintaining this rom. This will be the second unofficial lineage os rom. How long are you going to continue supporting this?
[E 2015 Android Development] Seraph08:
for the foresable future. here, considering there's 'now two unofficial' lineage builds, i see no reason to continually drop nightlies/what have you. ill release these on a schedule where i find the upgrades worth doing a new one. I'm one of the lead developers for two ROMs now. both im writing builds for surnia for.

if two unofficial builds are unnecessary, well say the word.

​
[E 2015 Android Development] Soneliem:
It's all up to you. Im on reseruction remix right now, but the first android n rom i tried was yours. Thanks for that! No hate/insult intended in any of my posts.
[E 2015 Android Development] Seraph08:
:highfive:
[E 2015 Android Development] Sher1234:
Same Goes for me too

You were the first one to provide CM14.1 for surnia

That's up to you to continue it (schedule->2weeks) or not

I'll looking forward for the 2 roms in which you are one of the lead developer

Thanks for CM14.1 & LAOS14.1

UNOFFICIAL byils are too smooth than OFFICIAL one

That's for sure
[E 2015 Android Development] kskillz2000:
Thanks again bro for all your hard work and dedication to bring us your superior work!!
[E 2015 Android Development] merothh:
It's all up to you Seraph. If time allows and you are willing I'm more than glad for your builds : )
[E 2015 Android Development] Seraph08:
never said i was stopping, finished one of my others today. already officially on the manifest.
[E 2015 Android Development] Doctur:
Yah i got a just breath after telling dude he stole Ashyx s TWRP systemless root method.(gotta love dm verity disable zip) I was even pissed as grateful as we are to these developer s with athanks or donation it should alwys go to dude who put work into the device especially when he didnt even owb A J3 Emerge... Smfh :confused:...i tested it and dude was tryi. to get me to pay him the bounty i posted ...even tho i closed it and was testing For Ashyx ...idk cool as dude he is but this Tuscon dude sry i didnt get the whole move ...totally piece of work ....why i never made these mistakes as a junior member hmm i read the rules lmao
[E 2015 Android Development] mykenyc:
Dude the only reason why I'm using Surnia is because i lost my Nexus 5x. I used all versions and it's darker in 7.1, there is also a Google Pixel rom which enables a modified SystemUI with the blue accents, the color is identical, it's a 7.1 thing. Also, Android 7.1 is the last version, in the screenshot the phone is updating, if that's the case then the screen shot is probably not even on 7.1, but upgrading to it from 7.0
[E 2015 Android Development] ivangonzalo16:
Bug with Wifi in LockScreen

I do not receive Whatsapp messages when the screen is locked, it is?
[E 2015 Android Development] sirhc:
Any new SystemUI elements are merged from AOSP. If the QS Panel color is different, it's not because of CM, or any other devs. Its because of the new changes in 7.1 merged from AOSP. So theoretically it is a "7.1 thing"
[E 2015 Android Development] PimpMy5Ton:
Deleted
[E 2015 Android Development] Nilesh414:
Cm 14.1 is including theme engine?

Support volte?
[E 2015 Android Development] ManuelLima1994:
Not have theme engine for now i use cm14.1

The Bugs un The auto rotation With system Ui stops maybe for this not have theme engine
[E 2015 Android Development] nbehary:
Yes, it is that in AOSP 7.1. See the same on my N7 Rom (7.1.0_r4, nothing to change that). That should be the same as the Pixels in theory, but doesn't have to be I guess. (since it isn't, unless that screenshot is from something on the DP and 7.1.1. There are likely little things in that that don't match due to how 7.1.0 was split off.)
[E 2015 Android Development] TheDarkAhead:
I dunno if Google forgot to finish something but when you go to edit the order of the tiles, the colour of the panel is still that dark turquoise colour. that's what made me think something was dodgy.
[E 2015 Android Development] PimpMy5Ton:
Dodgy lol, I like that ?
[E 2015 Android Development] bloodsaw:
I just installed this yesterday the rom runs great thanks [MENTION=5213176]Seraph08[/MENTION] great job on these builds. opengapps ARM/7.1/Aroma installer is working perfectly. Although there is one issue i've noticed with this phone when using opengapps aroma, [MENTION=6485916]squid2[/MENTION] TWRP 3.0.0-r2, android 6.0 roms with the SD card formatted for Adopted storage is that you can't install opengapps after installing the rom unless you reboot the recovery, the installer runs fine until the files are actually being installed then it reboots the recovery but is unable to decrypt adopted storage.

The error that people are receiving when using adopted storage and trying to move an app back to internal storage is something I noticed in the build [MENTION=5337314]CodyF86[/MENTION] made for CM14.0.
[E 2015 Android Development] dzidexx:
[MENTION=4038530]bloodsaw[/MENTION]

You should use twrp 3.0.2. Don't wipe "internal memory" and "adopted" of course. I didn't try aroma, mini - no problem.

I move apks with link2sd.

By the way.

Notification led don't work with missed calls?

I found:

Calibrator system UI, more.. advanced settings notify "on".

Whatsapp & phone I've changed to 5.
[E 2015 Android Development] ayush rao:
[MENTION=5213176]Seraph08[/MENTION], I was just going through the forum and found that u were responsible for bringing CM13 to the OnePlus 2, man I guess CM14.1 for our device is in good hands. U're doing a great job pushing out builds great job.
[E 2015 Android Development] bloodsaw:
I just checked I am infact using 3.0.2-r1 for some reason I thought it was 3.0.0-r2 that I was using.
[E 2015 Android Development] dzidexx:
3.0.2 has no problems with adopted storage.

Thursday I was on RR 5.7.4, ejected sdcard and flashed cm14.1, yesterday I flashed newest version(with sdcard this time). Without wipe internal memory in twrp. Advanced wipe - cache, system, dalvik, data.

Still I has all data on adopted storage. [MENTION=4038530]bloodsaw[/MENTION]
[E 2015 Android Development] devilfingers:
Are you getting correct Size values under storage with cm14.1???
[E 2015 Android Development] bloodsaw:
I don't think you understood the issue I was describing, When installing a rom+custom kernel+OpenGapps Aroma under the same install queue when the aroma installer is installing the apps it reboots the recovery but when the recovery starts it is unable to decrypt the adoptable storage
[E 2015 Android Development] dzidexx:
[MENTION=4038530]bloodsaw[/MENTION]

Use pendrive for flashing or create gapps-config.txt for stock gapps.
[E 2015 Android Development] multidude1000:
Guys is anybody facing issue regarding Mobile data access 3g/4g for XT1521,if yes how to resolve it :silly: thanks in advance.
[E 2015 Android Development] devilfingers:
Build from 11-07 kernel is set to Enforcing.
[E 2015 Android Development] hassantalal11:
Use fire kernal v7 for mobile data .in latest build I was also unable to use data.
[E 2015 Android Development] Seraph08:
7.1.2

(i haven't had a chance to test it yet)

obv bb is down

https://www.androidfilehost.com/?fid=745425885120721745​
[E 2015 Android Development] merothh:
Just flashed it. Works fine

And you might want to revert the Br0Zip commits otherwise we wont need developers anymore./s

Br0Zip :-

https://review.lineageos.org/#/c/167379/3

Bootanimation :-

https://review.lineageos.org/#/c/167622/1

Can you please make the kernel enforcing ? (If you are willing)

And if you are willing to include the AOSP look.(blue-grey in settings and notification instead of black).

Comparison:- https://m.imgur.com/a/m2IbB

Then please merge this commit :- https://review.lineageos.org/#/c/164074/
[E 2015 Android Development] merothh:
See what I said ? Sadly it only comes with a 40 day trial period after which you need to purchase a license :(
[E 2015 Android Development] Seraph08:
kernel remains permissive for viper.

i dont theme.

---------- Post added at 05:32 AM ---------- Previous post was at 05:30 AM ----------

https://github.com/jrizzoli/android_packages_apps_br0zip
[E 2015 Android Development] merothh:
It's not a theme. Just reverts to the AOSP colours from the black one set by lineage. Please see the imgur link.

I know. See my first post , I was being sarcastic. Please revert the Br0Zip commits (In my previous post).
[E 2015 Android Development] bozinsky73:
http://lineageos.org/Announcing-our-Mascot/

br0zip is a prank
[E 2015 Android Development] FanboyStudios:
I do like the idea though.... Oh and Microsoft went open source! *not* We can't have nice things. Lmao :silly:
[E 2015 Android Development] RubenPCA:
The post has been updated
[E 2015 Android Development] merothh:
Shouldn't Seraph be the one handling this ?
[E 2015 Android Development] Seraph08:
Actually handling this thread no. It was myself who PMed Ruben last night to update the thread. He's been handling holding this community spot very well since it got posted. I'm handling the builds.

so it is, and will be.
[E 2015 Android Development] merothh:
Thanks for pointing out.
[E 2015 Android Development] VenomMOD:
Yet again, another buttery smooth ROM that flies through anything. :good:
[E 2015 Android Development] vikkuarya:
Volte calls working?
[E 2015 Android Development] sirhc:
FYI this isn't full 7.1.2. Lineage hasn't merged in 7.1.2, all they did was update the manifest to sync 7.1.2 repos they don't maintain
[E 2015 Android Development] merothh:
Lineage Repos have now been updated based off 7.1.2
[E 2015 Android Development] Seraph08:
https://www.androidfilehost.com/?fid=745425885120726054​
[E 2015 Android Development] PimpMy5Ton:
Good stuff
[E 2015 Android Development] lentm:
Any way to use the global sim on Sprint locked Moto E with LOS 14.1?

The global sim works only on stock 5.1...
[E 2015 Android Development] kskillz2000:
Posting in multiple threads will not get you an answer faster. If it's locked it probably will only work on stock.
[E 2015 Android Development] MotoJunkie01:
The Sprint/Virgin Mobile/Boost Mobile variants of the Moto E (2nd Gen) (xt1526), are tightly network locked. There is currently no method to achieve DSU (Domestic SIM Unlock) on these xt1526 variants. However, unlocking for international GSM use is an option.

It is worth mentioning that the U.S. Cellular variant of the xt1526 comes with Domestic SIM Unlock out of the box.
[E 2015 Android Development] lentm:
International SIM Unlock is okay for me, but never works on LOS 14.1, only on STOCK with UICC unlock option.

Any ROMs other than STOCK, I get force close at cellular option after I change the radio option to GSM or just don't get the signal at all.

CDMA works just fine on any ROMs....
[E 2015 Android Development] MotoJunkie01:
No problem there. Install Stock 5.1, initiate the UICC Unlock option in Settings and you're done. Flash whatever ROM you want and the UICC will continue to be internationally unlocked. This only has to be done one time.
[E 2015 Android Development] lentm:
Yea I thought that would work too, but no luck.

I've tried CM 13, CM 14.1, LOS 14.1, and AOSP Extended, get no signal... :(
[E 2015 Android Development] MotoJunkie01:
Then your problem is not with the lock status of the UICC, but rather with your telephony or APN configurations. The UICC unlocking option in ,Stock 5.1 writes to the /dhob partition, essentially "informing* the relevant radio firmware that your UICC has been unlocked for international GSM use. Custom ROMs do not modify or edit /dhob. Therefore, once unlocked you should not be required to repeat the system update option of UICC Unlock.

Even though your device is now capable of utilizing international GSM networks, this doesn't necessarily mean that your device is configured to operate on that network -- apns-config.xml, eri.xml, etc will need to be configured to allow connectivity, cellular data, RIL, etc. Custom ROMs such as LineageOS, as I'm sure you know, allow for manual editing of the APN settings. Research and obtain the APN settings with respect to your particular international GSM network, and see if that solves your connectivity issues. If not, further edits in eri.xml, etc., may be required. It's nothing that a flashable zip can't accomplish for you. I'll help anyway I can.

---------- Post added at 07:15 AM ---------- Previous post was at 07:10 AM ----------

Sorry, I had forgot to mention that build.prop can be edited to force your device to stay in GSM/UMTS Mode.

Give me the potential network names of the providers you plan to use internationally. I'll write a flashable script to make your network config changes. I've been extremely tied up at work, but I think I have a base script that I can just edit.
[E 2015 Android Development] overthc:
Try this that works for me:

After flash ROM and GApps and reboot, setting the mobile and then use the dialer and dial *#*#4636#*#* then enter into the first option (upper) then select WCDMA Only, go out and go to Mobile Network and select Global. This works on my Sprint XT1526 using other international GSM Mobile Carrier.

:good:
[E 2015 Android Development] lentm:
Oh, I never thought of trying WCDMA only.

I will try tomorrow and report back. Thanks!
[E 2015 Android Development] MotoJunkie01:
Does the device return to it's build.prop persistent CDMA/LTE (auto PRL) mode after reboot?
[E 2015 Android Development] lentm:
I had to try multiple times to get "WCDMA Only" to stick, but got it to work.

I can confirm that this method works!!

Thank you very much!!! :laugh: :good:
[E 2015 Android Development] MotoJunkie01:
:good: Great info
[E 2015 Android Development] overthc:
Yes, it returns but stays configured the network :D
[E 2015 Android Development] MotoJunkie01:
From my experience, without editing build prop to permanently enable your preferred Network Mode, com.android.cellbroadcastreceiver will get buggy and even force your Network Mode back to the carrier specific default during and after voice calls. Even if this does not happen, WCDMA only Mode is extremely limited. Once your signal strength gets below 3G, signal is killed and baseband will not seek out 2G. This will result in a lot of dropped calls. WCDMA preferred ramps the baseband down to 2G once 3G signal becomes weak, thus sustaining in call connectivity. To ensure this mode, add these build prop edits with a root file manager/editor or build.prop editing app: Root is required:

persist.radio.ap.phonetype=1 ro.telephony.default_network=3

The first line forces your phone into GSM/Global Network Mode permanently (or until this value is changed). The second line sets Preferred Network Type to WCDMA preferred. Depending on your provider, preferred data usage, etc., you may wish to set this parameter to another value:

0 = WCDMA preferred

1 = GSM Only

2 = WCDMA Only

3 = GSM/WCDMA (auto prl)

These values are varying from 0 to 25 and include several unorthodox yet extremely effective preferred network type, including some GSM/LTE configurations. Again you should use the value that best suits your international GSM plan, the data package included in your plan, signal strength in the country abroad in which you will be using your device, etc.
[E 2015 Android Development] overthc:
Hi, my suggestion is just to set the mobile network the first time that you use the phone after flash a new room. And it works fine.

:cowboy:
[E 2015 Android Development] :
You guys should really either us PM's or start a thread in the proper place for all this.
[E 2015 Android Development] MotoJunkie01:
I agree with your suggestion 100%. Works on most ROMs indeed. However on those ROMs with a persistent build.prop config, network mode will return to default on each and every reboot.

I don't think we are being off topic as somebody suggested. This addresses an extremely common occurrence for members who use this device with its optional International UICC Unlock mode. I apologize for the lengthy colloquy. And, [MENTION=6362303]overthc[/MENTION] I apologize if I seemed argumentative on this topic.
[E 2015 Android Development] MotoJunkie01:
[MENTION=5213176]Seraph08[/MENTION] you are the man. Thank you
[E 2015 Android Development] :
I just found that if you set selinux to permissive in a terminal, then go into viper and install the driver and reboot, it works fine even with selinux going back to enforcing after the reboot.
[E 2015 Android Development] Seraph08:
real question: would not using terminal to set it to enforcing after the fact have the same effect? im asking cause for those who arent as savy, keeping it as is might be the safe over all bet, and then for those concerned with having it enforcing do it the way you suggested?

---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------

and im doing you guys a new build tonight. may security patch is in
[E 2015 Android Development] :
Yes, but the thing is it will get set back to permissive after every reboot and would have to be set back to enforcing with a terminal every time. You can also use the selinux changer app or what ever the hell it's called. It sounds easier to just set it to permissive once to install the v4a driver. Also, part of the fuss is permissive being set on boot is the main security issue I believe. I really couldn't care less personally. But anyway, it's as simple as opening a terminal, typing su then enter. Then typing setenforce 0. If people can't do that...
[E 2015 Android Development] Seraph08:
*no words must be said*

www.github.com/PA-CAF

went live last night. repos build ready. if you know what you're looking at. this entire forum should be grinning. needs more work, but for this device, things worthy of finding a dev to build it.

AOSPA-L just might rise again. Just differently this time.​
[E 2015 Android Development] :
I've already been playing with it. I just have a few errors to work out.
[E 2015 Android Development] Seraph08:
get at me on hangouts. i wrote the thing. im sure i can help.
[E 2015 Android Development] :
Defiantly. I was actually working with AOSPA's and my own repos, but that looks good. I'll start syncing before I hit the sack tonight and get ahold of you when I start a build and get an error. I've built a new beast that needs to earn it's keep.
[E 2015 Android Development] Seraph08:
The aospa hals will be one issue. Second the latest branch is being ran off a msm8998 caf branch. The hardware will be a fun part.

My repo uses the lineage ones just for hardware. Probably the only ones I did use. To provide the hals. It's exactly what aospal had to do.
[E 2015 Android Development] wicpp:
Terrible bluetooth performance after flashing the latest rom.
[E 2015 Android Development] kskillz2000:
What do you mean? Bluetooth works fine for me on 2 devices.
[E 2015 Android Development] wicpp:
I have XT1524, most of the times it does not connect to the already paired device. And I have to remove the device and repair the device to use it. Also when the device is turned off the phone menu bar still show that bluetooth device is connected.
[E 2015 Android Development] kskillz2000:
I mean sometimes that happens to me I have to reconnect the device, which is probably a bug as I've always had that issue. The other issue your having I have not seen, so i can't comment on that.
[E 2015 Android Development] Seraph08:
this was a known issue in cm sources before the May security patch merge. none of this is news.
[E 2015 Android Development] MotoJunkie01:
For anybody who needs it...this is the SELinux Mode Changer APK V3.2.0 https://drive.google.com/file/d/0B7-zQU1VihD3OVNldVpNSV9oU1E/view?usp=drivesdk
[E 2015 Android Development] wicpp:
What is this file? SELinux Mode Changer APK V3.2.0

What it has to do with this bluetooth performance?

Also when I try to download I get the following error messages.

"Sorry, this file is infected with a virus

Only the owner is allowed to download infected files."
[E 2015 Android Development] :
That is ancient. You should remove that link.

https://xdaforums.com/android/apps-games/app-selinuxtoggler-t3574688
[E 2015 Android Development] wicpp:
Can anyone explain what that application has to do with bluetooth performance?

Also I can not root my phone as some of the financial apps will stop working.
[E 2015 Android Development] :
Absolutely nothing. That was just an improper quote.
[E 2015 Android Development] wicpp:
So that means the issue is fixed after May patch?
[E 2015 Android Development] tonyjaimy:
is this rom enable lte band 5 ?

because moto not provideing this band on this mobile
[E 2015 Android Development] MotoJunkie01:
Ancient I don't know about. I just know the app works great for simple toggling between SELinux Enforcing & Permissive modes.
[E 2015 Android Development] :
But, it is the old, discontinued version of what I posted a link to that doesn't say it has a virus.