Hi
I broke my usb charging port accidentally
Fortunately, i have battery charger with two batteries
Now, I have one question can I flash kernels from the phone without the computer?
oh well... he is actually right.. if he had time don't you think you would have seen the fix? he isn't keeping fixes for himself obviously as you can see... just be patient... he is doing his absolute best! CheersThis isn't the place for begging. If you want something fixed then fix it yourself or be patient.
I had 0 free time to work on semc since last build, plus debugging these issues is becoming very hard
because the wifi/bt drivers for these devices are no longer actively developed.
The user complaints, lack of development and the whole sdcard corruption mess are making me
want to stop public releases on xda and just maintain the source trees.
Not sure that my method have enough science behind it to be called "testing" I use YouTube app and MX Player for the comparison.
With ART runtime instead of Dalvik we freed some of CPU resources, but with /data partition on a sd card it's no use because most of the time CPU is waiting for io.
- cm11: both apps are silky smooth, video seeking is fast (less that 1s);
- cm12: YouTube app- video playback stutters (at start and while playing), takes more time to load. Seeking time in both apps is more than 1s;
- cm13: slightly better than cm12 - video stutters only at the beginning, seeking time is as good as in cm11.
cm13 uses more RAM for system apps and makes a heavy use of zram. My guess that when you doing something in the browser the cpu constantly compresses/decompresses pages. And when you playing videos there are more strain on the cpu -> more heat...
P.S. Playing videos in browser is not for our devices. I suggest you to use YouTube app, or better NewPipe (thanks to @blueman24).
This isn't the place for begging. If you want something fixed then fix it yourself or be patient.
I had 0 free time to work on semc since last build, plus debugging these issues is becoming very hard
because the wifi/bt drivers for these devices are no longer actively developed.
The user complaints, lack of development and the whole sdcard corruption mess are making me
want to stop public releases on xda and just maintain the source trees.
Since cm13 isnt stable enough for some ppl, supporting cm11 for a while with cve updates is a good choice. We already dropped cm12/12.1 to have more time for cm13.What do you think about dropping CM11 development? Isn't it 'good enough' to make a final build? This would save you some time.
This isn't the place for begging. If you want something fixed then fix it yourself or be patient.
I had 0 free time to work on semc since last build, plus debugging these issues is becoming very hard
because the wifi/bt drivers for these devices are no longer actively developed.
The user complaints, lack of development and the whole sdcard corruption mess are making me
want to stop public releases on xda and just maintain the source trees.
Man.. you quoted a wrong person.DAMN straight bro.
What do people expect when running MM on 5 year old phones?
If you are still using one of these Legacy Xperia's then you can use KK CM11. It works like butter and is still supported. If you flash CM13, then you should be prepared to live with bugs.
Thanks to everyone involved in LX. Let it be know that your work is really appreciated.
Made some changes to make my post clear!
How do i get the most out of XPERIA PLAY regarding feature completeness and multitasking?
What about swapfile/swappartition?
Better go with CM11 as it uses less RAM?
On Xperia Play i recommend you to use vanilla firmware with working slide-out.
Using LX on this device is pointless, it's like using rom that doesn't support qwerty slider on xperia pro.
(Don't get me wrong, i'm fully support LX, but not on that device)
Anyone help me!!
I flash boot.img from zip & success.
But when I choose apply update from adb in recovery, I can't flash the zip.
They say ERROR : PROTOCOL FAULT (NO STATUS)
What should I do??
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]