Hi everyone,
As many of you would have known, despite USB Host functionality being present in ICS, USB DACs have yet to be supported on our devices. This issue has also been starred by more than a thousand people on Google's site but still has not been noticed. (Link here: http://code.google.com/p/android/issues/detail?id=24614&sort=-stars&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars)
Quoting a fellow XDA member: If Google did their work then we could use relatively cheap USB DACs with our Android phones and enjoy great music sound quality, no matter which cheap DAC/DSP the manufacturer has seen fit to include. Now with ICS this is a simple software fix, which makes it all the more irritating (someone has managed to add support for these in a Nook Colour kernel that works with CM9).
Right now, we can bring it up to a real Google Engineer while they visit my school (I have no idea how my school manages to be on such good terms with Google). All you need to do is help to vote this issue up so it gets the first pirioty to be asked. Perhaps then, we will get a chance to put the spotlight on our issue.
Vote the issue up here: http://www.google.com/moderator/#15/e=1fc068&t=1fc068.40&f=1fc068.665f43&q=1fc068.665f43
Please vote this up and share this out to your social networks. Lets make Android a even better operating system for all!
Quick update: Since this was posted it has risen in priority!
Please continue to give your support so our issue will be answered! (And remember to tell your friends to help too!)
Bumping this thread up!
Please continue to give your support on this issue! (And of course, remember to tell your friends to help too!)
Can I give it more than one vote? haha ):
It would be nice to have DAC/AMP support on Android by default.
Hi buddy,
thank you for the information and discussion! I'm more of a business head than engineering but I am a lossless guy who loves his media players. Can you tell us more about what kind of things would be possible if Google enables this support?
So we all know that sometimes the stock standard camera app aren't the best , and that sometimes other stock cameras from other phones are better , or take better photos.
And since we have some very skilled developers on this and other forums, they have been able to port these stock app to work on multiple phones from different brands.
My goal is to have a list of all these apps . This thread will try to keep track of such apps, by being uploaded to a website , or link to the actual forum thread.
But I need the communities help, if you know or would like me link your app, one which works across multiple brands, please pm me or link it in this thread.
so here goes
List : Backup before trying any of these, you have been warned
Razr m camera port Developer: unknown
works on: 4.0
Lg Optimus G ported (may not work, make sure you make backup)
Developers: Defcomg, feav
works: ics & jb different versions
Huawei p1 cam mod
works: ICS, maybe jb?
Developers: defcomg
Click to expand...
Click to collapse
Ps: If i have linked your port and have not mentioned you as the developer, or I cant find the orignal developer , please let me know ,no insult ever intended
Pps:if I have listed your port and you want the link removed i will be happy to do so, just send me a p.m
Thank you list:
Defcomg, feav
Click to expand...
Click to collapse
Reserved for possible future need:
I also hope this thread helps developers find other developers who are good at modding stock camera apps, and which they can then help each other , and in turn make more ports of a better camera apps : The Dream
great idea
Thanks ,yeah lets just hope it stays active long enough to get a sticky, this would actually make it so much easier to try out camera ports that people may not ever know about
Greeeeaaat
Inviato dal mio Nexus 4
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....)
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch off/on - you switching off one sim and then can't bring it alive even after reboot.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
ViperOS lacks updates. Otherwise, it's a great rom really
Egyptiandroid said:
ViperOS lacks updates. Otherwise, it's a great rom really
Click to expand...
Click to collapse
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
comunity said:
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
Click to expand...
Click to collapse
Then, can you suggest a ROM that has the fewest bugs, besides great battery backup?
Egyptiandroid said:
can you suggest a ROM that has the fewest bugs
Click to expand...
Click to collapse
it was done in my previous message - DotOS. One more choice - LOS from HigwayStar. As I found these twos are both without "sim switch off/on" bug. But they have some other bugs (f.e. dark video).
Now I switched from DotOS to HigwayStar because HWS still working on it, and DotOS is freezed.
comunity said:
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch of/on - you switching of one sim and that can't bring it alive.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
Click to expand...
Click to collapse
It amazes me how anyone can post anything on this forum...
Can't you just dislike this post?
It amazes me how anyone can post anything on this forum.
Click to expand...
Click to collapse
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
comunity said:
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
Click to expand...
Click to collapse
If you're so dissatisfied, don't change ROM's then.
Hey. There's a good bugless(ughh) ROM it's called stock ROM. If you're not satisfied You can actually tell anything to them cuz you have paid for it. Have you tried that?
If you're so dissatisfied, don't...
Click to expand...
Click to collapse
my question was not about my satisfaction. it was about statistics - how many bugs from my list and which ones have every ROM published here.
I don't required recommendations or suggestions. I will be glad to see simple answers about each of 12 item - bugs exist or not. from anyone who had test them by himself )
Let me show answer example that I'm expected on:
LOS 14 from HigwayStar
fast charge - working but haven't indicator in status bar.
root - Magisk 16 built in ROM installation script
NFC & safetynet test - working, my payments were accepted lot of times. installing xposed module broke safetynet test (
VOLTE - supported, but I can't test bcz of absence 4G
sim switch of/on - working.
flight mode - after switching it off you can make new calls without any bodymovements.
led indicator - working out of the box. you can setup 16 mln colors, blinking speed and delays.
double tap to wake up - working from the box.
one key (energy saving switcher on left side) - may work, but ROM author decided to switch it off in latest release
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo especially for dark scenes.
finger print actions - work after reswitching navigation buttons, even without registering FP.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use. simply calculation issue, bcz battery isn't really draining by sleeping BT.
it's not an example. it's my real report about ROM that I'm currently using.
this report may be also about my DotOS usage, but i switched from DotOS to HWS because DotOS - frezed, and HWS - still under development.
Do you know what all bugs(super annoying) the stock ROM have? Did you bust into Lenovo forum and post things like this?
If yes then wait for their update (rip in advance)
If no then go try that and tell me if somebody gives a #@!*
This ROM development is nothing you own. It's developer's hobby which they do in their free time. So creating a thread like this with such a demanding attitude is crossing the line.
You said about the long post on every ROM like intro and blah. Blah. You should read them.
* We are not responsible for bricked devices, dead SD cards,
* Third World 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 us for messing up your device, we will laugh at you.
If you think you can make something better do it by contributing towards ROM development.
Wow! So much angriness for one simple question! )))
Dear Senior Member Siva Mk, let me ask you why you are wasting your time and writing to me one more "long post",
You said about the long post on every ROM like intro and blah. Blah. You should read them.....
Click to expand...
Click to collapse
instead of provide us answers for my question, if you have any one?
You are right - no one owes nothing to nobody! at this and all other forums.
I DON'T REQUIRE from somebody, and from ROM developers especially - any warranties and immediately fixing all existing and not existing bugs. Please reread my very first sentence in first post.
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning.
Click to expand...
Click to collapse
I simply want to get help from other users (or ROMs' authors) and collect in one place info about ROMs critical bugs, which maybe helpful for all of us here, to choose ROM, most appropriate for himself.
I have a question - I had asked it. On my previous post I gave an example of answer that I expected. If you haven't such answer - please don't grow Universe entropy and simply ignore my posts and topics. Let we all stop this flooding, and will concentrate on help one to another
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
medwatt said:
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
Click to expand...
Click to collapse
He's just another one who wants attention
medwatt said:
And who are you
Click to expand...
Click to collapse
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Nice thread, Sorry there is no bug-less rom available for P2 right now ?
For me the only rom that has no bugs is stock mm 6 even stock nougat for me has a bug that Lenovo can't solve till now linegue os by HWS is the best with minor bugs that does not affect daily drive
comunity said:
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Click to expand...
Click to collapse
Dude seriously if all people have a attitude like yours developers will just stop building roms altogether.