Hero rom black screen possible fix - G1 General

When I installed the Hero rom, everything seemed fine until I tried the htc setup, it forced closed and left me at a black screen with the status bar, and a lock screen only.
Well, I finally managed to get the rom working. When I first tried the htc setup, I would try to do the test out the virtual keyboard screen, and that's when it would force close. Well, I tried skipping that step, and everything seemed to work fine after that.
So, if you're having the black screen after flashing, try skipping the step witht he virtual keyboard and see if that works. Hope this helps at least some people.

Related

Issue with Auto-Rotate

I have encountered an unusual issue (bug?) on the HD and wondered if anyone else had seen the problem (and found a solution!)
First the issue:
When I rotate the device to landscape, applications initially rotate properly. However, after a few seconds the phone dialer screen appears (in landscape mode). It blinks once or twice (like the screen is redrawing) and stays there for perhaps five seconds before switiching back to the original app. However, even though the device is still held i landscape, the application is now in portrait mode too and the only way to get it back to landscape is to rotate the device back to portrait then to landscape again...at which point the whole cycle repeats.
Things I have tried to clear the problem:
So far, all I have tried is a soft reset, which I thought had cleared the problem at first. Sadly, however, it's back.
Repeatability and conditions:
I've only done one soft reset so far as I wanted to investigate a bit further first
It initially happened in Opera with GSen off (it is installed though)
It happens whether or not GSen is active
It happens in all applications, not just Opera (obviously GSen is active when it happens in other applications)
I don't have a HD (yet) but i've read somewhere that GSEN is not working correctly on the HD. There is suppused to be a tool called "Gyrator2" which does the same but is more stable on the HD.
regards jan
hausen said:
I don't have a HD (yet) but i've read somewhere that GSEN is not working correctly on the HD. There is suppused to be a tool called "Gyrator2" which does the same but is more stable on the HD.
regards jan
Click to expand...
Click to collapse
May be an option, but I haven't had any problems with GSen and I seem to get the issue whether or not GSen is active. I have even had it in an instance where GSen had not been activated since the previous reboot.
Thanks for the thought though, I'll investigate...
please don't use GSen since it's heavily bugged atm for the HD.. Gyrator2 is an option even though consumes a lot of cpu power (device become slow whenever Gyrator2 rotates the screen)
iain.fraser said:
I have encountered an unusual issue (bug?) on the HD and wondered if anyone else had seen the problem (and found a solution!)
First the issue:
When I rotate the device to landscape, applications initially rotate properly. However, after a few seconds the phone dialer screen appears (in landscape mode). It blinks once or twice (like the screen is redrawing) and stays there for perhaps five seconds before switiching back to the original app. However, even though the device is still held i landscape, the application is now in portrait mode too and the only way to get it back to landscape is to rotate the device back to portrait then to landscape again...at which point the whole cycle repeats.
Things I have tried to clear the problem:
So far, all I have tried is a soft reset, which I thought had cleared the problem at first. Sadly, however, it's back.
Repeatability and conditions:
I've only done one soft reset so far as I wanted to investigate a bit further first
It initially happened in Opera with GSen off (it is installed though)
It happens whether or not GSen is active
It happens in all applications, not just Opera (obviously GSen is active when it happens in other applications)
Click to expand...
Click to collapse
Will the problem go away if you uninstall GSEN? I mean, not just making it inactive, but to completely remove it.
eaglesteve said:
Will the problem go away if you uninstall GSEN? I mean, not just making it inactive, but to completely remove it.
Click to expand...
Click to collapse
Annoyingly enough (in one way) I've not had the issue since I soft reset a few hours ago. I'm keeping a close eye to see if i can trap what I have been doing just before the issue recurs.
I have suspicions about PCM Contacts but have no good reason to, other than the fact the problem started at roughtly the same time as I installed the latest version.
Next step is to try removing GSen, as you suggest, but I want the issue to recur first to see if I can make some sense of what's happening...
The problem isn't with Gsen.
This happened to me while browsing, it just kept flicking back to portrait and then coming out of Opera.
As a result I thought I'd install Gsen and everything worked perfectly for about an hour. I left the phone (locked) for a while to attend to a few other things and then it started again.
Now I've not had the phone long 10 days or so but I have installed a lot of cabs and applications. At first I thought it might be a bug on the HD but unfortunately it could be anything.
What I will say is that I didn't have this problem before I added new tab icons (manilla), installed Schaps AC or changed the calc skin. Gsen was next on my list.
A soft reset seemed to work for me.
Hope this helps.
Mav.
Switching the phone on and off seems to clear the problem for a while. Anyone solved this?
My solution
Just wanted to say that i had this exact problem.
Fugured it had to be a problem with som custom stuff i had installed, and so it was.
Started uninstalling backwards from the last installed thing, and found that the problem was caoused by a custom status icon cab I installed.
Named Colored Top Bar WWE ST.cab
If you have something similar, this could be the problem.
(BTW, I'm not bashing the author of this file at all. Everyone should know that installling custom stuff is your own responsibility)
Mavrick said:
The problem isn't with Gsen.
This happened to me while browsing, it just kept flicking back to portrait and then coming out of Opera.
As a result I thought I'd install Gsen and everything worked perfectly for about an hour. I left the phone (locked) for a while to attend to a few other things and then it started again.
Now I've not had the phone long 10 days or so but I have installed a lot of cabs and applications. At first I thought it might be a bug on the HD but unfortunately it could be anything.
What I will say is that I didn't have this problem before I added new tab icons (manilla), installed Schaps AC or changed the calc skin. Gsen was next on my list.
A soft reset seemed to work for me.
Hope this helps.
Mav.
Click to expand...
Click to collapse
i cannot conclusively say if it's a problem with GSEN or not. but i had the exact same problem with GSEN installed, but not activated. i couldn't solve the problem so i did a hard reset (i didn't bother uninstalling gsen and try it again). i don't have problems anymore, but i do have all my old applications installed, except for GSEN. i currently do not have gyrator or any other screen rotating app installed. i don't have a need for them at the moment. so i don't conclude anything, you can deduce from here.
Bascha said:
J
Fugured it had to be a problem with som custom stuff i had installed, and so it was.
Started uninstalling backwards from the last installed thing, and found that the problem was caoused by a custom status icon cab I installed.
Named Colored Top Bar WWE ST.cab
Click to expand...
Click to collapse
I have the same Top Bar and don't have the issue you guys have been describing.
my problem is kinda similar but a little different, my opera works fine w/ landscape and portrait, but when I try to access My Faviorite in landscape mode, it would only display in portrait even though I was holding it landscape and the second half of the screen was still the page content. it's weird and I still didn't got time to do a hard reset first, any one experience this?
I have this issue (damnit), and I am using those color-top-bar-icons. However, I have never been using GSen, I am using gyrator 2. Can anybody confirm that it is top-bar-icons that's causing the problem?
I have the issue and I don't have the top bar colored icons installed.
I do have Gyrator 2 but the problem still occurs when Gyrator 2 is not running.
I don't know why it occurs and it goes away by itself...seems sporadic.
I got Gyrator2 on mine too, but I don't see people in Gyrator thread complaining about this happening...um...do I really need a hard reset for this?
(by the way, I disable all rotation and only enable the programs I used, of course Opera is disabled)
update from mine, I just did a hard reset the the landscape favorite in Opera still got messed up, so I restored my device and gave up. gotta wait for new official ROM maybe...

"Loading Sense" issue on startup sometimes

Not really a bog deal I hope but it would be nice to avoid it altogther.
On a few occasions I have restarted the phone i note that after the splash screen it goes to the wallpaper and "loading sense" appears at the top with messaging or some such in the top left corner where it says "start" normally.
If I do nothing it will stay like this and not automatically load the Home screen - ie screen will go dark and even activate screen lock [I have looked for various lengths of time!]
If I touch any button or the screen at this stage it will go to the Home Screen and the screen works fine.
Anyone else get this irritation and anyone know why it happens and/or how to make it boot into the Homescreen normally all the time?
Thanks
what rom are you using?
I had this exact issue myself. Not really a problem, as I just touched the screen and Sense appeared immediately. It was obviously running, but the screen hadn't been refreshed for some reason.
All I can say about it is that I've not had it since upgrading to a newer ROM. It did happen on 1.66, but now I'm using a Dutty ROM (v0.8), which is based on one of the v2+ ROMs.
+1 I get it on stock 1.66 WWE, I just press the X and it carries on as normal.
I am using wwe 1.66 stock rom on an unlocked phone on voda
I get this whenever i restore a prior SPB backup file. I always have to load it twice then it works for some reason.
I've had this issue before and think its to do with the messaging app, as mentioned above hitting x in the cormer works.
Doesnt seem to be HD2 specific though as its also happened to me on my old Polaris
I got this from time to time.
Look at the soft keys. When it happens with me, I always see the soft keys of Messaging. I suppose Inbox is trying to connect. I just press the home key to call up the home tab.
I get this from time to time, doesn't seem to be any particular pattern to it. But as above touching the Screen/Start seems to clear it.
So is everyone just going to leave it?
Could it be a program in the Startup folder in Windows?
Ever since I installed pocketMax's PhoneAlarm, it happens every time the phone is booted up.
It does goes to the home screen after about 60-90 secs.

[Q] Serious Touchscreen Lag Issue [UPDATED]

First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...

[Q] Droid X Screen Problem - Hardware or Software?

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

Screen Behaving Abnormally

my nexus 4 is behaving abnormally... the lower part of the screen(1 cm) is unresponsive to touch(tested with pointer location) and sometimes out of the blue the touch input for the entire screen stops working and works after a couple of lock/unlock and the sometimes the phone starts pressing anywhere by itself.... I was running pa latest version... it was working fine ... so i restored the phone to the old pa since i need pie because bottom screen not working= no navbar.... it still didnt work and screen with similar problems. have anyone experienced something like this... is it something with the screen or other hardware parts ... help!
i had this issue with the bottom right side and a irresponsive touch screen at times, it was fine at beforehand, i backup and reflashed and it worked, using PA. it depends if the phone was fine for months before or something that has happened when you first used it. try restore to stock rom and kernel
If you've already done a factory reset, it's likely a hardware problem. You'll probably have to have someone repair it. If you're really desperate, I guess you could try putting it in the freezer for a few minutes, and seeing if that fixes any connection problems. That might just make it worse/cause other problems though. It works with hard drives on occasion.

Categories

Resources