CyanogenMod for the XTZ - Xperia Tablet Z Q&A, Help & Troubleshooting

Is the SGP311DE/B (16GB/WIFI) already support?
Can I just follow the guide from the cyanogenmod wiki?

chris23az said:
Is the SGP311DE/B (16GB/WIFI) already support?
Can I just follow the guide from the cyanogenmod wiki?
Click to expand...
Click to collapse
Not yet none of the devs have the wifi only version yet, everything at the moment is LTE based.
Sent from my SGP311

hopefully all versions /WIFI&LTE) are treated the same in the further development.
not the WIFI only device at some point no longer be maintained.

chris23az said:
hopefully all versions /WIFI&LTE) are treated the same in the further development.
not the WIFI only device at some point no longer be maintained.
Click to expand...
Click to collapse
Think they will all be treated the same, I think it's just no devs have the wifi only models yet and there are differences in the firmware.
Sent from my SGP311

where can I find info that the wifi version is not supported
http://wiki.cyanogenmod.org/w/Pollux_Info
Or is it something with the bootloader?

should I exchange the SGP311DE for a better support?

chris23az said:
where can I find info that the wifi version is not supported
http://wiki.cyanogenmod.org/w/Pollux_Info
Or is it something with the bootloader?
Click to expand...
Click to collapse
The info on that page is somewhat subtle, in the specification box on the right of the page the device is "Also known as" SGP321. That's the code for the LTE version, while the wifi-only versions are SGP311 and SGP312 (16 and 32 GB, respectively).
I soft-bricked my SGP312 whitin the first 12 hours I had it in my hands, but thanks to a couple of very friendly developers, I managed to revert the device to a stock one, relocking the bootloader and flashing the stock ROM. It seems that the boot.img used in the pollux CM image is strictly addressed to the SGP321, and thus not useful at all on a wifi only model.
Hope this helps,
Alberto

If set this CyanogenMod, I will root? SGP321

Related

{Information}CyanogenMod for the Play

A few of Sony Ericsson's newest devices are queued up to get CyanogenMod Custom ROM. Thanks to recent code submitted by Diogo Ferreira, the bits needed to bring my favorite custom ROM to three smartphones in the Xperia family:
- Xperia Play: r.cyanogenmod.com/#change,7126
- Xperia Neo: r.cyanogenmod.com/#change,7128
- Xperia Arc: r.cyanogenmod.com/#change,7127
Currently the code to add these phones to the CyanogenMod family is awaiting approval to be merged into the CyanogenMod repository. Once that's done we can expect nightly builds to follow not long after.
From that point it's just a matter of time before Release Candidates and a Final Build is available.
Source: http://r.cyanogenmod.com/#q,status:open,n,z
Via: http://pocketnow.com/android/sony-xperia-play-neo-and-arch-getting-cyanogenmod-custom-rom
Woohoo! I am getting a bit sick of my SE ROM, I want a Cyanogen!
very nice, i wasn't expecting official nightlies for our play's
Great!!!!!!!!!
Official CM7 on my Xperia Play is Very very Great
Come on!!!!!!!!
I'd like to hear word from the FreeXperia team. Are they maintaining CM7 officially?
At any rate, I already ROM Manager ready for action ^^
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
RacecarBMW said:
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
Click to expand...
Click to collapse
We're making progress on CDMA phones.
The problem is that simlocked phones don't have RCK_H key so there's nothing to crack the unlock key from. But as said, I'll check it, I have some people willing to test.
Looks as though it has now been merged. Really looking forward 2 flashing nightlies. Cyanogen best mod by a looooooonnnnggggg stretch.
And just in time so that Verizon users can join the party
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
deovferreira said:
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
Click to expand...
Click to collapse
Hi Diogo. Glad to hear from you. Does this mean Xperias will be listed on CM homepage under supported devices, and will get official forum's section?
Given that most of the features worked already in the betas (great job by the FX folks), the main question for the Play resides on the camera. What's the status on that?
And for those people who have ROM Manager Premium, will the nightlies come through it as well?
No ETAS on camera. It will be done when it's done but we're looking into it.
As for nightlies, they should be available soon.
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Mills00013 said:
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Click to expand...
Click to collapse
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
deovferreira said:
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
Click to expand...
Click to collapse
Awesome. The only reason I asked is because of how its different from other devices. The kernel always has to be flashed with fastboot. So I just didn't know how the updates would work or anything like that. I assume we just flash one to start the process and go downhill from there.
deovferreira said:
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
Click to expand...
Click to collapse
I agree completely. It appears that the kernel was working fine, there is just something in the CM build that was preventing the radio from working correctly. Logcat was telling me that it detected a CDMA mode and enabled it but then the phone module would crash. It was late when I started looking into it though and didn't do a lot of research, but I imagine that someone has encountered this with a CDMA port from a GSM cousin before. I'll do some more investigation this evening.
The boot will always have to be flashed separately using fastboot due to the way the sony ericsson bootloaders transforms the boot image on flashing. System updates will be done using the recovery, as usual. At some point the kernel and system may get out of sync, the symptom would be wifi failing to enable, at which point people would have to flash a new kernel.
As for CDMA, the RIL libraries should be different as should some settings in build.prop.
Awesome. I'll see what I can do this evening, and maybe even pump out a working build from the source for CDMA users.
Guys, stay calm.
this is FreeXperia CM7 "just" as official CM
So that is what you all wanted.
We worked over some time now with Diogo, all of us 3 ( Diogo, jerpela and me) have commited our changes, put them together and worked together.
All will be good See it as a surprise
I'm working for over 1 month now everyday on camera support. For now nothing new, but new knowledge
currently i'm looking into camera for new 4.x Firmware release, maybe SE changed something in a good way for us...
Best Regards
Bin4ry
Team FreeXperia
Ok I just read the thread and maybe I missed it, my xperia play is from Rogers. Will I be able to install cm 7?
Sent from my Play, with XDA Premium.

[Q] Ant+

Does anyone know if Ant+ support is working in the CM12.x builds yet? Actually any info regarding this would be appreciated.
Also, should Ant+ be working in any of the stock based builds such as http://forum.xda-developers.com/xpe...m-existenz-ultimate-1-0-5-light-dark-t2835196 ?
Again, not a lot of info out there and it's hard to search for as the + is always getting dropped.
Which ANT+ chip is in the Z2?
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
This is a good question.
It's a Qualcomm 801 SoC. https://www.qualcomm.com/products/snapdragon/processors/801
Is that helpful? I dunno.
Post #2 in the thread I linked to has some tips for knowing what hardware is used. If you are running a stock ROM (or any with ANT+) you can follow step number 3, simply running the ANT Support Checker app.
iRant said:
Post #2 in the thread I linked to has some tips for knowing what hardware is used. If you are running a stock ROM (or any with ANT+) you can follow step number 3, simply running the ANT Support Checker app.
Click to expand...
Click to collapse
Yes, I had a go at that today. I am running a Paranoid ROM based on CM11 I think. I can't even get the checker app to run, just immediately crashes.
I am going to try to move to the ROM I cited in OP, which I think is based on stock. It *should* support ANT+. No confirmation yet though.

Root for marshmallow?

As the title states... Is there a process to root marshmallow for the Z4 tablet?
Yeah, do check the info board at your local butchers store. I'm sure it will be announced there first.
ramontomzer said:
As the title states... Is there a process to root marshmallow for the Z4 tablet?
Click to expand...
Click to collapse
same procedure as ...
So far (March 10th) SONY have not posted the sources for the kernel.
Going via GitHub is too much work for me...
And the sources there might not be a good match for their released ROM.
EDIT (after seeing the NEW version number in XperFirm at 23:00):
they lumped many devices together: http://developer.sonymobile.com/dow...rchives/open-source-archive-for-32-1-a-1-163/
I will have a look at the m*ss.
And might roll my own root...
@DHGE what is the link that you share justnow ?
is it for rooting ?

Stable Roms without missing features?

I wanted to ask, witch Roms are stable and support all features of Kenzo.
It seems that in several Roms there are different Problems,
from wakelocks and Battery drain,
over Wifi Problems
to missing Fingerprint or VolTE support.
Is it a Problem with Android 6.0 or also with 5.1 based Roms?
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
jimakos98 said:
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
Click to expand...
Click to collapse
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
DarkAlucard said:
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
Click to expand...
Click to collapse
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
jimakos98 said:
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
Click to expand...
Click to collapse
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
DarkAlucard said:
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
Click to expand...
Click to collapse
Well, if you are going to flash this rom you are going to have to flash the appropriate firmware too, since CM is based on it. If you flash the rom without flashing the firmware, you might end up with missing options in settings (I tried this and the "fingerprints" tab was missing). As soon as I flashed the firmware everything got fixed. Also, an official rom means that it is developed by a member or a group of members that have created the original project, while unofficial roms can be built by anyone. For example I can take a CM build and customize it the way i want and then release it to the public. This makes it an unofficial rom, since I'm not a member of the CM development team. But if a rom or an update releases on the CM website, then it is considered to be official.
By the way about the VoLTE support, quoting from OP Q&A:
Q) Is VoLTE supported? (Also useful if you have GApps related problems).
A) No. We use all proprietary blobs from MIUI Marshmallow alpha 'leaked' builds and those builds itself do not have it working. So we'll have to wait until Xiaomi fixes it in their marshmallow builds in future. Also we can't fallback to old LP radio blobs/libs and are not suited with current setup. #blamexiaomi
Click to expand...
Click to collapse
I guess you'll have to wait for Xiaomi to release a stable working MM build if you want voLTE support. :/

Latest Los14 build for 5120 with support for encrypting and where to find it please?

Hi all!
Have a 5120 device (4g) and the versions of Los14 i tried and that are available for download now don't seem to have support for encrypting, which is important to me. So i was wondering if anyone can help point me towards last version of Los 14 that has support for that, and where and if it is available for download.
Strangely enough even later versions made for 5110 (wifi) seem to support encrypting.
Or am i doing something wrong?
Did you try with walther's builds from https://forum.xda-developers.com/t/rom-unofficial-lineageos-14-1-android-7-1-2.3950114/ or something else? Ask in that thread, I've got the wifi variant and don't use encryption.
ektus said:
Did you try with walther's builds from https://forum.xda-developers.com/t/rom-unofficial-lineageos-14-1-android-7-1-2.3950114/ or something else? Ask in that thread, I've got the wifi variant and don't use encryption.
Click to expand...
Click to collapse
Thanx for answer!
I did try those builds you suggested, not aware od any other sites with appropriate roms.
Will ask in that thread.

Categories

Resources