In due for our major rollout event, ARM. Project will be coming to your mako. We are an non-profit organisation alike cyanogenmod, but only focusing on creating a global aftermarket kernel for the Android OS, specifically to remove the major setbacks of linux.
What's so awesome about the kernel apart from stock manufactured vanilla kernels?
- this includes custom codes which are open-sourced, which aims to tweak the linux kernel to the peak for Android. This gives you a feeling like having Android and, at the same time, feel like you have the smoothness like ChromeOS.
What's in the codes you add?
- they are just codes ported over from other lightweight open-source OS, but, will also include our own various inspirations.
Currently, we are in closed development for mako. We are in need of 2 Maintainers for source building and basic bugfixes and 2 testers for alpha testing. Please PM me to discuss on.
We hope to help shape your phone's future!
nicholaschw said:
In due for our major rollout event, ARM. Project will be coming to your mako. We are an non-profit organisation alike cyanogenmod, but only focusing on creating a global aftermarket kernel for the Android OS, specifically to remove the major setbacks of linux.
What's so awesome about the kernel apart from stock manufactured vanilla kernels?
- this includes custom codes which are open-sourced, which aims to tweak the linux kernel to the peak for Android. This gives you a feeling like having Android and, at the same time, feel like you have the smoothness like ChromeOS.
What's in the codes you add?
- they are just codes ported over from other lightweight open-source OS, but, will also include our own various inspirations.
Currently, we are in closed development for mako. We are in need of 2 Maintainers for source building and basic bugfixes and 2 testers for alpha testing. Please PM me to discuss on.
We hope to help shape your phone's future!
Click to expand...
Click to collapse
Can't wait to see how this turns out
Let's just say the release is near!
First few versions will not include features as it will be more of a build clean fix.
Features will come in time by time.
DO NOT report bugs in the development thread. Report it here with the following info:
- Logcat
- dmesg
- A brief description of what happened.
Yes, we are happy to share our rationale. Recently, we received requests from users and community members, some of which signed a Change.org petition to support Project Treble on the OnePlus 5 and OnePlus 5T. Project Treble is a really exciting technology, but it is not the right fit for us now. I assure you we’re still updating our devices and will continue to deliver high-quality, stable software updates. That being said, we always welcome feedback, and I want to further shed some light on why we are not implementing Project Treble on these devices.
Project Treble requires a storage partition, by which the Android framework and vendor image are separated. However, because partitions were not required of Android N and previous versions of Android, all of our current devices do not feature a partition. According to our tests, if we were to modify the partition layout via OTA there is a risk that devices will brick during the partitioning. We feel this poses too great a risk for our community of users, which is why we have decided not to implement Project Treble on current OnePlus devices.
While Project Treble can increase the rate of Android OS updates, it mainly accelerates the Android framework updates. We were one of the first manufacturers to release an update to Android O. Our software team is committed to delivering high-quality and stable major OS upgrades, and we will continue to look for ways to improve the quality and rate at which we deliver software updates in the future. That being said, we look forward to the future of Project Treble, and how it will evolve to better support devices ahead.
Source : https://forums.oneplus.net/threads/join-our-oneplus-5t-ama-now.686679/page-41#post-17271933
? Share your opinions! ?
It could be a option to provide the tools to make the needed partition once the device is old enough. Say for the OP3. With a big warning that usage is on your own risk. Just like some vendors do when unlocking the bootloader.
I think that would make Al lot of us happy.
GeminiRx said:
It could be a option to provide the tools to make the needed partition once the device is old enough. Say for the OP3. With a big warning that usage is on your own risk. Just like some vendors do when unlocking the bootloader.
I think that would make Al lot of us happy.
Click to expand...
Click to collapse
Too much risk of bricking
Today it has been announced in the XDA that redmi Note 4 got its project treble compatibility and it is a full project treble compatibility.
So when is Moto G5 s going to receive any kind of project treble compatibility but I think that it is relative the easier than the Xiaomi devices because it has all the resources available and I don't think there is any kind of heavy modification from the Motorola side as Xiaomi
But motorola does not offer enough sources to enable trebel i think..
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
jdesignz said:
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Google can explain, but don't expect anything for this device. It's good for the future, but this device is in the past.
jdesignz said:
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
There's an additional abstraction layer / API between the OS and the hardware drivers,
that make it easier to update the Android OS across different vendors with the same chipset (SoC) and hardware features (and long-term probably also across newer Android and Kernel versions, not sure though)
In essence you should be able to run an AOSP build from e.g. Huawei on Sony phones, LG, etc. as long as the components are the same,
meaning: e.g. phone calling, WiFi, etc. all should be working out of the box after installing that, camera and specific features (e.g. dedicated sound DAC) might be a different story though and require adjustments (not sure how that is realized in detail with Treble)
The thing with Project Treble is that it has to be considered right from the start, meaning there need to be (2 ?) additional partitions for updates available:
Partition A (current),
Partition B (new)
So that means for existing device it would involve re-partitioning and/or adding additional partitions to make a device Project Treble "ready",
which is practically impossible since this cannot be achieved with OTA updates.
I've read that older Huawei (or other vendor, Xiaomi ?) has this experimentally added (community ?) but this would require TWRP and/or custom manual intervention through recovery
and most people aren't able to do this - so it's unrealistic that existing device without Project Trouble could be "upgraded", retrofitted through that means
that's at least the superficial level that I got to understand from the discussion from other Sony devs
Hope that helps
Anything that can be developed for this phone have to be figured out very fast because Moto is going to release the G6 family very soon and as you know that once a new family gets released the older family gets less attention and gradually dies over the time and sadly I can see that there are no dedicated developers for this phone so the community has to take the responsibility to do anything possible for this phone as soon as possible.
In particular, I want to port Omnirom 4.4 to a device which has sources for that particular device available from it's manufacturer's website. Note: the documentation available from the github repo is very sparse and underwritten, particularly in the area of porting and building that port.
4.4 dates back to when I was still active (FYI I have not been active in the development community for 3+ years, kind if just popped in to check things out)
In general, a branch THAT old will not have any support and you likely won't find anyone bothering to code review any submissions. I'm not sure what the current state of the instructions for building for supported devices is.
No project has EVER had significant documentation on porting, because every device is different and the barriers you run into are different every time... It's something that is incredibly time consuming and you learn by doing. It requires general analysis and diagnostics/troubleshooting/problem solving skills. If there were a way to write a step-by-step porting guide - you would see far more devices supported at far higher levels of quality than what you actually see.
What device is this? I'm really surprised that you've found complete AOSP sources from the manufacturer. That's basically unheard of for anything other than Google devices and Sony's AOSP project. If you've merely found a kernel source code drop - congratulations, you've got around 1% of what you need.
Hello
A bit of a beginner question.
I am looking for an option to avoid personal data leaks to corporations (paranoid version ). It makes me uncomfortable that every single word I say or text I write is being sent to the servers, being analysed by the online algorithms, etc. I believe that a phone is a personal device, and this is not acceptable.
Which is why I am looking for a phone that would allow to clean up the bloatware and telemetry modules, by either removing them from the stock firmware, setting up restrictive firewall rules, or by installing something like LineageOS or similar.
My question is whether it is reasonable to get the new Pixel 7 (in my area it costs around $600) or would you recommend looking into other models, some chinese models, for a similar price?
I am considering Pixel, as it is known to be one of the best phones in its price range (but as I understand mostly because of the software part, which I would like to meddle with).
Thanks for your opinions!
Yes, the pixel is a great phone. Paranoid Android (privacy ROM) supports it. The pixel is very easy to work with.
thetraveller1 said:
Hello
A bit of a beginner question.
I am looking for an option to avoid personal data leaks to corporations (paranoid version ). It makes me uncomfortable that every single word I say or text I write is being sent to the servers, being analysed by the online algorithms, etc. I believe that a phone is a personal device, and this is not acceptable.
Which is why I am looking for a phone that would allow to clean up the bloatware and telemetry modules, by either removing them from the stock firmware, setting up restrictive firewall rules, or by installing something like LineageOS or similar.
My question is whether it is reasonable to get the new Pixel 7 (in my area it costs around $600) or would you recommend looking into other models, some chinese models, for a similar price?
I am considering Pixel, as it is known to be one of the best phones in its price range (but as I understand mostly because of the software part, which I would like to meddle with).
Thanks for your opinions!
Click to expand...
Click to collapse
The Pixel is, at it's core, developed by Google (which is primarily an advertising company, which is why they have so many great "free" apps, which you pay for with your data), as is Android itself. When you buy a new Android phone, it will come preloaded with multiple proprietary Google apps, which you can not easily uninstall. If you really want a privacy oriented phone, the Pixel with a custom ROM might work. Personally, I use Lineage OS, also for the extra privacy, as it is open-source. Lineage OS does not have any Google apps installed by default, although you can install them if you wish. If you look at Lineage OS's website and click on "GET LINEAGEOS" you can see devices that are supported. Since creating a custom ROM takes time, most of the supported devices are over three years old (yes, the Pixel 7 is not officialy supported). However, certain newer devices are supported, as is my Samsung Galaxy A52 4G (2021), which I run Lineage OS on. You could get the Pixel 7 and run this unofficial build of Lineage OS on it, but if your only getting it because the camera software is good, don't, because your going to remove that software and replace it. Another thing to keep in mind is sometimes the camera support isn't really great with custom ROMs, so do you research to make sure the phone you get has good camera support with whatever ROM you choose. Lineage OS did just develop a much better camera app for it's 20th release, though. Hope this helps, and if you have any questions let me know!
Hi, =)
if privacy is a concern for you, using a Google Pixel device may not be the best option as Google is known to collect user data for targeted advertising and other purposes. You may want to consider other options that prioritize privacy such as phones running on the Android-based LineageOS, or the privacy-focused /e/OS, or a device from a vendor known to prioritize privacy, such as Fairphone or Purism. You may also want to consider alternative operating systems such as iOS or Ubuntu Touch. Ultimately, the best option for you will depend on your specific needs and preferences, so consider your budget and requirements before making a decision.
If you want a device that protects your privacy out of the box with no modification, the Pixel series is not for you. In fact I'm not aware of any OEM Android device that is privacy oriented - Google services by nature depend largely on telemetry and user data for targeted advertising.
That being said, if you want a platform that can easily support a privacy oriented OS, the Pixel is honestly one of the best choices, due to the ease of which you can unlock the bootloader and flash a new OS such as LineageOS, CalyxOS, or others. This means you'll need to familiarize yourself with the concepts of ADB, flashing, bootloaders, etc.
ChristianMorris said:
Hi, =)
if privacy is a concern for you, using a Google Pixel device may not be the best option as Google is known to collect user data for targeted advertising and other purposes. You may want to consider other options that prioritize privacy such as phones running on the Android-based LineageOS, or the privacy-focused /e/OS, or a device from a vendor known to prioritize privacy, such as Fairphone or Purism. You may also want to consider alternative operating systems such as iOS or Ubuntu Touch. Ultimately, the best option for you will depend on your specific needs and preferences, so consider your budget and requirements before making a decision.
Click to expand...
Click to collapse
I happen to have the Librem 5 phone, developed by Purism. Frankly, although it is extremely security and privacy oriented, it currently has many downfalls: high price (starts at $1,999), not many apps (Linux smartphones are pretty new), and the battery lasts less than 24 hours on a full charge (due to not having a good suspend mode, I assume)
V0latyle said:
If you want a device that protects your privacy out of the box with no modification, the Pixel series is not for you. In fact I'm not aware of any OEM Android device that is privacy oriented - Google services by nature depend largely on telemetry and user data for targeted advertising.
That being said, if you want a platform that can easily support a privacy oriented OS, the Pixel is honestly one of the best choices, due to the ease of which you can unlock the bootloader and flash a new OS such as LineageOS, CalyxOS, or others. This means you'll need to familiarize yourself with the concepts of ADB, flashing, bootloaders, etc.
Click to expand...
Click to collapse
Lmao remember “freedom phone” what a joke.
I wonder if even a rooted android phone will not give away all kinds of info. Some roms I presume will mitigate that somewhat, but I feel you are tracked everywhere you go in this world. How about a decent burner or 3? Use it for a week or so then destroy it. And then buy a pixel 7 for the features when you don't care who's looking. And don't forget your paid (forget free) VPN.
@thetraveller1 flash Graphene, relock the bootloader, and you'll basically have state of the art privacy and security on your Pixel 7.
GrapheneOS: the private and secure mobile OS
GrapheneOS is a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Thanks everybody for the replies!
As I understand, Pixel remains the most widely supported device by various Custom ROMs, and getting a Chinese smartphone or Samsung would mean I would be limiting the choice of the available/pre-built ROMs as well as future support with security patches?
ethical_haquer said:
You could get the Pixel 7 and run this unofficial build of Lineage OS on it, but if your only getting it because the camera software is good, don't, because your going to remove that software and replace it
Click to expand...
Click to collapse
I understand that unofficial means it wasn't built by the LineageOS team, rather by a 3rd party. And it probably means that some functionality may be missing/not working and it's not promised to be getting regular updates as new versions of Android come out (including applying official google security updates) unless I learn to make firmware builds myself?
thetraveller1 said:
Thanks everybody for the replies!
As I understand, Pixel remains the most widely supported device by various Custom ROMs, and getting a Chinese smartphone or Samsung would mean I would be limiting the choice of the available/pre-built ROMs as well as future support with security patches?
I understand that unofficial means it wasn't built by the LineageOS team, rather by a 3rd party. And it probably means that some functionality may be missing/not working and it's not promised to be getting regular updates as new versions of Android come out (including applying official google security updates) unless I learn to make firmware builds myself?
Click to expand...
Click to collapse
One of the reasons people use custom ROMs is because they often support devices longer then the stock ROM. For example, a device that was only supported by the manufacture till Android 11 could be running a custom ROM on Android 13. Lineage OS official builds get weekly updates; unofficial builds typically still get updates, but not as often. In either case, it is up to the individual that developed the build to provide support, and the more popular a build is, the more likely it is that it will be supported for many years. To answer your questions: no, getting a non-google phone will not necessarily limit custom ROM options, or updates; and getting an unofficial build doesn't mean it wont get updates, but installing updates on unofficial builds requires flashing the new builds manually, which can be a hassle.
thetraveller1 said:
Thanks everybody for the replies!
As I understand, Pixel remains the most widely supported device by various Custom ROMs, and getting a Chinese smartphone or Samsung would mean I would be limiting the choice of the available/pre-built ROMs as well as future support with security patches?
I understand that unofficial means it wasn't built by the LineageOS team, rather by a 3rd party. And it probably means that some functionality may be missing/not working and it's not promised to be getting regular updates as new versions of Android come out (including applying official google security updates) unless I learn to make firmware builds myself?
Click to expand...
Click to collapse
Take a look at Shizuku and the apps that use it like FreezeYou!. MySudo and Insular are another couple to check. You may find a solution without having to switch ROMs.