yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] PriPhaze:
April's Fool Rom? Cuz i bootlooped :v

Dammit i hate this day haha maybe its just me

EDIT: Alright i was being paranoic :) the updated is good and i finally boot succesfully
[E 2015 Original Android Development] PimpMy5Ton:
For some reason OTA not working, is this known already??
[E 2015 Original Android Development] :
Just tried the new build, rather dissapointed.

cLock not working, only displaying the digital clock, no weather displayed (using yahoo or open weather map server)

Error in weather setting main settings menu (no weather service installed-but there is) you tube freezes.

Random freezing in setting menu or setting sub menu ie like sound/notifications.

Overall not what I expected, although I'm flitting between RR, AICP and CM13 at the moment, the 01/04 official nightly of CM13 is broken so gave me an opportunity to give this latest RR a whirl.

Edit

I had an xposed module installed, an android N module that gives setting subtitles, have uninstalled that just to see if makes a difference and I'm afraid its no different.
[E 2015 Original Android Development] dandrumheller:
Not seeing issues with weather here. Dirty flash over previous build, including xposed, and convert to hybrid SD storage. Have not run into any errors yet, other than systemui crash initially on first boot. Has not recurred.
[E 2015 Original Android Development] :
Strange, after a full wipe and reflash, all good now, maybe my original flash was too dirty?

Must remember some soap next time ! :D
[E 2015 Original Android Development] Alisson Nasc:
the surnia rom is compatible with Squid Kernel for the 2015 Moto E LTE?
[E 2015 Original Android Development] PimpMy5Ton:
I use Inazuma_Kernel_Surnia_R3 with Resurrection Remix, I love the usb fast charge feature, it's the best :p
[E 2015 Original Android Development] :
I'll have a look at that :)
[E 2015 Original Android Development] ayush rao:
How does the fast charging work. I just flashed it on my phone but now I have second thoughts cause my dad won't buy me a new phone till I'm 16. I hope someone could explain how it works and will it damage my phone
[E 2015 Original Android Development] scohut:
Still loving this rom and new build seems great so far, there's one thing that has me puzzled though. I'm trying to use the selinux plugin with kernal audiutor and it doesn't seem to stick, or set permissive on boot. Can someone tell me what I may not be doing right? I've never used the kernal helper before trying this rom.
[E 2015 Original Android Development] :
I'm trying to find some info for you, but there isn't Much around, I can only assume that if surnia is plugged in laptop/PC via USB, it charges faster, but then there must be a thermal issue here?

I'll continue searching, I like you am curious/a little excited.......

Not that excited, just an expression!!! :D

After the 01/04 issue with CM13, I've decided to have a play with some other ROMs, RR being the first, I want to test some lollipop ROMs too, my XT1524 has never had a custom lollipop ROM installed, I'm interested to compare 5.1.1 ROMs with 6.0.1
[E 2015 Original Android Development] ayush rao:
Well I'm worried (Though I knw I shouldn't be), so I'm back on squids kernel if u find out something do let me know

Thanks!
[E 2015 Original Android Development] :
Don't be worried! Its fine now you gone back to squid kernel :)
[E 2015 Original Android Development] PseudoDev:
Is it me or this ROM for some reason gives me unconditional lags.. I mean it lags a lot. Any help? Is it the GApps? Do I need to use another version ???
[E 2015 Original Android Development] Silent Visitor:
I'm using the Pico GApps

I didn't get any lags sir

Might be its u not the ROM[emoji6] [emoji6]
[E 2015 Original Android Development] MarquesYOLO:
I'm using Pico OpenGapps too and I'm also feeling some lag. It's not the smoothest Rom available but it works well.

I have a question, is there a way to get 2 pages in quick settings like all the other roms? I prefer a smaller QS panel and I don't know how to "activate" the option. Thanks in advance.
[E 2015 Original Android Development] Silent Visitor:
I guess that option has been removed

Another problem I encountered for the second time was when I flashed this ROM after everything when I looked up to all apps I just found SuperSu missing. Had to install it again.

Did anyone else face this one??
[E 2015 Original Android Development] scohut:
SuperSu was missing for me too. I ended up doing a clean install and then it was there. It's not too painful for me to clean install anyway so I didn't mind.

Hey Silent Visitor you wouldn't happen to be able to answer my question from page 44 about the selinux plugin for Kernal Audiutor to set permissive automatically on boot would you? I don't know anything about tweaking the kernal (nor do I care at all normally) but just wonder if I'm doing it right. It's not really that big a deal though, just a couple clicks to get to misc/selinux option anyway.
[E 2015 Original Android Development] Silent Visitor:
My friend !! Even I too don't know that thing

Never done it before nor use kernel audiutor at all

Sorry bud ?
[E 2015 Original Android Development] scohut:
Ya the only reason I need to set to permissive is I ended up using Viper, audio fx just didn't do it for me.

Are you on Androidforums by any chance SV? My name is scoson over there.
[E 2015 Original Android Development] Silent Visitor:
Nope bud I'm only on Moto E 2015 section

Even viper and audio fx didn't do for me!!
[E 2015 Original Android Development] ayush rao:
U can get audio fx to work by a quick build.prop edit
[E 2015 Original Android Development] PriPhaze:
I don't know which version of Viper4android you are using but I'm Using the Viper +Atmos and works flawlessly.

You don´t even need to switch between Permissive or enforcing Selinux.

Mine is on enforcing all the time and it works like i said.
[E 2015 Original Android Development] Alisson Nasc:
why my card of memory appears with such a strange nomenclature do I eat that of the annexed image?
[E 2015 Original Android Development] klingon888:
Bug found - latest release of FW, clean install with full wipe of data, system, cache, dalvik - Slightly different issue than the first bug I reported with the phone app crashing. That bug was fixed with latest release and I'm now able to swipe left on Call History without app crashing. But now another bug - Open phone dialer, click on Call History, tap on any caller in the history (somewhere in the middle). Phone app will crash. Rebooted phone and still same.
[E 2015 Original Android Development] PseudoDev:
Themes crash for me
[E 2015 Original Android Development] Android_noob17:
Logs or it didn't happen
[E 2015 Original Android Development] :
#ResurrectionRemix - v5.6.7- 20160409

Changelog :

- Android 6.0.1- r24

- Add 5 RR 1 PB header logo

- Update taskmanager switch button

- Add Heads-up button in the extended statusbar

- SystemUI: Fix Dual Tiles Qs Color Switch Text

- Revert Restart System UI on theme Change and NP color switch

- Heads Up Snooze

- Fix low battery warning level

- 2 more SB Custom logos

- HeadsUp: add timeout option

- Reverted clock second (Avoid to lag issues)

- Fix Applying Notification Colors To Light StatusBar Background

- Tune up dexopt dialog

- Settings: Make Most RR settings Searchable

- DevelopmentSettings: Synchronize USB connection data state

- Lockscreen : Fix bottom area visibility

- media: Add flags, channelMask, and UID to audio session callbacks

- audio: Don't play sound effects if stream is muted

- SystemUI: show visualizer in shade-locked view

- Bugfixes for systemUI

- Fix location tile not showing in the keyguard

- NetworkManagement: Add ability to restrict app WiFi background data access

- SystemUI: ensure volume record exists before showing notification

- MountService: ensure VolumeRecord with UUID exists before modifying

- Implement left swipe on lockscreen

- Framework changes for resetting data usage statistics

- LLS: Use window attachment callbacks

- SysUI: Add event logs for live lock screen interactions

- Fix battery stats helper derp

- Update ambientsdk version 1.5.2

- Add Weather Content Provider

- Add state member to WeatherLocation class

- Reset timer when a new weather service provider is selected

- Force Heads up in all applications

- Add system property to control config_enableAutoPowerModes

- SysUI/LLS: Slide panel out when collapse called

- QS:Re Add LS Tile and Adapt to AOSP panel

- translation imports

- For more info Track Github Activities

Downloadhttps://www.androidfilehost.com/?fid=24459283995316773
[E 2015 Original Android Development] KazuDante:
[MENTION=4910973]Vatsal[/MENTION] Otus link is missing...or was it still in the works?
[E 2015 Original Android Development] zeeshanhussain12:
Otus update 5.6.7

Download:- https://www.androidfilehost.com/?fid=24459283995317144

Changelog:- http://hastebin.com/nejitifofe.vhdl
[E 2015 Original Android Development] KazuDante:
Thank You
[E 2015 Original Android Development] Joel Oliveira:
Moto E2 Otus , since the stock 5.0.1 has a problem with Snapchat , shooting with the snap , the phone restarts . However the Otus XT1511 received the android 5.1, and this problem with Snapchat was resolved. I would like to fix this problem in the RR ? .... Sorry for my English , I used google translator . I'm from Brazil .Thank you very much in advance!
[E 2015 Original Android Development] Jandus:
Encryption crashing?

Greetings!

Have 3 different Moto Es (XT1526) that all use RR now (5.6.7) - superb ROM. Love it. :)

Have noticed one rather major problem with all my devices. When I wipe clean and flash the ROM, install gapps, then go in and try to encrypt the phone, it restarts and sits at 0% then after a minute or two pops up the error box "Unfortunately, the phone has stopped." Happens on all 3 of my devices.

I can reboot and use the device normally even after the error message so it hasn't even started encrypting me thinks.

Anyone else have this issue? Workarounds? Need any other info?

Thanks!

Jandus
[E 2015 Original Android Development] :
Resurrection Remix v5.6.7 #Changelog

It's still v5.6.7 just builds rolling out with fix for few minor issues

Changelog :-

Audio FX From cos13

Fix Secure LockScreen On Icoming Call

Point Amibent display tile longpress action to it's own settings

SystemUI: fix double tab launching custom lockscreen icon

Lockscreen : Fix dead-zone in bottom area

Incorrect evictor key in TokenCache

SystemUI: add closed all tasks event log

SystemUI: add RecentsView EventLogs

SysUI: reset mCanDismissKeyguard in setBarState

Downloadhttps://basketbuild.com/filedl/devs...esurrectionRemix-M-v5.6.7-20160412-surnia.zip
[E 2015 Original Android Development] RubenPCA:
[MENTION=4910973]Vatsal[/MENTION] Thanks For you time for work in this rom, Great ROM !

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------

[/COLOR [MENTION=4910973]Vatsal[/MENTION] http://prntscr.com/arrzno
[E 2015 Original Android Development] abyz12:
[MENTION=645600]vast[/MENTION]al but this link is only for surnia not for otus
[E 2015 Original Android Development] Navin9:
Will Doze mode is working on this rom?
[E 2015 Original Android Development] lbwarped:
Since flashing my Moto E, I've lost my ability to connect to my workplace's wifi. They say that my phone is only trying to obtain an IPv6 address, and the wifi networks only support IPv4, so my phone stays at "Obtaining IP address" for a while and then fails to connect.

I looked through the options (including Developer ones, like using Lollipop's version of DHCP, which didn't work, either). Is there an option to enable IPv4 or disable IPv6 within Marshmallow/RR/CM? A Google search wasn't much help, as most all articles about Android and IPv6 are quite old.
[E 2015 Original Android Development] ReLLiK88:
Just wanted to say that this is a great rom [MENTION=4910973]Vatsal[/MENTION] and I appreciate your work on this device. Right now it's my daily, although at one point I would like to check out AICP and maybe another.
[E 2015 Original Android Development] abyz12:
[MENTION=645600]vast[/MENTION]al I think in RR ROM sound is too low
[E 2015 Original Android Development] Silent Visitor:
Well if you feel so you can try increasing your phone sound too.

But be careful with the tweaks.
[E 2015 Original Android Development] :
How would we do this? I tried the latest build of this a couple of days ago, I was very impressed with the new graphic designs, but the ringtone volume was way too quiet, one reason why I went back to squids CM13, but that has a quiet ringtone too, even at full volume...

Any advice to raise the ringtone/notification volume? I'm sure it was much louder in previous builds?
[E 2015 Original Android Development] Silent Visitor:
[MENTION=4422917]ivan39[/MENTION]

Worked really well for me. Just gave the same tweaks.

Make a Nandroid backup and them give a try!

All the best.

Credits: zhuhang
[E 2015 Original Android Development] scohut:
Anyone know how to make cast work so my Roku stick shows up. Or is cast only supposed to work with Chromecast? AllConnect and Roku app are working pretty crappy for me after just trying again.

And thnx for the volume tip, I also applied it!
[E 2015 Original Android Development] scohut:
After some searching I added this line...

persist.debug.wfd.enable=1

..to build.prop on the bottom and I now have the menu switch to enable wireless displays in cast, and it does find my roku. Shows an icon on status bar when I play phone video in VLC player but not doing anything on the tv. This is just while on home page in Roku. Any suggestions? I'll keep trying for now.

I just tried casting on my gf's phone (a Kyocerra) and it connects and displays right away. Mine just sticks on (connecting) what to do?
[E 2015 Original Android Development] Silent Visitor:
Pleasure brother!!!

??
[E 2015 Original Android Development] abyz12:
Anyone tell me where is 5.6.7 RR build link for otus
[E 2015 Original Android Development] grofweg:
There isn't one?

https://basketbuild.com/devs/resurrectionremix/otus
[E 2015 Original Android Development] zeeshanhussain12:
otus update

download:- https://www.androidfilehost.com/?fid=24499762636001482
[E 2015 Original Android Development] scohut:
I went into a bootloop a couple days ago on surnia (first time ever for me) but it was because of a theme update. That's what recoveries for :) Isolated incident. I love this rom tho and I'm gonna make it my wife! Yes, I'm weird..
[E 2015 Original Android Development] :
So its perfectly acceptable for someone to say this rom has a big enough problem it continually reboots? How is vatsal going to feel when he reads that? Probably something is amiss and not necessarily the ROM, 90 % of these problems can be attributed to installation error or something else(mods themes xposed, ect)

I'm not being high and mighty or pointing an accusing finger, if I was then I humbly apologise for the tone of my post, but surely its better to say "I have a problem and I have reboots" rather than lay the blame at vatsals hard work?

Are any of you following the CM13 thread for surnia?

I suggest you take a look, lots of people have abandoned it because of all the problems it currently has, and I personally have moved from CM13 to this ROM because it does not have the problems the current CM13 has, and I'm grateful to vatsal for that.

If my suggestions or questions really have caused the op and you guys offence then I'm very very sorry, the last thing I want to see is people abandoning this ROM just like people have abandoned CM13 because so many people complain about it being buggy.
[E 2015 Original Android Development] Android_noob17:
I don't think anybody will abandon a rom just because a few builds are buggy. That's the nature of roms (or anything for that matter). But instead of jumping down somebody throat, try helping them out.
[E 2015 Original Android Development] IronTechmonkey:
People should feel free to report problems with the ROM, which is not inherently an insult, in fact that is the point of threads like this.

That being said, reports like "it's buggy" or "it's rebooting a lot" are generally useless without full descriptions and logs.

A proper issue report:

- Will come from a clean flash with no mods whatsoever.

- Will include a thorough description of the steps someone would take to reproduce the issue.

- Will be accompanied by a logcat taken when the issue occurs.

This is not a "free software distribution portal. It is a development thread.
[E 2015 Original Android Development] :
I've apologised for my tone, and I'll apologise again.

If anyone misinterpreted the point I was trying to make, then I'll apologise a third time.

As someone just posted, a vague report of random reboots doesn't help anyone, and I know that myself, I'm no purist or any expert, I've had problems recently with my device and people have been kind enough to help, so if anyone assumed my tone was seemingly to jump down anyone's throat, I was not, I asked the poster about any mods or any changes he made (as anyone would) and I asked about his installation methods because in other surnia threads, its become clear a minority of users have not followed installation instructions and have run into problems, particularly when flashing certain gapps packages.

Please accept my sincere and deepest apologies, my problem is I get far too passionate about these things and may seem bossy or impolite.

I'm trying my hardest to help everyone here and I'm telling the truth when I say I have not had any problems with this latest release of resurrection remix.

I know some with have errors and issues that another person won't but I don't like to see the blame being put squarely on the ROM that all developers work so hard to bring us and enjoy when there are so many other factors to consider when someone has a problem.

I hope this resolves this issue and I can continue to offer any help or advice to anyone however I can.
[E 2015 Original Android Development] ÀnkanKoley:
Moto e otus::

Rom is awesome, every thing is perfect, no lag, only issue is:

lots of reboot while setting up my device :( And after that there is also some random reboot, hard to say for what! No Mod,No extra App, only Open Nano Gaap And RR Latest :(

Had to switch back to mokee again.
[E 2015 Original Android Development] :
That's exactly what I was referring to in my last post, and I am going to ask a question.....

How do you install your gapps package?

There were lots of issues recently with CM13 where people using certain open gapps packages were facing lots of reboots during set up.

It was made clear in the CM13 thread that some open gapps package had an issues with some builds, especially cm13.

One person then commented that in twrp he had flashed the ROM, rebooted into android then rebooted back into twrp and flashed his gapps package, and couldn't work out why he was getting reboots......

I'm only asking this because some people have since admitted to this incorrect procedure to install gapps, I'm not accusing you of incorrect flashing either, but the question needs asking to eliminate that possible promlem!

I'm also not saying that's the reason for your reboots, but its a possibility if you have not flashed the ROM and gapps at the same time, one after the other.....

I can suggest you change the gapps package you use, I personally use A gapps pico, search Google apps minimal here on xda, if that interests you.......

I personally have never had any reboots with this build or with CM13, while many other users complained about this issue!

If you dirty flashed this ROM, try wiping system/data/internal storage in twrp and clean flash the ROM, I know you will lose user data but I must make the point to you and everyone, I have a much better and far more stable device when I clean flash.
[E 2015 Original Android Development] ÀnkanKoley:
yes i did a clean install, and flashed the gapps and rr together.

I too madly want to use this rom as my daily driver.
[E 2015 Original Android Development] sirhc:
I'm no wizard but reboots are most likely coming from the new LiveDisplay api. I've had this same issue due to a bad merge and had to fix it myself
[E 2015 Original Android Development] IronTechmonkey:
That is a reasonable guess (in the absence of logs and full descriptions from people who are reporting issues). Live Display did recently get an overhaul which seemed to have left some issues. For what this is worth: In Otus CM13 it has caused FCs or just failed to make the change when attempting to toggle mode from Live Display QT. As mentioned by dev squid2 in this post from the Otus CM13 thread: http://xdaforums.com/showpost.php?p=66451841&postcount=768 it may be fixed by the commit(s) referenced in that post. direct link to referenced commit(s) here: http://review.cyanogenmod.org/#/c/140832/. Eventually that should make its way into RR.

---------- Post added at 02:24 AM ---------- Previous post was at 02:20 AM ----------

Well then remember to give it foot massages and ask it "Honey, how was your day?" :silly:
[E 2015 Original Android Development] ÀnkanKoley:
How to fix?
[E 2015 Original Android Development] IronTechmonkey:
Merely stating that the ROM is rebooting, and then asking when it will be fixed is just not helpful to yourself or others. Another term for "random reboots" is "troubleshooting that has not been done yet". Please Read the thread and provide proper bug reports as described just a few posts before you reported that you were having a problem, or wait for the a version of the ROM containing the commit that was referenced immediately before your most recent post. I wrote the following for you yesterday but did not post it because I did not want to seem like a nag, however it seems like stuff you need to know as this is SOP for bug reporting:

As described very recently in this thread as well as countless other places, a proper issue report...

- Will come from a clean flash with no mods whatsoever.

- Will include a thorough description of the exact steps someone else would take to reproduce the issue.

- Will be accompanied by a logcat taken when the issue occurs.

In following this bug reporting work-flow you would want to start by providing more specific details

- What device (brand, model)?

- Exactly what version of which recovery are you using.

- Name/Version of ROM flashed (exact filename of installer zip).

- Name/version of Gapps package (flashed exact filename of installer zip).

- What actions were being taken just before it rebooted while you were configuring it.

- What was the last app being used before a "random" reboots?

- Try to log the issue. You could log it via adb from a computer command prompt and let the log run until a reboot occurs then stop the log and save the buffer to a file. There are other ways to have the log write directly to a file.

- Even if you cannot capture a log of problem via ADB, install a logging app (eg catlog) and capture a log while you configure the system. Even if it does not catch the error there is still a chance that something in the log might be helpful.

Also, it could not hurt to review what would be considered a squeaky clean ROM flash. Some of these steps may seem excessive but it is better to be thorough and review all steps when dealing with issues:

- Power off the device.

- Boot to recovery from a powered down state (not reboot from ROM to recovery)

- Wipe dalvik and system cache.

- Factory reset.

- Flash ROM and most recent version of open gapps.(recommend Open Gapps pico or nano)

- Wipe dalvik and system cache again.

- Do not flash anything else whatsoever.

- Reboot to system.

- Go through the initial setup and let the device sit unused a few minutes to scan for media etc.

- Reboot the device.

- Install logcat app on the device and start logging before you continue configuring the device so you might be able to capture any errors. Even if you don't capture errors, such a log might be helpful.

- Methodically proceed with your settings changes and installation of apps incrementally, pausing frequently to test the device for a while.

- If you encounter a problem try to reproduce it intentionally and log it.