yashsingh1/xdaforums huggingface dataset:
[Xperia Tablet Z Original Android Development] Entropy512:
It's hopefully something achievable. Problem is it's low on nearly everyone's priority list and it's one of those problems that just seems to be a headscratcher. Since it worked in CM10.0, it should be possible to get it working in 10.1/10.2 - but Steve was having weird issues that didn't make sense on d2. Thing is that the causes of the issue he was theorizing should've broken 10.0 too...

Summer is ending, so that might help a bit. Keep in mind that the non-Windy Pollux is working extremely well. Problem is that few people have the Pollux variant and we've both been busy with other things. In my case a little bit with finalizing find5 (which may happen today), and more with generic "other stuff than CM" - I haven't even been working much on find5. Some things that have happened over the past two weeks may be leading me to retire from Android work. Pulser is working on a different approach to solving this mess we've been dealing with, but he's not as burned out/disgruntled as I am.

Sorry for being so cryptic, but there have been hints dropped here and there as to what's going on over the past two weeks.

They have been far more cooperative than any other manufacturer. There are limits to what a manufacturer can do sometimes due to lawyers, in this case, Qualcomm's arcane binary redistribution policies that make it damn near impossible to distribute blobs separately from a fully built firmware (the whole JBQ mess...)

Before you go on an anti-Qualcomm tirade though, remember: There are no angels in this industry. The only company more friendly than Qualcomm has been was TI, and they've basically exited the mobile business. I've worked with Samsung Exynos and those chips are a ****ing nightmare - Support from an OEM isn't a magic bullet that solves everything, but it's a massive help and in many cases, simply helps with motivation. If an OEM lies to your face all the time (Samsung), you lose any and all desire to work with them. Sony has been consistently honest and supportive of us.

HDMI/MHL is not supported in any device in CM that I'm aware of with 10.1/10.2 - Everyone has had too much else on their plate.
[Xperia Tablet Z Original Android Development] nycbjr:
Happy Sunday!

I just now figured out all the keys to getting GPS on Windy.. See attached pic, I'm traveling for my sisters wedding and have some family things to attend to, but will post something later this afternoon.

Edit, I should add its allot more than just dropping the new blobs into /system/etc/firmware, allot

:D
[Xperia Tablet Z Original Android Development] Entropy512:
Sweet. Even if your approach isn't itself mergeable, it should be something that can be cleaned up into something mergeable.
[Xperia Tablet Z Original Android Development] nycbjr:
Indeed, I'm done with family obligations (for now). I'm going back and removing stuff till it breaks so I can have a nice lean patch (or how to) for us to submit, working on that now!
[Xperia Tablet Z Original Android Development] GretaLewd:
Great news :good:

Let's hope your fix can be incorporated into CM :fingers-crossed:
[Xperia Tablet Z Original Android Development] nycbjr:
It will be able to, its running on Baked (which is a amalgamation of CM/AOKP/ETC), 4.2.2 based, once I wittle it down to whats needed (I tend to take the fire-hose approach to development lol) I'm going to run a 4.3 build and see if it still works.

---------- Post added at 04:31 PM ---------- Previous post was at 03:45 PM ----------

so far I've been able to trim nearly everything I added to the system image (which is great, we like lean), now onto the ramdisk, that's where the fun is :D
[Xperia Tablet Z Original Android Development] shangrila500:
While I know that is true, the Nexus part, it is a damned shame. There are so many devices that are so much better than the Nexus devices and they just get ignored cause the Nexus is easy to build for.

---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------

I would hate to see you leave, I have seen you in several different forums before and of would be a shame to lose another excellent developer.
[Xperia Tablet Z Original Android Development] nycbjr:
Going smoothly here, I've finished all the pruning I feel ok with, fully integrated the ramdisk changes into the standard cm10.1 pollux/fusion tree's and running a test build now of 10.1. if that goes well I'll have a better understanding of just what is required, maybe after my flight tomorrow we can IRC to discuss the right approach to getting all this integrated and submitted to gerrit, i've submitted stuff before for the TF700t, I'm aware of the process, which is why I'm not jumping to get something out today, I want to have something to submit and have a prayer of passing review lol It'd be nice to get some cred :)

so Entropy, I do have a question that might help me prepare for gerrit code review. So the majority of the gps fix is in the ramdisk, specifically files in sbin and changes to init.qcom.rc, those are in the fusion3 tree, they aren't necessarily detrimental to the other devices from what I can tell, they are all additions, so the mod's would be to the fusion.mk and the add's to the init.qcom.rc (and the additional rootdir files pulled from sony stock) I'm still working on pruning those so we only submit what is necessary to get it working, after this initial build (and compiler cache is primed) this should go faster as I can just whip off a bootimage testing removals in a few minutes time. My question is in general does cm prefer this be moved to the devices tree (pollux_windy), and duplicating things (with the proper overrides), or do they prefer it stay where it is, and integrate the additional stuff?

I'm carefully logging these changes this time so I can document what is necessary, taking the scientific approach :D

Edit:

cm10.1 build went pretty smoothly (only missed a few little things) but gps is working! I'm running a build on a cm 10.2 (jb 43) based variant I've been working on (to be released soon). will update you when complete and if it works with 10.2.....
[Xperia Tablet Z Original Android Development] LeBoy:
=================================

SGP311 + JB 4.3 + GPS = Awesomeness

=================================
[Xperia Tablet Z Original Android Development] nycbjr:
I can tell you for sure with 10.1(4.2.2), it kicks the pants off any android gps I've owned, I got a lock in under a second, and that was with 27 satttelite in range! Mind you I'm traveling in St Louis, its pretty flat here lol..

I'm having trouble with 10.2 (4.3), getting a werid error about trying to connect to the audio policy, then it repeats the windows manager never comes up. Trying a vanilla build now (at the gate hah), if it boots ok then I may have messed up the tree merge's, but I hope that 4.3 isn't going to prove challenging, even if it really has nothing compelling for moving to it, other than "its newer".
[Xperia Tablet Z Original Android Development] Entropy512:
Maybe submit what you have now and -1 it to indicate it still needs work - I might clean it up for you. Depending on what needs to change, we'll make a decision as to what to change. On other devices we've made changes to have "device specific" stuff split out into a new .rc file

For blob changes, what I usually do is (assuming you've synced themuppets to get blobs...): "repo start" a new project in vendor/whatever, add the new blobs and .mk changes, commit them, then do "git format-patch -o ~/Documents/ HEAD^" - then I upload the resulting .patch file to Dropbox and give people a public link.
[Xperia Tablet Z Original Android Development] andymg350:
What did you use to test your GPS? Seems I'm having issues with GPS test and Google maps.
[Xperia Tablet Z Original Android Development] nycbjr:
I think I can manage that.

---------- Post added at 03:14 PM ---------- Previous post was at 03:11 PM ----------

I haven't posted the fix yet lol. But I use GPS status and toolbox for testing mainly and then androsensor both are free in the play store
[Xperia Tablet Z Original Android Development] nycbjr:
Update! turned out I was trigger happy on the merge button, 4.3 is building now, but it seems selinux maybe interfering with some of the start up stuff. I'm going to try one thing first, then seek help, selinux has been the bain of my existence for years, its time to settle the score...

in the meantime I'm fairly comfortable with the 10.1(4.2.2) required changes, I'm going to try and submit to gerrit today, Entropy I'm guessing you want to know when I press submit so you can review it?

EDIT.. strike the selinux stuff, I figured it out and 10.2(4.3) is now working, I forgot to update one of the gps libs.

SO.... GPS is working on 4.2.2 and 4.3! The patch is the same, I plan to submit this afternoon!
[Xperia Tablet Z Original Android Development] Entropy512:
Just add myself to review, and probably Guilio Cervera and codeworkx too. While they don't have Windys, they will have input on general code structure and review. Codeworkx is the one who did the exynos4 init rearrangement a few weeks ago.
[Xperia Tablet Z Original Android Development] nycbjr:
wow ok, both you AND codeworkx is going to be reviewing? I better double check everything lol (esp spaces vs tabs!)
[Xperia Tablet Z Original Android Development] Entropy512:
lol. Well whitespace is something that needs to be right for merge. But I'll probably just clean it up myself.

If you -1 it or mark it as WIP in the commit message, reviewers are far less harsh.
[Xperia Tablet Z Original Android Development] nycbjr:
good to know, I'm happy to report I was able to remove nearly everything I added in my fire-hose approach, I'm preparing to submit, I feel much more confident than this morning, it boils down to just a couple of additions to the init.qcom.rc, a new bin, and some updated proprietaries, since cm uses the muppets for vendor who do I contact to get them added/updated?

EDIT NM! just re-read the submit how to 3 posts above :), I will dropbox as you suggested
[Xperia Tablet Z Original Android Development] DooshPastesh:
I have also screen flickering... I'm using two accounts but flickering is visible on both. On first account apex, second trebuchet. It's present since the beginning of cm 10.2... But veeery rarely.
[Xperia Tablet Z Original Android Development] andyvdsteen:
For me it got worse since 20130902-nightly on Yuga and very rare on Pollux.
[Xperia Tablet Z Original Android Development] nycbjr:
I just submitted the 2 patches to gerrit, you can find the updated blobs necessary to have functioning GPS on windy here: http://tinyurl.com/windy-gps

patch 1

http://review.cyanogenmod.org/#/c/49738/

patch 2

http://review.cyanogenmod.org/#/c/49739/

you can get me offline faster at nycbjr@gmail.com I hope I did ok, I triple checked everything!
[Xperia Tablet Z Original Android Development] remma:
Would it be possible tot add the 10.2 builds tot unristrict.li?

Verstuurd vanaf mijn GT-I9070 met Tapatalk 4
[Xperia Tablet Z Original Android Development] bjm374:
Am I right in thinking we might soon see a version with working GPS or do we need to apply the patch somehow to get it working on the current version?
[Xperia Tablet Z Original Android Development] nycbjr:
You would be correct, the code is in review now, and should be incorporated into cm's nighties soon. I may try and release something in the meantime, but baked is still 4.2.2 based... not sure anyone would want it lol
[Xperia Tablet Z Original Android Development] bjm374:
I'm still running BB-9...
[Xperia Tablet Z Original Android Development] nycbjr:
well then stay tuned, I smell something baking.. lol

Sorry to hijack the thread a bit guys, but I'm pretty excited about windy gps, I almost sold the tabz...
[Xperia Tablet Z Original Android Development] Entropy512:
It's a matter of getting a whole pile of stuff merged. Kali decided to upgrade all blobs on all devices to 4.2.2 blobs, which required some other kernel patches. It's now a matter of making sure he merges everything that is in our local builds. :)

Once it all gets merged, I don't know when the next windy build will be for 10.1 - since 10.1 is on weeklies now. windy missed the RC2 cutoff by a few hours, but I'm guessing it'll probably be on the next 10.1 RC build.

To be clear: I now have working GPS on my windy, and the next build for windy should have it too.
[Xperia Tablet Z Original Android Development] bjm374:
How did you get your GPS working?

I'm off on holidays in about 3 weeks. It would be nice to have the GPS working for that but if not I'll just have to use my phone...
[Xperia Tablet Z Original Android Development] Entropy512:
nycbjr posted the gerrit links above, and one of his gerrit links has his blobs in the comments.
[Xperia Tablet Z Original Android Development] Entropy512:
I have a 311 preordered, SHOULD be here Saturday if it ships on time. Although the way my weekend schedule is, I probably won't be able to touch it until Monday.
[Xperia Tablet Z Original Android Development] JeauxAdam:
I'm stuck until Tuesday I'm assuming because of the holiday weekend. I'm getting more and more excited for it as I see people's initial response to receiving there tablet!
[Xperia Tablet Z Original Android Development] championswimmer:
i might be getting the LTE one (321) soon too.

I'll be compiling AOKP ofcourse, but i'll look forward to contributing something constructive towards the CM device trees too as I have always done in the past for all Xperias I have worked with.

But maybe all bugs will be squashed already before I get hold of it :p

heck it's amazing that most of the recent Xperias have had 80-90% bringup done even before they have landed on retail.
[Xperia Tablet Z Original Android Development] Kali-:
the know bug list is really short:

hdmi
[Xperia Tablet Z Original Android Development] Entropy512:
Yeah, I miss out on all the fun. That's kinda why I have been working on the Find 5 a bit, I wanted the chance to do an early bringup effort as a challenge. Great learning experience - will I take on another Oppo? Don't know. I admit I've been kind of neglecting the Z since mine is a 6603 not a 6602. (I can't rely on it when traveling. :( )
[Xperia Tablet Z Original Android Development] sploony:
I solved my issue, that is flashing it back to a Japanese system dump.

Apparently it failed using the flashtool, I tried with multiple PC's

So flashtool is not working (in my case) with:

- VMware (Windows 7 32, and 64 bits nor with Ubuntu) so VMWare is a no-go

- Windows 8 (keeps disconnecting the device, and yes I installed the "unsigned" drivers)

- Windows 7 x64 (on my laptop, even dual boot did not fix it. Also, don't use a USB3 connection)

In the end I used it on my HTPC (Windows 7 x64) and it would flash right away.

Hopefully CM will come soon for the SGP312 version :) Thanks again Kali- for help trying to get CM 10.1 to work on the SGP312 version.

If I can help you testing CM 10 for the SGP312, just let me know. At least now I "know" how to flash it back :)
[Xperia Tablet Z Original Android Development] championswimmer:
For the tab at least you'll be the wifi maintainer. ;)

We all others are having the LTE one. Ha ha.

And yep mine arrived today.

[MENTION=2492127]Kali-[/MENTION] we have IR already ?
[Xperia Tablet Z Original Android Development] DentTette:
Just FYI,

Volumenode on a SGP311 is /dev/input/event5

Trying to build my own CM based on the patches in review
[Xperia Tablet Z Original Android Development] Soundchasr:
It looks like there are a lot of version of this tablet. Which versions with this Rom work on?

Thanks!!
[Xperia Tablet Z Original Android Development] parapaul:
I posted this in the FXP community on G+ but will probably get a better answer here:

The IR port and Remote Control app are very useful and the app is really quite well made. Is there any possibility, when CM is being built for this device, that the remote control functionality can be maintained?

Either by

1. Keeping the stock app

2. Extracting the .apk to sideload it after flashing CM

3. Sourcing an alternative, non-proprietary app?

I can't wait to have CM10.1 running on my XZ phone and tablet :)
[Xperia Tablet Z Original Android Development] Entropy512:
Currently, only 3G/4G variants (321 and maybe 322?)

Wifi-only versions (311/312) are not currently supported as no maintainer has a 311/312 device yet. I'll be working on fixing/testing the 311 (wifi 16GB) when mine arrives. I think I preordered late enough that I didn't get in the first batch of shipments, as Amazon is now saying my device won't arrive until Tuesday (despite ordering overnight Saturday delivery shipping...)

Edit (update): I have no idea when I'm actually going to get this thing. Delivery estimate May 28 (Tuesday), but it hasn't shipped yet, and the product page now says "usually ships in 3-5 weeks".
[Xperia Tablet Z Original Android Development] Entropy512:
Possibly. The IR APIs were so crappy on Samsungs that the effort to reimplement them in CM for the IR-enabled Samsung tablets died pretty quickly, but Sony's stuff tends to be cleaner and more modular.
[Xperia Tablet Z Original Android Development] championswimmer:
I want to work, or rather just learn by doing and seeing all you guys' work on IR. It's something that interests me. Our college team that builds automated crawlers, I am the guy doing IR there. Have been working on lots of codes for IR sensors lately.

But that was not android and that involved more sensing than signalling with IR. So i have no idea how much that experience/knowledge can be used here. :D

But heck I am interested here, because the Tab Z is the first device I am using that has IR.

It definitely is EXTREMELY useful.
[Xperia Tablet Z Original Android Development] Soundchasr:
Thanks for clearing that up. I'm waiting for the 16GB wifi version too! :good:
[Xperia Tablet Z Original Android Development] Entropy512:
Support for the 311/312 (wifi) variants will probably take longer than expected.

The device sold out during the preorder period, so I have no idea when mine is actually going to ship from Amazon.
[Xperia Tablet Z Original Android Development] gordo79:
I have a uk 16gb WiFi only not rooted and I have not unlocked the boot loader. If you guys need a system dump or anything to help get cm onto the WiFi models.
[Xperia Tablet Z Original Android Development] championswimmer:
It seems, key events and nodes for the hard keys are different.

Also internal storage sizes are different.

Wifi and lte ones are not as similar as i expected initially.
[Xperia Tablet Z Original Android Development] DentTette:
Here is the internal storage info, if it helps ;)

http://pastebin.com/sDET8aQa
[Xperia Tablet Z Original Android Development] jerpelea:
FXP221 released
[Xperia Tablet Z Original Android Development] parapaul:
I have a UK wifi 32gb model - likewise if you need anything I'm very willing to help if I can.
[Xperia Tablet Z Original Android Development] Kali-:
i just finished to merge a bunch of patch on cm-10.1 for all the Z family and GPS fix for windy is part of it

after some more test we will kick an experimental build
[Xperia Tablet Z Original Android Development] bjm374:
I shall wait patiently for you guys to sort it because my eyes glaze over and my mind wanders when you guys start talking about commiting blobs and gerrit links... hahaha
[Xperia Tablet Z Original Android Development] triplec76:
Good job guys and thank you for your work.

I'm excited to get this going so let's stop patting each other on the ass and get it done. :laugh:
[Xperia Tablet Z Original Android Development] shangrila500:
Quick question guys/gals, I was replying to someone when I thought of this....

Since everyone is wanting working HDMI/HHL does Sony even have that in their 4.2.2 AOSP rom?
[Xperia Tablet Z Original Android Development] nycbjr:
if you want an early preview, head on over to http://xdaforums.com/showthread.php?t=2327168 I've posted a new bb9 incorporating my GPS fixes.
[Xperia Tablet Z Original Android Development] andymg350:
Just flashed the new cm10.1 experimental build with GPS fixes its so good to see the full potential of our XTZs finally being realised on AOSP roms. Thanks for everything you guys your doing a great job! once I get some money beers are on me.

Some screenshots of my brief testing standing at my door coz its raining lol
[Xperia Tablet Z Original Android Development] LeBoy:
Cool!!!

[MENTION=345392]nycbjr[/MENTION]: And as soon as we have the Android 4.3 with GPS out of the oven, you can sure count on some extra rounds of beer from me ;)
[Xperia Tablet Z Original Android Development] nycbjr:
Hehe ok, frankly I was a bit miffed at my team for dragging their feet cause I wanted to release something lol, there really isn't anything really great or different about 4.3 except that its "newer", but I get that, I'm working on a side thing I may release in the very near future. think CM but with a baked skin..

I want to thank the CM guys, Kali, Entropy, etc they were a real pleasure to work wtih, I wouldn't mind being asked to do more with CM.. hint hint hint :D
[Xperia Tablet Z Original Android Development] Kali-:
CM10.2 will get this stuff soon

right now i'm adding some stuff to 10.1:

next will be

system_monitor, the sony thermald replacement

should give to same termperature as stock

monitor more sensors

config come from Sony (ofc better then mine) and are made for each device

support modem mitigation

and much more

when all is ready i will queue another experimental with it (probably later today)
[Xperia Tablet Z Original Android Development] parapaul:
I haven't been back to this thread (or the XZ thread) for a while as things seemed to have dropped off here, and the CM builds were rolling out steadily for both.

Just wanted to add my thanks for the continued work - from the CM team and [MENTION=345392]nycbjr[/MENTION] for tracking down and sorting the GPS problem :good:
[Xperia Tablet Z Original Android Development] nycbjr:
haha funny I had put allot of that in while I was tracking down the GPS stuff, having to remove it so I could have a nice lean commit (which I am thrilled went in as smooth as butter)
[Xperia Tablet Z Original Android Development] jerpelea:
FXP236 released
[Xperia Tablet Z Original Android Development] GretaLewd:
I wouldn't rush to go to 4.3.

There are many complaints about "micro-hangs" where sometimes there is a small delay, or maybe you have to press twice on an item to get a response. This was very noticeable when using the AOSP browser in both the 4.3 ROMs I have tried on my Tablet Z (CM10.2 and PAC). I would sometimes have to press 3 times on an item before it would respond. :(

It was so annoying I've gone back to a 4.2.2 ROM (Baked, BB-9). No more problems with touches not working - and working GPS :)

This issue was reported to & fixed by the ParanoidAndroid team in their ROM which I use on my phone. (The PA team even call it "Freeze-free"). It's something to do with an official (JWR66V ?) and trial (JSS15J ?) version being released, and developers using the trial 'buggy' one.

Until the CM team state they have also fixed it, I am staying on 4.2.2 ;)
[Xperia Tablet Z Original Android Development] LeBoy:
Thanks for the tip! I really appreciate.

I think it's time to try a baked ROM. I will install CM 10.1 on the weekend and wait a little bit more for a stable CM 10.2 ;)
[Xperia Tablet Z Original Android Development] gabx:
I am a little confused about CM/FreeXperia./TheMuppets githubs, especially the proprietary_vendor_sony repo.

If I want to build this rom, shall I follow blindly the CM wiki

http://wiki.cyanogenmod.org/w/Build_for_pollux

and use their manifest

or add some local_manifests ?

I am looking to build 10.1

Thank you
[Xperia Tablet Z Original Android Development] andyvdsteen:
I noticed that I had Disable Hardware overlays untagged in Delevoper Options. I tagged it, which fixed the screen flicker issue totally on both Yuga and Pollux.