yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] severin333:
[MENTION=4683552]maxwen[/MENTION] : I get the exact same glitches using eagleeyetom Build with updated video blobs (posted here). For me, it happened on BoomBeach, but also on some websites while browsing (I think it was .gif or .gifv which didn"t display properly)

Usually, scrolling make the glitches go away/come back so issue might be related... If you ask, I might test it again and provide logs if some are useful, but doing clean flash again and again is not really fun...
[ONE Original Android Development] maxwen:
Ok - I see. If you now could come with a x-step description so that I can test it without thinking to much :)
[ONE Original Android Development] :
Well, i have no idea what kind of description you're asking. But these glitches just appear mainly on menus or pop up options where there is text involved saying 'SHOOT' 'ATTACK' like this lol :p. Sorry, but i can describe like this only as i have no knowledge about the development.

But if want me to do some research, please tell me how and i will do it.

Thnanks
[ONE Original Android Development] maxwen:
Ideally a description like

1) install app x

2) in app x select y

3) a.s.o :)
[ONE Original Android Development] :
Can i do Record screen?

Please let me know as i will have to install one of those rom and then record.

Or if anyone on the thread reading this can reproduce that glitch
[ONE Original Android Development] maxwen:
Screen recording would be fine too if its easier then to describe in words :)
[ONE Original Android Development] joefso:
does omni also use find7HAL ? ( as it uses its device tree ) ?
[ONE Original Android Development] :
Flashed one of those Rom and installed the app.

As you can see in the video, whenever the menu is pressed there are photos that shows scratching effect, text is missing,

here's the video

https://youtu.be/zjFqDraQNMY

And thank you for taking this bug into consideration :)
[ONE Original Android Development] ogrillion:
Basically the graphic glitch happens in the game clash of clans and I read boom boom beach but I don't play that game.

Its in most of the menus. Like in the video above the window he opens - that's the defense log showing people who attacked you. The icons on the bottom that are gold purple and black all should have numbers but its glitched. Also when you scroll sometimes the numbers pop in.

And what's odd is the next tab which show bases you attacked will look completely normal.

Also when in the various building menus you will see distorted graphics.

Thanks for taking an interest in this. Generally the other devs don't care and it's one reason I love omni since it doesn't suffer the graphics issues.

CM seems to not care or blame it on the game. But when it's only happening on the OnePlus and only on cm12.1 how can you blame it on a game

Edit: also if its helpful this glitch was introduced around April 24th nightly of cm12.1. The last nightly that had no graphic issues for me was 4-23-15.
[ONE Original Android Development] maxwen:
Well on the 23.04 was this graphics blob update :) https://github.com/TheMuppets/propr...mmit/f1bef88be927ee6a146cc2242caa6e4ce8f3bb44
[ONE Original Android Development] ogrillion:
I like that it took you hardly anytime to find that.

I searched all through cm gerrit looking for changes that would cause the issue. I was planning on building cm minus whatever commit but couldn't find it. Never thought to check where you did - which makes total sense.
[ONE Original Android Development] maxwen:
What HAL?
[ONE Original Android Development] 69gm:
Well no wonder! I was looking here!

https://plus.google.com/u/0/+OmniromOrg/posts

Thanks guys!!! :good::highfive:
[ONE Original Android Development] maxwen:
well - it could be just a coincidence or even a side-effect of this with another change

such things are always hard to track-down.

Going to test our next blob update upfront with you to test :)
[ONE Original Android Development] Renosh:
Was a bit busy but I see you even got a video. I'll forward to some devs and see if they're willing to build minus this blob to test for the issue. Thanks maxwen you're awesome
[ONE Original Android Development] joefso:
Camera HAL
[ONE Original Android Development] maxwen:
[MENTION=4366455]rockhardy[/MENTION]
[MENTION=1019852]ogrillion[/MENTION]
[MENTION=5972963]Renosh[/MENTION]

if you would like to help

This is a flashable zip of a planned graphics blob update

https://drive.google.com/file/d/0B4vRAhHheUkxS0NWNmRxbHd0cVE/view?usp=sharing

Create nandroid backup FIRST and then flash this in recovery

Then try the games that caused issues.

If you then get the glitch - ok it was the blobs - restore your backup and we need to revisit this blob update.

if not - we are fine with the next blob update using this :)

---------- Post added at 11:38 PM ---------- Previous post was at 11:38 PM ----------

yes but not latest version
[ONE Original Android Development] ogrillion:
Getting an error that the zip is for a find7 and my device is a A0001

Sure I can change something in the script but not at a computer
[ONE Original Android Development] maxwen:
LOL - ok sorry - forgot that :)

will create a new one :)
[ONE Original Android Development] scanno:
Look at the latest homebuild. It has the updated display blobs

Verstuurd vanaf mijn TF300T met Tapatalk
[ONE Original Android Development] maxwen:
Yeah I know but switching between nightlies and homebuild is a PITA

just to test that - therefore this.

Zip updated now with fixed device check
[ONE Original Android Development] ogrillion:
There a new link or the original one?
[ONE Original Android Development] maxwen:
time so sleep as it seems :)

https://drive.google.com/file/d/0B4vRAhHheUkxdWY3VGc3Z1A4N0k/view?usp=sharing
[ONE Original Android Development] ogrillion:
Haha NP was afraid I missed it or something stupid on my end.

So downloaded and flashed - and I do now have the graphic glitches now.

I feel better now that its been narrowed down a bit to what's causing it. But it also sucks because I am sure those updated blobs have advantages no?

Thanks for taking the time to investigate !
[ONE Original Android Development] maxwen:
Thanks for testing but this is bad news for us also cause we also need to find a solution

if we really need to update the blobs at some point.

So I might come back to you for another test round :)
[ONE Original Android Development] ogrillion:
Of course anything I can do to help. Least I can do for all the time you put in.
[ONE Original Android Development] :
Sorry, was sleeping. It's really good that you figured out what is causing the bug. Thanks again for this.

I will help in testing upcoming builds :)

So, how do we suppose to inform other developers about it? because last time i did that and my post ended up nowhere (Deleted).
[ONE Original Android Development] 69gm:
Just wanted to report that the new nightly (6/27) is up and running well!

[MENTION=4683552]maxwen[/MENTION], this one is supposed to fix nightly OTA, correct?

Thanks again for the great work!
[ONE Original Android Development] maxwen:
We will know tomorrow
[ONE Original Android Development] maxwen:
do you actually know if the same problem exists on oxygenos?
[ONE Original Android Development] ogrillion:
No, no graphical glitches on oxygenos, but they are still running Android 5.0.2 or whatever -not sure if that matters for this issue.
[ONE Original Android Development] maxwen:
But their graphic blobs are way newer then what we have so lets try them :)

https://drive.google.com/file/d/0B4vRAhHheUkxV09mUEd1czUzQ2s/view?usp=sharing

---------- Post added at 11:29 PM ---------- Previous post was at 11:15 PM ----------

Why should we?
[ONE Original Android Development] ogrillion:
Flashed fine and just to confirm no graphical issues at all.

Good idea! Hopefully when oxygen os 5.1.1 comes out it will use different blobs from cyanogen
[ONE Original Android Development] maxwen:
thanks for testing
[ONE Original Android Development] 69gm:
Is this something that will be pushed into the next nightly?
[ONE Original Android Development] Maarren:
Not that benchmarks matter,but I have something strange when using one. After I run antutu the phone gets stuck at running with 1 core only. 25-6 nightly. All 4 cores available after a reboot.
[ONE Original Android Development] schaggo:
I'm guessing [MENTION=4683552]maxwen[/MENTION] answer: Dont run antutu benchmark then, if it f**** up your phone ?
[ONE Original Android Development] Maarren:
Agreed, but then again I guess it should not be possible for any app to do this. So therefore I at least mentioned it.
[ONE Original Android Development] maxwen:
dmesg please - but pretty sure thermal throttle

And BTW how you tell number of cures?
[ONE Original Android Development] Maarren:
http://pastebin.com/CniGbaBg

I tell by looking at the performance tab of omnirom. It is always jumping around with the number of cores. But after this, there only stays 1 core online. Also multitasking is/stays slow afterwards.
[ONE Original Android Development] maxwen:
well - in this log sensor temp is still 70deg which will not clear core limits

(69 would ☺)
[ONE Original Android Development] Maarren:
In other words I should retest and wait longer.
[ONE Original Android Development] maxwen:
you can check sensor value and cores also when you enable "Show CPU info" in dev settings
[ONE Original Android Development] Maarren:
Well thats a bit strange the reading is already cooled down to 40 degrees, but still only 1 core. (Almost if the dmesg value has an offset or something, but I dont really know about these things) See attached screenshot.

It is not like the phone has been very hot. I dont even need to finish the benchmark. If I abort half way past the first run it is already running on 1 core).
[ONE Original Android Development] maxwen:
then again full log please
[ONE Original Android Development] Maarren:
See attachments ,log and screenshot were made almost simultaneously.

But I dont want to waste your time, maybe first somebody else can test and confirm. (To make sure that its not something screwed up on only my phone)
[ONE Original Android Development] maxwen:
nah - you really found something :)
[ONE Original Android Development] chrcol:
omnirom lollipop feels like a downgrade to me.

I cannot change wifi region

I cannot set 2g as preferable network

settings in general seems dumbed down, is less to play with. I was able to fine tune the auto brightness on omnirom kitkat.

Is there any way t overcome these restrictions in particular wifi region setting?
[ONE Original Android Development] chrcol:
wow what a childish useless post.

if you dont know the answers to my questions then dont post, not some sick belief that people cannot provide negative feedback.

this applies to you two also

abhibnl , AdrianM
[ONE Original Android Development] maxwen:
Yep - you definitely need a break and have more fun in life :)
[ONE Original Android Development] abhibnl:
Well i would simply ignore your post and like maxwen said, you definitely need a break buddy!

Sent from OnePlus One
[ONE Original Android Development] musklor:
Cyandelta my poor connection loves you :)
[ONE Original Android Development] Maarren:
I see your thermal bugfixes on gerrit, thanks that your working on it.

Sorry if below is a dumb question, but I'm curious.

Why is this something which you must/can work on? I would expect this is something the manufacturer Qualcomm/OPO makes/tests and then it is not touched ever again.

In other words if this eventually is merged, am I at risk of frying my phone if it there still is a bug?
[ONE Original Android Development] taufiqs:
then you should downgrade to kitkat. Other lollipop rom also cant fulfill your request.
[ONE Original Android Development] maxwen:
But you know that you don't need something with "cyan" to get delta updates? :)

---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------

You flashed a custom ROM

That means whatever happens is your fault :)
[ONE Original Android Development] musklor:
Pfff sorry it's opendelta. Not cyandelta...

[emoji42]
[ONE Original Android Development] tmotard:
I'm using this great ROM for a while now. Got one problem.

After a while (once a day) when switching from WiFi to 4g, a loose the connexion from gsm/3/4g. OK in WiFi but have to reboot to have operator network connexion.

Which logs must I provide in this case ?

Thanks a lot.
[ONE Original Android Development] tmotard:
Since several days the file as a size of 0b ?
[ONE Original Android Development] ogrillion:
Just a heads up [MENTION=310776]maxwell[/MENTION] I been trying the latest cm nightly and random ROMs built with it. Seems the graphic issue with clash of clans is fixed.

The game itself updated, so I think that is why its fixed. So maybe there's still an issue with the drivers? but now I lost my way to test

Just seems odd to me that the OnePlus was the only device with issues with that game, reason I didn't want to blame it on the game.
[ONE Original Android Development] anandbibek:
The graphic glitch was present in many AOSP and other OEM ROMs like HTC, Samsung official devices. It was certainly a game bug. Nothing to do with OnePlus or Cyanogenmod.

Latest update of game fixed it.
[ONE Original Android Development] ogrillion:
Idk my wife has a nexus 5 and running 5.1.1 and no graphic bug at all. This was prior to the update.

And any google search I did for the glitch resulted in oneplus one users complaining.

I tend to think you are correct since the game updated and now its fixed, but I don't fully agree with you [emoji3]
[ONE Original Android Development] Maarren:
In recent weeks I now have had 3 times that the systems does freeze. Phone does not respond to buttons and does not turn on anymore and I have to force a reboot. Last time was last night after I heard a notification of an incoming email and wanted to check.

Any suggestions how I can make a useful log or something in this case?
[ONE Original Android Development] scanno:
Perhaps /proc/last_kmsg could reveal something.
[ONE Original Android Development] :
I never experienced the graphic bug in CoC while running Omni, with all other rooms I did have. Weird though.
[ONE Original Android Development] tmotard:
Got a reboot this morning. here some logs, if that could help...
[ONE Original Android Development] sax0406:
The phone gets hot on Omni, even on slight usage. Haven't had this this on other ROMs. Is this normal?
[ONE Original Android Development] maxwen:
Enable CPU overlay in dev settings and check if what you do is really light usage
[ONE Original Android Development] Maarren:
For me the file looks quite unreadable. But here it is.
[ONE Original Android Development] webore:
No new builds .

it seems that there's no space left on the build server.

please fix it .
[ONE Original Android Development] 69gm:
New build is up! Seems they fixed the issue.
[ONE Original Android Development] aosp:
[MENTION=591147]Entropy512[/MENTION] [MENTION=4683552]maxwen[/MENTION] [MENTION=5965253]samstone86[/MENTION] [MENTION=905572]scanno[/MENTION]

Have you guys seen the changes made by [MENTION=4800121]Sultanxda[/MENTION]

http://xdaforums.com/showthread.php?t=3120259

[ROM+KERNEL][5.1.1] Unofficial CyanogenMod 12.1 with CAF 3.4.0 kernel [July 4, 2015]

https://github.com/sultanxda/android_device_oppo_find7op/commits/android-5.1

https://github.com/sultanxda/android_kernel_oneplus_msm8974/commits/android-5.1

https://github.com/sultanxda/proprietary_vendor_oppo/commits/android-5.1

https://github.com/sultanxda/android_kernel_oneplus_msm8974/commits/android-5.1
[ONE Original Android Development] maxwen:
yes - and whats the point?
[ONE Original Android Development] aosp:
Possible fixes for the touchscreen not responding?
[ONE Original Android Development] maxwen:
you have the problem on opo?
[ONE Original Android Development] aosp:
Yes but I couldn't generate a bugreport with the keycodes or by adding the bugreport shortcut to the power menu both seem to be borked on opo :/ I can flash back if you got another working approach to grab some bugreport logs for you?
[ONE Original Android Development] :
While running Omni, this is a first. I really haven't read anyone with touchscreen issues on the omni thread.
[ONE Original Android Development] aosp:
http://xdaforums.com/showthread.php?p=61705959

[5.1.x]Omni nightlies for Find 7a/7s

To those with touchscreen issues (not responding after resume) - I will upload a test kernel later. Only people who know how to flash kernel only should try this please :)
[ONE Original Android Development] :
I don't think that's our device, anyway, if you say you are experiencing it I won't doubt you.

Hopefully maxwen can give you a hand and figure it out.
[ONE Original Android Development] fermasia:
As stated, this is not OPO but Find 7.
[ONE Original Android Development] aosp:
You do know that both the find7 and the find7op aka opo aka bacon aka 1+1 aka oneplusone aka a0001 share the below sources right?

https://github.com/omnirom/android_device_oppo_msm8974-common/commits/android-5.1

https://github.com/omnirom/android_kernel_oppo_msm8974/commits/android-5.1
[ONE Original Android Development] maxwen:
yes - the driver code is all the same just the TS firmware is different

Therefore I was asking if some 1+1 users see the same issues.

Regarding the issue in general - there is not really a way to fix this

since none of the maintainers see the issue and we wont do any

blind-maybe-fixes "just for fun" :)

Someone doing his own kernel builds could jump in here and try the

different "versions" of that TS driver (you can choose between Oppo, OxygenOS, CM, ...)

all are the same but a little bit different :)

To see if it fixes the issues for "those people"

You can also try to ask [MENTION=905572]scanno[/MENTION] and/or [MENTION=3544509]eagleeyetom[/MENTION] about this

Since this really only requires a kernel boot.img it would also dont be

an issues regarding homebuild vs. nightly
[ONE Original Android Development] webore:
add T9 support to the dialer please .

From cm :

http://review.cyanogenmod.org/#/c/83986 to 83994

And maybe more .

these patches include support for Hebrew,Russian,Chinese,Korean,etc .
[ONE Original Android Development] fermasia:
True, yet it's still not the same firmware, so won't be of any use for your problem.

I'd say, as nobody else has reported touchscreen issued with the current driver, let's see if somebody can replicate what's happening to you and be sure it's not your phone.

Besides that... I'm now running an own version of my custom kernel with OOS firmware, if you want to try, let me know.
[ONE Original Android Development] maxwen:
Not really interesting for me so you have to wait until someone wants to do it.
[ONE Original Android Development] :
For the smart people on the thread, how can I make DPI changes survive flashing nightlies?

Thanks
[ONE Original Android Development] fermasia:
[MENTION=4683552]maxwen[/MENTION]

Regarding brightness levels, I'm finding that the lowest step is way too dim for my usage (and my eyes, I guess). I know it has been already asked, but I was just wondering: a) the old kitkat interface to customize the brightness levels has been completely stripped off lollipop, right? b) and do you recall if there's anything in omni's gerrit concerning this subject - any way to customize brightness levels in lollipop?

Thanks :good:
[ONE Original Android Development] nadiros:
I may not be smart, but I'm industrious [emoji12]

I use this app for all my settings. Works well

https://play.google.com/store/apps/details?id=com.flextrick.settingssaver

For those who flash often, and when you want a clean install, its pretty sweet. This plus TiBU makes it a breeze
[ONE Original Android Development] :
Is it automatic? Once I flash the nightly and reboot are my DPI settings applied?

Thanks for the recommendation
[ONE Original Android Development] nadiros:
Yes DPI settings are saved as well after a dirty flash. I do have the pro version but don't think it matters. People were using scripts in addon.d (iirc)to save the build.prop but it's not recommended is there may be changes from one nightly to the next.

*Edit: Once again maybe not what you're looking for but after you download the nightly if you quickly open up the zip you can edit the build.prop with a file explorer from there and change the DPI before you flash it too.
[ONE Original Android Development] 69gm:
Having a weird issue...TMobile LTE doesn't show up on APN list. It uses TMobile GPRS which works but technically isn't the correct one. Another friend of mine's OPO goes to Metro PCS! Supposed to be TMobile!

Anyone else experiencing this? Anyone found a fix?

Thanks in advance!
[ONE Original Android Development] darkobas:
if you change default dpi in build prop google backup stops working
[ONE Original Android Development] schaggo:
Weirdly, on OmniRom backup always shows "backing up to local debug cache only" which I interpreted as "Sorry I'm broken" anyway.

Am I wrong?

Regarding dpi, how about local.prop instead of build.prop?
[ONE Original Android Development] maxwen:
See my answer on g+
[ONE Original Android Development] webore:
I have an issue with opendelta .

the log is here :

Trying to find zip 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip' on '/data/media/0'... I:Looking for zip at '/omni-5.1.1-20150711-find7op-NIGHTLY.zip' I:Looking for zip at '/data/media/0/omni-5.1.1-20150711-find7op-NIGHTLY.zip' Unable to locate zip file 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip'. Installing 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip'... Checking for MD5 file... Skipping MD5 check: no MD5 file found sysutil: Unable to open 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip': No such file or directory E:Failed to sysMapFile 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip' E:Error installing zip file 'OpenDelta/omni-5.1.1-20150711-find7op-NIGHTLY.zip' Done processing script file

should I move the zip file to /sdcard ?
[ONE Original Android Development] :
I tried following some directions to do this on CM9, thinking they should be similar, but it didn't work.

If you have any instructions for LP would appreciate if you'd share.
[ONE Original Android Development] 69gm:
Is the server problem back again? Noticed latest build is 0MB again.
[ONE Original Android Development] spanish33:
[MENTION=4683552]maxwen[/MENTION] is odex version possible?
[ONE Original Android Development] maxwen:
Not decided yet
[ONE Original Android Development] nadiros:
Looks like the build for the 15th is up on the server. I haven't tested it and it doesn't show in open delta so just an FYI.
[ONE Original Android Development] :
Pretty nice battery on stock kernel. This is pretty much 95% on LTE. Thanks for all the hard work team OMNI.
[ONE Original Android Development] karthi89:
Only missing thing is advanced location setting on notification drawer.. I play ingress a lot and its hard to switch location mode. [MENTION=4683552]maxwen[/MENTION] can you please add this. Also. 75 animation scale I requested earlier.
[ONE Original Android Development] scanno:
Why would you need that? I play ingress I never need advanced location settings.
[ONE Original Android Development] maxwen:
Adding new steps is painful boring work. And more effort as it sounds because of the way this is implemented in AOSP.
[ONE Original Android Development] karthi89:
Incase of incorrect location, I can toggle btw high accuracy or gps.

---------- Post added at 07:04 AM ---------- Previous post was at 07:03 AM ----------

Okay.. Don't strain then.. I ll try to make me comfortable with 0.5 ?.. Adv location settings?
[ONE Original Android Development] ghmail2:
gravitybox + xposed works pretty well.

it gives you almost all the features (doubletap to sleep, quick setting tiles and many other things)

---------- Post added at 08:43 AM ---------- Previous post was at 08:43 AM ----------

ondemand or smartmax?
[ONE Original Android Development] :
Smartmax
[ONE Original Android Development] chrcol:
question.

why when I check updates is none yet a nightly is built everyday?

on kitkat I didnt have the issue.