hi all,
i'm experiencing a weird problem. i've been flashing lots of roms (cm10.x, omni, stock-based ones), and suddenly my phone's camera started not working. however, if i turn the device off completely, start charging it, and turn it back on, the camera is fine until a reboot (even after unplugging from the charger). removing the sim card and rebooting also helps sometimes.
i've tried:
- factory reset
- flashing different roms
- revering to stock
- some forum post on the 'net about deleting the 'dcim' folder on both sd cards (wtf lol)
- disassembling the phone (my warranty is void anyways) and checking the main, battery and the camera's ribbon cable connection (they're fine)
i'm pretty sure it's not a hardware problem, but i can't be certain, of course.
anyone had this issue before? any suggestions? something else i forgot and should try?
thanks,
bamdad
update: somehow, after installing the new 4.3 firmware, it was alright for a while, then it started happening again. since my back cover was in quite a rough shape, i ordered a new one; after putting it on, the camera started working normally.
now i really don't get this, because i've taken the device apart dozens of times. it might have something to do with those little copper contacts being corroded on the old back cover, someone correct me if i'm wrong. the strange thing is that the camera seemed to work fine with the back cover off.
well, it's fixed now, but for how long? :/
this is just insane. yesterday i tried omnirom again, played around with it, then restored my backup of the official .199 firmware, and some time later tried to take a photo - boom, camera and flash hasn't worked since. now that i think of it, i distinctly remember trying a previous build of omnirom before the last time my phone went bonkers.
now i'm not hinting at that it's omnirom's fault directly, since apparently lots of people are using it without similar issues, and at the end of the day custom roms aren't responsible for damaging a device, but it's strange.
if someone has any pointers as to what should i do, i'd be really appreciative. i'm going to try flashing from an original ftf file, maybe this has to do with some firmware stuff that's reeeally over my head. fingers crossed..
the funny thing is that it works great after restoring my backup of omni. bloody hell. : ) i mean what am i missing here? : )
okay, so i managed to (maybe) fix it. the trick was to *not* use omnirom's cwm recovery to restore the stock rom, rather flash the stock kernel with philz touch, *then* restore the backup. man.. hope this lasts.
started again this morning on dark lord's blackxt (stock .199-based), torch went too. rebooting and the other tricks didn't do diddly-squat. however, a trip to recovery and back fixed it. i did install doomkernel, but it's probably not the one that helped, because i've been using that last time the problem started.
btw, i know i'm spamming this topic all alone, but maybe someday this will prove useful to, or someone who knows what's going on will laugh and tell me to idk reformat the whole device or flash some obscure firmware file or something.
Related
just a quick one, my X1 with standard software has started to randomly reboot which is getting on my nerves!
Its also losing new messages when it does this. so any ideas before I test its bouncability on the wall
If you have installed an app recently, or can pinpoint something you've done, try to uninstall/undo that.
I would personally hard reset (search on the X1 board for the how to via the hardware keys, or just choose Clear Storage from the Settings/System menu).
Make sure you've at least sync'ed all your data to your PC first. Then connect back up, and contacts etc will be restored.
If you haven't already, try SPB backup (or Resco's , or Sprite's) - they are all time-limited trials so no problem with a quick backup-restore sequence. You can choose just about anything to backup from your device with these.
If you're feeling adventurous, consider trying one of the more popular ROMs, you won't look back!
I've tried the custom ROMs in the past but decided to go back to stock.
Already hard-reset it and was still doing it, and now I've gone to update it (its back to stock) on the SE update service and its still rebooting.
Its now stuck on the four colour screen!!! I am really hating this phone
I've now managed to get the Stock ROM on but when it comes to installing the Stock SPL both my pc brings up a blue screen (never done before) and phone dies again.
I've also noticed when I clear storage it turns off but won't come back on, only way it does come back on is by removing the battery
Any help guys??
mine kept doing this. Sent it to SE and they replaced the mobo.
yeah gone today, see what happens
Had same problem while using stock and custom roms . Then i searched xda for stable & fast rom and i did it. Not advertise but i really like 826x rom =)
I decided to do a reboot just to have a fresh start after adjusting some app. The phone was stuck at the flashing Darky logo for indefinite amount of time. After a minute or so of flashing logo, phone vibrates shortly and continues flashing the logo. That repeats each minute.
Taking out the battery and retrying didn't help, same thing.
In the past 48h since last boot, I've installed a bunch of apps, mostly games, so it's natural to look for a culprit among them. However, right now I can hardly do anything with the phone. I can access the recovery menu, download mode probably as well and that's it.
I'm ready to flash the Resurrection Edition, but first I'd like to exhaust other options for fixing the problem or at least backing up everything I can. I have partial backups but would very much like to access the latest changes that weren't backed up.
My questions are:
1) Is there some kind of boot logging that I could turn on, access and which would point to the problem? I'm comfortable using ADB if it's needed.
2) I did a CWM backup. What did it backup? Primarily, what about contacts, SMS messages?
3) The most important question: If I reflash the ROM and then use CWM restore, will the problem repeat itself? (If an app is the source of the problem and all apps are backed up and then restored, I'm afraid the problem won't go away. I see few big image files in the backup folder which suggests that everything will be restored as it was. Bootloop too?)
Additional hints for experts on what might be causing the problem:
There are only two incidents that come to mind.
First is that I did a wipe flash of darky 9.1, then a regular flash of 9.2. After I discovered my GPS simply doesn't work on 9.2, I did a regular flash back to 9.1. This was about 2 weeks ago. Is there something in this procedure that might leave some problems that would show up in the future?
Second thing is a incident I had 2 days ago (the time last reboot was done and last time I've had a successful boot).
I left the phone ON over night, and in the morning found it turned off. I thought it might be a dead battery so I plugged it in. It wouldn't start for few minutes but then booted normally.
During that day I found it OFF one more time, for no apparent reason. This time battery was nowhere close to low. It turned off while in standby/locked screen mode so I can't say that it was doing anything in particular.
(Even the turning off during the night is suspect. It had sound on, it was near my head, and I'm sure that low battery warnings would wake me up. It might just be the case it turned off for no apparent reason like it did during the day.)
i think, that when you flashed 9.1 over 9.2, it could leave some weird things, because everyone is talking bout updating, and no-one even think about downgrading rom.
Answer 1. If you used SpeedMod kernel, I think you can turn Logging in Tweaks Menu at RM, and start phone with plugged USB cable to computer (running adb).
Dunno bout other kernels.
Darkyy normally turned off logging, because ROM was bit faster without it.
Answer 2. Probably contacts were synced to Google (contacts.google.com) <--- try it
I think SMS messages are backed up together with whole ROM (contacts too).
Answer 3. Probably yes, problem will repeat. I don't know but maybe there is some way you can restore only some things, not whole system.
I think you should make "Backup Everything" in CWM, then try flashing 9.2 again.
Weird that GPS were not working there.
It seems something bad was happening that caused random reboots.
What apps that require root, you were using? Swapper, Galaxy Tuner, Overclocking?
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
Hi, guys. So I got this phone relatively recently and tragedy has already befallen it. While I was at Youmacon in Detroit, I broke the screen. I don't know how I did it, even now. One crack. Then the top half inoperable. Then the entire thing inoperable. I wanted to use Markers to find out exactly what was broken, but when I was touching the inoperable parts of the screen, the phone kind of seemed to... freak out? It froze up then rebooted. And then it was stuck in a boot loop. Not that I could use the phone if it did boot, but it wasn't booting anymore. I am running SliMM 3.8 with EliteKernel, by the way.
So I bought a replacement touchscreen along with the glue stickers to mount it. Installed it, it was working, but, uh... I didn't do a very good job of it. It's sticking up on the left by quite a bunch. Anyways, it was still bootlooping so I restored a fairly recent nandroid backup. The battery started to tank at light speed once the OS was actually up. I was losing 2% a second and had no idea why. Even with the charger plugged in, it was still losing faster than it was gaining. Like, how??? It also seemed to be prone to overheating in this state. Then I tried various different configurations for fresh flashes, most of them causing it to fail to get past the bootloader. I was thinking maybe EliteKernel was encouraging it to overclock and go nuts, so I wanted to use Advanced Stock, but introducing DRM restoration or certain Magisk mods usually made it stop working.
So... I'm currently looking at a situation where I might just give up on this phone and buy a new one. I did like this phone a lot when I was using it though. So... what could have been causing that insane battery consumption? Is there some special procedure I should be using to install the following? SliMM 3.8, Advanced Stock Kernel, XZ SystemUI, Magisk, phh su, xposed, DRM restoration
If you recommend I get a new phone, I really like the compact form factor. What's a good small phone with good development support?
iPhone.
Really.
Other than that - flash full stock (wiping everything). If that works, then you can continue.
Perhaps you short-circuited something while replacing the LCD+touch screen ?
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?