What is it?
This is a FlashCast mod to give your Chromecast a nearly stock OS. Although Team Eureka (obviously) believes that the features we've added to Eureka-ROM make it superior to the stock OS, we realize that it's not for everyone. Perhaps you want a clean base to develop from, or maybe you want want to try out a new feature from Google before Eureka-ROM is updated. Either way, the last thing we want to do is force you to use a ROM you don't want. To that end, this ROM is completely stock, save for two modifications:
update_engine is removed so that your vulnerable bootloader is preserved.
FlashCast is installed to the recovery partition instead of the stock recovery, to mitigate any bootloader updates Google may try to push through other methods.
Please note that this ROM contains no SSH, ADB, Telnet, or other means of remote shell access. In addition, it has no OTA system, so it is your responsibility to update to newer versions using FlashCast. We recommend that you use Eureka-ROM instead unless you have a specific reason for wanting a stock experience.
Where do I get it?
Build 44433 (latest version):
http://pdl.team-eureka.com/minimal/44433.zip
SHA256: 3cdebca7789d3024b036fdd2e82a06bbf6015d8fa2bf8f0a4f85fe819419cc73
MD5: c536136b76839fca00cf49dd220bb6a0
Build 27946:
http://pdl.team-eureka.com/minimal/27946.zip
SHA256: 56d35b1c06ed116aa3ee93f10fcf08b92b6a92c280a53d20c98a2d949d29b9f9
MD5: c74e4d3791847152ebde11e2090970eb
Build 26653:
http://pdl.team-eureka.com/minimal/26653.zip
SHA256: b1c62828e76b35da918aad438bc598c52c407e657431bc397664616e83d24fc9
MD5: 6db4d1c8fe7ab20268f4e99f3c70667f
Build 22062:
http://pdl.team-eureka.com/minimal/22062.zip
SHA256: cf6c2b4b1b2603abed51efc2cb39d7a6f882669946e8d879b5d1e4fd13156db9
MD5: cfaa7e4ca5f9686eb96dcb36e531c3f2
Build 19084:
http://pdl.team-eureka.com/minimal/19084.zip
SHA256: 74fa139c87c7affc5dab5f27cd1623845a89606d80fbfa7d5505bc137ece25a6
MD5: 271e628598dff919199e684921d158ff
Build 17977:
http://pdl.team-eureka.com/minimal/17977.zip
SHA256: fd5fd2daa40b5915f729e96e467c904a79f541196bb512679a61b3376cc49672
MD5: 54f4513432447156cd46fc868dffc487
Build 17250:
http://pdl.team-eureka.com/minimal/17250.zip
SHA256: 26d127c75d57d7aa4b8900cb27f3a3bba5f2690840f3e1dfa7c581bfb7c0aeec
MD5: c9adbd48d6e58113ec30ed8cd136bf16
Build 16664:
http://pdl.team-eureka.com/minimal/16664.zip
SHA256: 9a657d0b7945cf69c8127deb5a98f198a74cd959c09aae250f81ec3ad4a0f7e4
MD5: d961b63a2112294cfa6eefcf3eee205d
Build 16041:
http://pdl.team-eureka.com/minimal/16041.zip
SHA256: 212dfde7cd34a09a8699b9eb2064da34bac3f973cbce5bb7952ecdcdd1608c09
MD5: eac8b93a2da723fb29eb7ea7be4744cf
Build 15250:
http://pdl.team-eureka.com/minimal/15250.zip
SHA256: 54af712df8edf165de63d6f690642d234d12e8cd01889f877bf9fe93ef8a807a
MD5: e8a51bdbcd4e96da3a13b539ca314da4
Just to clarify. It has Google Whitelist right?
mathorv said:
Just to clarify. It has Google Whitelist right?
Click to expand...
Click to collapse
Yeah, all stock Google, no custom whitelist in this one.
If we are currently still running the Eureka ROM based on 14975 and using the custom whitelist feature that you guys integrated into the 14975 Eureka ROM image, would it CURRENTLY be possible for us to take advantage of all these new apps that are going to be flooding the Google Play Store/Chrome(PC browser apps/extensions) Web Store, or MUST our Chromecast be the newest updated version 15250(with either a future Eureka ROM update to 15250, by flashing this "nearly stock OS build" 15250, or simply someone just has a stock, NON-rooted Chromecast that has taken all the OTA updates and has recently updated itself via an OTA to the newest stock 15250 firmware build) ? I understand that by using Eureka ROM's "custom whitelist" that you guys manually update the whitelist yourselves and it's obviously not physically possible to update your whitelist fast enough to keep up with the "stock Google whitelist," thus always lagging slightly behind the stock Google whitelist AND quite possibly accidentally leaving out some of the lesser-known Android apps and/or Chrome Apps and/or Chrome Extensions that have been added by Google to their stock whitelist, due to the simple fact that you guys just haven't learned of them yet or just haven't been told of them yet?
Basically, if one wants to be able to take advantage of all these new apps that will be flooding Google's stock Chromecast whitelist over the coming weeks/months, etc., to cover all our bases right now so that we're not either hoping that you guys find out about lesser-known apps such as, for a hypothetical example: XCompany's "FancySchmancy Chromecast Media Caster", should we use this upload that you posted so that we're on the newest 15250 and use the stock Google whitelist? Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Could this installed on ANY ChromeCast or just ROOTABLE Chromecasts?
does this require a chromecast that has been already rooted?
or can i use this on my unrooted chromecast without the vulnerable bootloader?
In order to install this Vanilla Chromecast 15250 with blocked OTA.
Chromecast has to be ROOTable and has to be flashed with [FLASHER][v1.1.1 - 2013-11-29] FlashCast
It works 100% THE SAME AS non rooted 15250 Chromium, nothing special about it. It's taste of 15250 for develpers and people bored with feature rich 14975.002 eureka mod.
BTW: Great idea for future development cycle - quick minimal releases before major releases.
EDIT:
Works as should and for sure Whitelist is by Google so Fling is not available, AllCast is working like a charm.
jsdecker10 said:
Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Click to expand...
Click to collapse
No. It's not a whitelist issue as the Team-Eureka whitelist includes what's on the Google whitelist.
Apps built on the released SDK require:
On Chromecast: The "magic stuff" that is in the 15250 build (or newer)
On casting device (for Android): The "other magic stuff" that is in Google Play Services 4.2.34 (or newer)
Being present on Google whitelist (or Team Eureka whitelist)
Eureka-ROM v1.1 is built on 14975, so it fails condition 1 for new apps.
Stock Chromecasts should have auto-updated to 15250 already.
Installing this stock, root-preserving, non-updating, no features added ROM will give you:
All Google official apps, including the new releases built on the released SDK
That's it.
No unapproved/beta apps (at the time of this post this includes fling, vbukit, and Audiour)
No ADB, SSH or Telnet
None of the other Eureka-ROM features (static IP, alternate DNS, web panel, etc)
jsdecker10 said:
If we are currently still running the Eureka ROM based on 14975 and using the custom whitelist feature that you guys integrated into the 14975 Eureka ROM image, would it CURRENTLY be possible for us to take advantage of all these new apps that are going to be flooding the Google Play Store/Chrome(PC browser apps/extensions) Web Store, or MUST our Chromecast be the newest updated version 15250(with either a future Eureka ROM update to 15250, by flashing this "nearly stock OS build" 15250, or simply someone just has a stock, NON-rooted Chromecast that has taken all the OTA updates and has recently updated itself via an OTA to the newest stock 15250 firmware build) ? I understand that by using Eureka ROM's "custom whitelist" that you guys manually update the whitelist yourselves and it's obviously not physically possible to update your whitelist fast enough to keep up with the "stock Google whitelist," thus always lagging slightly behind the stock Google whitelist AND quite possibly accidentally leaving out some of the lesser-known Android apps and/or Chrome Apps and/or Chrome Extensions that have been added by Google to their stock whitelist, due to the simple fact that you guys just haven't learned of them yet or just haven't been told of them yet?
Basically, if one wants to be able to take advantage of all these new apps that will be flooding Google's stock Chromecast whitelist over the coming weeks/months, etc., to cover all our bases right now so that we're not either hoping that you guys find out about lesser-known apps such as, for a hypothetical example: XCompany's "FancySchmancy Chromecast Media Caster", should we use this upload that you posted so that we're on the newest 15250 and use the stock Google whitelist? Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Click to expand...
Click to collapse
1. Any new apps that use the new API will not be available in the current Eureka-ROM that is based on 14975. This is because the new API is not enabled in its Eureka_shell binary, which is the program on the device that literally runs almost every application.
2. Our custom whitelist is no longer a manual entry process, and auto updates when google pushes new applications. This means rooted devices now get apps just as fast as stock devices, as long as they are on a ROM version that supports said application.
3. Disabling the custom whitelist on the 14975 based rom will not allow you to use the V2 API apps, as I stated in #1
We are working on a new version of Eureka-ROM, but are just having a few small things hold us back. This is why the release is taking longer then normal, and as such, we released this minimal image for those who would like to update for the time being.
Just posted build 16041 for you crack flashers out there, enjoy!
Can you post the Google ota link also for these?
Sent from my XT1060 using XDA Premium 4 mobile app
jay0lee said:
Can you post the Google ota link also for these?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We do not post those publicly because we don't want users accidentally flashing the update and loosing the ability to root. Please shoot me a PM if you would like the direct link from google for the OTA.
ddggttff3 said:
We do not post those publicly because we don't want users accidentally flashing the update and PERMANENTLY losing the ability to root. Please shoot me a PM if you would like the direct link from google for the OTA.
Click to expand...
Click to collapse
(Emphasis and typo fix added ). Remember, FlashCast relies on an exploit that any unmodified Google OTA will patch, so applying a stock Google OTA won't just result in a tempory loss of root, it's a permanent and irreversible loss of root.
A new exploit would need to be found in order to get root back, and at least so far there doesn't seem to be one in sight.
So that's why Team Eureka is being overly cautious.
Just wondering if this was sent out to Chromecasts? I just checked my version number and am on the latest. Unless something else happened (I've had frequent unable to boot messages a couple weeks ago and rebooting fixed them).. my Eureka ROM may have been wiped.
ralphwiggum1 said:
Just wondering if this was sent out to Chromecasts? I just checked my version number and am on the latest. Unless something else happened (I've had frequent unable to boot messages a couple weeks ago and rebooting fixed them).. my Eureka ROM may have been wiped.
Click to expand...
Click to collapse
No, this is strictly a download and manually flash thing.
What makes you think your Eureka ROM has been wiped? Can you no longer get to the web panel at http://ip_of_chromecast ?
bhiga said:
No, this is strictly a download and manually flash thing.
What makes you think your Eureka ROM has been wiped? Can you no longer get to the web panel at http://[i]ip_of_chromecast[/i] ?
Click to expand...
Click to collapse
No web interface, and Chromecast app shows the latest.
The one I flashed manually was the one with the older FlashCast (which would be the first Eureka ROM). At some point I may have come back to stock without my knowledge.
ralphwiggum1 said:
No web interface, and Chromecast app shows the latest.
The one I flashed manually was the one with the older FlashCast (which would be the first Eureka ROM). At some point I may have come back to stock without my knowledge.
Click to expand...
Click to collapse
Spontaneously returning to stock is highly unlikely - the update parts are removed/disabled in Eureka-ROM and rooted stock ROM. And true stock ROMs aren't posted to avoid accidents.
There was a previous potential issue where interrupting an update could leave you in a partial state that seemed like a stock ROM, though. (Can't find the post...)
The $1M question is - does FlashCast still boot? If so, you are fine and can simply re-flash Eureka-ROM or rooted stock.
bhiga said:
Spontaneously returning to stock is highly unlikely - the update parts are removed/disabled in Eureka-ROM and rooted stock ROM. And true stock ROMs aren't posted to avoid accidents.
There was a previous potential issue where interrupting an update could leave you in a partial state that seemed like a stock ROM, though. (Can't find the post...)
The $1M question is - does FlashCast still boot? If so, you are fine and can simply re-flash Eureka-ROM or rooted stock.
Click to expand...
Click to collapse
I just posted a question here: http://forum.xda-developers.com/showpost.php?p=51084756&postcount=575 which is exactly the same. I was on EurekaROM before and am now on 16041 stock firmware without my consent. I'm going to try flashing to see if I'm still rooted.
Can you still flash a different DNS with this ROM?
Rooksx said:
Can you still flash a different DNS with this ROM?
Click to expand...
Click to collapse
Yes you can flash the DNS modification packages that were released awhile ago.
Just posted OTA 16664, enjoy!
Related
Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.
File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.
It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve
There are 3 stock firmware updates since last Eureka - stock with updates disabled and Eureka Mod
31432, May 22, 2015, General bug fixes and stability improvements
https://www.google.com/search?q=chromecast+firmware+31432+site:productforums.google.com
32904, June 18, 2015, General bug fixes and stability improvements
https://www.google.com/search?q=chromecast+firmware+32904+site:productforums.google.com
38401 ,? ,?
https://www.google.com/search?q=chromecast+firmware+38401+site:productforums.google.com
Thanks to [FLASHER] [v1.3 - 2014-07-07] FlashCast we got reliable recovery and from my point of view it's the only way to make Chromecast unbrickable. From my point of view it's the major advantage of rooting Chromecast.
If Chromecast is unbrickable why not to make Eureka - stock with updates disabled and Eureka Mod people can revert to any stable version if they'll feel that new versions will not suit them.
Questions:
Does anyone use any advanced features of Eureka Mod?
Is Eureka Mod OTA the only feature of the Mod people use?
Is it time consuming to compile stock with updates disabled?
Can anyone but Eureka Team compile Stock with updates disabled or Eureka?
Yes it's possible to unroot Chromecast - Eureka Team can provide you with revert-to-stock firmware.
i don't see the point.
doing all that seems like way more work than just keeping a parity with extras (that you don't have to use). you can stop updating or jump around on versions of eureka already...
2¢
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
You might try to ask the tech support what is in this update for example the MMS fix surely feels like must have (well known by now mms bug allowing to execute a code send by mms) but if that something you could manage to dodge on your own then just ignore it.
About the ROM with some nice looks n feels well we don't have any TBH we don't have any so called "daily driver" at all but I can suggest installing a custom launcher some of the more liked ones were on sale not so long ago you just have to track the app sales
I don't suggest any cause I don't know the forum rules regard the advertising.
Edit: There's Cyanogenmod 12 but it's bugged, not something u want to use daily.
ioy said:
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
Click to expand...
Click to collapse
There's only 1 rom available for the 64 bit and that's the one patrik made the cm12 and it has a good amount of bugs so it's not suggested as a daily driver yet. Nothing else but that and stock.
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436
syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.
TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs
I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.
ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from
syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?
saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs
Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.
You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".
I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk
Yeah, can't get it to stick on a stock 932.
You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.