{Mini/MiniPro/Active/Live}[DEV][KitKat 4.4.4][CM11.0] LegacyXperia - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

{Mini/MiniPro/Active/Live}[DEV][KitKat 4.4.4][CM11.0] LegacyXperia - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
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 Mini, Mini Pro, Active
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

Reserved

## 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.

Nice Working / Not working list for a first alpha built! :good:

Please respect the developers wishes and do not post "Thank You" and "waiting" ect. in the thread, if you wish to say thanks simply click the thanks button.
Make sure to read all posts including post#3 where Mike says:
mikeioannina said:
Please do not spam the thread with "thanks" posts.
Only use the thread for development discussion, anything else belongs to the Q&A thread.
Click to expand...
Click to collapse
Thread cleaned

Such a great work!
is there any hope to have ART working in our phones? any goods about having ART in our device or it doesn't make much difference for us?
(sorry for too many "?" )

Mobile data now working
First of all thanks for bringing KitKat to our devices
Now to the issue, everything is working fine except mobile data. The mobile data connection checkbox is checked and to be on safer side roaming checkbox is also checked, still no internet connection or any E or H sign on Network icon
EDIT::
Toggle network mode to 2G and 3G, 4 to 5 times then automatically seems to work, I dont know what triggers this
anyway now all things are workind and is buttery smooth

deamonoid said:
First of all thanks for bringing KitKat to our devices
Now to the issue, everything is working fine except mobile data. The mobile data connection checkbox is checked and to be on safer side roaming checkbox is also checked, still no internet connection or any E or H sign on Network icon
After that i checked the APN it was there and enable, then I manually added the APN configuration still no luck.
This problem is not mentioned in Working/Not working list, so thought this would be a issue.
Any more I can do to help you solve this problem, then it will be my pleasure :highfive:
and my device is coconut(wt19i)
Click to expand...
Click to collapse
have you try to reinstall the rom with a full wipe once again ?
will report you as soon as possible, but i though the data connection normal and had no issue.

installed
okay, I installed the ROM, its very smooth and looks awesome
But since i got an MDPI LWW, layout bugs are there (already reported by mike)
rest is fine!

The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now

i have xperia ray, what about perfomace? better than 4.3 ?

Why??
No USB mass storage. But why?

Bug in recovery
Hey Mike I found a bug in the CWM recovery while installing the kk-gapps the installation blue bar went outside than the defined space...
And the other thing is not a bug but a concern where is the screenshot option....

good
Arbelzapf said:
The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now
Gesendet von meinem NookColor mit Tapatalk
Click to expand...
Click to collapse
I flashed it in my smultron and it boots good and works well. Still testing!! the 4.4 launcher doesnt have swipe left to google now even it is ON in google settings.
---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------
siddharthnair96 said:
Hey Mike I found a bug in the CWM recovery while installing the kk-gapps the installation blue bar went outside than the defined space...
And the other thing is not a bug but a concern where is the screenshot option....
Click to expand...
Click to collapse
I had this bug too. In CWM the blue bar went beyond the screen and it stayed as "cleaning up and setting the meta data" for a long time, and it got complete. I have never encountered this before.

hi mike thanks sooo much for rom
for now all things runs cool and superfast
i have 2 questions:
1.where is the brighness control in status bar??i mean with scrolling in there?!
2. i have this bug in cm10.2 too
in phone app whene i export my contacs from sd card when i go to phone app it gives me FCs
in cm10.2 i found a way too fix it:i go to phone settings and disable the auto complete dialing .
but in cm11 there is no option like that and at every luanch it gives me FC(
plz help meeeee

Link2sd problem
Link2sd not working, Link2sd can easily link the internal app but when opening the app it is force closing, when I checked the app status the library file was not linked. I then again linked the file, but no use the app is still force closing
Is Link2sd supported for Android 4.4?
I will post logcat on bugtracker
Sent from my Xperia Live with Walkman using Tapatalk

Link2SD works but...
deamonoid said:
Link2sd not working, Link2sd can easily link the internal app but when opening the app it is force closing, when I checked the app status the library file was not linked. I then again linked the file, but no use the app is still force closing
Is Link2sd supported for Android 4.4?
I will post logcat on bugtracker
Sent from my Xperia Live with Walkman using Tapatalk
Click to expand...
Click to collapse
Same here mate... Link2SD works with 4.4 Kitkat... i think its a problem with some other compilation... Let Mike look into it I guess he may be able to do something... When i open the app it works but after linking Super Backup to the SD card Super Backup Force Closes every single time.....

Arbelzapf said:
The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now
Gesendet von meinem NookColor mit Tapatalk
Click to expand...
Click to collapse
Make sure you've flashed the right kernel (which is included in zip).

mihaum said:
Make sure you've flashed the right kernel (which is included in zip).
Click to expand...
Click to collapse
Pardon my ignorance. My Mini is a secondary phone for toying around with and I don't use it that often. So I'm not used to the whole "flashing kernel first"-thing which I haven't seen on other devices before.
Anyway, it's right in the OP which I failed to study carefully enough, so sorry for being stupid.
EDIT: Flashed successfully, obviously

@Arbelzapf, no problem - we're just humans after all

Related

[ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Grouper

Ohai! Guess I'll jump in here.

Yup... Spoiled by the participating...

Caution - SDcard directory changes with 4.2 installation
For those of you that are new to 4.2 releases, be aware that installing and running this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash and start this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Edit: Installed the latest version (as of 12/17) of CWM and it.too was unable to find my nandroid backup once it was moved to the /sdcard/0 directory by the 4.2 installation process. To restore my old rom I had to do a clean install, then install ES file Explorer, move the clockworkmod directory to /sdcard/ and THEN restore.

freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
You need to upgrade your recovery to the latest cwm or twrp. The issue has been fixed since 11/16

freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. (I haven't tried the latest version of CWM.)
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy

The slider in the Quicksettings menu for brightness is very laggy. Volume seems fine though. Also, my battery meter in Quicksettings sometimes says 0%, even though I'm at 97%.

runandhide05 said:
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
Click to expand...
Click to collapse
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.

Thanks, will give it a try.

freecity said:
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Click to expand...
Click to collapse
Also note a full wipe is a MUST coming from any other ROM or even eos3
And I didn't read it as implying anything.
Just be sure to update recovery
All good Buddy

Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium

TheUndertaker21 said:
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
In a way.. It has the option to put the soft keys in the left side like tab ui but keeps the top status bar
Sent from my Nexus 7 using Tapatalk 2

Haha that'd do. Thanks for reply.
Sent from my Nexus 7 using xda premium

That's pretty sweet.

New build out. Eos is on a roll

Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.

demandarin said:
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
Click to expand...
Click to collapse
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2

DJLamontagneIII said:
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yep..dirty flashed rom an reflashed gapps. All running well so far.

Unless instructed otherwise from eos4 nightly to nightly a dirty flash is fine.
Also the latest update fixes ALOT of the third party apps FC'ing.
So put firefox, kindle, and many more on the problem squashed list.

Anybody having issues using the latest nightlys with custom kernels? I tried using Franco's kernel and I am unable to install paid apps with it. I get the USB storage error.

[ROM][GT-I9190][Official][4.4.4] CyanogenMod 11.0 for S4 Mini 3G (EOL)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING! This ROM is for the GT-I9190 variant only!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Q/A thread:
http://forum.xda-developers.com/showthread.php?t=2558702
Please use the above unless you have something development-related to contribute here. Thank you.
Code:
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Screenshots:
View attachment 2439447 View attachment 2439448 View attachment 2439449
CM-11.0 Install Guide
Note: CM for Galaxy S4 Mini is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Download CM-11.0 and gapps-jb zips and put in /sdcard
Nightly: http://get.cm/?device=serrano3gxx&type=nightly
UPGRADE REQUIRED
gapps version 20140606
MD5SUM: d840e20fba6f0e2b85d1aebe493a88fa
Please verify the md5sum to be sure you got the right one.
Before you install CM-11.0: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into ClockworkMod recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use ClockworkMod Recovery.
Warning: Only use this recovery to flash CM-11.0. Otherwise, you risk bricking your phone!2
Wipe data and cache.
Flash cm-11*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM11.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM11.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM11.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Useful Links:
BBQLog changelog
serrano3gxx CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR NIGHTLY BUILDS!
Source repos for serrano3gxx
https://github.com/CyanogenMod/android_device_samsung_serrano3gxx
https://github.com/CyanogenMod/android_device_samsung_serrano-common
https://github.com/CyanogenMod/android_device_samsung_msm8930-common
https://github.com/CyanogenMod/android_kernel_samsung_msm8930-common
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/serrano3gxx
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/serrano-common
Other Issues?
Use this for obtaining logs.
For nightlies, bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Credits:
Epic Touch CM Team for the install instructions
Everyone that donated beers
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

Can't wait to try it. The new cwm link is still down though.
I don't even know what's new or improved about kitkat. Just a sucker for version numbers.

Does it support 4G?
Sent from my GT-I9195 using XDA Premium 4 mobile app

Kit kat is working, yay!!! Thank you, thank you, thank you!
For the first nightly it's actually super stable, haven't had a single reboot since last night when i installed it.
Only thing missing is the trebuchet options, like removing the search bar, and choosing which screen is your default home screen, but im sure thats all pretty much in development.
Performance is also excellent, 20900 antutu. Feels as buttery smooth as ever.
Sent from my GT-I9190 using xda app-developers app
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
imputazz said:
Does it support 4G?
Sent from my GT-I9195 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check out the 9195 cm11 thread, you are in the 3g thread
Sent from my GT-I9190 using xda app-developers app

BushTechy said:
Only thing missing is the trebuchet options, like removing the search bar, and choosing which screen is your default home screen, but im sure thats all pretty much in development.
Click to expand...
Click to collapse
Actually, if you press menu button and select settings, you can change this there.

arco68 said:
Actually, if you press menu button and select settings, you can change this there.
Click to expand...
Click to collapse
I have pretty much scrutinized all the settings, i don't see it.
When u press menu and settings in the home screen the menu below appears, cant remove the search bar there, nor choose which tile is your default home screen.
Sent from my GT-I9190 using xda app-developers app
Edit: cant seem to upload the screenshot, but its a google menu, with only google app and search settings, but not what i have mentioned

Sent from my GT-I9190 using xda app-developers app

BushTechy said:
I have pretty much scrutinized all the settings, i don't see it.
When u press menu and settings in the home screen the menu below appears, cant remove the search bar there, nor choose which tile is your default home screen.
Sent from my GT-I9190 using xda app-developers app
Click to expand...
Click to collapse
You need to be using the launcher3 for those settings, the other launcher is googlish.

@arco68
I have just reflashed the rom and gapps, "launcher3" doesn't appear to be on the gti9190s cm11. In the App manager under all apps tab there is only "launcher", can anybody else with 9190 confirm this?
Sent from my GT-I9190 using xda app-developers app

So i managed to get the launcher going with some help
Found a minor bug, if you remove an app from your home screen, the search bar turns into the word "remove" in red where you can drop the app, but if you disable the search bar, then that word in red is also removed, and you cannot get apps of your homescreen until you have re_enabled the searchbar
Sent from my GT-I9190 using xda app-developers app

First impressions on 4.4.1
It's marvellous so far. Less random reboots and improved battery life. Minor bugs such as camera freezes. But not so important and will definitely be handled by this awesome team (@arco68 & the company).

will this rom support dual sim variant???
or any way to use it on my dual sim variant??

pankaj_GB said:
will this rom support dual sim variant???
or any way to use it on my dual sim variant??
Click to expand...
Click to collapse
Cyanogen mod dont support any dual sim phone...

Gapps package in first post updated.

Downloadinggggggg.............

New gapps overwrites launcher3, had to restore mine from back-up, can anybody confirm this?
Sent from my GT-I9190 using xda app-developers app

there is some weird pixellation in video mode in the camera ,
i hope arco is aware of that

step-2 said:
there is some weird pixellation in video mode in the camera ,
i hope arco is aware of that
Click to expand...
Click to collapse
Same here. But the resulting recorded video is as it should be, non-pixelated.

today swithed cm11. smooth, especially after switching art. but cm is not what it had been 1,5 years ago. a lot of own approaches and some unnecessary apps one should get rid off.
would very appreciate if someone would provide slimkat nightlies... black apps, slim, additional settings as touch a sensistivity are great features normal cm is missing.
nevertheless most is working fine, just some issues with flash and torch at this development stage. all else seems to be quite good. - thanks for sharing!
Sent from my GT-I9195 using xda app-developers app

{[REQUEST] Interface options
Hi guys,
can i first say, great work. And if i knew how to do this myself i would.
Just wondering if you could put in an option to hide the clock in the top right corner... like the option in the interface to hide the battery icon.
Also need an option in the camera to use external SD card for main storage. Have tried 3 other camera apps from the play store but none have this option either.
Keep up the fantastic work.:good:

[SCRIPT] [tool] [windows] [4.4] convert any rom to full f2fs

This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*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. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work

Screenies
Screenies atlast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Excellent test on
Big thanks

c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.

belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!

belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.

c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.

hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1

belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm

I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX

fantastic job, works great with cm11-m6,very faster

Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.

tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes

NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!

callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!

Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?

Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk

work in 4.4.3?

Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?

@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)

[ROM][LP] [5.1.1-r4][Unofficial] PACMAN rom [2015-07-04]

Hello everybody,
I've just compiled PACMAN-ROM for my new Z3C. Current version is PAC-LP MR1 Beta2.
Device trees are CyanogenMod's so probably all device specific CM-bugs will be there too.
The boot.img inside the zip contains CM 12.1 kernel and "Cyanogen Recovery" (no backup right now!).
For alternative recoveries/kernels scroll down to "TESTED - WORKING"...
If the rom is stable for daily use (as I hope) I'm gonna build newer version periodically (depending on PAC & CM updates).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDITS:
2015-07-09:
i've been trying to get rid of the latest problems, i.e. crashing android browser, opera browser, voice recorder and google apps (if installed). tried 4 or 5 builds in the meantime. i've got no idea why and not the skills to search in log files.
if anyone likes to test and find out, i uploaded version from july 4th.
2015-06-25:
New Version - updated CM & PAC sources. Some new PAC features there!
Version is PAC-LP MR1 Beta2 now. Unstable with crashes.
2015-05-24:
New Version - updated CM & PAC sources
2015-05-12/13:
New Version - updated CM & PAC sources
Volume bug on in-call got solved today!
2015-05-01:
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's!
http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Flash it before or after installing the PACROM zip. It contains the zip's
kernel + DualRecovery. Installing the rom zip will overwrite recovery again
so for backups it might be necessary
to flash it always before installing a new zip, e.g.
2015-04-29:
- Screenshots
- Yes! I got it running. After some hours of use, it seems really smooth & snappy. No reboots.
- How I installed everything: Root on Kitkat stock rom, backup TA-partition, install
Dual-recovery, update to Lollipop rooted, make nandroid backup of hole system,
unlock bootloader, flash PACMAN boot.img, wipe data/caches,
flash PACMAN zip + GAPPS ... quite some hours of work.
TESTED - WORKING:
- 2G, 3G, 4G
- wifi, wifi hotspot
- bluetooth audio
- nfc
- usb otg
- GAPPS (mentioned below)
- titanium backup
- PAC customizations (not all tested)
- video playback on youtube, vlc, mxplayer
- camera & video recording
- GPS using Google Maps
- headphone sound
- XZDR recovery (version 2.8.15 not working): http://nut.xperia-files.com/
- FOTA TWRP recovery (persistent in fota kernel partition): http://forum.xda-developers.com/z3-...12-nightly-t3010550/post58854063#post58854063
- M5 kernel (CM12.1 based): http://forum.xda-developers.com/z3-compact/orig-development/kernel-m5-kernel-t3115498
BUGS:
- phone call volume loud / not reducable in dialer app. (skype & whatsapp calls are alright) solved on 150512
- If alarm clock is set active -> reboot leads to normal shutdown -> deactivate alarm for that case
- photo: Little fish-eye effect on short distance (it's not that little actually)
NOT TESTED YET:
- encryption
Installation notes: Unlocked bootloader required
- flash boot.img (rashr on phone/ fastboot on pc), then boot into custom recovery
- wipe cache, wipe art/dalvik cache
- when coming from a different rom wipe data (factory reset)
- when changing between different gapps packages format system may be useful
- flash rom zip
- if needed flash gapps zip
Download PACMAN: https://www.androidfilehost.com/?w=files&flid=30581
Download GAPPS: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Device trees used: https://github.com/filou76/manifest/blob/master/z3c.xml
Credits!!!:
PACMAN project for their great and cool work!! www.pac-rom.com/#Home
All CM developers for giving a solid custom rom ground!!
All Z3C developers who are trying hard to make this great phone ready for daily use, especially those couple of root/bootloader/recovery hackers!! bilbao1 for the great howto root/backup etc! [NUT]'s for this very cool online kernel builder!
Google, of course

Screen shots please...

I guess its a cm based. So we need unlocked bl right?

shakkirk said:
Screen shots please...
Click to expand...
Click to collapse
It's the same as any Lollipop based PAC ROM, so just search the web for pics.
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
Yes.

at least a custom rom for z3c. thanks man for your efforts...

basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
I think PAC is AOSP & CM based. Custom kernel. Unlocked bootloader, yes.

drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
Happy to build actually it's not that difficult with CM device support. Probably I'll build some monthly versions or so...

drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)

becks0r said:
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
Click to expand...
Click to collapse
:good: In case of resurrection remix you only need to add/edit 1 file (local_manifest) to be able to compile a working rom. All the rest it just setting up ubuntu, init/sync repo an start building ...

Hmm it could be a reason to unlock bootloader.,)

XZDualRecovery
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's! http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Just flash it before or after installing the PACROM zip. It contains the original kernel + DualRecovery. CyanogenRecovery really sucks, not even a way to make backups. Now we can

does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!

beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
there's nothing like this included. as far as i know custom roms/ custom kernels can't handle drm keys from TA partition. not sure about flashable drm replacement, i don't think it will work, but maybe it does
perhaps someone knows more about this sony image processing stuff.
isn't that all software based? if so, i could imagine that a good camera app (FV-5 or something like) can bring the same results.

Great work mate. Been running a few hours with the updated boot.img
Hopefully there is no "memory leak"

beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
That fix is only useful on stock Sony based rom's.

bugs update
(1) i found a small, almost funny bug. couldn't reboot to recovery today because phone always ended with shutdown. i desperately flashed the boot.img again but no change. only after deactivating everything i thought not being active at installation the problem disappeared.
well, it's the active alarm, that i use every morning ...
(2) in call volume issue seem's to be somewhere hidden in android_device_sony_z3c/audio/mixer_paths.xml of the repo. just in case someone likes to search :laugh:

I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk

mrrflagg said:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
Hi, thank's for that! I've just reproduced what you wrote. On my phone this is also connected to active alarm clock. It's rebooting fine when alarm is off. So, quite the same as my last post.
I have no suggestion about real bug reports, because of 2 reasons: this is an unofficial build, primarily for myself ... but shared. I would stop building if Z3C would get official PAC support. And I've just started building roms 2 months ago. So, I'm not having the skills (yet) for advanced debugging. Right now it's more like being voluntary apprentice :laugh: ... I'm gonna add your input it into 1st post.
For now stability of this rom is mainly dependent on PACROM itself and official CM support.

Im glad you could reproduce the same bug. I think you have done a great job mate. I'm loving this ROM and appreciate your efforts. I'm trying to figure the dev side of things myself, not having much luck yet.
Sent from my Xperia Z3C using Tapatalk

Good job, m8!
Can someone post a picture, taken by camera on this phone with this rom ?
A picture of a door , or a wall, for example. Any picture featuring a rectangular shape with straight lines.
I had a broblem be4 on CM12 @z3c , the camera ( any camera app ) took pictures, distorting proportions, like there was a fisheye filter applied

[ROM][UNOFFICIAL] LineageOS 11 for D605

*** Disclaimer
Code:
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 the instructions or the linked things before doing anything!
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 and I promise, I will!
Introduction
I decided I wanted a more up-to-date CM11 build, so here it is, a new build of LineageOS 11, for D605!
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
* Quite default LineageOS 11 but with USB OTG and offline charging
Installation instructions
* Under construction
Changelog
* Creating once finished
Downloads
Checksums:
* Uploading once finished
Download
* Uploading once finished
Sources
* https://github.com/Avamander/android_device_lge_d605
* https://github.com/Avamander/android_kernel_lge_d605
FAQ
* Under construction
Thanks To/Credits
Code:
* Varcain
* Puresoul_CZ
So, let me know if you're even interested.
XDA:DevDB Information
LineageOS 11 for D605, ROM for all devices (see above for details)
Contributors
Avamander, Varcain, Puresoul_CZ
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-09-25
Last Updated 2020-07-04

Planned:
* Fix to reallow XPosed

Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?

thePanz said:
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
Click to expand...
Click to collapse
About CRACK, haven't checked, not sure a patch has been released for LOS11, if it has after the build date, let me know and I'll rebuild it.
I used the this https://wiki.lineageos.org/devices/d855/build but replaced d855 in commands with d605 and manually downloaded the sources to the according folders.

@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?

thePanz said:
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
Click to expand...
Click to collapse
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?

Avamander said:
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Click to expand...
Click to collapse
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.

thePanz said:
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
Click to expand...
Click to collapse
Let me know if the latest works. If it doesn't, let me know if TWRP works

Avamander said:
Let me know if the latest works. If it doesn't, let me know if TWRP works
Click to expand...
Click to collapse
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive

thePanz said:
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
Click to expand...
Click to collapse
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.

Avamander said:
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Click to expand...
Click to collapse
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)

thePanz said:
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
Click to expand...
Click to collapse
That means it would still break the signature if I would release a signed image.

Quick update: the offline-charging is not working.
Switching off the phone and connecting the charger will boot up the phone in the default mode, not "only charging".

I know this might be a minor bug but auto brightness doesn't work.

DJ-SMOKE_300 said:
I know this might be a minor bug but auto brightness doesn't work.
Click to expand...
Click to collapse
Never has, never will, there's no brightness sensor hardware.

Avamander said:
Never has, never will, there's no brightness sensor hardware.
Click to expand...
Click to collapse
Oh. Thanks for clearing that up. All in all its mostly stable. :good:

Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.

DJ-SMOKE_300 said:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
Click to expand...
Click to collapse
Seen that happen a few times, but without logs of the crash I can't help you.

1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?
---------- Post added at 23:26 ---------- Previous post was at 23:11 ----------
Avamander said:
(...)
Installation instructions
* Use TWRP, wipe everything, (...)
Click to expand...
Click to collapse
Is there really a reason to clean Internal storage and sdcard?

> 1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
It's more work to create the file for the recovery to verify it. The space is part of the link.
> 2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?[
Nope
> Is there really a reason to clean Internal storage and sdcard?
Internal storage? If you mean /data, yes, but /sdcard doesn't need to be wiped.
As a sidenote, I've been rebuilding the entire system today, will see if that brings back the WiFi.

Better Mobile App

welcome