Active Topics
-
Nokia Booklet 3G (RX-75) Drivers (60)
to Alternatives by Maemish - 3 days, 23 hrs ago -
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 6 days, 19 hrs ago - more...
|
2016-03-05
, 10:29
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#572
|
Since yesterday, I run the sensors drivers from KOT49H (so older than the KTU84x based which are the ones in CM11) and they haven't crashed yet.
| The Following User Says Thank You to romu For This Useful Post: | ||
 |
|
2016-03-05
, 11:30
|
|
Posts: 411 |
Thanked: 1,105 times |
Joined on Jan 2010
@ Europe
|
#573
|
You know about the general bug 820: sensors: random crashs?
KOT49H CPU consumption is too high, those of llelectronics work perfectly in Messwerk and CPU consumption is okay, but rotation stops working in lipstick, that's what i observe with 2.0.1.7.
Last edited by BluesLee; 2016-03-05 at 12:46.
KOT49H CPU consumption is too high, those of llelectronics work perfectly in Messwerk and CPU consumption is okay, but rotation stops working in lipstick, that's what i observe with 2.0.1.7.
Last edited by BluesLee; 2016-03-05 at 12:46.
|
|
2016-03-05
, 14:54
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#574
|
Thanks for this information. So, I made some analysis and yes, the KOT49H driver eats too much CPU but not in the same way as does the KTU84x.
With the KTU84x (the CM original driver), the driver eats CPU when it crashes.
The KOT49H didn't crash during my testing (I've switched to the KRT16M to see how things are going). I saw it eating too much CPU, but only when the phone was awake. As long as the phone is asleep, the CPU consumption is far from being significant. So, imho, that could be an acceptable tradeoff, because my N5 is asleep most of the time.
I'm keeping the KRT16M for a moment.
With the KTU84x (the CM original driver), the driver eats CPU when it crashes.
The KOT49H didn't crash during my testing (I've switched to the KRT16M to see how things are going). I saw it eating too much CPU, but only when the phone was awake. As long as the phone is asleep, the CPU consumption is far from being significant. So, imho, that could be an acceptable tradeoff, because my N5 is asleep most of the time.
I'm keeping the KRT16M for a moment.
|
|
2016-03-05
, 17:51
|
|
Posts: 1,746 |
Thanked: 1,832 times |
Joined on Dec 2010
|
#575
|
Originally Posted by RealJohnGalt
basically headsets working with it. since they work with the Jolla phone but things go to **** on the N5
When you say "better bluetooth," do you mean that you have working bluetooth audio with the cm11 base?
Edit: the sensor disparity is quite possibly related to bootloader version. When bootloader changes have broken blobs, z axis rotation has seemed (from my experiences) to have been the first to go. If you check strings or glance through leaked qcom vendor sources, you'll see that the differing blobs support the various hammerhead hardware.
| The Following User Says Thank You to m4r0v3r For This Useful Post: | ||
 |
|
2016-03-13
, 02:45
|
|
Posts: 191 |
Thanked: 129 times |
Joined on Dec 2009
@ Bloomington, IL
|
#576
|
Anyone out there using the Nexus 5 with Sailfish on T-Mobile US and have MMS working? I've tried all the APN settings I can think of and none of them seem to allow me to send a picture message.
__________________
qAndora - Pandora Radio on the N9/N900
qAndora - Pandora Radio on the N9/N900
| The Following User Says Thank You to Jef91 For This Useful Post: | ||
|
|
2016-03-13
, 18:16
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#577
|
MMS doesn't work for me on the N5 in France.
| The Following User Says Thank You to romu For This Useful Post: | ||
 |
|
2016-03-13
, 20:55
|
|
Posts: 654 |
Thanked: 2,368 times |
Joined on Jul 2014
@ UK
|
#578
|
I couldn't get MMS to work for me on the N5 in the UK, but I don't know if that's because I bought the US version of the phone my mistake, or because of something specific to the Hammerhead port, or because it just doesn't work at all on Sailfish.
In my experience, MMS is pretty flaky on Sailfish anyway - I can receive MMS messages on my Jolla phone, but not send them (EE, UK).
In my experience, MMS is pretty flaky on Sailfish anyway - I can receive MMS messages on my Jolla phone, but not send them (EE, UK).
 |
|
2016-03-14
, 10:15
|
|
Posts: 151 |
Thanked: 775 times |
Joined on Oct 2014
|
#579
|
I have working MMS with Jolla phone and Oneplus One in Finland. And I think I had it also with Nexus5 when I had that phone (If I hopefully remember right).
So MMS's are working with at least Jolla and Oneplus One with Sailfish Port.
Do you have "Settings - Mobile network - MMS Access Point" visible in Nexus 5?
If yes -> I would say that there is just some configuration problem with towards your Network provider.
ps.
https://together.jolla.com/question/...us-to-improve/
So MMS's are working with at least Jolla and Oneplus One with Sailfish Port.
Do you have "Settings - Mobile network - MMS Access Point" visible in Nexus 5?
If yes -> I would say that there is just some configuration problem with towards your Network provider.
ps.
https://together.jolla.com/question/...us-to-improve/
|
|
2016-03-14
, 12:20
|
|
Posts: 307 |
Thanked: 488 times |
Joined on Sep 2010
@ USA around Chicago
|
#580
|
Originally Posted by Jef91
It usually works if you switch to 2g. I think I got it working with 4g but I am not sure if it is working anymore.
Anyone out there using the Nexus 5 with Sailfish on T-Mobile US and have MMS working? I've tried all the APN settings I can think of and none of them seem to allow me to send a picture message.
Try the following setting:
Con name: T-Mobile MMS
apn: internet2.voicestream.com
proxy: 216.155.165.50
proxy port: 8080
mms message center: http://216.155.174.84/servlets/mms
__________________
Apps for iPhone & iPad
• Malayalam Keyboard for iPhone • Telugu Keyboard for iPhone • Gujarati Keyboard for iPhone
Apps for iPhone & iPad
• Malayalam Keyboard for iPhone • Telugu Keyboard for iPhone • Gujarati Keyboard for iPhone
Edit: the sensor disparity is quite possibly related to bootloader version. When bootloader changes have broken blobs, z axis rotation has seemed (from my experiences) to have been the first to go. If you check strings or glance through leaked qcom vendor sources, you'll see that the differing blobs support the various hammerhead hardware.