Related
Some of the terminologies for noobs or someone new to android platform
Sources:
1) First Source
2) Second Source
Please let me know if I have missed something or something stated below is wrong!!!!
1- Android:
Android refers to the concept of a humanoid“robot”, and on November 5, 2007, Google announced this to be the name of the open source mobile operating system based on the Linux platform. The platform's operating system, middle-ware, user interface, and application software composition was known as the first mobile terminal to create a truly complete and open mobile software system. Similar to the iPhone, the Android WebKit browser was enabled with touch screen, advanced graphics, and internet functionality. Users can use the phone to check their email, search the web,and watch videos online. In comparison to the systems that came before it such as the iPhone, the Android system was a single integrated platform for the entire Web service instead of having a more centralized focus on search functions such as that included in the iPhone browser.
2- Open-source:
Open-source is software that anyone is allowed to see the 'source' code. In the context of Android, Open-source refers to the approach to the design, development, and distribution of software. This offers accessibility to a software's source code for modification, improvement, bug-fixing, and security-enhancement. CyanogenMod is based on this principle.
3- AOSP:
Android Open Source Project
4- APK:
APK or Android Package, is an acronym that refers to an Android installation package that is programmed in the Android phone's file format. Similar to the APK format, the Nokia phones used to use sisx, sis, and jar formats to install the packaged files. APK files can be installed via the phone, through USB, or through installing auxiliary programs on your computer.
5- ROM:
ROM in this case refers to the device firmware (in simple words, this is the mobile operating system installation package) for mobile devices such as the Android system, the iPhone iOS, and Windows mobile phones. In order to install a new ROM to a mobile device, the device must first be unlocked before the ROM can be flashed to the device. “Flashing” refers to writing a new ROM to a mobile device by replacing the firmware with a new firmware.
6- RAM:
RAM or Random Access Memory is a storage partition of the phone that is used to store and preserve temporary data. It can read and write at any time, and RAM is usually the temporary storage medium for the operating system or other programs that are running. (referred to as system memory)
7- Recovery:
Recovery can be reached through the VOLUME UP continuously pressed, and is often referred to as recovery mode. Simply put, Recovery is a flashing interface. You can choose to install the system recovery interface, ghost backup your system, restore your system, or many other things. Flashing a recovery and flashing a ROM do not conflict with each other. In this mode you can carry out a lot of advanced operations,for example, convert partition format, backup, restore, install a patch package, empty non-system data, and format the partitions, among other things.This mode is very powerful. There is some operating risks, so be careful when performing these actions.
CWM related options for instance, are explained below:
-Reboot system: now restart the phone
-Apply sdcard: update.zip update.zip installation root directory of the SD
-Wipe data / factory reset to clear user data, restore factory settings
-Wipe cache partition to clear the cache
-Install zip from sdcard install zip from SD card
-Backup and restore backup and recovery
-Mounts and storage mount memory
etc.
8- Root:
Root privileges can be likened to the Windows system's Administrator privileges. The Root Super Android system administrator user account has sovereign rights to the entire system. This account is able to modify and operate all objects on the device. Systems cannot be changed or revised unless it is through the Root permissions.
9- adb:
Adb or Android Debug Bridge can be used through Eclipse DDMS to debug Android applications. In fact, the Google Android system uses these debugging tools. In addition to the above feature, we can do adb state management on the device, or use it as a mobile device simulator. It can also be used to enter the various states of the phone such as the recovery,installation programs, copy files, or even run the shell.
10- External SD Memory:
The technical name for this type of memory is “built-in non-volatile mass memory”, but is more commonly known as ROM or Read Only Memory. Obviously, this type of memory is not actually read only, or else we wouldn't be able to make changes to the internal memory, and smartphones would simply be pretty bricks with call functions.
External SD Memory (abbreviated SD Card) are memory storage devices that are bought separately from the mobile devices, and can be inserted into the device to increase on board storage space.
11- Firmware:
Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
12- Kernel:
The kernel is the basic component of the operating system.It is the part of the software that provides secure access to the computer hardware for many applications. The kernel can decide which functions are restricted or limited for each program or application, and the time frames that each process can use hardware.
13- FC:
Short for Force-close or forcibly closed, this is mainly an error that occurs when a program encounters a fatal error and needs to terminate the process.
14- Phone is “bricked”:
Cell phone enthusiasts jokingly refer to the failed flashing of a rom to a mobile device and the subsequent disabling of the phone’s boot processes as “bricking” the phone. If this is manufacturer induced, the phone becomes useless – a veritable “brick” of useless hardware and circuitry.Thankfully, if the “bricking” of the phone is only due to the improper installation of the new system, you can fix the issue through the bootstrapped recovery interfaces.
15- Android Play Store:
The Android Play Store or Play Store is the hub for all developed applications for the Android platform. It can be directly compared to the Apple App Store, and includes a vast majority of the apps that are found inits Apple counterpart. Users can browse, download, and install all types of applications, and while many are free, there are also many that are paid, so this provides an incentive for many major media companies to develop for Android in order to increase profits.
16- CM:
CM stands for CyanogenMod, which was founded by Steve Kondikin 2009. CyanogenMod is a launcher shell for Android and can be flashed from Rom. Currently, CM is available in CM7, CM9, and the beta CM10 versions.
17- Flash Memory:
This is memory that comes with specialized storage such as on mobile devices with items that are already pre loaded such as applications,pictures, music, etc. Under normal conditions, these types of memory are read-only, and will not allow users to overwrite preexisting data.
18- Restoring factory settings:
Restoring factory settings will erase all user settings on the mobile device, so before performing this action, it is recommended to backup all user data. This process rewrites the current ROM on your mobile device with the stock ROM that the device originally came preloaded with. Depending on which maker or system, restoring factory settings will erase user settings,installed software, or some combination of both.
19- OTA:
OTA refers to “Over the Air” updates. These updates are usually downloaded using a data connection as opposed to the normal WiFidownload. The point of these types of updates is that they can be downloaded at any time.
20- Fastboot:
Fastboot literally means starting quickly. In fact, fastboot is a special method of booting the phone through the computer that can allow the user to access a streamlined set of options that increase the efficiency of performing some processes.
21- Superuser:
A superuser is a root permission management software. This software is designed to help you manage which applications on your device have root permissions in order to avoid any unintentional damage to your device from malicious or untrusted applications.
22- APP to SD, APP2SD:
Some Android systems have the option to move application data from the internal memory to the SD card, and still be able to effectively run the programs. This method can also be used to transfer app data to and from phones without having to re-input all previously entered data. Another use for APP2SD is that by moving app data to the SD card, it frees internal memory from clutter and improve phone speeds.
23- Busybox:
A set of Unix tools / commands that has been compiled for use on your phone. These are not usually full-featured versions of the Unix commands found on the larger platforms counterparts, but they are pretty close and useful nonetheless.
24- Bloatware:
Software or 'apps' that you don't need, but come pre installed to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit. For example, the Photobucket app included on the G2 by TMobile.
25- Dalvik-Cache:
The dalvik-cache directory holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
26- Google Apps (GApps):
An add-on for Google's applications (Market, GMail etc.), packaged separately to avoid copyright issues
27- Logcat:
A debugging tool built into Android devices that displays system logs as they occur.
28- NANDroid:
A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
29- Unlock:
Most GSM devices are locked to only work with the sim cards of a particular carrier. Obtaining root access (e.g. installing CyanogenMod) on the device usually does nothing to the sim-lock. The usual way to unlock the device to all SIM cards is to obtain a subsidy unlock code from a carrier.
I still stand by that this is a logcat -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Jellybean Xperia S
Ben36 said:
I still stand by that this is a logcat -
View attachment 1656035
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
good one....
U have a typo at 3rd point
Deodexed?
Sent from my MT27i using xda premium
Hi guys
So my z2 has been plagued by this weird bug since I bought it. Basically every time I have a missed call the process com.android.phone crashes twice and I lose connectivity for a second.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am on 4.4.4 rooted now, but it happened on 4.4.2 as well. Any idea on what might cause it?
Max
Are you using any xposed modules? Could be the issue
Sent from my Xperia Z2 using Tapatalk
Mr.R™ said:
Are you using any xposed modules? Could be the issue
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
I'm using these, but disabling them did nothing. Haven't tried a clean install yet(too lazy). I was just wondering if anyone had this bug.
I can't remember what caused it for me or how I fixed it but I'm sure it was one of the Xperia mods, from there the only module we have in common is gravity box tho. I assume you rebooted after disabling them?
Sent from my Xperia Z2 using Tapatalk
maxiedk said:
Hi guys
So my z2 has been plagued by this weird bug since I bought it. Basically every time I have a missed call the process com.android.phone crashes twice and I lose connectivity for a second.
View attachment 3013336
View attachment 3013337
I am on 4.4.4 rooted now, but it happened on 4.4.2 as well. Any idea on what might cause it?
Max
Click to expand...
Click to collapse
I'm so glad that I found this post. I thought I was the only person having this exact issue. It ONLY occurs when I miss a call or if I clear a missed call notification.
I get this same error message:
Then I noticed, my status bar goes through a small cycle of events. I think this is where the answer may lie, but I have no idea what is causing it:
What you see above is the chronological order of how my status bar changes immediately after clearing the error message from the screen. It appears as if there is some sort of SIM card error only momentarily which then knocks me offline and then my phone reconnects.
It doesn't matter how long the time between the error message first appearing and when I clear it, the status bar always goes through this cycle. Basically, it doesn't appear to have anything to do with the actual phone call, it has to do with clearing this error. By the way, what I think is a SIM card with the red "X" on it appears on the screen for about 1 second before vanishing. The whole cycle lasts about 5 to 6 seconds. Also, notice that after the SIM card is gone, there is an open space between the icons on the status bar. Very strange.
These are the steps that I have taken to clear the error but to no avail:
1.) Rebooted my phone (many times)
2.) Cleared the phone app cache
3.) Booted into CWM and cleared the cache and the Dalvik cache
4.) (I use Xposed) Disabled all the modules and rebooted
5.) Diabled all the modules, booted into CWM, cleared the cache and the Dalvik cache and rebooted
My phone is a Sony Xperia Z3 compact:
Rooted running 4.4.4
Stamina mode is turned off
Running Xposed framework and several modules - one of them is Garvitybox
The following apps are installed with root access:
Busybox On Rails
Greenify
GSam Battery Monitor
ES File Explorer
ROM Toolbox Pro (nothing activated)
Secure Settings
SetCPU (1 profile set when screen turns off)
Tasker
Titanium Backup
Wakelock Detector
Xposed Installer (modules: AppOpsXposed, BootManager, GEM Xperia Xposed, GravityBox, Greenify, Xposed Macro Expand)
If any could please help to solve this error message I would greatly appreciate it.
Mr.R™ said:
I can't remember what caused it for me or how I fixed it but I'm sure it was one of the Xperia mods, from there the only module we have in common is gravity box tho. I assume you rebooted after disabling them?
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Yes, I removed all of them, rebooted and cleared cache and dalvik. Still nothing.
JoeSchmoe22 said:
I'm so glad that I found this post. I thought I was the only person having this exact issue. It ONLY occurs when I miss a call or if I clear a missed call notification.
I get this same error message:
Then I noticed, my status bar goes through a small cycle of events. I think this is where the answer may lie, but I have no idea what is causing it:
What you see above is the chronological order of how my status bar changes immediately after clearing the error message from the screen. It appears as if there is some sort of SIM card error only momentarily which then knocks me offline and then my phone reconnects.
It doesn't matter how long the time between the error message first appearing and when I clear it, the status bar always goes through this cycle. Basically, it doesn't appear to have anything to do with the actual phone call, it has to do with clearing this error. By the way, what I think is a SIM card with the red "X" on it appears on the screen for about 1 second before vanishing. The whole cycle lasts about 5 to 6 seconds. Also, notice that after the SIM card is gone, there is an open space between the icons on the status bar. Very strange.
These are the steps that I have taken to clear the error but to no avail:
1.) Rebooted my phone (many times)
2.) Cleared the phone app cache
3.) Booted into CWM and cleared the cache and the Dalvik cache
4.) (I use Xposed) Disabled all the modules and rebooted
5.) Diabled all the modules, booted into CWM, cleared the cache and the Dalvik cache and rebooted
My phone is a Sony Xperia Z3 compact:
Rooted running 4.4.4
Stamina mode is turned off
Running Xposed framework and several modules - one of them is Garvitybox
The following apps are installed with root access:
Busybox On Rails
Greenify
GSam Battery Monitor
ES File Explorer
ROM Toolbox Pro (nothing activated)
Secure Settings
SetCPU (1 profile set when screen turns off)
Tasker
Titanium Backup
Wakelock Detector
Xposed Installer (modules: AppOpsXposed, BootManager, GEM Xperia Xposed, GravityBox, Greenify, Xposed Macro Expand)
If any could please help to solve this error message I would greatly appreciate it.
Click to expand...
Click to collapse
I guess we just have to wait until Lollipop.
I think I found the solution. Are you using Titanium Backup? If you are, use one of the batch actions and "defrost" everything (unfreeze) on your device, reboot and the error should be gone. When I did the process manually and unfroze apps one by one it didn't work. But when I used the batch action it fixed the problem. Not sure why, but it's perfect now, no more errors!!!!
JoeSchmoe22 said:
I think I found the solution. Are you using Titanium Backup? If you are, use one of the batch actions and "defrost" everything (unfreeze) on your device, reboot and the error should be gone. When I did the process manually and unfroze apps one by one it didn't work. But when I used the batch action it fixed the problem. Not sure why, but it's perfect now, no more errors!!!!
Click to expand...
Click to collapse
Thanks for the tip. I flashed a custom rom and the problem is gone for me.
They suggest turning off smart calling in this thread http://forum.xda-developers.com/xpe...enz-ultimate-1-0-5-light-dark-t2835196/page31, but I don't know if it will work in the stock version.
Intro:
This thread is about a common & bothersome android OS error:
"System UIDs Inconsistent
UIDs on your system are inconsistent, you need to wipe your data partition or your device will be unstable"
popping at the system startup/boot/reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Detail:
There have already been nearly a hundred threads on this topic, partly because of the problem is so prevalent and ubiquitous...
It has been reported from a wide range of devices, running various ROM/any android version. Most people got fed up trying numerous unbecoming solutions & landed up formatting their devices, and often landed up losing all userdata!
Generally it appears after flashing new ROMs/Kernels and the issue is more common with people who tend to try out different ROMs, therefore have to backup and restore the NANdroid backups in brief intervals.
Wiping data partition is not always desirable, as it would cost you all the saved application data, including contacts and messages.
Unfortunately there was no definite cure till now, but fortunately enough, there's something now!
This error is not necessarily emerging from your system apps/core/kernel etc etc (though, the error message seems more like a system prompt!) , rather it might be originating from petty handful of user-apps (even from those you had uninstalled in the past!!! but their corpse have somehow remained as zombies!).
Acknowledgement:
Thanks to xcreatir for hinting at this excellent piece of idea on XDA, on a similar thread.
Many more people got close to the solution, but missed the target by a whisker, and got deflected towards weird and terrible 'solutions'!
But, the problem is easy to fix, and indeed self-explanatory (and also logged by android automatically)!
Pre-requisite:You'll need root-access.
So, get your phone rooted, before you proceed (if its not already).
Solution:STEP 1.
Use a file explorer with root access (e.g. ES File Explorer OR Root Explorer OR File Explorer with Root Addon and browse to /data/system/
and locate a file named "uiderrors.txt"
Here I have relied on ES File Explorer with root privileges.
TIP: Must check "Show hidden files" in the settings of your chosen file manager.
Screenshots:
STEP 2.
Open it via any text reader
Screenshot:
STEP 3.
Look at the last few lines, you'll find the culprit apps whose leftover files have been causing the problem:
05/07/15 11:44 pm: Package com.rovio.angrybirdsseasons has mismatched uid: 10520 on disk, 10125 in settings
05/07/15 11:45 pm: Package ma.wanam.xposed has mismatched uid: 10485 on disk, 10230 in settings
Click to expand...
Click to collapse
In this case, the programs were:
com.rovio.angrybirdsseasons (Angry Birds Seasons)
and
ma.wanam.xposed (Wanam Xposed)
Click to expand...
Click to collapse
This will be completely different in your case.
Disclaimer:
By no means, I'm pointing fingers to these two apps as the culprits (rather, they are some of the best apps available!), this can happen with any give app. Thus, will be completely different in your case.
TIP: Please look through your own "uiderrors.txt" file very carefully to find out which are the apps having UID mismatch in your case!
You need to find every app mentioned in your "uiderrors.txt" file which had UID mismatch. Its not a difficult job, trust me. The list wont be long!
STEP 4.
Now browse to /data/data/
and
/data/app/
you'll need root privileges, otherwise things will show blank.
Screenshots:
STEP 5.
Select the folders with the names mentioned in"uiderrors.txt". Be careful of selecting anything else! This can land you in troubles. Mark only the ones mentioned in your own,
In my case I have to mark/select
/data/data/com.rovio.angrybirdsseasons
and
/data/data/ma.wanam.xposed
+++
/data/app/com.rovio.angrybirdsseasons.apk
and
/data/app/ma.wanam.xposed.apk
OR
/data/app/com.rovio.angrybirdsseasons-1.apk
and
/data/app/ma.wanam.xposed-1.apk
Click to expand...
Click to collapse
Remember: the apk file can bear any number after its name: e,g, it could also be com.rovio.angrybirdsseasons-4.apk
So, don't worry you have to mark everything that matches the name, forget the suffixes!
Again, the culprit files would be completely different in your case than what I have listed here.
Please take a close look at your own "/data/system/uiderrors.txt"
Screenshots:
6. Carefully delete them by hitting Delete Button at the bottom. Be careful of deleting anything else!
7. Reboot & enjoy!
You're done! No more errors! No need to format your device, keep all your data intact.
Caution:
Programs like Link2SD/ App2SD etc tend to complicate the issue to some extent.
In such cases, you must also scrutinize following directories besides: /data/data/ to find any leftover files belonging to those that are mentioned in your uiderrors.txt
These can hide inside (I'm not asking you to delete all of the below directories, just delete specific subdirectories/files as mentioned in your uiderrors.txt:
\data\sdext2\
\data\sdext2\data\
\data\sdext2\app\
\data\sdext2\app-lib\
[Remember, these directories might slightly: instead of "sdext2", you may find "sdext3" OR "sdext4" OR something a little more different. This is basically the mounting point of your SD Card's 2nd partition, formatted into linux file systems: ext2/ext3/ext4]
Click to expand...
Click to collapse
Delete meticulously any such traces!
Good Luck!
UPDATE! i sorted my issue out i had to go to the SD card in recovery and delete the DATA/System files! and everything thats in it, cheers
i have an issue in that i cant get to desktop on my phone to reset the counter as the popups overwhelm me with " System UIDs Inconsistent" i simply cant do anything with it so what i have done is reset factory settings from Recovery rather than the ROM, ive used Odon to reinstal the ROM but i then realised its nothing to to the the OS/ROM i have pretty much tried everything and the one thing i cant do is get the phone to the desktop to install the Apps that will sort this out i dont suppose any of you have an alternative way please? id be really greatfull i just need to stop these popups telling me "System UIDs Inconsistent" and i believe the ONLY way to do this is via your phones operating system in your settings but i cant get the phone past the "Search Wifi" startup when you first install a new ROM?
DJwa163 said:
TIP: Please look through your own "uiderrors.txt" file very carefully to find out which are the apps having UID mismatch in your case!
You need to find every app mentioned in your "uiderrors.txt" file which had UID mismatch. Its not a difficult job, trust me. The list wont be long!
Click to expand...
Click to collapse
I'm not sure about your definition of long, but 46 errors in my case...
Anyway, 46 apps deleted and now the error is gone, many thanks
Still I wonder if there was no other way to get the UID's back in sync, without deleting affected apps.
All 46 apps were linked with Link2SD, so I'm guessing something went wrong there.
IMO S50
thanks. its work:good::good::good::good::good::good:
Hi friends,
After updating my Samsung J5 to Android 6.0.1 I m getting error "Unfortunately, SmartManager Clean SDK has stopped" when choosing "Storage" option in Smart Manager app.
Problem persist even after clearing cache & data of all 3 apps Smart Manager, Smart Manager Provider & Smart Manager Clean SDK from App manager. I have even tried wiping & formatting cache from Recovery mode.
I dont want to factory reset my device, does anyone having any idea how to get out of this?
My Phone is Samsung J5
Region India
Same problem with the galaxy s7 :/
Dalex33 said:
Same problem with the galaxy s7 :/
Click to expand...
Click to collapse
It seems that there is no solution at this moment, I will try factory reset & get back soon.
Error Screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
deepak0148 said:
It seems that there is no solution at this moment, I will try factory reset & get back soon.
Click to expand...
Click to collapse
Guys, Problem found, its the Memory Card!
Friends, whosoever is facing the error "Unfortunately, SmartManager Clean SDK has stopped" on tapping the "Storage" option in the "Smart Manager" App, just follow the given steps.
1. Backup all your Memory Card data in some other device (Ex. PC/Laptop)
2. Format the Memory Card from phone only (Important) & restore all the backedup data back in Memory card & thats it.
Clear the recent programs & App Caches & restart the device & now there should be no error. The problem should be resolved.
I have applied these steps on Samsung Galaxy J5 (Region: India, Model: SM-J500F) with Android Version 6.0.1 & the problem is resolved.
Cant say about other devices, you may please try on your device (only if you are facing the above error) & tell us your experience.
Thanks for reading. :good:
I'm encounter the same issue on a S6 edge, so, not possible to format SD card (there is no).
Another idea guys?
Thanks for your help
grumly_37 said:
I'm encounter the same issue on a S6 edge, so, not possible to format SD card (there is no).
Another idea guys?
Thanks for your help
Click to expand...
Click to collapse
Same problem s5 and this method doesn't work for me anyway thanks
New solution
It's from Microsoft apps i deleted all Microsoft apps and
Did a full wipe all my problems were solved
Did you try only after deleted Microsoft apps? Because I don't want to full wipe my device
Smart Manager
deepak0148 said:
Guys, Problem found, its the Memory Card!
Friends, whosoever is facing the error "Unfortunately, SmartManager Clean SDK has stopped" on tapping the "Storage" option in the "Smart Manager" App, just follow the given steps.
1. Backup all your Memory Card data in some other device (Ex. PC/Laptop)
2. Format the Memory Card from phone only (Important) & restore all the backedup data back in Memory card & thats it.
Clear the recent programs & App Caches & restart the device & now there should be no error. The problem should be resolved.
I have applied these steps on Samsung Galaxy J5 (Region: India, Model: SM-J500F) with Android Version 6.0.1 & the problem is resolved.
Cant say about other devices, you may please try on your device (only if you are facing the above error) & tell us your experience.
Thanks for reading. :good:
Click to expand...
Click to collapse
anyone tried this??..i'm encountering the same problem...any feedback guys who tried his method??
To avoid such error in future
Guys, to avoid such problems, before checking for software updates, please unmount the memory card, then remove it physically.
Update your phone & re-insert card, there should be no error like this.
I have tried this method in J5 2016.
no luck for me...after formatting the sd card on my phone, i tried to run it and the pop up message did not appear...however, when i transferred the files back to the sd card, that message popped up again in smart manager...i didn't installed any apps yet so the problem remains...haaaay
I was able to solved this issue ONLY with a wipe of my phone
After, it's ok :good:
After my Samsung galaxy j5 updated to Android 6.0 its getting trouble to login to my Google account.
Solved on S6 EDGE - No MemoryCard
Hi all, I had the same issue after upgrade my S6 edge. The solution that worked for me was by going to CONFIGURATION - APPLICATIONS - APP ADMIN. Then there "Show System Apps" and go to
SmartCardManager and SmartManager Clean SDK --> STORAGE --> REMOVE DATA AND CACHE.
As additional information Im not root, and I have deactivate all Office Apps.
Hope it could help someone :good:
deepak0148 said:
Guys, Problem found, its the Memory Card!
Friends, whosoever is facing the error "Unfortunately, SmartManager Clean SDK has stopped" on tapping the "Storage" option in the "Smart Manager" App, just follow the given steps.
1. Backup all your Memory Card data in some other device (Ex. PC/Laptop)
2. Format the Memory Card from phone only (Important) & restore all the backedup data back in Memory card & thats it.
Clear the recent programs & App Caches & restart the device & now there should be no error. The problem should be resolved.
I have applied these steps on Samsung Galaxy J5 (Region: India, Model: SM-J500F) with Android Version 6.0.1 & the problem is resolved.
Cant say about other devices, you may please try on your device (only if you are facing the above error) & tell us your experience.
Thanks for reading. :good:
Click to expand...
Click to collapse
didn't work for my (J500H)
the problem appeared after i get my data back to the SD card
tried to factory reset , wipe cash ,format the SD from my PC
still giving me "unfortunately, smart Manager clean SDK has stopped."
Dear abokassem,
Now Samsung might have fixed this glitch.
As of now there is no such issue in my phone J5 2016 (JF510) on software upgrade.
Hope it will not showup on upgrading your software.
Thanks
i have alot of issues on my phone j5 2016 (510fn/ds) errors like "keyboard has stop", "google services has stop",etc.. allways rebooting as well..
i dont know what do, have tried some things but didn't work
P.S. sorry for bad english
Remember that YOU DO ALL THIS AT YOUR OWN RISK, I DO NOT BE RESPONSIBLE, AS WELL AS THE AUTHORS OF THE FIRMWARE AND FILES.
At the moment, who has devices from the box on EMUI 12, it is not possible to install services.
The given tutorial is valid for region 432 devices. I haven't tried other regions, it might work but maybe not.
And approach this case with a clear head, patience and straight hands .... and everything will work out, 100% CHECKED and so we begin.
Preparation:
We download all the necessary utilities and files, and save them in one new folder in an accessible place, for example, on the desktop;
Files for installation on a computer;
- Download the official HiSuite from the link
HUAWEI Hisuite Free Download | HUAWEI Support Global
HUAWEI HiSuite is the official Android Smart Device Manager tool,HiSuite helps users to connect their HUAWEI smartphones and tablets to PC and perform various tasks.
consumer.huawei.com
- HiSuite 10.0.0.550 OVE (EN)
- HiSuite 10.0.0.550 (CN)
- HiSuite.Proxy utility
Files for installation on a smartphone;
- Google Play Services 21.24.56 (GPS 21.24.56)
- Google Services Framework (gsf+10)
- Google Services Framework (gsf-fix2)
-Googlefire
All files except the first one are attached under the instruction
Save the last 4 files in your convenient e-mail cloud, then you will need to download them from the cloud on smart, because on version 10.1 - 10.1.0.131 the USB connection will not be active.
STAGE 1. System rollback to EMUI 10.1 - 10.1.0.131.
A. Rollback to version 11
If we are on EMUI 12, then we roll back to EMUI 11 using the HiSuite application on the computer. To do this, remove HiSuite 11.0.0.550 OVE if installed on your computer and install the previously downloaded official HiSuite. We connect the smartphone to the computer and perform all the proposed steps to connect and synchronize the smart with the computer. Next, after successfully connecting the smart with HiSuite, click on “System Update”, a window will appear and give permission, another window will appear and click on “Other version”, and then on “restore”. Smart will be flashed with a rollback to firmware version 11, which HiSuite will offer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
B. Rollback to version 10
If it is not clear to someone, I have written this instruction for rolling back to version 10, I am attaching a video (rollback is made up to 11; 25 minutes) by reference;
. Personally, I rolled back on this video.
I guess we are already on the 11th version. We roll back to the 10th version, and more specifically to 10.1 - 10.1.0.131, the most optimal version for installing services. To do this, remove HiSuite on your computer and install HiSuite 11.0.0.550 OVE and the HiSuite Proxy utility.
1. Install HiSuite 11.0.0.550 OVE
We install it on the computer and connect the smartphone, in principle, the same synchronization actions as in point A. Next, we close the utility, but do not turn it off, for this we need to configure it in the program settings, which can be configured on the screen below;
2. Install and configure HiSuite.Proxy.
First, delete the entries in the upper cells that are crossed out, the rest remains as in the screenshot
Next, we patch the HiSuite utility by pressing the "Setup" button, as in the screenshot above. If there are no red inscriptions, then the process is successful, the main last point was identical as in the screenshot below. So we leave the HiSuite.Proxy utility, DO NOT CLOSE.
3. Search for the required firmware version in the Huawei Firm Finder resource.
Open the Huawei Firm Finder resource in the browser using the link; https://professorjtj.github.io/
On this page, we need to pick up our 131st firmware version, how to do it? In the top line of filters, enter the data of the smart model, firmware region and the required basic firmware version. (Example; my smart model is ANA-NX9. The assembly number, at the moment, is 12.0.0.276 (C432E5R4P5). In the first paragraph of the Phone Model, enter ANA-N, then the second paragraph, the region, enter C432, for the Russians C10, etc. the third and fourth paragraphs are optional). Next, what are we looking for from the list? We need PRELOAD, CUST, OVS firmware. We find 131 OVS and select for download by clicking on “add rom”, we also do it with the subsequent PRELOAD and CUST. One BUT: PRELOAD is selected with the designation R of your firmware, for example, I have R4 from the firmware data 12.0. By clicking them one by one, links to the selected firmware components are automatically added to the HiSuite.Proxy utility in the upper cells that you previously cleared.
An exception in the process of selecting firmware for the Russian region C10, we do through the upper right menu "Database", then select "Downgrades" and already select the firmware, as indicated above. In addition, in the network and Internet settings of the computer, if it is not activated, we activate the VPN.
I am attaching screenshots;
4. Open the HiSuite utility on the PC (smart is connected to the PC via USB). Next, the rollback process is the same as in paragraph A. At the bottom, click the "System Update" button. A window opens with a suggestion to downgrade the firmware version and click Update.
During the process of downloading and installing the firmware, do not close the HiSuite and HiSuite.Proxy utilities on the PC. Good luck.....
Hope the process went well. Before starting with the installation of services, download 4 files from the cloud on smart, which was indicated at the beginning of the instructions. In advance to a new folder, suppose the name of the Program.
STAGE 2. Installing Google Services
1. Installation of services, the process itself.
The best instruction for this process will be the following video (the process we are interested in starts at 10;29 minutes) at the link;
(By the way, this video also includes a downgrade for the P40 lite, practically a complete package of Installing Services for the P40 lite.)
My advice is to review carefully. And then get down to business, slowly, pause, return along the track if necessary. In the video, everything is practically chewed and clear, I installed it successfully the first time. I hope you install the services successfully. I will make a reservation about some of the nuances that I encountered, due to inattention and ignorance, I had to reinstall again after each successful installation.
Important point!!! In this process, you will have to change the year in the smart settings, delve into the course of events. But I will be brief, the first time you bet on 2019, the second time on 2021, and the last one on autotime and will return to the current year.
At the end of the installation, there will be moments of testing the play market, the main thing is that it opens and you can unwind the options. And even if you can’t enter the playmarket account settings, don’t be scared, everything is OK. Further, after the process is completed and the smart is restarted, notifications for non-certification may still pop up, this is how the card will fall, do not be alarmed. After the reboot, contrary to everything that I read to you above, we proceed to the next item.
2. Push activation
- On smart, open the “Files” application and look for a folder with 4 downloaded files.
- Install the GPS file 21.24.56.
- We go in the settings of the smart, applications, applications, in the upper right corner, click on the four dots and select Show system processes, look for the Google Services Framework in the list and delete it.
- Again in the folder with files and install gsf10.
- Open the Phone application and enter the code *#*#426#*#* to check the activation of push notifications, in theory the result should be CONNECTED.
- We repeat the removal of Google Services Framework.
- Again, in the folder with files and install gsf fix2.
We reboot the phone and then check the push method above. Ready...
!!! Further important actions after all;
We go to the Play Store in the settings and turn off auto-updates for applications.
Then We go to the smart settings -> applications -> applications -> Google Play Store -> Traffic statistics -> Transfer in the background (transfer to the disabled position). We do the same step for Google Play Services.
Enter the Google Play Market and disable Play Protect.
We do not update Google Play Services, AT ALL !!! Google Play Services only works with version 21.24.56 installed by us.
We do not install any clone application. Services are not friendly with them and can present another hemorrhoids.
3. Device certification.
We do according to the instructions, simple and understandable, by reference;
Как снять блокировку Google Play: "устройство не сертифицировано Google"? • Android +1
Как вы наверное уже знаете компания Google начала блокировку работы фирменных приложений, а на экране Android появляется ошибка "устройство не сертифицировано Google". Решаем эту проблему! C марта 2018 года компания Google ввела новую политику по борьбе установки своих фирменных приложений, GAPPS...
androidp1.ru
. After the process in the play market in the settings, Information, the annoying “Device is not certified” will disappear, but after a while it will come out. Do not pay attention, does not affect the work of the Market.
And lastly, update the system only via OTA (over the air).
That's all.......
If you have any questions, write in a personal, I will answer as soon as possible.
I wrote the given tutorial on the basis of several tutorials, and on the basis of my experiments and mistakes, to finally arrive at a perfect and 100% working tutorial for the moment.
Vitiok70 said:
- Google Services Framework (gsf+10)
- Google Services Framework (gsf-fix2)
Click to expand...
Click to collapse
can you please upload these files?
jovanostojic said:
can you please upload these files?
Click to expand...
Click to collapse
He has the files; https://forum.xda-developers.com/m/badmania98.619592/
But if i reset the smartphone i Lost everything?
Rxfireblade said:
But if i reset the smartphone i Lost everything?
Click to expand...
Click to collapse
Yes, of course
Cannot find the files from this link. Am I missing something?
Vitiok70 said:
He has the files; https://forum.xda-developers.com/m/badmania98.619592/
Click to expand...
Click to collapse