yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Android Development] faux123:
Ugh... You guys made me re-installed CM 7 RC4 with my latest kernel 2.4.3 LV coming from Orange Glacier. I tried all sort of orientations and durations, ALL of my sensors work perfectly...

ALL of my KERNELS (Sense/Froyo/Gingerbread) share the SAME DRIVERS for all these sensors. I was on my Orange Glacier when I read this post, I tested on my Orange Glacier and it was working perfectly there too.

I suggest full wipe perhaps (/system, /data, and /cache)... That's how I reinstalled CM7 RC4 with my latest GB kernel...

Should have stayed away from the forum.... This was how I got burned out the first time... :(
[myTouch 4G Android Development] ~~Tito~~:
I understand your frustration, but I really did see an orientation issue through out the day. I formatted all the partitons and wiped data just to be sure before I flashed RC4 and your kernel, everything else is golden though, performance is awesome and batterylife is a bit improved. Just thay weird orientation issue. I havent had it in a few hours but, if it happens again ill post a logcat. Its a weird random occurrence though.
[myTouch 4G Android Development] Uchennadi:
The orientation only locks up when I been on a call, and maybe I moved the phone from my ear to check something on it, and back to my ear again. I just hit the power button to turn the screen off, and then back on again. Everything then goes back to normal. It rarely happens, but every time it does, the power button screen off and on usually fixes it.
[myTouch 4G Android Development] gaww:
I was getting some instances of orientation issues BEFORE I did a full wipe (fastboot erase, etc.) and clean install of everything - as faux suggested (I had a bust in WiFi with RC4 that was not the ROM - works fine now).

He also had no issues after reinstalling RC4 after doing a full wipe.
[myTouch 4G Android Development] ~~Tito~~:
Exactly my symptoms, but everything else is awesome!
[myTouch 4G Android Development] madwolf27:
Mine issue is a little different, seems ok UNTIL It turn off the screen, which locks it the sensors. I will try the full wipe/reinstall of RC4 tonight.

Faux, I want to say THANK YOU for the incredible things you do here for all of us and know you far exceed any hope or expectation of the end user.
[myTouch 4G Android Development] faux123:
I tried many different combinations, screen on/off, proximity sensor near/far, lux 10~90... and I can't get them to fail... ugh... maybe I have a super phone ;)

My phone OC to 1.84 @ low voltages without crash, sensors works, WiFi range is good etc etc.... I don't know what to say... Maybe my kernel is exposing all the crappy quality control issues for the HTC Glacier HW?!?!? BTW, I had a bad screen phone which I replaced with a good screen phone from T-Mobile a couple of months ago... maybe the QC is much better for the newer batches.... Just a wild guess... My phone just works with all sorts of experimental crap I threw at it...
[myTouch 4G Android Development] ~~Tito~~:
I haven't had any issues so far, bit I am for certian they happened yesterday. I'll keep a look out for it and post a logcat when it happens.

I am using kernel 84 Btw.
[myTouch 4G Android Development] elry567:
Hey faux is this kernel compatible with royal mint I tried it but it didnt go very well?
[myTouch 4G Android Development] clamder:
i'm able to replicate it every time now. it's when i make a call and the proximity sensor turns the screen off when the screen is close to my head. after doing that, without turning the screen on or off, the orientation won't change. hitting the power button off and then on, that fixes this.
[myTouch 4G Android Development] clamder:
please read the OP. any other gingerbread roms, please use 2.15 or below. only cm7 29+, rc3, rc4 can use 2.3.0+.
[myTouch 4G Android Development] madwolf27:
I have the poorer screen AND, while my phone is just fine with lv it will not OC to 1.84 without locking up. So they are definitely different. Tonight I will try the full wipe and I will try the stock voltage. We will see if it makes a difference. FWIW I have been using your kernels for a long time now and never saw any issue until 2.3+
[myTouch 4G Android Development] elry567:
I can oc all the way up to 1.84 love to rub it in my bro face hes got an iphone 4 and my phone leaves his in the dust :)
[myTouch 4G Android Development] infraled:
This was posted right above the download links for the kernels:

"Warning Version 2.3.0+ is COMPATIBLE ONLY with CM7 RC4, RC3 and nightly 31+, all older versions including RC1, RC2, RoyalGinger (RC2 based), nightly < 28 and GB MIUI should stay with version 2.1.5!"

I emphasize this because it is these kind of questions that tax and frustrate our good developers here. Please read all documentation first before asking a question and make sure you have read or searched through the entire topic first to see if it has already been addressed.

@clamder thanks for replying to him. I'm going to do my best to try to help out more in these threads to help offset the questions asked to the developers. I enjoy faux's work and would rather answer inane questions for him than have him eat a gun over the repeated basic questions already answered.
[myTouch 4G Android Development] madwolf27:
Ok. After a full wipe/reinstall (I also installed Faux's Kernel BEFORE ever booting up RC4 witht he stock Kernel) My problem has all but gone away. It's now exactly and replicable the same as Clamder's. It is only a minor annoyance now rather that the phone killer it was.
[myTouch 4G Android Development] madwolf27:
AHA!! I figured out the culpret(s)!!! (?) !!!

Reinstalled all of me apps after the wipe and all was fine until I rebooted. It started again. The only 2 "services" that started after the reboot were CpuNotify and an app that enabled the speakerphone when you flip the phone. I uninstalled that and rebooted and fixed the frozen sensors. I found ANOTHER app to do the same, "upsounddown" and it caused the SAME problem. Uninstalled it and rebooted and unfroze the sensors. About to try yet another app "Flip to Mute" and see if it causes the same.

Yep, third app results in same. Verified and repeated. Stock CM7 Kernel does not have this bug with these apps.
[myTouch 4G Android Development] faux123:
Nice investigative work... what are these apps? Interesting that these "apps" caused the sensors to freeze...
[myTouch 4G Android Development] madwolf27:
Flip - Speakerphone

UpSoundDown

and

Flip to Mute 2

So far, ANY app designed to activate something via orientation in a call.

Upsounddown and flip to mute froze the sensors as soon as they activated during a call. Flip - Speakerphone froze the sensors as soon as it's "service" started.
[myTouch 4G Android Development] madwolf27:
Oh, and, btw, your Kernel is SOOO much nicer to the battery than the stock kernel :)
[myTouch 4G Android Development] faux123:
I installed upsounddown.. LOL.. took me a while to figure out how to use it... And yes I was able to FINALLY freeze my sensors, but they come back after screen off/on cycle.

Anyways, I made a few changes to the kernel's speaker AMP driver and accelerometer drivers... I am going to test it out real quick before I release an update...

This is REALLY NICE WORK man... this REALLY helps me in my kernel hacking... Thanks...
[myTouch 4G Android Development] faux123:
Announcement Version 2.4.4 is OUT!!!!

Fixed the rotation bug found by the Amazing MadWolf27 :D Major Kudos to him....
[myTouch 4G Android Development] madwolf27:
Thanks Faux :D
[myTouch 4G Android Development] camalus:
Well done both of you. Cheers on the quick fixes.
[myTouch 4G Android Development] macheteZen:
Congrats on the success guys, is this fix applicable to the 2.1.5 MIUI kernel as well? I was also having some accelerometer concerns in regards to the MIUI music player on my test drive. I know, I know wrong thread. :-)
[myTouch 4G Android Development] faux123:
Crap, I hate this... I knew this would happen once cm 7 team made a drastic change since nightly 31... Ugh... Ask option94 to update miui framework libs to the latest GB kernel :p
[myTouch 4G Android Development] macheteZen:
Sorry faux didn't intend to stress ya out anymore. MIUI isn't really my dd so no worries but ill repost this there. :-) hate to make demands since I don't make ROMs.
[myTouch 4G Android Development] itzzspencer:
thanks for your hard work!! i donated a dollar. its not much, but its the least i can do =)
[myTouch 4G Android Development] itzsmokey:
back to the old

So does 2.4.4 have the old wifi drivers or the new one from 2.4.2?
[myTouch 4G Android Development] drshorty:
Don't work on royalmiui. Error on wifi.
[myTouch 4G Android Development] faux123:
It has the cm7 driver.
[myTouch 4G Android Development] gaww:
Please don't bug faux on the WiFi issue - the CM7 WiFi driver should be fixed on CM7 and not here.
[myTouch 4G Android Development] itzsmokey:
thanks for letting me know...i'll stay with 2.4.2

and its a simple question since i dont care much about the hotspot but i do care for a stronger wifi receiver....so its not a bother its just a question...no issues here :D
[myTouch 4G Android Development] gaww:
T

Then I would consider staying with 2.4.2 (I am). It really is much stronger.
[myTouch 4G Android Development] phaino00:
I agree about 2.4.2 vs. the later versions. Seems like a more solid connection, if you will.

Sent from my HTC Glacier
[myTouch 4G Android Development] :
Lately, I've been having problems with CM7 and the latest Kernels from here. My phone gets very unstable after awhile with this kernel so I decided to just leave it on CM7's kernel and I haven't had.any problems for a day now. I'm hoping this post can help development or maybe someone can help me out...BTW, it's all Kernels 2.3.0 to 2.4.4. Stock Voltage.
[myTouch 4G Android Development] :
Wow, just kidding, right when I said that, my phone started bugging out. Its gotta be CM7
[myTouch 4G Android Development] itzsmokey:
I agree big time
[myTouch 4G Android Development] darinmc:
Using the latest. Solid wifi, GPS locked np, bt, fast as hell, as in my coworker with an iPhone 4 said "holy sh*t" fast, no issues with orientation, great battery so far, I've ran this phone into the ground trying to get it to bug out and nothing. I'm out of ideas on how to test it... did a run where I had music going, pulled up voice search and ran a navigation, switched immediately to vplayer and played a xvid movie, jumped to NHL gamecenter live and pulled up a live feed of a game, home and opened up a 3d game. No lag, no stutter, snappy the entire time, all the while with a soundtrack for my stresstest. Incredible work faux. I can't imagine what is left to get the to final. Oh and its clocked at 1 ghz with setcpu smartass. Mighty fine work good sir.
[myTouch 4G Android Development] lanternslight456:
sounds badass, can't wait until Royal Ginger gets it's update so I can get this running. Really Excited
[myTouch 4G Android Development] laggo:
I am still getting the lock screen issues with latest kernal and cm7 nb34. SV or LV doesn't matter. I have disabled the TV animations so I can recover it by letting it sleep again then trying to unlock again but it is getting annoying. I don't have these issues with just cm7.
[myTouch 4G Android Development] Mistic99:
Have you done a full wipe recently?
[myTouch 4G Android Development] laggo:
Yah. I did a full wipe when I went to 34. Boot, system, data, SD, cache, devlik, factory... the whole meal.

I even flashed the reset kernal then the new one.

I guess it didn't take right? I had to move back to stock cm last time because of this. Maybe its just my chip.
[myTouch 4G Android Development] jdkoren:
Maybe try clearing Dalvik cache when you flash the faux kernel and let it sit a few minutes on first boot. I'm on RC3, got the upside-down lockscreen today for the first time in weeks, but otherwise everything's good.
[myTouch 4G Android Development] laggo:
What do you mean?

Boot recovery

Wipe everything

Mount USB and copy files

Flash cm

Boot and wait 5

Boot recovery

Clear cache + delvik

Flash reset kernal

Flash faux

Boot and wait 5

Reboot

wait 5

Setcpu - smartass - onboot

^ that is what I did last time, hoping it might help, but it didn't :sadface:
[myTouch 4G Android Development] darinmc:
I never wait before flashing the kernel, just flash the ROM then the kernel then reboot, wait a few, reboot, wait a few and set up. what do you mean by reset kernel? 2.3.0?
[myTouch 4G Android Development] ckisgen:
try fixing permissions in recovery after clearing both caches just prior to flashing new kernel

also, up your min clock to 368hz
[myTouch 4G Android Development] darinmc:
Oh and based on wifi analyzer I see a max loss of about 6 dBm between the 2.4.2 kernel and the cm7 revert. It's a fair distance lost, but definitely not as much as I was expecting considering the comments in the thread. I live in a condo with THICK walls on the first floor, and have perfect coverage everywhere. I do have a first gen wireless N router that uses external antennas, so I suppose that helps, but I really thought I was going to have to stand in the same room as the router after reading how big of a difference the reversion made.

Here is a pic where I was getting -75 dBm, my condo is in the white box, the router is behind one exterior wall in a corner, it does not have a direct line from the window. To make sure I emailed the photo to myself from where I was standing, worked fine. Not a significant test of reception, but it at least showed me packets were being sent and received since I immediately got an email notification.

I know not everyone is having the same success I am, I just think that with all of the problems people are posting it's important to point out that people running the kernel with success don't always post about their success, so all you see are negative responses. I've ran faux's kernels on stock, OG, RGL, IGL, miui, UD, RM, CM7, and RG, all with absolute success. Any errors I encountered were fixed with wipes/cache clears/permissions, careful reading of the op and a little patience.
[myTouch 4G Android Development] gaww:
I had posted pictures of my success with 2.4.2 versus results with standard CM7 in an earlier post here and on CM7 RC thread. Besides a marked difference in range on a so-so wireless access point, I do not get disconnected when using both WiFi and Bluetooth as I do with CM7. For that reason alone, I am staying with 2.4.2 for now.
[myTouch 4G Android Development] :
I don't know what he exactly means but I've been having problems with CM7 and royalginger and it's really bugging me. occasionally my lockscreen becomes unresponsive yada yada but what never fails is my homescreen becoming unresponsive. It bugs the ****.out of me cause it wasnt like this about a week or two ago. I can't scroll through my home pages without a HUGE delay or a force close message, but I can use my phone, app drawer, and browser shortcuts and sometimes the page dots. Also, my app drawer becomes unresponsive sometimes as well. Can someone help?
[myTouch 4G Android Development] theWHITE1:
Good Looking Out

Thanks faux123 and MADWOLF27 for fixing the Gyro issue. It happened to me today and I get home and see the update. Dowloading now and installing. BIG THANX!! :D
[myTouch 4G Android Development] :
Most of the problems that people have should be with the gingerbread off and on animations I notice once. I cut it off. My phone seems to work perfectly fine. As soon I have it on i can easily go to youtube and play a video turn off the the screen and rotate the phone to get a sleep like state. Then wake the phone to have my phone not responding or upside down lock screen.
[myTouch 4G Android Development] darinmc:
...I just wanted to show some good results with the 2.4.4 kernel. That is all. Like I said in the quoted post above...
[myTouch 4G Android Development] The_F_Word:
Ok I'm using u.d. with built in gingerbread, do I use the first time kernel first or just flash the l.v. right away?

UltimateDroid is better then cry..on..again mod :) sent from rooted mytouch 4g. with xda premium
[myTouch 4G Android Development] faux123:
Just want to be clear, UD KANGED CyanogenMod's sources WITHOUT giving much credit to CM team. They might have tweaked UI here and there but underneath, the Framework and core libraries are ALL CM7. (they tried VERY HARD to hide that fact, but it is essential CM7).
[myTouch 4G Android Development] The_F_Word:
Yeh thats true, I still like ud :) nothing personal. Ok Il change my signature lol, but yeh is this the right kernal for ud?

sent from rooted mytouch 4g with xda premium :)PS. I'm a battery addict!
[myTouch 4G Android Development] Marine6680:
Well I am running the latest kernel on my recent cm7 RC4 flash.

With the stock kernel I had issues with the wifi causing a hot reboot loop after I turned it on. Flashed faux's kernel and no more issues. Seems I am just going to stick with immediate flashing of faux kernels from now on. To bad, I wanted to do a direct comparison between stock CM kernel and Faux kernels.

I mean I know faux's kernels are the best, but I don't want to get jaded so I wanted reminded just how much better they were. :D As it turns out, apparently quite a lot better, seeing as my phone can actually run now. ;)
[myTouch 4G Android Development] verysick:
I like diz1 more than the other kernel available for cm7, battery doesn't get hot, only when I'm at 1.84 for 2 long.
[myTouch 4G Android Development] mikejet:
I have not been able to do the quadrant score above again. The closest I can get is 2600's
[myTouch 4G Android Development] mikejet:
My phone really really hates Interactive for some reason. I tried min 246 max 1.7 and it reboots on Interactive.

:mad:

I really want to get that same Quadrant score consistently
[myTouch 4G Android Development] Amac1222:
Just ran this!! Amazing! Ran at 1.84 min/max on performance setting. Smartass and interactive didn't come close. Ran consistent 59-61 on linpack
[myTouch 4G Android Development] graffixnyc:
Performance will eat your battery badly. Because even it you have a min set it will always run at the max. So if you have a min of 246 and a max of 1.84 and set the performance governor it will constantly run at 1.84. That's my understanding anyway, I could be wrong. But I wouldn't advise having it clocked at 1.84 on a constant basis. Its going to really stress your CPU.
[myTouch 4G Android Development] Amac1222:
oh no i wouldn't set it there ever for any extended period of time... i have profiles setup to save my battery.. i just wanted to run it maxed out for the hell of it to see how high it could go lol.

just having a little fun haha
[myTouch 4G Android Development] whoamanwtf:
My gps doesn't work on here, I just get searching for gps, is this a known issue?

Sent from Mytouch4G smartass CM7
[myTouch 4G Android Development] Lakeshow423:
So majority of people don't run setcpu settings? They just let the kernel do it's thing? Bettry battery life? Thanks for the info in advance! I've been reading but just want to know what the majority of people are running to optimze batt life. I don't OC either, phone is fast enough :D
[myTouch 4G Android Development] Marine6680:
I believe this kernel defaults to 1.1ghz smartass governor. So no, you do not "need" setCPU.
[myTouch 4G Android Development] jdkoren:
Has anyone confirmed that this kernel extends battery life given the same settings compared to the CM7 RC1 kernel?
[myTouch 4G Android Development] TRDburglar:
In the Cyanogenmod settings, under performance, there are CPU settings which allow you to set min and Max CPU speeds as well as governors. So I find CPU settings redundant.
[myTouch 4G Android Development] jdkoren:
I'm still using setCPU for battery %, battery temp, and charging profiles. Unless they incorporate that somehow into the CM settings, I don't see any other way.
[myTouch 4G Android Development] verysick:
i just set charging & temp profiles...
[myTouch 4G Android Development] jhjmonnee:
Running at 1.7 smartass gov

not too shabby
[myTouch 4G Android Development] Infinite76:
So i been reading the whole thread and i just want to confirm 2 things. One) Does everything work? BT? Wifi? Video? And Two) those who are using SetCPU what are your setting profiles? I just want to get an idea of what direction i want to go. I dont need to push to get 1.8 and 2300+ on quadrant. i just want a stable kernel that is snappy but i am most concerned with battery life on moderate to high use.
[myTouch 4G Android Development] aussiehairspray:
Everything seems to be working great!
[myTouch 4G Android Development] Infinite76:
Which version are you running stock voltage or low voltage?

Sent from my beautiful mind
[myTouch 4G Android Development] andrewiz2kewl:
kernel issue or is it just me?

Hi idk is it just me or does this kernel lower anyone else's internet speed? because after flashing this I tested my 4g again I get 0.5mb/s and I usually get around 3-4mb/s and also on my wifi network I got only about 1.5mb/s and usually get around 6-7mb/s. So is there some kind of limiter on this kernel on data speeds?
[myTouch 4G Android Development] verysick:
Just want to say thanks for all you have done...
[myTouch 4G Android Development] Ayeso:
Currently running CM7 RC1 and I found, while this runs good, I have odd graphical glitches on my launcher bar, unsure why.

will post an example later.
[myTouch 4G Android Development] faux123:
It should work... because UD == CM7 :D

BTW, I was not offended by your post.. I just want people to know that UD is a KANGED copy of CM7... People can download and use UD and I don't have a problem with that.. Just want to spread the word and give the credit to CM Team :D
[myTouch 4G Android Development] jlacy76:
Want to try this kernal, I see it says" If you HAVE NOT installed my performance tweaked kernel, then you need to FLASH the Performance Kernel First"

Where do I find that?
[myTouch 4G Android Development] lanternslight456:
Its the download called the cfs tweaked kernel in the original post.

The link

http://www.mediafire.com/?bc194uqnxg6n11y
[myTouch 4G Android Development] jlacy76:
Thank you.
[myTouch 4G Android Development] CB620:
i notice now that upon flashing the kernel my oovoo no longer connects over wifi only 4G. is there a fix?
[myTouch 4G Android Development] Marine6680:
I just flashed the latest kernel straight to cm7 with no other intermediate steps. (other than the cache wipes) Was that not the proper procedure? Seems it works fine though.
[myTouch 4G Android Development] darinmc:
It'll work fine, the only other option is to flash the 2.3.0 kernel which faux tweaked to act similar to the BFS while keeping CFS compatibility first, then flash 2.4.4 over it, keeping the tweak while having his latest. The way you did it has his classic CFS, which still runs great so it's really just a matter of what you want to try. I have to say, though, that I really like the 2.3.0 tweak. It is extremely responsive when bouncing between apps.
[myTouch 4G Android Development] The_F_Word:
Has anyone come up with the lockscreen not popping up anymore problem? And also the screen of anamation not working even if it is on problem yet?
[myTouch 4G Android Development] faux123:
Special Public Preview Release:

Updated bunch of drivers and added LATEST PATCH from CodeAuroraForum (CAF) for 2D/3D wake_lock (which means MORE Power Savings from Power Hungry Graphics Drivers)...

Low Voltage Version ONLY and NO SUPPORT until officially released...

You are welcome post issues or problems related to this special version here, but there will be NO SUPPORT for them.

The File ==> Version 2.4.6 Low Voltage <==

When reporting issues, make sure you specify the kernel version FIRST

ie,

Issue: blah blah

ROM: CM NB #36

Kernel: 2.4.6 LV

BTW, I am interested in hearing the Power Savings from this special version... I want to see how much power is saved by this latest CAF patch...
[myTouch 4G Android Development] itzsmokey:
getting it right

So I just want to be clear....all these new kernels don't have the updated WiFi Driver from 2.4.2, right? Till the CM team fixs it
[myTouch 4G Android Development] ckisgen:
that is correct (as far as 2.4.4 and 2.4.6 not having them .. can't speak for exactly what/when it's gonna take on the remedy)