Introduction
One of the biggest benefits of ROOT for me was being able to see my WiFi passwords.
When Oreo came out, this got broken. This is my solution to that issue.
So I made some changes to an existing open source WiFi key viewer on GitHub by Nexxado.
After some testing, and quite a bit of feedback (in this thread) the app finally reached a point where it was stable on all devices tested.
Now that it's stable - there will probably be very few changes going forward.
The project is availabe on GitHub in case anyone wants to make their own changes
You can get the latest version here
XDA:DevDB Information
Oreo Wifi Passwords, App for all devices (see above for details)
Contributors
Hotfingers
Source Code: https://github.com/David-Mawer/OreoWifiPasswords
Version Information
Status: Stable
Current Stable Version: 2.1.5
Stable Release Date: 2017-12-27
Created 2017-11-21
Last Updated 2017-12-27
Version History
The version at the top is the newest one.
Also - the apk's are attached to this post at the bottom)
v2.1.5 (27 Dec 2017)
If there's more than one WiFi entry with the same name, then it will store the one with the password.
v2.1.4 (18 Dec 2017)
Make a setting to allow all the passwords to be visible / hidden by default.
v2.1.3 (17 Dec 2017)
Handle password arrays better than before.
Fix pre-Oreo changes broken in 2.1.2
v2.1.2 (16 Dec 2017)
only show the first 3 letters of the password - single tap copies the entire password to the clipboard.
changed loading of files to try remove bugs from some devices.
v2.1.1 (9 Dec 2017 post sun-set )
fixed broken dialogues in "Dark" theme
made pre-Oreo process a bit stricter (should no longer get bssid as the id by mistake).
v2.1.0 (9 Dec 2017 pre-sunrise )
used new library (RootShell by StEricson) to read files.
cleaned up some error handling.
v2.0.7 (3 Dec 2017 - evening)
changed the bug button from "add" to "refresh"
allowed manual entry for the Oreo config file location.
replaced "refresh list" menu option with "add item"
v2.0.6 (3 Dec 2017 - morning)
removed all compile-time warnings (including use of deprecated interfaces).
removed some un-used icons for the apk
v2.0.5 (2 Dec 2017)
re-added database, slightly different loading process (may prevent first hang on some devices).
v2.0.3 (also 26 Nov)
placed stricter error handling around loading of data.
v2.0.2 (also 26 Nov)
Added a checkbox to indicate current connection
v2.0.1 (26 Nov):
Removed database access, and several technical settings that were getting in the way.
Updated build platform from 23 to 24 (which is more stable, but not yet forcing Oreo which is version 26)
Fixed display to be responsive (text-boxes grow when the font does).
v 1.134 (25 Nov 2017):
some general clean-ups, and reviewing permissions needed. Hopefully fixing bugs reported in first few posts.
v1.132: initial build
Thanks for sharing. It loads forever on my Oneplus 3 on Stock OOS 5.0 (8.0.0)
LGXX said:
Thanks for sharing. It loads forever on my Oneplus 3 on Stock OOS 5.0 (8.0.0)
Click to expand...
Click to collapse
Hmm, sadly that's not enough info for me to do anything.
If there's a way you can send me a LogCat of the time when you try to run the app, then maybe I can see what's happening.
Hotfingers said:
Hmm, sadly that's not enough info for me to do anything.
If there's a way you can send me a LogCat of the time when you try to run the app, then maybe I can see what's happening.
Click to expand...
Click to collapse
https://ibb.co/dHTQyR
Works for me on my OP3
LGXX said:
https://ibb.co/dHTQyR
Click to expand...
Click to collapse
Hmm, OK so the main error is: -
Code:
.... 3406 E ActivityTyigger: activityResumeTrigger: not whiteListed com.pithsoftware.wifipasswords/com.pithsoftware.wifipasswords.activities.MainActivity/17
When I had a quick look on Google, there were several people having issues like this with a battery saving mode called "Doze" (here's an example post of their issue).
So not sure if this makes sense at all. If you haven't messed with the default battery savings settings on the ROM, then this probably doesn't apply to your situation.
Also, there's an interesting article in Stack-Overflow that may help - please let me know if it does.
OK - so the current download count is over 70 users; not too much feedback - so I'm assuming it's working
Working good for me on 8.1 Pixel XL
LGXX said:
Thanks for sharing. It loads forever on my Oneplus 3 on Stock OOS 5.0 (8.0.0)
Click to expand...
Click to collapse
I am having the same problem - just loads forever without showing anything. Pixel 1 XL Oreo November update only stock rooted. When I get a USB cable I'll do a logcat.
new build ready for testing
LGXX said:
https://ibb.co/dHTQyR
Click to expand...
Click to collapse
ragnarokx said:
I am having the same problem - just loads forever without showing anything. Pixel 1 XL Oreo November update only stock rooted. When I get a USB cable I'll do a logcat.
Click to expand...
Click to collapse
Hi guys,
Ok - so I tried a few things that should get the app to run better.
(the link on the OP has been updated to point to the new apk)
Please will you download, and let me know if the new version works any differently on your devices.
Thanks
Hotfingers said:
Hi guys,
Ok - so I tried a few things that should get the app to run better.
(the link on the OP has been updated to point to the new apk)
Please will you download, and let me know if the new version works any differently on your devices.
Thanks
Click to expand...
Click to collapse
Sadly nothing changed on my OP3 :/
I don't have Doze optimization enabled for this app by the way.
Just a text size issue. I have in my accessibility font size and display size set to "Large" which is causing the wifi password to be cut in half.
You can see it in the modified screenshot that is attached.
As a feautre request, can you add the feature to show the wifi password for the current wifi connection? Maybe move it to the top of the list or in a seperate header at the top. It could then say that the device is currently connected to: (SSID) Password/Passphrase: (passphrase) or some such..
Just a suggestion.
Thanks
New build posted on the OP (version 2.0.1).
Changes are: -
1. fixed display so that it adjusts to custom font sizes
2. updated build platform from 23 to 24 (this may help with your issue @LGXX, but i've still got no idea for sure)
3. removed ability to manually add entries.
3. removed lots of redundant Settings
dechronic said:
Just a text size issue. I have in my accessibility font size and display size set to "Large" which is causing the wifi password to be cut in half.
You can see it in the modified screenshot that is attached.
As a feautre request, can you add the feature to show the wifi password for the current wifi connection? Maybe move it to the top of the list or in a seperate header at the top. It could then say that the device is currently connected to: (SSID) Password/Passphrase: (passphrase) or some such..
Just a suggestion.
Thanks
Click to expand...
Click to collapse
Hey @dechronic, I've just release version 2.0.2 where the current connection is indicated by a checkbox
LGXX said:
Sadly nothing changed on my OP3 :/
I don't have Doze optimization enabled for this app by the way.
Click to expand...
Click to collapse
Hey @LGXX, please let me know if the latest version (2.0.2) works on your machine (i've re-wired a lot under the hood, and am hoping it makes a difference).
Hotfingers said:
New build posted on the OP (version 2.0.1).
Changes are: -
1. fixed display so that it adjusts to custom font sizes
2. updated build platform from 23 to 24 (this may help with your issue @LGXX, but i've still got no idea for sure)
3. removed ability to manually add entries.
3. removed lots of redundant Settings
Click to expand...
Click to collapse
Mine is just looping when I start it and not showing any data.
I noticed that the SuperSU toast is saying it is giving permission for /data/misc/wifi/wpa_supplicant.conf which is the pre-Oreo location.
I got this error in the logcat
11-26 07:19:02.633 E/BufferItemConsumer(4079): [unnamed-4079-576] Failed to release buffer: Unknown error -1 (1)
dechronic said:
Mine is just looping when I start it and not showing any data.
I noticed that the SuperSU toast is saying it is giving permission for /data/misc/wifi/wpa_supplicant.conf which is the pre-Oreo location.
I got this error in the logcat
11-26 07:19:02.633 E/BufferItemConsumer(4079): [unnamed-4079-576] Failed to release buffer: Unknown error -1 (1)
Click to expand...
Click to collapse
Thanks for the info - I tried putting soe extra error handling around the "load data" processes.
Please let me know if it works (release 2.0.3)
Quick question, does removing database mean that app only shows current state of WiFi config file?
So, you will not store WiFi codes as a record for future reference, phone update/flash?
Still loads forever with 2.0.3
Related
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Introduction
- This ROM is for the Apollo and Thor devices only
- Fire Nexus ROM is a refreshed and updated version of the formerly named HDX Nexus ROM.
- It was the first ROM I ever made for the Kindle HDX Tablets
Information + Features
- Pure AOSP Experience
- Open GAPPS nano is built-in
- SuperSU is built-in
- Lean and fast
- Ideal for customisation through Xposed
Prerequisites for Installation
- Safestrap v4 or TWRP recovery
Fresh Installation
- From recovery perform a Factory Reset
- Flash the ROM File
- Reboot and enjoy!
Upgrading to new version
- Flash the ROM File
- Reboot and enjoy!
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Source Code
- Kernel Source: Kindle HDX stock kernel, build number 1314.4.5.5.1
XDA:DevDB Information
kk-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-02-25
Last Updated 2019-10-02
Release Notes / Changelog
17 October 2016
- Ported Google's October 2016 security patches
- Ported Google's September 2016 security patches
13 August 2016
- Ported August 2016 Security Patches
- Ported July 2016 Security Patches
22 June 2016
- June 2016 Security Patch Level
25 May 2016
- May 2016 Security Patch Level
- Added security patch level string to settings app in the "About" page
- Enable swype gestures for Keyboard App
- Fixed keyboard suggestions force closing apps
09 Apr 2016
- April 2016 Security Patch Level
28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
17 Feb 2016
- Initial Release (Fire Phone Only Release)
Reserved
Initial Release
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
I don't plan on going back to Kit Kat, but thank you!
ggow said:
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
Click to expand...
Click to collapse
I tried LTE (4G) on my Thor. But it is not working. I found no network provider.
schr01 said:
I tried LTE (4G) on my Thor. But it is not working. I found no network provider.
Click to expand...
Click to collapse
- Try adding an apn
- Also it can take as long as 5 minutes to acquire mobile network
Sent from my Nexus 6 using Tapatalk
Irregular reboots
ggow said:
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
Click to expand...
Click to collapse
On a fresh thor (HDX 7 WiFi) install via Safestrap 4 (coming from Fire OS 4.5.5.1) I experienced a reboot twice so far...
ggow said:
- Try adding an apn
- Also it can take as long as 5 minutes to acquire mobile network
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I can not use APN. I only know the network provider name (Medion).
But the name does not appear after searching.
schr01 said:
Sorry I can not use APN. I only know the network provider name (Medion).
But the name does not appear after searching.
Click to expand...
Click to collapse
Are you seeing a baseband version in the settings page?
BOFH2k said:
On a fresh thor (HDX 7 WiFi) install via Safestrap 4 (coming from Fire OS 4.5.5.1) I experienced a reboot twice so far...
Click to expand...
Click to collapse
The ROM at the moment is based off 4.5.2, that's probably the reason why your experiencing this. Next update I'll be moving to the FireOS 4.5.5.1.
ggow said:
Are you seeing a baseband version in the settings page?
Click to expand...
Click to collapse
Thanks for the tip with the APN settings. My LTE with ALDI Plus (Eplus) is now working..
Dirty Flash over HDX Nexus v4.0.5
ggow said:
25 Feb 2016
- Fixed Screen Rotation
- Fixed Proximity Sensor
- Fixed Compass
- Speed up boot time
- Fixed CVE-2015-6602
- Fixed camera picture orientation
- Fixed setting default launcher for latest versions of Google Now Launcher
- Fixed Exchange has Stopped crash on startup
- This may need a fresh install if coming from Nexus ROM 4.0.5
Click to expand...
Click to collapse
tl;dr - Dirty flash over HDX Nexus v4.0.5 works (with caveats)
Being the conservative type I held back flashing this release ALAP. Developed a nervous twitch; dog and kids were worried.
My experience:
- starting from a well exercised Nexus v4.0.5 build on an unlocked thor
- above included a handful of Xposed modules and dozens of 'privileged' apps that demand root
- wiped cache/dalvik, dirty flashed 20160225 (nothing else), second cache/dalvik wipe; reboot
- very fast initial start-up (30 sec) followed by several min repopulating caches
- immediately spammed with "process android.process.acore has stopped working" toasts - ugh
- fought way to settings>apps>all and cleared data from Contacts Storage
- messages stopped and everything, including Xposed modules, appears to be working!
- no reauthorizations needed ...
- set animation scales to .75 to match previous responsiveness; may be an artifact of cache rebuild
Still early in testing; will update post as needed. Experience may not apply to Safestrap v4 users (wait for next release)
tl;dr v2: holy-crap-a-saurous!! Never expected it to be this easy. May further delay migration to CM13. Everything just works.
ggow said:
- Dated 25 Feb 2016
- Change log will be on Post #2
- LTE should be working - Can someone please test this on Apollo and Thor
Click to expand...
Click to collapse
FYI - Google location services not working in 20160225 which is a carry over from v4.0.5. Hoping future release can incorporate fix from Fire Nexus ROM for 5th gen devices.
For the curious neither device has a GPS chip in WiFi only models but can obtain an approximate location (often quite good) via Google's location service. The service does work on 3rd gen HDX devices as evidenced by the various CMxx roms.
Davey126 said:
FYI - Google location services not working in 20160225 which is a carry over from v4.0.5. Hoping future release can incorporate fix from Fire Nexus ROM for 5th gen devices.
For the curious neither device has a GPS chip in WiFi only models but can obtain an approximate location (often quite good) via Google's location service. The service does work on 3rd gen HDX devices as evidenced by the various CMxx roms.
Click to expand...
Click to collapse
Location services will be fixed in the next release
Sent from my Nexus 6 using Tapatalk
so, what are the advantages over Nexus ROM 4.0.5 if I may ask?
Anything worth switching to this one until CM 13 is stable enough for daily use (I planned on switching to CM 13 when CM team starts releasing monthly builds and camera is working)?
New Build is Up
- Dated 28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap and then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
- Change log is also on Post #2
jonashrem said:
so, what are the advantages over Nexus ROM 4.0.5 if I may ask?
Anything worth switching to this one until CM 13 is stable enough for daily use (I planned on switching to CM 13 when CM team starts releasing monthly builds and camera is working)?
Click to expand...
Click to collapse
Assuming you are running 4.0.5 now the primary differences will be in the underpinnings (shared across several devices), ongoing support (v4.0.5 is frozen) and enhancement/fixes introduced over time.
Fwiw - I continue to use HDX Nexus as my daily driver as it is fast, stable and feature complete. Augmented with Nova, Greenify and a few Xposed modules it looks/feels/performs like Android 5/6. I have several devices running CM11/12/13 and occasionally dabble with other flavors such as SlimLP. Some of those roms do hold an advantage on lower resource devices due to optimizations introduced by Google over time. So far nothing has convinced me to switch away from pure, delicious KK in AOSP clothes on a well provisioned HDX.
ggow said:
- Dated 28 Feb 2016
- Switch to using FireOS 4.5.5.1 binaries and boot.img
- TWRP users, dirty update will be fine
- Safestrap users should update to official Amazon FireOS 4.5.5.1, KingRoot, Re-install Safestrap and then install ROM.
- Fixed Location Services
- Updated Gapps to open_gapps-arm-4.4-nano-20160228.zip
- Change log is also on Post #2
Click to expand...
Click to collapse
Confirming Location Services is now working. Woohoo!!
---------- Post added at 11:06 AM ---------- Previous post was at 10:45 AM ----------
Not sure where to post this; will happily move if there is a better location. I wrote about the following behavior in a Nov 2015 post (Nexus 4.0.5). It remains an annoyance as a misfire will immediately FC the foreground app along with any work-in-progress. I was hoping this might magically disappear in more recent builds but it's still there. Thanks in advance for any consideration this warrants; understand it might not be fixable.
On two devices the foreground app FCs if a 'misspelled' word is corrected by selecting a replacement from the ASOP pop-up window. This happens with 100% certainty (app independent; keyboard independent) EXCEPT if the highlighted word begins in the first position of the current input field. Obviously frustrating when near the end of a lengthy input/email/post and loose everything. Of course, the problem can be avoided by disabling the AOSP spell checker under input settings but I prefer to keep it on as: 1) it clearly highlights unrecognized words with a red underscore; and 2) the suggestions are often better than those offered by popular keyboard apps. Note you can display the word list w/o triggering a crash. Just can't select a replacement. Did some reading on this awhile back; has something to do with illegally copying data from an overlay into a foreground window (can't immediately find the reference). Normally one would say it's an app/rom problem but it does not happen on a native Nexus 7. Also wasn't a problem with Nexus v2.
Summary: Foreground app FCs when a replacement is selected from the pop-up list of suggested alternatives when a misspelled word is highlighted (AOSP spell checker).
Davey126 said:
Confirming Location Services is now working. Woohoo!!
---------- Post added at 11:06 AM ---------- Previous post was at 10:45 AM ----------
Not sure where to post this; will happily move if there is a better location. I wrote about the following behavior in a Nov 2015 post (Nexus 4.0.5). It remains an annoyance as a misfire will immediately FC the foreground app along with any work-in-progress. I was hoping this might magically disappear in more recent builds but it's still there. Thanks in advance for any consideration this warrants; understand it might not be fixable.
On two devices the foreground app FCs if a 'misspelled' word is corrected by selecting a replacement from the ASOP pop-up window. This happens with 100% certainty (app independent; keyboard independent) EXCEPT if the highlighted word begins in the first position of the current input field. Obviously frustrating when near the end of a lengthy input/email/post and loose everything. Of course, the problem can be avoided by disabling the AOSP spell checker under input settings but I prefer to keep it on as: 1) it clearly highlights unrecognized words with a red underscore; and 2) the suggestions are often better than those offered by popular keyboard apps. Note you can display the word list w/o triggering a crash. Just can't select a replacement. Did some reading on this awhile back; has something to do with illegally copying data from an overlay into a foreground window (can't immediately find the reference). Normally one would say it's an app/rom problem but it does not happen on a native Nexus 7. Also wasn't a problem with Nexus v2.
Summary: Foreground app FCs when a replacement is selected from the pop-up list of suggested alternatives when a misspelled word is highlighted (AOSP spell checker).
Click to expand...
Click to collapse
- I'll look into this before the next release
Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU
The easiest way to send files to a device.
• Internet-less: Easily send files to all the devices in your network that use EasyJoin. Without pairing and Internet connection. Without ads and tracking.
• Files: Send photos, music, videos, documents and apks to a device fast, accurate and without limitations. Take advantage of all the bandwidth of your network and safeguard your data plan and internet bandwidth.
• Safety: End-to-end encryption when you transfer files.
• Privacy policy: We don't collect any data from you when you use the application.
There is a "Go" version for Android and Windows.
Get the Android version from XDA labs
Since xda-labs are down at the moment you can download the "Go" version from the site: https://easyjoin.net/android_free.html
Differences between Android versions "Go" and "Essential"/"Pro".
Less permissions. You can do less so you give less permissions.
When you close the app any background activity is also closed.
Has been removed broadcast listeners that could bring the app alive.
Auto accepting files is the default behavior.
Files are automatically saved in the corresponding system media folder based on their type.
If you need more functionalities try the "Essential" and "Pro" versions. XDA thread.
Unfortunately it crashes when I try to send something on my phone (HTC 10 Android 8). Furthermore it seems like the easyjoin app doesn't recognize my PC.
Freezy202 said:
Unfortunately it crashes when I try to send something on my phone (HTC 10 Android 8). Furthermore it seems like the easyjoin app doesn't recognize my PC.
Click to expand...
Click to collapse
You give me no info about the issues. It is crash the android or the windows version? Do you get any error that you can send me? Do you have enabled the Windows app to pass through your firewall?
I have a problem with the app on my phone. After I select a file and push the arrow, all I get is a black screen and that's it until a window pops up, which states "easyjoin go doesn't respond". Now I can send you feedback with system logs. I hope this will help.
Access through firewall is enabled.
Freezy202 said:
I have a problem with the app on my phone. After I select a file and push the arrow, all I get is a black screen and that's it until a window pops up, which states "easyjoin go doesn't respond".
Click to expand...
Click to collapse
Let me know if the issue persist with the next update (1.0.1 v2).
Nice. Now it works perfectly
Update Android 1.0.3
Solved an issue about sharing an installed application.
Bug fixes and minor improvements.
Update Android 1.0.4 and Windows 1.0.1
Bug fixes and minor improvements.
Update for Android 1.0.6
Solved an issue that could affect the search for new devices.
Bug fixes and minor improvements.
Will try it...
Update Android 1.0.7
Added shortcuts on app icon (Android 7.1 and later).
You can freely select multiple devices when sending a file.
Added second grid view with bigger image previews.
Privacy enhancement: android:fullBackupContent set to false.
Added Chinese translation.
Bug fixes and minor improvements.
Thankyouthankyouthankyou! This app totally fills my needs for a reliable and simple OTA file transfer. One thing though, and forgive me if this is covered by Essential or Pro: could it be possible to change the directories (i.e. from internal to external sdcard) for the received files?
slit said:
could it be possible to change the directories (i.e. from internal to external sdcard) for the received files?
Click to expand...
Click to collapse
This is possible in the other two versions but even there currently you can't write in all folders on the sdcard, only on the app folder.
Since i want to keep this version as simple as possible i prefer to not add options that are available in the other versions.
Update for Android & Windows
Android 1.1.1
Added Spanish translation.
Bug fixes and minor improvements.
Windows 1.1
Added Spanish translation.
Bug fixes and minor improvements.
The purchase of this application supports the development of the Essential and Go versions.
Keep this app installed and in a next update of the versions Essential and Go there will be a little gift for you!
Thank you.
Support: EasyJoin thank you!
Hi again!
Lately I'm having this weird problem where EasyJoin Go closes without warning while attempting to transfer any file or folder from Windows to my device. Also, when the transfer is successful, the files are partially transferred to my device (i.e. a folder with three files, only two transferred).
I recently changed my router, but everything else (windows and device side) seem to work perfect. Is there something I should take a look at?
Cheers,
slit said:
Hi again!
Lately I'm having this weird problem where EasyJoin Go closes without warning while attempting to transfer any file or folder from Windows to my device
Click to expand...
Click to collapse
Hi. Please read the FAQ and especially this: https://easyjoin.net/faq.html?15.
Are you using the latest version of the Android app? In this version a notification is created during sending/receiving a file that should prevent Android to suspend the app.
easyjoin said:
Hi. Please read the FAQ and especially this: https://easyjoin.net/faq.html?15.
Are you using the latest version of the Android app? In this version a notification is created during sending/receiving a file that should prevent Android to suspend the app.
Click to expand...
Click to collapse
Yes, updated both (W10 + Play Store) yesterday after seeing your update available. Sadly it's still a no go. Yes, I did check the FAQ beforehand.
What I find strange is that it feels like a trial and error, and when it works, it only transfers partially as I mentioned in my previous post
Thanks for your help though, I appreciate it.
Nice. Works fine in my device...............
Now it seems to work perfectly. I bought the Thank you! gift on Google Play. Thanks again, and merry xmas!
Ambient Music Mod is a Shizuku/Sui app that ports Now Playing from Pixels to other Android devices.
Requirements
Android device running Android 9.0 or above (11+ recommended).
Shizuku (Android 12+) or Sui Magisk module (Android 9+).
Shizuku does not require root, instead needing an ADB command or a few button presses to be made every reboot.
Features
Full Now Playing support, based on the latest version from Pixel devices and the latest music databases
Automatic Ambient Music recognition, with settings to control how often recognition runs - finding the right balance between battery usage and convenience
Now Playing History, Favourites and Summary support
Support to trigger recognitions manually, including a homescreen widget
On Demand recognition on supported devices, using the Google Assistant-backed recognition engine for songs that are not in the local database (must be triggered manually)
Show Now Playing songs on the lock screen (accessibility service required)
View the full track list of recognisable songs, and change the database location if your taste does not match your device's locale
Screenshots
Changelog
2.3.1
- Fixed crash on Android 14 Beta 3
2.3
- Android 14 Beta 2 support
- Added option to control Ambient Music Mod externally from apps like Tasker with options:
Enable Now Playing
Disable Now Playing
Toggle Now Playing
Start an On Device Recognition
Start an Online Recognition (if supported & enabled)
- External Access can be protected by an Access Token which must be provided by the apps interacting with it (enabled by default)
- Updated dependencies
For info on how to use External Access, check the page in the app or the Wiki page
2.2.2
- Fixed On Demand not working via the root method on some devices
- Improved Track Listing info, showing more details on tracks where available and fixing the Ask Google button
- Crash fixes
2.2.1
This is quite a large update, please make sure to update Ambient Music Mod and then Now Playing from the Updates screen after installing
- Enabled Now Playing Summary in the Now Playing History, a new feature that's not even on Pixels yet, which displays statistics about your listening habits including genre, artists, and timings from the last 30 days (configurable down to 1 day up to 365 days)
- NNFPv3 (the updated model) is now enabled on all devices except legacy armv7. Google have switched Pixels over to using it, indicating music databases for the legacy model may stop being updated at some point.
Please note that due to format changes, a database update will be forced after updating, and any saved On Demand recognitions will be removed. This is unavoidable, and Google has already done this on Pixel devices with official Now Playing
- Added experimental option to download extra country databases (up to two)
- Added option to periodically (daily/weekly/monthly) back up to a specified location
- Improved track list viewer speed by caching track info in Ambient Music Mod, rather than loading it from the Now Playing database every time. This will increase the storage footprint of Ambient Music Mod, but you can clear the app's cache if it becomes an issue.
- Added a track info viewer to the track list, displaying all available information for a track on one page, including links to play tracks in the database
- Added option to edit and delete stored On Demand tracks
- Updated database downloader, and implemented a system whereby the system Job Scheduler (which is relied on to schedule downloads) gets told to expedite downloads where possible. This should improve the speed of database downloads.
- Improved Lock Screen detection logic
- Fixed an issue where some switches in the app behaved differently depending on whether the text or the switch handle was pressed
- Fixed an issue where notifications for Now Playing were being re-enabled after being disabled by the user on some devices
nb: Version 2.2.1 fixes a cache issue with 2.2 which may impact updates. For this reason, it has replaced 2.2 and that version has been removed.
2.1.2
- Fixed Restore option not showing any options of files to restore
2.1.1
- Improved adaptive lock screen overlay
- Fixed insets on 3 button devices
- Allow install on x86_64 devices without libhoudini or libndk
2.1
- Added x86_64 support
- Fixed Android 13 Shizuku issue
- Updated switch style
- Removed "run when battery saver enabled" as it was not functioning and cannot be fixed
- Fixed overlay continuing to appear when bedtime mode is enabled
- Added message about static noise to playback screen
2.0.5
- Fixed an issue where on device recognition would not work on some devices using Shizuku
2.0.4
- Added the ability for On Demand recognitions to run without the Magisk overlay module, so long as the device is rooted. You must start Shizuku as root or use Sui to make use of this method, and the overlay is still preferred if it works on your device. Please read the Wiki page for more information.
- Further improvements to the On Demand overlay, fixing issues on OnePlus devices
- Fixed the Lock Screen overlay not appearing when Smart Lock is enabled
- Fixed Alternative Encoding and Lock Screen Overlay colour options not being backed up
2.0.3
- Added armv7 support
- Fixed crashes on Android 10
- Fixed an issue where some tracks were not showing up in the track list or in the track count (US database is actually 69k tracks, not 53k)
- Added an option to change the lockscreen overlay text colour
- The lockscreen overlay text now has a slight shadow, improving visibility
- Added caching for updates, which should prevent rate-limit issues. You can force an update check (ignoring cache) by swiping to refresh.
- Enabled landscape orientation
- Fixed background crashes in Now Playing, which may help download issues.
- Improved Magisk On Demand module overlay installing, which may fix bootloops on some devices
Note: Due to issues with the backend database update system, there have been two database updates in the last two days. This is now fixed, and future updates will be timely rather than all at once. Apologies for any inconvenience.
2.0.2:
- Added alternative encoding option, fixing distortion/crackling on some devices when enabled
IMPORTANT: You must also update Now Playing to 1.0.1 for the alternative encoding option to work. Use the Updates page in the app to update Now Playing.
- Increased max gain to 3.0 to cope with new encoding which requires a higher gain on some devices
- Reduced the chance of audio recording errors
- Removed "Timeout" notification as it was more useless than it was useful
- Fixed unclickable Chips on Recognition Success page (eg. Ask Google)
Click to expand...
Click to collapse
InstallationDownload the latest APK from the GitHub Releases page and install it. Ambient Music Mod will download and install the latest Now Playing APK for you as part of the setup process.
If you have any questions, please read the FAQ before opening a GitHub issue or replying to the thread.
App keeps asking to update and there is no update
toolhas4degrees said:
App keeps asking to update and there is no update
Click to expand...
Click to collapse
My bad, forgot to knock the internal version back down after testing the update dialog. I've "updated" the APK on GitHub, it's exactly the same build with the correct internal version, and will install on top
Awesome module! Unfortunately, I couldn't get it working. (SM-A725F - Galaxy A72, Android 11)
When doing the test recognition, it says "Ambient Music failed to start". When I try multiple times, it does actually listen, but when it's done listening, it gives me "No response from Ambient Music".
I paid attention to all the steps and fixes, but none of them worked. Tried with LSPosed and Edxposed. Also tried without whitelist and checked, that ambient services has mic permissions.
SkylinesHD said:
Awesome module! Unfortunately, I couldn't get it working. (SM-A725F - Galaxy A72, Android 11)
When doing the test recognition, it says "Ambient Music failed to start". When I try multiple times, it does actually listen, but when it's done listening, it gives me "No response from Ambient Music".
I paid attention to all the steps and fixes, but none of them worked. Tried with LSPosed and Edxposed. Also tried without whitelist and checked, that ambient services has mic permissions.
Click to expand...
Click to collapse
Interesting that it's started listening fine but didn't respond at the end, that suggests that maybe the delay time isn't long enough. Try using it as if it were working, see if it picks up music playing as that doesn't have the same delay limit
Quinny899 said:
Interesting that it's started listening fine but didn't respond at the end, that suggests that maybe the delay time isn't long enough. Try using it as if it were working, see if it picks up music playing as that doesn't have the same delay limit
Click to expand...
Click to collapse
Tried that, didn't work. Couldn't see any addition on my lockscreen, when playing music. My phone starts lagging when turning off or on, as soon as I enabled the recognition on lockscreen.
SkylinesHD said:
Tried that, didn't work. Couldn't see any addition on my lockscreen, when playing music. My phone starts lagging when turning off or on, as soon as I enabled the recognition on lockscreen.
Click to expand...
Click to collapse
You should still get a notification of the song even with the lockscreen overlay disabled
Quinny899 said:
You should still get a notification of the song even with the lockscreen overlay disabled
Click to expand...
Click to collapse
I didn't get any notification of the song.
SkylinesHD said:
I didn't get any notification of the song.
Click to expand...
Click to collapse
Alright then so it's probably not working at all. Can you do a log dump from the app? Instructions are in the FAQ.
This is the dump I got
SkylinesHD said:
This is the dump I got
Click to expand...
Click to collapse
Thanks, that's very useful:
Code:
sound_trigger_platform: platform_get_lsm_usecase: No lsm usecase found for exec_mode 0
is in the logs, suggesting it doesn't like the sound_trigger_platform.xml file, specifically the lsm_usecase bit. Unfortunately the current version of the app fails to zip that right when dumping, so could you do the following please:
- Send the current file in /system/vendor/etc/sound_trigger_platform_info.xml
- Disable the Magisk module in the Magisk app, and reboot
- Send the new file in /system/vendor/etc/sound_trigger_platform_info.xml (this should be different to the first, and be original to your device)
I'll then try to figure out if something else may be required to be added on some devices, or if there's a limitation of the 'magic numbers' in the file I took from the Pixels (in which case it will likely sadly never work).
I'll also fix the dump thing so it zips the xml correctly for the next build.
Cheers!
Quinny899 said:
Thanks, that's very useful:
Code:
sound_trigger_platform: platform_get_lsm_usecase: No lsm usecase found for exec_mode 0
is in the logs, suggesting it doesn't like the sound_trigger_platform.xml file, specifically the lsm_usecase bit. Unfortunately the current version of the app fails to zip that right when dumping, so could you do the following please:
- Send the current file in /system/vendor/etc/sound_trigger_platform_info.xml
- Disable the Magisk module in the Magisk app, and reboot
- Send the new file in /system/vendor/etc/sound_trigger_platform_info.xml (this should be different to the first, and be original to your device)
I'll then try to figure out if something else may be required to be added on some devices, or if there's a limitation of the 'magic numbers' in the file I took from the Pixels (in which case it will likely sadly never work).
I'll also fix the dump thing so it zips the xml correctly for the next build.
Cheers!
Click to expand...
Click to collapse
Got the files, I hope the issue will be fixable. Good luck!
SkylinesHD said:
Got the files, I hope the issue will be fixable. Good luck!
Click to expand...
Click to collapse
Re-enable the module, extract and drop the attached file in /data/adb/modules/AmbientMusicTest/system/vendor/etc/ and reboot, see if that helps
Side note, I really need to change that AmbientMusicTest name
Quinny899 said:
Re-enable the module, extract and drop the attached file in /data/adb/modules/AmbientMusicTest/system/vendor/etc/ and reboot, see if that helps
Side note, I really need to change that AmbientMusicTest name
Click to expand...
Click to collapse
Great, this really works! But now I noticed another problem..
The database is loading for ever when I go on Track list, it also cannot recognize any song.
SkylinesHD said:
Great, this really works! But now I noticed another problem..
The database is loading for ever when I go on Track list, it also cannot recognize any song.
Click to expand...
Click to collapse
It's unlikely to be loading forever, it just takes a long time to load. Leave it for a few minutes and it should load.
Meanwhile, if the module is working now you'll probably want to play with the amplification a bit, test the output with the test playback and fingers crossed it'll start recognising things then.
Quinny899 said:
It's unlikely to be loading forever, it just takes a long time to load. Leave it for a few minutes and it should load.
Meanwhile, if the module is working now you'll probably want to play with the amplification a bit, test the output with the test playback and fingers crossed it'll start recognising things then.
Click to expand...
Click to collapse
The output is perfect, I left it loading for about ~2-3 mins., I'll try again. Hopefully it'll work.
SkylinesHD said:
The output is perfect, I left it loading for about ~2-3 mins., I'll try again. Hopefully it'll work.
Click to expand...
Click to collapse
If it still doesn't load after like 5 minutes (there's also a progress bar that should show progress) after restarting the app, what region are you in? I've previously tested the database parsing with en_GB and en_US and it was working fine but maybe it's broken for another one
Quinny899 said:
If it still doesn't load after like 5 minutes (there's also a progress bar that should show progress) after restarting the app, what region are you in? I've previously tested the database parsing with en_GB and en_US and it was working fine but maybe it's broken for another one
Click to expand...
Click to collapse
I'm located in germany (probably something like de_DE)
There is a progress bar, but it doesn't show me a progess. It's just like.. loading
On miui 12.5 I think my Problem is that I can't grant the App access to the microphone.
McFlypants said:
On miui 12.5 I think my Problem is that I can't grant the App access to the microphone.
Click to expand...
Click to collapse
Tap the microphone prompt in Ambient Music, you have to grant it manually via the app info (not sure why Google didn't just implement a prompt like everyone else does). I have also found that sometimes when you've just granted it access it doesn't immediately respond to test recognition, if you find it still sits loading after that then kill Ambient Music via the recents, reopen it via Ambient Music Mod, return to Ambient Music Mod and try running the recognition again.
Disclaimer
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Rules
- Please search the thread before asking questions
- The old thread is linked below - a lot of good information there.
- Please try to stay on topic, I know it's not always possible
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg where possible
Fresh Installation
- Backup your existing ROM first
- Wipe the /data partition (but you can keep the media storage)
- Flash the ROM File
- Flash Open Gapps: use an ARM 7.1 version smaller than the "full" size to make sure it fits
- Reboot
- Enjoy!
Old Thread
- https://forum.xda-developers.com/t/rom-05-jul-2020-lineageos-14-1.3517481/
Downloads AFH
- LineageOS Builds for Thor
- LineageOS Builds for Apollo
Downloads Google Drive
- LineageOS Builds for Thor
- LineageOS Builds for Apollo
Source Code
- Kernel Source
- Common Device Tree
- Thor Device Tree
- Apollo Device Tree
Credits
- LineageOS
- Cyanogenmod
- CodeAurora
- ggow
- Hashcode
- Cpasjuste
- dpeddi
⏱ Change log / Release Notes
TBC
- SELinux now Enforcing
- Fixed almost all denials
- SafetyNet now passes Basic Integrity and CTS profile match
- Fixed watchdog bark in WiFi driver when SELinux is Enforcing
- Shim libwvm.so to fix DRM crash
- Add signature spoofing patch for micro-g support
17 March 2022
- Add zram support
02 February 2022
- Added WiFi patches by @void555
- Added aptX codec support - I don't have any devices to test it - let me know if you do.
- This release is the first to feature almost perfect WiFi capability.
🛠 Worklist / Tasks
- [todo] SELinux
New Build is Up
Dated 02 February 2022
- Added WiFi patches by @void555
- Added aptX codec support - I don't have any devices to test it - let me know if you do.
I encourage everybody to switch to this ROM now. The wifi problems are gone and the ROM itself is stable for a long long time. And with its high quality display it could serve as a reader for much more years.
Thanks for your continued support of these devices. Is clean flash absolutely necessary? Or is there a chance dirty flash will be fine?
Dirty flash is fine
@ggow : let´s talk about Android Webview as it is one of the very important components and one with high security demand. Is it best to use the one from Google play store which receives regular updates?
Which on is packed into the Rom?
cl-i said:
@ggow : let´s talk about Android Webview as it is one of the very important components and one with high security demand. Is it best to use the one from Google play store which receives regular updates?
Which on is packed into the Rom?
Click to expand...
Click to collapse
LineageOS provides Android Webview which is based off Chromium (which is open source)
I don't use google play store on my devices, so normally I roll with the one included in the OS.
I used to include Bromite WebView in a build for another device which is also open source and Chromium based (if I remember correctly). It is supposed to be much more de-googled than even Chromium.
So we get a fresh chromium web-view version from linageOs everytime you build a new ROM. but no way to update between..
cl-i said:
So we get a fresh chromium web-view version from linageOs everytime you build a new ROM. but no way to update between..
Click to expand...
Click to collapse
This is the repo that get's built into lineageos. And yes it's only updated when you get a newly built rom. The frequency of update is also dependant on the upstream Chromium source code.
GitHub - LineageOS/android_external_chromium-webview
Contribute to LineageOS/android_external_chromium-webview development by creating an account on GitHub.
github.com
hi,
i changend the aosp webview to bromite webview (with twrp)
Installing SystemWebView
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! - bromite/bromite
github.com
it works very well on apollo
ggow said:
This is the repo that get's built into lineageos. And yes it's only updated when you get a newly built rom. The frequency of update is also dependant on the upstream Chromium source code.
GitHub - LineageOS/android_external_chromium-webview
Contribute to LineageOS/android_external_chromium-webview development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Hi, just FYI, both Bromite the browser and Bromite System WebView can be manually updated by downloading and installing from here or here.
I‘m playing real racing 3 on the hdx7 since April 2014. To keep it running, I’m constantly fighting with free main memory. All unnecessary apps & system apps are disabled. Playing with buil.prop parameters for memory (davlik.vm.heapsize=256m , davlik.vm.heapgrowthlimit=128m) saved me from “out of memory“ 2 years ago, but the game grows quick.
Any idea for more memory, perhaps inside the kernel?
by the way, los16 wasn‘t able to run Rr3 any more Due to mem.
cl-i said:
I‘m playing real racing 3 on the hdx7 since April 2014. To keep it running, I’m constantly fighting with free main memory. All unnecessary apps & system apps are disabled. Playing with buil.prop parameters for memory (davlik.vm.heapsize=256m , davlik.vm.heapgrowthlimit=128m) saved me from “out of memory“ 2 years ago, but the game grows quick.
Any idea for more memory, perhaps inside the kernel?
by the way, los16 wasn‘t able to run Rr3 any more Due to mem.
Click to expand...
Click to collapse
I'm having a look at getting zram working.
Not sure if its working as expected, but this happened on prior versions too...
If I set the Wifi to only stay on when charging, thinking that I am trying to preserve battery and let the wifi go off if I'm not using the tablet, the Wifi doesn't automatically turn back on when I pick it up and turn the screen on. If I then enable the wifi... it switches on, but no networks appear. I find that either restarting or toggling airplane mode brings things back.
I found Wifi turns OFF and doesn’t turn on when switching the tablet on later. This doesn’t reduces my fun with the new Rom version. Keep wifi in ‘always on‘ mode. All my new wifi phones and tablets let wifi stay on all the time.
Bwangster12 said:
Not sure if its working as expected, but this happened on prior versions too...
If I set the Wifi to only stay on when charging, thinking that I am trying to preserve battery and let the wifi go off if I'm not using the tablet, the Wifi doesn't automatically turn back on when I pick it up and turn the screen on. If I then enable the wifi... it switches on, but no networks appear. I find that either restarting or toggling airplane mode brings things back.
Click to expand...
Click to collapse
cl-i said:
I found Wifi turns OFF and doesn’t turn on when switching the tablet on later. This doesn’t reduces my fun with the new Rom version. Keep wifi in ‘always on‘ mode. All my new wifi phones and tablets let wifi stay on all the time.
Click to expand...
Click to collapse
I'm not seeing that behavior, the WiFi seems to always reconnect here (at home).
If you post logcat and dmesg I can take a look.
.. I see it only with "stay on only when charging" Wifi option, but thats not a mode I'm using any more.
ggow said:
I'm not seeing that behavior, the WiFi seems to always reconnect here (at home).
If you post logcat and dmesg I can take a look.
Click to expand...
Click to collapse
Here is a logcat from the last few hours where I had the wifi set to go off when sleeping, and it stays disabled when I turn the screen back on to use it.
02-12 14:12:56.958 24874 24874 I art : at void android.webkit.WebView.ensu - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com