Kernel - HTC Sensation

Is it possible, at all, for a kernel to disable the internal sensors in a way that even a reflash with any rom/kernel/RUU does not re enable them?
The following sensors quit working after a kernel flash..
phone never has been handled hard or dropped, 3 months old.
accelerometer
gyroscope
light
magnetic field
orientation
proximity
lights under button after sleep state.

What kernal?
Sent from my HTC Sensation 4G using XDA App

Galaxa12 said:
What kernal?
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
I dont want to place blame at all, im not even mad, but i was using a cm7 build then flashed faux's kernel for asop/cm7
Pyramid-Kernel-0.1.9-CM7-1.56GHz i think it was

Reflash the rom and see if they spring back to life

bonesy said:
Reflash the rom and see if they spring back to life
Click to expand...
Click to collapse
tried reflashing the kernal i was using, superwiped and reflashed that rom, nada.
super flashed and went back to arhd and nada, super whiped, ran the ruu for my phone and still nada.
flashed radio and nada,....
turned s-on and am waiting for my replacement phone to come,...
still want to know if its possible for a kernel to fry them

Related

[Q] Black screen on wake up

Happens 3-4 times already,without a reason sometimes when i try to switch it on it shows black screen,i'm trying holding the power button but no use.. only when i remove the battery for minute starts working again.Phone is brand new rooted with stock Rom 2.3.3.
Any suggestions would be greatly appreciated.
Same for me with superposr rom on Google Nexus s. But never with oxygen rom.
Is flashing custom rom the only solution?
L00n said:
Happens 3-4 times already,without a reason sometimes when i try to switch it on it shows black screen,i'm trying holding the power button but no use.. only when i remove the battery for minute starts working again.Phone is brand new rooted with stock Rom 2.3.3.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
do you have your cpu overclocked, or any undervolt scripts installed? my phone would freeze, or phone would crash if i overclock to high and if i install any undervolt scrips over 25mv
No overclock no scripts, I was thinking about overclock but didn't do it,really start worring now.Thanks for the replay.
what are your cpu settings ? something has to be off. i dont know what else would cause this
245.8 - 1.0 ghz what else you wanna know and thanks for your time, sir.
bump ... any advice will be appreciated.
L00n said:
245.8 - 1.0 ghz what else you wanna know and thanks for your time, sir.
Click to expand...
Click to collapse
Just try to wipe phone and reflash your rom and see if it fixes it
sent from my unity loaded inspire 4G
My phone acts up at 245 no problems at 348
Sent from my ADR6400L using xda premium
rayford85 said:
Just try to wipe phone and reflash your rom and see if it fixes it
sent from my unity loaded inspire 4G
Click to expand...
Click to collapse
I will try it,thank you kind sir.
How do I do that??? I have the same problem
josh_ww said:
How do I do that??? I have the same problem
Click to expand...
Click to collapse
Go in recovery. Do a full wipe ,then reflash your rom
sent from my unity loaded inspire 4G
when you talk about reflashing my rom, what exactly do you mean??
My problem is that I have a stock phone (not rooted, just the stock rom) and I did a factory reset and now my phone goes into that black screen and I can't do anything :S
Oh if your not rooted disregard my earlier post. Only meant for rooted phones. Sorry I'd contact HTC about it and see what they tell ya
sent from my unity loaded inspire 4G
So I'm not the only one with this problem ... Wonder what exactly is causing this...
L00n said:
So I'm not the only one with this problem ... Wonder what exactly is causing this...
Click to expand...
Click to collapse
if reflashing your rom didnt fix the issue i would turn your minimum cpu setting up to like 350, something like that. sometimes our phones act funny at low cpu settings. Not all phones, but some. try that and see what happens
So far so good,if it happens again I will try that,thank you for your time.

[Q] CM7 based roms all cause SOD...does anyone know what's causing this?

Everytime i have tried flashing a CM7 based rom, and i've tried almost all of them, once the screen goes to sleep it won't wake up. i think that's called sleep of death (SOD), pardon my n00bness if i'm wrong. the odd thing is that when i press the wake button, the phone and even the digitizer wake up because i can hear/feel the phone unlocking when i make the sliding motion on the screen, but the screen itself will not wake up. Does anyone have any idea what's causing this? or better yet any ways of preventing/fixing this?
Do you have this issue on stock?
Sent from my LG-P999 using xda premium
What kernel r u using? If u flashed uv kernel try to use stock voltage, some devices don't work well with custom uv kernels
Sent from my LG-P999 using xda premium
I have this problem with all 3 kernels, stock, oc UV, and oc stock voltage .. I've had this phone for a month now, this is what makes it a waste of money for me. Even my girl has this problem with her g2x, yesterday I put cm 7.1, hers started doing it too.. and she's had 3 replacements..
Sent from my LG-P999 using Tapatalk
Did u wipe ur data and format system before flashing? Try to fix permission too. Only guessing but maybe the battery is bad, as far as I know u not getting new one with replacement, so if u had same issue on stock rom that could be a problem.
I had 2 replacements but had that problem only if undervolt too much.
Sent from my LG-P999 using xda premium
Well, I don't think its the battery dying but someone mentioned here before that if you look at the battery where the connectors are, there's 4 on the battery but 3 on the phone
Sent from my LG-P999 using Tapatalk
FatalityBoyZahy said:
Do you have this issue on stock?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No this issue only occurs on CM7 based roms, OTA 2.3.3 based roms work great
Waldano said:
What kernel r u using? If u flashed uv kernel try to use stock voltage, some devices don't work well with custom uv kernels
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I haven't purposely flashed any non-stock kernels alongside the roms, unless all the roms i flashed included UV kernels....but i've flashed almost every CM7 based rom
Waldano said:
Did u wipe ur data and format system before flashing? Try to fix permission too. Only guessing but maybe the battery is bad, as far as I know u not getting new one with replacement, so if u had same issue on stock rom that could be a problem.
I had 2 replacements but had that problem only if undervolt too much.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did wipe data, format system and even fix permissions and still same problem occurs, I don't think it has to do with the battery tho because stock OTA based roms don't have this issue...it must be something particular about the CM7 base
Also, could it be the fact that i have the WIND mobile optimus 2x? it says p999-DW on the back though
use miui it doesnt have the SOD problem cm7 did it the last time i had it (3 days ago)

[Q] Problem with accelerometer!!

I have a rooted Nexus S i9023 running CM9 RC1 with Air Kernel... I usually have auto rotate turned off because I don't like it! But then a few days back my device used to auto rotate automatically with the rotate being turned off.. It solved itself after a few days so I didn't bother. But it's just stuck in landscape mode and will not switch no matter what I do! It happened while I was using KangyU also and it happened with it also 3 times. Everytime I need to perform a factory reset and flash a new ROM and then it solves :/ I used androsensor and it does show a value for Accelerometer but my phone simply does not rotate! Is there a problem with my accelerometer? Do i need to give it to the service center or can I do something that will solve it? Any help appreciated
If doing a factory reset/ reflash fixes it. Then it is not a hardware issue.
Not factory reset persay. I need to flash a new ROM for it to go normal
Sent from my Nexus S using xda premium
This is probably a problem with your Kernel or ROM, please flash a stock ROM to ensure that the accelerometer is fine. If you are afraid you might lose anything make a backup or so.
Okay yeah AiRKernel might be the problem. Thanks I'll try it and let you know. Thanks!
Sent from my Nexus S using xda premium
I went stock.. But AndroSensor is still showing the same reading it was showing on CM9.. And the auto-rotation bug only comes after a few weeks into any ROM.. Also everytime that occurs I get a prompt saying
" Complete action using
Clock
Tune In Radio "
Everytime I get that pop-up I'm stuck on landscape for infinity. So can it be an app problem? It's happened so far on 3 ROM's I've used (KangyU, CM9, Paranoiandroid)
so I doubt whether it is a ROM issue. Maybe a Kernel issue because I've used AirKernel on all 3 of them
Could be either I suppose. Not sure how either could cause it though
The sensor read out should be the same no matter what rom is on there. That is normal. The app itself tells you what the read outs from each sensor should be as well
My point. But what I mean is, If readings are the same then the behaviour should be same as well right? Where is the accelerometer exactly located?
Sent from my Nexus S using xda premium
It happened on Stock also :/ stock ics stock kernel. Same popup :/
Accelerometer issue?
Sent from my Nexus S using xda premium
kkricardokaka95 said:
It happened on Stock also :/ stock ics stock kernel. Same popup :/
Accelerometer issue?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
If a new rom and kernel didn't fix it then it might be hardware.
Strangest thing happened. I uninstalled Tune In Radio and voila auto rotate back! So the app was the issue! But any idea what might have possessed that app to do so? :/
Sent from my Nexus S using xda premium

Loss of proximity sensor with custom kernal

I have 2 infuses, mine running JB CM10 fantastically (thanks Scott et Al) and my sons back on stock rooted GB. My problem is when ever I gry to flash a better ROM such as emancipation... or simply entropy's kernel for GB I lose the use of the screen on a phone call. As soon as the call is placed or received the screen goes dark and stays there till the call terminates... am not new to flashing... did all the necessary cleaning prior to install and ended up odening back to a form of stock GB. Works fine in both stock and rooted stock, any suggestions?
Sent from my SGH-I997 using xda premium
Guess no one has any guesses for me....
Sent from my SGH-I997 using xda premium
My phone does something similar, I just tap the proximity sensor and it usually comes back up.
There are apps in the market place that can read out your sensor info
Sent from my SGH-I997 using xda premium
jdsatyr said:
I have 2 infuses, mine running JB CM10 fantastically (thanks Scott et Al) and my sons back on stock rooted GB. My problem is when ever I gry to flash a better ROM such as emancipation... or simply entropy's kernel for GB I lose the use of the screen on a phone call. As soon as the call is placed or received the screen goes dark and stays there till the call terminates... am not new to flashing... did all the necessary cleaning prior to install and ended up odening back to a form of stock GB. Works fine in both stock and rooted stock, any suggestions?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Op: are you saying that on 1 infuse, it works fine. The other infuse, custom rom causes prox sensor loss?
That is to say, that 1 particular infuse, only stock kernel will work?
I recalled 6 months back, another user mentioned this to me. despite of all he did, other custom firmware causes prox sensor loss. Only stock kernel ran his phone properly. He traded his in or upgraded..I don't recalled exactly.
gl
qkster said:
Op: are you saying that on 1 infuse, it works fine. The other infuse, custom rom causes prox sensor loss?
That is to say, that 1 particular infuse, only stock kernel will work?
I recalled 6 months back, another user mentioned this to me. despite of all he did, other custom firmware causes prox sensor loss. Only stock kernel ran his phone properly. He traded his in or upgraded..I don't recalled exactly.
gl
Click to expand...
Click to collapse
Sadly.. that's exactly what I'm saying... anything but stock shuts down the Prix sensor while using phone
Sent from my SGH-I997 using xda premium
elliot.newnham said:
My phone does something similar, I just tap the proximity sensor and it usually comes back up.
There are apps in the market place that can read out your sensor info
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Tapping has no effect and rbe apps to test the sensor sow or running fine on stock and dead on custom roms
Sent from my SGH-I997 using xda premium

Weak WiFi on jb ROMs?

I have been trying out a few ROMs and it seems the WiFi on the jelly bean ROMs are weak compared to ICS roms. Has anyone had this problem.
Sent from my HTC Sensation using xda app-developers app
ojp420 said:
I have been trying out a few ROMs and it seems the WiFi on the jelly bean ROMs are weak compared to ICS roms. Has anyone had this problem.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I've used Bruce's CM10 builds and recently switching to the official Cyanogen CM10 builds. Last week I tried out Nikez's JB 4.2 AOSP build. I had great wifi on all of them. Like satndin gout in my front yard with the wifi router in the basement in the back of my house good. So it's not the ROM itself. (Though it could be a combination of the ROM and some app or mod you're running)
You might have a weak connection on the wifi anteneas inside the back case of the phone. Take the back cover off, look at the gold pins on the phone, and make sure they are all raised up. You can take a tiny screw driver and pry them up a little more to make sure they are getting good contact with the back cover (which is the antenea). Juts be VERY careful when doing it.
It might not help, but it's a cheap thing to try.
I have tried that too but its strange I can switch to a ICS ROM and I will have full bars in my whole house but with the jelly bean ROMs its one or two bars unless I'm right next to it.
Sent from my HTC Sensation using xda app-developers app
ojp420 said:
I have tried that too but its strange I can switch to a ICS ROM and I will have full bars in my whole house but with the jelly bean ROMs its one or two bars unless I'm right next to it.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I've got some WiFi tweaks in my kernel that might help. My kernel, Sultan, has the WiFi voltage increased to the max and it has some WiFi signal parameters altered at the kernel level so WiFi networks with weaker signal can be seen. If my kernel doesn't really help then I can build a kernel just for you that forces the system to use the BCM4329 WiFi driver instead of the BCMDHD WiFi driver; that may help. BTW, if you download my kernel then make sure you download the one for Jelly Bean and not the one for Sense.
I tried your kernel and my WiFi is still weak compared to ICS but does seem a little stronger
Sent from my HTC Sensation using xda app-developers app
This is a confirmed issue, its not kernel related, because even with the kernels with improved wifi voltage (which is more voltage than stock), its still a weaker signal than on an ICS based rom.
James1o1o said:
This is a confirmed issue, its not kernel related, because even with the kernels with improved wifi voltage (which is more voltage than stock), its still a weaker signal than on an ICS based rom.
Click to expand...
Click to collapse
Is it an issue with proprietary drivers/code or a issue with JB itself?
I tried two different ones but both the same still weak WiFi ... I am new to HTC so I might not be wiping something right but anyways what kind of recovery should I use and what should be wiped every time I flash a new ROM
Sent from my HTC Sensation using xda app-developers app
ojp420 said:
I tried two different ones but both the same still weak WiFi ... I am new to HTC so I might not be wiping something right but anyways what kind of recovery should I use and what should be wiped every time I flash a new ROM
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
4ext recovery and before flashing any rom format all partitions except sdcard
That is awesome and terrible news all at the same time thanks guys
Sent from my HTC Sensation using xda app-developers app
So is that the one that says touchcovery
Sent from my HTC Sensation using xda app-developers app
I am using twrp 2.2.0 now what's the difference
Sent from my HTC Sensation using xda app-developers app
ojp420 said:
I am using twrp 2.2.0 now what's the difference
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
most users who are S-ON(like me) 4ext has a feature which calls smartflash
before flashing any rom you have to enable smartflash before flashing(if you are S-ON)
and then flash the rom
for S-ON devices it is one way to boot a rom after installation
if you are S-OFF you don't need that feature
So if I'm s off then ext4 isn't really a must have for me
Sent from my HTC Sensation using xda app-developers app
ojp420 said:
So if I'm s off then ext4 isn't really a must have for me
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
yes but it is more preferable for any kind of installations(roms,kernels)
if i am not wrong
personally i haven't used twrp but i think you are fine
rzr86 said:
yes but it is more preferable for any kind of installations(roms,kernels)
if i am not wrong
personally i haven't used twrp but i think you are fine
Click to expand...
Click to collapse
In your case TWRP should work just fine
rzr86 said:
yes but it is more preferable for any kind of installations(roms,kernels)
if i am not wrong
personally i haven't used twrp but i think you are fine
Click to expand...
Click to collapse
4ext was really buggy for me. 1 of the many bugs I experienced with 4ext was that sometimes after flashing a kernel the phone would get stuck at the HTC screen and I would have t use fastboot to flash a boot.img file in order to get my phone to boot; flashing another kernel in the recovery didn't work and it would still be stuck at the HTC screen -_- If you have S-OFF then use TWRP. Just my 2 cents.

Categories

Resources