in july i flashed my phone over to energy's most current cookie rom and put the froyo build that danij3l had been working at on my hd2 and it worked beautifully aside from the battery life. i switched to hyperdroid in august or september and it was running even better than dan's build had; i was getting ~100 hours uptime out of each boot, SODs were rare, calls were fine, the phone barely froze. i was in love.
over the last 2? weeks however i've been having a huge amount of problems keeping my phone going. certain websites i access in android make my phone crash; it resets itself but will hardly ever get past the stick together splash screen without a hard reset. when i do get it to boot back into windows i immediately get the "device memory is critically low" message. i lost a TON of my shortcuts in my start menu completely randomly (can't access stuff like file explorer, i have to start a new task in task manager to get to anything) and when i go into settings ->system->memory it says the total amount of storage is 19.09mb and that i have NOTHING available.
keep in mind that's AFTER many a hard reset and device wipes; i can't get my phone to believe that it does in fact have more than that; in the "about" screen it says it has something like 451mb memory available it apparently can't access?
i've been trying to run a task29 to wipe it entirely before putting vbnrom reloaded 2 on it but everytime it gets to the part where it verifies my phone information it says it can't connect, while simultaneously my phone will pop up that stupid annoying low memory message D;<
if anyone has any light they can shed on this it would be really appreciated as i'm absolutely flabbergasted at this.
my radio is 2.12.50 btw
Related
I am experiencing random lock ups and freezes. It happens especially when I receive texts and incoming calls after about 30 minutes of no use. WiFi does not work either. It is very annoying and frustrating as I lose the text or miss the call. I have to reset the phone to get it working again. Sometimes it takes several resets.
EDIT: Other random tidbit...after playing with the phone a bit more, I have found that the phone functions perfectly when plugged into the power outlet-WiFi, texting, incoming calls...Maybe it has something to do with the power settings when not plugged in?
Is anyone else experiencing this?
Does anyone have a guess at what might be the problem?
I am running:
SPL 2.47
2.42.50 radio
DCD Custom 3.2.6
I have never had this problem until about a week ago. I am wondering if it is a hardware issue as I have tried re-flashing several times. It will work well for a few hours then act up again. I am thinking about relocking my phone and taking it in for service, but that is a last resort.
Thanks in advance for any help.
same thing happened to me. It started ever since i switch out for a new battery though. I seriously think it's my battery that causes these random freezes.
hmmm...it does seem to be a battery issue as it works while plugged in. Is there any way to reset the battery somehow?
Freezes here too
I've had my phone freeze twice in the last two days. Yesterday at work, connected via activesync, when I disconnected the screen wouldn't come on. Then today I was connected to the wall charger, disconnected and the screen wouldn't come on again. Had to remove the battery both times to get the phone working again.
My experiences
When the 6800 came out I liked it so much that I hooked my entire family up with one and I have seen more problems than a lot of people. I just thought I would share some of the freezing problems I've seen and what I've dont to replace them. And if the device is not freezing when it is plugged into the wall is the screen off like in idle, or is it real dim and still up? And one great thing you can do to reduce daytime freezes is to leave the device off at night when you charge it (if you can stand to do that), or at least soft reset when you grab it to start the day.
1) The most common reason for lock ups that I've seen is memory drain. It is caused from programs you've installed that continually run in the background. The biggest killer is recieving calls when the phone has been sitting at idle too long or trying to run activesync or an internet browser.
Fix: You can try to go back and remove the programs that you've recently installed till you lack this problem, but the ultimate fix is to hard reset.
2) Some registry edits have poor efects on the way the phone performs and this is when it seems everything is good, you are keeping the memory clear with a task manager, yet it still freezes in the middle of doing something.
Fix: Every titan seems to act a little differently than others. The only time I hack the registry is when one of my family members phone is having an issue, or when I get bored and I want to mess around with my own's performance. The remedy for this is installing the stock carrier rom and then moving to a rom of your choice. Read the posts too. Make sure the radio is compatible with the rom. Trust me in this forum you can find anything.
3) Memory boosting software like memaid or oxios close apps are great, however, with some programs they interfeer with each other and cause problems.
Fix: Forget this memory programs. Find a rom with good memory management.
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
bdlane said:
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
Click to expand...
Click to collapse
A hard reset or rom flash will wipe your registry since it's included in the new rom and also stored in the hard reset rom. So if you screw it up, worse case you hard reset, or reflash with a new rom/same rom, doesn't matter.
You can also back up your phone prior to making any changes, and if you screw up, hard reset and then restore the backup.
BTC
Hello,
I've been struggling with a problem for about 5months and finally rationalized what happens and now seek a fix. Yes, sometimes the device is slow. It can go about 3days w/o need for reboot, but if I sense it slow, I bounce it cleanly.
My HD2 will freeze, by itself left alone, or after charging, or while in use. A battery pull reset will only get me past this. At first I thought it might have to do with low storage space but it occurs even after clearing space and bouncing.
When the device boots from the pulled battery, it gives the time & date of the last time I had to pull the battery (say 3 days ago). This is consistent on each occurrence. It seems on the battery pull, the device looks to the registry or some other pointer to the date/time rather than the device hardware clock.
Once the unit boots, if I don't notice, it want to attach to my phone provider, and in the logic of the negotiation, the unit freezes as it cannot sync with the phone provider as the date/time is not in line with their connect criteria.
FIX is boot device, do not enable phone radio, set time & date manually, enable radio for phone and a sync can be done to enable phone system time synced.
The question is, What can I do to stop this sloppy phone from going back in time, or crashing on me when I want to make a simple call?
I think a tweak of some sort has to be in place to enable the negotiation with the phone provider as well.
using WM65, the boot screen gives:
R 2.15.50.14
G 15.42.50.11U
D 1.66.76641
&
device program storage now: 180MB free
device storage now: 50MB free
card storage now: 350MB free
I've had this unit a year now, and recently started using the LeoCpuSpeed at 998MHz thinking it might help functionality.
thanks in advance,
_h
still happens, any fix?
hyphe said:
still happens, any fix?
Click to expand...
Click to collapse
SOrry if you already mentioned it, are u using custom or stock ROM?
Sometime, registry tweaks might cause those problems.
I would suggest you to flash the CORRECT STOCK ROM and see if those problems still persist. If yes, there might be defect/damaged to any of the components of your device
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment First.txt
View attachment Second.txt
View attachment Third.txt
So. Bit of an update.
Turns out it's not actually just getting locked in the bootloader. It seems it's been doing a soft reboot.
I've been running "adb logcat" whilst trying different things, until the phone crashes. That's how I got the previous logcats. However, upon "rebooting" the adb logcat continues to run. I can provide a logcat for those, should anybod want it.
WeButterTheBread said:
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment 4613124
View attachment 4613125
View attachment 4613126
Click to expand...
Click to collapse