yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] sino8r:
It's something you've screwed with because the new, aggressive undervolting is on the experimental kernel only. I do know what you're referring to having a couple G1s and MT3GS not being able to OC as high as others. This is something else because I've seen the tables on the stable and they are barely undervolted. Plus, as far as the OCing goes... it's set at the same old 1.5 ghz like regular cm9 is by default. It must be an old 3rd part app or something clocking you too high at boot. I've had this before so don't panic... fight the reboots until you can change the settings or wipe. Not much else you can do.... sorry. It's definitely not the rom though. If your hardware responds this way to cm9... might be something wrong because it really shouldn't be this sensitive. Good luck!

---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------

This is a good example of normal behavior in which another was having an issue (or thought it was related). Mine can handle 1.7 for a little while until I push it too hard with "dead trigger" or something similar. That's pretty normal to have small variations like this on chipsets but not like what the other guy was describing... that was a bad setting (due to 3rd party OCing app) or bad hardware all together.
[T-Mobile myTouch 4G Slide] SilverL:
I'm pretty sure the undervolting tweaks in the stable are the same from day r1. The experimental is the one that gets all the crazy stuff. So if they have a problem with stock then something ELSE is wrong.
[T-Mobile myTouch 4G Slide] sino8r:
Very true but from his post and what he was describing didn't seem normal. I mean the stable kernel isn't aggressively OCed/UVed by default. That's some app that he has setting it way too high or low from a past rom. Either that, or his hardware is seriously burnt out :( I'd try a good ole fashioned wipe before deciding though...

---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------

Ding! Ding! Ding! You get the prize! Lol!

Exactly... and btw, so far... the aggressive 96mhz UC/UV is working great! No freezes overnight/ deep sleep etc. Might make a decent kanged addition to your rom ;)
[T-Mobile myTouch 4G Slide] mattlowry:
well the first time as soon as i clicked 1.7 it restarted then i set it again on the ondemandx governor it ran fine for a while then rebooted in my pocket. and when i say restart it goes to splash screen and stays there
[T-Mobile myTouch 4G Slide] rtiangha:
Guys, I cleared both caches and am otherwise running the stock version of this rom. I don't undervolt or overclock or do anything of that nature. I don't even play games on this phone! R5 experimental worked fine too but I decided to stick with stable because I didn't use any of the new features. But for some reason, I get reboots using r7.
[T-Mobile myTouch 4G Slide] soldierexile:
Works on s-on device as well as s-off, no problems with the s-on device yet either, works on both. Have to flash kernel from adb on fastboot screen though.
[T-Mobile myTouch 4G Slide] AdamWill:
Thanks a lot for this! Couple of questions: the only difference between this and the build from a few days ago on the CM9 thread is the remote dialer exploit fix, right? And can it be flashed over that build without a wipe? Thanks again!
[T-Mobile myTouch 4G Slide] ohgood:
server errors on playstore ?

home button doesn't work ?

can't do much without those working so far ;)

oh, genius button no worky either.

EDGE only on tmo towers, and wifi is slow.

(this might be a bug release?)
[T-Mobile myTouch 4G Slide] Fuzi0719:
No problem with earphones here. In fact, my music with earphones sounds exceptional with this ROM. Using PowerAMP.

---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------

Those work just perfect here on this ROM.
[T-Mobile myTouch 4G Slide] gtmaster303:
How do you receive MMS with no data??? o.O
[T-Mobile myTouch 4G Slide] ohgood:
I had some filesustem errors on my sdcard... all is well now, even Google+ hangouts are working!

very nice, fast from.... thank you sir!
[T-Mobile myTouch 4G Slide] AdamWill:
I think you have a bad flash. I don't have any of those problems here. This is really just a slightly modified CM9.1 stable, there's no reason it should be that buggy, so you probably need to re-flash.
[T-Mobile myTouch 4G Slide] Some_dude36:
As I said I don't recieve many MMS messages so I just turn data on when I get one . Which isn't often so it's no big deal.
[T-Mobile myTouch 4G Slide] SKAm69:
I think what he really means is the volume on headset while calling isn't changing and is always loud. I'm also having this issue. But this bug has been always there.
[T-Mobile myTouch 4G Slide] onebornoflight:
First version didn't fix my battery drain at all. Still had the wake lock so I was gonna dl new version and try it but drop box has disabled links due to high traffic.
[T-Mobile myTouch 4G Slide] butch87402:
Hey what happened to the vibrate mode is like when I turn the volume all the way down it freezes then goes to silent as if it skips vibrate
[T-Mobile myTouch 4G Slide] ryaninc:
Hey, I don't know if it's related to the new kernel or if some other tweaks were added but Google+ Hangouts now WORK. I tried them several times on the original 9.1 ROM and they never worked, so something definitely changed.

Just thought I'd mention it so you can add it to the OP since it's kind of awesome. :D
[T-Mobile myTouch 4G Slide] OGIGA:
Headphones volume during call doesn't work for me either. Slide moves, but volume stays fixed (really loud).
[T-Mobile myTouch 4G Slide] Emmanuel U:
I haven't noticed any bugs, but I'm at 68% battery with 9 hours on stock battery :good:
[T-Mobile myTouch 4G Slide] wesgarner:
You have some tweaks on here you may want to revert

Commented on your commit on github too:

https://github.com/xmc-wildchild22/...mmit/d215a7a0e0d20966e5f01407f8ed119a5c1dda15
[T-Mobile myTouch 4G Slide] scverhagen:
this relates to mpdecision on the "exp" branch which I am testing...

This is NOT included in this build. The kernel for this is from the "aosp" branch.
[T-Mobile myTouch 4G Slide] aeroxy:
I am very happy this copy of ROM so far. It looks like the battery will not work very well when I use Google Maps. Other than that, it works just fine. Good work.
[T-Mobile myTouch 4G Slide] Riyal:
This is what happened to mine also. Hmmm seems like a headphone compatibility issue.

@OP Did you rebuild this from source? Or KANG it from the previous one and modified it?
[T-Mobile myTouch 4G Slide] GravvyTrain:
Yes I was wondering this too. Can the new release be flashed over the first one?

Also, I have never really messed with the CPU governors before, and I put mine on 'conservative' a couple days ago. It seemed to me like I got a bit more juice with no noticeable negative effects on functionality. :cowboy:
[T-Mobile myTouch 4G Slide] nosuchfile:
checked http://dylanreeve.com/phone.php

found that phone IS vulnerable to exploit (r1 ROM)

cleared cache, cleared dalvik

flashed r2 ROM (s-off)

reboot, tested via website, and phone no longer vulnerable to exploit

no obvious problems with ROM

thanks dev, good work as always! :good:
[T-Mobile myTouch 4G Slide] AdamWill:
I don't think you're right.

scverhagen wrote:

"This move may be controversial--I have moved many of the experimental features to the main kernel because they should be stable enough for everyday use. From now on, the exp kernel will be used to test new features and which will be moved to stable once they are adequately tested."

and looking at the git log, the undervolting stuff seems to have gone into the 'stable' kernel between r5 and r6.

So for now those of us who might not want to risk the undervolt/OC stuff can only run old stable. My battery life is good enough without the UV/OC stuff so I'd really prefer to skip it.

---------- Post added at 03:18 PM ---------- Previous post was at 03:15 PM ----------

I believe there's some more aggressive UV/OC in 'stable' r7 compared to 'exp' r5, but it gets a bit head-stretching comparing the logs. If you want to check yourself, this is the log for exp:

https://github.com/scverhagen/htc-kernel-doubleshot/commits/exp

and this is the log for 'stable':

https://github.com/scverhagen/htc-kernel-doubleshot/commits/master

These are the new undervolting changes between stable r5 and stable r7:

https://github.com/scverhagen/htc-kernel-doubleshot/commit/736d013acfefeb336e85daee5568eb46f76fb67e ("AGGRESSIVE undervolting")

https://github.com/scverhagen/htc-kernel-doubleshot/commit/78a3efce5d99bd7b3c9bb13d52fc1c2ebdd1f62e ("allow even more acpu undervolting...")

https://github.com/scverhagen/htc-kernel-doubleshot/commit/0c35f1ccec8a22bb8246dc3a0cb7c86fc76b24dd ("acpu: Undervolt even more...")

the combined impact of the first and third is fairly significant.
[T-Mobile myTouch 4G Slide] sino8r:
Yikes! I dunno... That's why I love setcpu because of safemode. Normally, I can escape those situations but it helps when I do get stuck when experimenting with new clock settings.

---------- Post added at 05:45 PM ---------- Previous post was at 05:29 PM ----------

Hmmm... it looks like you are right... there are a few more than I expected. (I hadn't reviewed all the commits in a couple days) The tables still seem conservative enough to be stable for 90% of users. Maybe we need to wait on more input from users. Right now, I have one running exp kernel (self), one with stable (wife), one with stable (friend), and another with stable (work-friend) and haven't had any complaints. I'm running exp. for a few days before recommending/flashing for them. So far, I've pushed the heck out this with no hiccups. I guess everyone here should post their findings just in case. I'm just a bit confused because all seemed so well and stable on exp r5 and should carry over nicely for r7 stable. Now, if you were referring to exp r7... I'd understand because there are a few more drastic changes in UN/UV that MIGHT affect a few users. I guess we'll see but all is swell right now :)
[T-Mobile myTouch 4G Slide] scverhagen:
undervolt/instability

I would check for overclocking and governor settings that some apps "set on boot" (kernel tuner, cyanogenmod performance menu).

Strange things can occur when flashing kernels and having these settings "applied" on boot.

REVERT all of these setting changes back to the default values (overclocking, undervolting, io schedulers) and then try to flash the new kernel. Also, does this occur with the R7 exp kernel?

I can undo the undervolting changes...
[T-Mobile myTouch 4G Slide] scverhagen:
Ok. That confirms it. Ill revert the undervolting and release.
[T-Mobile myTouch 4G Slide] AdamWill:
Well that's the thing, you can't just test it on four phones and figure it must be fine for everyone, because the whole problem when it comes to OC/UV is that processors differ.Maybe you know the whole screed, but CPU manufacture is messier than maybe people think it is. The manufacturer produces a whole bunch of processors, then tests them at all sorts of different voltage/speed levels.

They have to draw some kind of compromise between yield and performance. All the produced processors will never have identical capabilities, they all come in on a bell curve. A very few will be amazing, capable of running at 2GHz off of 0.5v or whatever ridiculous numbers you want to plug in. A very few will be crappy, and need 1.5v to manage 800MHz without falling over. And all the rest will be in the middle of the bell curve, still spaced out. Some will be capable of more than others.

Manufacturers usually draw their cut-off point near the bottom of the bell curve; they don't ship the terrible processors, and then they set the 'stock' speed and voltage of that particular processor wherever it needs to go to let them ship, say, 90% of the processors they produce. They could set the cut-off point way higher and sell a 'faster' processor without changing the manufacturing process at all, just by changing the cut-off point and having more of the produced processors fail QA. (This is how some Intel/AMD 'enthusiast' CPUs come about, BTW - this process is sometimes referred to as 'binning', the manufacturer will identify the processors at the top end of the bell curve and 'bin' them separately, then set their clock higher or voltage lower or both and sell 'em for more money).

Given this is how processor manufacture is done, the only settings you can actually be sure will work 100% reliably on all the processors that got shipped _are the stock ones_. That's how the stock settings were decided in the first place, they're the level at which most of the produced processors pass QA and can be shipped.

Given that it's a bell curve, it may well be true that say 80% of shipped processors are actually capable of quite a bit better than the stock settings, which is why OCing / UVing *often* works for people, and why they maybe can't understand that it doesn't work for everyone - we all have the same phone, right? But there's always going to be that 10% or 20% of CPUs out in the market which happened to be the ones at the low end of the bell curve, that just passed QA, and will fall over if OCed or UVed. Which is why I don't think it's a good idea to do stock OCing/UVing, particularly on a ROM that's meant to be a fairly 'stable' one, as this one is. It should be left as a reversible, optional, tweak, it's not appropriate for a stock setting.
[T-Mobile myTouch 4G Slide] Shani Ace:
Hi there, I got a problem with my ringtone. I put a mp3-song in the system\media\audio\ringtones directory (as I always did before on cm9) and chose it in my ringtone settings as the default ringtone. But everytime I get a call, it doesn't ring, instead I hear another short ringtone. when I try to play the mp3 from the systems folder, winamp says it can't be played, but the same file on my SD works just fine. Actually, it's the same with most of the ringtones I can choose between in the ringtone settings, none of them sound when clicked on.

This bug is really annying since I don't really get notificated when someone calls me.

Does anyone know a solution? Thanks in advance!
[T-Mobile myTouch 4G Slide] inkling:
Thanks for all your hard work. Does this mean that when you've reverted we should look for an r8?
[T-Mobile myTouch 4G Slide] SilverL:
or a 7b

I also looked through the commits, I missed all of those but my mind was fried from work and I was just leaving too... Oh well we cant catch everything. Sorry for being human.
[T-Mobile myTouch 4G Slide] hapa8o8:
RingsExtended App :silly: HOLLAAH~:highfive:
[T-Mobile myTouch 4G Slide] Shani Ace:
Well thanks for the advice, but I doubt that this app will do anything different than what I do manually. Besides this is a feature of the ROM that worked fine in all previous versions, so there must be a kinda bug or so.
[T-Mobile myTouch 4G Slide] sino8r:
Exactly, those 10% should have never passed. Their tests are way too broad and seem to haven't gotten even more lax since the advent of multicore chipsets. So now we are here with 1 phone out of 10 to 20 mentioned that has issues. You know what I did with those G1 and MT3GS phones? I sent 'em back ;) Well... whatever. To each his own and all that stuff....
[T-Mobile myTouch 4G Slide] AdamWill:
we don't all have that option; I'm in Canada, you can't buy the phone here. I got it second hand off eBay. Can't 'send it back'.

edit: oh, and btw, if they get stricter and ship fewer processors, the processors cost more money, so your phone costs more money. Pretty simple. If they're trashing 20% of the CPUs they produce that's costing them more money than trashing 10%, and that cost gets passed on.
[T-Mobile myTouch 4G Slide] rtiangha:
Thanks scverhagen! I used to overclock PCs all the time so I know how inconsistent machines can be. This phone runs fine on stock speeds, but I guess I must be in that 10-20% that can't deviate too far. Nothing wrong with the phone since it runs fine on stock. It's just the luck of the draw when it comes to the potential overclocked-ness (or undervolted-ness) of the CPU and/or GPU.

Thanks for all your hard work! The battery life on this thing thanks to your tweaks is super-awesome!
[T-Mobile myTouch 4G Slide] gtmaster303:
CPUs are never trashed, especially if they still work at a lower speed. They're just put into a "lower end" setup.

i.e. Intel Core i Series>Pentium>Celeron, etc.

Will it cost more money? Probably, because you have to make new chips anyway. Will the price go up? I doubt it. We all know the what a phone should be priced at, and the manufacturer would know better than to produce a phone that they can't make a profit on, by raising the price. Noone would buy it
[T-Mobile myTouch 4G Slide] demkantor:
iphone....

:D
[T-Mobile myTouch 4G Slide] blackknightavalon:
R3 ROM with R7 kernel and I got 27 hours of battery life out of my Mugen with moderate use. Can't produce screencap because of the reboot issue involving switching either airplane mode or wifi on or off.

Sent from Spaceball One.
[T-Mobile myTouch 4G Slide] Paitor:
Hi, I can't activate wifi on r7. Great work with the camera flash and qr code issue though.
[T-Mobile myTouch 4G Slide] scverhagen:
Stable or exp?
[T-Mobile myTouch 4G Slide] Paitor:
Do you need a log of it or something. How do I make one if so?
[T-Mobile myTouch 4G Slide] SilverL:
Stable or Experimental kernel?

S-ON or S-OFF?

Depending on those answers he may then need a log, orr you may just need to wipe and reflash.
[T-Mobile myTouch 4G Slide] AdamWill:
Of course I was simplifying a bit, the post was long enough already =)

They _do_ trash the ones that are just really bad, basically defective. Desktop manufacturers, like you say, then usually 'bin' the whole rest of the bell curve so they can sell the worse-performing ones cheaper and the better-performing ones better...this is why OCing usually isn't much good on the chips produced early in a given CPU's lifecycle, but better later on, because they refine the manufacturing process and so all the processors usually come out working better, so even the ones binned for low-end sale are often actually capable of much better.

I don't know if this is how Qualcomm and other embedded vendors do it, though, or at least to the same extent. They don't seem to sell such a widely differentiated range of 'models' as the desktop vendors do, but I don't follow that scene as much as I used to the desktop one.
[T-Mobile myTouch 4G Slide] blackknightavalon:
Stable, but I look at the reboot issue as more of an inconvenience than anything else. It would help if HTC/T-Mobile would release official ICS for our device so we can get the drivers.
[T-Mobile myTouch 4G Slide] anitgandhi:
That would be the day. Not releasing an OTA update, fine I'll live. Atleast give us a dev rom. As far as I can tell It can't be all that hard since sensation got an OTA update...
[T-Mobile myTouch 4G Slide] AdamWill:
My guess is the doubleshot just isn't a big enough seller to bother with. Sensation was a pretty popular device on multiple carriers. doubleshot...not so much. We're probably just too few people for HTC to care about.
[T-Mobile myTouch 4G Slide] onebornoflight:
Which is why I went with the relay instead of another doubleshot. Sad but true... I am done with HTC.
[T-Mobile myTouch 4G Slide] SilverL:
Sliders used to be real big, but they've fallen. I am trying to get some stuff working in my AOKP port the main problem is that AOKP doesnt have official support for sliders and so far none of the sliders I've seen with it have their sources published.

Also them releasing a ICS rom wont do much more than allow sensed ports and provide SOME binaries(which other phones of the same model, base, processor, etc already provide anyway). And the configuration files for some of these things are the same regardless.
[T-Mobile myTouch 4G Slide] iceolate:
I really like this release, guys. I've been following along for a long time. I like this device, and these releases are really making it prime time.

I have a question about the hardware keyboard. Normally, if you press the ALT or CAPS key once, it'll just do it for that character. But pressing it once sort of locks it every time on one press. Does anyone know what I'm talking about?
[T-Mobile myTouch 4G Slide] abnormalreply:
I haven't been able to get Spirit UL to function properly with CM9.1. The app starts. It appears as if it's playing; song names show up, I have a signal, etc. But I hear nothing. I know it's not a problem with the sound of the phone itself beacuse I can still hear ringtones/volume slider beeps when I adjust the volume with headphones on. The app just doesn't seem to be producing sound or something. Any idea what I could be doing wrong? Running r7 experimental kernel, but it wasn't working on stable r5 either.

---------- Post added at 12:10 AM ---------- Previous post was at 12:05 AM ----------

CAPS/ALT works fine for me. One press for one character, two presses to lock.
[T-Mobile myTouch 4G Slide] strapped365:
That's an issue I have with SwiftKey, come to think of it all slider phones suffer from it. I get around it by holding alt or caps then entering the letter or character then letting go of alt or caps
[T-Mobile myTouch 4G Slide] abnormalreply:
Small bug report: flash does not work down to 5% with the r7 experimental. I'm not sure at what point it stops working, but it wasn't working <25%, so maybe it's back to the default 30%?
[T-Mobile myTouch 4G Slide] sino8r:
You have to hit the change it from headphone to speaker. Play with it a bit more. It works fine and even better than stock fm app.

Yeah, those asswipes finally addressed that issue. They are so freaking slow with that app. Ridiculous...

I think he was referring to the qwerty though. It's something weird though because it works fine for me and everyone else.

Works fine here (1 exp, 3 stable r7 phones). You must have S-Off... for some reason certain init.d scripts and sys (kernel) edits don't work properly on S-On devices.
[T-Mobile myTouch 4G Slide] seancojr:
Thanks for confirming this. I had wondered about what caused that for some time.
[T-Mobile myTouch 4G Slide] strapped365:
Yeah i know he was talking about the physical keyboard, I was too. Just having SwiftKey active messes up the physical keyboard
[T-Mobile myTouch 4G Slide] Paitor:
Oki, I run the stable one. The phone S-OFF. I will try a wipe and reflash to begin with.
[T-Mobile myTouch 4G Slide] Shani Ace:
I got another major bug! Somehow the hardware buttons on the front suddenly don't work anymore (they're not broken since they work in recovery). But the same keys (home, menu,, back, google) on the keyboard work.

I think I'll just go back to kornyones ROM, that one was really stable. Don't know what you're doing with your ROMs but even the not experimental kernel seems to be messed up.
[T-Mobile myTouch 4G Slide] abnormalreply:
I figured out Spirit UL. Thanks. I had to do Settings > Audio > Method > qdsp5v2. And about the flash not working down to 5% r7 exp, I am S-OFF.

edit: I re-flashed r7 stable and the flash is working below 30% now.
[T-Mobile myTouch 4G Slide] Paitor:
The phone didn't boot up. It got stuck in the boot screen. Had to flash original cm9 to get it to work. Why did that happen?
[T-Mobile myTouch 4G Slide] sino8r:
Oh yeah, that WAS the bug lol! Not sure why I said that and what I was thinking :silly: anyways, the swiftkey devs finally addressed the bug and said they were looking into it. Its one of the most voted bugs has been there forever. Still angry about but have moved on to Jelly Bean keyboard pro which works well as a replacement, I guess... still miss my swiftkey :(
[T-Mobile myTouch 4G Slide] strapped365:
I got SwiftKey on sale for a dollar and it has really gave me my money worth. The only complaint I had with it was I couldn't use the kb, but now I don't mind the bug because it keeps me from being dependant on my kb, because my next device prolly won't be a slider