Ael kernel - Galaxy Note 4 Q&A, Help & Troubleshooting

Just a question. The sview hack doesn't work yet on the ael kernel v8. However it works on startup while is booting up!?
That is to say, I can see the bit animation on full screen when open, but when closed a smaller boot animation pops up through the sview screen.
So it kinda works but not when the phone is on!?
Sent from my echoepopped note 4

Related

Strange ICS bug

I flashed the stock ICS rom with CF root kernel the day they came out and everything went fine. However, there is something strange that happened to me twice so far. At random times and while the phone was locked (lockscreen) when I tried to unlock it and use it the screen goes crazy and it becomes blurry with numbers and lines and colors blending like crazy (reminds me of the matrix film with the numbers running down). This happened to me twice and only with the ICS rom and it goes away with a hard reset.
Has anyone else experienced this?
Hard reset?? on ICS?? if im not mistaken thats factory reset??
Switch Off
Vrayhem said:
I flashed the stock ICS rom with CF root kernel the day they came out and everything went fine. However, there is something strange that happened to me twice so far. At random times and while the phone was locked (lockscreen) when I tried to unlock it and use it the screen goes crazy and it becomes blurry with numbers and lines and colors blending like crazy (reminds me of the matrix film with the numbers running down). This happened to me twice and only with the ICS rom and it goes away with a hard reset.
Has anyone else experienced this?
Click to expand...
Click to collapse
Switch Off CRT Animation, in custom rom it is built-in, no idea for stock though.
Yes. I've experienced this too. Just two times in about two weeks, nothing to worry about, though. Pressed the on/off button and the glitch went away. Seems to be a problem with the graphic driver. Or maybe just a Touchwiz launcher problem on ICS, don't really know.
I'm on a unrooted ICS (updated via Kies) Note.
G
Same thing happened to me once while browsing on the default browser and rotated screen from portrait to landscape : colored lines salad, not responding to middle button or touch buttons. After turning screen off then on everything was fine again.
Stock LPY rooted, flashed with Mobile Odin Pro.
Same happened to me. Default unrooted ICS, Kies-updated.
So it appears that this occurs whether someone has rooted their device or not. Hopefully Samsung will publish a stable ICS built to end this barrage of issues with the new Firmware experienced by many. It feels like we are Beta testers on this device.

[Q] First touch problem

Hello,
I have this really annoying problem with my phone: After power buton is pressed and phone wakes up, very often (not allways, but I was unable to track conditions) first touch on display - no matter where - controls the status bar (pull down or brightness adjust). So if I want to unlock my phone, I have to do swipe on lockscreen two, sometimes three (because of the delay) times before phone actually unlocks.
I tried to disable HALO, entire exposed framework, lockscreen notifications (built-in in my rom) -> none of this worked. It does this even when lockscreen is disabled.
I don't use doubletap2wake or swipe2wake
Nexus 4:
6.2 Nexus5Experience ROM with stock kernel, without LTE, no oc (link)
Has anyone experienced similar behaviour? I don't know where else should I look.
Thanks in advance
zipp
P.S.: I would have asked in rom thread directly, but I don't have permision to post there.
Which kernel are you using?
Unleashed by my Nexus 4
I'm using the same ROM currently and have the same issue.
I use stock rom's kernel. I tried franco and hellscore, but I lost root with them, so I reverted back to stock rom's kernel.
Do you think it might be kernel connected?

Cloudy G3 Dalvik to ART switch then Black screen!

Have been running Cloudy G3 for a while on my D800 with no problems. Just last night I switched to ART instead of Dalvik, because i saw that the 1.2 version of CLoudyG3 supported it. Immediately my phone went black and has been unresponsive. l cannot even get it the LG logo to pop up. It came up once, but never again. its as if it is completely lifeless... Only mod i was running was Exposed mainly for the APM and Lockscreen flashlight.
Happened to my g3 just now, i almost had a heart attack. Earlier today i switched to ART. What i did was take off the battery and put it back and it started just fine. I wonder if ART was the problem, before it became unresponsive and screen turned off i was playong with zooper widget. I hope someone.can give us an answer to why this happened. Oh im using stock im not rooted jtlyk.
antiparadigm said:
Have been running Cloudy G3 for a while on my D800 with no problems. Just last night I switched to ART instead of Dalvik, because i saw that the 1.2 version of CLoudyG3 supported it. Immediately my phone went black and has been unresponsive. l cannot even get it the LG logo to pop up. It came up once, but never again. its as if it is completely lifeless... Only mod i was running was Exposed mainly for the APM and Lockscreen flashlight.
Click to expand...
Click to collapse

[DISCUSSION] Problems & Bugs on stock CM11S

I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.
ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk
ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.
ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app
SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.
magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.
i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.
M9 just came out. Only in a matter of time we get the ota for the next update
jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app

AOSP Oreo s-view cover

Hello, I'm a fresh member of this forum and recently upgraded my Galaxy Samsung S4 (i9505) from stock to AOSP Oreo. After the upgrade everything worked more or less as expected, the ROM is stable enough for daily use.
Unfortunately the S-view is not working like expected, if I open the (original) Samsung s-view cover the screen lights up and if I close the cover the screen goes off, but there is no clock in the display as before. Also with an incoming phone call the screen doesn't show up, or I can pick up the call by wiping over the cover window.
I installed the files below:
Unofficial TWRP recovery.img
JDCTeam-8.1.0-20171209-BETA.zip
open_gapps-arm-8.1-nano-20180119-UNOFFICIAL.zip
Kernel-B--B-PWR-CORE-AOSP-O-v3.2.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Also, I tried the 'S View Lite' app from play store. After closing the cover the screen is shown for a few milliseconds,but no sulution there. I also repeated the installation a few times (thanks for the nice youtube video's) to be sure I made no mistakes.
Because I miss the S-view functionality like it worked before, I post this question on the Q&A (my question on jdcteam-android-source-project-oreo-t3685231 did not get much response). Maybe someone can help me to get it going, tell me if it's working on her/his dvice or tell me I have to live with it like it is ?
there is no lineageOS rom with the Sview.
the Sview is based only on TW rom, so nothing newer more than a 5.0.1 TW rom.
and all Sview apps don't work correctly.
If you want S View, go back to TouchWiz.
If it's ever going to work on AOSP ROMs, it only does to lock the screen instead.
Sent from my Redmi Note 4 using XDA Labs

Categories

Resources