[Q] One issue after flashing Galaxy task 7.0 - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hello Everyone!
I just flash Galaxy task 7.0(new released ROM) on my tablet.
It almost works perfectly. However, I have one issue that I always get a pop-up message below when I reboot my device.
The application com.sec.android.app.worldclock has stopped unexpectedly.
What I can do is either to close it or send report to Google.
Any better solution on this issue? Where can I find the application and remove it from my tablet.

There is no problem with the rom. First try wipe data in app settings and if that doesn't work....Did you do a full wipe before installing? Whether you did or not do it agin. In cwm wipe cache, wipe dalvik and wipe data/factory reset. Do each one twice then you know it has worked, cos I heard that sometimes cwm can miss some files doing a wipe. Then install the full galaxy task 7 again. I am using it and have no problem with world clock or anything else.

Related

[Q] phone wipes itself out on every reboot

Hello, I am having issues with my phone (Optimus V) after installed a custom ROM. I have AOSP 2.3.4/CM7 and thunderc 1.1.0. My issue is that every time I reboot my phone, it goes into recovery mode and wipes all data out and restarts the phone, so I have to go through the initial setup every single time. I don't know what to do to solve this issue. Thank you very much for your help in advance.
Wipe system, data, cache, and dalvik's cache, and re-install aosp's, or recover from a backup. Also, make sure you're not running - problem solved.

Force Close problems...

Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Would a Hard reset maybe solve this?
mk2vr6 said:
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Click to expand...
Click to collapse
Would be my first impression too.
Just do a complete system / nandroid backup in recovery mode (or by using the CWM Manager app).
Then Boot into recovery mode and do a factory reset.
Then reboot into recovery again, wipe cache partition and Dalvik cache too.
Then reboot the phone.
If that does not help, then you may have to flash the ROM (and afterwards CF-Root kernel) again.
Please remember to backup before and wiping cache(s) after flashing.
That will prevent most common FCs.
Good luck !
I had the same problem on my galaxy note, happened when i disabled the samsungservice.apk under system/app (was trying to remove Samsung bloat)
Put back the samsungservice.apk there and no more forced closes for the find my phone settings

[Q] FOXHOUND Revolver Ocelot Rom installation / upgrade issues

Hello all,
Sorry that i have to post this out of the thread as i cannot post on the development thread for this rom.
I have a Samsung S2 which is rooted. With the release of Foxhound Revolver Ocelot, i tried upgrading from the previous release Foxhound sniper wolf. However i had this issues with the upgrade. I then also tried fresh install but too had problems, i tried for more than 10 times so this is roughly what i gotten
Steps for Upgrading
1. Went into recovery mode and Wipe cache and also wipe dalvik cache
2. Installed from External SD card, Aroma launcher ran and choose siyah kernel and Touchwiz S3 and choose custom install where I chose all applications.
3. Installed ok, phone rebooted and then ran the upgrade applications.
Upgrading symptoms.
a. Either it hang at the boot rom page. Force reboot and it run upgrade applications again
b. When it booted up again, i got an error android.phone not responding and i had to reboot since nothing will be displayed (black screen with notification). Tried fixing permissions in the recover mode didnt work.
c. a few times even when i chose Touchwiz launcher during installing, when it managed to boot up it gave me Apex launcher. When this happen it was very buggy (no input)
I then decided to try a fresh install
Steps Fresh install
1. Boot into recovery mode and factory reset , wipe cache and dalvik cache
2. Install rom and choose siyah, touchwiz s3 as default launcher then installed all software from custom installation and reboot to the wizard process
3. Once after wizard mode reboot and wipe cache and dalvik cache
Fresh install issues
a. It hangs at the end of wizard setup and cannot proceed once the setup is done. When the happens wipe cache and dalvik cache doesnt do anything to help. (meaning if the phone fails at setup wizard i have to repeat the install process. but before that i need to wipe the internal storage)
b. Once i wipe the internal storage, installation and going to the setup wizard is good. Touchwiz launcher also works perfectly. However i am faced with another issue. I am using Mybackuppro to back my data and apks. I did attempt to install superuser and make sure in extweats my phone was rooted before continuing..
What happen is that I can restore my sms/mms/contacts/ but if i reboot the sms icon will disappear and then be re-recreated again (funny symptom)
For mybackup pro app data + apks restore, i can restore only apps but not data. If i try that the phone will reboot. I wrote to the mybackuppro developer but they told me it had something to do with the ROM, not their software.
So at the moment i am not able to use the new rom due to the above problems and i am back on sniper wolf rom..i can only use the new rom if i dont want to port my apk data over, something which i am not willing to do n ow. Was wondering if anyone faced the same issues and managed to work through these problems and can offer some advice?
Thank you.
Hello,
i'm having the same issue. I did a fresh install following all the steps, but the rom freezes after i setup my google account. Then, it reboots and the launcher seems to don't work. I tried with touchwhizz as default, nova launcher and even apex launcher. I just can't get this rom working.
Thank you for this awesome rom anyway, sniper wolf is fantastic. But if anyone knows how to solve this please help me.
Sorry for my English.

[Q] Can't wipe Dalvik Cache

I was flashing CM9 from CM7 on my Motorola Defy, botched it up intially due to a slip of my finger which led to me to Clear the cache first. But then I restarted the entire process by Clearing Data -> Installing -> Flashing Kernel and so on...
But when I tried to clear the Dalvik Cache, the phone didn't delete it. It didn't give me a message that it wiped the cache, but it didn't say otherwise either. This led me to believe that the cache just didn't exist anymore.
As a result, I'm unable to install apps - Says there is no memory and I need to make more. Also, everytime the phone comes on is treated as the first time. It takes me through the whole process of Setting up an account and everything. This has rendered my phone obsolete.
Please help me!
Thanks in advance.
~Bloo (newb) ^_^
EDIT: Solved, reflashed the stock SBF. But is this the only solution? :O
Have you tried doing a clean install?
Honestly, any time you get issues like this where the phone gets stuck (either in a boot loop or resetting your settings every boot, etc.) it's best to just wipe/factory reset and re-flash everything.
This is also why it's important to make backups so that if something does go wrong when flashing, you can just restore and be good to go.
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
bloomark said:
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
Click to expand...
Click to collapse
A clean install seems like the main thing to do (again). If you want, you could try going back to stock.
Installing again didn't do the job. Still can't wipe Dalvik Cache and the Setting still reset on every boot.
The chief problem I have with this is that I'm in India whereas the stock baseband is Europe. So to change it I've to reboot and can't do that because it resets every boot. @[email protected]
Is it a problem with the Kernel?
I'll go back to stock, but it seems a bit complex and I'm afraid I'll brick my phone. :'(
EDIT: Felt it was important to mention that the boot screen still shows CM7.1 and not CM9
I have a similiar problem.
Everytime I choose clear Dalvik men, it looks like he freezes for about a second or two. Then you see the 'menu' no - no - no - no - yes, clear dalvik memory - no - no - no (or something like that) pop up for half a second, and then it is gone. Is this a problem in CWM? Or is it in my phone?
I have a similar problem too! When I hit 'clear dalvik cache', the CWM screen just flashed once and nothing happened, and nothing says 'cleared dalvik cache' or similar...
Me too , how to solve it? Can anyone help? Mine is samsung gio
I have an issue similar to yours with my tablet (samsung galaxy tab 4 10.1 or SM-T430NU) in which it doesn't mount /data and it doesn't let me wipe to factory. Still haven't found how to fix this.

[Q] Messaging has stopped - S3 i747 Cyanogenmod 11

Hi all,
So I flashed my rom from RRemix ROM over to Cyanogenmod 11, everything seems to work fine with the exception of texting... I keep getting the message "Messanger has stopped", this happens on both the default app as well as Handcent.
I tried clearing my cache and wiping the app data... I also tried clearing cache and divik cache in CWM v6.0.4.7. Now, I was going to try to reflash gapps but of course there is some kinda bug with CWM v6.0.4.7 where it won't let me flash gapps (http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900), and there is no upgrade to CWM for the S3 i747 ATT... I guess I could downgrade? Or should I switch to another recovery app?
Any other ideas? I wanted to ask before I just wipe the phone and start from scratch.
Thanks guys! If I missed any important information let me know!
You know what... doing a I guess it's called a "dirty flash" wasn't the best idea.... I assume that is what the Cyanogenmod autoinstaller does?
Went back to my old ROM and will try a clean install later on.

Categories

Resources