Database Info

Since I'm a supposed noob, To beans on MIUI for SGSIII; I535:

On MIUI regarding [Official] "MIUI.us V4.1 2.9.7 (09/12/2012) Alpha 5"
I would like to report a text message crash.
How I encounter the crash:
Open text messaging software,
Click any message thread,
use the return/back key
CRASH!
I'll report anything else I find in this thread as well, but it would be nice to have this moved to the development section.
Thanks!~
~JLe

Beans also puts his ROMs on rootzwiki so you could report there if you'd like. Or wait till you have a high enough post count to report it in the Dev forum here.

Resperith said:
On MIUI regarding [Official] "MIUI.us V4.1 2.9.7 (09/12/2012) Alpha 5"
I would like to report a text message crash.
How I encounter the crash:
Open text messaging software,
Click any message thread,
use the return/back key
CRASH!
I'll report anything else I find in this thread as well, but it would be nice to have this moved to the development section.
Thanks!~
~JLe
Click to expand...
Click to collapse
that is a known bug; knowing Beans, he'll fix it, he usually does

Give us BATTERY_STATS back

If you already got your Nexus 5 or installed a custom Kitkat ROM you already have noticed that your favorite battery stats tool, whether it is BetterBatteryStats, GSam of wakelock detector, does not work.
Well it is not uncommon for some API to be changed so when a new Android version comes out it usually takes us a few days to get hands on a device and fix things.
But this time is different and important enough for me to take time to summarize the situation.
A little history
Android has a service called 'batteryinfo' that collects a lot of info about what goes on on your phone. That service is not perfect but it provides some pretty important information about what is important to our battery monitoring apps: an insight into what drains our battery.
Our apps communicate with that service and therefore claim the android.permission.BATTERY_STATS permission protecting the access to that service. This permission is of the category "dangerous", notifying users of the fact that they should check why an app requires that permission. For a battery monitoring app it is logical to require it.
This change of course impacts devs as their apps became unusable with that release with no perspective for a fix without an expensive workaround (as e.g. already implemented in BetterBatteryStats 1.15+).
But more alarming, it prevents users to get an insight in what drains their battery and make decisions to keep or drop apps depending on the 'cost' in terms of battery life!
If I was a conspiration theorist I may believe that this change was made on purpose to prevent users from seeing how all the pre-installed apps - including those from google - affect their user experience by reducing the battery life / usability.
What happened
With kitkat starting to ship things happened pretty fast and first feedbacks started to emerge reporting that the service could not be contacted. It took me some time to get hands on a kitkat phone (in fact I flashed my gnex with an inofficial ROM and had to make sure that the errors I got were not cause by that ROM and corresponded to the behavior on a Nexus 5.
After some research two changes in 4.4 are responsible for the problem:
1. batteryinfo was renamed to batterystats
2. the BATTERY_STATS permission has been unavailable to apps (moved from protectionLevel 'dangerous' to 'signature|system'
This is the change preventing apps to be granted that permission: https://android.googlesource.com/pl...it/+/3714141d287c965ea3451831dd5167f63f8db87b
As you can see the change refers to an issue number but this issue is not documented in the public tracker (welcome to not-really-open-source).
I have posted a request on the android-platform forum to request a clarification on why that change was made (https://groups.google.com/forum/#!topic/android-platform/f-7Td9aeFKY) but DID NOT GET ANY satisfying feedback. Therefore I have filed an issue in the public bug tracker for this change to be rolled back (https://code.google.com/p/android/issues/detail?id=61975&thanks=61975&ts=1383910497).
I kindly invite you to upvote this request by staring it.
Please star it, adding a comment "I vote for this" or "Please undo this" to the thread does not do any good:
- comments are not counted, only stars
- that forum is not there to express opinions, it's for bug reports and requests. Unrelated matters like opinion will have no other result than annying the reader.
What devs should know
1. BATTERY_STATS has been moved to protectionLevel=18 (signature|system) and is not accessible to apps anymore
2. On KitKat copying an app to /system/app does not grant protectionLevel=18 anymore. This has been changed in KitKat and the target directory to gain those rights is /system/priv-apps
3. The service delivering battery stats was called 'batteryinfo' in previous Android version and is called 'batterystats' in KitKat
[update 2013-11-16]
*dream out loud*
In an open source world the community owns the source right? Wouldn't it be cool if some senior android devs would review this change and - assuming there is no good reason for it - would revert it in their fork to provide their users with what I believe is an important feature?
[/update]

I really would like to hear from some senior devs maintaining a repo about the idea of taking control and reverting that change

Google has release 4.4_r1.2 and still no joy.
Changes are here:
https://android.googlesource.com/platform/frameworks/base/+/android-4.4_r1.2

Re-enable BATTERY_STATS in a custom ROM
I wrote up a post in another thread about what a ROM developer can do to re-enable Battery Stats (non-root) in a custom Rom. Very simple, but wanted to point it out should anybody be wondering...
http://forum.xda-developers.com/showpost.php?p=48029013&postcount=26

For CM2016' KitKats only
chamonix said:
I really would like to hear from some senior devs maintaining a repo about the idea of taking control and reverting that change
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Does it make sense ?
Thanks for any help.

oF2pks said:
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Does it make sense ?
Thanks for any help.
Click to expand...
Click to collapse
Can you help me understanding what this mod/change is about? My suggestion was about reverting a change that was made by google to restrict the access to a certain permission. You link is to a post with a title suggesting something like blocking the ability for apps to hold wakelocks. Such a stunt would be a really bad idea IMHO but maybe I missed an important point

idea of taking control
chamonix said:
suggesting something like blocking the ability for apps to hold wakelocks. Such a stunt would be a really bad idea IMHO
Click to expand...
Click to collapse
Thanks for feedback; i'm real fan of wakelock-blocker's theory, and was wondering if :
- is it useful ?
- can it help user to take control on any kind of restriction ?
I found that completely awesome under KK (static use) but i was very disappointed on testing with LP (anarchic behaviour). BetterbatteryStats was the best observer i found around, and i thought that both were complementary; indeed Beanstalk did use use both with KK: wakelock-blocker' mod and performance/wakelock(similar to your top-app) from Omnirom. But with Omnirom, the mod was rejected : https://gerrit.omnirom.org/#/c/9266/ ; to quote you ("some senior devs maintaining a repo about the idea of taking control"), this link show how much they do ?
Recently, I discover that Beanstalk (6?) was pushing this complementary further forward: https://github.com/scotthartbti/and...mmit/5fb687ae0940a12c8f7c9e457b6d5f12f028736b
I hope there was not too much confusion or loose in my first post and i believe BetterBatteryStats is a better option that can be toggled at any time. (I won't get a lot of thanks with my KK thread....)

[ROM][evita]MoKee 4.4 (2.10.14)

{
"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"
}
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (countless other scenarios apply here). Please do some research if you have any concerns about features included in the product you find here 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 (seriously, I will laugh really hard!). Your warranty will be void if you tamper with any part of your device / software.
Introduction:
MoKee OpenSource is based on the Google AOSP and CyanogenMod project. 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.
The Mfunz Forums launched this project on the 12th of December 2012, and is committed to make this ROM better and better.
Since this project is open source, anyone interested can participate in the development. Newcomers are always welcomed!
Types of Releases:
MoKee OpenSource has 4 kinds of releases: official release, beta, nightlies, and unofficial builds.
Official release: This version is tested throughly by developers and users, so it is the most stable build
Beta: When a device is newly added, there will be beta versions for testing, but there might be unknown bugs and problems
Nightlies: Nightlies are compiled automatically by servers, so it will have the latest features but beware of uncompleted works
Unofficial builds: These builds are compiled from source or ported by non MoKee developers
Official Releases:
MoKee Open Source supports many devices, but the developers may not have all devices in hand, so if there are device maintainers that can help out, the official releases will be decided by them, MoKee Open Source will only maintain the nightlies to ensure the usability of the ROM. However, for devices with no device maintainers, MoKee Open Source will decide when to release official builds or nightlies. Therefore, if you have a device maintainer, please get the official releases from your respective device maintainer's thread or nightlies from MoKee Open Source.
Features:
Incremental updates
OTA updates - update on the fly!
ListView animations
Multi window
Calendar - with lunar and solar calendars
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
Built in timer in Apollo - determine when to stop playing music
MoKee NotePad
MoKee Setup Wizard
Active Display
HALO
Adjustable navigation bar height
Unique Power Saver functions!
Custom screen off animations
** Not yet merged
PIE control
Auto hide status bar
Smart capture
Preview option in launcher (similar to the preview function in launchers found in Play Store)
Many more! Since we are constantly adding new features, see changelogs to keep updated!
Links:
Official Site:
http://www.mfunz.com
Statistics:
http://stats.mfunz.com
Bug Tracker
http://issues.mfunz.com
Changelog
http://changelog.mfunz.com
GitHub
http://github.com/MoKee
Code Review:
http://review.mfunz.com
Installation Instructions:
1. Wipe data/factory reset
2. Flash ROM
3. Flash Gapps
4. Reboot
Issues with themes:
Please refer here: http://forum.xda-developers.com/showthread.php?t=2577469
Donations:
http://www.mfunz.com/en/donations/
Credits:
- MoKee Developers: http://www.mfunz.com/en/contributors
- CyanogenMod
- AOSP
- Koush for open-sourced SuperUser
- ParanoidAndroid for HALO
- Slim Roms
- @gimmeitorilltell for helping me through some initial build errors
XDA:DevDB Information
MoKee 4.4 (Unofficial), a ROM for the AT&T HTC One X
Contributors
Black!Jack
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.14/2.15
Based On: CyanogenMod/MoKee Open Source
Version Information
Status: Stable
Stable Release Date: 2014-02-10
Created 2014-01-25
Last Updated 2014-02-10

Downloads
Mod Edit: Download links removed.
GApps Downloads
PA GApps
BaNkS GApps
Recovery Downloads for 4.4 Roms
CWM
TWRP

Changelog
All MoKee changelogs can be found HERE.

Z1cK said:
Look cool. Downloading... Will report feedback. Good job !!
Sent from my One xl
Click to expand...
Click to collapse
I hope you enjoy it. I have been running it for quite a while and I have no complaints.
A Q&A thread has been started for non development related questions, requests, chatter etc...
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2623699
Let's all try to keep this thread clean!
Sent from my One X using Tapatalk

OK. It booted fine and everything is working well. :thumbup:
Sent from my One xl

gimmeitorilltell said:
This looks great! I'm excited to see that I was able to help someone out! This rom looks promising and it seems like it's gonna be a busy thread for you. Congrats!
Click to expand...
Click to collapse
Thanks to you my friend! I appreciate your help. It was nice to have someone to "steer" me in the right direction; and not actually "drive" me to my destination. Logic prevails yet again!

Z1cK said:
OK. It booted fine and everything is working well. :thumbup:
Sent from my One xl
Click to expand...
Click to collapse
Of course it is!
And just so that everyone knows, this DevDB project includes some important tabs at the top.
Screenshots
I have uploaded a bunch already, and I plan to add a whole lot more!
Downloads
In addition to my dev-host account, I will also be uploading them to XDA - you can find them in this tab; complete with md5 checksums.
Q&A
Pretty self explanatory. Let's keep anything not development related there; after-all, that is what it is there for! I will ask mods to move posts that do not belong here there. Repeated requests to the same people will get you BlackListed and ignored. Really, it's not that big of a request!

If your post disappears, it was probably moved to the Q&A Thread for this ROM, since the OP has asked that this thread stay dev talk, and questions etc go into the Q&A thread.
Thanks.

Madcat8686 said:
BJ, WIFI works for me and so does ADB. I am really digging this Rom. Battery life is phenomenal as I have come to expect from 4.4.2 Roms.
I saw one minor glitch when I first was setting up the Rom. The "X Remove" stayed at the top when I was removing a widget. It eventually went away after a reboot but I consider this cosmetic at best and it never happened again.
Other than that I have nothing but thanks for the outstanding Rom to report.
Click to expand...
Click to collapse
Great to hear. As this was sort of a dry run I didn't add or take anything away from the initial build. However, moving forward, I will be adding some useful features, and removing some unneeded nonsense. At the top of the main ROM page there is a tab for Feature requests. If you, or anyone else has a request for something you would like to see added, or subtracted, please put it there. It will be easier for me to keep track of everything that way. I have already received some great suggestions and look forward to receiving more. Please remember that I do this with my free time, and that I am not obligated to make all changes requested. That being said, I will do my best to accommodate "reasonable" requests. Thanks.
Additionally, at the top of the main ROM page there is also a section for Bug Reports. Please try to place all bugs, or possible bugs there. Again, this just makes things easier to keep track of. And as always, logcats are always appreciated when reporting issues.
Sent from my One X using Tapatalk

Black!Jack said:
Great to hear. As this was sort of a dry run I didn't add or take anything away from the initial build. However, moving forward, I will be adding some useful features, and removing some unneeded nonsense. At the top of the main ROM page there is a tab for Feature requests. If you, or anyone else has a request for something you would like to see added, or subtracted, please put it there. It will be easier for me to keep track of everything that way. I have already received some great suggestions and look forward to receiving more. Please remember that I do this with my free time, and that I am not obligated to make all changes requested. That being said, I will do my best to accommodate "reasonable" requests. Thanks.
Additionally, at the top of the main ROM page there is also a section for Bug Reports. Please try to place all bugs, or possible bugs there. Again, this just makes things easier to keep track of. And as always, logcats are always appreciated when reporting issues.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Sweet. Will do. I can't for the life of me think of anything to add I really like it as is but I'm sure there is room for improvement. Tomorrow I'll be taking the phone into "Cell reception hell" and we will see how it handles a lot of red lines in reception. There have been a few Roms that couldn't hang there.
And as for the free time, I take my hat off to you sir. I am pretty much in the same boat and I have to manage my time accordingly. I really want to churn out a Rom as well. Any tips and note you have would be much appreciated. I have Pheonixita's guide and a few other guides from the Android dev thread but I'm not there yet.
I envy you! JK (You are my hero right now though!)

Ok. Two days in "cell signal hell" and here's what I got. The phone only rebooted twice when the signal was weak or not present. I say "only" because other Roms rebooted multiple times during weak to no cell reception unless in airplane mode.
I captured a Logcat and I hope it is useful. Funny thing is, I'm not totally convinced it was a reboot because the phone woke up as usual but when I checked the battery status there was a gap with a red signal status underneath it.
I also included a screenshot so you can see when it happened.
The battery still had 40% when I plugged it in to transfer files so it's been pretty good.
For others, this is after extended periods in and out of extremely weak to no cell signal which is tough on any Rom. Even when the phone was stock I had reboots and shutdowns because of this.
I ran the 3.18 RUU and wiped my SD card last week to clean out the phone so I know the hardware is working great.

Madcat8686 said:
Ok. Two days in "cell signal hell" and here's what I got. The phone only rebooted twice when the signal was weak or not present. I say "only" because other Roms rebooted multiple times during weak to no cell reception unless in airplane mode.
I captured a Logcat and I hope it is useful. Funny thing is, I'm not totally convinced it was a reboot because the phone woke up as usual but when I checked the battery status there was a gap with a red signal status underneath it.
I also included a screenshot so you can see when it happened.
The battery still had 40% when I plugged it in to transfer files so it's been pretty good.
For others, this is after extended periods in and out of extremely weak to no cell signal which is tough on any Rom. Even when the phone was stock I had reboots and shutdowns because of this.
I ran the 3.18 RUU and wiped my SD card last week to clean out the phone so I know the hardware is working great.
Click to expand...
Click to collapse
I'm no expert with logcats, but right before AndroidRuntime started its shutdown process it looks like it was trying to load "xposed" binary 47. What xposed modules are you running?
Sent from my One X using Tapatalk

Black!Jack said:
I'm no expert with logcats, but right before AndroidRuntime started its shutdown process it looks like it was trying to load "xposed" binary 47. What xposed modules are you running?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I running greenify and CPU temp in status bar. I wonder if one of the Greenify experimental options caused it?

Black!Jack said:
Of course it is!
And just so that everyone knows, this DevDB project includes some important tabs at the top.
Screenshots
I have uploaded a bunch already, and I plan to add a whole lot more!
Downloads
In addition to my dev-host account, I will also be uploading them to XDA - you can find them in this tab; complete with md5 checksums.
Q&A
Pretty self explanatory. Let's keep anything not development related there; after-all, that is what it is there for! I will ask mods to move posts that do not belong here there. Repeated requests to the same people will get you BlackListed and ignored. Really, it's not that big of a request!
Click to expand...
Click to collapse
Nice Black!Jack your first KitKat! I thought about this one, but Ive got something else special coming.

Amazing rom, fantastic job.

wait what ? rom is all that but I think I am having a problem
the ringtone thing ... when its on vibration it works but when its on ringtone (there is sound) and some one call me I hear nothing and I cant notice my phone ringing ...

Never had that problem on this ROM. Did you clean flash?
Sent from my Evita

Getting ready to brunch new build now! Removed Asian apps. Attempting to integrate battery bar. Any last minute requests before I start the build? No promises though.
FYI... The work iPhone really sucks. Trying to be open minded, but not seeing anything that wows me. Mediocre at best, and definitely behind the times in features... From what I can tell so far. Oh, and you have to pay for everything. Pffffftttt. At least I got to keep my One XL too!
Sent from my HTC One XL using Tapatalk

Black!Jack said:
Getting ready to brunch new build now! Removed Asian apps. Attempting to integrate battery bar. Any last minute requests before I start the build? No promises though.
FYI... The work iPhone really sucks. Trying to be open minded, but not seeing anything that wows me. Mediocre at best, and definitely behind the times in features... From what I can tell so far. Oh, and you have to pay for everything. Pffffftttt. At least I got to keep my One XL too!
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
The only APK I can think of would be F-Droid (open source play store equivalent). This Rom is outstanding. I don't see how this day can get any better. I picked up a Grouper for 30 bucks like new. The guy just didn't want it and never used it. lol.
P.S. Don't forget to let us know if it's a boy or girl!

I've got a new build ready. Uploading now.
This one is still completely stock. Bouncing between edits and housework (prepping for the baby). Hopefully tonight I can release the more feature packed version i have been envisioning.

[ROM][BETA][6.0.1 r43][tate] Bliss Rom 6.4 by Team Bliss

{
"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"
}
Team Bliss is pleased to present to you
Bliss 6.4
Bliss is one of the most highly customizable roms that you can install on your mobile device, and we hope you have a truly blissful experience.
A huge thanks to CyanogenMod for the source and all the work and dedication their team puts in to keep us updated.
Bliss is CM13 based, with some features added in from various roms, and we will continue to update features as they become available.
We will keep up to date with the latest CM code, and updates will be posted on a regular basis.
However, please do not ask for ETA's. We will update the links as soon as they become available.
We will not tolerate any rudeness or anyone being disrespectful in this thread.
We will do our best to answer your questions or concerns as soon as possible.
Visit our website for features that include:
Member sign-up, staff information, all the latest rom downloads, the option to open support tickets for issues & more!
BlissRoms Website
Personalization Options
CM13 Theme Engine
Status Bar
Statusbar Clock & Date Options (Left/Center/Right/Hide/Etc)
Battery Icon Options
Customizable QS Tiles
Navigation & Button Options
Toast & Listview Animations
Recents Options
-Memory Bar
-OmniSwitch (Option to replace recents menu with Omniswitch)
Notification Drawer
-Status Bar Header (Weather)
-Tile Options
-Flashlight Option
-Custom Color Tile Options (Set Background, Icons & Text)
Heads Up Notifications
Lockscreen Options
-Long Press Lock Icon to Sleep
-Shortcuts
-Music Visualizer Options
-Power Button Lock Options
-Lock Method Options
Power Menu Options
-Power Off
-Reboot
Gesture Anywhere
-Location Options
-Trigger Regions
Animations
Slim Animations
App Circle Bar
-Included Apps
-Trigger width, position and height
Sound Options
-Link Ringtone & Notification Toggle
-Media, Alarm, Ring & Notification Sound Options
Display & Light Options
Brightness Level
Adaptive Brightness
LiveDisplay
Rotation
Ambient Display
Double Tap to Sleep
Sleep Time
Wake on Plug
Cast Screen
Wallpaper
Expanded Desktop
LCD Density
Daydream
Font Size
Show Search Bar in Recents
Notifications
Heads Up
Do Not Disturb & Access
Device Lock Options
App Notifications
Notification Access
Filter Notifications
More Stuff Included
Bliss Download Section
-All current downloads for your convenience
[/LIST
AudioFX Equalizer
-SuperSU - Huge thanks to @[COLOR="DeepSkyBlue"]Chainfire[/COLOR]
-Bliss Wallpapers (via launcher’s Wallpapers)
-Home Launcher Option
-CM Camera
-User Profiles
-System Profiles
-Location Options
-Security Options
-Privacy Options
-Accounts & Sync
-Language & Input
-Backup & Reset
-Date & Time
-Accessibility
-Printing
-Developer Options
-Rom & Hardware Information
-Changelog
-Bliss OTA Updates
--Many other settings throughout the rom. Take some time to familiarize yourself with all the blissful options!
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
We recommend using any of the following sets of GApps:
Open Gapps Project
Bliss - Beta Builds
Team Bliss is not responsible in any way for anything that happens to your device in the process of flashing.
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
FIRST CHECK SECOND POST - Make sure your device doesn't have any special instructions.
*Make sure you are rooted.
*Make sure you have a custom recovery installed. (TWRP is the preferred recovery)
*Download the latest Bliss Rom & the latest GApps package.
*Boot into recovery.
*Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
*Flash Bliss Rom
*Flash Google Apps package (for 6.0!)
*Flash Touch Fix
*First boot may take up to 10 minutes
CURRENT ISSUES
*Camera doesn't work yet
*Cannot select "Allow" when granting app permissions. (Use Settings>Apps to manually allow)
If you have a major bug to report that has not been reported already, and is not a known issue with CM,
please take the following steps to report it to us. It will save you time, as well as us.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
*Some elements may vary from build to build*
Team Bliss is a team consisting of developers and device maintainers that work on this project in our
spare time to be able to give Android users a custom rom packed with features that will make a lasting impression.
@[COLOR="DeepSkyBlue"]pimpmaneaton[/COLOR], @[COLOR="DeepSkyBlue"]jackeagle[/COLOR], @[COLOR="DeepSkyBlue"]nprev420[/COLOR], @[COLOR="DeepSkyBlue"]remicks[/COLOR], @[COLOR="DeepSkyBlue"]Deliberate[/COLOR], @[COLOR="DeepSkyBlue"]xboxfanj[/COLOR], @[COLOR="DeepSkyBlue"]skyliner33v[/COLOR], @[COLOR="Magenta"]nerdyblonde[/COLOR], @[COLOR="DeepSkyBlue"]pjgraber03[/COLOR], @[COLOR="DeepSkyBlue"]electrikjesus[/COLOR], @[COLOR="DeepSkyBlue"]bracketslash[/COLOR], @[COLOR="DeepSkyBlue"]Vortex1969[/COLOR], @[COLOR="DeepSkyBlue"]death2all110[/COLOR], @[COLOR="DeepSkyBlue"]Dark_Eyes_[/COLOR], @[COLOR="DeepSkyBlue"]Men_in_black007[/COLOR], @[COLOR="DeepSkyBlue"]BitOBSessiOn[/COLOR], @[COLOR="DeepSkyBlue"]blueyes[/COLOR], @[COLOR="DeepSkyBlue"]asianflavor[/COLOR], @[COLOR="DeepSkyBlue"]genesixxbf3[/COLOR], @[COLOR="DeepSkyBlue"]nicholaschum[/COLOR]
Huge thanks to all members of Cyanogenmod for the source.
Also a huge thanks to Chainfire, DirtyUnicorns, NamelessRom, SlimRoms, EuphoriaOS,
CRDoid, OmniRom, Temasek, AICP & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thanks to @[COLOR="DeepSkyBlue"]skyliner33v[/COLOR] for making our wallpaper & optional boot animations, @[COLOR="DeepSkyBlue"]electrikjesus[/COLOR] for making the current boot animation as well as others,
@[COLOR="DeepSkyBlue"]pjgraber03[/COLOR] & @[COLOR="DeepSkyBlue"]electrikjesus[/COLOR] for developing and maintaining our website,
@[COLOR="DeepSkyBlue"]death2all110[/COLOR] for developing the Bliss Wallpapers app, and @[COLOR="DeepSkyBlue"]nicholaschum[/COLOR], @[COLOR="DeepSkyBlue"]genesixxbf3[/COLOR] and @[COLOR="DeepSkyBlue"]tobitege[/COLOR] for the OTA xml generator.
Thanks to @[COLOR="DeepSkyBlue"]Kryten2k35[/COLOR] for the original source of the OTA app.
We do NOT ask for or expect any donations from users.
If someone takes it upon themselves to donate to us, of course it will be appreciated,
and all funds will be used to pay our server fees.
If someone does choose to donate, our PayPal link is below.
PayPal Link
Special Thanks @transi1 @monster1612 @Hashcode
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using Bliss! We appreciate each and every one of our users!
XDA:DevDB Information
Bliss Rom by Team Bliss for KFHD 7 - tate, ROM for the Amazon 7" Kindle Fire HD
Contributors
electrikjesus
Source Code: https://github.com/BlissRoms-Devices/android_device_amazon_tate
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Beta
Current Beta Version: 06.16.17
Beta Release Date: 2016-06-17
Created 2016-06-17
Last Updated 2016-06-19

Reserved
GUIDE, FAQ and Useful Links
Much of what follows applies to many ROMs. If you have suggestions for things to be added to this guide or find any errors then please let me know.
Purpose and Rules of XDA
XDA is a development site. It is for learning and sharing. It is not here to "provide" apps or support to users. Most of the people that develop or help or support do so in their free time. No one "owes" you anything. You are not "entitled" to anything. Those that help others, are polite and try to help themselves will be more likely receive helpful and polite assistance.
Rule number one of XDA is : Search
Other rules include:
Be respectful
Be tolerant
Be helpful
Don't be an ass
Q&A or Dev Thread?
There is a separate development thread and Q&A/Discussion thread. Right now, I am happy for you to report all issues in the development thread.
But as it is a development thread, you should provide logs where ever possible and only report bugs if you have clean flashed. Telling others there may be an issue if you dirty flash is acceptable but please word it as such not a bug.
A little banter is accepted in the development thread, but please don't turn the thread into a chat room. Let's keep it fun but not so long nobody can be bothered to read, otherwise I'll have to revert to using the Q&A.
The Q&A is still there and available and is more "free".
Flashing
You should clean install for best results. If you "dirty flash" then at least wipe cache and dalvik/ART and you MUST provide logs with any issues.
Clean v Dirty Flash
There are a number of interpretations of clean flash. In recovery you should factory reset or wip everything except internal storage. This will wipe your apps and most app settings.
Whilst there are ways of backing up your settings they are not recommended because they can cause issues when there are changes to the ROM which affect how settings are stored or recorded. Do not restore system data: this often leads to forced closes and constant error messages.
You can use a backup app like Titanium Backup or Parcel. Sometimes restored apps can cause issues, and it is better and cleaner to re-download them, although not everyone has the time or inclination to do this.
If you do not wipe as per above, then you are dirty flashing. This is quicker and often works. But because things are left behind from the previous flash this can result in weird issues. When you dirty flash you really should wipe cache and dalvik/ART, so that there aren't residual
Reporting Issues
Before Reporting Issues
If you have issues with your new flashed system there are a few things to do before you report them.
First, if you have dirty flashed then try a clean flash to see if the issue remains - many issues are cleared this way. Also, it is very difficult to pin-point certain issues after a dirty flash.
Also, if you have Xposed installed then remove that before reporting. This is because Xposed can change things deep within the OS and make things behave differently, which in turn makes it very difficult to troubleshoot and resolve issues. This is Xposed hate - many devs require this and will not offer any support if Xposed is installed.
Reboot. It's surprising how many issues can be resolved by this simple step. Especially if an app is misbehaving or using a lot of battery.
How to Report An Issue
The biggest bugbear of those trying to help with issues is when they are not properly reported and require to have the same questions answered over and over. The circumstances may require different information, but here are a few common items to consider posting:
Version. Often people miss this and are reporting something that was solved days or weeks ago. Others say "latest" when it may not be. Quote the version number and/or build date.
Firmware. Again, quote the date or source.
GApps. The GApps version can affect which version of Google Play Services and PlayStore, amongst others that are used. Whilst often GApps can be "out of date" without any issue, when there is a lot of development by CM this can be very relevant.
Whether you clean or dirty flashed.
A log. Necessary if you dirty flashed, very useful even if you clean flashed. See below for how to do this.
How to replicate the issue. The more specific about how the issue arises and when, the more likely you are to get a quick resolution. If no one can replicate the issue it is unlikely they can resolve the issue.
How to Take a Log
This is an excellent guide.
Some kernels have their own log/bug report option to make things easier.
Useful Links
Google and the XDA search bar are your friends.
Whatever you want to ask or find, it's probaly already there. This is why you often see replies just saying "Search!"
XDA: RULES - MOD HELP - SUMMED UP 1 - SUMMED UP 2 - BEST WAY TO GET A LOG
Frequently Asked Questions
No one answered my question.
Maybe no one has read it yet - you may need to give it time. Maybe no one knows the answer yet. Have you already tried to solve the issue? Were you polite? Did you give enough information? There is no need to keep bumping your post.
Which folder does the OTA file get downloaded to? Is it the full file or just the incremental update? Are there nightlies?
/sdcard/Download and it's the full file. They aren't nightly but they are normally very frequent.
Does BlissPop support Layers / RRO?
No. It has the CM theme engine.
Which kernel is best for....?
Stock is really quite good, so I'm not going to suggest any others, as there aren't many now and are easy to find on XDA. So much depends on you: your setup, apps, usage, signal. The list goes on. The real best way to find out is try them for yourself; give each one a few days to settle and you can observe battery usage, smoothness, speed, tweakability etc. But there is no Holy Grail kernel - one that gives the best of everything for everybody. "Performance" and "battery" aren't mutually exclusive, but most kernels are biased towards one or the other. Kernel governors and hotplugs also have an effect. If you are interested in a kernel, read some of the kernel thread.
One last point. When there are changes from CM the date and commits of a kernel can be important so the kernel and ROM aren't out of sync.
How is Battery Life
This often gets asked, but there is no clear answer that suits everyone. So lets start of by saying the team finds battery life to be very good.
There are however many things affecting battery life. Your apps, settings and signal all have a big effect. As does how often your apps are updating and whether over wifi or mobile data. Additionally, which kernel and it's settings also have an effect. As does screen brightness. Certain social and messaging apps can have a huge drain. How often you flash a new ROM has a big effect too. Ideally, from a battery life perspective, you should allow everything to settle and go through a couple of charge cycles. With the frequency of BlissPop updates I have never achieved this!
So every user will have different battery life and typical screen on time. Make sure when doing comparisons you really do it on a like for like basis.
If you want to investigate battery usage, consider apps like Wakelock Detector (WLD) and Better Battery Stats (BBS) as well as GSAM Battery Monitor. These will often pinpoint where battery is being consumed and what is waking your device. Quite often you will see an app misbehaving which can often be resolved with a simple reboot.
?
?

Reserved
MOST RECENT UPDATE
BETA Bliss Rom 6.4 - 06-17-2016 Build is LIVE!
Here we are with another update for Bliss ROM. Big improvements all around, OTA is working now, and a few new things to help make things pretty. Builds are all uploading now, so I recommend a clean flash, and from here, the OTA app should work fine.
At this point, I think the ROM is pretty stable, but it will stay in BETA until we have enough feedback and positive reviews of the ROM.
Bliss Maintenance folder for tate
BUILD CHANGELOG
Since the first release yesterday, I only worked on getting some of the selinux issues ironed out. I will push whatever changes I missed to our device repo soon. Other than that, the rest of our devs have been hard at work, squashing bugs and adding some new features, so check the changelog in the About Bliss app for more info
BUILD HINTS
Optimizations - Graphite, Pipe, Bliss_03, UKM, QCOM_Bionic, ROM - 4.9, GCC - 4.9-Linaro, Kernel - Linaro 4.9, auto-wipe of caches after flashing!
Gapps 6.0(!), backup/restore might work, not sure yet.
Please do NOT report missing features or repeat reports of issues that are known!
Reminder: We will not add any other camera, do not ask for it, flash it yourselves.
Flashing Instructions:
FIRST revert theme to stock theme before flashing (just to be safe)!
Make a nandroid backup!
Flash ROM + gapps + Touch_fix, then wipe cache and dalvik
CM's Superuser is included, do not flash SuperSU!
Open issues:
A few CM related issues might exist.
Some features might be missing, which is to be expected.
Camera does not work right yet.
Will not allow user to select "Allow" in permissions dialogs.
Some issues may be present with Wi-Fi when switching networks.
Other bugs/issues in CM-maintained packages?
Sidenotes: please do not quote the whole update post, just hit the thanks button!
No reports for issues with xposed installed, please.
Enjoy flashing!

OK, Maybe I'm just used to how things go in the LG G2 forums, but I would have expected a comment, or some feedback by now I assume. Maybe that isn't how things work over here, but let's see if we can give it a try.
If you try out this ROM, please also try to let me know what you think, or if you run into any issues and they weren't listed with the release notes, please also share those with a Logcat or kmsg if needed.
Thanks folks!

electrikjesus said:
OK, Maybe I'm just used to how things go in the LG G2 forums, but I would have expected a comment, or some feedback by now I assume. Maybe that isn't how things work over here, but let's see if we can give it a try.
If you try out this ROM, please also try to let me know what you think, or if you run into any issues and they weren't listed with the release notes, please also share those with a Logcat or kmsg if needed.
Thanks folks!
Click to expand...
Click to collapse
The community here is pretty small nowadays (maybe ~15?). Other than that, you'll notice the frequent ones around here.
Though I haven't tried the ROM on my kindle, it ran superbly great on my N4! Thanks for the bringup to the device and will try it soon on my Tate. Greatly appreciated!!
Sent from my SM-G935T using XDA Labs

electrikjesus said:
OK, Maybe I'm just used to how things go in the LG G2 forums, but I would have expected a comment, or some feedback by now I assume. Maybe that isn't how things work over here, but let's see if we can give it a try.
If you try out this ROM, please also try to let me know what you think, or if you run into any issues and they weren't listed with the release notes, please also share those with a Logcat or kmsg if needed.
Thanks folks!
Click to expand...
Click to collapse
I'm going to see if I can port this over to the 8.9". so far, I'm planning on reverting the kernel back to 3.0.72+ to try to fix the camera issues; other than that, I don't expect too many modifications to be made in the near future.

monster1612 said:
I'm going to see if I can port this over to the 8.9". so far, I'm planning on reverting the kernel back to 3.0.72+ to try to fix the camera issues; other than that, I don't expect too many modifications to be made in the near future.
Click to expand...
Click to collapse
Let me know how it works out on the Jem We might have to follow suit on the Tate if so.

I for one would like to thank you this ROM and your work, it is truely welcomed IMHO. I bought my sons a pair of ASUS tablets not long ago and have been considering getting myself one, but this ROM may save me from having to do that! :good:
I have been running it for almost a week, though my time with the tablet has been really limited due to work. And although I have not taken logcats the only issues I have had at this point are interface slowdowns/sluggishness (reduced after tweaking performance settings) and force close of Settings when attempting to access Settings/Bliss Settings/Buttons.
I will try and get a logcat on the Settimgs issue.

Quick Fix for camera:
http://forum.xda-developers.com/kindle-fire-hd/7-development/cm13-quick-camera-fix-t3421847

Looks like my latest test build fixes the issue with accepting permissions Here is a link to my g-drive folder with that build: https://drive.google.com/open?id=0B2hjuvxuncgYS3Q0bGk5MHpGWjA
Clean flash is recommended. I used OpenGapps 06-13 with no issues or conflicts. Camera still doesn't work, but we are all working on that (Thanks to @alexander_32 & @monster1612 for all their work too!!!) Will be making another post hopefully soon with more news

Thanks to the bliss team and cm team and all who had a hand in this ROM. PROPS I luv this ROM its working great took about 15 mins to boot but so far running great. Camera doesn't work we all know but I never use it on Tate so no luv lost there. found one problem at first when I clicked a link it rebooted no clue why but hasent done it again so far fingers crossed.outher then that great work guys.I'll report any bugs I find along the way in a few days.

The ota update doesn't appear to be working. It says update available but shows as null and when press download a message saying URL incorrect contact ROM developer.
Sent from my Amazon Tate using Tapatalk

Yeah I get that to. And google fc and a lot of random reboots and it takes 8 to 10 mins to boot each time.I'm on it now still like the ROM.

trulyparis said:
The ota update doesn't appear to be working. It says update available but shows as null and when press download a message saying URL incorrect contact ROM developer.
Click to expand...
Click to collapse
This is because we are still in beta. OTA will work properly once we move to official.
xrebelhellx said:
Yeah I get that to. And google fc and a lot of random reboots and it takes 8 to 10 mins to boot each time.I'm on it now still like the ROM.
Click to expand...
Click to collapse
When I use an older opengapps, like 06-03 for instance, I get 0 errors from play store or play services.

SUPERSU INSTALLATION

@electrikjesus gave me a permission to post this.
UPDATE (M4B30X)
https://www.androidfilehost.com/?fid=385035244224390121
Installation: Full wipe/Flash ROM + Open GApps
Source: https://github.com/alexander3244/android_local_manifest/blob/bliss-mm/local_manifest.xml
https://github.com/alexander3244/android_local_manifest/blob/bliss-mm/roomservice.xml
If you have a jem device, feel free to use my source and post a build in the respective thread.

alexander_32 said:
@electrikjesus gave me a permission to post this.
UPDATE (M4B30X)
https://www.androidfilehost.com/?fid=385035244224390121
Installation: Full wipe/Flash ROM + Open GApps
Source: https://github.com/alexander3244/android_local_manifest/blob/bliss-mm/local_manifest.xml
https://github.com/alexander3244/android_local_manifest/blob/bliss-mm/roomservice.xml
If you have a jem device, feel free to use my source and post a build in the respective thread.
Click to expand...
Click to collapse
Works great. Thank you much.

SAME BUILD (M4B30X) WITH 3.0.101 KERNEL
https://www.androidfilehost.com/?fid=385035244224391780
Installation: Full wipe/Flash ROM + Open GApps
I was able to just swap kernel sources and after deleting zip package, boot.img and some files it took only 20 minutes to get a build (because more than 90% was done already).
So, you can now try to find the difference between first build (3.0.72 kernel) and the second one (3.0.101 kernel).

alexander_32 said:
SAME BUILD (M4B30X) WITH 3.0.101 KERNEL
https://www.androidfilehost.com/?fid=385035244224391780
Installation: Full wipe/Flash ROM + Open GApps
I was able to just swap kernel sources and after deleting zip package, boot.img and some files it took only 20 minutes to get a build (because more than 90% was done already).
So, you can now try to find the difference between first build (3.0.72 kernel) and the second one (3.0.101 kernel).
Click to expand...
Click to collapse
Nice. Getting some occasional screen tearing, but otherwise works well.

Great rom guys, it's fast (not a rocket, but fast, yeah), all that i need works, the sound mods works too, really! And this baby is really a sound machine, powerful until now, and i like this! So many thanks to all devs that i already tested a rom!

General Pixel watch-faces compatibility with GW4

As many of you may be aware, the pixel watch faces have been released as an .apk installable through adb.
The watch faces offer basic functionality right of the bat on the GW4, however, many sources online detailing the ability to install this on WearOS 3 devices fail to mention the short comings of the app.
I have been able to install without issues but I have encounter a number of bugs that come from installing on the GW4.
- AOD fails to update the minute mark unless awoken manually.
- Activating AOD by covering the display with your hand while on an app, results to a frozen like state instead of showing digital clock and blur like on a standard Samsung watch face. (fixed by "waking" the watch again)
- May or may not consume more battery due to bugs. (so far it seems like battery life seems slightly lessened)
- Some complications do not work.
- PLEASE mention in the thread if you have seen any other bugs.
I assume that these bugs also occur on the GW5 due to running the same chipset and possibly identical software.
From the bugs it seem that the watchfaces apk is not meant to work as a standalone app, and of course requires dependencies from the Pixel watch software.
Im a bit disappointed that big android media websites (including the XDA article of the watch faces) fail to mention this even after numerous days after releasing the articles. A lot of these article websites are quick to bring out content without testing what they put out there..
I have been keeping an eye of these issues with no apparent update on the bugs.
Hoping a dev picks up the apk and is able to develop a fully working port for the galaxy/ wearOS 3 watches.
If anybody find any info please update the thread!

Your observations are all correct. I'm quoting myself from another thread on here about this issue, because I dug a little bit into the logcats as I was running the Pixel Watchfaces on my Galaxy Watch 4 and I noticed these errors right around the minute mark, when the AOD should have been updating:
Code:
10-16 12:41:02.507 313 318 E [email protected]: Error opening event_count for wakeup59: Original kwl [Path]=../../devices/platform/10510000.dwmmc2/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wakeup/wakeup59: Permission denied
10-16 12:41:02.507 346 346 E audit : type=1400 audit(1665916862.503:672): avc: denied { read } for pid=313 comm="Binder:313_2" name="event_count" dev="sysfs" ino=39047 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R890_11_0004 audit_filtered
10-16 12:41:02.509 346 346 E audit : type=1400 audit(1665916862.507:673): avc: denied { read } for pid=313 comm="Binder:313_2" name="max_time_ms" dev="sysfs" ino=39052 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R890_11_0004 audit_filtered
10-16 12:41:02.510 346 346 E audit : type=1400 audit(1665916862.507:674): avc: denied { read } for pid=313 comm="Binder:313_2" name="wakeup_count" dev="sysfs" ino=39048 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R890_11_0004 audit_filtered
10-16 12:41:02.510 346 346 E audit : type=1400 audit(1665916862.507:675): avc: denied { read } for pid=313 comm="Binder:313_2" name="total_time_ms" dev="sysfs" ino=39051 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R890_11_0004 audit_filtered
10-16 12:41:02.510 346 346 E audit : type=1400 audit(1665916862.507:676): avc: denied { read } for pid=313 comm="Binder:313_2" name="expire_count" dev="sysfs" ino=39049 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R890_11_0004 audit_filtered
Now I'm not an Android dev, just have superficial ADB and Linux knowledge, but the Error opening event_count for wakeup59 with a Permission denied error seems to indicate Permission issues, possibly regarding a wakelock event, which the app would have to execute in order to run its code to update the watchface. Since it's not allowed to wake the CPU from a sleeping state, it never updates
Further, granting all user-grantable permissions for the Pixel Watchfaces through pm grant in the adb shell doesn't change this behaviour

There is a graphical glitch on dome watch faces some number are not displayed properly loke the numbers for 35 to 55 on the attached watch face

hoss_n2 said:
There is a graphical glitch on dome watch faces some number are not displayed properly loke the numbers for 35 to 55 on the attached watch face
Click to expand...
Click to collapse
I tried shrinking the picture of these numbers and it seems to have solved the problem
com.google.android.wearable.watchface.rwf_1.0.87.473139107_concentric_fixed_sign.apk
drive.google.com

123哆3 said:
I tried shrinking the picture of these numbers and it seems to have solved the problem
com.google.android.wearable.watchface.rwf_1.0.87.473139107_concentric_fixed_sign.apk
drive.google.com
Click to expand...
Click to collapse
This works great on my GW5 44mm, thanks for taking the time to fix it!

123哆3 said:
I tried shrinking the picture of these numbers and it seems to have solved the problem
com.google.android.wearable.watchface.rwf_1.0.87.473139107_concentric_fixed_sign.apk
drive.google.com
Great , it worked ! Thanjs allot
Click to expand...
Click to collapse

seriosbrad said:
This works great on my GW5 44mm, thanks for taking the time to fix it!
Click to expand...
Click to collapse
Hey, did it fix the AOD issue for you?

Does it work on the Galaxy watch 4 classic or just the normal Galaxy watch 4

hanisir3 said:
Does it work on the Galaxy watch 4 classic or just the normal Galaxy watch 4
Click to expand...
Click to collapse
It is working with me in galaxy watch 4 classic

hoss_n2 said:
It is working with me in galaxy watch 4 classic
Click to expand...
Click to collapse
Can you say how you did it step by step
I would really appreciate it

How to apoly this watchface? How to sideload?

klisza1993 said:
How to apoly this watchface? How to sideload?
Click to expand...
Click to collapse
Check this thread:
https://forum.xda-developers.com/t/...d-workarounds-for-galaxy-watch-4-gw4.4379825/

any trick for AOD FIX?

123哆3 said:
I tried shrinking the picture of these numbers and it seems to have solved the problem
com.google.android.wearable.watchface.rwf_1.0.87.473139107_concentric_fixed_sign.apk
drive.google.com
Click to expand...
Click to collapse
Why is your apk flagged by VirusTotal?

rgrapow said:
Check this thread:
https://forum.xda-developers.com/t/...d-workarounds-for-galaxy-watch-4-gw4.4379825/
Click to expand...
Click to collapse
idk, I just decompiled the apk file form ApkMirror, modified the image and recompiled it. If you don't trust me, you can do it yourself.

Did anybody get the AOD to work?
Love the watch face but can't really use it if I can't rely on the watch to show the correct time

Below Site is reporting malware in above Google drive file
VirusTotal
VirusTotal
www.virustotal.com

123哆3 said:
I tried shrinking the picture of these numbers and it seems to have solved the problem
com.google.android.wearable.watchface.rwf_1.0.87.473139107_concentric_fixed_sign.apk
drive.google.com
Click to expand...
Click to collapse
Well Pacific and Big time and other watch faces aren’t working

Don't use the original, this is a better version of the original concetric watchface and works flawlessly on my GW4 classic. Rebember to give the developer the thumbs up in forum and in playstore
[CLOSED] Mod edit...
Mod edit: Content of opening post removed on request of thread owner and all his posts in this thread deleted. Oswald Boelcke, Senior Moderator
forum.xda-developers.com

Installed it a few hours ago, normal version without the fix for the concentric face. Battery seems to drain equally if not a little slower than with original faces