Hi all!
I've got a little problem with Virtuous Quattro and Virtuous Affinity randomly rebooting into Virtuous logo and from there I have to pull the battery to be able and start it up again.
Never had this issue before with any other rom(s) so I dont know what to do!
When I was on Virtuous Quatro I got the tip to convert my partitions to ext3 wish acctualy helped me to go from 2-3 reboots a day too 1. But its still anoying with a random reboot a day
Now Im using Virtuous Affinity and a little while ago it did the exactly same thing... rebooted to logo and I had to pull the battery ones again.
I REALY like both of these roms and especialy quattro and would love to be able to use them w/o reboots.
If you have any clue what the problem could be, rom, app, radio, partitions etc please write a line here
Is there any application that could make a logg what happend right before it crashed?
My phone:
HTC Incredible S | Rev S-OFF
Recovery: 4EXT Recovery Touch v1.0.0.3 Beta8
Kernel: 2.6.35.14-UNITY-V10-g6b8d035
Radio: 3822.10.08.28_M
ROM: curently Virtuous Affinity v1.48.0 (Vivo)
Oh and sorry if my english spelling and grammar is bad
edit: could it be the kernel thats undervolting and my processor cant handle it? Im gonna try on Affinity to up the voltage anyway and report back when I tested it a bit
You should stick all the CPU settings in stock and see if that has any effect
Sent from my HTC Incredible S using XDA App
same for me withe no oc
Installed oc/uv beater 2 and uped the voltage slightly. So far it's been stable and no reboots. Think it might be the problem. I'm still on affinity btw. Dunno if quattro's kernel support voltage changing.
Sent from my HTC Incredible S using XDA App
i used to have to auto reboots on sense roms including Virtuous Affinity but now i am on Virtuous Quattro and it does not reboot. Not even once and i have been using it for days..
I have this same problem...WITH MY DESIRE HD...i know this is an Incredible S thread but when i Googled 'Virtuous Quattro Randomly Reboots' it was the first link, so i'm here. anyway, tried everything suggested and still reboots... :-(
Related
Hi
I´m running Android Revolution HD 1.0.2 ROM, and it really fast and cool.
But... i have an issue with the videorecorder. It starts recording about 20 - 40 seconds after i hit the start button...
Anyone else having this bug?
Hi, i don't have that issu and i'm with the same Rom. I read somewhere in the original post of Android Revolution HD 1.0.2 ROM that somebody have the same issu. Just read more careful and you will find it .
Haven´t noticed any bug yet on mine
Hi,
I have s-off and clockworkmod installed on IS (bell). Android version 2.2.1, baseband version 20.23.30.0802U_38.02.01.17_M, software number 1.37.666.3. Now what I would like to know is what are my next steps for installing ext4 1.0.6 mod, and a radio and Revolution HD. I read that the radio I install should match my version, is this correct? Or do I use Radio_20.2804.30.085AU_3805.04.03.22_M? If not where can I find my version. Also should I stay on froyo or upgrade to gingerbread?
Any help is greatly appreciated....
Mikael have you tried to wipe your data? Also the dalvik cache should be cleaned (advanced in cwm).
This should do the trick
hi, you already try new unity v2 kernel?
Sent from my HTC Incredible S using Tapatalk
Running the same as you and camera works fine, tho video doesnt start instantly for me either. but its not 20-40 secs, mine starts up at about 3-5 seconds after button push.
maybe a bit buggy cause of an upgrade from 1.0.1 to 1.0.2 maybe and it conflicts somewhere, is it the stock camera/camcorder or did u install Android_Revolution_HD_Sense_3.0_Camera_5.1.x_v.0.12. Maybe if its stock install that and see how it performs.
Hmm, I'm running 1.0.1 with no problems. Video recording takes exactly as long as it did with the stock Rom, 2-5 seconds.
Have you tried a different SD card? Sounds to me like the SD card speed isn't fast enough. HTC themselves cites the SD card as the problem for 'photo taking delays' and 'choppy video, video record delays.'
Again, I'm on 1.0.1 with a full wipe beforehand and dalvik wipe so its difficult for me to say.
Mikael1711 said:
Hi
I´m running Android Revolution HD 1.0.2 ROM, and it really fast and cool.
But... i have an issue with the videorecorder. It starts recording about 20 - 40 seconds after i hit the start button...
Anyone else having this bug?
Click to expand...
Click to collapse
You are using v1.0.2 ... This a bug reported by other users too ... Please go report in mdj's kernel thread ... This is a kernel issue ...
Sent from my HTC Incredible S using XDA App
humm
knightrocker said:
You are using v1.0.2 ... This a bug reported by other users too ... Please go report in mdj's kernel thread ... This is a kernel issue ...
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
im using same ROM did full wipe including d cache and installed rom than right away the radio and i dont have any delay maybe half a second
yer mine makes the beep noise then few secs later timer starts no big deal for me all seems to work well
might be better if you posted this question in the actual DEV area for this rom
baste07 said:
might be better if you posted this question in the actual DEV area for this rom
Click to expand...
Click to collapse
Yes, you' re right. By the time I posted this question, i was'nt permitted to post in DEV area....
But I am now.
In the meantime I have installed a different ROM, and now my cam is working perfectly.
Sent from my HTC Incredible S using XDA Premium App
jul644 said:
im using same ROM did full wipe including d cache and installed rom than right away the radio and i dont have any delay maybe half a second
Click to expand...
Click to collapse
I'd have to say mine is about the same, no issues with video. But I was getting a delay in messages as far as sending/receiving goes. I would probably assume I should reflash my radio after switching between a few roms lately
Most likely It's the radio.
Sent from my HTC Incredible S using XDA Premium App
I have my Inc running Cm7 7.1 RC1
Radio 2.15.10.05.06
Kernel Chads Incredikernel 7062011
Why the hell is this setup so unstable?
Some days it runs fine.. Other days I get force closes on messaging, Android market, the camera,
Its so annoying..
To everyone else how stable is your phone on an every day basis?
Exact same setup as you, once in awhile FC on startup for a few apps, but no FC otherwise. what's really annoying though is sometimes entire system becomes unresponsive and auto reboots
Sent from my HTC Incredible
Wrong section to post this thread btw
TheLynxy said:
Exact same setup as you, once in awhile FC on startup for a few apps, but no FC otherwise. what's really annoying though is sometimes entire system becomes unresponsive and auto reboots
Sent from my HTC Incredible
Click to expand...
Click to collapse
If you undervolted your kernel then this is a common issue, and it means you should raise the voltages.
--
Also I haven't gotten any FC's running CM7.1 #106 nightly.
If it's bugging you enough and you want to *try* and fix it then I suggest you flash the latest nightly (#136 or 137) - but make sure you do a full wipe and format /system. Also clear all your caches. If you do restores from TIbackup then make sure you don't restore data.
That's all I can suggest, hope your problems with CM gets sorted out eventually.
^ Also try fixing permissions.
Sent from my Droid Incredible running a random CM7 nightly.
im not undervolted... sounds like cm needs a better stable code
Sent from my ADR6300 using XDA App
i fixed permissions
Sent from my ADR6300 using XDA App
I get the force closes and unresponsiveness time to time no matter what rom. Most of the time it's an app but every once in while it is a system app.
A lot of times it is poorly written apps not the rom. Run without any apps and you will see your phone runs great for a long time. Unfortunately theres no way to know if an app is written well without trying it. I wish google had a better way to control this.
I'm on and off CM. Ive been running 7.1.0. for about a week havent had a problem/FC. I have also restored app+data using TBU even though it isn't recommended Do you have this problem with any other roms.
Sent from my ADR6300 using XDA App
Gorilla* said:
im not undervolted... sounds like cm needs a better stable code
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
lol, cm's code is fine...
Usually things like this are user error/app related, and if not, then most likely something wrong with your phone. Otherwise we would see a mass amount of users reporting these problems. Which we don't..
Running CM7, I've had no fc's at all, no app problems, etc when following instructions, other than in the past some of the legitimate bugs that have popped up, and been fixed.
Did you flash RC1 over a nightly or any other previous CM build?, restore apps with Ti-Backup, Over or underclocked the kernel at all, Other various things that could result in fc's? Might wana try just running with no apps like nfiniti9 said, on a fresh install, Default kernel, and then see what happens.
I used the same setup besides the radio. I'm using 2.15.00.11.19 and I found it to be really buggy as well. Right now I'm using nightly 130 and incredikernel 06192011. I found this kernel to be more stable for me.
Sent from my Droid Incredible using XDA App
I have same setup with aggressive undervolt script from chad. Have not had a force close or reboot yet, and I have been using RC1 since it dropped, and nightlies for weeks before that. I am using the new GB leak radio also.
Obvious, but have you done a full clean wipe/flash? Check MD5 sum?
CM7RC3
Latest Incredikernel
Never changed radio
100% stable
OMFGB nightly 7-05
chads beta 2 with usb fast charge
stock radio
800 min voltage and -25 max voltages.
nothing to complain about, stock battery lasts anywhere from 5- 13 hours depending how hard i use it
any issues i was having i think i found out the problem... i was uaing titanium to restore after a full wipe and i was restoring all my settings wbich messed the phone up again after a clean wipe... this time i got smarter and did a clean wipe but i only restored my applications instead of system settings... this seems to have fixed issues for now.
Sent from my ADR6300 using XDA App
Running cyanogenmod 7.0.2.1 and I'm about to switch to 7.0.3 because I'm getting a lot of force closes lately, running the latest incredikernel as well.
1. This doesn't belong in development. Being a QUESTION, it would be much better suited to Q&A.
2. The OP is the fool that was trolling Chad's thread.
Facedown41 - I'd recommend flashing the latest nightly, its perfectly stable with a lot of new features. 7.0.3 is a bit dated.
Mercutio5 said:
CM7RC3
Latest Incredikernel
Never changed radio
100% stable
Click to expand...
Click to collapse
Same here. I just started using CM for about a week or so but so far not 1 fc 100% stable and fast.
Cm7 7.1 RC1 <---- problem right there.
RC = 100% stable.
im still on 7.0.3
The solution to your problem is to run a cache cleaner. This happened to me many times before and if you run it, it clears up a lot of space in the data/data partition so your apps have room in the memory to run w/o force closing!
When I plug my phone in to charge it stays at 800mhz instead of throttling down to 100-400mhz like its supposed to. I'm on pinnacle ROM and its taking forever to charge. Anyone else have this issue and maybe have a fix for it? Thanks.
Are you using Tegrak?
Yes, I do have it set to throttle down and using Ondemand scheduler.
Kill it and check if it get fixed. I recommend rebooting it after you change tegrak's settings.
Killing it seemed to have worked for now. How can I fix it so I can still overclock? It hasn't done it all the time, Just recently but I haven't installed any new apps or anything.
Sent from my Cappy using the XDA app.
Try clearing the app's cache. Maybe even Dalvik if you have too? Don't know.
I'll try, thanks man.
Sent from my Cappy using the XDA app.
well, getting rid of tegrak didn't help. Still charges and stays at 800mhz.
Sent from my Cappy using the XDA app.
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
prbassplayer said:
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
Click to expand...
Click to collapse
Tried that and still no difference......can't figure it out.
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
prbassplayer said:
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
Click to expand...
Click to collapse
It might be a problem with something included in Pinnacle but I can't narrow it down.
Ondemand 100min-1200max with stock voltage settings.
Na Fusion VII Beta is doing the same thing. I think its a tweak on the kernel maybe? I've been kinda busy and will be for the next few days, so don't know when I'll mess with different kernels.
I'll try the other kernel option and see what I can find.
Sent from my Cappy using the XDA app.
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
rmntruexjr said:
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
Click to expand...
Click to collapse
Using cpuspy or other monitoring software, what speed is it stuck at when charging? Are you running tegrak as well?
Sent from my Cappy using the XDA app.
Well tried a fresh install of Fusion and it still does it......
Geezer000 said:
Well tried a fresh install of Fusion and it still does it......
Click to expand...
Click to collapse
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
prbassplayer said:
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
Click to expand...
Click to collapse
I have flashed Fasty ki2, Fusion, Pinnacle, Apex and so far they all do it with or wothout tegrak.
Fresh look bump.....
Hi
Is any way of improving the 3G reception on the Incredible S, i have great 3G in my area and supposedly inside also (website shows excellent coverage inside and out) but inside my home it is sporadic at best?
What ROM are you using?
Have you tried a different kernel?
Sent from my HTC Incredible S using XDA App
I am using the virtuous unity witth the unity 9 kernel at present
It's unconfirmed and untested (by me) if this will work for your problem but today I downloaded Auto Manager Memory which let's you decide how much ram to give to certain functions. One of these options is Content Provider. I'm not sure exactly what it does but by giving more memory to that section you can probably get better 3g service.
Sent from my HTC Incredible S using XDA App
If you are s-off you can try flashing a different radio
Nonverbose said:
If you are s-off you can try flashing a different radio
Click to expand...
Click to collapse
Anything those of us who can't be arsed going through the process to s-off can do? (have h-boot 1.16.0000)
Just learning about all of this so any advice welcomed, currently running virtuous affinity 1.48 rom, s-on (htcdev bootloader unlock)
Any other info I can give that would help?
This is all started with the older version of De-Sensed rom v.1.4 then installed Virtuous Inquisition latest rom next and recently updated the kernel from 005 Faux to 007 last week. I've been wanting to try out the De-sensed rom ver.1.5 and flashed the new kangbang kernel sr7.0. Turns out it wasn't for me.
I always wipe in between flashing roms and I didn't back up any roms at all. I just simply flash the new roms. Well anyways, I went back to Virtuous inquisition w/ faux007. Now I don't have wi-fi, not only i couldn't transfer numbers to the message app now i can't even go to the message app and retrieve the contacts. Goo manager is not even installed either.
First time installing this rom, everything was a breeze and everything went well. What happen?
Z33type said:
This is all started with the older version of De-Sensed rom v.1.4 then installed Virtuous Inquisition latest rom next and recently updated the kernel from 005 Faux to 007 last week. I've been wanting to try out the De-sensed rom ver.1.5 and flashed the new kangbang kernel sr7.0. Turns out it wasn't for me.
I always wipe in between flashing roms and I didn't back up any roms at all. I just simply flash the new roms. Well anyways, I went back to Virtuous inquisition w/ faux007. Now I don't have wi-fi, not only i couldn't transfer numbers to the message app now i can't even go to the message app and retrieve the contacts. Goo manager is not even installed either.
First time installing this rom, everything was a breeze and everything went well. What happen?
Click to expand...
Click to collapse
Are you s off or s on? If your s on you gotta do fastboot flash the kernel...then flash the Rom...your WiFi problem is due to the fact that the WiFi lib/driver wasn't flashed...hope that helps/made sense...
Sent from my HTC PH39100 using Tapatalk 2
And if that don't help try to reflash the Rom , I just had the same issue and that's what worked for me .
I've never had the messaging app work correctly on either the de-sensed or virtuous. Posted about it on here, but no one ever responded. If you are s-off re-wipe everything and reflash the ROM. Check the md5 sum on the .zip you've got for the ROM just in case.
Sent from my HTC PH39100 using xda premium