3C portal - Known Issueshttps://www.3c71.com/android/?q=taxonomy/term/10
List all known issues for all applications, including work-around when available.
enPlay Store Installation/Update issueshttps://www.3c71.com/android/?q=node/2616
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>Unable to install the app, from Play Store or Amazon or manually? Receiving error XXX? Play Store asking you to pay again for an app?</p>
<p> </p>
<p>As detailed everywhere on the net, <strong>most Play Store issues are resolved by clearing Play Store/Google Services Framework apps' data and rebooting</strong>. Sometimes recreating your account on the device is necessary. Search the net for the specific error number reported by Play Store. FWIW I'm not the developer of the Play Store app so you should really ask support from the actual devs of those apps when you have such a problem.</p>
<p> </p>
<p>If <strong>your device is not rooted</strong>, only the above can solve your issue, and <strong>3C Toolbox or any of my apps or any apps <span style="color: #ff0000;">cannot create </span>or solve this issue</strong>. </p>
<p> </p>
<p><strong>If your device is rooted</strong>, you can 1- check available space in all partitions, especially /cache and /data, 2- clean-it up from all remains, eg any files or folders containing the app package name (ccc71.at for the 3C Toolbox Pro, found in Play Store app detail page URL) in both /data and /system folders. Once your device is cleaned-up, installation should proceed as usual, should any Play Store issues be resolved. FWIW, app file remains are an OS issue, apps don't control installation or un-installation in any ways.</p>
<p> </p>
<p>Here you can find more information (and solutions?) to <a href="https://www.google.fr/search?q=play+store+error+-24">error -24</a> and most <a href="https://www.google.fr/search?q=play+store+error">Play Store installation issues</a>.</p>
</div></div></div>Thu, 10 Sep 2015 08:58:59 +00003c2616 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2616#commentsSuperSu does not grant root after app updatehttps://www.3c71.com/android/?q=node/2614
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>SuperSU, by default, removes root permission to apps having been updated! So you may notice after an app update that root features are no longer functioning as expected.</p>
<p> </p>
<p>This is caused by an option in SuperSU called "Re-authentication", enabled by default which requires manually granting again root to any udpated apps having been granted root previously. Sadly this option has been turned on by default and may cause any root apps to malfunction after an update.</p>
</div></div></div>Fri, 10 Jul 2015 10:26:30 +00003c2614 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2614#commentsSuperSU does not grant root during boothttps://www.3c71.com/android/?q=node/2613
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The app (affect 3C Toolbox, System Tuner) may not be granted root during boot, hence fail to apply any boot settings!</p>
<p>This is caused by an option in SuperSU which is disabled by default "Enable su during boot". Simply enable it and everything will be fine.</p>
<p> </p>
<p>This option when disabled will refuse root to any apps (even though root has been previously granted) until SuperSU receives the BOOT_COMPLETED message from Android. This makes the whole process very unreliable because there's no way to predict when apps will receive the BOOT_COMPLETED. This message is sent to all apps (having requested it), one after the other. So any apps receiving the message before SuperSU will not be granted root. Any apps receiving it after will be granted root.</p>
<p>Please also note that this option is very misleading into making us believe all apps will receive root, even those which did not get manually granted root. This is not true, only apps manually granted root before will receive root during boot.</p>
<p> </p>
<p>In summary the SuperSU option called 'Enable su during boot' must be enabled in order for any boot settings to be applied properly and this is true for any apps on Play Store using root during the boot process. Sadly this option has been turned off by default and may cause any root apps to dysfunction dramatically.</p>
</div></div></div>Fri, 10 Jul 2015 10:24:13 +00003c2613 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2613#comments3C Toolbox - SD Mover limitations on Android Lollipop 5.x and abovehttps://www.3c71.com/android/?q=node/2606
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>Starting with Lollipop 5.x, linking is only possible using permissive (unsecure) kernel mode. This can be set and unset using the following commands: setenforce 0 and setenforce 1 respectively.</p>
<p>However Play Store policies do not authorize publised app from doing so. For that reason, SD Mover is disabled on Lollipop 5.X and above.</p>
<p> </p>
<p>To enable SD Mover in such circumstances you can either disable secure mode in an init.d script (not recommended) or you can <strong>create the following 2 scripts under the app data folder</strong> (/data/data/ccc71.at/ for the full version or /data/data/ccc71.at.free/ for the free version):</p>
<p>File name: dse</p>
<ul><li>Content: setenforce 0</li>
<li>Permissions: r-xr-xr-x (555)</li>
</ul><p>File name: ese</p>
<ul><li>Content: setenforce 1</li>
<li>Permissions: r-xr-xr-x (555)</li>
</ul><p> </p>
<p>Creating those 2 scripts will enable the SD Mover features while preserving kernel security at all times, and <strong>is the recommended method to enable SD Mover</strong>.</p>
<p> </p>
<p>In rare circumstances, those scripts (more precisely the command setenforce 0) may not be authorized even for root user. If so, SD Mover will not be enabled and you will need to install a custom kernel either allowing such command or entirely disabling security (not recommended).</p>
</div></div></div>Sat, 04 Apr 2015 16:49:46 +00003c2606 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2606#comments[ANDROID_BUG] Widgets disappear after each app updates or reboothttps://www.3c71.com/android/?q=node/2594
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>This is an OS bug and has been reported to Google, please <strong><a href="https://code.google.com/p/android/issues/detail?id=188137">stare at the issue here to get it resolved faster</a></strong>. <a href="https://code.google.com/p/android/issues/detail?id=188137">https://code.google.com/p/android/issues/detail?id=188137</a></p>
<p> </p>
<p>This issue <span style="color: #ff0000;">affect any apps on Play Store, with stock launchers (<strong>LG, Google, Samsung, Motorola, etc</strong>) on Android 4.1 and above</span>. There is a known bug in OS / stock launchers, that causes added widgets to disappear from stock launchers when the related app is updated. <span style="color: #ff0000;">Other third party (non-stock) launchers are not affected by this bug or have never been reported to suffer from this!</span></p>
<p> </p>
<p><strong><span style="color: #0000ff;">A possible workaround is to kill the launcher when that happens. It works on LG G4</span>. Please let me know if it works on others, I'll update this page!</strong></p>
<p> </p>
<p>There is <span style="color: #ff0000;"><strong>no other workaround to this issue because of the way Android OS updates the app</strong></span>. The larger the app the longer it will take the OS to update it. During the whole update process the app is made unavailable, and if a launcher decides to update it, it will likely dismiss it. <span style="color: #ff0000;"><strong>Only the launchers can implement a workaround</strong></span>.</p>
<p> </p>
<p><span style="color: #ff0000;"><strong>Here are things that can help prevent losing widgets</strong></span>:</p>
<p>- Move apps to internal storage, the update process will be faster reducing the chance of being affected</p>
<p>- Use a third-party launcher, most appear to have implemented a workaround.</p>
<p>- Disable affected apps auto-update.</p>
<p> </p>
<p>To make this less frustrating, <span style="color: #3366ff;">please save your widget configurations so you can apply them again quickly</span> when adding back your widgets.</p>
<p> </p>
<p>You can find more information here where <strong>other devs/users have reported the same issue</strong>, possibly <strong>affecting any paid apps</strong>: </p>
<p><span lang="EN-US" xml:lang="EN-US"><a href="https://koxx3.wordpress.com/2014/07/01/widgets-disappearing-with-samsung-4-4-2-roms/">https://koxx3.wordpress.com/2014/07/01/widgets-disappearing-with-samsung-4-4-2-roms/</a></span></p>
<p><span lang="EN-US" xml:lang="EN-US"><a href="http://androidcommunity.com/kitkat-bug-may-be-affecting-widgets-on-your-handset-20140508/">http://androidcommunity.com/kitkat-bug-may-be-affecting-widgets-on-your-handset-20140508/</a></span></p>
<p><a href="http://stackoverflow.com/questions/23144968/widgets-gone-after-app-update">http://stackoverflow.com/questions/23144968/widgets-gone-after-app-update</a></p>
<p><a href="http://android.calengoo.com/pagedoc/pageadvanced/pagewidgets/styled/pagewidgetproblems.html">http://android.calengoo.com/pagedoc/pageadvanced/pagewidgets/styled/pagewidgetproblems.html</a></p>
<p> </p>
<p>3C apps affected by this (any versions):</p>
<ul><li>Battery Monitor Widget Pro</li>
<li>System Tuner Pro</li>
<li>Process Monitor Widget Pro</li>
<li>3C Toolbox Pro</li>
</ul><p> </p>
<p>While I understand how frustrating this can be, there is nothing I can do to fix this.</p>
<p> </p>
<p>Thanks for your understanding and don't forget to <strong><a href="https://code.google.com/p/android/issues/detail?id=188137&amp;thanks=188137&amp;ts=1443683951">stare at the issue here to get it resolved faster</a></strong>.</p>
</div></div></div>Fri, 23 May 2014 23:24:54 +00003c2594 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2594#commentsBattery mA reportinghttps://www.3c71.com/android/?q=node/2590
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>Battery mA data is often provided by Android kernel, however some devices may exhibit a number of issues, varying greatly with every devices:</p>
<ul><li>mA in standby is incorrectly high: mA is stuck around -200mA in standby, requires using Estimates in standby.</li>
<li>mA while unplugged is incorrect: mA is incoherent when unplugged, requires using Estimates while unplugged.</li>
<li>mA is constantly negative once fully charged and still plugged. This is automatically taken care of by the app.</li>
<li>mA remains close to 0 at all times. Requires changing 'mA retrieval method' in battery / monitoring settings (possibly to HTC Devices or Estimated).</li>
<li>mA is reversed. Requires changing 'mA retrieval method' in battery / monitoring settings (possibly using HTC DNA or Reverse uA/mA).</li>
<li>mA is slow to adapt to device usage, device has likely no current sensor (or undetected) and is reporting estimated mA.</li>
</ul><div>If you can't solve any of the above, please send a support requets from app settings, help and support, <span style="text-decoration: underline;">mentioning the issue you're facing</span>. Empty requests cannot be looked at.</div>
</div></div></div>Fri, 04 Apr 2014 10:01:02 +00003c2590 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2590#commentsAds turning screen blackhttps://www.3c71.com/android/?q=node/2589
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>If you ever experience issues with your screen going black when ads are refreshed, please take a look at this thread on XDA. This offers a solution:</p>
<p><a href="http://forum.xda-developers.com/galaxy-s3/help/i9300-ads-screen-black-t2429659">http://forum.xda-developers.com/galaxy-s3/help/i9300-ads-screen-black-t2429659</a></p>
</div></div></div>Tue, 01 Apr 2014 13:26:20 +00003c2589 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2589#commentsSystem App clean-uphttps://www.3c71.com/android/?q=node/2572
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>Cleaning system apps is the process of integrating system app updates into the Android ROM permanently, eg into the /system partition. It has been noted that in very rare circumstances this could cause the following issues:</p>
<p>1) On Android 4.4 running GEL launcher, <span style="color: #ff0000;">cleaning-up Google Search may prevent the next boot from completing properly</span>. If you find yourself in this situation, you will ned to either wipe data or run the following command from a PC: "adb shell su". Once the first boot has completed no other issues has been noted. Restoring/installing a third-party launcher from recovery can also solve this issue.</p>
<p>2) On Android 4.4, <span style="color: #ff0000;">cleaning-up Google Keyboard may cause the back button and keyboard to stop functioning until next reboot</span>. Under rare circumstances the issue may persists after next reboot, if so uninstalling Google Keyboard and restoring it to either User or System partition fixes it. This issue has mostly been found to occur when doing clean-up with Titanium Backup.</p>
<p>3) During the process the <span style="color: #ff0000;">affected system apps are temporarily unavailable which could results in some apps temporarily failing to work or crashing</span>. However this issue is automatically resolved at the end of the clean-up process or after rebooting the device.</p>
<p><span style="color: #ff0000;"><strong>4) Before cleaning many system apps, please try to do so on a non-critical app, reboot and check if the app is still ok. Then proceed with the other apps.</strong></span></p>
<p> </p>
<p>No other issues have been reported at this time. NB: This issue also affects apps like Titanium Backup.</p>
</div></div></div>Tue, 14 Jan 2014 13:44:54 +00003c2572 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2572#commentsMIUI ROMs badly affect battery logginghttps://www.3c71.com/android/?q=node/2565
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>It has been reported that recent versions of <a href="http://en.miui.com/thread-317-1-1.html">MIUI ROMs have an issue with their alarms</a>, causing any app relying on intervals to get notified 5 times less.</p>
<p>For Battery Monitor Widget, default battery logging is performed every 10 minutes by default, however on MIUI ROMs it turns into 50 minutes and there's no way to work-around this without impacting battery severely and risking other users with non-MIUI ROMs be affected.</p>
<p>For Android Tuner, you may optionally set app to update and log mA data every minute, which on MIUI Roms will turn into an update and logging every 5 minutes instead.</p>
<p> </p>
<p>If your device is rooted, you can use <a href="http://www.3c71.com/android/?q=node/2560">Xposed framework</a> and a module dedicated to fix this. You can <a href="http://forum.xda-developers.com/showthread.php?t=2481178">download the MIUI Xposed framework here</a>. Then install the "Alarm Time Fix" module, enable it and reboot.</p>
<p>If not rooted, I'm sorry but you will have to report this issue to MIUI development team to get it fixed. </p>
</div></div></div>Sun, 22 Dec 2013 14:40:27 +00003c2565 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2565#commentsAndroid KitKat (4.4.2) app-killing bughttps://www.3c71.com/android/?q=node/2564
<div class="field field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above clearfix"><div class="field-label">Forums: </div><ul class="links"><li class="taxonomy-term-reference-0" rel="sioc:has_container"><a href="/android/?q=forum/10" typeof="sioc:Container sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Known Issues</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>This Android OS bug is only present in KitKat version 4.4.2 (fixed in 4.4.3), more information is available here: <a href="http://www.androidpolice.com/2014/03/07/bug-watch-stopping-apps-on-android-4-4-2-can-silently-kill-related-background-services-a-fix-is-on-the-way/">Android Police</a></p>
<p>To prevent <strong style="color: #800000;">3C Toolbox</strong>, <strong><span style="color: #800000;">Battery Monitor Widget Pro, System Tuner Pro or Process Monitor Widget Pro</span></strong> from being killed you can <span style="color: #ff0000;">add <span style="text-decoration: underline;">a notification icon shortcut</span> to make the app persistent using the 2 options available at the bottom of the notification settings <span style="text-decoration: underline;">as shown on below screenshots</span></span>.</p>
<p> </p>
<p>For free/pro users, the following alternatives are available:</p>
<p>- Use the recorder in 3C Toolbox, System Tuner or Process Monitor Widget</p>
<p>- Enable battery recording and monitoring interval in Battery Monitor Widget (the default on KitKat)</p>
<p> </p>
<p>Android KitKat (4.4.x) exhibits a known issue in which any apps can get killed at any time without possibility to recover. This may affect widget updates or background services like battery monitoring.</p>
<p>Swiping away an app from the recent task list may also get the app killed along with all its services (affecting widgets), so the best way to avoid this is to avoid swiping app away from the recent task list.</p>
<p>More technical information about this issue are available here (developer discussions):</p>
<p><a href="https://code.google.com/p/android/issues/detail?id=63793">https://code.google.com/p/android/issues/detail?id=63793</a></p>
<p><a href="https://code.google.com/p/android/issues/detail?id=63618">https://code.google.com/p/android/issues/detail?id=63618</a></p>
<p> </p>
<p><span><span style="color: #800000;"><strong><span style="text-decoration: underline;">3C Toolbox</span></strong></span><strong style="color: #800000;"><span style="text-decoration: underline;"> settings</span></strong></span></p>
<p><img src="/android/sites/default/files/Screenshot_2013-12-22-17-42-57.png" width="180" height="320" /> <img src="/android/sites/default/files/Screenshot_2013-12-22-17-43-19.png" width="180" height="320" /> <img src="/android/sites/default/files/Screenshot_2014-01-11-20-50-44.png" width="180" height="320" /></p>
<p><span style="text-decoration: underline; color: #800000;"><strong>Battery Monitor Widget settings</strong></span></p>
<p><img src="/android/sites/default/files/Screenshot_2014-03-29-15-06-59.png" width="180" height="320" /> <img src="/android/sites/default/files/Screenshot_2014-03-29-15-07-14.png" width="180" height="320" /></p>
</div></div></div>Sun, 22 Dec 2013 08:48:31 +00003c2564 at https://www.3c71.com/androidhttps://www.3c71.com/android/?q=node/2564#comments