Intro
This is a bit different than most postings here, as I'm not providing any binaries to install on your phone and instead providing a simple tool, rattlesnakeos-stack, to build your own OS based on AOSP on a regular basis, with your own signing keys, and your own OTA updates. This probably will be interesting to a small subset of users as it does cost money to run this infrastructure in AWS.
What is RattlesnakeOS
RattlesnakeOS is privacy focused Android OS based on AOSP for Google Pixel phones. It is my migration strategy away from CopperheadOS (hence the name similarity) which is no longer maintained.
Features:
Based on latest AOSP 9.0 (Android P)
Support for Google Pixel, Pixel XL, Pixel 2, Pixel 2 XL
Monthly software and firmware security fixes delivered through built in OTA updater
Maintain verified boot with a locked bootloader just like official Android but with your own personal signing keys
Latest Chromium browser and webview
Latest F-Droid client and privileged extension
Free of Google’s apps and services
What is rattlesnakeos-stack
Rather than providing random binaries of RattlesnakeOS to install on your phone, I've gone the route of creating a cross platform tool, rattlesnakeos-stack, that provisions all of the AWS infrastructure needed to continuously build your own personal RattlesnakeOS, with your own signing keys, and your own OTA updates. It uses AWS Lambda to provision EC2 spot instances that build RattlesnakeOS and upload artifacts to S3. Resulting OS builds are configured to receive over the air updates from this environment. It only costs a few dollars a month to run (see FAQ for detailed cost breakdown).
{
"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"
}
How do I set this up?
Head over to the github repo and take a look at the README for full setup, build, and flashing instructions.
Project Fi
Cool stuff, I'm definitely going to try it now! Your repo says that Project Fi will most likely not work, but it runs on the T-Mobile towers. Is there an additional feature that Fi needs? I don't use the e-sim, just a normal nano.
snapbackula said:
Cool stuff, I'm definitely going to try it now! Your repo says that Project Fi will most likely not work, but it runs on the T-Mobile towers. Is there an additional feature that Fi needs? I don't use the e-sim, just a normal nano.
Click to expand...
Click to collapse
It potentially can work w/ Project Fi if you target just a single supported carrier by manually setting APN settings. I haven't ever tried it as I don't have Project Fi, but here's a post from CopperheadOS subreddit where a user was able to get it working with T-Mobile.
I'm running my first build now! Can't wait to see how this turns out. I just had to build with the custom hosts file. No need for Ad Blockers now!!
Update. The first build finished without a single issue and flashed just fine! Thanks for bringing this to the Pixel line!
How might one create userdebug builds using this stack?
Anyone messing with this?
Related
Now with data spoofing.
Spoofed permissions:
READ_PHONE_STATE - You can now make your device return spoofed data from the methods protected with READ_PHONE_STATE permission. There is a demo app
{
"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"
}
you can use to see the effect of spoofing and revoking READ_PHONE_STATE permission. Run the app revoke or spoof run the app again.
Since majority of time spend on READ_PHONE_STATE spoofing was about laying the needed infrastructure for spoofing in general, expect new spoofed permissions shortly.
ROM info:
This is a preview build bases on CM7 nightly builds. Some things may not work some features may be missing.
Some applications may not work properly with revoked permissions.
You can revoke permission of SYSTEM applications!!! DON'T DO IT UNLESS YOU KNOW WHAT YOU ARE DOING.. However reboot resets the permissions of the system applications so you probably can recover.
If an application is running changing some permissions like say INTERNET will not be fully applied until the application is restarted.
If you come from CM7 nightly or CM7 RCx you probably don't need to wipe. I something is not working do a wipe.
Google apps are not included. You need to download them separately and flash them right after the ROM.
It will probably require ClockworkMod 3.x to flash properly.
You uses it at your own risk and I cannot be held responsible for the consequences.
Some technical stuff:
If an application checks for its permissions it will appear that all required permissions are granted. This is done to keep some ad networks code happy. As far as I've tested this is safe since the permission check is done at the remote end of the call when protected method is invoked. Please report your findings.
Screen shot:
This is the extended Manage application screen.
Download:
direct link: update-pffmod-0.9.1-HERO-DEV-20110418-signed.zip
storage provided by: http://onlinestoragesolution.com
old builds:
direct link: update-pffmod-0.9.0-HERO-DEV-20110329-signed.zip storage provided by: http://onlinestoragesolution.com
I've mirrored your rom on my server: here
tried this and it's smooth enough to be used daily
gonna give it more time
new build with data spoofing see the first post.
Is it possible to integrate this feature into existing CM 6.2 roms?
Or, maybe, look at the source of this patch so it can be included to popular ROMs?
Proposed feature is indeed a great one, but CM7 is not stable enough currently..
k0rner said:
Is it possible to integrate this feature into existing CM 6.2 roms?
Or, maybe, look at the source of this patch so it can be included to popular ROMs?
Proposed feature is indeed a great one, but CM7 is not stable enough currently..
Click to expand...
Click to collapse
revoke permissions patch is available here http://review.cyanogenmod.com/4055 and here http://review.cyanogenmod.com/4056
xda member pulser_g2 has backported it to 6.5 may he can help you.
I have not submitted the spoofing code to CM. I'll wait for the revoke part to be merged first.
Hi,
Some time ago I have read an article about the /e/ foundation and its goal to offer to everybody the chance to have a free mobile OS. I think that it's a really good idea but unfortunately the os is not yet available on the Xiaomi Mi5.
So I give you a link to get more information and to make a request for our device!
Sorry for my poor english
Flash lineageOS with microG its same stuff
I know this response is late by a few years, but Please post device requests only in the /e/OS Forums.
Hi @Kabula2000,
the Mi 5 - "gemini" is now officially supported by /e/OS,
actually A11/R based
piero-e said:
Hi @Kabula2000,
the Mi 5 - "gemini" is now officially supported by /e/OS,
actually A11/R based
Click to expand...
Click to collapse
Thanks for sharing that info @piero-e
Jawor245 said:
Flash lineageOS with microG its same stuff
Click to expand...
Click to collapse
No: https://www.ed.ac.uk/informatics/ne...patras-haoyu-liu-privacy-data-sharing-android
PURJUJU said:
No: https://www.ed.ac.uk/informatics/ne...patras-haoyu-liu-privacy-data-sharing-android
Click to expand...
Click to collapse
The version of Lineage tested in that study had gApps installed, so it is unsurprising it was leaking data to Google. LineageOS without gApps was not tested, but there is nor reason to think that it, or LIneageOS for MicroG would leak any more information than /e/OS. in fact, the original paper on which that article was based (which can be found at https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf) states (my emphasis)
> On all of the other handsets the Google Play Services and Google
> Play store system apps send a considerable volume of data to Google,
> the content of which is unclear, not publicly documented and Google
> confirm there is no opt out from this data collection. LineageOS
> collects no data beyond this data collected by Google and so is
> perhaps the next most private choice after /e/OS.
petefoth said:
The version of Lineage tested in that study had gApps installed, so it is unsurprising it was leaking data to Google. LineageOS without gApps was not tested, but there is nor reason to think that it, or LIneageOS for MicroG would leak any more information than /e/OS. in fact, the original paper on which that article was based (which can be found at https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf) states (my emphasis)
> On all of the other handsets the Google Play Services and Google
> Play store system apps send a considerable volume of data to Google,
> the content of which is unclear, not publicly documented and Google
> confirm there is no opt out from this data collection. LineageOS
> collects no data beyond this data collected by Google and so is
> perhaps the next most private choice after /e/OS.
Click to expand...
Click to collapse
And I can also read "In summary, we find that /e/OS collects essentially no data and in that sense is by far the most private of the Android OS variants studied"
{
"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"
}
PURJUJU said:
And I can also read "In summary, we find that /e/OS collects essentially no data and in that sense is by far the most private of the Android OS variants studied"
Click to expand...
Click to collapse
Yes, and without gApps installed, vanilla LineageOS and Lineage OS for MicroG - will collect the same amount of data as /e/OS.
So, in terms of data sent to Google, the earlier comment
Flash lineageOS with microG its same stuff
Click to expand...
Click to collapse
is essentially correct
reading the old white paper published by the /e/ team some years ago, they says they remove code still in lineage that makes calls to gogol.
the LeOS G.S.I. maintainer say the same, so e/OS is in fact
( LineageOS sources -- google ) + microG + nextcloud
{
"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"
}
Hi friends
Here's a pseudo stock kernel
"Why pseudo stock?"
R = simple at the moment a stock defconfig is used with minimal changes while the rest are in the kernel source
"Why is the kernel called Prisma?"
R = that is quite simple because initially this kernel is a fork of the prish kernel, and also in the form of a tribute to one of my favorite anime, I forgot to mention that the temporary logo is based on said anime
Compatibility:
OneUI 3.x and GSI using the android 11 vendor as a base
Downloads: https://drive.google.com/file/d/1sfrlQ9-Lt88dNUFpZ_27_fTTdJqYNIiO/view?usp=sharing
Changelog:
-Basically most of the changes in prish except for the changes at the defconfig level, for example the governors are not enabled and / or configured
-Technically I did a kind of upstream to tag 116, I say that it is a kind of upstream because in everything I was investigating the change was only applied to the tag, basically the kernel was not modified
Credits:
Basically the same as in Prish plus a few people who helped me a lot, among which are
@Yillié for supporting my spam in telegram
@manudinath for supporting my spam in telegram, and explaining in detail things that I did not know about this device
@neel0210 by commits and fixes in Prish
Testers:
Considering that I am somewhat new to these things and very little known, only one person helped me by testing the kernel, although I do not know if he has an account in this forum
In case of finding serious bugs you can send me a message on Telegram @licht_estarossx
I am also open to suggestions
Source: https://github.com/KatoTempest/PrismaKernel_9611
reserved
Changelog:
R4
-upstreamed to 124 tag
-a setting only for aosp is being used in this version, so it might not work correctly in stock rom
-A small fix to the script (in twrp it looked pretty weird, but it's fixed now)
-This kernel build was compiled with google tools instead of lineage tools, maybe it works better / worse
manudinath said:
Click to expand...
Click to collapse
Something happens?
Very Nice my friend
Nah,
LichtEstarossx said:
Something happens?
Click to expand...
Click to collapse
Nah, no at all.
very good kernel, miss support for magisk modules, it would be nice if they partnered with some module to further improve performance.
This will also work for latest stock firmware right?
Nice
Could I flash this over with Odin using download mode to unbrick a phone (A51 Sprint 4G only)?
I'm wondering what's the benefit of this kernel?
Hi,
Some time ago I have read an article about the /e/ foundation and its goal to offer to everybody the chance to have a free mobile OS. I think that it's a really good idea but unfortunately the os is not yet available on the Xiaomi Mi5.
So I give you a link to get more information and to make a request for our device!
Sorry for my poor english
Flash lineageOS with microG its same stuff
I know this response is late by a few years, but Please post device requests only in the /e/OS Forums.
Hi @Kabula2000,
the Mi 5 - "gemini" is now officially supported by /e/OS,
actually A11/R based
piero-e said:
Hi @Kabula2000,
the Mi 5 - "gemini" is now officially supported by /e/OS,
actually A11/R based
Click to expand...
Click to collapse
Thanks for sharing that info @piero-e
Jawor245 said:
Flash lineageOS with microG its same stuff
Click to expand...
Click to collapse
No: https://www.ed.ac.uk/informatics/ne...patras-haoyu-liu-privacy-data-sharing-android
PURJUJU said:
No: https://www.ed.ac.uk/informatics/ne...patras-haoyu-liu-privacy-data-sharing-android
Click to expand...
Click to collapse
The version of Lineage tested in that study had gApps installed, so it is unsurprising it was leaking data to Google. LineageOS without gApps was not tested, but there is nor reason to think that it, or LIneageOS for MicroG would leak any more information than /e/OS. in fact, the original paper on which that article was based (which can be found at https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf) states (my emphasis)
> On all of the other handsets the Google Play Services and Google
> Play store system apps send a considerable volume of data to Google,
> the content of which is unclear, not publicly documented and Google
> confirm there is no opt out from this data collection. LineageOS
> collects no data beyond this data collected by Google and so is
> perhaps the next most private choice after /e/OS.
petefoth said:
The version of Lineage tested in that study had gApps installed, so it is unsurprising it was leaking data to Google. LineageOS without gApps was not tested, but there is nor reason to think that it, or LIneageOS for MicroG would leak any more information than /e/OS. in fact, the original paper on which that article was based (which can be found at https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf) states (my emphasis)
> On all of the other handsets the Google Play Services and Google
> Play store system apps send a considerable volume of data to Google,
> the content of which is unclear, not publicly documented and Google
> confirm there is no opt out from this data collection. LineageOS
> collects no data beyond this data collected by Google and so is
> perhaps the next most private choice after /e/OS.
Click to expand...
Click to collapse
And I can also read "In summary, we find that /e/OS collects essentially no data and in that sense is by far the most private of the Android OS variants studied"
{
"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"
}
PURJUJU said:
And I can also read "In summary, we find that /e/OS collects essentially no data and in that sense is by far the most private of the Android OS variants studied"
Click to expand...
Click to collapse
Yes, and without gApps installed, vanilla LineageOS and Lineage OS for MicroG - will collect the same amount of data as /e/OS.
So, in terms of data sent to Google, the earlier comment
Flash lineageOS with microG its same stuff
Click to expand...
Click to collapse
is essentially correct
reading the old white paper published by the /e/ team some years ago, they says they remove code still in lineage that makes calls to gogol.
the LeOS G.S.I. maintainer say the same, so e/OS is in fact
( LineageOS sources -- google ) + microG + nextcloud
{
"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"
}
PixelExtended for Mi11x,pocof3,redmik40 [Alioth]
What is this?
PixelExtended is an Open Source Custom ROM based on PixelExperience, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features missing in Pixel Experience, The ROM will keep it's Pixel ideologies it's primary focus and wont stray into the dark and deep void that is bloat.
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
Features That are Available At the Moment
Click Here To See Features List
As only Essesntial Features will be added so this list will updated whenever there is a new feature
NOTE :- All possible features are toggleable so you always can choose to be stockish
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from SourceForge
Donate
Liked my work? Give me a beer
Stay tuned
Our Telegram Group
Our Telegram Channel
Android OS version: 13
Security patch level: May 2023
Build author/Device Maintainer: chaitanya1256
Device Source code: https://github.com/PixelExtended-Devices
Source code: https://github.com/PixelExtended
PixelExtended Developer: Aryan Gupta
Awesome. My favorite feature of all the features that have been out on Android in the last 4 years is google voice assistant. What that is is the microphone on the Gboard from the pixel devices.
A lot of Android 12 roms have had it for the Poco f3 but now with android 13 only one rom seems to have and that evolution X as long as you don't update android system intelligence on the latest build. I don't know how they do it exactly. I believe it has pixel probs and the google app is version 14.17.30.29.arm64 the fact it ends in .29 is supposed to mean something.
The pixelify model is supposed to do it but it never works. I have never heard of single person getting the voice assistant to work and stay working. If it's built with the rom it works.
Here's a couple of screenshots. If you can't oh well but it's the best feature in forever with android
Pixel extended not working voWifi
Poco F3 Vodafone turkey
need install firmware or not ?
One of the most remarkable features introduced in the past four years on Android devices is the Google Voice Assistant. It is essentially a microphone integrated into the Gboard on Pixel devices. While many Android 12 ROMs have incorporated this feature for the Poco F3, it appears that with Android 13, only one ROM, Evolution X, currently includes it. However, it is essential to avoid updating the Android System Intelligence on the latest build to ensure its functionality. The specifics of how they implement this feature remain unclear, but it seems to be associated with the Pixel problems, and the Google app version is noted as 14.17.30.29.arm64, with the ".29" potentially holding significance.
There is also the Pixelify model that supposedly enables the feature, but it has proven unreliable. To date, there have been no reports of individuals successfully getting the voice assistant to work consistently unless it is prebuilt into the ROM.
Although I understand that screenshots might not be available, I can assure you that this feature is widely regarded as one of the best additions to the Android platform in recent memory.