LAZY TWEAKS
Another Optimzer. Transparent, No BS, carefully picked from Redhat, Github, Suse, Linux documentations and Android researches, Adjusted and tested to Android.
FEATURES
`ALL IN ONE KERNEL OPTIMIZATIONS` - FROM TOP TO BOTTOM.
WHAT'S DIFFERENT THIS TIME?
LAZY TWEAKS IS AN AIO OPTIMIZER, Carefuly researched to bring significant changes to every device out there, simply like a universal kernel.
WHAT DOES IT MODIFIES?
Everything which lazy tweaks modifies are logged at /android/lazy.log.
to keep it short, it changes fundamental runtime properties according to your needs.
from ram management to your game rendering, lazy tweaks will try to improve it.
SETUP
just open lazy tweaks app and select desire mode, qs mode changer tile is also available.
Version Lawliet Changelogs:
Lazy Lawliet is now available!
Whats new?
- fixed all problems from previous versions
- dropped branches and used one unified script (switched branch changed to ram optimizer)
- better hrtick detection on installation
- rebased on MVK (Maximum velocity kernel)
- cpu task scheduler improved
- performance improved (https://t.me/lazytweak/8367?single)
- battery, cpu and ram adjustments
recommended kernel: perf+ for better tunables support for lazy.
Big thanks for all the people who supports, test lazy and people who guide to make lazy stable. thank you very much.
Note: Updated with compability fix for devices that uses /sys/block/sd* node.
thanks to sir goutham for testing it.
APK is for controlling modes
GITHUB
https://github.com/iamlazy123/lazytweaks
CREDITS:
@tytydraco for his knowledge and script
source code: https://github.com/tytydraco/KTweak
XDA
if i forgot to mention someone pls tell me. thank you
AKIRA (for his advices)
telegram for support and inquiries
https://t.me/lazytweak
Release Channel
Lazy Tweaks Releases
https://t.me/lazytweaks
downloads:
see attachment
The Telegram link earns you an instant No Thanks from me, i like people who post stuff on XDA to talk about and support it here, and not try and make people install a crappy 3rd party app to drag users away from here...
Maybe thats just me though
73sydney said:
The Telegram link earns you an instant No Thanks from me, i like people who post stuff on XDA to talk about and support it here, and not try and make people install a crappy 3rd party app to drag users away from here...
Maybe thats just me though
Click to expand...
Click to collapse
thanks for the feedback! ill also try to help/support people from here to the best i can.
Lazy 4, Lazy 3.2, Lazy fixed ???
Hi op, can you clarified what has to be downloaded please ?
solid.snake said:
Lazy 4, Lazy 3.2, Lazy fixed ???
Hi op, can you clarified what has to be downloaded please ?
Click to expand...
Click to collapse
i recommend latest version sir lazy v4.
73sydney said:
The Telegram link earns you an instant No Thanks from me, i like people who post stuff on XDA to talk about and support it here, and not try and make people install a crappy 3rd party app to drag users away from here...
Maybe thats just me though
Click to expand...
Click to collapse
A lot of Android app and development groups are on Telegram as well as XDA because it's easy to use. If you're concerned about third party issues, trackers, etc, there's a fully FOSS build of Telegram available on F-Droid.
https://f-droid.org/en/packages/org.telegram.messenger/
Mokura3rd said:
A lot of Android app and development groups are on Telegram as well as XDA because it's easy to use. If you're concerned about third party issues, trackers, etc, there's a fully FOSS build of Telegram available on F-Droid.
https://f-droid.org/en/packages/org.telegram.messenger/
Click to expand...
Click to collapse
Nope
1) Why should i have to install a 3rd party app (totally irregardless of its internals, tracking etc) to engage with a dev who has started on (and used) XDA. Far too many "devs" are using XDA to gain and audience and then totally disrespect it by trying to move their userbase onto othe rplatforms
2) Its again the rules of XDA to do 1). Devs must provide support here or face having their threads closed
So, like i always say to devs posting Telegram links, are you on XDA or not? Make a choice.
73sydney said:
Nope
1) Why should i have to install a 3rd party app (totally irregardless of its internals, tracking etc) to engage with a dev who has started on (and used) XDA. Far too many "devs" are using XDA to gain and audience and then totally disrespect it by trying to move their userbase onto othe rplatforms
2) Its again the rules of XDA to do 1). Devs must provide support here or face having their threads closed
So, like i always say to devs posting Telegram links, are you on XDA or not? Make a choice.
Click to expand...
Click to collapse
No offense, but :
Being on Telegram doesn't prevent a dev from Being here... I already subscribed to many Telegram Channel starting from here, and I can tell you that resolving a pb is much faster than here.
Also, topic are better structured on TG, I mean you only interested by the changelog ? Just hit #changelog, and the bot will provide you link. Same for bugs, suggestions, download link....
I feel very sad for you to choose not to try his module, just because of a Telegram link provided aside xda...
I do hope to see many more Telegram link here despite of your though.
Just a reminder to everyone: please try to keep things civil here. This thread is still about the Magisk module and not about the usefulness of Telegram
Respect the dev's decision and as long as everyone adheres to the XDA rules, this thread may offer a Telegram group chat as the dev chooses to do so
Oh thank you Now I can play pokemon go with gps joystick on my 2gb ram phone (got better ram management). Joystic is not disappearing more often as previously. But there is problem with other modules. First time when I flashed it my viper and Dolby module refuse to open (force close). Phone reboot takes so much times, Sometimes I had to force start device.
Then I thought there must be some issue so I uninstalled and flashed in magisk again but My other modules disappeared and not getting location in some apps.
Tested on
redmi 3s, arvanasoft modified miui rom android 6.0
stable update is up!
Updated github links and script. hopefully this release will fix all bugs from previous builds.
if u have issues. feel free to message me on telegram or XDA.
lAlKenDi said:
Updated github links and script. hopefully this release will fix all bugs from previous builds.
if u have issues. feel free to message me on telegram or XDA.
Click to expand...
Click to collapse
Now I have problem with only youtube vanced app. It's force closing. Otherwise very great module. I love it.
Vinayakn73 said:
Now I have problem with only youtube vanced app. It's force closing. Otherwise very great module. I love it.
Click to expand...
Click to collapse
thats great! i hope you get better experience!
Version Igris Changelogs:
DEV:
- retuned sched_migration for better heat and battery management
- reduced swappiness to fair value for a better multitasking and battery usage
- updated ram management per mode
- retuned scheduler for a better and smoother experienced (if ur a geek, iops was greatly improved)
- updated cpu ramps (bb should give more battery, etc)
- added wakelock blockers (if ur kernel supports it)
- added debug disablers
- added adreno gpu tunables (if ur kernel supports it)
- added options to install empty thermals
- reduces bufferfloat for faster network speed and performance
STABLE:
same as dev but remove the kernel tunables from ktweak
tldr: this version should give you what each mode does and bb should be thicc without perf cost.
will be updating github next week stay tuned!
Update
Update is Up!
if u have any issue feel free to drop it HERE. Enjoy!
After the mobile phone restarts for a period of time, the vibration motor has been working, how to stop the motor?
It keeps bootlooping after flashing it.
edit:I reflash it and it works fine.
Related
Is it possible to download the complete source code that Sony used when they compiled the ROM for Xperia V. I know where to find the kernel source and of course Android is very easy to get but what about everything else. I'm especially interested in knowing if they made any changes to Android or if they only cluttered the phone with add-ons.
Since Sony did abuse the phone and broke it to badly to make a reinstall possible I'm mainly just interested in getting the sources for my own education and understanding of the system. Perhaps even to try some simple reverse engineering to fix some really absurd settings like NFC not working in lock screen and such before I sell the phone and never ever talk about or to Sony again.
please use search and/or google
http://developer.sonymobile.com/downloads/xperia-open-source-archives/
good luck in your development of this
gregbradley said:
please use search and/or google
...
good luck in your development of this
Click to expand...
Click to collapse
Thank you for at least answering me however, I have goggled a lot about this and the link you posted to the best of my knowledge contains only the kernel source plus a few other system programs that are used on the host side when compiling. I'm honestly quite surprised that the answer to this is not well known. I have also since yesterday tried to find out what branch of android is used but that too seem to be obscured in darkness.
AlgoJerViA said:
Thank you for at least answering me however, I have goggled a lot about this and the link you posted to the best of my knowledge contains only the kernel source plus a few other system programs that are used on the host side when compiling. I'm honestly quite surprised that the answer to this is not well known. I have also since yesterday tried to find out what branch of android is used but that too seem to be obscured in darkness.
Click to expand...
Click to collapse
from what I am aware of those are the full sources used to compile the ROM, not just the kernel.
what do you mean by "What branch of android is used"
gregbradley said:
from what I am aware of those are the full sources used to compile the ROM, not just the kernel.
what do you mean by "What branch of android is used"
Click to expand...
Click to collapse
Well, look at the size. It is about 250MB, about the size of the kernel. The Android source is in the gigabyte range, I also have downloaded and compiled the kernel and the file you download contains a kernel folder and a external folder with the helper programs I mentioned.
Well I can't links since I'm to new here but if you do a search for "Codenames, Tags, and Build Numbers" on Google you will see that there are several branches for each version of Android. But now when I looked closer at that list it just so happens that 4.1.2 only has one branch so you can ignore that question, i was tired yesterday and was looking for 4.1.1 that has more like six branches. Still seems hard to find out what would be the right one in that case.
OK, I see what you want.
I am not sure where to find that info, but there will be some on here that will know.
try PMing championshipswimmer or DooMLoRD
They are busy people, but they may be able to point you in the right direction.
For those of you already running thecommunity build of OxygenOS 3.5, you will receive an OTA to the community build (3.5.1) very soon. For those of you who are not running the first community build, you can flash 3.5.1viathe links below. Afterwards, you'll continue to get future OTAs delivered directly to your device.
This new version includes:
Changelog
Accent color added
Battery icon customization added
LED customization added (Display)
sRGBmode added (Display > Screen mode)
Night mode added
Dark mode theme optimized
General bug fixes
Please help make OxygenOS even better by filling out the opinion survey and/or the bug report form.
https://goo.gl/forms/qFsrbyvxRbmjQnIi1 - Feedback on UI/UX
https://goo.gl/forms/l5etNY41zhmYI6tk1 - Bug Reporting Sheet
Visit the download page here: http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.5.1_community_build/
Direct Download Link :
http://oxygenos.oneplus.net.s3.amaz...6_OTA_002_all_1608301010_6ee96e2225c34a71.zip
Google Drive Link :
https://drive.google.com/file/d/0BwuhxALNsjtpbVVsVnV3YjJQdXM/view?usp=sharing
Dark mode theme optimized... full black?
Mr.Ronik said:
Dark mode theme optimized... full black?
Click to expand...
Click to collapse
Yep, can confirm, now dark mode has the black background back
Can someone confirm me whether the dpi issue Is fixed or not?
Dont want to sound rude, but is there a point for one plus updating the 3.5.x builds?Rather than updating MM i think they should work on Android N .
shalom06 said:
Dont want to sound rude, but is there a point for one plus updating the 3.5.x builds?Rather than updating MM i think they should work on Android N .
Click to expand...
Click to collapse
This is a community build, not final or the like. They can't have two teams working on a ROM?
Sent from my ONEPLUS A3000 using Tapatalk
Had a quick look at the survey and spotted this... please tell me they are not thinking about adding more crap into their OS?
Have you installed Clean Master? *
If so, which feature do you use the most?
Clean Junk
App Lock, protect your privacy
Battery saver, hibernate apps
Antivirus
Phone Boost
Notification Management
Uninstall, backup and move your apps
I don't use it
I really do not like where this is going.
darkjedi said:
This is a community build, not final or the like. They can't have two teams working on a ROM?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Honestly? I don't think so. Waste of money.
If they're working on a MM build, i suppose it will take veeeery long time before we can see something based on Android 7.
Fentadroid said:
Honestly? I don't think so. Waste of money.
If they're working on a MM build, i suppose it will take veeeery long time before we can see something based on Android 7.
Click to expand...
Click to collapse
Or just flash CM14 when the nightlies start.
Fentadroid said:
Honestly? I don't think so. Waste of money.
If they're working on a MM build, i suppose it will take veeeery long time before we can see something based on Android 7.
Click to expand...
Click to collapse
Soon cm will provide android N for us in the mid or start of Oct. So no worries
Still can't find a way to get embedded battery percentage hope this is something they can add back in
3.5.1 analysis
is any one here flashed 3.51 yet? how about performance overall, battery? ui improvements? else?
Please report
daleski75 said:
Or just flash CM14 when the nightlies start.
Click to expand...
Click to collapse
I know but... Only if you don't mind pictures quality....
given the direction OOS is heading (w/ the community builds) I'd prefer to stay on CM, just hoping OP drops the OOS camera blobs like Carl Pei said they would so we can have equal quality photography on custom ROMs soon
sad since OOS 3.2.4 is pretty amazing as is.
Fentadroid said:
Honestly? I don't think so. Waste of money.
If they're working on a MM build, i suppose it will take veeeery long time before we can see something based on Android 7.
Click to expand...
Click to collapse
They already have two teams working on ROMs. One for OOS and the other for H2OS. This is probably done by the H2OS team. If you don't like it, don't use it and stick with 3.2.4 since this is just a community build.
Sent from my ONEPLUS A3000 using Tapatalk
darkjedi said:
They already have two teams working on ROMs. One for OOS and the other for H2OS. This is probably done by the H2OS team. If you don't like it, don't use it and stick with 3.2.4 since this is just a community build.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
At some point though they will deprecate 3.2.x and 3.5.x will take over with all of the (possible) value added software we love like cleaner master!.
Very thankful we have a fantastic dev community here who will strip out whatever crap OP put in.
daleski75 said:
At some point though they will deprecate 3.2.x and 3.5.x will take over with all of the (possible) value added software we love like cleaner master!.
Very thankful we have a fantastic dev community here who will strip out whatever crap OP put in.
Click to expand...
Click to collapse
There's no indication that they'll do that. But...you always have the option to install another ROM instead. OR as you said, strip **** out you don't want. But take into account that they're a Chinese company, with a vast majority of their user base probably is in China, so they want to cater that user base. I don't mind the visual aspects of 3.5, but you're right that more bloat is bad.
PSA if anyone hasn't already tried, installing a Substratum theme causes the phone to get stuck at 1+ logo upon reboot
Sent from my OnePlus One using XDA Labs
darkjedi said:
There's no indication that they'll do that. But...you always have the option to install another ROM instead. OR as you said, strip **** out you don't want. But take into account that they're a Chinese company, with a vast majority of their user base probably is in China, so they want to cater that user base. I don't mind the visual aspects of 3.5, but you're right that more bloat is bad.
Click to expand...
Click to collapse
Running my own builds of CM13 here and don't think I will GI back to stock.
stryker09 said:
PSA if anyone hasn't already tried, installing a Substratum theme causes the phone to get stuck at 1+ logo upon reboot
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
Hi!, you can open File Manager in TWRP and delete Substratum's APK and reboot phone
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.
Hi community!
There is a WIP (Work in Progress) ROM being mainly developed by @Rortiz2 and @diegocr: https://github.com/LOSMantis
Current ROM Status:
- Not Stable
Not Working:
- Sound
- OMX
- Maybe more...
Developers out there that would like to join development are welcome!...
Notice: This is a WIP ROM. It needs to be compile from the source (build steps could be adapted from the Nexus Player https://wiki.lineageos.org/devices/fugu/build) if someone wants to try it out. Ready to flash builds would maybe be available when the ROM is more stable. Please do not ask for ETA, it is being developed in the spare time of the developers!
michael.santos said:
Hi community!
Anyone already seen this project on github: https://github.com/LOSMantis ?
It is a shame that this project are not being discussed here on XDA so more devs could help on this project...
Hope this post will "awake" some devs (maybe @Pretoriano80?) for this project...
This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
'I believe @diegocr and @Rotiz2 were working on it some and couldn't get the sound to work. Not sure if actively though...
This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
FireOS is very well maintained, even the oldest fireTVs/sticks getting still proper updates...
Sus_i said:
FireOS is very well maintained, even the oldest fireTVs/sticks getting still proper updates...
Click to expand...
Click to collapse
Yes, but full of bloatware, with some blocking mechanisms or black listed apps, no Google Play Store...
We are not allowed to change the home app easily, to use the standard Android settings without Amazon home app, not install already purchased apps on the Google Play Store and so on...
With root you can disable remove the "bloatware", although personally i dont think there is much i dont use. The fireOS TV is fairly smooth and easy to navigate. The android TV version is worse (IMO, I have a NVidea). You can disable the NIMH app, although i have yet to find any app it is blocking. The play store for androidTV is horrible. LauncherX is fairly easy to install. As with tank and sloan, i would expect issues with roms.
...
Rortiz2 said:
Can you and other people (that did this aswell) stop creating threads like this?
We're working on mantis yes but this takes its time...
For now all is working except OMX and Audio so it's not worth to release anything.
We will create the ROM thread when it's enough usable.
Just wait...
Regards.
Click to expand...
Click to collapse
Hi Rortiz2,
Why are you so mad about this thread? We did not ask for a working ROM or any release dates and we appreciate all your time and dedication to the project...
As I wrote in the subject, this is a WIP (Work in Progress) ROM... Have seen so many threads like this in other forums here on XDA where the ROM only boots but nothing works...
I have created this thread to allow other devs to join the project (if nobody talks about it, than nobody knows that a project already exists and can not help).
But if you would like to do this project alone, just tell me an I will delete this thread...
Best regards,
Michael
...
I got really excited when I saw this thread. I cannot wait for stock Android for the Firestick 4K. I will 100% donate to the dev's who get this working!!
Rortiz2 said:
It's ok, leave the thread here. If somebody wants to help there's no problem.
Click to expand...
Click to collapse
Just throwing out an idea here but would getting some kind of test build out help? Perhaps getting some catlogs from the community could help find a solution? Again just throwing an idea out.
AngryManMLS said:
Just throwing out an idea here but would getting some kind of test build out help? Perhaps getting some catlogs from the community could help find a solution? Again just throwing an idea out.
Click to expand...
Click to collapse
+1 for a test build, I've got a bricked 4k that boots both the hacked bootloader and TWRP, but whatever image I install has no display...
So I would like to try anything else even if stuff is broken on it (just to see if I can get a display).
thx.
michael.santos said:
Hi community!
Anyone already seen this project on github: https://github.com/LOSMantis ?
It is a shame that this project are not being discussed here on XDA so more devs could help on this project...
Hope this post will "awake" some devs (maybe @Pretoriano80?) for this project...
This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
This being said, i'm sure that it will be released as soon as the guys behind it will consider it stable enough.
P. S. BTW, thread title is misleading and probably aldo violates XDA rules.
Pretoriano80 said:
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Click to expand...
Click to collapse
I totally understand and respect that. I did bring up having some kind of developer/user test build done just in case that could help further along getting said bugs fixed by getting catlogs that might help narrow down what is causing the issues. But if the devs feel that doing that would only slow things down (or even not help at all) then I respect that decision.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
Click to expand...
Click to collapse
That's the nature of things when it comes to Lineage OS ROMs (and AOSP in general). Sometimes devs are able to get the ROMs to have nearly all the functionality of the device working... and sometimes not. But I generally prefer Lineage myself due to the overall experience being faster since LOS tends to not have all the bloat that stock ROMs sometimes have - especially Amazon devices which feel so bloated down with garbage I will never use.
Pretoriano80 said:
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
This being said, i'm sure that it will be released as soon as the guys behind it will consider it stable enough.
P. S. BTW, thread title is misleading and probably aldo violates XDA rules.
Click to expand...
Click to collapse
Hi Pretoriano80,
As I already replied to one of the devs, I never asked for a release date or ROM for flashing. The title also is marked as WIP (Work in Progress), that means that the ROM is in development and not ready for use...
I have seen that you already made a great job with the custom kernel. Thanks! Would you also like to help this project as it seems it also can use your kernel? Kernel dev with ROM devs would be the best team!
Thanks again to all devs that work hard for releasing new stuff for the Amazon devices...
How's the progress so far?
Looks like nothing much: https://github.com/LOSMantis/android_vendor_amazon_mantis
Too bad !!
dead project ?
I made a test build (with many warnings). Also I used the kernel from @Pretoriano80.
You can download it here: https://www.androidfilehost.com/?w=files&flid=324510
Please note that I couldn't test this out yet, so be careful of what you do. (Will try it out for myself soon)
Ungeskriptet said:
I made a test build (with many warnings). Also I used the kernel from @Pretoriano80.
You can download it here: https://www.androidfilehost.com/?w=files&flid=324510
Please note that I couldn't test this out yet, so be careful of what you do. (Will try it out for myself soon)
Click to expand...
Click to collapse
it's not worth to test since it's a dead project, it would be more usefull to begin a new project developing LineageOS 16 rom , At least we will be able to use the new Android/Google TV UI.
robin994 said:
it's not worth to test since it's a dead project, it would be more usefull to begin a new project developing LineageOS 16 rom , At least we will be able to use the new Android/Google TV UI.
Click to expand...
Click to collapse
LineageOS 16 won't ever be able to happen for the Mantis version because it doesn't support treble, the most it could do is LOS 14.1 since it's a legacy device.
Hello,
I've been missing for quite a long time from XDA, but I'm about to get a new phone soon (maybe another OnePlus?) and I came here to check for new custom ROMs updates.
But it seems I cannot find any custom ROM for the OnePlus 10 Pro (yet?), why is that?
Thanks for the info.
No msm unbrick tool, no sources and so on.
Oneplus sucks every phone a little bit more! 10 pro is definitely my last OP phone
You can try GSI roms, but they're buggy (e.g. fingerprint sensor is not working)
Also you cannot unbrick your phone unless you send it to 1+ which makes development hard
Source tree is different default compilable sources.i hope someone could port it.
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
galaxys said:
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
Click to expand...
Click to collapse
What mods are you using mate?
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
See a my reply to other post on oneplus 10 pro
ectoplasma22 said:
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
Click to expand...
Click to collapse
İ can't found it .could u share for me .it has same tree our devices i could work it.
metrixx02 said:
İ can't found it .could u share for me .it has same tree our devices i could work it.
Click to expand...
Click to collapse
There's a telegram group, check the pinned posts
Xiaomi 12 | OFFICIAL
Xiaomi 12 Official Group • English only chat • Read Rules ( /rules ) • Channel : @Xiaomi12GlobalUpdates • Photography group : @Xiaomi12GlobalPhotography • Off-Topic Group : @PocoOffTopic • Customization Group : @PocophoneCustomization
t.me
I've found this: https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450
And this: https://github.com/OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8450
But, sadly, I've also read this post: https://forum.xda-developers.com/t/how-not-to-guide.4458091/post-87108519
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
dladz said:
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
Click to expand...
Click to collapse
Yeah, I remember the old times here on XDA, there was so many threads proposing many different flavors.
I used to flash and try new ROMs almost everyday...
Now I have to get a new phone, I came here to check and I've realized it all changed.
It's even hard to find ROMs for Google Pixels and OnePlus phones, I don't know what happened but it's kinda frustrating...
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Honestly mate, I've had enough phones to know that it should have happened by now.
I'm very patient, no problem in waiting, but every single OnePlus device has had several ROMs by this point bar none
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Why do you need google roms? are they better?
Otherwise it finds 2-3 threads about to change to global or EU version.
But that is not you want?
lorenx said:
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Click to expand...
Click to collapse
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
EtherealRemnant said:
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
Click to expand...
Click to collapse
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
toolhas4degrees said:
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
Click to expand...
Click to collapse
There's also the fact that A/B partitions lead to plenty of bricks and the devs get blamed for it plus the issues that come with AVB 2.0, manufacturers not releasing full kernel sources... It's all a circus.