Related
These are pretty standard on just about every ROM out there for pretty much all phones since Jelly Bean, and yet we still dont have the ability to add in more nav buttons or change around the order of them or anything on a single Nexus 6 ROM. We just barely seem to be getting the ability to change the height and I even saw one ROM that could change what happens on long press to one of the buttons. Yet no significant customization for even moving around the order of the 3 stock buttons. Do we have some issue on the N6 that is causing developers to not be able to implement this feature?
It'll come. But jeepers, the device is only a month and change in people's hands.
The feature is coming into the works, there are more important features than customizing the navigation bars.
The developers do the work as a hobby and for free. If you wanted to, you can contribute, otherwise wait.
EniGmA1987 said:
Do we have some issue on the N6 that is causing developers to not be able to implement this feature?
Click to expand...
Click to collapse
Probably a few issues causing this.
First the phone came out a bit over a month ago, and was quite hard to get for a large portion of that time. Some devs didn't get their device until recently.
Second, they perhaps haven't had a lot of time recently to get to working on their custom ROM. This isn't their job, they have families, jobs, school and perhaps other things that are more important than working on their ROM. There have been a lot of holidays the past month or so, which also impedes them.
Third they need to plan. Look at what Lollipop has changed, what new things they can work on + what things they should bring back from their previous work. Perhaps they don't see navigation bar customization as a priority over the stuff they are working on. There is a lot of things that I would like to see that custom ROMs haven't touched for the most part. Reorganize the notification toggles for example. Navring edits. Lockscreen customization. And probably 50 other things that were standard on many 4.X ROMs. I am sure we will see eventually, that were included in many custom ROMs for Kitkat and other older OSes plus some new fun things (Ambient Display customization maybe).
Perhaps they are buying into the rumors that 5.1 is coming very early next year. And don't want to risk putting a lot of effort into 5.0.X when 5.1 could break whatever it is they have done. While this isn't likely a real cause in this instance, in other forms of development this has given some developers pause.
tl;dr: Patience is your friend. Hide the navbar and get a navbar replacement if you can't wait, I think LMT works.
zephiK said:
The feature is coming into the works, there are more important features than customizing the navigation bars.
The developers do the work as a hobby and for free. If you wanted to, you can contribute, otherwise wait.
Click to expand...
Click to collapse
No need to be a ****, I was asking a serious question on if there were some limitations of the N6 framework that other devices dont have to deal with. Its not a complaint exactly, but a request for information on the issue. I have been through a LOT of devices over the last few years and all other devices I have seen get the feature even when they are brand new within a week or two of being unlocked. So it just seems like maybe there was an issue with significant changes to the OS framework causing developers to not be able to copy most of the code or something.If it is simply that no developer thinks it is a priority then that's fine, I was just wondering the reason.
Softkeyz (app in the play store) is working on adding lollipop support. It's a great nab bar app that I used on my Nexus 7.
EniGmA1987 said:
No need to be a ****, I was asking a serious question on if there were some limitations of the N6 framework that other devices dont have to deal with. Its not a complaint exactly, but a request for information on the issue. I have been through a LOT of devices over the last few years and all other devices I have seen get the feature even when they are brand new within a week or two of being unlocked. So it just seems like maybe there was an issue with significant changes to the OS framework causing developers to not be able to copy most of the code or something.If it is simply that no developer thinks it is a priority then that's fine, I was just wondering the reason.
Click to expand...
Click to collapse
I wasn't being one. Users tend to criticize or be impatient for certain features that isn't present. @cupfulloflol said the same thing I did but elaborated more into detail so if the lack of details is what makes me what you call me then I apologize. I was getting straight to the point without the bonuses.
All I'm saying is that these developers are working for free and doing what they do as a hobby without being motivated by a salary. Features are being incorporated on a day-to-day basis, you just have to wait. Its one of the trade offs of having the newest and latest, you'll have to wait.
My point still stands, if you want to contribute and implement the customization for navigation bar then you can do so. There are tutorial guides on how to remap the buttons on the navigation bar in the themes & apps section, you can do them yourselves or port code from Kit Kat onto Lollipop on navigation bar customizations.
The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new commits added to the for the most part unstable staging master branch code from Google AOSP that has not yet been tagged for a future Lollipop update., hence the reason for 5.0.2_Plus name. The only change added to the code that was not committed first by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it. At the moment because of limited testing as I do not own a Nexus 4 and all changes have been tested on the Nexus 5 felt untill a few return performance reports best to call this a beta version. With that said the same changes have made some improvments and fixed a few issues experienced by Nexus 5 users using the oficial 5.0.1 update or compiled from the AOSP android-5.0.2_r1 branch. So if start receiving comments that all has been well on the Mako build or see say 100 download without a complaint reported will remove the beta tag. I suspect this will be the case as the commits are not device related.
I honestly started the project for the Nexus 5 with the idea that maybe as a community a few developers could help work on the project so everyone had an updated version of the latest release version that included the latest fixes and had not intended on compiling for the Nexus 4. After my second release another XDA member had asked if it would be possible to make a Nexus 4 port for a friend. At that point as there had been little interest in the project by other Nexus 5 Developers I would post the Mako ota package I compiled for the user who had asked for one. I also have my own Starship Rom and am part of a new developer team so again was meant as a community project and not intended to be released as my Rom or really even released at all with the intention of being a resource for other developers to either use as the base of whatever new AOSP Rom they may intend on developing or selectively picking pieces or fixes. So going with the same idea after compiling the asked for Mako version thought why just limit the idea to just the Nexus 5 as all Nexus devices share the same code from AOSP with exception of needing to add a different set of propriety vendor blobs and choosing a different lunch command for building. So the same goes as intended for the Nexus 5. If any Nexus 4 developers would be interested in joining in on the project Just let me know and I will grant full access to the Github account and create a new branch so we can test and insure the master branch is always %100 stable if it is going to be used by other Nexus developers..
A few examples of the commits that have been added.
https://github.com/Android-AOSP/And...mmit/20063610490eabc91db5ef13a550ecbdcdc6dc1a
https://github.com/Android-AOSP/And...mmit/16c0cfd5920c6d09824d13b7ee94436de87b37e3
https://github.com/Android-AOSP/And...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
https://github.com/Android-AOSP/And...mmit/18cca2773e4f3890e2ff9ca416400d48f62b98f5
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mmit/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_mako-ota-ota-5.0.2_plus_r2.0_test.zip.zip - 184.51 MB
aosp_mako-ota-ota-5.0.2_plus_r1.0_test.zip - 184.52 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is %100 Stock but going with past experience if mrg666 has a Kernel availible for your device it should be the Kernel you are using.
Mirage Kernel for Stock Nexus 4
http://forum.xda-developers.com/nex...el-mirage-nexus-4-stock-rom-06-04-14-t2485368
Change Log 5.0.2_plus_r2
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
This is %100 AOSP with no extra theming at all including bootanimation so no screen shots, as a Nexus User are probably aware what AOSP looks like at this point.
Don't mean to be rude, but you're still living in 2014, apparently. LOL . Classic mistake, I guess. Check the title dude.
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
This is exactly what i have been looking for, we need more Roms like this. Thanks OP downloading now:good:
chairshot215 said:
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
Click to expand...
Click to collapse
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Good rom so far, only thing was that data roaming was enabled by default.
dragos281993 said:
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Click to expand...
Click to collapse
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
nibla101 said:
Good rom so far, only thing was that data roaming was enabled by default.
Click to expand...
Click to collapse
Will look into that I'm happy to know it is working out. I basically just took my N5 source added the Mako vendor blobs and compiled using a different lunch command. Will go back and see if data roaming being enabled by default is a result of my updates or is set in general aosp 5.0.2 after work. Even though intention is keeping as pure as can be should still be looked at.
Think it would be nice if we could get a few devs together from across the current Nexus devices lineup and do our best to keep an aosp Rom available adding in the latest updates and bug fixes into the most current release for all Nexus devices. Not just for users but for other devs to use in their own aosp based work. Beleive if we could get something like that going would be pretty sweet and not all that time consuming. Still lots of updates added by Google devs every day. Some a bit more complicated then what I have done that a small group could easily bang out and test. Everything comes from the Master aosp branch that can get messy with constant new commits around the clock but think if selective in adding into latest release could be a beneficial project. So using my phrase of the week with that said I am going to build and post a version for all the Nexus devices in an attempt at gaining interest in the project. Again with that said I am torn for tonight as can try producing thr first N5 version that is sprint compatible or build for my Nexus 9. I am very much looking forwored to trying it out with jusst Simple ol aosp but at the same time feal bad for the Nexus 5 Sprint users who are all stuck on stock because other Roms are missing the aditional files added in for the radio to work. Decitions, decitions, decitions.
chairshot215 said:
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
Click to expand...
Click to collapse
LMAO. That was funny
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
groovepeppy said:
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
Click to expand...
Click to collapse
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
chairshot215 said:
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
Click to expand...
Click to collapse
will test it later
thank you for responding
groovepeppy said:
will test it later
thank you for responding
Click to expand...
Click to collapse
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Hi,
can any of you recommend the Rom to be fully functional and without any major bugs? Which of the basic normal functions must work and most do not work:
- enabling / disabling locations from the drop-down upper bar
- the ability to remove the search bar from the bottom of the background of the main screen and the date and time from its upper part (unnecessarily blocks the space, from this are the widgets)
- adaptation to fast charging, with a minimum current of 2000 mAh
- small date and watch with seconds on the upper beam
- list of connections as in older versions of android with a specific date and time, not in the type "3 days ago"
- dark background in the call list and sms messages
- software flashlight
- 8 shortcuts in one line (upper pull-down bar)
- main screen number of columns 8, number of lines 9
- working encryption
- average memory consumption max 1.5 GB
- security update status> March 2020
- advanced restart
- gallery with menu offering after the first click, e.g. image rotation, etc.
- installation file without Gapps and max 600 MB!
- rom created min 1-2 months ago, constantly updated
None of the following systems:
AospExtended-v7.0-santoni-20200309-1447-Dhruv-BUILDS (my favorite, No. 1)
crDroidAndroid-10.0-20200319-santoni-v6.4-LuisROM
Havoc-OS-v3.3-20200306-santoni-Official
Xtended-santoni-OFFICIAL-20200316-XQ-Rel-v7.0
RevengeOS-3.2-Q-OFFICIAL-santoni-20200319-0633
aicp_santoni_p-14.0-WEEKLY-20200328 (my favorite, No. 2)
RR-P-v7.0.2-20200213-santoni-Unofficial-LuisROM_9
AospExtended-v6.7-santoni-20200318-1847-Final_9 (my favorite, No. 3)
SuperiorOS-Phoenix-santoni-OFFICIAL-20200331-0941 (my favorite, No. 4)
can offer the above combined functionalities without the need to install additional software.
Worst of all, the developers do not respond to comments and submissions.
Some of them are almost perfect, but the grid density, hotspot, or the right number of columns settings are missing.
I was thinking about LineogeOs .. but this is a very limited rom in terms of personalization and settings. Practically like MIUI.
Table from a comparison of Roms:
https://docs.google.com/spreadsheets/d/1tCVfL3i3j6H9mWrmzM_q-erkzYRjm2PRzNjwmNyNTPE/edit?usp=sharing
How about you build your own ROM ? No offence. I've been thinking the same I too need the exact features you ask for. But I do not have any coding knowledge to build a rom. Tho I'm willing to learn but I don't find anything that would teach me lol. (searching YouTube too build a rom would be futile since some videos are either old that it's not the current format and or if it is the current format they talk as if we already have knowledge of what they're talking about). But otherwise lineage with nothing in it would make good empty cup to fill tea or coffee of your wish to fill in. But I know it's p.i.a to have additional softwares like magisk or apps, thus comes ROMs of other better developers but with one noticeable flaw that the ROMs are not customised to your liking. So the only option left for you is to build your own ROM. I guess lineage allows you to customise and share your ROM however you like it.
Lineage hasn't been updated in 7 days(usually within 5 days you'd have gotten an update) .. I think the official version is gonna jump from 16.0 to 17.1. if it did I hope the features you asked for would be there. Obviously except the gapps one.
Thanks for the message .. what are you not angry
I also thought to build my ROM, I have energy for it, but no time at the moment. I did not check how to build instructions ... if you do not need to be able to program it sure and it would do the trick.
In addition, Remi 4x is a bit old equipment, but still without a successor in these dimensions and with such a battery. So he'll probably live some more. I do not know to what extent the knowledge and rom prepared for a given phone can be used to transfer everything to a possible new phone model.
In my opinion, LineageOs is unnecessarily updated every day ... it's a waste of time - because no one updates the phone so often! Unless there are some patches from your phone by checking for updates (partial additions, like in Windows) that I don't know about?
Downloading 600 MB of data each time is also an unnecessary load on connections.
In fact LoS 17.1 may be showing up at any moment, but I am convinced that not much will change. Do not understand and understand that the community and developers completely ignore bug reports! I also do not understand the logs, since the applications are based on freshly installed software and ordinary uncomplicated, perfectly visible faults.
A lot of new ROMs are being created, but if I don't see earlier versions and the creator is little known then I will certainly not install such software. Unfortunately, I value privacy.
All in all, I prefer a ROM with minimal additions, embellishments, etc. but with lots of settings. The Rom remix was such, but from June 2019 it is not updated.
In addition, I see a lot of duplicate settings not needed from several places on the system. Elementary deficiencies in the ergonomics of use. I have the impression that Android was built for the first time and in addition they were students ... and yet it already has several editions. How much time has passed and how much discussion was about dual-sim, and yet it was a standard that was obvious.
Developers are developers, but certainly Google itself is extremely mixed in all this. Probably, if not for the huge number of devices and even more subcontractors, something could be created that would be fully open to the benefit of all users, such as Firefox, Openstreetmaps or Linux Manjaro.
Probably I will return into Los:
https://forum.xda-developers.com/li...c-settings-t4083435/post82298887#post82298887
Many people complain about this and seems like few know about the issue. I should say that I'm not a dev, I just figured it out and tired of writing it after each complaint, which is why I write it as a new thread.
So, in short, there are ways in which gcam speaks with the camera. With RN8(t), we need the app use raw10 rather than raw_sensor for us to be able to have photos. This means that you need a version which either shoots with raw10 by default, or lets you switch from raw_sensor to raw10.
Sadly(?) there are not many that allows this, and almost all are version 6.x ones except Nikita's. The modders I found that allow switch or use raw10 are Nikita, overwhelmer, fu24, wyroczen, and trCam of tigr. There can be others, these are just those that I found. and I did not try each and every one of them. So if you are suffering from this problem, go for these modders' versions.
I may add that I like to use Parrot043's mod, as its output is practically what I want, yet unfortunately it is not usable without raw_sensor. Like his/hers, Arnova8G2's, BSG's, and many others' mods don't (didnt?) work. Yet as they are making new builds every now and then, maybe they will include a switch later on.
I should note that neither of those that I tried can do (good) astrophoto - or it was the case for me. Also none of these managed to produce good shadows (shadows in both Photoshop sense, shadows as shadows, and the transitive area between blacks and whites). On the other hand, it can be a problem with my device as I have seen people shooting pretty fine photos with these - including, interestingly, astrophotos. I just try and wrote my experience. Do NOT rely solely on my experience. Go and try for yourselves. This is just a starting point for those of you that have the problem, not an ultimate guide.
About auxiliary cameras, I cannot say much as I had them working at some point (with a fix from PA devs, I forgot the name of the dev and the patch sadly, and with fu24's version), yet now again they are broken. Funny part is that Paranoid Android claims to have them all working from the start, and other than me, I saw no one complaining that wide and macro don't work. Probably something is broken with my mobile, which is why I cannot say much on the issue.
Of the custom ROMs, I have found only Paranoid Android allowing shooting with raw_sensor. It might be the case with some other ROMs, so you better go check it out for yourselves as well. I can confirm that Pixel Experience and LineageOS did not allow shooting with raw_sensor, but it can change as well. Everything, as we know, comes down to the devs. This is just my experience, and I do not test each and every ROM every other day.
I hope that this will be useful for you, and there won't be complaints about pink/purple lines. This is because of GCam, not ROM builders as such. You can, surely, "force" the ROM builders to include raw_sensor shooting, yet it's up/down to them to do it or not.
So, I hope that this will help you to have a better idea about the problem, and you can solve it easily/easier.
Hi everyone.
I just got my Note 8 and it is a beast!
my phone prior to this was actually an Xperia Z1 (yep, the one from 2013), which has LineageOS 7.1 (Nougat) loaded onto it. I loved that rom, so much I actually put the same LineageOS version on my ASUS tablet too. So I'm pretty used to the trebuchet launcher and Nougat system in general.
the previous owner of my Note8 had pretty much installed all the updates up till late last year, so It's got the 9 Pie update installed. Android 9, combined with the One UI launcher, and topped with annoying "Bixby???" button I keep accidentally pressing, is all a little too crazy for me, coming from LOs Nougat.
with my scouring of forums, I've seen a few people suggest that staying on Oreo is better for battery life / performance / usability compared to the Pie update.
Compared to my Z1, this thing is a speed demon, it certainly isn't slow... but I do notice that the battery seems to drain a bit even when the phone is left in standby, and considering it's a fresh factory reset OS with almost no user apps installed, I'm a little concerned to see it's using 3gb of memory on just bloat and background services.
So pretty much I've been looking into the custom rom situation for the Note8.
My main priority is debloating and stability. I've seen the popular Hades and Deluxe roms, but they look almost more like they are adding features and customization, rather than stripping the useless bloat. Also they seem to be pushing even newer android versions now.
I've seen that TeamEXYKings put out a few light roms, even ones supporting nougat. which I'm interested in trying, anyone have any thoughts on these? It looks like support has dropped for them.
Points I understand so far.... (correct me if I'm wrong)
*Currently, I can't flash because my KG state is in Prenormal, still waiting the 7 days with simcard and phone staying on.
*Exynos has an unlocked bootloader, snapdragon doesn't. It seems to be a common opinion that Booatloader can't be downgraded, so therefore I won't be able to roll back an oreo or nougat rom? yet I've seen some people claim they were able to after they unlocked the bootloader (very confused)?
*Most Roms take away Spen functionality? I do need this, but only for the pressure sensetivity in my art apps, I don't care too much about the drawing on notes/screenshots/off screen/ring shortcut. Will I still get the basic funcationality of my Spen on a custom rom?
*Seems there are some Galaxy S8 roms that have Note 8 functionality and vice-versa.. should I consider these? are there any drawbacks/bugs to consider?
sorry for the long post I'm open to anyone's thoughts and suggestion, cheers!
TLDR: new phone, not too keen on Android Pie and excessive Samsung bloat. please suggest light and stable rom for note 8.
dc_all said:
Hi everyone.
I just got my Note 8 and it is a beast!
my phone prior to this was actually an Xperia Z1 (yep, the one from 2013), which has LineageOS 7.1 (Nougat) loaded onto it. I loved that rom, so much I actually put the same LineageOS version on my ASUS tablet too. So I'm pretty used to the trebuchet launcher and Nougat system in general.
the previous owner of my Note8 had pretty much installed all the updates up till late last year, so It's got the 9 Pie update installed. Android 9, combined with the One UI launcher, and topped with annoying "Bixby???" button I keep accidentally pressing, is all a little too crazy for me, coming from LOs Nougat.
with my scouring of forums, I've seen a few people suggest that staying on Oreo is better for battery life / performance / usability compared to the Pie update.
Compared to my Z1, this thing is a speed demon, it certainly isn't slow... but I do notice that the battery seems to drain a bit even when the phone is left in standby, and considering it's a fresh factory reset OS with almost no user apps installed, I'm a little concerned to see it's using 3gb of memory on just bloat and background services.
So pretty much I've been looking into the custom rom situation for the Note8.
My main priority is debloating and stability. I've seen the popular Hades and Deluxe roms, but they look almost more like they are adding features and customization, rather than stripping the useless bloat. Also they seem to be pushing even newer android versions now.
I've seen that TeamEXYKings put out a few light roms, even ones supporting nougat. which I'm interested in trying, anyone have any thoughts on these? It looks like support has dropped for them.
Points I understand so far.... (correct me if I'm wrong)
*Currently, I can't flash because my KG state is in Prenormal, still waiting the 7 days with simcard and phone staying on.
*Exynos has an unlocked bootloader, snapdragon doesn't. It seems to be a common opinion that Booatloader can't be downgraded, so therefore I won't be able to roll back an oreo or nougat rom? yet I've seen some people claim they were able to after they unlocked the bootloader (very confused)?
*Most Roms take away Spen functionality? I do need this, but only for the pressure sensetivity in my art apps, I don't care too much about the drawing on notes/screenshots/off screen/ring shortcut. Will I still get the basic funcationality of my Spen on a custom rom?
*Seems there are some Galaxy S8 roms that have Note 8 functionality and vice-versa.. should I consider these? are there any drawbacks/bugs to consider?
sorry for the long post I'm open to anyone's thoughts and suggestion, cheers!
TLDR: new phone, not too keen on Android Pie and excessive Samsung bloat. please suggest light and stable rom for note 8.
Click to expand...
Click to collapse
Rather than trying to address everything I will stick to what is most important for you, debloating and stability. Both Deluxe and Hades rom let you choose most of what bloatware you want during the Aroma installation, although they vary slightly in what is selectable but if you don't want Bixby for example just don't select it in Aroma. For stability you won't go wrong with a stock based rom.
If you love Lineaage OS you can flash Lineage 17 which is stable, you can find the latest build in the link I will post below, however this will remove the Spen functionality so it is literally just a touch pen and I don't know if the pressure censor works for drawing. You will need to flash Gapps with this to get the Google play store.
https://images.stricted.net/lineageos/greatlte/
I want to make you aware, just in case you don't know, that as soon as you flash TWRP this trips Knox so Samsung Pay will never work again, it breaks other things too like Shealth and Secure Folder but most stock based roms have this patched so they work, just not Samsung Pay.
Another option is to buy a package disabler, which is what I use, so I can disable or enable any app with just a click so then you can stay fully stock.
stonedpsycho said:
Rather than trying to address everything I will stick to what is most important for you, debloating and stability. Both Deluxe and Hades rom let you choose most of what bloatware you want during the Aroma installation, although they vary slightly in what is selectable but if you don't want Bixby for example just don't select it in Aroma. For stability you won't go wrong with a stock based rom.
If you love Lineaage OS you can flash Lineage 17 which is stable, you can find the latest build in the link I will post below, however this will remove the Spen functionality so it is literally just a touch pen and I don't know if the pressure censor works for drawing. You will need to flash Gapps with this to get the Google play store.
https://images.stricted.net/lineageos/greatlte/
I want to make you aware, just in case you don't know, that as soon as you flash TWRP this trips Knox so Samsung Pay will never work again, it breaks other things too like Shealth and Secure Folder but most stock based roms have this patched so they work, just not Samsung Pay.
Another option is to buy a package disabler, which is what I use, so I can disable or enable any app with just a click so then you can stay fully stock.
Click to expand...
Click to collapse
Thanks a bunch for your advice, very helpful.
and thanks for bringing up the knox thing. I have heard that, though I forgot to mention it in my post. I think I'll be fine without those samsung features.
I'll keep a close eye on Hades and Deluxe then. There seems to be the most information about them online and even some video reviews.
I'll look into the newer lineageOS too, it sounds like it will meet my needs, but I would hate to lose some functionality on Spen or camera, so Stock based may be the way to go..
Also I hadn't ever heard of a Package disabler.. definitely going to look into that too.
Another great perk for LOS was the privacy guard, being able to disable apps loading at startup or not allowing them to run in background really extended my battery life. I'll have to look into similar options from 3rd party apps.
thanks again for your help.