[Q] CM10 from BRUCE - Graphic problems (artefacts) - HTC Sensation

Hi, yesterday I flashed my stock HTC Sensation for the first time with CM10 4.1.2 from Bruce. I unlocked Bootloader, flashed 4EXT, wiped all, flashed Bruces ROM, flashed Gapps... I am still S-ON. Everything running great, but I have some graphic problems:
In default Camera app in panorama mode, I have many colored stripes, that are blinking on screen in about second interval.
I find two games not working. "Whale Trails" and "Riptide GP". Both start with black screen and sound only. If i turn off and turn on display with power button, I can see also graphic in Whale Trails, but it has a few stripes with frozen graphic on top of it, but game graphic under this frozen stripes is running normal.
In Riptide GP a couldnt see any graphic by no means...
I have sometimes some problems with colored mini stripes and dots even in Chrome browser, so I am using default CM10 browser.
I tried lower CPU frequency, but this didnt help.
Do you have any idea, where can be problem? THX!

Chrome and panaroma glitches are known problems.. Yet to fix those
As for the games.. Mostly because of using old adreno drivers of gpu (ics) yet to have jb drivers iirc
Sent from my HTC Sensation using xda premium

OK, so all my described problems will be (maybe) fixed in some of the future Bruces ROM? Including newer GPU drivers? So I should wait, or I should flash "something" now to repair it? Thank you for your patience with one noob

Mastegl said:
OK, so all my described problems will be (maybe) fixed in some of the future Bruces ROM? Including newer GPU drivers? So I should wait, or I should flash "something" now to repair it? Thank you for your patience with one noob
Click to expand...
Click to collapse
we need to wait :/
there is no fix yet for them

Thank you for clarifying the situation When there will be some new ROM from Bruce, should I do full wipe again before flash? I rather dont I read somewhere that I dont need to wipe when flashing from previous build... is it right?

Mastegl said:
Thank you for clarifying the situation When there will be some new ROM from Bruce, should I do full wipe again before flash? I rather dont I read somewhere that I dont need to wipe when flashing from previous build... is it right?
Click to expand...
Click to collapse
yes ..no need of full wipe ..when updating the same rom

Related

[Q] Phone shuts down.

My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.

[Q] android revolution hd

i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
76redrum said:
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
Click to expand...
Click to collapse
Hi,
What version did you install?
3.6.8 or 4.1.8?
Did you do a MD5 checksum?
Did you super wipe?
Did you add any mods?
If you want help,you need to post more information...
Hi i had the same sort of problem with my ARHD but I find out that the faux kernel was causing for difficulties.
Installed a stock kernel and all problems solved.
Still respect all developers
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
76redrum said:
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
Click to expand...
Click to collapse
Hi,
It does sound like a kernel problem.
Try the kernel in my signature.
Absolutely no problems there.
ill try the stock kernel thanks to all
phone:htc senation
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any digestions would be very appreciated
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any sugestions would be very appreciated
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
seatown1two said:
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
Click to expand...
Click to collapse
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
---------- Post added at 03:15 PM ---------- Previous post was at 02:25 PM ----------
Hawke84 said:
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
Click to expand...
Click to collapse
Hi, i've been running the 3.6.x Roms for a while now and think they're great, but was getting interested in the sense 3.5 stuff. What in particular do you like about the 4.1.x roms? Just seeing if it's worth the full wipe effort .
Thanks
Mike
ArcticWolf91 said:
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Click to expand...
Click to collapse
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Hawke84 said:
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Click to expand...
Click to collapse
Lol yes, you are not the first to tell me that, and believe me lesson learned. Though I did mention that it was rooted and that it would be running this Rom. But yes now I am troubleshooting the phone with this person and I may have to give them a refund because they opened a case with eBay.
mrew42 said:
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
Click to expand...
Click to collapse
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
seatown1two said:
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
Click to expand...
Click to collapse
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
mrew42 said:
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
Click to expand...
Click to collapse
how do you up the speed for idle..silly question i know

[Q] Can't turn screen back on after hitting the power button in the camera app

This is doing my head in to the point I have borrowed a new HTC Sensation only to find the problem exists on this phone also.
When using the Camera App If I hit the power button the screen turns off. I am then unable to switch the screen back on - It appears the phone crashes.
Behaviour some times differs depending whether I have taken a photo or not.
The following behaviour is observed:
The lights stay illuminate on the soft keys at the bottom of the screen.
The phone can receive calls how ever it doesn't ring and I unable to answer them.
This problem is confirmed on 2 seperate devices which have been flashed with:
Android Revolution HD 3.6.12
10.58.9035.00U_10.15.9035.02_2 radio
I have also run super wipe on the phone before installing the HD Rom.
Please help!?
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
big_sw2000 said:
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
Click to expand...
Click to collapse
Cheers moved to ICS and its now fixed.
edwardblum said:
Cheers moved to ICS and its now fixed.
Click to expand...
Click to collapse
Having the same issues on both mine and my wives phones, both running AR 3.6.11 along with lag and other issues! Pretty fed up - and considering a different ROM. How is the ICS ROM, any issues like the 3.6.11? Is it hard to install?
I would try Elegancia ICS. Maybe a little pain to install, if you need to update your firmware.
http://forum.xda-developers.com/showthread.php?t=1429953
Firmware
http://forum.xda-developers.com/showthread.php?t=1432220
You may have to superCID if the firware dont work. Also easy todo
See post 4
http://forum.xda-developers.com/showthread.php?t=1192300
Have a read of the last 10 pages or so of the ICS thread for superCID info if your stuck, but it is easy.
I will give it a try! Do you just download the zip firmware and flash it?
It's not a rom problem, it is faux's kernel problem.
You can flash bricked kernel to solve.
banasik72 said:
I will give it a try! Do you just download the zip firmware and flash it?
Click to expand...
Click to collapse
Put the img zip directly on the SD card, not in any folder.
Boot the phone in to bootloader Power on volume down same time.
Just follow the instructions.
DO NOT POWER OFF REMOVE BATTERY ETC.
You will have to remove file from memory card before rebooting.
If you fail with the upload, then you will have to superCID

MT4GS will not wake up using Virtuous Inquisition 4.0.2

I recently downloaded virtuous inquisition on my mytouch 4g slide. I have an intermediate understanding of computers and was able to install the ROM and am quite happy with the experience it offers. I however have began to experience my phone freezing and not waking up. While I am usually able to have the phone enter and exit sleep mode no problem, sometimes when I press the power button to enter sleep mode, the screen will go black, but the backlight on the physical keys and slide out keyboard will remain on. Pressing the power button will not turn off the backlight or bring the screen back from sleep mode. Interesting to note that when I call my phone while in this state it will still ring and vibrate, however the screen will still not light up and I can not answer. The green notification light will also still blink. The only way I found to get out of this state is to physically pop out the battery and then restart. I was not experiencing this problem with stock ROM. Thanks for your help!
Do you have Revolutionary S-Off or do you have the new bootloader that is HTCdev unlocked & S-on?
When this happens see if trackpad wake works. I know on cm9 when I have sleep of death the trackpad wakes it right up
Sent from my HTC MyTouch 4G Slide running MikXE
WeekendsR2Short said:
Do you have Revolutionary S-Off or do you have the new bootloader that is HTCdev unlocked & S-on?
Click to expand...
Click to collapse
I just got my MT4GS about a month ago and am running the new S-on 1.45.0013 version unlocked by using Hasoon2000's tool at http://forum.xda-developers.com/showthread.php?t=1532809
strapped365 said:
When this happens see if trackpad wake works. I know on cm9 when I have sleep of death the trackpad wakes it right up
Click to expand...
Click to collapse
While both my trackpad and power button worked to wake up while in stock, only my power button worked from day 1 when I started using Virtuous Inquisition. My trackpad activated nothing while in sleep mode. I assumed this was just a normal part of the ROM?
When you installed your ROM did you do full wipes and then fastboot flash boot boot.img to seperately install your kernel? If not, that'll mess up tons of different stuff.
WeekendsR2Short said:
When you installed your ROM did you do full wipes and then fastboot flash boot boot.img to seperately install your kernel? If not, that'll mess up tons of different stuff.
Click to expand...
Click to collapse
Yes, I did wipes to system data, catche, and Dalvik catche in CWM all directly before installing the ROM. Right after I installed the .zip file, I flashed the boot.img file in fastboot.
That just DOESN'T sound like anything my wife or me have ever experience on VI. It's always been one of the most stable ICS ROMs either of us has ever used. AMAZING battery life too. VERY strange! Are you running extreme OC or anything that might make it unstable? If not, that one just stumps me. ....maybe UV?
WeekendsR2Short said:
That just DOESN'T sound like anything my wife or me have ever experience on VI. It's always been one of the most stable ICS ROMs either of us has ever used. AMAZING battery life too. VERY strange! Are you running extreme OC or anything that might make it unstable? If not, that one just stumps me. ....maybe UV?
Click to expand...
Click to collapse
No, I am not even OC because I have found the speeds when running VI on my phone to be fast enough and fine. Overall, I would agree that VI is extremely stable and have not found really any other major glitches. Only the minor tethering and camera glitches that they disclose when downloading. In someways this makes me inclined to think it could possibly be hardware, however I find it strange that I never have this particular problem in stock ROM.
corlip1 said:
No, I am not even OC because I have found the speeds when running VI on my phone to be fast enough and fine. Overall, I would agree that VI is extremely stable and have not found really any other major glitches. Only the minor tethering and camera glitches that they disclose when downloading. In someways this makes me inclined to think it could possibly be hardware, however I find it strange that I never have this particular problem in stock ROM.
Click to expand...
Click to collapse
Maybe it's just a timing issue in that the hardware issue arose after changing ROMs. Possible a packet got corrupted during the download. Maybe redownload and flash over what you have now? I just don't know.
Why don't you make a nand if that doesn't work and then flash MikTouch. It's stock just debloated & rooted. Maybe that will give you some indication that you aren't getting right now.
It may BE as simple as a hardware issue. Not good by any means but it may pinpoint it.
VI Blackouts
VI w/the GB kernel 2.6 would blackout like that from my experience. Check the third post on rootz and load the v3 beta kernel. I used VI for a few months, until I switched to CM9. I think I only blacked out once during that time with that kernel.
SSr2 said:
VI w/the GB kernel 2.6 would blackout like that from my experience. Check the third post on rootz and load the v3 beta kernel. I used VI for a few months, until I switched to CM9. I think I only blacked out once during that time with that kernel.
Click to expand...
Click to collapse
Do you have a link to the page you are referring? I have not upgraded the kernel and want to make sure of the steps. Thanks!
corlip1 said:
Do you have a link to the page you are referring? I have not upgraded the kernel and want to make sure of the steps. Thanks!
Click to expand...
Click to collapse
rootzwiki com/topic/22041-mt4gsrom26-04-2012virtuous-inquisition-v402-aosp-experience-senseless-ics-403/
hopefully this isn't against the rules, but just trying to help

[Q] Both cameras stopped working

I was using viperS after coming from ARCHD and camera was working fine, until one day I got an error saying "cannot connect to camera" etc. I have tried flashing both roms again and cm10 and cm9 and still it doesnt work. I have searched and found no fixes for this. Anyone ever have a problem like this?
What version did you flash of the ViperS
ViperS 1.3.5 With True S off
jslim38 said:
What version did you flash of the ViperS
ViperS 1.3.5 With True S off
Click to expand...
Click to collapse
I flashed 1.3.5 and I have the newer mainboard so I had to use the wire trick to s off to unlock bootloader and root
I had to do the wire trick also. Have you tried other versions of ViperS and before flashing the Rom did you try super wipe
ViperS 1.3.5 With True S off
jslim38 said:
I had to do the wire trick also. Have you tried other versions of ViperS and before flashing the Rom did you try super wipe
ViperS 1.3.5 With True S off
Click to expand...
Click to collapse
No I had the newest version of ARCHD before I flashed vipers 1.3.5 and I have tried superwipe, Im not sure if this makes any difference but I found some test pictures from a market camera app and they were green and purple.
bump, anyone?
Kevinjs said:
bump, anyone?
Click to expand...
Click to collapse
seems like drivers got corrupted
run a RUU go to complete stock and check the camera's
ganeshp said:
seems like drivers got corrupted
run a RUU go to complete stock and check the camera's
Click to expand...
Click to collapse
I ran a RUU and the problem is still here, It must be a hardware problem I guess? Shame I was actually using the 1080p video a lot and bought a fisheye for the phone.
Bump
I'm also having a problem with my sensations cameras.
Neither the front facing or main camera are working. When i open up the camera app it goes black screen then straight back to home. Also in zdevicetest both cameras have a red cross through them.
Things i have tried so far:
Superwipe
Reinstall rom (ARHD 6.8.0)
Tried a few different kernels (sebastianFM, stock, Faux)
Went back to stock via RUU
Replaced main camera module on mobo
So, noooo idea what to try next now. It did the same thing about a year ago and just started working again of it's own accord, but then a month or so later it stopped and never recovered on it's own. Heh.
Any thoughts anyone?
anybody have any solutions for this i got the same problem since i upgraded from gingerbread arhd too ics and since then my face cam stopped working my main cam works without problem

Categories

Resources