yashsingh1/xdaforums huggingface dataset:
[Xperia Tablet Z Original Android Development] nycbjr:
New errors, dunno if this is progress or not lol, I took a bunch of stuff from flo etc

E/LocSvc_eng( 666): I/===> int loc_eng_set_position_mode(loc_eng_data_s_type&, LocPosMode&) line 652
E/LocSvc_eng( 666): I/===> int loc_eng_start(loc_eng_data_s_type&) line 513
E/LocSvc_api_v02( 666): E/locClientSendReq:2022]: invalid handle
E/LocSvc_adapter( 666): E/virtual loc_api_adapter_err LocApiV02Adapter::startFix():278]: set opertion mode failed status = eLOC_CLIENT_FAILURE_INVALID_HANDLE, ind..status =

http://pastebin.com/2rk1vJYC - logcat

http://pastebin.com/RYJuJXfK - dmesg
[Xperia Tablet Z Original Android Development] jerpelea:
sorry for long delay FXP232 is uploading

enjoy
[Xperia Tablet Z Original Android Development] bjm374:
Is it Pollux only or Pollux_Windy too?
[Xperia Tablet Z Original Android Development] Shanliang-:
When you click on the FXP232 release, you will see different files, and Pollux and Pullux-windy are both there.

Here's the link to those files: http://uploaded.net/f/c2ke3c
[Xperia Tablet Z Original Android Development] telx85:
G'day guys,

I'm downloading now, takes forever, but does anyone know where to get the Stock ROM back?

I've haven't seen any progress in the GPS issue, and I need to check whether my hardware is at fault or the Custom ROM's are broken as my WiFi is intermittent at best.

Tel'X
[Xperia Tablet Z Original Android Development] zylstrajs:
EMMA might be able to help... http://developer.sonymobile.com/services/flash-tool/
[Xperia Tablet Z Original Android Development] telx85:
Ahh.. good point.. ill look into that. Although I now use CM10.1, very stable… just no GPS…
[Xperia Tablet Z Original Android Development] DooshPastesh:
Hi, I'm New to sony devices. I know that recovery is joined with kernel. Is it possible to backup stock 4.2.2 with cm 10.1 or 10.2 recovery then flash cm and if I don't like it go back to stock?

Wysłane z mojego SGP321 za pomocą Tapatalk 2
[Xperia Tablet Z Original Android Development] om22:
yes but if you want to boot stock again after restore you have to flash stock ftf again with everything excluded but the kernel.

so:

1. flash CM kernel

2. do a backup

3. restore if you fell uncomfortable with CM

4. flash stock ftf but choose to exclude every thing besides the kernel (AND DON´T WIPE DATA)

you´re back on your stock backupped rom then
[Xperia Tablet Z Original Android Development] remma:
So there is no way to return to stock without connecting to a PC?
[Xperia Tablet Z Original Android Development] DooshPastesh:
Hmm I'm thinking about flashing whole cm not only kernel and then go back to stock rom. How about that?

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Xperia Tablet Z Original Android Development] om22:
then insert "flash cm" between "do a backup" and "restore"
[Xperia Tablet Z Original Android Development] DooshPastesh:
Simple. ;) I forgot that I can flash only kernel from tft thanks.

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Xperia Tablet Z Original Android Development] Entropy512:
If you do the backup from CM10.1/10.2 kernel - you'll back up an unbootable configuration.

If you do the backup from a CWM-repacked stock kernel - you'll back up a valid config and should be able to restore that backup. Unfortunately, CWM repacks of stock kernels are proving rare. I am going to try and do one for .370 pollux_windy some time this weekend (I need to do so in order to do GPS debugging)
[Xperia Tablet Z Original Android Development] om22:
hmm i succesfully restored my stock backup with the cm kernel´s CWM(i also made the backup with it); then flashed stock kernel again and it booted.
[Xperia Tablet Z Original Android Development] Entropy512:
Yeah that works - but it's easier if your backup is made from a kernel that can boot whatever you backed up. :)
[Xperia Tablet Z Original Android Development] DooshPastesh:
I 'll stick to cm. 10.2 is awesome. As good as my nexus.

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Xperia Tablet Z Original Android Development] om22:
yup i love it it´s also smoother than cm10.1.

[MENTION=359497]FXP[/MENTION] will you create a new thread for CM10.2? I think it would be a good idea.
[Xperia Tablet Z Original Android Development] pangiotis24:
entropy is there any progress on the gps issue?next week i will receive my pollux windy so i will be able to help you with logs
[Xperia Tablet Z Original Android Development] LeBoy:
The pollux_windy GPS issue seems to be a really tough one. I suspect that even Sony is having troubles getting Android 4.2.2 running stable on the device since there is no signs of an update for the Wifi-only owners yet :(

Let's just see who figures it out first, the Sony engineers or the XDA boys ;)
[Xperia Tablet Z Original Android Development] Entropy512:
I spent most of this weekend sleeping - burnout monster decided to come back and chew on my brain for a bit.

What I need to do is get a stock CWM-repack kernel for .370, then get things sorted to compile a stock kernel for .370 from source - then I can use my SMD debugging patches to look for differences between stock and CM.
[Xperia Tablet Z Original Android Development] chesterchen:
Quick toggles and notifications on CM10.1/2?

Dear people,

Just would like to find out if there was a way to have the status bar at the bottom of the screen, like in stock Sony, when using CM10.1/2?

So instead of having to go right up to the top right/left of the screen to pull down (from top of the screen) the quick toggles/notifications, we can swipe up (from bottom of the screen) to access our quick toggles and notifications?

Also, would it be possible to have the back/home/programs buttons at the right/left of the bottom bar instead of the now centralized?

Thanks,

Chester
[Xperia Tablet Z Original Android Development] om22:
CM follows the AOSP design line. AOSP 4.2/4.3 has the navigation buttons centered and the statusbar on top of the screen so it´s like that in CM10.1/10.2.

The only Roms i know where you can change it are PAC-man, Paranoid Android or AOKP.
[Xperia Tablet Z Original Android Development] pangiotis24:
is the touch screen bug fixed(it was fixed on latest .307 firmware).i don't have the tablet yet but i ask because i haven't seen any related commit but it is fixed on the unofficial cm 10.2 build for pollux.he says he has added some blobs from the .307 firmware
[Xperia Tablet Z Original Android Development] GretaLewd:
I'm running cm 10.2 (17th August nightly) on my 311. No touchscreen problems so far.
[Xperia Tablet Z Original Android Development] om22:
it´s fixed since almost a month i think. i know it was already fixed in cm10.1, just like now in cm10.2
[Xperia Tablet Z Original Android Development] nycbjr:
Let me know what you need from me, I'm considering dumping this tablet in disgust, Sony should be ashamed lol..

I've pretty much given up for now, and hadn't heard anything from you :)
[Xperia Tablet Z Original Android Development] Entropy512:
I've just been massively busy, and recently demotivated by things that have nothing to do with Sony.

I want to collect more data and poke at this more before resorting to the safety net. (Yes, I can ask questions of Sony engineers - but I'm also doing this for the learning experience, so prefer to try and do things myself if at all possible. It's REALLY nice to have that safety net though. It's massively refreshing after having Samsung lie to me over and over and over and over again.)
[Xperia Tablet Z Original Android Development] triplec76:
I am with you on this. I bought this tablet for a couple of main reasons. 1. - Sony supposedly has excellent developer support which made me think with other sony mobile devices, multiple ROMs would be easy to come by. 2. - GLONASS GPS - The main function of a tablet for me is usage of the GPS. Even with the Stock ROM, the GPS is flaky and takes considerably longer to lock a signal than my Galaxy Note 2. 3. - Stock support of Sony features such as Sixaxis controller, etc.

I have been patiently waiting for what seems to be a couple of months now, with no real resolution in sight from my perspective. I waited through my 30 day return period thinking that ROM developers would squash my GPS bugs, but (not their fault, obviously) they have only made the problem worse.

At this point I am hoping for a new release of the Galaxy Note 10.1 (w/ stylus) to sell off my Xperia Tablet Z. I can't be without a tablet unfortunately and I don't particularly care for investing in a year-old model of anything.

I really wanted this to work out badly and still hope it does. The tablet is sleek, powerful, water resistance is a huge plus....This tablet has many things going for it. Personally, I think they should have doubled battery life and made the tablet twice as thick and I would be willing to wait out these problems I'm experiencing.
[Xperia Tablet Z Original Android Development] pulser_g2:
My gut feeling says we will be able to make GPS work after we get better stuff in terms of newer stock build.

Regarding speed of fix, remember the pollux windy doesn't have a modem and thus cannot use cell triangulation to get a quick location to help with faster GPS fixing. I hesitate to say AGPS as I can't remember if that's the correct term for cell triangulation to feed faster fixes.

I took my tablet for some extended use and honestly I actually find it brilliant - I have a nexus 10 and find the tablet Z can outlast or match the nexus in use.

I also did a test and left the nexus 10 in sleep for 8 days (and counting... Now on 10). No reboots there on the nexus (some people had them, that's unrelated), and only 1% battery used to idle.

I reckon with a little tweaking we can get qualcomm devices down to similarly low power consumption.
[Xperia Tablet Z Original Android Development] triplec76:
The battery issue I will not argue because I've never had anything other than an ipad.

However, where I am using my devices as a gps, there is 0 cell service. Unless there is a process going on that I don't know about, the internal gps antenna would be the only item usable. As a matter of fact, I use my devices in airplane mode because the battery drains quickly with no cell service for a few hours.

The Note 2 will lock immediately while the Tablet Z can take anywhere from 5 seconds to never, requiring a reboot to function properly.
[Xperia Tablet Z Original Android Development] Entropy512:
I've never had any problems on stock with slow GPS.

And if your goal is to run CM - I'd avoid the next Note 10.1. Only two CM maintainers got the last Note 10.1, and of them, one has mostly retired, and the other is currently trying to fix GPS on the wifi Z. ;)
[Xperia Tablet Z Original Android Development] Sebz4n:
How stable is this? Enough for daily driver? Is it snappier than stock and how is battery and Wifi?
[Xperia Tablet Z Original Android Development] triplec76:
Under the same conditions (Airplane mode on, both devices in cases), my Note 2 picks up a GPS signal within seconds while the XTZ may not pick one up at all without a reboot.

My daily driver doesn't have to be CM. Any ROM/Stock will do as long as it does the job I need it to do. I just thought that CM or another ROM would fix my problem. I'm going to get another chance to test the XTZ out again this week after flashing the US 312 FTF this weekend. I have been off of the original Stock ROM for quite some time now. Testing around my house this weekend was promising.

I forgot to mention that I didn't mean the last 10.1 to come out. I don't think that is a Note (no S-pen). It is a Galaxy Tab 3 10.1, and yes, I am aware it sucks.
[Xperia Tablet Z Original Android Development] Entropy512:
The Note 10.1 (GT-N80xx) is about 90% abandoned by its CM maintainers... Considering that I'm one of the two, I should know.

Don't know anyone who is messing with the Tab3s yet. The Tab2s only got reliable love because they were OMAP.

Unfortunately my priority lately has been getting Find5 to CM10.1 stable - next on my list after that is focusing on windy GPS. Unfortunately, devices that use the APQ8064 GSS instead of using an external modem for GPS are rare - windy and flo are the only ones I know of.
[Xperia Tablet Z Original Android Development] triplec76:
What I was saying was a new 10.1 that hasn't been announced yet. There is some news that possibly two new Samsung tablets will be announced the beginning of September. Depending on the specs of those (if they are announced) and the status of the XTZ, I may look at switching.

I did realize after the fact that an LTE tablet probably would have been the way to go if I were going to depend on the GPS signal. So that may be another direction I may go by the end of the year.
[Xperia Tablet Z Original Android Development] LeBoy:
Can someone confirm if CM supports Cifs/SMB protocols to mount network shares using CifsManager for example?

I'm still running stock and the necessary modules are not included :(
[Xperia Tablet Z Original Android Development] jerpelea:
FXP234 released
[Xperia Tablet Z Original Android Development] Entropy512:
Remember, if it's Exynos-based, don't expect it to have decent CM support. In fact, given how light the development communities for tablets tend to be, don't expect an Exynos-based Samsung tablet to have any CM support in the future. Something can always change, and someone might randomly step up - but consider it highly unlikely considering that the Note 10.1 was only supported because people with previous Exynos4 experience had an interest in it, and all of those people have chosen not to purchase any more Exynos devices.
[Xperia Tablet Z Original Android Development] triplec76:
Thanks for your advice here.

In a perfect world where a device has great features/functionality, CM or other development is less interesting for me. There are some features that development provides which are really nice, but I have found that on my Note 2 I really haven't been using any features that stock does not provide. I really don't have a burning desire at this time for added features to the XTZ, just properly functioning hardware.
[Xperia Tablet Z Original Android Development] NeverGone\RU:
Guys, does CM Updater work for you?

My XTZ gets stuck in Recovery when I try to update to 20130827 nightly: the progressbar passes about one third, then device reboots and starts in Recovery again, trying to install this update.

Is it just me?

Installing the same update with adb sideload worked just fine, so that doesn't seem to be a "bad download".
[Xperia Tablet Z Original Android Development] pandaball:
There was a bug with recovery, they merged in stuff that broke signature checking that results in infinite reboots a day or two ago. Fixed in the latest nightly (I think), flash it manually :)
[Xperia Tablet Z Original Android Development] NeverGone\RU:
Forgot to say that I tried to update from 20130826 to 20130827 (bought a tablet just yesterday), so it's probably still not fixed :)

Was it "fix --update_package using legacy path" commit?

Will check today on 20130828 update.
[Xperia Tablet Z Original Android Development] pandaball:
Yep. The latest nightly (20130828) has the fix merged I think. Haven't tested it though.
[Xperia Tablet Z Original Android Development] pangiotis24:
concerning the gps issue, sony 4.2.2 for windy has started rolling out so they have obviously found a solution
[Xperia Tablet Z Original Android Development] Entropy512:
I'm fairly certain that it just needed some blob tweaks of some sort. I still am fairly certain it is somehow related to the modem issues we had when combining 4.0/4.1 modems with 4.2 GPU blobs on mint.

Either way, while I'd love to know why the old blobs didn't work, new GSS blobs will probably do the trick.
[Xperia Tablet Z Original Android Development] GretaLewd:
But will it work with 4.3 :eek: ?
[Xperia Tablet Z Original Android Development] Entropy512:
Maybe they will, maybe not. Too early to tell, but I'm guessing it's more likely that 4.2 GSS blobs will work with 4.3 than 4.1 GSS blobs - Qcom made a bunch of changes midway through 4.2 that resulted in most 4.2 GPU blobs stomping on 4.1/4.0 modems on MSM devices, and the GSS on APQs is pretty much sitting where the modem does on MSMs as far as the SMD channels go.
[Xperia Tablet Z Original Android Development] GretaLewd:
Thanks for the very informative answer :good:

Sorry I can't hit the thanks button - used up my daily allowance :(
[Xperia Tablet Z Original Android Development] Mr_Dark:
Compiled CM-10.1 for SGP311 last week, but I noticed the battery drains slowly while charging. Now I finally made a new build with some debugging info enabled in the PowerManagerService and it seems like it gets stuck in some sort of loop. When I remove the usb cable or pull the device out of its docking station, the looping stops. When you boot while the device is charging this doesn't happen, but once you re-plug the power cable it starts again.

After some more digging around it seems like something is constantly sending KeyEvents to the system, which makes the system things someone is pressing buttons or touching the screen.

Can anyone help me debugging this so it can be fixed, I'm planning to use the tablet for a project but for that it needs to be able to stay on at full brightness all day, which is not possible if the battery drains :)
[Xperia Tablet Z Original Android Development] Entropy512:
Hmm, I'll need to take a look, but I haven't seen any odd "input event looping" stuff when charging... Odd TS behavior when charging is usually a sign that your power supply is flaking out and noisy.

That said - Full brightness plus active CPU = it's pushing the limits as to whether it'll actually be pulling enough power from the supply to charge. I should play with this a little this weekend. (I've got a bench power supply with current display.)
[Xperia Tablet Z Original Android Development] Shanliang-:
Perhaps the CM and FXP devs are already aware of Sony releasing the open source archive for the SGP312.

Just in case, I leave the link here:

Open source archive for build 10.3.1.C.0.136

I hope with this we can get lots of improvements :)
[Xperia Tablet Z Original Android Development] pangiotis24:
the main improvement we may get of this is the solution on the gps issue of windy ,the only really important issue on cm for this device
[Xperia Tablet Z Original Android Development] Shanliang-:
I was wondering if devs could take any advantage of this regarding MHL connectivity. As this is one of the reasons that makes me miss stock (for the rest, I'm pretty happy with CM's performance and config settings).
[Xperia Tablet Z Original Android Development] Entropy512:
MHL is probably an issue in display-caf not the kernel.

Quite a few Qcoms had MHL die when going from 10.0->10.1 and no one really had the time to get it working again. It was definitely something in display-caf because mako had working Slimport with AOSP display, but not when it was temporarily using display-caf.
[Xperia Tablet Z Original Android Development] Shanliang-:
Thanks for your quick reply. What I understand from your answer is that it means MHL is something achievable in 4.3, as long as someone put their hands on it. Or it means it couldn't work at all?
[Xperia Tablet Z Original Android Development] Kali-:
already looked on it

apparently nothing new

we may try to use the new gps blob ...
[Xperia Tablet Z Original Android Development] sidelong:
No clues about how to root it?
[Xperia Tablet Z Original Android Development] NeverGone\RU:
Looks like I found something weird...

Screen flickers on a secondary account:

[YOUTUBE]Z0RlXUydLdU[/YOUTUBE]

Steps to reproduce:

1) create a second user and add a google account

2) install Chrome and enable data synchronization

3) tap the address bar and start typing

Flickering does not occur in portrait mode, but occurs when holding the device upside down.

Worst of all — nothing related in logcat.

Anyone else with this?

Update: this also happens on primary user account, but way less often...
[Xperia Tablet Z Original Android Development] jerpelea:
FXP235 released
[Xperia Tablet Z Original Android Development] andyvdsteen:
I have only one account and screen flickers since the first 10.2 nightly on Z and Tablet Z.
[Xperia Tablet Z Original Android Development] andyvdsteen:
Are you using a custom launcher?

I use Holo Launcher HD, and experience screen flickers. Also on Nova Launcher. But I cannot reproduce any flickering when using Trebuchet.

---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------

Now that I know it should be something with the launcher, I decided to play a bit with its settings.

I had an option 'Keep in memory' switched on. With this option didabled, the flickering seems to have disapeared.
[Xperia Tablet Z Original Android Development] triplec76:
Glad to hear we are closer to a GPS solution. My latest experience with the GPS with stock 370 was that I got a much faster lock with airplane mode on than off.

It also "seems" to help if I open GPS test while trying to acquire a signal. Not convinced it is actually helping yet. I still feel like it should not be this difficult to acquire a lock, but once it does, I don't lose it.

I realize this may not be the best place to discuss my own problems with this device, but I am really looking forward to this ROM with full functionality. Maybe if the GPS issue is resolved we will see development really pick up as a whole.
[Xperia Tablet Z Original Android Development] GretaLewd:
I think sadly it's the other way round....Maybe if we had more development then things would pick up around here and the GPS issue would be resolved.

Dead here at the moment - but then I expected it. If you want development, buy a Nexus :(
[Xperia Tablet Z Original Android Development] phillipssat:
Whats about HDMI/MHL is it running stable in newest 10.1 / 10.2 ??

I ask myself where is the advertised open source support from Sony ??
[Xperia Tablet Z Original Android Development] hasenbein1966:
If you want development, buy a Nexus - or a much-sold Samsung... (My SGS2 still has great development.)

I think a Tablet Z is too expensive, so not so many people have it, and even less developers.

Nexus devices have an excellent bang for the buck factor and are kind of hyped always, so developers are more inclined to buy one.

Aside from that, all knew from launch on that shortly the 4.1.2 stock ROM would be followed by a 4.2.2 one, so why waste time on 4.1.2?

And 4.2.2 just has launched, so some patience is what the doctor orders! Now finally it makes much more sense to start developing (perhaps also a kernel for stock ROM with clocking / volting, battery optimization and CIFS / NFS functionality? *dreaming* :) )
[Xperia Tablet Z Original Android Development] andyvdsteen:
Doesn't seem to be a working solution after all. Screen does still flicker.