So I was looking into a new phone I could buy new, had a headphone jack and telephoto lens, and maybe stereo speakers, and came across this phone.
I noticed that the Note 9 used to have lineage os support up until 17.1, and was wondering if there was any specific reason support was dropped? Is it hard to port 18.1 and 19.1 versions of LineageOS to the Note 9?
Some other questions I had about ROM'ing the note 9:
- Does performance degrade significantly when on ROMs?
- How is battery life?
- How's the camera, and is there a gcam apk that can use all the lenses?
- what features would I lose if ROM'd the device, and is their any ways to reinstall them or get mods (like thru magisk) to get them back?
- did the pen even work when it had LineageOS support? Is there apps/mods that can be installed to make it work?
For context, I'm coming from a Pixel 3a, and cross shopping with these:
- an A72 (4g), still 3 yrs of OEM software support
- Moto Edge 2020, LineageOS support, Plastic back and no IP rating to ruin so I don't feel bad about replacing the battery
- S10/+/5G, very good phone, just wouldn't feel to confident in replacing the battery
Any advice on how living with any of these phones ROM'd nowadays would be greatly appreciated.
Hi, @JayAbbhi,
I am currently using a N9 that has not be rooted, but has been heavily debloated via adb. I prefer to use it over a N20U.
I think LineageOS support for the N9 has ended, but you can ask in the LineageOS threads on the forum.
APNMirror has updated LineageOS application files for applications, such as Phone, etc...
I tried the LineageOS phone, contacts and messages apps on N9 and N20U.
GIF images cause the messaging app to crash on both phones.
Couldn't access one section of the phone (Version 23, Android 10) on the N9.
I don't access the internet (surf, chat, etc...), and mainly use FOSS apps with NetGuard.
N9 is a Beast!
edit: APKMirror, not APNMirror site...
Related
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.
anyone ever come across a fix for this?
nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
On my S7 Edge, S8, and S8+, I've been able to selectively disable Battery Optimizations from apps like Nine (Email), Facebook Messenger, and other apps to ensure they don't go into deep sleep mode (Doze) to ensure timely receipt of emails or Facebook Messenger Messages.
On my Note 8, the menu is unchanged from the other devices, but I noticed the functionality is no longer working. The difference being Android OS 7.1.1 vs. 7.0 on the other devices.
In FB Messenger, the tell is when you open the app after a few minutes, if you see the orange bar that says "connecting to network", you know the app disconnected in deep sleep (Doze). With Battery Optimization disabled for this app, this disconnect should no longer occur, but it is.
In Nine, the tell is when your phone randomly pushes a bunch of emails to you, sometimes 20-30 minutes delayed when on the earlier Samsung models, the emails come in right away. This is not an app-related configuration issue, but Doze issue.
Perhaps a glitch? Has anyone else tested on their Note 8 and experienced the same?
I wouldn't even know how or where to report a bug like this to Samsung.
No one ever replied. Has anyone experienced the above? Perhaps resolved now? I ended up going back to my S8+ because of this problem.
Had same problem with random disconnections even with Battery Optimizations and Battery Monitor disabled for Messenger, Im using an old version now (91.0.0.19.70) with the old interface and no problems since... I found latest versions of messenger very buggy at least for me.
About Nine, don't know as I use Outlook and never had a problem with it since I have this phone.
iFlasher said:
Had same problem with random disconnections even with Battery Optimizations and Battery Monitor disabled for Messenger, Im using an old version now (91.0.0.19.70) with the old interface and no problems since... I found latest versions of messenger very buggy at least for me.
About Nine, don't know as I use Outlook and never had a problem with it since I have this phone.
Click to expand...
Click to collapse
On my S8+, I use the latest versions of FBM (beta stream). No issues with regards to connectivity itself (the app is buggy sometimes as its beta though). It was only on the Note 8 where even disabling the battery optimizations for Messenger (and other apps) still forced them to disconnect.
I have the same issue. My phone is Factory unlocked and from Malaysia, used with an American Sim card inside.
So I recently bought the Asian version
SM-N9500
Android 7.1.1
I also experience the issue. Took EVERYTHING off app optimize battery usage. Even took it off monitor list and added to white list. Delay is still there.
I've just downloaded an app off the play store called PNF No-Root which basically pushes every 5min (you can set different interval up to 1min) that syncs everything. So far i've gotten whatsapp msg 2m-3mins late but so far I can't figure out what else to do to fix this.
This is driving me insane when my entire business is built online and I need to respond ASAP.
Was this ever resolved? I'm worried the issues will carry through on the S9
settings>devicemaintteinance>battery>unmonitored apps>ad apps, select which apps you do no want to be monitored an will be always running
winol said:
settings>devicemaintteinance>battery>unmonitored apps>ad apps, select which apps you do no want to be monitored an will be always running
Click to expand...
Click to collapse
I'm aware of these steps. The issue was on the Note 8, these steps were ineffective as opposed to the S7 / S8 series of devices where it worked just fine. I was wondering if this was ever resolved on the Note 8.
WorldIRC said:
I'm aware of these steps. The issue was on the Note 8, these steps were ineffective as opposed to the S7 / S8 series of devices where it worked just fine. I was wondering if this was ever resolved on the Note 8.
Click to expand...
Click to collapse
For resolved you mean that if it works in note 8? Well, it works fine with my 950F exynos 128 GB, in fact, vital systems app are not easily dozed, the likes such as chrome, keyboard, playstore, gallery, sms, gmail, etc
winol said:
For resolved you mean that if it works in note 8? Well, it works fine with my 950F exynos 128 GB, in fact, vital systems app are not easily dozed, the likes such as chrome, keyboard, playstore, gallery, sms, gmail, etc
Click to expand...
Click to collapse
Do you use Facebook Messenger on your phone?
No, I do not, I never do, in fact I have all facebook related things disabled with bk
winol said:
No, I do not, I never do, in fact I have all facebook related things disabled with bk
Click to expand...
Click to collapse
Ok it would be tough to test with you then. With Messenger, if Doze is enabled, the app will keep losing its connection and every time you open it, it would say connecting to network. With Doze disabled for Messenger, this problem goes away, except on the Note 8.
I was able to test a Canadian S9+ on Oreo, the issue does not seem to affect it. I am optimistic that the Oreo update for Note8 will address this.
Yes, it's not just the Note 8, I think and I strongly believe that the problem is related to the crappy nougat version 7.1.1., I had the very same problem (email not syncing, and delaying (lollipop and marshmallow don't have it!) even on pixel, opo 3t, and s8, all of them had Android 7.1.1., the problem was almost fixed on 7.1.2.
Now, had the pixel 2 xl, with Oreo, for a while, switch back to Note8, and the problem came along.
This is the main important reasons to make me update to Oreo on note 8
Ariyax said:
Yes, it's not just the Note 8, I think and I strongly believe that the problem is related to the crappy nougat version 7.1.1., I had the very same problem (email not syncing, and delaying (lollipop and marshmallow don't have it!) even on pixel, opo 3t, and s8, all of them had Android 7.1.1., the problem was almost fixed on 7.1.2.
Now, had the pixel 2 xl, with Oreo, for a while, switch back to Note8, and the problem came along.
This is the main important reasons to make me update to Oreo on note 8
Click to expand...
Click to collapse
I almost figured it had to do with 7.1.1.
Good [present time of day]. forumites!
As per the title, I've installed ripee's LineageOS 17.1 ROM on my Tab S2, and everything seems to be working, bar the camera. I've seen several posts around the interwebs claiming that that is indeed a common occurance with this ROM, but most of them were somewhat dated, so I was wondering if a solution had cropped up in the meantime. Failing that, can anyone recommend a ROM with working camera? I plan to use the tablet mostly for running Linux over Linux Deploy, but a built-in camera comes handy every now and then.
Thank you all in advance.
Without having registered I followed for almost two years here in the forum the fantastic work that @Ivan_Meler is providing for owners of an old Galaxy S7. I got mine from my daughter. She wasn't happy any more with it because it was outdated and battery life too short. I do have a mobile phone (Nokia slider-phone), but didn't want a smartphone that calls home to Google and others all the time and is overloaded with bloat-ware. As I prefer Open Source (using Linux (Mint) as normal PC-OS) to saveguard as best as reasonable my personal data, I thought I would try a custom ROM on the S7. It took me some time reading and following up the various little (!) problems the users of Ivan Meler's LOS 18 & 19 had until I decided that it was time to try it out myself.
I got the - I think - usual problems when flashing the S7 with LOS 19.1 and flamegapps. Black screen, boot-loop, etc. but not too nasty. Finally it turned out great; with LinageOS 19.1 and a number of dedicated apps (bromite, k9-mail, Signal, Musicolet music player, VLC, Memorix, Navigator_MapFactor ) and most importantly NetGuard-V2.300 the Galaxy S7 runs like a charm and battery life is excellent. With NetGuard I deny some of the home-phoning apps (especially Navigator) the access to Facebook and Google statistics, etc. A marvelous tool provided by Marcel Bokhorst.
I have to admit that I would not pay nor do any banking with a smartphone, I prefer cash and my LinuxPC for online banking. And until now I have not inserted the SIM-card into the S7 as I still use my Nokia. With the S7 I am using my home W-Lan and throughout the city (in Bavaria) there are free hotspots from BayernWLAN. Ok, you might call me a too conservative user, but for me it works out perfectly. Until now .... we will see how things develop.
Now I have registered and thank @Ivan_Meler and all who support this fantastic forum!
Kalli
Hello,
I'm very new to android roms
Well, I did a little bit of that back in pre-2010 times and some times with my samsung galaxy nexus, but I assume things have changed a lot since then.
I have many XT1929-17 Z3 non-play and a couple Z4 XT1380 and a few Z2F
I want to try many things,
Download all firmware from each phone, and upload firmware to a phone (I guess that's the flash device and radio firmware , not sure)
Make setup a phone to my taste, make a backup so I can continue messing around without having to go through the entire setup process again !
Next, I have the crappy verizon firmware, I would like the stock android or Z3 motorola stock firmware instead of the verizon one ! WIth all the non-erasable bloat- and spy-ware
Next, I am stuck on Android 9 forever, I would like to try android 10/11/12 especially if the moto mods and gestures are still working. Really, just android 10 would be great, the only thing I really want is darkmode notifications and settings !
After that, if there are roms for those, I would like to try lineageos, grapheneos, pixel experience and the other popular firmwares that are made for many phones.
I would like the fastboot and adb windows 10 offline drivers to remote control all aspects of the phone. (I will be using many of those phones as wifi cameras and I'm trying to reliably stop and start recording 240fps video with wifi remote control)
Oh, and I would like to try just plain linux on those phones, if that's even possible. Even if that's just cpu/ram/wifi. I'd like to use one of them as a mini server
I think that's pretty much all I want to try with these phones, do you have advice on how to do this on Moto Z3 non-play ?
Thanks !
you cannot run linux on android smartphone, except you're talking about "linux" on top of "android kernel" which still provides full hardware HAL access. the overhead is nearly the same as running android, so no point in this. but here you go.
https://docs.ubports.com/en/latest/porting/introduction