well, I have done a little experiment with my Nokia, seeing that there is again between the sections of Nokia 6 and Nokia 5, I found that the Nokia 6 has already a semi stable rom of Android Oreo based on lineages os 15
and doing a bit of logic, I assumed that the rom could work on the n5, since the romes of the n6 and n5 are compatible with each other, and it really works, accepting that it has some details, one of them is that the buttons do not work. navigation, the fingerprint reader does not go either, and the audio does not go either, the latter works halfway, since adding the file mixer_paths_nd1.xml in the system / vendor / etc path manages to raise the audio service
and as usual, the camera is not as good as stock or gcam and also brings some minor bug when recording at high speed
if you want to try it here is the link, preferably try it having installed android 8.1 stock
link to post
https://forum.xda-developers.com/nokia-6/development/lineage-15-1-t3896279 :good::good::good:
Give the list of which is working and not working
What happened to this project?
Related
I've tried out several of the ROMs available for the Droid 4 and I was already taking notes on each of them, so thought I'd share a review on each here. I already posted my thoughts on LineageOS 14.1 in a previous thread so we'll skip straight to crDroid.
crDroid 3.8.5 is the latest addition to the D4 scene. It runs Android 7.1.2 and is based on LineageOS 14.1, apparently branched from the spyder builds. Its advantages include support for JJB's overclock kernels, in fact WiFi doesn't work without it; support for use of the altpart Safestrap to repurpose the webtop partition and give you the largest 1.3GB /system partition in your stock slot; built-in signature spoofing for MicroG/Xposed support; the most recent (Jan/2018) Android security patch level; integrated custom fonts; Ad Away browser integration; great battery life; and its own cool settings section with lots of other custom features. Like all Android V5+ versions this supports hand-wave notifications on the lock screen.
Its disadvantages are that it's fairly thick due to being on 7.1.2, and unless you're running MicroG or a very tiny Gapps package (Slim Zero or OpenG pico), it can be slow, though not nearly as bad as LineageOS 14.1 on which it's based. Videos are jerky and audio stutters. It's really intended to be used with MicroG. And despite being around only six months, it is no longer officially supported by the crDroid team, so no further updates at this time. A major factor for users of Google Voice is that it displays the routing phone number of your call rather than your actual destination phone number during the call, which can be confusing at worst and annoying at best. The call log still shows the correct destination phone number though. I'm not sure where the bug for this lives but it is specific to the ROM. Most annoyingly, the swipe-to-unlock is quirky - you have to swipe fully from bottom to top, and fairly quickly. It usually takes a couple attempts before the phone unlocks, making it difficult if not impossible to do with one hand.
Verdict: Best of the AOSP V7 ROMs for D4. But V7 isn't necessarily the best choice for D4 because of its high RAM usage. Unless there's a reason you absolutely need to run V7, i.e. for an app, you're better off with an older release that uses less RAM.
Thanks for you review. It is awesome to see that there still is active members hanging around. In my mind Lollipop was a bit laggy on Droid 4 compared to KitKat roms but Marshmallow and specially Nougat roms have improved the situation. I can consider Nougat as a daily driver for Droid 4 in 2018. I just hope that we could still see Android Oreo Go edition on our device.
So after seeing announcements about Project Treble and GSI floating about the internet I thought I'd look for a version to use on my Honor 9 Lite and came across this thread:
https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/android-pie-kirin-guys-t3830420
Users have had Android Pie running on a honor 7X so I thought there can't be that much difference between the 2 devices, so why not give it a try? If it goes wrong I can always use my stock backup.
So I flashed as per the instructions in that post and it works, really well. So much so that I'm gonna keep it as a daily driver.
Be careful which version of Gapps you use, the BitGapps mentioned in the post has been discontinued by the Dev, I initially tried OpenGapps but it was for 8.0 so failed to install.
If you search around you can still find the last version of BitGapps that was released, and is version 9.0 compatible.
What's Good
Installs pretty quick
Fast, much faster than EMUI - Could be a Placebo effect, but general use is very snappy and downloads/app installs seem very quick
Wi-Fi working fine
Bluetooth working fine, confirmed on Ticwatch and Car radio
Mobile data works fine
Finger print reader works fine
Sound and phone calls work fine
What's not so Good
This Rom is based off AOSP, don't expect any of the Huawei/EMUI functions or features.
On first boot the ROM is bare bones, hardly any apps installed, looks like an old version of Android rather than a shiny new one.
You have to enable guestures before the swipe navbar appears
You'll have to use a 3rd party launcher to get the full Android P look. The Quickstep launcher in this version of AOSP has sqaure icons and certain options like wallpaper/widgets etc just FC. - I chose Lawnchair for this.
Hotspot doesn't work at all, it just disables wi-fi then FC
You may have to mess around with the display settings to make things align correctly, for some reason everything seemed to be shifted to the left edge. I chose small display size with large font size to smooth it out
Camera obviously, same issues as we had on the 8.0 roms, banding/poor tracking/poor quality (Biggest downside) I've not rooted, so not tried any of the camera ports. Open Camera app has the same issues.
Sound over bluetooth was distorted (not confirmed, could be my car radio)
Some graphical glitches. Stutters & frame drops when using task switcher, switching to chrome from recents has a lag/distorted effect and menus appear out of focus and take a second or two to correct
Any Questions I'll try to answer as best as I can.
I've tried many different gsi images on my H9L. Most did make my phone 'feel' faster, I guess mainly due to the overhead EMUI takes and eliminating it does remove some burden from the phone. However, that's where the advantages stopped. Many of the issues you mention on Pie are on Oreo also. I had too many issues to overcome and make it 'daily driver' usable that it just wasn't worth it, so went back to stock and removed as much huawei/honor stuff as i could via root, then removed root. This seems to give me best of both worlds, i.e. close to vanilla android but everything, hardware wise, just works as intended. Since I have BL unlocked and TWRP working i can also keep updating, via HURupdater, with official updates for as long as huawei/honor keep posting updates; e.g. currently on B135 with Aug security patches, that is just as good as any GSI image now (Aug18).
Hi,
I'm acually working on LineageOS 15.1 and I'm running into a problem:
In frameworks/base/core/java/android/content/BroadcastReceiver.java (in the method PendingResult beginning with line 86) the resultCode is set to 4!
This is
Code:
RESULT_SMS_UNSUPPORTED
added in API level 19
public static final int RESULT_SMS_UNSUPPORTED
Set by BroadcastReceiver to indicate that the message, while possibly valid, is of a format or encoding that is not supported.
Constant Value: 4 (0x00000004)
My problem is, I can't figure out, where and why this is set!
So, it's not possible to send a message via SMS...
Any help is welcome!
These two main problems are left in LineageOS 15.1:
Camera not working
Sending SMS not working
There are a few minor problems, but they are not important.
If there is no further help, this finally will be the end of developing this ROM! :crying:
thanks for the work
im just want stable rom.
my stock ROM reboot too much everday after rooting.
so now im using 14.1 no reboot here, you already lose lots good options in the LA14 camera like slow motion(high fps rate) and EIS \ OIS
this phone slowly dying
even my old sony(LWW) was develop from android 2.3 upto 7.1 (through CM to lineage) about 7 years (include custom roms)
Superrman said:
thanks for the work
im just want stable rom.
my stock ROM reboot too much everday after rooting.
so now im using 14.1 no reboot here, you already lose lots good options in the LA14 camera like slow motion(high fps rate) and EIS \ OIS
this phone slowly dying
even my old sony(LWW) was develop from android 2.3 upto 7.1 (through CM to lineage) about 7 years (include custom roms)
Click to expand...
Click to collapse
I understand what you are saying but I think the users enjoying Bernie's ROM are practical users who do not care about latest (crap) features like live emoji or animojis or whatever teenage functions they implement. Real innovations are not to be found. Currenty i switch between my iPhone 7 and Z5c every other week. I still think my Z5c rocks!
I would love to try L15 so I sincerely hope Bernie will find support for his development.
Berni-0815 said:
Hi,
My problem is, I can't figure out, where and why this is set!
Click to expand...
Click to collapse
I've been skimming through LOS repos. AFAICT, the only place in which that constant is used is here.
Antonio
antonio.galea said:
I've been skimming through LOS repos. AFAICT, the only place in which that constant is used is here.
Click to expand...
Click to collapse
Yes; I know. But I've set a logging command at this point and the code is never reached.
So, it ("4") must be set somewhere else...
I've set so much logging commands in some suspicious sourcecode-files but I can't figure out, where this could happen.
The logging commands are showing this chronological order:
Code:
packages/apps/Messaging/src/com/android/messaging/util/PhoneUtils.java #getCanonicalByCountry()
- MessagingApp: (bt): Number valid at this point! getCanonicalByCountry(): canonicalNumber: +nnnnnnnnnnn
>>> It must happen [B]after[/B] the above sourcecode-file and [B]before[/B] the next ones: <<<
frameworks/base/core/java/android/app/LoadedApk.java (Don't find anything)
frameworks/base/core/java/android/content/BroadcastReceiver.java #getResultCode() #PendingResult() #getPendingResult() and #setPendingResult()
- BroadcastReceiver: (bt): PendingResult(Line 86): resultCode: 4
It's currently on Lineage OS 17.1, I've tried installing the Family Link child app on it but it won't complete setup properly.
I read somewhere that flashing the "stock" opengapps would allow the setup to complete but when I tried flashing it with TWRP, there isn't even enough space in the /system partition so that's a no-go.
What else could I try that would work? I'm assuming it's possible to just flash back to stock but I would prefer to stick with LOS as it can just do a lot more than stock (especially warm-light).
This seems to say that Digital Well-being has taken over the functionality of Family Link Child:
Family Link parental controls now integrated with Digital Wellbeing beta
Since Digital Wellbeing and Family Link controls have pretty similar goals with different but sometimes similar audience, it makes sense that Google will integrate the two or at least connect them …
androidcommunity.com
I'm having the same issue. Trying to setup my Nexus 6 with Lineage 17 for my child. I can't seem to get Family Link working. The latest is the phone says "Device Profiles" are needed, which I guess doesn't come with this ROM or OpenGapps?
I was never able to get it to work on Lineage 17 or 18. But I decided to give Pixel Dust (Android 9) a try and everything works flawlessly with Family Link.
Hello everyone,
I'd like to install the latest version of LineageOS on my Sony Xperia 1 ii and the guide looks fairly straight forward (I've installed Lineage on many devices) but my question pertains to the Pro Sony apps (eg. Cinema Pro, Photo Pro, etc). I've extracted the APKs from my current install, but as I'm reading more, these will not work on LineageOS. Has this something to do with the DRM keys in the Trim Area Partition? I've read several guides for other Xperia phones and this looks like a VERY complex procedure. I have no plans to revert back (last Android security update on my phone is June 2022) so if I don't need my DRM keys, I'm good with that. I've heard there are modified APKs for these Pro apps. Would these work on the 1 ii? Only ones I've come across are from the Xperia 5
Thanks
Hey Cole,
I've been using Lineages 20 from almost 3 months now and just updated the new build today.
My main concern was coverage. I get barely 1 or 2 bars here but have a decent wifi. For some reason, the stock rom on my phone doesn't have wifi calling feature so I was really upset with that.
Lineage OS has fixed that issue for me and after a few days I've started missing the Pro Camera app.
I've found these two versions ported/modded from the 5 Mark 2 community.
1.3 works flawless
1.5 is also good except using the 70mm lens in Pro/Manual mode(App will get crashed and the only way to reopen is clearing data)
Make sure to disable the Camera button to launch Camera. With that enabled, whenever you take a photo from Pro/Manual mode, it keeps re-launching the app(applies for both versions)
Note: Installing these apks will take a little more time than other apps at the same size so do not panic
If you installed 1.3 then you have to uninstall to install the 1.5 as the update will not install
Here is the 1.5 version
Thank you very much for these. Really appreciate it !!
Sada52 said:
Here is the 1.5 version
Click to expand...
Click to collapse
Thank you for this app. On xperia 1 mark 3 lineage os20 works perfectly. Could you tell me where to get or how to port the cinema pro application?