yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] teameos:
Welcome to Eos! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.

Bigrushdog - Project lead, Chief Developer [Xoom || Galaxy Nexus || HTC One (M7)]

RaymanFX - Co-leader, AOSP code maintainer [Xperia S || Nexus 7 (2013) || OPPO N1 || OPPO Find7a]

jrior001 - Jenkins/Gerrit Admin, CAF code maintainer [HTC One X]

anders3408 - Frameworks Developer [OPPO Find5 || OPPO N1]

Roach - Frameworks Developer [Nexus 4 || Nexus 7 (2013) || HTC One (M8)]

Connor Baker [Nexus 4 || HP Touchpad]

NX Gesture Navigation Bar
EOS Weather Engine
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Network Indicator
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Force Navigation Bar on any device
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
MORE...

We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded.

Team EOS Flo Nightly builds

Flo <<< Link >>>

Deb <<< Link >>>

G-Apps Package

Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:

GApps <<< Link >>>

These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.4.x COMPATIBLE RECOVERY.

Detailed instructions

:

Going to EOS4.4.x from a rom < 4.4.x:

Backup everything !

Go to recovery

Make a full wipe / factory reset

format /system

Flash the rom

Flash optional kernel

Flash gapps

Reboot

Updating from EOS 4.4.x #XX to #YY:

You can usually skip the full wipe step.

If ever you encounter an issue make sure you make a full wipe first before reporting though.

Nexus 7 (2013) aka Flo/Deb comes with a custom kernel, featuring the latest kernel.org mainline patches and designed specially for EOS.

Contribute

Gerrit Review

Jenkins Build System

Github

XDA:DevDB Information

TeamEOS, ROM for the Nexus 7 (2013)

Contributors

teameos, RaymanFX

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: AOSP

Version Information

Status: Stable

Created 2014-05-20

Last Updated 2014-06-27
[Nexus 7 (2013) Original Android Development] RaymanFX:
first one is mine!

Test and feedback please :)

Rock stable for weeks now and I can't get mine to crash or anything, all the recent kernel updates I applied also seem to play nicely.
[Nexus 7 (2013) Original Android Development] matt4321:
Awesome that EOS is back, had it on my Xoom for years.

Does the kernel have the kexec patch in place for use with multirom?
[Nexus 7 (2013) Original Android Development] RaymanFX:
Argh, shame on me for forgetting about that one!

I'll intergate is as soon as possible.

If you're feeling generous, you can always submit the patchset at review.teameos.org though :)
[Nexus 7 (2013) Original Android Development] teddy0209:
Thanks Team EOS and RaymanFX!!!

Will try it after work... =)
[Nexus 7 (2013) Original Android Development] deathblade:
Glad to see eos again, had it on my dad's Xoom for the longest time, always was super solid with some unique features, gotta try this soon
[Nexus 7 (2013) Original Android Development] RaymanFX:
Important updates for the next nightlies:

1) Multiboot kexec-hardboot patch as requested by [MENTION=4393511]matt4321[/MENTION]

2) Linux 3.4.91

https://github.com/TeamEOS/kernel_asus_flo/commits/kk4.4
[Nexus 7 (2013) Original Android Development] Rozza C:
Installed this on my tablet last night.

So far, so good. Really like it. :)
[Nexus 7 (2013) Original Android Development] mpmilestogo:
Yay! Really like this news. I notice there is a nexus 5 build as well. Will there be a forum for that device? Going to install on my nexus 7 today. Used this on the Xoom until it de-xoomed :)
[Nexus 7 (2013) Original Android Development] jiffy1080:
I'm still rocking an EOS build on my Xoom and it is now running great on my Nexus 7. I have all the OG Tiamat backgrounds in rotation on my Nexus 7 and M7. I missed you guys...
[Nexus 7 (2013) Original Android Development] loopism:
Welcome back :)

Nice to see the EOS name back :good: - loved it on my 2012 Nexus 7, so I'll give it a whirl on the 2013 model
[Nexus 7 (2013) Original Android Development] waz675:
Wow, great to the teameos name here. Thumbs up! :D
[Nexus 7 (2013) Original Android Development] waz675:
Installed and running nice, using elemental kernel as it compliments my HTC M8 running elemental kernel, heh heh :p

But the ROM is running nicely! The options seem to be nice, I don't think I saw a "date in status bar" option but I did install this at 1am so went to bed quickly. Morning is crazy here, our kids run crazy for ages *cough*
[Nexus 7 (2013) Original Android Development] RaymanFX:
Them newz!

In the next nightly, you'll get full sweep2wake and doubletap2wake support in the kernel thanks to [MENTION=4195844]show-p1984[/MENTION] !

I cherry-picked the corresponding commits into the EOS kernel because I liked those.

Keep in mind they don't drain your battery at all, or at least not more than the kernel did before thanks to the usage of IRQs.

s2w and dt2w are disabled by default not to confuse new EOS users.

However, I put together a nifty little device settings app that will let you toggle those two features easily:

https://github.com/TeamEOS/device_asus_flo/commit/6090f9a064c456b8e24667fd12a587529d856cf2

To access it, head over to Settings->Device->More... and there you are :)

Keep in mind all this will be available in the next nightly build, so stay tuned and watch the status: http://jenkins.teameos.org/

Also, for some reason, haters or 'trolls' seem to have voted this thread 1 star.

Due to the lack of negative criticism in this thread, I think the 'stars' should actually reflect the user's opinion of this ROM.

So if you like EOS on your device, please spend that one second it takes you to vote this thread 5 stars. Thanks!
[Nexus 7 (2013) Original Android Development] waz675:
Hi, I haven't read the thread to double check, took our kids to the zoo today, 9 hour day, drained. Anyway, found out the hard way that GPS doesn't seem to work at all. The app, sygic showed no satellite coverage bars at all whilst my phone running same app +map showed bars and worked as expected. The app on the n7 was sitting at "waiting for coverage" type error message.

Sorry if this is a known problem, I'll re read this thread tomorrow. Severe chronic pain, 2 crazy active kids and 4 hours driving plus zoo adventure = one tired me, body and mind!

Thanks for putting teameos available again :D
[Nexus 7 (2013) Original Android Development] rifraf1:
Anyone running this on a DEB model with MultiROM installed?

I have tried 3 different nightlies and it will not boot, just curious if any has had luck with this configuration.
[Nexus 7 (2013) Original Android Development] TheIronMaiden:
For whoever is wondering, the new nightly (6/20) is based off of 4.4.4 , because we all crave the latest and greatest...

---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------

EOS is one of my favorites btw
[Nexus 7 (2013) Original Android Development] teddy0209:
Except, deb version doesn't boot..
[Nexus 7 (2013) Original Android Development] bgiesing:
I am loving the NX Gesture Bar but this ROM is missing a lot even compared to AOSPA. No floating notifications like Hover or Heads Up, no global immersive mode, doesn't have the new theme engine, and quite a lot more...
[Nexus 7 (2013) Original Android Development] cammel:
Wow! It's awesome you guys are back!! I really loved your roms on my good old Moto xoom!

Just a few questions before flashing this awesome rom tonight on my Flo, the link to the gapps from the OP is not showing anything, is there any other gapps package that you recommend? And the last one... Are you going to implement theme engine on your rom?

Thanks a lot for your hard work and for coming back!! ???

Enviado desde mi XT1058 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] poondog:
You realise, there are some roms that can be their own original thing rather than be a kang bang features from other roms? :)

Just saying.. not everyone likes a merge everything Rom, some like it clean :) that's what I look for in an EOS rom
[Nexus 7 (2013) Original Android Development] bgiesing:
I don't like merge everything ROMs either but every ROM has immersive mode at least! Also this ROM already has the theme engine but it is the old one and a lot of the best themes are no longer compatible with it. Finally, hover/heads up isn't necessary but it is useful.

Still said, it is one of the smoothest ROMs I have tried.
[Nexus 7 (2013) Original Android Development] poondog:
True in a way

It's also a bit disrespectful in a way imo to merge all the features a team has worked hard on

But each to their own
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Hover gets in the way and the new theme engine is still buggy. If you want them so bad learn to compile and cherry pick like I did and stop acting like a spoiled little brat!
[Nexus 7 (2013) Original Android Development] bgiesing:
No reason to hate... I was making a suggestion! Do they have to implement it, no, but could it possibly help? Maybe.

I wasn't trying to sound mean but if I did then sorry.
[Nexus 7 (2013) Original Android Development] poondog:
its ok mate

I maintain a kernel for the HTC one and sometimes I get fed up with requests to merge everything other kernels have.. if some people had their way, then every rom and kernel would be the same; a sloppy job with all feeatures they want

Thats why I have this opinion :)
[Nexus 7 (2013) Original Android Development] badgone88:
Please could someone upload some screenshots ?

Thanks
[Nexus 7 (2013) Original Android Development] shaolinz:
Guess their all out of pics haha
[Nexus 7 (2013) Original Android Development] RaymanFX:
Welp, EOS looks like AOSP, you might aswell just search YouTube for any nexus device ..

If you need screenshots from my device for whatever reason, let me know and I will happily provide :)
[Nexus 7 (2013) Original Android Development] -[-Xehanort-]-:
Hey everyone.

Anyone here have a problem with DEB? :confused: I installed on mine but it stuck at Google logo.

I have use this ROM before on my TILAPIA and it work fine.
[Nexus 7 (2013) Q&A] Pharez87:
I would like to if it is possible to run logcat 4.4.2 on my device I just rooted it this morning using the wugfresh programs one click easy install.
[Nexus 7 (2013) Q&A] wantabe:
[Tutorial] How To Logcat ; )
[One (M8) Q&A, Help & Troubleshooting] avivzamir:
hi,

i have the factory unlocked Verizon HTC One (M8) but im using it on a GSM network.

the phone has an update but it tells me it can only be updeted on a CDMA network.

is there a way to change that without rooting the phone?

thnx!
[Verizon Samsung Galaxy S III] dandydon414:
I've taken the time to theme some KK apks (contacts.apk, teleservices, systemui, settings, framework, dialer). I only have a few pngs that I haven't themed but it's pretty complete. If anyone is interested, I will provide the pngs. This only for xhdpi (320) and AOSP roms.
[Verizon Samsung Galaxy S III] Yardie_Style:
interested
[Verizon Samsung Galaxy S III] Zenia:
Look great but i am not a developer. I am interested to see the .apk and install them on my s3.
[Verizon Samsung Galaxy S III] dandydon414:
what rom are you running?
[Verizon Samsung Galaxy S III] Zenia:
beanstalk-4.4.275-20140325-d2lte.

its 4.4.2 with baseband version i535vrlf2

thank you for quick respond
[Verizon Samsung Galaxy S III] dandydon414:
here you go

contacts: https://drive.google.com/file/d/0Bx1c6k1NlKGkZ2xuWHo0czVYM28/edit?usp=sharing

dialer: https://drive.google.com/file/d/0Bx1c6k1NlKGkTUhTc1VKSW90M0U/edit?usp=sharing

framework: https://drive.google.com/file/d/0Bx1c6k1NlKGkZ2VSRC1PaXNRdW8/edit?usp=sharing

settings: https://drive.google.com/file/d/0Bx1c6k1NlKGkNUl3TUpnS04xTWM/edit?usp=sharing

systemui: https://drive.google.com/file/d/0Bx1c6k1NlKGkZ2szUl84eTFuZjQ/edit?usp=sharing

teleservices: https://drive.google.com/file/d/0Bx1c6k1NlKGkYS14X2tIU3BDNTg/edit?usp=sharing

all these pngs need to be copied to the drawable-xhdpi of each apk. for systemui you can't modify the apk and just copy it back to the priv-app folder. you'll get FC on systemui. I usually open up the rom zip with 7-zip, extract the apks (system/priv-app folder system/framework for framework.apk), look for the drawable-xhdpi folder then drag the pngs into that folder. after you do this for each apk copy them all, except framework.apk, to the system/priv-app folder. framework.apk goes into the system/framework folder. copy the rom back to your sd card, go into recovery and reflash the rom without doing any wiping. if you have xposed you might have to re-enable it and reboot

I know it sounds like alot of work. I usually modify the rom before I flash it. This process should work with any aosp kk rom. I've flashed several and always theme the apks before I flash it. these not flashable zip files.

DO THIS AT YOUR OWN RISK

ALWAYS NANDROID FIRST

THIS IS ONLY FOR THE S3

NOT RESPONSIBLE IF YOU MESS SOMETHING UP

I've installed plenty of roms and always do this and have not had any problems.
[Verizon Samsung Galaxy S III] dandydon414:
looks like beanstalk is up to version Build 4.4.285
[Verizon Samsung Galaxy S III] Zenia:
yes but 275 more stable in my opinion and i am on verizon
[Verizon Samsung Galaxy S III] dandydon414:
have you tried c-rom. by the same developer. I've had zero issues so far
[Verizon Samsung Galaxy S III] Zenia:
well i am happy with that one no problem at all.dirty unicorn was my favorite one but no updates at all
[Verizon Samsung Galaxy S III] dandydon414:
yeah dirty was nice. still waiting for a kk version like you
[JASJAR, XDA Exec, MDA Pro Software Upgrading] boongdang:
download at http://www.business.orange.co.uk/servlet/Satellite?pagename=Business&c=OUKPage&cid=1142943309969 and extract yourself
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
Via a PC, as you can't through Android itself
[One (M8) Q&A, Help & Troubleshooting] kenloon2009:
I find out video and picture can move to sd card using gallery but documents like pdf, excel,word not cannot, even I use Polaris office also can not save into ad card.. can everyone help Me?
[Xposed General] LWH.31752:
I'm not sure if anybody can help but I'll give it a try. My xposed modules will only work after a soft reboot. Xposed framework runs fine after a normal boot but not the modules. Any idea why?
[Xposed General] haydnlj:
Strange.. did you have a volume key held on reboot (that can disable the framework for the current session)?
[Xposed General] LWH.31752:
No. Never do that and it does this all the time. On a full reboot xposed framework shows it's active but none of the modules run despite being activated.
[Xposed General] abhimanyu bajaj:
Check your bootmanager... and disable all xposed modules from that.... it can cause them not to run at boot up... happened to me too
[Xposed General] LWH.31752:
Bootmanager? The only bootmanager I'm aware of is the one I installed that's part of xposed. And those modules aren't listed in that app.
[Xposed General] GermainZ:
Check the logs in the Xposed Installer.
[Xposed General] LWH.31752:
What should I be looking for in the logs? There's a ton of isSupportApp. And some other stuff I'm not precisely sure of.
[Xposed General] GermainZ:
You can paste it here (use [CODE][/CODE] tags) or on a pastebin (e.g. bpaste.net, sprunge.us.)
[Xposed General] GermainZ:
Don't hijack others' threads, please. Your issue isn't related to the OP's. Anyway, ask for help in the module's thread, not here. This forum is for questions related to the framework/installer, not module specific support (read the stickied guidelines thread for more info.)
[Xposed General] GermainZ:
Most of your modules are getting installed to /mnt/asec, so they're not getting loaded correctly since that's not mounted yet when Xposed loads the modules. They're not paid modules, though, so I'm not sure why that's happening.

Is encryption enabled on your device?
[Xposed General] LWH.31752:
No, encryption is not enabled.
[Xposed General] rovo89:
I believe they will also be moved to /mnt/asec if you move the app to the SD card. Try keeping them (or at least the APK) on internal storage.
[Xposed General] LWH.31752:
Thanks for the info rovo. That seems to have done it. Can't believe I didn't think of that sooner. LoL Thanks to all who replied and tried to help.
[Xposed General] vishal11in:
Sorry to use this thread for my issue.

The first time i install the unsigned app using android studio. The apps get installed perfectly and after reboot it shows as File does not exist.

The second install from the Android Studio works fine.

Any advise.
[Xposed General] Raj333:
Plz help i have done moving app to internal bt didn't help

bKdkdL3N---------------------------

31-Jan-2017 6:45:51 pm UTC

Loading Xposed v54 (for Zygote)...

Running ROM '4.4.026.P0.140702.A109' with fingerprint 'Micromax/A109/A109:4.4.2/KOT49H/4.4.026.P0.140702.A109:user/release-keys'

-----------------

31-Jan-2017 6:50:39 pm UTC

Loading Xposed v54 (for Zygote)...

Running ROM '4.4.026.P0.140702.A109' with fingerprint 'Micromax/A109/A109:4.4.2/KOT49H/4.4.026.P0.140702.A109:user/release-keys'

Loading modules from /data/app/com.mohammadag.knockcode-1.apk

Loading class com.mohammadag.knockcode.XposedMod

-----------------

31-Jan-2017 6:52:36 pm UTC

Loading Xposed v54 (for Zygote)...

Running ROM '4.4.026.P0.140702.A109' with fingerprint 'Micromax/A109/A109:4.4.2/KOT49H/4.4.026.P0.140702.A109:user/release-keys'

Loading modules from /data/app/com.mohammadag.knockcode-1.apk

Loading class com.mohammadag.knockcode.XposedMod

-----------------

31-Jan-2017 7:00:52 pm UTC

Loading Xposed v54 (for Zygote)...

Running ROM '4.4.026.P0.140702.A109' with fingerprint 'Micromax/A109/A109:4.4.2/KOT49H/4.4.026.P0.140702.A109:user/release-keys'

Loading modules from /mnt/asec/com.mohammadag.knockcode-1/pkg.apk

Loading class com.mohammadag.knockcode.XposedMod

-----------------

31-Jan-2017 7:05:33 pm UTC

Loading Xposed v54 (for Zygote)...

Running ROM '4.4.026.P0.140702.A109' with fingerprint 'Micromax/A109/A109:4.4.2/KOT49H/4.4.026.P0.140702.A109:user/release-keys'

Loading modules from /mnt/asec/com.mohammadag.knockcode-1/pkg.apk

File does not exist
[Droid Ultra Q&A, Help & Troubleshooting] bluh5d:
I am on 4.4 my phone says there is an update I am guessing its 4.4.2 I am currently rooted. If I upgrade will I loose Root ?
[Droid Ultra Q&A, Help & Troubleshooting] akellar:
Impossible to say, we don't have 4.4.2. There's already a few threads discussing keeping root on the small update though.
[Droid Ultra Q&A, Help & Troubleshooting] bluh5d:
i have a droid maxx what do you have ? Also can you direct me towards those posts ?
[Droid Ultra Q&A, Help & Troubleshooting] bluh5d:
I did the update its still on 4.4 though so it doesn't loose root.
[Droid Ultra Q&A, Help & Troubleshooting] bigv5150:
Take it for what its worth but I updated my wife's RAZR m with 4.4.2 and couldn't keep root. I tried to hide root update failed tried root survival using supersu update failed. Both times it failed due to root being detected. Will it be the same for the maxx I don't know but it ain't looking good.
[Galaxy Note II Q&A, Help & Troubleshooting] jkd:
I made a mistake, I installed the ROM [ ROM] [TouchWiz 4.4.2] *eZKAT*, then flashed with the patch wifi, as it not to work I returned to my previous ROM DN3 v3.2 but since I do not have IMEI anymore.

I have even to flasher with official ROM but anything makes for it, always not of baseband.

Official ROM used:

N7105XXDMB6_N7105XEFDMB3_N7105XXDMB1_HO ME.tar.md5 and N7105XXALJ5

How can't get my imei ?
[Galaxy Note II Q&A, Help & Troubleshooting] note2nooby:
You made a backup of your EFS.

If you didn't then it will be really hard to restore your own IMEI. You shouldn't try to revert back your bootloader.

Give more info what you did exactly?

Which bootloader have dn3 rom?

Here's the correct way to do things

http://xdaforums.com/showthread.php?t=2755247

Read the #4 reply.

Sent from my GT-N7100
[Galaxy Note II Q&A, Help & Troubleshooting] jkd:
For my EFS i have a backup done with TWRP.

My phone: n7105 LTE

when i was DN3 and before flash [ROM][TouchWiz 4.4.2] *eZKAT*, i have 4.1.2 bootloader.

baseband : N7105XXUEMJ9

bootloader : N7105XXDMA5

OK what i do, well first i flashed eZKAT and flash wifi patch (because wifi don't work and after still don't)

Then reboot and see that i lost my IMEI

Then i tryed to flash 4.1.2 rom stock and restore EFS with TWRP, but not work still no IMEI

Finaly i restore my DN3 4.3 v3.2 from TWRP and have

now no baseband

bootloader: N7105XXDMB6

Now i don't no what is my bootloader
[Galaxy Note II Q&A, Help & Troubleshooting] note2nooby:
There is an app phone info samsung on the play store. Get it and check . here are many threads started by user who tried to restore their IMEI. Try to search in the forum you will find many useful info.

And you have your backup so it should not be so bad. Me I m not rooted stock so I'm not so qualified to guide you. Search the forum.

Sent from my GT-N7100
[Galaxy Note II Q&A, Help & Troubleshooting] mohit141785:
first of all go to sammobile and get 4.3 stock rom for your region. Then boot into recovery and wipe everything. Then flash the stock rom u downloaded via odin.if you have not flashed the ezkat rom via odin. Then this will solve your problem. Most probably you would have flashed the ezkat rom via recovery so its no big deal as flashimg via recovery does not change your bootloader. So go flash a stock rom 4.3 version via odin.it should silve your problem if it still exist then root your phone(after flashing stock 4.3 rom via odin) then get twrp recovery and try restoring your efs.good lu k
[Galaxy Note II Q&A, Help & Troubleshooting] jkd:
i flash the wifi patch via odin

i just flash 4.3 stock rom but still no IMEI
[Galaxy Note II Q&A, Help & Troubleshooting] mohit141785:
Did you flash stock via odin? Try restoring efs backup.

---------- Post added at 11:49 PM ---------- Previous post was at 11:45 PM ----------

Did u make a titanium backup when you were on dn3 rom. If yes then you can restore your dn3 rom and restore titanium backup( both system and user apps) and if nothing works then probably just flash stock rom dont root it and take it to service center.
[Galaxy Note II Q&A, Help & Troubleshooting] jkd:
I flash stock via odin

install TWRP via odin and restored EFS but still no IMEI

Maybe try 4.4 rom stock !!??
[Galaxy Note II Q&A, Help & Troubleshooting] mohit141785:
Yes you can try. Which boot loader you are on now

---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------

Also if you want to flash 4.4 then dont flash stock first. My advice would be to first flash any aosp rom 4.4 via recovery( after full wipe offcourse) then again try restoring your efs

---------- Post added 21st May 2014 at 12:00 AM ---------- Previous post was 20th May 2014 at 11:59 PM ----------

If even then problem persists then download stock 4.4 rom for your region from sammobile and flash via odin
[Galaxy Note II Q&A, Help & Troubleshooting] jkd:
no baseband

bootloader version: N7105XXUEMK9

there is no 4.4 for my region

i try to flash again
[Galaxy Note II Q&A, Help & Troubleshooting] eZdubzitmk4:
Well first of all the patch is for tmobile dude.

Just odin to stock and start over

Sent from my NoteII