yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] saywhatt:
I did. People on the other end of the line have told me that they could barely hear me. There's a mic fix somewhere in OPO that you can flash.
[ONE Original Android Development] Flatric:
Or you can just disable "OK Google" everywhere, that fixed it for me
[ONE Original Android Development] joefso:
The google play service patches, are in slimsabers github:
[ONE Original Android Development] Hateislove:
Heads up for calls

Hello.

I can't get heads-up for incoming calls. Like, I do get heads-up for a missed call. But why is

There no heads up for incoming calls? It always turns to fullscreen. Heads-up for all other apps working. Please help.

Thanks.
[ONE Original Android Development] Martin_Ro:
Will check it...

Like I already said like 20 times: we currently focus on exodus 5.1. So we will not invest time into 5.0.2. Both, Dave and me are currently very limited in our time to android developement, so we can't look into things that most likely are fixed in the 5.1 branch anyway.

We will indeed still look into commits like the above example to fix stuff as it takes only a few minutes to check...

Btw: headsup for incoming calls is indeed working on my first test builds for 5.1...
[ONE Original Android Development] TheCrazyLex:
Looks like a really nice ROM, thank you!
[ONE Original Android Development] Larkin24:
Thanks for the update.
[ONE Original Android Development] Zach1928:
None of the proposed fixes have worked for me so I opened a ticket[emoji29]
[ONE Original Android Development] cccheel:
Just flashed this rom coming from cm12os, and none of my capacitive buttons work...
[ONE Original Android Development] marcy9487:
Try a clean flash.
[ONE Original Android Development] cccheel:
Reflash

OK, I will try again. Any recommendation for GApps?
[ONE Original Android Development] marcy9487:
Use PAGapps.
[ONE Original Android Development] ChoclateAddict:
Hello,

Will there be another update with fixes?
[ONE Original Android Development] Arrjaan:
There will always be updates. When we do not know. The developers have said multiple times that their focus lies on upgrading to 5.1 but I am sure they will fix critical bugs if they find any.
[ONE Original Android Development] fenderson:
Alarm wakelocks

Hi!

I am experiencing plenty of alarm wakelocks in almost all apps.

It is keeping my phone awake almost 35% of the time.

Any suggestion?

Mauro
[ONE Original Android Development] louisaus:
You should use Amplify with Xposed Framework to kill all those pesky wakelocks :) It requires a 2 dollar donation, but its a greatttt app!
[ONE Original Android Development] Martin_Ro:
Him, odd, we don't have all your wakelock issues (beside the pesky play store wakelock from time to time) might be xposed or an special app. Especially xposed is a real pain....
[ONE Original Android Development] fenderson:
No... I don't have any special app... but wakelock detector.

The "*alarm*" wakelock is present almost in every app running... I could try as [MENTION=6652233]louisaus[/MENTION] suggested to install amplify and kill *alarm* wakelocks... but I am afraid some apps could misbehave.

So, nobody else is experiencing this? BTW I did a full wipe coming from CM12s.
[ONE Original Android Development] joefso:
What do you get when you do this:

adb shell dumpsys alarm > AlarmDump.txt
[ONE Original Android Development] ChoclateAddict:
Could we have a release of exodus with the google play store wakelock and the alarm wakelock fixes?
[ONE Original Android Development] denyo81:
Excellent Rom. Clean fast and smooth. Works better for me as COS12. I'm in love with Exodus. :D
[ONE Original Android Development] Gamm86:
Read a few pages back...
[ONE Original Android Development] ChoclateAddict:
I have read it, it says that he will still look into commits to fix stuff. ..so I don´t " really" get your comment
[ONE Original Android Development] Heisenberg:
You just answered your own question, that means it's being worked on.

Transmitted via Bacon
[ONE Original Android Development] ChoclateAddict:
You guys are mean, I was just wondering when the fixes would be merged since this is a nightly rom and forgive me for not reading the last 20 pages
[ONE Original Android Development] Heisenberg:
Nobody's being mean, I just interpreted the post for you which gave you your answer. You can rest assured that it's being worked on and it'll be ready when it's ready.

Transmitted via Bacon
[ONE Original Android Development] navinthomas:
CAF Code

[MENTION=4429892]Martin_Ro[/MENTION]

"Try the stock COS12 camera and see if that has clear image. If it doesn't, ask the maintainers if they use caf code (which I'm pretty sure they don't). If that's the case then that rom is in the same boat as vanir."

This is a reply I got from the developer of the CameraNextMod app. One of the features in his app doesn't work in Exodus. I was wondering whether you use this CAF code.
[ONE Original Android Development] expiredd:
I'm thinking about clean flashing this ROM. I've test so far SlimSaber and Robbies CM12.1 ROM built with AK kernel.

Should I stick to stock kernel or do you recommend AK, Boeffla or other?

Now that PA Gapps are discontinnued which Gapps do you recommend? Would like to install something similar to the old pico Gapps.
[ONE Original Android Development] L0X0R:
[MENTION=4153349]timmaaa[/MENTION]

gratz on the forum moderator status man. Just noticed it :P

We're honoured to have you in our rom thread :p
[ONE Original Android Development] fenderson:
I will tell you as soon as I grab a PC.

Right now here are my findings:

- Flashing a different set of GAPPS doesn't fix it.

- A different kernel (namely Franco) does. With that kernel no more "alarm" wakelocks.
[ONE Original Android Development] firenxe:
any downsides as to using franco kernel and which version may I ask?:)

I've been having this particular issue since i flashed exodus + pico gapps
[ONE Original Android Development] fenderson:
Terribly sorry... but I was wrong...

Even if only in fewer apps... alarm wakelock is still there :(
[ONE Original Android Development] phoenixita:
Ok guys! I'm on cos 12 and I want to change ROM...reading the thread i saw that this ROM is battery friendly...but I'm scared from this wakeloks....should i flash it or wait 5.1 version to be released? I'd like your suggestions. Seeing on the github there is a staging branch for 5.1 so the wait won't last longer.
[ONE Original Android Development] Larkin24:
Wait.
[ONE Original Android Development] OmegaBlaze:
Flash. Learn about your phone. There's no reason to be scared of any ROM :cool:
[ONE Original Android Development] Larkin24:
Your right he should test it out before 5.1
[ONE Original Android Development] Heisenberg:
Thanks mate.

All he was saying is that the wait won't be much longer, he wasn't being inpatient in my view.
[ONE Original Android Development] Heisenberg:
PA Gapps have been picked up again by another contributor.
[ONE Original Android Development] expiredd:
Great! Last time I checked thread it was closed. Did they create new thread?
[ONE Original Android Development] Heisenberg:
Wait, wrong link, standby...

Here it is:

https://plus.google.com/communities/104296728204658607730

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
To add to that:

http://xdaforums.com/android/software/reborn-gapps-5-t3074660
[ONE Original Android Development] Heisenberg:
Except that thread has been closed now.
[ONE Original Android Development] L0X0R:
"This project was originally Started and developed by [MENTION=2777334]TKruzze[/MENTION] One of the best and great developers of XDA but due to some reasons TKruzze couldn't continue and announced his retirement and left a door open for anyone willingly can update this project so i decided to carry this project Untill unless TKruzze comes back. So lets hope he comes back soon"

You sure?

ahh found it. Thanks.
[ONE Original Android Development] LucentBirch:
This "mobile radio active" stuff is getting really annoying...I haven't been able to find anything about it being acknowledged by google at all...has anyone else heard anything about what causes it or if there's any way of stopping it?
[ONE Original Android Development] Martin_Ro:
Google will not comment on that as it is an oneplus device, no google device. But you all look to much into wakelocks at all. Battery is nice on that ROM, so who cares what's going on in the background ?

I never have had better battery with other ROMs that might not have that wakelock, so who cares ?

We are fully working on 5.1 and then we have a new game anyway as this will not longer rely on vanir build system...
[ONE Original Android Development] rrohanjs:
multirom manager detected that the included kernel has kexec-hardboot patch, so i presume its safe to run this rom as primary rom right ? no need of flashing another kernel ?

anyone else here running multirom with no issues with the included kernel ? if not the included kernel then which one would you recommend
[ONE Original Android Development] phoenixita:
Will flash as soon as i get home! :D

---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------

What if I repo sync your 5.1 branch on my pc? Will i be able building an early version of the ROM for personal testing? :D
[ONE Original Android Development] Bobbi lim:
Is the download link in the first post down? I'm having some issues opening up the link with Windows 10 - project Spartan.
[ONE Original Android Development] Gamm86:
Currently down. Try again later.
[ONE Original Android Development] denyo81:
That's can I to 100% confirm.

Battery life is amazing with stock kernel!

Compare with other roms I tried.

Don't need any apps like xposed or custom kernel. This Rom is very smooth and stable.

No issues with play services.

It seems so for me, when the devices goes into deep sleep exodus save extreme much battery. Is a bettery saver in the Rom include?
[ONE Original Android Development] iruiz2:
How much Screen On Time do you get?
[ONE Original Android Development] denyo81:
Sorry I can't answer your question.

I'm charge my phone 3-4 per day.

But I see a big difference when the akku is discharging compare with other roms like COS12 or Nightlys. You lost percent from akku like a count down. But with Exodus never faced that.
[ONE Original Android Development] jojuti1:
Flash problem

Hey everyone,

I have a problem with flashing the most actual version of the Rom. Everytime i try to flash it, my OnePlus One says following message :

Backuptool: backup

Not backing up files from incompatible version: 5.0

Failed to check whitelist!

Installing ROM...

Well, after the "installing Rom" message it just sticks there. I waited about 15 minutes, nothing happened. So i used my Nandroid Backup.

But i really want to test this rom^^ So has anyone a tip what i should do?

To my Phone: Cm12 (OPO edition), twrp. Ofc i flashed clean.

Mfg Jojuti

PS: sorry for that english :rolleyes:
[ONE Original Android Development] Setting.Out:
Flash new firmware.. CM firmware..
[ONE Original Android Development] jojuti1:
Do you mean the newest cm nightly?
[ONE Original Android Development] Setting.Out:
That's one way, or just the firmware.. Both work..
[ONE Original Android Development] phoenixita:
So I've flashed it the ROM is awesome. Full of a lot of features. Now i'm wondering wich kernel do you prefere in this thread :D
[ONE Original Android Development] kalapapa:
Keep stock kernel, it works the best. If you want to tweak the kernel, flash ukm and install synapse
[ONE Original Android Development] phoenixita:
I will test battery life with stock kernel then. Thanks a lot.
[ONE Original Android Development] Martin_Ro:
No special battery saver, but Dave optimized the kernel.

Small Update to the current work:

We still work on 5.1 but Dave and me have only a real small amount of time currently and me are currently fighting some server issues (that's why the download page is sometimes down)
[ONE Original Android Development] lokesh.3440:
Thanks for the update Martin_Ro . I shall keep my fingers crossed.
[ONE Original Android Development] L0X0R:
Thanks man.

Sometimes I wonder if I should try other roms because you guys don't have time as much as other rom makers do. But with the rom as good as it is I just haven't brought myself to leave it :P

Still back on the 19th build from last month cause I'm just waiting till 5.1 to do a full wipe.

Keep trudging along guys =]

Looking forward to it.
[ONE Original Android Development] rastojusko:
Hello people

Have you tried anyone 5.1?

http://www.vanir-exodus.net/experimental/bacon/
[ONE Original Android Development] yanner2012:
No, I'm waiting for developer announcing it. They write that 5.1 is in testing.
[ONE Original Android Development] L0X0R:
agreed. Even if there is an experimental build I'd rather wait till they are ready so that I can keep it and use it fully =]
[ONE Original Android Development] Gamm86:
Yes, I have. Flashed it without issues and it booted up without problems.

It looks like a very basic build without the Vanir bells and whistles.

Everything seems to work. I could send messages, receive data and calls, BT, Wifi, etc...

Back on my Nandroid backup atm though.
[ONE Original Android Development] joaon:
Which GApps did you flash? I'm having lots of Google applications FCs...
[ONE Original Android Development] lokesh.3440:
You can use slim gapps 5.1 or DHO gapps51.
[ONE Original Android Development] Zephyr!:
Flashed the latest Slim Gapps. Any work around?
[ONE Original Android Development] sonygoup:
Can I flash from Euphoria and keep my file on storage?

Think its called dirty flash
[ONE Original Android Development] Heisenberg:
Yes you can keep your internal storage. You actually never need to wipe your internal storage when installing a ROM. When changing ROMs you should wipe system, data, cache, and dalvik cache (this is called a full wipe), so if you're coming from a different ROM that's what you need to do. A dirty flash is when you don't wipe anything, or only wipe cache and dalvik cache, this is ok when you're flashing an updated build of the ROM you're already on.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] sonygoup:
Thank you I'll be flashing it now :)
[ONE Original Android Development] ak:
[MENTION=4153349]timmaaa[/MENTION]

All my Congratulations for your new title

Sent from my A0001
[ONE Original Android Development] Heisenberg:
Thankyou, sir, much appreciated [emoji106]

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] cbendan:
I would like to use this ROM, but after flashing ROM and GAPPS (after full wipe), all work ok. But after recovering the data nandroid backup (from YNG1TAS17L), home, menu and back buttons, stop working.

Could this be because of the firmware?

Thanks and good work.
[ONE Original Android Development] Heisenberg:
No it's because you restored a data nandroid from another ROM, you can't do that, you can't restore data from a completely different ROM. You can only restore CM12S data if you're actually running CM12S, you can only restore Exodus data if you're actually running Exodus. See what I'm saying? You need to perform a full wipe (system, data, cache, dalvik cache) and flash the ROM and gapps again, and don't restore any incompatible data. Can I just ask where you got the idea that you could restore data from a different ROM? Did you read that somewhere?

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] Arrjaan:
In addition to timmaaa, if you do want to keep your data when you switch roms, you should use an app like Helium or Titanium Backup.
[ONE Original Android Development] arifqur:
Congrats on becoming the forum moderator
[ONE Original Android Development] rogi19:
I'm running the 5.1.1 experimental build for almost a whole day and i got to say it's rock solid, awesome job guys!
[ONE Original Android Development] cbendan:
Thanks, I thought that I could restore a data nandroid backup from a different ROM based on the same version. In fact, I've done it before (Nandroid data from CM11S Calkulin's battery saver to stock CM11S).
[ONE Original Android Development] Heisenberg:
You were successful on the other occasion purely because Calkulin's ROM is just CM11S with a few tweaks.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] kholdstare21:
Do you use Skype? I would really want try this and Skype is required for my daily driver.
[ONE Original Android Development] strange1712:
You can use Skype 4.9 with current 5.0.2 versions...

---------- Post added at 11:11 AM ---------- Previous post was at 11:08 AM ----------

5.1 experimental version is barely different from cm12.1 nightly... It's just the base, I guess they haven't really tweaked it a lot at all...
[ONE Original Android Development] malavan:
Awesome@timmaa very nice guy and awesome admin
[ONE Original Android Development] rogi19:
I just tested it and it works
[ONE Original Android Development] kholdstare21:
Thanks! I will try this one when its released.
[ONE Original Android Development] auerbach:
titanium is great

i recommend it

---------- Post added at 03:35 AM ---------- Previous post was at 03:30 AM ----------

i flashed it

looks like cm12.1 !!

no exodus logo or animation or updates ?!
[ONE Original Android Development] yanner2012:
It's experimental, you must be patients and waiting for release or nightly.
[ONE Original Android Development] droidzeus:
just like over clocking has its own downsides like damaged motherboard

does downlcoking this ROM to 1.5 GHz can result in same
[ONE Original Android Development] Ahmed Shawky:
Guys is this better than Liquidsmooth V4 ?
[ONE Original Android Development] venky716:
Overclocking pushes the cpu over the oem specified limit and so can cause damage.

Underclocking just limits the cpu, it also results in lower heat produced so underclocking can only do more good than harm.

Sigh.
[ONE Original Android Development] Zephyr!:
*facepalm*
[ONE Original Android Development] Heisenberg:
Saying one ROM is better than another specific ROM can be pretty disrespectful to the devs. Only you can decide which is the better ROM

for you

, through your own testing.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] karluag:
Hi, what is 5.1.1 ?
[ONE Original Android Development] frewys:
The latest android release version from Google
[ONE Original Android Development] Ahmed Shawky:
Thanks for reply

I just looking for the one with more stable
[ONE Original Android Development] Heisenberg:
If there are any stability issues they'll most likely be talked about in last ten pages or so of the ROM thread, so the best idea is to read the last ten pages of each thread.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
I feel like there should be rules about these types of questions if there aren't already. Doing pre-reading should be an expected thing before asking questions right? To make more informed responses.
[ONE Original Android Development] Martin_Ro:
Ok, somebody found the expermental build... sneaking around all the time ;)

This first experimental build was done to verify the build system itself. We moved over to cm's build system with roomservice (before we used vanirs with bootleservice).

This move we made because of two reasons:

1. to reach more safety in the build area. We suspected some of the issues we have had (like skype) to be a build system issue

2. to make the sync's easier and faster for our contributors. The one who did a clean sync for our Code knowns: It pulls everything for every device because bottleservice only is able to pull the kernels for given devices. Roomservice likewise syncs only the base system without the device dependend stuff and pulls the device dependend stuff only if needed (if you try to build for a device the first time). We even pushed this more forward by adding the vendors (synced with TheMuppets repos) to roomservice. This makes it easier and faster for all the contributors (and even for ourself).

To change to cm's build system hasn't been that easy task as it heavily relies on their repos (github.com/CynanogenMod) and their vendor (github.com/Cyanogenmod/android_vendor_cm). So I have had to change this, also I have had to add the ability to fetch our repos (github.com/TeamExodus) and their repos, as we don't want to fork and maintain all their repos. And I have had to move all their vendor based stuff to our vendor folder (github.com/TeamExodus/android_exodus).

Took me more than a week to finish that, but like the experimental build demonstrates, it seems to be finished.

So the experimental build is basically a cm build with our modified build system. But we already have started to merge back some of our basic stuff. More will come the next days.

I have to add some optimizations to the build system, we have had added to vanirs to make builds faster, because the current build takes around the double time, we needed with our latests improvements on vanirs system. But this isn't really hard and should also be done the next few days.

Regarding issues with the experimental build and play service:

You have to use a 5.1 gapps on the Exodus 5.1 builds, the old 5.0 gapps will most likely not work...
[ONE Original Android Development] kalapapa:
I appreciate all the dedication you guys have put into this rom
[ONE Original Android Development] pa.pn2:
found it too.flashed.so far everything works fine.smooth.some stuff is missing like navbar resize but i dont mind.waiting for future builds martin:)thx
[ONE Original Android Development] mittimus:
Tried the experimental build, looking good so far but i have one big problem:

i switched the connection from LTE to 3G 'couse don't have an LTE promo with my operator; after that i lost the connection permantly..Tried to reboot, switch Airplane mode, switched on-off Cellular data but nothing happened.
[ONE Original Android Development] Heisenberg:
There's no point in reporting bugs for that test version, it's just that, a test version, it hasn't actually been released publicly.

XDA Moderator

Transmitted via Bacon
[ONE Original Android Development] L0X0R:
[MENTION=4153349]Heisenberg[/MENTION] Curious about the name change man :P

What's up with that? :P
[ONE Original Android Development] joefso:
it is what happens when timma gets some power, it is all breaking bad from now on
[ONE Original Android Development] :
I think modern medicines finally worked on timmy, he walked off the wheelchair and started cooking meth !! :silly:
[ONE Original Android Development] badagaio:
I've found a strange bug on the latest ROM (5.0.2). While on my pocket the phone kept "unlocking" itself and typing numbers on the emergency dial. This never happened with another ROMs. The only solution I've found for this was disabling double tap to wake. Keep in Mind that this only happened with this ROM.

Even though, fantastic rom, snappy and with great battery life. :D
[ONE Original Android Development] Flatric:
Settings -> Hardware -> something with prevent accidential wakups
[ONE Original Android Development] badagaio:
That's on, the problem persists. One friend of mine also installed the same ROM and has the same problem.
[ONE Original Android Development] frewys:
Do you use hardware keys? completely turned them off?

There is an option under hardware/general button options/home wake-up device

On mine, it was ticked on as default.
[ONE Original Android Development] rrohanjs:
i have that off as well and i also face the same issue
[ONE Original Android Development] Martin_Ro:
You want to try disabling and reenabling prevent accidental wakeup. An other possible reason: What firmware do you have installed ?
[ONE Original Android Development] badagaio:
Yup. Im using hardware keys. I've disabled he home wake up button. Let's see what happens. Thanks for the tip!
[ONE Original Android Development] Daedulus Minion:
It's due to ghost touches. Happens for me too. Not specific to this rom.
[ONE Original Android Development] badagaio:
Well, it never happened to me before. I think that after disabling the home button for wake up the problem is gone. :)