Search results

I opened my phone again and used a multimeter. The black and white antenna connectors are good and the speaker/antenna assembly looks good too, what could be the issue?

Hi everyone, I recently bought a LG G2 D802 16GB from Amazon. Everything is working good, I only have one huge issue: the network... Every time the phone connects to 3G, it stays strong for a few minutes then the signal quality goes down until it disconnects and falls back to EDGE, which is...

Hey everyone, I cracked my 3.5 years old screen just yesterday. The phone is still fully functional, but I bought a LG G2 as a replacement (I was looking for a <200$ phone with a good camera that is fully supported by CyanogenMod). It means that the Note will not be my daily driver anymore...

Just wondering if anyone has managed to connect to a BLE 4.0 device with this ROM?

More impressions after a few days of usage: random slowdowns are very seldom compared to CM12.1, standby time is muuuuuch better than before, and video recording seems to be working properly. It's very good!

Looks neat! I will definitely use this in the next release. thanks.

I finally switched over to Marshmallow and I must say my phone feels slightly less **** than before. The only real issues are the keyboard feeling sluggish compared to CM12.1+war, and the ever lasting tearing issue with gralloc. Great release, thanks bauner.

War r3 works just fine for me with latest NightOwl CM12.1. 600h uptime with the last one! Then I had to reboot. No ETAs for a Marshmallow build because of upcoming exams and then I'm going to San Francisco for 7 months. :D:D

Thanks bauner however I'm sad about my 300h+ uptime

bauner I'm trying to bring up War Kernel for this ROM. It bootloops and reboots back to the recovery each time I try. I merged the Mali API bump and MMC block minor patches, is there anything else I'm missing here?

Announcing War Kernel r3 Changes over r2 : - Revert to 57Hz panel. I figured out it doesn't play well with our current HWC. Once this is fixed I might bring back panel OC. - Built with GCC 5.3 - 50mV CPU undervolt - Fixed Mali resume step Download : * war_kernel_r3_cm121.zip for NightOwl...

There's no such thing as TW 4.3.

BT4 support might be already enabled in NightOwl, see this thread: http://forum.xda-developers.com/galaxy-s2/help/sgs2-bcm4330-bluetooth-4-0-t1565551/post45493157#post45493157

Just built War r3, testing it. Will be released in the next few days, Marshmallow build will follow.

Soon :o

Remove ABS tweak and SSCoolingEngine from your phone, forever

What are you implying here? lol

Got a spontaneous reboot tonight with latest 20151211. Screen was turned off when it happened. Using the stock kernel. SIM card wasn't recognized after the phone rebooted, so I did it again manually and it was fine. Maybe a hardware issue? :( Got a new Anker battery with a dark theme (for OLED...

Hey bauner, could you rebuild this ROM with the latest security patches merged? Thanks :)

Raw/TW runs on Touchwiz 4.1.2 and War runs on CM12.1.

Did you know that the Oculus Rift DK2 was using a Galaxy Note 3 panel? Because it's VR they need high framerates. Turns out they are using panels overclocked to 75Hz. Stock Galaxy Note 3 runs at 60Hz. I am developing a kernel for the Galaxy Note GT-N7000, and successfully overclocked our panel...

It's your choice to destroy your flash storage within months, but I definitely won't implement it in this kernel.

You should probably check for wakelocks because it is really bad indeed

stelistcristi I have been trying to make Nameless HWC work on our device (again). JB HWC is out of the question since it implements the 0.3 API which is not supported since Android 4.3. - Pushed hw/hwcomposer.exynos4.so, libcec.so, libddc.so, libedid.so, libExynosHWCService.so...

Keep in mind that r3p1 drivers have never been shipped in any 4210 device. JB was using r2p4 ;) pegasus-m400 platform is meant for 4x12 devices, otherwise it's orion-m400. In r2p4 the lowest step (160MHz) is set on resume.

bauner I just realized the 267MHz step in r3p2 drivers is actually overvolted to 1050mV. r2p4 for reference. So it's already fixed in War r2.

Is it happening with War r1? Also do you know your phone's voltage group? EDIT: bauner I spotted a typo in the Mali platform file exynos4_pmm.c that sets the GPU at 200MHz with a very low voltage when the clocks are enabled (when it goes out of sleep I guess). That could be the cause of some...

No idea, but you can always try and flash the original kernel back if anything goes wrong

So, can anyone report on the battery life for War r2?

Congrats on your release! :D

Just for the kicks: it's possible to boot our phone with a reduced screen resolution. The touchscreen doesn't match so it's completely useless. 1280x720 (S3/Note2) 800x480 (S2)

Good job :) I wouldn't be surprised if this was a gralloc issue undercovered by this change.

Oh that's a weird error you have there. Just look at Kbuild, there's a check for Mali license files. For some reason the GPL file drivers/gpu/mali400/r3p2/mali/linux/license/gpl/mali_kernel_license.h is not found so that triggers it. You can remove the check safely I guess. Have you modified...

I don't understand your question

Just use Raw TW. I don't plan to support Touchwiz ROMs anymore.

Announcing War Kernel r2 Changes over r1 : - 13-step cpufreq for better scaling - Switch to interactive cpufreq governor from 3.4-marshmallow, as recommended by Android. Snappier. - 3-step DVFS for Mali: 160/200/267MHz instead of 134/267. UI and gaming are much smoother while limiting power...

War Kernel r2 will be released soon, bringing a snappier and smoother experience. Battery life should be equivalent or slightly better. I'm not sure if it's worth releasing a Mali r4p0 test version considering there are some obvious bugs with these drivers :/ I will replace my SSD for...

I want to use closed-source apps as little as possible

Battery life on my phone was really bad these days. Wakelock detector showed me that the stock Messaging app was keeping my phone awake all the time... I disabled "Automatically retrieve messages" to get rid of this wakelock. It's caused by a MMS waiting to be retrieved... I believe my APNs are...

Looks like a problem with libMali, you might want to apply this patch to add r4p0 drivers (blobs here)

I just reuploaded War r1 with the camera recording fix

It's ok here when the conversation related to the SMS i'm just receiving is not open in the app, if the app is not open or if the screen is turned off.

Really cool! :good: I tested the Messenger (from Google) and Hangouts apps, same issue

Something is really annoying with the default MMS app: every time I receive a message while the conversation is open, there is no notification or vibration. So I find myself missing a lot of messages this way, because I'm not always looking at the screen and it turns off just after that. Nothing...

I am testing Mali r4p0 drivers from HardKernel. It works and looks a little bit smoother to me, however Epic Citadel has a slightly lower benchmark score and I am observing very rare graphical glitches. I will release a test version soon. This will be a blind test: two versions, r3p2 and r4p0...

Some changes to the defconfig would do the trick ;)

KalZakath you're such in a hurry :D I don't plan to merge TWRP until it is available in a next version of NightOwl. Because it is not bugfree yet. And I don't see what's wrong with the current version lol Camera recording fix will be merged pretty soon.

Can anyone else confirm?

Thanks bauner Forgot to say that this release is not compatible with device encryption. I do not plan to merge it since I won't be able to test it.

Should be good now