Database Develop

Most likely a Software Problem [help]

hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.

thelistening said:
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
Click to expand...
Click to collapse
Try to upgrade to the 27.08 Radio/SPL combo. Follow all of the instructions contained within that post. It will suggest you also re-install your recovery. Do it. Once all of this is said and done, if its a software issue, it should be solved.
I had this same issue prior to the upgrade, and all is fine now. Mine didn't FC tho. If I touched the bottom of the screen, it would select something at the top. any questions or a perfect walkthrough, my direct email to my cell is in my info on the left.
<<<<<<<<<< Over there.

ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.

thelistening said:
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
Click to expand...
Click to collapse
Oh crap. You have the funky color camera?! That might actually be a hardware issue. But we can certainly try this out. I have the gTalk PC app, and it's up and running now if you wanna run through this.

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks

That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.

djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!

ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??

duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out

Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution

jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.

dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

[Q] HEELLLPP!! I didnt strapsafe, now I dont know what to do!!

To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.

Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.

Issues upon issues upon more issues!

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?

m7 sprint - random reboots only w/non-sense roms

Alright, I have an issue that's been getting ridiclious the past few months. Ironically it all started when trump took office, but that's another subject....
On any rom besides a sense based rom, and i've tried alot, AICP, CM, Lineage, candy, etc etc. I'll have random reboots when getting text messages, or random reboots when trying to send a text message. I've tried all these roms wiped, with and without gapps, and i end up with the exact same result. Straight up random reboots.
The moment i wipe and restore the stock sense i imaged immeditately unlocking, no issues. I flash badboyz, no issues. I've been experimenting the past few months, and i can honestly say it only happens on non-sense roms. I thought it was because of gapps. So i ran CM11, which has been flawless since 2014, and without gapps, after a fresh flash and boot, the 1st text message i receive, instant hard reset.
The phone was s-on when i bought it, i took the latest OTA to grab carrier and OEM software and radios, then i did only the bootloader unlock, flashed TWRP, imaged my system. that was back in 2014 when the phone was first released. Since unlocking i've been running cm11 flawlessly for several months, at times a week or so of uptime, and i use my phone heavily.
Now it's to the point, when i flash a clean CM11, no gapps, just sitting on the table with the tethering on, either USB or wifi, it'll reboot. Sometimes itll get into a reboot loop and it'll take up to 10x of hard resets until it gets android fully loaded (mind you no gapps, no 3rd party, just the rom itself) before it's usable, that's if it doesn't run itself dead with the bootloops.
What's blowing my mind, if it's hardware, then why no issues on sense? Why only issues on non sense, and why now and not before? and the differences are all i can think of is software from: htc, sprint, google
When those 3 are removed, stability issues. but why now and all of a sudden?
anyone want me to supply something from adb? this has truly got me interested. I'm willing to copy and paste and upload some info. I'm really wondering what this issue is.
Thanks!

Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk

swerff said:
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Here's what I would say:
Because non-Sense ROMs don't have the same drivers, HTC developers, etc, they tend to be less stable as a group. The developers work hard to mitigate that, but the random reboots are the hardest for them to figure out. If you go through non-Sense ROM threads for years, you'll see that common complaint.
Now, as for CM11 being solid and now it's not, my guess is that updated firmware, radios, etc caused it. CM11 is quite a few years old and was written under older radios.
When the m7 was my daily driver, I had good luck on these three ROMs. They had the occasional reboot, but it was about once a week at most and rebooted right back in.
Resurrection Remix
PAC ROM
NusenSeven (Sense based from the m9)

I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk

I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk

swerff said:
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Misread and thought you updated radios recently. Not sure how replacing the battery would help, but you never know.
I had been running the three ROMs mentioned above with minimal issues when I used the m7 as my daily driver. I had run the latest RUU (see development section) to update to the latest radios, firmware, etc first. As I recall, all three were good. NusenSeven being stock based was most stable, but the others were good too.
swerff said:
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Worth a shot, but your instability seems relatively reproducible. Personally never done it. So I'm not sure that would help, but like I said before, you never know.

Well, tonight I'm going to replace the battery.
If that diesnt help, going to relock and ruu just to make sure, unlock and flash the same zip I've been using for years.
If there's still issues, something is going down regarding big brother not enjoying his stuff on my phone.
That's my take and opinion.
Sent from my One using Tapatalk

Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk

swerff said:
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Great! I'm glad it worked. It is odd, but what you say makes sense. Maybe the Sense ROM had something optimized in the kernel or ROM that the non-Sense ones don't. That's why I love this site; I learn something new everyday. Thanks for putting the results of your work in the thread for future members who may have the same problem.:highfive:

Well, update
It eventually got back into its old habits of randomly rebooting after ending phone calls or sending /receiving messages.
Soon after that it had issues if not coming out of airplane mode, which would require a hard restart, soft restarts were unsuccessful.
About week ago my son wanted to play on it, so i enabled airplane mode so he wouldn't accidentally call anyone.
Enabled airplane mode.
Handed phone to him.
Within 30 seconds I took it back, and in this time frame all he was doing was holding it/touching screen.
The phone now endlessly reboots to the initial HTC logo for maybe 5 seconds, goes black, and repeats. It will do this until the battery is dead.
Plugging in charger results in no battery charge state, screen or LED. After several moments of being plugged in with no signs of life, it'll light up to HTC screen, only 5 seconds later to go black and repeat, endlessly.
Holding power + volume down I can access the bootloader, which before it resets again I can pick recovery option.
It'll then reboot into HTC screen, saying entering recovery up at the top, but never doing so, and continue with boot loops.
The power button is not stuck, as holding only volume down will not encourage bootloader initialization.
Ideas?

swerff said:
Ideas?
Click to expand...
Click to collapse
It seems to have gone beyond the Sense working but non-Sense not working issues it started with. At this point, I'd probably try to RUU the thing back to stock and see if that fixes it. If not, I'd venture something hardware related. I wrote a guide on how to do this mainly because I kept forgetting all the steps. Hope it helps.
https://forum.xda-developers.com/sp...de-reset-phone-using-ruu-htcfastboot-t2876110

This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk

swerff said:
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
That's too bad. I don't know what to tell you my friend. I saw you could access the bootloader and select recovery, but if it's not stable enough to stay in fastboot, then that's beyond my knowledge capability. At this point, if it were me, I'd buy a new device or take it to a repair shop.

I'm investigating surface mount memory readers and the like.
I'm hoping to solder up something to pull the memory in binary.
The phone wasn't encrypted. There's a handful of photos I'd love to recover. Not having an external sdcard is stupid.
Sent from my One using Tapatalk