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
Related
KitKatDS - Android 4.4 (CM 11.0) for the myTouch 4G Slide
README
Emmanuel U said:
Ugh... (oh how I've dreaded making this post, go grab the kleenex or you can just skip the next paragraph and get to the jist)
So my (previously used and "refurbished") myTouch is slowly becoming useless. So I had originally dropped it onto concrete (a month and a half ago) in which I didn't notice any visual/cosmetic damages so I assumed I was fine. However promptly after attempting to open my keyboard I notice my phone would freeze for 5 or seconds before registering the hardware event and rotating screen etc. It eventually began to progress to display weird digital artifacts at random times during use (which would cause annoying lag). Then one faithful day, the 'lag' was getting to excessive while I urgently needed to use my phone so I battery pulled in hopes of rebooting the phone as quickly as possible to use...but just my luck; the phone turned back on but the display didn't (in the sense that I felt the phone vibrate when I initially pressed the power button alongside seeing the small red light in my trackpad light up). So after a stressful day of trying to play with my phone in fastboot/adb I managed to turn my display back on. But now the display failure has progressed to the point of my phone only being usable when they keyboard is pulled out around 2/5 of the way and kept in that position....all other positions render the display useless. This makes it fairly difficult to use the device seeing as it has to be kept in this abnormal position to function.
Jist: I ordered a temporary Galaxy S2 off ebay until my contract ends so that I can switch carriers all together. So I won't really be able dev on this phone like I use to with it being broken. However I'll try to still occasionally update my roms as far as upstream...but any bug fixes at this point sadly won't be able to come from me as debugging on this phone is tedious. But keep in mind I'll still poke my head periodically in this forum and see if my 2 cents is needed anywhere. But don't expect anything more from me then 'upstream updates'.
Good day guys and remember to have a firm grip on your phone at all times.
Update:
First of all I'm quite flattered to all the people who offered up a MT4GS to giveaway, such a generous community we have here :good:
However this will not be necessary as I still have a slightly working MT4GS...the only reason I got a GSII is because it's not functional enough to be my daily driver due to the position it has to be held in to function. Nevertheless I can still develop on the phone (which was why I stated I was planning on updating this rom soon). But I'd like to say thanks again directly to @BaconPancakes and @Ziida and anyone else who may have been planning to offer me a a MT4GS...but it won't be needed.
Click to expand...
Click to collapse
Notes:
Found a dead link? Let me know! (check my sig for a backup of all my files for the time being)
You must only use the included kernel! Or else DO NOT report bugs
Bugs/Issues:
ADSP (1080p Camcorder) occasionally leaks memory and force closes. Reboot to fix. (I'll fix when sync with CAF)
You tell me of any other issues?
Disclaimer:
Code:
#include <emman.h>
/*
* Your warranty is now void.
*
* 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Thanks to:
Team Hydra
SilverL
Scverhagen
Team DS & CyanogenMod
Team Hydra
Code Aurora
Bruce2728
Evervolv
LiquidSmooth
CarbonDev
SlimRoms
RootWebGod
Overhauling
SultanXDA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
Recommended KK 4.4 Gapps: De-Bloated
Latest MD5: 77f07aefbddcac575b3a0c84d7f945f4
v1.4:
AFH | Mirror #1 / #2
All Releases: AFH | TRU Mirrors
Sources
Rom Source
ION Kernel Source
Changelog:
Code:
[B]--- v1.4 ION- December 9, 2014 ---[/B]
- Updates from Upstream CM
- Camcorder is now fully functional
- WildKernel Updates
- ADSP may occasionally leak memory when changing camcorder to 1080p, resulting in an force close. A reboot will fix. (I will fix this after I sync with CAF)
[B]--- v1.3 ION w/ WildKernel v001 - October 7, 2014 ---[/B]
[COLOR="Red"][B]- [URL="https://copy.com/iA8SGsLIcULaTOyS"]Kernel[/URL] must be downloaded separately, and flashed alongside KKDS v1.3 [/B][/COLOR]
- Camcorder Issues Fixed
- Battery issue patched
- No bugs :) (for now lol)
[B]--- v1.3 ION - February 2, 2014 ---[/B]
- [B]Full Wipe is required for camcorder to function from all previous versions (1.1 and below).[/B]
- Kernel Memory Map has had major changes, RAM is currently at 518mb (I will allocate more in time)
- Video Recording and Playback fully functional
- Camera app was rolled back a bit because current upstream version has some issues
- All bugs fixed except those listed in OP
[COLOR="red"]- [B]This and All future versions will have an ION kernel and will not be able to use any other previous kernels (unless noted otherwise).[/B][/COLOR]
- Tell me how this new kernel feels?
[B]--- v1.2 ION Preview Build 2 - January 31, 2014 ---[/B]
- [B]Full Wipe is required for camcorder to function from all previous versions.[/B]
- Kernel Memory Map has had major changes, RAM is currently at 518mb (I will allocate more in time)
- Video Playback works
- 720p video recording works
- Vidc is now fixed, all that is left now is Venc.
- Lots of kernel drivers have been updated for ION from CAF- [B]This and All future versions will have an ION kernel and will not be able to use any other previous kernels (unless noted otherwise).[/B]
- EGL libs updated, no more laggy apps.
[B]--- v1.2 ION Preview - December 14, 2013 ---[/B]
- [B]Full Wipe is recommended but NOT required from 1.1 or below.[/B]
[COLOR="red"]- [B]This and All future versions will have an ION kernel and will not be able to use any other previous kernels (unless noted otherwise).[/B][/COLOR]
- Black Screen Bugs are fixed.
- Memory Map Overhaul
- Ramdisk changes (ION)
- Camera Rotates Regardless of System Setting
- Feature Updates from CM Upstream
- Tell me how this new kernel feels?
[B]--- v1.1 - December 4, 2013 ---[/B]
- SDcard is now fully fixed.
- Mounting USB Storage is fixed
- LCD Density lowered to 220 to make layouts look better.
- Ramdisk changes
- Feature Updates from CM Upstream
[B]--- v1.0 Beta - December 1, 2013 ---[/B]
- Initial Release
Screenies:
Coming Soon!
AOSP Browser is being funky across the board on 4.4. It's being kind of screwy on my Nexus 4 too and it's due to the removal of WebView (IIRC, AOSP browser was just a wrapper). I wouldn't worry too much about that as opposed to the other problems.
There should be better performance though, I've been reading about great improvements on older phones using KitKat ROMs (like the Nexus One).
WoW
Emmanuel U said:
"KitKatDS Beta - Android 4.4 (CM 11.0) for the myTouch 4G Slide"
Click to expand...
Click to collapse
Thank You Man...:victory:
You're awesome Emmanuel..
Thanks for this one! Flashed, and booted.
Bugs which I've found, mostly related to SD card:
Occasionally, Settings crashes when tapping on Apps.
Apps crashes when sliding to "ON SD CARD".
SD card is recognised by File Manager, but not by Camera. Files can be accessed via File Manager.
When Gallery opens, a pop-up says "No external storage available". But, the folders found on the SD card do appear in Gallery, behind the pop-up. Same thing happens when opening pics from File Manager. Gallery opens the pic, but still says "No external storage available". Then, tapping anywhere on the screen exits Gallery. Apollo can also access and play audio files from SD card.
And sometimes, phone soft-reboots when installing apks.
Something about switching Wi-Fi on. Sometimes it says "Turning Wi-Fi on..." aaaand keeps saying that, whilst Wi-Fi remains off. Rebooting the phone fixes it.
Gesture-typing on Android keyboard doesn't seem to work.
Oops, oops. Android Runtime (ART) causes bootloop.
I think the LCD density should be lowered. 240 is much. For instance, I've set up a PIN protection on the lockscreen and it says "6..." instead of "6 MNO", "7 P..." instead of "7 PQRS", "9..." instead of "9 WXYZ" - I've personally set it to 200 and now everything's well displayed.
Keep up the good work!
Wow it's Kitkat! Thanks a lot!
There has been a misconception on a bug with this rom, all other internet browsers work. The only one that does not function is the stock browser app.
SDcard still needs more playing around with and the lcd density has been changed to 220 as it looks better. Hopefully once fixed an update will be out soon making this rom a stable, in which I can go help out @scverhagen with 3.4
I was able to fully fix the SDcard today, expect (hopefully) the first stable release tomorrow.
Awesome dude, thanks for the sources! I can update my rom
I am totally keeping an eye on this thread. In addition to using my phone as a phone (LOL), using it as a wifi/bluetooth hotspot is also a major use case for me. Looking forward to seeing other people's experience and if the tethering works works out, I might just jump onboard too!
Sent from my MyTouch 4G Slide using Tapatalk 2
Update, Enjoy!
Downloading now!
Sent from my MyTouch 4G Slide using Tapatalk
rtiangha said:
Downloading now!
Sent from my MyTouch 4G Slide using Tapatalk
Click to expand...
Click to collapse
Me too! Thanks Emmanuel U!
I'm due for a reflash anyhow, so if I don't hear any serious complaints within the next day or two I'll be testing this one out as well!
KitKatDS v1.1
Gesture-typing works.
Apps crashes are gone.
I don't know how to reproduce this bug, but... So far, twice, the menu and back keys randomly stopped working, but a device restart fixes that.
And the "Google Keyboard" isn't of much use since it never opens and always crashes. Dunno why it's there. I'm using the Android Keyboard anyway.
Pretty stable ROM, I'd say. Nice work!
Is ART working? I haven't had a chance to download and flash it on my MT4GS. It made things extremely smooth on my Nexus 4.
Sorry for the stupid question, but are these the install steps - so we're all on the same page? Also, I have S-On - does that make a difference? Or did that only apply to GB & ICS? [Answer: Yes, it makes a difference!! Need to flash boot.img - follow steps below]
-Backup anything important (pictures,downloads,etc)
-Copy over new ROM + compatible GApps
-Boot into recovery: power down (take out bat if needed)->hold vol down + pwr button->vol down to select recovery->pwr but to select
-Do CWM Recovery Backup (if desired - really no reason unless backing up stock/OEM ROM)
-Wipe data/factory reset, wipe cache partition, Advanced->Wipe dalvik cache, Wipe bat stats
-Power off->hold vol down + pwr button->vol down to select recovery->pwr but to select Fastboot
-Plug in usb cable, should say FASTBOOT USB
-Flash boot.img kernel Using MyTouch_4G_Slide_All-In-One_Kit_V2.0.rar
--Put boot.img file from ROM zip into data/kernels/ dir
--Select "With this command"->Flash Kernel button. Will say "device not found", ignore. Should end up saying finished
-As soon as phone reboots, unplug usb & pull batt, & then reboot into CWM recovery
-Install zip from SD card: Flash new ROM
-Install zip from SD card: Flash new GApps
-Reboot system Option. Should take ~2minutes
EDIT:
Thx for the response SKAm69 - Updating this so others dont get confused. I tried w/o flashing the boot.img first & the wheel just kept spinning, 15+min! With the updated steps above I was able to get it to work. Thanks!!!
kevin71246 said:
Sorry for the stupid question, but are these the install steps - so we're all on the same page? Also, I have S-On - does that make a difference? Or did that only apply to GB & ICS?
-Backup anything important (pictures,downloads,etc)
-Do CWM Recovery Backup (if desired)
-Copy over new ROM + compatible GApps
-Boot into recovery: power down (take out bat if needed)->hold vol down + pwr button->vol down to select recovery->pwr but to select
-Wipe data/factory reset, wipe cache partition, Advanced->Wipe dalvik cache, Wipe bat stats
-Install zip from SD card: Flash new ROM
-Install zip from SD card: Flash new GApps
-Reboot system
Click to expand...
Click to collapse
If you are S-On you definitely have to fastboot flash boot boot.img
Feedback
Feedback: (I'll update if I get more)
-Very fast, responsive ROM (Not sure if this is the wonderful work of the Dev or KitKat in general. App installs, for example, are very quick. While setting up my phone I installed ~10 apps across wifi in about 2 minutes, including searching & clicking. In previous JB ROMs this easily would've taken 10+ minutes
-Trackball functionality is hit or miss
-Broke stock browser black screen - I know this is a known bug - not a big deal. Chrome works great
-"Google" Now(?) banner on home screen doesn't fit - Only see "...le" characters from "Google". Not a big deal at all, but looks odd. Long press holding it doesn't seem to work to delete it. Sure there's a way in the settings to remove it...
-Some emails I noticed I see the same 'stock browser black box' inside of. ie, open an email and find black box for some emails.
-"Complex" text messages send via email are not able to get "downloaded" to phone. You will see a toast error message. Reproduce: send yourself a text via email to your phone with 50+ chars in subject line, with multiple formatting in body. But it works fine for a email text like "Test" as subject & "Test" as body (Deal breaker for me since I get text email pages from work to my phone )
KitKat Specific Notes (Can't blame Dev for this)
-Not loving the KitKat additional security requirements for Corp Outlook, but not a big deal (requires pin locking now)
-HATE Google Conversations view - Setup gmail via builtin "Email" app (not GMail app) & all emails get grouped into conversations. I don't see any setting to undo this. I HATE IT!! Anyone know how to disable this?
Can't forget to say thanks to the Dev for all the efforts here! Nice job! Just curious - how long does it take to do something like this?!!
---------- Post added at 12:54 PM ---------- Previous post was at 12:35 PM ----------
Emmanuel U: You have quite a few recent ROMs out there for this phone. Any one in particular you'd recommend? (Differences?) Due to the text bug I just reported for this particular KitKat ROM I need to revert to JB version X so my phone works for work. Need something stable. 4.3.1 sounds appealing. Thanks & nice work & we all appreciate all your time put into this!
kevin71246 said:
Feedback: (I'll update if I get more)
-Very fast, responsive ROM (Not sure if this is the wonderful work of the Dev or KitKat in general. App installs, for example, are very quick. While setting up my phone I installed ~10 apps across wifi in about 2 minutes, including searching & clicking. In previous JB ROMs this easily would've taken 10+ minutes
-Trackball functionality is hit or miss
-Broke stock browser black screen - I know this is a known bug - not a big deal. Chrome works great
-"Google" Now(?) banner on home screen doesn't fit - Only see "...le" characters from "Google". Not a big deal at all, but looks odd. Long press holding it doesn't seem to work to delete it. Sure there's a way in the settings to remove it...
-Some emails I noticed I see the same 'stock browser black box' inside of. ie, open an email and find black box for some emails.
-"Complex" text messages send via email are not able to get "downloaded" to phone. You will see a toast error message. Reproduce: send yourself a text via email to your phone with 50+ chars in subject line, with multiple formatting in body. But it works fine for a email text like "Test" as subject & "Test" as body (Deal breaker for me since I get text email pages from work to my phone )
KitKat Specific Notes (Can't blame Dev for this)
-Not loving the KitKat additional security requirements for Corp Outlook, but not a big deal (requires pin locking now)
-HATE Google Conversations view - Setup gmail via builtin "Email" app (not GMail app) & all emails get grouped into conversations. I don't see any setting to undo this. I HATE IT!! Anyone know how to disable this?
Can't forget to say thanks to the Dev for all the efforts here! Nice job! Just curious - how long does it take to do something like this?!!
---------- Post added at 12:54 PM ---------- Previous post was at 12:35 PM ----------
Emmanuel U: You have quite a few recent ROMs out there for this phone. Any one in particular you'd recommend? (Differences?) Due to the text bug I just reported for this particular KitKat ROM I need to revert to JB version X so my phone works for work. Need something stable. 4.3.1 sounds appealing. Thanks & nice work & we all appreciate all your time put into this!
Click to expand...
Click to collapse
Alright I'll take another look at LCD density (I thought I had nailed it because everything looked to proper scale). I've noticed the menu/back button unresponsive bug, The black screen bug won't be fixed (as far as I'm concerned) until we can get a 3.4 kernel on KK. This text message problem, is it from the stock messaging app or Hangouts?
Technically it took me about a month to get KitKat booting for our device, however if put into reality (based on time actually spent devving, not just time being passed by) I would say it was about a week
CyanogenMod 11 (based on Android 4.4.4 "KitKat") for the HTC Liberty/Aria/Gratia/etc
NOTE: Just to make this clear, this is UNOFFICIAL, and NOT supported by CyanogenMod.
Hboot 1.02 or higher is required! (Revolutionary or HTCdev unlock)
Liberty is now an official device on the androidarmv6 project
This means updates will show up in Settings > About phone > CyanogenMod updates
However updating via the updater may not always work, due to very constrained system space.
Patches can be submitted to http://review.androidarmv6.org/
Huge thanks to everyone working on marvel/Wildfire S (Olivier, izi501, feroxx, Kevinjoa, thehacka1, benjamingwynn, JDevs, more I don't know?) & the androidarmv6 team
The kernel includes TONS of CPU governers, and a couple extra I/O schedulers.
I don't really care for kernels with this many CPU governers, but the rest of the changes to the kernel are useful, and it's more work taking them back out so I left them in
No idea what may or may not be better, but the default seems to work fine.
Screenshots: http://winsuk.net/screens/liberty/cm11/
Required recovery: http://forum.xda-developers.com/showthread.php?t=2474662
Known bugs/etc:
Slow - everywhere (I recommend CM9 or CM10)
Apps sometimes don't load on boot (appear to be completely gone) - even system apps
WiFi hotspot doesn't work
Screen brightness sometimes sticks at dim when turning on
Transparent GIFs in browser have a solid background
Large images in browser are usually broken
No adb screenrecord
No ART
Notes:
USB tethering: enable it, unplug & replug, then enable it again and it should work
For a transparent status bar, enable high-end graphics in Performance settings
USB debugging verify (the popup when you plug into a new PC) doesn't always work, so it has been disabled
Gesture typing, Photosphere, and voice recognition: all require closed-source libraries from Google built for ARMv6, which don't exist.
I can't make any of these work unless Google does.
Downloads!
Newest builds from the androidarmv6 buildbot can be found here:
http://download.androidarmv6.org/_builds/liberty/
Mirrors for stable build RC11:
cm-11.0.0-RC11-liberty.zip - d94c7e2163ce434241bfc0ee02c84eb1
androidarmv6: http://download.androidarmv6.org/_builds/liberty/stable/cm-11.0.0-RC11-liberty.zip
Google Drive: http://goo.gl/D635Gc
xda devdb: http://forum.xda-developers.com/devdb/project/dl/?id=9311
MediaFire: https://www.mediafire.com/?kf3it5ckd46mf3o
Google Apps: http://forum.xda-developers.com/showthread.php?t=2756379
Google Search cannot be installed from the Play Store, however if you can get an apk for it (like here maybe), it will work (sans voice) with one setting change:
1. install Google Search app (from apk)
2. open it, and hit Yes, I'm in
3. let it crash
4. open Google Settings from the app drawer
5. navigate to Search & Now > Voice > "Ok Google" hotword detection
6. slide hotword detection to off
7. done, it works
There is also an app to sort-of enable voice search in Google Search/Now: http://forum.xda-developers.com/showthread.php?t=2709285
Source:
Manifest with full ROM & kernel source
Kernel source only
Previous builds can be found here or here or here
Changelog of builds:
20140614 (June 14th, 2014):
First build from androidarmv6 jenkins
CM Updater added (should be getting weekly builds from jenkins through it soon)
Miscellaneous changes from CM and/or androidarmv6
20140607 (June 7th, 2014):
Android 4.4.3
Disabled fading edges on text for a small speedup - before, after
Switched to gps.conf with SUPL (assisted GPS) support - I can't tell a difference, but it may speed up GPS for some
Terminal Emulator updated
Upstream CM things (I don't keep track )
20140519 (May 19th, 2014):
Re-added missing fonts for various languages (they got removed during the KK bringup)
Removed what livewallpapers were left - this will not only free up some space on /system, but also /data because they had to be cached there
Removed CM Wallpapers to free up /system space (as with the live wallpapers, should free up a little on /data as well)
Removed 05mountsd script - most sd-ext solutions seem to have mounting built in now, and it conflicts with some
SELinux enabled in kernel - this may improve battery life as audit was constantly crashing without SELinux
Changes from CM (including new theme engine, oooh!)
20140507 (May 7th, 2014):
Got camera working (all of it including timelapse no glitches either)
Added some extra encoder/decoder files - not sure if they are doing anything right now
Latest changes from CM (whatever that may be)
20140503 (May 3rd, 2014):
Fixed hardware video decoder (& encoder)
Fixed GPS
20140501 (May 1st, 2014):
Baseline build
XDA:DevDB Information
Unofficial CyanogenMod 11, ROM for the HTC Aria
Contributors
WinSuk, Olivier, izi501, feroxx, Kevinjoa, thehacka1, benjamingwynn, JDevs, androidarmv6 team, more I don't know?
Source Code: https://github.com/androidarmv6/android/tree/cm-11.0
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 2.6.x
ROM Firmware Required: hboot 1.02 (Revolutionary or HTCdev unlock)
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20140614
Beta Release Date: 2014-06-14
Created 2014-05-01
Last Updated 2014-12-04
The camera has the opportunity to fix?
fmshe said:
The camera has the opportunity to fix?
Click to expand...
Click to collapse
Maybe... Our camera blob (from gingerbread) is extremely outdated, and something it relies on was removed in 4.4.
New build uploaded:
20140503 (May 3rd, 2014):
Fixed hardware video decoder (& encoder?)
Fixed GPS
http://goo.gl/c6Kekq
c298645ed377de26a6c3a833b7b70fc0
xda devdb mirror: http://forum.xda-developers.com/devdb/project/dl/?id=5948
MediaFire mirror: https://www.mediafire.com/?ld5pld43a3x2pr9
I've now tested Google Apps and everything seems to work fine, so I changed the OP to only have one link for them (what I would recommend using)
But the Play Store won't let you install Google Search (aka Google Now)
Awesome! Hoping you could get the camera working. This is quite exciting.
Sent from my Nexus 7 using Tapatalk 2
No way this is happening I gave this phone to my mom and she is not the biggest tech enthusiast but there are some things that just don't work with GB. You once again breath new life into this device. Thank you!
Sent from my Nexus 7 using Tapatalk
New build, snap snap
(sorry, hard to make "new build" original every time )
20140507 (May 7th, 2014):
Got camera working (all of it including timelapse no glitches either)
Added some extra encoder/decoder files - not sure if they are doing anything right now
Latest changes from CM (whatever that may be)
http://goo.gl/4YeJLa
e6c97b311bc3a32e1a17f0c199821f0b
xda devdb mirror: http://forum.xda-developers.com/devdb/project/dl/?id=6027
MediaFire mirror: https://www.mediafire.com/?f8tulxczubrzfcx
If you are updating from a previous build and the camera app doesn't appear, run this from terminal emulator or adb shell:
Code:
su
pm enable com.android.camera2/com.android.camera.CameraLauncher
Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk
Cosmo123 said:
Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I don't think it's possible because we don't have an arm v7 soc. The Aria is a v6, which is very old and most likely will never get updated. Though, Google now somewhat worked on the Aria when I was running CM9 (only contextual info). No voice features though.
You can try use the app Utter, which is similar to Google now in that it controls your phone via voice. I'm not sure if it works on our Arias.
Sent from my Nexus 7 using Tapatalk 2
kura808 said:
I don't think it's possible because we don't have an arm v7 soc. The Aria is a v6, which is very old and most likely will never get updated. Though, Google now somewhat worked on the Aria when I was running CM9 (only contextual info). No voice features though.
You can try use the app Utter, which is similar to Google now in that it controls your phone via voice. I'm not sure if it works on our Arias.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I didn't mean the voice functions of Google Now, just the app itself. So basically Google Search, Google Now cards and notifications.
Cosmo123 said:
Hey WinSuk, I know these are annoying questions, but Google Now is basically the only thing missing that's keeping me from installing this on my mom's phone. I understood your explanation about voice recognition and Google's libraries and am now wondering if that's the same reason Google Now isn't working. Do you think it will ever be possible to install Google Now? Thanks so much!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Just tried the newest Search app, and it works fine after you disable hotword detection : O
1. install Google Search app (I don't really want to distribute an apk myself, so here is a trustworthy source)
2. open it, and hit Yes, I'm in
3. let it crash
4. open Google Settings from the app drawer
5. navigate to Search & Now > Voice > "Ok Google" hotword detection
6. slide hotword detection to off
7. done, it works
I think ima add this to the OP...
Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2
kura808 said:
Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What do you think about symlinking the whole data partition to the SD card? Just an idea.
Could you do me a favor and take a few screenshots of the used storage and ram? Would also be interesting to know how much of the system partition is used/free. Thanks again
Sent from my Nexus 5 using Tapatalk
Cosmo123 said:
What do you think about symlinking the whole data partition to the SD card? Just an idea.
Could you do me a favor and take a few screenshots of the used storage and ram? Would also be interesting to know how much of the system partition is used/free. Thanks again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry but I don't know how to symlink it lol. Is that like how when we used to use darktremors a2sd mod?
So after installing 7 apps, I only got about 18mb of rom left lol. The amount of free ram is quite good though.
Sent from my LT30p using Tapatalk 2
kura808 said:
Just installed your ROM and it runs great!! Such a difference coming from your cm9 build. Quite impressed.
I was wondering if s2ext will work with this ROM? I understand kitkat broke the SD card support but our rom storage is quite small. I was only able to install a few apps before hitting the limited memory alert Lol. Are there any work arounds? =)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What app are you using?
I tried Link2SD, but it doesn't like the /sd-ext mount point... can be fixed by deleting /system/etc/init.d/05mountsd and rebooting.
Status bar loses transparency
fmshe said:
Status bar loses transparency
Click to expand...
Click to collapse
Read the first post?
WinSuk said:
Notes:
For a transparent status bar, enable high-end graphics in Performance settings
Click to expand...
Click to collapse
WinSuk said:
Read the first post?
Click to expand...
Click to collapse
thank you
The storage space is the most difficult part on this device right now...
Missing fonts for languages have been added, but even after stripping out the live wallpapers, it (and a few other changes) leaves just under 13MB free on /system... Google Apps takes up 26MB.
I'll be taking CMWallpapers out before the next release, but at 9.3MB - that isn't quite enough...
The newest recovery (6.0.4.8) also won't fit without stripping out everything that isn't needed (images, comments & linebreaks in files, etc).
We may have to start using custom partition sizes soon...
Another option is symlinking Google Apps to the /cache partition (40MB, mostly unused), like the gapps package I linked for 4.3
WinSuk said:
Another option is symlinking Google Apps to the /cache partition (40MB, mostly unused), like the gapps package I linked for 4.3
Click to expand...
Click to collapse
Are there any downsides to this? Isn't the cache partition just as fast etc?
Do you think your ROM is already usable as a daily driver? As I said I don't own the phone anymore and can only rely on the community before I install it for my mom.
Do you think ART will ever work? I think this phone would benefit from it greatly. Thanks
Sent from my Nexus 5 using Tapatalk
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
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
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13.x (T),which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
About Optimizations
Android Runtime
Disable debugging related features
Compile with D8 optimizations
Adjust watchdog timeout
Android Bionic
Sort host cache in-memory for performance
Switch to jemalloc memory allocator
msmset and pthread related changes
Android Build
Compile with ARMv8-2a-dotprod optimizations
Compile with O3
Compile with lse+fp16
Don't compress resources and assets
Use dexpropt speed
Increase heap size and use aapt2
... and sqlite, zlib related optimizations
Android Recovery
Allow installation of unverified zips i.e the most functional change ever
Android FWB
Reduce blur intensity to ease CPU/GPU
3 finger screenshot support (Please check under Gestures)
Added related missing permissions
SurfaceFlinger related optimizations
View/Layout optimizations
Android Telephony
Latest prebuilt APN from Stock
Updated CarrierConfigs from CAF
Additional cherry-picked IMS related fixes
Android System
Safetynet fixes
Improved Magisk evasion fixes
Disabling data for all connection interfaces and not just mobile data
Additional alarms and ringtones
Dialer
Allow auto-call recording as per country laws
UI changes
DocumentsUI
Start with Internal Storage instead of Downloads
Gallery2
Start with albums activity
Trebuchet
Allow double tap to sleep on homescreen
Updater
Allow local update feature
About Issues
MotoCamera's night mode doesn't work correctly (same as LineageOS), replaced by Aperture, use GCam if needed. MotCamera4 fixed thanks to Marc
NR only mode (5G only mode) works with Jio only. For using 5G on other ISP, use NR/LTE or any other bands, during heavy network traffic, it switches to 5G and fallbacks to 4G during power save automatically
Downloads Links
LineageOS 20.x (Unlocked Bootloader) :Link : https://drive.google.com/drive/folders/1wXGs7pitUvOCETdCHjVsvpVD3iilbiNl?usp=share_linkGoogle Applications :Not required (has inbuilt minimal set of Google Applications including SetupWizard)Flashing and updatingLineageOS clean install :- (Optional) Flash the boot.img recovery from the ROM zip with Fastboot- (Optional) Wipe the data & cache (Backup to make sure not to loose data)- Flash the LineageOS ROM zip from the Recovery- Reboot to recovery again- (Optional) Every additional zip you want to flash like Magisk- Reboot to systemLineageOS Update using "Local Update" feature :- You need to be on an existing ROM developed by me- Download the ZIP from download link above and storage in local storage (example Downloads folder)- Go to Settings -> System -> Updater- Click 3-dot buttons and select Local update- Select the zip using File Manager- Let it update (takes some time)- RebootIssues and reports- Report issues only if you are using the ROM kernel- If an additional mod is installed, make sure it's unrelated, and mention it- Make sure the issue wasn't discussed earlier in the threads- Share a log of the error with CatLog for example- Make sure you also tell the ROM version you're using
XDA:DevDB Information
[ROM][13.0][OPTIMIZED] LineageOS 20 for Moto Edge 30
Contributors
Daedroza, Albert
Source Code: https://github.com/daedroza
ROM OS Version: 13.x Android T
ROM Kernel: Linux 5.4.x
Version Information
Status: Stable
Created 2023-01-26
Last Updated 2023-01-26
Changelog (You can use updater to update from local storage)
Android 13 Blobs + Android 13
June 25, 2023
Sync with June security patches
Added MotCamera4
Added Android 13 blobs
Updated system wide ad block hosts
Android 12 Blobs + Android 13
May 15, 2023
Sync with May security patches
Added Dolby support
Minimal ad block (system-wide, all apps)
April 18, 2023
Sync with April security pathces
Even more aggressive battery optimizations
Wifi optimizations (2.4GHz bonding)
More fluidity at 60HZ
March 27, 2023
Hot-fix for 5G Networks
Enabled 5G by default if supported
Enabled 5G Voice over Network (VoNR)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Thanks for your response!
I've picked "most" of the patches across different ROMs but there might be one or two missing. For time being, you can use Magisk and Zygisk to hide your relevant apps.
For me, using Magisk + Zygisk Hide on Google Play Store gave certified status which is good enough for me. At the moment, I am using ProtonAOSP's related patches (mostly with exception for others) for SafetyNet from Android 12 but it seems Android 13 is bit different. I will take a look into it however I am sure you can get it done easily using Magisk + Zygisk combo for time being.
EDIT: Magisk fixed. Please use builds after 18th February!
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff included?
alekksander said:
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff inincluded
Click to expand...
Click to collapse
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
profound answer. thank You.
Daedroza said:
I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
Click to expand...
Click to collapse
does it mean no plans to release g'less variant?
Daedroza said:
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
Click to expand...
Click to collapse
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
alekksander said:
profound answer. thank You.
does it mean no plans to release g'less variant?
Click to expand...
Click to collapse
No plans as such. Building Android 13 is already very costly for me with these optimizations. Building it twice once with and without is something I am not looking forward to simply because of my constrained resources. I do a lot of building outside Lineage too, so simply cannot waste my SSD read/write cycles. Secondly, I already shipped first version with those services built-in. Removing those in next update will cause a lot of problems and could be fixed with clean flash only.
JorgeTone said:
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
Click to expand...
Click to collapse
MindTheGapps is a more complete Google services package which includes accessibility and few other components. My minimal built-in package doesn't include those. If you require accessibility services, my recommendation is to use official Lineage with MindTheGapps.
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
alekksander said:
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
Click to expand...
Click to collapse
The UDFPS implementation is same as official build, no difference whatsoever except that my build has slightly more screen flashes because the UDFPS implementation doesn't support multi rect correctly. A workaround is present in official build that causes more battery life to be consumed.
For now that workaround is reverted in my build because I'm trying to understand how far it's effect is on battery life.
I don't think you will even notice it if you use 90HZ+ or more as default.
EDIT: Reverted to original Lineage implementation on new release!
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Daedroza said:
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Click to expand...
Click to collapse
Thank you. Amazing work. Works like a charm, just as you said. Passed the CTS test straight away. BTW I am not using Magisk to begin with so have nothing to do on that front. Cheers mate. Thanks.
Daedroza said:
Changelog (You can use updater to update from local storage)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Click to expand...
Click to collapse
Hi, thanks for this build.
March 27 changelog ?
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Roonicks said:
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Click to expand...
Click to collapse
Check in display dark theme and there is a menu there
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
aslam2121 said:
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
Click to expand...
Click to collapse
You can use Battery Manager to detect applications that are sucking battery life or just check Battery Usage graph. Usually few applications hold some wakelock to perform activities in the background which usually ends up being the culprit. My recommendation is to disable applications running in background and disable background mobile data usage.
If you have done clean install, I recommend waiting for cache to build which generally takes time if you have lots of applications.
@aslam2121 : Check with new April build, there are more battery optimizations which reduces random wakelocks.
Thanks for this awesome ROM, any chance to add Dolby Atmos? (Without rooting the phone)
Where to get the boot image? And can I flash magisk zip directly from recovery?