yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sam45:
Only on rotation & aosp browser (so also when searching via google search for example)
[Samsung Galaxy Nexus] aosp:
Well the CM11 tuna kernel on branch cm-11.0 is Linux 3.0.101 and has no upgrades on the omap4 platform side so the same old drivers google gave us are in use so the graphics issues on kitkat should still be present [MENTION=4112553]dhacker29[/MENTION] is working on the omapzoom 3.4 tuna bringup on his personal github patience daniel son ;)
[Samsung Galaxy Nexus] youStolemylaptop:
It's also in some apps that use the browser. (Instagram, Reddit is fun, etc.)
[Samsung Galaxy Nexus] stranostrano:
May be a dumb question but did someone tried to switch from ashmem to pmem?
[Samsung Galaxy Nexus] bsmitty83:
So I just added this to the ever growing number of local sources my laptop has on it and this is basically what I thought would be my only chance at getting a build to somewhat work beyond the command line . this is basically exactly what I was doing on my own , merging all the old files that 3.4 doesn't have and then trying to fix the build errors one by one , but I'm glad there's some talented people working on this , I believe Amperific is back on a 3.4 workup too .
[Samsung Galaxy Nexus] stranostrano:
back on my tought about pmem instead of ashmem, would you make a try with pmem forcing the 2d engine to do color conversion, scaling, rotation, etc. We'LL need more mem but ...
[Samsung Galaxy Nexus] bsmitty83:
Maybe for a 3.0 kernel ...
[Samsung Galaxy Nexus] stranostrano:
Why? We have already "pmem" on 3.3 and 3.4 kernel. It's capability of allocate large contiguos buffer is used in some camera function.
[Samsung Galaxy Nexus] bsmitty83:
First we gotta compile a kernel with all the graphic and video drivers ( not to mention everything else ) , and unless someone rewrites the drivers there gonna be the same as the 3.0 , just incorporated into Linux 3.4 , so to test if pmem would help 4.4 , it would be better to try on a 3.0 kernel.
[Samsung Galaxy Nexus] stranostrano:
Ah ok. that's make sense. thank you
[Samsung Galaxy Nexus] metalspring:
I'd be willing to try building a 3.0 kernel that uses it

however im no kernel dev, basically i can build from source with a few modifications

that said, how hard would it be to switch pmem? is it just a simple config change or a whole lot more involved?

Edit: btw, my current kernel source on my pc is franco kernel
[Samsung Galaxy Nexus] stranostrano:
Sorry but I'm not sure about and I haven't sufficient skills on ARM to point you in right direction, but I think it's not such different. I think it's just a simple config change to switch from "android shared memory" to "process memory allocator".

Maybe you can find some hints on android kernel reference tutorial.

p.s.: if some devs thinking about we are getting a wrong way, please tell us before we start a useless hard work. thank you.
[Samsung Galaxy Nexus] Prasad:
Guys, no matter what I do I just can't get the ROM from dhacker's tweet working!! This time I've tried flashing the factory nexus image and then retrying with TWRP instead of CWM, yet my phone is back to the Google logo to stay.
[Samsung Galaxy Nexus] stranostrano:
+ or - ot: I was thinking about the PowerVR gpu. It use a microkernel (software firmware) for all higher level events at the GPU level and then I think it's difficult to achieve a decent debugging.

-"....thinking" -

some hints?

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

wth. someone else can confirm this? I'm just downloading.
[Samsung Galaxy Nexus] Prasad:
... Not to mention I only attempted to flash his ROM, not even tried the gapps. The ROM just fails for me no matter what recovery I use but works for you guys here !?
[Samsung Galaxy Nexus] AbhishekS:
It has worked for many people.
[Samsung Galaxy Nexus] stranostrano:
flashed. rebooting and ...get working CM.

info:

coming from jb4.3

wipe factory

flash rom

flash gapps

wipe cache

wipe dalvik (I hope it's not ART gapps)

reboot

wait a little

p.s.: bad news. If I'm not wrong that's built with new graphics driver then graphical glitches are still present
[Samsung Galaxy Nexus] Prasad:
Yeah, how about this:

Coming from stock 4.3

Wipe all/factory reset

Wipe /system

Flash ONLY ROM

Wipe cache

Wipe Dalvik cache

Reboot

Wait forever at google logo
[Samsung Galaxy Nexus] Vekhez:
Using TWRP 2.6.3.1

Wipe Cache, System, Data, Dalvik.

Flash ROM, then ART GAPPS.

Reboot.

Profit?!
[Samsung Galaxy Nexus] Prasad:
No, break even. I moved to KitKang ROM, no complaints.. can't keep trying a ROM that just doesn't work.
[Samsung Galaxy Nexus] stranostrano:
probably something wrong with files downloaded. anyway don't waste times. some issue here. animations it's not smooth and panorama works but without image preview. reverting back to saberPA now and apart this digression, we have to stay on topic.
[Samsung Galaxy Nexus] fcisco13:
Wrong thread to ask.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] Prasad:
Just... no.
[Samsung Galaxy Nexus] Vekhez:
Yeah. I was content on this ROM... But the hotspot doesn't work... And it doesn't on KitKang either (well it turns on but it doesn't have a internet connection) but SlimKat seems to work fine..

You using the Maguro right?
[Samsung Galaxy Nexus] Prasad:
Absolutely.
[Samsung Galaxy Nexus] akash3656:
Not the right place to ask, but I won't shoot you down. This happened to me before (on another ROM). Turns out the download was corrupted. And also use TWRMP 2.3.6.1 or the latest CWM.
[Samsung Galaxy Nexus] RajatPatel:
Guys this is a devs' thread, we should discuss this stuff somewhere else but not here. Nobody likes to read through the pages for unnecessary content. Let our enthusiastic devs do their work, we should not disturb them i guess.

Hope you guys understand. Thank you.
[Samsung Galaxy Nexus] pvkiniyan95:
do not disturb

guys in order to keep this thread clean and to continue our discussion i've created this thread. Hope we use it and wont annoy the developers..

I also request the developers to take a look at it occasionally if not periodically to answer our queries and to announce your status or update pls...

http://xdaforums.com/showthread.php?p=47548733 :D:D:D
[Samsung Galaxy Nexus] stranostrano:
any progress? have you found a right way to make modifications and compile?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] latest omapzoom 3.4 branch https://github.com/smaeul/kernel_samsung_tuna/commits/test [MENTION=4610477]Mevordel[/MENTION] has made the most progress so far [MENTION=4112553]dhacker29[/MENTION] Is using the same branch as the op
[Samsung Galaxy Nexus] bsmitty83:
He's using the same branch yes, but he didn't eliminate any code just to get it to build

But I'm still just putzing around . hashcodes comments about how much it would take to get our GPU to work has got me wondering how its all gonna work
[Samsung Galaxy Nexus] aosp:
He got it working on the amazon kindles have you looked at the superior repos?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Before trying to get the updated drivers working on 3.4.X have you tried on 3.0.X first?

https://github.com/CyanogenMod/android_device_samsung_superior/commits/cm-11.0

https://github.com/CyanogenMod/android_device_samsung_piranha/commits/cm-11.0

https://github.com/CyanogenMod/android_kernel_samsung_piranha/commits/cm-11.0

https://github.com/TheMuppets/propr...mmit/4359694e9a58fa4614cdb9d51a95eccef122378c
[Samsung Galaxy Nexus] bsmitty83:
I did , I never could get the modules to build outside the source , but I'm still working on a solution , the 3.4 project is just a side project to the updated drivers . I'm gonna clean up my working folder and get to it lol

right now im gonna update my 3.0 kernel with some new stuff and then load up 4.4 for some testing , has anybody grabbed a log of the graphic glitches yet ? if not ill start there
[Samsung Galaxy Nexus] pattyboi:):
ill work on getting one when i get back from school+ any test builds you come up with for the 3.0.x with anything new you need tested ill be happy to help with
[Samsung Galaxy Nexus] ilMessia:
Have a look here for the logs http://xdaforums.com/showthread.php?t=2530132
[Samsung Galaxy Nexus] stranostrano:
Thank you aosp for your effort. Could you point me to the repos of kindle you've talking about?

I think you refer to a powervr one and not to adreno, but I can't find anything.
[Samsung Galaxy Nexus] aosp:
check a few of my older posts ;)

[MENTION=4608636]bsmitty83[/MENTION] you building roms too right?

Have you added the below ifdefs to the tuna BoardConfig.mk?

BOARD_ALLOW_EGL_HIBERNATION := true

BOARD_EGL_WORKAROUND_BUG_10194508 := true
[Samsung Galaxy Nexus] bsmitty83:
No I've been strictly working on kernels , I don't have broadband at home right now so I haven't been able to clone a ROM source . I tried those "updated" commits from a few pages back and still no good on 4.4 , the only relevant commit was to make selinux permissive on boot , the others were net (ipv4 &ipv6 ) related .
[Samsung Galaxy Nexus] aosp:
Well those should be in the BoardConfig.mk for the tuna and I'm surprised most kk roms are not using them it was the first commit I noticed relevant to the GNeX once source was available and it should help the graphics at least one Googler cared for the omap4 ;)

https://plus.google.com/106715949401433045760/posts/GZrTCdCsiso
[Samsung Galaxy Nexus] stranostrano:
sorry but the 3.4 kernel source of pandaboard omap4 4460 doesn't could help us?
[Samsung Galaxy Nexus] bsmitty83:
It all helps ( all the 3.4 sources ) relatively, its at best a model of what the code should look like , but its not a copy and paste job .

I might try to source shiny ROM and build it with the new commits [MENTION=2838735]aosp[/MENTION] linked , cuz I was on it with my own kernel and it was crazy fast , just the graphic glitch that would eventually crash phone but I like it and will work on that now I guess . hope Verizon don't mind my 100gig data usage for the last few months , thank god for unlimited data
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] I just had a little time to read up on webview and I want you or any GNeX kitkat users to try something easy for me and let me know if it fixes up the graphic glitches in the browser etc ok

create the file below in the exact location if you don't have it already

/data/local/tmp/webview-command-line

now make sure the text below is inside the file

disable-webview-gl-mode

check permissions

chmod 0644

reboot and make sure the file is at the same location with disable-webview-gl-mode now test the browser report back ;)
[Samsung Galaxy Nexus] wisefreakz:
Wait a minute... Trying that!!
[Samsung Galaxy Nexus] AndyYan:
I don't understand this part: "reboot and make sure the file is at the same location with disable-webview-gl-mode", but I did all remaining steps and Browser still welcomed me with the b!tchy black block :banghead:

Sent from Samsung Captivate Glide @ CM10.2
[Samsung Galaxy Nexus] wisefreakz:
[MENTION=2838735]aosp[/MENTION] did what you asked.

Created the file, add the text, set permission and rebooted.

After, file still there... Glitch still present!
[Samsung Galaxy Nexus] aosp:
I forgot to mention add ro.debuggable=1 to the build.prop then reboot let me know ;)
[Samsung Galaxy Nexus] clnzx2:
Doesn't seem to work for me but I could have screwed it up
[Samsung Galaxy Nexus] aosp:
make sure USB debugging is enabled in developer tools and you have ro.debuggable = 1
[Samsung Galaxy Nexus] wavedashdoc:
Ok make this simpler. Post exactly what we need with the revision.
[Samsung Galaxy Nexus] flip360:
Did everything, still black boxes in browser. Using a taste of kitkat Rom
[Samsung Galaxy Nexus] kuronosan:
What file extension is this supposed to be? It didn't work for me. Still black boxes.
[Samsung Galaxy Nexus] ashclepdia:
What was just said just made me think of a post I saw in a ROM thread recently, something about a missing lib (libchromeview.so or something I believe)

Now I dont know much, but maybe in that same line instead of "webview" maybe use "chromeview"?

This was prolly a stupid post on my part so that's all I'll say :/
[Samsung Galaxy Nexus] pattyboi:):
dont ever say any guess is stupid if your trying to help man,i saw the same thing in a thread a lil bit ago,it might actually help out..
[Samsung Galaxy Nexus] xolanir:
Tried the suggestion, and it didn't work. Thx for trying though!
[Samsung Galaxy Nexus] jhonnyx:
no file extension; not every file has ;)
[Samsung Galaxy Nexus] kuronosan:
Okay, well it definitely didn't work then. I'll try changing "webview" to "chromeview" later.
[Samsung Galaxy Nexus] ashclepdia:
I had done some searching after my post earlier and came across multiple bug reports and issues related to the new chromium webview. Granted they aren't the same graphical issues we seem to be having here on Gnex, but has got me wondering if it isn't just some weird issue due to a buggy release from google concerning their new webview. Cuz it seems like chrome and other browser that use their own web view engines within application seem to be working just fine correct?

Makes me wanna experiment with trying to use the older one for now somehow(best thing I can do is try switching out libs since I have no Dev knowledge really that would be of any use)

(Apologies since I know this isn't exactly 3.4 kernel development related but with all the talk about trying to fix or at least "work around" graphical issues in this thread I thought it would fit best here for now due to how active the thread is :) )
[Samsung Galaxy Nexus] skitty:
Yea, it was me that posted about the libchromeview.so file missing from /system/lib. I was guessing it was to do with webview. The chromium version is only about 1 mb in size whereas the the above one is over 30 mb and is present on the nexus 5. I think we should do a teardown on the factory image and compare libs etc to see what is missing/different. I did try just adding the file afterwards but I guess it needs to be there when building the rom
[Samsung Galaxy Nexus] aosp:
What did I tell you guys from the start my findings were not meant for the blogs but for devs and once [MENTION=4112553]dhacker29[/MENTION] is on it well you ain't stopping him ;)

OMAP: remove pvr services and omaplfb from kernel

- http://goo.gl/wXtMpV

omap: Add ION system heap to omap board file

- http://goo.gl/1naJ6J

toro: Upgrade PVR to 1.9@2166536 - http://goo.gl/XAJSEO

Add pvr source to upgrade to DDK 1.9@2166536 · dhacker29/android_device_samsung_tuna - http://goo.gl/SjQlhw

This is just the beginning I got more trust me but regarding webview the gits expose that experiment and like everything with android we beta testing for Google ;p
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION] hit me on hangouts when you want ;)
[Samsung Galaxy Nexus] bsmitty83:
You got it , dhacker beat me to it lol , I got slimrom synced on my laptop and will start bringing all these commits in , since I think it'll compile the PVR now that I'm building the whole ROM , then at least we'll have some new binaries that can be used on other ROMs . but if dhacker is on it , then no worries
[Samsung Galaxy Nexus] aosp:
Yeah changes to both are needed kernel and device to bring the tuna inline with the newer omap drivers and currently the tuna is not even using optimizations for our chip like

OMAP_ENHANCEMENT := true

BOARD_USE_SYSFS_VSYNC_NOTIFICATION

OMAP_ENHANCEMENT_MULTIGPU

OMAP4 done right examples below

https://github.com/KFire-Android/android_device_amazon_omap4-common/commits/cm-11.0

https://github.com/CyanogenMod/android_device_samsung_omap4-common/commits/cm-11.0

Google Nexus support is the best
[Samsung Galaxy Nexus] aosp:
Google Android Experiment ongoing..

Hide Experimental WebView from dev settings DO NOT MERGE

Bug 10427705

The persist.webview system property is no longer needed, so removed too. - http://goo.gl/NP29nE

Remove support for switching WebView.

WebViewFactory remains as an abstraction layer, but will now always

creates Chromium WebView instances.

- http://goo.gl/WzjiP6

At least appops could be used

They could as least put in big bold letters on the android site

Thanks for beta testing TROOLOL
[Samsung Galaxy Nexus] protowave:
��Ҋ�j��[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
wipe_all_ram : all ram wiping is done
* FB base addr = 0xbea70000! lock PLL Done
* PANEL_S6E8AA0_ID_READ : 0xa2, 0x8e, 0x9b.
message.command =
message.status =
message.recovery =
Starting kernel at 0x81808000...
<hit enter twice to activate fiq debugger>
debug>

Almost ready for testing some experiments/kernels/ROMs.
[MENTION=4112553]dhacker29[/MENTION], [MENTION=4608636]bsmitty83[/MENTION], [MENTION=402297]sma[/MENTION]eul ;) You guys are doing so well, wish i could help you.
[Samsung Galaxy Nexus] Mevordel:
What resistor value are you using?
[Samsung Galaxy Nexus] protowave:
150K at the moment.

I'll try with (from post in uart 3d):

but my electronic shop only has 150K,255K,523K with 1% precision.

so for 301K and 619K i bought 330K and 680K 10%.

As UART/USB converter I'm using the openFTDI smd (open hardware and designed from a friend of mine, sorry page in Italian) + Arduino that gives me 3.3V.

Looking to integrate a micro usb male port and some resistors with a selector in the converter board.
[Samsung Galaxy Nexus] protowave:
523k Ohms 1% gives better result:

====== VCELL : 376375, SOC : 55, nType : 5 ======
[Charger] nScaledVCELL : 376375000, nDesriedSOC, : 52, nMaxSOC : 102, nMinSOC : 2
[ omap_power_get_reset_source :47]	PRM_RSTST : 0x2
wipe_all_ram : all ram wiping is done
* FB base addr = 0xbea70000!
lock PLL Done
* PANEL_S6E8AA0_ID_READ : 0xa2, 0x8e, 0x9b.
message.command =
message.status =
message.recovery =

Starting kernel at 0x81808000...
<hit enter twice to activate fiq debugger>
debug> kms   console
console mode
kmsg
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 3.0.96-leanKernel-8.2-05327-g0dd40b6 (imoseyon@ubuntu) (gcc version 4.7.4 20130812 (prerelease) (Linaro GCC 4.7-2013.08) ) #1704 SMP PREEMPT Sun Sep 22 21:38:58 PDT 2013

__OTHER LOGS__
[Samsung Galaxy Nexus] Mevordel:
They don't have to be so accurate, thankfully. See http://xdaforums.com/showpost.php?p=24879172&postcount=50

Are you getting a dmesg with 150? Or a console? I remember getting a console with 619 and dmesg with 150
[Samsung Galaxy Nexus] metalspring:
hmm, not sure if this was mentioned but would this commit help any??

gpu: pvr: Update to DDK 1.9.RC1.JB@2113614

https://github.com/Ezekeel/GLaDOS-nexus-prime/commit/19aecca9756540787ff2057f07ca327b9baf4dde
[Samsung Galaxy Nexus] ashclepdia:
Thanks for reminding me how much I miss ezekeel and glados lol.

He was always at forefront of Dev until his accident. Still love all the great guys we have here too tho, love how y'all keep pounding away!
[Samsung Galaxy Nexus] bsmitty83:
That would be the ddk were shooting for , but I don't think it ever worked the way it was committed , we need all the new binaries and libs that go with the kernel mods , so that's why I've been building a ROM with the new ddk , it should produce new ones , it takes me a min to build a ROM so hopefully soon well have a solution for us all
[Samsung Galaxy Nexus] Enter The Nexus:
I can test some ROMs daily for Toro (if you all need me to...) just PM me.
[Samsung Galaxy Nexus] times_infinity:
You could ask Hashcode for help. He got a 3.4 kernel booting on the Kindle Fire which has an OMAP4 soc.
[Samsung Galaxy Nexus] JackpotClavin:
I got in contact with Hashcode and talked about the 3.4 kernel for the GNex. He informed me that a lot of the ducati and memory management parts have been shifted around on the 3.4 kernel, making it very difficult to get and codecs and camera stuff working if we were ever able to get the display and other stuff to work. As a result of this, I've decided to stop working on this 3.4 kernel port.

If anybody wants to continue working and improving this, the source is available on my github. Good luck!
[Samsung Galaxy Nexus] josip-k:
Bummer.
[Samsung Galaxy Nexus] Segnale007:
Respect and thanks for the efforts you have made!!!
[Samsung Galaxy Nexus] josip-k:
I think its possible. I mean,galaxy 3 i5800 will get it. And its an low- spec phone. 2011 xperias will get it too,and they are much weaker. I dont understand...
[Samsung Galaxy Nexus] sakindia123:
This doesnt have anything to do with specs..
[Samsung Galaxy Nexus] Adi_Pat:
Looking at your github now..

Maybe the panel driver needs a rewrite to support the new DSS code implementations.
[Samsung Galaxy Nexus] Misledz:
Been less than 15mins and you 2 fat-fatia's are here :P Well here is your expertise, talked to dhiru about this but he's focused on the 3.0 port.
[Samsung Galaxy Nexus] renaud:
No, it came when I ported it to the sgs, but unofficially of course. Some time after it was out for the nexus s
[Samsung Galaxy Nexus] josip-k:
Renaud,is there any chance you can port this kernel to gnex?
[Samsung Galaxy Nexus] gnustomp:
"One does not port a kernel, especially Linux"
[Samsung Galaxy Nexus] fishhelmet:
Shouldn't that be "One does not simply port a kernel into gnex"
[Samsung Galaxy Nexus] gnustomp:
Nup. One does not port Linux.
[Samsung Galaxy Nexus] gnustomp:
We don't port it, we build it to work with whatever, but never port something 100% free and open, like Linux. Technicality here. =P

(Sorry to confuse people, this can be done, is just use of the word ’port'.)
[Samsung Galaxy Nexus] renaud:
OK, so you are the only one speaking like this. But thanks for explaining your point of view.
[Samsung Galaxy Nexus] deepayanneogi:
Just saw xperia s JB is coming with 3.4.0 kernel , presently it has 3.0, Its not that hard then if they can officially give it,but yes SONY has tons of kernel devs who got actually paid for that work, here its all free work so yes I understand.
[Samsung Galaxy Nexus] josip-k:
Re: [WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started

Ask renaud.
[Samsung Galaxy Nexus] DanielSanchez:
Re: [WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started

Are you blind?
[Samsung Galaxy Nexus] aosp:
That's the same commit Google reverted cause they wanted to upgrade the tuna with minimal work Nexus half arse support

You must of missed my earlier post but [MENTION=4112553]dhacker29[/MENTION] is doing what google did not do support the right way

Add pvr source to upgrade to DDK 1.9@2291151 · 1116cc2 · dhacker29/android_device_samsung_tuna · GitHub - http://goo.gl/VoYKu1

toro: Upgrade PVR to 1.9@2291151 · 3515f2a · dhacker29/proprietary_vendor_imgtec · GitHub - http://goo.gl/2UVn81

OMAP: remove pvr services and omaplfb from kernel · dhacker29/android_kernel_samsung_tuna · GitHub - http://goo.gl/wXtMpV

omap: Add ION system heap to omap board file · dhacker29/android_kernel_samsung_tuna · GitHub - http://goo.gl/1naJ6J
[Samsung Galaxy Nexus] gigsaw:
KRT16S: Would be better to use this version?
[Samsung Galaxy Nexus] aosp:
Well guys I forgot another one

this time the Wi-Fi chip and once again demonstrating how Google clearly neglected this awesome phone

This would explain all the Wi-Fi issues GNeX users been experiencing they have been lots of fixes since the update Google Nexus Support gave us

This is the last update the GNeX Wi-Fi received from Google

net: wireless: bcmdhd: Update to version 5.90.195.114 · e411d31 · anarkia1976/AK-tuna · GitHub - http://goo.gl/Tb7Qhv

This is the last big update from the awesome [MENTION=3685904]anarkia1976[/MENTION]

net: wireless: bcmdhd: Update to version 1.88.41 · 2d72cbe · anarkia1976/AK-tuna · GitHub - http://goo.gl/cNnDE9

And these are the newest Wi-Fi GNeX drivers on AOSP

net: wireless: bcmdhd: Update to version 1.88.45 · e222a63 · android/

kernel_common · GitHub - http://goo.gl/7XrUix

[MENTION=4112553]dhacker29[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] Google Nexus Support is poo ;)