yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] neofral:
wait i don't think that's necessary. try removing the ticked option "use rm -rf instead of formattting" in TWRP.

i had this problem when converting between fileformats

---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------

try undoing the the file system formats using TWRP. when you convert back to ext4 don't forget to untick the option i mentioned in the above post.

just restore your backup if you have one (i hope you do).

this is how i returned to 5.0
[Sony Xperia T, TL, TX, V] WhiteNeo:
Probably not until tomorrow. Will test a patch zip later, but not sure if it will help.

Actually, this Android 5.1 thing and the fact that I'm not the only one facing these data mount issues make me wonder if this version is ready for our phones yet.

Considering the fact that the extremely minor changes in 5.1 do not provide too much additional use, I am honestly thinking about canceling development on CM12.1 for now.

Sensors can be fixed, but I have no idea how to fix the occasional bootloops..

Maybe stable and optimized CM12 is a better choice for us?

(Opinions please! :D)

Tried this.. Also dirty reflashed the whole ROM - no effect on the bootloop.

It might be caused by my F2FS source updates, but then we would also have reports of people running CM12 with this issue. Also I have tested the kernel with exactly those updates for nearly a week without issues.. :/

Thanks for the log! Was unable to grab one due to disabled usb debugging..

However, if it's that line which was causing the issue, I'd have had no idea anyway. :D

Really strange, this issue..
[Sony Xperia T, TL, TX, V] boris_k:
@WhiteNeo, What about building of separate kernel with replacing /mnt/media_rw/sdcard0 & /mnt/media_rw/sdcard1?
[Sony Xperia T, TL, TX, V] MESA:
Well i clean installed cm12.1 and for me the phone was not that smooth(maybe a placebo), also screen rotate not worked, and when i charged it it bootlooped when i checked it, so i reversed to CM12(find it more stable for now). :)
[Sony Xperia T, TL, TX, V] iLitvinov:
With CM12.1, in most cases my XV goes restarting when I finish an incoming call. Battery status goes up and down: from 64% to 46% after making a call, and back again up to 84% after some minutes. However, no bootloops so far.
[Sony Xperia T, TL, TX, V] boyangaZ:
hi to all, im a new poster here, but i followed sir Neo's work...great and thanks for all...my experienced on 5.1 is, it only bootloop when i installed the beta xposed for 5.1 and use amplify (maybe same issue with http://xdaforums.com/showpost.php?p=59930818&postcount=1537), i even didnt have the proximity issue/sd mounting issue ...i always clean install, wipe dalvik 2x...until now, my battery is ok, no bootloop or restarts...currently using 5.1

[MENTION=535343]all[/MENTION]

lets wait for sir Neo's fix or patch, im sure he's working on it...

thanks...
[Sony Xperia T, TL, TX, V] WhiteNeo:
Regarding the sensor issue.. Could anyone running CM12.1 extract system/lib/hw/sensors.msm8960.so from my latest CM12 build and move it to the same location in his system, with rw-r--r-- permissions?

This might be the fix.
[Sony Xperia T, TL, TX, V] devies:
First of all thank you for your hard work. I have been using your rom since your first neo version !

I can confirm sensor is working with this file in place. :good: Auto rotate button in notification drawer is working too :D. For me CM12.1 is stable and so far I haven't had any problems with boot loops. I don't use Xposed framework.
[Sony Xperia T, TL, TX, V] banciii:
I would say Yes. :P At least until the first "stable" nightly builds come, where you could start the building from. :-$ CM12.1 is nice, but in this form, is not as nice as buggy and also uses a lot more RAM and slows down the device many times. :(
[Sony Xperia T, TL, TX, V] Aria.A97:
Or maybe instead merging latest CM sources, focus on your theme or some more Kernel Features :D (I'm using your latest CM12 and has no bugs so far :good: )
[Sony Xperia T, TL, TX, V] WhiteNeo:
Sounds good! Thanks for testing. :good:

I guess the bootloop issue is related to the early stage that the sources are still in. Or to a dirty install.

Did you clean install CM12.1, by the way? :)

Probably you're right. I will run a new CM12.1 build this weekend, to provide a fix for the sensor issue, and afterwards.. Well, we'll see. :D

Don't know what additional kernel features to add. :D

Display control is beyond my skills, I fear. There's not too much (useful) stuff left that could be added. ^^

Maybe finally finishing my theme would indeed be the best idea :)
[Sony Xperia T, TL, TX, V] iLitvinov:
Almost same as mine, except using titanium backups (I do not use TB at all) and Google store force closes. In my case YouTube app force-closed repeatedly. Clean install fixed this issue. I also confirm better battery life with 12.1.

Where did you get Xperia port? Would you please share the link?
[Sony Xperia T, TL, TX, V] devies:
It's somewhere in this thread... Here you go:

http://xdaforums.com/xperia-t-v/v-d...homebuilds-t2967819/post58461387#post58461387
[Sony Xperia T, TL, TX, V] zirhaze:
Just wondering what is with this "Cell Standby" that it uses 20% of my battery in one day (haven't done anything with phone today, literally). Tried to google, but couldn't find anything too useful. Also would be cool to hear what tweaks have everyone else done to their phones to get more battery life out of it :).
[Sony Xperia T, TL, TX, V] banciii:
Eg. I changed back to 5.0.2 and the average system RAM usage is the exact half of 5.1 (~150MB) and it also much faster and smoother. Of course it can be Greenify and it's awesome new Deep hybernation feature, which is not working on 5.1 Xposed yet. But the point is, battery life did not look significantly better, yet. :P
[Sony Xperia T, TL, TX, V] Kureiji:
I think I found a bug in latest CM12 release. Normally in messaging app, some conversation phone number prefixed with "+84" (country code), some other number has "0" prefix. But in latest build only number with "0" prefix has their contact names displayed (I save numbers in contact with "0" prefix).
[Sony Xperia T, TL, TX, V] pakroid:
Thx!!

I flashed 5.1 with clean install. No bootloop encountered.

The sensor problem fixed by the about solution. Thx!!:good:
[Sony Xperia T, TL, TX, V] Chefov01:
I have the same problem, it'll probably get fixed in an upcoming update. :)
[Sony Xperia T, TL, TX, V] emartino:
I also did a dirty update to 12.1. first and had many issues with Android Wear or Hangouts. They closed so often I could not uninstall them... With a clean install everything just works great. I did not change anything (voltage, frequency, file-system, ...) and did not use Titanium. No bootloops or anything else. The phone is much(!) faster than with 12.0.2 (maybe because of the clean install?). So I would prefere the 12.1. to the older one.

Only wish would be to have the internal memory merged with the internal SD as I am always quickly running out-of-memory when adding some new Apps. I never felt comfortable enough to follow the guides floating arround to do that.
[Sony Xperia T, TL, TX, V] mirhl:
There are no tweaks. You just need to find what's your specific problem. Check betterbatterystats or wakelock detector
[Sony Xperia T, TL, TX, V] Enjkshan12345:
...

[MENTION=5122093]WhiteNeo[/MENTION] i confirmed that sensor nw is workring and there's no bootloop issue!!

i flashed the rom for 3 times and there isn't bootloop

but the full wipe is required not recom.

And thanks for ur hardworking <3
[Sony Xperia T, TL, TX, V] rysykas:
What is the best option to disable overclocking?
[Sony Xperia T, TL, TX, V] WhiteNeo:
Huh? :D

Keep stock frequencies, maybe? :D

I didn't change the default frequencies, so if you don't OC there will be no difference in battery life. :)
[Sony Xperia T, TL, TX, V] emartino:
Could anyone post the required sensor library (system/lib/hw/sensors.msm8960.so) - so that I do not have to go back to 12 and then back to 12.1?

Thanks a lot!
[Sony Xperia T, TL, TX, V] neofral:
i've renamed the extension from so to txt. just rename and should be fine
[Sony Xperia T, TL, TX, V] hondza01:
works sensors.msm8960.so, I have clean installation,without bootloop
[Sony Xperia T, TL, TX, V] Drunkware:
Thank u for so much info!:good::good::good:

Could u tell me what bloatware in CM are talking about? And which of them I'm going to remove, if I flash your zip? :)
[Sony Xperia T, TL, TX, V] Aria.A97:
Check second post in that thread. I wrote which apps it will remove :good:
[Sony Xperia T, TL, TX, V] WhiteNeo:
I'm trying to figure out the reason for those nasty bootloops on CM12.1.

Need some information from everyone that encountered this issue:

- Performed a clean install or dirty one?

- Running F2FS or EXT4?

- What did you do before the issue occurred?

Thanks in advance for your assistance! :good:
[Sony Xperia T, TL, TX, V] neofral:
i never noticed bootloop, but a very-very long startup time. i would like to make sure we are talking about the same thing. and to me it occured in both options (that's in both-both :D ). also clean with F2FS and EXT4, also dirty install in both file systems
[Sony Xperia T, TL, TX, V] Aria.A97:
I had totally clean install, wiped everything using both FS Options and Advanced Wipe (Cache/Dalvik/Data/System/InternalSD/Android Secure)

First time, I set up my phone, Installed Only 1 user app : Titanium Backup, pressed "Restore My Device ID" reboot, Bootloop :D

For second time I did a clean install from scratch again, after phone booted, unchecked "Mount namespace seperation" from SuperSU app, reboot, and Bootlooped.

Then I rebooted to recovery, And saw that phone is not able to mount Data partition :laugh:

Whatever, I flashed your latest CM 12 build, Again wiped everything with that kernel, and now for 4 days, it's running good enough :good: So I doubt that updated F2FS sources was causing issues :rolleyes:
[Sony Xperia T, TL, TX, V] Tommy_PL:
1. Wiped everything (cache, system, data, sdcard, secure) except MicroSDcard (ext_sd) - did F2FS format

2. Installed 12.1 / SU_2.46 / Gaps (from this thread),

3. Started 12.1 and playing for a while - rebooting, installing aps and so on. Everything was great - performance, filling and no bugs at all (except sensors) and I can say it is very smooth ROM.

4. I decided to "push in" SIM card and go for serious tests with carriers - so, I had to POWER OFF unit and take battery out.

5. After POWER ON bootloop - and "finito" - I've waited for about 20 minutes and nothing happens - just popup screen with cyanogen logo blinking circle.

So, for me bootloop started after POWER OFF and sim card insert till that everything had worked fine.
[Sony Xperia T, TL, TX, V] WhiteNeo:
So.. All bootloops so far seem to have occurred on F2FS?

Maybe CM12.1 is not (yet?) compatible with this file system, then.

You can differ this bootloop from usual boot process of you've set a different boot animation via Theme Engine.

The never ending bootloop shows the default CM animation instead of your custom one. :)

That's why I figured it was an issue with mounting "data" partition. Which might indeed be related to F2FS.
[Sony Xperia T, TL, TX, V] MESA:
1. Did a clean install here(without wiping sdcard)

2. Usimg F2FS

3. Well installed all my apps, rebooted the phone twice to install viber and after putting it to charger it was bootloped(after some time).

Btw replacing the file from CM12 will get auto-rotate working or its a CM12.1 sources problem? :)
[Sony Xperia T, TL, TX, V] Aria.A97:
Ok maybe CM 12.1 is not compatible with F2FS, but why it also failed in recovery?
[Sony Xperia T, TL, TX, V] banciii:
After the update, it takes about 1 min before I get the PIN request, until that I can use my phone without signal o.o
[Sony Xperia T, TL, TX, V] WhiteNeo:
This problem occured as well in the last version. Still looking for a fix. :)
[Sony Xperia T, TL, TX, V] finac94:
Ok...I downloaded the update and put it on my sd card. Then I turned the phone off, put it in fastboot mode and flashed the boot.img from the new rom...then I went into recovery, installed the new update, wipe cache and dalvik and reboot (it also said I had no root and if I want to install it and I said "yes"). Imidiately after it booted, I started using it and it rebooted....then the 2nd time it didn't reboot so I first checked the storage by taking a photo and transfering to external sd card and everything went fine. Then I opened up a game, started playing and after about 20 seconds it kicked me out to the home screen...then the icons dissapeared for some time and the whole home screen refreshed for a few times and then it just froze and I couldn't do anything so I did a battery pull. I'm gonna check if it's gonna behave better now and post the experiences :fingers-crossed:
[Sony Xperia T, TL, TX, V] WhiteNeo:
If you keep facing such issues, I suggest a clean install. :)

No problems here.
[Sony Xperia T, TL, TX, V] finac94:
I fixed it by rebooting into recovery and flashing the SuperSu update manually...I also wiped cache and dalvik once more to be on the safe side and then i rebooted into system. I waited until it optimized all the apps again and tried playing that game again and I played for a few minutes and had no problems. So I guess the broken root caused the problem (because in twrp after installing the rom i said to install supersu which I believe I shouldn't have done in the first place...and I also noticed that I couldn't get into the SuperSu app so that made me think that the broken root caused all the problems. The only thing not working for me right now is the new Music app...but it's not a big deal because I'm using Shuttle music player so i just disabled the preinstalled one. :)
[Sony Xperia T, TL, TX, V] MoraX1992:
Thanks, worked fine for me! Very smooth
[Sony Xperia T, TL, TX, V] Jonny_Hood:
at my first try i had this SU issue too, bud in the Changelog was nothing to find that SU is integrated so i flashing it direct at the clean installation with GApps.

The new Music app works fine for me also the Equalizer even with Bluetooth, bud i would prefer the Apollo Player because it has donwnloaded Covers and Artist Pic´s (I like that kind of stuff)

After 30 Min listen to music at 1% Battery :eek: my device finally shutdown now i wait 1hr to Check if this bootloop bug exists :cool:
[Sony Xperia T, TL, TX, V] finac94:
Your battery drained from 100% to 1% in 30 minutes?? :confused: :eek:
[Sony Xperia T, TL, TX, V] merlin_zaraza:
Installation aborted

Hi,

I have Xperia V. Got next message while installing cm-12-20141216-UNOFFICIAL-tsubasa.zip:

This package is for "LT25i, tsubasa" devicesthis is a "mint"

Please help.
[Sony Xperia T, TL, TX, V] Jonny_Hood:
No No the Battary shows 30 Min 1% before shutdown, I unplugt the Device at ~8.oo h and shutdown at ~11.45 h (German time) after 2 times installing and testing i got 6% Battery left then i put the Display timer on 30 Min (because i want to drain Battery) and at 1% i start listen to Music and the Device ran and ran and ran xD
[Sony Xperia T, TL, TX, V] WhiteNeo:
Flash the included boot.img via Fastboot.. Or remove the first few lines starting with "assert getprop" from META-INF/com/google/android/updater-script in my rom zip :)
[Sony Xperia T, TL, TX, V] Jonny_Hood:
Look here http://xdaforums.com/showthread.php?t=2581336
[Sony Xperia T, TL, TX, V] finac94:
Oh ok then :D do you maybe remember how much screen-on time you got?
[Sony Xperia T, TL, TX, V] Jonny_Hood:
No SRY but i was using the Device all the time ... i guess it was a lot :p

And the hour is over and i can not reproduce banciii bootloop bug :good:

So far everything works, no bug´s found no fc´s

could someone do an other Bluetooth Test i have only one BT Device to test ;)
[Sony Xperia T, TL, TX, V] Aria.A97:
Last build is smoother than previous one :D

I have no problem till now.

Just found one small UI issue(or maybe it's not) : At lock screen carrier name should be more left aligned :confused: for me it's almost in the middle of screen.
[Sony Xperia T, TL, TX, V] Shady_BlackSn0w:
Flashed looks good no bugs till now

Smoother :thumbup:
[Sony Xperia T, TL, TX, V] WhiteNeo:
I think carrier name is centered between the status bar icons and the left screen edge.

Didn't really disturb me, honestly. :D

I have heard several people telling me its smoother now.. So I think I'll stick with SaberMod in future. :good:

Thanks for the feedback! :)
[Sony Xperia T, TL, TX, V] merlin_zaraza:
Cool.

Are there OTA updates? Any plans?
[Sony Xperia T, TL, TX, V] WhiteNeo:
Maybe in a few weeks, but for now I'm going to stick with manual updates :)
[Sony Xperia T, TL, TX, V] WhiteNeo:
Wow.. 250 rom downloads in less than 20 hours? Are you kidding me? :D

Thanks for your support, everyone! :laugh:
[Sony Xperia T, TL, TX, V] pakroid:
1. Clean flashed 12.1, gapps for 5.1, su

2. Resized the internal storage to 4Gb.

3. Changed all available partitions to f2fs.

4. Restored all apps via Titanium Backup, at this time error prompt of "Google store force closed" keeps popped up (and lately I found that TB's latest update fixed this issue).

No bootloop and everything run just fine, except the sensor problem.

No significant battery drain like the previous cm12 neo version, which eat a lot of battery by "mobile radio active". But the battery life did not as good as I was using stock 4.3...

One issue I noticed is at the battery info screen, Wifi always showed "on" even if I manually turned it off. Of course I did not chooses the "scanning always available" option.
[Sony Xperia T, TL, TX, V] iLitvinov:
Here's my XV setup: your CM12.1 ROM (clean install without formatting internal storage and MicroSD), F2FS, implemented sensor file from your CM12.0 ROM. No bootloops so far.
[Sony Xperia T, TL, TX, V] awerqw22:
Bootloop when rebooting after installing xposed.
[Sony Xperia T, TL, TX, V] elikcandy:
Clean install

Using F2FS

I had installed all my apps, rebooted phone 2 or 3 times and then got bootlop.
[Sony Xperia T, TL, TX, V] WhiteNeo:
Thanks for your replies!

Let's change this question.... Did anyone encounter a bootloop using EXT4?

The file fixes all sensors, so yes. :good:
[Sony Xperia T, TL, TX, V] emartino:
I am still using EXT4 and I have no bootloops.
[Sony Xperia T, TL, TX, V] Tommy_PL:
I did exactly the same 12.1 install with EXT4 (instead F2FS) - no bootloop so far ... Still testing, "rebooting / powering off and on" like crazy after every install. Will report later if something goes wrong. But after 3 hrs no bootloop. No charger has been connected yet to unit.
[Sony Xperia T, TL, TX, V] SSVsSunSt:
No bootloop on ext4 so far :)
[Sony Xperia T, TL, TX, V] saved-j:
no bootloops on ext4 CM12.1

I sign onto that - no problems with 5.1 with ext4 under cm12.1
[Sony Xperia T, TL, TX, V] bse4792:
hi WhiteNeo

is it in anyway possible to add this http://xdaforums.com/showthread.php?t=2712253 to the CM12/12.1

it's a way to get much more space for apps, by repartition the internal SD card.
[Sony Xperia T, TL, TX, V] emartino:
Oh yes, any way to increase the internal storage would be great! Especially with a convenient way (installer, flashing, ...). With my luck to forget an important letter in a command line tool and on such critial areas I would not do this manually...
[Sony Xperia T, TL, TX, V] WhiteNeo:
My ROM is compatible with this mod, but you gotta follow this guide manually. Can't be added to the ROM itself.
[Sony Xperia T, TL, TX, V] banciii:
Sorry, it's a GApps (probably a Google App [Search]) update, not a CM one. With earlier GApps, the search bar stays full white. :P

---------- Post added at 10:55 AM ---------- Previous post was at 10:39 AM ----------

If you don't mind, I would recommend to follow [MENTION=2328357]colonel_lp[/MENTION]'s guide from that thread: Post #85
[Sony Xperia T, TL, TX, V] MESA:
Hello. Yesterday I clean installed cm12.1 again and its very fast. The phone was in charge all night and now i found the phone rebooted asking for pin. Strange will see what happens with next charging. :) For me cm12.1 is faster than 12 and that is good. :)
[Sony Xperia T, TL, TX, V] lcarolo:
Using your CM12 and it works very fine ! thanks ! (when i have some time i will try CM12.1)

I would like to know if it is possible to have the "pocket mode" feature like in kitkat ? (screen switch on automaticaly when pull out of pocket), maybe it is not yet implemented in lollipop ?

I know there is the "gravity screen" app, but it's not working as fine as the base function in KK...

Keep going that great work !
[Sony Xperia T, TL, TX, V] Rindar:
Okay, something's weird here.

I'm using latest CM12 5.0 (final). And managed to get a bootloop.

Phone was working just fine for a few days after (dirty) flashing that update, during which I didn't tweak anything.

My best guess is F2FS update.
[Sony Xperia T, TL, TX, V] pakroid:
After a few day of clean install of CM12.1, I got boot loop finally...

I guess it was caused by the failure of f2fs, since I can't even backup the data partition at recovery.
[Sony Xperia T, TL, TX, V] Kureiji:
Can I say that CM12.1 works fine with clean install + ext4 + sensors.msm8960.so from CM12 zip? :D:D:D
[Sony Xperia T, TL, TX, V] emartino:
Yes, this seems to be the pattern...
[Sony Xperia T, TL, TX, V] banciii:
Well, if I install only a few user apps (12, not 79 as I usually do), 5.1 is indeed very fast and smooth (with F2FS) without any bootloop (so far). :)
[Sony Xperia T, TL, TX, V] WhiteNeo:
It seems that F2FS on data partition is the reason for the bootloop.

Probably CM12.1 is just not fully compatible with that one.

I think I will remove this entry from fstab in next build, so people don't run into this issue anymore.

This will disable mounting of F2FS formatted data partitions..

You people might help me testing and verifying this fix indeed works.

Just follow the instructions in OP on how to revert to EXT4 - and only do so for data partition. :)

I hope that's the fix..

Will do some testing with old F2FS sources.. Maybe those are stable on 5.1
[Sony Xperia T, TL, TX, V] WhiteNeo:
Alright. Done with experiments. :D

Reverting the updated F2FS sources apparently fixes the bootloop issues. :good:

Expect a fixed build tomorrow :)
[Sony Xperia T, TL, TX, V] zirhaze:
I am having issues with "Cell Standby" draining my battery. Haven't done anything whole morning and day with phone (probably 6 hours phone has just been sitting there) and battery is at 85%, which should not happen in my opinion... Anyone else has this problem or is there a fix of somekind to this problem :o?
[Sony Xperia T, TL, TX, V] mirhl:
Use betterbatterystats or wakelock detector to find the right bad process.

Logcat (radio and/or main) may also help
[Sony Xperia T, TL, TX, V] WhiteNeo:
Here we go! Fixed and stable CM12.1 is online! :)

I've rebooted my phone like 20 times in the last hours, to check for random bootloops. None appeared.

So, you can safely use F2FS with this ROM now. :good:

Also added my previous sensors fix.

Enjoy!
[Sony Xperia T, TL, TX, V] SSVsSunSt:
With repo update, I hope?
[Sony Xperia T, TL, TX, V] banciii:
He always do, but if u r not sure, just check the OP's changelog. ;)
[Sony Xperia T, TL, TX, V] colonel_lp:
Hey, how is the xposed 5.1 working with the latest update?
[Sony Xperia T, TL, TX, V] banciii:
It works fine for me (with those very few modules, which are compatible with the latest xposed and does not cause bootloop :P)
[Sony Xperia T, TL, TX, V] lesnoychinik:
Thank you Neo to work! Everything works fine, just have one - I can not do bacup, like starting to do, and then restarts TWRP, create a folder backup, but it is empty ...
[Sony Xperia T, TL, TX, V] pakroid:
Same here...

Thanks for Neo's great work anywyay ;)
[Sony Xperia T, TL, TX, V] hondza01:
fixes as backup TWRP ?

Thanks WhiteNeo accepted the functionality of the latest version , graphical errors in the calendar after several startups lost . sensory function , it is necessary to clean install , upgrade did not remove the previous errors. Will update fixes as backup TWRP ? Then try xposed ...