Jump to content

stadtmobi

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

7 Neutral

About stadtmobi

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    ZTE Open C
  1. Questions: Is your issue related to this ROM? Has it begun after you flashed a new version of this ROM or after you flashed it for the first time? Have you blocked mobile data access for instagram? Are other apps working with mobile connection? Have you already rebooted your device? Have you already cleaned/deleted the dalvik cache? Have you already uninstalled and reinstalled this app? Do you use any particular ad blocking or firewall app?
  2. Merci. the correct file permissions solved my problem!
  3. do you know how to check the android logcat informations? http://developer.android.com/tools/debugging/debugging-memory.html Like this you can watch out for the apps that do block your device. As a hobby android app programmer i can tell you that it is very easy to occupy RAM. So just one single app can be the reason for your bad experience. You could also try the following: 1. Do a full backup 2. Reinstall CM 13 again 3. Wipe cache 4. Use it without installing any app -> how's the behaviour? 5. Install only one app after another and try to keep an eye on the performance/ram. Like this you could also detect the app that causes your problems without messing with logcat
  4. Thank you. I've overwritten the deskclock.apk with the one from the 0308 build and rebooted but now the deskclock does not work anymore (not listed in the installed apps and if i try to install it via opening the apk it says PARSE ERROR. Do i have to follow a special procedure or to degrade the app to a non-system app before uninstalling it and reinstalling the new one? If you know how to read the RAM informations on your phone (f.e. for the last three hours), you'll find the memory hungry apps. Try to figure out the ones you can remove without problems or at least revoke their start-at-boot right and recheck the RAM information. The Open C (i assume you have this device) is a low budget device with less than 512mb ram. If it will be loaded with persistent apps like a recent high-end device (galaxy s6) it won't make you happy
  5. First results: Deactivated AudioFX (headphones and speakers) and deinstalling µg UnifiedNlp (no GAPPS) (https://f-droid.org/repository/browse/?fdfilter=wifi&fdid=org.fitchfamily.android.wifi_backend) really increased the performance. --------- @KonstaT I remarked this morning that the alarm clock crashes while the alarm rings and i try to touch the onscreen snooze/cancel button. The alarm clock also crashes when i try to open the settings (widget settings do work). I think it's a general problem with the default alarm clock application because of the logcat output (below) Edit: Found the same issue here: http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808/post65866609#post65866609 03-27 22:39:54.133 13840-13840/com.android.deskclock E/AndroidRuntime: FATAL EXCEPTION: main Process: com.android.deskclock, PID: 13840 Theme: themes:{} java.lang.RuntimeException: Unable to resume activity {com.android.deskclock/com.android.deskclock.SettingsActivity}: java.util.IllegalFormatConversionException: %d can't format java.lang.String arguments at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3137) at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3168) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2515) at android.app.ActivityThread.-wrap11(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1363) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:148) at android.app.ActivityThread.main(ActivityThread.java:5461) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) Caused by: java.util.IllegalFormatConversionException: %d can't format java.lang.String arguments at java.util.Formatter.badArgumentType(Formatter.java:1489) at java.util.Formatter.transformFromInteger(Formatter.java:1689) at java.util.Formatter.transform(Formatter.java:1461) at java.util.Formatter.doFormat(Formatter.java:1081) at java.util.Formatter.format(Formatter.java:1042) at java.util.Formatter.format(Formatter.java:1011) at java.lang.String.format(String.java:1554) at android.content.res.Resources.getQuantityString(Resources.java:483) at com.android.deskclock.Utils.getNumberFormattedQuantityString(Utils.java:799) at com.android.deskclock.SnoozeLengthDialog.setSummary(SnoozeLengthDialog.java:93) at com.android.deskclock.SettingsActivity$PrefsFragment.refresh(SettingsActivity.java:285) at com.android.deskclock.SettingsActivity$PrefsFragment.onResume(SettingsActivity.java:132) at android.app.Fragment.performResume(Fragment.java:2263) at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1008) at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1148) at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1130) at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1963) at android.app.FragmentController.dispatchResume(FragmentController.java:174) at android.app.Activity.performResume(Activity.java:6348) at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3126) at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3168) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2515) at android.app.ActivityThread.-wrap11(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1363) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:148) at android.app.ActivityThread.main(ActivityThread.java:5461) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) 03-27 22:39:54.143 724-1308/system_process W/ActivityManager: Force finishing activity com.android.deskclock/.SettingsActivity 03-27 22:39:54.149 724-1308/system_process W/ActivityManager: Force finishing activity com.android.deskclock/.DeskClock
  6. I also have some performance problems but i've installed a lot of application. I didn't use any tweaks or hacks. I will try to find and report the memory-hungry apps
  7. Thank you KonstaT! The new build works great. By the way: I've remarked also that the live display day/night switch did also not work on the last build 20160308. It works now too. Time for another donation :)
  8. Thank you for your effort. By clean install do you mean i cannot install it and apply afterwards a nandroid backup?
  9. No ambient light/proximity sensor on my device. If i revert to the cm13 build befor your latest, rotation works correct. For the logs: I get no log activity while rotating the phone after the problem appears. Hereby the log after a fresh reboot when rotating still works: 03-15 13:52:17.175 633 668 I ActivityManager: Config changes=480 {1.0 262mcc7mnc de_DE ldltr sw320dp w533dp h296dp 240dpi nrml long land finger -keyb/v/h -nav/h s.6 themeResource=null} 03-15 13:52:17.185 633 834 I InputReader: Reconfiguring input devices. changes=0x00000004 03-15 13:52:17.186 633 834 I InputReader: Device reconfigured: id=3, name='goodix_touchscreen', size 480x800, orientation 3, mode 1, display id 0 03-15 13:52:17.313 1594 1594 D PullToRefresh: Setting Padding. L: 0, T: 0, R: 0, B: 0
  10. What did you revert to 2.7 - Doze Service? Can you explain how please
  11. Thank you. I've installed Droid Hardware Info: The ST3-Axis Accelerometer works correct. Until now i haven't found a way to reproduce it but i think it is after letting it in standby mode for a while. It will be the same problem as described in the cm ticket you've linked. I encounter it with all apps. Newpipe just uses a manual screenrotation when the playback is started. It does not read any sensor data (my good). My logs do not show anything in particular. Am i the only one with that issue? I will make a nandroid backup and remove the doze service to test it.
  12. Two observations for the latest build: 1) From time to time the auto-rotate does not work anymore. The rotation is then still working if i use apps like newpipe for watching youtube videos but not for apps like firefox. If i do a restart, the auto-rotation works again for a while 2) If i'll do a quick restart to solve the issue. The system reboots to the PIN entry screen but does not take any touch entries. I can also not confirm a restart anymore. The only thing that helps is to remove the battery to restart.
  13. Hi again. I had some more issues and now i've found the reason: I've activated on CM12.1 the option "update cm recovery during update". During my first update to CM13, the CWM recovery was replaced with the CM stock recovery. Now after a wipe, a reinstall of your cwm i was able to install cm13 from sd card. Edit: my OpenC runs now much faster than before. I think i've messed up the sd card handling somehow.
  14. I have checked the MD5 sum , no file corruption found. Android SDK *.31 is the latest official build for Ubuntu LTS 14.04.
  15. Thank you! I'm testing it right now on my open c. Until now no bugs or glitches found. By the way: i could not apply this update via the usual way (zip on sdcard root directory). My try via adb sideload on my linux desktop showed "error: protocol fault (no status)". I've duckduckgo'ed it and found a temporary solution and the reason: the sideload now requires a newer adb version than the system standard 1.0.31 (on *buntu 14.04) and the solution can be found here: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1402195 It's answer #6 -> Download and extract the pure adb file and launch via terminal (./adb sideload..) https://skia.googlesource.com/skia/+archive/cd048d18e0b81338c1a04b9749a00444597df394/platform_tools/android/bin/linux.tar.gz
×

Important Information

By using this site, you agree to our Terms of Use.