yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] molonad:
hi in this rom is not implemented outdoor mode in live display ? for me little important , i cant see screen when is bright sunnlight outdoor :( very dissapointing for me :(
[ONE Original Android Development] Arrjaan:
It is implemented, see settings--> display
[ONE Original Android Development] FloorFox:
Hey guys

I am getting this 1013 and android system wakelocks. I clean installed 27th April build. I can get 5 hours max with browsing and whatsapp only. Help someone :(
[ONE Original Android Development] molonad:
For me it was invisible in settings, post me pls screenshot Where it is, i cant see it in live display
[ONE Original Android Development] Zephyr!:
[MENTION=4388175]xperia<3[/MENTION] elaborate the 1013 wakelock and post ss
[ONE Original Android Development] FloorFox:
Audiomix
[ONE Original Android Development] Zephyr!:
Block it using Wakelock blocker.
[ONE Original Android Development] DrNinjaa:
[QUOTE=xperia

Disable ur touch sounds and lockscreen lock and unlock sound. Disabling it sometimes causes pausing of the audio when u listen to music with screen off.

#HappyFlashing#
[ONE Original Android Development] rrohanjs:
Does live display drain more battery than normal? If yes then approximately how much % more?
[ONE Original Android Development] ogrillion:
So I really like this ROM..

I been trying most of the Lollipop roms because I been having tons of battery drain from Android System. And on this ROM for like this first time ever Android System is so low on the list, and even in GSAM its not at the top..!

And the battery life has been great all last night and all day.. However all of a sudden now I noticed my battery draining rapidly. I had to install BetterBatteryStats because GSAM just would show Android OS for the wakelock but no actual details.

Betterbatterystats shows under Kernel Wakelocks a "AlarmTimer" keeping my device up constantly. The only thing that changed was GSAM was updated, so I uninstalled that.. Rebooted.. Still have this wakelock.

I turned off WiFi thinking maybe because I am at work thats causing it, but no.. My latest test is reflashing the ROM, wiping cache / dalvik and seeing if it stops.

Has anyone ever have had this before?

**Edit** also its not listed under the wakeup blocker

**Edit 2** Incase anyone has a similar issue that I just did, it seems it was caused by GSAM Battery the root companion. They just updated it and thats when I started getting the wakelock. Just uninstalling it didn't get rid of it, and dirty flashing the ROM didn't fix it either. I had to dirty flash and wipe cache / dalvik then the wakelock stopped appearing.. Odd didn't realize an app like that could cause an android OS wakelock.
[ONE Original Android Development] Ucarty:
Smooth sailing on 5.1. Great work!

Looking forward to missing Exodus features. (The updater, Settings integrated SU)

Is there a reason you took the experimental down again?
[ONE Original Android Development] L0X0R:
They haven't released 5.1 yet. experimental wasn't for us to use in the first place. Just let them finish the rom.

People kept downloading it and wondering why this and that doesn't work on an 'experimental' build. I wonder why they took it down. /s
[ONE Original Android Development] Ucarty:
Agreed. Letting them finish the rom in peace with as much user testing as they themselves choose sounds like a great idea. Was hoping to maybe find an automatic build system however. I rather enjoy nightlies.

I will consider myself lucky in this case and see if I will continue to find no reason for this to be labeled experimental.

Thanks for the clarification, I thought Martin meant the curious were supposed to find the experimental, or at least that this wouldn't be a problem.

Again good luck to the devs!
[ONE Original Android Development] L0X0R:
Ye totally. I can't wait for proper release either.

I'm mostly referring to the google+ community in that frustrated vent :P

Some people were trying to submit bugs for an experimental build of the rom that isn't finished at all. Obviously they aren't taking bug reports for it. So complaining about something you're not even meant to have is just kinda annoying :P
[ONE Original Android Development] critofur:
Can't find the built in Xposed installler? "Per App" kernel settings?

Just trying this ROM for the first time now as I was really excited to read about the built in Xposed installer . I've been anxious to find a ROM that works well with Xposed so I can finally try Amplify. (It pisses me off so much that Google does not include something like Amplify BEFORE adding gobs of wakelocks to our phones!).

Would also like to know what will be the best way to have "Per App" kernel settings with this ROM so that I can limit the CPU usage of certain CPU hog/battery draining apps? Will I need a custom kernel, or can I use the one that comes with Exodus [latest 5.0.2 version from 5/11/2015]?

Thank you - excited to try your ROM after finding that every single 5.1.x ROM I've tried to have one problem or another...

:good:

EDIT: Also, how do you get updates for the Host blocker? I did not see any sub menu for Host blocker, clicking it just toggles it on/off.

---------- Post added at 01:17 PM ---------- Previous post was at 12:34 PM ----------

Unfortunately, ,Google Play Store has stopped.

:crying:

Damn. Can I not use 400 DPI with this ROM? Should I switch to 408? Should I get a log and post it? It's funny, I got this error when I clicked the link to XDA under the notes for Amplify app on Play Store, as soon as I install Xposed, nobody will want to help with errors like this I guess... (I have not installed Xposed yet, but my reason for trying this ROM is because I read it came with a built-in Xposed installer).
[ONE Original Android Development] return.of.octobot:
exodus-5.1-20150507-UNOFFICIAL-bacon

I've created a mirror for the 20150507 Experimental 5.1 build, but it seems as though I am too noobish to be allowed to link to it. If anyone is interested let me know, maybe you can post it for me. Or you could just repremand me for trying to link to a build that was removed by the developers, which ever floats your boat.
[ONE Original Android Development] Heisenberg:
Did you actually get permission from the dev to post a mirror? You usually need permission from them to do that. They removed it for a reason.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] return.of.octobot:
No, I did not and I doubt I would be able to acquire such permission, as you said they took it down for a reason, although I think the bulk of that reason involved users not understanding what 'experimental build' means. As far as the ROM itself, from my experience it seems to be running without a hiccup.

With that said, this IS the internet and once you put something out there it stays out there. However, I understand why you feel it would be considered inappropriate to post the mirror here.
[ONE Original Android Development] Heisenberg:
Just contact Martin and see if he has a problem with you posting a mirror, if not then I say go for it.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] return.of.octobot:
Will do, I'll shoot him a message and if the results are favorable, I'll clear it with you as well.
[ONE Original Android Development] Heisenberg:
No need to clear it with me mate, I'm just offering some advice (I'm just a regular member here), it's completely up to Martin.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] return.of.octobot:
Roger that, I guess I just figured what with you being a moderator and all. Anyway, request submitted, we shall see how it goes.
[ONE Original Android Development] strange1712:
I would rather ask why would you want to mirror such build. It's been explained already it was just to test the build server, otherwise it's CM12.1 nightly from that date, not really an "exodus experimental build".
[ONE Original Android Development] critofur:
I need a recommendation as to which kernel I should try, with this ROM, in order to have "per app" settings?

I tried using Synapse with the included kernel, notice it is not supported...
[ONE Original Android Development] Heisenberg:
While I am a moderator I'm not a moderator in this section. Just another dude who loves Android.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
Your just like us after all ey man? :p
[ONE Original Android Development] Heisenberg:
Just another one of the guys.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
One of the guys.. plus a shiny coat. :P

The coat of moderation :P
[ONE Original Android Development] _ASSASSIN_:
It's just timaa except with Bryan Cranston staring you down ;)
[ONE Original Android Development] Heisenberg:
I got rid of timmaaa, he's in a barrel in the desert.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
Or was he in a bathtub.. :p
[ONE Original Android Development] Gamm86:
Franco R42 in combination with his FK Updater app.
[ONE Original Android Development] ngocmyan:
any news about update please ?:D
[ONE Original Android Development] L0X0R:
Wait. That's the only news you're gonna get.
[ONE Original Android Development] Gamm86:
Be patient. Keep an eye out on the following folder:

http://www.vanir-exodus.net/experimental/

They are surely working on a new version.
[ONE Original Android Development] beany>:
I feel compelled to say something to those reading .

Flashing something you find without official release may contain an element of risk, so only do so if you know what you are doing and don't cry for help if you have problems.

That is all.
[ONE Original Android Development] Gamm86:
I totally understand your point of view, trust me! :)

Nonetheless, I still have to come across the first OPO that became fully bricked after flashing a zip, regardless of what was being flashed in the first place. ;)

I see no harm in flashing something to test it out. There are plenty of ways to restore your phone to the point before you started "messing" around.

Imo, if you cannot restore your phone (using recovery, adb or fastboot) after having flashed a bad, corrupted or unsupported file for your proper device, then what are you doing on XDA in the first place. :p

Now, after rereading my previous sentence, a better warning would be; If you're incapable of doing what I previously said, then wait for official releases. :o
[ONE Original Android Development] beany>:
Agreed; many hunt these experimental and test builds and don't seem to realise there's a reason they aren't official, but as long as you know what you are doing there should be no problem. OPO has brought many people here that treat it like a free sweet shop and then expect others to sort their problems and also blame the ROM :)
[ONE Original Android Development] Ucarty:
Does 'most likely broken' mean, it's actually better than the last version, but still very off-limits to those who don't know what they're doing?
[ONE Original Android Development] Arrjaan:
No, it does mean that it is most likely broken and will not work properly ;) For 99% here it is best to only use official releases and not the experimental builds, unless you want to take a peek. But experimental builds are not meant to use as your daily rom.
[ONE Original Android Development] L0X0R:
Hey [MENTION=4429892]Martin_Ro[/MENTION] and team.

I saw a new update to the touchscreen issues at their commit review page.

Just wondering if this will be included in 5.1 when we get it? as I just checked and I have the tpk screen as well. I've had some touch screen issues. But not enough to RMA over.

Just keen on getting this loaded, as I don't want to swap to 12.1 and would rather stay on this rom.

Just wanted to mention it. Thanks =]
[ONE Original Android Development] Martin_Ro:
If cm applies it, we will too, as we use their kernel and devicetree as base.

Regarding the experimentals:

This is my personal download-folder to download the testbuilds from the Build-Server.

It's named "most likely broken" because it's exactly most likely that: Broken.

Also it's not for the OPO as I develope on a shamu, so trying to flash this on your OPO will not work anyway ;)
[ONE Original Android Development] Zephyr!:
Kernel supports multi rom? Just eager to know because I want to give a try to multi rom. But I don't want try any other custom kernels after seeing this one's awesome performance and battery life.
[ONE Original Android Development] Airlibik:
sry for the noob question but I didn't find nothing about it...

Is there a way to enable incoming call in heads up window? I didn't find the option to enable it
[ONE Original Android Development] Daedulus Minion:
I don't think it's there yet. Maybe possible infuture if the dev wants it.
[ONE Original Android Development] rrohanjs:
+1, would like to know this too .. multirom app says it has the required patch but has anyone tried it ?
[ONE Original Android Development] return.of.octobot:
Yes, the stock Exodus kernel does support MultiROM, they weren't lying to you.

I wouldn't be so quick to write off custom kernels though. They're not for everyone, but if you know what you're doing then custom kernels, AK in my case, allow you infinitely more flexibility then the magical stock kernel is capable of. Thus, if you're proficient in tuning kernels then you could just as easily configure a custom kernel to behave identically to the Exodus stock, and you can then go above and beyond that and optimize it further based on your own personal needs.
[ONE Original Android Development] navinthomas:
Double Tap bug?

Is it gone permanently?

I have had this EXACT same issue in CM 11S (44S). I couldn't live without the Double Tap to Wake feature. So instead I started to keep the screen facing away from the thigh (which is a bit unsafe and feels somewhat weird) whenever I keep the phone in my jeans pocket. I kept doing this till now so I have no idea whether the issue was solved in any of the subsequent updates (05Q) or in COS 12. After seeing your post I checked whether this issue exists with Exodus. Turns out that it does :(. The 'prevent accidental wake-up' option was already switched on. Tried turning it on/off. No effect. Also checked disabling the wake-up option for home button. I have no idea what this option actually does or is supposed to do. It doesn't wake up the device when I press home button. Anyway, disabling/enabling it had no effect on the issue. :crying:

I was hoping someone here has a solution for this.
[ONE Original Android Development] badagaio:
Well, solved the problem by switching my ROM. Exodus was fine but with a few strange bugs that made me change my mind.
[ONE Original Android Development] navinthomas:
Which ROM?

and what strange bugs?
[ONE Original Android Development] rrohanjs:
I faced the issue on other roms also, so what I do is i turn off dt2w when I'm out like wearing jeans or shorts but I'm adjusting to it cuz I keep tapping the screen to turn it on and then I realize I turned it off lol.. Keeping the screen facing outward is tooo risky for me and yes it feels weird.. And no one seems to have a solution to it because the proximity sensor option clearly doesn't work with dt2w
[ONE Original Android Development] navinthomas:
The proximity sensor does work. Try enabling it and keep a finger over the sensor. You will see that double tap won't work. In removing the finger it will work.

The real cause of our problem is something else I believe. The problem arises in only one of my jeans, not all of them. I guess it's related to how tight the pocket is. As far as I noticed, the chances of the issue appearing increases if the pocket is tight.

---> Sent from my awesome Bacon using the XDA Free mobile app
[ONE Original Android Development] jayOOMjay:
[MENTION=4429892]Martin_Ro[/MENTION]

Assuming that you guys are working on 5.1.1, i would like to bring this to your attention.

I have tried some 5.1.1 roms in all of them, i noticed delay in getting push notifications. To be specific , take the case of whatsapp, consider the phone has been in deep sleep for the last few hours with data on. only after when i open whatsapp i get the messages all together at that instant but if i check the time stamp of each message , the time that was sent is some hours or minutes ago.

i reported this in the respective rom's thread, there were people experiencing same issue, the funny fact is only when they heard about this some of them checked and confirmed.

Since you are taking time in releasing the rom i suppose you like to deliver only quality output so if possible, can you check this issue while testing ? I feel like this is something introduced in 5.1.1

[i used stock settings for all the roms i have tested, no custom kernel, no greenify or anything like that, network was perfect ]
[ONE Original Android Development] drnizeguy:
[MENTION=5034103]jayOOMjay[/MENTION]

There is a problem with the wifi on the OPO and some routers. On some routers, when the phone is in deep sleep, the connection will be turned off, even if 'always on' is enabled in the advanced WiFi settings.

I have this problem and that's the reason I'm on this ROM because it is 5.0.2

It is a combination of the 5.1.x and the router. I have 5 routers, only 3 have the problem.

If you're not on WiFi but on mobile data, then you have a different kind of problem.
[ONE Original Android Development] jayOOMjay:
Yes,today I just switched from 5.1.1 to this one , because it is 5.0.2.

I got a similar replies from others saying to turn ipv6 off in router configuration but first of all im using hotspot from my laptop so there are no options to do that.

also i use both wifi(home) and mobile data(office). in both cases i have this delayed notifications. not sure if wifi is a factor but there must be some other factors too (heart beat time out?). It would be better if a developer can address this issue.:confused:

btw. what is your configuration with exodus? kernel ? firmware? kernel profile ?
[ONE Original Android Development] drnizeguy:
Well, this topic suggests a fix, you could try it. I didn't try it, I'm sticking to this ROM because it runs flawless and I don't have any problems.

I'm on latest firmware (with the touchscreen fix) and AK kernel with a -60mV under volt.
[ONE Original Android Development] avinashadvani:
What is the latest firmware? And the touchscreen fix I'm very interested in..
[ONE Original Android Development] drnizeguy:
http://www.slimdevs.com/bacon_firmware_update_2015_05-15.zip this is the new firmware with touchscreen issue fix extracted from the cm nightlies. This is with the oxygen modem so it could be be, when flashing a cm12 ROM you get errors because of a different trustzone. In that case you have to edit the update script in the ROM zip, OR flash old radio, then ROM gapps etc, new firmware.
[ONE Original Android Development] L0X0R:
Be aware, I think this fix was removed from the nightlies due to battery drain caused by DT2W. So either turn that off or wait for a new fix.

Source
[ONE Original Android Development] ATT Intruder:
There is a simple solution for that issue. Flash the CM11 modern and proximity sensor fix. I've been running it like this since I upgraded to lollipop and this fixes that issue.

You can search for my post and both files are attached. I've not posted much in a long time so it won't be hard to find

Here. http://xdaforums.com/showthread.php?p=60605463

FIX: CM12 no calls, sms, mms on Deep Sleep and Bluetooth connectivity issue.
[ONE Original Android Development] Flak:
I get a 404 for the modem download.
[ONE Original Android Development] ATT Intruder:
Updated link http://wikisend.com/download/143816/CM11s_XNPH05Q_modem.zip
[ONE Original Android Development] ovanitas:
I flashed Exodus couple of week ago and was very happy with the results (thanks for great work!!). As soon as the new touch screen driver is not yet released by Team Exodus, I firstly tried FC, then Stock kernel with touchscreen fix, both dirty flashed. Franco took 60-70 mAh in idle state and the Stock kernel takes 22-25 (half a day experience for the latter).

In both cases the idle state drain is higher than 10 mAh I have had with eXcaliBur of Exodus. Not sure if the higher drain can be attributed to the new touchscreen driver, or some other issues (dirty flashing, week compatibility with Exodus ROM, etc.). Any similar experience to fix touchscreen until Exodus comes up with its own solution?

Thanks.
[ONE Original Android Development] phoenixita:
Cm reverted touch firmware cause it was causing battery drain. Someone said that disabling dt2w solved the drain a little bit. Try testing this workaround :D [MENTION=2168288]ovanitas[/MENTION]
[ONE Original Android Development] ovanitas:
Will wait for newer kernel rather than disable this useful feature :) Thanks for the info.
[ONE Original Android Development] HatRiGt:
How to change lock screen wallpaper ?? Der is no option in settings ..
[ONE Original Android Development] Zephyr!:
Any update?
[ONE Original Android Development] Martin_Ro:
We are still working on it. We decided to do some more advanced new setup for our build setup.

For instant we currently move our custom code (that what is not only enhanced cm stuff) to an own repository to better be able to maintain stuff.

We are not interested into the "who is the fastest to release" stuff but want to bring forward our programming abilities...
[ONE Original Android Development] muhkobb:
If the next release is as rock solid as the latest nightly release I'm down for waiting.

This is hands down the bestest (yes, bestest) and most stable ROM I have ever been running on my OPO.
[ONE Original Android Development] ernestnwanu:
Couldn't figure out how to turn off the hardware keys on the latest nightly, is that no longer possible?
[ONE Original Android Development] critofur:
I tried switching to Franco r43 kernel to get the "touch screen fix" but now I'm getting tons of email FCs.
[ONE Original Android Development] mrgnex:
This worked for me:

xdaforums.com/android/general/guide-change-cyanogenmod-12-lock-screen-t3014524

Sent from my Bacon
[ONE Original Android Development] marcy9487:
You can use

THIS

app, or use GravitiBox.
[ONE Original Android Development] philou 77:
Bluetooth oneplus one

good morning

I have worries of loss of Bluetooth losque I am online with my telephone and my car.

I try unsuccessfully to redemarrer the telephone and cast off with the car I always have break of with a sound of other one quote deforme.

that blow needs it to fair I came back on the ancient version to try

thank you in advance

warmly
[ONE Original Android Development] vesparados150:
I second that! after flashing different roms, i always find myself back here... Look foward to the next update!

On another note, do any of you experiencing Android system (Alarm: android.net.netmon.lingerExpired...) wakelock?
[ONE Original Android Development] mjprashanth:
brilliant ROM

I agree. this is a brilliant ROM. the best.

---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------

I agree. Thank you so much for your hard work. This is the most stable ROM I have used on Oneplus. I now have a better battery life per charge and the ROM smooth as glass with no hiccups so far.

Thanks again
[ONE Original Android Development] KewalG:
Does the touchscreen fix firmware work with rom?

And if yes then please can anyone link it?
[ONE Original Android Development] Zephyr!:
Exodus nightly available?
[ONE Original Android Development] mdv53:
On version 10-10-2014 contacts fc. I use the gapps from de op. Does somebody having the same problems?
[ONE Original Android Development] gknnn':
No problem for me - clean installation.

Gesendet von meinem A0001
[ONE Original Android Development] K Rich:
Alright.... I've had enough fun with 38r, I'm coming back to Vanir!!

Question, can someone tell me what is included in the DHO gapps vs the DHO minimalist gapps?
[ONE Original Android Development] drnizeguy:
Same problem here.

Running on a fresh install.
[ONE Original Android Development] famonaco:
What's about new version 14/10/14?
[ONE Original Android Development] ottoeriksson:
Im running 14/10/14 with PA gapps without any problem. No fc in contacts.