yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] vnai:
I actually don't want people with CDMA variants of surnia using this ROM as I can't test it and there are lot more unfixed issues in CDMA variants which no one is fixing even in upstream LineageOS.

If possible share the logcat logs with me over email to vishnu [at] vishnunaini.com and I will try to investigate.
[E 2015 Android Development] fastbootflash:
Only one small thing though. The size of this rom is really big. Is there any particular reason for it. Anyways still gonna download and flash anyways. Great rom BTW. Thanks [MENTION=7963704]vnai[/MENTION]
[E 2015 Android Development] vnai:
It is big because it uses DEX preoptimisations to pre compile the java bytecode for pre installed apps so that the onboard ART JIT compiler need not bother with it. It is enabled on most stock roms but custom roms dont bother with it as it increases the build times for the developers.
[E 2015 Android Development] xukashi:
Read Changelogs ?

Includes Dex Pre optimisations making the zip bigger by 100MB
[E 2015 Android Development] enter.hk:
So how to use adaway...

I like the ROM and want to stay away from Root...
[E 2015 Android Development] vnai:
Never tried it but I believe you can use the same methods you use on stock ROMs.
[E 2015 Android Development] enter.hk:
I would be nice if u build adaway in ROM...
[E 2015 Android Development] vnai:
I am sorry but I don't think I will do that. I will stick to try keeping a stock lineage experience.
[E 2015 Android Development] vnai:
the cellular settings bug in CDMA devices will be fixed in the next release.

I have preliminary patch for the camera shutter double tap bug but I am not sure if it will fix it as I am unable to reproduce the bug. I based my patch entirely on the logs provided by [MENTION=7165185]mcduffy[/MENTION]. I will include the patch in the next release.
[E 2015 Android Development] beast99:
What is dex preoptimization :confused: [MENTION=7963704]vnai[/MENTION]
[E 2015 Android Development] :
I'm on a Boost Mobile XT1526. Just flashed this ROM last night, moving from cm14.1. Clean flash, wiping dalvik, cache, data, and system. As the other guy said, com.android.phone stops when I tap on Cellular networks. If you need a logcat let me know, I can grab one later after I get back home.

Settings crashed once last night also but I'm unable to reproduce it. It happened while the phone was switching from landscape mode back to portrait mode. It hasn't done it since and I wasn't able to reproduce it.

Camera shutter button takes two or three taps to work but I see that it might be fixed in the next update.

Other then that this ROM is buttery smooth and not seeing any bugs other than the ones mentioned.

EDIT: never mind about the cellular settings bug, I just read about it being fixed.
[E 2015 Android Development] vnai:
Read this https://source.android.com/devices/tech/dalvik/configure.html for full details
[E 2015 Android Development] vnai:
Updated release with cellular settings crash fix on CDMA devices

https://github.com/vishnunaini/lineage-surnia-releases/releases/tag/20170115

The camera shutter double tap bug will require more work.
[E 2015 Android Development] beast99:
Thanks for all your work bro:)
[E 2015 Android Development] battle_hardened:
How do I shut off the battery charging notification light?
[E 2015 Android Development] sonnu0100:
Setting - notification - setting icon upper right side - battery light ..

This is the way for cm14 , not sure if it can used to toggle off in this rom too.

I am currently on CM14.1 as i have cdma variant .

HiT Thanks if SomeBody Helps you..

---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------

Can u check and confirm the setting close issue in cdma varaint is resolved. My net speed is low and this is my daily driver too . If it is working smoothly on cdma variant xt1526 , i can proceed to download .

Waiting for any xt1526 user feedback !!

HiT Thanks if SomeBody Helps you..
[E 2015 Android Development] battle_hardened:
Thanks! I can't believe I missed that:rolleyes:
[E 2015 Android Development] vnai:
For CDMA devices only:

[MENTION=7165185]mcduffy[/MENTION] confirmed to me by email that the cellular settings crash has been fixed in the latest release I sent to him before releasing publicly. There are some other crashes in CDMA carrier settings that also exist in the official cm 14.1 versions that are still unfixed as they are related to non-availability of some qualcomm binary blobs and pretty much out of my hands.
[E 2015 Android Development] sonnu0100:
Thanks for the build and confirmation.

Will try and report back tomorrow's night as its the only time my phone will have some rest [emoji4] . loving this phone due to developers like you which make it alive . Appreciate your hardwork on building this.

HiT Thanks if SomeBody Helps you..
[E 2015 Android Development] oppodi:
I'm not seeing an option to enable volte in xt1521

I'm using your ist build
[E 2015 Android Development] vnai:
VoLTE only works in SIM slot 1. Is your baseband up to date? Is LTE enabled on your phone? Who is your carrier?

Type *#*#4636#*#* in the dialer. Go to phone information. Is volte enabled?
[E 2015 Android Development] debojyotidey:
someone has cm file manager working?
[E 2015 Android Development] kskillz2000:
On what build? It's working for me a little buggy tho
[E 2015 Android Development] debojyotidey:
I can't access the sdcard from it...can you?
[E 2015 Android Development] kskillz2000:
Sorry im thinking of the wrong thread. I've yet to try this build...
[E 2015 Android Development] debojyotidey:
does anyone have a workaround?
[E 2015 Android Development] mcduffy:
I have the same problem even on CM 14.1 with Root access enabled. I use ES File Explorer app instead.
[E 2015 Android Development] debojyotidey:
me too :highfive:
[E 2015 Android Development] oppodi:
Baseband should be up-to-date I was using volte in stock mm . When I enable volte provisioned it automatically turns off after some time. I'm using it on SIM slot 1. Carrier:jio
[E 2015 Android Development] vnai:
the issue with exact same conditions doesn't exist on my xt1521. I need the logcat radio logs or else I won't able to say anything.
[E 2015 Android Development] debojyotidey:
do you have any fix for sd card issue in cm file manager bro?
[E 2015 Android Development] vnai:
I wasn't aware of this issue till now. I will look into it.
[E 2015 Android Development] vnai:
New release

2017-01-18-10

https://github.com/vishnunaini/lineage-surnia-releases/releases/tag/20170118

https://github.com/vishnunaini/lineage-surnia-releases/releases

fix camera initialisation delays

fix camera refocus after camera switch

Upstream LineageOS changes:

new bootanimation

CDMA users can now edit apn's without issues
[E 2015 Android Development] Buzbee2:
[IMG="Install error"]https://app.box.com/s/0isc8u413ho8cyq0jlticm9vr7n7g3l0[/IMG]

Does anyone else get two unknown commands during install?
[E 2015 Android Development] vnai:
There are some post install scripts in cm that expect busybox utilities to be present in the recovery but last year both aosp and cm switched to google's new command implementation called toybox. Toybox is not feature complete yet and is missing some commands some old scripts expect to be present. The "log" command is one of them. This does not break installation and safe to ignore.
[E 2015 Android Development] K.I.R.K:
first I was skeptik: how can one guy (@vnai) provide a completely new rom. what's about testing and programming by community? so I always watched vnai's work and I saw he's part of the lineage community and so my trust grew.

finally I switched from last CM rom to this lineage rom and I'm completely happy! it's a great rom! I had to flash superSU because of using titanium backup. I installed on a XT1524

thx vnai and sorry for hesitation :D
[E 2015 Android Development] vnai:
Things to ponder about. Google Play thinks this ROM is certified by them.

Screenshot attached
[E 2015 Android Development] Prashanth_tester:
A small request. Is it easy to implement Pixel like navbar directly baked into the rom? or if its even possible?
[E 2015 Android Development] Tathagata Nandi:
does it supports any theme engine like substratum??
[E 2015 Android Development] enter.hk:
No...
[E 2015 Android Development] Sher1234:
It worked for me for some themes but not all & some time causes bootloop
[E 2015 Android Development] sonnu0100:
Try pixel mod in themes section . made specially for this rom .

HiT Thanks if SomeBody Helps you..
[E 2015 Android Development] govind1233:
http://lineageos.org/Update-and-Build-Prep/

Lineage pushing first official builds next week...BT they will be weekly
[E 2015 Android Development] vnai:
Lineage official builds for surnia will not have VoLTE as maintainer stated here https://review.lineageos.org/#/c/154523/ in comments. IMS will not be reimplemented as it's breaking builds on other motorola msm8916 devices like osprey.
[E 2015 Android Development] govind1233:
Yes I know bro...My Asus Zenfone 2 laser Z00L also have same problem
[E 2015 Android Development] vnai:
An update for everyone

1. I fixed the camera double shutter bug by using a rebased version of the camera app from qualcomm but the new tree has given rise to entirely new range of bugs that broke video functionality. So I won't be shipping this rebased tree. I actually tried fixing the shutter bug on my own but the code structure in the app is very bad and requires some time to understand it. Even upstream lineageos is trying to rebase the tree for the sake of supporting newer devices like marlin and sailfish but the tree is in no position to be shipped.

2. How many of you will be okay with doing a full wipe for a future build if it involves moving to a more secure build?

Currently my ROM is signed with AOSP's default test-keys but this is dangerous if OTA's are enabled. Some attacks are possible. I have to instead move to custom release keys but this involves fully resetting data and system. Old cm recoveries won't work. TWRP is okay. I built a new cm recovery with the release keys that fully works with my ROM. Will everyone of you be okay with a wipe in the future?

I also planned on releasing two types of builds but I decided against this as I don't have time to spare for such frequent builds.
[E 2015 Android Development] Sher1234:
It not a problem with me as whenever you provide an update i test all the roms released over the week and then back to LineageOS with IMS

& But which sort of 2 builds you were planning to release earlier (every week)?
[E 2015 Android Development] vnai:
I thought about releasing one with test-keys for people who can't reset their data and one with release keys for people who are willing to. But I decided that it is too much hassle because I have to fully clean my build environment when I change signing keys. This increases my build times by a huge margin.
[E 2015 Android Development] vnai:
The reset will be a one time affair. Once you move to builds with release keys you need not reset it agian and can directly apply updates.
[E 2015 Android Development] vnai:
All users who continuously use my ROM. Please vote in the poll here.

https://www.strawpoll.me/12161623
[E 2015 Android Development] SoloRazr:
I am cool with it. ?
[E 2015 Android Development] fastbootflash:
the new build is really smooth. Thanks [MENTION=7963704]vnai[/MENTION].
[E 2015 Android Development] satyamsaudai:
Is Themes present now?
[E 2015 Android Development] vnai:
Surprise news:

Upstream LineageOS maintainer has just now added back VoLTE support to the official builds. The official builds when released will probably come with VoLTE support reducing the need for this ROM to exist.

I will hold back on my move to release keys till atleast the first official builds start and then decide about the future of this ROM.
[E 2015 Android Development] vnai:
In the mean time a new build

https://github.com/vishnunaini/lineage-surnia-releases/releases/tag/20170120

Changelog:

All pre-installed app dex executables are now compiled as Position Independent Code to protect against ROP exploits.

sha256: c19ae91abbe900c18fe9cf83fe122181c63d4593fb718d0e3e5d63870e4d009c

It still uses test keys for now. A normal update is fine.
[E 2015 Android Development] Sher1234:
Yup seen that commit applied by Alberto97. But the changes that you made specifically to the kernel are good and leads to great battery of about 5:30 sot on 12hr backup

So I would say I'll try the latest LineageOS official & then report which is the best & you should also release LineageOS unofficial but monthly would be great
[E 2015 Android Development] RubenPCA:
Changelog ?
[E 2015 Android Development] battle_hardened:
Changelog is two posts above you.

I still can't believe how smooth this ROM is as my daily driver. You are the man vnai:cowboy:
[E 2015 Android Development] bob babetto:
He sees no sim
[E 2015 Android Development] msandroid121:
true

yes and when whatsapp was installed in cm it showed the use of a custom rom

but now it does not pop up the custom rom message !

great work bro ! ;)
[E 2015 Android Development] artu72:
Is a dirty update fine? (I am on 0115 version)
[E 2015 Android Development] Sher1234:
Yup dirty flash will be fine
[E 2015 Android Development] vnai:
Dirty update from my old ROM's is fine.
[E 2015 Android Development] vnai:
Just built a ROM from the official sources for surnia. It now has VoLTE. People who need OTA updates along with VoLTE can now go back to the official builds.
[E 2015 Android Development] msandroid121:
Link plz?
[E 2015 Android Development] vnai:
If you flash the test unofficial build you will face issues doing OTA updates to the official build because of signing keys. Just wait for the official build. My test build was also incomplete because I disabled a lot of things to make the build compile faster. Not good for others.
[E 2015 Android Development] vnai:
Future builds will not include CM File Manager.

It is utterly broken at the moment and LineageOS developers are also not showing any interest in it. It might be dropped from LineageOS entirely. Use third party alternatives.
[E 2015 Android Development] Soneliem:
I can see why the Devs aren't supporting CM file manager any more. Starting with no root, it looks like that they are trying to make Los safer. And doing a good job with it as well.
[E 2015 Android Development] sonnu0100:
Flashed latest build on xt1526 . Clean flashed with open gapps (pico )

Got some problems

Device booted normally.

Network goes and come at very fast rate (network-no network- network)

At this time i can open setting -more -mobile network .

But can bot change any option as when i select network mode , phone hang .

After some time the device show no sim ,

Can not open mobile network in setting (com.settingg.phone , something like that is stopped , not remember the full name )

Tried this yesterday's night on my daily driver .reverted back to backup (cm14.1unofficial) .

Any solution . Will provide logs when my pc will come from service centre (probably day after tomorrow) .

The same network coming-going also come on cm14.1 but i can select the GLOBAL MODE in setting and the LTE(recom.) But in fhis build it hangs while changing .

Xt1526 is cdma varaint , so by default it has LTE/cdma selected in network mode . By changing to global i can change to use gsm sim or lte .

Somebody posted the same problem in CM thread .

https://xdaforums.com/showthread.php?p=70636441

Hit THANKS if somebody help you
[E 2015 Android Development] vnai:
The bug appears to show up the most on the cdma variants but actually appears to a much smaller extent on GSM variants. Please send the logs to my email vishnu[- at -]vishnunaini.com . I tried reproducing on an xt1521 but I hit it very rarely and the logs are no good.

Actually don't give the logs from my build. If possible take the logs while using the official lineageos build that will come out today. The official build will give much better logs than my build.

Send both the general logcat log and the radio log.
[E 2015 Android Development] sonnu0100:
Is this of any use . Posted by other user on cm14.1 thread . Same problem .The user have posted the logs too.

https://xdaforums.com/showthread.php?p=70636441

Hit THANKS if somebody help you
[E 2015 Android Development] vnai:
I Need some details from you guys.

Doesn TWRP on surnia always have the problem of not preserving gapps across OTA updates if device is encrypted?

What is the situation on non-encrypted devices?

Does cm-14.1 recovery always fail to flash gapps, even the small ones like pico and nano ?
[E 2015 Android Development] vnai:
I have new builds ready but recoveries are having a hard time flashing it so I am holding back on releasing it till I do all test cases.
[E 2015 Android Development] ENRIQUEMM:
On my unencrypted xt1524, with squid twrp-surnia-3.0.2-r5.img, making dirty flash always preserves the gapps. Before in official cm was not able to do the updates automatically, always gave error and had to make a dirty flash with wipe cache and dalvik

I just remember that I update automatically, having configured the sd in portable. I currently have it as an intern
[E 2015 Android Development] ayush rao:
Deleted
[E 2015 Android Development] vnai:
I am well aware of that. addon.d functionality is broken on twrp on encrypted devices.
[E 2015 Android Development] ayush rao:
Oh re-read ur post again and really understood what u meant. I'm sorry I won't be of much help, I don't encrypt my device.
[E 2015 Android Development] vnai:
Finally after 4 hours Fixed cm-14.1 recovery's refusal to flash any gapps. But gapps preservation across OTA's on encrypted devices is still broken in both twrp and cm-14.1 recovery.
[E 2015 Android Development] :
I've had no trouble with gapps preservation without using encryption. Here are some logs from your 1/20 build from my Boost Mobile XT1526 with LTE not working. Ever since 1/18 any ROMs with what ever was committed for VoLTE I assume, have the same problem.
[E 2015 Android Development] vnai:
I looked into the logs but they don't say much. There are actually reported LTE networking switching issues all across the board on CDMA msm8916 devices using Lineage. There is a bug somewhere in the core networking code but I can't pinpoint the bug. The logs everyone is sending me are entirely for different bugs that were caused by the one bug that wasn't logged well. This is not a NullPointerException or an IllegalStateException where the fixes could be trivial. I have to do full gdb debugging but my GSM XT1521 phone is not showing this bug at all for me catch it. It appears to be only a problem on CDMA devices.

So CDMA users should be careful while using this ROM. For now I have reverted the ROM link on the main post back to the 0118 one.
[E 2015 Android Development] battle_hardened:
Official LineageOS 14.1 is up for download now
[E 2015 Android Development] K.I.R.K:
dirty flash failed :crying:
[E 2015 Android Development] Sid32:
Wait for experimental build.
[E 2015 Android Development] Sher1234:
Experimental build will not be released for surnia so clean flash lineage build
[E 2015 Android Development] battle_hardened:
That was to be expected, hopefully you have a backup:fingers-crossed:

I did a backup with titanium backup, then clean flashed, flashed gapps, fire kernel, supersu, then boot and restore with titanium backup. So far it runs smooth, only the stock calendar app crashes but I use a third party app anyway.:cool:

Edit: camera doesn't focus on tapping :(
[E 2015 Android Development] riccardosimo:
Where? :eek: gimme the link please :(
[E 2015 Android Development] Adi-ct:
usual place for LineageOS: https://download.lineageos.org/surnia
[E 2015 Android Development] K.I.R.K:
https://download.lineageos.org/surnia
[E 2015 Android Development] noogi:
Surnia - only Moto without experimental ROM, Why?
[E 2015 Android Development] msandroid121:
No official forum ??
[E 2015 Android Development] vnai:
Experimental ROMS were withdrawn for all moto msm8916 devices because the permissions cannot be safely migrated over without making the telephony blob crash.
[E 2015 Android Development] vnai:
New release

Changelog:

*Increased the max possible device volume by 10%.

*Updated Spanish and Portuguese translations.

*Providing a separate root addon and removal zip.

*CM File Manager removed for stability reasons.

*Kernel Security fixes.

*Disallow background clipboard access by default

*Disable bluetooth as first install default. Can be enabled later.

*Multiple stability fixes in the settings app.

*Disabled unprivileged ptrace by default.

If you use gapps, Always flash gapps immediately after flashing an update or else gapps wont be preserved.

Root Addon:

Flash the root addon zip using your recovery. TWRP is recommended. Removal zip is also available.

Links:

https://github.com/vishnunaini/lineage-surnia-releases/releases/tag/20170126

https://github.com/vishnunaini/line...neage-14.1-20170126-17-vishnunaini-surnia.zip

Su addon:

https://github.com/vishnunaini/line...leases/download/20170126/root-addonsu-arm.zip

Su removal addon:

https://github.com/vishnunaini/line...ownload/20170126/root-addonsu-removal-arm.zip

If you use my ROM, do not use the SU addon from official lineaeos website. If you use my ROM, you have to use the addon provided by me because the signing keys are different.
[E 2015 Android Development] vnai:
CDMA users should try to avoid this ROM as I couldn't fix the reported network switching issues yet. No problems for GSM and GSM-LTE users.
[E 2015 Android Development] Prashanth_tester:
a small gripe if you will vnai: when the phone is charging, the quick tile for the battery(with the charging symbol) is quite pixelated like a small image enlarged. Is there any way to fix this?
[E 2015 Android Development] Sher1234:
Thanks

Tried the official LineageOS on XT1521 I ended up having worst battery & performance which i have never encountered on your build, so i was hoping for your build
[E 2015 Android Development] vnai:
I can try but I have to find out where the code for that particular component of android is. These low level images are not stored as image files but instead stored as constant arrays of manually entered data directly in the source code so that low level code can easily display it. Finding stuff without knowing where they are is hard. I will try but no guarantees.
[E 2015 Android Development] rootingguide:
I have flashed this build and the su addon and i still have no superuser. I did it twice. I did clean flash. Cold it be something on my side? Anyway this ROM is great and i`m just gonna use it with phh superuser which works :P
[E 2015 Android Development] vnai:
Some misbehaviour exists with the root addon because my build is a user build for security reasons. It does not have any debug options and selinux rules are stricter than what the official build enforces(official build is a userdebug build). I will not be downgrading any security functionality for personal reasons. If necessary install third party root utilities instead of the addon I have provided.

If everyone is reporting that the addon does not work I will stop providing the addon in future builds.
[E 2015 Android Development] SoloRazr:
Can I do dirty flash to the latest build or need to do it clean?
[E 2015 Android Development] vnai:
Dirty is okay.
[Galaxy S 4 Q&A, Help & Troubleshooting] spyroz540:
Hi, I have a Galaxy S4 i9505 running TWRP 3.0.2-0 jfltexx. I am having a problem where TWRP won't boot up when using the key combination of Volume UP + Home + Power, it will show up with the Galaxy S4 screen then at the top left corner it will show kernel not seandroid enforcing, recovery booting. Then it will boot to a black screen and then after 3 seconds it will vibrate and boot into android like it normally does. However on Flashify (Android App for flashing) I click the 'Reboot to Recovery' Button it boots into TWRP and it runs like a charm.

Android is running completely fine, stock 5.0.1.

Help will be appreciated.

UPDATE : SOLVED, Thanks to [MENTION=5502148]QueryVillain[/MENTION]

Solution :

1) Volume up + Power button while device is off

2) As soon as you see something in upper left corner, release both buttons and you will be booted to recovery