Database Users

[Noob Time] Why FLash To CM 10.1 ?

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

[Q] Dialer Issues / Crashes

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] [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***

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...

Custom roms problem

Hello,
i tried AICP, aosp extended, aquarios rom and with every rom i have same problem.
The problem is that every rom stutters and animations lag,they are not smooth. Also when im scrolling between home pages it also lags,simply all animations stutter.I see that all people are having great time on these roms and i think im only one who has such problem. Every time i tried clean install ,but problem persists. I have H870 model.
The only rom that is working good is fulmics for me,it is really smooth but i prefer pure android,like aosp extended,and cant use it. What can i do guys about this? thanks

It's not a custom ROM problem. Have you tried this :
https://forum.xda-developers.com/showpost.php?p=71953461&postcount=22
Or upgrading the adreno drivers? (see the thread about new drivers)

Thanks for your reply. The rom itself has already latest gpu drivers (aosp extended rom),but i installed drivers manually and problem is still there. I realised when i change governor in kernel adiutor (for example from interactive to sched) phone works smooth next 15-20 minutes and then stutter starts again.

OK, good. In the thread mentioned above, there are many people who have no lag. Have you tried my other suggestion? Worked for me and many others.

I will flash later aosp extended and try with force gpu,thanks

Reflash Magisk, clear cache. Clear Dalvik-cache

You mean to first remove magisk with its uninstaller,flash it again and then clear cache/dalvik cache?

MK2000 Kernel crashing?

I noticed the official MK2000 Kernel by @askermk2000 is closed, so I hope its OK to discuss here. There's a CLANG compiler edition of them floating around somewhere that actually is a great deal better (faster/smoother) that I don't see being mentioned around here much.
Only issue is that I've noticed my phone started rebooting randomly with it. I've suspected a hardware issue for a while so I picked up an additional H918, installed a different rom to test performance, and am now finding that it, too, occasionally reboots when coming out of sleep.
The only thing these two handsets have in common is that they are both H918 variants and are both running the latest 2.2 CLANG compiled edition of the MK2000 kernel. They are otherwise running different oreo firmwares (one stock, one Alpha Omega) and are both started fresh (no restore). I have to believe something is up with that kernel, but as we have a lack of Oreo kernels with Kcal currently, I'm hesitant to give it up. Has anyone had a similar experience, especially with the H918 variant?
Seems like a Kernel panic- the phone doesn't completely reboot (doesn't show the yellow warning screen) but starts back up from the T-mobile (in my case) loading screen.

Looks like you're getting soft reboots for some reason if it's starting at the boot animation screen (well, not much moving on the pink T-Mobile screen).
I haven't had such issues so far on my H918 running a data-only SIM card on Alpha Omega Oreo, using the latest mk2000 2.2-based kernel uploaded by Phoenix591 over here (no idea why there's also an LS997 version of the kernel as that variant's stock Oreo is unrootable) on Aug. 6. Are you using that exact same kernel?

C D said:
Looks like you're getting soft reboots for some reason if it's starting at the boot animation screen (well, not much moving on the pink T-Mobile screen).
I haven't had such issues so far on my H918 running a data-only SIM card on Alpha Omega Oreo, using the latest mk2000 2.2-based kernel uploaded by Phoenix591 over here (no idea why there's also an LS997 version of the kernel as that variant's stock Oreo is unrootable) on Aug. 6. Are you using that exact same kernel?
Click to expand...
Click to collapse
I've been using the CLANG editions. I had the regular 2.2 previously, but someone recommended trying the Clang ones as they are superior in performance. Device didn't heat up, seemed pretty responsive and snappy, but man would it just **** the bed sometimes when we needed it most (usually happened upon wake up from sleep- imagine wanting to wake up to see the notification you just got and suddenly having the device reboot).
Good news is that I dirty reflashed AO rom and this time chose to leave stock Kernel intact and did NOT flash MK kernel on top of it, and now it seems to have eliminated the rebooting. It was definitely the kernel. I lose some things like KCAL, so I hope screen retention doesn't start happening on this model, but otherwise the phone seems much better now!

Screen retention will show up sooner or later, especially if you move between very light and very dark backgrounds. Once you see it, then you may want to look into some screen filter apps (non-rooted users do this, and you'll need to make sure that the app has an 'enable on boot/reboot' function) or try some of the other mk2000 Oreo kernel versions. All of askermk2000's kernels, including older versions, are still available over here in lots of subfolders.