yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] mrxtc89117:
I have used open gapps pico 4/29 with no problems.

I'm now using open gapps stock 5/6 with a custom gapps-config because I want the google dialer and contacts and dialer framework and I wanted to remove some stock CM apps and live wallpapers that I will never use. It works with no problems.

I'm on build 5/05 with squid kernel and xposed.
[E 2015 Original Android Development] nguyenquangduc2000:
I have successed in building my first rom for surnia. Thank you so much [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] :
Im not sure you are allowed to post that here, as i don't think its relevant, seeing this is a development thread for CM13......

I would post that in a new thread just in case the mods come down on you.

:)
[E 2015 Original Android Development] yelupic:
Hi, Ivan39, old friend, nice to have you back one more time.

I'm delighted for nguyenquangduc2000 having built his first ROM based on squid2's (and others) work.

What else would fit better into this thread, than to see that someone follows the path of the "masters"?
[E 2015 Original Android Development] :
I agree!

I just don't want to see anyone getting told off (like I was hahaha)

Just being "over cautious"

A famous star wars quote from a new hope springs to mind.........

Great job though :D
[E 2015 Original Android Development] nguyenquangduc2000:
I do not post for making wars, I only want to be thankful to squid2 who help me finished my build.
[E 2015 Original Android Development] :
No one is making wars my friend, I didn't think it was "appropriate" to post your work in this thread, and my friend yelupic said it was a good thing, and I congratulate you on your work, and hope I didn't offend :)

---------- Post added at 11:04 AM ---------- Previous post was at 10:58 AM ----------

How is the currently nightly? I've moved away from this for various reasons have going a great ROM, but my heart calls for CM13, just wandered if the current nightlies are stable and bug free?
[E 2015 Original Android Development] AndersCF:
This runs so smoothly. Thank you for your amazing work on the Surnia, with this ROM, your kernel and your TWRP this is a great phone. Excellent work man.
[E 2015 Original Android Development] nguyenquangduc2000:
I think this build is as stable as cm13 now. Because I did not change anything. :)

I also think I will make for surnia BlurOS rom nextweek, based on source of xdavn.com
[E 2015 Original Android Development] mrxtc89117:
The nightly 5/6 is pretty stable although I experience some lag but that may just be my setup. I have too many things on to isolate it. I'll put that in a seperate post.

Glad you are back.
[E 2015 Original Android Development] mrxtc89117:
I had to do a clean install last night. Apparently you cannot dirty flash an open gapps package with a different one.

I had open-gapps-pico and I wanted to use open-gapps-stock because it had the google dialer and contacts and dialer framework. the stock cm dialer had a problem with sip and I depend on it for reception at home.

Then I had the idea of why not replace other stock cm apps with google apps like the calculator etc. also. You can do that with a gapps-config.txt assuming your gapps package has it.

It worked in the beginning but I started getting wierd permission errors. So never upgrade to a bigger gapps package using dirty flash.

Here's my gapps-config for anyone curious. I don't recommend trying it. This is my backup phone so I can play with it.

I clean flashed last night with the open-gapps-stock and gapps-config. Seems stable so far but I'll know in a few hours.

Edit: If you are going to use the google dialer, you have to manually set the permissions for the phone under settings->apps and also set it as default, or it will crash.
[E 2015 Original Android Development] :
Clean flash is always recommended when changing gapps package.

I've also started clean flashing all nightlies, for me, I get a very stable and bug free configuration...

Nothing wrong with dirty flashing, i just have an air of caution over recent CM13, probably no need to be TOO cautious, but I always fear the worst (for some reason)

There's been a lot of talk about gapps, which packages to use and stuff like that.

Despite my own and other members warning against it, a minority still have developed a strange and unorthodox way of flashing gapps, by flashing the ROM, rebooting to android to check its working, then returning to recovery to flash gapps, and then they are puzzled as to why they get so many errors!

I've come across this strange installation method in other forums on XDA.

I can't understand the reasons for this or what anyone is hoping can be achieved (apart from many errors)

I may sound like a broken record (By keep going on about gapps) but the devs flashing instructions are more than clear!

Just going back to your post, i never got any open gapps packages to work on CM13, and used a google minimal package.

But I've been testing another ROM over the past week, and the usual gapps I use doesn't work, but I can only get open gapps to work on the other rom :)
[E 2015 Original Android Development] mrxtc89117:
I think the different gapps packages may be market related. Maybe A gapps is for the EU market. I tried it and it looks different and it would not go thru after Google login. Seems some sort of restriction.

Maybe when I have time later I will look at the script and see if it is.

My clean flash last night i still running well. I did have to reinstall some apps again. I restored them from Titanium backup but it did not run well. Installing them again from the Play Store fixes it.

Edit: I did not install the squid kernel this time. Although the squid kernel is superior, I think the real world difference is negligible (without further tweaks e.g Kernel Adiutor). It's also one less thing to think about when things go wrong.
[E 2015 Original Android Development] :
This is a issue not a problem, by that I mean we discuss how our devices work and operate under different conditions and parameters.

So we should, that's what the duty of a "tester" is all about.

I've tried various configurations over the past week because I've had time on my hands to test more and experiment.

I notice that most people are running hacks and mods (squid kernel, custom boot animation, ext) and again, its good to test these things to see how the device responds or handles these unofficial modifications.

One thing I find amusing and at the same time a little annoying is some of the less experienced users are trying out these modifications we discuss, sometimes with disastrous results.

We have some people saying and thinking that a custom kernel will give their phone secret super power, 10 rocket launchers and the ability to travel at lightspeed........ok, maybe that's being sarcastic and cynical and not meant to offend anyone, but rather I'm questioning why people are putting these things on their phone just because others have got it.........I've got into several conversations over the past month where people have begged me to explain how I've got a certain mod or customisation on my device, and they think these are just "super cool must have add ons"

The complexity of the kernel and what is does is beyond the inexperienced user, i suggest if they don't know what its for or what it does, then they have no need for it.

I take my testing role very seriously, because I work in such different and constantly changing conditions, its the ideal way to put said device through it's paces, and I have the luxury of having a moto 1st gen I'm testing in these conditions too, so how one behaves at work with all my mods while I'm running the other with a bear clean install of CM13 solely to test the network/data under changing locations and environments is a great test.

I just hope you consider my input relevant and appreciate I can only give my honest and open opinion on the test I personally conduct :)
[E 2015 Original Android Development] ayush rao:
The WiFi soft reboot issue is back on the latest nightly.........
[E 2015 Original Android Development] :
You gone back to CM13? I'll stay where I am for now.......
[E 2015 Original Android Development] mrxtc89117:
I agree. People should completely understand what these mods do first. If you don't know what it is, then you don't need it. The squid kernel, just as an example, if you install it as it is, the benefits are negligible in a real world experience. The stock kernel runs just as smooth and fast. Custom kernels are for tweaking and that's where you see the benefits. But you have to know what you are doing. Even then, it can cause instability and lockups.

I'm back to the stock kernel for now. I had my fun and that was it. It's a really good kernel to tweak.
[E 2015 Original Android Development] ayush rao:
I m back!!!! U should try it. The latest builds r really stable
[E 2015 Original Android Development] DPyro:
Does this work with Canadian SIMs now? Couldn't detect my SIM card before.
[E 2015 Original Android Development] kesavvel:
will we get doze feature in mm ??? do surnia support doze ??
[E 2015 Original Android Development] ayush rao:
I think it does in CM13, cause I've had much better standby when compared to CM12.1 or any other lollipop ROM for that matter
[E 2015 Original Android Development] kesavvel:
check this thread please ! and check whether our dev supports doze

http://xdaforums.com/android/apps-games/app-check-doze-support-t3374265#post66742641
[E 2015 Original Android Development] ayush rao:
It turns out our device doesn't support doze. This is rather shocking cause my device has incredible standby time........
[E 2015 Original Android Development] kesavvel:
mmmm but our device dosen't support doze ! anyway thanks ! :) I checked it with moto g2 also ! Sadly no doze for it too . But will not be an big issue moto e rocks with cm !!!
[E 2015 Original Android Development] ayush rao:
Probably this feature is enabled on our device based on a criteria other than the sensor
[E 2015 Original Android Development] kesavvel:
maybe ! but android offical site says the same ! that doze needs that sensor so that device will enter deep sleep mode and google cloud time sync !

---------- Post added at 10:14 AM ---------- Previous post was at 09:59 AM ----------

how much on - screen time do you get with mm ???

please say about your usage also ??!!

:confused:
[E 2015 Original Android Development] ayush rao:
I watch lots of YouTube, check the XDA forums using the XDA Labs app and I also play lots of dude perfect. With that usage i get around 4 hrs of SOT
[E 2015 Original Android Development] kesavvel:
Thank you is cm 13 stable right now ? Do you use wifi or mobile data ?
[E 2015 Original Android Development] ayush rao:
Very stable
[E 2015 Original Android Development] kesavvel:
Do you use wifi or mobile data ?

Thanks in advance
[E 2015 Original Android Development] ayush rao:
I almost only use Wi-Fi.
[E 2015 Original Android Development] DPyro:
Still can't detect my SIM card!
[E 2015 Original Android Development] _dud3:
I still got issues with encrypting my device. I clean installed 05/08 build, than did "fastboot erase userdata" and successfully encrypted my device. But than only notification bar was accessable by swiping from top, quick settings did not. On lock screen nothing happened after swiping from top! Connecting the device via USB was not possible as the dialog to choose connection option did not show up. So I did another "factory reset" and am now stuck on bootloop (optimizing 23 apps > reboot > optimizing 23 apps > reboot > and so on).

Could fix this issue by myself: Forced power off, than format/full wipe, reflashed 05/08 build, reboot, fastboot erase userdate, encrypt device, cleared data/dalvik/data again, reboot.
[E 2015 Original Android Development] magicw:
when I plug in my headset phone does a soft reboot on latest versions (0507 and 0508). Does anyone else recognize that?
[E 2015 Original Android Development] therealprof:
For about two weeks the bluetooth daemon keeps on crashing. Anyone else have the problem or (even better) a cure?
[E 2015 Original Android Development] mrxtc89117:
I just plugged my headset and no reboots. I'm on build 5/09, stock kernel, opengapps, xposed XT1526.
[E 2015 Original Android Development] ayush rao:
Same here I don't have any reboots on plugging in headphones
[E 2015 Original Android Development] ayush rao:
R u guys sure doze doesn't work. I never got this standby on CM12.1
[E 2015 Original Android Development] xtermmin:
Not sure if it's a Doze feature, but I notice that if I leave my phone idle for more than an hour or so, then quickly check to see what LTE band it's connected to, it shows that it's been connected to a slower-but-stronger-signal band (13), and then shortly connects to the faster-but-slightly-weaker-signal band (4). Basically, it looks like it's falling back to the strongest signal at times of idle to save battery life.

I'm running an older build (04/08), but battery life has always been fantastic for me. Been on battery for 4 days, 3 hours SOT, still have 40% battery left, guesstimating 3 days remaining.
[E 2015 Original Android Development] magicw:
yeah I'm also fine again with todays 0510 version. Maybe the clean install after several updates via updatemanager also may have helped. :D

What I still recognized however is a weird behaviour at login after reboot:

I'm having the Dual SIM international version XT1521 and, after boot up when SIM login appears you will not be able to switch to the second SIM once you failed logging into first SIM in the first trial.

If you then type in the correct PIN in a second trial the device tells you that SIM1 is unlocked. But then it does not change to SIM2. Changing of the SIM login can be recognized by a different colour of the SIM symbol. Green for SIM1 and Blue for SIM2.

Only remedy is to reboot and then - hopefully log into SIM1 in the first trial :eek:
[E 2015 Original Android Development] helpful_onlooker:
Hi all - anyone had any luck getting data to work on the US Cellular XT1526? I have a Verizon SIM, and voice/text work, but no data...
[E 2015 Original Android Development] mrxtc89117:
You have to set the fsg-id thru fastboot if your network is listed.

http://xdaforums.com/moto-e-2015/or...moto-e-lte-t3329100/post65938830#post65938830

Also set the APN in the carrier settings in the settings page manually if it's not there. I'm on Ringplus so I don't know what those values are.
[E 2015 Original Android Development] :
I've returned to my "home" this evening, having took a week or so away from CM13 I decided to rejoin the testing program

Just flashed the 10th of may nightly, I'm impressed that the old speed and fluidity from early nightlys is back. So far so good, and I'm using open gapps for the first time ever on CM13.........
[E 2015 Original Android Development] helpful_onlooker:
Nice! I had to turn airplane mode on and off. It connected to Verizon over LTE!

Talk and text did not work, so I had to go into the network menu (*#*#4636#*#*) and set to cellular - USA Band kept the phone on LTE permanently and talk/text did not work

Now, on cellular mode, talk and text work, but they switch to roaming. Data doesn't say LTE unless I switch airplane mode on and off again.

Here's the fsg-id I used:

fastboot oem config fsg-id verizon

and the APN:

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MCC: 311

MNC: 480

APN Type: default,dun,mms,supl

APN Protocol: IPv4/IPv6

APN Roaming Protocol: IPv4/IPv6

Bearer: LTE

everything else: Not Set/None

I'm running cm-13.0-20160510-nightly-surnia
[E 2015 Original Android Development] xtermmin:
The fsg-id should be "vzw", not "verizon". You also might want to reflash the radio because setting the bands in the network menu (cellular, USA band, etc) messes up things.

I'm using an XT1529 on Verizon with no issues. All I had to do was set my fsg-id and edit the APN to include the MMSC URL (the default one that gets loaded doesn't have it), and I think I switched the Bearer to Unspecified, but I'm unsure if it makes a difference.

It correctly connects to LTE (13 and 4, not sure about 2) and falls back to 1x when making calls.
[E 2015 Original Android Development] mrxtc89117:
It's not the ROM. It looks like the bands are not the same so you won't get any data as far as 4G LTE goes. You have to check and see if the phone's hardware actually supports the bands. Sorry I can't help you any further. It's as far as I know.

http://www.droid-life.com/2015/02/0...sm-cdma-wcdma-lte-verizon-att-sprint-tmobile/
[E 2015 Original Android Development] xtermmin:
The USC XT1526 does indeed work on Verizon, both CDMA (B0/B1) and LTE (B4/probably B2 as well but I haven't been able to verify). It's missing Band 13.
[E 2015 Original Android Development] distoy:
I use the wunderground weather app and it works just fine. I use celsius as temperature unit. But in the pulldown menu the temperature is shown in Fahrenheit.

Could somebody with access to jira file a bug report on this? (As of yesterday there is no report on this. Jsut a comment on a closed ticket that is about somethin different)
[E 2015 Original Android Development] helpful_onlooker:
Thanks for that - is there a list of fsg-ids available? My googling wasn't helpful...

My USC XT1526 connects to Verizon on both Band 2 and Band 4 - luckily for me RI has good Verizon coverage with those bands.

Regarding the radio - do I flash fsg.mbn and NON-HLOS.bin from the stock Verizon 5.1 ROM?
[E 2015 Original Android Development] ayush rao:
I'm on the May 8 build and this issue no longer affects me. Which build r u running?? Updating solved my problem
[E 2015 Original Android Development] xtermmin:
Apparently Moto maintains a list on Google Drive here, but it's protected, and nobody's been able to access it.

I didn't flash a different radio, just used the USC one. To reset the modem back to stock (to undo the band selection), just boot into fastboot and erase modemst1 and modernst2. The system will re-generate them on boot.
[E 2015 Original Android Development] ayush rao:
Has anybody been getting this weird exclamation mark on their weather forecast
[E 2015 Original Android Development] helpful_onlooker:
Ok. Here's what I did (this is a USC XT1526 running the 2016.05.10 cm13 surnia build):

-reflashed USC modem (SURNIA_USC_5.1)

-set fsg-id to vzn (fastboot oem config fsg-id vzn)

-erased modemst1, modemst2

-factory reset

-reflashed 2016.05.10 cm13-surnia build

-booted, ran through setup

-set APN to internet, mmsc to http://mms.vtext.com/servlets/mms (I can't save the APN without an entry in the APN field)

-rebooted

Currently, the phone identifies as Verizon Wireless. I have talk and text, but no data network.

[MENTION=6485916]squid2[/MENTION] - if there is additional testing you would like me to perform with my USC XT1526, I'd love to help. It isn't my daily driver so I can do whatever to it.
[E 2015 Original Android Development] mrxtc89117:
On my Boost Mobile XT1526 activated on Ringplus, I had to use the stock rom first and provision it for PRL and Profile update before I could make it work on CM13. Not sure if verizon is the same.
[E 2015 Original Android Development] distoy:
I also run 20160508. It was a different problem: I missed changing the unit in the weather backend. Seems to be that the widget is configured by cLock and the statusbar info by the weather backend settings.
[E 2015 Original Android Development] kskillz2000:
Having a issue with MMS still, anyone else having issues receiving pics?
[E 2015 Original Android Development] mrxtc89117:
I've been dirty flashing almost everyday with the new builds. 5/13 build works well. But my question is with all the flashing, does this fragment the nand drive and should I run fstrim or maybe it just does it at flash.

I tested the adopted storage feature and it works with 128gb sdcard. I downgraded to something smaller because I dont really need that much space, and split it 75/25. It works as it should.
[E 2015 Original Android Development] vayavalla:
How did you split it?

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[E 2015 Original Android Development] mrxtc89117:
You have to split the sd card thru adb. It is the only way I found that works. Just reboot after you finish with adb and you will have your adopted storage and external too.

http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
[E 2015 Original Android Development] mrxtc89117:
It could be a problem with codecs. Try builds from 5/12 and above. There's been a fix for ffmpeg. Then go into Settings->Sounds and select your Phone ringtone. If you can hear it, then it should work. If not, then I don't know.
[E 2015 Original Android Development] Gilmar Mess:
Woww man thx so much its work :):):)
[E 2015 Original Android Development] IronTechmonkey:
Flashing latest version and going into setting should be the first thing done in troubleshooting (and paying attention to commits or ROM news as you seem to be doing certainly helps) but when someone manages to have the same problem on and off for 6 months in multiple ROMS while others dont have that problem it is clear that there were other factors at play in regards to underlying cause. In any event, thank you very much for the suggestion (I'm out of official TYs).
[E 2015 Original Android Development] Az Biker:
THIS THREAD HAS BEEN CLEANED!

Please remember to treat each other with respect and without inflammatory, or provoking commentary. This thread exists to aid in development, not be a playground for disruptive antics. Stay on the development topic, and stay away from violating XDA Rules.

Further posting of disrespectful, inflammatory, or disruptive comments will impact the individual user's account.
[E 2015 Original Android Development] kesavvel:
the current nightly is awesome !! i am going to use it as my Daily Driver (huge thanks to the devs team !) ! but in the notification tiles torch still exists ! and usb tethering is also visible while editing tiles mode these two are visible ! when done button is clicked they disappear ! this is not a major bug but makes me feel the os may have too many bugs that are not visible ! otherwise the os is awesome ! please try to fix it as soon as possible
[E 2015 Original Android Development] ayush rao:
Even I have experienced this issue, I assume it's because this device doesn't support torch. I just delete those tiles in the edit option.
[E 2015 Original Android Development] kesavvel:
ya i too did the same ! hope will be fixed in future updates
[E 2015 Original Android Development] elscud:
That happens with the stock 6.0 rom, maybe it's not a bug
[E 2015 Original Android Development] :
What torch?

What USB tethering???

I'm cheating by the way, and use the Android N notification............
[E 2015 Original Android Development] kesavvel:
is it happening in our stock rom ??
[E 2015 Original Android Development] MarquesYOLO:
Weather app and theme pls? Love it!
[E 2015 Original Android Development] kesavvel:
nice ! i like it ! :good:
[E 2015 Original Android Development] shadow252:
I suppose they mean that torch icon on the notification drawer appears when editing a layout but disappears after it's done. Nevertheless I wonder what's with USB Tethering icon, cause I don't have it while editing tiles. Maybe it's due to the fact that I'm using AICP at the moment.

When editing tiles:

After saving layout:
[E 2015 Original Android Development] kesavvel:
check with adding new tiles to notification panel ! usb tethering will be available in the list , just add it and click done ! then the icon will be missing , and will return when you again edit tile list !!!:)
[E 2015 Original Android Development] :
No problem

The app is Xwidget and the widget is called "Lockscreen widget 7"
[E 2015 Original Android Development] shadow252:
Oh, I think I understood it. USB tethering icon is not showing up, because you have to connect your phone by USB cable in order to make icon appear. ;)