I am new to all this and am trying to understand the kernel, I installed jellybam 3.2.0 and now 3.3.0, when I did that would I have automatically installed a new kernel, or is that not replaced?
From what I have read the kernel allows the jellybam ROM to talk to the hardware, so that said is it possible that the kernel I am using could be what is causing my Bluetooth to keep connecting and disconnecting BUT also my proximity sensor not to work? Sorry if this is the wrong place to ask
I have done a quick search but couldn't find anything to confirm my suspicion.
My kernel at the moment is 3.0.053-g099c572
Sent from my Sensation using xda app-developers app
bluetba said:
I am new to all this and am trying to understand the kernel, I installed jellybam 3.2.0 and now 3.3.0, when I did that would I have automatically installed a new kernel, or is that not replaced?
From what I have read the kernel allows the jellybam ROM to talk to the hardware, so that said is it possible that the kernel I am using could be what is causing my Bluetooth to keep connecting and disconnecting BUT also my proximity sensor not to work? Sorry if this is the wrong place to ask
I have done a quick search but couldn't find anything to confirm my suspicion.
My kernel at the moment is 3.0.053-g099c572
Sent from my Sensation using xda app-developers app
Click to expand...
Click to collapse
Yes every ROM usually includes a kernel, which is supposed to work well with the ROM. Maybe it's the kernel causing bluetooth problems, but it may also be the ROM itself which is buggy, or you firmware which is outdated. You'd better ask in the ROMs thread for more info. There are a lot of things which could cause problems and it's difficult to find out the cause sometimes. If they can help you in JellyBam's thread you could try another ROM and see if problem persists
Sent from my HTC Sensation Z710e using Tapatalk 2
Thanks for taking the time to explain that - it is appreciated and confirms my thoughts
Sent from my Sensation using xda app-developers app
Related
I'm am running leedroid 3.1.2 with the recommended radio but my signal is up and down. So my question is do I need to flash is again. I flashed it when I first installed leedroid 3.0.1. Also has anyone noticed any lag with 3.1.2 mine seems to have a lot compared to 3.0.3. Any suggestions would be great
Sent from my Desire HD using XDA App
skeeter86 said:
I'm am running leedroid 3.1.2 with the recommended radio but my signal is up and down. So my question is do I need to flash is again. I flashed it when I first installed leedroid 3.0.1. Also has anyone noticed any lag with 3.1.2 mine seems to have a lot compared to 3.0.3. Any suggestions would be great
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Unfortunately, a Radio may not work as well for one person as it does for another. For the most part, it's going to be location based. The recommended radio is just something that works well for the Dev, based on their location. You can always try a different radio, but your results will vary. And in some cases, you may not even see a difference at all. Worst case scenario, you can always go back.
Thank you. I was just reading about ril files didn't know if I needed to look into that as well? Any ideas?
Sent from my Desire HD using XDA App
skeeter86 said:
Thank you. I was just reading about ril files didn't know if I needed to look into that as well? Any ideas?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
The way I understand RILs (and I could be wrong) is that they are basically drivers. If that's the case, using the wrong RIL would be like just using whatever HP driver for your HP printer. It's a crapshoot as to whether it'll work, and it might not work well if it does.
Well I went ahead and flashed the latest ota radio and ril files I'm gonna give it a try got the highest speed test so far 4.0 down and 3.0 mps up. Thanks for the input!
Sent from my Desire HD using XDA App
skeeter86 said:
Thank you. I was just reading about ril files didn't know if I needed to look into that as well? Any ideas?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you haven't already, there's a new radio thread by tribalartgod in the dev section that you should keep an eye on, as well as the "radio without eng s-Off" thread by shadowfox. There's also the RIL thread and original radio thread, both over in the desire hd section.
Inspired Ace 1.0.1¦ XDA Premium
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)
Ok so I just Rooted my phone recently and everything is ok but one thing is messed up is. There is no audio. Is there any way to fix this? And if so then how can i fix it? And suggestions will help thanks for your time!
Also sorry if this was asked and answeres somewhere else before. I just couldnt find it anywhere.
Sent from my Desire HD using xda app-developers app
Avacell said:
Ok so I just Rooted my phone recently and everything is ok but one thing is messed up is. There is no audio. Is there any way to fix this? And if so then how can i fix it? And suggestions will help thanks for your time!
Also sorry if this was asked and answeres somewhere else before. I just couldnt find it anywhere.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
The post says "Our DHD is NOT 100% compatible with the Euro DHD. A rom using their kernel will yield no sound. The downgrade rom is one of those, so you must either flash a compatible rom after this procedure is done, or you must flash a compatible kernel (linked below) to get sound back."
I found this quote above, it seems the the downgrading rooting process kills audio due to uncompatible kernel install. In order to get audio back you need to flash a compatible rom or kernel (DHD or Inspire 4G)
I'm sorry I actually already solved the problem. Thanks for your help though.
Sent from my Inspire 4G using xda app-developers app
I've got ics on soff desire s and can't use Bluetooth it searches but doesn't find anything and knowone can see me. Ive checked installed apps and nothing effects it.
Any suggestions?
Thank you
Sent from my HTC Desire S using xda app-developers app
*bump
Sent from my HTC Desire S using xda app-developers app
my device work very well
Same issue
I am having the same issue. Not able to search for any device or anyone can see me. When I turn on bluetooth it turns on but not finding anything. Taken it to a service center, he suggested to revert the OS to 2.3 and check (not sure how to revert back to 2.3) if that is still not working then he would replace the hardware. Please suggest, is there anything I can do to fix the issue from OS level.
Note: My phone not rooted and installed official RUU update4.0 from HTC dev.
I've fixed my Bluetooth I reflashed the ruu.
I now run custom Rom and it works perfect.
It's just software so try flashing ics again
Good luck and I hope it works for you
Sent from my HTC Desire S using xda app-developers app
hoyler30589 said:
I've fixed my Bluetooth I reflashed the ruu.
I now run custom Rom and it works perfect.
It's just software so try flashing ics again
Good luck and I hope it works for you
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Which ROM did you install? I tried installing PACman and Viper ROM's but still the same issue. After multiple tries it will detect the bluetooth device but does not connect, now again if you try to search the same old story. Not sure if this is the hardware issue or software issue.
mvvamsi said:
Which ROM did you install? I tried installing PACman and Viper ROM's but still the same issue. After multiple tries it will detect the bluetooth device but does not connect, now again if you try to search the same old story. Not sure if this is the hardware issue or software issue.
Click to expand...
Click to collapse
Tired different ROM's (Viper, JellyFirebean v2) some times it works and some time it does not. Seems to be some issue with the hardware will get it checked in Service center...may be later.
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.