I have random boot loop issues every once in a while (once or twice a week) ever since flashing the Revolution HD 3.6.4 ROM.
I did nothing to the phone other than flash the rom and the 'recommended' radio, so whatever kernel came bundled with the rom is what I stuck with (I believe it's kernel 0.2.3.16 by faux123 according to the RevHD readme).
I'd like to attempt to eliminate this boot loop issue by flashing a different kernel but there are many out there. Can someone chime in and recommend a stable kernel, other than the 0.2.3.16, that you are happy with?
Other than the random boot loop issues, I'm really happy with this rom!
I used the default faux kernel at first but switched to bricked v1.4r1 after having major battery drain. Everything has been working perfectly for days and battery life is great. No problems at all
Bricked!!!
The first week I've used Faux... Its pretty good, but had higher drain with it.
Tried Bricked and now still with Bricked...
Odd that people are experiencing battery drain issues with the Faux kernel. Battery IMPROVEMENT was the first thing I noticed when switching to Rev HD.
I'll give Bricked a try. I avoided it till now... something about a kernel called "Bricked" that is non-confidence inspiring.
So I'm taking it Revolution HD and the Bricked v1.5 kernel play well together? Any recommended apps RevHD includes that I should delete due to compatibility issues?
I read someplace that Daemon Controller doesn't work well with Bricked, or may be I read it as works "better" on Faux...
Either way, all I need to do is make a Nandroid backup and flash with Revolutionary correct???
~EDIT~
It appears there's 3 Bricked kernels available. Which one do I want?
*v1.5* [ondemand, smartassv2 optional, PREEMPTIBLE, recommended] Click me
*v1.5* [ondemand, smartassv2 optional, PREEMPTIBLE, [email protected]] Coming soon, for now: Good night - Not all devices can handle this!
for: v1.5, Android 2.3.5, Sense 3.5 [CAMFIX] Click me
Click to expand...
Click to collapse
The "recommended" or the Sense 3.5 one???
~EDIT x2~
Duh, nevermind; "camfix" is just that. It's a camera fix for the other "recommended" kernel. RTFM
Yep, that's all you need to do. (At least, it's what I did and it work fine). I am also running bricked and I notice better life than Faux. Boots quicker too.
yup bricked worked for me too! with faux the battery drain was crazy!!!!
Faux 0.2.4 beta 3 seems to have cured the battery drain. Also, I am getting better performance with this kernel compared to bricked.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Do I need to wipe any cache files? The official Bricked thread doesn't make any mention of needing to delete anything.
How to install?
Just flash from recovery. Though it creates a boot.img out of the one on your phone while flashing, it should work with the majority of ROMs out there.
Click to expand...
Click to collapse
I used the stock and it was fine but alot of positive feedback from bricked
I'm using the one that came with the rom. Battery life isn't TOO bad. But I'm still patiently waiting for 3.6.5 that's supposed to be out today.
Bricked is easily THE Kernel to use!
Its stable as a rock - since I've begun using it I have never had a boot loop
I used to have V0.91 and it was soo smooth it gave butter a run for its money!
However, I'm not so sure about the new v1.5 Kernel. It doesn't feel as smooth as 0.91. I also had V1.4r1 which wasn't as smooth as 0.91 either.
I'm wondering if it's something i've done because everyone's raving about how smooth V1.5 is.
I'm still using bricked 0.91 and is rock solid.
No need to update to any other version or kernel because is so lighting fast that is not worth changing to something else.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
I have used both bricked and faux kernels. Here are my observations: Faux is faster but has bad idle battery life. I actually get better awake battery life using faux. Bricked seems to be slower but I get amazing idle battery life.
I have used bricked 1.4r2 and faux 2.3b4, 2.3b16, 2.3r3, and 2.4b6.
If you use bricked be aware that not all phones can support the 320Mhz GPU version.
After installing ARHD , it ran well, fine battery life, no hiccups, after some days it started showing colours. Battery drain was major also the heat issue, non stable, read somewhere It's kernel issue so changed to briked kernel, guess what no issues.
Im using Bricked 1.5 @ 1.56Ghz but have tested up to 1.83Ghz without problems, works awesome. was using Bricked 1.4rc1, with the GPU @ 320mhz
iammer said:
I have used both bricked and faux kernels. Here are my observations: Faux is faster but has bad idle battery life. I actually get better awake battery life using faux. Bricked seems to be slower but I get amazing idle battery life.
I have used bricked 1.4r2 and faux 2.3b4, 2.3b16, 2.3r3, and 2.4b6.
If you use bricked be aware that not all phones can support the 320Mhz GPU version.
Click to expand...
Click to collapse
+1
This is exactly what i experienced when comparing the 2. Although new faux kernel is only slightly worse idle battery life, no longer bad battery life
I'm using Bricked 1.5 with ARHD 3.6.5 and it's the best ROM/kernel combination I've ever used. Blazing fast and my temps never get above 25c (but temperatures dropped a lot anyway when I got the anker battery)
The First 5 nanoseconds I used the default Kernel coming with the rom...as soon as the 6th nanosecond was about to start, my battery jumped out of my Sensation XE, running around and tried beating me, giving me Bad names and so on...finally it begged for another Kernel...and I flashed 1.5 bricked one....the battery jumped back into my phone and feels very comfortable right now in combination...also with 3.6.5...so I do
well I gotta say, going from arhd 3.6.5 to cmd7 made a world of difference in terms of battery saving. maybe in the future I'll go back to arhd.
Related
Hello I have run both the stock cm7 and cattleprods 4.3.1 with smartass
Even going as far as to use SetCPU profiles to reduce CPU to 245 min/Max on screen lock. Im able to squeeze 11-12 hours with decent usage
from what I unslderstand reading the lord UV kernal people are lacking hsupa which is something I rather like. And while im ok with 12hours usage if something unexpected it long dinner party after work, im SOL
Any help or tips would be great
Thanks
Drew
Sent from my Desire HD using XDA App
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Wrong forum for this. It should be in general but the lordmod kernel probably isn't the hsupa killer it was probably the radio swap I did. I fixed it but it was a PITA!
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Click to expand...
Click to collapse
Can I get a little assistance? I read throughout the your thread and the one u linked. There are about 15 different kernals and UV zips
Thanks. Im really interested in trying this out
Drew
Sent from my Desire HD using XDA App
Mustang302LX said:
Wrong forum for this. It should be in general but the lordmod kernel probably isn't the hsupa killer it was probably the radio swap I did. I fixed it but it was a PITA!
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
Sorry I couldent figure which forum would be most appropriate
anyone can move it if they are so inclined.
Drew
Sent from my Desire HD using XDA App
helushune said:
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Click to expand...
Click to collapse
Do you just flash the lordmodV4.4.1-BFS-BFQ.zip file in recovery?
What do you do with lowervoltages-25.zip?
Thanks for the assistance this will be my first UV type kernel
Drew
drewdatrip said:
Do you just flash the lordmodV4.4.1-BFS-BFQ.zip file in recovery?
What do you do with lowervoltages-25.zip?
Thanks for the assistance this will be my first UV type kernel
Drew
Click to expand...
Click to collapse
Wipe Cache and load the 2 .zip files just like a ROM. Hopefully you won't lose HSUPA like I did (I still think it was the radio swap but I refuse to try this again as it was a pain to fix).
Sounds good. Ill report back with my findings regarding the HSUPA and overall batt improvements.
Thanks
Drew
drewdatrip said:
Sounds good. Ill report back with my findings regarding the HSUPA and overall batt improvements.
Thanks
Drew
Click to expand...
Click to collapse
I'll tell you the -50mV kernel mod froze the phone numerous times when opening an app to where I had to pull battery. The -25mV mod didn't help at all for my battery life. My phone drained same as always which is terrible but not great either.
drewdatrip said:
Can I get a little assistance? I read throughout the your thread and the one u linked. There are about 15 different kernals and UV zips
Thanks. Im really interested in trying this out
Drew
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'd say go with BFQhs CFS or the V(R) I/O flavor (edit: scratch that, looks like he pulled the VIO one until tomorrow), they're supposed to be faster than the others. The non-undervolted kernel might give you fine battery life so there's a possibility you won't need to undervolt at all. Also, flashing an undervolt patch is optional.
Unlike Mustang, my phone responded extremely well to the -25mV but seemed to go back to typical drain when I switched over to -50mV. And it seems like it's enjoying the Pinky ultra undervolt so far. Like LorDmod says, try them out and see what works.
Flashing the kernel's simple,
Do a backup
Reboot in to recovery
Clear /cache
Clear Dalvik cache
Install kernel zip
Install undervolt zip (optional)
Reboot and enjoy
This is just my experience - during extensive testing for my APN modification thread I ran multiple versions of lordmod and never lost HSUPA speeds from the kernel itself. Any loss of speeds were due to other issues which were identified and corrected.
henrybravo said:
This is just my experience - during extensive testing for my APN modification thread I ran multiple versions of lordmod and never lost HSUPA speeds from the kernel itself. Any loss of speeds were due to other issues which were identified and corrected.
Click to expand...
Click to collapse
Yeah like I said I'm 99.9% sure it was the change in radio that did me in but it just so happened to be just before flashing the kernel and I didn't notice till the next day I lost HSUPA. I personally will stick with stock CM7 kernel just because I messed with my own head lol.
I just flashed the kernal last night with the -25. HSUPA is still intact. Ill report back on Bat life
Drew
helushune said:
Unlike Mustang, my phone responded extremely well to the -25mV but seemed to go back to typical drain when I switched over to -50mV. And it seems like it's enjoying the Pinky ultra undervolt so far. Like LorDmod says, try them out and see what works.
Click to expand...
Click to collapse
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
gordec said:
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
Click to expand...
Click to collapse
My experience mirrors yours. No matter where my battery is when I flash a ROM the drain remains the same. I've also done the whole wipe of battery stats and no difference either. It lasts me long enough as I charge it overnight anyways while I sleep so oh well I'm not too worried about it anymore really.
I recently removed the battery percent from the status bar. All I ended up doing was obsessing over it and had to see where it was all the time. So now I just use the gauge and feel better about the battery lol and not even focus on battery too much unless I'm away from my charger for an extended period of time.
I use lord mod 4.4 and I have hsupa. I never lost it.
Sent from my Inspire 4G using XDA Premium App
Mustang302LX said:
I'll tell you the -50mV kernel mod froze the phone numerous times when opening an app to where I had to pull battery. The -25mV mod didn't help at all for my battery life. My phone drained same as always which is terrible but not great either.
Click to expand...
Click to collapse
That is because your device can't handle it, every device handles it differently.
As an example, my device handles UUV fine, but when attempting to use PUV it boots, but with any random reboots and application FCs.
NikolaiT said:
That is because your device can't handle it, every device handles it differently.
As an example, my device handles UUV fine, but when attempting to use PUV it boots, but with any random reboots and application FCs.
Click to expand...
Click to collapse
Right which sucks cause I wanted to try the others lol. Oh well I guess.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
gordec said:
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
Click to expand...
Click to collapse
Trust me, it makes absolutely no logical sense to me either. It seems to really like the PUV version as well so I'm not complaining.
For me, there is a noticeable difference between the stock kernel and undervolting. Stock CM7, my phone drains at around 3% per hour. Undervolted, it's slightly less than 1% per hour and possibly even better with PUV.
With the CFS BFQhs and -25 UV I got another hour and change. I feel like I used it the same maybe more. Im gonna try another one of his kernel and maybe the -50 or UUV see if NY device can hang with it.
Sent from my Desire HD using XDA App
I'm using InsertCoin 3.4.2 on my phone, but haven't settled on what kernel to use yet. I've tried bricked 1.5, good battery life and the phone ran fast with it, but it had a habit of freezing or sometimes crashing when exiting the camera. I've tried faux but it ran red hot and had abysmal battery life. So now I'm back on the stock kernel for the moment at a crappy 1.2ghz,have marginally worse battery life than bricked kernel, and this too is causing the phone to run warm.
What other kernel options do we have that are completely stable, along with good performance and battery life? Any suggestions?
Does the lack of replies mean there are no alternatives?
I'm currently trying bricked 1.6 beta2, and the phone runs warm, keyboard is laggy at times as well as some games, and it can still freeze when exiting the camera. So this one is no good either.
Sent from my HTC sensation using Tapatalk
Why not try the stock 3.5 its pretty good on my phone, its rock solid and my phone is running nice and cool with great battery life.
Which version of faux's did you use?
Right now we are pretty much limited to faux, bricked, and stock. Well not really limited since 3 is pretty good already. they each have their pros and cons. im also currently waiting for a new release that will hopefully satisfy my needs
Jump1ng said:
Why not try the stock 3.5 its pretty good on my phone, its rock solid and my phone is running nice and cool with great battery life.
Click to expand...
Click to collapse
Is that the stock kernel linked on the InsertCoin thread? If so, that's the stock one I've already used. Works okay, but battery life wasn't quite as good as bricked, and no overclocking so I was stuck at 1.2ghz. Is there a sensation XE kernel knocking around anywhere? As that's 1.5ghz and still a stock bug free kernel.
As for what version of faux I tried, I can't remember now, but it was only within the last week or two as I've only even been rooted for a fortnight, and was the newest version AFAIK.
I've just tried bricked 1.6 beta1, and that froze almost instantly, so that's out too...
Hey guys, I bought myself a Nexus S one month ago and I've flashed about 15 different ICS ROMs. Is it just me or are there almost no stable ICS ROMs? All of them had random reboot issues apart from AOKP and CM9. I had no reboots on AOKP but the clock got stuck every 2nd day, so my phone wouldn't wake me in the morning which is even worse. CM9 I liked a lot, but I couldn't phone in the hands free mode (don't know the propper name of it in english) because the mic wasn't loud enough. Currently I'm on ras cream sandwich and it reboots while i'm listening to music which is really frustrating. Oh and before i forget, I always flashed matr1x kernel and used smartass governor, no OC.
Is there any stable ICS ROM apart from CM9 and AOKP? Or can i fix the other bugs?
Thanks in advance!
Your problem is the kernel, not the rom. My phone also reboots while listening to music in the undervolted matrix kernel. Stay with rascream and flash the _thalamus kernel and see how stable it is. That kernel is really stockish and stable. If you don't want to flash you could try to raise your voltages to stock values in nstools. Some phones like undervolting, some not. ;-)
Verstuurd van mijn Nexus S met Tapatalk
hm I didn't know matrix kernel was undervolted, I thought that's only the case with trinity TEUV kernel by default well I'll try another kernel for the time being and see how that goes.
Yeah. Some of our phones can't handle the voltages mathkids kernel supplies outta the box unfortunately. Either adjust them back to the stock ones or search for another kernel. I prefer either thalamus or Simple Kernel. I just recently flashed the latest version of the former and its great. You can try Air kernel if you want a few more governors and whatnot.
Sent by pocket technology.
Like.. that's what STOCK is all about.
The people that made the phone are the most interested in making a stable ROM, no compromises.
Most stable and fast rom
Try APEX ROM 1.1.2 (latest release), that's what i'm using until aokp milestone 6 comes out. there is no lag, no reboots (just if u OC too much),...
Slim rom with no tweaks is smooth. Try it and u will not regret it.
Good luck
Vs Nexus S 4G
MIUI roms are very stable these days.
Sent from my Nexus S using Tapatalk 2
Well it differs from phone to phone. My phone is good with Matrix kernel. Might be one of the best custom kernels to run for my phone if not the best. Matrix isn't a compromise for my phone.
Sent from my Nexus S 4G
For several days I'm with Slim ICS and Matr1x and I have no problems with random restarts. No OC and no tweaks!
Try CyberGR ROM
I have installed CyberGR ROM and I have not suffered any reboot. I followed one by one all the steps of the development part and I'm quite happy with it.
Good luck.
Well, if you really want stable, get Stock 4.0.4. I'm on 1100+ hours on uptime without a single reboot... The only thing I've done to the stock 4.0.4 is getting root.
I would also like to know. from my own experience, stock 4.0.4 is best, but can CM9 very be made that stable? I'm running it now with ink kernel and no tweaks and it seems slightly laggy :/ should I flash brainmasters tweak pack?
Sent from my Nexus S using xda premium
Bugless Beast hasn't given me any issues. I've rebooted to flash other kernels but the only two kernels that have given consistent performance are Simple(stock with bln) and thalamus. Once I get my new battery, I may see how long I can go without rebooting. But if you want rock solid, go with stock ROM. Hell, my cousin has an EVO 4G and has almost 1200 hours up time. Lol.
Sent by pocket technology.
AOSP+ definitely belongs to this category. Stock with a few useful modifications.
You should try AOKP again
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Apart from stock, Have you tried BuglessBeast? Very stable. No need to flash any custom kernels.
if ur using ra scream use one of the trinity kernels. its super stable, super smooth, and long battery life
im using this black ice rom, in love with it .. shud try
alexfiorani said:
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Click to expand...
Click to collapse
I searched the internet and apparently I'm not the only one with that problem. I tried AOKP twice (i think build 32 or something and m5), always with matr1x kernel. Could this also be a kernel Issue?
I don't know that much about Android, but what I found out in the past days is that my Nexus S can't handle UV. I also get very high Android OS battery usage sometimes but I don't know why. High meaning Android OS once used more battery than display even though i had 2h screen on time. I suspect it's got something to do with titanium backup not restoring apps correctly, but that's just a stab in the dark.
Currently I'm on Apex v1.1.2 with stock kernel. No random reboots so far. I didn't restore apps via titanium backup (which was a pain in the ass). So far Android OS seems to use way less battery than before. But yesterday I had something like SOD when received a call while using TuneIn, so I had to pull the battery and call back. Not what I call stable.
I know that's a lot of text and probably also a bit OT sometimes but I hope some of you will read it , I'm not really a flashoholic and I'm getting sick and tired of switching roms, but I need my phone to be reliable. I'm really tempted to just switch back to stock ROM with stock kernel at the moment...
the things I'd really like to have is bln, notification toggles and stability.
i flashed cyanogenmod 9 rc1 yesterday.
everything is ok and performance is good.
i flashed bricked kernel 1.31 because my battery life was very bad.
but now, the battery life is worse..
i even cant stay 5 hours if i do something with my phone
Well, it is a RC, so it won't be perfect.
Try underclocking your cpu a bit it helps.im running aokp with bricked . I underclock and its helped out the drain quite a bit. But in my case I think the drain is also comming from sweep to wake and zram. I might try re flashing keeping these things out. But try the underclock it does help.
Sent from my Sensation using xda premium
OP: You may want to describe your normal device usage for more help. You may also want to install Better Battery Stats from playstore to see if you have an app causing a wake lock.
I've run CM9 RC1 with the standard and tamcore kernels. I can get almost 2 days usage with either one and normal usage, but that really boils down to how I use my device...
I have been using TrickDroid V6.2 as my daily driver for nearly a month now. It is a phenomenal ROM and has worked extremely well. I recently switched to ViperOneS after reading all the great accolades (including from torxx himself). The ROM is excellent as well and seems noticeably smoother than TrickDroid to me. Strangely, I ran Antutu benchmark using both ROMs and found a huge disparity in performance. The TrickDroid variant clocked in with a score around 7700. The ViperOneS variant clocked in at a measly 2300. This is using the very same One S phone. I still consider the ViperOneS ROM to run noticeably smoother than TrickDroid, but am confused by the huge disparity in performance.
Another interesting note, I ran the TrickDroid test without closing any other open programs, but closed all programs prior to running the ViperOneS test.
Any insight is appreciated.
*I reran Antutu on my phone (currently using ViperOneS) and score shows 3300.
Solutions:
- ROM reflash
- Different kernel
My issue has been resolved and the ROM is performing better than anything I've tried thus far. Running ViperOneS v1.1 with Fusion UV kernel.
abracadabra11 said:
I have been using TrickDroid V6.2 as my daily driver for nearly a month now. It is a phenomenal ROM and has worked extremely well. I recently switched to ViperOneS after reading all the great accolades (including from torxx himself). The ROM is excellent as well and seems noticeably smoother than TrickDroid to me. Strangely, I ran Antutu benchmark using both ROMs and found a huge disparity in performance. The TrickDroid variant clocked in with a score around 7700. The ViperOneS variant clocked in at a measly 2300. This is using the very same One S phone. I still consider the ViperOneS ROM to run noticeably smoother than TrickDroid, but am confused by the huge disparity in performance.
Another interesting note, I ran the TrickDroid test without closing any other open programs, but closed all programs prior to running the ViperOneS test.
Any insight is appreciated.
*I reran Antutu on my phone (currently using ViperOneS) and score shows 3300.
Click to expand...
Click to collapse
Benchmarks don't matter, if it seems smoother just use and enjoy!
Sent from my HTC One S using xda app-developers app
JmPTaz09 said:
Benchmarks don't matter, if it seems smoother just use and enjoy!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Although I agree to some degree, it's still strange to have such a difference with only a ROM swap. Any ideas what might be the root cause?
Possible that the io scheduler is responsible. Try changing it and see what happens.
Edit>> Here is a link to a post of mine where I posted a screenshot of my quadrant benchmark http://forum.xda-developers.com/showpost.php?p=30850098&postcount=1125
I get some of the best benchmarks and GUI smoothness with this ROM. Benchmarks do NOT matter at all, by the way. They just spit-ball the range of performance your device may or may not be able to handle. Smoothness, load times, etc... are what matter in reality.
Strangely, the new kernel included in the 2.21/2.31 RUU updates drastically improved my benchmark scores...not that it matters anyway. As many people above have said, benchmarks really do nothing and are quite easy to trick. I remember disabling EXT4 journaling on the Galaxy Player jumped my quadrant score by 1000.
@klin: That wouldn'T make sense in realtime usage
Thanks for the feedback fellas. Appreciate the input.
Went from TD7.10 (the end) to stock to Viper, no good
About 2 weeks back, I went back from Trickdroid 7.1.0 to One S stock. Though some of the items (lockups in camera) stopped, I wasn't really happy with the stock. Still no 4.1 update, just 4.0.4, so thinking about Trickdroid I saw Torxx went to Viper builds. I installed it with faith, however was very wrong: Network failures, USB mount failed, mobile network fails ever so often, data network not stable, Issues hanging up a call. Yes I did cache wipe, full data wipe etc. Still it came with these things. So I checked the Trickdroid site again: 8.0.0 (so 7.1.0 wasn't so much the end). Installed TD 8 and it works like a charm again. Just can't seem to find the Google Now which should be installed by the Tweaks....
My first Viper flash didn't seem to go so well either. I reflashed and everything seems to be working well now. Antutu is reporting in the 7000+ range again.
I would recommend reflashing if you're still interested in ViperOneS. If not, TrickDroid is a fine ROM, too.
I'm running Viper One S with fusion overclock UV kernel and have tried TrickDroid(s) and find the Viper smoother and better on battery life. I have gotten six hours screen on time with Viper.
abracadabra11 said:
My first Viper flash didn't seem to go so well either. I reflashed and everything seems to be working well now. Antutu is reporting in the 7000+ range again.
I would recommend reflashing if you're still interested in ViperOneS. If not, TrickDroid is a fine ROM, too.
Click to expand...
Click to collapse
Tnx. I might try it again later on. For now, TD is best in my opinion (based on stability and speed, not in customization perhaps). I am keeping track of Viper next to CM10. I still believe in Custom Roms for better use of your phone. Does the Viper Rom also include Google Now? Didn't see it..
Fredfly said:
I'm running Viper One S with fusion overclock UV kernel and have tried TrickDroid(s) and find the Viper smoother and better on battery life. I have gotten six hours screen on time with Viper.
Click to expand...
Click to collapse
I just flashed fusion kernel and have had a similar experience.
ROM runs extremely smoothly and battery performance is much better than what I had with TrickDroid. Strangely, TrickDroid preserved battery better at night (maintained about 2% more than Viper does).
I reran Antutu after kernel flash and score was 7700.