Hello together,
have a small problem with my development environment..
A closer look on the Android Debug Bridge, to the logcat feature with plug an Galaxy S3
to the Computer, the Logcat shows no outputs in long format, and the big problem with
that device is the ActivityManager of Logcat, that shows no outputs.
become on Logcat ActivityManager that output -> sometimes only PID or mDVFSLock.acquire...
I dont know whats this mDVFSLock.. hast Sasmung block the ActivityManager Feature with
Galaxy S3? with my S2 everything runs smoothly, no problems on Logcat Activity Manager.
I need the Output Infos of the Logcat Activity Manager.
Knows everybody where ist the Problem with that device or give it a trick or tweak/script for
that function, I hope an experienced developer can help me with this problem.
thanks in advance.
greetings
I solved that Problem. Can be closed.
greetings
A large reason for this section to exist is for people to share development. If you solved your issue, at least share what the issue was and how you went about solving it so the next person can benefit from your experience.
garyd9 said:
A large reason for this section to exist is for people to share development. If you solved your issue, at least share what the issue was and how you went about solving it so the next person can benefit from your experience.
Click to expand...
Click to collapse
I concur, I have searched high and low to get the correct output, The only answer I found was that the activity name output is disabled on consumer devices except for Dev phones such as the Nexus range, I know this is false as my HTC desire with its stock firmware outputs the correct strings.
This would be extremely helpful with the icon pack I am currently building.
so please share.
garyd9 said:
A large reason for this section to exist is for people to share development. If you solved your issue, at least share what the issue was and how you went about solving it so the next person can benefit from your experience.
Click to expand...
Click to collapse
sorry, you right men.
i think its nobody interesting here, but like to help where I can..
voodooboy3000 said:
I concur, I have searched high and low to get the correct output, The only answer I found was that the activity name output is disabled on consumer devices except for Dev phones such as the Nexus range, I know this is false as my HTC desire with its stock firmware outputs the correct strings.
This would be extremely helpful with the icon pack I am currently building.
so please share.
Click to expand...
Click to collapse
I know the only good.
i show yesterday on the googles APIs (android.app) and found the Class ActivityManager,
and search it for the Output -> mDVFSLock, but can not found.
later i think that can be a Rom Problem (or with Java Code @Class) and have decided to
flash a non-manufacturer firmware (or based Custom Rom).
Solve:
I try a Cyanogen Mod and a few AOKP Roms, and see that the Output works here fine.
With Samsung's Stock Jelly Bean Stock Rom (or Custom) it does not work. I think Samsung block
it, in the Classes or must tweak, i dont know to 100%, but CM or AOKP Rom other,
and had a few Tweaks more integrated.
try for your Device a CM 10.1 or AOKP Rom with Android 4.2.1 and hope you reach your goal.
Best Regards
Ok thanks for the update I thought that may be the case.
Related
Anyone else not getting sound on a call from Viber? People can hear me...I can't hear them.
Hi,
This is a member of Viber's development team.
@spielnicht - what device do you have? Do you have stock or custom ROM?
Which Viber version?
Thanks in advance.
Viber Team
Viber no sound on GARMIN ASUS A10
Hullo,
same problem here. I got a GARMIN ASUS A 10 with Android 2.1-update1 and VIBER is 2.1.2 version
Many thanks for any help
leo
This problem can have 2 different reasons:
1. The device is not officially supported by Viber. Unfortunately, that's the case of GARMIN Asus...
2. Sometimes Custom ROMs may be the source of this problem.
Android GARMIN-ASUS: Why Not?
Hi there and thank you very much for your reply.
To be very honest with you, I don't see clearly the point why it isn't.
I know many, many GARMIN-ASUS happy users here in Europe who would be very happy to use your excellent peace of App along with all the other working ones...Actually, it is the first time I'm able to fully install an App from the Android Market which is not properly working on my device...with no prior information :-( ...By the way, the device is (apparently) working fine with all other Viber features (especially texts, which is already quite nice)...and if there are no special (technical? commercial?) reasons, I wonder why you cannot work out this GARMIN-ASUS related sound issue as well...
Have an excellent day from Europe!
leo
Well,
As a company, we naturally have limited resources. We wish we could develop full compatibility for all devices out there, but unfortunately we can't.
We're looking at the global market shares of Android devices, and GARMIN-ASUS is one of the least popular ones (even though we acknowledge that it is not a "bad" device, etc.)
I didn't say we would neglect it, I just said it might take sometime before we attend to test it fully. In the meanwhile, if indeed you know so many Viber users who are longing for full compatibility, you may gather them and jointly open many ticket to our support team. The more tickets, the bigger chances that we will prioritize this task
Here's the link to our support team: http://support.viber.com
no entry for device compatibility or similar
Well,
I'd like to do that but, apparently, the wizard for support queries doesn't allow me to do that (I mean, either to me or to the thousands of other Garmin-Asus all around ) as, apparently, there is no- entry for such an issue.
leo
You can find a way to simply open an individual ticket and then write your request (again - please note that only if it is a joint request by many users, then it will have effect).
Hello, Thank you Viber Team for replying to the issues in this thread.
I recently (yesterday) installed Viber on my Galaxy S2 X - Telus (Canada) and it installed without issue. I can see friends and call / msg them but when I connect I can't hear any audio and they can't hear me as well. I have tried using both 3g/4g and wifi and received the same result.
Have you experienced this issue before? Is there a way for me to pull a log to determine the error. I'm just guessing but it seems lke the signalling is working properly and there is a problem establashing the rtp stream.
Thank you in advance for any assistance you can provide. I look forward to using this kick ass app
xluthor
I see you also sent me this via private message, so please see my response there
Same issue, galaxy S (I9000)
I m having the same issue in galaxy S, that I cant hear anything but the other person do hear.
I have stock rom, 2.3. With viber ver 2.1.2.
I also saw this model in the support list.
I also raised a ticket 2 days ago, which still in process of evaluation.
Suggestion required!
Thnx
Thanks for opening the ticket on our support site, our team will contact you back shortly.
The no-sound issue on some Galaxy devices is still being investigated by our dev team, and that is why tickets like the one you opened are important to us.
If a solution is found with your help and our support team, please share it here for all users to see
they can't hear me...
Hello, I got Samsung Galaxy S, custom ROM... rc4, Android version 4.0.3, VIber version 2.1.4
Everything is great but people can't hear me !
a few days ago I had another problem. I could not get the code, but it resolved after one day when I installed the second time, and now this....
I hope you help me about it ... Thanks
@dzgoran -
Might be a problem with the Custom ROM. Have you tested Viber on Stock ROM? Same problem?
why? i dont know.. I was downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1398223
tnx...
You'll need to contact that ROM's developers. Unfortunately we can't afford to fully support all Custom ROMs out there...
Viber Team said:
You'll need to contact that ROM's developers. Unfortunately we can't afford to fully support all Custom ROMs out there...
Click to expand...
Click to collapse
Also a problem with the sound of the Nexus S-I9023, no notice or sound. After unlocking I get a call or SMS.Viber 2.1.6,,android 2.3.6
Sorry for the English
Thenx
Hi,
I'm not sure I fully understood the problem... Kindly try to elaborate so I could assist.
Viber Team said:
Hi,
I'm not sure I fully understood the problem... Kindly try to elaborate so I could assist.
Click to expand...
Click to collapse
Viber does not allow me notifications received calls or messages.
After unlocking receive notification of missed calls or SMS.Viber 2.1.6 and 2.3.6, Android.
thenx
I understand now.
Please make sure of the following:
1. Your C2DM service is working properly. You can check it with Android developers themselves, and also make sure a Google Account is associated with your phone.
2. Do Viber's notifications work fine when your phone is not locked?
3. Have you tested this issue when connecting to different WiFi networks?
Hi !
I'm a newb on this forum, just got my first android device : a Samsung Galaxy Tab 2 7 inches...
I installed Galaxian-Soup's AOKP-Milestone 5 (as explained on this thread) and it almost works : the only problem so far has been that the microphone seems to be off...
Is this a known bug of AOKP ? I searched the web for this and found that some people have been having this problem on other devices...
Could anyone please help me ? I like the features of AOKP (specially the Rom Control thingie and the ability to hide the navigation bar), so I'm not really happy to go back to stock...
Thanks !
David.
Post issues with the ROM'S in the thread for the ROM's (the one you linked to)
Read the thread - multiple people have posted about this and it is a known issue.
Thanks for this (very constructive and helpful) comment.
I can't post in the original thread because (as I mentionned) I'm a noob on this forum and the rules forbid me to post in the developer areas...
Also, I have read the posts you are referring to (although after having posted this one). Let me rephrase my question :
Is this a known bug of AOKP or is it specific to the GT2 ?
Is there any way to get the (excellent) Rom Control thingie without flashing AOKP (and therefore keeping my mic working) ?
Cheers,
David.
davidp57 said:
Is this a known bug of AOKP or is it specific to the GT2 ?
Is there any way to get the (excellent) Rom Control thingie without flashing AOKP (and therefore keeping my mic working) ?
Cheers,
David.
Click to expand...
Click to collapse
known bug to device. Keep in mind they just created the device tree and the aosp Rom will have quirks. Answer to second question. No.
good day.
Thanks for your answer !
Let's hope that it get fixed soon, I miss my Google Talk video chats
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....)
hello,i come looking to inquire about how dificult in would be to create a rom, that would boot directly to a browser (prefferably iceweisel) to run a series of html5 based apps my developement team is working on. security would be a massive factor. any developers that might have input please contact me and i can better fill you in on whats happening.
side note
the team i mentioned in the original post is very good with java script and the like but actual mobile devices are out of their line of expertise. thank you in advance for any help.
plainstribune.com said:
hello,i come looking to inquire about how dificult in would be to create a rom, that would boot directly to a browser (prefferably iceweisel) to run a series of html5 based apps my developement team is working on. security would be a massive factor. any developers that might have input please contact me and i can better fill you in on whats happening.
Click to expand...
Click to collapse
Maybe you should think of creating a Launcher app especially if you want your soft be able to launch on a different devices.
I was doing research on android's Biometric authentication .As we know back in android Marshmallow(6.x.x) we got native support for fingerprint recognition/fingerprint authentication.Not too long samsung started giving new way to unlock devices iris scanner in s8/s8+ last year,so it's there own implementation in S/W and so main problem is you cant use their implementation in any custom rom because AOSP upstream does not supports it.Now from Android Pie onwards they deprecated FingerprintManager API and bring us new BiometricPrompt API,means we can use other methods like iris,face recognition and other methods for unlock/authentication.Probably iris or face recognition might come in coming pixel.
So my main point of making this post is to discuss about the existing device with proprietary sensors like in galaxy s8/s8+/s9/9+,note8/9,mi8,poco f1 etc etc! .
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
one thing i want mention:-i remember galaxy s5 released with android 4.4.x,which clearly dont have FingerPrintManager Api,but some smart dev xda managed to get that sensor working on android M based custom ROM .Sooooo maybe we will able to get our,s face IR working in next iteration of android pie.
I am learning about the android"s arch(also learning how to develop custom roms from scratch)
So devs on xda who have knowledge ,must share .i am always ready to learn
topics i refer for case study:-
https://source.android.com/security/biometric/
https://www.xda-developers.com/iris-scanners-native-support-android-p/
https://www.xda-developers.com/android-p-new-biometrics-api/
Help me out! I can only REPLY to threads, I can not POST such one!
thetripleS said:
Help me out! I can only REPLY to threads, I can not POST such one!
Click to expand...
Click to collapse
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Jaskirat singh said:
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Click to expand...
Click to collapse
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
thetripleS said:
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
Click to expand...
Click to collapse
Go here you get an idea which sub-forum you need to post
https://forum.xda-developers.com/poco-f1
.
RUPESHBW said:
Who are you to tell him what to do xda is about sharing tech knowledge there is nothing wrong in posting by new member. He giving his knowledge i had question with his argument above i got my answer. If you cant let other not demotivate.
Click to expand...
Click to collapse
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Jaskirat singh said:
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Click to expand...
Click to collapse
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
RUPESHBW said:
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
Click to expand...
Click to collapse
Its ok :/
Jaskirat singh said:
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
Click to expand...
Click to collapse
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it. But it's impossible to know for sure until actual official Pie comes.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
i was wandering around and testing some things with this device.
Yes! That ir receiver(sensor) IS behaving as camera (which is not a color sensor only takes IR as input)
For testing i used miui hidden settings app
Go to hardware test(CIT)>52.ir camera.
And voila! You can see output on screen what this sensor sees
NOTE:- you can open this CIT settings if you tap kernel version number times, but you won't get that "ir camera" option, soooo you have to install that app
Btw anyone working or creating device tree for this device?
Well yea xiaomi is notorious for not giving up whole source, that's kinda bytuh thing
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
frietketeltje said:
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
Click to expand...
Click to collapse
I'm not sure where to look, to be honest. This seems more like a back-end thing that makes development easier, rather than adding new features? At least that's what I remember.
Also note that I have no interest in custom ROM's personally; I'm modding stock MIUI instead.