I am not sure whether this thread is off topic or not. But this problem is really boring and I wish somebody can look into it and find a permanent solution.
My tab is international version, no matter I flash the DXKM2 stock firmware or Roto's JME-V4 with CF-Root, I always encounter the camera failed error. But it do works before I install any 3rd software.
So far I doubt it's due to some system application removal, because I have another Galaxy S with exactly same 3rd party software installed without this problem. I only deleted some unnecessary built-in apps in system folder. Here is the list I deleted apps:
IMEs (I use TouchPal for Chinese input)
Samsung widgets (I like very clear homepage)
Ebooks (I use ibook)
Live wallpapers (to reduce power consumption)
Email (I use K-9 mail)
Samsung Unified Inbox
SNS (Chinese can't use facebook)
It's very weired that I didn't install anything since last time to take picture. Seems like the pad idles certain time then the camera has problem itself.
Anybody encountered same problem like me and even found the root causes? Please help.
Update:
OK, I found the root cause by deleting files one by one. Found that the Email.apk and Email.odex can't be deleted. Once I copy back those two files from backup, and restart, the camera functions well now.
dahuzi said:
I am not sure whether this thread is off topic or not. But this problem is really boring and I wish somebody can look into it and find a permanent solution.
My tab is international version, no matter I flash the DXKM2 stock firmware or Roto's JME-V4 with CF-Root, I always encounter the camera failed error. But it do works before I install any 3rd software.
So far I doubt it's due to some system application removal, because I have another Galaxy S with exactly same 3rd party software installed without this problem. I only deleted some unnecessary built-in apps in system folder. Here is the list I deleted apps:
IMEs (I use TouchPal for Chinese input)
Samsung widgets (I like very clear homepage)
Ebooks (I use ibook)
Live wallpapers (to reduce power consumption)
Email (I use K-9 mail)
Samsung Unified Inbox
SNS (Chinese can't use facebook)
It's very weired that I didn't install anything since last time to take picture. Seems like the pad idles certain time then the camera has problem itself.
Anybody encountered same problem like me and even found the root causes? Please help.
Update:
OK, I found the root cause by deleting files one by one. Found that the Email.apk and Email.odex can't be deleted. Once I copy back those two files from backup, and restart, the camera functions well now.
Click to expand...
Click to collapse
i just installed the [ROM] 29/Jan Middle East P1000JPJM4/Ext4 with MoDaCo Kernel and the camera failed toooo... just wondering if you can give a detailed orrientation on how to correct this... thanks and greatly appreciated in advance
i have found some apk's that are undeleteable in my tab:
Browser
Email (required by Camera)
Stk
TouchWiz30Launcher
TwWallpaperChooser
Who's idea to tie
Email (required by Camera)
Click to expand...
Click to collapse
to the camera is beond me bought an enhanced client and i'd hoped clean replacment would doit.
Ive never touched the email apk... I froze it once but defroze it. I dont think I messed with the email.odex
I rooted with super one click and flashed KhasMek Voodoo Plus v3 kernel. Anyone have any idea how to fix it? thanks!
how was this fixed?
im not sure but I cant tell how was it solved
In all the cases above, the camera start failing at some point after an install of 3rd party software.
and I believe in their case, the camera works on stock rom.
Is yours really broken on gb stock safe (in your other posts you mention so). Pure state after Odin.
Don't start restoring apps.
Sent from my GT-P1000 using xda app-developers app
Hi everyone. Its my first post on this HTC Glacier forum. My wife owns the Glacier but I don't really have time with her phone to mess with it and figure this out myself (we are both very busy through out the day). The stock gallery shows no media (pics or videos) in my phone, but I have QuickPic installed and it shows all the pics and videos. It wouldn't be such a problem cuz I don't care for the stock gallery itself (I prefer QuickPic) but if you are texting and decide to add a attachment there is no option to use Qickpic to get that file (only the stock gallery). You would have to use QuickPic to view the file first then from there use the share option to sent it as MMS, but since my wife is learning to use the phone (she came from a Blackberry) she finds it anoying that way. I later installed the Gallery 3D to check it out but it also shows no media in her phone.
The phone is pretty much stock 2.2.1, perm-rooted with Visionary (haven't done the s=off option though). Thank for your time and I'm sorry if this has been discussed cuz I searched but didn't find it
...if you are texting and decide to add a attachment there is no option to use Qickpic to get that file (only the stock gallery).
Click to expand...
Click to collapse
I can't give you a solution to your problem, but I'm pretty sure the stock messaging app lets you take the pictures from QuickPic. I do it all the time.
Try going into "Manage Applications" and click on and clear the defaults on your stock gallery app. Once you do that, the next time you try and attach a picture it will ask you which application you want to use to attach it, then you can just re-select QuickPic.
Thx Alan, I'll try that.
Ok so I figure out what the problem was (had to steal the phone from her for about 30 min). It seems DRM Protective Content has to be running for me to view my media. I had it frozen with TB since that's the way I have it in my Vibrant and it causes no issue there, its just one of those system apps that I didn't want/needed to be running but for some reason the stock galley (in the Glacier) needs it to view your media... weird. Anyways when I plug the phone to the PC it turns DRM off and then I cant view my media again. Even after I disconnect it and go check to see if DRM is running (which it is) my gallery still says "no media" but Quickpic shows it though. I have to go back to TB then freeze then unfreeze DRM and then I'm able to view my media in the gallery... weird also.
Also... with QuickPick and Gallery 3D installed, I still don't have the option to choose either one when applying a attachment while sending a text message (only the stock gallery is available to choose). I cleared the data on all 3 galleries and also on the messaging app to see if then it gives me the option to choose, but nothing. Any ideas people. THX ahead.
Hmm had no idea the stock gallery was linked to DRM. Probably has something to do with HTC Sense and it's closed sourceness.
Does the DRM get refrozen when you actually mount your sdcard on the pc or just by plugging it in on charge only? It sounds like some sort of bug created by TB. If that DRM actually is a vital(or semi-vital) piece of the stock sense, then perhaps when you froze it that created bugs for the parts of the system that used it.
I've noticed in certain cases some actions will stick to the settings even once you undo the changes through the app you created the changes with. For example, on my stock Rom I used automate it pro to set my Bluetooth to power on when an external power source was connected. Eventually I disabled this rule and uninstalled the app, but those settings stuck permanently and now whenever I use my stock Rom and plug it in to charge, Bluetooth will turn on. Perhaps something similar is happening to your wife's phone...
I'd say try downloading a different messaging app like handcent or go sms and seeing if they have the same problem attaching photos. Perhaps the stock sense message app is linked to the stock gallery and I just don't remember that. I'll check one of my old backups and let you know what I find.
____________________________________
Sent from the AFB Corporation's Main Communication Portal
This question is to the devs:
Why not try to keep the /system/ partition as low as possible?
As far as I know, any non-essential apps to get your app running can be installed through the /Data/ folder, which can be A2Ext'ed and won't need to eat up our NAND memory.
So why don't devs just push all the apps that can be in /Data/, to /Data?
Apps to consider moving to /Data/:
Theme chooser and livewallpaper
Camera, Gallery
Any kind of games
Browser
Additional misc. apps like dpi changer and Torch
Maps
Calendar, Calculator
Music, FM, Soundrecorder
SuperUser, ROM Manager, SpareParts
GMail, Talk
Apps that should stay in /system/:
Any kind of *services.apk
Any kind of *providers.apk
Any kind of background apps
Setup wizard
Keyboard
Phone, Messaging, Launcher
Bluetooth
Settings
Market
Bumping for some insight!
There's no way that no one has considered this before. I want to know what's wrong with doing this.
My questions is as my title explains.
I just used the shiny new root tool to root my phone, so of course the first thing I did was boot up Titanium Backup and restore all of my apps and some of my settings.
I made sure that I was pretty careful not to override any system apps/settings, or at least so I thought.
Everything is working fine, except that now all of my toggles are completely gone.
Notification drawer: Missing
Quick Settings Panel: Missing
Settings -> Display -> Notification Drawer: Missing
Was just wondering if anyone had any ideas, or if I'm forced to do a reset and restore again :/
Nevermind I fixed it. I used Titanum Backup to wipe my two Settings Storages and that worked.
Just thought I'd post that in case someone else does the same thing.
I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it
highaltitude said:
I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it
Click to expand...
Click to collapse
Agreed. Never a good idea to try to restore Settings (or really ANYTHING other than user apps) when going cross-ROM, and especially cross-Device. Sometimes you can get away with it if the roms are based on the same origin (i.e. a modified stock rom from stock), but if there's ever any changes to the available settings (nearly always the case), there's a huge risk.
Glad to see you fixed it.
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.
@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.