Database Users

[Long]Trials and Tribulations of my G1. Issues and Insight.

WARNING This is a long post describing various events of my G1 and things I was going through, so Im basically doing a dump of my thoughts and possible reasonings to put everything I can report, case it is a ROM, Hardware, or Software flaw somewhere or just user error. But since this forum is about feedback for devs or rom providers =)
Ok I dont know where to begin with this post. Last night my G1 needed a wipe. Why? Cause all it did was reboot over and over not getting past 1st home screen, then finally android screen. What happened before this? All I have of the things going on during that time frame was this:
(Now before the below stuff, earlier that day, Quest Live glitched on me, and when I was at the home screen, I tried to scroll left and right and it got stuck half way, which WORRIED me since I thought the touch screen was messed up. To my luck after a reboot and iso alcohol rub down on screen, it was fixed. Tho only after I unplugged it from the car charger (Which seems to really make the G1 % battery jump in record speed.. glicth?) Or Power Manager issues? Tho this wasnt the updated one, so the new one may have fixed the issues the dev said power manager was causing.
I plugged in the usb to a ubuntu running PC. To charge it, thus triggering Power Manager. Same time, I was trying to install SnapPhoto, which it downloaded, but didnt install, I was also noticing abit of lag, So I ran task manager to turn off some apps running in background, Camera, Gallery, Gaming Buzz Widget, Weather app Widget, Calender. (Then as I rem.. I tried to update AdFree when the new version came out.. it didnt install but same time when I tried to load it, it just came up black.. sign of a bigger issue maybe?)
After that of course couple of them came back. Then I tried to change the volume using the side button, It didnt respond, The on screen worked fine tho. So I decided ok, time to reboot fresh on the phone. Rebooted, Then it loaded to home screen before radio signal, then rebooted. After getting tired of not booting, (I had unplugged it from the USB btw which at 1st kept the charging light on before I rebooted it. ) I pulled the battery out. Which MAYBE I pulled it out at the wrong time during the android screen. Cause after that and I put it back in, all it did was goto the G1, then Android cycling screen, but no longer went to the home screen to try to load. Then was too late for this trick, but the Safe mode attempt. Which MAY have worked when it made it to the home screen, but once it was on Android only, safe mode didnt load at all. Just endless stuck on Android. So I had to wipe 1st then I reapplied the JF 1.51 update.zip to fix it and get the G1 to turn on again and boot.
Advice tip: If you can still boot to the home screen "somewhat" next time it cycles, try holding "Menu" in to have the G1 bypass any apps and load into safe mode, which may allow you to uninstall or fix whatever the issue is.
To my surprise. The Apps when the G1 started installing again went to the SD card. (I do not use apps2sd, Only Lucids orig) Now thats when I noticed more hell.. I went to the market to look at "My Downloads" and WHAM, the 10 apps it auto downloaded (Which I guess was a sync) are the only ones in the My Download section.. nothing from my past downloads.. Which is 110 more apps.
Advice tip: Use Atrackdog to "Export" your database to a text file and keep that on your PC. This way if ANYTHING happens, you least know which apps to look for.
Advice Tip: Upon reflection I probably should have made a nandroid backup after 1.51 was smooth. So if you havent, Id suggest looking at it) I know I will once Im set back up.
So now I am left with a interesting ponder. I msged Lucid to see if his scripts would allow me to use my 2GB which had my 1.51 data on it and somehow relink it to the G1 and have everything restored, then recopy to the 4GB which is my current one. But chances are I need to 1 by 1 install again. (Anyone know how you get apps back that arent on the market anymore? Extract from the SD card maybe?)
Anyways now I am wondering, If you install too much to the G1, will it in the end cause a problem? Im not a dev so I dont know how that all works with the ROM builds. But that wouldnt be good news if you have 129 apps, things could start messing up. (Tho not sure if that was a cause for any of the above)
Another thing I learned, if you have a GOOD screen protector on the G1 (Not the one it came with) and it smears up, or gets smudgy it seems it may interfere with the response of the touch screen. Ive notice if the screen thinks its being pressed in, a app could hang, lock up or choke the G1 to where it fixes itself by doing a reboot. Now that sounds odd that the G1 is sensitive to smudges or oil from your hands (If you had a humid hot day). Anyways fixed that with iso rubbing alcohol and a soft wipe cloth. Then rebooted.
Now my next task is to 1: Find out if my Cache since the wipe is running on the SD still, or if its on Internal. The app "Move Cache" I hear could do that, but I heard it messes up market, maps etc.. so not what I wanna do atm. Then I just gotta see if I can restore apps from SD using a app or terminal, which I am studying now, but just wanna end this post for now.
Will post more as I get around to it. Maybe I can restore the market cache manually.

do you still experiencing the touch screen error problem after all the steps you have taken? because i have the same problem. sometimes when i use touch screen to switch screens, the screen get stuck in the middle and shaking. i also cannot select anything correctly by touching. and i've read from various forums that this has something to do with the charger / charging process. i think that my problem occured because i charged using usb cable to my computer. because i never done that before (i usually charge my phone using a wall charger) and when i did, the problem happened.

How I fixed it? I turned off the G1, used rubbing alcohol with a tissue to gently wipe the screen off and clean it. Then turned back on and it was fine.

Unresponsive screen

Android 2.3, 407band, DSC 7.0 rom, Go launcher (default), Zeam launcher (secondary)
Today while using an app called wallbase, I hit the home button while the app was setting a wall paper for me (normally I wait until it says wallpaper set). The home screen popped up but then Go launcher had a FC error (which it has never had since I've been using it). It had the option fc or wait I hit wait. Next my wall paper went black then my screen followed by two vibrations and a notification sound I never heard my device make.
I rebooted to the lock screen with a black background and no service on the screen. It was unresponsive to my touch and after about 10sec. it gave the same two vibrations and sound from before then shut the screen off. The power button did not turn on the display so I had to hold it down for about 20sec for it to reboot to dell logo. From there i went into nandroid and flashed severals roms loaded to the lock screen, rinse/repeat, to find the same result (simple streak, streakroid, older version of dsc).
I reset permissions, wiped cache and dalvik, calibrated screen. Want to avoid a factory reset because I don't have a backup.
Help guys? Mods please move to the appropriate forum.

If all fails and you don't have another alternative.
install the DSC v0.70 update, it shouldn't delete your 'data'.
I would backup your streak, better be safe than sorry.

So I tried letting it sit with the battery out for the night (6 hours) and booting it up this morning with the ac charger. It loads to the same lock screen (standard screen with black background and no service on screen) and all my start up apps loads, it even showed me a text notification. I did notice that the time was wrong though and never changed.
Any one have this issue before? What suggestions are there to combat this? The G.Note doesn't fit into my budget right now. May have to factory reset this and sell it as a last resort.
Help guys?

Outlook for this issue looks grim. Seem others with a similiar issue on different devices have had to factory reset or return it to manufacturer.
Before I do that, is there are any possible way for me to backup some of my app data?
Anyone know if Dell still helps with this device?
I use the app cadrebible often(its the only one I really care about) but it doesn't auto sync/backup and my last manual backup must be from Dec2011 - yea makes me want to cry.

I can load into fastboot, so is there a way I can uninstall a few apps I suspect are causing the issue? Move files from the phones to the sd card/computer?

factory reset. Mod feel free to close thread. -- yes im crying.

Did you try calibrating the touch screen?

Verizon i815 random reboots

Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.

I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium

Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.

Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.

Good luck! hopefully the new one is error free.

I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr

Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.

Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.

Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...

Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.

My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.

gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.

I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium

[Q] Intermittent blank screen problem

I am having a very frustrating intermittent blank screen problem with my Galaxy S4 (GT-i9505). In its current state it has stock lollipop from Sammobile (I9505XXUHOB7_I9505BTUHOB4_I9505XXUHOB7_HOME.tar) flashed onto it. No root.
Randomly after locking my screen, or after a screen timeout, the screen won't turn back when trying to unlock it with the side or home button. The phone and capacitive touch still works completely in the background and I can answer calls and hear notifications coming through, but no display. The display turns back on after a while, but troubleshooting has become difficult as this problem is extremely irregular.
It started when I had stock Kitkat installed from Sammobile. I have rooted my phone previously but the Rom upgrade to latest KitKat took it back to stock. The screen would go blank and after a couple minutes it would turn on when I unlocked it and it would be ok for a couple days. But then the blank screen problem would come back, and its length has seemed to get longer aswell. This includes no display when the phone boots up.
Things I have done so far to try fix it (during the periods when the phone display magically resumes):
- wipe cache and factory reset (no luck)
- reflash stock kitkat Rom, wipe cache and system data (Phone was fine for about a week but intermittent blank screen problem came back)
- Take battery out and drain residual capacitance by pressing buttons while battery out (sometimes worked but extremely irregularly and eventually stopped fixing the problem)
- Put phone on charge and try unlock or turn phone on (sometimes worked in the beginning if I left phone on charge for a while but this method doesn't work anymore)
- Flash lollipop Rom (I9505XXUHOB7_I9505BTUHOB4_I9505XXUHOB7_HOME.tar) via odin, wipe cache and data before and after flashing (phone worked for about a week but intermittent problem eventually came back)
- Reflash same Rom as above AND .pit file (CSB_signed_Fusion3_EUR_0325_V2.pit) via Odin to re-partition tables in case of corrupt partition (Phone was fine for a day but when I woke up in the morning the phone screen wouldn't turn on so this didn't seem to solve the problem)
As it stands, my phone's display pretty much stays on for a day with perfect function, and then randomly the display won't resume after locking it, and stays this way for about another day.
What I would like to know is if I am COMPLETELY starting fresh when I flash with odin, re-partition with a .pit file, and wipe the cache and system data in stock recovery after the odin re-flash. Or is it possible that in an unrooted phone with stock recovery, I am missing something that might remain corrupt and is causing this intermittent problem. Maybe dalvik cache? Or does this get wiped with the odin reflash?
To me it seems like some low level system file is building up and eventually getting corrupt. I am not 100% sure but I doubt it is a screen hardware problem since the display problem only happens when turn the display off and on with the side lock button (it never turns off unless I tell it to turn off or after a screen timeout and it never turns off if I knock it or bump it)
I would really appreciate your help. There is a lot to read here but I wanted to thoroughly explain my situation. Taking it in for repairs is my absolute last resort.
Thanks!

S5 SM-G900F : Black screen/Boot loop; Help?

tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits