{
"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"
}
Code:
/*
* Disclaimer
*
* 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.
*/
Introduction
LineageOS 11 is a free, community built, aftermarket firmware distribution of Android 4.4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit their Gerrit Code Review.
Aims
This ROM is created with the purpose of kick-starting some development to make our Nexus Q's useful again. The newest working ROMs for this device were from 2014 and CM11 based. These are now very outdated and needed security patches to be safe to use and so I have built a new ROM from the latest LineageOS 11 sources.
Once this ROM has been optimised for the Nexus Q a little further, I shall explore altering the interface for TV and Desktop editions to make the device more useful. I may also attempt to port newer Android versions (5.0+) in the future so we can get a full Android TV experience on this device and compatibility with newer apps.
Features
Improved LED support
Stock Nexus Q boot animation (see #4 for preview)
Standard CM11/Lineage OS 11 features
More Steelhead-specific tweaks & additions coming soon....
Working
WiFi
Bluetooth
NFC
HW Acceleration
HDMI Output
Audio
Volume Control
Capacitive sensor
LED Ring (Limited functions)
Optical out (simultaneous output with HDMI audio)
ART Runtime (you can switch from Dalvik in Dev Settings)
Not Working
Amplifier
Audio output switching
You tell me!
Installation
Connect Nexus Q to PC via USB
Enter bootloader: Connect power and once blue light has illuminated, quickly place hand over Nexus Q. LED will turn red.
Boot into recovery mode:
Code:
fastboot boot recovery.img
Wipe /system and then factory reset to wipe /data & /cache
Select "Install zip" and then "Install zip from sideload".
From your PC, sideload with ADB:
Code:
adb sideload lineage-11-20180228-UNOFFICIAL-steelhead.zip
Sideload Gapps in the same fashion (if desired)
Reboot (be patient first boot can take some time!)
Enjoy!
Changelog
Code:
* 28-02-2018: Restored default Google boot animation from stock image
* 23-02-2018: Enabled LED control when display is on
* 22-02-2018: Initial Release
Downloads
ROM: lineage-11-20180228-UNOFFICIAL-steelhead.zip
Recovery: recovery.img
Gapps (Optional): Open Gapps (4.4, Nano)
Download Mirror: AndroidFileHost.com
Thanks To
Code:
* CyanogenMod / Lineage OS contributors
* hharte (for his prior work on the Nexus Q)
* Matthew Kovnesky (for reminding me about my promises to work on the Nexus Q!)
XDA:DevDB Information
Lineage OS 11 ROM for Nexus Q (Steelhead), ROM for the Nexus Q
Contributors
wollac11
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2018-02-28
Created 2018-02-22
Last Updated 2018-02-28
Reserved
New build! (02/23) - Additional LED Ring Control
XDA isn't letting me upload new files at the moment as it keeps producing errors building checksums and so I've given up and started hosting new builds on AndroidFileHost until they fix it. Once XDA have sorted the issues then I'll try to upload them here (as well as using AFH as a mirror) but for now any new uploads will just be on the latter.
Anyway, in this new build (20180223) I have improved LED ring functionality by modifying the Android notification framework so that the notification light can be changed by apps even with the display on. In theory it is now very easy to control the LED as we like since it can be used like any a phones notification LED but without the screen off limitation.
At some point I might try to develop an app which syncs the LED to music or something cool but in the meantime if anyone else fancies having a go at something like that then please do as you will now be able to without using any Nexus-Q specific APIs.
You can test this new functionality using an app like LightFlow from the Play Store which can set custom notification colours for any app and you'll see the LED ring change.
I also made a quick demo of cycling between colours which you can see a video of here: https://plus.google.com/+CharlieCallow/posts/WAfcBmg7MYF.
The built-in The CyanogenMod/Linage LED control still seems to be a bit flaky but it's fine with third-party apps which have LED settings (like Lightflow).
Anyway you can download the new build from below. If you are upgrading from the first build just flash this one over the top and wipe /cache & davlik cache.
Download: lineage-11-20180223-UNOFFICIAL-steelhead.zip
New build! (02/28) - Original Nexus Q Bootanimation
A tiny new update from the last build. This one swaps out the Lineage OS boot animation for Google's original boot animation from the Nexus Q stock system image.
Also, XDA seems to have fixed the file upload issue so the latest version is uploaded here again but I'll upload to AndroidFileHost shortly a link it as a mirror.
Download: lineage-11-20180228-UNOFFICIAL-steelhead.zip
Preview:
wollac11 said:
A tiny new update from the last build. This one swaps out the Lineage OS boot animation for Google's original boot animation from the Nexus Q stock system image.
Also, XDA seems to have fixed the file upload issue so the latest version is uploaded here again but I'll upload to AndroidFileHost shortly a link it as a mirror.
Download: lineage-11-20180228-UNOFFICIAL-steelhead.zip
Preview:
Click to expand...
Click to collapse
Could you upload it to androidfilehost ???
svemat said:
Could you upload it to androidfilehost ???
Click to expand...
Click to collapse
Sure, it's up on AndroidFileHost now: https://androidfilehost.com/?fid=962187416754466172. I've also added a link to the Nexus Q page on my AndroidFileHost.com developer profile to the OP as a download mirror for all of the files posted.
Development update
So, good news: I think I have the a build which should support the amplifier, HDMI audio and optical output in the same ROM.
Bad news: My Nexus Q seems to have given up the ghost! It seems the Micro HDMI port has failed. I can't get a signal out of it no matter what I boot regardless of the display I connect to. I hoped it might be the cable but I tested with a spare cable I had lying about and still no joy! This could mean the end of this little project as I can't procure another Nexus Q here in the UK and I can't really do this without a working unit! :crying:
I've ordered a brand new Micro HDMI cable to test for certain but it's not looking good! I'll keep everyone updated.
wollac11 said:
So, good news: I think I have the a build which should support the amplifier, HDMI audio and optical output in the same ROM.
Bad news: My Nexus Q seems to have given up the ghost! It seems the Micro HDMI port has failed. I can't get a signal out of it no matter what I boot regardless of the display I connect to. I hoped it might be the cable but I tested with a spare cable I had lying about and still no joy! This could mean the end of this little project as I can't procure another Nexus Q here in the UK and I can't really do this without a working unit! :crying:
I've ordered a brand new Micro HDMI cable to test for certain but it's not looking good! I'll keep everyone updated.
Click to expand...
Click to collapse
Did you check on IFIXIT the replace the Brocken piece? Really sorry to hear.
svemat said:
Did you check on IFIXIT the replace the Brocken piece? Really sorry to hear.
Click to expand...
Click to collapse
It's not likely to be easy to repair if that connector is broken and parts will be hard to come by. I'll wait for the new cable and see how that goes first.
In the meantime, I have managed to test my new build by connecting to the Nexus Q via Vysor as a workaround to see what's going on. While autoswitching still doesn't work yet, the amplifier now does work and so I'll be posting a separate amp build soon for those who want to use the amp instead of audio over HDMI or TOSLINK.
I am also hoping at some point to add A2DP sink support so that the Nexus Q can be used as a bluetooth receiver. That would be particularly handy with the amp build for people who want to add bluetooth to a set of bookshelf speakers.
Keep up the great work, recently dusted off my Q and this looks promising, would love if we could have simultaneous Bluetooth output but unsure if the hardware supports it. Do hope we can get an auto audio switching feature or a togglable setting to switch audio outs.
Thank you soooooooo much! I can't believe there are somebody still remembering Nexus Q.:good:
Any update on the build with amplifier support?
xthing said:
Any update on the build with amplifier support?
Click to expand...
Click to collapse
Sorry, this project got sidelined when I had issues with my Nexus Q's HDMI port. I got it mostly working again for now but I've since been very busy with work & other projects. I hope to pick this up again late August / early September. In the meantime I'll try to dig out the existing build I have with working amplifier support as I've had a few requests for it!
wollac11 said:
Sorry, this project got sidelined when I had issues with my Nexus Q's HDMI port. I got it mostly working again for now but I've since been very busy with work & other projects. I hope to pick this up again late August / early September. In the meantime I'll try to dig out the existing build I have with working amplifier support as I've had a few requests for it!
Click to expand...
Click to collapse
Awesome, looking forward to it!!
Install
Install appfull
Install
wollac11 said:
Sorry, this project got sidelined when I had issues with my Nexus Q's HDMI port. I got it mostly working again for now but I've since been very busy with work & other projects. I hope to pick this up again late August / early September. In the meantime I'll try to dig out the existing build I have with working amplifier support as I've had a few requests for it!
Click to expand...
Click to collapse
Please pick it up again! I've just done my occasional forlorn search for Nexus Q goodies and had a brief burst of hope. I recently got a Google Glass for the price of a curry which has renewed my interest in the old Google gear, my ideal situation would be the Nexus Q acting as a Cast target with working LEDs and amplifier, that's all I would want. I have it running on an old Cyanogen install but that's not exactly functional.
Just stumbled upon my old paperweight, the Nexus Q and decided to look around before finally tossing it - glad I did! I am looking forward to trying this out this week. Hopefully the amp will work (and some pretty LEDs) as this was my player for my outdoor stereo.
Anyway thanks for reviving my hopes!
So I dusted off the Q ball and plugged it in to give it a shot and I got an issue when upon rebooting into the bootloader screen. I cover the Q, it flashes and turns red, then nothing. If I cover it again, it spins blue LEDs and I am prompted with the following:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT BE UNDONE"
Then i get the following choice:
"No"
"Yes -Disable recovery flash"
"Go Back" - which just reboots it again.
At the bottom it says "ClockworkMod Recovery v6.0.3.1, Formatting /data... Formatting /cache..."
Which should I select to upgrade to this to the LineageOS? I remember there being issues with these getting bricked so I just wanted to double check.
Also, what program do I use for fastboot? Is there a link - its been too long!
Thanks for the help.
Related
Disclaimer:
Code:
All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking your device.
{
"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"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application; with this, you can host your unofficial MoKee builds on our server!
Features:
Odexed for faster performance (only in official releases, nightlies are deodexed)
Incremental updates
OTA updates - update on the fly!
Native exFAT support (Samsung devices only)
ListView animations
Multi window
Calendar - with lunar and solar calenders
Lunar calendar in lock screen
Task switching sidebar in recent apps (the list will increase if you install supported apps)
Bulk SMS recipients
Adjustable SMS font size
SMS sending delay
Smart dialing
Speed dialing
IP dialing
Custom carrier name
Network speed in status bar (upload and download!)
Built in timer in Apollo - determine when to stop playing music
MoKee Setup Wizard
Active Display
Adjustable navigation bar height
Unique Power Saver functions!
Custom screen off animations
** Not yet merged
PIE control
Auto hide status bar
Smart capture
Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Multi-window:
Screen Off Animations:
Scale down:
Fade out:
Unique features:
Feature-rich settings:
Links:
Official Site:
http://www.mokeedev.com/en
Google Plus Community (join us for faster response!):
https://plus.google.com/communities/112433388317801966872
Statistics:
http://stats.mokeedev.com
Nightly Build Status:
http://build.mokeedev.com
Bug Tracker:
http://issues.mokeedev.com
Changelog:
http://changelog.mokeedev.com
GitHub:
http://github.com/MoKee
Kernel Sources:
https://github.com/MoKee/android_kernel_bn_omap
Code Review:
http://review.mfunz.com
Final Release:
http://rom.mk/?device=hummingbird&type=history
http://rom.mk/?device=ovation&type=history
MoKee Gapps (full list):
http://www.androidfilehost.com/?w=files&flid=11492
Installation Instructions:
1. Wipe data/factory reset
2. Format /system
3. Flash ROM
4. Flash MoKee Gapps
5. Reboot
Donations:
All donations will be used for bandwidth, you can see the current bandwidth usage here:
http://traffic.mokeedev.com
Current rate is 6TB per/month, extra at USD0.02/GB
So yea, show some "MoKee lurve" here:
http://www.mokeedev.com/en/donations
Credits:
- MoKee Developers: https://github.com/orgs/MoKee/members
- CyanogenMod
- AOSP
- Koush for open-sourced SuperUser
- Slim Roms
- OmniROM
- @omkarsathe92 for the videos!
XDA:DevDB Information
MoKee OpenSource Project, ROM for the Barnes & Noble Nook HD, HD
Contributors
martincz, Ryuinferno
Source Code: https://github.com/MoKee
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-24
Last Updated 2015-07-29
set_metadata_recursive: some changes failed
status 7 error
looks like I can't install it, 140531 Release.
What recovery should be used?
Thanks
antebr said:
What recovery should be used?
Thanks
Click to expand...
Click to collapse
Use the one from CM11 thread.
Thanks for the wonderful ROM
Cool boot animation :good:
Flashed the latest nightly. Booted up fine. But for some reason the keyboard wouldnt show up while registering the tablet. Probably fault with Gapps package? I dont know. So I skipped tablet registeration. Navigation bar was disabled, so I enabled it through settings (Buttons>enable on-screen nav bar). Pretty much like CM but has special features like Active Display, Short Cut bar ( which shows up in recent apps), list view animation, Split view. We can also "lock apps" in the recents menu which prevents it from being cleared away.
But got " Unfortunately, Google Keyboard has stopped" error all the time and I couldnt type anything.
IMO this would get more users if this was posted in the "Android Development" forum.
EDIT: Hmm it seema the problem is gapps package in GENERAL. Weird. Tried both PA gapps and the one from cyanogenmod site. Both cases force closes and keyboard unable to open. Went on and did a fresh install without any gapps package and had no crashes and the keyboard worked as well. But for me its pretty useless without Play Store.
adwait.bhandari said:
Use the one from CM11 thread.
Thanks for the wonderful ROM
Cool boot animation :good:
Flashed the latest nightly. Booted up fine. But for some reason the keyboard wouldnt show up while registering the tablet. Probably fault with Gapps package? I dont know. So I skipped tablet registeration. Navigation bar was disabled, so I enabled it through settings (Buttons>enable on-screen nav bar). Pretty much like CM but has special features like Active Display, Short Cut bar ( which shows up in recent apps), list view animation, Split view. We can also "lock apps" in the recents menu which prevents it from being cleared away.
But got " Unfortunately, Google Keyboard has stopped" error all the time and I couldnt type anything.
IMO this would get more users if this was posted in the "Android Development" forum.
Click to expand...
Click to collapse
Just a heads up; you can change your boot logo using the rom toolbox app.
@martincz
Thanks for building Mokee for the Nook HD/HD+!
I haven't had the chance to check everything but so far it looks pretty nice. However, I have Ovation and the build has an incorrect storage_list.xml in framework-res.apk. It appears to be a generic storage_list and not for our devices.
I flashed the latest nightly but upon checking the release build, it also has the same incorrect storage list. Of course with this incorrect file, storage in settings does not read sdcard1 and a file manager is unable to find it as well. Additionally, when connected to a PC the device just comes up blank. I just took a look at the Hummingbird build and it also has the incorrect storage_list.xml.
I've attached a file below containing the correct storage_list.xml for our devices.
https://www.dropbox.com/s/dq0ayclmfvndbk0/storage.zip
Btw, I flashed the latest Mokee gapps listed in the OP and had no problem with the keyboard came right up and away I went.
Thanks again and I'm hoping you can get this squared away. Also, as mentioned in an above post, I think this would get more exposure in the "regular" Android development. This "original" forum has always been kind of a dead area in the Nook forum.
Mike T
webdroidmt said:
@martincz
Thanks for building Mokee for the Nook HD/HD+!
I haven't had the chance to check everything but so far it looks pretty nice. However, I have Ovation and the build has an incorrect storage_list.xml in framework-res.apk. It appears to be a generic storage_list and not for our devices.
I flashed the latest nightly but upon checking the release build, it also has the same incorrect storage list. Of course with this incorrect file, storage in settings does not read sdcard1 and a file manager is unable to find it as well. Additionally, when connected to a PC the device just comes up blank. I just took a look at the Hummingbird build and it also has the incorrect storage_list.xml.
I've attached a file below containing the correct storage_list.xml for our devices.
https://www.dropbox.com/s/dq0ayclmfvndbk0/storage.zip
Btw, I flashed the latest Mokee gapps listed in the OP and had no problem with the keyboard came right up and away I went.
Thanks again and I'm hoping you can get this squared away. Also, as mentioned in an above post, I think this would get more exposure in the "regular" Android development. This "original" forum has always been kind of a dead area in the Nook forum.
Mike T
Click to expand...
Click to collapse
Ow snap! That's what the problem was . I should have read the OP more carefully regarding the GAPPS. I had totally freaked out when I saw that the storage was not accessible. I thought it was only with mine.
Excited to see this. Once pie control is ready I'm all over this.
Sent from my Nexus 5
adwait.bhandari said:
Ow snap! That's what the problem was . I should have read the OP more carefully regarding the GAPPS. I had totally freaked out when I saw that the storage was not accessible. I thought it was only with mine.
Click to expand...
Click to collapse
Same thing happened to me yesterday lol. Flashed this rom and then wondered why I couldn't download anything. I freaked out and flashed back to CM.
Sent from my SPH-L710 using Tapatalk
Where does one put the new strafed file?
Sent from my PC36100 using xda app-developers app
jpisini said:
Where does one put the new strafed file?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Don't know if "strafed" is just a typo, or you are talking about the correct storage_list.xml file I referenced above??? If you are talking about the storage_list file, it pretty much has to be compiled in the build. I just attached that file so that the dev could see the difference between his framework compiled in the build and the correct one.
It is contained in the framework-res.apk in /system/framework of the rom. If someone has experience with apktool, (requires java) it can also most likely be edited. Unfortunately, with my limited experience I tried and could not get it to work.
Btw, downloaded the latest nightly and it still has not been corrected. From the looks of it, the dev hasn't been active on XDA since he posted this here. He may end up being another in a long string of disappearing devs in the Nook HD forum.
Mike T
OK thanks my phone changed storage to strafed and I didn't notice.
Sent from my PC36100 using xda app-developers app
I tried the latest stable build this morning it still can't see the sdcard.
-------------
Tried inserting the file in before flashing no luck same errors.Unfortunately not my area. I have tried building from source and just can't seem to get it straight.
It's already fixed, try the next RELEASE version, or go for the nightlies
Will do so sometime this week thanks. It does look pretty cool the little bit I did play with it.
Sent from my SPH-L900 using XDA Free mobile app
New version is much nicer and it does see the sdcards. No FCs yet either. So far I am enjoying it.
Never mind had to format my nook as it overheated just playing with settings. Shame I really like the look and feel.
Sent from my SPH-L900 using XDA Free mobile app
Running the latest mokee on my HD+. Very nice experience. Android version is 4.4.4. It does overheat a bit.
I'd just like to say thank you to the Mokee team.
I've been on Cyanogenmod nightly's for ages but switching to this (01\09\14 nightly) has invigorated my tablet.....So much quicker and fluid than before....
Might even give it a spin on my Oneplus One ?
Thanks again.
Sent from my BN NookHD+ using XDA Free mobile app
Is overheating still an issue? I'd love to give this a try but as everything "works" on my current ROM (albeit slowly) I'm a bit hesitant to try this, overheating is important to me since I read a lot on my tablet.
kingKANG
by bracketslash
{
"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"
}
Goal: Provide a similar CyanogenMod and AOKP experience which I enjoy to others with the same taste
Methodology: Build CyanogenMod (latest version) locally and cherry-pick unmerged revisions so that we may have the best of the future right now. AOKP will be built straight from nightly source.
Reasoning: It's silly to wait for the next new thing...With CyanogenMod's Gerrit code review, I've found it to be nice to able to pick-and-choose things that seem beneficial.
Release Type Update 08262014
I have now listed the URL to get onto Google Drive where my buildbot automatically uploads to once finished building. These are not tested, as I can't flash a new ROM every day. However, they are a nightly build catching you up to CM11, plus whatever cherry-picks I talked about previously...This means that previous cherry-picks are maintained even throughout the nightly builds.
Second Release Cherry-Picks 08202014 [discussion begins HERE]:
Add an option in the InCall UI to perform call recording
Change-Id: Icc86a0a7ae9d2493a837d02f321df7cb1387cded
cmhw: add tap to wake tunable
Change-Id: I82c913ceee0b23e2ab1e8261b36123cac898d589
m8: Increase the volume step at which the safe volume warning shows
Currently the warning shows up at less than half volume, at normal
listening volume. This bumps it up a bit.
Change-Id: Ie85bb036f75a55b2eb6d1802baba11e632c19908
GPE IR hal implementation. Ported from M7 work.
Using SmartRemote app, the standard in user IR remote apps, it was
confirmed IR code recored fails using AOSP IR hal implementation.
Using the GPE HTC IR hal, with associated resources, blast as well
as record works. There appears to be no conflicts having both
implementations on the device at the same time.
Change-Id: I2a97112a977d98ef601ce4e0f3922f3f7cd5e680
m8: switch to 400 density
Change-Id: I09f7bbe802c9ac7b6d7ad9dc1295b494b31f39d0
Old Builds
Initial Release Cherry-Picks 08192014:
cmhw: add tap to wake tunable
Change-Id: I82c913ceee0b23e2ab1e8261b36123cac898d589
m8: Increase the volume step at which the safe volume warning shows
Currently the warning shows up at less than half volume, at normal
listening volume. This bumps it up a bit.
Change-Id: Ie85bb036f75a55b2eb6d1802baba11e632c19908
GPE IR hal implementation. Ported from M7 work.
Using SmartRemote app, the standard in user IR remote apps, it was
confirmed IR code recored fails using AOSP IR hal implementation.
Using the GPE HTC IR hal, with associated resources, blast as well
as record works. There appears to be no conflicts having both
implementations on the device at the same time.
Change-Id: I2a97112a977d98ef601ce4e0f3922f3f7cd5e680
m8: switch to 400 density
Change-Id: I09f7bbe802c9ac7b6d7ad9dc1295b494b31f39d0
While I do build these locally, I'm not an expert by any means. You are responsible for everything by downloading and installing this ROM. I am not liable for anything related to the installation, etc.
Installation:
Boot to recovery
IF COMING FROM A DIFFERENT ROM: Full Wipe (Dalvik Cache, System, Cache, Data)
IN GENERAL, IF COMING FROM A PREVIOUS VERSION OF THIS ROM: No wipe required (Dalvik Cache and Cache wipe recommended after installation)
if you have any errors, it is recommended to perform a Full Wipe and then try again
Install kingKANG ZIP
Optional: Install Google Apps
Wipe Dalvik Cache/Cache
Reboot, wait for it to load completely
Reboot again, because hey, why not?
Download:
XDA DevDB CM Download
Android File Host CM Download
Android File Sharing CM Download
MD5sum: Android File Host MD5sum generated during the build process
[*]Nightlies: Google Drive FOR CM AND AOKP [these are built nightly after 12:00AM and take roughly 25 minutes to build each, then they are automatically uploaded to Google Drive]
Nightly file formats:
CM: cm-11-YYYYMMDD-UNOFFICIAL-HHmm-m8.zip and .md5sum
AOKP: aokp_m8_kitkat_unofficial_YYYY-MM-DD.zip and .md5sum
You want to download the one with the newest datestamp AND hourstamp on it.
Make sure to download Google Apps (the latest):
Google Apps
FOREWARNING: Call recording without consent, or recording at all may be illegal in your country. I am not liable for what you do with this feature or anything that happens due to this feature being enabled. You are using it at your own will and discretion.
Thank you to CyanogenMod and its community as well as AOKP's community for the opportunity.
Thank you to XDA and the community for allowing me here.
Thank you to HTC, Google, and all other hardware/software sponsors for the environment with which we work in!
If you have any issues, please report, but do note that this is largely just CM11 and AOKP respectively with several cherry-picks to fit to my liking.
If mods have any issues, please contact me!
XDA:DevDB Information
kingKANG, ROM for the Verizon HTC One (M8)
Contributors
bracketslash
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod & AOKP
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2014-08-19
Beta Release Date: 2014-08-19
Created 2014-08-20
Last Updated 2014-08-29
Thanks!
Any chance you can cherry pick the Call Recording feature?
http://review.cyanogenmod.org/#/c/69850/
paulg1981 said:
Thanks!
Click to expand...
Click to collapse
No problem, enjoy!
krazie1 said:
Any chance you can cherry pick the Phone Recorder feature?
Click to expand...
Click to collapse
Sure, I can give it a shot. From which ROM? Pretty sure it will have to be a source-based ROM.
bracketslash said:
No problem, enjoy!
Sure, I can give it a shot. From which ROM? Pretty sure it will have to be a source-based ROM.
Click to expand...
Click to collapse
Its from CM, they just didn't make it official I added the link to it in my last post.
krazie1 said:
Its from CM, they just didn't make it official I added the link to it in my last post.
Click to expand...
Click to collapse
I have it cooking up right now. Not sure if it will work, they seem a little dicey about it in the comments (having "fixes" for it and such...but I will try it!)
EDIT: Also, I'm a weirdo about ETAs...I love it when people give ETAs, but realize that I work 45hrs/wk and I am also a full-time student...Real life comes first, but I still love you guys.
EDIT2: The feature requested is in a broken status...They can't get everything to work with it, so I'll wait for a more finished one before picking it.
bracketslash said:
I have it cooking up right now. Not sure if it will work, they seem a little dicey about it in the comments (having "fixes" for it and such...but I will try it!)
EDIT: Also, I'm a weirdo about ETAs...I love it when people give ETAs, but realize that I work 45hrs/wk and I am also a full-time student...Real life comes first, but I still love you guys.
EDIT2: The feature requested is in a broken status...They can't get everything to work with it, so I'll wait for a more finished one before picking it.
Click to expand...
Click to collapse
You be the Man Thank you!!!!
I remember there being an issue with the speaker phone mic not working correctly. Is this issue resolved here? Just curious.
trill12 said:
I remember there being an issue with the speaker phone mic not working correctly. Is this issue resolved here? Just curious.
Click to expand...
Click to collapse
I believe it has been.
Sent from my HTC One_M8 using Tapatalk
trill12 said:
I remember there being an issue with the speaker phone mic not working correctly. Is this issue resolved here? Just curious.
Click to expand...
Click to collapse
buckmarble said:
I believe it has been.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The speaker phone microphone works afaik but the speaker phone part does not. That's what I've found in my own testing. I haven't seen anything come up in Gerrit, so maybe it is just me having that issue.
bracketslash said:
The speaker phone microphone works afaik but the speaker phone part does not. That's what I've found in my own testing. I haven't seen anything come up in Gerrit, so maybe it is just me having that issue.
Click to expand...
Click to collapse
Last I saw the speakerphone issue was fixed in the device tree in the sound configuration xmls. But if its anything like it was on the m7, its intermittent. Sometimes a reboot would bring it back. It was a frustrating issue.
Sent from my HTC One_M8 using Tapatalk
buckmarble said:
Last I saw the speakerphone issue was fixed in the device tree in the sound configuration xmls. But if its anything like it was on the m7, its intermittent. Sometimes a reboot would bring it back. It was a frustrating issue.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Speakerphone has been officially fixed since 7/30 Nightly, you can hear the person and they can hear you
krazie1 said:
Its from CM, they just didn't make it official I added the link to it in my last post.
Click to expand...
Click to collapse
I built it and had to undo all of the blocks that they had for it. Uploading right now.
FOREWARNING: Call recording without consent, or recording at all may be illegal in your country. I am not liable for what you do with this feature or anything that happens due to this feature being enabled. You are using it at your own will and discretion.
bracketslash said:
I built it and had to undo all of the blocks that they had for it. Uploading right now.
FOREWARNING: Call recording without consent, or recording at all may be illegal in your country. I am not liable for what you do with this feature or anything that happens due to this feature being enabled. You are using it at your own will and discretion.
Click to expand...
Click to collapse
Hey Does HDMI work with audio?
young0ne said:
Hey Does HDMI work with audio?
Click to expand...
Click to collapse
I'm really not sure! The only response that I can think of is that if it works in the latest CyanogenMod 11 nightly that it will work here as well. Try it and see?
Thanks!
Second Release Cherry-Picks 08202014:
Add an option in the InCall UI to perform call recording
Change-Id: Icc86a0a7ae9d2493a837d02f321df7cb1387cded
cmhw: add tap to wake tunable
Change-Id: I82c913ceee0b23e2ab1e8261b36123cac898d589
m8: Increase the volume step at which the safe volume warning shows
Currently the warning shows up at less than half volume, at normal
listening volume. This bumps it up a bit.
Change-Id: Ie85bb036f75a55b2eb6d1802baba11e632c19908
GPE IR hal implementation. Ported from M7 work.
Using SmartRemote app, the standard in user IR remote apps, it was
confirmed IR code recored fails using AOSP IR hal implementation.
Using the GPE HTC IR hal, with associated resources, blast as well
as record works. There appears to be no conflicts having both
implementations on the device at the same time.
Change-Id: I2a97112a977d98ef601ce4e0f3922f3f7cd5e680
m8: switch to 400 density
Change-Id: I09f7bbe802c9ac7b6d7ad9dc1295b494b31f39d0
bracketslash said:
I'm really not sure! The only response that I can think of is that if it works in the latest CyanogenMod 11 nightly that it will work here as well. Try it and see?
Thanks!
Click to expand...
Click to collapse
It works great this is a Daily Rom for me cuz everything I use works great.
Glad to hear it! Thank you.
Sent from my One M8 using XDA Free mobile app
bracketslash said:
Glad to hear it! Thank you.
Sent from my One M8 using XDA Free mobile app
Click to expand...
Click to collapse
have a question for you in the future will you make a Or add some Android L features to the rom
young0ne said:
have a question for you in the future will you make a Or add some Android L features to the rom
Click to expand...
Click to collapse
I don't think that much has been released on our side for Android L...I will look into it, though. I do have plans to contact some developers for inclusion of their apps.
{
"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"
}
INSTALLATION
* Download ROM and the latest GAPPs (Pico).
* Full wipe and format is ALWAYS suggested to avoid odd issues.
* Flash ROM, GAPPs.
* SUPERSU INSTALLATION
* Wipe cache & dalvik cache
* Reboot
Cyanogenmod Apps (C-Apps)
OMNISWITCH FLASHABLE ZIP
Stock Apps (from Tate's CyanogenMod builds)
Browser
Gello Browser
Music (Eleven)
Calendar
ExactCalculator
CREDITS
@monster1612 @Hashcode @transi1
Contributors:
@alexander_32
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.101+; 3.0.72+
Status: Release Candidate
Current Version: MOB31K
SOURCE
local_manifest
tate
bowser-common
omap4-common
kernel
proprietary
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
DISCLAIMER:
Code:
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.
KNOWN ISSUES
You tell me
For Google Calendar: Just install the apk file and update the app in Google Play
TWRP BUILDS
Created 2016-10-17
Last Updated 2017-01-30
Last build was made using @r3t3ch ' s (THIS TOXIC TEENAGER IS NOT WELCOMED HERE AND MY OTHER THREADS) repositories. You'll not see his builds anymore
I still facing with youtube issues. Any idea to solve it?
fauner said:
I still facing with youtube issues. Any idea to solve it?
Click to expand...
Click to collapse
Yes, I know where it is. But you need to wait some time. I have other projects. Sorry. It's all about not enough time and financial resources. You can try other my other MM releases. Especially BeanStalk and Temasek's CM13. Try what works best for you.
Plans have changed. I'll bring a SNAPSHOT build soon, with necessary fixes.
Fantastic Alexander
NEW SNAPSHOT BUILD
https://www.androidfilehost.com/?fid=385035244224386332
Installation: Full wipe/Flash ROM + OpenGApps
You can use this build for now. I need to do more corrections, so I'll bring my best version soon and will delete this one later.
What will be changed in the future release:
1. Snap video recording will be corrected (not a big deal, you can successfully use Open Camera for that)
2. I'll remove some system apps, (like stock browser) and post it here, so if you really need it, you can just download apk files and install it as user apps. (This is for improving performance)
3. I'll remove screen blinks (Am I only one who see it? Let me know, leaving a comment)
Previous build made by rata** (r3t3ch) was removed. I want to emphasize he made that build. His toxic behavior and manner of talking speak for itself. Clearly, he's not an adult human being. He doesn't want to admit his mistakes, thinks he's a center of the universe, knows everything and poops in the brain if you just trying to help him. This is unacceptable and I will not stand such a toxic behavior.
What's new:
1. You can normally watch YouTube now (no patchy sound, it was easier than I thought)
2. Stock browser was replaced with Gello browser (already regret about it, the size is too big. Though it works)
If you'll find something not working, leave a comment here, I'll check it and if I'll not find it - shame on you. Though you can prove me wrong using logic and facts.
Hello,
Is there a suitable kernel for cm13 which allows for CPU to run at 1.7mhz, CPU voltage adjuster, USB fast charge, and speaker gain adjuster? Any number of adjustments is fine.
Thanks
ddvche said:
Hello,
Is there a suitable kernel for cm13 which allows for CPU to run at 1.7mhz, CPU voltage adjuster, USB fast charge, and speaker gain adjuster? Any number of adjustments is fine.
Thanks
Click to expand...
Click to collapse
Texas Instruments' description the maximum is 1.5mhz, so clearly I don't recommend you to find a suitable kernel for cm13 which allows for CPU to run at 1.7mhz. You can try AudioFx or DSP Manager to adjust your speaker.
I have no time for custom kernels. I'm too busy, you know. And unfortunately, often too much distracted (which is the main reason why I do these things so slowly). I need to correct CM13, Omni, Slim6, CandySix + bring 3 more AOSP MM ROMs (it's close, finally I found missing piece to make it boot), so I can say my job is finally done (I'm not satisfied for now). I want to finally start working on Nougat for tate.
Ok, everything seems fine except Snaps video recording. If I'll not find solution for that, I'll just bring last version of this SNAPSHOT and then move on. I have a lot to do.
Also, seems like nobody uses Google Calendar. (error -505 in the Play Store). The solution in the description.
PLEASE REDOWNLOAD THE BUILD
https://www.androidfilehost.com/?fid=385035244224386732
Installation: Full wipe/Flash ROM + OpenGApps
I can't fix Snap Camera video recording for now. My advice to you: disable Snap Camera or better delete it (I always delete system Camera). Install Open Camera or another 3rd party app. No problems with 3rd party camera apps (Of course, I didn't try them all, it's impossible) And let's be realistic: you won't get good images or videos with this type of camera anyway. The purpose of this camera is video calling which it does. (not sure if it works with 3.0.101+ kernel but 100% I've seen Hangouts video calling working on one of my MM ROMs).
Like I promised, no screen blinks for now and I've removed some system apps (which you can find in the description if you need it).
I need to move on to the next ROMs now.
Deleted
bjbirch said:
Does anyone know if there is an updated twrp for Tate,can you post a link to it please as my current twrp isn't working properly
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=94712
Also, now there is a link in the description.
alexander_32 said:
https://www.androidfilehost.com/?w=files&flid=94712
Also, now there is a link in the description.
Click to expand...
Click to collapse
Thank you for the reply,I found a copy of a newer version for the kfhd Tate that I had uploaded to Dropbox ,after I had posted on this thread,I shall check the download link to check that it is the same one
Sent from my K10000 using XDA-Developers mobile app
Heellloo
Hey Alex,
Great job in creating these ROMs, I will test them out as soon as possible and will of course provide feedback, hopefully all goes well. Also if you are planning on bringing nougat for this device, then you my friend are a wizard! Can't wait to hear back from you.
Edit: Okay... For some it keeps on saying "download failed" for the open_gapps-arm-6.0-pico-20161028, I've tried downloading it from github as well. Man, such bad luck already at 2:50am =(
Finished downloading the ROM before though.
Stone. Cold said:
Hey Alex,
Great job in creating these ROMs, I will test them out as soon as possible and will of course provide feedback, hopefully all goes well. Also if you are planning on bringing nougat for this device, then you my friend are a wizard! Can't wait to hear back from you.
Edit: Okay... For some it keeps on saying "download failed" for the open_gapps-arm-6.0-pico-20161028, I've tried downloading it from github as well. Man, such bad luck already at 2:50am =(
Finished downloading the ROM before though.
Click to expand...
Click to collapse
Thanks. I want to finish my MM contribution in the near future then get some rest until winter (I feel exhausted). I'll start a Nougat on Kindle campaign somewhere in winter.
alexander_32 said:
Thanks. I want to finish my MM contribution in the near future then get some rest until winter (I feel exhausted). I'll start a Nougat on Kindle campaign somewhere in winter.
Click to expand...
Click to collapse
Hopefully all goes well =)
Quick request, whenever I try and download open_gapps-arm-6.0-pico-20161028 it keeps on saying "download failed" when it comes to finishing at around 106mb. Is it possible if you can upload this in Google drive (or any other cloud server) so that I can download this without it failing. I've tried looking for aalternative websites where I could download the gapps, but it ended the same way xD. Thanks bro! =)
Stone. Cold said:
Hopefully all goes well =)
Quick request, whenever I try and download open_gapps-arm-6.0-pico-20161028 it keeps on saying "download failed" when it comes to finishing at around 106mb. Is it possible if you can upload this in Google drive (or any other cloud server) so that I can download this without it failing. I've tried looking for aalternative websites where I could download the gapps, but it ended the same way xD. Thanks bro! =)
Click to expand...
Click to collapse
Have you tried downloading open_gapps-arm-6.0-micro instead of open_gapps-arm-6.0-pico
Stone. Cold said:
Hopefully all goes well =)
Quick request, whenever I try and download open_gapps-arm-6.0-pico-20161028 it keeps on saying "download failed" when it comes to finishing at around 106mb. Is it possible if you can upload this in Google drive (or any other cloud server) so that I can download this without it failing. I've tried looking for aalternative websites where I could download the gapps, but it ended the same way xD. Thanks bro! =)
Click to expand...
Click to collapse
I believe you have a problem with your browser. I've downloaded the last one pico package (a minute ago). I'm on Linux Mint 17.3 Mate (Chrome for Linux).
It was browser
alexander_32 said:
I believe you have a problem with your browser. I've downloaded the last one pico package (a minute ago). I'm on Linux Mint 17.3 Mate (Chrome for Linux).
Click to expand...
Click to collapse
Alright, got it to download =)
The boot time took around 4 minutes, I was really surprised when I saw Android Upgrading because everything looked so different, the looks of it beats them all. The setup was quick and simple. My first impressions of the ROM were that it looks good and is more reliable than android 5.1 (my experience with 5.1 was dreadful, too laggy!) The reason as to why it's more reliable is because for once the stock camera app actually works! This got me surprised. For kernel adiutor I did configure the "low memory killer" and chose very aggressive, however, since this is marshmallow I understand how much RAM it takes up, I had around 240mb of RAM left so not really sure if that's a good or a bad thing (in this case). Battery seems decent enough. For quadrant standard, I ran the full test and got around 12,398 that's actually quite good considering on android 4.4 I usually get around 8,000-9,000. I just want to know why the GPU OC is set on 384 as max. I did encounter a lot of minor bugs, in this case in the settings app whenever I click on a GUI the borders on top go from its original colour to black constantly. In the quick settings, whenever I were to click night mode, it would show the screen blinking for around a second or two (not sure if this is normal).
Regardless of the minor bugs, this ROM has potential! Hopefully in future releases you can get it to work more stable and lagfree. Can you recommend me which of the android 6.0 ROMs work best for you? Thanks man! This ROM still beats any android 5.1 I've tried on this device.
Kind regards,
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-04-01
Last Updated 2018-07-19
Wow thats good. Thank you very much.
Hi, Myself5! Thanks a lot that you still support our device though you have newer devices.
User experiences and issue list for 2019-03-11 Release
First of all, thanks to @Myself5, @rcstar6696 and all other members of the CarbonROM team for the release of CarbonROM 6.1 Oreo for our device! :good::victory:
User experiences with CarbonROM 6.1:
Installation was smooth. I flashed cr-6.1 and OpenGapps ARM 8.1 on top of my working cr-5.1 installation (dirty flash), so all of my apps and their settings were kept. MindTheGapps 8.1.0 arm, which are recommended by the Carbon devs, are also working fine. Keep in mind that there is no guarantee that a dirty flash works in all cases, so you might have to wipe your data partition. This generally is recommended when updating to a new Android version anyway.
Besides of some small issues (see below), everything runs stable and the system is snappy and smooth. Thermal management and charging speed is fine.
Magisk 16.0 works fine, as well as Xposed Framework (SDK 27) v90-beta3 or alternatively Systemless Xposed (SDK 27) v90.1-beta3 Magisk module. However, there are some force-closes of background apps every now and then, caused by the beta status of Xposed v90.
My Xperia Torch Boost Magisk module is still working well on cr-6.1.
Selinux is set to enforcing, just as it was in cr-5.1.
I found out that Android Messages SMS/MMS app has a high battery drain, which e.g. is also reported for Pixel devices on Android 8 Oreo, so a general bug by Google. Because of this, I switched to Textra SMS (of course you can also use one of the other SMS/MMS apps around), which fixes the battery drain.
Improvements in comparison to cr-5.1:
The camera button now acts exactly like in Sony Stock ROMs, so now focussing and taking pictures is possible with Stock Sony Camera. You can also invoke the Stock Sony Camera by long-pressing the camera button, just like in Stock ROMs, but this doesn't work when the device is off or locked. In this case you can use a double press on the power button, which can be enabled in Carbon Fibers settings.
Booting the device is noticably faster than on cr-5.1.
Lower battery drain than on cr-5.1.
Better, more uniform design.
The ROM is being updated to the latest Android Security Patches.
Apps can be "locked" in the Recent Apps, so when pressing the Clean All button, they keep running.
4K video recordings are possible.
Missing features in comparison to cr-5.1:
There is no option to turn on Network Traffic Indicators yet. (This has been added in 2018-04-05 Weekly.)
Default Camera-App does not allow to save photos to sd-card, puts photos in wrong orientation and is all around very limited. However, there are good alternatives like Open Camera and the Stock Sony Camera. (Since 2018-05-01 Weekly, Snap Camera is used again.)
Issues in Carbon ROM 6.1:
Video recording doesn't work yet with the built-in Camera app, as well as with several other apps like Open Camera and the Stock Sony Camera. Until this is fixed, you can use Footej Camera for video recording as a workaround. (This has been fixed in 2018-05-08 Weekly by @AdrianDC and Milos Ratkovic.)
DoubleTap2Wake isn't working yet. (This has been fixed in 2018-04-11 Weekly.)
The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. (See @Myself5's reply in post #14.)
The gyroscope doesn't work properly yet with certain apps, e.g. Vr Tester - Gyroscope Sensor App and Accelerometer Gyro Tester. (Obviously this is a bug of those apps or of Oreo in general, since @Myself5 could reproduce it on his Pixel 2 XL device, running on stock ROM. Many other apps that use the gyroscope are working fine on cr-6.1.)
Saving and accessing files on SD card doesn't work for certain apps and tools, which could be a Linux permission or SELinux denial issue. For further information and partial workarounds, see post #45, post #49 and post #51. (This has been fixed in 2018-06-05 Weekly.)
Screen Cast still isn't working for me with 2018-04-11 Weekly (I tested this with a Sony and an LG Smart TV which both connected fine to my Z3c on stock ROMs), even with the new boot image from post #103 which is working with @Myself5's Fire TV stick and Wireless Display Adapter. This has been fixed in 2018-04-17 Weekly.
WiFi isn't working on 5 GHz band in some countries, as has been reported in post #1634 on the Z2 cr-6.1 thread, including links to posts with possible workarounds and fixes. There's also an article in the xda wiki with further information. Since 2018-05-01 Weekly, Germany (DE) is used as Wifi country code, but there have been several reports by users from other countries that this doesn't work for them, so is not an universal fix. As a workaround, until this is fixed, you can use my Magisk module from post #195, which you have to change to your own country code by following the instructions that I gave there. Edit: @marcogiannetta posted an improved Magisk module in post #373 which changes the Wifi Country Code accordingly to the system language. A similar issue (wifi dosent connect in Iran) also has been reported on the bug tracker and is being looked after by the devs. Edit: According to post #2092 on the Z2 thread, this issue can also be fixed by installing WiFi regional problem solver Xposed module.
Music files can't be played from SD card with Vanilla Music, Sony Music and several other players. This issue was fixed in 2018-05-08 Nightly, but reappeared on 2018-05-15 Nightly. Until this is fixed again, you can use jetAudio HD Music Player as a workaround. (This has quickly been fixed again in the 20180515-2340 Weekly build.)
When making a screenshot via the Power menu, most of the time the Power menu itself is visible in the screenshot. There should be a slight delay (just 1/10th second might already be sufficient), so the Power menu is already hidden again before the screenshot is taken. This has been fixed in 2018-07-05 Weekly.
Apps like Netflix, MyCanal and MagineTV don't work because DRM WideVine is not supported yet, whereas in CarbonROM 5.1 it was supported. This has been fixed in 2018-08-15 Release.
Lock screen rotation has been removed since 2018-09-11 Release. It was a useful feature when using the phone in landscape orientation e.g. in a car holder and IMO should be added again. Edit1: As a workaround, I made LockscreenRotationEnabler Magisk module which adds this functionality by adding a setting to 'build.prop'. Edit2: Lock screen rotation can also be enabled with GravityBox [O] Xposed module.
NFC extended length isn't supported, which is needed e.g. for reading identity cards with apps like AusweisApp2. (This has been fixed in 2019-03-11 Release.)
NFC-HCE isn't supported, which is needed for Google Pay. (This has been fixed in 2019-03-11 Release.)
Wish list for some further improvement of Carbon ROM 6.1:
Long press camera button to wake and launch camera app when the screen is off or the phone is locked. Edit: I found a workaround which I described in this post.
A toggle to switch to dark UI theme for quick settings. Edit1: The dark UI theme can be forced with ForceDarkModeOreo Xposed module. Edit2: ForceDarkModeOreo unfortunately is one of the Xposed module which cause random app crashes, so it's not advisable to use it. Let's hope that the devs will add this feature eventually.
About time this one got its own thread, huh
Everything works great, no bugs so far and no problem with camera recording (using Footej Camera), though missing hardware key rebindings and i cant enable power notifications
Downloading right now. Lets see how it compares to Omni 8.1
EDIT (my comment from a few pages later):
After a few days with it, I can say it's already suitable for daily use. Using MindTheGapps (tho I will switch to OpenGapps pico, I don't want Google app ), Magisk 16.
It's smooth and very stable. No crashes or major issues for me so far.
Battery life is acceptable, worse than stock (doh), and perhaps even LOS 14.1. Thermal management and charging speed is fine.
No idea about the camera, mine is broken (HW) and I never use front one.
A few suggestions and comments:
Add some power balancing options like with LOS (better performance or battery life).
Also, I love how you can customize RGB values on LOS to make it more yellowish even during day, plus night light. Any idea what workaround I could use? My blueish screen is killing me and I can't use night light all day.
Good to hear night mode is being worked on.
How to make quick tiles menu like on 7.x? I preferred auto expanding options for mobile data and silent mode. Can't find it in fibers.
Hi, Great that development is ongoing - Thanks a lot!
One thing, got the same problem with the none carbon Oreo Version:
got problems with whatsapp. Video isn't running. The phone doesn't build up a connection. Chat works, but whatssap call or video not.
Skype ist working without problems ...
Any Ideas?
I installed it with a full wipe - system, cache, dalvik, data, internal storage. Used TWRP 3.2 for ROM (to mind error 7) and TWRP 3.1 for installation of MindTheGApps.
Thanks for help!
Thanks for the ROM, working great for me.
I have accidently deleted live wallpaper picker. Tried download a few different versions from the internet but nothing works. Where can I get the one this ROM is using?
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Nice post, okij
okij said:
[*]The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. Also, forcing dark theme via Dark Tricks Xposed module doesn't work.
Click to expand...
Click to collapse
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Kocane said:
Nice post, okij
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Click to expand...
Click to collapse
Doesn't substratum work?
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
Substratum works fine
Greets ted!
okij said:
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Click to expand...
Click to collapse
For things like Networks indicator: Some additional features will surely come with time, as you said.
Video recording: I think it was the Z3 thread where I explained it in detail: The commits to fix Video recording do work (kind of), but are WIP, so we're all working on getting them stable and polished, then they will be merged as fast as possible. When that happens is rough to estimate, I wouldnt expect it to take much longer than 2-3 Weeks though.
DT2W: As you said. Fixed and merged, will be included in the Next Weekly.
For the Dark Theme: Isn't that a Pixel only feature? For that to work you'd need assets for a "dark theme". On Pixel devices those are on the /vendor partition, so obviously not present on our Z3C. Correct me if I'm wrong please.
Thanks for the detailed report, will gladly keep on checking it with followup builds.
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
It does. Install the Substratum app and flip the switch in CarbonFibers -> Privacy to make it work.
The Switch is disabling the Security measures Google merged in the March ASBs. By default Subs completely removes them, but we decided to go for an opt-in for those that want to use it while keeping the "security" Google intended to have with merging it for those that don't want to.
First off all, thank u for this amazing work! Rom is awesome.
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
2 - Someone can tell me if led notification works? Not work here...
Sorry bad English...
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Any idea anyone?
Thanks!
marlontravagli said:
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
Click to expand...
Click to collapse
Yes, this is a great additional feature when using DT2W and one of the reasons that I use GravityBox. @Myself5: It would be great if you could implement this feature for those of us who don't use Xposed. In GravityBox it can be found under "Power tweaks -> Proximity wake up" and the additional option "Ignore for incoming call" which is also worth implementing.
2 - Someone can tell me if led notification works? Not work here...
Click to expand...
Click to collapse
I can confirm that LED notifications are working here, just tested this with missed call (using Google Dialer) and incoming email (using AquaMail).
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Laus_bub said:
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Click to expand...
Click to collapse
I don't use WhatsApp, but I guess that the not working video call has to do with the not fully working video recording (see #1 in the issues list I posted here).
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
ElLoloFR said:
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
Click to expand...
Click to collapse
Did you try removing all other modules? For me the very same thing is happening if I try to use the fbind (Folder Bind) module. You can try to remove all modules, if u use the Magisk Manager for Recovery Mode (mm).
I tried and :
"No magisk installation found."
So I installed Magisk v16, then installed this one.
I could install mm, this was the only module installed.
I uninstalled mm, rebooted without uninstalling Magisk V16, and the phone booted !
But I can't open Magisk Manager v5.6.4, stucked in the app logo...So Magisk seems to be installed, but I can't use it :/
EDIT : Well, after a recovery reboot, reinstall f magisk V16, phone boot correctly and Magisk is alive.
I don't know how this is working, but it's working.
No doubt, you helped me, many thanks
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions & Downloads :
https://github.com/penglezos/device_xiaomi_raphael/releases/latest
Bug report :
Do not report bugs if you are: having a decrypted system, running a custom kernel, being rooted or using any other mods.
Please provide a detailed description of your issue as well upload a log file whenever possible.
Support the development :
If you found this helpful, please consider supporting development with a PayPal donation. All support is appreciated.
Source Code :
https://github.com/penglezos/kernel_xiaomi_raphael
Reserved.
Any known bug?
Do you need to install Gapps? Any recomendation if needed?
I installed this rom and it works fine, but the fod doesn't work with the screen off, is it like that or is there any configuration or procedure to be done?
ashwany.yadav said:
Any known bug?
Click to expand...
Click to collapse
None.
vetalpeo said:
Do you need to install Gapps? Any recomendation if needed?
Click to expand...
Click to collapse
Mindthegapps, nikgapps.
alessandro-villa said:
I installed this rom and it works fine, but the fod doesn't work with the screen off, is it like that or is there any configuration or procedure to be done?
Click to expand...
Click to collapse
It's not included in LineageOS sources either my code.
I tested this ROM for two days and so far it is a great experience without any major issues. Thanks!
Issues which I ran into:
- Fingerprint scanner works much worse when night backlight is turn on.
- Google camera from Play Store don't work, it just crashes.
Cool. But I cant download with android orginal browser and phone calls just playing ringtoone but nothing appeared in scrren to amswer and I should call to a number to unhide incoming call dialog!
Hello everyone.
First of all, a big BIG thank you @Englezos for this ROM, even unofficial. For the little I used it, it is extremely functional, much more than the unofficial ROM /e /OS https://community.e.foundation/t/un...-mi9t-pro-raphael-e-os-q-build/24814?u=parhit (last update in May 2021 and many bugs). No worries on my side about digital recognition, ergonomics and even the separation of personal and professional profiles (via Insular). I had a bit of trouble installing it (the adb sideload was showing 40% and made me restart but it didn't work, same thing the second time but there I just waited maybe a bit more before seeing with relief the Lineage logo).
I'm reporting some bugs I've encountered, on the personal or pro side.
# Applications (via Aurora Store)
Yuka https://play.google.com/store/apps/details?id=io.yuka.android&pli=1 doesn't launch, the screen is white and makes a strobe effect
Brain FM https://play.google.com/store/apps/details?id=com.brainfm.app&hl=en_US stays on initial load
UpHold https://play.google.com/store/apps/details?id=com.uphold.wallet&hl=en&gl=US same
# Default browser
I can't download via the default browser .apk files, it says to check in the settings but I couldn't find anything. Another
# General configuration
The alarm clock does not ring if the phone is switched off. So I was late this morning
Again a BIIIIG UP. I was going to go back to MIUI out of spite but to have a stable OS, thanks to you I stay on the right side
MartinPL said:
I tested this ROM for two days and so far it is a great experience without any major issues. Thanks!
Issues which I ran into:
- Fingerprint scanner works much worse when night backlight is turn on.
- Google camera from Play Store don't work, it just crashes.
Click to expand...
Click to collapse
1. That's the default AOSP behavior until Google changes it. You can try lower the density.
2. Because this device is not a Google Pixel.
mablue said:
Cool. But I cant download with android orginal browser and phone calls just playing ringtoone but nothing appeared in scrren to amswer and I should call to a number to unhide incoming call dialog!
Click to expand...
Click to collapse
It appears that it was a LineageOS bug which is already fixed and will be included into the next build. About the phone calling issue that you just described I can't reproduce it.
parhit said:
Hello everyone.
First of all, a big BIG thank you @Englezos for this ROM, even unofficial. For the little I used it, it is extremely functional, much more than the unofficial ROM /e /OS https://community.e.foundation/t/un...-mi9t-pro-raphael-e-os-q-build/24814?u=parhit (last update in May 2021 and many bugs). No worries on my side about digital recognition, ergonomics and even the separation of personal and professional profiles (via Insular). I had a bit of trouble installing it (the adb sideload was showing 40% and made me restart but it didn't work, same thing the second time but there I just waited maybe a bit more before seeing with relief the Lineage logo).
I'm reporting some bugs I've encountered, on the personal or pro side.
# Applications (via Aurora Store)
Yuka https://play.google.com/store/apps/details?id=io.yuka.android&pli=1 doesn't launch, the screen is white and makes a strobe effect
Brain FM https://play.google.com/store/apps/details?id=com.brainfm.app&hl=en_US stays on initial load
UpHold https://play.google.com/store/apps/details?id=com.uphold.wallet&hl=en&gl=US same
# Default browser
I can't download via the default browser .apk files, it says to check in the settings but I couldn't find anything. Another
# General configuration
The alarm clock does not ring if the phone is switched off. So I was late this morning
Again a BIIIIG UP. I was going to go back to MIUI out of spite but to have a stable OS, thanks to you I stay on the right side
Click to expand...
Click to collapse
Thanks for your words and your detailed feedback. I'm glad that you have managed to installed the rom successfully.
About the Yuka app unfortunately its not available on my country and I can't install it via Google Playstore.
Brain and Uphold apps are loading and working fine.
Android browser: It appears that it was a LineageOS bug which is already fixed and will be included into the next build.
The alarm clock won't work if your device is powered off. Why would you want such thing?
Hi Englezos, thanks for the fast feedback.
Englezos said:
About the Yuka app unfortunately its not available on my country and I can't install it via Google Playstore.
Brain and Uphold apps are loading and working fine.
Android browser: It appears that it was a LineageOS bug which is already fixed and will be included into the next build.
The alarm clock won't work if your device is powered off. Why would you want such thing?
Click to expand...
Click to collapse
Yuka only in France? ****... Maybe with a VPN? Can I help?
Brain.fm and Uphold working fine? Holy sh*t. I don't know why it doesn't work here. What tool do you use to install apps?
Browser: ok, I am using Bromite but it sounds good if it will be fixed.
Alarm: well, an alarm clock that doesn't ring is strange, isn't it? I didn't have a watch and I turn off the phone at night. So I thought the alarm would go off even if it was off (which is what was happening with Murena). Am I the only one doing this?
Installed this ROM as OTA for Los 19.1 (SebaUbuntu). Thanks for new version.
All work as need.
MoodRoff said:
Installed this ROM as OTA for Los 19.1 (SebaUbuntu). Thanks for new version.
All work as need.
Click to expand...
Click to collapse
So you dirty flashed this ROM? Via recovery?
Plex82 said:
So you dirty flashed this ROM? Via recovery?
Click to expand...
Click to collapse
Yes, need do format data later install
Englezos said:
About the phone calling issue that you just described I can't reproduce it.
Click to expand...
Click to collapse
I always have this problem in iran region with mobile calls +98Xxxxxxxxxx.
And it's too bad .Maybe I think it's a nonclean installation bug
parhit said:
Hi Englezos, thanks for the fast feedback.
Yuka only in France? ****... Maybe with a VPN? Can I help?
Brain.fm and Uphold working fine? Holy sh*t. I don't know why it doesn't work here. What tool do you use to install apps?
Browser: ok, I am using Bromite but it sounds good if it will be fixed.
Alarm: well, an alarm clock that doesn't ring is strange, isn't it? I didn't have a watch and I turn off the phone at night. So I thought the alarm would go off even if it was off (which is what was happening with Murena). Am I the only one doing this?
Click to expand...
Click to collapse
At least it's not available on my country. Maybe get some logs related to this app.
Rest applications are installed through Google Playstore.
Alarm is ringing well when the phone is powered on.
mablue said:
I always have this problem in iran region with mobile calls +98Xxxxxxxxxx.
And it's too bad .Maybe I think it's a nonclean installation bug
Click to expand...
Click to collapse
You should always clean flash when coming from another rom. Try another phone app also.
New release is up with November security patch and many critical fixes!! Links are on the first post!!
Does this rom passes safetynet by default? Also google photos spoofing is there or not ?
deleted
Englezos said:
New release is up with November security patch and many critical fixes!! Links are on the first post!!
Click to expand...
Click to collapse
Hi there. Great
So is it necessary to reinstall everything from scratch or is a classic update possible? This is the first time I've had an update available on an unofficial ROM