Hi,
Since build 5.10 rotation and light sensor are broken eventough I flashed the latest kk modded modem from this website. I would like to know if someone with a D800 and SlimKat over 5.10 have those two things working.If someone could post this in the SlimKat thread in development section which I cant as it needs more than 10 posts I would be thankful.
Thanks
Software forced rotation works but automatic rotation doesnt, its the position senser thats not working.
Maybe he has moved to new sources have you tried flashing stock kitkat modem at all as this is the obvious choice to me?!
Ok, I flashed the modded kk modem from xda thread from 4 april made to fix rotation and it didnt work. Now guess what? I did what you said and flashed original LG modem found somewhere in the 20 spet 2013 thread and everything worked! I wonder which one is newer.
Thanks!
Glad you're sorted. The stock kit Kat one is newer the modded one is just recently modded not created.
Sent from my LG-D802 using Tapatalk
Related
Iv already got a GPS lock when I was on xdabebbs ROM 3 different times. Then I clean flashed carbon and mahdi. Well in carbon and mahdi, if I hit GPS to see where I am, It'l Lock like 3houses down. So its kinda close. But when I type in an address to navigate to it, the GPS signal just gives up and says GPS signal lost. I even flashed the g2gpsfix.zip but no luck . but that zip works great on ROMs that aren't for 24a
Which version of Mahdi? Depending on the version (April release, beta release, or May aka Release 1) you need different versions of the baseband to have working sensors, rotation, GPS, etc.
If you are using a version prior to Release 1, you also need to flash a stock-based ROM in order to purposely configure the sensors.
IOW, you should read this post:
http://forum.xda-developers.com/showthread.php?p=52568043
And then upgrade to Mahdi 2.5 Release 1, using the stock kitkat baseband.
Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
phoenix_rizzen said:
Which version of Mahdi? Depending on the version (April release, beta release, or May aka Release 1) you need different versions of the baseband to have working sensors, rotation, GPS, etc.
If you are using a version prior to Release 1, you also need to flash a stock-based ROM in order to purposely configure the sensors.
IOW, you should read this post:
http://forum.xda-developers.com/showthread.php?p=52568043
And then upgrade to Mahdi 2.5 Release 1, using the stock kitkat baseband.
Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
Click to expand...
Click to collapse
Thanks. But I'm already running the 24a kk ota version of mahdi
sent from your moms phone
[Case history]
I've been using CM11 for quite a while and one day I messed up. I installed a Kernel that wasn't compatible with CM11 and I couldn't boot the phone. So I used ADB to push a CM11 ROM and flashed it using TWRP and it was fine...until...
I found that all my sensors were not working....well not all, but 'all'. Please let me explain.
I noticed that Rotation doesn't work anymore; I noticed that Auto Brightness would not work anymore; I also notice Accelometer wouldn't work.
So I downloaded the app 'Phone Tester', and I went to the 'Sensor' section and there was nothing detected there! No sensors at all.
However, I have this cover for my phone and when I cover the phone the screen will go out --> I assumed that means the proximity sensor works? I also noticed that the screen will blackout when I am on a phone call.
[My question]
I searched a bit and had two speculations.
1.) Baseband/Modem problem? --> I tried flashing the KK Modem for D802 and it didn't fix the problem
2.) Kernel problem? --> I think this is quite possible...but didn't flashing the ROM = flashing in a Kernel?
Any help is appreciated!
If I were you I would flash it back to stock and see if they work then
sent from my T-Mobile LG-VS980
herman925 said:
[Case history]
I've been using CM11 for quite a while and one day I messed up. I installed a Kernel that wasn't compatible with CM11 and I couldn't boot the phone. So I used ADB to push a CM11 ROM and flashed it using TWRP and it was fine...until...
I found that all my sensors were not working....well not all, but 'all'. Please let me explain.
I noticed that Rotation doesn't work anymore; I noticed that Auto Brightness would not work anymore; I also notice Accelometer wouldn't work.
So I downloaded the app 'Phone Tester', and I went to the 'Sensor' section and there was nothing detected there! No sensors at all.
However, I have this cover for my phone and when I cover the phone the screen will go out --> I assumed that means the proximity sensor works? I also noticed that the screen will blackout when I am on a phone call.
[My question]
I searched a bit and had two speculations.
1.) Baseband/Modem problem? --> I tried flashing the KK Modem for D802 and it didn't fix the problem
2.) Kernel problem? --> I think this is quite possible...but didn't flashing the ROM = flashing in a Kernel?
Any help is appreciated!
Click to expand...
Click to collapse
it is a baseband issue, as you know cm has not incorporated the lg kk changes which means that the kk baseband would not work you have to flash the d802 jb baseband and you will get sensors working again
XxZombiePikachu said:
it is a baseband issue, as you know cm has not incorporated the lg kk changes which means that the kk baseband would not work you have to flash the d802 jb baseband and you will get sensors working again
Click to expand...
Click to collapse
Thanks! I flashed the JB Baseband and it actually worked!
hi
i installed lastest cyanogen mod for my G2 but unfortunatly i found out that most of my sensors are disabled like the gyroscope.
any idea why ? anything i need to install ?
thanks
You need the proper baseband for CM11.
CM11 uses jelly bean sources so you need the 4.2.2 baseband. cloudyfa has them, search around in these forums or on Google. That will fix the sensors. Keep in mind when returning to a 4.4.2 Rom that you need to flash the 4.4.2 baseband..
(note: if you have the verizon lg g2 and you're using unofficial cm11 that's based on 4.4.2 sources, you need to flash that. Again, cloudyfa has a repo)
Last week there was a problem im CM which f...ed up sensors. Same problem in some CM based AOSP Roms. In this case has nothing to do with baseband.
Should be fixed now. Just flash newest version.
tropenfrucht said:
Last week there was a problem im CM which f...ed up sensors. Same problem in some CM based AOSP Roms. In this case has nothing to do with baseband.
Should be fixed now. Just flash newest version.
Click to expand...
Click to collapse
We hope that ?
Q&A for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
4 cores working with the screen on... battery life....
stuck at logo after kernel flash
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
DT2W double tap to wake
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Hear myself in the phone... rom or kernal problem?
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
asustweaker said:
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
Click to expand...
Click to collapse
did you flash kitkat version or lollipop version? Sounds like you flashed lollipop version
Nicholi85 said:
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Click to expand...
Click to collapse
Update the touch screen firmware....there's an echo call via android terminal emulator or in my updated version in synapse
Nicholi85 said:
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
Click to expand...
Click to collapse
These are ROM related errors...the call echo especially... Depending on ROM I could help....also see if it still persists in my latest update
Love this kernal, and I flash when installing a new LP build, but I've been having problems lately. After initial setup or reboot I get the" NO UCI SUPPORT " message. I'm running LiquidSmooth's latest build for the LS980, is anyone else having this issue.
Run om g3 based roms?
VictorAKAx said:
Run om g3 based roms?
Click to expand...
Click to collapse
No. This kernel is for AOSP-based ROMs. G3 ROMs are stock-based.
Typos courtesy of my Ice Cold LG G2 (D803).
just flashed your kernel, got stuck in a boot loop.
VS980, liquidsmooth 3.2 milestone.
what can i do? was excited to try out your update
Great kernel, running super smooth on AICP.
Thanks!
He's working on the fix for cm 12.1.
I sent my files on hangouts, just wait
edit: figured it out
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
perforatedpaper said:
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
Click to expand...
Click to collapse
Use the 0 init method:http://forum.xda-developers.com/showpost.php?p=56948464&postcount=73
I'm using F320K with BlissPop v2.3 rom, when flash this kernel for lp 5.0.2, it cause loopboot. Pls up kernel fix for lolipop 5.1. Hope to see it soon. Thanks u
llamas612 said:
I'm assuming that those are 5.0 based, since they're from January, right?
Click to expand...
Click to collapse
I think they're KitKat based. I tried already and it caused my d800 to go in a boot loop.
I wonder if anyone has got, perhaps, the 5.1 d800 version? I'm getting kinda desperate since my fav rom switched to a kernel that makes my phone really really hot.
Really need a link to latest 5.1 B14ckB1rd kernel for D800 :/
Pls...
Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards