OmniROM Unofficial Builds
As you all know, OmniROM has been announced yesterday. This brand new ROM contains a lot of new, exciting functionality. One of these new functions is the multi-window support! Just like ROMs on some Galaxy Notes, or the ancient Cornerstone, you can run two applications simultaneously! Aside from that, the best thing about this ROM is the focus on the community: while the ROM itself is not available yet, the developers behind it really seem to be willing to listen to the community, which is a really good thing.
As the team of OmniROM states on their website:
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. We offer you an alternative to other ROMs that may choose to water down their distribution at the expense of providing options for the user.
Click to expand...
Click to collapse
And the list of features as listed by XpLoDWilD in this topic:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
Click to expand...
Click to collapse
Unofficial builds
However, builds are not available yet. Logically, the ROM probably has not been thoroughly tested yet and that's why they are not building their source on a nightly basis. If you are as impatient as I am, you probably want to get your hands on this ROM as soon as possible! That's why I compiled OmniROM from source, for the Nexus 7 (grouper).
This flashable ZIP has not been tested yet by myself, but it should be OK. Compiled on Ubuntu 13.04 x86_64, completely as-is from the repository of OmniROM. Let me say again that this ROM is not modified by me; it is directly compiled from source and packaged into a ZIP. All credits go to the team behind OmniROM at http://omnirom.org.
Downloads
The builds below will probably be updated about every three days. I recompile from source whenever significant modifications are added to the multi-window functionality.
16/10 (working fine, with multi-window)
custom_grouper-ota-eng.chaoszx.zip (145.9 MB)
https://mega.co.nz/#!yEsHkDSa!PtTVqVPcvFY3FqP20M-1Vnq87rkVMPKJJ4aPuJA0IH8
14/10 (does not boot):
omnirom-4.3-20131014-NIGHTLY-grouper-unofficial.zip (138.7 MB)
https://mega.co.nz/#!HVF3DDAY!FveJvAE2Wffm2WNcezemTAwHYAleOKf13-zg82cZ118
Thank you
If you appreciate the time I spend to compile these ROMs from source for you, a donation would be appreciated as it would cover a bit of my expenses on power. Aside from that, I am hoping to save some money before I go to university next year, so any donation is much appreciated! PayPal donations can be sent to [email protected]. Thank you in advance for your support.
Notes
Multi-window can be activated by opening an app. Then go back to the launcher by pressing Home. Load up another app. Press the Multitask button, long-press the app you opened previously, and hit 'Split View'.
The Back button is not working at boot. To fix it, go to Settings > Language and Input > Default (under Keyboard & Input Methods) > Google Keyboard. The force closes of the AOSP keyboard won't happen now, and your Back button will work fine.
Reserved.
Reserved as well.
Flashing failed :/ Will try again.
Hypercaine said:
Flashing failed :/ Will try again.
Click to expand...
Click to collapse
Hang on, I am about to flash it on my Nexus 7. If it doesn't flash, I'll check what's wrong and fix it within an hour
Flashing right now, this is gonna be great!
Sent from my SCH-I535 using xda app-developers app
FAILED
set_perm: some changes failed
E:Error executing updater binary in zip ´/sdcard/
Error flashing zip
Same problem here
Confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
chaosz-x said:
confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
Click to expand...
Click to collapse
f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...
The issue with the flashing is resolved. Before uploading the new ZIP, I am investigating the ROM itself. Check back in about an hour at least
Eagerly waiting
Sent from my Nexus 7 using XDA Premium HD app
Chaosz-X said:
Check back in about an hour at least
Click to expand...
Click to collapse
This looks suspiciously like an ETA, if I ever saw one...
When installing, flashing failed. Also, upload to a site that is android-friendly? Mega is hard for me to use. Maybe mediafire?
Failed for me also.
Sent from my SCH-I545 using Tapatalk now Free
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
podagee said:
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
Click to expand...
Click to collapse
I take it you get a set_perm (status 7 error)? This has to do with the updater script trying to give permissions to a file that doesn't exist, it is relatively easy to resolve. I'll take a look once I get home. BTW, tilapia, mako and flo are probably officially supported, which is why they are mentioned, as this is an unofficial build, it isn't (yet) mentioned
Sent from my Nexus 7 using xda app-developers app
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Chaosz-X said:
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Click to expand...
Click to collapse
FWIW I'm having the exact same problem with my build....it won't boot. Using sources synced as of yesterday morning.
I'm also re-syncing to see if that helps.
Thank you for your efforts! Waiting to try it
God I hate this new ADB system in Jelly Bean. Only allows a logcat if you grant access through Android itself. But when your device doesn't boot, it is impossible to get live logcats atm. Still working on a fix and progress is being made though
Related
Team EOSJB 4.1.1 TF700TNIGHTLIES
Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Nightly builds:
Goo.im
Mirror1
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom. Please use these gapps rather than other gapps packages, as we know that this package works.
Gapps package gapps
--
Features:
Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Kernel Note: As with the rest of the GPL sources, the kernel can be found at http://git.teameos.org/eos/kernel/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery.
Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS or JB based rom.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
---
Enabling voice search in google now
Go into Settings
Go to "Language & input"
Scroll down to "Speech" and click on "Voice Search"
Click on "Download offline speech recognition"
Swipe Across to the "ALL" tab if needed
Download your speech pack for your language
hiemanshu is your maintainer for this device.
Known issues:
GPS
Portrait applications
Quick list of features:
Theme manager support
init.d
busybox
SuperSu for root access (can't live without root)
Colour customisation of the clock and statusbar
Soft key long press actions
Custom targets on he navigation key long-press popup ring (Where google now is shown)
Many many more
Nice! Thanks brother
Sent from my Transformer Pad TF700T using XDA Premium HD app
I'll jump in just for fun.
Wow now teameos comes through in a big way. Why haven't I unlocked yet again??
bigrushdog said:
I'll jump in just for fun.
Click to expand...
Click to collapse
hey bigrushdog! Now that EOS is here, I know this tablet has arrived!
My favorite ROM on the Transformer Prime has made the jump. Can't wait to get home and try this. Finally a reason to unlock and root my device.
Now I have a reason to change my stock recovery. Thanks a lot guys.
Sent from my HTC One X using xda premium
What can the CM10 version better than the others that it's here already?
The portrait bug is the one thing holding me back from flashing this. Grrrrrrr!
With the risk of pointing you to something either very stupid or very obvious, or both, the ROM referenced here:
http://forum.xda-developers.com/showthread.php?t=1779133
reputes it has fixed the screen tearing, and enhanced portrait mode (and some not specified fixes to portrait mode). Would it be of use to contact the dev and see what (s)he has been up to?
What about the lag problem with bluetooth headset we have with stock ROM ?
Does it still exist with this ROM ?
And I will maintaining this ROM as well. So contact me for any issues Working on solving the tearing and portrait mode issues
Sent from my Galaxy Nexus using xda app-developers app
bigrushdog said:
I'll jump in just for fun.
Click to expand...
Click to collapse
Mother effer!!! Bigrushdog from miui on the evo 4g? Of so what's the chances of getting miui on the infinity?
Sent from my SPH-D710 using Tapatalk 2
gmfeny said:
Mother effer!!! Bigrushdog from miui on the evo 4g? Of so what's the chances of getting miui on the infinity?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You want me to try that too
hiemanshu said:
You want me to try that too
Click to expand...
Click to collapse
Jesus, what can't you do?
Sent from my JellyBean Burrito (Inspire 4G)
Will this fix the I/O-issues?
i get lots of reboots, to the point of being unusable what has this rom got to offer that cm10/bb/others dont?
Drewman294 said:
Jesus, what can't you do?
Sent from my JellyBean Burrito (Inspire 4G)
Click to expand...
Click to collapse
Sprint faster than Bolt
Can't get the rom to boot. It gets stuck at the Asus logo.
Unlocked ICS bootloader
Twrp 2.2.2.1 the latest.
Fully wiped including data, system, Cache and dalvik.cache
Then installed hiemanshu's cm10 9/14 alpha and boots fine.
And for some strange reason
I can't go into fastboot. It says starting fastboot USB download however don't see the device in fastboot. Just waiting for device. All win drivers are installed. I do see Asus bootloader in device manager.
I was going to erase cache from fastboot just like my hox.
EDIT I'm not sure about seeing Asus bootloader while in fastboot. Have been at this for 5 hours now. So if you ask me my name I probably say Asus bootloader
EDIT2 I think fastboot issue is resolved. Thanks hiemanshu.
Sent from my HTC One X using xda premium
I no longer seem to have access to fastboot either...
MartyHulskemper said:
I no longer seem to have access to fastboot either...
Click to expand...
Click to collapse
fastboot -i 0x0B05 devices try that
Fourth Night NightliesFreshly build every fourth night
Disclaimer
YOUR WARRANTY IF NOW VOID
I am not responsbile for bricked devices, dead SD Cards,
or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in the ROM
before flashing it!! YOU are choosing to make thse modifications, and if
you point the finger at me for messing up your device, I will laugh at you!
I would still consider this a "beta" release as its still so new and there will be bugs with it. I don't do anything to this version besides sync repo, small changes, and build. If you looking for a modified version of CM10.2 Check out my androfly for flo. Its modified and has linaro
Features:
CM10.2
Android JB 4.3
Root
Busybox
Working OTA system
Apollo
Camera/ Focal
CM File Manager
Zipaligned
All Images, Sounds, APK's Optimzed
Install Instructions
Download Latest ROM
Place on the Root of your SDCard
Reboot into Recovery
Scroll down and select "wipe"
Select factory reset/wipe data
press return
Select install ROM
Install GAPPS (optional)
Reboot and Enjoy all the Happiness that is CM10.2
Downloads
ROM Builds - ACTIVE-
Download the Latest
FAQ
Q: After I flash your ROM, I lost root. How do I regain root access
A: You actually didn't lose root, you just need to re-enable root access. Follow these steps
Settings
Click on Developer Options (if you don't see developer options follow the next 2 steps)
Scroll to About Tablet
Click on Build Number 7 times to enable Developer Options
Then click on Developer Options
click on root access and change to apps and ADB
Q:
Mine too
Can't wait to get home and download!
Sent from my SCH-I605 using XDA Premium HD app
Just curious, are you actually part of the team or just posting the thread?
whoamanwtf said:
Just curious, are you actually part of the team or just posting the thread?
Click to expand...
Click to collapse
No not part of the team, I downloaded the source code a while ago, but updated and built this this morning. It was official as of last night I was following cm10.2 pretty closely as I was working on stuff for a couple other devices i build for. Im also working on a Linaro stock version for us
Upload is almost done...a few more mins
Was emoji support removed? I swear I had emojis when I used Tablet Talk on my 2012 Nexus 7, but it's not working here. Am I missing something?
A.C.Sanchez said:
Was emoji support removed? I swear I had emojis when I used Tablet Talk on my 2012 Nexus 7, but it's not working here. Am I missing something?
Click to expand...
Click to collapse
Not that im aware of, I can look and see if it was or not. I normally dont use emoji's
Official build!! Sweet!
Sent from my Nexus 7 using Tapatalk 4
Thread title should be UNOFFICIAL to avoid confusion.
CMNein said:
Thread title should be UNOFFICIAL to avoid confusion.
Click to expand...
Click to collapse
This is the Official source, not modified, so its the same builds as you will see from them and its also officially supported by them. Unofficial would be something that is not support by the cyanogenmod team... so its really not unofficial
clmowers said:
This is the Official source, not modified, so its the same builds as you will see from them and its also officially supported by them. Unofficial would be something that is not support by the cyanogenmod team... so its really not unofficial
Click to expand...
Click to collapse
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Anybody having any luck using this build with SlimPort?
When I plug in to an HDMI device the Nexus 7 soft resets.
Thank you for any insights.
CMNein said:
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Click to expand...
Click to collapse
He's right this is not an official thread. Hope mods see this and get the title changed. Fooled me.
Don't like me........BITE ME!!!
justibasa said:
He's right this is not an official thread. Hope mods see this and get the title changed. Fooled me.
Don't like me........BITE ME!!!
Click to expand...
Click to collapse
Yeah, not trying to give him a hard time, but XDA readers can get confused easily at times.
Wow just flashed and got 6799 on quadrant.
Sent from my GT-N7105 using xda app-developers app
CMNein said:
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Click to expand...
Click to collapse
Yeah, I found out lol. I was under the impression that if its officially supported by them and source was from their repo, and built using their stuff, it was official my b./..but either way every 4 nights official or not lol
digweed4me said:
Wow just flashed and got 6799 on quadrant.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
How can I enable root?
I've read a few things that we have to manually root after we flash roms, but my toolkit isn't reading my tablet when I connect it...
Is there a flashable zip for root?
Kevin Goot said:
How can I enable root?
I've read a few things that we have to manually root after we flash roms, but my toolkit isn't reading my tablet when I connect it...
Is there a flashable zip for root?
Click to expand...
Click to collapse
Root is installed already, What you might have to do is to enable it in the dev options
Android 4.4
S3 builds are focused on being a simple, stable, and "stock-like" experience for your Android device.
View the source code at: http://github.com/jakdillard
----------
Developed by:
Jakdillard
----------
Devices currently supported:
Asus Nexus 7 (2013)
LG Nexus 5
S3 includes modifications to extend the basic functions of Android. With each update to Android, S3 features may change to work with the current version.
Feature list:
- Full Google Experience
- Clear Recents with VM Cache drop
- Reboot In Power menu
- Screenshot In Power menu (enable in developers settings)
- Advanced Reboot options (enable in developers settings)
- Swapped "on click" and "longpress" behavior for WIFI, Mobile network, and BlueTooth tiles
- Init.d support
- SuperSU root
Instructions:
First time flashing device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Fastboot oem unlock > fastboot flash recovery recovery.img.
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Known Issues:
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ and Picasa album viewing. Also I DO NOT USE FACE LOCK SO I DIDN'T INCLUDE IT SINCE I BELIEVE ITS A WASTE OF SPACE.
ROM: Link
G-Apps (INCLUDED)
Follow the above link for the complete source to make your own changes or to completely debug down to the core of the rom also follow my github for detailed changes.
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project.
WANT TO CUSTOMIZE THIS ROM READ THIS:
Want to add or remove anything or customize for yourself use DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs.
Hi. Just installed this and I like it. A few others have been having issues with chrome and location services causing soft reboots and really bad stability. This ROM does not have that problem. I tried first with the full PA gapps and had issues with Google search and the Google calendar FC. Wiped and clean installed and used the Banks gapps. All is good now.
Gonna go install the Elemental X kennel now.
Thanks for the ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app
going to try this and add some tweaks to it get more power of using aosp
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
ridobe said:
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
Click to expand...
Click to collapse
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
I have to look over those other roms sources to see what they are missing more the likely they don't have the location services pointing to the right adapter or still using the old way of making device trees causing make to not put the overlays together correctly.
Nice ROM Jak!
Syncing your Repo now!
Update 10-29-2013
http://d-h.st/RlW
10-29-2013
Added Google Play Edition Bootanimation
Added missing Flo props ( sound should be a little better )
Added missing proprietary DRM
De-Odexed ROM
Update 11-3-2013
Well there a beta quality build of KitKat in the op this will not be a daily driver until I have a complete source to work with and proper proprietary binaries but good luch and enjoy. Also consider this a nightly project as features will slowly be added.
Always under the radar for some reason, but your builds are always fantastic. Great job as always on 4.4. Loving the additional features.
Update 11-6-2013
http://d-h.st/bjj
New update but still no camera
jakdillard said:
http://d-h.st/bjj
New update but still no camera
Click to expand...
Click to collapse
Changes?
dictionary said:
Changes?
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 7 mit Tapatalk 4
dictionary said:
Changes?
Click to expand...
Click to collapse
I know he added a file manager and volume rocker wake. Those two weren't in the OP for the first build.
Sent from my Nexus 7 using Tapatalk 4
Unfortunately flash fails inTwrp 2.6.3.1.
Awesome. Best KitKat ROM of all I have tried so far. Smooth and no fc or other issues at all so far. Stable in tests that other ROMs have failed. Thank you!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Mindrocket said:
Unfortunately flash fails inTwrp 2.6.3.1.
Click to expand...
Click to collapse
I believe twrp has updated to 2.6.3.2
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
Every last person using any 4.4 with the new Google Experience Launcher.
jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
I just double tap the home button. It's less annoying.
Love Jack's creations. Keep up the great work and thanks for sharing.
Why Omni?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Taken from http://omnirom.org/why-omni/
Screenshots and more info are here
BACKUP YOUR PHONE!!!
* Your warranty was void when you started messing around with your phone.
* These builds are unofficial and are unsupported.
* ONLY YOU AND NO ONE ELSE IS RESPONSIBLE FOR ANYTHING BAD THAT MIGHT RESULT FROM FLASHING THIS ROM!
* Finally Blah Blah Blah good luck!
This ROM probably has the same requirements as any other AOSP 4.4 based rom with the 3.4.x kernel.
Nandroid and then a full wipe.
ROM when its up you can Download Here
PA 0-Day Gapps Get it here
if needed SuperSU 1.75
KNOWN BUGS
Probably whatever is wrong with other KitKat 4.4 roms so...you tell me?
This is based on work done by xHausx for the HTC Evo 4g LTE. You can view the original thread HERE
Thanks
Especially xHausx for the device and common repos and for taking the time to help me get the build process running.
intervigilium for kernel and device repos, because without him most HTC devices would still have Sense
XpLoDWilD, pulser_g2 and all of Team OmniROM
CM for the various repos and for all they've done for the community
XDA:DevDB Information
OmniROM, a ROM for the HTC One S
Contributors
mo976, xHausx
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Abandoned
Created 2013-10-31
Last Updated 2013-12-03
Reserved
NO SD CARD!!!
A fix is being worked on but... NO ETA's
Looks promising. Cant wait to try it.
Thanks for keeping the One S alive.
Gotta try this! Thanks
Sent from my One S using XDA Premium HD app
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
yooouuri said:
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
Click to expand...
Click to collapse
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
mo976 said:
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
Click to expand...
Click to collapse
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Flashalot said:
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Click to expand...
Click to collapse
Well I'm trying anyhow after going through the various dependency files just to double check. I'm hoping it was just a bad build or something so I am pulling down the repo from scratch and hopefully will have a new build in a few hours.
Sent from my One S using XDA Premium 4 mobile app
Looking forward to this
And maybe try the 1.20 radio...
First working build is up try it out let me know!
mo976 said:
First working build is up try it out let me know!
Click to expand...
Click to collapse
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
nespresso33 said:
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
Click to expand...
Click to collapse
I noticed that but wasnt sure if its a feature or bug...lol it seems to come and go...
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
yooouuri said:
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
Click to expand...
Click to collapse
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
mo976 said:
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
I will check if that's whats missing. I am not sure how to disable strict mode by default since its a setting. Lock screen delay should be the same as cm since its the same kernel.
Sent from my One S using XDA Premium 4 mobile app
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
mo976 said:
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
Click to expand...
Click to collapse
Maby a logcat will give the information you'll need?
yooouuri said:
Maby a logcat will give the information you'll need?
Click to expand...
Click to collapse
I understand what it says but...it may as well be Chinese because I am not any closer. I attached if you want to take a look.
[ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw)
CyanogenMod and D2VZW: Together Again!
--------------------DANGER!! CMUpdater is providing the new CM13 Marshmallow nightly builds and notifying you of an update. IT SEEMS THERE ARE NO MORE UPDATES FOR CM12! 12/10 seems to be the last one. If you flash CM13 without looking into things first, you could be in for a world of hurt! Check out invisiblek's Official CM13 Nightlies thread in this same forum. BEWARE!!--------------------
De-unified Lollipop builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances... If you've done it or want to try, please tell us what happens.)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will put a picture
* of you up and throw darts at it.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit the Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Regarding the Stagefright Exploit: The latest patch update to protect against the security vulnerability was merged for the 8/14 nightly. Please update to that or later to make sure you are fully protected, though work still continues.
XDA Article on the Stagefright Exploit: http://www.xda-developers.com/stagefright-explained-the-exploit-that-changed-android/
Download Links :: Download Links Broken!! - On or about 12/18 the links for 12.1 ceased to function. The links for 12.1 and 13 are all listed on the same page at the moment as well. While 12.1 builds have continued to come out every few days or so for other devices, the last one for the d2vzw is for 12/10 at the moment. I don't know if this is a temporary of permanent state of affairs but inquiries are forth coming. In the mean time, the 12/10 build is in the "d2vzw ROM Extras" link below so at least we got that, thanks to XdrummerXboy.
Also, if you have a build from about 11/15 and later hanging around you could upload it for others to access, if need be, by following the instructions from this post: Upload Instructions
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly LINKS ONLY WORKS FOR CM13 NOW!!
Download with daily commits tracked:http://www.cmxlog.com/12.1/d2vzw/
>>These are the de-unified d2vzw builds now instead of the d2lte builds you previously used<<
Google apps addon:
TK Modular GApps by TKruzze. Get your GApps from the Master. Follow his installation instructions.
Open GApps:opengapps.orgThey are modular AND have the option of Aroma Installer. Updated daily. Very interesting story on these. There is the website, and an XDA thread.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
Other Options:
The Gapps Central For those of you who just have to be different, a GApps Smorgasbord, by TheXGX
Banks Gapps removed after just one too many malfunctions... If you use 'em and have a problem, update from the Play Store your offending app or flash one of these others, but don't come complainin'.
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
A MF1 firmware only zip is in the "d2vzw ROM Extras" link below, as well as individual modem choices.
Other Possibly Useful Stuff
d2vzw ROM Extras
Link to TWRP Recovery You can flash the .img file right in TWRP recovery 2.8.4 or later!
- All you ever wanted to know about how Cell service works but were afraid to ask: Cell Wiki
- Samsung Galaxy S 3 the most popular phone of all time? Still? https://en.wikipedia.org/wiki/Samsung_Galaxy_S_III
Notes - Possible Bugs
Bluetooth observed as flaky with some connected devices.
CMUpdater apparently only functional with TWRP 2.8.7.0
4G/LTE Data might not start on bootup (lately) - With Wifi disconnected or off, go to Settings>Mobile Networks>Access Point Names and select one of those not already selected. Give it a few seconds. Should be good till next reboot.
Addendum to Data Issue: If you can't live with the above solution (like me) then downgrading to the ML1 modem has fixed it, seemingly without any ill effects. Modem is in the "d2vzw ROM Extras" link above.
>>Attention ATT, T-Mobile and other GSM Network Users (International)<<
If you use your d2vzw on one of the GSM networks, you will have to flash the d2gsm_rilblobs.zip file in the 'd2vzw ROM Extras' link above or your phone won't operate properly!
The CyanogenMod team (of which I'm not a member) always thanks everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Another Note: CM12 was introduced to our phone first by mastamoon and Invisiblek: Many thanks to them! There may be data on those threads that can help someone, so I've included those links for reference:
Mastamoon's Unofficial CM12 (and cm11) thread.
Invisiblek's Unofficial CM12 thread by amf66.
<Disclaimer: OP is not a Dev. Just a normal schlub.>
XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
Master Cylinder, Nardholio, Device Maintainer: Nardholio
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VRBMF1
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-20
Last Updated 2017-06-10
YES!!! Long live the GS3... ?
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
NoCrAppleHere said:
YES!!! Long live the GS3... ?
Click to expand...
Click to collapse
Agreed!
Sent using Tapatalk
Master Cylinder said:
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1
Click to expand...
Click to collapse
A link or two would be a great addition.
Thanks for the thread!
phonetool said:
A link or two would be a great addition.
Thanks for the thread!
Click to expand...
Click to collapse
@Master Cylinder, you can use mine for now.. http://mastamoon.truelinux.net/firmware/ Just note that you have to flash the firmware first, then the modem. Otherwise the firmware, which contains a modem, will overwrite the newer modem.
CyanDelta sounds greate. However, I get FC with it. Reboot does not help.
I'm on 5/13 nightly.
Anyone has the similar problem?
yorkwar said:
CyanDelta sounds greate. However, I get FC with it. Reboot does not help.
I'm on 5/13 nightly.
Anyone has the similar problem?
Click to expand...
Click to collapse
And you downloaded or had a 5/13 build zip to operate from to setup? And you had at least 750mb free space before pushing the zip over or dloading it? Maybe one needs more than that amount space? When did it fc?
When looking at the Google Apps linked above, what is the difference between arm and arm64?
Sent from my ME173X using XDA Free mobile app
XdrummerXboy said:
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It's a good thought. Hmmm.... In 2 weeks this will have 15 pages and probably no need to go back, but I'm certainly still open to it if others want it.
phonetool said:
A link or two would be a great addition.
Thanks for the thread!
Click to expand...
Click to collapse
mastamoon said:
@Master Cylinder, you can use mine for now.. http://mastamoon.truelinux.net/firmware/ Just note that you have to flash the firmware first, then the modem. Otherwise the firmware, which contains a modem, will overwrite the newer modem.
Click to expand...
Click to collapse
Thanks masta. Yeah, I was contemplating putting up Dropbox links (was a little blurry eyed last night.) I just remembered Invisiblek still has some up. Also, I guess I could put up Google Drive links which are never gonna go away....
brandonb0013 said:
When looking at the Google Apps linked above, what is the difference between arm and arm64?
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I knew I'd left an unanswered question there. They just started listing them this way. Use the 'arm' which is for our phone. I'll update that on the OP, maybe put a little explanation, when I get more coffee in me... :silly:
Yeah I knew I'd left an unanswered question there. They just started listing them this way. Use the 'arm' which is for our phone. I'll update that on the OP said:
Great. I love how everyone is quick to answer any questions people have. That's what makes flashing so enjoyable. Anywho, when I do my next flash, I'm going to try using those linked gapps. Changing of it fixing my BT crashes? Probably slim to none. But it's worth a shot!
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
1 vote to link both earlier threads
Would be good to link MM's and amf66’s Invisiblek threads. There's a lot of info and the Cm12x development progressed very quickly, so most info is still fairly current.
But then, I minored in history, sooo....
XdrummerXboy said:
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
AyUaxe said:
Would be good to link MM's and amf66’s Invisiblek threads. There's a lot of info and the Cm12x development progressed very quickly, so most info is still fairly current.
But then, I minored in history, sooo....
Click to expand...
Click to collapse
The speed of progress is what makes those threads age so quickly, but for those of you who are sentimantal, and to afford worthy applause to @mastamoon and @invisiblek, I've put in links.
"Another Note: CM12 was introduced to our phone first by mastamoon and Invisiblek: Many thanks to them! There may be data on those threads that can help someone, so I've included those links for reference:
Mastamoon's Unofficial CM12 (and cm11) thread.
Invisiblek's Unofficial CM12 thread by amf66."
Links work there.
OK, gonna try a clean install with the gapps in the op. Try not to restore from titanium as much as possible. This last install I had bluetooth problems and lost count of the restarts whether charging or not. See how this goes.......
stevet86 said:
OK, gonna try a clean install with the gapps in the op. Try not to restore from titanium as much as possible. This last install I had bluetooth problems and lost count of the restarts whether charging or not. See how this goes.......
Click to expand...
Click to collapse
What kind of bt issues? Bt share has stopped? Also, i never had issues with reboots on any flashes I've performed. Only issue for me is bt.
Sent from my ME173X using XDA Free mobile app
Why no updates since the 18th?
Shakes The AssClown said:
Why no updates since the 18th?
Click to expand...
Click to collapse
Yeah, it's been a few and there's a lot of commits piling up but he did put out builds for 17 days in a row so I guess we got to cut him some slack.
brandonb0013 said:
What kind of bt issues? Bt share has stopped? Also, i never had issues with reboots on any flashes I've performed. Only issue for me is bt.
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
I have to go into the Bluetooth settings and manually connect my headset whenever I turn it on. I can see it there but it never connects until I select it.
stevet86 said:
I have to go into the Bluetooth settings and manually connect my headset whenever I turn it on. I can see it there but it never connects until I select it.
Click to expand...
Click to collapse
Hmm. Mine always connects, just shuts off randomly. Let me know if it helps. I see the next nightly is quite extensive but so far no BT changes. I plan on trying it though
Fyi, I'm going to go into rehab soon bc I'm having nightlies withdrawal. ???