Mods - you can delete this thread as it turns out it is NOT a general issue, but a ROM issue. Thanks!
For some reason, my notifications have started silencing. Ringtones still work - but SMS, Email, etc don't. This effect seems to go away after reboot.
I am a pretty experienced Android user, and have checked volume and sound to make sure they are set right - which they are.
Using Cyanogen 5.0.4.1, but have not had this problem before so I'm thinking it is an app issue.
I don't want to start uninstalling apps willy-nilly...anyone else having this issue?
This is my logcat when a message is received:
Code:
W/Service ( 236): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 236): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
V/Telephony( 292): getOrCreateThreadId uri: content://mms-sms/threadID?recipient=%2B19793184040
V/Telephony( 292): getOrCreateThreadId cursor cnt: 1
I/power ( 92): *** set_screen_state 0
D/Sensors ( 92): using /dev/input/event6 (name=compass)
D/Sensors ( 92): using /dev/input/event3 (name=proximity)
D/Sensors ( 92): using /dev/input/event0 (name=lightsensor-level)
D/lights ( 92): 0 255 255
D/SurfaceFlinger( 92): About to give-up screen, flinger = 0x14c150
D/AK8973 ( 80): Compass CLOSE
Are you using a dock? If so it's happening to me too. If I reboot and don't use the dock it stops. There was some talk about it in the CM thread as a known issue.
uberingram said:
Are you using a dock? If so it's happening to me too. If I reboot and don't use the dock it stops. There was some talk about it in the CM thread as a known issue.
Click to expand...
Click to collapse
Indeed! Thanks for the pointer.
Mods - you can delete this thread as it turns out it is NOT a general issue, but a ROM issue. Thanks!
This is an app to control and test CPU-related parameters on OTF-compatible kernels. In realtime.
(HP Extreme, HP ICS, Etana. NOT guestekrnL as that has its own app with a lot more features.)
This app is BETA - may contain bugs.
It's been tested on HP 2X Extreme (Stock 20R), HP-ICS-RC1 (CM9-kang) and Etana (2.6) on CM7 & MIUI.
At boot it restores the minimum and maximum frequency using its own script, 88_myrt_otf, which again reads values stored in /data/myrt.
It relies on the kernels' own scripts to restore the OTF-parameters at boot-time. On HP it writes saved configs to /data/spicabootcfg, and on etana to /data/tweakaio/tweakaio.conf
To ROM-Chefs: You may now include this app in your ROMs under the following conditions:
1) You mention it is included somewhere in the ROM-release post.
2) You clearly state the app is in a BETA-state.
3) You link to this thread.
4) That you let me know
The first 3 can of course be done in a single, short line, and the last by posting a message in this thread or a PM.
Changelog:
0.7.2 - Fixed small display bug after adjusting mhz-steps. Added button to delete all files created by the app. Displays CPU-speeds correctly on ICS. Moved download to Google Play
0.7.1 - Adds option to "snap to" frequency and voltage table frequencies. Adds option to show color-coded voltages on CPU-page. On kernels without defaults specificed, selects voltage-table entries as defaults.
0.7.0 - Added support for Etana's new OTF-structure, while hopefully still working on older Etanas and Spica.
0.5.6 - Added support for vibrator strength on Etana. (Kernels May 11th or newer). You may have to uninstall old versions before installing this one, as it adds a permission for vibration.
0.5.5 - Added option to always start at: Last used page, CPU-page, Monitor-page or Reboot-page.
0.5.4 - Added reboot page.
0.5.3 - Fixes crash on Etana NON-OC kernels.
0.5.2 - Auto-moved sliders now work. Now disables controls correctly if root-access denied.
0.5.1 - Fix for permission denied issue on CM9. (Min/Max-Frequencies would not be set.)
0.5.0 - First Beta.
Technical background in post 2. Read it, it will be useful before using the app.
Known issues and misc. in post 3.
Please report any erratic behaviour in this thread, and look closely for whether your settings are restored correctly after boot. If you report a bug or other strangeness, please state the exact version of Myrt OTF, ROM and kernel.
Myrt OTF in Google Play
Tech. background.
Myrt OTF reads the current values of the CPU-frequencies and the OTF-parameters. It adjusts those values in realtime when you move the sliders. When the app exits, those values are written to files which will be used to restore the values at boot. The app itself never reads those files.
This means that if you adjust a value in for example the Etana Tweaker, an app which only adjust values to be used at boot-time, Myrt OTF will not see those values.
Myrt OTF adjusts the values in use now, and also saves them for use at boot-time.
Keep that in mind when using the kernel-specific tools and this app.
If you use either the HP Tweaker or Etana-tweaker, make sure to exit those apps with the back-button, not the home button. (This will force them to read the updated settings when they re-start.)
Known issues:
o Sometimes, when starting the app for the first time after boot, it may show "N/A" for the processor speeds. Just exit the app and start it again to fix it. (The app adjusts the permissions for the required files, sometimes it will try to read the speeds before the permissions are set.)
o If you use/have used other overclocking apps, they probably have left scripts in /etc/init.d which modify the processor-speeds as well. The last script to execute wins. If you don't get the expected min-max frequencies after boot, check for leftover scripts in /etc/init.d
thank you for you work mate.... your works are excelents and always are welcome.... once again, thank you very much
You're welcome!
Thank you very much mate!!
You're a true hero for this community
Thanks man! Love your App very much and I'll try the new one immediately!
Thanks a lot for this Trym
Edit:
Installed and doing what it supposed to do, I hope everybody buys your game Gemi from the Google Play Store to support you amazing work and participation here at XDA
As always tremendous work
Hi I have a bug using etana kernal the app is force closing when I go to system monitor. Using temask Kang 88.
04-22 10:03:12.910 I/ActivityManager(1693): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.myrt.otf/.OTFActivity } from pid 1863
04-22 10:03:13.000 I/ActivityManager(1693): Start proc com.myrt.otf for activity com.myrt.otf/.OTFActivity: pid=3881 uid=10078 gids={}
04-22 10:03:13.640 I/ActivityManager(1693): Displayed com.myrt.otf/.OTFActivity: +650ms
04-22 10:03:25.420 E/AndroidRuntime(3881): at com.myrt.otf.f.onPreExecute(Unknown Source)
04-22 10:03:25.420 E/AndroidRuntime(3881): at com.myrt.otf.c.a(Unknown Source)
04-22 10:03:25.420 E/AndroidRuntime(3881): at com.myrt.otf.TitlePageIndicator.a(Unknown Source)
04-22 10:03:25.420 E/AndroidRuntime(3881): at com.myrt.otf.TitlePageIndicator.onTouchEvent(Unknown Source)
04-22 10:03:25.430 W/ActivityManager(1693): Force finishing activity com.myrt.otf/.OTFActivity
04-22 10:03:25.930 W/ActivityManager(1693): Activity pause timeout for HistoryRecord{409acbb8 com.myrt.otf/.OTFActivity}
04-22 10:03:28.850 I/ActivityManager(1693): Process com.myrt.otf (pid 3881) has died.
04-22 10:03:28.850 I/WindowManager(1693): WIN DEATH: Window{409286b8 com.myrt.otf/com.myrt.otf.OTFActivity paused=false}
04-22 10:03:36.600 W/ActivityManager(1693): Activity destroy timeout for HistoryRecord{409acbb8 com.myrt.otf/.OTFActivity}
04-22 10:04:01.350 I/ActivityManager(1693): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.myrt.otf/.OTFActivity } from pid 1863
04-22 10:04:01.380 I/ActivityManager(1693): Start proc com.myrt.otf for activity com.myrt.otf/.OTFActivity: pid=4039 uid=10078 gids={}
04-22 10:04:02.050 I/ActivityManager(1693): Displayed com.myrt.otf/.OTFActivity: +675ms
04-22 10:04:13.490 E/AndroidRuntime(4039): at com.myrt.otf.f.onPreExecute(Unknown Source)
04-22 10:04:13.490 E/AndroidRuntime(4039): at com.myrt.otf.c.a(Unknown Source)
04-22 10:04:13.490 E/AndroidRuntime(4039): at com.myrt.otf.TitlePageIndicator.a(Unknown Source)
04-22 10:04:13.490 E/AndroidRuntime(4039): at com.myrt.otf.TitlePageIndicator.setCurrentItem(Unknown Source)
04-22 10:04:13.490 E/AndroidRuntime(4039): at com.myrt.otf.OTFActivity.onOptionsItemSelected(Unknown Source)
04-22 10:04:13.520 W/ActivityManager(1693): Force finishing activity com.myrt.otf/.OTFActivity
04-22 10:04:14.030 W/ActivityManager(1693): Activity pause timeout for HistoryRecord{40989408 com.myrt.otf/.OTFActivity}
04-22 10:04:15.440 I/ActivityManager(1693): Process com.myrt.otf (pid 4039) has died.
04-22 10:04:15.440 I/WindowManager(1693): WIN DEATH: Window{4092d0c8 com.myrt.otf/com.myrt.otf.OTFActivity paused=false}
04-22 10:04:15.440 I/WindowManager(1693): WIN DEATH: Window{40983dd0 AtchDlg:com.myrt.otf/com.myrt.otf.OTFActivity paused=false}
04-22 10:04:24.690 W/ActivityManager(1693): Activity destroy timeout for HistoryRecord{40989408 com.myrt.otf/.OTFActivity}
Sent from my Optimus 2X using XDA
it's cool~~ thx!
What about including the Autobrightness settings like in GuesteOC?
Would be so nice!
I'm very enthusiastic after testing the app! Very nice work!
Thanks!
Sorry for my english
@Shadowchas: Thanks for the report. That's an odd one. Going to install temasek kang 88 to see if I can reproduce.
Was this beta 0.5.0 or beta 0.5.1?
NedbuR said:
What about including the Autobrightness settings like in GuesteOC?
Would be so nice!
I'm very enthusiastic after testing the app! Very nice work!
Thanks!
Click to expand...
Click to collapse
EDIT. I misread (haven't had my coffee yet.) Sorry, that's not doable, the autobrightness-adjustment setting is a guestekrnL-feature, not available on other OTF-kernels. (As far as I know. If someone knows otherwise, please let me know.)
(My previous answer was about the softkey-lights, which is doable.)
@Shadowchas: I can't reproduce the bug on tamasek 88 with etana 2.6.32.59 (and the kernel-version should be irrelevant here. It was very relevant of course ;-)).
Going to fix some (unrelated) things and upload 0.5.2, can you please try that one and tell me if it still happens? If it does I can PM you a 'special' version to track down the bug.
TrymHansen said:
@Shadowchas: Thanks for the report. That's an odd one. Going to install temasek kang 88 to see if I can reproduce.
Was this beta 0.5.0 or beta 0.5.1?
Click to expand...
Click to collapse
Hi its 0.5.1
Edit will try 0.5.2 now
Sent from my Optimus 2X using XDA
TrymHansen said:
@Shadowchas: I can't reproduce the bug on tamasek 88 with etana 2.6.32.59 (and the kernel-version should be irrelevant here).
Going to fix some (unrelated) things and upload 0.5.2, can you please try that one and tell me if it still happens? If it does I can PM you a 'special' version to track down the bug.
Click to expand...
Click to collapse
No same bug I'm afraid. Happy to help bug fix feel free to pm me
Sent from my Optimus 2X using XDA
K, thanks, will PM you within an hour with a debug-version.
Work great with -42 build CM9!
Thanks for your support to this community...!
Sent by LG Optimus 2x
Thanks, right back at you. I'm still using one of your themes.
Hey! Recently I read some article about an app Discolight for Sony xperia SP, which is really great but it has some issues with missed calls notification, message notification etc.
Sony pushed out EXPERIMENTAL API for illumination bar.
Is there someone who knows what to do to make my xperia SP indicate my notifications with "tuttifruti" colours?
like in the picture?
Thanks!
Please ask in Q&A section. next time if you want to make a thread with a question, make it there.
delete it while you can. and you can find the same question in that section.
Dezideria07 said:
Hey! Recently I read some article about an app Discolight for Sony xperia SP, which is really great but it has some issues with missed calls notification, message notification etc.
Sony pushed out EXPERIMENTAL API for illumination bar.
Is there someone who knows what to do to make my xperia SP indicate my notifications with "tuttifruti" colours?
like in the picture?
Thanks!
Click to expand...
Click to collapse
I think you can use UDisco to do such effects, I think it was called rainbow. But as for notification effects-I don't know.
This app also make separate color leds for xperia SP
"Led Music Effect" is valiable in playstore
Xposed is crashing my app
Have a look at this issue:
https://github.com/mikepenz/MaterialDrawer/issues/1283
The stack trace starts in de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117) and the author of MaterialDrawer claims that you are breaking the vector drawable in a weird way.
No problem with the rest of the apps... Miui Calendar notifications do have sound... Is this a bug?
Still facing this problem... anyone?
I have the same issue with Google Calendar. Reminders and Events are saved correctly using google assistant, but notifications do not have sound. Can anyone help?
Old post, I know. But the problem still persists. I decided to do a logcat to see the difference between the phone unlocked and calendar in the foreground, and phone locked with calendar in the background:
Unlocked. Foreground.
Code:
I VolumeVibratorManager: Immersion vibratePattern() uid:10178packageName com.google.android.calendar volumeValue 127
D VibratorService: vibrate() opPkg = com.google.android.calendar usageHint = 10
D VibratorService: startVibrationInnerLocked() VibrationEffect.Immersion
D VibratorService: Turning vibrator on for 530 ms with amplitude 127.
D ImmersionVibratorService: ImmVibePlayIVTEffectWithStrength returns 0
E VibratorService: Vibration finished, cleaning up
Locked. Background
Code:
I VolumeVibratorManager: Immersion vibratePattern() uid:10178packageName com.google.android.calendar volumeValue 127
D VibratorService: vibrate() opPkg = com.google.android.calendar usageHint = 10
E VibratorService: Ignoring incoming vibration as process with uid = 10178 is background, usage = USAGE_NOTIFICATION_EVENT
https://android.googlesource.com/platform/frameworks/base/+/a5f043a^!/