yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Ejvyas:
Issues reported earlier:

1. I can enter the custom NTP server. There is no save button. When I return to that screen the NTP server is blanked out. It may be changed in the background (I didnt check) but the textbox remains blank for me after I return to the screen

2. I have turned on "Allow Downloads over Metered Networks" Still there is a notification from zookeeper "Waiting on network. Check WiFi". I always use Data connection. I Never use WiFi or turn on WiFi - thanks Tmobile

3. System Updates-->Check daily at...I have "2:5" as default. Its still 2:5 for me. Didnt change to 2:05.

4. All "Edit" buttons on the cron screen result in FC for me. Still present

2,3 seem to be fixed. I can reproduce 4 - will send catlog later. 1 - I will test later (need GPS for today)

How do we upgrade from c->D

1. press check

2. Fetch rom

3. reboot now

this takes me to recovery. It does not auto-run the upgrade. Am I missing something?

PS: I have reinstalled scripts
[ONE Android Development] uudruid74:
Should work with Philz or TWRP, but only tested on Philz
[ONE Android Development] superiscch:
Edit: didn't see that this is for 12.1, will ask again in cm13 topic :)
[ONE Android Development] Ejvyas:
I use Philz. It just rebooted to recovery. Didn't execute any scripts
[ONE Android Development] uudruid74:
Important

First, the full Dodo install (330MB) is now available. This is a different install method (flash it exactly the same way!) and instead of an image file thats tough to modify, its a tar file (tar files preserve Unix permissions but are otherwise like a ZIP). Previous versions may not have been installing the firmware (my bad). So Dodo installs firmware, kernel, and then formats /system and extracts all the files. It doesn't have to layer su or viper or atmos or anything after the fact. This was going to be my new method as its smaller and more flexible. Download here ...

https://eddon.systems/Download/WildLife/ROM/download/Dodo.zip

or

https://drive.google.com/file/d/0B9a4c293xQN_R0FZcThGTGpKRG8/view?usp=sharing

Did you notice I said "was"? I am also sorry to inform everyone that due to circumstances beyond my control I will be completely off the Internet for awhile and the Eddon Systems Website is coming down. If anyone wants to continue work on ZooKeeper, my github is https://github.com/uudruid74/Zoo-Keeper Feel free to fork the code and do whatever with it. I have added a link in the OP to the Google Drive ZIP as that may last longer than my server since I'm cutting payments today.

Bye all! It's been fun while it lasted. This is an awesome ROM and I'm sure it will function well until you are ready to take the plunge into a bowl full of bacon flavored marshmallows. I've heard Jgcaap's Marshmallow ROM is running really well these days. Both [MENTION=5956955]Purerawenergy[/MENTION] and [MENTION=2040569]jgcaap[/MENTION] should have access to make changes to this thread and the OP if need be. There is already a link to the CM13 thread in the OP.

:crying:
[ONE Android Development] Ejvyas:
Thanks [MENTION=5880917]uudruid74[/MENTION] for your efforts. It has been a pleasure working with you. My phone has never been so stable.

I'll probably jump off into cm 13 [MENTION=2040569]jgcaap[/MENTION].
[ONE Android Development] jgcaap:
big thanks for all support bro :)
[ONE Android Development] conalt:
Thanks for the full Dodo update file!
[ONE Android Development] Sanjoov:
Dolby Atmos rocks maaan. Crystal clear sound..impressed and amazed.
[ONE Android Development] Ejvyas:
Finally upgraded to Dodo. Dolby Atmos is wicked cool. Wondering what others are following since there won't be any more updates here
[ONE Android Development] JJohnson1988:
Probably jgcaap's CM13 builds.
[ONE Android Development] bucketheadmjs:
I just switched from Sultan's CM 12.1 to this build. I thought I saw mention of adding OTA updater to the ROM. What would be the point of that if there won't be future updates for this version?
[ONE Android Development] JJohnson1988:
I'm pretty sure CM12 is done with, and someone could pick up after uudruid's work and continue maintaining it for CM13 releases.
[ONE Android Development] Ejvyas:
[MENTION=5880917]uudruid74[/MENTION] was working on OTA and testing cm 13. However he had to take an unexpected hiatus. So unless anyone takes over his work this thread is done.
[ONE Android Development] Purerawenergy:
He was in the testing phase of the updater right before he left, fingers crossed he'll be able to finish it.. I know he did f#@*ing wonders with this ROM. I installed Dodo today as a backup (secondary) for when I install MultiRom again. This ROM is smooth, stable, responsive, fast and efficient. I can't believe the battery life and features he added to it. He put many hours and a hell of a lot of work into it and did an amazing job!

My prayers are with you [MENTION=5880917]uudruid74[/MENTION] and I hope you get through whatever you're going through okay my friend.

No mas Tòmas
[ONE Android Development] bucketheadmjs:
I second that. Thank you [MENTION=5880917]uudruid74[/MENTION] for a great ROM and hope to see you back soon.

On another note, I updated firmware away from the recommended OP firmware to the 1/25 H2OS firmware with good result. I am in the states and not on T-Mobile so YMMV. BTW the OP firmware gave me touch screen sensitivity issues.
[ONE Android Development] Sanjoov:
I agree bros. This ROM is amazing as far as all that Tomas has stated and the battery is phenomenal too. Dolby Atmos is incredible.

Do go back to MM ROMs like Tugapower, Jgcaap, Marsh and Broken too. But keep returning to Dodo in last few days.

Bless you [MENTION=5880917]uudruid74[/MENTION]
[ONE Android Development] Purerawenergy:
Would you mind sharing the firmware you are using with a link perhaps? I too am in the States and am having mixed results with OP recommended one. Thanks

No mas Tòmas
[ONE Android Development] bucketheadmjs:
Sure thing: http://xdaforums.com/showthread.php?p=64968748

Post #1352
[ONE Android Development] bucketheadmjs:
So quick firmware update. I've found that I can noticeably less battery life out of the 1/25 c7-11 firmware. A user in the modem thread posted a combination of the c6-241 modem and an update firmware. He has referred to it as the Frankenstein firmware. I am testing that now.
[ONE Android Development] rrohanjs:
i'm on Badger right now, so to update to Dodo i have to only flash the 2 update files to update badger to cuscus (4.27 mb) and cuscus to dodo (216mb) ?
[ONE Android Development] bucketheadmjs:
I can't say for sure. I clean flashed Dodo. However, my interpretation of the OP would lead me to believe you are correct. I would get a confirm with someone a bit more familiar with this ROM though...
[ONE Android Development] JJohnson1988:
Correct.
[ONE Android Development] Ejvyas:
Please share with the community your test results. I am also in US and I use TMobile. I am having touch issues with OP firmware.

I was doubting my fingers :silly:

Super smooth & stable ROM with amazing battery, working GPS, in built xp, moab, ota & a host of other features
[ONE Android Development] Purerawenergy:
I am using the newest CM Firmware (I think it's 01.25.16) but I'm not certain as there are so many updates and versions it's become a clusterf#@€ and is confusing. I'll upload it to Dropbox if anyone needs it. I don't know if the one in the OP has been updated, but I got it from some nice member in our thread. With this newer one I am getting very consistent results.. Call quality and reception is excellent and my touchscreen is very responsive. I rarely ever drop below 2 bars (out of 4) while inside my house, though I am constantly connected to Hi-Speed Internet. Outside my home it seems to ALWAYS show LTE and coverage is great, data is fast w/o any internet as I never connect anywhere in public and I really can't travel often because of medical issues. As far as battery usage it's noticeably better than H20 and older CM. I do know for a fact when a device is trying to get a lock on LTE but reception is poor it will eat up your battery like a wild hog, which is why it's always best to switch to 3g, even 2g (especially when connected to internet or when deep sleeping.) I use to use Smart Network by Wanam for this very reason but obviously now it's not needed.

When I flashed Frankenstein and my phone was sitting in it's normal spot charging overnight it was locked on LTE and and the signal bar in settings>battery was a very consistent dark green all night long. However when I started moving around with it device struggled to maintain even yellow so consequently appetite for juice was voracious.

This firmware is really a clever integration and based on modem thread seems to be working for some people so flash it and see.

Hope this helps you guys.

Oh, I'm in Port St. Lucie, Florida with T-Mobile just FYI.

No mas Tòmas

---------- Post added at 02:08 PM ---------- Previous post was at 01:50 PM ----------

I'm sorry, I forgot to mention that though I love this ROM, I switched back to [MENTION=2040569]jgcaap[/MENTION]'s cm13 MM builds full time. But the newest cm firmware works great with either ROM.

No mas Tòmas
[ONE Android Development] bucketheadmjs:
I no longer have touchscreen issues but I do not use T-Mobile. I would suggest testing. I imagine you will be able to remedy your touchscreen issues easily but radio performance seems to differ greatly based on location and carrier and hardware. I know next to nothing about these things.
[ONE Android Development] Ejvyas:
Please share the dropbox link. I guess if it doesnt work for me How do I rollback? this ROM has it in-built. There is no separate firmware post here I guess
[ONE Android Development] conalt:
You can also just install the dodo.zip file from http://eddon.systems/Directory.php/Download/WildLife/ROM/download

Since that is the full rom, you can just wipe cache and dalvic like you would when updating any other rom.
[ONE Android Development] Purerawenergy:
Here's the latest firmware from CM (dated Jan 25) via my Dropbox: https://www.dropbox.com/s/juirghkpoyo5owa/bacon_firmware_update_2016_1-25_.zip?dl=0

If it doesn't improve reception, data, touchscreen, etc., just flash one of the other two firmwares listed in the OP of [MENTION=2040569]jgcaap[/MENTION]'s CM13 thread or (if [MENTION=5880917]uudruid74[/MENTION] included it in this rom) just dirty flash it and wipe cache & dalvick cache. There's also an integration of the best parts of all these firmware combined built by one of the developers from the radio/modem thread. It's called the Frankenstein Firmware and has been posted several times recently in our CM13 thread as well. Hope this helps you guys

No mas Tòmas

---------- Post added at 12:35 AM ---------- Previous post was at 12:29 AM ----------

Oh and you mentioned something about this thread NOT having firmware listed separately however in the OP where it says downloads there is a hyperlink right next to the word "downloads" called (I think) "other links" that directs you to many other things besides Wildlife ROMs., just check it out but look carefully okay? Have a good night guys.

No mas Tòmas

---------- Post added at 12:38 AM ---------- Previous post was at 12:35 AM ----------

Edit: It says "Other Stuff" not other links.

No mas Tòmas
[ONE Android Development] DrNinjaa:
Loving the ROM due to its very low standby battery drain and smoothness but having soft reboots every time an app is updated or a new app is installed.

I did wipe cache and dalvik cache twice,even dirty flashed the ROM once again over my setup.

I'm using very few xposed modules(greenify and amplify) and even after disabling the xposed do cause the same issue. Any such issues with anyone using the ROM.?

Any help will be really helpful...

Thanks to the dev for taking so much pain to craft this ROM with so much awesomeness..
[ONE Android Development] JeromeLeung:
The firmware you linked seems to have caused my proxy sensor to stop working, but it does fix the touch issues...
[ONE Android Development] Purerawenergy:
It's hard to tell what each one will do until you flash them. Like I said, that was posted in cm13 thread so may have been for marshmallow which is why I also said if it didn't work flash one of the other two. Sorry it didn't work out for you. Looks like cm may be going back to their older firmware so you may search for that one (think it was may of 2015] and see if that one works.
[ONE Android Development] Ejvyas:
I have better response from disabling MOAB via ZooKeeper (just a click) and using AdAway instead. I remember the last time I tried MOAB (on my own) it was slowing down my device and lot of legitimate sites were blocked.

I am back to the full bacon potential after disabling MOAB and enabling AdAway

I guess I dont need ZooKeeper now as the only other feature was OTA (which wont be updated) ?
[ONE Android Development] JeromeLeung:
I actually did the same thing in disabling moab and noticed the same results. As for me, I think I'll hold onto zookeeper in case the OP comes back[emoji14]
[ONE Android Development] Sakti51:
Is there any new firmware like c7 for 5.1.1 without breaking proximity sensor?
[ONE Android Development] jimmy2027:
Can't seem to find it anywhere... but can anyone provide the xposed uninstaller for this ROM? I tried flashing the uninstaller from official xposed thread and led to bootloop.
[ONE Android Development] Uqbar:
And, more important: where's everything? The main site is gone!!!
[ONE Android Development] jimmy2027:
Please see below, if you missed this post:
[ONE Android Development] Uqbar:
Yeah! That's only message no.418!

Such a important message should have been posted rigth within the OP, the one that every stupid like me reads as no.1 for the project news.

Thanks a lot anyway!
[ONE Android Development] Sanjoov:
[MENTION=5880917]uudruid74[/MENTION] where are you
[ONE Android Development] Uqbar:
M.I.A.

He'll re-surface sometime in the future.
[ONE Android Development] jgcaap:
What do you guys need? Maybe I can help.
[ONE Android Development] jimmy2027:
Hi Jgcaap, if it is possible with you, can you provide the xposed uninstaller for jgcaap's modified v75 version? And also Zookeeper, if available.

I tried using the uninstaller from the Xposed official thread, but only led to bootloop.

Thanks so much ;)
[ONE Android Development] jgcaap:
Just reflash the rom..
[ONE Android Development] bucketheadmjs:
This is from the OP:

https://www.dropbox.com/s/usrpmh6bqxg9q0f/xposed-uninstaller-20150831-arm.zip?dl=0

---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------

And if you want exposed again without flashing the entire ROM:

https://www.dropbox.com/s/paeyof952a33g8k/xposed-HACK-v75-sdk22-arm-Macca-Hack.zip?dl=0
[ONE Android Development] Chaprnks:
All the .systems links are down...
[ONE Android Development] bucketheadmjs:
Many of us have moved on to [MENTION=2040569]jgcaap[/MENTION] CM 13 builds. I suggest giving it a go, it is excellent. If you are dead set on CM 12.1 Sultan's builds are very very good.
[ONE Android Development] plasticglock:
Just visiting the thread for the first time in a while. Sorry to hear of uudroid74 's problems.

I actually just came here to say how well my OPO is doing! I am still on Badger. This ROM smooths right out after a couple days and seems to work forever. As of today my phone has been running for 1,063 hours straight. That's right I have not rebooted for over 44 days. The battery still lasts great and I am not having any glitches. Everything works. No plans to reboot any time soon.

I find this to be amazing. I believe Badger to be a very special configuration. I will eventually move on to the cm13 build, but I have to say the bar has been set high.

Thank you to all involved. :good::good::good::good::good:

EDIT: it finally rebooted at about 1,220 hours. It was sitting flat on my desk.
[ONE Android Development] Purerawenergy:
Can someone PLEASE dropbox/drive me his "Show On Locksceen 3" app? I didn't know his website was down and the code written by him is so good it survives into Marshmallow. My prayers are with you Evan (@uudruid74) and you have my number if there's anything I can do for you brother. Thanks in advance.
[ONE Android Development] Setting.Out:
https://drive.google.com/file/d/0B34M6zvBOQ1KWTJuRlBxdmx3bjQ/view?usp=drivesdk
[ONE Android Development] Purerawenergy:
Brother I am forever in your debt. This piece of code has survived through lollipop and into marshmallow and is the only way I know of to easily and quickly change the MM locksceen wall. Thank you and I apologize for having been such a smart ass. You're a heck of a nice guy, intelligent, compassionate, caring and certainly (obviously) supportive. Appreciate you buddy.
[ONE Android Development] Setting.Out:
Lol.. Bribery (flattery) comes before presents, not after... ;)
[ONE Android Development] uudruid74:
These days you can ask me yourself and I can email it to you or Dropbox it! The server will be back online soon, but my car is in the shop and just needed ANOTHER $100 for more parts that weren't in the budget. But, I'm getting there!

Yes, folks. I'm back! I may just be lurking about in the shadows getting ready to gear back up, but we're gonna have some fun very soon!
[ONE Android Development] :
Any thoughts on expanding this project to nougat and beyond ?
[ONE Android Development] jgcaap:
welcome!
[ONE Android Development] uudruid74:
I'm actually going for a new direction in the future. I currently have a number of devices (netbooks running RemixOS, my car head unit running Lollipop, etc) and I keep wanting to install the same stuff on all of them. I also want certain hardware support and stock updates. As many of you know, once you change anything in the system partition, you can't do most updates without replacing the whole ROM again and losing your changes.

I will be experimenting with some technology that will allow you to keep a pristine system.img from your favorite ROM, even stock. No modifications to the system image at all, but you'll possibly need a modified kernel and hacked boot image. Then, when you flash certain add-ons (Viper, new cameras, supersu, xposed, etc), this will be written to an overlay instead of the system image. This means that the system image can be updated and reflashed and your changes remain (and I'll figure out some way to bypass the overlay on boot in case you mess something up). Eventually, we'll be able to take jgcaap's excellent modifications and apply them as overlays on top of another ROM, as well as test individual pieces separately. So, some parts like libC and likely Dalvik changes should move between ROMs pretty fluidly, but expect changes to frameworks to be more specific to an Android version or even the host ROM. This will need a lot of testing.

This means you don't have to download a new 500MB ROM because of a change in a 2MB library, you can just copy that one file over and reboot. I'm not sure if I'll hack an existing recovery tool to support this, or .. since I won't modify system.img at all .. I may re-purpose ZooKeeper!

At the moment, I have a bunch of other stuff to finish up and I'm waiting for my new phone as well. I may take a stab at a custom launcher as well, although that will be later in the year (designed more for automotive use).
[ONE Android Development] :
Take your time. This is a very intensive process than I thought, thanks for the explanation, I hope it will be worth it at the end. Nonetheless best of luck
[ONE Android Development] uudruid74:
Great thread. I've posted a link back to you. I had a single post (#4?) that was supposed to contain links like that, but you are already maintaining a superior list!

More about me at https://eddon.systems
[ONE Android Development] Bradl79:
great work.... does Ardvark have apple coding?
[ONE Android Development] paix_keeper:
Yes it does as stated before by OP :good:
[ONE Android Development] uudruid74:
Just wanted to everyone to know that I've updated the first 5 posts or whatever. Lots of new information and links. I'm testing the battery life of blu_active and I'll see about making it the default. My phone gets brutalized pretty badly and blu_active is keeping 2 cores off and the other at 300Mhz (the min) with the screen on, but the thing is noticeably faster than the old "interactive". Most cases, there isn't enough difference to justify, but this is impressive.

Jgcaap has been releasing new 12.1 versions, but with a new one every day and instructions to test one version against the other, I feel its best to wait until after the smoke clears before rolling out a new WildLife. However, I think this will be soon, and I'll be testing the first "Update" flash, specifically designed for small file size and a dirty flash so you can upgrade and not have anything changed. If that goes smoothly, I'll look into OTA.
[ONE Android Development] djcoolguyno1:
any working mirror of the rom

i have problem downloading
[ONE Android Development] uudruid74:
Towards bottom of first post is a link that says Additional Downloads. You'll see a WildLife folder. Or here is a direct link.

https://eddon.systems/Download/WildLife/Aardvark.zip

More about me at https://eddon.systems
[ONE Android Development] Bradl79:
anyone had any other issues with Aardvark not deep sleeping, i went from jgcaaps 11/17 rom to aardvark and i was noticing high battery drain and noticed, it never went into deep sleep mode, i had the same exact set up as i did on the previous rom
[ONE Android Development] uudruid74:
This is right now ....

I'll be updating to newer build with the clang optimizations very soon.

More about me at https://eddon.systems
[ONE Android Development] Bradl79:
i was just going to do another clean wipe, but i will just wait for ur update, i love the rom u and jgcaap keep up the great work.
[ONE Android Development] Purerawenergy:
This is a repost from earlier this evening Evan.

http://xdaforums.com/showthread.php?p=63979136

A thank you (and other feelings) for the work you are putting in my friend.

Tom 2.0
[ONE Android Development] uudruid74:
Testing Badger update right now based on jgcaaps 11/23. This contains compiler changes so almost every file changes and the update will be 215MB. Once this is done, I'll post the update zip and the full install zip.

Changes by me over Aardvark include no reboot to install Viper, default CPU governor goes to blu-active, and OOM killer is tweaked to hopefully avoid the 'super lag' when you get low on RAM.

Look for Badger in 24 hours

More about me at https://eddon.systems
[ONE Android Development] Setting.Out:
Jorge made a 23rd build at 12:00 that has notable performance improvements over his later 17:00 build.. Equally stable, battery being subjectively the same, have a test and see...
[ONE Android Development] digitalpig82:
Could you please share your "about phone" page of that first 23/11 build (with the build date shown)? I think I'm on that build too, but I'd like to know for sure. :) Thanks in advance.
[ONE Android Development] Setting.Out:
It should be 324.98mb in size...
[ONE Android Development] digitalpig82:
Check! That's the one I'm running now, thanks. :good: (you're on a different kernel, though.)

I was confused since it has a build date from 21/11, but it just seems to be this way then.
[ONE Android Development] Setting.Out:
Got bored, had to flash something.. :)
[ONE Android Development] uudruid74:
[MENTION=5165039]Setting.Out[/MENTION] thanks for verifying my findings. Does Xposed work properly with that earlier one as well?

All .... Its apparent that testing has failed. Do not expect Badger tonight. Need to get these issues sorted

More about me at https://eddon.systems
[ONE Android Development] Setting.Out:
I don't run xposed... But probably not as the one released a few hours later was reported to have issue..
[ONE Android Development] uudruid74:
Yes, but that was the latter one compiled with clang. If clang was the issue, and I'm thinking it was, then the earlier one could have worked. No biggie. We'll have to wait on jgcaap. There really aren't any huge bugs in Aardvark that would make an upgrade important.

More about me at https://eddon.systems