Hi guys, first tine poster here so I apologise for any mess ups.
I have the international version of the Note 3 (N9005), and I've just flashed the most recent Snapshot of Cyanogenmod ( cm-11-20140609-SNAPSHOT-M7-hlte.zip ) and everything works fine with the exception of two things. The first (and minor) issue is that I can't seem to find the feature to select the amount of home screens.
The main issue is whenever I make/receive phone calls.Whenever I try to make or receive phone calls, the dialler app screen won't display so I can't select things like loudspeaker or any other call features, and the only way that I can hang up the call is to wake the screen up using the menu button and selecting the 'hang up' feature from the scroll down menu. Its annoying because otherwise the ROM is amazing.
Any help will be appreciated.
Try temasek unofficial cm11. He builds from the cm sources and adds custom kernel. Dont forget to backup efs, fsc, and fsg.
AO7 said:
Try temasek unofficial cm11. He builds from the cm sources and adds custom kernel. Dont forget to backup efs, fsc, and fsg.
Click to expand...
Click to collapse
Hi, thanks for the reply. I've just flashed temaseks unofficial cm 11 mod and I still have the same issue. Any ideas?
Related
Good Evening Dudes
I'm just introduced on this section and it's first time than i ve had a stuff like this awesome samsung
Smooth Fast Strong And God ! it's the beautifull customisable stock rom (it's really beautifull to compare with htc stock rom)
well the question is not here and the target also
i've never had the oppotunitities to try a CM 10.1 on any device Htc desire x hasnt official CM and not possible to port CM10.1 cauz Htc doesnt provide the kernel source.... damn
(it's was juste for put in situation)
What's the real interest -Gain can i expect with the CM10.1 on the Galaxy S4 ?
Whith this rom it's sound interesting to put a custom kernel also.
what can we do with cm 10.1 than we cannot with a stock rom ?
Yeah a know , i can make a backup on my stock rom , flash the cm 10.1 try and if doesnt like it restore to the backuped stock.
Thanks for your time
If you had any other suggestion better than the CM 10.1 (i know it s on nightlies sound like equal as alpha but
topic is open :s
Well the Stock ROM is pretty much as bloated as a whale. CM is only 200MB in size, so first of all it will save space on your internal memory. Second of all, you won't have a lot of processes running in the background like you do now, your phone will be a LOT more responsive. Ofcourse, as with any custom ROM, there will be some bugs and those ROMs will need testing and updates (that's why nightlies exist). But eventually there will be stable versions and imo, it'll beat the stock any day. On the other hand, the stock ROM has some functions like the IR blaster, the smart-pause, smart-scroll and hover function, etc. If you're a big fan of those things, stick with your Stock ROM. But if you would like to a clean, simple, bloat free and faster experience than you have now, a custom ROM is a great way to achieve it. But that's not the only thing ofcourse, CM also has some extra functions and customization options you won't find in your stock ROM, you can tweak your system quite a lot and there are some things I couldn't live without (for example swapping your menu key for your recent apps switcher, and putting the menu function on the long press ).
Thanks a lot
Sound really interesting
CM 10.1 it's more in touch with i'm looking for
The actual build of CM 10.1 can be used on a basic day usage ? or it's better to wait a few days ?
If i flash the cm now ? need also to flash another kernel or just flash the zip by philw touch recovery ?
can i come back to my stock backuped rom after if i want ? with the restore function of philz touch recovery ?
I'm using Philz Recovery too and yes you can flash CM10.1 from there (I have the latest build from June 12th on it). Before you flash, make your sure you wipe/factory reset your phone in Philz Recovery. You might also need to flash the CM10.1 rom 2 or 3 times (the second time it usually works), on the first try it always gives a Status 7 error (don't worry). Look at the thread for the Offical CM10.1 Nightlies, there's a lot information there!
It's working pretty good for me, I haven't found any major bugs so far. Just make sure you make a Nandroid backup in Philz Recovery first (and store it your external SD card for safety and to save space ofcourse ). You can always return to that backup through the restore function in Philz Recovery yes.
Also, if you update your CM10.1 with a new nightly build (for example next week, or next month), do it manually and flash it in the recovery each time. Updating it from the Settings->About->Cyanogenmod Updates menu bricked my phone today, so I guess there is still a bug there. Besides that, there are no issues what so ever according to me.
PS: You're from Liege? I'm from Genk
last question before the first try
With the original Cm we need to flash gapps separately or it's inside the rom ?
If external suppose to take the last release on goo
If I remember correctly you need to flash it separately
Sent from my GT-I9505 using xda app-developers app
Try This one -> http://forum.xda-developers.com/showthread.php?t=2296266
Yeah after flash the rom 4 times finally she install correctly ( 3 times error7 but no affraid)
Ui is clear, phone running smooth and very well no issue with wifi or 3g
The first bug i ve seen was about the carrier name -- the carrier name is showed like an id on a database (think the code for showed the cells with carrier name is not correct)
For the rest no speciq issue detected
Thanks a lot for your help
PS : i ve also find a answer to one of my question
when use cm you must flsah the gapps separately and link is coming on cyanogen page.
I ve read also than the build for the S4 T-mobile seems to work fine on this phone more bugs corrected on it ?
No trying BT for the moment cauz i dont had BT device
@disturbed : i ll try the rom linked this evening . Thanks a lot
Hello all.
I recently unlocked and rooted my Verizon Galaxy Nexus (the first time I've done this) and flashed this ROM to it: http://forum.xda-developers.com/showthread.php?t=2532320
The ROM seemed quite glitchy, the quick toggles were not working correctly and eventually one day when I tried to turn on my phone, it got stuck in a boot loop. I then flashed back to stock using the Nexus Root Toolkit. I still wanted a custom ROM, so I then flashed this ROM to my phone: http://forum.xda-developers.com/showthread.php?t=2427087
This ROM is almost completely working, but I have some issues with it. For example, some of the quick toggles do not work correctly. My data toggle does not change when I short press it, the bars just stay orange (screenshot here: http://i.imgur.com/vpOgpBe.png) Could someone tell me what this means? Is it supposed to be like this? I would assume that short pressing the data toggle is supposed to turn mobile data on or off, correct? The quick toggle settings are a standard feature across all Omni ROMs, right?
I also cannot get an internet connection over data now either. My MMS messages have also not been working since I installed the Fork My Life ROM.
Some other minor issues I have with the ROM is that when I short press the location toggle, it will sometimes close the quick settings window.
Should I post about these problems in the ROM's thread? Are any of the above normal happenstances in an Omni ROM? This is my first post on XDA so please cut me some slack.
JayBurd said:
I recently unlocked and rooted my Verizon Galaxy Nexus (the first time I've done this) and flashed this ROM to it: http://forum.xda-developers.com/showthread.php?t=2532320
*snip*
I still wanted a custom ROM, so I then flashed this ROM to my phone: http://forum.xda-developers.com/showthread.php?t=2427087
*snip*
Should I post about these problems in the ROM's thread?
Click to expand...
Click to collapse
Maybe someone can answer your other general Omni questions, but yes, if there's bugs in an unofficial modified OmniROM, those should probably go in that ROM's thread. Is the bug caused by Omni or the modifications? Since it's not stock Omni, we err on the side of caution and go with it's the modifications.
Hi, I have installed the latest nightly's and snapshot on my Note 3 N9005 and I am struggling to Dial anyone. The screen keeps going blank. It is a little better when using my Bluetooth Headset but is really totally useless. I usually have to take the battery out and reboot to gain control back.
I have tried
Full Wipe before each install. (cache & data)
CM11 - 27/07/14
CM11 - 26/07/14
CM11 - 25/07/14
CM11 - 08/07/14 M8
All have the same problem.
I am using CWM V6.0.4.7.
I would much rather use Cyanogenmod and am being forced to use one of the Stock ROMS OMEGA V21 which is ok but not what I am after. Is anyone else having this issue? Can I use another dialer?
Any help would be appreciated
:fingers-crossed:
doughty400 said:
Hi, I have installed the latest nightly's and snapshot on my Note 3 N9005 and I am struggling to Dial anyone. The screen keeps going blank. It is a little better when using my Bluetooth Headset but is really totally useless. I usually have to take the battery out and reboot to gain control back.
I have tried
Full Wipe before each install. (cache & data)
CM11 - 27/07/14
CM11 - 26/07/14
CM11 - 25/07/14
CM11 - 08/07/14 M8
All have the same problem.
I am using CWM V6.0.4.7.
I would much rather use Cyanogenmod and am being forced to use one of the Stock ROMS OMEGA V21 which is ok but not what I am after. Is anyone else having this issue? Can I use another dialer?
Any help would be appreciated
:fingers-crossed:
Click to expand...
Click to collapse
Update
I have changed the power button so it allows me to end the call when pressed. This corrects the problem and turning the "Prevent accidental wake-up" off in the Display and Lights section in the Setting Menu. This make CM11 usable thank goodness. :good:
I had the same problem with the latest CM11 M8 nightlies and snapshot version. Also almost useless GPS.
Got suggestions like changing the proximity sensor settings and pulling apart the phone to clean the sensor.
I installed C-ROM on the recommendation of a friend and bingo problems fixed.
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...
phone: sprint sph-l720
Rooted: cf auto root
Unlocked: s4 unlocker
Problem: started after i flashed my first rom cm 11 through the installer from cynogen mod. I was un able to make calls with any sound or recieve any calls at all and could recieve texts but not send them.
Things that I have Tried: I have flashed cm 10.2, cm 12 from antares nightly, pac-rom, l720 od2 stock rooted rom 5.0.1 that has random black screen problem and the dialer keeps crashing. I have used cwm recovery and twrp from the antares thread.
my question: what is the common problem with my device that could be causing all of these same types of glitches? For this to happen across all the roms that iv flashed so far, and how can i fix it?
ps. problems occur in any number of combinations(depending on the rom) but seem to the be same basic issues ie: no audio, no wifi, cant receive texts, cant send texts or both, cant make calls or receive calls or calls made have no sound.(i am using gsm based movistar.cl network for sim) any help would be great ty.
over the moon said:
phone: sprint sph-l720
Rooted: cf auto root
Unlocked: s4 unlocker
Problem: started after i flashed my first rom cm 11 through the installer from cynogen mod. I was un able to make calls with any sound or recieve any calls at all and could recieve texts but not send them.
Things that I have Tried: I have flashed cm 10.2, cm 12 from antares nightly, pac-rom, l720 od2 stock rooted rom 5.0.1 that has random black screen problem and the dialer keeps crashing. I have used cwm recovery and twrp from the antares thread.
my question: what is the common problem with my device that could be causing all of these same types of glitches? For this to happen across all the roms that iv flashed so far, and how can i fix it?
ps. problems occur in any number of combinations(depending on the rom) but seem to the be same basic issues ie: no audio, no wifi, cant receive texts, cant send texts or both, cant make calls or receive calls or calls made have no sound.(i am using gsm based movistar.cl network for sim) any help would be great ty.
Click to expand...
Click to collapse
Have you tried any touch-wiz custom roms? My phone HATES AOKP/SP/CM dialer.apk's. It just doesn't work, plain and simple. You may be screwed forever so long as you have your current motherboard. I have tried everytime a got a radio or bootloader update, and no dice. Same thing. Happens exactly like your problem. That same motherboard just bit the dust out of the blue. Maybe the failure is related to the intolerance to the CM-family of ROMs? I don't know. I have a new one I'm just trying to remember how to root again. I will let you know if the new motherboard likes CM-based ROM's or if I'm still stuck with touch-wiz.
i have almost the same problem
I am experiencing the same problem. I can receive text and sent text messages but I can't receive calls. I can make calls but I Can not drop the call. even if I press the end, I just got stuck up on hanging up screen. then it just keeps calling. can anybody here help me how to fix this????
I am using sprint Samsung L720.
@over the moon @dece25
What ROMs and carriers have you been using? AFAIK, most if not all AOSP-based ROMs does not cater to GSM carriers out of the box - you need to replace some RIL lib files for the problems to disappear, but then it won't work with CDMA carriers. I have the libs for CM12.1 but not other ROMs...
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
This is why I always modify the stock ROM slightly or find a ROM that is slightly modified because of ISSUES ISSUES ISSUES! I understand that these people really do put a lot of time and effort into these ROM's but most of the time they have too many bugs. I am using the stock OH1 (5.01) ROM with root, hotspot hack, font changer and a icon changer and it works great!
AndyYan said:
@over the moon @dece25
What ROMs and carriers have you been using? AFAIK, most if not all AOSP-based ROMs does not cater to GSM carriers out of the box - you need to replace some RIL lib files for the problems to disappear, but then it won't work with CDMA carriers. I have the libs for CM12.1 but not other ROMs...
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Hey, i have the same problem as mention cant receive calls and i cant hangup outgoing calls. I live in Asia and im using the JDC team rom. Could you provide the RIL files for the fix?
Kzpl0x125 said:
Hey, i have the same problem as mention cant receive calls and i cant hangup outgoing calls. I live in Asia and im using the JDC team rom. Could you provide the RIL files for the fix?
Click to expand...
Click to collapse
I'll only be able to pull off the trick for ROMs that have both a CDMA version (for Sprint variant) and a GSM version (for ATT/TMo variant), so that I can compare the libs and pull out necessary ones for flashing. Also, I have only used CM12.1 to this moment.
I'll attach my fixes for CM12.1 here: http://forum.xda-developers.com/showthread.php?t=2927776 (check last page), but DO NOT flash these on any othet ROMs. This is just for when you want to try things out with CM12.1.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]