{Neo/Neo V}[DEV][KitKat 4.4.4][CM11.0] LegacyXperia

Status
Not open for further replies.
Search This thread

aliendna51

Senior Member
Jul 20, 2011
235
16
Heraklion
Thanks! Now I know a lot more about how memory works. I'll try lagfix when I notice lagging again ;)

Any ideas on the sound problem I described?

Ah, also the browser has this typical kitkat lag. There's a fix somewhere (I think carbon rom has implemented it). Could that be included in the next version?

Sent from my MT11i using XDA Free mobile app
 
Last edited:

aliendna51

Senior Member
Jul 20, 2011
235
16
Heraklion
Thanks! Now I know a lot more about how memory works. I'll try lagfix when I notice lagging again ;)

Any ideas on the sound problem I described?

Ah, also the browser has this typical kitkat lag. There's a fix somewhere (I think carbon rom has implemented it). Could that be included in the next version?

The mp3 problem is quite annoying.. Does anyone have a clue?

Edit: mp3s work with mplayer (which uses its own decoder) so the problem definitely has to do with the embedded mp3 decoder of Android. Any clues after that?

Sent from my MT11i using XDA Free mobile app
 
Last edited:
  • Like
Reactions: tinyXperia

nikhildangui

Senior Member
Mar 7, 2013
78
49
Goa
Thanks! Now I know a lot more about how memory works. I'll try lagfix when I notice lagging again ;)

Any ideas on the sound problem I described?

Ah, also the browser has this typical kitkat lag. There's a fix somewhere (I think carbon rom has implemented it). Could that be included in the next version?

Sent from my MT11i using XDA Free mobile app

u tried that app lagfix?? i installed in on my LX CM11 Xperia Neo V and it gives error :( Not Supported :(

fstrim: FSTRIM: Not a typewriter for all 3 , that is /system /data and /cache

But in the end it says Hurray its done....reboot...

is it working or not ?? can anyone plz help
 
  • Like
Reactions: sknerus75

aliendna51

Senior Member
Jul 20, 2011
235
16
Heraklion
u tried that app lagfix?? i installed in on my LX CM11 Xperia Neo V and it gives error :( Not Supported :(

fstrim: FSTRIM: Not a typewriter for all 3 , that is /system /data and /cache

But in the end it says Hurray its done....reboot...

is it working or not ?? can anyone plz help

It says it's not supported in my Neo V either.. It says it could be a kernel problem, so I don't know

Any opinions on that sound problem of mine? It's really frustrating..

Sent from my MT11i using XDA Free mobile app
 

neng24

Senior Member
Jan 5, 2014
135
25
It says it's not supported in my Neo V either.. It says it could be a kernel problem, so I don't know

Any opinions on that sound problem of mine? It's really frustrating..

Sent from my MT11i using XDA Free mobile app

im using Device Controller.it has fstrim feature.download it from playstore.

Sent from my MT11i using XDA Premium 4 mobile app
 

mikeioannina

Recognized Developer
Mar 22, 2011
1,949
26,986
Ioannina
Lenovo P2
Xiaomi Mi Mix 2
It says it's not supported in my Neo V either.. It says it could be a kernel problem, so I don't know

Any opinions on that sound problem of mine? It's really frustrating..

Sent from my MT11i using XDA Free mobile app

im using Device Controller.it has fstrim feature.download it from playstore.

Sent from my MT11i using XDA Premium 4 mobile app

Our devices use MTD storage which doesn't support fstrim. You are wasting your time.
 

neng24

Senior Member
Jan 5, 2014
135
25
ooohhh!!!thanks for the information mate:D

Sent from my MT11i using XDA Premium 4 mobile app
 
Last edited:

aliendna51

Senior Member
Jul 20, 2011
235
16
Heraklion
Thanks indeed Mike! That explains it. If we're not here to learn we're here for nothing ;)

Any ideas on that mp3 decoding problem of mine??

Sent from my MT11i using XDA Free mobile app
 

mikeioannina

Recognized Developer
Mar 22, 2011
1,949
26,986
Ioannina
Lenovo P2
Xiaomi Mi Mix 2
Thanks indeed Mike! That explains it. If we're not here to learn we're here for nothing ;)

Any ideas on that mp3 decoding problem of mine??

Sent from my MT11i using XDA Free mobile app

I use a build with the latest sources at the moment and don't have issues.
Other people who build from source also haven't noticed issues with MP3 files since a long time.

I really want to release some new builds but I didn't find the time for it yet.
 

mikeioannina

Recognized Developer
Mar 22, 2011
1,949
26,986
Ioannina
Lenovo P2
Xiaomi Mi Mix 2
## Nightly build 20141006 - cm-11.0
* Latest cm11.0 changes
* Replace kernel as3676 LED driver with the stock ICS one. Includes the following bugfixes:
- Torch not blinking together with notifications on urushi
- Keyboard not blinking together with notifications on mango/iyokan
- Music light should be working again on coconut
- Users are able to tweak the LED max current again, like in previous android versions and early nAa kernel versions
- Fading led effect is removed since the old driver doesn't support it (at least not yet)
- Removed ugly camera hacks for urushi that fixed torch when using the newer led driver
* Removed button backlight indication while booting in recovery - only the notification LED is used now
* Removed solid blue notification LED while in recovery
* Disabled WiFi Direct support - mogami
* Fixed WiFi hotspot - mogami
* Testing SDIO changes from stock kernel that could improve WiFi - mogami
* Included nAa spi_qsd workarounds for cy8ctma300_touch - zeus
* Testing fix for qdsp5v2 crashes on certain operations (like using Viber)
* Security fix for CVE-2012-6657
* Increased ZRAM swap size to 192MB
* Set background app limit to 16
* Set background services limit to 8
* Disabled stereo recording flag again on coconut to fix speaker issues
* Updated MMC kernel drivers
* Camera: set semc-focus-area correctly
* Added scrolling to the light picker dialog to fix issues on mdpi devices

Builds will roll alphabetically for all devices until tomorrow
 

simono_pl

Senior Member
Jun 7, 2009
897
312
What GAPPS should I download except Universal if I do update from previous build ROM and GAPPS?
Download GApps Minimal Edition 2014-10-05 GPS 030 [Universal DPI] (36 MB)
Download GApps Minimal Edition 2014-10-05 GPS 032 [160 DPI] (24 MB)
Download GApps Minimal Edition 2014-10-05 GPS 034 [240 DPI] (26 MB)
Download GApps Minimal Edition 2014-10-05 GPS 036 [320 DPI] (27 MB)
Download GApps Minimal Edition 2014-10-05 GPS 038 [480 DPI] (27 MB)
Download GApps Minimal Edition 2014-10-05 GPS 070 [x86 Services] (38 MB)

Edit:
I found needed information. Now I know that I should download GAPPS for 240 DPI.
 
Last edited:
  • Like
Reactions: cross22

ankurvij

Senior Member
Dec 13, 2011
84
24
INDIA
Is the Download server down? or it;'s just me :crying:

Not Found

The requested URL /devs/LegacyXperia was not found on this server.

Apache/2.2.15 (CentOS) Server at s.basketbuild.com Port 443
 
  • Like
Reactions: hooooossamq
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 201
    eiOWgKr.png


    Code:
    [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]

    This is an unofficial build of CM11.0.
    This is an attempt to stay close to official cm11.0 and not make crazy hacks to make things working.

    This is a pure CM build, only contains official CM features. I will not add any other external feature/app/etc.


    For an up-to date working/not working list, bug tracker, useful guides & FAQ, visit our website:
    http://legacyxperia.github.io


    WARNING: This ROM uses a modified internal memory layout.
    Our /system partition is originally 400MB but this space is not enough for a fluid kitkat experience and a full installation with proper google apps.
    Our /cache partition is also too small to fit art-cache when we enable the ART runtime. We originally had 100MB /cache but art-cache needs ~150mb of free space.
    I have repartitioned the internal memory layout, giving:
    450mb in /system
    469,5mb in /data
    8mb in /cache

    If you want to use this ROM you will always have to use the included kernel or use a kernel that includes the layour changes. Bug reports with non-standard kernels will be ignored.
    You will have to wipe the device and make a clean install.
    You cannot restore nandroid backups from previous android versions or restore nandroid backups from this ROM to other ROMs that don't use the new partition layout since you risk corrupting the data.
    I suggest to use Titanium Backup, Helium or any other similar app to backup your data if you really need to.


    Requirements:
    * Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
    * LT15i (Arc) users need to flash LT18i (Arc S) ftf
    * MT15i (Neo) users need to flash MT11i (Neo V) ftf

    Steps required for correct installation (order is important):
    1: Flash boot.img in fastboot & reboot into recovery
    1.1 (optional): If the device is not booting, reboot to bootloader again and run:
    fastboot erase system
    fastboot erase userdata
    2: Enter recovery, go to mounts and storage
    3: Format /system, then /data and then /cache (Important step!)
    4: Flash update zip
    5: Flash gapps (recommended package is the one provided in the link below)

    Steps 1.1, 2 & 3 are not needed when you install new cm11 nightlies on top of older cm11 builds in the future

    If you want to return to a ROM that doesn't use the new partition layout, you need to follow the above steps again (only replace boot.img & update zip with the ones you want to use).

    How to build:
    [GUIDE][DEV] How I build my own CM11.0 test builds

    Changelog:
    Release/nightly changes

    Working/Non-working list
    CM11.0 with new kernel 3.4 status

    Downloads:
    https://s.basketbuild.com/devs/LegacyXperia
    PLEASE DON'T MIRROR OUR UPLOADS

    Recommended Google Apps:
    Google Apps Minimal Edition

    KCzv621.png


    NOTE:
    Following xda's rule #12 spirit: If you are developing something that is based on my work, you MUST first seek my permission, you must add my name in the credits and you must add links pointing to my original thread and to my github sources.
    Breaking this rule will lead me to report the thread to the moderators.


    NEW!!! BUG Tracker
    If you want to help fixing those bugs, please report the bugs in the bug tracker. Thanks!
    Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.

    XDA:DevDB Information
    LegacyXperia, ROM for the Sony Ericsson Xperia Neo

    Contributors
    mikeioannina, nobodyAtall, pcfighter, Blefish
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Latest version of official ICS firmware: 4.1.B.0.587 or the latest supported baseband: 8x55A-AAABQOAZM-203028G-77
    Based On: CyanogenMod

    Version Information
    Status: Beta
    Current Beta Version: nightly 20140702
    Beta Release Date: 2014-07-02

    Created 2013-11-27
    Last Updated 2014-09-06
    77
    Thread closed

    Since people don't learn how to read, I can't handle this situation anymore.

    I come in the thread and instead of finding something useful, there are only the same posts repeated again and again, ignoring my posts and xda rules.

    Thread locked until further notice.
    68
    New build coming - READ THE WHOLE POST

    ## Alpha 2 build 20131210 - cm-11.0
    * Latest cm11.0 changes
    * Updated to android 4.4.1
    * Repartitioned internal memory layout
    * Fixes:
    - Battery indicator alignment
    - PIN/PUK layout
    - Lockscreen clock layout
    - Camera flash in photo mode (urushi)
    - Music distortion on lock/unlock sounds
    - Disable back key on incoming call
    - Gesture typing
    * Many bugfixes from CM upstream
    * Many bugfixes/small features ported from cm10.1/cm10.2
    * Features:
    - APN Settings
    - Mass storage settings
    - DeskClock: Add increasing volume option for alarm clocks
    - DeskClock: Profile support
    - DeskClock: Add back user-defined world cities
    - "Clear all" button on recent apps
    - Hardware key settings
    - Lockscreen shortcut configuration
    - 2G/3G toggle
    - Circle battery
    - Battery with percentage
    - Noise suppression
    - Allow some customization in Launcher
    - Add cLock settings back to lockscreen settings
    - Allow configuration of wake on plug behavior
    - Allow configuration of country code for wifi
    - Display rotation settings
    - WhisperPush secure messaging
    * Temporarily disabled low ram config to enable 4.4 UI features
    * Disabled animated bootlogo to free some /boot partition space
    * Added all resolutions in camera
    * Enabled Performance Profiles
    * Enabled zRAM by default
    * Testing a SYM key change on mango & iyokan

    Builds will roll alphabetically for all devices until tomorrow
    Gapps package is also updated, please redownload it.


    WARNING: This update introduces a modified internal memory layout.
    Our /system partition is originally 400MB but this space is not enough for a fluid kitkat experience and a full installation with proper google apps.
    Our /cache partition is also too small to fit art-cache when we enable the ART runtime. We originally had 100MB /cache but art-cache needs ~150mb of free space.
    I have repartitioned the internal memory layout, giving:
    450mb in /system
    469,5mb in /data
    8mb in /cache

    dalvik-cache/art-cache is now stored in /data partition
    We still have to use the lite gapps that are provided in LX basketbuild folder.

    If you want to use this ROM you will always have to use the included kernel or use a kernel that includes the layour changes. Bug reports with non-standard kernels will be ignored.
    You will have to wipe the device and make a clean install.
    You cannot restore previous nandroid backups or restore nandroid backups from this ROM to other ROMs that don't use the new partition layout since you risk corrupting the data.
    I suggest to use Titanium Backup, Helium or any other similar app to backup your data if you really need to.


    A note to other devs that use LX as a base to their KitKat ROMs: If you decide to modify the partition layout, please use the same layout in your kernel so people will be able to backup/restore nandroid backups between 4.4 ROMs and they won't need to wipe the whole device when they switch between 4.4 ROMs.


    Requirements for the new partition layout:
    * Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
    * LT15i (Arc) users need to flash LT18i (Arc S) ftf
    * MT15i (Neo) users need to flash MT11i (Neo V) ftf

    Steps required for correct installation (order is important):
    1: Flash boot.img in fastboot & reboot into recovery
    1.1 (optional): If the device is not booting, reboot to bootloader again and run:
    fastboot erase system
    fastboot erase userdata
    2: Enter recovery, go to mounts and storage
    3: Format /system, then /data and then /cache (Important step!)
    4: Flash update zip
    5: Flash gapps

    If you want to return to a ROM that doesn't use the new partition layout, you need to follow the above steps again (only replace boot.img & update zip with the ones you want to use).

    Only use the thread for development discussion, anything else belongs to the Q&A thread.
    61
    ## Alpha build 20131127 - cm-11.0
    * Latest cm11.0 changes
    * Initial KitKat 4.4 build

    Builds will roll alphabetically for all devices until tomorrow

    Please do not spam the thread with "thanks" posts.
    Only use the thread for development discussion, anything else belongs to the Q&A thread.