android-4.2-jelly-bean

RecognitionListener in JellyBean Freezes if not spoken to immediately

ぐ巨炮叔叔 提交于 2019-12-03 12:19:51
A speech-recognition based app I am working on works well on all versions of Android starting from API 8 (Android 2.2). But on a Nexus S 4G (Android 4.1.1), RecognitionListener will simply halt for about 1 minute , then issue an ERROR_SERVER via its onError() callback. If spoken to within 1-2 seconds (of that onReadyForSpeech bleep), it will behave properly as expected. What changed in JellyBean that could explain this behavior? More importantly, is there a way to make it behave like in the older versions of Android? (i.e. keep listening, then issue ERROR_SPEECH_TIMEOUT if not spoken to within

How to develop custom status bar in android JellyBean 4.2.2

给你一囗甜甜゛ 提交于 2019-12-03 11:05:17
I want to develop customized StatusBar. I know i am not the only one with this requirement. But still want to know the opinions. After lot of search on StackOverflow, i found that people have modified status bar using tools but thats not i need. I am bit looking into the direction of developing of my own Status Bar with my own branding and layouting of the system icons. Also i have seen on Google play store about having a customized status bar app like omega status bar and couple more. I am looking for the same implementation. I also learnt that these kind of apps are installed on non-rooted

WiFi Direct on Android not working properly

别说谁变了你拦得住时间么 提交于 2019-12-03 08:53:31
I am trying to develop an app using wifi direct in android Jelly Bean 4.1.1. If p2p is enabled I immedialtely call mManager.discoverPeers(mChannel, actionListener); After that I am getting a call back to the onPeersAvailable(WifiP2pDeviceList) I am testing with 2 Samsung(Google) Nexus device and wifi direct is turned on on both. But this call back is returning an empty list of peers. But for instance if I click on the Search Peers button on the default wifi direct interface immedialtely the second device fires the WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION and this inturn calls

How to properly update a notification post api 11?

江枫思渺然 提交于 2019-12-03 07:03:30
问题 Before Notification.Builder came into existence the way to update a notification that was already in the notification tray was to call setLatestEventInfo() and then send the notification back through the NotificationManager.notify() call with an ID that matches the first notify() call you made. Now setLatestEventInfo() is deprecated with the message: Use Notification.Builder instead. But I cannot find any documentation about how to properly update a notification using Notification.Builder .

httpurlconnection is very slow on Android 4.2

删除回忆录丶 提交于 2019-12-03 06:58:14
I can succesfully connect, send and receive data by using httpurlconnection. But it takes very long time to load all the data on my phone (Samsung s4, 4.2) and on android 4.2 emulator. But it takes almost 1-2 seconds (which is very fast) to load pics on Android 2.3.x emulator. Faster than my galaxy s4 on http connection. I'm using AsyncTask and my code works fine on both. It is just slow on android 4.2s. I tried removing chunkedStreaming, keep alive, changing timeout values etc. but still no success Here is my code HttpURLConnection urlConnection = (HttpURLConnection) url.openConnection();

onEditorAction() is not called after Enter key has been pressed on Jelly Bean emulator

馋奶兔 提交于 2019-12-03 05:38:07
I'm having a problem with the behavior of the latest Jelly Bean emulator. I have several EditTexts in my app. An OnEditorActionListener provides special handling when a user presses the ENTER key on the keyboard. This worked up until ICS, but now on Jelly Bean the listener callback method onEditorAction() no longer gets called. Only a new line is inserted into the EditText . This can be reproduced this way: EditText testEditText = new EditText(context); testEditText.setOnEditorActionListener(new OnEditorActionListener() { public boolean onEditorAction(TextView v, int actionId, KeyEvent event)

Android OS bug with some devices running Jelly Bean/4.2.1 - TextView.setError(CharSequence error) Missing icon

好久不见. 提交于 2019-12-03 05:00:00
问题 Some, but not all, devices running Jelly Bean (4.2.1) appear to be missing the exclamation point error icon that should appear on a TextView (or, more commonly, an EditText ) that has an error set on it via TextView.setError(CharSequence error). The Galaxy Nexus definitely seems to be missing the icon. The effect is that the error status set by setError is only apparent when the EditText has focus. This makes setError(...) much less useful as it's often used to encourage users to return to

Questions about Google Play application assets encryption

六眼飞鱼酱① 提交于 2019-12-03 04:12:12
Starting from v4.1 Jelly Bean , Google has introduced a new application assets encryption feature for Google Play. Seems that there were some problems when upgrading apps consisting in persistent data being lost after reboot, caused by the change in apk directory (old one was /data/app , and now it is /mnt/asec ). So, when publishing (or updating an already published app) on Google Play, for OS 2.3+, Can I disable this option and publish an unencrypted application? What is the current state of the issue? Is there a workaround? Besides this problem, the idea of providing additional protection

Android - Show/Hide system bar on 4.2.2 (Nexus 10)

假如想象 提交于 2019-12-03 03:58:52
I got issue with Nexus 10 - 4.2.2. I was testing code below on Galaxy Tab 10.1 with 4.0.4 and it was working fine: try { Process proc = Runtime.getRuntime().exec(new String[]{"sh","startservice","-n","com.android.systemui/.SystemUIService"}); proc.waitFor(); } catch (Exception e) { e.printStackTrace(); } try { //REQUIRES ROOT Process proc = Runtime.getRuntime().exec(new String[]{"su","-c","service call activity 42 s16 com.android.systemui"}); //WAS 79 proc.waitFor(); } catch(Exception ex) { //Toast.makeText(getApplicationContext(), ex.getMessage(), Toast.LENGTH_LONG).show(); } But on Nexus 10

Jelly Bean Issue - wifiManager.getConnectionInfo().getSSID() - extra “”

有些话、适合烂在心里 提交于 2019-12-02 22:06:32
Hi all bug reporting for your information. link Problem details : The Code - wifiManager.getConnectionInfo().getSSID() The above code to returns the current SSID, it is returning the current SSID with extra quotations around it. For eg. the SSID internet is returned as "internet" . This is only seen on Jelly bean 4.2 using device Nexus 7. This bug is causing errors in our app as we compare the current SSID with the SSID that we are trying to connect too. The code wifiManager.getScanResults(); however still returns all SSID's without extra quotation marks. this is not a bug and behavior is