Related
ever since i flashed cyan6 ive been getting super battery problems and im starting to think its my phone and i should call htc. so before you ask questions lemme tell you what ive done. ive changed my setcpu to ondemand 998 to 245, 384 to 225 when the screens off. ive used auto brightness instead of my own custom brightness. ive also tried the HTC battery calibration process and that didnt do much either. on cm6 under about phone>battery use my display is always the highest percentage by far. for example its been 93 percent with 8 minutes on. ive also flashed wildmonks kernel to save battery and saw low results. any help would be super appreciated
Don't call HTC about problems with custom roms. Flash back to stock and see if the problems persist. I have no problems with the current nightly builds.
Don't use setCPU the way you are using it because it interrupts those values which are in the kernel already. setCUP is only for overclocking, that is it.
evilkorn said:
Don't call HTC about problems with custom roms. Flash back to stock and see if the problems persist. I have no problems with the current nightly builds.
Don't use setCPU the way you are using it because it interrupts those values which are in the kernel already. setCUP is only for overclocking, that is it.
Click to expand...
Click to collapse
really? so dont underclock at all. just overclock. and your saying i should flash back to stock froyo?
Just uninstall setCPU for the sake testing. All values should remain as default in that application except for the max high-end value if you want to over-clock, but even then it's such a small difference I view it as more of a show-off point rather than a practice use state.
Flash one of the newest nightly builds, see if your battery problem goes away.
Don't bother HTC if you have problems with custom roms only about problems with the stock rom.
evilkorn said:
Just uninstall setCPU for the sake testing. All values should remain as default in that application except for the max high-end value if you want to over-clock, but even then it's such a small difference I view it as more of a show-off point rather than a practice use state.
Flash one of the newest nightly builds, see if your battery problem goes away.
Don't bother HTC if you have problems with custom roms only about problems with the stock rom.
Click to expand...
Click to collapse
ok ill definately that now. ill letchu know later thanks. any more help is appreciated
So you have battery problems with a custom ROM, and you think it's HTC's fault.... wat?
Sure, send it in. $245 later, they'll send you a stock Nexus One with a new motherboard.
khaytsus said:
So you have battery problems with a custom ROM, and you think it's HTC's fault.... wat?
Sure, send it in. $245 later, they'll send you a stock Nexus One with a new motherboard.
Click to expand...
Click to collapse
yea ok not what i meant. i dont think the problem is gonna vary on which rom im using. i think its my phone. i heard the suggestion of a logcat but ive never used it before.
b33zy682 said:
yea ok not what i meant. i dont think the problem is gonna vary on which rom im using. i think its my phone. i heard the suggestion of a logcat but ive never used it before.
Click to expand...
Click to collapse
Install OS monitor. Open the app, go to the right tab messages. Now hit menu, options, scroll down to dmesg, filter tag, and type in the 4 letters batt. Now go out of settings and to the right tab messages and see your numbers. When you find data you want to keep for comparison, click export.
RogerPodacter said:
Install OS monitor. Open the app, go to the right tab messages. Now hit menu, options, scroll down to dmesg, filter tag, and type in the 4 letters batt. Now go out of settings and to the right tab messages and see your numbers. When you find data you want to keep for comparison, click export.
Click to expand...
Click to collapse
idk what this does but i did it and i have 0 messages now. nothings popping up anywhere
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
For as cool as the Sense UI is, I don't think it was quite ready for the Hero.
Plus there are bugs that have been talked about quite a bit in the official 2.1 update for the Hero.
Hero + Sense = Dialer lag. Even after rooting and running a (mostly) much cleaner flavor of version 2.1, any rom I installed still had lag in the dialer app.
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
brookegray said:
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
Click to expand...
Click to collapse
It's possible that the bootloops happened to you because of the overclocked (OC) kernel in DarchDroid. Some phones cannot boot at overclocked speeds and will just bootloop while trying to load up.
The latest DD 2.8 already comes with an undervolted (UV) kernel, which some phones can boot better than the regular OC kernel, so it may just be that your phone doesn't like OC at all. Lots of phones here are like that.
Try flashing and booting DD2.8 on a FULL battery. You'll have a much better chance booting an OC kernel on a full battery, and while it's plugged into the charger still.
Another good Vanilla ROM I really liked was Ic3Rom, but it is no longer kept up so it's not as current as DD or the 2.2 Cyanogen Froyo ROM.
Good luck!
Try turning off the dialer sound in settings. That fixed the lag for me.
If you try the latest froyo nightly, it should boot, it's capped at 691- which is still overclocked but seems like everyone can boot.
Sent from my HERO200 using XDA App
Help: Sprint tech Actually Sent Me Here to Root my Phone!
mkhopper said:
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Click to expand...
Click to collapse
I've been complaining to Sprint about the lag since before 2.1. Last night a Sprint tech said to come here for an "unofficial" way to get my phone running smooth, including rooting it to make it do things that aren't "supported." So after searching around here I see posts about Nandroid, rooting, backing up, restoring, and flashing roms. I've rooting iPod Touches but never a phone. I want to try this while I have hours to kill at work. Forgive the shortcutting but can you:
1. Point me to an updated step by step guide.
2. Point me to an updated recovery image.
3. Point me to an updated ROM that you PRAISE.
4. Pray for me.
Thanks,
Ken
kenwhittaker said:
Forgive the shortcutting...
Click to expand...
Click to collapse
Welcome to XDA! Just as an FYI, many of us here don't take too kindly to this. We have had to put in our time searching and reading -- it's only fair that you should too.
That being said, this thread will tell you how to root and will include a recovery image: http://forum.xda-developers.com/showthread.php?t=694572
That's all you get from me Now it's up to you to browse around and find a ROM that you like best. No one here can tell you which one the "best" one is....it's all about personal preferences and tastes. Browse the Development forum and try several ROMs. Also check the Themes and Apps forum for cool extras. You'll soon find what you like.
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
chromiumleaf said:
Welcome to XDA!
Click to expand...
Click to collapse
Thank you. I'm well on my way. Rooting as I type. I'll check out the Dev threads.
I am running a non OC version of aloyuisus and i am loving it nothing ever lags i don't run task killers. I get great battery life, last me all day with moderate use, if i tether i always make sure its plugged in otherwise its never plugged in until late night. I listen to Audible and mp3s and probably make about 1 - 1.5 hrs worth of calls a day.
no random reboots either,
Nannuq said:
I am running a non OC version of aloyuisus
Click to expand...
Click to collapse
Thanks buddy. I'll look for a download link for that one. I just dropped to RUU 2.27.651.5 so I can root.
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
I had this same problem. Even after rooting and installing fresh 2.3.3 it wasn't much better. I was almost to the point of taking the phone back to sprint when i found Cyanogenmod 6. I started with test 4 which was still pretty buggy but the current nightly that is out is awesome. FroYo is the best thing that has ever happened to my phone. No Lag, EVER.
RocStar629 said:
i found Cyanogenmod 6.
Click to expand...
Click to collapse
The 5MP Cam, preview, and video camera? No video playback problems? I need to find that one!
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
this is a bug that was never fixed by htc when 2.1 was released and finalized. do a google search, lots of people are having this issue. no fixes for it either as the hero was left behind by htc.
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
danaff37 said:
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
hes talking about the dialer lag.
chromiumleaf said:
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
Click to expand...
Click to collapse
That one statement can't be said enough.
Read, attempt to comprehend, read some more and then do the work.
There are some apps and / or scripts nowadays that will give you "1-click root", but I frown on these to be honest. There's too much "magic stuff" going on behind the scenes that you're not aware of and if an issue pops up, it's harder to backtrack to figure out what went wrong.
1-click root apps are fine, later on down the road when you're comfortable with the process and just want to get it done, but manually running through the steps to root, backup and finally flash a new rom is the best way to go.
(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.
Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me
I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel
Had that issue at the Gym the other day, not even on Bionix.
I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App
Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.
r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.
i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/
There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.
Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL
Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!
sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..
I think it's hardware.... One of the unlucky ones....
Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.
hello all, ive just been having these issues, their always random, either its screen of death, random reboots, google services f/c'ing, it doesnt matter what rom i flash, or if i fastboot back to stock, nothing changes, theres always "something" that goes wrong. I've tried, and tried and tried but something always seems to be messed up with this phone. I dont know what im doing wrong, I've been flashing roms for years and never had so many problems, except, I had these same issues on the nexus 5, same thing.
anybody ells going through this? or is it just me?
i have both nexus 5 and nexus 6, i know both of them very well, is there anything i can help you with? ive figured out solutions to the majority of random things theyve thrown at me..
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Andromendous said:
Thanks for the help. Well, every rom i try has browser f/cs, google play f/cs random reboots sometimes it reboots and wipes cache for some reason. Sometimes its like system ui f/cs so it just does a "soft" reboot, i have audio issues even on stock, like when i get a call, the ringtone starts out real quiet then boosts all the way up, sound is distorted over 50%, i tried to up my voltage by 15mv global and that didnt help anything..... Im not sure what to do, i already switched out the phone once, i think im at the end of my 15 day byers remorse period
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
noidea24 said:
Ima jump in here and try to provide a helpful response.
The nexus 6 is the best device I've ever owned beside my beloved g2, I did have to get my nexus 6 replaced the second day I had it because of a battery issue, but no problems ever since.
As far as the Gapps force closing, try using a different set of Gapps. I prefer to use the latest version of the multirom twrp and always use Banks Gapps(pm me if you can't find them.)
Only onn two, maybe three, roms have I had soft reboots/blackscreens/systemui closes. And most of the time they can be solved with a different kernel and a bit of tuning with an app such as faux123 or kernel auditor.
Audio problems can be hard to fix, but let's make sure you can distinguish the problems from the features. An example of a common misconceptions is the audio "clipping" or "lagging" when rotating the screen. This is a feature, it is swapping the left and right channels to keep the audio correct. There is a build prop line you can edit to diable this.
The phone ringtone volume steadily increasing is also a feature in most roms, including stock. It can be found in Settings>sound and notifications> and somewhere near the vibrate option.
Sound distortion is a problem I suffered from on older roms. I eventually started using viper4android on ALL of the roms I install with the superior audio driver (power drain is unnoticeable). All the settings are super easy to use, and easy to discover while playing a song and listening to the differences. Just make sure selinux is set to permissive.
I don't think increasing/decreasing the voltage can be any good for the hardware. If your car says "premium only" then you shouldn't run regular or racing fuel, you should stick to what was intended to work. You can kill battery life, starve the cpu/gpu, increase lag and overheating when messing with voltages.
Try this.
Go get the LATEST version of twrp, go find the Pure nexus rom and download it and Banks gapps, also go find francos kernel and download the latest release.
WIPE EVERYTHING TWICE (cache, dalvik, system, data) and install ROM>KERNEL>GAPPS and reboot into your super stable phone!
Message me for anything else!
Click to expand...
Click to collapse
Thanks for the info. As for the google f/cs, so far that was only on one rom, and i havent had it since. Only browser f/cs are what im dealing with now. As for the sound. I understand the differences between the features, this is not a feature, i know what you mean by increasing ringtone, my issue is nothing like that, its not like, the sound slowly gets louder and louder... It starts out real quiet, and then BOOM full volume. Sometimes the speakers pop a little. Its weird, because it only does this the very first time a sound is played, if i have for instance, touch sounds enabled, and go through my ringtones, i dont have any sound issues. But if i turn off touch sounds, then go back to ringtones, the very first one i select will be reeeeal low.... And then BOOM full volume. This was the very first thing i checked when i switched out phones, and the very first time i tryed it on the brand new phone it did this very same thing. I just assumed it was a known issue.
Sent from my Nexus 6 using Tapatalk
simms22 said:
what bin number does your phone have? try raising your cpu, inly at your highest cpu, by 20-30mV more. about it wiping the cache, what build android are you on? it used to do that to me all the time, but not since android 5.1.1 hit aosp.
Click to expand...
Click to collapse
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms, right now, im on cyanideL which is LYZ28E, and so far, ive had two reboots, one of them had wiped cache by itself apon rebooting, same sound issues, same browser force closing, i even tried chrome, which force closed the second i loaded a web page, other than that, taptalk, g+ hangouts all work fine, its just these 3 or 4 same issues with pretty much all roms
Andromendous said:
bin number? do you mean BUILD number? I have the tmobile variant of the nexus 6, before i started flashing roms, the first thing i did was download the factory image of 5.1.1 for the tmobile version, which is (LYZ28E), then i found the unenforced encryption boot.img someone posted which is the same boot.img, I unlocked, flashed the stock 5.1.1 image, unencrypted the device, then went on to flashing roms
Click to expand...
Click to collapse
ok, got ya.
which browser do you use btw?
simms22 said:
ok, got ya.
which browser do you use btw?
Click to expand...
Click to collapse
sorry, i edited my post above, I try to use AOSP, which seems to be the best, it force closes the least, but chrome immediately f/c's, firefox works pretty good too, but it has graphical glitches all over the place,
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Andromendous said:
ugh..... so i just wiped everything twice and flashed pure nexus rom, and i have no service, at all... . it just never ends.
Click to expand...
Click to collapse
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
simms22 said:
reboot.
try this rom, with the latest gapps, and supersu, its Terminus https://goo.gl/ojD6Z6
now i know that this rom has no issues. if you start developing issues, its either something that your doing, or defective(or something else?).
Click to expand...
Click to collapse
well, its definitely getting interesting. I just tried optipop, and my sound was working normaly! but to my amazement, it was very laggy and system animations werent working correctly, if i backed out of a screen, sometimes it would slide down, sometimes the creen would just flash white and would switch to the last screen, if that makes any sense. I got the same thing as all roms, no network, but i went and searched for networks and it failed, but then my network signal popped up, and when i tried it a gain, tmobile popped up.
so now im trying tremindous, and its doing the same thing with the network, im testing everythnig ells now.
BTW, what kernel would you suggest?
Andromendous said:
BTW, what kernel would you suggest?
Click to expand...
Click to collapse
either elementalx, vindicator, despair, or lean kernel.
simms22 said:
either elementalx, vindicator, despair, or lean kernel.
Click to expand...
Click to collapse
Why not Franco kernel? Just a question
gee2012 said:
Why not Franco kernel? Just a question
Click to expand...
Click to collapse
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
simms22 said:
he doesn't include ondemand and no oc. i know his conservative is similar to ondemand, but its not the same. and i strictly use ondemand. about oc, he made me an oc kernel that i used for a little, but its old now. amyways, i dont really use his kernel, but we are still friends
Click to expand...
Click to collapse
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
gee2012 said:
How is OC for batterylife? Is there a big difference when you OC to say 3Ghz and what about heat issues or do you undervolt?
Click to expand...
Click to collapse
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
simms22 said:
i get from 5-6.5h sot using 3033mhz/300mhz ondemand/deadline. and the n6 doesnt have a heat issue. in fact, i have a hard time getting it over 75C whwn im pushing it to try and get hot.
Click to expand...
Click to collapse
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Andromendous said:
Ok, running Terminus with the latest hellscore kernel and i cant believe it but everything is working good so far. Gonna test some more now. Thanks for the help simms
Click to expand...
Click to collapse