[4.4] Omni nightlies for the Oppo N1

maxwen · Jan 7, 2014

Thomaslje said:
Is there lock screen widgets or not, cant seam to find it.

Settings - security - enable widgets

Thomaslje · Jan 7, 2014

Nightly update

Hello. Can any one give me a guide on how I update to the latest nightly rom, do I just flast the new one in TWRP or di I need to completly erase all things.

Harfainx · Jan 7, 2014

Reboot to TWRP, wipe cache and Dalvik. Then flash. No full wipe needed.

I'm not using Omni now, but can't you update directly when an update is available?

Sent from my N1 using Tapatalk

Thomaslje · Jan 7, 2014

Nice

Harfainx said:
Reboot to TWRP, wipe cache and Dalvik. Then flash. No full wipe needed.

I'm not using Omni now, but can't you update directly when an update is available?

Sent from my N1 using Tapatalk

lol I can thx for that dude.

Entropy512 · Jan 8, 2014

Harfainx said:
Reboot to TWRP, wipe cache and Dalvik. Then flash. No full wipe needed.

I'm not using Omni now, but can't you update directly when an update is available?

Sent from my N1 using Tapatalk

Don't even bother wiping cache/dalvik.

Reboot to TWRP and flash - or use OpenDelta to autoupdate.

aeacus · Jan 10, 2014

Any update about the O-Click integration?

Στάλθηκε από το N1 μου χρησιμοποιώντας Tapatalk

iqbalaydrus · Jan 11, 2014

I had several restart just after 12 hours using omni. Suddenly the screen freezes, and it goes black slowly from the bottom, and it restarts. have you recognize this issue?

Sent from my N1 using Tapatalk

maxwen · Jan 11, 2014

iqbalaydrus said:
I had several restart just after 12 hours using omni. Suddenly the screen freezes, and it goes black slowly from the bottom, and it restarts. have you recognize this issue?

Sent from my N1 using Tapatalk

Provide file /proc/last_kmsg after the reboot

Sent from my N1 using Tapatalk

iqbalaydrus · Jan 11, 2014

maxwen said:
Provide file /proc/last_kmsg after the reboot

Sent from my N1 using Tapatalk

I can't seem to recreate the reboot. But it's still there, the slowly getting black screen. What should I provide if it doesn't reboot?

Sent from my N1 using Tapatalk

-edit-

The reboot happened. Here's the file https://docs.google.com/file/d/0B7FWOTw3HmTZV3hFc1Y3Z0gyMFU/edit?usp=docslist_api

Entropy512 · Jan 13, 2014

iqbalaydrus said:
I had several restart just after 12 hours using omni. Suddenly the screen freezes, and it goes black slowly from the bottom, and it restarts. have you recognize this issue?

Sent from my N1 using Tapatalk

I've seen this happen a few times, I need to put up my logs for maxwen to look at.

Happens most often for me when pulling up the AOSP keyboard in Chrome, also once in Facebook. Does not seem to occur with Hacker's Keyboard. Often causes the really slow "black refresh" without a restart.

It's probably #1 on my personal "N1 annoyances" list, I just have been too busy to look in detail at tracking it down.

BTW, Max, have you tried lalit's kk_2.7 branches of display/media/audio-caf yet? I was planning on testing them out this weekend but didn't get around to it.

iqbalaydrus · Jan 14, 2014

Entropy512 said:
I've seen this happen a few times, I need to put up my logs for maxwen to look at.

Happens most often for me when pulling up the AOSP keyboard in Chrome, also once in Facebook. Does not seem to occur with Hacker's Keyboard. Often causes the really slow "black refresh" without a restart.

It's probably #1 on my personal "N1 annoyances" list, I just have been too busy to look in detail at tracking it down.

BTW, Max, have you tried lalit's kk_2.7 branches of display/media/audio-caf yet? I was planning on testing them out this weekend but didn't get around to it.

I'm glad to hear that I'm not the only one with the issue. The maintainer on top of that. I'm too in love with omni to switch to other ROMs. I hope this issue to quickly resolved.

Sent from my N1 using Tapatalk

anders3408 · Jan 19, 2014

Entropy512 said:
I've seen this happen a few times, I need to put up my logs for maxwen to look at.

Happens most often for me when pulling up the AOSP keyboard in Chrome, also once in Facebook. Does not seem to occur with Hacker's Keyboard. Often causes the really slow "black refresh" without a restart.

It's probably #1 on my personal "N1 annoyances" list, I just have been too busy to look in detail at tracking it down.

BTW, Max, have you tried lalit's kk_2.7 branches of display/media/audio-caf yet? I was planning on testing them out this weekend but didn't get around to it.

Sounds very similar to the blue screen issue on find5 when a MDP underrun occurs. Hmm interesting.

Sent from my N1 using xda app-developers app

maxwen · Jan 19, 2014

anders3408 said:
Sounds very similar to the blue screen issue on find5 when a MDP underrun occurs. Hmm interesting.

Sent from my N1 using xda app-developers app

BTW: I never had this so far which doesnt make it better

Dont use chrome (dolphin user) but always AOSP keyboard

Also - I have enabled "force GPU rendering" in developer settings
would help if someone who faces the issue tries if this makes
any diff at all.

asbkar · Jan 19, 2014

maxwen said:
BTW: I never had this so far which doesnt make it better
Dont use chrome (dolphin user) but always AOSP keyboard

Also - I have enabled "force GPU rendering" in developer settings
would help if someone who faces the issue tries if this makes
any diff at all.

"Force GPU rendering" does not seem to help, but "Disable HW Overlays" do. Just gave it a few minutes testing after changing it, but the behaviour in chrome seems better... Will report back tomorrow.

Entropy512 · Jan 20, 2014

asbkar said:
"Force GPU rendering" does not seem to help, but "Disable HW Overlays" do. Just gave it a few minutes testing after changing it, but the behaviour in chrome seems better... Will report back tomorrow.

Points even more towards a hwcomposer issue.

I may post up a test build using our "new" CAF branches to see if it helps. It seems to on my device, but even an "old" build seemed fine recently.

Entropy512 · Jan 20, 2014

anders3408 said:
Sounds very similar to the blue screen issue on find5 when a MDP underrun occurs. Hmm interesting.

Sent from my N1 using xda app-developers app

Lots of IOMMU page faults?

anders3408 · Jan 20, 2014

Entropy512 said:
Lots of IOMMU page faults?

Yep. Also tried latest display-caf and several other changes without luck. Aldo seems very random and only some people get the issue.

Sent from my N1 using xda app-developers app

Entropy512 · Jan 20, 2014

anders3408 said:
Yep. Also tried latest display-caf and several other changes without luck. Aldo seems very random and only some people get the issue.

Sent from my N1 using xda app-developers app

Interesting. I chatted with maxwen briefly and it sounded like the "bluescreen" issues were different (no IOMMU page faults, but MDP underruns).

Does "disable HW overlays" also reduce the underruns? (I'm guessing that it might considering how disable HW overlays works)

Omni's qcom-4.4_kk2.7 branches of audio/media/display-caf seem to produce less "slow black refresh" issues on the N1. Switching over audio requires some device tree changes (see open n1 changes on omni gerrit)

Odd question - when I set this up in devDB there was an entry for "source" that I pointed to omnirom's github... Does that actually show up anywhere? I probably need to add clearer source links.

(This is my first attempt to use devDB)

asbkar · Jan 20, 2014

Meh, "Disable HW overlay" did not work. Couple of reboots, and a black slow wipe + reboot now.
last_kmsg attached.

anders3408 · Jan 20, 2014

Entropy512 said:
Interesting. I chatted with maxwen briefly and it sounded like the "bluescreen" issues were different (no IOMMU page faults, but MDP underruns).

Does "disable HW overlays" also reduce the underruns? (I'm guessing that it might considering how disable HW overlays works)

Omni's qcom-4.4_kk2.7 branches of audio/media/display-caf seem to produce less "slow black refresh" issues on the N1. Switching over audio requires some device tree changes (see open n1 changes on omni gerrit)

Odd question - when I set this up in devDB there was an entry for "source" that I pointed to omnirom's github... Does that actually show up anywhere? I probably need to add clearer source links. (This is my first attempt to use devDB)

Well normally its an underrun yes, but I've tried changing back one line that oppo did mpd4_something which had a comment line saying fix blue or black screen issue iirc. That did show the blue screen/underrun issue still as before but now it also did show a lot iommu page faults. The interesting thing is, oppo has never had that issue, or so they say. And mainly its changes that qcom suggested. I took a chat with oppo about that issue we had/have on find5 to see if it could show some light on the issue.

Sent from my N1 using xda app-developers app

[4.4] Omni nightlies for the Oppo N1

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Member

Senior Recognized Developer

Senior Recognized Developer

Inactive Recognized Developer

Senior Recognized Developer

Member

Attachments

Inactive Recognized Developer

Similar threads

Top Liked Posts