yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] LeonardK:
much of this has been addressed already.

That's no bug. the Android is NOT able to have swype input. On the other hand you can just install the Google Keyboard which installs the libraries needed for that.

Some say so too. Mine is quite good.

Try turning of Wi-Fi when doing so. Tbis has already been outlined before.
[Sony Xperia T, TL, TX, V] WhiteNeo:
Thanks for sharing your experiences. :)

I am aware of the delayed pin request issue, but currently don't have an idea how to fix this. If I may ask, why do you consider this a serious issue? I personally reboot my phone several times a day - especially when developing - but after getting used to the delayed pin it's no big problem. Of course, it's a bug. But it's still better than an issue that would have a permanent impact on phone usage. :)

Considering the vibrator intensity setting, can other people confirm this isn't working on mint? On my Xperia V everything works fine.

The blue flashing might possibly be fixed by disabling hardware overlays in developer settings, but it is caused by official Sony 4.3 kernel source and a known bug even in Stock roms.

The other minor bugs you mentioned are caused by CM sources and will probably be fixed soon. The missing Swype feature in keyboard is a known issue in AOSP ROMs, as the keyboard is missing a proprietary library by Google. Install Google keyboard to get working gesture input. :)

If the phone shuts down at night, you can try installing the app Safe Charge from Google Play and disable wifi before going to sleep. Both are possible fixes for this issue that is as well present in Stock Sony 4.3 firmware for our phones. :good:

And if you have problems with battery life, I could need a screenshot of your Battery Stats in settings, as well as some screenshots of the app Wakelock Detector, right after you noticed the bad battery life.

Some general suggestions regarding battery life are underclocking and/or undervolting your cpu, as well as using intellimm governor. Also make sure AutoSync and location access is disabled in Settings, if you can live without it. Also disable NFC if you don't need it.

You might also choose 2G only network mode, this will include great battery savings, as tested by me. :)

Thanks for using my ROM! :good:
[Sony Xperia T, TL, TX, V] Ulatexperia:
lt29i

works on TX??
[Sony Xperia T, TL, TX, V] Ckovvi:
No.
[Sony Xperia T, TL, TX, V] Chefov01:
I have the same bug on my T, but I thought it was normal for some reason. :D
[Sony Xperia T, TL, TX, V] Imhuurd:
Im still waiting for Multi-user feature to show up :/
[Sony Xperia T, TL, TX, V] WhiteNeo:
And I'm waiting for people to report if this feature is stable in official builds :D

Don't have the time to test myself atm. :)
[Sony Xperia T, TL, TX, V] harnorizer:
First, I want to thank you [MENTION=5122093]WhiteNeo[/MENTION] for the wonderful job. I really appreciate.

I left from cm-12-20150314-UNOFFICIAL-mint to cm-12-20150321-UNOFFICIAL-mint just by flashing the latest rom without wiping/factory resetting. And I have the bug some people have talked about a few pages back, where my device goes off while on charge and the led is stuck on green and the phone won't turn on until it's restarted by pressing and holding Volume up+Power button. :( But my case is worse because mine happens not only when it's on charge, but also when the phone is idle, so I'm not sure the "Safe charge" app from the playstore will do much help. Please help, thanks so much.
[Sony Xperia T, TL, TX, V] principemoro88:
you're right , the sim is not a real problem. But a big annoyance because I can't send sms or calls for a few minutes.

Overlay hardware? I have not activated this function. However, I remember that it was also in stock, but very rarely.

The swype isn't fundamental. I stay with default CM keyboard ;)

Yes, in 4.3 is rarely turned off the phone, but it was enough to reboot. In CM instead the phone dies. As I said, I have to revive it whit combo power+up. But then is it really a wifi problem? I have to tray!

At finally, it's useless to waste time to post my screen. I ruined the thread. Whit 100% i do about 8 hours.

I have 1.62ghz, governor intellim and i/o scheduler deadline (i would Row but don't exist in this kernel). Then, i don't have active nfc, bluetooth, gps, autosync and 3g. I use only wifi to home and 3g when i go out whit wifi-off. I'm very careful in this :)

[MENTION=5122093]WhiteNeo[/MENTION] thank you so much for respondend to me. Thanks to other users , I will consider them too!
[Sony Xperia T, TL, TX, V] Carlos_Mad:
Vibration intensity never worked on my T
[Sony Xperia T, TL, TX, V] harnorizer:
Same here, never worked. Settings crashes every time I try to change it on my T
[Sony Xperia T, TL, TX, V] Darkierage:
I find "insufficient space" warning really crucial for daily usage since I cannot update or instal any new applications. I have moved every single app (which can be moved) to SD card but still problem exists. I want to try resize partition in order to make this rom perfect for daily usage :) Before this ROM I was using NeoWave rom but since I have tried this one I want use it badly. I would like to ask you guys for any guide/source about resizing partition, I can find more then one for sure but most of them are specific for other phones and I want to be sure I will use correct and tested one.
[Sony Xperia T, TL, TX, V] WhiteNeo:
Alright, will see what I can do. :)

Check general Xperia T forums. A nice, beginner-friendly guide with some unnecessary steps has been posted there. :good: :D
[Sony Xperia T, TL, TX, V] el_angelo:
this was working in a previous version though...
[Sony Xperia T, TL, TX, V] Darkierage:
Thx man! My bad that I didnt notice it :) But I blame the thing I am not usual General section visitor :D
[Sony Xperia T, TL, TX, V] WhiteNeo:
Could anyone check if /sys/devices/virtual/timed_output/vibrator directory exists on your devices and includes a file called "level"?

If yes, I think I know how to fix the force close. :good:
[Sony Xperia T, TL, TX, V] Chico5432:
Yes there is vibrator directory but file "level" is not there. There are directories power and subsystem and files enable and uevent. each time I open dir. "subsystem", I get the same directories and files again and again....
[Sony Xperia T, TL, TX, V] Arcano:
If it is of any help to you, in stock 4.3 the directory does exist, however no such "level" file.

There exists: "enable", "subsystem" and "event" files; and a "power" subdirectory, which contains another five files.
[Sony Xperia T, TL, TX, V] WhiteNeo:
And what about /sys/devices/i2c-12/12-0049 directory? A file called "intensity" should be inside. :)

Thanks for your help btw :D

Also I could need a logcat of the force close when pressing the vibrator settings. Probably will include a "file not found" exeption.
[Sony Xperia T, TL, TX, V] Chico5432:
"intensity" is not there.

Application settings unfortunately stopped working
[Sony Xperia T, TL, TX, V] LeonardK:
Here you go, the logcat is there.

The problematic missing file/dir is: /sys/devices/i2c-12/12-0049/intensity

Thx for debugging, didnt yet notice the bug xD

U seem to be on the right track. The corresponding driver has "vib" in it :)
[Sony Xperia T, TL, TX, V] WhiteNeo:
Thanks a lot. :good:

This might be a permission issue (which I doubt, regarding the fact that the exact same permissions are set in init.rc on tsubasa) or the file is not created in init scripts.. Probably a line has to be added in init.rc to create the "intensity" file on boot and vibration settings should work just fine..
[Sony Xperia T, TL, TX, V] LeonardK:
Hm, there are lc898300_* files in that dir, one having the suffix intensity. Maybe they are just differently named? O.o

cat lc898300_intensity gives 'a' O.o
[Sony Xperia T, TL, TX, V] billysimon99:
Calendar Sync

Calendar isn't syncing for me. Is there a fix for this somewhere that i missed? Thanks in advance!
[Sony Xperia T, TL, TX, V] WhiteNeo:
The names I used in my device repos are the ones that worked in CM11, so why shouldn't they in Lollipop? :o

I wonder if this setting works in official builds. If yes, I might merge the related code.

You can install Google Calendar, add your account and one event, then uninstall.

Should fix AOSP Calendar. :good:
[Sony Xperia T, TL, TX, V] Carlos_Mad:
For your info, I remember that the vibration intensity did not work in my T when I were using your CM11 based ROM. I had the same problem than now, selecting the vibration intensity stops the settings application. I'm sorry I did not report at that time, I had many issues (SOD) with that ROM and the vibration fail was in second place.
[Sony Xperia T, TL, TX, V] harowa:
Before flashing a new ROM I first ever remove the aosp calendar app and the aosp camera app.
[Sony Xperia T, TL, TX, V] theflanker:
Can I ask you which files (lib - permission etc) you have removed to uninstall the Camera AOSP? I would try to install the Social Z2. Thank You
[Sony Xperia T, TL, TX, V] harowa:
I remove the apps from the zip file, nothing more.

Open Zip, navigate to /system/app and delete folder Calendar (includes Calendar.apk) and Camera2 (includes Camera2.apk).

For me it helped, maybe it is dirty.
[Sony Xperia T, TL, TX, V] billysimon99:
Ah awesome, thanks! btw just to let you know im getting settings fc on every reboot, and dialer fc, but dialer fc only after i switched themes using the cm theme engine so maybe it has sth to do with that. doesnt seem to affect functionality tho, just thought i'd report my experience (: Otherwise, great rom, thanks for the hard work!
[Sony Xperia T, TL, TX, V] romcio47:
Can someone, please, provide only a kernel from the latest build?
[Sony Xperia T, TL, TX, V] WhiteNeo:
People, prepare for JustArchi's ArchiDroid optimizations in next build. ;)

Will bring a noticeable boost and up to 6x more performance in certain binaries. :good:

I'm not at my computer at the moment. What do you need the kernel for, if I may ask? :)
[Sony Xperia T, TL, TX, V] romcio47:
I wanted, (if it's possible to do something like that) to test different combinations of CM12 builds+kernels to compare the battery life and finally decide which CM12 ROM I should use. My battery is more than 2 years old and I haven't changed it since November 2012 so today it lasts for a very short amount of time.

I wanted to try:

official CM12 + official kernel

official CM12 + your kernel

your CM12 + official kernel (but I think the result is pretty predictable...)

your CM12 + your kernel

But as I see - you want to use yet another optimizations - so I guess I will move to your build pretty soon, the official CM12 starts to be pretty heavy and sluggish. Also the support from codeworkx is... well... I've changed my mind, there's almost no support.
[Sony Xperia T, TL, TX, V] tajimura:
By the way, that setting didn't work in official CM11 too. Also in FXP.
[Sony Xperia T, TL, TX, V] WhiteNeo:
My kernel is using CAF source, which is not fully compatible with stock. So probably you will face issues. Xperia V owners using my kernel with official CM have broken wifi, for example. :)

But yeah, the test build I'm currently running is pretty freakin' fast, so to say. :D

I can't believe this phone is running with only two cpu cores. I've been able to underclock the cpu to 810 MHz without noticeable lags. :o

In that case, we have nothing to lose and I might release a test build with tsubasa's vibrator settings code after my next build is out. :good:
[Sony Xperia T, TL, TX, V] romcio47:
So... I guess I'll just have to say - I can't wait for to release to test it!
[Sony Xperia T, TL, TX, V] romcio47:
[MENTION=5122093]WhiteNeo[/MENTION] - is there a way to move safely from official CM12 to your builds without wiping anything? I didn't have much time for tests but I've already tried just flashing your ROM over CM12 and it hangs up on bootanimation. I will also try to wipe /system and then flashing rom+gapps+su - maybe someone have already tried this?

Thanks in advance
[Sony Xperia T, TL, TX, V] WhiteNeo:
If you're using an older nightly than my build you can update the way you tried. Otherwise there might be data conflicts that could cause a bootloop. :)
[Sony Xperia T, TL, TX, V] CS Fan 991:
Long time no see !

What's up bro ? :D

This phone is boring ( almost 2 years I got it ) and I want to buy a new but not very expansive phone 200-250 Euro , what do you suggest ( Nothing without an IR port :D )

And if you are going to buy a new phone I would like to buy the same one as you have 'cus you da best and most helpful DEV ever !!
[Sony Xperia T, TL, TX, V] WhiteNeo:
Hey there. :)

First of all: Thanks! :D

I was thinking about buying a HTC One M8.. Price is a little higher (around 300-350) but the phone is indeed really awesome. ^^

But well. I'm still not 100% sure and can't really afford it.. So probably will wait some more time - and maybe the Z4 is out by then, which will most likely be another great phone. :good:
[Sony Xperia T, TL, TX, V] CS Fan 991:
What about 1+1 ? , I dont like Xperia phones they are bad . They only use the best cameras but some special features .... nope and their cameras have the best sensors , and lens but their app sux...

HTC m8 , just found one for 250 .. But I dont like them , I dont like their Sense UI , even they have a huge dev. community ( same as nexus )

And Nexus 6 is a too overpriced , same as their new nexus 9 tab...

Samsung- Bloatware , Sux , Locked board ...

Motorola Moto X , and others arent that good but overpriced

But my 1st choise is the 1+1 , since it has a good price good specs
[Sony Xperia T, TL, TX, V] WhiteNeo:
... And a nasty display bug that still has not been fixed, after more than 3 official updates afaik. :D

But of course the choice is up to you. :good:

By the way, M8 appeared in Google Play edition as well, so you can easily flash a fully stable AOSP rom and get rid of Sense.

Porting Sense is harder than getting rid of it. ^^ And if you've ever used this UI for a longer time (like I did on my old HTC Desire), you will quite often miss it. Most features you need are already included, while the UI is still amazingly fast if compared with (most) other stock ROMs.
[Sony Xperia T, TL, TX, V] CS Fan 991:
GPE is discounted and very rare in my country ( nobody undesrands here what AOSP means :D =
[Sony Xperia T, TL, TX, V] ziggyke:
First:
[MENTION=5122093]WhiteNeo[/MENTION] or maybe another forum member. I'm now at the official TWRP 2.8.5.0 installed on the FOTAkernel partition and I already flashed the boot.img from the latest ROM zip-file via fastboot to my boot partition, but I'm still getting the error about the set_metadata_recursive.

"set_metadata_recursive: some changes failed E: Error in executing updater binary in zip '/sdcard/xxx.zip' "

I still have to alter the update-script (like stated in my previous reply) in the zip for being able to flash this great ROM, could it be that there is something wrong with the binary updater and should be updated?

Second:

I like to being able to switch to F2FS, but when performing step 7 in the OP. TWRP says that "mkfs.f2fs" is missing and couldn't format with "mkfs.f2fs" and therefore is using "rm -rf", but when I check which FS the partition has been fortmatted in it stays on ext4 instead of f2fs is this a normal behaviour or is there something wrong with my version of TWRP and should I use an .img for TWRP 2.8.5.0 with F2FS built in support for Xperia T (where can I find this one?).

Just checked teamwin website and TWRP 2.8.6.0 is available, but not yet for our device. Maybe in that new version the "mkfs.f2fs" is added and it isn't a problem.

Third:

The link in the OP towards the gapps is on AFH, but when I see the named zip file it looks like it is from [MENTION=4375679]Euroskank[/MENTION] or isn't it? If so is the newest from 03-14-2015 and newer also compatible for your ROM? Or are gapp packages made for android 5.1 not downwards compatible with android 5.0.x?
[Sony Xperia T, TL, TX, V] WhiteNeo:
The first two issues are caused by your FOTAKernel recovery. I recommend reverting to default FOTAKernel and using the in-built latest TWRP in my kernels - at least as long as you're using my ROM. :) Will save you all the trouble. :good:

mkfs.f2fs is only present in my recovery because I added the kernel support. :)

Yes, I created a mirror of the last version of Euroskank's 5.0 gapps because they were not accessible at the original page anymore. 5.1 gapps caused force closes for several people - you may read more about this a few pages back in my thread.
[Sony Xperia T, TL, TX, V] ziggyke:
I reverted back to the original FOTAkernel and with success! :good:

I found a how to here.

Don't use the zip in that post, because that is for the Xperia M!

Instead download your proper stock ftf and use that to follow the flashtool procedure. If you don't know where to find your proper stock ftf, then you can use this handy tool and then proceed by flashing with flashtool.

Now I get your recovery with F2FS support! :victory:

Upside: MTP is working for the first time in TWRP recovery! :good:

Downside: After formatting sdcard (internal storage) as F2FS writing via MTP is as slow as a turtle (+/- 1500 items and size of +/- 1,5GB is going to take 21 hours according Android File Transfer and on ext4 this was done in minutes) and can't adb into the recovery, I get the following:

$ adb devices
List of devices attached
CB5123FLKM	unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.

In the ROM I gave adb root permission, adb debug is on and my computers is authorized and it is no problem to adb when ROM is booted:

$ adb devices
List of devices attached
CB5123FLKM	device
$adb shell
root@android:/ #

Is this normal behavior or should I be able to adb into your recovery?

Thanks for the quick reply and give good explanation and pointing out that I should check your thread more often on comments. :)
[Sony Xperia T, TL, TX, V] LeonardK:
I had a similar bug. To fix it:

Copy the public key from your PC into the storage of the authorized adb keys of your phone:

cat /path/to/your/pubkey >> /path/to/phones/authed_keys
[Sony Xperia T, TL, TX, V] froma72:
I switched to Sony z2, with 3gb ram life's easy now, quite annoying :) It's around the m8's price, take a look on it, I think it's a very good price per quality phone.

T is now in wife's hands, she appreciate its speed using basic apps.
[Sony Xperia T, TL, TX, V] DanielGuta:
What can we do to fix volume flutuation?
[Sony Xperia T, TL, TX, V] LeonardK:
For everybody experiencing the 5.0.x memory leak: There's a Xposed module for that ;)
[Sony Xperia T, TL, TX, V] tajimura:
More details, please. On my T xPosed is not working (keeps telling "installation could only be done manually from recovery").
[Sony Xperia T, TL, TX, V] Tolios1999:
Memory leak fix

REALLY? Confirmed working?

I found it. A module to get rid of the Android 5.0.x ColorFade memory leak. But I read there that: " There's really NO NEED to use it on custom ROMs like CM12, they already applied the patch in question."

I don't have xposed installed yet, to avoid messing around too much with this great ROM.

Did you apply it? Any results?

Thanks!
[Sony Xperia T, TL, TX, V] LeonardK:
I do not experienced that in first place, but some others do.
[Sony Xperia T, TL, TX, V] Tolios1999:
I do experience memory leak. But I don't know if it is this particular memory leak or some other. Maybe OP or other members could look in to this and share any opinion?
[Sony Xperia T, TL, TX, V] syntesys:
Memory leak issue has bee patched in CM12: LINK
[Sony Xperia T, TL, TX, V] Tolios1999:
So, no need to use this xposed module. Thanks!
[Sony Xperia T, TL, TX, V] LeonardK:
just wondering why then some say that they'ld experience it O.o. But this xposed module wont help as it does the same, so if you ARE experiencing memleak, it is a different one :-/
[Sony Xperia T, TL, TX, V] LeonardK:
Wow, have you tried fixing the vibration thingy?

and:

> Removed USB "Mass Storage" and "Charge only" modes

why this? :-/
[Sony Xperia T, TL, TX, V] WhiteNeo:
These two modes were not working on most phones, including mine. :D

Will run a test build with experimental vibration fix tomorrow. :good:
[Sony Xperia T, TL, TX, V] LeonardK:
Yep, they seemed to be not so stable though sometimes working ^^
[Sony Xperia T, TL, TX, V] simon27gr:
Why no android 5.1 in the new build?
[Sony Xperia T, TL, TX, V] WhiteNeo:
Because I was working quite hard on improving this ROM.. Will try to build 5.1 next weekend.
[Sony Xperia T, TL, TX, V] LeonardK:
Additionally not all repos seem to have the 12.1 branch yet, so (I didn't specifically check) our device *might* not be ready yet for 5.1.

Additionally:

Many fixes of 5.1 were already in CM12 ;)
[Sony Xperia T, TL, TX, V] Arcano:
No matter how much is given, some people will always want more... :(
[Sony Xperia T, TL, TX, V] el_angelo:
Must say that this is by far the best build you made, and I for one, appreciate the time you take to improve the 5.0 branch instead of switching to 5.1 directly! Hence my donation....
[Sony Xperia T, TL, TX, V] WhiteNeo:
Many thanks for supporting my work. :victory:
[Sony Xperia T, TL, TX, V] smardu:
Xposed is not working on 5.1

Better a 502 rock stable
[Sony Xperia T, TL, TX, V] harowa:
Better an 5.0.x stable than an 5.1 unstable, but better an 5.1 stable than an 5.0.x because of Xposed.
[Sony Xperia T, TL, TX, V] dottnick:
no ota, guys...

we've already spoken about it, xposed is not a priority and is not a stability choice in favor of the rom developing, then do not use it for leverage

some side effects of xposed alpha stage could run the risk of having bugs not related with the Neo's rom and make him crazy around your logs...

(for example i'm not having some bugs that are complained inside the thread and i could bet that are related to personal mods applicated on the rom)

no one should despise the work that WhiteNeo is doing with this great rom, so it's a better choice not harassing him with 5.1 ota

but certainly it's not fair, imho, pressing him to stay on 5.0.2 (that he already said that will update and bugfix with slow realeases)

preventing him from pursuing, CALMLY, (even the CM team has'nt released first build of cm 12.1, so calm down...) to 5.1 experiments

of which benefits and google related improvements could make all of us happier with our device (without leaving it behind the competition in terms of updates)

So i hope that our great developer will do great things like today with 5.0.2 improvements, but the same for future cm 12.1 builds for which i've waiting patiently :)
[Sony Xperia T, TL, TX, V] Carlos_Mad:
Installed and working more fluent than previous releases :). Now using underclock 1.45 with fantastic performance, no need for overclock. The under voltage keeps the phone cold, OK. The vibration intensity is not working on my T. Checking for SOD with wi-fi, I have it connected everytime. I'll report if any SOD happen.

Thank you for this fantastic ROM. :good:
[Sony Xperia T, TL, TX, V] billysimon99:
I was wondering if anyone else is getting massive lag issues, sometimes to the point of making the phone unusable. Apps take forever to load, and sometimes they just stop responding, and general responsiveness of the phone is just really sluggish. I first used the previous build after switching from omni switching to f2fs and resizing my internal memory partition, and the rom was really quite fast and responsive. However after a few days I started noticing really bad lag issues, and didn't know what was causing them. So I installed trickster mod to play around with the kernel settings a bit, which didn't really help. I then flashed the latest build when it was released, and I'm running the kernel in the intelliactive governor and deadline scheduler, but still face pretty bad lag issues. Once in a while the phone seems to be quite responsive, but most of the time it's just sluggish. Any thoughts on what could be causing this? And what experiences have you guys had with different kernel settings with regard to performance and battery life? Governors, schedulers, read ahead values, voltage settings? Thanks in advance! (: