Kernel & Rom Information:
The kernel which has been included in this CM11 Milestone 9 rom is basically the stock kernel for CM11. So this means no custom tweaks to the source or kernel configuration. The only patches which are being applied in this kernel are the official kernel.org patches, which fix a lot of regressions which have been found until now. This should make the kernel more stable and could potentially also have influence on battery life and memory management. The rom which has been included is the milestone 9 build from cyanogenmod.org. Each milestone build I will release a updated kernel version with it as well. Next milestone build hopefully will include a 3.4.30+ kernel. If you have any problems with this release, or encounter strange behaviour, please report it in this thread. Other questions are also welcome, but please no feature requests.
Before you install CM11.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 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.
Fresh install
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM11 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!
Upgrades from previous CM11:
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.
Download:
Download Kernel Package Only (Kernel 3.4.11) CMKernel.zip
Download Full Rom Package (Kernel 3.4.5) cm-11-20140804-SNAPSHOT-M9-e975.zip
Screenshot:
{
"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"
}
Just a small update on this matter:
I started with updating the android-kernel-gproj from the standard Cyanogenmod sources.
Currently my girlfriend is running a first test kernel updated to 3.4.5 at the moment.
In the coming days I will keep updating the sources, and hope to release a first public test kernel around the CM11 Milestone 9 release date.
So if you're interested keep an eye on the forum.
Greetings PsychoGame
The github which I will push all the sourcecode to is: https://github.com/PsychoGame/lge-kernel-gproj and is located in the CM-11.0 branch.
Once it is considered stable and tested for some time, I will try to get the updated code merged with the Cyanogenmod sources.
This way all official CM builds will make use of the updated kernel source.
I can't make any promises as I am not authorised to make any changes in the official CM kernel sources, so it will depend on the github user "rmcc" I believe to merge my request.
In the meantime I decided on a way to release my kernel as following:
When CM-11 Milestone 9 will be released I will download the zip file from the official Cyanogenmod servers.
The original boot.img in the zip file will be replaced with the updated kernel boot.img.
I have to note that the updated kernel will be exactly the same as original CM kernel, only with updated sourcecode, which means regression fixes etc.
Hopefully I have given enough insight in the course I will follow for now, and feel free to ask any questions.
Greetings PsychoGame
PsychoGame said:
Hello LG Optimus G users,
I'm a linux enthousiast who also likes to play around in Android development.
At the moment I'm using a Samsung Galaxy S Plus which has CM11 with kernel 3.4.99 available.
My girlfriend uses a LG Optimus G, and I saw that the kernel version used is 3.4.0.
Would anyone be interested in a updated kernel?
At the moment of writing it's kernel 3.4.100 which introduces bugfixes, optimalisations and so on.
Also if you're able to help out that is also appreciated.
I know how to patch and compile the kernel, but it's a lot of work to patch up to version 3.4.100 in my own, so if you are willing to help out please leave a message.
Greetings PsychoGame
Click to expand...
Click to collapse
PsychoGame said:
Just a small update on this matter:
I started with updating the android-kernel-gproj from the standard Cyanogenmod sources.
Currently my girlfriend is running a first test kernel updated to 3.4.5 at the moment.
In the coming days I will keep updating the sources, and hope to release a first public test kernel around the CM11 Milestone 9 release date.
So if you're interested keep an eye on the forum.
Greetings PsychoGame
Click to expand...
Click to collapse
PsychoGame said:
The github which I will push all the sourcecode to is: https://github.com/PsychoGame/lge-kernel-gproj and is located in the CM-11.0 branch.
Once it is considered stable and tested for some time, I will try to get the updated code merged with the Cyanogenmod sources.
This way all official CM builds will make use of the updated kernel source.
I can't make any promises as I am not authorised to make any changes in the official CM kernel sources, so it will depend on the github user "rmcc" I believe to merge my request.
In the meantime I decided on a way to release my kernel as following:
When CM-11 Milestone 9 will be released I will download the zip file from the official Cyanogenmod servers.
The original boot.img in the zip file will be replaced with the updated kernel boot.img.
I have to note that the updated kernel will be exactly the same as original CM kernel, only with updated sourcecode, which means regression fixes etc.
Hopefully I have given enough insight in the course I will follow for now, and feel free to ask any questions.
Greetings PsychoGame
Click to expand...
Click to collapse
your efforts and ideas are simply awesome! It will be great if you can do it. gee based ROMs are not fully compatible with E975 and we are stuck at 3.4 kernel version. If you really manage to do this you will be our hero! No one has done it yet (maybe no one has tried) and that there's no response till now to your thread may be because people think it's not possible. But reading your posts I'm really hopeful that you can do it. Keep the good job on.
Also i think yu need to consider the latest kernel sources released fa KK..... Coz CM kernel source is JB one..!!
Sent from my LG-E975 powering Stock 4.4.2 & SOLID Kernel
Big thanks mate!! Will try as soon as it will be available.
hasan4791 said:
Also i think yu need to consider the latest kernel sources released fa KK..... Coz CM kernel source is JB one..!!
Sent from my LG-E975 powering Stock 4.4.2 & SOLID Kernel
Click to expand...
Click to collapse
For now I will stick to the standard kernel, and in the meantime will look into updating kernel to KK sources.
Will need to find out which "device specific" drivers need to be extracted from the current kernel, and implemented in the newer source.
This will take a lot more time than simply patching the current kernel.
It will definitely have my attention, as the next android version seems to be bundled with the 3.10 kernel.
So this will also take some porting.
Greetings PsychoGame
PsychoGame said:
For now I will stick to the standard kernel, and in the meantime will look into updating kernel to KK sources.
Will need to find out which "device specific" drivers need to be extracted from the current kernel, and implemented in the newer source.
This will take a lot more time than simply patching the current kernel.
It will definitely have my attention, as the next android version seems to be bundled with the 3.10 kernel.
So this will also take some porting.
Greetings PsychoGame
Click to expand...
Click to collapse
Thats cool then....we are waiting for another thrill...!!
Thank You, the update Would bei awesome
Sent from my LG-E975 using XDA Premium 4 mobile app
Hello everybody,
This is the first public release of my updated kernel.
I included the official CM11 rom with it, as it is meant to be used in combination with this rom.
Probably it should also work with CM11 based roms, but I do not guarantee it.
If you get strange behaviour with this updated kernel rom please notify me with some steps to reproduce it.
In this case I can find out what went wrong.
Greetings PsychoGame
thanks a lot sir. contact the moderators. It's time to move to development section. Happy to see another hardworking dev here
Hey, is there any info on this Kernel ?
Digidice said:
Hey, is there any info on this Kernel ?
Click to expand...
Click to collapse
The changelogs for this kernel are as follow:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.1
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.2
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.3
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.4
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.5
If you don't want to get through all these changelogs, I will post a summary of the changes later on.
Greetings PsychoGame
On your first post on page one, there are no info about the kernel, what it does etc.
Is that maby in another post ?
PsychoGame said:
The changelogs for this kernel are as follow:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.1
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.2
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.3
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.4
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.5
If you don't want to get through all these changelogs, I will post a summary of the changes later on.
Greetings PsychoGame
Click to expand...
Click to collapse
I'd like to use the updated kernel on PAC MAN ROM. I think it will be very useful if you make a patch that can be used on every CM based ROM, it'll be very useful. also, dt2w and s2w features are appreciated
akahroba said:
I'd like to use the updated kernel on PAC MAN ROM. I think it will be very useful if you make a patch that can be used on every CM based ROM, it'll be very useful. also, dt2w and s2w features are appreciated
Click to expand...
Click to collapse
Hello akahroba,
I will create a update package which will be usable on all roms as well, so a kernel only package.
For people who currently wan't to test the kernel without waiting for the kernel only package it is possible to install the CM11 package from here, make a rom backup of the CM11, flash the rom of choice and restore only the boot.img from the CM11 backup in CWM or TWRP.
I will look into the dt2w and s2w, but this will not be merged in this kernel base as of now.
First will try to get the kernel source base as up-to-date as possible and as close to CM as possible.
When finished with step one will look into other things as for example the 3.10 kernel for the future L release builds and also more CA-codebased sourcecode.
Greetings PsychoGame
Any improvements on Google camera side and third party apps video calling??
arpit85 said:
Any improvements on Google camera side and third party apps video calling??
Click to expand...
Click to collapse
I'm not quite sure if the kernel updates will have major impact on these things.
In my opinion this is more graphics driver side.
I know the driver binary blobs which are used in the Cyanogenmod are a littlebit dated, these have to be updated for the Kitkat release.
I'm also looking into this matter, I have to be carefull not to work on too many things together as this will slow down the overall development process in my opinion.
Greetings PsychoGame
arpit85 said:
Any improvements on Google camera side and third party apps video calling??
Click to expand...
Click to collapse
Kernel source in cm repo is outdated... Its nt stil updated to newer source... Tats t issue with Google camera nt working properly..... Coz in stock kk I can able to use all features of Google camera without ny issues.... For third party video calling issue, i duno wats t prob....!!
Sent from my LG-E975 powering Stock 4.4.2 & SOLID Kernel
hasan4791 said:
Kernel source in cm repo is outdated... Its nt stil updated to newer source... Tats t issue with Google camera nt working properly..... Coz in stock kk I can able to use all features of Google camera without ny issues.... For third party video calling issue, i duno wats t prob....!!
Sent from my LG-E975 powering Stock 4.4.2 & SOLID Kernel
Click to expand...
Click to collapse
Thanks for the info, I wasn't aware of this yet. Will obtain the V20 Kitkat kernel sources from LG and try to extract the device specific sourcecode from it.
This maybe will give me some insight in whats going on with this problem.
It's unfortunate that I can't experiment very much as I would like to as my gf uses it as her primary mobile.
I will try my best to obtain a LG Optimus G of my own as well.
Greetings PsychoGame
Related
WELCOME TO OptiBean RC1 for LG LU6200
RC2 Link is on post # 4
Below are the details of this ROM.
NOTE: I am not responsible for bricking your android phone for installing this customized ROM.
Use it at your own risk but rest assured that this has been tested thoroughly to avoid such errors.
Just post an error report on this thread for further development of this ROM. I also consider DONATIONS.
ROM DETAILS:
Pre-installed Apps:
Holo Launcher HD 1.0.6
XDA Assistant
Airdroid
Flash Player [May not Work on some Apps]
Movie Studio
Rebooter
Torch
Youtube
And some Inverted GAPPS by JustinBean
Tweaks:
Ported from CM10 latest build 4.0.1 JB
Running 3.0.8 Hi1Jason Kernel
Mms app [bubble style tweak] - Created by DeNitE
Build prop tweak
-Internet Speed
-VM Heap size increase
-Better battery life
-Buttery Smooth [Depends on Units sometimes]
-Better Camera/Video Decoding & Encoding
-Faster Reboot
-Faster Application Loading
-And many more
Customized Boot Animation [Droid Razr New]
Beats Audio Modification [For Sound Quality] [Removed}
And many more... I cannot remember All.
{
"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:
[URL="https://www.dropbox.com/s/fpcc1i4fxguhll3/OptiBean_RC1_LU6200_2.zip"]https://www.dropbox.com/s/fpcc1i4fxguhll3/OptiBean_RC1_LU6200_2.zip[/URL]
Installing This ROM?
1. First make a back-up your current ROM. And make sure your phone is rooted and CWM is installed.
2. Wipe data/Factory Reset
3. Wipe Cache
4. Wipe Dalvik Cache
5. Wipe Battery
6. Install from SD Card then Select the File
7. Wait till it is complete then Restart.
8a. For those who backup their contacts in their SD card w/ a VCF file,
if you want to restore it after then you must NOT sign in on your google account or just
click "Not now" then proceed to finish the initial config then restore first the contacts before doing anything else.
8b. For those who backup their contacts using Google Auto Sync and want to restore it,
just follow the on screen instruction and make sure you have internet connection.
9. Enjoy the ROM! Press thanks if you like it and DONATE if want more of it.
Note: After the ROM boots up completely, wait for it to properly scan the SD card as it is still loading.
And there is a possibility that the Camera App will lag at first use but after using it for a while it will be as smooth as butter [based on my experience]
Please Support My Work By Simply Donating to my Account if You like It.
It's not easy for me being here in the Philippines to upload such a file because of slow internet connection.
That is why I need to pay an expensive Connection just to do my work and projects.
Thank you in Advance.
Credits For the Following Persons:
Hi1Jason - For Everything Esp. for the Kernel
JustinBean - For Some Inverted Apps
Astrix from s3forums for the tweaks and tutorials
And for the Testers for risking their phones for using this ROM
Sceen Shoots Already Posted!
NOTE: I don't have my Optimus LU6200 anymore. I upgraded to LTE 2 so I cannot test my new ROM for this Unit, Sorry for cutting you here.
CM10 Screen Shoots
;
;
;
;
;
;
tks!
[ROM] [CM10 port] OptiBean RC2 for LU6200 (JB 4.1.2) Now Available
OptiBean RC2 Intsructions:
1.)First make a nandroid backup
2.) I recommend that you use Hi Recovery v1.0 for LU6200
Link:
http://forum.xda-developers.com/showthread.php?t=1951554
Click to expand...
Click to collapse
3.) After changing your recovery to Hi Recovery,
4.) Wipe System, Wipe Data, Wipe Cache, Wipe Dalvik
5.) Flash ROM [Link Below] and lates JB Gapps [link below]
6.)Restart Phone
Note: You can flash 2 or more file in just a single flashing using Hi1 Recovery,
You can download latest Jelly Bean Gapps Here: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Happy Flashing. Enjoy.
Release Candidate 2 Link: [Download]
http://d-h.st/WY4/
Click to expand...
Click to collapse
Release Candidate 2 Changelogs:
-Latest Stable Build of CM10 JZO54K [JB 4.1.2]
-Latest Baseband
-Latest Kernel build from Hi1Jason [3.2]
-Faster Internet Speed
-VM Heap size increase
-Better battery life
-Much Smoother
-Better Camera/Video Decoding & Encoding
-Faster Reboot
-Faster Application Loading
Fixes:
Long Charging Time Issue Fix
Boot Animation Fix
Some Apps FC fix
Annoying Vibration on Dialer Fix
More APN list support
Bugs:
Please report to me if you found anything on this ROM. I'm happy to work with you guys.
Can we REALLY format the external disk with that rom? I've tried Hi1jason's CM10 v3.0 rom but sim toolkit is not working and has a few bugs. One thing I like with his rom is a longer battery life. More power kababayan!
Hi1jason's CM10 v3.1 is out. Will try it soon.
SIM Toolkit is not Working on CM10 on our phone
devcon69 said:
Can we REALLY format the external disk with that rom? I've tried Hi1jason's CM10 v3.0 rom but sim toolkit is not working and has a few bugs. One thing I like with his rom is a longer battery life. More power kababayan!
Hi1jason's CM10 v3.1 is out. Will try it soon.
Click to expand...
Click to collapse
Well based on search here, Currently, SIM Toolkit will not work on our phone. Maybe on some other countries it'll work. I have used Hi1Jason's kernel for this ROM and I have tweaked it to make it more battery saving. I'll be posting in a while the details of this ROM.
wow wow wow i wanna eat jelly bean....can't wait!!!!
Where is d link?
Thanks in advance.
Sorry for the Delay. I have found some minor bugs while on my final test. I have canceled the upload for some changes.
Awesome Beats will be deleted for some conflicts in the ROM. But I'll post the link of it later if you wish to flash it on your phone.
Meanwhile, this will just be a RC1 version.
Thank You for the Support.
LU6200
How is the battery life, bro?
Read Carefully
BinCanCook said:
How is the battery life, bro?
Click to expand...
Click to collapse
Please Read carefully on my post.
It is already stated on the ROM description.
Thank you.
I'll be posting it tommorow...
JB for LU6200
your dropbox account is locked.
Is there any mirror?
Thank!
Sorry for the inconvenience
BinCanCook said:
your dropbox account is locked.
Is there any mirror?
Thank!
Click to expand...
Click to collapse
I would like to apologize for what hapened. It seems that too many members downloaded my OptiBean RC1. But dont worry, the next link that I will be posting is the RC2 Already.
Please Donate Guys if you like my work.
First of all, thank you for your hard work. It's go great to see someone from the same country I live in developing a rom for this phone! (Im not Filipino though).
By the way, the rom is huge in size. (320mb!) Is this because of Gapps included in the rom? AFAIK, it is against Google's policy to include Gapps in a custom rom. You may have to remove the apps from your rom and link a set of gapps from Goo.im or something similar.
I'm downloading the rom now. Will report back after testing it.
Gapps
pins2u said:
First of all, thank you for your hard work. It's go great to see someone from the same country I live in developing a rom for this phone! (Im not Filipino though).
By the way, the rom is huge in size. (320mb!) Is this because of Gapps included in the rom? AFAIK, it is against Google's policy to include Gapps in a custom rom. You may have to remove the apps from your rom and link a set of gapps from Goo.im or something similar.
I'm downloading the rom now. Will report back after testing it.
Click to expand...
Click to collapse
Actually those are inverted Gapps that I have included. And in my next release it will be based from the latest cm10-M2 from cyanogen MOD... It will be packed with latest features of cm10.
It's just for testing. Because some of the GAPPS are not compatible with it so I have to select those that works.
Don't worry my Boy, I will seperate it once everything is in order. So for now, it will be included since it is not really released by google itself. It has been modified by some devs here so no worries.
mac20dnangel said:
Actually those are inverted Gapps that I have included. And in my next release it will be based from the latest cm10-M2 from cyanogen MOD... It will be packed with latest features of cm10.
It's just for testing. Because some of the GAPPS are not compatible with it so I have to select those that works.
Don't worry my Boy, I will seperate it once everything is in order. So for now, it will be included since it is not really released by google itself. It has been modified by some devs here so no worries.
Click to expand...
Click to collapse
Okay. it was just my 2 cents.
Anyway, I've been running the rom for past 2 days and it looks fine.
Here are just a few things that I want to address...
- Led flashlight toggle cannot be enabled for the notification bar.
- Can notice very minor graphical glitches found in UI animation.
- There seems to be some battery drain. I'm not sure what causes this. (Could be wifi?) It's not just for your rom, but prevails all other roms for this phone. For other devices that I had (see my signature), 1% or less per minute with WIFI on was very normal. but I'm getting at least 3 to 5% per hour now which is not satisfactory at all. Do you have any information on this?
RC2 os Coming
pins2u said:
Okay. it was just my 2 cents.
Anyway, I've been running the rom for past 2 days and it looks fine.
Here are just a few things that I want to address...
- Led flashlight toggle cannot be enabled for the notification bar.
- Can notice very minor graphical glitches found in UI animation.
- There seems to be some battery drain. I'm not sure what causes this. (Could be wifi?) It's not just for your rom, but prevails all other roms for this phone. For other devices that I had (see my signature), 1% or less per minute with WIFI on was very normal. but I'm getting at least 3 to 5% per hour now which is not satisfactory at all. Do you have any information on this?
Click to expand...
Click to collapse
Thank you by the way for your support. Your donation is a big motivation to me... Im currently working on the latest cm10-M2 build by cyanogen and Im in my half way... Im just kind of busy in my work and school.
Your feedback is much appreciated.
Wifi issue is caused by the tweak that I have made to its wifi connection.. Maybe I'll try to make fix it with the latest tweaks..
RC2 build info:
Latest JB build 4.1.2
Latest Superuser
Latest Recovery 6.0.1.5
System Apps updated
S3 camera app ported
Better sound/music app
And more...
Need all your support.
Please have some donations.
Thank you..
Sometimes i can't make system menu appear (which has pover-off, reboot, bootloader)
I thought it's maybe not a problem resulting from my hardware
still observing
((I have resolved it via installing a apk, rebooter
Your rom let me abandon MIUI ( ´ ▽ ` )ﾉ
THX!!!!!!!
Sent from my LG-LU6200
Thank You
wildsky said:
Sometimes i can't make system menu appear (which has pover-off, reboot, bootloader)
I thought it's maybe not a problem resulting from my hardware
still observing
((I have resolved it via installing a apk, rebooter
Your rom let me abandon MIUI ( ´ ▽ ` )ﾉ
THX!!!!!!!
Sent from my LG-LU6200
Click to expand...
Click to collapse
Thank You for your Support.!!!!
Im currently working on my next version of OptiBean.
It's now more stable than the first release.
Made some customization.
Remove some apps and added new ones.
Running 4.1.2 - Updated JellyBean Version
And Powered by the latest kernel made by hi1jason
All thanks to him.
Watch out for the next Release Candidate of OptiBean ROM for Lu6200!
If you like my work. Don't forget to drop coins on my account. It will help me do more projects.
Press thank if you like it.
GUYS,
GOOD NEWS. I'M DONE WITH MY LATEST BUILD OF OPTIBEAN AND ITS BEEN ON BETA-TESTING STAGE AND CURRENTLY RUNNING SMOOTH.
HOPEFULLY I COULD POST IT AS SOON AS POSSIBLE.
JUST DONATE IF YOU WANT TO, BUT IF NOT THEN YOU ARE NOT FORCE. BETTER TO SHUT YOUR MOUTH IF YOU DON'T HAVE ANY GOOD THINGS TO SAY.
CHANGES:
Latest JB Build (CM10) 4.1.2
Latest Recovery 6.0.1.5
Latest Hi1Jason 3.1JB Kernel
Latest Apps
Remove/Separated GAPPS
More tweaks and fix
New Boot Animation
Added new apps
Ported SG III Camera
and more....
SOON TO BE RELEASED (",)
No harsh feeling here but donation should be pure giving. What you are asking starts to look more like selling as you emphasize the word "donation" in every post you make.
If you really need funds to continue, better monetize your rom. Create some locked features, and make an app that unlocks them and sell it on Play Store.
Sent from my GT-P6200 using xda app-developers app
Hello Everyone!!
So here is a new ROM I compiled yesterday, it does have a lot of features and it is called SONIC OPEN KANG PROJECT
I didn't open a new thread for it because I'm not gonna be updating it unless many users encourage me to do so...
Anyway I thought I should share it with you guys, for who ever wanna test it
Here is this ROM's features:
http://sonic-developers.com/?page_id=160
Also here is a quick review for the ROM:
And for more info visit their website:
http://sonic-developers.com
Download Link:
I've started uploading my files to androidfilehost.com , hoping you like it more than Dev-host
SOKP-MS-04-KK444-KTU84Q-20140726-amami.zip
Here are my screenhots as well:
Hello Guys,
Since our lovely Z1C is relatively new, it doesn't have many CM based ROMs, so I thought why not porting some
from the closest phone to ours (which is obviously Xperia Z1).
So I'll be presenting five ports for five ROMs as mentioned in the title, but I'm gonna start with a simple guide for how to port the ROM yourselves
All you have to do to port a CM11 based ROM from Z1 is:
Download the Z1 ROM and extract it wherever you want
Open META-INF\com\google\android\updater-script with any text editor and remove first five lines (assert)
Download This for old builds, and This for new builds, then unzip it
Copy and replace "boot.img" from the previous zip to your Z1 ROM
Copy and replace "modules" folder to system\lib\modules in your Z1 ROM
Open system/build.prop with any text editor and change this value:
Code:
# Graphics
ro.sf.lcd_density=480
to become:
Code:
# Graphics
ro.sf.lcd_density=320
that is it, although there are optional things you may do before compressing the ported ROM:
In system/build.prop search for honami and replace them with amami
And then search for C6903 and replace them with D5503
Also you may wonna add "Compact" here:
ro.product.model=Xperia Z1 Compact
Click to expand...
Click to collapse
You may also open META-INF\com\android\metadata and do the same replaces
Resign the ROM.zip after compressing it
Important Notes:
DO THIS ON YOUR OWN RISK
You must be running KK ROM before flashing these ROMs down below
This method won't work on Slimkat, although you can grab it from Here
All bugs in these ROMs are related to the original ROM not issues caused by posting
Fell free to report any bugs you face though, and I'll enlist them in known issues
PacMan ROM and MoKee ROM are officially supported, so there is no need to port them
Instructions for all ROMs down below:
Copy the zip to your device
Reboot into recovery
Backup of your system (optional)
Do a factory reset and format [/system]
Flash the Zip
XenonHD & BeanStalk
:::The XenonHD ROM:::
This was built in (2014-04-02) [Build 5]
It contains CM11 FXP312 Kernel
Zip is resigned
Screenshots:
Download link:
update-XenonHD-04-02-14-signed-amami.zip - 238.44 MB
New build's port can be found here: (Not tested by me)
http://forum.xda-developers.com/showthread.php?p=53365536
For more info and screenshots, visit the Original Thread
:::The BeanStalk ROM:::
This was built in (2014-03-11) [Build 3]
It contains It contains CM11 FXP312 Kernel
It has random reboot bug
Zip is resigned
Screenshots:
Download link:
BeanStalk-4.4.255-20140311-amami.zip - 251.39 MB
For more info and screenshots, visit the Original Thread
:::Gapps:::
GApps Standard 4.4.2 (10/5)
Removes AOSP Camera and AOSP Gallery and Replaces it with the Google variants
Removes AOSP Launcher2/Launcher 3 and CM Trebuchet and Replaces it with Google Now Launcher
Adds Google Search aka Google Now
All necessary syncing apks and libs
GApps Minimal 4.4.2 (10/5)
~20 MB
Playstore
Syncing apks and libs, etc.
Google Camera 4.4.2 (16/1)
Automatically removes AOSP Camera/Gallery and adds Google Camera/Gallery
FaceLock 4.4.2 (10/5)
Adds Face unlock
GenieWidget 4.4.2 (10/5)
Adds stock news and weather widget
AOSP Calendar Sync 4.4.2 (16/1)
Adds syncing ability for AOSP Calendar (not in Core or Standard packages)
AOSP Browser Sync 4.4.2 (16/1)
Adds syncing ability for AOSP Browser (not in Core or Standard packages)
This was copied and pasted from Original Thread (you can find more Gapps mirrors here)
Personally I prefer [and have tested] the minimal Gapps package, it is the best
Great work!
I wonder if you would do Slimrom also, it is a mainstream ROM with many innovations that other ROMs have copied.
[edit] Duh I just read your comment about slimkat. That'll learn me to read OPs properly...
wow, this looks good, i think ill try MoKee, just one question, is everything working ?
Just flash rom and some gapps ?
juried said:
Great work!
I wonder if you would do Slimrom also, it is a mainstream ROM with many innovations that other ROMs have copied.
[edit] Duh I just read your comment about slimkat. That'll learn me to read OPs properly...
Click to expand...
Click to collapse
actually, just today; @akshaybz has opened a thread for slimkat (not ported, compiled) here:
[ROM][4.4.2][KOT49H] SlimKat - Amami [Build 4][Alpha][UNOFFICIAL]
Enjoy
xhizors said:
wow, this looks good, i think ill try MoKee, just one question, is everything working ?
Just flash rom and some gapps ?
Click to expand...
Click to collapse
Well I didn't test everything, but the ROM was flawless, wifi is OK
Yes just flash rom and some gapps, try it and give a nice feedback
Might be a dumb question, but will updating them through the rom settings mess anything up?
RevokOne said:
Might be a dumb question, but will updating them through the rom settings mess anything up?
Click to expand...
Click to collapse
I don't expect updates to appear in the ROM's settings, but if they do,
yes updating that way should mess up a lot, it should make a bootloop.
anyway if you see an update for the ROM you're using, just tell me and I'll port the new release right away
omarainea said:
I don't expect updates to appear in the ROM's settings, but if they do,
yes updating that way should mess up a lot, it should make a bootloop.
anyway if you see an update for the ROM you're using, just tell me and I'll port the new release right away
Click to expand...
Click to collapse
I been building ROMs on linux trying and testing build from source..Im new to it and the device has been a long time HTC user. So guess all are from Z1 with afew changes you posted similar to the stock port way. I built a few roms so apart from the one I'm supporting. Carbon and PAC ROM has shown
Sent from my Xperia Z1 Compact using Tapatalk
Thread Updated
Ported MoKee 2014-03-31 Release
Ported Carbon 2014-04-01 (Build 2)
Also updated kernel in OP and in these two builds to 3.4.0 CM11 gb37510f From FXP313
I think I'll be updating the thread every week from now on, until these ROMs get a compiled version
Enjoy
How are the cameras qualities on these roms?
---
Sendt fra LG G Pad
slonn said:
How are the cameras qualities on these roms?
---
Sendt fra LG G Pad
Click to expand...
Click to collapse
Exactly like in CM11.0
omarainea said:
Exactly like in CM11.0
Click to expand...
Click to collapse
And how exactly is the quality in CM11, I can't seem to find a definitive answer in either CM thread?
Any updates on the roms btw?
Cheers! :good:
Thread Updated
e2zippo said:
And how exactly is the quality in CM11, I can't seem to find a definitive answer in either CM thread?
Click to expand...
Click to collapse
I don't know how to describe its quality, I think the best way to know is by trying
e2zippo said:
Any updates on the roms btw?
Click to expand...
Click to collapse
Yeah it's been a week, so here are the Updates of this week:
Updated Carbon ROM to build 4 (2014-04-09)
Updated MoKee ROM to build 2014-04-04 (its kernel was updated to FXP314)
Added XenonHD ROM latest release build 5 [2014-04-02] (download link in second post)
it is very customizable (can't describe it enough)
you can check more info about it in its main thread
about the kernel update, it seems like FXP team have messed up thier kernel a little
so when I tried it on Carbon and XenonHD I got some sort of bootloop,
but it worked fine on MoKee, so MoKee is the only ROM that has FXP314 kernel,
I don't recommended anyone to use it for porting so I didn't upload it
omarainea said:
about the kernel update, it seems like FXP team have messed up thier kernel a little
so when I tried it on Carbon and XenonHD I got some sort of bootloop,
but it worked fine on MoKee, so MoKee is the only ROM that has FXP314 kernel,
I don't recommended anyone to use it for porting so I didn't upload it
Click to expand...
Click to collapse
Actually the problem is not much with the latest kernel, but rather with the ROMs:
Recently there was a huge changeset merged in CM tree, among other things it took in kernel a lot of CAF code\blobs from 4.4 Sony sources, and Xperia CM ROM was rebased on this CAF kernel.
It means, that the ROMs based on CM must be rebuild using latest sources, otherwise they'll have a bootloop with the new CAF kernel =)
TheQwertiest said:
Actually the problem is not much with the latest kernel, but rather with the ROMs:
Recently there was a huge changeset merged in CM tree, among other things it took in kernel a lot of CAF code\blobs from 4.4 Sony sources, and Xperia CM ROM was rebased on this CAF kernel.
It means, that the ROMs based on CM must be rebuild using latest sources, otherwise they'll have a bootloop with the new CAF kernel =)
Click to expand...
Click to collapse
Huh, Thanks for the info bro,
seems like I should read more very now and then to know this kind of stuff.
Thread Updated
Added Paranoid Android ROM
This was built in (2014-04-15)
It contains CM11 20140410-Nightly kernel
Updated MoKee ROM
This was built in (2014-04-14)
The ROM was deodexed (original ROM was odexed)
It contains CM11 20140410-Nightly kernel
hi, should i have a unlock bootloader for test this roms? i can´t unlock it
canteo said:
hi, should i have a unlock bootloader for test this roms? i can´t unlock it
Click to expand...
Click to collapse
unfortunately yes, if you want to flash a custom kernel, you have to have an unlocked bootloader (and that is required to flash custom ROM)
{
"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"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
THIS ROM REACHED IT'S END OF LIFE (EOL). NO NEW BUILDS. Last stable build is one from 16.02.2016.
These builds are UNOFFICIAL builds for our device, and will work on every E98x variant (so that includes E980, E981, E985, E986, E988, E989, I've tested it on E988). I took some liberty and lots of my free time to bring this one to us all, so I hope you'll enjoy as much as possible.
Also, there is unofficialy-unofficial support for F240 variants via flashable custom kernel.
Please, to avoid asking already answered questions, read post #2 (titled as README.md) and search though the tread.
Downloads:
You can download latest builds from BasketBuild* or Android File Host or via included OTA app, if you're already using one of SlimLP previous builds.
* Basketbuild contains only builds after 29.11.2015, if you need older builds, please, use AFH.
To use on F240x (Korean & similar variants), you'll need to flash F240x specific kernel. You can use my official kernel (more info & download links in post #2) or WildKernel.
GAPPS:
Use Slim GAPPS for 5.1.1 (available here), use my pico build of OpenGApps (look under "Goodies" in second post) or download from The Open GApps Project
Changelog:
Since changelog is getting a bit too big for a forum post, I've moved it to my GitHub. Please, for full changelog click here
IMPORTANT:
For those still flashing latest build of this ROM, please use kernel from this link. It has fixed issues with LMK which made device go around and kill everything.
README.md
This is unofficial, fully customized build of SlimLP for our device, based on my device and kernel sources.
Device sources can be found here, while kernel sources can be found here.
Keep in mind that Slim is still in beta so there are more features to come.
Kernel features:
- Governors: Intellidemand, Intelliactive, Intellimm, Wheatley, onDemandPlus, DanceDance, adaptive, smartass2, interactiveX, ondemand, userspace, powersave, interactive, performance, msm_dcvs
- Hotplug: MPDecision (disabled by default) and Faux's Intelliplug (default one)
- Thermal control: Faux's intellithermal
- additional schedulers: VR, SIO, SIO+, FIOPS, ZEN and default stock ones
- Million and one TCP cong. alghoritm
- Faux Sound Control
- Fast charge (up to 1.5A)
- Underclocking and overclocking support
- Patched GPU drivers
Device source changes:
- Fully working RIL (thanks to rmcc for fixing this finally),
- Enabled init.d,
- Fully functional LiveDisplay (reverted from new, shiny and crashy interface to old, working one),
- Updated build fingerprint
- Updated device info
- Added policy for running V4A without SELinux permissive
- Density changed to 400, device screen feels better that way
- Changed gps.conf
- Fixes for camera (thanks to Emmanuel U)
- Fixes for screen flickering
- Added some missing options from stock build.prop
- much more on git
As with every device, some changes may introduce instabilities and problems. Please, don't hesitate to tell me here (or PM me) about them, but if you really want something I can't reproduce fixed, you need to provide me some logs. Also, first rule of ROM development - don't ask for ETAs (and I really mean that, next one with question in 'when' format will be blatantly ignored, don't say I didn't warn you).
INSTALLATION:
0) Backup your app data, messages, contacts etc... it's your responsibility.
1) Download ROM zip file, MD5 file (not necessary) and GAPPS; put them on your phone,
2) Make sure you have fully working recovery. Recommended is TWRP 2.8.7.0, maintained by nerdyblonde (big thanks!)
3) Go into the recovery, make a backup first, then wipe /system, /data, /cache & dalvik-cache
4) Install ZIPs from recovery (ROM zip first, GAPPS and additions later)
5) Reboot and enjoy
Always use latest build, unless told & stated otherwise.
UPDATING:
1-a) Download ROM zip file from thread or via OTA app
1-b) Download MD5 file (not necessary, but not a bad idea too)
1-c) Download newer GAPPS version (your previous GAPPS package will be preserved, do this in case you simply want to update/change package)
2) Boot into recovery
3) Create a backup! (Always have a backup. Don't say I didn't warn you...)
4) Flash ROM zip, GAPPS and other goodies you like.
FOR F240x USERS:
You have two kernels to choose between:
- WildKernel (maintained by Emmanuel U, big thanks from me)
- zeKrnl ("official" SlimLP for E98x/F240 kernel, maintained by me, see next paragraph for download links)
Download links for zeKrnl (current: v1.8_lollipop-f240x):
- Build 19.10.2015 (initial release): link
- Build 04.11.2015 (e980 follow-up): link
- Build 19.02.2016 (e980 follow-up): [url removed] (broken)
P.S. v1.8 won't work on other ROMs. You have been warned.
To make NFC work (as mentioned in this post):
syyune said:
3. As for NFC, I found a tip how to make it work in a Korean forum a few days ago. That is, just remove /system/vendor/firmware/libpn544_fw.so.
I applied that tip and it worked! Not only I can turn on and off and make NFC work, but also it didn't prevent the system to go into deep sleep.
If you can include this patch into your kernel, it would be more perfect.
Click to expand...
Click to collapse
Big thanks to syyune for finding that out and all testing provided.
Also, if you encounter problems with wireless (it works on first boot, but can't be enabled after that etc.), please flash this fix and report back. That zip will replace e980 wireless firmware with one from stock F240 ROM. @Sam Ash was kind enough to provide files and to test my theory, so you should give him some kudos.
ViPER4Android:
V4A is now included and default (instead of buggy and stupid AudioFX). I haven't pre-set it because I know that quality profile depends on user and I didn't want to fiddle with that - so it's up to you to choose quality level after first app run and let app install modules.
SCREENSHOTS:
XDA is forum for Android fans & power users, not an image hosting site, so please visit this imgur gallery.. More screenshots will be added as soon as there is a need for that
THEMES:
Slim for E98x supports RRO Layers (patched for Layers L1 and Layers L2.1 support), with Layers Manager preincluded in ROM and theme backup script (no need to reinstall theme after dirty flash anymore) To those who will ask: no, I haven't included any themes, that's your job
XPOSED FRAMEWORK
If you can't get official Xposed to run, try with Wanam Xposed.
BUGS & ERRORS:
If you encounter an error, please, don't hesitate to pull logs (logcat and kmsg, don't forget kmsg!) from your device and send them to me. That's the only way I could fix if something wrong, because not every device and not every user is the same. If something works on my device, maybe won't work on yours; if I encounter some other bugs, maybe you won't; so yeah, please, if you encounter something I don't know about, logs, logs, logs and logs.
Also, don't expect support if ROM flashed on your device is patched or modified in any way (for example: Lucky patcher and similar c***) because I won't simply answer to those questions. I'll tolerate Xposed simply because I know lots of you love that little addition, but c*** like Lucky patcher and other hacks aren't welcome.
TL;DR: "kmsg & logcat or it didn't happen" policy applies to all bugs, crashes, annoyances etc.
T-Mobile and other users with in-call sound/mic problems
Check this solution: [link] or try any of fixes available on the forum.
Bluetooth issues:
Flash this zip and let me know does it work. Big thanks to zombigrn for experimenting and making this zip!
Keep in mind that on newer (02.11.2015 and later) builds, those files are already included.
GOODIES:
1) zeKrnl test builds:
Since zeKrnl is (kind of) constantly developed, I've decided to upload tested beta builds with changes and fixes for everyone interested enough to test them. You can grab latest test builds by clicking on the link for your variant (both e980 and f240, but builds only for Slim)
Build 14112015
Build 23112015
Build 26.11.2015 (e980)/28.11.2015 (F240x)
2) Custom GAPPS pico package
Since I'm building a bi-weekly zip of openGAPPS pico package, I've decided to add links to current download (since it's displayed in OTA app). Current version is from 23.11.2015 and can be downloaded from here. THIS HAS BEEN DISCONTINUED!
EVERYTHING ELSE:
Please make sure you have read the complete forum (or at least did a search) before you ask questions. Be nice to others. Be nice to yourself.
reserved2
thanks man, we'll give it a try !!
Excuse me for my bad english , will have some screenshots ?
4.4.4 rom did Pac could publish for more fans? sorry for the Off topic
Sweet!!! Thank goodness hopefully call audio is working and text I'll deal with the rest lol
javi1609 said:
thanks man, we'll give it a try !!
Excuse me for my bad english , will have some screenshots ?
4.4.4 rom did Pac could publish for more fans? sorry for the Off topic
Click to expand...
Click to collapse
I'll make some shots later, there isn't too much to be shown right now since rom is in Beta and this is first buid.
You can download PAC 4.4.4 with custom kernel from my AFH (see my signature )
crashpsycho said:
Sweet!!! Thank goodness hopefully call audio is working and text I'll deal with the rest lol
Click to expand...
Click to collapse
Well, call audio wasn't tested, but SMS is working normally. Phone takes maybe 30-40 seconds to connect to network (damn old libs) after boot but after that, everything is OK.
And to all of you who are testing it: first boot just takes time, it's not my fault.
Can you build one for F240x?
Can you try running it with Emmanuel's kernel and test if it boots? Also, do you have device sources for F240?
I don't know the differences in sources, that's why I'm asking you.
ShadySquirrel said:
Can you try running it with Emmanuel's kernel and test if it boots? Also, do you have device sources for F240?
I don't know the differences in sources, that's why I'm asking you.
Click to expand...
Click to collapse
For device sources, I don't have, but for kernel sources, there is @Genie's here https://github.com/AOSO
And @Emmanuel U here: http://forum.xda-developers.com/opt...rnel-wildkernel-build-1-featurlicous-t3069629
I'll test a bit later. Will this ROM be updated frequently?
---------- Post added at 08:04 ---------- Previous post was at 08:03 ----------
Most Custom ROMS are just one shot, like one build then, GONE! Will this be continued like BP or COMMOTIO or CM?
ShadySquirrel said:
Can you try running it with Emmanuel's kernel and test if it boots? Also, do you have device sources for F240?
I don't know the differences in sources, that's why I'm asking you.
Click to expand...
Click to collapse
E980 roms should boot on f240x devices if they flash a f240x kernel. However some users occasionally report wifi issues, idk if caused by using an e980 rom.
But there isn't too much changed between both gpro devices, majority of the changes lie in the kernel.
Now. I'm using your Rom since you uploaded and posted it there. I have now 1 issue: i geht random black screens. HW overlay doesnt help. I must reboot my device! If i usw The camera: black screen too. Tested with snapdragon camera, stock and Google.
I found a bug: can't dissable NFC. I must delete NFC.apk...
My Idea for The 2nd update: include The quickboot apps into your Rom. Its possible to enable via developer settings, but doesn't help, if The files missing. I flashed them ans found The link in xda.
2nd idea: Kernel Mods. On some other lollipop Roms my phone charges faster. I think you must edit somethink in The kernel... I'm using a 2.1A charger.
If you want more bugs then wait 12h. You'll get all bugs, which i can find. I'll test wifi, call, Bluetooth, IR remote, etc. Everything.
MitoTakatori said:
For device sources, I don't have, but for kernel sources, there is @Genie's here https://github.com/AOSO
And @Emmanuel U here: http://forum.xda-developers.com/opt...rnel-wildkernel-build-1-featurlicous-t3069629
I'll test a bit later. Will this ROM be updated frequently?
---------- Post added at 08:04 ---------- Previous post was at 08:03 ----------
Most Custom ROMS are just one shot, like one build then, GONE! Will this be continued like BP or COMMOTIO or CM?
Click to expand...
Click to collapse
I'll give my best to put at least two updates per month. I'm preparing a new build right now (added stuff to kernel, added Layers support
etc.) and I'll start porting to another ROM soon so you'll be covered
I'll check Emmanuel's sources tomorrow after exam, it's 3 am here right now, and I'll try to make a build.
Emmanuel U said:
E980 roms should boot on f240x devices if they flash a f240x kernel. However some users occasionally report wifi issues, idk if caused by using an e980 rom.
But there isn't too much changed between both gpro devices, majority of the changes lie in the kernel.
Click to expand...
Click to collapse
I'll take a look at your sources, thank you for bringing that device up.
Sent from my LG-E980 using XDA Free mobile app
ShadySquirrel said:
I'll give my best to put at least two updates per month. I'm preparing a new build right now (added stuff to kernel, added Layers support
etc.) and I'll start porting to another ROM soon so you'll be covered
I'll check Emmanuel's sources tomorrow after exam, it's 3 am here right now, and I'll try to make a build.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! That is awesome. :good:
Maybe work with brother @Emmanuel U for the kenel for F240x. I am willing to test any builds whether kernel or ROM. As long as it's for F240x.
battlekaier said:
Now. I'm using your Rom since you uploaded and posted it there. I have now 1 issue: i geht random black screens. HW overlay doesnt help. I must reboot my device! If i usw The camera: black screen too. Tested with snapdragon camera, stock and Google.
I found a bug: can't dissable NFC. I must delete NFC.apk...
My Idea for The 2nd update: include The quickboot apps into your Rom. Its possible to enable via developer settings, but doesn't help, if The files missing. I flashed them ans found The link in xda.
2nd idea: Kernel Mods. On some other lollipop Roms my phone charges faster. I think you must edit somethink in The kernel... I'm using a 2.1A charger.
If you want more bugs then wait 12h. You'll get all bugs, which i can find. I'll test wifi, call, Bluetooth, IR remote, etc. Everything.
Click to expand...
Click to collapse
Random blackout is because of something else (connected to Live Display it looks). I'm working on that right now, don't worry.
Kernel has fast charge, you'll have to enable it via some kernel app (Tame, Kernel Adiutor...). Max is I think 1.2A, my phone charged under 2h on 2A charger.
I'll check out for other stuff, blackouts and some other stuff are my primary now.
Sent from my LG-E980 using XDA Free mobile app
MitoTakatori said:
Thanks! That is awesome. :good:
Maybe work with brother @Emmanuel U for the kenel for F240x. I am willing to test any builds whether kernel or ROM. As long as it's for F240x.
Click to expand...
Click to collapse
Thanks, I'll see what I can do. In the meantime, try running it with his kernel, and if it works and you don't mind that your device is named as E980, I'll put a build for you.
Sent via carrier pigeon.
Hm. My battery is dying so i need up to 3hours to charge. And that with fast charge...
---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
Maybe can you buy me a zerolemon battery and send me? I'll pay everything. Shipping, battery, etc. Don't worry. Zerolemon dont ship to germany. :|
battlekaier said:
Hm. My battery is dying so i need up to 3hours to charge. And that with fast charge...
---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
Maybe can you buy me a zerolemon battery and send me? I'll pay everything. Shipping, battery, etc. Don't worry. Zerolemon dont ship to germany. :|
Click to expand...
Click to collapse
Get a new battery as soon as possible, no charger or kernel mod will help you with that.
ZL doesn't ship here, too xD
Sent via carrier pigeon.
Without fast charger i need up to 8hours...
I think i buy zerolemon from eBay. They send to germany <3
SLIMLP + SLIM GAPPS + WK#5
Booted. I'll try with xposed if it works.
---------- Post added at 10:02 ---------- Previous post was at 09:56 ----------
No theme engine?
MitoTakatori said:
SLIMLP + SLIM GAPPS + WK#5
Booted. I'll try with xposed if it works.
---------- Post added at 10:02 ---------- Previous post was at 09:56 ----------
No theme engine?
Click to expand...
Click to collapse
No, Slim doesn't support themes yet, so I've patched sources to include Layers, it will be included in next build.
I tapped on submit too fast. Ok, I'll check sources tomorrow and try to build. Thank you for testing this
Sent via carrier pigeon.
{
"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"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* 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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01
Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me
FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.
Thanks for posting this rom. Thank you for your awesome developing.
Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks
great work and z3 compact?
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly
mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.
2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!
cm14.1 wowww :good:
After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?
OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18
Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again
Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...
Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?
Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).
...anyone gotten Xposed Framework installed/working with this? Halp
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this
@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.
Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk
New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers
March update is online. Enjoy!
Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned
People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188
The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk