Rooted about a week ago when revolution came out, and everything went smooth. The only issue I had was when i flashed my first ROM the dock on the sense 3.0 homescreens is pixely around the edges. I know this isn't a major problem but its very annoying and i really want it fixed. I've looked all over and can't seem to find a fix for this. I've flashed a few different roms, wiped, cleared data, ect and nothing seems to help. Any help greatly appreciated thanks!!
lavcoles said:
Rooted about a week ago when revolution came out, and everything went smooth. The only issue I had was when i flashed my first ROM the dock on the sense 3.0 homescreens is pixely around the edges. I know this isn't a major problem but its very annoying and i really want it fixed. I've looked all over and can't seem to find a fix for this. I've flashed a few different roms, wiped, cleared data, ect and nothing seems to help. Any help greatly appreciated thanks!!
Click to expand...
Click to collapse
its a known issue even htc know about it but here is a temp fix http://forum.xda-developers.com/showthread.php?t=1194882
thank you, exactly what i was looking for
Related
So you may have read in my last thread that I was haveing problems with eaglesblood its ashamed too because it really is a kick ass ROM but i think it needs some work. No matter what I do I keep loosing my data conection. I just Installed Bionex and it runs great and it had no problem connecting to the network but it doesnt have the cool tweeks that EB has. I think I am going to try cm7 though. The things I really want are first the power controls in the notification bar that was kick ass nex profiles I liked that the ability to customize the lockscreen that was cool too.
I would like to know if it is just me or if others are having this problem too. There has got to be something I am doing wrong I doubt they put out a ROM that has that many problems and All I hear is good thyings about EB so it has to be me. Please someone help me fix this because I am tired of dam stock GB Help Help Help!!!!!
it happens to me too, i just power phone off and on it comes back.
yeah it only happens the first time I power off or reboot after install the rom I see there is a new thread today about data not working on ROMS based on 2.3.4 or 2.3.5 but it works fine on 2.3.3 what I did was a hard reboot and it started working again.
Charlie
Hi guys,
I've come from a Rooted/Rom'd Hero and just got my Sensation yesterday, it's already been rooted and had quite a few roms on it, but I think I've found one I think I'm going to use daily (Pyramid3D v7.4.0), though for some reason the text is slightly stretched, and that's putting me off quite a bit as everything looks out of proportion, just slightly
Anyone know how to fix this/if it's a current problem?
(Would've posted on the thread, but I've not got enough posts lol)
Thanks,
Dan
edit; re-installed the rom and still does it :/
First off, I just want to say Hi to everyone on the forums, this is my first post, but I've been lurking for quite a while, waiting for the right time to flash my phone –Should have done it sooner
Also, I want to thank everybody involved here, especially devs, for all of their hard work! -- I’m really not trying to suck up here… Just trying to portray sincere gratitude --
Anyway, I tried searching the forums here for related issues, as well as, the interwebs, but didn’t find anything relevant. So I apologize in advance if this is a known issue or a repost… Also, I tried posting this issue in the Gummy 1.01 release thread, but I’m a newbie so, I have to post it here:
This past weekend I finally got fed up with the buggy STOCK ROM for my SCH-i500 (Fascinate) and took the plunge and installed the latest Gummy build available for it (1.01). Everything is running very well so far, and I only have a few minor gripes, but all in all, it’s pretty awesome! Except for one big issue that I found…
If I try to add a photo widget to any of the launcher home screens, the screen goes black, and the bootup animation starts up, followed by a window that states “android.phone has stopped”. This is how I did it:
Menu>>Add>>Widgets>>Photo Gallery>>Choose an image>>[select an image]>>Crop.
This does not happen when I choose the other two options (“Choose an album” or “Shuffle all images”). I think this is either an issue with ICS 4.04, or Apex launcher. I think this because the same thing happens with my friends Galaxy Nexus; he is running Liquid ROM - not sure what version - based on ICS 4.04 with Apex launcher. It’s a completely different phone and he has a different kernel, which makes me assume it might be related to ICS 4.04 and/or Apex. … I’m not sure though because I’m not a dev…
Is anyone else having this issue?
*Update: Tried it again, and it completely crashed the phone this time. I had to pull the battery out to boot. Also, the phone started in “Safe Mode”. I just rebooted one more time, and everything seems fine again…
I'm having the same problem with my Verizon G NEX, Ive searched online and haven't found anything except for this post its a pretty strange bug if you ask me. anyone know of a fix ?
Just an update for anyone who comes across this thread... The issue has been resolved in the updated version Apex that just came out (v1.1.0).
Hi all,
My brother owns a Nexus S that I've helped him unlock, and consequently installed CWM and CM7, then CM9 and now CM10.
A few months ago, while on CM9 he started experiencing FC's that did not specifically state what app was causing.
This has increased in frequency, and wiping everything and starting from scratch in either ICS or JB has yielded no change.
He has Radio i9020xxki1, and latest CM10 available as of a couple days ago.
I am attaching the bug report generated when FC'd, but I don't really know how to tell what is causing the issue from reading it.
Any help would be appreciated!
madhouze said:
Hi all,
My brother owns a Nexus S that I've helped him unlock, and consequently installed CWM and CM7, then CM9 and now CM10.
A few months ago, while on CM9 he started experiencing FC's that did not specifically state what app was causing.
This has increased in frequency, and wiping everything and starting from scratch in either ICS or JB has yielded no change.
He has Radio i9020xxki1, and latest CM10 available as of a couple days ago.
I am attaching the bug report generated when FC'd, but I don't really know how to tell what is causing the issue from reading it.
Any help would be appreciated!
Click to expand...
Click to collapse
Nobody knows or can give me hints on how to decipher the bug report?
Hey guys,
My phone has been acting weird lately. It starts by, lets say, lagging.
I reboot the phone and it gets stuck into a reboot cycle... Great. The only way to fix this is to restore a back up.
I tried reinstalling the rom a couple of times, which resulted into the same problem after a couple days of use.
I've also tried the bubba kernel which, again, resulted into the same problem.
Some specs:
S-OFF, Supercid, HBOOT 2.15, RADIO 1.11
Not sure which ones are actually relevant, but I mentioned it anyways
Any suggestions/questions are welcome. Anything. Thanks for reading.
Well, since you have SuperCID and S-Off you clearly have a basic knowledge of what you are doing. I can only think that it is the kernel or the ROM. I'd never mess around with a kernel, because that is probably the only thing I trust HTC on, that's why I've kept stock. Have you tried another ROM? You might be madly in love with the appearance and the functionality of the ROM, but if it is laggy and is causing you to have to repeatedly restore backups, then you are best off using a smooth one. I also use the CM10.1 nightlies, and I agree with that. If you are seeing screen tearing, then that is not your phone being a retard, that is a known bug that they are going to address. However, some suffer worse than others. My One S is at the grand age of one year and is suffering quite badly from it, yours may not. Also, if you're talking about the RAM dropping from around 350MB at boot to around 150MB in 24 hours, that's pretty normal too.
The screen tearing is rarely noticeable, its actually almost non existent.
Im running the cm10.1 kernel that came with the rom.
I did try ViperOneS but it wouldnt even go further past the splash screen throughout the first reboot after installation in Aroma. Did flash clear fastboot cache and flash boot.img but it didnt work so I gave up on that, lol.
This morning I decided to back up my current rom and restore it after wiping everything, something I only do when installing a new rom. So far my phone is behaving like it should.
I just opened the thread to get help when needed and to get idea's as to why it's behaving like that.
Thank you for your response
Sent from my One S using xda app-developers app
Somebody who has a greater knowledge on this subject than me, most likely usaff, will pop up within the next couple of days and give you some better help than I could. I've only known what I'm doing for a couple of weeks, so I'm new at it, but since I'm a bit of a noob I can give advice that noobs will understand. Since you're clearly not a noob, I didn't help that much.
Maybe some more info is/can be helpfull.
Wich nightly you running?
You say it runs for few days, then you get problems, So it runs correct after initial install.? If So, what programs do you install/use (wich might cause tot make it unstable)
Can you tell how you install the ROM in steps.
Verstuurd van mijn HTC One S met Tapatalk
I haven't experienced this problem in a while anymore. I think a full wipe/reset did the trick before restoring a back up. Thread may be closed