Hey all! It looks like dev forums are really the main places this is being discussed, so I thought I'd drop in and see if any of y'all had noticed this or figured out a fix for it:
I'm running Linux on Dex from my Note 9. Goal has been to set up Eclipse for code purposes, but also to see how useful it might be as a pentest box. At least 10 times now I've set the thing up, installed everything I want, followed what Samsung indicated were 'proper' shutdown procedures, and like clockwork when I plug it in again the next time the whole image is glitched out. The last time I did this was last night, and after I plugged it back in the screen was white with an invisible terminal window, where the green text only showed up when I moused over it. That's the first time it's done that, but it regularly either turns black, or elements render on top of each other, menu bars don't work, etc.
As far as I understand, we should be able to hover at the top of the screen, hit the 'back' arrow, accept the option to shutdown the container, then exit out of LoD, and then unplug the phone in order to close things 'gracefully'. When I have absolutely nothing installed, it seems to work, but the second I start installing tools from the Kali distro, it loses its mind and glitches everywhere. Granted I'm using Katoolin for those installs, but I would have imagined if they install properly and it's shut down properly, it ought to work, right?
Any of y'all have any experience with yours doing anything like this?
Related
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.
I rooted the first day and also did lag fix. Worked fine until this afternoon I haven't installed anything today and the only root app on the phone was (besides SU, BusyBox, etc) Root Explorer. Suddenly today while trying to update Twitter and Facebook via the Samsung Feeds widget I get a "network communication error". So I pull the battery and turn the phone back on and I get a very long Verizon splash screen and then it goes black. The capacative keys will light up and blink when you touch them but no other phone action besides that.
Any idea for a fix before I have to go get a replacement? Tried to run the unlagfix batch file and of course I get permissions denied since I can't SU from the phone.
Guess I got a little excited before trying the basics, here's what I did to fix it in case anyone else has the same problem...
1. Wait for the boot animation to stop and get to the black screen
2. Connect USB to PC
3. Run cmd.exe
4. cd to your Android SDK tools directory
5. Run "adb reboot recovery"
6. Once the recovery menu comes up volume button down to "restore factory settings" and hit the home button
7. Volume down to "clear cache" and hit the home button
8. Reboot phone
Something similar happened to me on a BB and also on my original Droid.
What worked: Put it on the charger. Walk away, watch a ball game, or a movie and a half, get some food, think about something else for about four hours.
Come back and try again.
It's a weird thing with these devices. As near as I can figure, they can actually run the battery down faster than the OS/firmware realizes, and then they need a good bit of charge to get running again. In all of my own cases, running off of AC didn't help, either, which really freaked me out.
If it's still not working by morning, start thinking about taking it in.
Good luck!
Updated, got it working.
kvaughan said:
Updated, got it working.
Click to expand...
Click to collapse
Awww Right!
Next time, what you may be able to do is run adb logcat to view the realtime log from the phone to get an idea of what's going on.
It's also good to remember that the rage*.bin file that you put into /data/local/tmp is an exploit that should get you root access back temporarily.
Of course, the steps you outlined above are also very helpful. Thanks!
The phone has been working very well, no problems of any kind. It is rooted and I'm using Go Launcher along with Widget Locker for the lock screen.
I just updated the Widget launcher application and everything was working just fine.
However, the last time I woke the phone, the display was bonkers. The lower 1/3 of the screen was grey, over writing the icons for the functions located there on the home screen. When I scroll through the home screens, the lower 1/3 continues to be greyed out. However on close inspection, the underlying icons can bee seen and are activated with a touch as normal.
The overwriting seems to be somewhat of a repeat of the top 1/3 of the screen. With the moto lock screen there is a digital clock displayed in the upper part of the screen and that is showing up in the lower third also.
This greying out is more like a Ghosting effect. The screen also has a general background flicker in the upper section that is not greyed out or ghosted over. I did nothing like dropping the phone or dunking it. This does have what I would somewhat characterize as connection issue. BWDIK.
Does anyone have any idea as to what could have caused this to pop up as a problem? The new version of Widget Locker seemed to be doing just fine and I had configured it to take more icons in the ICS default theme. Everything was going great until it suddenly was not.
Suggestions or accounts of similar problems would be appreciated. I sure hope there is a cure. The phone has been great and darned capable. I'd hate to have to change it out.
Reboot your phone.
If that doesnt work, make a backup in Clockwork and wipe data.
If that doesn't work, it's hardware related.
Sent from my DROIDX using Tapatalk 2
Thanks for the help.
Could you be a little more specific as to how to make the backup and then restore?
I've restarted the phone several times. That won't clear it up.
Download droid2bootsrtap>install>flash recovery>reboot recovery
Scroll to backup/restore (use vol keys select w/ camera key)
Select backup, let it do it's thing
Select wipe data
Reboot
Thanks for the additional help.
That did not seem to get the job done for me. I still have the problem with the top third of the screen being displayed again as an overwrite of the bottom third.
One odd thing did occur while I was working on this. I had the phone connected to the charger. It was in "sleep" mode with a dark screen. I picked up the phone, pushed the wake up button top. and at the same time I disconnected from the charger. When the screen first displayed it was displaying correctly and clearly with no overwrite. I don't believe I have a failed display in the sense of dead sections or pixels. It seems that there is some cross connection in how it is being addressed so that the upper one third is being written twice, one of those being an overwrite of the lower one third. The icons that should be showing in the lower third dispaly are visible through the "fog" created by the overwrite.
I have contacted the local smartphone Mr. Fixit and ordered the new screen. The problem may be deeper than that though. Any other suggestions would be appreciated. I like the way the phone operates and am getting to understand it after about a year of working with it. It is rooted with the handy WiFi tether operating, along with a few simple customizations. It would be great to get it sorted out as I don't want to go the upgrade route at this time.
Have you tried reSBFing? I had a similar problem, except the lower 3/4 of screen went black. Got an insurance replacement, but when i was wiping my old phone, i SBFd, and the screen worked again. Granted, i still had to send the phone in, so no idea how long it would've lasted.
Sent from my DROIDX using xda premium
Nothing to do with SBF'ing. The phone is rooted, and it worked the first time, several months prior to the problem.
I finally got the screen replaced and that part is working well. Nice and bright with no ghosting of another section. However, I now have developed a problem with the dialer turning off the screen when the call starts dialing. No capability of using number pad or even hitting the End Call button. Returns to the default lockscreen when call ends from a disconnect on the other end. still a great mystery.
Question: how's your camera working?
Sent from my DROIDX using Tapatalk 2
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
I've used had my Ouya for a few years now and today it just locks up. I get static audio, vertical lines, and lockups. I took the Ouya out and I noticed it is super hot. The fan only kicks on for a second during boot but never again... so it just seems to sit there and fry.
1: That fan should be kicking on.
2: It only locks up when I do certain things. Like Search, Factory Reset, nagivate menus, do stuff. If I just let it sit there, it typically won't lock up, but has.
I am kinda at a loss. I am thinking of reflashing another rom on it to see if that works. It boots up normally just locks up after about 10min. I am having problems with getting ADB working. When I connect it, it connects as a Media device MTP but no ADB driver being requested. I also cannot see the device with adb. I've tried the sysrq+Alt+i methods but it just reboots to a black screen with a ! on it. Doesn't really do anything from there.
Any suggestions?