yashsingh1/xdaforums huggingface dataset:
[Xperia Tablet Z Original Android Development] isimobile:
On 321 .307 fixed the problem. I investigated it a bit and it looks like two firmware files fixed the issue for the .307 update or at leased improved it a lot. I copied those two files to my own personal builds.

pollux/proprietary/etc/firmware/touch_module_id_0x3a.img

pollux/proprietary/etc/firmware/touch_module_id_0x4c.img

The kernel seems to have not changed from the prev version to the .307 version, so that is why I am speculating it is these two files. It is a lot better but it still occurs in my version. Mostly on any application that have a "Zoom" feature it happens for me. Not as often as it used to be, but it still does even with the newer files but a lot better. hth

You can extract those file form the .307 firmware.

[Edit] [MENTION=2492127]Kali-[/MENTION] Maybe you can update the files for the nightly builds to see it it helps?

---------- Post added at 07:07 PM ---------- Previous post was at 06:55 PM ----------

Here is a full list of proprietary files I think that is different from the .307 version compared to what is in the nightlies.

pollux/proprietary/bin/efsks

pollux/proprietary/bin/qcks

pollux/proprietary/bin/thermald

pollux/proprietary/bin/updatemiscta

pollux/proprietary/etc/firmware/apps.mbn

pollux/proprietary/etc/firmware/dsp2.mbn

pollux/proprietary/etc/firmware/dsps.b01

pollux/proprietary/etc/firmware/dsps.b02

pollux/proprietary/etc/firmware/dsps.mdt

pollux/proprietary/etc/firmware/touch_module_id_0x3a.img

pollux/proprietary/etc/firmware/touch_module_id_0x4c.img

pollux/proprietary/lib/libQSEEComAPI.so

pollux/proprietary/lib/libacdbloader.so

pollux/proprietary/lib/libaudcal.so

pollux/proprietary/lib/libcsd-client.so

pollux/proprietary/lib/libril-qc-qmi-1.so
[Xperia Tablet Z Original Android Development] lowtraxx:
I diffed the open source components of .344 against .370 and the only thing changed seems that GPU rendering in webkit/webcore is disabled and CPU rendering is used instead. The kernel changes were all merged already. I will play around a little more with the Firmware you mentioned and the changes I found. Maybe something pops up.
[Xperia Tablet Z Original Android Development] lowtraxx:
Update: added a update.zip that does all the work for you ;)

-----

Hi,

could you guys please try to replace the contents of your /system/usr/idc/clearpad.idc with the following from .370

I am not 100% sure it is gone now, but in my case it only happend once in the last few hours.

# Device Type
touch.deviceType = touchScreen

# Pressure
touch.pressure.scale = 0.0074

# Size
touch.size.scale = 16.57

# Touch Filter
touch.filter.level = 1
touch.filter.path = /system/lib/touchfilter/tftype4.so
touch.filter.tftype4.Enabled = 1
touch.filter.tftype4.AssumedDelayFactorA = -11.71
touch.filter.tftype4.AssumedDelayFactorB = 12.53
touch.filter.tftype4.AssumedDelayFactorC = -0.81
touch.filter.tftype4.MaxSpeed = 0.036
touch.filter.tftype4.PositionFactorA = 0.2
touch.filter.tftype4.PStablePositionFactor = 0
touch.filter.tftype4.DirectivePriorityFactor = 0.95
touch.filter.tftype4.LatestSpeedWeight = 0.9
touch.filter.tftype4.GapResolver = 0.8
touch.filter.tftype4.OrgSize = 8
touch.filter.tftype4.AccSize = 8
touch.filter.tftype4.AddInitialAcc = 1
touch.filter.tftype4.DefaultInitialAcc = 0
touch.filter.tftype4.DragRangeSize = 3
touch.filter.tftype4.NoAccDistanceMin = 15.0
touch.filter.tftype4.NoAccDistanceMax = 500.0
touch.filter.tftype4.NoAccRate = 0.3

You also need to copy the mentioned tftype4.so to /system/lib/touchfilter/tftype4.so

I attach it, but you also can just take it from the .370 firmware. Dont forget to set the permissions as the touchfilter folder does not exist (755 for the folder, 644 for the tftype4.so file)

I am also using the updated blobs isimobile described in his post, but I dont know if that is relevant, as I used them from the getgo. The files specifically of interest should be:

pollux/proprietary/etc/firmware/touch_module_id_0x3a.img

pollux/proprietary/etc/firmware/touch_module_id_0x4c.img
[Xperia Tablet Z Original Android Development] skiwong20:
i went ahead and tested the touch update. i defently improvment of the scrolling in browser
[Xperia Tablet Z Original Android Development] isimobile:
I can also confirm it is a lot better. Great catch! Was bugging me a lot. I have had no issue since applying the patch.
[Xperia Tablet Z Original Android Development] Kali-:
i can raise a big WARNING:

pollux/proprietary/bin/efsks

pollux/proprietary/bin/qcks

will broke radio (on 4.2.2 kernel path is changed)

pollux/proprietary/bin/thermald

will broke thermal (sony do not use it, and i had to hexed to get it working)

pollux/proprietary/lib/libQSEEComAPI.so

potentially can complete broke rom (not completly sure, but i'm not going to test)
[Xperia Tablet Z Original Android Development] Kali-:
[MENTION=615507]lowtraxx[/MENTION]

i have taken i quick look of /system/lib/touchfilter/tftype4.so

on stock rom touch.filter.path is referenced only on libinput, so this blob without the changes on this lib should be useless :/
[Xperia Tablet Z Original Android Development] jerpelea:
FXP229 released
[Xperia Tablet Z Original Android Development] lowtraxx:
Then it seems only the smaller touch.size.scale made it better. I will experiment with the libinput from my 4.2.2 yuga stock rom and post my results here. But at least we are getting closer.

Update: Seems to have no negative effect. If it does make the situation better I don't know, but it does not make it worse (at least for me). I am attaching the libinput.so from the Stock Xperia Z ROM so you guys can try if you want.
[Xperia Tablet Z Original Android Development] Kali-:
[MENTION=615507]lowtraxx[/MENTION]

according to cm changelog should be safe, as the CM changes are legacy input and samsung stylus and both are disabled on our build

https://github.com/CyanogenMod/android_frameworks_base/commits/cm-10.1/services/input

anyway, we may have to take a look of config_minScalingSpan
[Xperia Tablet Z Original Android Development] isimobile:
I had a look today and made some changes to my build and tested, here is my result hth.

I removed all the # Touch Filter items (touch.filter.*) from the clearpad.idc file.

# Device Type
touch.deviceType = touchScreen

# Pressure
touch.pressure.scale = 0.0074

# Size
touch.size.scale = 16.57

I also removed the system/lib/touchfilter/tftype4.so file.

I kept the touch_module_id_*.img file from the newer .307 firmware.

The touch sensitivity stayed great so far ie no zooming happened so far. Also I kept libinput.so as is.

Side note: I looked at the opensource repo on github for sonyxperiadev and the their clearpad.idc file in the 321gp/lagan also had the three items: # Device Type, # Pressure and # Size not just the one that is currently in cm.
[Xperia Tablet Z Original Android Development] Kali-:
today i played with the idc and we we just need

touch.size.scale = 16.57

going to move the idc into device
[Xperia Tablet Z Original Android Development] triplec76:
Has anyone else experienced low volume on pollux_windy?

Also, what is the status on the GPS usability on pollux_windy?
[Xperia Tablet Z Original Android Development] Kali-:
recently we discovered some firmware was missing

recent build should have fixed that but gps is still broken

didnt got spare time to look on it (fix this issue without the device is not so nice)
[Xperia Tablet Z Original Android Development] triplec76:
Thanks for the reply.

I wish I had the time right now to properly help, but I do not. This tablet is really pretty good, but it would be great with a good custom kernel and ROM.
[Xperia Tablet Z Original Android Development] nycbjr:
Kali, really? recently? I knew this a month ago, there is more than just the missing blobs, there are several changes you have to incorporate into the ramdisk, but when you do the device is unstable and randomly reboots. I've spoken with the sony aosp team who have logged the bug. Basically one of the blobs has corrupted section headers, this doesn't cause issues in 4.1 apparently but in 4.2 it does.

I've been offering my help (openly) for weeks yet I'm completely ignored.

I offer it again....
[Xperia Tablet Z Original Android Development] Kali-:
i'm really open to get contribution, some example are also in this thread

i'm sure u will understand that sometime i can miss some post, and sorry if i miss your :/

if u are referring to the sonyxperiadev, i'm not part of this project and i just seen your report

the only Z where GPS isnt working are SGP31x

the script u mentioned are from CAF but i refuse to use

the better place to talk is #freexperia on freenode, also, if u have fix u can just submit your patch to CM gerrit
[Xperia Tablet Z Original Android Development] nycbjr:
Thanks Kali, I was starting to take it personal lol, and sorry if I seemed overly sarcastic, and I do understand its tough to see everything in here (I thought I pm'd you too).

Anyways, not sure what "CAF" script you are referring to (as in the same place that display-caf and audio-caf originate?).

And yes I know that the LTE versions have working GPS, I mentioned earlier that after some research I discovered that the windy is currently the ONLY Snapdragon device without a modem, the modem and GPS (from what I could tell) work together, the firmware is downloaded from the SOC, much like early broadcom closed source wifi chips were in the linux kernel (I'm not sure thats 100% correct but its my theory at least).

I plan to dig up what I did today (via my github) to get it working, I had reverted all this a month ago when my builds started to produce a ram disk where yoiu couldn't press the vol + key to enter it, I was racking my brain, turns out I missed a commit on bootrec-device so it didn't have the proper key mapping lol.

I can't submit these to gerrit (yet) until Sony releases 4.2.2 and we can grab those blobs, as I said when you put the firmware in place with my ramdisk changes, when(if) your tablet boots and you launch maps, you will see the location services in the notification center doing its thing. Problem is the device then resets, and sometimes never gets into the windows manger, I tried to strace it but it doesn't write any errors, just bamn reset. I traced it to what appears to be a malformed blob, gss,mdt has corrupted sections headers. Anyways I'l try and pop on IRC today, just be gentle, I was starting to think you hated me lol
[Xperia Tablet Z Original Android Development] jerpelea:
FXP230 released
[Xperia Tablet Z Original Android Development] Mountainjew:
Does anybody else find the animations really choppy on cm compared to stock? I think maybe Sony have some optimizations that aren't included. Basically makes cm10.1 and 10.2 unusable for me, as stock feels way faster. Same launcher/settings etc, restored from titanium backup.
[Xperia Tablet Z Original Android Development] om22:
Play around with the schedulers from the performance settings. It seems deadline is very smooth. Also the new build from 08/01 seems to be much smoother on my phone and also on the tablet.

Gesendet von meinem Xperia Arc S mit Tapatalk 4 Beta
[Xperia Tablet Z Original Android Development] Mountainjew:
Yeah I've tried fiddling with the schedulers and governors, but seems to make very little difference. Might try just reinstalling all my apps from scratch instead of backup and try to single out any naughties. Doubt it'll make a huge difference though.
[Xperia Tablet Z Original Android Development] Kali-:
ill recommend to stay on interactive, change CPU Governor broke Power HAL
[Xperia Tablet Z Original Android Development] om22:
My cpu governor is always interactive on my phone and tab but as scheduler i have sio on my phone and cfq on my tablet because i think for single core devices (my xperia arc) sio works best and for multicore i use cfq.

Mayve theres almost no difference tough :p

Gesendet von meinem Xperia Arc S mit Tapatalk 4 Beta
[Xperia Tablet Z Original Android Development] isimobile:
[MENTION=2492127]Kali-[/MENTION] Noticed in last nights kernel merge there is a small error in arch/arm/mach-msm/board-sony_pollux-gpiomux.c

/* Chip selects for SPI clients */
static struct gpiomux_setting gpio_spi_cs_config = {
.func = GPIOMUX_FUNC_GPIO,
.drv = GPIOMUX_DRV_12MA,
.pull = GPIOMUX_PULL_UP,
};

---> [B]is in the wrong place[/B]

it should move to after the #endif for both cm10.1 & cm10.2

hth
[Xperia Tablet Z Original Android Development] Kali-:
yes, sony source have it missplaced

fixing
[Xperia Tablet Z Original Android Development] Mountainjew:
The strange thing about the speed issues I've been getting on cm rom is that I don't have any such issue on PAC rom. Both with cm10.1 and cm10.2 only. Not sure if PAC is maybe built on AOSP sources or CM, but its very strange nonetheless.
[Xperia Tablet Z Original Android Development] skiwong20:
pacman is based off cm source mainly
[Xperia Tablet Z Original Android Development] Entropy512:
FYI, after months of pretty much not doing any Android work at all, I'm finally starting to return to this. If you put something up on gerrit, even if it's a horrible hackjob that has no chance of getting merged, it'll at least give me an idea where to start looking.

Edit: By the way, a section header size of 0 in the .mdt may not mean anything. If you look in arch/arm/mach-msm/peripheral-loader.c , you will see that only the program headers are used.

That's really weird... The gss.* files do appear to be loaded on pollux_windy, their presence alone is not causing an issue. The GSS is issuing watchdog bites after startup, I'm not sure why.
[Xperia Tablet Z Original Android Development] Shanliang-:
I guess things will improve around here as AOSP archives from Sony for 4.2.2 have been released. Only for LTE for now, though. But I suppose CM is now focusing all efforts in 4.3.

Good to have you around here, Entropy. :good:
[Xperia Tablet Z Original Android Development] Entropy512:
After poking around, this seems eerily similar to the nightmares we had with not being able to talk to the modem on mint many months ago. It appears that the APQ8064 treats the GSS almost identically to how MSM8960 treats the modem - same SMD edges and channels and such.

That was fixed by disabling GPU-IOMMU sync in the kernel - but that can't be done on APQ8064 as far as I can tell (it hoses the **** out of graphics... And yes, I tried diddling with kgsl_iommu= settings in the kernel cmdline)

I could be totally barking up a wrong tree here, but I have no more time until next weekend at this point. Someone can look at the mint (Xperia T) CM10.1 thread, I think I linked my smd/smsm debugging patches there. Someone will probably have to apply those patches to a .370 kernel tree and compare .370 with those patches to CM10.1 with those patches.
[Xperia Tablet Z Original Android Development] nycbjr:
Yeah the section header thing was just a theory (only thing I had to go on lol), I've been working on re-engineering what I did exactly to get it to work. I will absolutely share and submit to gerrit as soon as I do (I suspect tomrrow), I just wish sony would get with the program and release the wifi 4.2.2, I/we need those blobs.

Rough idea of what I did:

I merged allot of stuff in the init.qcom.rc from the wifi stock boot.img, which included a number or call's to a couple of other *.rc's/sh's in the ramdisk root, and 2 rc's in /system/etc, init.qcom.modem_links.sh and init.qcom.mdm_links.sh, I also added about 4-5 binaries into the ramdisks /sbin (from the stock wifi rom), and a couple of additional binaries in /system/bin.

I was having trouble re-tracing my steps (should be easy cause of git right?) because there must have been some kind of commit to the kernel (I use cm kernel src) that caused one of the /sbin binaries to render the unit unbootable if left in init.qcom.rc. When I checked out the version from git that had worked I couldn't boot the tab anymore, was driving me crazy lol, I will try again tomorrow (work permitting) and hopefully I'll have what was needed to get it going.

As I said when I got the tab booted (took a few times) with the ramdisk changes and the gss* in place in gps status I got the flashing location icon, and in logcat I saw all the fun communications it was doing with the satellites! But after a few minutes the tab would just freeze and reboot, and then generally never boot fully until I removed the gss blobs, just would start the boot animation, and a second later reboot again.

this is the binary that worked a month ago, but now causes a no boot condition (guessing some kernel merge or something else I'm doing) it hopefully isn't necessary. I know my commits are a mess (I really need to have better commit messages), but if you look at my git hub about a month ago, thats when I had it working before I reverted all changes trying to figure out why I couldn't get the up + vol key to access recovery (turned out to be a change made to the bootrec-device, thank god for Meld and directory compare! lol

/sbin/checkabortedflash

I tried to strace zygote, and other boot processes, and try and grab a dmesg before the reset, but nothing (not one damn thing) got written!

Glad to have you back, and I look forward to working with you and Kali. :victory:
[Xperia Tablet Z Original Android Development] jerpelea:
FXP231 released
[Xperia Tablet Z Original Android Development] nycbjr:
That makes sense, I'll take a look around, hopefully in the mean time sony drops 4.2.2 for the wifi only tab, and the blobs/ramdisk/kernel src will provide a more elegant solution.

I had logged an issue on the sony aosp github, I may post a comment and see where they are at, they were going to talk to management about adding the blobs to the aosp project.
[Xperia Tablet Z Original Android Development] Entropy512:
So far, I've looked through the various .sh scripts and can't find anything obvious that would help us - those scripts are common for all qcoms, and all of the GPS-related stuff we don't have references binaries not present in .370 stock.

You didn't try pulling a last_kmsg after reset???

http://review.cyanogenmod.org/#/c/33982/ may be useful - reworked patch for APQ8064 kernel is attached

I could be totally barking up the wrong tree with the smd stuff... It would be useful to run a .370 build with the above kernel patch applied and compare the logs. When I get back I'll work on getting the infrastructure to compile a stock kernel together.
[Xperia Tablet Z Original Android Development] Entropy512:
I'll look at those when I get home. :)

Some of what you describe makes it really sound to me like something similar to the mint modem issues ages ago, where some of the GPU shared memory stuff was stomping on modem shared memory - then it caused the modem to just not communicate, here it seems like it may be causing crashes or blobs stepping on each other.

I REALLY, REALLY HATE debugging smd issues... The whole mint modem challenge was a time consuming nightmare. At least from that experience I've got a few ideas. :)

Edit: The fact that graphics wasn't coming up when it was working is very interesting. That's more evidence it's somehow related to that GPU-IOMMU sync patch and the modem troubles we had on mint.

Bad news is, we can't disable that patch on this device without making it unusable.

Edit 2: In your logcat of it "working" I see no signs of location doing anything - what you pasted was something else communicating as far as I can tell. What's also strange is that on my device, a GSS watchdog bite causes an attempt to restart the GSS subsystem without resetting the whole SoC - but on yours, a GSS restart causes a full reset of the whole SoC.

Fun experiment: I tried pulling GSS blobs from the new Nexus 7 (flo):

Initially, they don't boot at all. Secure boot fails, wrong keys.

So I edit arch/arm/mach-msm/scm-pas.c so that pas_supported returns 0 when id is PAS_GSS

If you do this, then graphics goes bat**** insane (bootanimation is really jerky, and randomly jumps around the screen)

I am now 90% positive that the issues windy is having are due to a similar problem to what mint had months ago, where GPU-IOMMU sync stepped on the modem and stopped it from communicating. GSS on the 8064 uses the same SMD edge as the modem does on MSMs, so this isn't entirely surprising.

The bad news is: It's a lot harder (possibly impossible) to disable GPU-IOMMU sync on 4.2 on an 8064.

The possible good news is:

Those GSS blobs from flo might play nice with CM10.2's GPU firmware/blobs
[Xperia Tablet Z Original Android Development] nycbjr:
So much for "can't work on android till the weekend" lol!

as to the log and not seeing evidence of "working" I was pretty sure that this:

D/QMI_FW ( 297): QCCI: Received NEW_SERVER cmd for 00000100:00000100
D/QMI_FW ( 297): QCCI: Received NEW_SERVER cmd for 00000100:00000100
D/QMI_FW ( 297): QCCI: Received NEW_SERVER cmd for 00000100:00000100
D/QMI_FW ( 339): QCCI: Received NEW_SERVER cmd for 00000100:00000100
D/QMI_FW ( 182): QCSI: QMI_CSI_RX: cntl_flag - 00, txn_id - 0001, msg_id - 0001, msg_len - 0012
D/QMI_FW ( 182): QCSI: QMI_CSI_TX: cntl_flag - 02, txn_id - 0001, msg_id - 0001, msg_len - 000e
D/QMI_FW ( 182): QCSI: Sent[16]: 21 bytes to port 768
D/QMI_FW ( 182): QCSI: QMI_CSI_RX: cntl_flag - 00, txn_id - 0001, msg_id - 0001, msg_len - 0012
D/QMI_FW ( 182): QCSI: QMI_CSI_TX: cntl_flag - 02, txn_id - 0001, msg_id - 0001, msg_len - 000e
D/QMI_FW ( 182): QCSI: Sent[16]: 21 bytes to port 1024
D/QMI_FW ( 182): QCSI: QMI_CSI_RX: cntl_flag - 00, txn_id - 0001, msg_id - 0001, msg_len - 0012
D/QMI_FW ( 182): QCSI: QMI_CSI_TX: cntl_flag - 02, txn_id - 0001, msg_id - 0001, msg_len - 000e
D/QMI_FW ( 182): QCSI: Sent[16]: 21 bytes to port 1536

was the gps talking, its not in the logcat output when the blobs aren't there, and is when they are, anyways I know for a fact that it was working very briefly cause I got the location services icon and lots of output in the log, however I managed to misplace both the zip and the logs, so I have no evidence, so as far as you guys are concerned I'm a nut job lol, but I swear it to be true!

I was going to check "flo" for blobs but figured they wouldn't have them cause flo has a modem in it, interesting experiment, I'd like to test that myself..

The longer it takes sony to drop the official update for 4.2.2 makes me wonder if they 2 are having issues with gps on the windy lol!

Feel free to email or message me offline, or I can join you on irc if you want to chat about this real time, nycbjr@gmail.....
[Xperia Tablet Z Original Android Development] Entropy512:
Nope, flo is the wifi-only Nexus 7. No modem as far as I can tell. 3G versions aren't out yet.

Either way, flo GSS firmware blobs REALLY piss off 4.2 Adreno, but pulser might have luck using them with 4.3 Adreno blobs.
[Xperia Tablet Z Original Android Development] nycbjr:
So I think I made progress of sorts overnight (inspiration hit!), I did a build using my current tree (based heavily off yours thank you! lol), I merged in bunch of the sony ramdisk stuff again this time being a little more conservative and I have a booting tab with blobs in place, and its not resetting, unfortunately still not 100%m, not getting the location indicator in the message center. So not sure if I missed something, or if this is actually better, loc_srv_api isn't timing out, its almost as if its working, but not, lol

logcat

http://pastebin.com/x5w3jYha

dmesg

http://pastebin.com/8wAQzAX2

Edit..

IC you are in Oswego NY, grew up outside of Syracuse, small world
[Xperia Tablet Z Original Android Development] Entropy512:
ooh if loc_srv_api isn't timing out that's good... won't be able to look until I get back from a short trip.

Owego, not Oswego. The s makes about 200+ miles of difference.
[Xperia Tablet Z Original Android Development] nycbjr:
So i started messing around with this again, this time with cm10.2, I'm not a programmer, just a hacker, I'm very weak with c, I want to do the same experiment with the flo blobs, can you share the code that you did to scm-pas.c? I can't quite make it compile lol
[Xperia Tablet Z Original Android Development] Entropy512:
pulser tried it - didn't work. :(
[Xperia Tablet Z Original Android Development] nycbjr:
He isn't using my ramdisk lol, plz!